feat(observe): expose terminal tombstone lifecycle - #202
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.
Makes queue-v5 protection observable and closes a natural recovery gap found during rollout.\n\n- observer exports current terminal tombstone count and next expiry\n- GARM emits a structured event when delayed JobAssigned is actually suppressed\n- scheduler recovery resumes an fsync-backed active attempt after its process is interrupted by the manager restart; if progress already happened it finalizes without another restart, otherwise it repeats the checkpoint-first idempotent sequence\n\nGARM v0.2.1-nddev.83 reproducibly builds at f9594a5ff67643a3b1f9e3357db6a96b45e1ec83797ff9ad0189302a264bb238.\n\nVerification: make verify; full derivative race/build completed locally before binding the expected digest.