reviewlisted

# Code review Review $ARGUMENTS, or the working diff if nothing was given (`git diff` for uncommitted, `git diff <base>...HEAD` for a branch). Read `.claude/project-profile.md` first for the stack, conventions and quality bar. Say so if it is missing and review on general principles instead, noting that convention findings will be weaker. ## Scope **Review the diff, not the repository.** Pre-existing problems in untouched code are out of scope, except where the diff makes one materially worse. If you find something serious outside the diff, note it in one line at the end under `pre-existing`, and do not let it crowd out the actual review. ## What to look for ### Security - Secrets, keys, tokens or infrastructure identifiers committed in code or config. - Untrusted input reaching a sink: HTML injection into the DOM, SQL built by string concatenation, shell commands built from user input, path traversal in file operations. - Authorization checked on the server, not only hidden in the UI. A gate enforced only in the client is not a gate, and the network tab is right there. - Row-level or record-level access rules present for any new table or column. - Privileged credentials used only server-side, never shipped to the client bundle. - Responses that return more fields than the caller needs, especially anything personal. ### Correctness This is where real bugs live, and it deserves more attention than style. - Unhandled promise rejections and swallowed errors. - Off-