beads/issueops
CI Bot 0dd0133eaa refactor(ready): derive the --explain filter from workapi (bd-3fs.3)
bd-ehi collapsed the two ready-default builders into
workapi.BuildReadyFilter. A third fixed copy survived: runReadyExplain and
runReadyProxiedExplain each inlined WorkFilter{Status: StatusOpen,
SortPolicy: SortPolicyPriority}, so a change to what "ready" means would
have moved the listing and left the diagnostic explaining a different set.

Both now call readyExplainFilter, which asks the shared builder. The limit
stays 0 rather than taking workapi.DefaultReadyLimit: --explain is a
whole-graph diagnostic, and inheriting the listing's 100 would explain part
of a larger graph while reading as though it had explained all of it.

The forbidigo exemption for cmd/bd/ready*.go stays - readyInput still
carries a types.WorkFilter field, and the blocked views still pass a bare
one - but its reason no longer claims --explain takes readyInput's filter,
because it does not and now visibly builds its own.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-01 05:52:49 +00:00
..
errors.go feat(storage): one guarded issue-lifecycle surface for the CLI and linked consumers (#5191) 2026-07-31 11:26:38 -07:00
issueops.go feat(update): enforce close policy when a status update crosses into done (#5206) 2026-07-31 18:23:06 -07:00
issueops_external_test.go feat(storage): one guarded issue-lifecycle surface for the CLI and linked consumers (#5191) 2026-07-31 11:26:38 -07:00
reader.go refactor(ready): derive the --explain filter from workapi (bd-3fs.3) 2026-08-01 05:52:49 +00:00