[LuisAlejandro]

Summary

• OpenRouter video models are now callable. openrouter joins the video registry against a submit→poll preset, because POST /api/v1/videos answers 202 with a job id rather than a finished clip. The synchronous openai-video handler reported that 202 as success with an empty data array, so a combo stopped instead of trying its next target.
• The finished clip is fetched with the provider credential and re-served from GET /api/v1/media/{id}, because unsigned_urls points at an endpoint that 401s without the OpenRouter key. An expired job is now terminal instead of polling until a misleading 504.
• Media URLs are built from the caller's own forwarded host (X-Forwarded-Host/X-Forwarded-Proto, then Host), not the bind address or BASE_URL. Served media is scoped to the key that generated it, and files expire on the call-log retention window.

Related Issues

• Closes fix(providers): OpenRouter video reports success and returns a URL the caller cannot open #16369
• Related to fix(api): job-based video writes no usage or request-log row, and drops the calling API key #16370 — the usage/call-log rows for this path, and the usageHistory attribution fallback, are an independent PR (fix(api): record job-preset video calls and attribute them to the API key #16378), not stacked on this one. Both are based on release/v3.8.52.

Validation

• Change type: provider
• Focused tests and category gates from the golden path
• npm run lint
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR

node --import tsx/esm --test tests/unit/services/openrouter-video-job.test.ts tests/unit/services/resolve-request-origin.test.ts   # 13/13 pass
node --import tsx/esm --test tests/unit/registry-direct-exports.test.ts tests/unit/media-provider-ordering.test.ts tests/unit/model-id-path-injection.test.ts tests/unit/local-catalog-import-media-api-format.test.ts   # pass
make typecheck        # clean
make lint             # clean
npm run check:provider-assets   # passed

• npm run check:provider-consistency did not run locally: it is a bun script and bun is not installed in this environment (npm suggests cd node_modules/bun && node install.js). CI-only for this branch.
• The provider.ts translate-path golden snapshot fails locally on zyloai, which this diff does not touch. release/v3.8.52 is already red — see 🔴 Release branch not green: release/v3.8.52 #15306.

⚠️ base-red inherited: #15306

Tests Added Or Updated

• tests/unit/services/openrouter-video-job.test.ts — extended: registry→preset wiring, submit→poll completion served as a URL, owner-tag digesting, retention prune, api-key-context owner, malformed-id traversal, cancelled job.
• tests/unit/services/resolve-request-origin.test.ts — new (forwarded host/proto precedence, comma-separated headers, direct-call fallback).

Coverage Notes

• open-sse/handlers/videoGeneration/mediaStore.ts and src/shared/utils/resolveRequestOrigin.ts are covered directly by the two test files above, as are the preset's auth-gated download and owner stamping in open-sse/handlers/videoGeneration/job.ts.
• src/app/api/v1/media/[id]/route.ts is thin and mostly delegates — the id pattern, the owner digest and the file read all live in mediaStore and are asserted — but the route's own ownership comparison (unowned id → 404) has no route-level test. Correcting an earlier claim in this description that the route was covered by these tests. Worth a reviewer's eye; say the word and I will add one.

Reviewer Notes

• GET /api/v1/media/{id} is new. The id is validated against the exact pattern mediaStore generates, so it cannot escape MEDIA_DIR; an unowned id returns 404 rather than 403 so the route does not confirm that it exists; session auth may read any id.
• Retention deliberately reuses CALL_LOG_RETENTION_DAYS (default 7) through a prune-on-write sweep: one knob, no scheduler. Lowering it also shortens how long served media URLs stay valid, and nothing expires while no generation runs.
• The video route establishes runWithCallLogApiKeyContext, the wrapper the images and chat paths already use. Here it is what makes the media owner attributable; the same identity feeds the usage/call-log rows in fix(api): record job-preset video calls and attribute them to the API key #16378.
• Overlap with fix(api): record job-preset video calls and attribute them to the API key #16378: both PRs set that wrapper on the video route. The comment and the helper are byte-identical in both, so that block merges cleanly; the diffs meet at the handleVideoGeneration call site, where this PR threads mediaOrigin, and in job.ts, where fix(api): record job-preset video calls and attribute them to the API key #16378 splits the function head for recording. Whichever lands second needs a trivial rebase (keep the incoming wrapper, add the other change).
• openrouter is added to the video registry only; the chat provider of the same name is untouched.