[test-qa-hourly] Cover version-fenced video claim failures

[i-xtsu-sixyou-ken-mei]

Summary

• add focused regression coverage for the new version-fenced podcast video claim RPCs
• verify an empty compatible queue returns null for both visual and localization workers
• verify database/RPC errors are surfaced instead of being mistaken for an idle queue
• assert both repositories pass the supported visual version and lease owner to the v2 claim RPCs
• format the new test with the repository Prettier rules after CI #731 exposed the mismatch

Scope

• test-only change
• one new Vitest file
• no production implementation, dependency, workflow, documentation, configuration, or CI gate changes

Validation

pnpm --filter @zapengine/podcast-pipeline test -- src/services/video-job-claims.test.ts
pnpm --filter @zapengine/podcast-pipeline format:check
pnpm --filter @zapengine/podcast-pipeline test:ci
pnpm verify changed

GitHub Actions is the source of truth for this connector-only run.

Run update

• CI #731: coverage, deploy gates, dead-env, and Fly Docker verification passed; format check failed
• commit b1519558: applied repository Prettier formatting without changing test behavior
• CI #732: completed successfully
• branch remains current with main
• PR remains open, non-draft, mergeable, QA-only, with no reviews or unresolved review threads
• separate product PR fix(podcast): start generated scripts with the Zap Podcast intro #129 remains open and does not overlap this QA diff
• latest inspection on 2026-07-28 found no new CI, review, mergeability, or scope blocker

Auto-merge

All PR-level safety conditions are satisfied. Auto-merge was attempted; do not bypass protections or merge immediately if repository settings reject it.

Next QA target

After merge, add worker-loop coverage proving a version-mismatched queue is treated as idle without incrementing attempts or logging a processing failure.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
zap-engine-frontend	Ready	Preview, Comment	Jul 27, 2026 6:40am
zap-engine-landing-page	Ready	Preview, Comment	Jul 27, 2026 6:40am