Repository navigation
chore(pins): tokenfuse v1.15.0, wardryx 2.0.0, vouchryx v0.3.0, costcrew v0.7.0; the gateway's wardryx key becomes pep - #133
Merged
Conversation
…w 0.7.0; the gateway's policy-plane key is a pep wardryx 2.0.0 refuses a viewer key on POST /v1/decide and POST /v1/filter-tools. The gateway, the MCP broker and scopyx present the one policy-plane key on every governed call, and the gateway and the broker fail closed, so a viewer key would refuse every governed call once the new image took traffic. - install.sh mints the gateway's entry as default:pep on a new box. - A re-run leaves .env as is, so wardryx_gateway_role rewrites that one entry's role from viewer to pep before the first up. The secret, the org, an agent list, every other entry and every other line stay byte for byte, and the admin key is never rewritten. - New gate scripts/wardryx-gateway-key-is-pep.sh (invariant 37), nine teeth cases, scenarios in features/the-gateway-key-is-a-pep.feature, in gates.yml, .githooks/pre-push and the CLAUDE.md gate list. - Pins: tokenfuse and tokenfuse-control-plane v1.15.0, wardryx v2.0.0, vouchryx v0.3.0, costcrew v0.7.0 in compose.yaml, components.json, README and the teeth anchors. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
TAIPANBOX
added a commit
that referenced
this pull request
Oct 19, 2026
…to #140 Renames docs/releases/v1.1.36.md to v1.2.0.md and covers every merged PR since v1.1.35: #131 (typed stub), #132 (client keys, broker blocks raw secrets), #133 (pins, pep key), #134 (networks), #135 (provider key, drills key), #136 (agent tokens), #138 (keyryx custody and witness), #139 (digest pins and signatures), #140 (the wave's pins and conflicts). #137 is open and not included. The Upgrade first list is taken from each PR's body and from the diff against v1.1.35: new required variable (GATEWAY_CLIENT_KEYS), new uids, new default services (keyryx, keyryx-witness), the approval signer, the network move, the new refusals, and the outbound HTTPS the install now needs. Moves the stale pins in the README (console v1.1.48, tokenfuse v1.18.0). No other file names the release version: the install.sh banner and components.json carry none. Gates run here: features-are-bound, no-owner-quotes, manifest-is-true. Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
TAIPANBOX
added a commit
that referenced
this pull request
Oct 19, 2026
…to #140 (#141) Renames docs/releases/v1.1.36.md to v1.2.0.md and covers every merged PR since v1.1.35: #131 (typed stub), #132 (client keys, broker blocks raw secrets), #133 (pins, pep key), #134 (networks), #135 (provider key, drills key), #136 (agent tokens), #138 (keyryx custody and witness), #139 (digest pins and signatures), #140 (the wave's pins and conflicts). #137 is open and not included. The Upgrade first list is taken from each PR's body and from the diff against v1.1.35: new required variable (GATEWAY_CLIENT_KEYS), new uids, new default services (keyryx, keyryx-witness), the approval signer, the network move, the new refusals, and the outbound HTTPS the install now needs. Moves the stale pins in the README (console v1.1.48, tokenfuse v1.18.0). No other file names the release version: the install.sh banner and components.json carry none. Gates run here: features-are-bound, no-owner-quotes, manifest-is-true. Co-authored-by: Claude Haiku 5.5 <noreply@anthropic.com>
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.
Pins the four security releases of 2026-10-18 (
@decided 2026-10-18, paraphrased: release the wave-0 fixes and pin them in the launchers before wave 1).viewerkey on/v1/decideand/v1/filter-tools. A fresh install mints the gateway's key (shared by the gateway, the MCP broker and scopyx) aspep; on a re-run, an existing.envhas exactly that one entry rewritten from viewer to pep, its secret, org and agent list unchanged, file mode kept, every other key untouched.scripts/wardryx-gateway-key-is-pep.sh(invariant 37) with 9 teeth cases (451 in the harness).Breaking: an installed box that is not re-run keeps its viewer entry; with wardryx 2.0.0 the gateway and the broker then fail closed (403 from the policy plane). Migration: re-run install.sh before the new images take traffic. A new box is not affected.
The real proof is this repository's install.yml on a fresh runner with the new images.
🤖 Generated with Claude Code