Repository navigation
Bind inventory mutation kills to oracle provenance - #785
Merged
Merged
Conversation
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.
Inventory mutation controllers could count a subject or helper
AssertionErroras a kill because they trusted formatted unittest failure text. This change records actual traceback code identities before unittest cleanup and requires the selected synchronous test body or finite unittest assertion helpers to be the origin. It retains the original ten source mutations and adds the previously surviving post-status and fsmonitor mutations; no inventory implementation, mathematical statement, bound, axiom, kernel outcome, authorship or scientific disposition changes.Native commit
2b93a6d2279e5f3edff0eb991e4fdb25d64a6b8fand hosted head9c21bdfabed78477f7ef7e6ef4fb28bad1b31214have identical tree9c036c987ca439135a1784bb5e79711782df8a79. The native composition preserves Main #783's six canonical/decision files before this documented follow-up. Its prior source commit and prerequisite-bound Git delta are retained in the evidence; published Main history remains the normal parent.Observed local validation on the exact test and recorder bytes in that tree:
02536f852c5cf69a5d3125d50cd485f26d77fa8459ccad82447a766a4dfe50a4; the existing invalid-escape SyntaxWarning is retained. This is not the final federation G11 gate. Hosted checks completed successfully for tested mergecc78eb354e2e65705bc76bd23ad9e28ccfd31175, whose tree matches this head: navigation run42692397895, workspace-landing42692398125, G11 component42692398310, federation drift42692397871and public shop42692397843. The hosted normal regression ran 2,576 tests with 25 skips; it does not establish the no-skips federation criterion. The focused component checks passed in both modes as described above.Main #783 and Workspace #56 are separately observed at
7738e4c2...and5dcb544c...; Workspace pins that Main. Both Workspace post-merge jobs succeeded. A later Main merge requires a fresh guarded Workspace pin comparison. The separate #784 Node repair is active; its earlier success is scoped to its tested base, and the original failed Node run remains preserved.This is a bounded synchronous unittest component, not a hostile-code sandbox, proof checker, whole Layer A audit, final G0/G6, scientific review, CBZ-0 or terminal Partial. Source-bound evidence is
libfile_fde3_f-a1d4cb841f208191aafdc61057043076_59a0f9f234e48191bc19fddcc0f80648, SHA-256bea63fdd7dc5e53174e2af4e08f3db91973546a45392def6763446f097f026d3; prior adverse probes are retained separately. A fresh head and default comparison remains necessary before normal integration.