# noCV engineering task library Content version 5 Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs. Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence. ## CLSP — A focused language server for configuration editing 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. **Field:** Compiler and language tooling. **Suggested stack:** TypeScript, JSON-RPC, Local protocol adapter, Vitest. **Engineer value:** Practice protocol ordering and document-safe editing. **Company value:** Inspect whether editor assistance preserves current user text and file boundaries. **Delivery agreement:** Test through local protocol messages; editor marketplace publishing is excluded. ### Setup prerequisites - Define the supported protocol subset and configuration grammar. - Create synthetic open/change/close messages and workspace fixtures. ### Own document state Validate lifecycle and positions. #### CLSP-101 — Reject configuration edits for unopened language-server documents **Bug · Medium priority · Foundational** noCV practice brief v5 · CLSP-101 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Own document state. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 80% · API design 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A change notification for an unknown URI crashes the document map. Validate document lifecycle. 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 - Open then change fixture - Change unopened document Deliverables - Document lifecycle handler and cases Rollout and recovery: Ignore unsupported lifecycle notifications with bounded diagnostics. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CLSP-102 — Convert language-server positions using a declared encoding **Task · High priority · Intermediate** noCV practice brief v5 · CLSP-102 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Own document state. Depends on: CLSP-101. Difficulty: Intermediate. Estimated focused work: 135 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Emoji before an error shifts the underline. Add position conversion matching the negotiated encoding. Acceptance criteria - ASCII positions map correctly - Supplementary characters map correctly - Out-of-range positions are rejected Implementation constraints - Do not assume byte offsets equal editor positions. Verification - Edit after emoji - Request position beyond line end Deliverables - Position codec and Unicode cases Rollout and recovery: Advertise only the verified encoding until others are implemented. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CLSP-103 — Apply configuration document edits in the supplied version order **Bug · High priority · Advanced** noCV practice brief v5 · CLSP-103 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Own document state. Depends on: CLSP-101, CLSP-102. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Delayed changes replace newer document content. Track monotonic document versions and ordered edits. Acceptance criteria - New valid version applies - Old version cannot overwrite - Invalid range leaves prior snapshot intact Implementation constraints - Apply one notification atomically to a cloned snapshot. Verification - Apply ordered incremental edits - Send stale version and invalid range Deliverables - Versioned document store Rollout and recovery: Request full resynchronization after rejected inconsistent edits. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Provide scoped assistance Return current diagnostics and bounded edits. #### CLSP-104 — Publish configuration diagnostics for the checked document version **Story · Medium priority · Intermediate** noCV practice brief v5 · CLSP-104 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Provide scoped assistance. Depends on: CLSP-103. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Parser results are published after users type more text. Bind diagnostics to the source snapshot checked. Acceptance criteria - Current results publish - Superseded results drop - Closed documents clear diagnostics Implementation constraints - Snapshot identity includes URI and version. Verification - Check unchanged document - Close or edit before check completes Deliverables - Diagnostic publication guard Rollout and recovery: Disable background checking and use explicit validation temporarily. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CLSP-105 — Complete configuration keys only within valid assignment contexts **Story · Medium priority · Advanced** noCV practice brief v5 · CLSP-105 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Provide scoped assistance. Depends on: CLSP-102, CLSP-103. Difficulty: Advanced. Estimated focused work: 165 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Completion suggests keys inside string literals and comments. Restrict suggestions using syntax context. 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 - Complete incomplete key - Request completion inside quoted value Deliverables - Context completion and cases Rollout and recovery: Return no suggestions when context cannot be determined. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CLSP-106 — Return configuration rename edits only for resolved local bindings **Task · High priority · Expert** noCV practice brief v5 · CLSP-106 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Provide scoped assistance. Depends on: CLSP-103, CLSP-105. Difficulty: Expert. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Rename replaces matching text inside comments and unrelated scopes. Resolve the selected symbol before creating edits. Acceptance criteria - Bound references rename - Shadowed symbols stay unchanged - Unresolved selection yields no edit Implementation constraints - This ticket supports one document only. Verification - Rename binding and references - Select comment text or shadowed name Deliverables - Symbol rename and isolation cases Rollout and recovery: Disable rename if symbol resolution is ambiguous. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CLSP-107 — Attach expected document versions to configuration code actions **Bug · High priority · Advanced** noCV practice brief v5 · CLSP-107 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Provide scoped assistance. Depends on: CLSP-104, CLSP-106. Difficulty: Advanced. Estimated focused work: 165 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 70% · API design 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Applying an old quick fix corrupts newer text. Include the snapshot version in the edit contract. 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 - 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. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Handle client interruption Cancel stale work and recover protocol errors. #### CLSP-108 — Cancel language-server requests without leaking pending work **Chore · Medium priority · Intermediate** noCV practice brief v5 · CLSP-108 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle client interruption. Depends on: CLSP-104, CLSP-107. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 60% · Performance engineering 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Repeated completion cancellation leaves tasks in memory. Add request-scoped cleanup for all terminal paths. Acceptance criteria - Success removes pending entry - Cancellation removes entry - Late result does not emit another response Implementation constraints - Request IDs may be reused only per protocol rules. Verification - Complete request - Cancel then deliver late result Deliverables - Request registry and cleanup tests Rollout and recovery: Limit concurrency if cleanup cannot be guaranteed. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CLSP-109 — Handle malformed language-server messages without losing healthy documents **Bug · High priority · Advanced** noCV practice brief v5 · CLSP-109 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle client interruption. Depends on: CLSP-101, CLSP-108. Difficulty: Advanced. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 60% · Security 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A malformed request resets the whole server and loses open buffers. Isolate parsing and protocol failures. Acceptance criteria - Invalid message gets bounded error - Healthy documents remain intact - Transport stays usable when framing permits Implementation constraints - Never log full document contents on parse failure. Verification - Send valid request after malformed one - Send oversized message Deliverables - Protocol error boundary and cases Rollout and recovery: Close only the offending transport when framing is unrecoverable. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### CLSP-110 — Create a reproducible configuration language-server transcript harness **Chore · Low priority · Intermediate** noCV practice brief v5 · CLSP-110 · A focused language server for configuration editing Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Handle client interruption. Depends on: CLSP-107, CLSP-109. Difficulty: Intermediate. Estimated focused work: 135 minutes; setup and prerequisite tickets are additional. Estimated field mix: Quality engineering 60% · Compiler and language tooling 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Editor reports are difficult to replay. Record synthetic protocol transcripts with deterministic response assertions. Acceptance criteria - Harness replays open/edit/action/close - Versions and request IDs are explicit - Fixture text is synthetic Implementation constraints - Recorded transcripts are public regression cases, not hidden grading answers. Verification - Replay successful rename - Replay stale action rejection Deliverables - Transcript runner and fixtures Rollout and recovery: Retain prior passing transcripts when behavior changes intentionally. Project prerequisites: Define the supported protocol subset and configuration grammar. Create synthetic open/change/close messages and workspace fixtures. Engineer value: Practice protocol ordering and document-safe editing. Company value: Inspect whether editor assistance preserves current user text and file boundaries. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence.