Repository navigation
ci: reuse verified PR artifacts across unrelated main changes - #880
Merged
Merged
Conversation
simonvanlaak
force-pushed
the
ci/pr-reuse-input-closure
branch
from
November 6, 2026 17:19
f9ff67b to
8a5b8ee
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Successful PR artifacts currently rebuild when unrelated commits land after their tested base. Admit the original artifact when its complete registered component source closure matches main, its tested base is an ancestor of main's landing parent, and the existing owner/target/runtime/toolchain digest and authenticated producer checks match. Missing commit or artifact evidence falls back to fresh work; original bytes and build provenance remain unchanged.
The input audit adds two external App Shell test dependencies to its registration, trigger filters and platform selector. No workflow jobs or cancellation rules are added. Public CI also exposed a reproducible test setup race: resizing left a smooth scroll running during the frog double-click. Flush resize layout and finish scrolling before the unchanged real pointer action and reveal/QR viewport assertions; no product behavior or timeouts change.
Validation: 84 delivery/workflow tests, 21 architecture tests, strict TypeScript, repository architecture checks and actionlint passed. Real Git fixtures cover advanced main, missing tested commits, changed inputs/inventory/modes, divergent history and failed retrieval. Public's failure reproduced with full Chrome on two CPUs; the final clean repair passed its full verifier with Chromium/Firefox (240 + 26 tests and analytics smoke). Hook fixtures include the newly consumed registration. Independent input audit, admission review, and final repair/integration review found no unresolved findings. Normal PR platform checks and post-merge main receipts remain delivery gates.