emrg: document TUI queue requeue re-tracking in quick-ref (review-fix parity) - #697
Merged
Merged
Conversation
… parity) The GUI queue-injection quick-ref entry documents the review fix (was_busy || i > 0 re-tracking, "同 #695") but the TUI entry — merged earlier — still describes only the initial implementation. A future cycle reading the TUI entry alone could misread the final state and re-discover the re-tracking as a bug. Append the review-fix note (9cb4194) to the TUI entry so both client-side entries carry the same final-state description.
argszero
commented
Aug 11, 2026
argszero
left a comment
Owner
Author
There was a problem hiding this comment.
✅ LGTM — cycle (doc-only quick-ref fix; diff reviewed: TUI queue-injection entry now documents the was_busy || i > 0 re-tracking fix (9cb4194) matching the GUI entry — prevents a future cycle from re-discovering it as a bug; no literal {var} braces added (placeholder guard clean — the 3 matches are pre-existing #569/#592/#623 lines); pytest 705 local green; CI pending)
argszero
commented
Aug 11, 2026
argszero
left a comment
Owner
Author
There was a problem hiding this comment.
✅ LGTM — cycle (CI PASS run 31495932246; diff reviewed: single-line quick-ref fix appending the review-fix note (9cb4194, was_busy or i > 0 re-tracking) to the TUI queue-injection entry, matching the GUI entry's description — no literal braces, placeholder guard clean, 705 pytest green locally)
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.
Summary
Doc-accuracy fix for the evolution prompt quick-ref: the TUI queue-injection entry (#695, merged earlier) described only the initial implementation, while the GUI entry (#696, merged later) documents the review fix —
was_busy || i > 0re-tracking of re-sent queued messages (commit 9cb4194) — as "同 #695" (same as #695).The TUI entry is the primary reference for that fix, so a future evolution cycle reading it alone could misread the final state and "re-discover" the re-tracking as a bug.
Change
emrg/server/evolution_prompt.md— append the review-fix note (R869 ❌:was_busycaptured pre-loop → M2+ re-sends re-queued but untracked → silently lost; fix: re-track each re-send whenwas_busy or i > 0, steer_committed removes injected ids, next queued_requeue re-sends the rest — converges) to the TUI queue-injection entry, matching the GUI entry's description.Verification
{var}braces in the entry)emrg --helpOK