Create docs/queen-archive-rules.md stating when a chat may be archived after its pull request lands - #8
Merged
gHashTag merged 1 commit intoJul 31, 2026
Conversation
…g when a chat may be archived after its pull request lands
Uh oh!
There was an error while loading. Please reload this page.
gHashTag added a commit
that referenced
this pull request
Jul 31, 2026
The loop now runs end to end without a human touching it: the Queen briefs a worker, the worker writes, the branch is committed and pushed, she accepts, the pull request opens, the next poll merges it. Proven live, not in a harness - #8, queen/1096-create-docs-queen-archive-rules-md merged into feat/queen-supervisor, task state `merged`. Three things stood in the way of the last step, and the first two were the same mistake wearing different clothes. The pull request was opened against a hardcoded `dev`. A bee's branch is cut from HEAD, so basing it on a branch HEAD is not on produces a conflict that can never resolve - which is exactly what #6 and #7 are, both CONFLICTING and both unmergeable. Work lands where it came from, so the base is the checkout's current branch. Polling and merging still asked the issue's repository about a pull request number that only exists in the checkout's origin. Creating had already been corrected for that; the two steps after it had not, so even a mergeable pull request would never have been found. And the probe polled before the review, which is always before any pull request exists - so the merge half of the loop had never once been reached. It polls again after acceptance now. A run in between refused with "the worker committed nothing, so the pull request would be empty" - the worker had found the section already present. That is the refusal working, and it was only legible because the silent exits started logging last cycle. Verified: make, make cassettes, run_chat_sse_e2e.sh (422 checks).
github-actionsBot
deleted the
queen/1096-create-docs-queen-archive-rules-md
branch
August 2, 2026 03:27
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 freeto 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#1096
Opened by the Queen for queen-swift.