add sessions/0033/SESSION-0033.0-TRANSCRIPT-2026-06-12T03-14--2026-06-12T03-27.md + replace placeholder/variant SESSION-0033.0-TRANSCRIPT-2026-06-12T03-14--INPROGRESS.md

sessions/0033/SESSION-0033.0-TRANSCRIPT-2026-06-12T03-14--2026-06-12T03-27.md

@@ -0,0 +1,59 @@
+# Session 0033.0 — Transcript
+
+> App: vscode-cowriting-plugin
+> Start: 2026-06-12T03-14 (PST)
+> End: 2026-06-12T03-27 (PST)
+> Type: capture (tracked-lite)
+> Posture: careful (capture default — output operator-reviewed)
+> Status: **FINALIZED**
+
+## Launch prompt
+
+`/wgl-capture` — "Undo doesn't render correctly in the preview pane".
+
+## Arc
+
+A capture session turning one operator observation into a filed, typed,
+source-linked Gitea issue.
+
+- **Clarified the symptom** (AskUserQuestion): "updates but wrong marks" in the
+  **F10 review preview**, reproduces **always** on undo. Reflected back the read
+  that undo reverts the buffer (text updates) but the overlay marks (since-baseline
+  diff / F3 author-coloring / F4 proposal blocks) go stale/wrong.
+- **Drafted** `issues/undo-renders-wrong-marks-in-preview.md` in the content repo
+  working tree (terse, bug-depth §5 template). Classified **type/bug**.
+- **Type/bug vs the tool:** `capture-issues.sh` only accepts
+  `epic|feature|story|task`, so it can't file a bug — even though the tracker has a
+  `type/bug` label and handbook §4.3's gate vocabulary includes "leaf
+  story/task/bug." Declined to mis-type the defect as a task to fit the tool.
+- **Filed `#38`** (type/bug, priority/P1 — operator decision) via `gitea-api.sh`
+  directly (labels API), since the deterministic capture script couldn't express
+  `bug`. → https://git.benstull.org/benstull/vscode-cowriting-plugin/issues/38
+- **Filed plugin feedback `#124`** (friction/medium) on the plugin tracker for the
+  capture-can't-type-bugs gap, framed as a taxonomy inconsistency to reconcile
+  across the Capture RFC §4, `ensure-capture-labels.sh`, `capture-issues.sh`,
+  `wgl-capture/SKILL.md`, and handbook §4.3.
+
+## Cut state
+
+Code repo clean on `main`. One issue filed (#38) + one plugin-feedback issue (#124).
+Draft `undo-renders-wrong-marks-in-preview.md` left uncommitted in the content repo
+working tree (operator's to publish — INV-8), alongside the other pending capture
+drafts + the F10 spec placed in session 0032.
+
+## Deferred decisions
+
+1. **Filed #38 with `type/bug` via a `gitea-api.sh` bypass** rather than
+   `capture-issues.sh`. Alternative: type it `task` to stay within the tool. Why:
+   the defect's honest type is `bug` (label exists; §4.3 recognizes it); the script
+   gap shouldn't drive mis-classification. The gap itself was logged as plugin
+   feedback #124. Priority P1 was the operator's explicit call.
+
+## Next /goal
+
+```
+/goal plan-and-execute #38 (undo renders wrong marks in the F10 review preview, P1) — reproduce the wrong-marks-after-undo case, find which layer (F3 attribution spans / F4 proposal anchors) goes stale on undo and reconcile it, confirm across edit→undo→redo
+```
+
+(P1 — supersedes session 0032's #33 pointer. #33 intra-emphasis hardening (P3) and
+#32 scroll-sync (feature, needs a Solution Design) remain open.)

sessions/0033/SESSION-0033.0-TRANSCRIPT-2026-06-12T03-14--INPROGRESS.md

@@ -1,23 +0,0 @@
-# Session 0033.0 — Transcript
-
-> App: vscode-cowriting-plugin
-> Start: 2026-06-12T03-14 (PST)
-> Type: capture
-> Status: **PLACEHOLDER — claimed at session start; finalized at session end.**
->
-> This file reserves session ID 0033 for vscode-cowriting-plugin. The driver replaces this
-> body with the full transcript and renames the file to its final
-> SESSION-0033.0-TRANSCRIPT-2026-06-12T03-14--<end>.md form at session end.
-
-## Launch prompt
-
-```
-Undo doesn't render correctly in the preview pane
-
-```
-
-## Deferred decisions
-
-_Autonomous-mode low-confidence calls the driver made and would have
-liked operator input on. Appended as the session runs; surfaced at
-finalize. Empty if none._