fix: lazy-load attachment safety (MIME filter, isLoading reset)

[siddseethepalli]

Addresses review feedback from PR #5019:

• Limit attachment data omission to video MIME types only (non-video attachments keep inline data)
• Reset isLoading and set failed on base64 decode failure in openInExternalPlayer and saveVideo
• Auth token (feat: initialize Next.js app in /web directory #1) and assistant ID routing (feat: add platform terraform for GKE deployment #2) were already fixed by PRs fix: use correct bearer token for lazy-load video fetch #5030 and fix: use local-assistant ID for /v1/ HTTP routes #5037

---

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f416b9912b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Avoid marking playback failed on save I/O errors

This catch handles both fetch failures and data.write(to: destURL) failures, so setting failed = true here can switch the attachment into the “Could not play video” state even when playback is actually fine and only the save destination failed (for example, permission denied or disk full). That regresses the user flow by turning a save-specific error into a persistent playback failure.

Useful? React with 👍 / 👎.

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[siddseethepalli]

The Codex feedback about save I/O errors setting failed = true was already addressed by PR #5058, which refactored the save flow to use a separate isSaving state. The catch block in saveVideo() no longer sets failed = true — save errors only reset isSaving, leaving playback state unaffected.