c10. Guide Walk

Opened 2026-11-13 from the session that ran the guide walk (Mark as an evaluator new to Qpoint, a Claude Code session as the evaluator's agent, driving the app's guide MCP server). The report is cycles/notes/2026-11-13-guide-agent-walk.md, with its captures beside it. The task as handed to this cycle's session:

Work through the report at cycles/notes/2026-11-13-guide-agent-walk.md (captures beside it), in its order.

1. The agent view (item 1): a view state of its own, not minimized, where the tour panel is hidden and the focus still draws — ring, dim/blur scrim, the agent's point callout and the step's callouts. Today set-view { minimized: true } turns the focus off and start() resets minimized. Make it the default while an agent drives (lastMove.by == "agent"), keep it across step moves, bring the panel back on the person's own move, give free-form point (no tour) the same focus, and update the server instructions in crates/app/src/guide/.
2. Callouts (1a, 1b): a row's callout points at its ringed row and keeps clear of neighbouring rows' key column, of another callout, and of the page's own text; more inner padding (tokens, not px literals).
3. The data source (1c): tour-state and read-step carry the source in effect, the instructions tell agents to check it before saying "yours", a learn tour on synthetic data says so in its panel, explain knows "synthetic".
4. The guide's words (1d, 1e): region text in the columns' own words and carrying source/harnesses; explain entries for the inventory columns, "sanctioned", "denied", and what this app does and doesn't judge.
5. Arguments (2), region text (3: panel leak, empty, truncated, labels, windows, plural) and the Help page's connect line (4). Item 5 is a design call — list it for Mark, don't build it.

Done = each item fixed or answered in the report (add an "Outcome" line under each), a story or headless test per view and callout change, captures of the agent view (panel hidden, focus drawn) and of a row callout placed correctly, and a review stop for Mark with what to look at.

Mark's ruling behind item 1, from the walk: "what feels natural when you're driving is to hide the tour guide panel unless you're writing that content to show something in particular. Otherwise, I just want to see what you're highlighting on the page and what your callout is saying about it." And: "when you hide that, we lose the nice highlighting background blurring."

Create a plan, ask any clarifying questions, suggest patterns I may not be considering.