Repository navigation
fix: bind idempotent DOM producer candidate archive - #699
Merged
EHotwagner merged 1 commit intoOct 11, 2026
Merged
Conversation
EHotwagner
deleted the
routine/at-idempotent-producer-delivery-20261011
branch
October 11, 2026 09:04
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.
The candidate reusable-workflow route selects the genuine nonpublishing Rendering producer at protected source
93b19deb5530241bc76055f69f11398bfd22eaa0, original run38122527072/a1, artifact11695963316. Source, run, archive size/hash and custody form one closed tuple. The public tuple remains unchanged.Rendering PR1425 passed all 14 compiled focus/MutationObserver product cases. The acquired archive passed whole CRC/hash and all 19 package-copy/source custody checks. Its original terminal+300 acquisition window was missed; a separate retained read supplied the same immutable bytes. Toolchain receipt data covers the original source-custody job only; producer-reported binary hashes do not establish every hosted job's binary closure. Historical AT failures and unknown custody remain preserved. A complete native Orca journey is pending.
Validation: admitted qualification passed all 93 named static workflow controls and four retained groups against the exact executable bytes, with observed empty cleanup and no escapes/post-pin failures. Only the owning document's qualification-status sentence changed afterward. Public mode, observer and native budgets remain unchanged. Architecture map unaffected.