QuickandClaude Fable 5
d9e27da59e
Notify the requesting profile once its media request is actually present in the catalog (roadmap 06, item 2). Completion transitions stay notification-agnostic; a presence-gated pass at the end of each reconcile run fires the notice, so it means "watchable in Silo", not "download finished". - New System.DispatchOperational: delivery insert + webhook/web-push outbox enqueue in one transaction, post-commit multi-dispatch. The webhook auto-disable notice now rides the same path (replacing its hand-rolled hub publish and the now-removed InsertOperational), which also delivers auto-disable notices over web push. - At-most-once delivery: partial unique index on (profile_id, reason_flags->>'request_id') plus a fulfilled_notified_at marker on media_requests, backfilled for pre-existing completed requests so deploys never flood. - Per-webhook notify_requests toggle (default on) through repo, service, API, and settings UI; gated independently of the episode reason flags. - request.fulfilled rendering in web inbox, realtime toast, web push payload, and Discord/generic webhook payloads, deep-linking to the matched catalog item. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
44 lines
2.0 KiB
SQL
44 lines
2.0 KiB
SQL
-- +goose Up
|
|
-- +goose StatementBegin
|
|
-- request.fulfilled notifications (docs/superpowers/plans/notifications/06,
|
|
-- item 2): notify the requesting profile once its media request is actually
|
|
-- present in the catalog.
|
|
|
|
-- Notify marker. NULL means "completed but the fulfillment notification has
|
|
-- not fired yet"; the reconcile task keeps presence-checking such requests and
|
|
-- stamps this after the delivery is created (or suppressed by preferences).
|
|
ALTER TABLE public.media_requests
|
|
ADD COLUMN fulfilled_notified_at timestamptz;
|
|
|
|
-- Flood safety: requests completed before this feature shipped must never
|
|
-- notify. Stamp them as already handled so only future completions fire.
|
|
UPDATE public.media_requests
|
|
SET fulfilled_notified_at = COALESCE(completed_at, now())
|
|
WHERE status = 'completed';
|
|
|
|
-- The reconcile task scans for pending notifications on every run.
|
|
CREATE INDEX media_requests_fulfill_notify_idx
|
|
ON public.media_requests (completed_at)
|
|
WHERE status = 'completed' AND fulfilled_notified_at IS NULL;
|
|
|
|
-- Per-webhook opt-out for request notifications. Defaults on: every channel
|
|
-- the requester configured should tell them (06, item 2).
|
|
ALTER TABLE public.notification_webhooks
|
|
ADD COLUMN notify_requests boolean NOT NULL DEFAULT true;
|
|
|
|
-- At-most-once per (profile, request): the operational insert path uses
|
|
-- ON CONFLICT DO NOTHING, so a reconcile crash-retry or multi-node race
|
|
-- dedupes here instead of double-notifying.
|
|
CREATE UNIQUE INDEX notification_deliveries_profile_request_key
|
|
ON public.notification_deliveries (profile_id, (reason_flags->>'request_id'))
|
|
WHERE type = 'request.fulfilled';
|
|
-- +goose StatementEnd
|
|
|
|
-- +goose Down
|
|
-- +goose StatementBegin
|
|
DROP INDEX IF EXISTS public.notification_deliveries_profile_request_key;
|
|
ALTER TABLE public.notification_webhooks DROP COLUMN IF EXISTS notify_requests;
|
|
DROP INDEX IF EXISTS public.media_requests_fulfill_notify_idx;
|
|
ALTER TABLE public.media_requests DROP COLUMN IF EXISTS fulfilled_notified_at;
|
|
-- +goose StatementEnd
|