Task library CMIGR Compiler and language tooling · Phased project 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.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 23h 30m + setup
Suggested stack TypeScript · AST adapter · Filesystem adapter · Vitest Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with CMIGR-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice conservative automated refactoring and reviewable uncertainty.
What the team gains Inspect whether migration automation reduces repetitive work without silent semantic changes.
Before you start Create synthetic supported and ambiguous call-site fixtures. Define the exact old/new API contract and a dedicated output directory. Delivery agreement Only the declared API migration is covered; ambiguous cases must remain manual.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Resolve syntax and binding identity.
PHASE 2 Preserve comments and reject ambiguity.
PHASE 3 Make changes reviewable and recoverable.
Find eligible calls Resolve syntax and binding identity.
CMIGR-101 Entry ticket; project setup still required Estimated field mix
Compiler and language tooling 100% CMIGR-102 Depends on CMIGR-101 Estimated field mix
Compiler and language tooling 100% CMIGR-103 Depends on CMIGR-101, CMIGR-102 Estimated field mix
Compiler and language tooling 100% Apply and verify safely Make changes reviewable and recoverable.
CMIGR-108 Depends on CMIGR-107 Estimated field mix
Developer tooling 60% Compiler and language tooling 40% CMIGR-109 Depends on CMIGR-108 Estimated field mix
Developer tooling 50% Compiler and language tooling 30% Storage systems 20% CMIGR-110 Depends on CMIGR-109 Estimated field mix
Developer tooling 60% Compiler and language tooling 40% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.