feat(aggregator): notification measurement — weekly sent-vs-acted-on roll-up (#1254 slice e) #3319

Activity

1. dezren39

   added

   kind/featureNew feature or capability requestNew feature or capability request

   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 Nov 1, 2026
2. dezren39

   added a parent issue on Nov 1, 2026

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

   assigned

   dezren39

   on Nov 1, 2026
4. dezren39 commented on Nov 3, 2026

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   🤖 Agent note · consumer contract now stated

   Design #3702 Phase 3 (audit task 5613, 2026-11-03) has stated the alert throat's truth contract in the code — pm-stack/aggregator/src/alerts.ts module header (PR #4977) — and closed the audit on #3702. What this means for the sent-vs-acted-on roll-up:

   • "Sent" now has a precise meaning: at least one accepted push send for that incident (runAlertTick only marks delivered/escalated when summary.sent > 0, aggregator(alerts): runAlertTick marks incidents delivered when every push send failed — critical incidents are silently lost, never retried #3685/PR fix(aggregator): retry failed incident pushes (#3685) #3690). gone outcomes are not sends; suppressed-quiet and suppressed-dedupe are ledger outcomes, not deliveries. A roll-up should count notification_sends outcome = 'sent' rows (or the delivered/escalated events), never delivered_at alone as a proxy for attempts.
   • Quiet suppression is contractual: inQuietHours on mergeQuiet-validated prefs (aggregator(alerts): mergeQuiet accepts out-of-range times (99:99, 24:60) — a malformed quiet window is silently reinterpreted instead of falling back to the default #3686) is the only clock; a suppressed row is a decision, not a failure, and belongs in a separate bucket from error.
   • Measurement of the throat's truthfulness (delivered-but-not-sent) should now be zero by construction — if a roll-up ever sees a delivered/escalated event with no corresponding sent row, that is a contract break worth flagging on the ledger.
5. 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
6. 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
7. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue 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
8. 6 remaining items

   Load more
9. dezren39

   added

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

   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/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 Nov 3, 2026
10. 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 code-o
    • Session / ID: task 8865
    • Found via: queue claim
    • Task: task 8865 (implement issue feat(aggregator): notification measurement — weekly sent-vs-acted-on roll-up (#1254 slice e) #3319 — weekly notification sent-vs-acted roll-up): claimed by lane code-o, execution lane direct; implementing the read-only /notifications page from the alerts.notification_sends ledger in a laptop worktree on branch queue/8865-3319-notifications-rollup.
    • Expectation: effort m; done = /notifications page matches the acceptance criteria (outcome=sent only, acted_on_at within 24h, rolling four-week window, non-mutating under-10% proposal), targeted tests pass, PR merged.
    • Links: issue feat(aggregator): notification measurement — weekly sent-vs-acted-on roll-up (#1254 slice e) #3319; parent issue feat(aggregator): installable PWA + push notifications — NEEDS DREW and quota walls reach Drew's phone within a minute #1254; PR docs(aggregator): state the alert throat's truth contract in alerts.ts (#3703) #4977
11. dezren39

    added a commit that references this issue on Nov 3, 2026

    feat(aggregator): /notifications weekly sent-vs-acted roll-up (#3319) (…

    ...

    f74234f
12. dezren39

    closed this as completedin #5193on Nov 3, 2026
13. dezren39

    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 3, 2026
14. dezren39 commented on Nov 3, 2026

    

    dezren39

    on Nov 3, 2026

    MemberAuthor

    More actions

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), lane code-o
    • Session / ID: task 8865
    • Found via: queue claim
    • Task: task 8865 complete — the /notifications roll-up is implemented and merged in PR feat(aggregator): /notifications weekly sent-vs-acted roll-up (#3319) #5193 (squash f74234f), closing issue feat(aggregator): notification measurement — weekly sent-vs-acted-on roll-up (#1254 slice e) #3319. Read-only page + /api/notifications.json twin over alerts.notification_sends: only outcome=sent counts, acted-on = acted_on_at within 24h of the send, per class per rolling week over four weeks, sub-10% classes render as display-only default-off proposals, Ack attribution and its limits documented on the page.
    • Expectation: met — full aggregator suite 1444 pass / 0 fail (incl. new test/notifications.test.ts); Codex review completed with no findings; tsc shows only the two pre-existing main errors.
    • Links: PR feat(aggregator): /notifications weekly sent-vs-acted roll-up (#3319) #5193; issue feat(aggregator): notification measurement — weekly sent-vs-acted-on roll-up (#1254 slice e) #3319