nope

[groupthinking]

https://uvai.io/dashboard?video=https%3A%2F%2Fyoutu.be%2Fg4-3AxelI_Y%3Fsi%3DjoOcKY35C8S30K_V is still failing @claude @copilot

[github-actions]

👋 Thanks for opening this issue! It has been automatically labeled for triage.

[groupthinking]

@CodeRabbit

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
gh issue view 159 --repo groupthinking/EventRelay --json title,body,labels,assignees,comments

Length of output: 1173

---

🏁 Script executed:

#!/bin/bash
# Search for video URL handling or YouTube-related code
rg -rn "youtube\|youtu\.be\|video" --type=elixir -l 2>/dev/null | head -20
rg -rn "youtube\|youtu\.be\|video" --type=js -l 2>/dev/null | head -20
rg -rn "youtube\|youtu\.be\|video" -l 2>/dev/null | head -20

# Search for URL parsing related to the dashboard video parameter
rg -rn "video" --type=elixir -C3 2>/dev/null | head -60

# Check for any URL utility files
fd -e ex -e exs . | xargs grep -l "video\|youtube\|youtu" 2>/dev/null | head -20

Length of output: 0

---

🏁 Script executed:

#!/bin/bash
# Get overall project structure
tree -L 3 --dirsfirst 2>/dev/null | head -80

# Look for URL-related utilities
rg -rn "url\|URL" --type=elixir -l 2>/dev/null | head -20

# Look at any LiveView or controller files that might handle the dashboard
fd -e ex -e exs -e js -e ts -e vue -e svelte . | head -50

# Check for any config or router files
fd "router" -e ex -e exs 2>/dev/null | head -5
fd "endpoint" -e ex -e exs 2>/dev/null | head -5

Length of output: 4565

---

🏁 Script executed:

#!/bin/bash
cat apps/web/src/lib/youtube-metadata.ts
echo "---"
cat apps/web/src/app/api/video/route.ts
echo "---"
cat apps/web/src/app/api/dashboard/route.ts
echo "---"
cat apps/web/src/lib/services/video-service.ts
echo "---"
cat apps/web/src/store/dashboard-store.ts

Length of output: 36436

---

🏁 Script executed:

#!/bin/bash
# Find the dashboard page component
fd "page" apps/web/src --type f | head -20
fd "dashboard" apps/web/src --type f | head -20

# Read the dashboard page
cat apps/web/src/app/dashboard/page.tsx 2>/dev/null || \
cat apps/web/src/app/page.tsx 2>/dev/null || \
cat apps/web/src/pages/dashboard.tsx 2>/dev/null

# Check for any component that reads the `video` query param
rg -rn "searchParams\|useSearchParams\|video.*query\|query.*video" apps/web/src/ -C3 | head -60

Length of output: 31925

---

@groupthinking, I've gone through the code and found two issues that would cause this URL to fail.

---

🐛 Bug 1: useEffect re-triggers on every store update (primary suspect)

In apps/web/src/app/dashboard/page.tsx, the useEffect that auto-processes the ?video= param depends on the searchParams object, not on its string value:

// ❌ Current — searchParams object reference can change on every re-render
useEffect(() => {
  const video = searchParams.get('video');
  if (video) {
    setVideoUrl(video);
    processVideo(video);
  }
}, [searchParams, processVideo]);

In the Next.js App Router, useSearchParams() can return a new URLSearchParams instance on each render — including renders triggered by store state changes inside processVideo itself (progress updates, activity log entries, etc.). This creates a re-trigger loop:

processVideo() → store update → re-render → new searchParams reference → effect re-fires → processVideo() again → ...

Each iteration adds a new video entry and race-conditions with the previous one, causing both to fail.

Fix:

// ✅ Use the string value as the dependency, not the object
const videoParam = searchParams.get('video');

useEffect(() => {
  if (videoParam) {
    setVideoUrl(videoParam);
    processVideo(videoParam);
  }
}, [videoParam, processVideo]);

---

🐛 Bug 2: Silent failure when all strategies are exhausted

In apps/web/src/app/api/video/route.ts, if BACKEND_AVAILABLE is false (e.g., Vercel deployment with no Python backend) and GEMINI_API_KEY is not set, the entire pipeline falls through to the transcript chain, which also fails silently. The final response is:

