build(android): forward-split verified supply chain from PR 108 - #112
Conversation
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (21)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Purpose
This is forward-split slice A from archival integration PR #108, rebuilt as a coherent net diff on current
main. PR #108 remains the historical integration reference and is not superseded or merged by this draft.Scope
The verification metadata was regenerated for this narrower slice. It does not pre-trust dependencies introduced by later PR 108 slices.
PR 108 traceability
Original work mapped here:
5fe404f2,0b349126,dd263997,3b090b62,ccd22376,f3d62d19,c4791257, and445b5f39. Exact dispositions and rationale are indocs/notes/2026-07-27-pr108-forward-split-traceability.md.Forward-split commits:
74308e48,39379263,c8a08e18,e4ec5880, and documentation correction19bf0dd7.Verification
Passed locally without metadata-writing flags:
./scripts/test-check-build-supply-chain.sh./scripts/check-build-supply-chain.sh./scripts/build-dovi-aar.sh --verify-provenance./gradlew testDebugUnitTest :androidApp:assembleRelease :androidTvApp:assembleRelease --no-daemon --max-workers=2git diff --checkThe first release build exposed 26 lint/release-tool artifacts not traversed by the generic resolver or unit tests. Their recorded hashes exactly match PR #108 metadata; an independent reviewer additionally fetched and verified them from Google Maven/Maven Central. The Linux AAPT2 hash was independently downloaded from Google Maven and is enforced by a regression fixture.
Independent code review found no remaining Critical, Important, or blocking Minor issues.
Remaining acceptance gate
Before release, test the rebuilt Dolby Vision artifact on an NVIDIA Shield with Profile 7 conversion, HDR fallback, seeking, and sustained playback. This draft does not claim that hardware validation.