Surface WC1 nav sphere radius and encounter titles from MODULE Section 1

[Copilot]

Two documented fields in WC1 MODULE files were never parsed: nav point sphere radii (byte 31 of each nav record) and encounter title strings (Section 1, offset 1564).

Nav point sphere radius

NavPoint.Radius existed in the model but was always 0. The parser skipped byte 31 (Sphere radius × 1000) and jumped straight to coordinates at byte 32.

// ModuleParser.cs — ParseNavPoints
int radius = data[off + 31] * 1000;  // was missing entirely
// ...
mission.NavPoints.Add(new NavPoint { ..., Radius = radius, ... });

Encounter titles (Section 1)

Section 1 (4928 bytes at offset 1564) stores encounter flavor text as 4 difficulty pools × 16 sortie slots × 77-byte records. Adds string[] EncounterTitles (length 4, indexed Beginner/Easy/Hard/Ace) to Mission; slot resolved via sortie % 16.

Surfaced in output

• Parser CLI: prints Encounter: Beginner: "12:00 at O.K. Corral" / ... per mission when non-empty; nav lines now include radius=N when > 0
• Viewer: nav detail panel shows "Radius" row when non-zero
• JSON/XML exports: EncounterTitles array included in all WC1 mission exports

Docs

• WC1-MODULE-FORMAT.md: added Section 1 layout description
• WCMissionParser/README.md: updated export schema and Known Limitations

Original prompt

What's next to work on for this project?

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.