{
  "status": "failed",
  "result": {
    "errors": ["All strategies failed — ensure GEMINI_API_KEY is set"]
  }
}

The dashboard store in processVideo treats this as a non-throwing result but marks the video as failed with no visible explanation to the user beyond the activity log. There's no user-facing error shown on the dashboard.

Quick check: Is GEMINI_API_KEY set in the Vercel environment for uvai.io? That's the most likely environmental cause if the code fix above doesn't fully resolve it.

---

Summary of fixes needed

Location	Issue	Fix
apps/web/src/app/dashboard/page.tsx	useEffect depends on searchParams object, not string	Change dependency to searchParams.get('video') string
Vercel env vars	GEMINI_API_KEY possibly missing	Ensure GEMINI_API_KEY is set in production

Want me to open a PR with the useEffect fix?

[groupthinking]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
gh issue view 159 --repo groupthinking/EventRelay --json title,body,labels,assignees,comments

Length of output: 1173

---

🏁 Script executed:

#!/bin/bash
# Search for video URL handling or YouTube-related code
rg -rn "youtube\|youtu\.be\|video" --type=elixir -l 2>/dev/null | head -20
rg -rn "youtube\|youtu\.be\|video" --type=js -l 2>/dev/null | head -20
rg -rn "youtube\|youtu\.be\|video" -l 2>/dev/null | head -20

# Search for URL parsing related to the dashboard video parameter
rg -rn "video" --type=elixir -C3 2>/dev/null | head -60

# Check for any URL utility files
fd -e ex -e exs . | xargs grep -l "video\|youtube\|youtu" 2>/dev/null | head -20

Length of output: 0

---

🏁 Script executed:

#!/bin/bash
# Get overall project structure
tree -L 3 --dirsfirst 2>/dev/null | head -80

# Look for URL-related utilities
rg -rn "url\|URL" --type=elixir -l 2>/dev/null | head -20

# Look at any LiveView or controller files that might handle the dashboard
fd -e ex -e exs -e js -e ts -e vue -e svelte . | head -50

# Check for any config or router files
fd "router" -e ex -e exs 2>/dev/null | head -5
fd "endpoint" -e ex -e exs 2>/dev/null | head -5

Length of output: 4565

---

🏁 Script executed:

#!/bin/bash
cat apps/web/src/lib/youtube-metadata.ts
echo "---"
cat apps/web/src/app/api/video/route.ts
echo "---"
cat apps/web/src/app/api/dashboard/route.ts
echo "---"
cat apps/web/src/lib/services/video-service.ts
echo "---"
cat apps/web/src/store/dashboard-store.ts

Length of output: 36436

---

🏁 Script executed:

#!/bin/bash
# Find the dashboard page component
fd "page" apps/web/src --type f | head -20
fd "dashboard" apps/web/src --type f | head -20

# Read the dashboard page
cat apps/web/src/app/dashboard/page.tsx 2>/dev/null || \
cat apps/web/src/app/page.tsx 2>/dev/null || \
cat apps/web/src/pages/dashboard.tsx 2>/dev/null

# Check for any component that reads the `video` query param
rg -rn "searchParams\|useSearchParams\|video.*query\|query.*video" apps/web/src/ -C3 | head -60

Length of output: 31925

---

@groupthinking, I've gone through the code and found two issues that would cause this URL to fail.

---

🐛 Bug 1: useEffect re-triggers on every store update (primary suspect)

In apps/web/src/app/dashboard/page.tsx, the useEffect that auto-processes the ?video= param depends on the searchParams object, not on its string value:

// ❌ Current — searchParams object reference can change on every re-render
useEffect(() => {
  const video = searchParams.get('video');
  if (video) {
    setVideoUrl(video);
    processVideo(video);
  }
}, [searchParams, processVideo]);

In the Next.js App Router, useSearchParams() can return a new URLSearchParams instance on each render — including renders triggered by store state changes inside processVideo itself (progress updates, activity log entries, etc.). This creates a re-trigger loop:

processVideo() → store update → re-render → new searchParams reference → effect re-fires → processVideo() again → ...

Each iteration adds a new video entry and race-conditions with the previous one, causing both to fail.

Fix:

// ✅ Use the string value as the dependency, not the object
const videoParam = searchParams.get('video');

