docs: archive Slice C and create Slice D intent baseline for issue #135 - #156
Conversation
Archive the merged client-external-control-plane-v1 change, sync its landed control-plane deltas into the canonical client-host-orchestration spec, and establish the docs-first kickoff baseline for client-capability-discovery-and-host-tests. Key changes: - archive Slice C OpenSpec artifacts under openspec/changes/archive/2026-03-02-client-external-control-plane-v1 and move its feature aggregation doc to docs/features/archive - sync the landed control-plane requirements into openspec/specs/client-host-orchestration/spec.md so the main spec reflects control-stdin, canonical action ids, and status snapshot semantics - update client/DESIGN.md and client/README.md to choose explicit actions:list discovery over unsolicited startup handshake for the next slice - refresh the host-orchestration master TODO ledger: mark CCLI-005/006 done, record Slice C archive evidence, and claim CCLI-007/008 for Slice D - create the client-capability-discovery-and-host-tests OpenSpec change plus its feature evidence doc, covering explicit capability discovery and host protocol regression testing Rationale: PR #151 is already merged, so Slice C must be archived before more implementation work begins. Slice D needs a docs-first baseline on top of the merged control-plane spec, otherwise the next implementation slice would start from an outdated canonical contract and leave hosts choosing between hardcoded action matrices and undefined handshake behavior.
Record the docs-only intent PR link for client-capability-discovery-and-host-tests in the active feature evidence doc. Key changes: - replace the pending Slice D intent PR placeholder with the live PR #156 link - rerun governance evidence truth after the evidence update Rationale: The feature aggregation doc is the source of truth for review and merge-gate evidence. Once the intent PR exists, its link should live in the feature evidence immediately so the next implementation slice can trace the merged docs gate without reconstructing it from GitHub history.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
https://github.com/zts212653/Deterministic-Agent-Runtime-Engine/blob/9efdfc73da39e61acbfd456c1e06f772577e5c26/docs/features/archive/client-external-control-plane-v1.md#L20-L24
This archived feature doc now points its OpenSpec artifact links at openspec/changes/client-external-control-plane-v1/..., but that directory was moved to openspec/changes/archive/2026-03-02-client-external-control-plane-v1/... in the same commit. As a result, readers following the canonical artifact links from this page hit missing files and cannot trace proposal/design/spec/tasks for Slice C, which weakens the docs-first audit trail.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Point the archived client-external-control-plane-v1 feature doc at the archived OpenSpec artifact paths instead of the pre-archive active change location. Key changes: - update proposal/design/spec/tasks links in docs/features/archive/client-external-control-plane-v1.md to openspec/changes/archive/2026-03-02-client-external-control-plane-v1 - rerun governance evidence truth after the archived-link fix Rationale: Once Slice C was archived, the feature aggregation doc became the retained audit record for that slice. Leaving its artifact links pointed at the deleted active-change path broke the docs-first traceability chain and forced readers to reconstruct archive locations manually.
|
Fixed the archived Slice C artifact links in The archived feature doc now points its proposal/design/spec/tasks links at Verification rerun after the fix:
|
1 participant
Summary
This is a docs-only intent PR for the next Issue #135 slice.
It does two things:
client-external-control-plane-v1)client-capability-discovery-and-host-testsWhy
PR #151 already merged the external control plane baseline, so Slice C needs to be archived before more implementation work starts.
The remaining Issue #135 gap is now narrower:
actions:listis not exposed on the CLI host protocol surfaceThis PR updates the canonical docs and OpenSpec artifacts so Slice D can start from the current main-spec baseline instead of the pre-Slice-C contract.
Scope
Included in this PR:
client-external-control-plane-v1underopenspec/changes/archive/2026-03-02-client-external-control-plane-v1openspec/specs/client-host-orchestration/spec.mddocs/features/archive/client-external-control-plane-v1.mdclient/DESIGN.mdandclient/README.mdto choose explicitactions:listdiscovery over unsolicited startup handshake for the next sliceclient-capability-discovery-and-host-testsNot included in this PR:
actions:listbridge implementationTODO / Change Mapping
CCLI-005CCLI-006CCLI-007CCLI-008client-capability-discovery-and-host-testsValidation
Executed:
../../.venv/bin/python -m pytest tests/unit/test_client_cli.py -q../../.venv/bin/python -m pytest tests/integration/test_client_cli_flow.py -qopenspec listopenspec show client-capability-discovery-and-host-tests --type change --json --no-interactiveopenspec validate client-capability-discovery-and-host-tests --type change --strict --json --no-interactive./scripts/ci/check_governance_evidence_truth.shResults:
45tests)21tests)0issuesMerge Gate Intent
This PR is intended to satisfy the docs-only intent gate for Slice D.
After this PR is merged to
main, the next step is to implementclient-capability-discovery-and-host-tests:actions:listthrough--control-stdin