feat(aggregator): /notifications preferences page + deep-link acceptance (#1254 slice d) #3318

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

   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
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

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

   

   dezren39

   on Nov 3, 2026

   MemberAuthor

   More actions

   agent-note:v1
   state: triaged
   task: task 8236 (triage, repo-health-code-pilot, lane code-l)
   worker: repo-worker-code
   issue: #3318

   Triage findings — #3318 (slice d of #1254) at current main

   Verdict: still live, not implemented. No hard-stop labels. Design PR #3314 merged; parent #1254 closed; epic #1184 open.

   Evidence (fresh gh checks this run):

   • Issue feat(aggregator): /notifications preferences page + deep-link acceptance (#1254 slice d) #3318 OPEN. Code search finds no /notifications page/route in the aggregator at current main — the preferences page does not exist yet.
   • All sibling slices are open: feat(aggregator): PWA installability — manifest, icons, install affordance (#1254 slice a) #3315 (a, PWA installability), feat(aggregator): Web Push plumbing — VAPID, subscription store + API, service worker (#1254 slice b) #3316 (b, Web Push plumbing), feat(aggregator): notification engine — class triggers, dedupe, quiet hours, escalation (#1254 slice c) #3317 (c, notification engine), feat(aggregator): notification measurement — weekly sent-vs-acted-on roll-up (#1254 slice e) #3319 (e, measurement; triage handed off as task 8224).
   • Slice (c) feat(aggregator): notification engine — class triggers, dedupe, quiet hours, escalation (#1254 slice c) #3317 was triaged today (task 8233): still live, with an implementation task enqueued; its scope builds the engine on the existing alerts throat (pm-stack/aggregator/src/alerts.ts, PR feat(aggregator): alert throat — sentinel intake, Supabase ledger, Web Push delivery + ack (#3676) #3680/fix(aggregator): alerts push UX — permission flow, quiet-hours off, test button, primary nav #3707) rather than a new delivery path. Much of slice (b)'s delivery surface already landed through that throat; any subscription-store remainder stays with feat(aggregator): Web Push plumbing — VAPID, subscription store + API, service worker (#1254 slice b) #3316.

   Ordering / blockers for slice (d):

   1. Rides with slice (c), as filed. The page's toggles/quiet-hours edits must change the stored subscription the feat(aggregator): notification engine — class triggers, dedupe, quiet hours, escalation (#1254 slice c) #3317 engine reads, and the send-test/deep-link acceptance can only be verified once the engine can send per class. Implementing the page before the engine's subscription model settles risks building the storage shape twice.
   2. Recommended sequence: feat(aggregator): notification engine — class triggers, dedupe, quiet hours, escalation (#1254 slice c) #3317 engine implementation (already enqueued) → slice (d) page against the engine's stored subscription + send-test wired to the engine → deep-link acceptance tests per design §3 (per-class landing on the item's triage-capable view; digest case lands on the filtered attention view; never the origin root).
   3. No Drew decision is blocked here: the acceptance criteria on this issue are complete as filed (stored-subscription effect on next engine decision, mobile-viewport send-test landing, dashboard nav reachability on the tailnet origin).

   This triage completes as triaged; the implementation follows the #3317 engine task in the queue.
8. 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