Gate behavior probes on runtime health - #65
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
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.
Root cause\n\nThe managed-image behavior test still treated bridgeConnected as execution readiness. In the 0.12.49 run, the Hermes bridge connected while its runtime endpoint was still cold; both probes then failed immediately with Runtime delivery failed: fetch failed.\n\n## Fix\n\n- Poll one agent projection per interval.\n- Require both bridgeConnected and runtimeHealthy before sending behavior prompts.\n- Report both values on timeout.\n- Rename the check to runtime-warmup to describe the real gate.\n\nThe OpenClaw leg already passed. This change makes the test consume the runtime-health signal introduced by the product fix instead of reproducing the old transport-equals-health bug.