impl(aggregator): add replayable freshness SSE and JSON twin #3978

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

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

   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

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

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

   

   dezren39

   on Nov 1, 2026

   MemberAuthor

   More actions

   🤖 Agent note · state: filed / parent-link blocked

   • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
   • Session / ID: OpenCode session ses_e5e671686ccffeQbtUrJqbsWZM, design task 4942
   • Handoff: Five-minute freshness reconciliation, fallback, and health UX from design design(pm-stack): event-driven freshness — replace the 5-minute polling feed with push (webhooks + SSE/WebSocket), polling as reconciliation only #1252; intended under epic epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184.
   • Blocker: GitHub rejects native child linkage because epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184 has 100 sub-issues (HTTP 422). The body references design(pm-stack): event-driven freshness — replace the 5-minute polling feed with push (webhooks + SSE/WebSocket), polling as reconciliation only #1252/epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184, but this issue is not yet a native child. No existing child was moved; resume linkage after Drew selects the hierarchy.
3. github-actions

   assigned

   dezren39

   on Nov 1, 2026
4. 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

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

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

   

   developing-todayBot

   on Nov 3, 2026 – with developing.today

   Contributor

   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 40 (priority/normal). 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
6. dezren39 commented on Nov 3, 2026

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
   • Session / ID: OpenCode session ses_e5e5d0089abffeESkh4gjA8pWE, task 8314, lane bf419306-c4ef-470f-a553-beabf93239de
   • Task: Triage impl(aggregator): add replayable freshness SSE and JSON twin #3978 at current main; verify current issue and related PR state, then identify whether the work remains live and appropriately scoped.
   • Next: Inspect linked PRs and current main, then post the triage outcome.
7. dezren39

   added

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue 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

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

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

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triaged (task 8314)

   • Agent: queue worker (repo-worker-code), OpenChamber scheduled lane
   • Session / ID: OpenCode session ses_e5e5d0089abffeESkh4gjA8pWE, lane bf419306-c4ef-470f-a553-beabf93239de, task 8314
   • Verdict: impl(aggregator): add replayable freshness SSE and JSON twin #3978 remains OPEN and correctly scoped; no linked PR or superseding implementation was found.
   • Verified at main: 32d47f73b6912da8224144558188eb01af2c037f. The aggregator has the existing Datastar fragment helpers (server.ts:509,517) and page fragments refreshed on load/dashrefresh; no /freshness/stream, /api/freshness-events.json, or freshness journal implementation exists under pm-stack/aggregator. feed.ts:340 still sets the 5-minute stale boundary.
   • Blocker / order: implement the durable invalidation source journal in impl(pm-stack): publish durable freshness invalidations from verified sources #3977 before starting impl(aggregator): add replayable freshness SSE and JSON twin #3978's SSE/JSON delivery layer. impl(pm-stack): publish durable freshness invalidations from verified sources #3977 remains OPEN and is currently claimed for separate triage task 8322; do not duplicate or parallelize that prerequisite. Keep impl(aggregator): add replayable freshness SSE and JSON twin #3978 open; no new follow-up task is needed because impl(pm-stack): publish durable freshness invalidations from verified sources #3977 already tracks the prerequisite and impl(aggregator): add replayable freshness SSE and JSON twin #3978 is the scoped implementation issue.
   • Access: design(pm-stack): one public URL for the dashboard behind Cloudflare Access (settled access model, not yet implemented) #1182 remains OPEN and blocked pending Drew's explicit go. Do not enable an external production route or broaden Access; this does not block local/tailnet implementation under existing authorization.
   • Hierarchy: native parent linkage under epic(dashboard): PM stack coherence - single-URL, fresh data, triage-able, hierarchical #1184 remains a separate issue tracked on design(pm-stack): event-driven freshness — replace the 5-minute polling feed with push (webhooks + SSE/WebSocket), polling as reconciliation only #1252; no child relationships were changed here. No code or tests changed in this triage.
9. dezren39

   removed

   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 Nov 3, 2026
10. dezren39

    marked this as blocking on Nov 6, 2026

    • impl(pm-stack): reconcile freshness gaps and surface push health #3976