> 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-session03-server-routes-and-websocket-parity/implementation_summary.md). # Implementation Summary **Session ID**: `phase17-session03-server-routes-and-websocket-parity` **Package**: `apps/server, packages/protocol` **Completed**: 2026-06-05 **Duration**: \~3 hours *** ## Overview Delivered the canonical Notice Board route family on top of the persistent server manager and protocol contracts. The session added `/notice-board` listing, context, post, and resolve routes, preserved `/notice` and `/notices` compatibility behavior, updated WebSocket hydration and `post_notice` handling for the expanded Notice Board payload, and locked the parity with focused real-mode tests. *** ## Deliverables ### Files Created | File | Purpose | Lines | | --------------------------------------------------------------------------------------------------- | -------------------------------------------------------- | ----- | | `apps/server/src/routes/noticeBoard.ts` | Canonical Notice Board routes and compatibility adapters | \~260 | | `apps/server/tests/noticeBoardRoutes.test.ts` | Real-mode canonical and compatibility route coverage | \~260 | | `.spec_system/specs/phase17-session03-server-routes-and-websocket-parity/IMPLEMENTATION_SUMMARY.md` | Session closeout summary | \~80 | ### Files Modified | File | Changes | | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | | `apps/server/src/server.ts` | Mounted the Notice Board router in the local API groups. | | `apps/server/src/routes/heroes.ts` | Removed legacy Notice Board route ownership. | | `apps/server/src/ws/clientMessageValidation.ts` | Accepted expanded `post_notice` payload fields and bounds. | | `apps/server/src/ws/handlers.ts` | Passed canonical Notice Board fields through hydration and posting flows. | | `apps/server/tests/routes.test.ts` | Adjusted route coverage for the extracted Notice Board router. | | `apps/server/tests/websocket.test.ts` | Added hydration, post, and resolve parity coverage. | | `packages/protocol/tests/events.test.ts` | Locked expanded Notice Board event shapes. | | `packages/protocol/tests/rest.test.ts` | Locked canonical and compatibility Notice Board route contracts. | | `.spec_system/state.json` | Marked the session complete and advanced the session history. | | `.spec_system/PRD/phase_17/PRD_phase_17.md` | Updated phase progress and the session tracker. | | `.spec_system/PRD/PRD.md` | Updated the high-level Phase 17 status note. | | `.spec_system/PRD/phase_17/session_03_server_routes_and_websocket_parity.md` | Marked the phase session complete. | | `.spec_system/specs/phase17-session03-server-routes-and-websocket-parity/spec.md` | Marked the spec complete. | | `package.json` | Bumped the patch version. | *** ## Technical Decisions 1. **Canonical route ownership moved into a dedicated router**: This keeps the Notice Board API surface centralized and removes it from the generic hero route module. 2. **Compatibility stayed on the same manager path**: Legacy `/notice`, `/notices`, and `post_notice` callers now normalize into the canonical Notice Board behavior instead of maintaining a second implementation. *** ## Test Results | Metric | Value | | -------- | ----- | | Tests | 2429 | | Passed | 2428 | | Coverage | N/A | *** ## Lessons Learned 1. Real-mode route and WebSocket tests are the fastest way to prove contract parity after extracting a shared router. 2. Session closeout is easier to audit when the phase tracker and root PRD are updated alongside the implementation summary. *** ## Future Considerations Items for future sessions: 1. Complete the web cockpit Notice Board UI and store normalization in the next session. 2. Continue the remaining Phase 17 work toward CLI, hooks, relay, and validation handoff. *** ## Session Statistics * **Tasks**: 24 completed * **Files Created**: 3 * **Files Modified**: 13 * **Tests Added**: 2 * **Blockers**: 0 resolved --- # 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-session03-server-routes-and-websocket-parity/implementation_summary.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.