> 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_01_baseline_validation.md).

# Session 01: Baseline Validation

**Session ID**: `phase32-session01-baseline-validation` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Confirm the reported fresh-mobile failure and validate the input capability signal before implementation.

***

## Scope

### In Scope (MVP)

* Reproduce the no-preferences AI Rogue mobile path on the current local or public demo build.
* Capture capability values for `pointer: coarse`, `hover: hover`, viewport, and `navigator.maxTouchPoints`.
* Verify that explicit `compact` remains playable on mobile.
* Verify that explicit `keyboard` remains intentionally keyboard-first on mobile.
* Compare fresh mobile and fresh desktop behavior.
* Record whether the minified React hydration warning is independent of the input blocker.

### Out of Scope

* Changing AI Rogue source code.
* Changing preference schema defaults.
* Adding new Settings UI.
* Adding public-demo deployment configuration.

***

## Prerequisites

* [ ] Phase 32 PRD and session stubs exist.
* [ ] Current research doc is available at `docs/ongoing-projects/ai-rogue-mobile-input-research-2026-06-24.md`.
* [ ] A local preview or static public-demo build can be served for probing.

***

## Deliverables

1. Fresh-state reproduction result for mobile and desktop.
2. Capability matrix for fresh mobile, fresh desktop, explicit keyboard, and explicit compact.
3. Recommendation on whether the pointer/hover heuristic is ready for Session 02 implementation.
4. Note on whether the observed hydration warning is independent or needs a separate blocker.

***

## Success Criteria

* [ ] Fresh mobile with no `ai-os.ai-rogue.preferences.v1` record reproduces blocked movement before the fix.
* [ ] Explicit compact mode can Start and move on mobile.
* [ ] Explicit keyboard mode stays keyboard-first on mobile.
* [ ] The selected auto signal resolves mobile or mobile-emulated phones to compact and desktop/fine-pointer contexts to keyboard.
* [ ] Any public-demo hydration warning is classified as independent or carried into Session 02 as implementation risk.


---

# 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_01_baseline_validation.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.