Report ambiguous configuration calls for manual review
Spread arguments and reassigned bindings make transformation unsafe. Return explicit skipped reasons.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Program analysis · Uncertainty
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 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.
Setup prerequisites
- Create synthetic supported and ambiguous call-site fixtures.
- Define the exact old/new API contract and a dedicated output directory.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
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 to include
- Classify supported call
- Classify spread and reassignment
Deliverables
- Eligibility report and cases
Rollout and recovery
Keep ambiguous files unchanged.
Value of the work
For the engineer: Practice conservative automated refactoring and reviewable uncertainty.
For the team: Inspect whether migration automation reduces repetitive work without silent semantic changes.
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.