fix: refresh Nexus Gateway recovery trust anchors - #176
Merged
James3014 merged 1 commit intoSep 16, 2026
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
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.
Refresh the fixed Nexus Gateway recovery trust anchors in
src/durable-operations.tsto the accepted Nexus-new #526 successor-manager lineage. The recovery bridge was still pinned to stale manager/contract hashes, so it would fail closed before a legitimate current recovery could begin.The change is intentionally limited to
src/durable-operations.tsandsrc/durable-operations.test.ts. It updates the accepted manager SHA-256 to6873dde17e08d4020620c2408e414327b176be723f5f23f01bee754b2627502c, updates the contract SHA-256 to3cd032639f69349bd44e61dec41551957e9034157febfff83e7fb3c89b5ef798, and adds an exact-value regression test while preserving the existing fail-closed negative controls.The published Candidate was verified with the focused durable-operations suite (
23/23passing), canonical TypeScript typecheck (tsc -p tsconfig.json --noEmit, exit 0), andgit diff --check.At PR creation time
mainhad advanced to45e44bb4326f3e72a6e0fa7d6e0737e0c8c78d3d. Fresh comparison shows those intervening main changes are in skill/workspace/config/documentation paths, with no overlap with this PR's two durable-operations paths. GitHub currently reports the PR mergeable; merge remains a separate gate after exact-head required checks and current Owner confirmation.