feat: freeze review runtime assets

[norvalbv]

Review 16 of 20 — hardened replacement stack. This is not a patch-equivalent split of #95; it is one layer of the larger redesign.

What this PR does

Completes the frozen executable/runtime asset capture used by review gates:

• Builds an exact, sorted registry of reviewer briefs, skills, packaged scripts, and baseline modules.
• Reads assets through descriptor-pinned paths and verifies source/copy/source identity.
• Preserves the executable-vs-non-executable mode class.
• Rejects unexpected tree entries, symlink escapes, special files, torn capture, and registry drift.
• Rolls back incomplete private copies instead of leaving a partially trusted runtime.

Why this slice exists

The review should execute one authenticated set of reviewer instructions and scripts. If target-controlled assets can change between discovery and execution, the reported verdict no longer describes a single reproducible snapshot.

Review carefully

• The registry is complete for Claude, Cursor, Codex/devkit reviewers, and baseline modules.
• Exact-tree validation catches both missing and injected assets.
• Descriptor-pinned reads close rename/symlink races.
• Executable mode semantics survive copying.
• Capture failure cannot leave a runtime that later appears valid.

Explicit non-goals

• Persistent cache-root identity is added in feat: isolate review cache roots #129.
• Repository-state authentication is added in feat: authenticate review repository state #130.
• This slice does not expose or run the final public command.

Stack position

• Base: feat: freeze review gate projections #127
• Previous: feat: freeze review gate projections #127
• Next: feat: isolate review cache roots #129
• Full review order: refactor: share gate worktree preparation #104 → feat: configure review-mode gate routing #108 → feat: harden packaged reviewer runtime #110 → feat: compare review lint baselines #111 → refactor: establish review execution primitives #113 → refactor: isolate review gate projections #114 → refactor: add review runtime fingerprints #115 → feat: capture exact review snapshots #116 → feat: isolate review dependencies #118 → feat: freeze review runtime inputs #120 → feat: capture complete review snapshots #123 → feat: materialize local review submodules #124 → feat: freeze review setup runtime #125 → feat: isolate review dependencies #126 → feat: freeze review gate projections #127 → feat: freeze review runtime assets #128 → feat: isolate review cache roots #129 → feat: authenticate review repository state #130 → feat: supervise review gate processes #133 → feat: fence review verdict caches #135

Review bottom-up. These PRs currently target their predecessor branches; do not merge a middle PR directly to main. After review, successors must be retargeted/rebased as predecessors land, unless an explicit stack-collapse landing process is agreed.

Size and evidence

• 5 files
• +272 / -18 lines
• Includes frozen-asset, fingerprint, reviewer-runtime, and rollback regression coverage.
• Originally published through devkit ship.
• This description update changes GitHub metadata only.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 29 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: 07a8055c-61aa-41c9-b243-30029e9f3829

📥 Commits

Reviewing files that changed from the base of the PR and between cad7d80 and af45337.

📒 Files selected for processing (5)

• cli/__tests__/review-asset-runtime.test.mts
• cli/__tests__/review-runtime-fingerprint.test.mts
• cli/lib/ship/review/asset-runtime.mts
• cli/lib/ship/review/runtime-fingerprint.mts
• gate-engine/review/runtime.mts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/review-stack-16-frozen-assets

---

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