Fail closed on non-durable Video Pack claims; preserve atomic Redis claim semantics

[Copilot]

Canonical issue

Outcome

Video Pack claim/recovery now enforces durable Redis coordination in production. The API no longer returns 202 processing unless a durable processing claim is actually recorded, preventing ready-pack clobber and non-durable acceptance.

Scope

• Included:
  • Production durability gate (claim path): claimPackProcessing now rejects production claims when Upstash REST credentials/client are unavailable (no isolate-local fallback for claim decisions).
  • API fail-closed behavior: POST /api/video/pack maps claim failures to 503 and does not schedule background extraction.
  • Regression coverage: added focused tests for production fail-closed claim behavior in store and route layers.
  • Example of the behavioral boundary:

    // production, no durable Redis config
    const claimed = await claimPackProcessing(identity); // throws
    // route returns 503 (not 202), and no extract is scheduled

• Explicitly excluded:
  • Changes to pack schema, extraction content logic, or ready/error record formats.
  • Changes to non-production fallback behavior outside the claim durability contract.

Risk

• Risk level: medium
• Failure mode:
  • Production environments missing Upstash REST config will now fail claims with 503 instead of silently proceeding with non-durable processing.
• Rollback:
  • Revert claim durability guard and route fail-closed handling in video-pack-store.ts and video-pack.ts.

Verification

List exact automated and manual checks, tied to the current head SHA.

• Focused tests
• Required CI
• Review threads resolved

Production evidence

Not applicable for this change set: behavior is a server-side correctness guard for claim durability and response semantics; no UI/runtime production artifact is introduced.

Agent handoff

• One canonical issue is linked
• No competing PR implements the same issue
• Acceptance criteria are satisfied
• Required checks pass on the current head
• Human decision is requested only for product, security, irreversible infrastructure, or production approval

• Fixes Make Video Pack Redis claims atomic to prevent races #1650

[vercel]

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

Project	Deployment	Actions	Updated
v0-uvai	Ready	Preview, v0	Sep 12, 2026 9:23am UTC

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: e62f344f-987a-44ef-897a-28556db285f5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🔍 PR Validation

⚠️ PR title should follow conventional commits format

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA 228f10f.

Ensure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice.

Scanned Files

None