feat: add Fox cloud lattice fragment publisher - #4339
Open
mgazza wants to merge 1 commit into
Open
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.
Summary
Safety
fox.pyBlast-radius isolation
GitNexus reports the live
FoxAPIclass as CRITICAL: 14 direct consumers and 201 affected symbols, including scheduler/write tests. This PR deliberately leaves that class and all its consumers untouched. The new publisher has only test callers.Invalidation contract
Every accepted discovery, liveness or removal change advances the durable provider generation and invalidates the shared compiler. The compiler fresh-reads all registered publishers before composition and retains last-known-good state on provider failure.
Validation
set_liveness→read_stateflow; no live Fox edgeStack