review-code-quality

# Review code quality Run a **code-quality-focused** review: naming conventions, TypeScript strictness, OXC (oxfmt/oxlint) compliance, duplication, readability, error handling patterns, testability, and type safety. Your reply must be a **plan of suggested changes**: concise, actionable, and structured-not only prose. ## Invocation Text after the slash command is additional scope/focus - narrow the review accordingly. If none given, use the default scope described below. ## Best practices alignment - **Naming** - Per root [AGENTS.md](../../../AGENTS.md): variables and functions `camelCase`; constants `CONSTANT_CASE`; constrained string set names `PascalCase`, members `CONSTANT_CASE` via `as const` objects (not `export enum`). No single-letter names except trivial loop indices; descriptive names for exports and public APIs. - **TypeScript** - Strict mode; no `any` or unsafe `as` without justification; no `@ts-ignore` without comment. Explicit return types on exported functions; inferred where trivial. Zod schemas co-located with inferred types where used. - **OXC (oxfmt / oxlint)** - Format and lint applied; no disabled rules that hide real issues; consistent style (spaces, double quotes, line width 80). - **Structure** - Single responsibility per file/function; files under ~300 lines, functions under ~50 lines where practical; clear separation (DTOs in `@repo/dtos-common`, routes, handlers, utils). - **Errors** - Hono `HTTPException` and centralized `onError` where used...