feat: track enabled and disabled runtime targets - #321
Merged
Conversation
Co-Authored-By: Codex <noreply@openai.com>
Pigbibi
force-pushed
the
codex/automated-target-lifecycle
branch
from
August 30, 2026 02:10
e0709f3 to
f6adb0b
Compare
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.
Adds a separate, read-only runtime-target lifecycle snapshot for the unified control plane.\n\nEnabled targets continue guard/heartbeat monitoring. Disabled targets remain visible in no-order validation rather than being confused with a missing execution report. Monitoring failures produce PARKED only; this change cannot enable targets, change execution modes, access broker credentials, or submit orders.