fix(development): owner-run boot recovery and stale PID protection - #167
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.
Implements #166; completes the CLI side of treeseed-ai/deployment#622.
Adds a fixed installed, non-root boot worker which re-reads manager-selected targets and uses the existing development start/overlay operations. Explicitly stopped sessions and released targets are not resumed. Process custody uses Linux boot/start identity and same-user process-group evidence so stale saved PIDs are neither reused nor signalled. Existing session-marked processes can be verified without inventing ownership.
Local lint and 138 tests pass, including PID reuse and foreign-session tests. Deployment scheduler and host acceptance remain required; this PR alone does not complete reboot recovery. RC72 is the matched installed worker payload. No production changes, purge, expiry, or credential writes.