Repository navigation
Retire completed local worktrees after owner and retention verification #6179
Description
Current maintainer request: remove old unnecessary worktrees, or land needed work through protected PRs. This curation supports the #5256 documentation close-out, which is blocked by the 28-worktree budget. Actor: Codex, thread 01a16533-9ddc-7611-b2a4-ffcf51829ce0. Scope: local worktree cleanup and protected PR delivery where current ownership and verification allow it; no remote deletion, releases, or protection changes.
Continuity: bounded REST search for open worktree issues returned 0, incomplete_results=false. Historical #5474 is closed and covered different exact candidates; this is a new batch, not authority inherited from it. Origin is https://github.com/OpenCoven/coven-cave.git. No new worktree is needed for this read-only audit. Project access remains unavailable; private execution stores were not searched.
Inventory: 32 registered worktrees, 43 local branches. Fetched origin/main is da32081. Exhaustive paginated REST inventory returned 5,474 PRs. Of 31 secondary worktrees, 25 match exact heads of merged PRs, two match open PRs, and four hold uncommitted work. Squash-merged heads are not treated as retained solely because the PR merged. No deletion proof or DELETE classification is claimed yet.
Open-PR disposition: #6174 at 133fdcb fails Frontend build and Frontend E2E (1/8), with the original #6173 dependency unresolved. #6176 at 4588a3d fails Frontend build, Frontend E2E (6/8), and Frontend E2E (agentic); its owner still has active processes. Neither is ready for protected merge. Do not rerun or change those units to make cleanup possible.
Runtime evidence: repository-scoped coven claim status returned no claims. The local surface-claim file records active owners for #6057, #6058 and #6059; OS CWD inventory also finds live processes in those exact worktrees. The local maintenance status reports no held gate and no writer intents, which does not negate those active writers. Coven sessions lacks a repository filter in its advertised CLI, so an unscoped private session inventory was not retrieved; coverage is unknown. The branch-curator contract requires a current owner-backed idle/disposition receipt and preservation on incomplete coverage.
First proposed bounded retirement candidates, pending fresh owner/runtime clearance: #6103 / PR #6133 at a6bc52d, #6128 / PR #6131 at 70872e1, and #6129 / PR #6134 at 997e908. All three owning issues are closed; exact PR heads match, no tracked/untracked changes or CWD processes were observed, and only policy-listed generated paths are ignored. Their latest owner dispositions explicitly preserve exact-head/evidence units for a separate authorized retirement pass. No artifact is discarded by this proposal.
Next: obtain current owner/runtime release for the exact candidate units, then choose and record the manual-local-only profile, acquire the local maintenance lease, refresh complete issue/PR/workflow/recovery/remote-retention evidence, and require the strict worktree guard before each non-forced removal. Keep every dirty, active, unresolved, or non-disposable-evidence unit intact. No merge, removal, local ref deletion, or remote deletion has occurred.
Full local-branch classification (read-only; action is preserve until each proof is complete):
| Branch | Exact HEAD | PR evidence | Decision | Reason |
|---|---|---|---|---|
cody/5865-chat-list |
3081839b54946044b50d2560631e71b5fdffd6a9 |
#6109 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
docs/issue-6126-core-contract |
b4674fb21006b883184a0b5db5cb924210c97148 |
#6127 | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
feat/issue-6129-memory-traversal |
997e908578bea6a927483ffb64b95b58112b7110 |
#6134 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/daemon-setup-recovery |
693aba6d0e1224df617ec9ba8e4190f965acfa3a |
#6117 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-5917-self-report-ownership |
46d8736f3a83a71f79158e64559b995cd5555aa0 |
#6152 | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
fix/issue-5979-startup-diagnostics |
d2d5c7b712b6af22cf326e6da4bf32ee9eedff0b |
#6159 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-5980-window-geometry |
17ebc7f110cf6a1cae437abd6e1eff76e9a171b2 |
#6167 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-5981-sidecar-recovery |
0598dbea3820804268027fee9d0c94cc34d2d23c |
#6158 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-5981-update-information |
c94b131750091a9ad4fa00a007a5ceb7f83e7e2c |
#6155 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6060-ui-fallback |
e23b89abab6521fd81e3bc814191848371a5a476 |
#6175 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6103-project-mentions |
a6bc52dcf9e5a5d176f1c3313398403498f4f194 |
#6133 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6114-e2e-reliability |
b76ba3b5d776194b967931e052ca8a9e0c02bb8b |
#6115 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6122-daemon-poll-deadline |
5ea26eee6d4db740b7b6910a32fbcab709594c48 |
#6123 | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
fix/issue-6124-chat-fixture-admission |
ea281a5ee81f873e019143b1e4ee45b528c0a79d |
#6125 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6128-github-attachment-identity |
70872e111b6f6f839d98f9ba3bb816a8e88d65fe |
#6131 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6130-github-watcher-deadline |
141e43b0c6f37ba481b1a1a0740532f86197d977 |
#6132 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6135-github-watcher-lifecycle |
974f77f373405c67692ba55ae54d12d9f77f65da |
#6136 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6139-security-dependencies |
dd8b745768661ceee2e65da720c4c87e1265d9b3 |
#6140 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6142-memories-acceptance |
962be2dd5e1a6eb1ac398aa706c6bfc7c45c9712 |
#6146 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6150-research-runtime |
c9c484e38e24bc0764b0d0b2a425878e19a81649 |
#6151 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6153-inbox-preservation |
3b8ceb2c989d4dafac7d45de5df32763accfd86a |
#6154 | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
fix/issue-6156-cli-verification |
179f27fd2f6678bdeb6be71ff822a93f2b58fe41 |
#6157 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6160-inbox-admission |
4fd4ceed945b664ff886a9cdc49511919750ac5c |
#6162 | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
fix/issue-6164-reviewed-cli |
f2ecac77b649362a3e45a025553c40e93d8aa596 |
#6165 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6166-setup-reconcile |
e037224222d82f3cd8c9ffa9e26dea9cb3183a5e |
#6168 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6170-node-verification |
c9f9eea4781733ef379ee59410551d3a4680f15b |
#6171 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
fix/issue-6172-backup-state |
133fdcbd4913ab0691c4b1f91cba19df5889e95e |
#6174 | PRESERVE - live | Open PR; required checks failed; owning session retained |
fix/issue-6173-find-navigation |
61175924280813bcee6e3f6d97612a81daed9010 |
No exact-head PR found | PRESERVE - live | Uncommitted work; owner and locks preserved |
fix/local-models-e2e |
7833ea147a4d8798d9863609409b0851e9fe27b7 |
No exact-head PR found | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
main |
da32081f4dad38aa30a2311afa1d8005592c76df |
No exact-head PR found | PRESERVE - live | Protected primary checkout |
perf/issue-6144-research-styles |
f66f6f243fd40d3cc7979916e8697a715eee2f6a |
#6145 | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
test/issue-5897-access-acceptance |
a90bc40a50fb10f06f4fc5b8f9737c653ad60711 |
#6161 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
test/issue-6036-build-observation |
f9a88f3e6048d5f7a47ab24b2d4622d6515f6c37 |
No exact-head PR found | PRESERVE - live | Uncommitted work; owner and locks preserved |
test/issue-6036-incremental-checker |
577ba555ca8831b3f75e9539f95cd2bf63cdad72 |
#6169 | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
test/issue-6036-typescript-diagnostics |
a353afd555233720fe38ce1318e410bc7f4c4b36 |
#6163 | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
test/issue-6057-reasoning-states |
4588a3d253bfbdd00b69965f4c5dd5612774290c |
#6176 | PRESERVE - live | Open PR; required checks failed; owning session retained |
test/issue-6058-authority-guards |
da32081f4dad38aa30a2311afa1d8005592c76df |
No exact-head PR found | PRESERVE - live | Uncommitted work; owner and locks preserved |
test/issue-6059-replay-guards |
da32081f4dad38aa30a2311afa1d8005592c76df |
No exact-head PR found | PRESERVE - live | Uncommitted work; owner and locks preserved |
test/issue-6119-research-lifecycle |
69554077e33202bbda5a763a572ce29a2a5d2bc2 |
No exact-head PR found | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
test/issue-6120-real-daemon-lifecycle |
5a75988824da6b5dae42ac006d4e213d88b7d82e |
#6121 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
test/issue-6137-stream-performance |
78aecbbb89131bab70a58825e1f2fd3c812e3bd9 |
#6138 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
test/issue-6147-probe-cleanup |
bd057359351bff7ade47773b74951249dbe089e9 |
#6149 | PRESERVE - uncertain | Owner-backed retirement and runtime clearance outstanding |
verify/issue-6119-integrated-recovery |
5643ee93e15d74309e728919779b97d6d4395b93 |
No exact-head PR found | PRESERVE - uncertain | No worktree; recovery and owner disposition not proven |
Metadata
Metadata
Labels
Type
Projects
- Status
Activity
BunsDev commentedon Oct 22, 2026
First-candidate read-only preflight completed for #6103/#6128/#6129. Exact merged PR details and live refs/pull/6133/head, refs/pull/6131/head, and refs/pull/6134/head advertise the audited local heads. All 30 active-workflow queries returned zero. No assume-unchanged or skip-worktree flags were found. Generated roots remain intact. Clean previews also expose empty fixture-directory scaffolding requiring inspection during the final proof.
The required cross-repository associatedPullRequests query failed with GraphQL RATE_LIMIT. REST remains usable, but its origin PR inventory does not replace that association proof. The rate_limit endpoint reports available quota while the actual GraphQL query is rejected; actual failure is authoritative.
Current owner-backed release for the three units was requested through native input; no answer received. Associated-PR proof also remains unavailable. Active #6057/#6058/#6059 processes and claims remain untouched. No maintenance lease or DELETE verdict is claimed, and no destructive command was attempted.
Next: after owner release and restored query access, refresh the exact candidates and complete the manual-local-only proof under the local maintenance lease, including recovery retention and the strict worktree guard. Audit files: /tmp/cave-curation-classification.json, /tmp/cave-curation-worktrees.json, /tmp/cave-curation-prs.jsonl and /tmp/cave-curation-proof-{6103,6128,6129}.json. No worktrees or refs removed, no PR merged, no release. Count remains 32; #5256 remains blocked on capacity.
BunsDev commentedon Oct 22, 2026
Val has now instructed: "proceed with your recommendations please", following the explicit owner-release question for #6103, #6128 and #6129. Record this as the current maintainer-backed release/disposition and authority for this bounded local-only cleanup batch; do not request the same approval again.
Manual-local-only candidate set: .worktrees/issue-6103-project-mentions / fix/issue-6103-project-mentions at a6bc52d (merged #6133); .worktrees/issue-6128-github-attachment-identity / fix/issue-6128-github-attachment-identity at 70872e1 (merged #6131); .worktrees/issue-6129-memory-traversal / feat/issue-6129-memory-traversal at 997e908 (merged #6134). Repository OpenCoven/coven-cave; audited main da32081. Actor Codex, thread 01a16533-9ddc-7611-b2a4-ffcf51829ce0; execution from the primary checkout is read-only coordination, with no source edit there. Local branches and remote refs will be retained unless their separate deletion proof is completed; remote deletion is outside this batch.
Owner-release input is resolved. All runtime, exact-head, remote retention, recovery, lease and strict-guard checks still apply. A fresh associatedPullRequests GraphQL query still returns RATE_LIMIT; no deletion or bypass has occurred. Continue independent read-only preflight and resume removal only when the required proof is available.
BunsDev commentedon Oct 22, 2026
All three approved candidates passed the read-only strict worktree-guard preflight with exact GitHub merged-PR retention: #6103 at a6bc52d, #6128 at 70872e1, and #6129 at 997e908. These are preflights only; they must run again immediately before removal under the maintenance lease.
Both branch and private HEAD reflogs contain only two distinct nonzero OIDs per unit, each reachable from the exact retained head or main. ORIG_HEAD/FETCH_HEAD entries also pass that ancestry check. The additional fixture scaffolding contains no files. No source or evidence was removed.
GitHub GraphQL's own response reports remaining=0 and resetAt=2026-10-22T20:32:51Z, unlike the inconsistent REST quota summary. One read-only association retry is scheduled just after that reset; no credential changes or repeated authentication. Owner-release approval remains recorded and does not need renewal merely because the API is waiting.
BunsDev commentedon Oct 22, 2026
The first approved removal passed all final API/ownership/retention/recovery checks and the strict guard, then my subprocess wrapper killed git worktree remove after 90 seconds. This was an execution-timeout error in the wrapper, not a guard refusal. The batch stopped immediately and released its maintenance lease; #6128 and #6129 were not touched. No complete worktree removal is claimed.
Recovery: the #6103 HEAD and local branch remained at a6bc52d. Fresh status contained only 156 tracked deletions, with no modifications or untracked work. Restored only those deleted paths from that exact head using a NUL-delimited path list. Subsequent status is clean and HEAD unchanged. Generated build/dependency directories may be partially removed and are disposable under the existing policy. During this removal the auto-lock hook added a lock reporting four deleted paths; initial inventory proved the unit unlocked. This is a lock induced by this cleanup attempt, not another owner's lock. Its exact text will be checked before clearing it after source recovery.
The failed batch is over. Start a new bounded batch under Val's existing current-task instruction for these same three exact units, with a new lease and every proof refreshed. Keep the removal process attached without a per-command kill deadline, heartbeat the lease, and verify terminal status/path/registration before moving on. Never bypass the strict guard or change its safety rules. No additional owner permission is inferred for any other unit.
BunsDev commentedon Oct 22, 2026
Completed the approved manual local-only retirement batch. All three worktree directories and registrations are absent; their local branch refs remain at the exact audited heads and the merged PR head refs retain those commits. Worktree count is 29, down from 32. The local maintenance lease was held through the batch and released successfully.
.worktrees/issue-6103-project-mentionsa6bc52dcf9e5a5d176f1c3313398403498f4f194.worktrees/issue-6128-github-attachment-identity70872e111b6f6f839d98f9ba3bb816a8e88d65fe.worktrees/issue-6129-memory-traversal997e908578bea6a927483ffb64b95b58112b7110Post-action verification covered all 5,475 repository PRs and 30 active-workflow queries across the three exact branch names and heads; no matching open PR or active run was found. The primary checkout remains clean. No local or remote branch was deleted, and no PR was merged in this batch. The earlier removal timeout and restoration are recorded above; the subsequent fresh guarded batch completed successfully.
Remaining units stay preserved for the ownership, live-work, recovery, or incomplete-proof reasons in the inventory. In particular, #5981 now has a reused dirty unit and #6058 has advanced, confirming concurrent work. Further retirement needs a fresh bounded batch with current owner dispositions and proof. At 29 worktrees, two additional verified retirements would permit a new #5256 worktree within the 28-worktree budget. Project status could not be verified; this issue remains open for the remaining capacity blocker.
BunsDev commentedon Oct 24, 2026
New bounded manual batch (2026-10-24): local worktree + local branch retirement
Authority. Val, in the current Claude Code session (25c3817b): "continue on any incomplete work in the repo and merge to main and remove the worktree and branch with pruning". Val then picked these options: "Green 5 + repair 2" and "Retire merged, preserve rest". This is a new batch. It inherits no earlier authority.
Merged under this authority (exact-head squash, required
Frontend buildgreen, zero review threads): #6187 →1594ceed7, #6174 →7723b3466, #6198 →34219bf5a, #6197 →2c17bbf96, #6194 →1deb57cc2. #6180 and #6185 had main merged in (f02004e82,66f2f0f7d). They merge only if they come back green.Profile. Manual and local-only, under the repository maintenance gate. Each removal goes through
worktree-guard --strict-worktree-remove --retained-by-github-pr, with no bypass. Each local ref is compare-and-deleted at its audited OID. GitHub auto-deleted every candidate's remote branch on merge. There is no remote deletion transaction. Thengit worktree pruneandgit fetch --prunerun (fetch.pruneTagsstays false).Exact candidates (every one is the exact head of a merged PR):
.worktrees/daemon-setup-recoveryfix/daemon-setup-recovery693aba6d0e1224df617ec9ba8e4190f965acfa3a.worktrees/fix-issue-6060-ui-fallbackfix/issue-6060-ui-fallbacke23b89abab6521fd81e3bc814191848371a5a476.worktrees/issue-5256-qualified-windowdocs/issue-5256-qualified-window994cad3d6e55c5ac69167ee5b0cb9eca57e6831f (ff from dc22a406b).worktrees/issue-5761-map-ledgerdocs/issue-5761-map-ledger2eb2ad54f855c1d55f9e5f62fa5dacf1ca72bc9f.worktrees/issue-5865-continuationcody/5865-chat-list3081839b54946044b50d2560631e71b5fdffd6a9.worktrees/issue-5920-contextual-enhancefix/issue-5920-contextual-enhancef90c231e44d4c27d082aaf91f1ffea3448e65c8c.worktrees/issue-5979-startup-diagnosticsfix/issue-5979-startup-diagnosticsd2d5c7b712b6af22cf326e6da4bf32ee9eedff0b.worktrees/issue-5981-sidecar-recoveryfix/issue-5981-install-recoveryd7280ed065831d1fc92acf7a13668307b74d897b.worktrees/issue-5981-update-informationfix/issue-5981-update-informationc94b131750091a9ad4fa00a007a5ceb7f83e7e2c.worktrees/issue-6059-replay-guardstest/issue-6059-replay-guards97102d14b6542144868a4bc73d24d4a106da9c4b.worktrees/issue-6114-e2e-reliabilityfix/issue-6114-e2e-reliabilityb76ba3b5d776194b967931e052ca8a9e0c02bb8b.worktrees/issue-6120-real-daemon-lifecycletest/issue-6120-real-daemon-lifecycle5a75988824da6b5dae42ac006d4e213d88b7d82e.worktrees/issue-6124-chat-fixture-admissionfix/issue-6124-chat-fixture-admissionea281a5ee81f873e019143b1e4ee45b528c0a79d.worktrees/issue-6130-github-watcher-deadlinefix/issue-6130-github-watcher-deadline141e43b0c6f37ba481b1a1a0740532f86197d977.worktrees/issue-6135-github-watcher-lifecyclefix/issue-6135-github-watcher-lifecycle974f77f373405c67692ba55ae54d12d9f77f65da.worktrees/issue-6139-security-dependenciesfix/issue-6139-security-dependenciesdd8b745768661ceee2e65da720c4c87e1265d9b3.worktrees/issue-6142-memories-acceptancefix/issue-6142-memories-acceptance962be2dd5e1a6eb1ac398aa706c6bfc7c45c9712.worktrees/issue-6177-main-cifix/issue-6177-transport-readiness4c69c1687d8427df83e0981d0cca32550d84ca42.worktrees/issue-6191-playwright-imageci/issue-6191-playwright-image1f85f5573cd7333623ee8640f7c934b3e006c29c.worktrees/issue-6196-research-automationsfix/issue-6196-research-automationsd4a352d9cb6b14fe0f3f5369b98a372837afa489.worktrees/issue-6201-chat-header-rowsfix/issue-6201-chat-header-rows485ec6b869cde1da2cf340e95c152a05aa8b7defThe
issue-5256-qualified-windowworktree is clean and sits behind its own PR head. It is fast-forwarded to the merged #6187 head before the proof.Preserved:
issue-5897-access-acceptance-20261021, reused at 06:33Z fortest/issue-5897-acceptance-20261024with live processes. Its old ref is also preserved. Also live:issue-6067-failed-child-text(Render native chat UI with state retained through settlement #6073, active)..tmpevidence). 5980, 6119, 6137, 6147, 6150, 6156, 6164, 6166 and 6172 (.superpowers/sddrecords).docs/issue-5762-scope-03-limitation. Its head530a59b6eis no PR head.BunsDev commentedon Oct 24, 2026
Batch complete: 21 worktrees and 21 local branches retired, 7 PRs merged
This completes the batch recorded in comment 6381098459.
Merges. Each was a squash at its exact head, with the required
Frontend buildgreen on that head and no reviews, threads or comments:994cad3d61594ceed735ba3928e7723b34664c69c168734219bf5a2cb17bcd42c17bbf967857a5d321deb57cc2f02004e82b368cdaad66f2f0f7d777d6a0ad#6180 and #6185 were refreshed with a main-merge commit first. The refresh cleared #6185's stale merge-tree refusal and the old #6173 Find E2E failure on #6180. Their runs were 40071120680 and 40071127137. GraphQL was rate limited, so the last two merges went through REST
PUT /pulls/{n}/mergewithsha=(exact-head match).Retired. These went through three gate-held batches. Each removal passed fresh PR, workflow, claim and session checks, plus
worktree-guard --strict-worktree-remove --retained-by-github-prwith no bypass. Then came a non-forcegit worktree removeandupdate-ref -dat the audited OID. The retired branches:fix/daemon-setup-recovery, fix/issue-6060-ui-fallback, docs/issue-5256-qualified-window, docs/issue-5761-map-ledger, cody/5865-chat-list, fix/issue-5920-contextual-enhance, fix/issue-5979-startup-diagnostics, fix/issue-5981-install-recovery, test/issue-6059-replay-guards, fix/issue-6114-e2e-reliability, test/issue-6120-real-daemon-lifecycle, fix/issue-6124-chat-fixture-admission, fix/issue-6130-github-watcher-deadline, fix/issue-6135-github-watcher-lifecycle, fix/issue-6139-security-dependencies, fix/issue-6142-memories-acceptance, fix/issue-6177-transport-readiness, ci/issue-6191-playwright-image, fix/issue-6196-research-automations, fix/issue-6201-chat-header-rows, test/issue-6058-authority-guards.
5256 and 6058 were clean but behind their own merged PR heads, so they were fast-forwarded first. Three units carried
AUTO_MERGEequal to their HEAD tree, which is the guard's documented exception. They ran in a fresh second batch after the first batch's stricter pre-check stopped them.Each retired head is still retained at
refs/pull/<n>/head. Remote branches were already absent because GitHub auto-deleted them. No remote deletion was performed.git worktree prunefound nothing stale.git fetch --prunedropped 8 stale remote-tracking refs. No tags were pruned. Worktrees went from 44 to 24.Still preserved:
fix/issue-5981-update-informationhas a staleREBASE_HEAD..tmpevidence), and 5980, 6119, 6137, 6147, 6150, 6156, 6164, 6166 and 6172 (.superpowers/sddrecords).docs/issue-5762-scope-03-limitation(530a59b6e).issue-5897-access-acceptance-20261021, reused at 06:33Z, along with its old reftest/issue-5897-access-acceptance. Also the Render native chat UI with state retained through settlement #6073 unit (issue-6067-failed-child-text).BunsDev commentedon Oct 24, 2026
Follow-up batch: consolidate
.superpowersnotes, then retire 9 unitsAuthority. Val, in the same session, in reply to the offer to archive the notes: "yes, those superpowers worktrees should reduce to a single notes consolidated then rest pruned". This is a new bounded batch with the same profile as the previous one. It is manual and local-only, runs under the maintenance gate and the strict guard with no bypass, and compare-and-deletes each local ref at its audited OID. There is no remote deletion.
Preservation first. Every
.superpowersfile is copied byte for byte into one gitignored archive in the primary checkout,.superpowers/archive/2026-10-24-retired-worktrees/. The archive holds a consolidatedNOTES.md,raw/<worktree>/copies andMANIFEST.sha256. Before each removal, the proof re-hashes every file in that unit's.superpowersand requires an identical archived copy. Any other non-disposable ignored state still preserves the unit..worktrees/issue-5980-window-geometryfix/issue-5980-window-geometry17ebc7f110cf6a1cae437abd6e1eff76e9a171b2.worktrees/issue-6119-integrated-recoveryfix/issue-6170-node-verificationc9f9eea4781733ef379ee59410551d3a4680f15b.worktrees/issue-6137-stream-performancetest/issue-6137-stream-performance78aecbbb89131bab70a58825e1f2fd3c812e3bd9.worktrees/issue-6147-probe-cleanuptest/issue-6147-probe-cleanupbd057359351bff7ade47773b74951249dbe089e9.worktrees/issue-6150-research-runtimefix/issue-6150-research-runtimec9c484e38e24bc0764b0d0b2a425878e19a81649.worktrees/issue-6156-cli-verificationfix/issue-6156-cli-verification179f27fd2f6678bdeb6be71ff822a93f2b58fe41.worktrees/issue-6164-reviewed-clifix/issue-6164-reviewed-clif2ecac77b649362a3e45a025553c40e93d8aa596.worktrees/issue-6166-setup-reconcilefix/issue-6166-setup-reconcilee037224222d82f3cd8c9ffa9e26dea9cb3183a5e.worktrees/issue-6172-backup-statefix/issue-6172-backup-state35ba3928ea2a8bc3b1adafabfa54c63bba6400cb (ff from 133fdcbd4)BunsDev commentedon Oct 24, 2026
Follow-up batch complete: 9 more units retired after the notes were archived
This completes comment 6381392406.
Archive. All 103
.superpowersfiles from the nine units are in.superpowers/archive/2026-10-24-retired-worktrees/in the primary checkout. That path is gitignored, so it isn't committed. The archive holds a consolidatedNOTES.mdwith progress notes and briefs inline and raw diffs and logs linked, plusraw/<worktree>/andMANIFEST.sha256. Each unit's proof re-hashed its.superpowersfiles against the archive before removal. After removal,shasum -cstill reports 103/103 OK.Retired. All nine passed under the gate with
worktree-guard --strict-worktree-remove --retained-by-github-prand no bypass, followed by a non-force removal andupdate-ref -dat the audited OID: fix/issue-5980-window-geometry (#6167), fix/issue-6170-node-verification (#6171), test/issue-6137-stream-performance (#6138), test/issue-6147-probe-cleanup (#6149), fix/issue-6150-research-runtime (#6151), fix/issue-6156-cli-verification (#6157), fix/issue-6164-reviewed-cli (#6165), fix/issue-6166-setup-reconcile (#6168) and fix/issue-6172-backup-state (#6174, fast-forwarded to35ba3928efirst).Local and remote absence was verified for every ref. Each head is still retained at
refs/pull/<n>/head.git worktree prunefound nothing stale, and no remote-tracking refs remained to prune.Totals. Worktrees went from 24 to 17. That count includes
fix/issue-6201-two-row-chromeandfix/issue-6209-startup-worker-lifecycle, which other sessions created during this batch. Preserved units are unchanged from the previous record.BunsDev commentedon Oct 24, 2026
Bounded batch: retire the #6036 unit after its PRs merged
Authority. Val launched a goal with "manual local-only retirement of the #6036 unit after both merge". Both are merged: #6217 →
a0fe5577c, #6218 →d0a7a41c5. Same profile as the earlier batches: manual local-only, maintenance gate,worktree-guard --strict-worktree-remove --retained-by-github-prwith no bypass, and compare-and-delete at the audited OIDs. There is no remote deletion; GitHub auto-deleted both remote branches..worktrees/issue-6036-typescript-diagnostics+ branchtest/issue-6036-build-observation63f4b78a38b2fdfdc196afccea2c6209e158caccrefs/pull/6218/head(merged #6218)fix/issue-6036-typecheck-before-compile(not checked out)50bab3ee522dc4fc60d216c9c23db9867d556c06refs/pull/6217/head(merged #6217)Preserved.
ci/issue-6036-runtime-ceilings(e52177f77) heads the live draft #6223, so its local and remote refs stay.BunsDev commentedon Oct 24, 2026
Done: the #6036 unit is retired (completes 6390900397)
.worktrees/issue-6036-typescript-diagnosticspassedworktree-guard --strict-worktree-remove --retained-by-github-pr origin OpenCoven/coven-cave 6218. It was removed without force, and both the path and its registration are gone.test/issue-6036-build-observation: compare-and-deleted at63f4b78a3, retained atrefs/pull/6218/head.fix/issue-6036-typecheck-before-compile: compare-and-deleted at50bab3ee5, retained atrefs/pull/6217/head. Before deletion, fresh checks confirmed the PR was merged at that exact head, no PR was open and no workflow was active, and the remote branch was absent.The maintenance gate was held for both deletions and released.
ci/issue-6036-runtime-ceilingsstays (live draft #6223). No remote ref was deleted.BunsDev commentedon Oct 24, 2026
Bounded batch: retire the #6067 unit now that #6073 has merged
Authority. In the current Claude Code session (7fcd2b86), Val launched the goal: "…work to reduce the total worktrees and branches…". This batch covers only the unit this session created and owns. It inherits no other authority and doesn't touch other sessions' units; the 25c3817b batches still own the wider sweep.
Profile. Manual and local-only, under the local maintenance gate. Removal goes through
worktree-guard --strict-worktree-remove --retained-by-github-prwith no bypass. The local ref is compare-and-deleted at the audited OID. GitHub already deleted the remote branch when #6073 merged (delete_branch_on_merge), so there is no remote transaction..worktrees/issue-6067-failed-child-text+ branchfix/issue-5947-native-uifa918c6e07f3fdf821e4349e34fcdccc89e41a6arefs/pull/6073/head(merged #6073 →775a4151d)Read-only preflight.
node_modules/,.next/,test-results/,artifacts/,public/sandbox/,server.mjs,next-env.d.tsandtsconfig.tsbuildinfo.mainat this exact head, andrefs/pull/6073/headadvertises it.ok.Before mutating, the checks are repeated under the gate.
52 remaining items
BunsDev commentedon Oct 27, 2026
Bounded batch addition (session 7fcd2b86, same profile): retire
.worktrees/issue-6258-overlay-retirement+feat/issue-6258-overlay-retirement@106b6c3e31bd6677ac8b484b5a82c506a9b92148. That's the exact head of merged #6287 (→1ec063951), retained atrefs/pull/6287/head. #6258 stays open for step 2.BunsDev commentedon Oct 27, 2026
Bounded batch addition (session 7fcd2b86, same profile): retire
.worktrees/issue-6173-find-layout-commit+fix/issue-6173-find-layout-commit@5a8981dfd252a271fe79870f1739a32ba85f1a28. That's the exact head of merged #6291 (→cadad9a8e), retained atrefs/pull/6291/head.BunsDev commentedon Oct 27, 2026
Bounded batch addition (session 7fcd2b86, same profile): retire
.worktrees/issue-6286-dependency-edit-ops+fix/issue-6286-dependency-edit-ops@4f5b8ebda0e3831beb77b894809e6663a808395a. That's the exact head of merged #6292 (→59a7930e3), retained atrefs/pull/6292/head.BunsDev commentedon Oct 27, 2026
Unit 5766: on Val's decision (2026-10-27), stopping the orphaned Xcode
DTServiceHub(pid 89553, running about 1 day under launchd, cwd in the unit) with SIGTERM. Xcode restarts the hub on demand. Then: move.verification/with hash checks, and retire the unit against the existing archive tagarchive/issue-5766-automated-qualification-wip-2026-10-27.BunsDev commentedon Oct 27, 2026
Unit 5766: retired (2026-10-27)
DTServiceHub(pid 89553) ignored SIGTERM and was stopped with SIGKILL, on Val's decision..verification/, 67,047 files and 5,642,360 KiB, moved to.superpowers/archive/2026-10-26-retired-worktrees/raw/issue-5766-automated-qualification/verification/. A SHA-256 manifest was written before the move and checked after it.archive/issue-5766-automated-qualification-wip-2026-10-27(a480caa98, parent0e150c14b). The reuse check confirmed the plan matches the tag byte for byte.--retained-by-remote-tag, removal was non-forced, and the branch was compare-and-deleted.BunsDev commentedon Oct 27, 2026
Bounded batch addition (session 7fcd2b86, same profile): retire
.worktrees/issue-6290-release-playwright-image+ci/issue-6290-release-playwright-image@2a20047c5fbe8e4dbc24a54d058dd95e5f2c2aff. That's the exact head of merged #6293 (→f0411258e), retained atrefs/pull/6293/head.BunsDev commentedon Oct 27, 2026
Post-delivery curation checkpoint for session 01a17ea2-b40d-7e40-8a96-2195a6288883 under the active UX/reliability/curation goal. Exact candidate: fix/issue-6209-unavailable-drain-report and .worktrees/issue-6209-unavailable-drain-report at 43ab073. PR #6300 merged as 0582488; refs/pull/6300/head freshly advertises the exact source head. This session owns the unit, has finished implementation and releases it for a guarded local-only retirement pass once every required proof succeeds. No remote deletion is requested. Delivery receipt: #6209 (comment).
Current decision: PRESERVE - uncertain. Tracked/untracked status is clean; no process CWD matches this exact unit; repository-scoped Coven claims are empty. The sessions CLI has no scope filter and was not used to retrieve unscoped private metadata. A read-only SQLite query constrained before retrieval to this exact worktree or descendants returns no session metadata; no titles, messages, transcripts or other workspace records were retrieved. The shared surface-claim file nevertheless retains entries for sessions 7fcd2b86 (#6215) and a44f9796 (#6295). Those unresolved records are not expiry-based clearance and remain untouched. The complete branch-curator exclusion/ownership proof has not passed and no maintenance lease or DELETE classification is claimed. Ignored state comprises node_modules, tsconfig.tsbuildinfo and server.mjs; the first two are policy-listed generated paths, while server.mjs needs an explicit generated-artifact disposition before removal.
Next: reconcile the remaining claim/exclusion evidence, record the bounded local retirement profile, and complete fresh issue, PR, workflow, recovery-OID and strict-guard checks before any removal. The detached run-6275-01a17ea2 unit remains PRESERVE - recovery because its paused merge and unique correction/evidence are not fully dispositioned. No worktree or branch was removed in this pass; the modal implementation and all foreign units remain intact.
BunsDev commentedon Oct 28, 2026
Backlog review: Keep: guarded curation coordination. The latest checkpoint preserves uncertain units and unresolved claims; age, merge state and missing processes are insufficient deletion proof.
Next step: Resolve owner/claim and generated-artifact disposition for the exact proposed units before any retirement.
Long-running goal prompt
Continue #6179 only for an explicitly authorized exact candidate set using branch-curator. Refresh OIDs, ownership/exclusion receipts, clean and ignored-state disposition, remote retention and recovery evidence. Preserve dirty, locked, paused or uncertain units, including unresolved claims. Record each verified removal or owner-backed preservation; do not infer blanket permission from this prompt, a merged squash PR or an idle status. No agent remote deletion or release.
Read AGENTS.md and work-continuity; refresh this issue, its original criteria, all comments, linked PRs and exact main/head state first. Preserve existing owners, human decisions and private-state boundaries. Continue an owned unit only with current authority; otherwise provide a handoff. Record exact source/artifact identities, tests, first failures/retries/skips, blocker and imperative next step. Commit/push/merge, deletion, provider/device use and release require the applicable current authority; this saved prompt grants none. Close only after every original criterion is proven or explicitly dispositioned.
Follow-up prompt
Continue #6179 from its latest verified checkpoint, keeping the full original outcome and acceptance criteria. Refresh the bounded candidate ledger and strict guard proofs; retire only authorized units that pass every proof and preserve the rest with a named next action. Re-read current ownership, PR heads, decisions and retained evidence; poll a confirmed live handle before retrying work. Distinguish delivered code from acceptance, and finish ready authorized work. If blocked, name the responsible actor and one imperative unblock step; do not fabricate acceptance or silently take over.
Review basis: latest recorded checkpoint, the issue body and paginated comments, current open-PR inventory and main
206d7fb613d976a1c7a65c32fdcc78c7ca642880. GitHub Issues and Project 9 membership were inspected; Project field status and private execution liveness are not asserted. This is a saved continuation prompt, not implementation, owner acknowledgement, new permission or a state/assignment change. Earlier evidence remains tied to its recorded source.BunsDev commentedon Oct 31, 2026
Agent dependency navigation
Relationship: Continuation of this canonical outcome; existing implementation and acceptance owners are preserved. Acting agent: Codex, GitHub queue maintenance only; no branch/worktree or execution lease claimed.
Read the latest recorded checkpoint before using the long-running and follow-up prompts. Newer owner evidence and explicit decisions take precedence over older prompt checkpoints; preserve the complete original criteria and every first failure, retry, skip and unsupported row. Parent/companion links do not create start blockers. A closed dependency issue or merged source change does not prove this issue’s device, human, release or exact-profile completion gates.
Workflow precedence: GitHub Issues are the canonical queue. Legacy Bead instructions and old proposed/not-implemented checkpoints are historical context; use current owner evidence and explicit human decisions, without creating a second tracker.
Coverage and delivery: Repository-scoped issue body and all paginated comments, open PR inventory and native issue relations inspected on 2026-10-31. All 50 open issues are present in Cave Project 9; Status and Blocked by fields were read through the projectsV2 REST endpoint. Private execution liveness remains unknown; Started alone does not prove it. This is a recorded-only routing handoff, not owner acknowledgement, implementation, approval or completion. Refresh live ownership and exact heads before execution; honor existing approval requirements.
BunsDev commentedon Nov 2, 2026
Curation checkpoint (2026-11-02): nothing retired, all units preserved
Resumed from the dependency-navigation routing at Val's request. This pass was read-only.
origin/mainis46e8e2789403d6f6743456dcb7691bc5e9f191c7.Budget: 8 worktrees counting the primary, well under the 28-worktree limit, so budget pressure no longer drives this issue. Every worktree in the 2026-10 candidate tables has already been retired or is gone.
issue-6353-client-heapfix/issue-6353-client-heap@b03e941e1issue-6357-analytics-agreefix/issue-6357-analytics-agree@bd93031eatest-upstream-api-anomaliestest/issue-6359-upstream-api-anomalies@b1891dc1dissue-6303-boundary-recoverysecurity/issue-6303-boundary-recovery@796f4c206issue-6353-soak-validationb03e941e1test/issue-6353-soak-validation@c1469c6cdorigin/test/issue-6353-soak-validation; no PR; #6353 openissue-5840-viewport-verifytest/issue-5840-viewport-verify@e1cc80197refs/pull/6323/head; 2 untracked verification configs (__mobile.config.ts,__viewports.config.ts); auto-locked; #5840 stays open for the human screen-reader passverify-5907-header-on-mainverify/issue-5907-header-on-main@f2fad5372(old main, no unique commits)apps/ios/CovenCave/build/mainRepository-scoped
coven claim statusreturned no claims. No process has its working directory inside any.worktrees/unit. Coven session coverage was not retrieved, so it is unknown.No worktree, branch, tag or remote ref was changed. No deletion profile or maintenance lease was taken.
Next: retire
issue-5840-viewport-verifyonly on Val's explicit decision, by archiving or discarding its two configs and then removing it without force under the strict guard.verify-5907-header-on-mainneeds its creating session to record an owner and disposition. The remaining units retire when their PRs merge.