useEffect(() => {
  if (videoParam) {
    setVideoUrl(videoParam);
    processVideo(videoParam);
  }
}, [videoParam, processVideo]);

---

🐛 Bug 2: Silent failure when all strategies are exhausted

In apps/web/src/app/api/video/route.ts, if BACKEND_AVAILABLE is false (e.g., Vercel deployment with no Python backend) and GEMINI_API_KEY is not set, the entire pipeline falls through to the transcript chain, which also fails silently. The final response is:

{
  "status": "failed",
  "result": {
    "errors": ["All strategies failed — ensure GEMINI_API_KEY is set"]
  }
}

The dashboard store in processVideo treats this as a non-throwing result but marks the video as failed with no visible explanation to the user beyond the activity log. There's no user-facing error shown on the dashboard.

Quick check: Is GEMINI_API_KEY set in the Vercel environment for uvai.io? That's the most likely environmental cause if the code fix above doesn't fully resolve it.

---

Summary of fixes needed

Location	Issue	Fix
apps/web/src/app/dashboard/page.tsx	useEffect depends on searchParams object, not string	Change dependency to searchParams.get('video') string
Vercel env vars	GEMINI_API_KEY possibly missing	Ensure GEMINI_API_KEY is set in production

Want me to open a PR with the useEffect fix?

[groupthinking]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
gh issue view 159 --repo groupthinking/EventRelay --json title,body,labels,assignees,comments

Length of output: 1173

---

🏁 Script executed:

#!/bin/bash
# Search for video URL handling or YouTube-related code
rg -rn "youtube\|youtu\.be\|video" --type=elixir -l 2>/dev/null | head -20
rg -rn "youtube\|youtu\.be\|video" --type=js -l 2>/dev/null | head -20
rg -rn "youtube\|youtu\.be\|video" -l 2>/dev/null | head -20

# Search for URL parsing related to the dashboard video parameter
rg -rn "video" --type=elixir -C3 2>/dev/null | head -60

# Check for any URL utility files
fd -e ex -e exs . | xargs grep -l "video\|youtube\|youtu" 2>/dev/null | head -20

Length of output: 0

---

🏁 Script executed:

#!/bin/bash
# Get overall project structure
tree -L 3 --dirsfirst 2>/dev/null | head -80

# Look for URL-related utilities
rg -rn "url\|URL" --type=elixir -l 2>/dev/null | head -20

# Look at any LiveView or controller files that might handle the dashboard
fd -e ex -e exs -e js -e ts -e vue -e svelte . | head -50

# Check for any config or router files
fd "router" -e ex -e exs 2>/dev/null | head -5
fd "endpoint" -e ex -e exs 2>/dev/null | head -5

Length of output: 4565

---

🏁 Script executed:

#!/bin/bash
cat apps/web/src/lib/youtube-metadata.ts
echo "---"
cat apps/web/src/app/api/video/route.ts
echo "---"
cat apps/web/src/app/api/dashboard/route.ts
echo "---"
cat apps/web/src/lib/services/video-service.ts
echo "---"
cat apps/web/src/store/dashboard-store.ts

Length of output: 36436

---

🏁 Script executed:

#!/bin/bash
# Find the dashboard page component
fd "page" apps/web/src --type f | head -20
fd "dashboard" apps/web/src --type f | head -20

# Read the dashboard page
cat apps/web/src/app/dashboard/page.tsx 2>/dev/null || \
cat apps/web/src/app/page.tsx 2>/dev/null || \
cat apps/web/src/pages/dashboard.tsx 2>/dev/null

# Check for any component that reads the `video` query param
rg -rn "searchParams\|useSearchParams\|video.*query\|query.*video" apps/web/src/ -C3 | head -60

Length of output: 31925

---

@groupthinking, I've gone through the code and found two issues that would cause this URL to fail.

---

🐛 Bug 1: useEffect re-triggers on every store update (primary suspect)

In apps/web/src/app/dashboard/page.tsx, the useEffect that auto-processes the ?video= param depends on the searchParams object, not on its string value:

// ❌ Current — searchParams object reference can change on every re-render
useEffect(() => {
  const video = searchParams.get('video');
  if (video) {
    setVideoUrl(video);
    processVideo(video);
  }
}, [searchParams, processVideo]);

