Why this is its own issue
Every phase of the Codex write substrate proved its own mechanism, but phase-local green tests do not prove that every production entry point converges on the same coordination substrate.
This issue tracks composed acceptance across those production boundaries.
Current status
This issue is partially implemented.
PR #1106 merged the workstation-safe composed acceptance suite and six production-path scenarios into dev.
Delivered there:
tests/codex-composed-acceptance.test.ts;- real spawned CLI children and a real HTTP server on temporary homes;
- entry-to-funnel manifest coverage;
- lost-transition behavior through HTTP;
- foreign-home zero-artifact refusal;
- same-effective-user cross-home single-lock behavior;
- Grok OFF surviving a real restart;
- restore truth through
ocx restore --json.
That work also found and fixed several real production holes, including OFF paths creating artifacts, stale server-captured config during /api/sync, foreign homes accepted over HTTP, and opaque busy results.
The workstation-safe portion should not be reimplemented.
Remaining scope
The issue remains open for the acceptance work deliberately deferred from #1106:
- Disposable-host service-class scenarios that must not run in ordinary workstation test discovery.
- Remaining production census rows that are not yet proven to converge on the coordinator.
- Final proof that no production writer can bypass the substrate under the supported service-manager paths.
The deferred service class includes the scenarios identified in the WP13 resume plan as:
The intended disposable-host entry point remains conceptually:
scripts/disposable-host/codex-service-composed-acceptance.ts
Service-manager tests require a host that can be destroyed or reset safely and should stay out of normal test discovery.
Related follow-ups
Focused correctness issues remain separate:
Those issues should not be folded into this acceptance tracker unless the missing acceptance scenario itself is the problem.
Acceptance criteria
Close condition
Close this issue only when the deferred disposable-host/service-class coverage and remaining production census are complete. The workstation-safe subset delivered by #1106 is necessary but not sufficient for closure.
Why this is its own issue
Every phase of the Codex write substrate proved its own mechanism, but phase-local green tests do not prove that every production entry point converges on the same coordination substrate.
This issue tracks composed acceptance across those production boundaries.
Current status
This issue is partially implemented.
PR #1106 merged the workstation-safe composed acceptance suite and six production-path scenarios into
dev.Delivered there:
tests/codex-composed-acceptance.test.ts;ocx restore --json.That work also found and fixed several real production holes, including OFF paths creating artifacts, stale server-captured config during
/api/sync, foreign homes accepted over HTTP, and opaque busy results.The workstation-safe portion should not be reimplemented.
Remaining scope
The issue remains open for the acceptance work deliberately deferred from #1106:
The deferred service class includes the scenarios identified in the WP13 resume plan as:
The intended disposable-host entry point remains conceptually:
Service-manager tests require a host that can be destroyed or reset safely and should stay out of normal test discovery.
Related follow-ups
Focused correctness issues remain separate:
Those issues should not be folded into this acceptance tracker unless the missing acceptance scenario itself is the problem.
Acceptance criteria
dev.Close condition
Close this issue only when the deferred disposable-host/service-class coverage and remaining production census are complete. The workstation-safe subset delivered by #1106 is necessary but not sufficient for closure.