Repository navigation
fix: require recovery lookup config - #44
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
oneshot | 8ed6096 | Sep 08 2026, 10:56 PM |
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
Remove fake production recovery identities and require validated Graph lookup configuration before any MCP call.
Scope and acceptance criteria
Product and security invariants
Invariant notes:
Recovery still has zero settlement submissions. UNKNOWN is preserved without authoritative Arc proof. Provider credentials remain external.
Validation
Commands and results:
Independent review evidence
Gate A — exact candidate tree before push
Base commit SHA: 48391e4
Candidate tree SHA: c63a4410a12044df11a419768fedf073392198a1
Candidate commit SHA: 8ed6096
Reviewer tool:
free-pi-cliReviewer model: deepseek-v4-flash
Verdict:
VERDICT: PASSFindings or residual risks: no blockers; token propagation assertion could be stricter; finite numeric window has no maximum span guard.
The reviewed tree equals the committed tree.
Gate B — exact remote PR head
Pull request URL/number: fix: require recovery lookup config #44 (fix: require recovery lookup config #44)
Remote head commit SHA: 8ed6096
Remote head tree SHA: c63a4410a12044df11a419768fedf073392198a1
Reviewer tool:
free-pi-cliReviewer model:
deepseek-v4-flashVerdict:
VERDICT: PASSFindings or residual risks: no blocking findings; token test could be stricter; numeric block window has no maximum span guard; live canonical Graph deployment/manifest IDs and live MCP/model adapters remain unconfigured by design.
Gate B reviewed the current remote head and matches Gate A's approved tree.
Agent policy / repository-policyand all applicable CI checks pass.Risk and rollback
Human merge