> 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_35/session_02_fixed_blocker_regression_coverage.md).

# Session 02: Fixed Blocker Regression Coverage

**Session ID**: `phase35-session02-fixed-blocker-regression-coverage` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Lock in regression coverage for the original default-enable blockers and the highest-risk fixed AI Rogue contracts.

***

## Scope

### In Scope (MVP)

* Verify or add lethal turn-start damage coverage across Movement, Strike, Surge, and Protocol, including each Protocol branch.
* Verify or add mounted runtime assistive summary coverage that changes after movement and includes motion, contrast, input, and run-state context.
* Verify or add coverage that production Play routes ignore or gate combat fixture scenarios while test-only deterministic combat remains available.
* Verify or add transient feedback sprite-pool bound coverage for long mounted runs.
* Verify or add coverage for simulation-owned selected-upgrade and progression-loadout initialization, direct durable claim normalization or rejection, and durable-to-runtime save hydration.

### Out of Scope

* Broad module extraction beyond test-directed fixes needed to expose a stable contract.
* Documentation-only cleanup that belongs in Session 09.

***

## Prerequisites

* [ ] Session 01 has identified which Phase 34 tests already cover each contract.

***

## Deliverables

1. Focused unit, integration, or e2e tests for AR-D6-001, AR-D2-001, AR-D1-002, AR-D4-001, AR-D1-001, AR-D5-001, and AR-D5-002.
2. Clear test names and assertions for fixed blocker behavior.
3. Focused AI Rogue test evidence.

***

## Success Criteria

* [ ] Each original default-enable blocker has a direct regression guard or recorded equivalent coverage.
* [ ] Oversized direct claims cannot produce wallet and ledger drift.
* [ ] Durable save payloads are converted through schema-owned helpers or an explicitly tested adapter.
* [ ] Focused AI Rogue unit and browser tests pass.

## Folded Audit Detail Routed To This Session

### Finding IDs Owned

* AR-D6-001: dynamic runtime summary must reach the mounted canvas or DOM accessible surface and update after movement.
* AR-D2-001: lethal turn-start status damage must prevent Movement, Strike, Surge, and every Protocol branch from resolving after defeat.
* AR-D1-002: production Play routes must not expose the deterministic combat fixture scenario through query params.
* AR-D4-001: inactive transient `feedback:*` sprites must be destroyed or bounded during long mounted runs.
* AR-D1-001: selected-upgrade and progression-loadout mutation must flow through simulation-owned APIs.
* AR-D5-001: direct oversized durable claims must not drift wallet and ledger amounts.
* AR-D5-002: durable saved-run snapshots must be distinct from live runtime snapshots and hydrate through schema-owned helpers.
* D8-001 and high-priority Coverage Gaps: direct tests are required for lethal DOT, assistive summaries, command/update mutation ownership, transient sprite bounds, durable claim validation, and durable-to-runtime conversion.

### Source Locations From Audit

* `src/extensions/ai-rogue/runtime/renderer.ts:852`: renderer-local selected upgrade mutation.
* `src/extensions/ai-rogue/views/play-view.tsx:125`: historical production combat fixture query path.
* `src/extensions/ai-rogue/runtime/index.ts:3`: historically broad runtime barrel and fixture exposure.
* `src/extensions/ai-rogue/runtime/simulation.ts:2419`: Surge/Protocol lethal status gap.
* `src/extensions/ai-rogue/runtime/renderer.ts:1298`: transient feedback sprite retention.
* `src/extensions/ai-rogue/persistence.ts:1006`: durable claim validation drift.
* `src/extensions/ai-rogue/runtime/types.ts:635`: live/durable runtime snapshot naming confusion.
* `src/extensions/ai-rogue/runtime/__tests__/simulation.test.ts:1`: coverage anchor for lethal-DOT matrix.

### Regression Evidence Required

* [ ] Lethal-DOT matrix covers Movement, Strike, Surge, and Protocol branches.
* [ ] Mounted assistive summary changes after movement and includes motion, contrast, input, and run-state context.
* [ ] Production routes ignore fixture scenario query behavior while tests keep a local/test-only deterministic combat hook.
* [ ] Long mounted run or synthetic descriptor test proves transient feedback sprite-pool bounds.
* [ ] Direct oversized claim regression proves no wallet/ledger drift.
* [ ] Durable saved-run conversion helper is tested.


---

# 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_35/session_02_fixed_blocker_regression_coverage.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.
