> 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_32/session_05_gameplay_test_coverage.md).

# Session 05: Gameplay Test Coverage

**Session ID**: `phase32-session05-gameplay-test-coverage` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Lock the first-run mobile gameplay path into automated tests and public-demo smoke coverage.

***

## Scope

### In Scope (MVP)

* Update schema, persistence, save-state, client, and Runtime Canvas tests for the new auto default.
* Add fresh-state mobile Playwright coverage with no seeded `ai-os.ai-rogue.preferences.v1`.
* Use a true mobile/touch context for mobile tests, not only viewport resize.
* Add desktop/fine-pointer coverage proving auto remains keyboard-first.
* Assert runtime turn advancement or event text after mobile move input.
* Avoid relying only on canvas pixel-signature changes for gameplay proof.
* Add or extend public-demo mobile smoke for `/extensions/ai-rogue/play`.
* Preserve no-bridge assertions for public-demo route coverage.
* Run focused and relevant repo gates for AI Rogue and public-demo changes.

### Out of Scope

* Full repo release closeout.
* CI pipeline wiring for every public-demo command unless already scoped by failing coverage.
* Real-device test automation beyond documenting residual risk.
* New gameplay content.

***

## Prerequisites

* [ ] Sessions 02-04 are implemented.
* [ ] Existing mobile and runtime Playwright specs are understood.
* [ ] Public-demo static preview or equivalent smoke harness can run locally.

***

## Deliverables

1. Updated unit/component tests for the auto default.
2. Fresh-state mobile gameplay Playwright test.
3. Desktop/fine-pointer auto-mode assertion.
4. Public-demo mobile gameplay smoke for Start plus first move.
5. Validation notes for residual real-device risk, if any.

***

## Success Criteria

* [ ] Fresh mobile auto can Start and advance from turn 0 to turn 1.
* [ ] Fresh desktop auto does not enable compact controls by default.
* [ ] Explicit keyboard and explicit compact override auto on all tested contexts.
* [ ] Public-demo route coverage exercises gameplay input, not just visibility.
* [ ] Public-demo smoke does not request `/__*` local bridge endpoints.
* [ ] Focused AI Rogue tests and relevant public-demo smoke pass.


---

# 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_32/session_05_gameplay_test_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.