Development record
Nothing removed the spent worktrees and branches after the v0.13.0 cut (tagged 2026-10-05), so the checkout still carries work that is already on main, and abcd peers reports 35 live peers and 51 differing records, which buries what is actually in flight.
Nothing removed the spent worktrees and branches after the v0.13.0 cut (tagged 2026-10-05), so the checkout still carries work that is already on main, and abcd peers reports 35 live peers and 51 differing records, which buries what is actually in flight.
Spent, with the work on origin/main and the worktree clean:
- worktrees: bump (chore/bump-x-text), dr6Spec (docs/build-loop-parallel-lanes), drainGuard (fix/guard-default-word-set), run-B (detached), agentsSwitch (fix/one-conventions-file-own-switch), board-readability (docs/board-readability, landed under another commit), board2 (feat/board-renderer), e8termr3 (fix/guard-link-bound), postcut (chore/post-cut-captures), scan50 (chore/capture-test-home-spellings);
- local branches with no worktree: chore/capture-dependabot-gate, feat/audit-owed-flag, feat/loop-parallel-lanes, fix/arm-only-under-review, integ/land-24d, plan/consistency-followups, plan/worktree-store-review, release/v0.12.0, release/v0.12.0-r2, fix/scanner-selector-closing-call (superseded by #779);
- remote branches: origin/fix/scanner-selector-closing-call (#777 closed, superseded) and origin/docs/capture-sibling-repo-owner-redaction (#749 closed; its record iss-2609291409053602 is resolved on main, the condition its closing comment set for deleting the branch).
Unlanded and unruled: worktrees A, B, C, D, E1, E2, F and integration (the 2 September security-sweep lanes, 10 to 124 commits each, none on main) and 18 local branches with no worktree (phase-9/* and readings/opening-run, 18 to 190 commits each, the cold-reading Iteration 2 work). Nobody has said whether they are kept or dropped. The September worktrees also sit under the abbreviated store key 488a0aa9, which AGENTS.md says names a directory no verb reads.
itd-118 (draft) is the automated form of this cleanup; until it ships, the release cut has no step that does it by hand. Related: a record captured on 2 September and held only on those unlanded branches says nothing maintains the worktree convention.
2026-11-02: origin/fix/statusline-tests-widen-git-budget (#1283 closed, superseded by the merged #1281) still stands. The guard's git-delete-unproven refuses deleting it, since its tip is merged by no route the guard can prove, and only the person can allow each delete, one command at a time. A cleanup verb would need to put the list to the person for one ruling.
Frontmatter
| id | iss-2610050532499080 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610050532499080-spent-worktrees-and-branches-survive-the.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2609291409053602The scanner still masks the repository owner's public GitHub handle when it names a sibling repository of the same owner, e.g. <owner>/<sibling> written in a record of <owner>/<repo>. isOwnRepoSlug (internal/adapter/scanner/identity.go) exempts the owner only in the repository's own owner/repo slug, so a managed repo that publishes to a sibling repo loses the handle in every record naming it, and each one is restored by hand. Extend the exemption to the remote's owner followed by '/<any repo name>', since that owner is public by the same argument; the owner alone and other owners stay masked. Reported from a managed repository that publishes to a sibling repository of the same owner.
- itd-118Merged work leaves no residue: abcd-managed repos delete a PR branch on merge, and abcd tidies the stale local branch, tracking ref, and worktree