Skip to content

docs: record minimum checkout set and remaining gates #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BunsDev merged 2 commits into from
Sep 9, 2026
Merged

docs: record minimum checkout set and remaining gates #152

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
173e988
docs: record minimum checkout set and remaining gates
BunsDev Sep 9, 2026
320cf64
docs: distinguish sequential worktree checkpoints
BunsDev Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions docs/roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,39 @@ image itself already built and passed its verification job. Repairing the
proposal requires both an authorized workflow-file write path and retry logic
that does not confuse an existing branch with a completed update and PR.

### Minimum checkout set and remaining gates

Final cleanup on 2026-09-09 UTC reduced the registered worktrees to two: the
primary checkout and parked PR #86. V17 was clean and had no observed process
ownership. After confirming its repair was superseded by merged #143, its exact
tip `d56e915` was preserved in both its local branch and the verified complete-history
Comment on lines +74 to +77

@BunsDev BunsDev Sep 9, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in 320cf64: the three-worktree count and v17 checkout preservation now explicitly describe the earlier checkpoint, superseded by the later two-worktree checkpoint. Specification guards (50 tests) and diff checks pass.

`retired-v17-history.bundle`; only the redundant checkout was removed.
The external recovery set contains `v17-retirement-20260909.json` in its audit
directory, with the absence and retained-ref checks.

The delivered heads of #148, #150, and #151 were compared against their merge
commits for every changed path. Their obsolete remote branches were removed
with exact-tip leases after preserving full histories in
`merged-audit-and-image-repair.bundle`. Local divergent history remains intact;
no force-deletion was used. At this cleanup checkpoint, before the follow-up documentation PR, the remaining
remote branches were main, parked #86, the pre-existing SDK archive, and the
incomplete image proposal tracked in #149.

[#151](https://github.com/OpenCoven/chat/pull/151) delivered the image proposal
repair and credential documentation. Both
[PR CI](https://github.com/OpenCoven/chat/actions/runs/34299445667) and
[rebuilt-image verification](https://github.com/OpenCoven/chat/actions/runs/34299428063)
passed. Issue #149 remains open for credential setup and a successful live
proposal; the operator has been asked to configure the dedicated token.

Protected [run 34299665723](https://github.com/OpenCoven/chat/actions/runs/34299665723)
was verified waiting for named `client-v1-conformance` environment review at
head `dadef69`. The operator was asked to review that existing run; no replacement
was dispatched or approval supplied by this audit. Later documentation and
image-proposal repairs do not change its conformance workflow or pinned inputs.
This remains a pending run, not successful release evidence. PR #86 and the SDK
release remain gated by their actual acceptance requirements.

## Historical audit — 2026-09-07

Audited 2026-09-07 against Chat `origin/main` at
Expand Down
Loading