F4: propose/accept diff flow — pending proposals, ✓/✗ review, seam-applied acceptance (Feature #12) #13
Reference in New Issue
Block a user
Delete Branch "feat/f4-propose-accept"
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?
Implements Feature #12 per the graduated Solution Design
vscode-cowriting-plugin-content/specs/coauthoring-propose-accept.md(session 0012; plan archived at finalize).What
cowriting.proposalscomment thread with a fenced diff and ✓ Accept / ✗ Reject actions. The document never changes without the human's say-so.applyAgentEditseam, so accepted text lands Claude-attributed with zero new attribution code; stale/orphaned proposals are flagged, never applied by guess.proposals[](typed, on the sharedanchors/Provenanceprimitives,schemaVersionstays 1) persists at propose time, survives reload, re-anchors; store prune now counts proposal anchors.PendingEditRegistry.matchEventreplaces per-hunk exact matching — the host word-diffs one applied WorkspaceEdit into several minimal hunks, which the F4 accept E2E exposed (seam edits fell through as fragmented human spans).Gate
typecheck · 75/75 vitest · both bundles · 16+3 host E2E (incl. the new F4 suite: propose/accept/reject/persist/re-anchor/stale/coexist, no LLM in CI) · scripted live smoke green (
run_8xPNs1QJ, 34.6s). In-editor propose→accept click-through documented indocs/MANUAL-SMOKE-F4.md.Closes #12
🤖 Generated with Claude Code