> 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/phase36-session05-sector-theme-audio-pack/tasks.md).

# Task Checklist

**Session ID**: `phase36-session05-sector-theme-audio-pack` **Total Tasks**: 20 **Estimated Duration**: 3-4 hours **Created**: 2026-06-28

***

Legend: `[x]` completed; `[ ]` pending; `[P]` parallelizable; `[SNNMM]` session ref; `TNNN` task ID.

***

## Progress Summary

| Metric              | Value   |
| ------------------- | ------- |
| Tasks Completed     | 20 / 20 |
| Estimated Remaining | 0 hours |
| Blockers            | 0       |

***

## Setup (3 tasks)

* [x] T001 \[S3605] Verify Session 04 routing contract, reserved basenames, media policy, and absence of preexisting final theme ambience files (`.spec_system/PRD/phase_36/session_04_theme_audio_routing_contract.md`)
* [x] T002 \[S3605] Inspect current music asset glob, theme ambience basename map, e2e audio proof, and music provenance schema before adding assets (`src/extensions/ai-rogue/runtime/audio.ts`)
* [x] T003 \[S3605] Create implementation notes for generation choices, provenance evidence, browser review, and validation commands (`.spec_system/specs/phase36-session05-sector-theme-audio-pack/implementation-notes.md`)

***

## Foundation (4 tasks)

* [x] T004 \[S3605] Create a local repeatable theme ambience generation script with exit-code handling, scratch output, final output, and no credential requirement (`scripts/generate-ai-rogue-theme-ambience.ts`)
* [x] T005 \[S3605] Define five theme bed source specs for coolant hum, corrupted index glitch bed, firewall alarm bed, vault sub-bass, and kernel core drive (`scripts/generate-ai-rogue-theme-ambience.ts`)
* [x] T006 \[S3605] Generate raw scratch masters without committing raw exports (`tmp/ai-rogue-theme-ambience/`)
* [x] T007 \[S3605] Render normalized 48 kHz stereo Ogg Opus loops to the exact Session 04 basenames (`src/assets/ai-rogue/audio/music/theme_cold_cache_ambience.ogg`)

***

## Implementation (6 tasks)

* [x] T008 \[S3605] Commit the remaining four optimized theme ambience loops with file names matching the route contract (`src/assets/ai-rogue/audio/music/theme_corrupted_index_ambience.ogg`)
* [x] T009 \[S3605] Update music provenance with source prompts, raw scratch paths, render stats, durations, bytes, codec, channel count, and sample rate for all five loops (`src/assets/ai-rogue/audio/music/provenance.json`)
* [x] T010 \[S3605] Verify or minimally repair real-file theme ambience lookup with types matching the declared route contract and exhaustive enum handling (`src/extensions/ai-rogue/runtime/audio.ts`)
* [x] T011 \[S3605] Extend browser audio proof to fetch and source-start all five real theme ambience assets without injected URL overrides (`tests/e2e/ai-rogue-runtime.spec.ts`)
* [x] T012 \[S3605] Update AI Rogue game-feel docs from reserved theme ambience contract to shipped asset pack with playback, fallback, and review notes (`docs/extensions/ai-rogue/game-feel.md`)
* [x] T013 \[S3605] Update media policy or session stub evidence so final theme ambience size and provenance rules are current (`.spec_system/PRD/phase_36/session_05_sector_theme_audio_pack.md`)

***

## Testing (7 tasks)

* [x] T014 \[S3605] \[P] Run focused runtime audio, adapter, and theme tests after asset and proof changes (`src/extensions/ai-rogue/runtime/__tests__/audio.test.ts`)
* [x] T015 \[S3605] \[P] Run TypeScript validation for changed script, test, and runtime imports (`tsconfig.json`)
* [x] T016 \[S3605] \[P] Run ffprobe verification for all five final ambience loops and record codec, channel, sample-rate, duration, and byte evidence (`src/assets/ai-rogue/audio/music/theme_model_vault_ambience.ogg`)
* [x] T017 \[S3605] Run asset-size validation and confirm every AI Rogue theme ambience loop stays under the 900 KB music cap (`scripts/check-asset-sizes.sh`)
* [x] T018 \[S3605] Run desktop and mobile browser audio pack proof with explicit loading, failed-request, page-error, and silent-fallback checks (`tests/e2e/ai-rogue-runtime.spec.ts`)
* [x] T019 \[S3605] Complete manual browser review across all five sector themes with product-facing UI only and diagnostics confined to tests or notes (`docs/extensions/ai-rogue/game-feel.md`)
* [x] T020 \[S3605] Validate ASCII and LF requirements, then update implementation notes with commands, evidence, and remaining non-feature caveats (`.spec_system/specs/phase36-session05-sector-theme-audio-pack/implementation-notes.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/phase36-session05-sector-theme-audio-pack/tasks.md?ask=<question>&goal=<endgoal>
```

`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.