Attach expected document versions to configuration code actions
Applying an old quick fix corrupts newer text. Include the snapshot version in the edit contract.
- Focused work estimate
- 2h 45m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Protocol design · Concurrency
Estimated field mix
- Compiler and language tooling70%
- API design30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
Fictional config editor Hazel speaks a bounded subset of the Language Server Protocol through a local transport adapter. Use a tiny declared configuration grammar and synthetic documents.
Setup prerequisites
- Define the supported protocol subset and configuration grammar.
- Create synthetic open/change/close messages and workspace fixtures.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- CLSP-101 · Reject configuration edits for unopened language-server documents
- CLSP-102 · Convert language-server positions using a declared encoding
- CLSP-103 · Apply configuration document edits in the supplied version order
- CLSP-104 · Publish configuration diagnostics for the checked document version
- CLSP-105 · Complete configuration keys only within valid assignment contexts
- CLSP-106 · Return configuration rename edits only for resolved local bindings
Acceptance criteria
- Matching version applies
- Changed version is rejected or recomputed
- Action describes its actual mutation
Implementation constraints
- Do not apply stale offsets optimistically.
Verification to include
- Apply fresh missing-delimiter fix
- Edit before applying old action
Deliverables
- Versioned code action and cases
Rollout and recovery
Hide code actions if client cannot enforce edit versions.
Value of the work
For the engineer: Practice protocol ordering and document-safe editing.
For the team: Inspect whether editor assistance preserves current user text and file boundaries.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.