# Session 0050.0 — Transcript

> App: vscode-cowriting-plugin
> Start: 2026-06-13T17-43 (PST)
> End: 2026-06-13T17-52 (PST)
> Type: capture
> Posture: autonomous (yolo)
> Status: **FINALIZED**

## Launch prompt

`/wgl-capture` — "When changing documents, we should decide what happens to the
review pane of the current document, and if the document switched to should get a
review experience or not"

## Pre-state

- Branch `main`, clean, pushed (origin/main). No in-flight sessions for the app.
- Tracker `benstull/vscode-cowriting-plugin` (host `git.benstull.org`); content
  repo `vscode-cowriting-plugin-content` cloned, with ~18 prior uncommitted
  capture drafts in `issues/`.
- Prior frontier exhausted (session 0047 note): remaining backlog items gated;
  operator directing. This is a capture session, not a build.

## Arc

1. **Claimed** tracked-lite session ID **0050** (`claim-session-id.sh --type
   capture`). Resolved app + content repo (`resolve-app.py`).
2. **Grounded** the ask by reading the code (Explore subagent over
   `src/trackChangesPreview.ts`, `diffViewController.ts`, `proposalController.ts`):
   confirmed the review pane is one-panel-per-doc keyed by URI
   (`trackChangesPreview.ts:45`) with **no** `onDidChangeActiveTextEditor`
   listener — so on document switch the pane **stays pinned** to its original doc
   (incidental, not designed) and the switched-to doc gets no review until
   `showTrackChangesPreview` is re-invoked. Per-doc review state (F6 baseline / F4
   proposals / F3 attribution) auto-creates on demand.
3. **Sized** the single ask: genuine forks (follow / pin / close; auto-review /
   on-demand) + needs design before build → `type/feature` (R3), `priority/P2`.
   Captures the decision-to-be-made; option space goes in Solution notes,
   non-binding.
4. **Drafted** `issues/review-pane-on-document-switch.md` in the content repo
   (working tree only, INV-8), full §5 template. Scanned clean for secrets
   (INV-3).
5. **Operator approved** filing as-is (feature, P2) via AskUserQuestion.
6. **Filed** → ensured labels (all pre-existing), then `capture-issues.sh` →
   **#57** (https://git.benstull.org/benstull/vscode-cowriting-plugin/issues/57).

## Cut state

- Session repo `vscode-cowriting-plugin`: clean `main`, nothing committed this
  session (capture touches only the content repo working tree). No PRs.
- Content repo: new draft `issues/review-pane-on-document-switch.md` left
  uncommitted for the Author to publish/discard (INV-8), alongside the prior
  drafts already there. Not pushed by this skill.
- Issue **#57** filed and open on the tracker.

## Deferred decisions

_None — single clear ask, operator approved the framing and type before filing._

## Operator plate

- One feature filed: **#57** (review-pane behavior on document switch, P2).
- ~19 capture drafts now sit uncommitted in `vscode-cowriting-plugin-content` —
  yours to commit/publish (or discard) when convenient.
- #57 needs a design before build (R3). No active plan frontier; operator to
  direct next.

## Next session prompt

`/goal` — operator to direct. Candidate: brainstorm a Solution Design for **#57**
(review-pane behavior on document switch) — settle the two coupled rules (outgoing
pane fate; whether the switched-to doc auto-gets a review experience) before
building. Other open: OQ-2 (F11 graduation), #32 (scroll-sync, needs design),
#35 (repo rename), #40 (undo provenance, P3, branch `s40-undo-provenance`
unmerged), #54 (undo still broken in sandbox).