# Manual smoke — F11 preview toolbar as the primary interaction surface (#43) F11 makes the rendered preview's **header toolbar** the primary interaction surface: beside the existing **Annotations** switch it gains a **Pin baseline** button and a **single adaptive Ask-Claude button** (Edit Selection when text is selected in the preview, Edit Document otherwise). The webview's *visual* behavior — the buttons, the live label flip, and the selection→source mapping — is verified **here**, not in the automated host E2E (the webview is a sealed sandbox; the host's message→seam wiring is covered by the F11 E2E suite). Run once per change that touches F11. Live turns hit the SDK; use a trivial instruction to keep them quick. ## Setup 1. `npm run build` 2. Launch the Extension Development Host (F5 in VS Code, or the Run panel) with `sandbox/` open. 3. Open a markdown document with a few paragraphs (e.g. copy `test/e2e/fixtures/workspace/docs/preview.md`). ## Steps 1. **Right-click gateway (PUC-6).** Right-click the markdown editor **tab** (or use the editor title bar) → **"Cowriting: Open Review Preview"**. The preview opens beside the editor. (The palette entry and `Ctrl+Alt+R` still work too.) 2. **Three header controls (PUC-1).** The header row shows, left to right: the **☑ Annotations** checkbox (on), a **⌖ Pin baseline** button, and a **✦ Ask Claude to Edit Document** button. They restyle with the theme. 3. **Adaptive label — selection (PUC-2).** Select a paragraph **in the preview** (drag across rendered text). The Ask-Claude button label flips live to **"✦ Ask Claude to Edit Selection"**. Click elsewhere to clear the selection → it flips back to **"✦ Ask Claude to Edit Document"**. 4. **Edit Selection (PUC-3).** With a paragraph selected in the preview, click **Ask Claude to Edit Selection** → a host input box appears → type an instruction (e.g. "tighten this") → submit. A **blue `cw-proposal` block** appears **inline at that paragraph** with **✓ / ✗** (the selection mapped back to its source block; the edit ran host-side). The editor does **not** change (INV-10). Accept with **✓**: the replacement lands; the block clears. 5. **Edit Document (PUC-4).** Clear the selection (button reads "Edit Document"). Click it → instruct (e.g. "fix any typos and tighten") → submit. Claude's whole-document rewrite surfaces as **one or more** independent blue proposal blocks (one per changed hunk), each independently **✓ / ✗**-able. Accept some, reject others — each behaves as an ordinary F10 proposal. 6. **Pin baseline (PUC-5).** Make (or accept) a few changes so the preview shows change-marks and a non-zero summary. Click **⌖ Pin baseline**. Expect: the change-marks **clear**, the summary resets to `+0 −0`, and the header epoch reads **`pinned