> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase17-session07-war-room-worker-relay-and-catchup/tasks.md). # Task Checklist **Session ID**: `phase17-session07-war-room-worker-relay-and-catchup` **Total Tasks**: 22 **Estimated Duration**: 3-4 hours **Created**: 2026-06-05 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[S1707]` = Session reference (phase 17, session 07) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 7 | 7 | 0 | | Implementation | 8 | 8 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **22** | **22** | **0** | *** ## Setup (3 tasks) Current Worker frame inventory, privacy baseline, and test harness review. ### packages/protocol * [x] T001 \[S1707] Review existing War Room socket frame vocabulary, blocked-field scanner, recent-event parser, and catch-up validator (`packages/protocol/src/warroom.ts`) ### apps/warroom * [x] T002 \[S1707] Review Durable Object socket handling, sender-excluded broadcast, persistence, hydration filtering, and reconnect catch-up flow (`apps/warroom/src/index.ts`) * [x] T003 \[S1707] Review existing Worker test helpers for fake storage, fake WebSocket pairs, authority capture, persisted history, and broadcast assertions (`apps/warroom/tests/warroom.test.ts`) *** ## Foundation (7 tasks) Protocol contracts and focused test scaffolding for Notice Board relay. ### packages/protocol * [x] T004 \[S1707] Add protocol type vocabulary for `notice_board_message`, `notice_resolved`, and `notice_board_catchup` Worker frames (`packages/protocol/src/warroom.ts`) * [x] T005 \[S1707] Define `notice_board_message` frame contract with canonical notice payload validation, bounded fields, exhaustive enum handling, and blocked-field rejection (`packages/protocol/src/warroom.ts`) * [x] T006 \[S1707] Define `notice_resolved` frame contract with notice id plus safe bounded metadata and explicit error mapping (`packages/protocol/src/warroom.ts`) * [x] T007 \[S1707] Define `notice_board_catchup` frame contract with bounded notice arrays, deterministic ordering, and schema-validated entries (`packages/protocol/src/warroom.ts`) * [x] T008 \[S1707] Extend safe recent-event filtering and summaries for Notice Board relay families without including raw payload details (`packages/protocol/src/warroom.ts`) * [x] T009 \[S1707] \[P] Create focused protocol relay test scaffold for frame constants, parser success, parser failure, catch-up bounds, and blocked fields (`packages/protocol/tests/warroomNoticeRelay.test.ts`) ### apps/warroom * [x] T010 \[S1707] \[P] Create focused Worker relay test scaffold with fake Durable Object storage, fake WebSocket pairs, and helper assertions (`apps/warroom/tests/noticeBoardRelay.test.ts`) *** ## Implementation (8 tasks) Worker relay persistence, sender-excluded broadcasts, catch-up, and docs. ### apps/warroom * [x] T011 \[S1707] Extend persisted room hydration for bounded Notice Board relay history with unsafe stored-history filtering before browser consumption (`apps/warroom/src/index.ts`) * [x] T012 \[S1707] Implement Notice Board relay history recording for message frames with idempotency protection, deterministic bounds, and failure-path handling (`apps/warroom/src/index.ts`) * [x] T013 \[S1707] Implement sender-excluded `notice_board_message` broadcast after schema-validated input and before compact safe persistence (`apps/warroom/src/index.ts`) * [x] T014 \[S1707] Implement sender-excluded `notice_resolved` broadcast and catch-up state update with exhaustive notice id handling and failure-path handling (`apps/warroom/src/index.ts`) * [x] T015 \[S1707] Send filtered `notice_board_catchup` frames to reconnecting sockets with bounded arrays and deterministic ordering (`apps/warroom/src/index.ts`) * [x] T016 \[S1707] Preserve existing `warroom_pending_catchup`, `remote_event`, and `warroom_room_notice` behavior while Notice Board relay is added (`apps/warroom/src/index.ts`) * [x] T017 \[S1707] Ensure malformed relay frames and blocked fields fail closed before persistence, diagnostics, logs, catch-up, or browser consumption (`apps/warroom/src/index.ts`) * [x] T018 \[S1707] Document Notice Board Worker relay frames, optional external-transfer boundary, catch-up behavior, and no-claim limits (`apps/warroom/README_warroom.md`) *** ## Testing (4 tasks) Focused protocol and Worker verification plus artifact validation. ### packages/protocol * [x] T019 \[S1707] \[P] Add protocol tests for valid relay frames, malformed frames, unknown fields, blocked fields, catch-up bounds, and safe filtering (`packages/protocol/tests/warroomNoticeRelay.test.ts`) ### apps/warroom * [x] T020 \[S1707] \[P] Add Worker tests for message relay, sender exclusion, bounded history, persisted unsafe-history filtering, and reconnect catch-up (`apps/warroom/tests/noticeBoardRelay.test.ts`) * [x] T021 \[S1707] \[P] Add Worker tests for resolution relay, unknown notice resolution, malformed frames, blocked fields, and legacy `warroom_room_notice` compatibility (`apps/warroom/tests/noticeBoardRelay.test.ts`) * [x] T022 \[S1707] Run focused protocol and Worker tests plus ASCII/LF validation for session artifacts (`packages/protocol/tests/warroomNoticeRelay.test.ts`, `apps/warroom/tests/noticeBoardRelay.test.ts`) *** ## Completion Checklist Before marking session complete: * [x] All tasks marked `[x]` * [x] All tests passing * [x] All files ASCII-encoded * [x] implementation-notes.md updated * [x] Ready for the validate workflow step *** ## Next Steps Run the implement workflow step to begin AI-led implementation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://faction-os.gitbook.io/faction-os-docs/.spec_system/archive/sessions/phase17-session07-war-room-worker-relay-and-catchup/tasks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.