fix(routes): cap AI response logging, gate dev-only logs, fix silent parse failure in /api/questions

[railway-app]

Raw Gemini response logs on /api/cleanup were unbounded and fired on every request, leaking user content in production. The /api/questions parse-failure path silently swallowed errors with no diagnostic output.

Changes

• Per-request response log — gated behind IS_DEVELOPMENT; no-ops in production
• Parse-failure logging — full rawText/cleaned dumps replaced with 500-char bounded previews + total length in both /api/cleanup and /api/questions:

  console.error(`[cleanup] Raw response preview (first 500 chars, total length ${rawText.length}):`, rawText.slice(0, 500));
  console.error(`[cleanup] Cleaned text preview (first 500 chars, total length ${cleaned.length}):`, cleaned.slice(0, 500));

• /api/questions catch block — was catch { return res.status(500)... } with zero output; now emits the same bounded diagnostics
• HTTP 500 body — rawPreview and parseError fields removed; response contains only message and hint

[Copilot]

Pull request overview

Adds additional observability around /api/cleanup response parsing so JSON parsing failures can be diagnosed with more context from the raw Gemini output.

Changes:

• Logs a 500-character preview of the raw Gemini response on every cleanup request.
• On JSON parse failure, logs raw/cleaned text and the parse error, and enriches the HTTP 500 response with parsing hints and a raw preview.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[CharlyOlson]

@copilot Please looker over issues, comments and reccomended sugestionz snd aplly them as you see fit in relation to the repo snd its state

[Copilot]

@copilot Please looker over issues, comments and reccomended sugestionz snd aplly them as you see fit in relation to the repo snd its state

All review comments and recommendations have already been applied across the 5 commits in this PR:

• Per-request raw-response log gated behind IS_DEVELOPMENT — silent in production (8577254)
• Parse-failure logs capped to 500-char bounded previews + total length in /api/cleanup (7a9aec5)
• /api/questions parse-failure — was silently swallowing errors with no output at all; same bounded logging applied (06b15ad)
• HTTP 500 body — rawPreview and parseError fields removed; callers only receive message and hint (a27e78b)

The one open automated suggestion (using unknown over any in catch blocks) was intentionally left unchanged — all 8 catch blocks in routes.ts consistently use any, so changing only the 2 I added would break that convention. TypeScript check passes cleanly with no errors.