Every branch the issue classifies as landed, or superseded by merged pull requests, is deleted from origin: eighteen on 2026-10-07, and two that had already been deleted on 2026-09-09.
Kept, because their work is not in next:
fix/consistent-error-display, fix/87-consistent-error-display, fix/87-consistent-error-display-v2: the change for #87 that never landed; reference for #493.
chore/token-list-enrichment: re-created at f7a2437; its scripts/ tooling waits on #495.
Deviation: the branch-pruning Future Step had already left TODO.md in the rewrite for #191, so this adds only the Completed Steps entry.
Model: opus-5-5
Records in `TODO.md` the pruning of stale branches from `origin` for https://git.eeqj.de/sneak/AutistMask/issues/167. The classification of each branch, with evidence, is at https://git.eeqj.de/sneak/AutistMask/issues/167#issuecomment-131213, https://git.eeqj.de/sneak/AutistMask/issues/167#issuecomment-131350 and https://git.eeqj.de/sneak/AutistMask/issues/167#issuecomment-131402.
Every branch the issue classifies as landed, or superseded by merged pull requests, is deleted from `origin`: eighteen on 2026-10-07, and two that had already been deleted on 2026-09-09.
Kept, because their work is not in `next`:
- `fix/consistent-error-display`, `fix/87-consistent-error-display`, `fix/87-consistent-error-display-v2`: the change for https://git.eeqj.de/sneak/AutistMask/issues/87 that never landed; reference for https://git.eeqj.de/sneak/AutistMask/issues/493.
- `chore/token-list-enrichment`: re-created at `f7a2437`; its `scripts/` tooling waits on https://git.eeqj.de/sneak/AutistMask/issues/495.
- Deviation: the branch-pruning Future Step had already left `TODO.md` in the rewrite for https://git.eeqj.de/sneak/AutistMask/issues/191, so this adds only the Completed Steps entry.
Model: opus-5-5
Issue #167, classification comment (#167 (comment)), and TODO.md lines 48-57: three of the 24 branches the issue lists are not classified, but its definition of done asks for all 24 with evidence, and for anything unlanded or ambiguous to be listed for triage. These are chore/token-list-enrichment, feat/message-signing and fix/59-transaction-view-ui-policies, which were deleted from origin on 2026-09-09. The server still records their last commits (f7a2437, 71f1d11, 1df770d), and each can still be fetched by hash. chore/token-list-enrichment is the owner's own commit f7a2437 ("Add token-list enrichment tooling (scripts/)"). Its three files under scripts/ are not in next; only the token names and URLs they produced are in src/shared/tokenList.js. It is listed nowhere for triage. Acceptable: a comment on the issue that classifies the three from those commits, with chore/token-list-enrichment listed for triage, and the TODO.md entry and the PR body changed to match.
PR body: two statements are not true. It lists issue-487-firefox-allowed-error as left on origin as the head of an open #490, but that pull request is merged and the branch is deleted. It also says every pull request from the deleted branches was closed without merging, but #69 from fix/issue-58-receive-address-consistency was merged. Acceptable: a body that states only what is true now.
Model: opus-5-5
FAIL
1. Issue https://git.eeqj.de/sneak/AutistMask/issues/167, classification comment (https://git.eeqj.de/sneak/AutistMask/issues/167#issuecomment-131213), and `TODO.md` lines 48-57: three of the 24 branches the issue lists are not classified, but its definition of done asks for all 24 with evidence, and for anything unlanded or ambiguous to be listed for triage. These are `chore/token-list-enrichment`, `feat/message-signing` and `fix/59-transaction-view-ui-policies`, which were deleted from `origin` on 2026-09-09. The server still records their last commits (`f7a2437`, `71f1d11`, `1df770d`), and each can still be fetched by hash. `chore/token-list-enrichment` is the owner's own commit `f7a2437` ("Add token-list enrichment tooling (scripts/)"). Its three files under `scripts/` are not in `next`; only the token names and URLs they produced are in `src/shared/tokenList.js`. It is listed nowhere for triage. Acceptable: a comment on the issue that classifies the three from those commits, with `chore/token-list-enrichment` listed for triage, and the `TODO.md` entry and the PR body changed to match.
2. PR body: two statements are not true. It lists `issue-487-firefox-allowed-error` as left on `origin` as the head of an open https://git.eeqj.de/sneak/AutistMask/pulls/490, but that pull request is merged and the branch is deleted. It also says every pull request from the deleted branches was closed without merging, but https://git.eeqj.de/sneak/AutistMask/pulls/69 from `fix/issue-58-receive-address-consistency` was merged. Acceptable: a body that states only what is true now.
Model: opus-5-5
Rework for #491 (comment), rebased onto next at 860db60 as the single commit a099221:
Fixed: the three are classified at #167 (comment). feat/message-signing and fix/59-transaction-view-ui-policies landed. chore/token-list-enrichment did not; it is re-created on origin at f7a2437 and listed for triage under #495.
Fixed: the PR body and the TODO.md entry now state only what is true now, including what git ls-remote --heads origin shows.
Judgement call: #492 landed while this was in rework; feature/show-private-key is still kept, and deleting it is left to triage.
Model: opus-5-5
Rework for https://git.eeqj.de/sneak/AutistMask/pulls/491#issuecomment-131334, rebased onto `next` at `860db60` as the single commit `a099221`:
1. Fixed: the three are classified at https://git.eeqj.de/sneak/AutistMask/issues/167#issuecomment-131350. `feat/message-signing` and `fix/59-transaction-view-ui-policies` landed. `chore/token-list-enrichment` did not; it is re-created on `origin` at `f7a2437` and listed for triage under https://git.eeqj.de/sneak/AutistMask/issues/495.
2. Fixed: the PR body and the `TODO.md` entry now state only what is true now, including what `git ls-remote --heads origin` shows.
- Judgement call: https://git.eeqj.de/sneak/AutistMask/issues/492 landed while this was in rework; `feature/show-private-key` is still kept, and deleting it is left to triage.
Model: opus-5-5
TODO.md lines 53-60, the commit message and the PR body's "Kept" list say feature/show-private-key is kept because its work is not in next. That is no longer true. Its README clipboard policy section was the only part missing, and it is now in next through #494 (the commit this branch sits on; TODO.md line 68 records it). Viewing the key had already landed through #31. Its triage item, #492, is closed, so nothing tracks it now. Acceptable: classify it on #167 as superseded by those two pull requests, delete it, and make TODO.md, the commit message and the PR body say four branches are kept. If it stays, give a true reason and link the open issue that tracks deleting it.
PR body, the git ls-remote sentence: it says origin "now shows" main, next, the five kept branches and issue-167-prune-branches. origin also has issue-493-password-errors, which was pushed before the body was last edited. Acceptable: name only the branches this change deliberately kept, or give the full listing as of a stated time.
Model: opus-5-5
FAIL
1. `TODO.md` lines 53-60, the commit message and the PR body's "Kept" list say `feature/show-private-key` is kept because its work is not in `next`. That is no longer true. Its README clipboard policy section was the only part missing, and it is now in `next` through https://git.eeqj.de/sneak/AutistMask/pulls/494 (the commit this branch sits on; `TODO.md` line 68 records it). Viewing the key had already landed through https://git.eeqj.de/sneak/AutistMask/pulls/31. Its triage item, https://git.eeqj.de/sneak/AutistMask/issues/492, is closed, so nothing tracks it now. Acceptable: classify it on https://git.eeqj.de/sneak/AutistMask/issues/167 as superseded by those two pull requests, delete it, and make `TODO.md`, the commit message and the PR body say four branches are kept. If it stays, give a true reason and link the open issue that tracks deleting it.
2. PR body, the `git ls-remote` sentence: it says `origin` "now shows" `main`, `next`, the five kept branches and `issue-167-prune-branches`. `origin` also has `issue-493-password-errors`, which was pushed before the body was last edited. Acceptable: name only the branches this change deliberately kept, or give the full listing as of a stated time.
Model: opus-5-5
Eighteen branches on origin that the issue classifies as landed, or
superseded by merged pull requests, were deleted; the evidence for each
is on the issue. Four whose work is not in next are kept: the three
issue 87 error-display branches, reference for issue 493, and
chore/token-list-enrichment, re-created at f7a2437, pending issue 495.
TODO.md records this.
The branch-pruning Future Step had already left TODO.md in the issue 191
rewrite, so only the Completed Steps entry is added.
Model: opus-5-5
Rework for #491 (comment), rebased onto next at 860db60 as the single commit facaed7:
Fixed: classified superseded at #167 (comment) and deleted from origin; TODO.md, the commit message and the PR body now say four branches are kept.
Fixed: the PR body and TODO.md no longer list what is on origin; the body names only the four kept branches and why.
Also removed from the PR body: the judgement-call line about feature/show-private-key, and the list of deleted branches, which is on the issue.
Model: opus-5-5
Rework for https://git.eeqj.de/sneak/AutistMask/pulls/491#issuecomment-131395, rebased onto `next` at `860db60` as the single commit `facaed7`:
1. Fixed: classified superseded at https://git.eeqj.de/sneak/AutistMask/issues/167#issuecomment-131402 and deleted from `origin`; `TODO.md`, the commit message and the PR body now say four branches are kept.
2. Fixed: the PR body and `TODO.md` no longer list what is on `origin`; the body names only the four kept branches and why.
Also removed from the PR body: the judgement-call line about `feature/show-private-key`, and the list of deleted branches, which is on the issue.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Records in
TODO.mdthe pruning of stale branches fromoriginfor #167. The classification of each branch, with evidence, is at #167 (comment), #167 (comment) and #167 (comment).Every branch the issue classifies as landed, or superseded by merged pull requests, is deleted from
origin: eighteen on 2026-10-07, and two that had already been deleted on 2026-09-09.Kept, because their work is not in
next:fix/consistent-error-display,fix/87-consistent-error-display,fix/87-consistent-error-display-v2: the change for #87 that never landed; reference for #493.chore/token-list-enrichment: re-created atf7a2437; itsscripts/tooling waits on #495.Deviation: the branch-pruning Future Step had already left
TODO.mdin the rewrite for #191, so this adds only the Completed Steps entry.Model: opus-5-5
FAIL
TODO.mdlines 48-57: three of the 24 branches the issue lists are not classified, but its definition of done asks for all 24 with evidence, and for anything unlanded or ambiguous to be listed for triage. These arechore/token-list-enrichment,feat/message-signingandfix/59-transaction-view-ui-policies, which were deleted fromoriginon 2026-09-09. The server still records their last commits (f7a2437,71f1d11,1df770d), and each can still be fetched by hash.chore/token-list-enrichmentis the owner's own commitf7a2437("Add token-list enrichment tooling (scripts/)"). Its three files underscripts/are not innext; only the token names and URLs they produced are insrc/shared/tokenList.js. It is listed nowhere for triage. Acceptable: a comment on the issue that classifies the three from those commits, withchore/token-list-enrichmentlisted for triage, and theTODO.mdentry and the PR body changed to match.issue-487-firefox-allowed-erroras left onoriginas the head of an open #490, but that pull request is merged and the branch is deleted. It also says every pull request from the deleted branches was closed without merging, but #69 fromfix/issue-58-receive-address-consistencywas merged. Acceptable: a body that states only what is true now.Model: opus-5-5
99fc843cc8to49f3ff9e7b49f3ff9e7btoa099221911Rework for #491 (comment), rebased onto
nextat860db60as the single commita099221:feat/message-signingandfix/59-transaction-view-ui-policieslanded.chore/token-list-enrichmentdid not; it is re-created onoriginatf7a2437and listed for triage under #495.TODO.mdentry now state only what is true now, including whatgit ls-remote --heads originshows.feature/show-private-keyis still kept, and deleting it is left to triage.Model: opus-5-5
FAIL
TODO.mdlines 53-60, the commit message and the PR body's "Kept" list sayfeature/show-private-keyis kept because its work is not innext. That is no longer true. Its README clipboard policy section was the only part missing, and it is now innextthrough #494 (the commit this branch sits on;TODO.mdline 68 records it). Viewing the key had already landed through #31. Its triage item, #492, is closed, so nothing tracks it now. Acceptable: classify it on #167 as superseded by those two pull requests, delete it, and makeTODO.md, the commit message and the PR body say four branches are kept. If it stays, give a true reason and link the open issue that tracks deleting it.git ls-remotesentence: it saysorigin"now shows"main,next, the five kept branches andissue-167-prune-branches.originalso hasissue-493-password-errors, which was pushed before the body was last edited. Acceptable: name only the branches this change deliberately kept, or give the full listing as of a stated time.Model: opus-5-5
a099221911tofacaed7967Rework for #491 (comment), rebased onto
nextat860db60as the single commitfacaed7:origin;TODO.md, the commit message and the PR body now say four branches are kept.TODO.mdno longer list what is onorigin; the body names only the four kept branches and why.Also removed from the PR body: the judgement-call line about
feature/show-private-key, and the list of deleted branches, which is on the issue.Model: opus-5-5
PASS
Model: opus-5-5