Twinned from https://github.com/cfsh/ninefold/issues/1103 by tools/beads/import_github.py's reconcile pass.
Suggestions from ninefold-reviewer's review of #1099
emit_issues_bd only excludes status == "closed" (tools/pr/digest.py, in the new emit_issues_bd's bd.list_issues() filter). bd's own status vocabulary also has deferred (per design 011 T4's board columns: open/in_progress/blocked/deferred/closed), and design 011 T3's card specifies operationalize_design.py --close sets an epic's children to deferred (not closed) when the epic itself closes. bd update <id> --status deferred is also just a standing bd primitive any session can run today, independent of T3. Net effect: once anything sets a bd issue's status to deferred — whether via a future T3 --close or a manual bd update, both possible today — that issue will render in the digest's OPEN ISSUES · COVERAGE · OWNERSHIP section forever as [UNCOVERED] backlog, indistinguishable from genuinely open work. notes/beads.md confirms bd list --json "dumps everything" (all statuses), so nothing upstream filters this for the digest.
Suggested fix: exclude (or distinctly reclassify, mirroring how meta issues are handled) deferred alongside closed in that filter, plus a test creating a deferred issue and asserting it's excluded/reclassified.
Not blocking — nothing today produces a deferred bd issue on the default path (T3 hasn't landed), so this is latent. Filed unclaimed per CLAUDE.md's "strategic uplifts: file them, don't claim them."
None.
No comments.