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

# Session 04: Settings And Copy

**Session ID**: `phase32-session04-settings-and-copy` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Make Settings, Loadout, Play, and HUD language match the raw and effective input-mode contract.

***

## Scope

### In Scope (MVP)

* Add `Auto` to the Settings controls choice.
* Show the resolved mode beside Auto, such as `Auto (compact)` or `Auto (keyboard)`.
* Preserve explicit `Keyboard` and `Compact` choices.
* Replace `Keyboard and canvas` copy unless canvas pointer input is also made valid in keyboard mode.
* Update Loadout summaries to handle Auto without collapsing it incorrectly.
* Update Play copy to include Auto and report the effective controls state.
* Ensure compact-control status copy agrees with the effective mode.
* Ensure HUD/runtime summaries agree with effective mode.
* Add component tests covering Auto selection and resolved copy.

### Out of Scope

* New settings diagnostics panels.
* New input devices such as gamepad or pointer lock.
* Default extension enablement.
* Runtime renderer refactors.

***

## Prerequisites

* [ ] Session 02 resolver/hook exists.
* [ ] Session 03 effective mode plumbing exists.
* [ ] Current Settings, Loadout, and Play copy locations are identified.

***

## Deliverables

1. Settings control with Auto, Keyboard, and Compact options.
2. Loadout, Play, compact-control, and HUD copy aligned to raw/effective mode.
3. Focused component tests for saved Auto and resolved-mode labels.

***

## Success Criteria

* [ ] Settings can save Auto, Keyboard, and Compact.
* [ ] Auto copy reports the current resolved mode consistently across views.
* [ ] Keyboard copy no longer promises canvas input unless implemented.
* [ ] Explicit choices remain visibly distinct from Auto.
* [ ] Existing accessibility and responsive behavior for control buttons remain intact.


---

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