improvement(repo): consolidation of boundary helpers + better unknown usage

[icecrasher321]

• Tighten z.unknown() wherever possible
• Add CI checks
• Consolidate helper pattern

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Apr 30, 2026 3:23am

[cursor]

PR Summary

Medium Risk
Touches many API endpoints’ request parsing and validation/error responses; behavior should be equivalent but could subtly change 400 handling or JSON parse failures across auth/billing/copilot routes.

Overview
Standardizes API route boundary validation by migrating many handlers from ad-hoc request.json() + safeParse/validateSchema/try-catch patterns to contract-bound parseRequest(...) with explicit context handling and per-route overrides for validation and invalid-JSON responses.

Updates boundary-policy docs (AGENTS.md, CLAUDE.md, .cursor/rules) to reflect parseRequest’s discriminated-union return and adds two new strict-mode annotation types (boundary-raw-json, untyped-response). Several routes also switch client/landing schemas (contact + demo request) to shared contract modules, tweak tests/mocks to use NextRequest/nextUrl, and harden workflow-checkpoint state cleanup by typing/narrowing unknown JSON before reconstruction.

^{Reviewed by Cursor Bugbot for commit e37e9f2. Configure here.}

[icecrasher321]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit e37e9f2. Configure here.}