mission-control-install-from-githublisted

# Mission Control Install From GitHub ## Purpose Install or repair the Mission Control bridge assets, daemon bootstrap path, and headless runtime without requiring the standalone UI. The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager. ## Use when - The user says to install Mission Control from GitHub or from the current repo. - The user wants a headless-only setup. - The daemon, plugin bundle, or local skills need a repair pass. ## One-command workflow Use exactly one command as the primary install path: ```text python scripts/mission-control-manage.py install ``` Only fall back to `scripts/install-mission-control-plugin.ps1` or `.sh` when the user explicitly wants a shell-native wrapper. ## Workflow 1. Run `scripts/mission-control-manage.py install` as the primary workflow. 2. Let the unified workflow install Python packages for `apps/server` and `apps/mcp-server` unless the user explicitly asks to skip package setup. 3. Let the unified workflow sync the repo-local plugin bundle and Mission Control skills into Codex home. 4. Let the unified workflow write or update the managed `mcp_servers."mission-control"` Codex config entry. 5. Let the unified workflow run headless bootstrap, daemon verification, bridge verification, and Ollama/Codex runner reporting. 6. Tell the user to force-quit and reopen Codex and Claude Code before they try to use Mission Control, because plugin and MCP changes are no