Repository navigation
Migrate Foundry login services to non-root boot services - #73
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
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.
Add a host-specific, plan-first migration for the three existing Foundry services. System LaunchDaemons preserve program/state/network configuration and run as mike with explicit HOME. Idle preflight, original-definition backups, removal of duplicate login definitions, authenticated Forge readiness, Curator/Ollama readiness and automatic failure rollback protect existing state. No reboot, encryption changes, credential migration, media processing or mount changes.
2026-11-15: read-only plan passed on Foundry. Four focused tests pass for non-root config preservation, existing-service/root refusal, no changes on busy preflight and restored login definitions after failed system bootstrap. Administrator installation is pending the local password. FileVault unlock, pre-login SMB/Keychain availability and actual reboot acceptance remain explicit limits.
Refs #72; deployment acceptance stays open until observed.