W107 — 0.11 Release Candidate Verification

[The-Running-Dev]

W107 — 0.11 Release Candidate Verification

Release maintainers can judge one additive candidate from a complete, reproducible
verification record covering the engine and every supported delivery surface.

Done when

• W107.1 A candidate commit and one clean packed archive digest are recorded; every consumer
  and host test uses that archive rather than a workspace import or a separately packed
  copy.
• W107.2 A clean src/engine/ install passes typecheck, determinism lint, unit/integration
  tests, build, archive-content assertion, replay corpus, and the W104 compatibility sweep.
• W107.3 A clean site install passes lint/typecheck/unit/browser checks and production build;
  documentation conversion and validation run from canonical sources and are no-op on a
  second generation.
• W107.4 The static host builds and its container smoke proves health, campaign retrieval,
  session creation, action preview/submission, save/resume and the W98/W99 operations
  through the declared API, with no source tree mounted at runtime.
• W107.5 Packed text/MCP consumers and the lockfile-backed consumer smoke compile and run;
  Platform, service-contract, Adventures and GameOfLife companion checks name exact
  compatible versions or commits and have no unresolved contract mismatch.
• W107.6 Required CI workflows are green at the candidate commit, including Pester with its
  pass/skip counts and documentation/deploy Chromium setup; a skipped or unavailable
  check is listed as such and never rendered as a pass.
• W107.7 A release-candidate report records command, exit code, duration, artifact digest and
  evidence URL for every row, with zero unexplained failure or dirty-tree substitution.

---

Agent instructions

Run /slice W107.

• Scope and criteria: design/30-slices.md § W107 @ c2e427d
• Signatures: W104's compatibility manifest, W105's publication artifact, and
  the repository release/check matrices referenced by CLAUDE.md.
• Out of scope here: fixing a failed gate inside the verification unit, changing candidate
  scope, tagging, creating a GitHub release, deploying, or publishing to npm.

Stop conditions and procedure: .claude/commands/slice.md. Not restated here.

[The-Running-Dev]

PR #460 verified W107.1, .2, .3, .5, .6, .7 against candidate commit 31a24c3 — see .claude/release-candidate-w107.json for the full gate-by-gate report.

W107.4 is not met: host-image.yml's smoke step only proves health/routing (/health/live, /health/ready, a 404 fallback), never a session, campaign, action, or save/resume through the host's API. No script in this repository makes that deeper assertion yet — independent of this environment's missing REGISTRY_TOKEN credential, there is no check that would exercise it even with the credential present. Left the box unchecked pending a decision (see PR #460's description for the three options considered).

[The-Running-Dev]

Update on W107.4: this is not a missing test, it's a criterion that can't be met as written.

src/host/SubZeroDev.GameEngine.Host/Program.cs is explicitly a static delivery surround (AddPlatformWebHost() + MapPlatformProbes() only — three static routes, two health probes). design/10-design.md (the canonical Platform Static Host section, ~lines 3419-3431) states the host 'must not receive actions, own sessions, calculate results, persist saves, or expose the engine package over HTTP', and lists a JSON/HTTP engine API, remote session, and server-side action execution as Explicit Non-Goals belonging to a later, not-yet-built hosted-engine-edge slice. That document is itself marked historical / 'nothing here is a specification to build to'.

The session/campaign/action/save-resume/W98-W99 API W107.4 describes lives in SubZeroDev.Platform's game-service workload — a different repository — not in anything this repository's host-image.yml builds.

Extending the workflow to assert those operations would mean adding endpoints to src/host/ that design explicitly forbids, which is a non-goal/criterion change I can't make inside a /slice session (see PR #460 for the full finding). Recommend correcting W107.4 via /slices rather than building code to satisfy a criterion that conflicts with the design. Leaving W107 at 6/7; W107.4's box stays unchecked.