🤖 Generated by the Daily AI Engineer (agent-improver)
Why
The flow scorecard's WIP section measures project-5 items, but its throughput/cycle-time proxy counts every closed issue org-wide. Work that closes off-board — a repo inside the board's known coverage gap (#2237), or a private-repo issue deliberately kept off the public board — moves the duration distribution even though it never traversed the Kanban the metric claims to describe. Raised in review on #2276.
What
Intersect the throughput population with board membership once doing so is affordable and honest: today a per-issue board lookup across ~280 closures per window is the same GraphQL cost that killed the scorecard's first live run, and intersecting before #2237 lands would make the flow metric silently inherit the coverage gap instead of exposing it.
Acceptance criteria
Part of #2271
Why
The flow scorecard's WIP section measures project-5 items, but its throughput/cycle-time proxy counts every closed issue org-wide. Work that closes off-board — a repo inside the board's known coverage gap (#2237), or a private-repo issue deliberately kept off the public board — moves the duration distribution even though it never traversed the Kanban the metric claims to describe. Raised in review on #2276.
What
Intersect the throughput population with board membership once doing so is affordable and honest: today a per-issue board lookup across ~280 closures per window is the same GraphQL cost that killed the scorecard's first live run, and intersecting before #2237 lands would make the flow metric silently inherit the coverage gap instead of exposing it.
Acceptance criteria
Part of #2271