add sessions/0042/SESSION-0042.0-TRANSCRIPT-2026-06-12T21-04--2026-06-13T07-16.md + replace placeholder/variant SESSION-0042.0-TRANSCRIPT-2026-06-12T21-04--INPROGRESS.md

sessions/0042/SESSION-0042.0-TRANSCRIPT-2026-06-12T21-04--2026-06-13T07-16.md

@@ -0,0 +1,62 @@
+# Session 0042.0 — Transcript
+
+> App: vscode-cowriting-plugin
+> Start: 2026-06-12T21-04 (PST) · End: 2026-06-13T07-16 (PST)
+> Type: capture (tracked-lite)
+> Posture: autonomous (yolo)
+> Goal: capture "When I pin the baseline, there should be no annotations in the
+> review panel"
+> Outcome: filed **#48** (`type/story`, `priority/P2`).
+
+## Launch prompt
+
+`/wgl-capture When I pin the baseline, there should be no annotations in the
+review panel`
+
+Opened mid-session, concurrent with the in-flight brainstorming session 0041
+(only that — my own — session in flight; warned + proceeded per autonomous).
+
+## Arc
+
+1. **Claim.** Claimed session 0042 (`--type capture`, tracked-lite). App +
+   content repo already resolved from 0041.
+2. **Ground the behavior.** Read `renderReview`/`colorByAuthor`/`renderReviewOp`
+   in `trackChangesModel.ts`: an **unchanged** block renders as
+   `cw-blk cw-unchanged` with `colorByAuthor` applied (line ~526). So after a Pin
+   baseline (baseline == current → every block unchanged), the change axis is
+   empty but **F3 authorship coloring still paints every block** — and the panel
+   *does* refresh on pin (`onDidChangeBaseline`), so it's not a stale render. The
+   author colors are the "annotations."
+3. **Scope fork (AskUserQuestion).** Operator chose **pin → fully clean panel**
+   (zero-diff state: change marks AND authorship colors gone), **not** the broader
+   "authorship never colors unchanged text." → a single, design-free increment.
+4. **Type.** Would be `type/bug`, but `capture-issues.sh` accepts only
+   epic|feature|story|task (the gap plugin feedback #124 tracks — not re-filed).
+   Filed as the accurate fileable type `type/story`, P2.
+5. **Draft + approval + file.** Authored
+   `issues/pin-baseline-clears-review-annotations.md`; operator **approved**;
+   ensured labels (`--host git.benstull.org`,
+   `WGL_CAPTURE_TOKEN_SERVICE=wgl-gitea-issues-readwrite-token-git.benstull.org`);
+   filed **#48** —
+   https://git.benstull.org/benstull/vscode-cowriting-plugin/issues/48
+
+## Deferred decisions
+
+- **Type compromise (driver, tooling-forced)** — filed as `type/story` though the
+  observation is bug-flavored (surprising behavior on a primary gesture);
+  `capture-issues.sh` can't type `bug`. The bug-typing gap is already tracked as
+  plugin feedback **#124**; not re-filed.
+
+## Loose ends
+
+- Draft `issues/pin-baseline-clears-review-annotations.md` left **uncommitted** in
+  the content repo working tree (the Author's to publish or discard — capture
+  INV-8).
+
+## Next /goal
+
+(Continuation is the 0041 handoff.)
+
+```
+/goal plan-and-execute #42 (SLICE-1 of the document-edit flow — Ask-Claude entry-point menu wiring), per specs/coauthoring-document-edit-flow.md
+```

sessions/0042/SESSION-0042.0-TRANSCRIPT-2026-06-12T21-04--INPROGRESS.md

@@ -1,20 +0,0 @@
-# Session 0042.0 — Transcript
-
-> App: vscode-cowriting-plugin
-> Start: 2026-06-12T21-04 (PST)
-> Type: capture
-> Status: **PLACEHOLDER — claimed at session start; finalized at session end.**
->
-> This file reserves session ID 0042 for vscode-cowriting-plugin. The driver replaces this
-> body with the full transcript and renames the file to its final
-> SESSION-0042.0-TRANSCRIPT-2026-06-12T21-04--<end>.md form at session end.
-
-## Launch prompt
-
-_(launch prompt not captured at claim time)_
-
-## 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._