187: Interview Preparation - Final Project Hardening
Required evidence
- clean typecheck, lint, build, and test commands;
- client, API, database, and selected E2E coverage;
- accessibility and keyboard verification;
- query-plan and index notes;
- threat model and safe error review;
- deployment smoke test, logs, readiness behavior, and rollback note.
Exit rule
Fix correctness and security issues before polishing presentation. A deployable explanation must be supported by runnable evidence.
Release record
Save the exact verification commands, environment assumptions, migration status, known limitations, and rollback trigger. Verify that production logs redact credentials and request bodies. A green local build is not evidence that the deployed API can reach its database or set secure cookies correctly.
Hardening walkthrough
Run typecheck, lint, unit/integration tests, build, and selected E2E tests from a clean checkout. Exercise login, unauthorized object access, create/update/delete, empty/loading/error UI, keyboard-only navigation, and a deployment smoke test. Inspect a representative SQL query plan and record why each index exists. Verify migrations forward and rollback assumptions, readiness during startup, structured logs, secret handling, and the exact rollback signal.
Rubric and edge cases
Score 2 points each for reproducible commands, API/client coverage, accessibility, query/index evidence, threat model, safe errors/logs, deployment readiness, and rollback. Test expired sessions, malformed payloads, duplicate requests, database unavailable, migration mismatch, slow network, empty data, and a failed build. Do not pass while a high-impact authorization or secret-leak issue remains, even if presentation is polished.