Add the second theme to components that only ever had one
Components that assume one theme, corrected so both render from the same tokens.
The ticket
Make one component render correctly in both themes.
Acceptance criteria
- Both themes are captured in the browser check
- Colours come from tokens rather than theme-specific overrides
- Contrast passes in both themes
- No colour is defined only inside a theme block
What lands as proof
Captures of both themes, which is the only way to catch a colour that was defined for one and inherited by the other.
Why teams defer it
- Everybody develops in one theme, so the other is only seen by users who prefer it.
- A colour defined inside a theme block looks correct until the other theme inherits nothing.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: make one component render correctly in both themes. 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 both themes captured in the browser check, 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.