fix(data-integrity): validate revocation replay on current ledger stack - #449
Draft
seonghobae wants to merge 2 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This was referenced Aug 14, 2026
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.
Objective
Reconstruct stale stacked PR #402's unique revocation-replay invariants on the exact current status-validation parent #448, without importing obsolete #400/#357 ancestry.
Exact stack identity
9c9edb212260e0ea6f1de89eb2b3b4e3c2a5722b;f0e854c444ecdecb4373ec81c0bec3a32f83893d;17fcbbe59267397c49fac208e2611130936eecb9;ArtifactLinkLedger.javaandArtifactLinkLedgerRevocationReplayTest.javaonly;Contract
Restart replay rejects a
REVOKEDtransition without a timestamp and rejects a second revocation transition for an already-revoked token. Persisted terminal revocation metadata cannot be rewritten or reconstructed as a non-revoked record.Scope boundary
This child changes revocation replay invariants only. It does not alter live revocation authorization, tenant lookup, token signatures, artifact delivery, read-status validation, or persistence technology.
Merge gate
Keep Draft while #448 and #435 remain unmerged. Require this exact child head's emitted checks and zero valid unresolved findings. After ancestors reach protected
main, rebuild or retarget this two-file delta onto the new exact protected base and regenerate all main-targeted CI, Security Scan, SAST, fuzz, current-head reviews, and qualifying independent approval. No evidence from #402, #400, #357, or predecessor heads transfers.