This repository was archived by the owner on Oct 23, 2026. It is now read-only.
Repository navigation
fix: requalify cutover authority cleanup after C2 integration (#399) - #450
Merged
Merged
Conversation
This was referenced Oct 8, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Successor to #448 on current main after #449's C2 integration. Exact base
0706f3bade8e772ea449540eeeae85aa4e806783, candidate304a92e86a38a11aeea56f3f436e5186d1452e83(treed4aedd96fe4d935ee6a9417407a85d8a70cfc51c). Reapplies the same six-file cutover authority cleanup with no productionsrc/server.tsedit: eliminates legacy authenticated HTTP cutover mutation endpoints that permitted caller-selected release activation without Nexus authorization, retains authenticated read-only/api/cutover/statusand the coordinated MCP cutover workflow, and replaces global cutover-mode tool allowlist with exact deployment-effect conflict semantics.Observed pre-fix RED: legacy HTTP
/api/cutover/startresponded 201 to an unbound caller-selected release. On this exact requalified worktree, 24/24 focused tests,npm run typecheck,npm run build, andgit diff --checkpassed. The three broadercutover-progressionfailures were reproduced unchanged on clean old main0b7c8e03...; not claimed PASS. The six changed files were replayed from PR #448, preserving its source file hash forsrc/mcp-cutover.ts.Exact-head GitHub Core/CI and independent reviewer evidence must be refreshed for this new subject. Do not infer acceptance, merge, runtime activation, or Issue closure from this PR. Existing #448 is historic stale-base lineage, not a second parallel implementation.