- INV-10: coediting is opt-in per document ('Coedit this Document with
Claude'); every surface (SCM/QuickDiff, comments, preview annotations,
edit entry points) gates on the active coediting set so other markdown
files are never hijacked. Adds PUC-7 (enter/leave), CoeditingRegistry.
- BUC-5/PUC-8/D8: on a coedited doc a comment fires a turn that replies
in-thread and offers an edit -> pending proposal (never edits directly).
- INV-11/D9: verified against the VS Code API that the native diff editor
cannot recolor changes per-author (diffEditor.* tokens are global;
inlineEdit./chat tokens are accept-state not author; diff-pane decorations
composite + are unreliable). Authorship lives in the preview (optionally a
decoration track-changes editor). New open Qs: Q5 (authorship surface),
Q6 (comment trigger).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Reframe §1 away from a redesign-of-the-old-plugin narrative and root it in
the real-world problem: coediting a markdown document with a machine is hard
today (rewrite-not-a-diff, all-or-nothing, blurred authorship, no clean
rendered view, opaque machine work). Solution and technical substance stand on
their own; proven patterns reused on merit, not as old-plugin lineage.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
BenStullsBets