v0.10.0 — EA's developer menu, Story scenes on demand, the play-test recorder

This release brings back the debug menu EA's developers used, which the retail game can never
open, and adds the tools used to find and report short-lived problems: a play-test recorder with
one-button bug bundles, and a way to start any Story scene without a save.

Changes

• The developer menu, restored. The game still contains EA's debug menu, but the module
  that runs it was cut off from the retail build. The port rebuilds that module from outside the
  game, so the menu works again: open the overlay (F1), go to Debug, and press Developer
  menu (or start with RECOMP_DEV_MODULE=1). From it you can:

  • set up any match (MODE - GAME): the match type (single, tag, three- and four-way,
    handicap), up to four fighters, each as the player or a CPU at three levels, and the venue;
  • play any Story scene (MODE - REAL TIME CINEMA), chosen on the CINEMA line;
  • look at a venue (MODE - STAGE VIEWER): its objects, morphs, environment attacks and
    the memory it takes;
  • and open the animation viewer, the create-player screen, the crowd test and the Blazin viewer.

  Every line and control is described in The developer menu.

• Any Story scene, in one step. The overlay's Debug tab plays a chosen scene (Play
  scene) from the main menu, with any profile, even a new one, and without going through
  Story. It returns to the main menu afterwards. RECOMP_SCENE=sc12 does the same at start-up, and
  python3 scripts/scenarios.py scene sc12 plays a scene and saves a contact sheet of it
  (guide). Several scenes can be played in one session.

• Play-test recorder and bug bundles. With Record play-tests on (launcher or overlay,
  Debug tab), each session keeps a frame-time table, the game's events, the mixed audio and
  the last 30 seconds of pictures. F9, View + left stick click on a controller, or the
  overlay's Mark a bug here saves the last seconds as a bug bundle to attach to a report. A
  crash or a hang saves one by itself. scripts/bug-bundle.py reads a bundle and points out
  hitches, picture flashes, black frames, audio gaps and clicks
  (guide). The frame table also counts texture uploads, cache
  evictions and the texture cache's size.

• Test tools for contributors: scenario fixtures and generated fight routes
  (scripts/scenarios.py), crowd test controls (scripts/crowd-lab.py), and agent tooling
  (scripts/triage.py, one shared AGENTS.md).

• CI now compiles the game-side code with MSVC (hooks, patches, the overlay), without
  game code, so a Windows compiler problem shows in CI instead of in Setup.

• Includes the v0.9.3 audio fixes. The toolkit is pinned at 5445b73: the v0.9.3 audio line
  plus asynchronous picture read-back (Direct3D 11 and Vulkan) and texture-cache statistics.

Validation

macOS (Apple Silicon): the developer menu was tested with scripted input and by the owner:

• every control;
• a match (Ludacris against David Banner at The Foundation, intro through KO, back to the menu);
• a Story scene;
• the stage viewer;
• the pause menu's way out.

The owner play-tested the scene player, including several scenes in one session. That covers
the fix for the freeze on a second scene. The full regression with everything off passes 15 of
17 checks. The two misses are the known output-device audio gate (audio.dry_queue, one dry
event each in combat and versus), which main misses the same way. The play-test recorder
was tested on macOS and the Steam Deck. Windows was not play-tested for this release; CI builds
it, now including the game-side sources with MSVC.

Known limits

• The developer menu is EA's tool, kept as it was. It opens with developers' stand-in
  fighters (Crow1); pick real fighters before starting a match. The announcer's intro line is
  missing in matches set up from it (the retail disc lacks that file).
• Leaving the menu or a Story scene goes to the main menu, not back to the fight or the Story
  point that was running.
• The animation viewer, create-player screen, crowd test and Blazin viewer are reachable but
  not documented.
• The Story scenes are known by their file names (sc00-sc21, gf1a-gf3c), not yet by what
  happens in them.

Updating

Run the setup for your platform and update the existing installation. The setup builds the
game locally from your own dump and preserves player data.