103 lines
4.9 KiB
Markdown
103 lines
4.9 KiB
Markdown
# Session 0028.0 — Transcript
|
||
|
||
> App: vscode-cowriting-plugin
|
||
> Start: 2026-06-11T21-25 (PST)
|
||
> End: 2026-06-11T21-31 (PST)
|
||
> Type: capture (tracked-lite)
|
||
> Posture: careful (capture default, §6.5)
|
||
> Status: **FINALIZED**
|
||
|
||
## Launch prompt
|
||
|
||
```
|
||
Capture session: file an issue for the markdown cowriting product vision —
|
||
clean zero-annotation editor (left) + interactive annotated markdown preview
|
||
(right) as the single review surface; annotations on/off toggle; per-author
|
||
track-changes (green=human, blue=LLM, strikethrough=deleted) with ✓/✗
|
||
accept-reject on LLM changes only, driven from inside the preview. Markdown-only.
|
||
```
|
||
|
||
## Outcome (one line)
|
||
|
||
Filed **issue #29** (`type/feature`, `priority/P1`) — "Interactive track-changes
|
||
review in the markdown preview (clean editor + accept/reject)" — capturing a
|
||
product-defining vision developed in a brainstorm during session 0027's
|
||
conversation.
|
||
|
||
## Pre-state
|
||
|
||
- Came directly out of session 0027 (which finalized just before): the operator
|
||
had hit the F6 two-pane diff (`ctrl+option+d`) with F3 attribution decorations
|
||
bleeding into it and said "I don't understand this."
|
||
- That sparked a brainstorm (in 0027's conversation, before this capture session
|
||
was claimed): single-pane Word-style track changes → in-editor inline → and
|
||
finally the clean-editor / interactive-annotated-preview split, markdown-only.
|
||
- No open issues on the tracker (Epic #1 + F2–F9 + #22 all shipped).
|
||
|
||
## Arc (turn by turn)
|
||
|
||
1. **Diagnosis (carried from 0027).** Identified the confusing screenshot as two
|
||
plugin layers colliding: F6 diff (red/green) + F3 attribution (blue Claude fill
|
||
/ green human border) on the same text. Confirmed the blue from the code
|
||
(`AGENT_DECO = rgba(99,102,241,.18)`).
|
||
2. **Brainstorm (superpowers:brainstorming).** Walked the operator from "single
|
||
pane, strikethrough, Word-like" through the forks:
|
||
- Surfaced that F7 (`ctrl+option+r`) already is a single-pane rendered
|
||
track-changes view; F9 already adds an author-coloring toggle.
|
||
- Operator wanted **B** (in-editor inline) + **accept/reject of LLM changes
|
||
only** → mapped onto F3 (who) + F4 (accept/reject).
|
||
- Operator disliked F3's editor border → led to "color only the delta, by
|
||
author" and then the realization that the **editor should carry zero
|
||
annotation** and all review lives in the **preview**.
|
||
- Operator locked **markdown-only** ("this should really be the
|
||
vscode-markdown-cowriting-plugin") — F6 deprecated as a view; **rename
|
||
deferred**.
|
||
- Chose to **capture** (not spec now).
|
||
3. **Capture (this session, wgl-capture).** Claimed tracked-lite session 0028;
|
||
resolved the content repo; sized the ask as a **Feature** (needs design, one
|
||
coherent increment); drafted `issues/interactive-markdown-review-preview.md`
|
||
section by section; handed it for review.
|
||
4. **File (on approval).** Operator said "file it." Fixed two script-config snags
|
||
(default host was `git.wiggleverse.org` → `--host git.benstull.org`; forced
|
||
token service resolved the wrong host's token → set
|
||
`WGL_CAPTURE_TOKEN_SERVICE=wgl-gitea-issues-readwrite-token-git.benstull.org`).
|
||
Ensured labels, filed **#29**, verified labels (`type/feature` + `priority/P1`).
|
||
|
||
## Cut state
|
||
|
||
- **Issue #29** open on `benstull/vscode-cowriting-plugin`:
|
||
https://git.benstull.org/benstull/vscode-cowriting-plugin/issues/29
|
||
- Draft `issues/interactive-markdown-review-preview.md` stays **uncommitted** in
|
||
the content repo working tree (INV-8 — the Author's to publish/discard).
|
||
- Code repo `main` clean & pushed (only the carried-in stray `specs/` untracked).
|
||
- No spec/plan artifact submitted (INV-6, tracked-lite).
|
||
|
||
## Tooling notes (for the next capture on a benstull-hosted app)
|
||
|
||
`ensure-capture-labels.sh` / `capture-issues.sh` default to `git.wiggleverse.org`
|
||
and to the host-less issue token. For benstull apps, pass `--host git.benstull.org`
|
||
**and** `WGL_CAPTURE_TOKEN_SERVICE=wgl-gitea-issues-readwrite-token-git.benstull.org`.
|
||
(Candidate fix worth a plugin-feedback issue: auto-derive the host from the
|
||
resolved app remote.)
|
||
|
||
## Deferred decisions
|
||
|
||
_Careful posture — the operator approved the filing (INV-1) and the type (Feature)
|
||
explicitly; nothing was auto-decided that needs review._
|
||
|
||
## Operator plate (loose ends)
|
||
|
||
- Session **0024** still unfinalized.
|
||
- Pre-existing uncommitted content-repo state not from this session:
|
||
`M specs/coauthoring-diff-view.md` + several untracked `issues/*.md` drafts.
|
||
- Stray `specs/coauthoring-out-of-workspace.md` in the **code** repo working tree.
|
||
- Capture-script host/token defaults (above) — candidate plugin-feedback.
|
||
|
||
## Next /goal
|
||
|
||
**Brainstorm / spec #29.** It's a `type/feature`, so it needs a **Solution Design
|
||
before plan-and-execute** (R3) — and most of the design already exists in the
|
||
issue body + memory. (Operator has in fact asked to brainstorm #29 next.) The
|
||
rename to `vscode-markdown-cowriting-plugin` is a separate deliberate gesture if
|
||
wanted.
|