fix(observer): separate visible image maintenance - #88
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
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.
Outcome
Observer schema v11 reports exact
gha-image-builder-<12hex>andgha-image-smoke-<12hex>inventory separately from orphan GitHub job runners. Legitimate stage-only image maintenance remains visible but no longer makes the production platform unhealthy; malformed lookalikes remain blockers.Image smoke output now reports
startup_mode: cold-onlyinstead of the retiredwarm_agentlabel. Recipe bytes and immutable b10/b4 aliases do not change; only smoke evidence changes.Runtime evidence
The real b10 stage-only build exposed one visible builder as
orphan_instances=1and temporary HTTP 503 while the real queue was empty. No synthetic GitHub job was created. After the builder/smoke teardown, health returned to 200 automatically.Boundaries
No provider, GARM, queue, image recipe, runner, credential, or trust change.