In the Next.js App Router, useSearchParams() can return a new URLSearchParams instance on each render — including renders triggered by store state changes inside processVideo itself (progress updates, activity log entries, etc.). This creates a re-trigger loop:

processVideo() → store update → re-render → new searchParams reference → effect re-fires → processVideo() again → ...

Each iteration adds a new video entry and race-conditions with the previous one, causing both to fail.

Fix:

// ✅ Use the string value as the dependency, not the object
const videoParam = searchParams.get('video');

useEffect(() => {
  if (videoParam) {
    setVideoUrl(videoParam);
    processVideo(videoParam);
  }
}, [videoParam, processVideo]);

---

🐛 Bug 2: Silent failure when all strategies are exhausted

In apps/web/src/app/api/video/route.ts, if BACKEND_AVAILABLE is false (e.g., Vercel deployment with no Python backend) and GEMINI_API_KEY is not set, the entire pipeline falls through to the transcript chain, which also fails silently. The final response is:

{
  "status": "failed",
  "result": {
    "errors": ["All strategies failed — ensure GEMINI_API_KEY is set"]
  }
}

The dashboard store in processVideo treats this as a non-throwing result but marks the video as failed with no visible explanation to the user beyond the activity log. There's no user-facing error shown on the dashboard.

Quick check: Is GEMINI_API_KEY set in the Vercel environment for uvai.io? That's the most likely environmental cause if the code fix above doesn't fully resolve it.

---

Summary of fixes needed

Location	Issue	Fix
apps/web/src/app/dashboard/page.tsx	useEffect depends on searchParams object, not string	Change dependency to searchParams.get('video') string
Vercel env vars	GEMINI_API_KEY possibly missing	Ensure GEMINI_API_KEY is set in production

Want me to open a PR with the useEffect fix?

@claude Verify that this aligns with your current versioning
@coderabbitai watch for Claude's response to inform your next step

[groupthinking]

Act on @coderabbitai plan

[coderabbitai]

Coding Plan

Summary

• Normalize YouTube URLs to canonical watch?v=ID format at the dashboard store entry point, eliminating si tracking parameters and short URL variations before any API calls
• Fix the broken regex in the Gemini analyzer that only handles ?v= format, causing silent failures for youtu.be short links
• Add defensive normalization in API routes as a safety net for direct API access
• Improve error surfacing when Gemini returns empty results to prevent silent failures

Implementation Steps

Phase 1: Create URL Normalization Utility

Add a reusable utility function that converts any YouTube URL format to a canonical https://www.youtube.com/watch?v={ID} URL, stripping tracking parameters like si.

Add normalizeYouTubeUrl Function

Extend the existing video ID extraction in youtube-metadata.ts with a normalization function that returns a clean canonical URL.

• Add normalizeYouTubeUrl(url: string): string | null function to apps/web/src/lib/youtube-metadata.ts
• Leverage the existing extractVideoId() function (lines 21-33) which already correctly handles youtu.be/ID?si=X format via the pattern /(?:youtu\.be\/)([a-zA-Z0-9_-]{11})/
• Return https://www.youtube.com/watch?v=${videoId} or null if extraction fails
• Export the function for use in store and API routes

🤖 Prompt for AI agents

Add a `normalizeYouTubeUrl` utility function to
`apps/web/src/lib/youtube-metadata.ts`. This is the foundational fix — every
other phase depends on it, so get it right.

- Add `normalizeYouTubeUrl(url: string): string | null` to
`apps/web/src/lib/youtube-metadata.ts`
- Internally call the existing `extractVideoId()` function (lines 21-33) — it
already handles `youtu.be/ID?si=X` correctly via
`/(?:youtu\.be\/)([a-zA-Z0-9_-]{11})/`, so don't reinvent it
- If `extractVideoId()` returns a valid ID, return
`https://www.youtube.com/watch?v=${videoId}`
- If extraction fails (null/undefined result), return `null` — callers MUST
handle this failure case explicitly, no silent swallowing
- Export `normalizeYouTubeUrl` so it can be imported by the store and API routes

Phase 2: Normalize URLs at Entry Points

Apply URL normalization at the dashboard store level before any API calls, ensuring all downstream services receive clean canonical URLs.

Task 1: Normalize URL in processVideo

Update the dashboard store to normalize YouTube URLs immediately when processing begins.

