Retire translation keys, images, and assets that nothing references
Keys and files nothing points at, removed with the bundle measured either side.
The ticket
Remove translation keys, images, and other assets nothing references.
Acceptance criteria
- Each removal is confirmed unreferenced, including dynamically constructed references
- The extraction report is clean
- Bundle or asset size is recorded before and after
- Assets referenced only from content or configuration are checked
What lands as proof
A clean extraction report plus the measured size difference.
Why teams defer it
- Dynamically built keys defeat static checks, so a naive sweep deletes something live.
- Assets cost bandwidth rather than correctness, so nothing forces the cleanup.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: remove translation keys, images, and other assets nothing references. 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 bundle smaller, extraction report clean, 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.