Complete configuration keys only within valid assignment contexts
Completion suggests keys inside string literals and comments. Restrict suggestions using syntax context.
- Focused work estimate
- 2h 45m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Syntax analysis · Completion
Estimated field mix
- Compiler and language tooling100%
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.
Acceptance criteria
- Assignment context gets known keys
- String/comment contexts suppress keys
- Incomplete assignment remains supported
Implementation constraints
- Use public grammar metadata, not hidden evaluator assets.
Verification to include
- Complete incomplete key
- Request completion inside quoted value
Deliverables
- Context completion and cases
Rollout and recovery
Return no suggestions when context cannot be determined.
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.