Repository navigation
Honor current probe contracts in admission cooldown planning - #29
Merged
Merged
Conversation
Invalidate retained completion evidence in the planning snapshot when its base probe contract differs. Preserve stored history and protect matching-contract successes.
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.
When the base probe contract changes, successes recorded under the previous contract could still protect a feed from admission cooldown. Clear contract-scoped completion and elapsed-work counters in the planning snapshot alongside sampled yield; retained Redis history remains unchanged until the normal completion path resets it.
Validation:
make check, Staticcheck, and regressions for mismatched and matching contracts, three completed zero-admission observations, and unchanged stored quality.