Localize one route into a new locale from the existing keys
A route localised from the keys that already exist, with a rendered capture as the check.
The ticket
Localize one route into a new locale using the existing translation keys.
Acceptance criteria
- Every string on the route resolves from a key
- The extraction report shows no untranslated literals
- The route is captured rendered in the new locale
- Text expansion does not break the layout
What lands as proof
A capture in the target locale, which is the only way to catch strings that expanded past their container.
Why teams defer it
- Translation arrives from outside the team on its own schedule, so the work is never fully in your control.
- Layout breaks from longer text are only visible once somebody actually renders it.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: localize one route into a new locale using the existing translation keys. 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 extraction report and a rendered capture of the route, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.