Add reviewer stabilization and TriageDesk evidence integrity fixes#80
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.
Summary
This PR reconciles the local reviewer-stabilization stack on top of the current \origin/main\ runtime-efficiency work.
It adds the next reviewer-facing stabilization slices without reusing the remote CR-090 through CR-093 lane:
Key trust fix
CR-096 fixes a TriageDesk review-evidence integrity issue:
eview_decision, matching the reducer-consumed key.
eeds_revision\ survives the real TaskLedger reducer path.
Validation
Notes
This branch was rebuilt on top of current \origin/main\ after remote PR #79 advanced main. CR numbering collisions were resolved by preserving the remote runtime-efficiency lane as CR-090 through CR-093 and moving the local reviewer/authority/TriageDesk work to CR-094 through CR-096.