#229 Send vanity redirects with Cache-Control: no-store

The router's edge 302 for every vanity alias (/will, /khaliq, /founder, /meet-with-*, /virtual-office) carries Cache-Control: no-store, the same header the Next.js /founder route handler sets. /founder picks a founder calendar at random per request, and an uncached redirect is what keeps each visit an independent draw.

The vanity redirect test asserts the header on every alias.

🤖 Generated with Claude Code

---

[!NOTE]
Low Risk
Small behavioral change to redirect response headers only; no routing or destination logic changes.

Overview
Edge vanity alias redirects (/will, /khaliq, /founder, /meet-with-*, /virtual-office) no longer use Response.redirect; they return an explicit 302 with Cache-Control: no-store so intermediaries cannot cache the redirect. That matters especially for /founder, which picks between two calendar URLs at random per request—a cached 302 would lock visitors to one founder.

The vanity redirect integration test now expects cache-control: no-store on every alias in the parameterized case.

^{Reviewed by Cursor Bugbot for commit 4f4783e9840e8547afd0c65db0a3da69cfbba0e8. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

---

Summary by cubic

Sends the router's edge 302s for vanity aliases (/will, /khaliq, /founder, /meet-with-*, /virtual-office) with Cache-Control: no-store so a cached redirect never pins a visitor to one /founder calendar. The vanity redirect test now asserts the header.

---

Agent Relay sessions

• claude session 23f84d9c · opened via gh pr create · last active 2026-10-16