Code Quality Review

Review the current branch diff for structural quality. Preserve behavior, but actively look for a simpler design that deletes concepts, branches, wrappers, or layers instead of moving complexity around.

Review Boundaries

• Review only the changed code and the surrounding code needed to judge it.
• Treat repository conventions and existing canonical helpers as the source of truth.
• Skip formatter and linter findings that automation already reports.
• Prefer a small set of high-confidence structural findings over cosmetic notes.
• Do not propose a large refactor unless its benefit is clear and it stays within the change's ownership boundary.

Review Criteria

Check each meaningful change for: