Recent updates sheet (Feature 21) #176

Merged

approver_agent merged 4 commits from task/recent-updates-sheet_96e2dc3f-1f8a-4114-bcb5-e0f93c349165 into feature/446472d5-2a84-4aa2-bb37-fdc80815615c-home-dashboard 2026-10-10 15:48:27 -04:00

Conversation 4 Commits 4 Files Changed 20

+1387 -10

4 Commits

Author	SHA1	Message	Date
dev_agentandClaude Opus 5.5	d9b63bd08c	Cancel an in-flight Recent updates read when the sheet closes ... The updates query now passes TanStack Query's abort signal to apiFetch, so closing the sheet while its read is pending aborts that GET. An immediate reopen then sends its own read instead of adopting the one sent before a newer event was stored, and marks seen only what that read returned. Closes MQ-176-01 (task 96e2dc3f-1f8a-4114-bcb5-e0f93c349165). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-10 15:07:37 -04:00
dev_agentandClaude Opus 5.5	6956f6f049	Read Recent updates afresh on every opening before marking them seen ... gcTime 0 only schedules removal of the cached list, so an immediate reopen within the query client's staleTime reused it and marked the old newest time seen. useUpdates now refetches on every mount, and the sheet shows and marks seen only a list read after it opened. Closes MQ-176-01. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-10 14:17:07 -04:00
dev_agentandClaude Opus 5.5	9978e200e6	Read Recent updates afresh per opening and guard their URLs by origin ... Address the review of PR #176 (Feature 21, task 96e2dc3f): - MQ-176-01: useUpdates drops its list as soon as the sheet closes (gcTime 0), so each opening reads GET /api/v1/updates afresh and only marks seen through the newest of that read, never a cached list. - MQ-176-02: parseUpdate checks each url with appPath from push/notification.ts, by parsed origin, instead of a prefix check that tabs and newlines got past; the url kept is the path as parsed. - MQ-176-03: TestMarkUpdatesSeen asserts updated_at is kept and settings subscribers are not told. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-10 12:35:58 -04:00
dev_agentandClaude Opus 5.5	74e33a6236	Add the Recent updates sheet behind the Home bell (Feature 21) ... GET /api/v1/updates lists the last 10 distinct notification events from the outbox, newest first and one per event key whatever its channels. POST /api/v1/updates/seen {"through": created_at} moves household_settings.updates_seen_at forward, so /api/v1/home's recentUpdates.unread is true only for an event stored since. The Home bell opens a Sheet listing the updates with relative times; a row opens its URL, and opening the sheet marks the updates seen, clearing the grape dot optimistically and putting it back if the mark fails. Maestro task 96e2dc3f-1f8a-4114-bcb5-e0f93c349165. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-10 09:03:47 -04:00