Repository navigation
Fix bounded natural replies to retained agent questions - #52
Merged
Merged
Conversation
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
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.
Natural replies can be blocked when unrelated retained tool output pushes an execution journal beyond its conversation-read bound. Select only the exact current question ancestry and gate its row and byte limits in the same SQL statement snapshot, preserving question, actor and execution authority.
Put ordinary GitHub dialogue first in the SCM guide and distinguish the conditional native tool registry from ordinary CLI permissions and the qualified source-only route. Regenerate the controlled walkthrough for version 0.2.38.
Validation:126 related host tests, full 270-module typing and Python lint/format; Studio 590 unit tests, lint/types/format/build; 80 controlled capture cases / 532 verified images; strict docs/discovery, 19 Python docs checks and 10 Node checks. The standalone public PostgreSQL regression passed in a fresh owned fixture (1 passed, no skips); exact source hashes, empty schemas/sessions, closed port and owned process cleanup were verified. No real model, application GitHub post or CRM effect was performed by this qualification. Required GitHub CI remains a merge gate.