fix(joblifecycle): released is the finish line, vanished is the orphan - #344
Merged
Conversation
The first steady-state hour said 119 vanished against 105 running and zero completed -- because the fleet's ordinary finish line is not the terminal map at all: the broker's reclaim releases a running intent once its execution lease ends, and the exporter read every such release as a disappearance worth suspicion. Where an intent was LAST SEEN now tells the stories apart: gone from running without a terminal record is released (~2 a minute, ordinary), gone from any earlier state is vanished -- it never provably ran anywhere, and the orphan name means something again. Claude-Session: https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF
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.
Deep-audit finding in the stream's first steady-state hour: 119 vanished / 105 running / 0 completed — the exporter labeled the fleet's ordinary finish (broker reclaim releasing a running intent after its lease ends, ~2/min) as
vanished, drowning the real orphan class.Disappearances now classify by last-seen state:
completed(terminal map, GARM's own record) ·released(gone from running — the ordinary finish) ·vanished(gone from a pre-running state — never provably ran; the class worth paging about later). Tests pin all three.internal/joblifecycleis not in the provider set — no release; thejob_lifecycledashboard's state breakdown picks the new label up unchanged, and its vanished panel becomes meaningful.https://claude.ai/code/session_01LsGid6U5RrQdFvJmvYdGCF