Skip to content

Correct W107.4 — static host criterion required a forbidden engine API - #461

Merged
The-Running-Dev merged 2 commits into
mainfrom
feature/slices-87e604
Sep 7, 2026
Merged

Correct W107.4 — static host criterion required a forbidden engine API#461
The-Running-Dev merged 2 commits into
mainfrom
feature/slices-87e604

Conversation

@The-Running-Dev

Copy link
Copy Markdown
Owner

Summary

W107.4 required the static host's container smoke test to prove session
creation, action preview/submission, save/resume, and the W98/W99
operations "through the declared API." design/15-platform-static-host.md
§8 explicitly forbids the host from receiving actions, owning sessions, or
exposing an engine API — those operations are contract-gated on the
engine's own API, not the host's. This was a boundary-conflation error in
the criterion, not a missing test; it can't be fixed by adding code (that
would violate the documented non-goal) and could only be corrected through
/slices.

  • Rewrote W107.4 to match what host-image.yml's smoke step actually (and
    legitimately) proves: 200 for /, /roadmap/, /docs/, liveness and
    readiness; 404 for a named unknown route; and the negative fixture that
    fails to start on a missing required artifact — with no source tree
    mounted at runtime.

Test plan

  • Confirmed design/FROZEN.md does not exist (design is unfrozen).
  • Verified .github/workflows/host-image.yml's smoke step covers only
    static routes/health/negative-fixture — no engine API surface.
  • Verified design/15-platform-static-host.md §8 non-goals forbid a
    Node.js engine process, JSON/HTTP engine API, or server-side action
    execution on this host.
  • Note: this desyncs issue W107 — 0.11 Release Candidate Verification #395's W107.4 checklist item; that reconciliation
    is /track's to run next, not this PR's.

W107.4 required the container smoke test to prove session creation, action
preview/submission, save/resume and the W98/W99 operations through the
host's declared API. 15-platform-static-host.md §8 explicitly forbids the
host from receiving actions, owning sessions, or exposing an engine API —
those operations are contract-gated on the engine's own API, not the host's.
The criterion now matches what host-image.yml actually proves: static route
smoke, health, and the negative missing-artifact fixture.
Follow-up to 1971f0e: the human-documentation drift check requires the
generated page to match its canonical design/30-slices.md source.
@The-Running-Dev
The-Running-Dev merged commit a84d9c9 into main Sep 7, 2026
8 checks passed
@The-Running-Dev
The-Running-Dev deleted the feature/slices-87e604 branch September 7, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant