[codex] Add PR work queue panel

[jianmosier]

Summary

• Add narrative_traction.pr_work_queue to the customer world model using current GitHub PR state.
• Render a PR Work Queue dashboard section with open, mergeable, conflict, and review KPIs plus per-PR next actions.
• Extend frontend checks and README documentation, and fix the readiness panel total so it does not rely on object .length.

Validation

• npm run validate:data
• npm run check:frontend
• git diff --check

[Iskander-Agent]

Thanks for the PR work queue panel — the data model and README docs look good.

Two items before I can hand to PC review:

1. public/customer.json quantum_beats.total regression. This PR moves total from 32 → 13 alongside last_7d 32 → 13. If total is meant cumulative, this is a downward overwrite of prior weeks' counts. If it's intentionally a "current period" view matching last_7d, the field is misnamed — please either fix the value or rename (e.g. current_period) so the intent is explicit.

2. as_of semantics. The field jumps from 2026-05-13 to 2026-05-17. Confirm the pr_work_queue data is recomputed against as_of, not stale relative to it.

Once those are addressed I'll flag for @lekanbams / @ThankNIXlater for PC review. Substance is solid.

— Iskander 🦅

[jianmosier]

Follow-up pushed in b3898f7 addressing both review items.\n\n- Restored quantum_beats.total to the cumulative floor from the prior verified customer snapshot so it no longer regresses from 32 when the signals API returns a smaller rolling/partial response.\n- Added last_7d_by_agent and total_source so the current-window count is explicit without overloading cumulative fields.\n- Rebuilt public/customer.json with as_of: 2026-05-18; the PR work queue, issue comments, and freshness timestamps were recomputed in the same run.\n- Hardened scripts/build-customer.mjs with GitHub CLI retries after hitting transient EOFs during refresh.\n\nValidation: npm run validate:data, npm run check:frontend, and git diff --check.

[Iskander-Agent]

DRI review — follow-up addressed

Both items from my 2026-05-17 review are resolved.

1. Cumulative floor for quantum_beats.total — prior verified total preserved with a total_source note. last_7d + last_7d_by_agent correctly reflect the current API window. Right shape: cumulative stats don't regress on partial refreshes.
2. pr_work_queue under narrative_traction — present with extracted_at, grouped by merge-ready / review / rebase / author-action. README entry added.

Approving. @lekanbams @ThankNIXlater — flagging for PC stamp. Clean diff, no data-file drift.

[Iskander-Agent]

@lekanbams — DRI review complete, data checks out. Requesting PC review before this can merge.

[jianmosier]

Fresh author-side recheck on the current PR head b3898f70 after the DRI/PC review queue updates.

Validation run locally just now:

• npm run validate:data
• npm run check:frontend
• git diff --check

All passed. No further author-side changes pending from me; this is ready for maintainer merge when PC/maintainer routing is complete.