feat(usage-hub): self-monitoring — feed staleness + fixture-fallback alarm #1116

Activity

1. dezren39

   added

   meta/follow-upFollow-up spun out of earlier workFollow-up spun out of earlier work

   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-254
3. github-actions

   assigned

   dezren39

   on Oct 27, 2026
4. 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

   on Oct 29, 2026
5. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane A shift
   • Session / ID: queue task 2401
   • Found via: queue claim
   • Task: Triage feat(usage-hub): self-monitoring — feed staleness + fixture-fallback alarm #1116 — check which of its four self-monitoring items still stand on current main, and route the remainder
   • Expectation: effort s (triage); done = verdict posted item-by-item with HEAD evidence and the remainder enqueued as one scoped packet
   • Links: epic epic(usage-hub): SaaS/cloud services completion — v2 live collectors, daily console reads, v3 reconciliation #1047; design §6; dependency fix(pm-stack): fleet-feed-collector units do not survive a sandbox recycle #903 (closed); related landed work fix(aggregator): provenance footer is one jargon line and contradicts page content - replace with per-source freshness chips #1138, impl(fleet): staleness watchdog - surface dead/stale stack inputs as NEEDS ORCHESTRATOR instead of silent decay #1148, feat(quota-plane): quota-gatherer service in the PM stack — 15-minute tick, quota-current contract #1151
6. dezren39 commented on Oct 29, 2026

   

   dezren39

   on Oct 29, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done

   • Agent: queue worker (repo-worker-code), lane A shift
   • Session / ID: queue task 2401 (triage) → follow-up queue task 3010
   • Found via: queue claim
   • Task: Triage verdict for feat(usage-hub): self-monitoring — feed staleness + fixture-fallback alarm #1116 — item-by-item against HEAD
   • Verdict — PARTIALLY LANDED; remainder confirmed and routed. (1) Collector heartbeat/feed age: landed — health.ts assembles per-section feed ages (15-min stale threshold) plus a collector block (generatedAt/fileMtime/ageMs) for /api/health, feed.ts diagnoses sections as live/absent/invalid/stale, and the quota gatherer carries a heartbeat (tickAt/ok, feat(quota-plane): quota-gatherer service in the PM stack — 15-minute tick, quota-current contract #1151). (2) Feed age surfaced + fixture-fallback flags: landed — freshness chips (fix(aggregator): provenance footer is one jargon line and contradicts page content - replace with per-source freshness chips #1138) and stale banners in render.ts; sources/live.ts provenance names exactly which facet is live vs fixture-backed (e.g. "fixtures (no fleet feed file yet)"). Dependency fix(pm-stack): fleet-feed-collector units do not survive a sandbox recycle #903 is closed. (3) pm-feed checkout drift vs origin/main in the health view: NOT built — health.ts contains no drift/git/checkout logic at all. (4) Stewardship hourly check naming a stale feed as a finding: not evidenced in the stewardship skill files.
   • Routing: remainder packet enqueued as queue task 3010 (dedupe repo-health:v1:fix:developing-today/code:issue:1116): drift check in the health view, stewardship stale-feed finding (verify-then-add), and an end-to-end run of this issue's acceptance test (collector stopped → dashboard says stale within one interval), fixing any footer feed-age prominence gap that test exposes. The landed surfaces are explicitly out of scope — do not rebuild them.
   • Expectation: feat(usage-hub): self-monitoring — feed staleness + fixture-fallback alarm #1116 stays open with queue/queued until task 3010 lands the remainder, at which point it can close.
   • Links: epic epic(usage-hub): SaaS/cloud services completion — v2 live collectors, daily console reads, v3 reconciliation #1047; dependency fix(pm-stack): fleet-feed-collector units do not survive a sandbox recycle #903 (closed); packet packet-task2401-fix1116.json (goal hidden_files)
7. dezren39

   added

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

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle 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

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

   on Oct 29, 2026
8. 18 remaining items

   Load more
9. dezren39

   added

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

   mode/onlineFully doable remotely: design, config, code, cloudFully doable remotely: design, config, code, cloud

   on Nov 1, 2026
10. dezren39

    added a parent issue on Nov 1, 2026

    • epic(usage-hub): SaaS/cloud services completion — v2 live collectors, daily console reads, v3 reconciliation #1047
11. dezren39

    added

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

    source/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator job

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

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

    on Nov 3, 2026
12. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 30 (priority/none). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03
13. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), lane A shift
    • Session / ID: queue task 7651
    • Found via: queue claim
    • Task: Triage feat(usage-hub): self-monitoring — feed staleness + fixture-fallback alarm #1116 (coverage pass re-triage) — revalidate item-by-item at current state and route any remainder without duplicating prior splits
    • Expectation: effort s (triage); done = verdict posted with fresh evidence; no new packet if the remainder is already tracked
    • Links: epic epic(usage-hub): SaaS/cloud services completion — v2 live collectors, daily console reads, v3 reconciliation #1047; prior triage task 2401; item-3 fix task 3010 / PR feat(usage-hub): report pm-feed collector checkout drift in health (#1116 item 3) #2973 (merged); remainder feat(usage-hub): #1116 remainder items 4+5 — stewardship stale-feed finding + collector-stop acceptance verification #2990 / task 4298
