[EHotwagner]

This PR is the selected Atlas capture of installed-C run 3 (39920080680), which fdev accepted as evidence in FS-GG/.github#4710 comment 6360636006. Refs #4710. It makes no source or workflow change.

Changes

• Report. A new C-J1 report section records run 3:
  • the path from run 2 (Game#727 → 0.7.0 → Re-pin the WASM receiver to FS.GG.Wasm 0.7.0 (Game#727 fix) (C-J1) #748/Prepare Workspace 0.19.3 adopting published FS.GG.Wasm 0.7.0 (C-J1) #749/0.19.3/Pin the installed-C caller and current-public cohort to published 0.19.3 (C-J1) #750);
  • the precheck, the admission (Admit exactly one installed-C run 3 (#4710 comment 6359693961) #753), the dispatch and the reset (Reset installed-C admission to None after the one admitted run 3 #754);
  • the 27/27 result, readbacks, budgets and peaks;
  • the Add the scheduled read-only Xantham upstream watch (Refs #751) #752 merged-tree note;
  • #4710 still open on the WASM-off browser path, plus the recorded limits.
• Atlas, new record: templates/wasm-installed-c-run-39920080680 (be521e72…, kind boundary). It carries the outcome, the evidence identities, the merged-tree lesson, the indirect bundle evidence and the open gap. It cites the report, caller, workflow, checker and materialize-assets.py at this head, Game 15e287d7 Lifecycle.fs, and the owner.
• Atlas, superseding record: a new version of templates/wasm-installed-c-managed-group-binding (df2e6ba4…) supersedes fc66cc11….
  • The receiver is now published 0.19.3 (9594ec20 / 7be0bcf5 / 6b3d8f2d, [0.7.0], SDK 090658bd), with the earlier receivers kept as history.
  • Run 3 is added.
  • "Not established hosted" is narrowed to: the WASM-off path, out-of-unit descendants, CPU pressure and cold-load timing, per-group memory, n=1, and the pilot's gaps.
• Validation: every baseline digest is preserved, and atlas validate reports 22 records.

🤖 Generated with Claude Code