docs(scope): mark notification follow-up complete

docs/audience-scoping-backlog.md

@@ -17,6 +17,7 @@
 - `resource.chapters`: documented and covered as authenticated safe lookup
 - `resource.importSkillMatrix`: documented as self-service and auth-verified
 - `project.isImageGenConfigured`, `project.isDalleConfigured`: covered as authenticated low-risk configuration checks
+- `notification` self-service and manager boundaries: auth-covered across list, unread counts, reminders, deletes, broadcasts, task creation, and assignment boundaries
 
 ### Dirty Files To Avoid Mixing Into This Batch
 
@@ -41,7 +42,7 @@ These files already have unrelated local edits. Audience parity work that would
 
 ### No Further Small Slices Currently Ready
 
-- the previously identified small hardening and tests/docs candidates have been completed
+- the previously identified small hardening and tests/docs candidates have been completed, including the notification auth follow-up
 - the remaining audience work is now either architectural (`comment.ts`) or blocked by dirty files owned elsewhere
 
 ### Needs Architecture Or Policy Design
@@ -73,19 +74,10 @@ These routes should not be batch-edited as “small safe slices” until a visib
   - keep parity changes on the `assistant.ts` side where possible
   - defer tool-level cleanups until the file is stable
 
-#### `packages/api/src/router/notification.ts`
-
-- Why blocked:
-  - unrelated local edits are already present
-  - TypeScript verification currently also reports a foreign issue in this file
-- Interim rule:
-  - do not mix notification hardening into this batch unless the other worker clears the file first
-
 ## Recommended Next Order
 
 1. `comment` architecture design ticket
 2. assistant-tools parity cleanup once the dirty files are free again
-3. notification follow-up once the dirty files and foreign TypeScript issue are resolved
 
 ## Slice Definition