• Import normalizeYouTubeUrl in apps/web/src/store/dashboard-store.ts
• At the top of processVideo() (line 559), normalize the incoming URL before passing to streamPipeline() (line 579) or legacyAnalyze() (lines 586, 605)
• If normalization fails (returns null), set video status to 'failed' with a clear error message instead of proceeding with an invalid URL
• This single change fixes the issue for both the SSE pipeline and legacy fallback paths

Task 2: Add Defensive Normalization in API Routes

Add fallback normalization in the API routes as a safety net for direct API calls that bypass the store.

• In apps/web/src/app/api/pipeline/stream/route.ts, normalize the URL after extraction (line 523) and before forwarding to the backend (line 625)
• In apps/web/src/app/api/video/route.ts, normalize the URL after resolveVideoUrl() (line 42) and before Strategy 1 backend call (lines 67-71)
• Return a 400 response with clear error message if URL cannot be normalized to a valid YouTube video

🤖 Prompt for AI agents

Apply `normalizeYouTubeUrl` at all URL entry points — raw URLs reaching any
downstream service is a production bug waiting to fire. This phase has two
targets: the store and the API routes.

**In `apps/web/src/store/dashboard-store.ts`:**
- Import `normalizeYouTubeUrl` from `apps/web/src/lib/youtube-metadata.ts`
- At the top of `processVideo()` (line 559), call `normalizeYouTubeUrl()` on the
incoming URL before it reaches `streamPipeline()` (line 579) or
`legacyAnalyze()` (lines 586, 605)
- If the result is `null`, immediately set the video status to `'failed'` with a
descriptive error message and return — do NOT proceed with an invalid URL under
any circumstances
- A successful normalization here fixes both the SSE pipeline and legacy
fallback paths in one shot

**In `apps/web/src/app/api/pipeline/stream/route.ts`:**
- Normalize the URL after extraction (line 523) and before forwarding to the
backend (line 625)
- If normalization returns `null`, return a 400 HTTP response with a clear error
message — never forward a broken URL to the backend

**In `apps/web/src/app/api/video/route.ts`:**
- Normalize the URL after `resolveVideoUrl()` (line 42) and before the Strategy
1 backend call (lines 67-71)
- If normalization returns `null`, return a 400 HTTP response with a clear error
message

Phase 3: Fix Gemini Analyzer Video ID Extraction

Correct the regex in the Gemini video analyzer that fails to extract video IDs from youtu.be short URLs.

Task 1: Fix buildSystemInstruction Regex

Replace the incomplete regex with proper video ID extraction that handles all YouTube URL formats.

• In apps/web/src/lib/gemini-video-analyzer.ts, update buildSystemInstruction() at line 132
• Replace the broken regex /[?&]v=([^&]+)/ with either:
  • Import and use extractVideoId() from youtube-metadata.ts, OR
  • Add a regex that handles youtu.be/ID format: /(?:youtu\.be\/|[?&]v=)([a-zA-Z0-9_-]{11})/
• Ensure the fallback to the full URL only happens when extraction truly fails, not just for short URL format

Task 2: Improve Empty Result Handling

Surface errors clearly when Gemini returns empty or null results instead of silently failing.

• In apps/web/src/lib/gemini-video-analyzer.ts, at line 204, detect when response.text is empty or parses to an empty object
• Throw an error or return a result with success: false and a descriptive error message
• This ensures the fallback chain in the API routes triggers properly rather than accepting silent failures

🤖 Prompt for AI agents

Fix two distinct production bugs in `apps/web/src/lib/gemini-video-analyzer.ts`
that cause silent failures for `youtu.be` short URLs. Silent failures are
unacceptable — they mask real errors and break fallback chains.

**Fix the broken regex in `buildSystemInstruction()` at line 132:**
- The current regex `/[?&]v=([^&]+)/` only matches `?v=` format — it completely
misses `youtu.be/ID` short URLs, a production-breaking bug
- Replace it with either:
- Import `extractVideoId()` from `apps/web/src/lib/youtube-metadata.ts` and call
it directly, OR
- Use a regex that covers both formats:
`/(?:youtu\.be\/|[?&]v=)([a-zA-Z0-9_-]{11})/`
- The fallback to the full URL must only trigger when extraction **truly** fails
— not silently for valid short URL inputs

