code-reviewlisted

# Code Review ## Purpose Perform structured code review focused on: - correctness - architecture - regression risks - security and performance issues --- ## Constraints - Apply @rules/php/core-standards.mdc - Apply @rules/api/general.mdc — when the diff adds or modifies an HTTP API surface (routes, controllers / `__invoke` request handlers, API Resources / DTOs serialized into responses, FormRequests, status-code / `response()` / `abort()` calls, `Idempotency-Key` handling), walk it against the API contract pillars. The dedicated walk lives in `@skills/api-review/SKILL.md` (Specialized Reviews → Always run); severities follow that rule's CR Severity Rules section. - Apply @rules/code-review/general.mdc - Apply @rules/refactoring/general.mdc — use the shared refactoring definition when assessing refactoring changes or when proposing refactoring; reject big-bang rewrites and prefer incremental migration. - Apply @rules/php/dependency-selection.mdc — when the PR diff adds a new `require` / `require-dev` entry to `composer.json`, walk the Activity + Compatibility gates from that rule against the PR description / commit body. A missing selection note is a **Critical** finding; an adopted archived / abandoned / branch-pinned package is a **Critical** finding on the spot; a single-maintainer adoption without bus-factor flag is a **Moderate** finding. - If the current project uses Laravel, also apply `@rules/laravel/laravel.mdc`, `@rules/laravel/architecture.mdc`, `@rules/laravel/