Repository navigation
Dashboard comments: add a pending/triage queue view and make comment counts kind-aware #1210
Description
Part of epic #1184 (PM stack coherence review, 2026-10-26).
Comment UX has no pending-queue view, counts conflate kinds, and failure copy promises a retry that does not exist. Evidence: comments.ts CommentsStore.counts() counts all kinds per object, so comment badges cannot signal 'awaiting triage'; pending counts exist only inside /api/comments.json and are rendered by no page. Failed GitHub comments read 'a fleet poster will retry', but no retry code exists, and there is no edit/delete/retract for any kind.
Acceptance:
- Every state=new/pending/failed comment in the store is reachable in <=2 clicks from the nav via a queue view (or Needs-you section).
- Badge counts distinguish notes from actionable comments by kind/state.
- Failed items show age + last error, and retry copy is corrected until a retry exists.
Acceptance criteria
- Every state=new/pending/failed comment in the store is reachable in ≤2 clicks from the nav via a queue view (or Needs-you section).
- Badge counts distinguish notes from actionable comments by kind/state.
- Failed items show age + last error, and retry copy is corrected until a retry exists.
Metadata
Metadata
Assignees
Labels
pm-stack (Pad/Grist) in developing-today/codeMedium: expected under 1 day of workNew feature or capability requestIntake review done: acceptance criteria, links, and normalized labels addedOrdinary priority (the default)Queue worker lifecycle stateFiled directly by a humanQueue worker lifecycle stateQueue worker lifecycle state
Activity
developing-today commentedon Oct 27, 2026
CODE-344
dezren39 commentedon Oct 28, 2026
Intake review
Fleet-monitor intake pass (protocol §5), 2026-10-28.
Still live: verified this run — the issue is open, and a merged-PR search found no PR that explicitly resolves it (no fixes-reference; the only real merged hit in the search set, PR #1318, does not mention it). It does not merely look solved.
Related: Related: epic #1184; the comment loop is also the subject of #1213's conditional end-to-end test.
Notes / risks: Risk: the false 'a fleet poster will retry' copy is a live honesty bug — fix the copy even if the queue view slips.
Suggested approach: Suggested approach: expose the existing /api/comments.json pending counts in a nav-reachable queue view; make counts kind/state-aware in CommentsStore.counts().
Labels normalized this pass (see the issue's label set); acceptance criteria appended to the body as the standard
## Acceptance criteriasection, original body preserved verbatim above it.17 remaining items
dezren39 commentedon Nov 1, 2026
🤖 Agent note · parked — Drew-owned PR boundary
queue/4922-1210-comments-queue.dezren39 commentedon Nov 1, 2026
Agent note (task 4922, lane B): picked up (attempt 2) and resumed the canonical PR #3987 rather than restarting — revalidated fresh: PR #3987 OPEN at cac2674, no hard-stop labels; Codex review completed on that head with no findings. Verification this shift (laptop worktree ~/git/fleet/4922): the #1210 test files pass 15/15 (comments-queue-1210 + curation-1497); full aggregator suite 923 pass / 1 fail, and the single failure (slice3.test.ts registry source assertion) fails identically on clean main — pre-existing, environment-dependent, unrelated to this PR. Merging PR #3987.
Merge pull request #3987 from developing-today/queue/4922-1210-commen…
dezren39 commentedon Nov 1, 2026
Agent note (task 4922, lane B): done — PR #3987 merged (2f8ab78). All four acceptance items verified: queue view at /comments + /api/comments/queue.json listing new/pending/failed with kind/state-aware counts (commentKindCounts/countsDetailed), failed items show age + last error with honest retry copy, #1210 tests 15/15 pass, full aggregator suite 923/924 with the one slice3 failure proven pre-existing on clean main (environment-dependent registry assertion, unrelated). Codex review of PR #3987 completed with no findings. Closing.