backlog-burndown "Grouping and File Claims" enumerates in-flight branches with three reads and then says "A branch no claim comment covers still has to yield a file set", reading the branch directly. One of the four inputs is bounded and three are not, and the combination converts every stale remote ref in the repository into a permanent file claim.
- The pull-request read is bounded: "the files changed by every open feature pull request".
git worktree list, git branch -r, and git branch are bounded by nothing.
A feature branch whose pull request already merged, but whose remote ref was never deleted, is still in git branch -r. A squash merge leaves its commits off develop, so git diff --name-only origin/develop...<branch> still reports its full file set. It carries no claim comment, so the fallback read applies, and no liveness test, merged-state test, or age test anywhere in the section retires it.
This repository currently carries roughly thirty such refs, which is separately tracked as branch-cleanup work. A first round run here would therefore defer nearly every group it forms and end reporting nothing it can act on, which is a throughput defeat rather than a safety failure but is enough to make the skill unusable on the repository that authors it.
The section needs a liveness test on the branch reads, matching the one the pull-request read already has. Candidates: exclude a branch whose pull request is merged or closed, exclude a branch with no open pull request and no claim comment and no registered worktree, or bound by age. Which one is a design call, since each has a different failure mode for a branch that is genuinely in flight but not yet pushed to a pull request.
A smaller item in the same bullet: "Exclude the open promotion pull request from that enumeration" excludes the pull request but not origin/develop, origin/main, and origin/HEAD, which both git branch -r and git branch enumerate and which carry no claim comment, so the fallback read applies to them too. Harmless while main and develop agree, and it claims files the moment main carries something develop does not.
This is distinct from #1274, which is about a branch this run itself abandoned. This one is about branches the run never created and cannot reason about.
Raised by the local-strict-review carried-content passes on the pull request that added this skill, and deferred there under that skill's own review-round budget.
backlog-burndown"Grouping and File Claims" enumerates in-flight branches with three reads and then says "A branch no claim comment covers still has to yield a file set", reading the branch directly. One of the four inputs is bounded and three are not, and the combination converts every stale remote ref in the repository into a permanent file claim.git worktree list,git branch -r, andgit branchare bounded by nothing.A feature branch whose pull request already merged, but whose remote ref was never deleted, is still in
git branch -r. A squash merge leaves its commits off develop, sogit diff --name-only origin/develop...<branch>still reports its full file set. It carries no claim comment, so the fallback read applies, and no liveness test, merged-state test, or age test anywhere in the section retires it.This repository currently carries roughly thirty such refs, which is separately tracked as branch-cleanup work. A first round run here would therefore defer nearly every group it forms and end reporting nothing it can act on, which is a throughput defeat rather than a safety failure but is enough to make the skill unusable on the repository that authors it.
The section needs a liveness test on the branch reads, matching the one the pull-request read already has. Candidates: exclude a branch whose pull request is merged or closed, exclude a branch with no open pull request and no claim comment and no registered worktree, or bound by age. Which one is a design call, since each has a different failure mode for a branch that is genuinely in flight but not yet pushed to a pull request.
A smaller item in the same bullet: "Exclude the open promotion pull request from that enumeration" excludes the pull request but not
origin/develop,origin/main, andorigin/HEAD, which bothgit branch -randgit branchenumerate and which carry no claim comment, so the fallback read applies to them too. Harmless while main and develop agree, and it claims files the moment main carries something develop does not.This is distinct from #1274, which is about a branch this run itself abandoned. This one is about branches the run never created and cannot reason about.
Raised by the local-strict-review carried-content passes on the pull request that added this skill, and deferred there under that skill's own review-round budget.