feat(j0di3): Forward Idempotency-Key and X-Request-ID through proxy

[jeromehardaway]

Summary

J0dI3's mutating endpoints (submit, score, rewrite, …) accept an Idempotency-Key for safe retries and echo X-Request-ID for support correlation, but the Next.js proxy was dropping both headers on every call. This wires them through the shared dispatch() so every troop and admin route benefits without per-endpoint changes.

What changed

• src/lib/j0di3-proxy.ts — dispatch() now forwards an incoming Idempotency-Key and X-Request-ID request header to J0dI3 when present, and surfaces J0dI3's echoed X-Request-ID back on the proxied response.
• __tests__/lib/j0di3/j0di3-proxy.test.ts — added two regression tests: header forwarding alongside X-Troop-Token, and response-side X-Request-ID echo.

Test plan

• npm test — full suite, 384/384 pass (9 in the proxy file)
• npm run build — passes (the CI-gated check)
• npx biome lint on changed files — 0 errors

Notes

• This is a proxy-layer enhancement, not a new endpoint. An audit confirmed the troop-facing J0dI3 surface was already fully wired; this header passthrough was the one genuine gap.
• No new env vars, routes, Swagger annotations, or Prisma migrations.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
vets-who-code-app	Ready	Preview, Comment	Jun 10, 2026 2:55am