Audit: production-mode-only code paths in the Node adapter

[smiggleworth]

Purpose

Audit task, not a bug report — produces an inventory, doesn't fix anything.

Procedure

1. grep -rn "isDevelopmentEnvironment\|process.env.NODE_ENV\|__DEV__" src/.
2. For each, verify production behavior explicitly (especially around the static-asset serving path from Static asset routing silently shadows dynamic routes with dotted paths; duplicated content-type parsing #28 — does dev mode skip any check that prod relies on, or vice versa?).
3. File gap issues for anything unacceptable.

Definition of Done

• Table: dev-gated branch | ✅ verified acceptable / 🔗 gap filed.
• No row left unmarked.

Audit results (2026-08-24)

Dev-gated branch	Result
No matches in src/ for isDevelopmentEnvironment, process.env.NODE_ENV, or __DEV__	✅ Production and development use the same adapter paths.

The static-asset path has no environment gate; #28 is handled directly by #35.

[smiggleworth]

Completed by #35, with the shared media-type helper exposed by askrjs/askr-server#44. The full local gate and hosted Ubuntu/macOS/Windows CI passed; no package was bumped or published.