Ben Stull 4c947acc43 fix: proposal threads disable the reply input — decide-only, INV-12 ...

Playing with F4, the operator hit VS Code's default "Reply…" box on a
proposal thread: no submit command is wired for cowriting.proposals, so
typed text had nowhere to go. Proposals are decide-only (accept/reject in
the title bar); discussion belongs in a coauthoring thread. Set
canReply=false so the dead input never renders, and expose canReply on the
test-facing RenderedProposal with an E2E assertion.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-10 23:26:11 -07:00

..

fixtures/workspace/docs

test: host E2E — crossrung round-trip + newer-major fail-safe (F5 SLICE-4, PUC-2/PUC-4, #14)

2026-06-10 23:05:38 -07:00

suite

fix: proposal threads disable the reply input — decide-only, INV-12

2026-06-10 23:26:11 -07:00

suite-no-workspace

F4 SLICE-5: host E2E (propose/accept/reject/persist/stale/coexist) + seam fix: event-level net-effect matching survives host word-diff splitting (INV-9) (#12)

2026-06-10 22:12:15 -07:00

runTest.ts

Fix #8: register warning stubs when no workspace folder; F5 opens the repo. Add selection context menus (#9)

2026-06-10 14:26:59 -07:00