chore(containers): ship the LiteParse page-ceiling image

[urjitc]

#744 merged the container-side fixes but could not ship them: staging and production pin the extractor image by digest, and Workers Builds deploys the Worker without rebuilding a pinned container. Production is still silently truncating long PDFs at 1,000 pages.

This bumps the pin to an image built from the merge commit.

c48cadd2 → 6f5ce124

What the new image contains

• explicit 5,000-page ceiling (LiteParse otherwise defaults to 1,000 and truncates without reporting it)
• 422 refusal for documents no tier can read — too long, encrypted, damaged — which the workflow now treats as terminal instead of buying an identical verdict from a paid provider on every reconciler sweep
• concurrency gate: each parse can hold gigabytes resident, so a third concurrent parse gets a retryable 503 rather than risking an OOM that kills every in-flight request

Verified against the pushed artifact, not a local rebuild

• Arch=amd64 OS=linux — wrangler cross-compiled correctly from an arm64 host, which is the failure mode worth catching here
• digest resolves in the Cloudflare registry
• real 8-page PDF parses end to end (status 200, 8 pages)
• 3 concurrent parses → one 503, two 200s, exactly the intended gate
• pnpm check clean; both staging and production pins updated together, other images untouched

Note

Only the extractor image moves. The dev config builds from the Dockerfile and is unaffected.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

Summary by CodeRabbit

• Chores
  • Updated the pinned Workspace File Processor container image for staging and production environments.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[capy-ai]

Capy auto-review is paused for this organization because the usage-cycle auto-review limit has been reached. Increase the limit or turn it off in billing settings to resume automatic reviews.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 012f43dc-ef95-40f1-a3ad-41270a6a6d14

📥 Commits

Reviewing files that changed from the base of the PR and between d6fde41 and 3675934.

📒 Files selected for processing (1)

• wrangler.jsonc

---

📝 Walkthrough

Walkthrough

The Wrangler configuration updates the pinned WorkspaceFileProcessor container image digest in both staging and production environments.

Changes

WorkspaceFileProcessor image update

Layer / File(s)	Summary
Update environment image digests wrangler.jsonc	The staging and production WorkspaceFileProcessor container image references now use digest 6f5ce1241aa607fd4b12588656aa587974352fe4a0eff3f0e526dbf78a78da49.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the container image update and the LiteParse page-ceiling change.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/liteparse-image-bump

---

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.}

[greptile-apps]

Greptile Summary

Updates the staging and production WorkspaceFileProcessor bindings to the same immutable LiteParse image digest. The concern that either deployed environment could retain the prior digest was disproved: an assertion confirmed both bindings resolve to sha256:6f5ce1241aa607fd4b12588656aa587974352fe4a0eff3f0e526dbf78a78da49, and Wrangler successfully parsed the updated configuration and generated runtime types. No defects were found, and the change is safe to merge.

Confidence Score: 5/5

Safe to merge: staging and production use the intended immutable LiteParse image, and the configuration parses successfully.

No publishable findings remain after exercising the changed image bindings and Wrangler configuration generation.

Files Needing Attention: No files need additional attention; wrangler.jsonc was the only changed file and was validated.

T-Rex Logs

What T-Rex did

• Ran a review-authored Node JSONC assertion against the parent and updated configurations.
• The old digest caused the parent configuration to fail, while the updated configuration passed for both staging and production with the required digest.
• Ran Wrangler type-generation for wrangler.jsonc and confirmed it parsed the updated configuration and generated runtime types without error.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "chore(containers): ship the LiteParse pa..." | Re-trigger Greptile}