governance(v21): authorize Product final materialization root closure

[laiqian0239-glitch]

Authorizes only the two causally proven base-owned Product Final materialization blockers exposed by #387 exact candidate aea4b5f2d462f887c5b6886ca8daa3d7308d00b0, Product Final run 31866143443.

1. Windows frozen Element job 94967429606 and Linux materialized Matrix job 94967429641 both fail building @yance/element-module because the already-governed LearningToolUiAdapter.tsx imports assistant-ui/tool-ui through ../../../vendor, while pinned Element materialization currently overlays only integration/element-module. Proposed repair is build-time only: reuse tools/matrix/bootstrap.js to overlay exact existing vendor/assistant-ui-tool-ui/v2026.2.13 at the identical pinned Element workspace path. Learning adapter/package/lock/Vite/0012 runtime patch remain unchanged; final runtime remains package.json + lib only.

2. Windows desktop job 94967429688 reaches rcedit after Electron/npm/production-deps/Node/Parlant GREEN, then fails because targeted git lfs pull returns repository LFS budget exceeded. Historical Final evidence also proved live Release retrieval can fail HTTP 503. Proposed repair keeps the exact official rcedit v2.0.0 x64 bytes/version/size/SHA authority but stores this one 1,360,384-byte reviewed binary as an ordinary Git blob via an exact .gitattributes exception; Final verifies tracked HEAD blob identity, size and SHA without LFS or live download.

Implementation authority, if this proposal is ordinary-merged with explicit owner authorization, is exactly 6 existing paths and must begin with a two-test failure-only commit. No Product runtime/feature, Learning adapter, dependency/manifest/lockfile, Element runtime patch, WP7 implementation, UAT receipt/status, retry/mirror/cache/downloader, checksum/version rewrite, broad LFS disablement or new Yance infrastructure is authorized.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 17 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 Plus

Run ID: 4b4a34a6-ee48-4138-80a8-0511558f2115

📥 Commits

Reviewing files that changed from the base of the PR and between 9aecf24 and d44eda9.

📒 Files selected for processing (1)

• governance/layered-ci/v21-product-experience-bilingual-search-final-materialization-root-closure-authorization.json

---

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

[laiqian0239-glitch]

@coderabbitai full review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

---

Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 23 minutes.

[laiqian0239-glitch]

@coderabbitai full review

[coderabbitai]

⚠️ Action not completed

Review rate limited.

---

Your included review limit is currently reached under our Fair Usage Limits Policy. This review may still proceed through usage-based billing if eligible. Your next included review will be available in 17 minutes.

[laiqian0239-glitch]

Independent exact-head authorization review for d44eda92a06abfbc6207dabb5b35cdca2ec17a66 under the repository's CodeRabbit-rate-limit fallback rule. CodeRabbit explicitly did not start the exact-head review because the review limit was reached; no CodeRabbit conclusion is claimed. Final proposal transport is ahead 2 / behind 0 from trusted main 9aecf248d7b5462aecaa852bbc3fe881446eda86 and the net diff is exactly one new governance authorization JSON. The prior implementation-branch RED was traced to proposal schema only (74-character workPackage exceeded the generic 64-character bound and workflowModificationAllowed lacked the mandatory exact workflowModificationPolicy); revision 2 shortens only the work-package identifier and adds the exact existing Product Final workflow path/count/digest, without changing causal evidence or implementation scope. Recomputed canonical SHA-256 sets match all declarations: authorization path 2c1ff5e3d043f0a4132b9d2290a8990a0bbd548a8efdce7cdde711a2cfb3e598; six implementation paths 4d992807421a33b406085bbb216635b19676bfb4842b23de278af903c3ba8bd2; two failure-first tests b9a1039dd81be3c13aae079d214ebfd630e2e370c27e77a4f86bccc0ac431d56; Element build-overlay paths 8d8a75b92f724dbbc6ca22d8f5a2c0a3ce304db9358016fa5987b82b688eac54; rcedit custody paths 669730a1c8b75d7f16907f8643c36d6341ccfcab35450dab4aba601cac00cd27; workflow path eca1bb2482379a5df234b391747d035ddde2419b6072f6fd279a58239e4e0322. Scope is root-cause bounded: (1) reuse existing Matrix bootstrap overlay to materialize only the already-governed assistant-ui/tool-ui v2026.2.13 tree at the identical pinned Element build-workspace vendor path while LearningToolUiAdapter, module manifests/lockfiles/Vite/tsconfig/project, Element ModuleLoader, and 0012 package.json+lib-only runtime delivery remain unchanged; raw vendor source is not authorized for runtime delivery; (2) preserve the broad future vendor/rcedit/*.exe LFS rule but create a later exception only for the exact reviewed vendor/rcedit/rcedit-v2.0.0-x64.exe, keeping the existing official v2.0.0 asset identity, 1,360,384-byte size and SHA-256 3e7801db1a5edbec91b49a24a094aad776cb4515488ea5a4ca2289c400eade2a, and require native Git tracked-blob/worktree identity + size + hash verification with no Git LFS materialization, live download, retry, mirror, package-manager acquisition, source rebuild or alternate binary. No Product feature/runtime, dependency, manifest/lockfile, Learning adapter, Element runtime patch, WP7 implementation, UAT receipt/status, unrelated workflow, checksum/version, broad LFS disablement, cache/downloader or new general-purpose Yance infrastructure is authorized. Exact-head Stage 6.4.5.9 and Layered CI are GREEN; ACV2 is GREEN; Product Final is correctly skipped on this governance branch. Review threads are empty. P0/P1 blocking findings: 0. Merge remains gated on the remaining common exact-head Model Brain Windows run, a final fresh-main/head check, and explicit owner authorization required by this proposal.