# 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. ## CMIGR — A safe source migration for a deprecated configuration API Fictional package Laurel replaces configure(name, options) with configure({name, options}). Build synthetic TypeScript-like AST fixtures or use the repository's installed parser; source is analyzed, never executed. **Field:** Compiler and language tooling. **Suggested stack:** TypeScript, AST adapter, Filesystem adapter, Vitest. **Engineer value:** Practice conservative automated refactoring and reviewable uncertainty. **Company value:** Inspect whether migration automation reduces repetitive work without silent semantic changes. **Delivery agreement:** Only the declared API migration is covered; ambiguous cases must remain manual. ### Setup prerequisites - Create synthetic supported and ambiguous call-site fixtures. - Define the exact old/new API contract and a dedicated output directory. ### Find eligible calls Resolve syntax and binding identity. #### CMIGR-101 — Identify deprecated configuration imports by resolved binding **Task · Medium priority · Foundational** noCV practice brief v5 · CMIGR-101 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Find eligible calls. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 90 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. Text search matches unrelated local functions named configure. Discover calls through the imported binding. Acceptance criteria - Imported binding matches - Aliased import matches - Unrelated local name does not match Implementation constraints - Scope is the declared module identifier only. Verification - Find direct and aliased import - Use unrelated local configure Deliverables - Call-site discovery and cases Rollout and recovery: Report candidates without editing if resolution is uncertain. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. #### CMIGR-102 — Exclude comments and string literals from configuration migration candidates **Bug · Medium priority · Foundational** noCV practice brief v5 · CMIGR-102 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Find eligible calls. Depends on: CMIGR-101. Difficulty: Foundational. Estimated focused work: 75 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. A prototype replaces examples inside strings and comments. Use syntax node kinds for candidate selection. Acceptance criteria - Executable call nodes alone qualify - Comment text remains unchanged - String contents remain unchanged Implementation constraints - Source analysis does not execute expressions. Verification - Find real call - Include matching text in comment and string Deliverables - Syntax filter and fixtures Rollout and recovery: Disable text-based fallback entirely. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. #### CMIGR-103 — Report ambiguous configuration calls for manual review **Story · Medium priority · Intermediate** noCV practice brief v5 · CMIGR-103 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Find eligible calls. Depends on: CMIGR-101, CMIGR-102. 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. Spread arguments and reassigned bindings make transformation unsafe. Return explicit skipped reasons. Acceptance criteria - Supported two-argument calls qualify - Spread or reassigned cases skip - Skipped locations are listed Implementation constraints - Do not invent argument meaning from names. Verification - Classify supported call - Classify spread and reassignment Deliverables - Eligibility report and cases Rollout and recovery: Keep ambiguous files unchanged. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. ### Produce conservative edits Preserve comments and reject ambiguity. #### CMIGR-104 — Transform the supported configuration call shape without reordering evaluation **Task · High priority · Advanced** noCV practice brief v5 · CMIGR-104 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Produce conservative edits. Depends on: CMIGR-103. 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. Wrapping arguments into an object could reorder side-effecting expressions. Preserve the old left-to-right evaluation order. Acceptance criteria - Name expression remains first - Options remains second - No expression duplicates or disappears Implementation constraints - Verify syntax structure without executing candidate expressions. Verification - Transform ordinary expressions - Use synthetic call expressions in both positions Deliverables - Transformation and AST-order checks Rollout and recovery: Revert transformed files if evaluation order cannot be preserved. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. #### CMIGR-105 — Preserve configuration-call comments during transformation **Bug · Medium priority · Advanced** noCV practice brief v5 · CMIGR-105 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Produce conservative edits. Depends on: CMIGR-104. 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. Comments between arguments vanish in generated output. Attach trivia using a documented preservation rule. Acceptance criteria - Leading and trailing comments survive - Argument comments remain near their expression - Unrepresentable trivia causes skip Implementation constraints - Do not silently relocate a directive comment. Verification - Transform commented call - Use directive-like ambiguous comment Deliverables - Trivia-preserving transform and cases Rollout and recovery: Leave affected call unchanged with a review reason. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. #### CMIGR-106 — Make the configuration migration idempotent **Task · Medium priority · Intermediate** noCV practice brief v5 · CMIGR-106 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Produce conservative edits. Depends on: CMIGR-104, CMIGR-105. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Compiler and language tooling 80% · Developer tooling 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. Running the migration twice wraps an already migrated call again. Recognize new syntax and preserve it. Acceptance criteria - Second run produces no diff - Mixed old/new files transform eligible old calls - Unrelated object arguments remain unchanged Implementation constraints - Idempotence is checked on printed source as well as AST. Verification - Run twice on migrated fixture - Run on mixed file Deliverables - Idempotency cases and migration guard Rollout and recovery: Stop repeated application if the second run changes output. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. #### CMIGR-107 — Reject overlapping configuration source edits before writing **Bug · High priority · Expert** noCV practice brief v5 · CMIGR-107 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Produce conservative edits. Depends on: CMIGR-104, CMIGR-106. 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. Nested eligible calls produce overlapping text edits and corrupt files. Plan edits with deterministic nesting handling. Acceptance criteria - Edits do not overlap - Nested calls follow documented policy - Ambiguous overlap skips file safely Implementation constraints - Prefer one syntax-tree rewrite over blind offset patches. Verification - Transform disjoint calls - Transform nested eligible calls Deliverables - Edit planner and overlap cases Rollout and recovery: Emit preview only for files with unresolved overlaps. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. ### Apply and verify safely Make changes reviewable and recoverable. #### CMIGR-108 — Preview configuration migration changes before applying them **Story · Medium priority · Intermediate** noCV practice brief v5 · CMIGR-108 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Apply and verify safely. Depends on: CMIGR-107. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Developer tooling 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. Developers need to review the exact transformation scope. Add a dry-run diff and skipped-call summary. Acceptance criteria - Preview writes no source files - Diff reflects proposed bytes - Skipped reasons include locations Implementation constraints - Default command mode should be explicit in usage. Verification - Preview supported fixture - Preview ambiguous file and compare unchanged bytes Deliverables - Dry-run report and immutability check Rollout and recovery: Disable apply mode if preview differs from actual output. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. #### CMIGR-109 — Apply configuration migration files with stale-input protection **Task · High priority · Advanced** noCV practice brief v5 · CMIGR-109 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Apply and verify safely. Depends on: CMIGR-108. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Developer tooling 50% · Compiler and language tooling 30% · Storage systems 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 developer edits a file after preview and apply overwrites it. Compare the original digest before replacement. Acceptance criteria - Matching source applies - Changed source is rejected - Failed replacement preserves recoverable original Implementation constraints - Restrict writes to the explicit fixture root. Verification - Apply unchanged preview - Modify file before apply Deliverables - Guarded writer and failure cases Rollout and recovery: Restore preserved original only after checking target identity. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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. #### CMIGR-110 — Summarize configuration migration outcomes without claiming full compatibility **Chore · Low priority · Intermediate** noCV practice brief v5 · CMIGR-110 · A safe source migration for a deprecated configuration API Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Apply and verify safely. Depends on: CMIGR-109. Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional. Estimated field mix: Developer tooling 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. A green migration summary implies the whole package is compatible despite skipped sites. Report exact supported outcomes. Acceptance criteria - Counts distinguish changed unchanged and skipped - Follow-up checks are listed - No semantic proof is asserted beyond tested contract Implementation constraints - Run parser/type checks available in the fixture harness. Verification - Summarize complete supported fixture - Summarize mixed skipped case Deliverables - Migration report and verification record Rollout and recovery: Mark migration incomplete when required checks fail. Project prerequisites: Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Engineer value: Practice conservative automated refactoring and reviewable uncertainty. Company value: Inspect whether migration automation reduces repetitive work without silent semantic changes. 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.