> 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/phase03-session02-task-queue-and-agent-template-contracts/tasks.md). # Task Checklist **Session ID**: `phase03-session02-task-queue-and-agent-template-contracts` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-05-29 *** ## Legend * `[x]` = Completed * `[ ]` = Pending * `[P]` = Parallelizable (can run with other \[P] tasks) * `[SNNMM]` = Session reference (NN=phase number, MM=session number) * `TNNN` = Task ID *** ## Progress Summary | Category | Total | Done | Remaining | | -------------- | ------ | ------ | --------- | | Setup | 3 | 3 | 0 | | Foundation | 6 | 6 | 0 | | Implementation | 7 | 7 | 0 | | Testing | 4 | 4 | 0 | | **Total** | **20** | **20** | **0** | *** ## Setup (3 tasks) Initial configuration and environment preparation. ### Cross-package * [x] T001 \[S0302] Verify Session 01 matrix, current route taxonomy, and protocol/server prerequisites (`.spec_system/PRD/phase_03/orchestration_gap_matrix.md`) * [x] T002 \[S0302] Create implementation notes and security artifact placeholders (`.spec_system/specs/phase03-session02-task-queue-and-agent-template-contracts/implementation-notes.md`, `.spec_system/specs/phase03-session02-task-queue-and-agent-template-contracts/security-compliance.md`) * [x] T003 \[S0302] Confirm current task-queue and agent-template unsupported-route baseline (`apps/server/src/lib/unsupportedRoutes.ts`) *** ## Foundation (6 tasks) Core structures and base implementations. ### packages/protocol * [x] T004 \[S0302] \[P] Create task queue contract types with bounded state, transitions, references, and validation errors (`packages/protocol/src/taskQueue.ts`) * [x] T005 \[S0302] \[P] Create agent template contract types with bounded defaults, constraints, suggestions, and validation errors (`packages/protocol/src/agentTemplates.ts`) * [x] T006 \[S0302] Export queue and template protocol modules (`packages/protocol/src/index.ts`) * [x] T007 \[S0302] Add queue/template REST request and response contracts with schema-aligned validation envelopes (`packages/protocol/src/rest.ts`) * [x] T008 \[S0302] Add queue/template WebSocket event frames with types matching declared contract and exhaustive union coverage (`packages/protocol/src/events.ts`) ### apps/server * [x] T009 \[S0302] Create server-side orchestration validation helpers with schema-validated input and explicit error mapping (`apps/server/src/lib/orchestrationValidation.ts`) *** ## Implementation (7 tasks) Main feature implementation. ### apps/server * [x] T010 \[S0302] Implement bounded task queue manager with deterministic ordering and idempotency protection for mutating paths (`apps/server/src/managers/taskQueue.ts`) * [x] T011 \[S0302] Implement local agent template manager with bounded suggestions and no historical raw template imports (`apps/server/src/managers/agentTemplates.ts`) * [x] T012 \[S0302] Add task queue REST routes for create, list, update, and reject with duplicate-trigger prevention while in-flight (`apps/server/src/routes/orchestration.ts`) * [x] T013 \[S0302] Add agent template REST routes for list, detail, and suggestion validation with bounded pagination, validated filters, and deterministic ordering (`apps/server/src/routes/orchestration.ts`) * [x] T014 \[S0302] Emit queue/template WebSocket updates with bounded payloads and no raw prompt, path, command, token, or terminal output fields (`apps/server/src/routes/orchestration.ts`) * [x] T015 \[S0302] Wire orchestration managers and routes into the server without changing auth, CORS, Origin, rate-limit, or body-size defaults (`apps/server/src/server.ts`) * [x] T016 \[S0302] Preserve queue-adjacent out-of-scope routes as deterministic 501 capability responses (`apps/server/src/lib/unsupportedRoutes.ts`) *** ## Testing (4 tasks) Verification and quality assurance. ### packages/protocol * [x] T017 \[S0302] \[P] Add protocol contract tests for queue/template exports, REST shapes, and WebSocket discriminants (`packages/protocol/tests/orchestration.test.ts`) ### apps/server * [x] T018 \[S0302] \[P] Add server route tests for queue/template happy paths, validation failures, unsupported paths, and sensitive-field non-echo (`apps/server/tests/orchestration.test.ts`) * [x] T019 \[S0302] \[P] Add WebSocket update coverage for queue/template mutations with explicit loading, empty, error, and unavailable state assumptions documented (`apps/server/tests/websocket.test.ts`) ### Cross-package * [x] T020 \[S0302] Run focused typecheck/tests plus ASCII, LF, and `git diff --check` validation (`.spec_system/specs/phase03-session02-task-queue-and-agent-template-contracts/implementation-notes.md`) *** ## 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] `security-compliance.md` updated * [x] Ready for the validate workflow step *** ## Next Steps Run the validate workflow step to verify session completeness. --- # 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/phase03-session02-task-queue-and-agent-template-contracts/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.