Repository navigation
chore(pm-stack): tracker hygiene - stale design issues #851/#852 still open though shipped; #781 predates the stack review #1183
Description
Finding
Evidence (live review 2026-10-26 ~22:40 CDT, laptop loopback + gh, cross-checked): Open app/aggregator issues include #851 (design: quota + throughput view) and #852 (design: needs-you attention view) - both SHIPPED (PRs #892/#900/#901 era) yet still open, so the pm-stack backlog overstates open design work and the sweeps keep re-triaging zombies. #781 (Pad/Grist hard-coded tailnet IP) is a real open topology bug from before the current program structure.
Proposal
Close #851/#852 as completed with links to the shipping PRs (or convert to pointers to their follow-ups in the coherence epic); confirm #781 still reproduces on current main and either schedule it into the coherence epic's topology theme or close with evidence. Sweep the remaining open app/pm-stack + app/aggregator list once for other zombies and list them on this issue.
Acceptance
- design(aggregator): quota + throughput view — pooled quotas, resets, burn rates, model-choice support #851/design(aggregator): 'needs you' attention view — session state taxonomy, machine-first #852 resolved with evidence links; a zombie list (closed or confirmed-live) posted here.
Acceptance criteria
- design(aggregator): quota + throughput view — pooled quotas, resets, burn rates, model-choice support #851 and design(aggregator): 'needs you' attention view — session state taxonomy, machine-first #852 are resolved (closed as completed with links to the shipping PRs, or converted to pointers to their follow-ups in the coherence epic epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184).
- pm-stack: Pad/Grist compose files hard-code one host's tailnet IP (100.99.113.103), breaking the documented move-hosts procedure #781 is confirmed still-live on current main and either scheduled into the coherence epic's topology theme or closed with evidence.
- A zombie list from one sweep of the remaining open
app/pm-stack+app/aggregatorissues is posted on this issue, each entry closed or confirmed live.
Activity
developing-today commentedon Oct 27, 2026
CODE-319
dezren39 commentedon Oct 28, 2026
Intake review
Related: #851 / #852 (the shipped-but-open design issues this closes) · #781 (the pre-stack-review topology bug to confirm) · epic #1184 (the coherence program whose backlog this cleans).
Notes: Still live — verified this run: a fresh API search finds no PR referencing this issue, so #851/#852 remain open zombies until someone does the closing work in the criteria below. The issue arrived with a
## Acceptancesection; the appended## Acceptance criteriaformalizes it.effort/s— the sweep-and-list work is small.Risks / suggested approach: the first worker to touch this should post the zombie list here rather than filing per-zombie issues, and close #851/#852 with links to their shipping PRs as the evidence.
Correction (repo-fleet-monitor, 2026-10-28T03:45Z): the original version of this comment cited an in-flight "PR #1582" — that reference came from a corrupted tool output during the monitor run and was wrong: no such PR exists (verified directly against the GitHub API). It has been removed; apologies for the noise.
— repo-fleet-monitor intake pass, 2026-10-28T03:34Z (corrected 03:45Z)
dezren39 commentedon Nov 1, 2026
Picked up queue task 2469 for current-state triage; checking referenced issues and existing ownership.
1 remaining item
dezren39 commentedon Nov 1, 2026
Triage verdict: partially outstanding
#852 is closed with shipping evidence; #781 is closed after merged PR #3293 (no live deployment claimed). #851 remains open; the shipped panel and merged #892 alone do not prove all joined-model, throughput and model-choice criteria are met. Related gaps include #1172, #1174 and #1170. No zombie sweep has been posted here. Route a scoped follow-up to verify or convert #851 to explicit follow-up pointers and perform the requested app/pm-stack and app/aggregator sweep; do not close issues merely from titles.
dezren39 commentedon Nov 1, 2026
Triage task 2469 completed; remaining tracker hygiene routed as queue task 4900. Issue remains open pending that work.
dezren39 commentedon Nov 1, 2026
Picked up queue task 4900 for tracker hygiene; verifying #851 against its full acceptance criteria and sweeping current open app/pm-stack and app/aggregator issues, with ownership and hard stops respected.
dezren39 commentedon Nov 1, 2026
One-pass tracker sweep — 2026-11-01
Fresh GitHub inventory: 126 open issues labeled
app/pm-stackand 93 labeledapp/aggregator(the sets overlap, so the counts are not additive). The completed-but-open candidates and older live exceptions were reviewed against current issue state, labels, linked implementation evidence, and current main:burn: []and has no liveburnTokensPerMinproducer; the root design record also lacks the requested cadence/wall contract. Closed design(aggregator): quota + throughput view — pooled quotas, resets, burn rates, model-choice support #851 asnot_plannedonly after creating aggregator: finish quota throughput data + record the design contract (#851) #3933 with those exact remaining criteria and attaching it as a child of epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184. impl(aggregator): /quota covers 8 SaaS services; the tracked estate is dozens - list the uninstrumented with reasons #1172 (coverage) and impl(aggregator): quota page shows numbers, not actions - surface expiring/cancelled-pool actions into /today + /attention #1174 (actions) remain separate open follow-ups.f00dde6891045f7f2d7a5136e19a521d7a3b9dd5); its completion comment records the laptop regression test results and explicitly says no live deployment was made.user/escalated+queue/blocked; this remains a Drew decision, not a zombie.queue/queuedfor triage.Evidence links: #851 disposition · #852 / PR #892 · #781 / PR #3293 · new follow-up #3933.