fix(app): patch openapi-effect randomUUID fallback

[skulidropek]

Summary

• vendor a Bun patch for @prover-coder-ai/openapi-effect@1.0.27
• make web request ids fall back when crypto.randomUUID is unavailable
• add consumer regressions for getRandomValues and no-Web-Crypto runtimes

Proof of fix

• Cause: the browser client crashed before the first /api request completed because @prover-coder-ai/openapi-effect assumed globalThis.crypto.randomUUID() existed in every browser/WebView runtime.
• Solution: docker-git now patches @prover-coder-ai/openapi-effect to fall back to crypto.getRandomValues() and then a deterministic clock/counter request id.
• Proof: the new consumer regressions pass against the patched dependency, bun install --frozen-lockfile accepts the patch registration, and the web bundle builds successfully.

Verification

• bun x vitest run tests/docker-git/openapi-effect-client.test.ts
• bun install --frozen-lockfile
• bun run web:build
• bun run --cwd packages/app typecheck

Upstream

• dependency fix PR: fix(shell): add request id fallback when randomUUID is unavailable openapi-effect#28

[coderabbitai]

Warning

Review limit reached

@skulidropek, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 47 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e5d192e0-74e6-4397-aaae-9656fee13c7f

📥 Commits

Reviewing files that changed from the base of the PR and between 5400aa6 and bffed32.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (4)

• package.json
• packages/api/Dockerfile
• packages/app/tests/docker-git/openapi-effect-client.test.ts
• patches/@prover-coder-ai%2Fopenapi-effect@1.0.27.patch

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/browser-randomuuid-fallback

---

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