docs: check dispatcher progress on every App heartbeat - #167
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
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.
An empty native App handoff queue previously ended a heartbeat before it checked the dispatcher, so completion of a read-only validator could leave ready work idle during the fifteen-minute investigation interval. The controller now checks both signals every pass, requests canonical continuation for ready work, and throttles only repeated deep investigation.
The live heartbeat was updated through the native automation API. This change records the same policy in the installed runbook, retaining single-owner execution, pause, validation and audit gates.
Validation: independent review approved the runbook; diff check and secret scan passed. Documentation only.