Repository navigation
Description
Residual of #1203 after PR #3311 merged (8ee2e1c).
What landed
pm-stack/aggregator/src/sources/ready-for-agent.ts now reads the harness live and exports dispatchStateFor(state, projectPath, issueNumber) — the work item's real state, or the explicit "not picked up". The harness facet (backend readiness, repository settings, work-item counts, GraphQL errors) is on /health and /api/health, and a failed harness read degrades health rather than hiding.
What is still not met
Acceptance item 3 of #1203 has two halves. The second half — "harness status appears on /health" — is met. The first half — "An issue labelled ready-for-agent shows its real dispatch state or an explicit 'not picked up'" — is not wired to any rendered surface: dispatchStateFor() has no production caller, and src/derive.ts:21 still counts the ready-for-agent label itself as implementing, so a labelled-but-undispatched issue still claims dispatch it never got.
Scope
- Give the aggregator a place to resolve RFA state for the issues it renders (the
rfafacet reachable from the item/board build path, cached as it already is). - Render the per-issue dispatch state on the item page and carry it in the item's JSON twin — real work-item state, or the literal "not picked up"; never inferred from the label.
- Stop
derive.ts'sIMPLEMENTING_LABELSfrom treating the bare label as dispatch proof, or label it explicitly as an inference next to the real state.
Acceptance
- An item page for an issue labelled
ready-for-agentshows the harness's real work-item state, ornot picked upwhen the harness has no work item for it. - The item's JSON twin carries the same dispatch state with its provenance.
- A test covers both the picked-up and not-picked-up cases (fixture state, no live harness needed).
- The label alone no longer reads as "implementing" without the dispatch state beside it.
Activity
developing-today commentedon Nov 3, 2026
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 8108 (small_fix, queued, priority 40) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
33 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 5, 2026
🤖 Agent note · bound
dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off