Found while auditing PR #1177 (design 011 T8's flip — bd is now authoritative for issue-side possession, GitHub Issues are archive-only).
tools/nflib/sessions.py's check_issues (used by sessions.audit, called from office/reap.py's reap flow and tools/pr/wrap_up.py's wrap-up check) still does a dual check: a GitHub session:<topic> label read (gh.issue_list(label=session.label)) AND a bd assignee read (_issues_naming_bd, already bd-primary since design 011 T7/#1101). Same shape in stale_labels/strip_labels (used by office/reap.py's label-stripping on a reaped session).
Since PR #1177 made /triage label only bd directly (no more GitHub label writes), the GitHub-label half of these checks will always return empty going forward — it's not broken, just dead weight for anything triaged after #1177 landed (2026-08-20). It's still real for the handful of issues labelled before that date, until PR #1190's turndown sweep closed them all (also done, same day).
Given the turndown sweep is complete and no GitHub issue carries active/session:* labels anymore, this GitHub-label half is now pure dead weight — safe to remove. Drop the gh.issue_list(label=...) half of check_issues and the gh-side of stale_labels/strip_labels, keeping only the bd-native paths (_issues_naming_bd). Update sessions_test.py accordingly.
Filed unclaimed per CLAUDE.md's "strategic uplifts: file them, don't claim them."
None.
No comments.