Reject configuration edits for unopened language-server documents
A change notification for an unknown URI crashes the document map. Validate document lifecycle.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Protocols · State machines
Estimated field mix
- Compiler and language tooling80%
- API design20%
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
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Open establishes document state
- Unknown change is handled explicitly
- Close releases state
Implementation constraints
- Follow the declared protocol subset's error behavior.
Verification to include
- Open then change fixture
- Change unopened document
Deliverables
- Document lifecycle handler and cases
Rollout and recovery
Ignore unsupported lifecycle notifications with bounded diagnostics.
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.