Keep host stop/start acceptance bounded - #228
Merged
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.
Objective
Make the real-manager host lifecycle runner measure stop/start and updater fencing directly, while keeping independent archival verification and interactive confirmation tests in their own gates.
Evidence
The first dev2 run found
host recovery statusfully inspecting encrypted backups for several minutes; the unconfirmedhost stopinvocation waited for a TTY prompt. Neither belongs ahead of a stop/start effect test. Existing CLI command-boundary tests already reject unconfirmed destructive operations. Recovery status remains a separate required row under Deployment #756. Source-only test change; no CLI runtime behavior or release tag changes.Acceptance
Rerun
TREESEED_HOST_LIFECYCLE_ACCEPTANCE=1 npm run accept:host-lifecycleagainst the published manager/CLI after Deployment #764 restores start ordering. Do not mark the complete matrix green until disposable-VM and dev2 receipts exist.Rollback
Revert this test-only change.
Refs: treeseed-ai/deployment#756