Protect graph publication and report contribution evidence - #393
Merged
Conversation
Kashkovsky
changed the title
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
1 participant
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.
Contributor HTTP routes could mutate publisher-owned canonical tags and assembly leases. They now deny those writes while preserving contribution action tags and internal publisher operations. This includes the independently reviewed boundary fix from #392.
Graph publishers receive and hydrate parse receipts, but that alone does not show whether the published build reused those facts. New-publication CLI results now include bounded contribution diagnostics: selected and integrity-checked result digests, hydration outcome, and the actual index reuse summary. The explicit
publisher-recomputepolicy and separate counts avoid treating receipt acceptance as authenticated contribution use; unchanged publications omit stale evidence.Validation: 17 boundary tests and seven diagnostics tests, including bounded non-mutation properties and paired clean-graph integration controls; typecheck and lint; clear development reviews for both slices; exact-HEAD global installations and synthetic CLI smokes for denied writes, action-tag operations, three hydrated receipts with zero reused files, whole-graph parity, and ordinary full rebuild behavior. All 43 CI checks passed on this combined head, including the governed Linux production performance profile. The earlier standalone #392 performance failure remains recorded; it was not waived or its thresholds changed.