Verify actual native-generated spell damage and resource outcomes

Add actual generated spell-damage coverage for client issue #1 (closed), extending the existing native packet bridge beyond supplied one-point hits. Retain 245 packets from client logic/probe d9f1e1db5386581b5a9ebda6fe1b68ed6bf34250 with character/monster inputs, per-target sums, SHA256 checks and exact binary provenance.

NativeMagicPackets validates every generated packet and enforces coverage of all 21 ordinary spell IDs, low/high ranks, original per-rank hit/target counts and amplification combinations. NativeMagicOutcomes delivers the bytes to real MagicDamageHandler instances in the existing disposable non-GM Beginner fixtures, checking actual target HP, effective MP, unchanged ammunition/currency, failed and unlearned casts. Element/MDEF examples, both Compositions, changed INT/MATK and misses are included. The existing validation-only CI job now runs the generated protocol check.

Local validation: 245 generated protocol cases and the complete disposable running-server suite passed (6,466 assertions, including unchanged regressions). The matching client native probe passed 790 checks. An initially missing anti-cheat fixture object was corrected; failed-cast coverage now requires real validation instead of accepting exception-based early exits.

No server production combat logic changes. Critical/cap semantics, status-modified defenses, secondary spell effects, native input, action timing, foreign rendering and lifecycle remain open; complete skill support is not certified. Related https://gitlab.mapplestrudel.com/idanc/mapplestrudel-client/-/issues/1 and #42, neither closed. Depends on !85 (which depends on !84). No merge or deployment; internal Docker/tmpfs database testing never connects to campaign state.