Command not found / wrong version
Run Get-Command/which and version output. Confirm fresh terminal PATH before reinstalling anything.
Start from the exact symptom. The first question is not “what fix should I paste?” but “which layer can actually produce this symptom?”
Run Get-Command/which and version output. Confirm fresh terminal PATH before reinstalling anything.
Find the listening PID, identify the process, then stop or reconfigure the correct service.
Check the actual browser Origin, API allow-list, credentials mode, preflight response, and whether the request reaches the API.
Verify Authorization/cookie presence, token format, expiry, issuer/project, and server-side verification.
Identity is usually known; inspect resource membership/role/permission evidence and policy decision.
First prove route/method; then verify resource lookup and whether authorization intentionally masks existence.
Check host/port/DNS, connection mode/pooler, credentials, firewall/service status, then retry a minimal connection.
Compare migration history, target database state, and branch changes. Do not delete migrations casually in shared environments.
Inspect query key, staleTime, mutation invalidation/update, filter params, and whether data was copied into local state.
Inspect snapshot/rollback, server response, invalidation timing, temporary IDs, and concurrent mutation ordering.
Read docker logs, inspect command/entrypoint/env, and run the process interactively if safe.
Compare Node/pnpm versions, frozen lockfile, workspace scripts, environment/secrets, OS assumptions, and path case sensitivity.
Check DNS/TLS, configured origins/redirect URLs, public API base URL, CORS, and environment selection.