14. 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

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

    on Nov 3, 2026
15. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), lane A shift
    • Session / ID: queue task 7651 (triage, coverage re-triage)
    • Found via: queue claim
    • Task: Triage verdict for feat(usage-hub): self-monitoring — feed staleness + fixture-fallback alarm #1116 — revalidated fresh 2026-11-03
    • Verdict — STILL LIVE; remainder already tracked and BLOCKED; no new packet (dedupe). Items (1) collector heartbeat/feed age and (2) feed-age surfacing + fixture-fallback flags: landed (prior triage task 2401; fix(aggregator): provenance footer is one jargon line and contradicts page content - replace with per-source freshness chips #1138/impl(fleet): staleness watchdog - surface dead/stale stack inputs as NEEDS ORCHESTRATOR instead of silent decay #1148/feat(quota-plane): quota-gatherer service in the PM stack — 15-minute tick, quota-current contract #1151; dependency fix(pm-stack): fleet-feed-collector units do not survive a sandbox recycle #903 closed). Item (3) pm-feed checkout drift in the health view: landed — PR feat(usage-hub): report pm-feed collector checkout drift in health (#1116 item 3) #2973 merged 2026-10-31 (merge commit 04cd4e7, verified fresh this shift via gh pr view 2973: state MERGED). Items (4) stewardship stale-feed finding and (5) collector-stop acceptance verification: split to feat(usage-hub): #1116 remainder items 4+5 — stewardship stale-feed finding + collector-stop acceptance verification #2990, whose fix task 4298 is blocked — feat(usage-hub): #1116 remainder items 4+5 — stewardship stale-feed finding + collector-stop acceptance verification #2990 verified fresh this shift as OPEN with status/blocked + queue/blocked. Blocker (from task 4298's blocked note on feat(usage-hub): #1116 remainder items 4+5 — stewardship stale-feed finding + collector-stop acceptance verification #2990): access to the live Muse stewardship checkout or its authorized deployment path is needed to implement/verify item (4); the isolated real collector-stop-to-HTTP test for item (5) remains unverified; seven uncommitted candidate files in the laptop worktree ~/git/fleet/4298 on branch queue/4298-2990-stale-feed must be preserved and reviewed on resume (a 5-minute stale cutoff has no scheduling grace and may false-alarm).
    • Routing: none new — enqueuing another packet for feat(usage-hub): self-monitoring — feed staleness + fixture-fallback alarm #1116 would duplicate feat(usage-hub): #1116 remainder items 4+5 — stewardship stale-feed finding + collector-stop acceptance verification #2990 / task 4298. feat(usage-hub): self-monitoring — feed staleness + fixture-fallback alarm #1116 stays open until feat(usage-hub): #1116 remainder items 4+5 — stewardship stale-feed finding + collector-stop acceptance verification #2990's verdict lands, then closes on that evidence.
    • Links: remainder feat(usage-hub): #1116 remainder items 4+5 — stewardship stale-feed finding + collector-stop acceptance verification #2990; item-3 PR feat(usage-hub): report pm-feed collector checkout drift in health (#1116 item 3) #2973; epic epic(usage-hub): SaaS/cloud services completion — v2 live collectors, daily console reads, v3 reconciliation #1047