Frontend Change Review

Review only unless the user separately authorizes fixes. Do not post comments or change pull-request state.

Review flow

1. Establish the base, changed lines, intended user outcome, owning application, and affected routes or states.
2. Read repository instructions and trace imports to the actual client, component, hook, primitive, endpoint, mock, and test definitions.
3. Trace changed data from input and identity through request, decoding, cache, state, rendering, interaction, and error recovery.
4. Compare with the same application's current patterns. Do not transplant another application's similarly named API or component contract.
5. Exclude untouched debt, style preferences, and hypothetical failures. Report only reachable regressions introduced, worsened, or materially touched by the diff with confidence of at least 80/100.
6. Anchor each finding to a changed location and provide mechanism, evidence, smallest safe direction, and exact validation.

Use evidence in this order: changed code and full rendered or data call chain, protecting tests, repository instructions, then other documentation.

Select references