docs: close AXR8 release and authority cutover - #101
Conversation
![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
Here are some automated review suggestions for this pull request.
Reviewed commit: a34acfd7fd
ℹ️ 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".
| # Sprint: ArchContext ↔ repo-harness Projection Runtime Integration | ||
|
|
||
| > **Status**: Approved | ||
| > **Status**: Done |
There was a problem hiding this comment.
After this commit marks every backlog row complete and changes the Sprint status to Done, the same document still states at lines 43–45 that the current conclusion is NO-GO for authority cutover. Because the stated prerequisite is now satisfied and the execution log says the cutover occurred, this leaves the Sprint's authority contradictory and can cause readers or agents to reject the completed cutover; update the decision to the final GO/completed state.
Useful? React with 👍 / 👎.
| - /Users/ancienttwo/Projects/arch-context-wt-axr1-arch-context-repo-harness-profile-canonical-nested-target-map-recursive-orphan-scan-and-explicit-mixed-file-adoption: active-worktree owner -> /Users/ancienttwo/Projects/arch-context-wt-axr1-arch-context-repo-harness-profile-canonical-nested-target-map-recursive-orphan-scan-and-explicit-mixed-file-adoption | ||
| - (none) | ||
| ## Active Sprint | ||
|
|
There was a problem hiding this comment.
The refreshed snapshot says the repository is Idle with no active plan or work, but its Active Sprint section points to the unrelated July authority-reading Sprint rather than the AXR Sprint closed by this commit (or no sprint). Consumers use tasks/current.md as the derived status snapshot, so this stale selection routes them to the wrong workflow artifact even before the 24-hour staleness window expires.
AGENTS.md reference: AGENTS.md:L7-L9
Useful? React with 👍 / 👎.
1 participant
What changed
archctx-contracts@0.4.0,archctx@0.4.0, andrepo-harness@0.14.0user_waiverwithout representing it as a Claude passWhy
The runtime and release gates were complete, but the tracked AXR8 plan, contract, review, and parent Sprint still reported an unfinished workflow. The pre-publish contract command also became invalid after publication because it correctly rejected a duplicate
archctx@0.4.0; the closeout now verifies immutable registry provenance instead.Impact
No product source or published tarball changes. This PR makes the workflow authority agree with the already verified registry and selected-runtime state.
Verification
repo-harness run verify-contract --contract tasks/contracts/20260809-0555-axr8-release-authority-cutover.contract.md --strict— 15/15 pass before archivalrepo-harness run verify-sprint -- --prepare-acceptance --contract ...— pass and evidence materializeduser_waiver, exact-subject boundbun run typecheckbun run verify:architecture-mermaid— 3/3 Mermaid diagrams renderbun test packages/contracts/test/contracts.test.ts— 176 pass, 0 failrepo-harness run check-task-workflow -- --strict— OK