**Fix silent failure on empty Gemini responses at line 204:**
- Detect when `response.text` is empty or parses to an empty object
- Instead of silently accepting this as a valid result, throw an error or return
`{ success: false, error: '<descriptive message>' }`
- This is critical: silent failures here swallow real errors and prevent the
fallback chain in the API routes from ever triggering

Research

The video processing flow starts in apps/web/src/app/dashboard/page.tsx, which reads the video query parameter and calls processVideo() in the Zustand store. The store sends the raw URL to /api/pipeline/stream (SSE backend proxy) with a fallback to /api/video (multi-strategy analysis). The Python backend has robust URL parsing via extract_video_id() in src/youtube_extension/utils/video_utils.py. However, the frontend passes raw URLs through without normalization, and apps/web/src/lib/gemini-video-analyzer.ts has a regex that only handles ?v= format URLs, breaking for youtu.be short links. A correct extractVideoId() function already exists in apps/web/src/lib/youtube-metadata.ts (lines 21-33) but is not used in the critical paths.

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

Add a `normalizeYouTubeUrl` utility function to
`apps/web/src/lib/youtube-metadata.ts`. This is the foundational fix — every
other phase depends on it, so get it right.

- Add `normalizeYouTubeUrl(url: string): string | null` to
`apps/web/src/lib/youtube-metadata.ts`
- Internally call the existing `extractVideoId()` function (lines 21-33) — it
already handles `youtu.be/ID?si=X` correctly via
`/(?:youtu\.be\/)([a-zA-Z0-9_-]{11})/`, so don't reinvent it
- If `extractVideoId()` returns a valid ID, return
`https://www.youtube.com/watch?v=${videoId}`
- If extraction fails (null/undefined result), return `null` — callers MUST
handle this failure case explicitly, no silent swallowing
- Export `normalizeYouTubeUrl` so it can be imported by the store and API routes
===============================================================================

Task: 2

Apply `normalizeYouTubeUrl` at all URL entry points — raw URLs reaching any
downstream service is a production bug waiting to fire. This phase has two
targets: the store and the API routes.

**In `apps/web/src/store/dashboard-store.ts`:**
- Import `normalizeYouTubeUrl` from `apps/web/src/lib/youtube-metadata.ts`
- At the top of `processVideo()` (line 559), call `normalizeYouTubeUrl()` on the
incoming URL before it reaches `streamPipeline()` (line 579) or
`legacyAnalyze()` (lines 586, 605)
- If the result is `null`, immediately set the video status to `'failed'` with a
descriptive error message and return — do NOT proceed with an invalid URL under
any circumstances
- A successful normalization here fixes both the SSE pipeline and legacy
fallback paths in one shot

**In `apps/web/src/app/api/pipeline/stream/route.ts`:**
- Normalize the URL after extraction (line 523) and before forwarding to the
backend (line 625)
- If normalization returns `null`, return a 400 HTTP response with a clear error
message — never forward a broken URL to the backend

**In `apps/web/src/app/api/video/route.ts`:**
- Normalize the URL after `resolveVideoUrl()` (line 42) and before the Strategy
1 backend call (lines 67-71)
- If normalization returns `null`, return a 400 HTTP response with a clear error
message
===============================================================================

Task: 3

Fix two distinct production bugs in `apps/web/src/lib/gemini-video-analyzer.ts`
that cause silent failures for `youtu.be` short URLs. Silent failures are
unacceptable — they mask real errors and break fallback chains.

**Fix the broken regex in `buildSystemInstruction()` at line 132:**
- The current regex `/[?&]v=([^&]+)/` only matches `?v=` format — it completely
misses `youtu.be/ID` short URLs, a production-breaking bug
- Replace it with either:
- Import `extractVideoId()` from `apps/web/src/lib/youtube-metadata.ts` and call
it directly, OR
- Use a regex that covers both formats:
`/(?:youtu\.be\/|[?&]v=)([a-zA-Z0-9_-]{11})/`
- The fallback to the full URL must only trigger when extraction **truly** fails
— not silently for valid short URL inputs

**Fix silent failure on empty Gemini responses at line 204:**
- Detect when `response.text` is empty or parses to an empty object
- Instead of silently accepting this as a valid result, throw an error or return
`{ success: false, error: '<descriptive message>' }`
- This is critical: silent failures here swallow real errors and prevent the
fallback chain in the API routes from ever triggering

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For design choice 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!