> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase39-session01-baseline-and-registry-skeleton/tasks.md). # Task Checklist **Session ID**: `phase39-session01-baseline-and-registry-skeleton` **Total Tasks**: 16 **Estimated Duration**: 3-4 hours **Created**: 2026-06-30 *** Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[S3901]` session ref; `TNNN` task ID. *** ## Progress Summary | Metric | Value | | --------------- | ---------------- | | Tasks Completed | 16 / 16 | | Remaining Tasks | 0 | | Last Updated | 2026-06-30 18:38 | *** ## Setup (2 tasks) * [x] T001 \[S3901] Verify Phase 39 Session 01 prerequisites, current AI Rogue test files, and validation commands (`.spec_system/PRD/phase_39/session_01_baseline_and_registry_skeleton.md`) * [x] T002 \[S3901] Confirm current depth-helper values and max-depth behavior before adding registry code (`src/extensions/ai-rogue/runtime/run-factory.ts`) *** ## Foundation (5 tasks) * [x] T003 \[S3901] \[P] Add current three-depth content baseline tests with product-safe assertions for theme, arc, guard, protocol, terminal, prefab, music, ambience, and objective behavior with explicit loading-free deterministic setup (`src/extensions/ai-rogue/runtime/__tests__/content-baseline.test.ts`) * [x] T004 \[S3901] \[P] Add golden determinism helpers for safe public world and first-turn run summaries with deterministic ordering and no private data capture (`src/extensions/ai-rogue/runtime/__tests__/golden-determinism.test.ts`) * [x] T005 \[S3901] \[P] Create level registry type contracts for level specs, generation, placements, guarantees, finale metadata, and validation results with types matching declared runtime contracts; exhaustive enum handling (`src/extensions/ai-rogue/runtime/content/types.ts`) * [x] T006 \[S3901] \[P] Create the content registry barrel for future migration imports without route, renderer, bridge, generated-data, or PixiJS dependencies (`src/extensions/ai-rogue/runtime/content/index.ts`) * [x] T007 \[S3901] Extend Kernel Sentinel boss presentation baseline tests for scale and audio metadata expectations while preserving current frame-selection behavior (`src/extensions/ai-rogue/runtime/__tests__/boss-presentation.test.ts`) *** ## Implementation (5 tasks) * [x] T008 \[S3901] Author the initial three `AiRogueLevelSpec` rows from current shipped depth 1-3 helper values and keep depth 4 out of scope (`src/extensions/ai-rogue/runtime/content/levels.ts`) * [x] T009 \[S3901] Implement `levelSpecForDepth(depth)` and authored-main-run out-of-range rejection without routing existing runtime callers (`src/extensions/ai-rogue/runtime/content/levels.ts`) * [x] T010 \[S3901] Implement structural registry validation for unique IDs, contiguous 1-based depths, non-empty enemy tables, and finale placement (`src/extensions/ai-rogue/runtime/content/validate.ts`) * [x] T011 \[S3901] Implement local reference validation for initial theme, enemy, protocol, prefab, terminal, objective pickup, music, ambience, label, and lesson fields with schema-validated input and explicit error mapping (`src/extensions/ai-rogue/runtime/content/validate.ts`) * [x] T012 \[S3901] Add registry tests for valid initial specs plus malformed duplicate, gap, empty enemy table, invalid reference, unsafe text, finale placement, and out-of-range lookup cases (`src/extensions/ai-rogue/runtime/content/__tests__/levels.test.ts`) *** ## Testing (4 tasks) * [x] T013 \[S3901] Run focused new and touched test suites for baseline, determinism, registry, and boss presentation (`src/extensions/ai-rogue/runtime/__tests__/content-baseline.test.ts`) * [x] T014 \[S3901] Run existing focused AI Rogue resolver and runtime suites to prove no shipped depth 1-3 expected outputs changed (`src/extensions/ai-rogue/runtime/__tests__/world.test.ts`) * [x] T015 \[S3901] Run typecheck and confirm the pure content registry does not introduce renderer, route, bridge, generated-data, or PixiJS imports (`bun run typecheck`) * [x] T016 \[S3901] Validate ASCII and LF requirements for new spec, tasks, tests, and content registry files (`.spec_system/specs/phase39-session01-baseline-and-registry-skeleton/tasks.md`) *** ## Completion Checklist * [x] All tasks marked `[x]` * [x] All tests and checks passing * [x] All files ASCII-encoded with LF line endings * [x] implementation-notes.md updated * [x] Ready for `implement` to start the implement -> creview -> validate sequence *** ## Next Steps Run the `implement` workflow step. --- # 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://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/archive/sessions/phase39-session01-baseline-and-registry-skeleton/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.