> 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/phases/phase_30/session_10_quality_gates_and_enablement.md).

# Session 10: Quality Gates And Enablement

**Session ID**: `phase30-session10-quality-gates-and-enablement` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Validate the extension end to end and prepare it for default enablement only after all gates pass.

***

## Scope

### In Scope (MVP)

* Run typecheck, lint, format check, unit tests, focused browser tests, build, bundle budget, asset-size checks, and private-runtime checks.
* Verify extension docs, capabilities, route behavior, runtime cleanup, privacy posture, and media provenance remain accurate.
* Fix failures in economy, save migration, RNG, simulation, combat, canvas rendering, interaction, mobile layout, reduced motion, and route cleanup tests.
* Decide whether the extension stays disabled, becomes opt-in, or is enabled by default.
* Capture remaining follow-up work for future content, collectors, WebGPU verification, worker protocol, or expanded progression.

### Out of Scope

* New gameplay features beyond fixing gate failures.

***

## Prerequisites

* [ ] Sessions 02 through 09 completed.

***

## Deliverables

1. Passing validation evidence for the accepted AI Rogue slice.
2. Updated documentation where implementation diverged from the original plan.
3. A clear enablement decision and follow-up list.

***

## Locked Visual Assets (`visual-assets.md`)

`docs/extensions/ai-rogue/visual-assets.md` holds the media-provenance record this session must verify stays accurate:

* Each committed asset has a provenance block (prompt summary, source file, cleanup steps, license note, size check) -- confirm these still match the files in `src/assets/ai-rogue/` and `docs/extensions/ai-rogue/generated/`.
* The committed atlas sizes (gameplay-atlas.png 11,446 B; ui-atlas.png 3,339 B) are well under the 200 KB policy; `bash scripts/check-asset-sizes.sh` should stay green. If atlases changed during Sessions 07-09, re-record sizes and provenance here before the enablement decision.

## Success Criteria

* [ ] Required commands pass: `bun run typecheck`, `bun run lint`, `bun run format:check`, focused Vitest suites, focused Playwright suites, `bun run build`, `bun run budget:check`, `bash scripts/check-asset-sizes.sh`, and `bun run runtime:check-private`.
* [ ] Documentation reflects the implementation state, deferred systems, and any changed decisions.
* [ ] No non-goal slipped into the initial implementation, including remote loading, unbounded token-burn rewards, unreviewed large media, or raw private telemetry exposure.


---

# 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/phases/phase_30/session_10_quality_gates_and_enablement.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.