Summary

Extract parseGeminiAuth() to shared infra module (src/infra/gemini-auth.ts) and use it in both:

• src/memory/embeddings-gemini.ts
• src/media-understanding/providers/google/inline-data.ts

Problem

inline-data.ts directly set x-goog-api-key header without handling OAuth JSON format:

if (!headers.has('x-goog-api-key')) {
  headers.set('x-goog-api-key', params.apiKey);
}

This broke media understanding when using OAuth authentication (e.g., {"token": "...", "projectId": "..."}).

Solution

• Created src/infra/gemini-auth.ts with shared parseGeminiAuth() function
• Both files now import and use this shared function
• Properly supports both traditional API keys and OAuth tokens

Testing

• pnpm check passes (format, types, lint)

Greptile Summary

Extracts the parseGeminiAuth() function from src/memory/embeddings-gemini.ts (added in the prior commit ac0613cf) into a shared src/infra/gemini-auth.ts module, and applies it to src/media-understanding/providers/google/inline-data.ts to fix OAuth authentication for Gemini media understanding (video/image description).

• New shared module: src/infra/gemini-auth.ts — detects OAuth JSON format ({"token": "...", "projectId": "..."}) and returns Authorization: Bearer headers, falling back to x-goog-api-key for traditional API keys.
• inline-data.ts: Replaces hardcoded x-goog-api-key + content-type header logic with parseGeminiAuth(), fixing the bug where OAuth JSON was set as a raw API key value.
• embeddings-gemini.ts: Swaps the local parseGeminiAuth implementation for the shared import (no behavioral change).
• Header override semantics are preserved in both call sites — caller-provided headers still take precedence.

Confidence Score: 5/5

• This PR is safe to merge — it's a straightforward extract-and-reuse refactor that fixes a real OAuth authentication bug with no behavioral regressions.
• The changes are minimal and well-scoped: a function is extracted verbatim from one file into a shared module and applied to a second call site. The extracted function is identical to the original. Header override semantics are preserved in both consumers. Existing tests (embeddings + video) validate the traditional API key path, and the OAuth path follows the same pattern already proven in the embeddings module. No new attack surface or risky logic introduced.
• No files require special attention.

_{Last reviewed commit: 962d59b}

_{(5/5) You can turn off certain types of comments like style here!}