F10: interactive track-changes review in the markdown preview (#29) #30
Reference in New Issue
Block a user
Delete Branch "f10-interactive-review"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
F10 (#29) — interactive track-changes review in the markdown preview. Resolves the surface-collision friction (F6 raw diff + F3 attribution + F4 threads colliding on the same text) into one model: write left, review right.
ctrl+alt+d) and retire the attribution toggle. F3spansFor, F4 accept/reject logic, and the F6 baseline stay as data layers.renderReview(baseline, current, authorSpans, proposals)overlays the F7 baseline diff (added/changed prose author-colored via the salvaged F9colorByAuthorsentinels; deletions struck) with pending F4 proposals as bluecw-proposalblocks carrying ✓/✗. PlusrenderPlainfor the off-state.acceptById/rejectByIdseam — the webview never mutates the document. Status-bar indicator surfaces pending proposals when no preview is open (PUC-6).renderAuthorship+ segmented control removed) and drops F6's any-file reach as a user goal (markdown-only).Spec:
specs/coauthoring-interactive-review.md(§7.2 slices SLICE-1..4). Plan:docs/superpowers/plans/2026-06-11-f10-interactive-review.md.Known v1 deferral: resolved proposals render as trailing
cw-proposalblocks rather than inline-at-anchor (spec §2/§6.2) — deterministic, never-dropped (INV-34); inline placement is a candidate follow-up.Test Plan
npm test— 189 unit (vitest, vscode-free):renderReview/renderPlain/colorByAuthorincl. duplicate-block coloring + determinism.npm run test:e2e— 46 + 5 host E2E green: open / annotations toggle / propose→accept→reject / clean-editor (INV-32) / hidden-F6 / status-bar (PUC-6).npm run build— clean typecheck + webview bundle.docs/MANUAL-SMOKE-F10.md(visual + real ✓/✗ clicks — sealed sandbox, not E2E-asserted).🤖 Generated with Claude Code