mirror of
https://github.com/Comfy-Org/github-workflows.git
synced 2026-11-05 00:17:37 +00:00
[PR #326] [MERGED] chore(groom): delete the superseded key-broker.mjs loopback proxy and its test #326
Labels
No labels
cursor-review-catalog-drift
groom
groom
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Comfy-Org/github-workflows#326
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/Comfy-Org/github-workflows/pull/326
Author: @mattmillerai
Created: 9/19/2026
Status: ✅ Merged
Merged: 9/20/2026
Merged by: @mattmillerai
Base:
main← Head:matt/be-15722-delete-key-broker📝 Commits (4)
91ea9a7chore(groom): delete the superseded key-broker.mjs loopback proxy (BE-4419 -> BE-4303)fac03b9docs(bump-callers): state the WATCHED_EXEC rule as the run-time test, not "what groom.yml starts"a1db233fix(groom): refresh the apt index before installing bubblewrap in preflightef6a446Merge remote-tracking branch 'origin/main' into matt/be-15722-delete-key-broker📊 Changes
5 files changed (+9 additions, -653 deletions)
View changed files
📝
.github/groom/README.md(+1 -60)📝
.github/groom/jail-shim.mjs(+1 -1)➖
.github/groom/key-broker.mjs(+0 -214)➖
.github/groom/tests/test_key_broker.py(+0 -374)📝
.github/workflows/bump-groom-callers.yml(+7 -4)📄 Description
ELI-5
The groom workflow used to reach Anthropic through a little localhost proxy,
key-broker.mjs. That was replaced a while ago by the agent sandbox, which usesbroker.mjsover a unix socket instead. The old proxy has been sitting in the repo ever since, loaded by nothing — but it lives inside the groom fleet's watched surface, so any commit that touched it would fan a no-op SHA-bump PR to every groom caller. This deletes it, its test, and its README section.What changed
.github/groom/key-broker.mjsand.github/groom/tests/test_key_broker.py..github/groom/README.md— removed thekey-broker.mjs — the localhost API-key proxysection (heading through itsgroom.yml wiringblockquote), and dropped the sentence in thetests/bullet about key-broker tests booting the real script undernode..github/workflows/bump-groom-callers.yml— rewrote theDELIBERATELY ABSENTcomment aboveWATCHED_EXEC.WATCHED_EXEC,WATCHED_ASSETSand thepaths:filter are unchanged — the deleted file was never listed in any of them..github/groom/jail-shim.mjs:7— comment says "the broker (broker.mjs)" instead of "the key-broker (broker.mjs)", removing the last misleading mention.Skip-caller-bump: trueas its sole trailing trailer (verified withgit interpret-trailers --parse), so the removal does not itself fan a churn bump. Please keep that trailer intact in the squash-merge message —preflight.shreads it only from the trailing trailer block.Why the deleted README section needed no relocation
The section's blockquote was the guidance to check: if it were the only place the sandbox /
broker.mjshand-off is described, that paragraph had to move rather than die. It is not.## The agent sandbox — agent-sandbox.sh + broker.mjsalready describes the per-job composition end to end — the broker step holdingsecrets.ANTHROPIC_API_KEYand startingbroker.mjson$BROKER_SOCK, the sandbox preflight, the agent step running with a DUMMY key andANTHROPIC_BASE_URLpointed at the in-jailjail-shim.mjs, the literal-key scan/capture tripwires, and thealways()broker cleanup. Nothing unique was lost, so the blockquote is deleted rather than moved.Evidence it is dead (re-confirmed, not taken on faith)
Deleting a credential-handling file is a capability removal, so I went and looked via every path rather than trusting the prior investigation:
grep -n "broker.mjs" .github/workflows/groom.yml→ the three agent jobs each runnohup node "$GROOM_ASSETS/broker.mjs" "$BROKER_SOCK"(lines 1501, 2001, 2941). No reference to the deleted file anywhere ingroom.yml.agent-sandbox.shandjail-shim.mjsreference onlybroker.mjs//run/broker.sock.gh search code "key-broker.mjs" --owner Comfy-Org→ 6 hits, all in this repo, all now removed by this diff (README ×2, the bump-fleet comment ×2, the test ×2). A second search forkey_brokerreturned nothing.git log -- .github/groom/key-broker.mjs→ one commit, the one that added it. Nothing has touched it since.WATCHED_EXEC, so its deletion cannot trippreflight.sh's decommission probe, andWATCHED_ASSETS(.github/groom) still resolves.GROOM_BROKER_PORT/GROOM_BROKER_UPSTREAMenv knobs and port8199now appear nowhere in the tree, so removing the README's knob table orphans no live configuration.git grep -n key-brokerreturns nothing.Judgment call
The ticket asked for two things that cannot both hold: rewrite the
DELIBERATELY ABSENTcomment to namekey-broker.mjsas removed, and havegit grep -n key-brokerreturn nothing. I resolved in favour of the mechanical check — the rewritten comment states the rule ("this list names only whatgroom.ymlactually starts") and identifies the deleted file by its originating ticket id (BE-4419) rather than by filename, so nothing dangling remains for a futuregrepto surface while the note still explains why the list is short. Flagging it because it is a deliberate deviation from the literal instruction.Verified
python3 -m unittest discover -s .github/groom/tests -p 'test_*.py' -v→ 393 tests, OKbash .github/bump-callers/tests/test_paths_contract.sh→ 148 passed, 0 failed; the groom fleet'sall 13 WATCHED_EXEC entries resolve to tracked filesassertion still passes and the entry count is unchangedbash .github/bump-callers/tests/test_preflight.sh→ 445 passed, 0 failedshellcheck -x .github/bump-callers/*.sh .github/bump-callers/tests/*.sh→ clean;shellcheck -x .github/groom/*.sh→ cleanpython3 .github/workflow-pins/check_workflow_pins.py→ OK, 11 workflows, 156uses:refs SHA-pinnedpython3 .github/agents-md-integrity/check_agents_md.py --root .→ passed (2 pre-existing warnings, unrelated)shellcheck -x .github/lint/check-org-repo-literals.sh && bash .github/lint/check-org-repo-literals.sh→ OKnode --check .github/groom/jail-shim.mjs→ OKgit grep -n key-broker→ no outputgit log -1 --format=%B | git interpret-trailers --parse→Skip-caller-bump: trueResidual
.github/groom/tests/sandbox-tests.shwas run but could not be made green on this host, and that is pre-existing. It fails atFAIL: broker credential proxywithnode: command not foundinside the bwrap jail — this host'snodelives outside the paths the jail bind-mounts. I confirmed the identical failure on the unmodified checkout before my change, so it is environmental, not a regression; CI is the authority for that suite. It is nonetheless a named groom artifact I did not observe passing against this diff. My change to the only file that suite exercises here is a one-word comment edit injail-shim.mjs.## The agent sandboxsection says that before BE-4303 "the three agent steps used a hand-rolledchmod/env -uscrub with the real key in the step env". Those describe the same period differently. With the blockquote gone, only the second account remains, and I left it untouched rather than rewrite history prose I cannot verify. Worth one pass by someone who remembers which is right.paths:negative glob + aWATCHED_PATHSPECSexclude) instead of deleting — note that theWATCHED_PATHSPECSblock that approach needs only exists once #324 merges, which it has not. I chose deletion because the evidence above shows no consumer, inside or outside this repo.Provenance
git grep -n key-brokeremptyDELIBERATELY ABSENTcomment identifies the deleted proxy by ticket id rather than filename, so thatgit grep -n key-brokerreturns nothing (see "Judgment call");sandbox-tests.shcould not be run green on this host for a pre-existing environmental reason (see "Residual")🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.