Repository navigation
Fix managed restart custody and readiness adoption - #292
Merged
Merged
Conversation
This was referenced Oct 9, 2026
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.
Refs #274; SDK #376.
Refresh the current manifest runtime before a non-plan restart, and use the existing manager-custody endpoint adoption path without redundant host-port probes. Preserve read-only plan, exact selection mode, failed refresh/build history and caller-owned port readiness.
Adds two unit regressions and one real native Git/caller-build integration regression with original golden scene/verifier bindings. Focused originals: 25/25 pass following 3 reproduced failures. Initial complete run failed on dirty index custody and missing native metadata allowlist; retained and corrected, not waived. Fresh complete suites and coded components must pass here before merge.
No new schema, runner, dependency, privilege, deadline, tag, UI or deployment. Temporary remote branch will be deleted after checked staging→main merges.