By-ear pass: quit feel + entry-authorization setup flow (spec 03-03 §5.3, spec 01 §3.6)

[wine-fall]

What it is

The sensory acceptance owed by the quit-correctness + guide auto-mode ship (#136, #137). Both changed how leaving and consenting FEEL, and the deterministic evidence stops short of that: #136's exit latency was measured in plain-mode pty runs only (0.03–0.12 s /quit-to-exit across 10 runs; SIGINT 0.05 s), not in the TUI where Ctrl-C rides the wire as a typed /quit; #137 retired the per-action y/N wall for entry authorization + conversational checkpoints, so the 2026-07-06 / 2026-08-01 interactive passes recorded in spec 03-03 §5.3 ran under a flow that no longer exists. The real-SDK smokes proved the mechanics (interrupt cuts the session in 0 ms; a .env read is denied by the PreToolUse hook; node --version runs with zero questions), not the conversation's feel.

Spec

specs/spec03/03-03-guide-harness.md §5.3 (the human-run repair bar, revision note in the criterion) and §7.3; spec 01 §3.6 (leaving, extended to the Q&A flows).

Done when

Each box is the user's verdict from a real run (make dev on a machine with at least one gap, TUI front-end); a "no" spawns its own follow-up issue rather than reopening this contract:

• TUI Ctrl-C / typed /quit mid-setup-conversation: off the air in about a second, no swallowed second /quit, no orphaned front-end (dev.log command received → exit).
• Entry authorization feels right: one y at the offer card, then the guide investigates and fixes while narrating — no permission wall, and it still stops to ASK (in prose) at anything destructive, forked, or costing money.
• The secret guard never intrudes on a routine diagnosis (no spurious "credential" denial mid-repair), and the voice walkthrough's open .../app/api-keys step goes through.
• The live policy check lands in at most two fetch rounds or degrades honestly with the link — a pass here also closes Voice guide's live policy check burns ~6 consent rounds — cap the attempts, then degrade honestly #102 by its own Done-when.

[wine-fall]

PR #139 adds to this pass: during a real guided install, Esc must stop the flow (cards drop, radio boots on, one 'stopped' line), the pinned wordmark must hold above the flooding log, and the per-turn reply must happen in the input line (no spotlight card; /done ends the chat).

[wine-fall]

PR #140 (the conversation-partner boundary, boot slice) adds to this pass: (1) mid-install Esc cuts the action but the guide stays — typing 'continue' now commands the GUIDE, not the DJ; (2) the three-point face (strip 'in the workshop', identity 'setup guide · claude', warm input ink) reads clearly on entry and hands back visibly at the end; (3) Esc at the idle reply prompt ends setup like /done; (4) /quit prints 'going off the air...' the moment it lands — the ~3s teardown should now read as closing, not hanging.

[wine-fall]

PR #141 (mid-broadcast /setup recall) adds to this pass: (1) type /setup while a song plays — the record should keep spinning while the offer/conversation runs, and the DJ should stay quiet until you hand back; (2) decline or /done — the broadcast should resume where it left; (3) the auth-failure hint (■ 'type /setup to fix it') should appear once, not per segment, when a voice key lapses; (4) after fixing a voice endpoint mid-run, the next segment should SPEAK with the new endpoint and the identity line should read hosted.