/projects: make the Project pool browsable — filters, counts, grouping by Kind/Status, honest truncation #1208

Activity

1. dezren39

   added

   kind/featureNew feature or capability requestNew feature or capability request

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   on Oct 27, 2026
2. developing-today commented on Oct 27, 2026

   

   developing-todayBot

   on Oct 27, 2026 – with developing.today

   Contributor

   More actions

   CODE-342
3. dezren39

   added

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   app/pm-stackpm-stack (Pad/Grist) in developing-today/codepm-stack (Pad/Grist) in developing-today/code

   on Oct 27, 2026
4. dezren39

   added a parent issue on Oct 27, 2026

   • epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184
5. github-actions

   assigned

   dezren39

   on Oct 27, 2026
6. dezren39

   added

   source/humanFiled directly by a humanFiled directly by a human

   effort/mMedium: expected under 1 day of workMedium: expected under 1 day of work

   meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels added

   on Oct 28, 2026
7. dezren39 commented on Oct 28, 2026

   

   dezren39

   on Oct 28, 2026

   MemberAuthor

   More actions

   Intake review — fleet monitor

   Liveness: Verified still live at intake (2026-10-28): issue is open and unheld, and a merged-PR search for #1208 returned only unrelated text matches (no PR title or fix reference resolves this item). Part of epic #1184 (PM stack coherence review, 2026-10-26); sibling batch #1210–#1222 was enriched in the previous monitor run.

   Notes: Counts already exist on /program, so the header-count work can reuse that derivation. Risk: filter semantics must match /api/projects.json exactly or the pages will diverge — test against the twin.

   Risks: Scope creep across the pm-stack pages is the main risk for this batch; the acceptance criteria above (converted from the issue's original Acceptance list) bound the work. CI on the aggregator's render/derive tests is the verification surface.

   Suggested approach: Take the acceptance criteria in order; keep the JSON twins in lockstep with the HTML pages, per the batch convention.

   Labels normalised this pass: source/human (coherence-review filer), effort/m, meta/enriched; existing kind/priority/status/app labels kept.
8. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   on Nov 1, 2026
9. 7 remaining items

   Load more
10. dezren39

    added

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    and removed

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    on Nov 1, 2026
11. dezren39 commented on Nov 1, 2026

    

    dezren39

    on Nov 1, 2026

    MemberAuthor

    More actions

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
    • Session / ID: OpenCode session ses_e5e675fb89affeb3Kpe4HuTKN0; queue task 4912
    • Found via: queue claim
    • Task: Implement project pool filters and honest draft/pagination completeness; coordinate the overlap with aggregator(projects): fetchProjectPool silently truncates the pool at 10 pages — a pool over 1,000 items is published as complete with the rest vanished #2459 and its queued task 5341.
    • Expectation: Combined filters/counts align with project JSON; draft omission and incomplete pagination are explicit and covered by targeted fixtures.
    • Links: /projects: make the Project pool browsable — filters, counts, grouping by Kind/Status, honest truncation #1208, aggregator(projects): fetchProjectPool silently truncates the pool at 10 pages — a pool over 1,000 items is published as complete with the rest vanished #2459, queue task 4912
12. dezren39 commented on Nov 1, 2026

    

    dezren39

    on Nov 1, 2026

    MemberAuthor

    More actions

    🤖 Agent note · picked up

    • Agent: repo-worker-code (OpenChamber scheduled lane)
    • Session / ID: ses_e5e674d64eeffeDebWj03vsWrt; queue task 4912 (resume)
    • Found via: atomic queue claim
    • Verified fresh: /projects: make the Project pool browsable — filters, counts, grouping by Kind/Status, honest truncation #1208 is OPEN; related aggregator(projects): fetchProjectPool silently truncates the pool at 10 pages — a pool over 1,000 items is published as complete with the rest vanished #2459 is OPEN. Open-PR searches for both issue numbers found no matches. No held, user/owned, do-not-merge, or do-not-auto-edit labels on /projects: make the Project pool browsable — filters, counts, grouping by Kind/Status, honest truncation #1208. Existing checkpoint names branch queue/4912-1208-project-pool-filters and worktree /home/user/git/fleet/4912; I will inspect and resume that work without discarding existing changes.
    • Next: inspect existing worktree and current main, then continue only the scoped /projects: make the Project pool browsable — filters, counts, grouping by Kind/Status, honest truncation #1208 work while preserving aggregator(projects): fetchProjectPool silently truncates the pool at 10 pages — a pool over 1,000 items is published as complete with the rest vanished #2459 truncation overlap.
13. dezren39

    added

    queue/blockedQueue or user escalation stateQueue or user escalation state

    status/blockedQueue or user escalation stateQueue or user escalation state

    and removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 1, 2026
14. dezren39 commented on Nov 1, 2026

    

    dezren39

    on Nov 1, 2026

    MemberAuthor

    More actions

    🤖 Agent note · blocked (packet_defect)

    • Agent: repo-worker-code (OpenChamber scheduled lane)
    • Session / ID: ses_e5e674d64eeffeDebWj03vsWrt; queue task 4912
    • State: BLOCKED pending owner clarification. No source files changed; the existing worktree was clean and fast-forwarded to current main.
    • Conflict: /projects: make the Project pool browsable — filters, counts, grouping by Kind/Status, honest truncation #1208 requires draft and pagination-completeness caveats in HTML/JSON, including a >1000-item fixture. Fresh aggregator(projects): fetchProjectPool silently truncates the pool at 10 pages — a pool over 1,000 items is published as complete with the rest vanished #2459 triage findings on 2026-11-01T09:09Z explicitly chose THROW at the 10-page cap, rejected adding a completeness signal as a larger change, and routed task 5341 for that throw guard and regression tests. Implementing explicit partial-pool metadata here would conflict with that decision/ownership; throw-and-omit cannot satisfy the requested incomplete-pagination display.
    • Decision needed: authorize /projects: make the Project pool browsable — filters, counts, grouping by Kind/Status, honest truncation #1208 to supersede/revise aggregator(projects): fetchProjectPool silently truncates the pool at 10 pages — a pool over 1,000 items is published as complete with the rest vanished #2459 and task 5341 toward explicit completeness metadata, or revise /projects: make the Project pool browsable — filters, counts, grouping by Kind/Status, honest truncation #1208 acceptance to align with throw-and-omit. Resume after the acceptance/ownership is reconciled.
    • Links: aggregator(projects): fetchProjectPool silently truncates the pool at 10 pages — a pool over 1,000 items is published as complete with the rest vanished #2459 · task 5341
15. dezren39

    added

    queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

    task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

    on Nov 3, 2026
16. developing-today commented on Nov 3, 2026

    

    developing-todayBot

    on Nov 3, 2026 – with developing.today

    Contributor

    More actions

    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 4912 (small_fix, blocked, priority 50) 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