Skip to content

hive-proxy.t27: who may spend a stored provider key over the Anthropic protocol; queen-contributor-keys v3 - #11253

Merged
gHashTag merged 5 commits into
masterfrom
feat/hive-proxy-4024
Oct 20, 2026
Merged

gHashTag merged 5 commits into
masterfrom
feat/hive-proxy-4024

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

Closes #11238

hive-proxy.t27: who may spend a stored provider key over the Anthropic protocol; queen-contributor-keys v3

Gates run on the merged tree (t27c from master): 2 spec(s) with tests clean and vacuous passes 0, seal --verify MATCH, tri types ratchet CLEAN, dupe_scan failure set a subset of master's (inherited red).

TEST specs/automation/hive-proxy.t27 tests=[17] fail=[0] vacuous=[0]
TEST specs/automation/queen-contributor-keys.t27 tests=[16] fail=[0] vacuous=[0]
SEAL specs/automation/hive-proxy.t27 :: all hashes MATCH
SEAL specs/automation/queen-contributor-keys.t27 :: all hashes MATCH
TYPES RATCHET: CLEAN
DUPE failing=4 extra-vs-master=[]

🤖 Generated with Claude Code

claude and others added 5 commits October 20, 2026 12:00
…hropic protocol and what the client is told; queen-contributor-keys v3 (Updates #10782)

specs/automation/hive-proxy.t27 (new, REPO 999-multibots-telegraf, scalar fns so
scripts/t27-logic.mjs lowers every body): the flag, the session-only owner rule,
the request/rate/in-flight caps, which keys are usable, the round-robin pick, the
upstream status/type/code table (402, 429, 529 pass; a refused stored key is a 502
api_error, never an authentication_error), and the Queen's own refusals.

specs/automation/queen-contributor-keys.t27 v3 (extension, not a copy): the Z.ai
Anthropic endpoint, the proxied-request cap and timeout, the upstream marker header,
and proxy_may_open (the Queen opens one enabled key that has an Anthropic endpoint).

gHashTag/999-multibots-telegraf#4024 is the feature issue; the render and Queen hosts
vendor these two files in their own pull requests.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
… it (Updates #10782)

TRIOS_KEY_PROXY=on turns the Queen's proxied-call door on; anything else leaves it
answering 503. proxy_flag_on is the rule, so no host spells the value "on" by hand.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…or code (Updates #10782)

own_type maps the proxy's own refusal statuses to an Anthropic error type, and the
codes for auth, body, content type, method and configuration are constants, so the
render host spells none of them by hand.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…stants now run assertions (Closes #11238)

"a probe waits long enough for a slow reasoning model" and "VERSION says what the
header's last note says" passed with 0 runtime asserts (the compiler folds a
constant-only comparison), so t27c test-report counted them vacuous. Each keeps its
title and its original asserts and gains calls that execute:

  probe_waits(timeout_ms, answer_ms): the 90 s probe timeout outlasts the 87 s Z.ai
  and 46 s NVIDIA answers the header records, is not met by an answer exactly at the
  timeout, and the old 15 s timeout did cut a 20 s answer.
  header_names(version, last_note): VERSION is the v3 the header's last note names, and
  not v2.

No constant, existing fn or other test changes; the two new fns are pure. t27c
test-report: queen-contributor-keys 16 pass, vacuous 0; hive-proxy 17 pass, vacuous 0;
t27b test --check exits 0 on both. Five mutants of the new assertions are caught.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…c protocol; queen-contributor-keys v3 (Closes #11238)

Merge of master plus sealing, gates run on the merged tree with t27c from master: tests clean with vacuous passes 0, seal --verify MATCH, tri types ratchet CLEAN, dupe_scan failure set a subset of master's.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@gHashTag
gHashTag enabled auto-merge (squash) October 20, 2026 06:37
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-20 06:40:56 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 48
PRs with All Checks Green 2
READY 2
FAILING 48
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=bc931a7f7fb3 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 9a3c839 into master Oct 20, 2026
33 of 36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

2 participants