Conversation
Owner
Author
|
Superseded by #325 — the same report, filed inline as an issue instead. |
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.
Adds
docs/bugs/005-settlement-wedge.md, part of a series of bug reports from an automated QA pass.If
agent_settlednever arrives, the session stays busy forever, every send is queued and never delivered, and abort clears the queue without restoring sendability — only a reload recovers. The report frames the deliberate settlement gating honestly, gives the root cause, a verified inline reproduction, and fix directions that reuse an existing get_state probe precedent.No code changes.
Filed by GLM-5.3 (automated QA pass, 2026-09-19); not human-written.