Conversation
Closes browseros-ai#1280 Delegated to queen-swift by the Trinity Queen.
Closes browseros-ai#1280 Delegated to queen-swift by the Trinity Queen.
gHashTag
added a commit
that referenced
this pull request
Aug 21, 2026
…ansition stops being asked Every queen/* pull request fails the cla bot - it does not know the Queen as a signatory - so the wake path re-briefed bees dozens of times a day about a red no code change can turn green (#74/#75, 23x/day measured on dev, recurring on release). A red made ONLY of administrative checks now logs queen.pr.gate_administrative, names the checks, and waits on the operator; one real failing check beside cla still wakes the worker. The wake path also asked the registry for accepted -> rejected on every single execution - a transition the state table has never allowed (.accepted permits only .merged), so it was refused every time, logging "Cannot move ... from accepted to rejected" beside each wake. The attempt is removed with the table's reasoning in place: the correction in the worker chat IS the wake; the record stays accepted until the forge says merged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
gHashTag
added a commit
that referenced
this pull request
Aug 21, 2026
…and the allowlist earns its default Three wire proofs collected in one worker turn. queen.worker.expensive fired for the first time in its existence: task browseros-ai#1131 recorded 10,650,930 input / 73,416 output tokens, priced at $6.55 by ModelPricing - the spend pipeline is live end to end, and the $10/day SwarmBudget gate can finally trip. queen.pr.gate_administrative fired at 17:38:56Z naming its check ("#74 is red only on administrative check(s) (cla); nothing a worker can fix") - no wake, no illegal transition. And the turn's finishing commit (queen.branch.committed 17:56:19Z) landed with the env allowlist active on the live server: ten variables are enough for real work, so the scrub flips to ON by default (TRIOS_BASH_ENV_ALLOWLIST=0 is the opt-out). make spend's note stops claiming the server "does not emit usage yet" - that cause died this evening; the 49 zero-token tasks are turns that finished before emission went live, and the note now says so. Co-Authored-By: Claude Fable 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
1 participant
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.
For gHashTag/trios#1280
Opened by the Queen for queen-swift.