Bring one setting back to a single place
One setting defined in three places with three different defaults, reduced to a single source.
The ticket
Consolidate a setting defined in several places into one source of truth.
Acceptance criteria
- One definition remains and every caller reads it
- Differences between the copies are reconciled explicitly
- Resolution order is tested
- The removed definitions are listed in the description
What lands as proof
Tests on the resolution order, which is where consolidated configuration usually goes wrong.
Why teams defer it
- Each copy was added because the first one was not reachable from where it was needed.
- The copies have different defaults, and picking one changes behaviour somewhere.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: consolidate a setting defined in several places into one source of truth. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means one source of truth, callers migrated, tests on the resolution, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- The run stops once the plan is written. Somebody reads the approach and approves it before any code exists, which is the cheapest moment to redirect the work.