Filter stale non-AoA errors from deferred coverage - #414
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.
PLAN
Fix deferred storage coverage so a disappeared non-AoA candidate does not carry stale runtime errors into the current owner snapshot, while preserving the candidate/provenance record and all current/AoA/global errors.
DIFF
discovery_absentnon-AoA candidate IDs from coverage and derived full-error aggregation.f12b36f581b3484bcadfd0ba01ba8e43fbc9ea33654fb7d895f952076c97d7a7, with its digest-bound owner budget receipt.VERIFY
sufficient=true.--checkagainst the committed source snapshot, ABI signature--check, scaffold--check, public-boundary validation, andgit diff --check: passed.LIVE HOST EVIDENCE
No live host state, install projection, service, or runtime was changed or used as publication evidence.
REPORT
The current deferred owner snapshot retains all candidates and authoritative current/AoA/global errors while dropping only stale errors attached to disappeared non-AoA candidates. The KAG family now describes the committed source tree.
RESIDUAL RISK
The change relies on the existing source-owned candidate identity and AoA-owner-record predicates. The generated KAG delta exceeds the default one-megabyte incremental budget because committed source anchors move with the updated
cli.pyand test; the exact digest-bound owner receipt records that exception. Downstream consumer acceptance remains the responsibility of the protectedRepo Validationcheck.