B3: ship review queue and explainability#147
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
Scope Notes
Verification
Upgrade Overview
Protected Areas
Compatibility Impact
This is an additive bridge-phase review layer on top of the shipped B2 capture pipeline. Existing provider and MCP workflows remain intact while explicit review queue and review apply surfaces are added for persisted review items.
Migration / Rollout
Deploy the Alice review and MCP changes together so review queue payloads, explanation fields, and action semantics stay aligned across API, MCP, recall, and resume behavior. No new packaging or demo workflow is included in this sprint.
Operator Action
Validate alice_review_queue ordering and filtering, then exercise approve, reject, edit-and-approve, and supersede-existing through alice_review_apply. Confirm approved actions change later recall and resumption output deterministically, and confirm rejected items do not behave like accepted continuity state.
Validation
Branch-local verification passed:
Rollback
Revert the squash merge commit to restore the pre-B3 review behavior, then re-run the review-specific tests, full suite, and Hermes smoke validation before redeploying.