fix(chapter-07): add security headers and readiness checks

↗ view on GitHub · Amal · 2026-05-24 · 0a153ed6

Chapter: 07 - Deployable hardening.

Plain-English map:
Add API and frontend security headers, wire the structured request logger into
the Express app, and add a readiness endpoint that checks whether dependencies
are available.

Why it matters:
Browsers and platforms need clear signals. Security headers reduce browser-side
risk, while readiness checks tell deploy platforms when the app can actually
serve traffic.

Principle:
Defense in depth plus honest health checks.

Precedent borrowed:
Upstream PR #78 and standard container/load-balancer practice that separates
liveness from readiness.

Upstream base: willchen96/mike@d39f580.
Original local commit: 73ff97a.
Repository amal66/mike
Author Amal <mamalanand3@gmail.com>
Authored
Parents 91f95485
Stats 1 file changed , +157
Part of Security headers and readiness checks

Capture this commit into my fork

Download a Markdown prompt that tells Claude how to port this exact commit into your working tree. Run it via claude -p < capture-commit-0a153ed6.md from inside the repo you want the change in.

⬇ Download capture-commit-0a153ed6.md