fix(auth): send people to their reports, and make a dead redirect fail the build

/projects was deleted with the hosted pipeline in b3dbf0b. Five redirects to it were not:

Every person who signed in would have landed on a 404. They now go to /reports — resources/views/reports/index.stx is what an account has instead of projects.

Why nothing caught it

Each guard failed for a different reason, and each was individually reasonable:

• marketing-links reads href attributes. These are window.location.replace(...) in a script, so the exact class of bug the test exists to prevent was invisible to it. It also only looked at the marketing pages — login.stx was never in its list.
• The post-deploy check probes /, the marketing pages and the two robots files. It never signs in, and /projects is not among them.
• The live site answered 200 on every one of those paths throughout, because the running release predates the deletion. It still serves /projects today and 404s /reports.

So the first correct deploy would have broken signing in, with all three checks green while it happened.

The fixes

tests/feature/marketing-links.test.ts now reads location.replace(...) and location.href = ... alongside href, and covers login, register, forgot, reset, account and AuthGuard.

Verified by reintroducing the bug rather than by assuming: the suite fails and names /projects. Restored, 28 pass.

.github/workflows/ci.yml — the post-deploy probe gains /login, /register and /reports. 200 is a weak assertion for the last one (it renders for an anonymous caller and lets AuthGuard bounce the browser, so curl sees the shell either way), but it still catches a route that stopped being registered and a page that 500s.

Verification

Clean slate, every gitignored artifact deleted first:

test-postgres unverified locally — no Postgres on this machine.

Worth knowing before merging

A green push to main fires the production deploy, so merging this releases everything from b3dbf0b forward in one go. Two open questions that a release makes non-theoretical:

• resources/views/account.stx still calls projectsFor(user), which queries a projects table whose model was deleted. Not traced. That page is in the probe list now, so a 500 would fail the deploy rather than ship quietly.
• buddy migrate regenerates 13 drop-table migrations every run — the model snapshot still describes projects, events, reports, report_blocks, report_shares, usage_counters and seven more. Harmless in CI against a fresh database; a real data decision against production.

🤖 Generated with Claude Code