refactor(*): set whole repo up to date with latest hexgate version - #17
Merged
Merged
Conversation
winlp4ever
approved these changes
Jul 15, 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 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.
Brings the repo in line with the latest
hexgaterelease.Renamed
HEXGATE_KEY→HEXGATE_API_KEYUpdated every reference across code, config, scripts, and docs to match the env var name expected by current hexgate.
Fixed the hexgate version never upgrading
make install-hexgateguarded the install on a bareimport hexgate, so a bumped pin inpyproject.tomlwas never applied (venv stayed on a stale version). It now alwaysuv pip installs the extra so the pin (hexgate>=0.2.9) is enforced.Surface agent/user bans to the frontend
A kill-switch ban now shows a clear message instead of a generic failure (or, for devops, nothing at all):
AgentBannedErrorand emit a structured error carryingcode/ban_type/target/reason;protocol.error()gained an optionaldetailsfield.details; added the missingerrorbranch to the Google ADK translator (also fixes any devops error previously being silently dropped).