Skip to content

docs: record verified merged worktree retirement #150

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 verified merged worktree retirement #150

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
081dc7f
docs: record verified merged worktree retirement
BunsDev Sep 9, 2026
31a5ee9
docs: clarify retirement evidence and inspection scope
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
27 changes: 27 additions & 0 deletions docs/roadmap.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,33 @@ the maintainer-held `chat-consolidation-20260907` recovery set as
`audit/refresh-20260909.json`. Main CI and merged diagnostic repairs do not
establish protected release acceptance. The program remains incomplete.

### Worktree retirement follow-through

A subsequent ownership check found no live process working in or referencing
four clean merged checkouts: `protected-matrix-v16`, `repin-cave-v0.3.12`,
`windows-chat-history`, and detached `/private/tmp/chat-main-check`. Each exact
tip was revalidated as an ancestor of refreshed main immediately before
`git worktree remove`; all four paths were verified absent afterward.

The three named local branches were deleted with `git branch -d`. Their remote
branches were removed atomically with exact-tip leases, and a fresh remote
listing verified their absence. The recovery set records these operations in
`audit/merged-retirement-20260909.json` and
`audit/merged-refs-retirement-20260909.json`. No force deletion was used.

@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.

Clarified in 31a5ee9: these are files in the audit directory of the maintainer-held recovery set outside this repository, not repository paths.


Three worktrees remain: main, parked #86, and v17. Review of closed #144 confirms
that merged #143 supersedes v17's shallow-checkout repair by retaining full Chat
history. The current workflow suite passed 59 tests with 19 platform skips;

@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.

Clarified in 31a5ee9: #144 is explicitly closed and unmerged; the delivered behavior is attributed to merged #143.

this is not Windows runtime or protected-matrix acceptance. V17's divergent
historical authority pins remain preserved in its branch and checkout.

[Issue #149](https://github.com/OpenCoven/chat/issues/149) tracks the CI-image
proposal failure and retry defect. Read-only inspection found no repository
Actions secrets configured: the proposed separate credential is absent. The
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.

@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.

Clarified in 31a5ee9: the observation is dated 2026-09-09 UTC and scoped to the repository and repository-accessible organization secrets returned to the authenticated maintainer. Both read-only REST lists were empty at inspection time.


## Historical audit — 2026-09-07

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