Harden Mission Control launch surface

.env.example

@@ -15,7 +15,7 @@ CODEX_MISSION_CONTROL_HOME=
 CODEX_TELEGRAM_WORKDIR=
 CODEX_BIN=/Applications/Codex.app/Contents/Resources/codex
 CODEX_TELEGRAM_SANDBOX=danger-full-access
-CODEX_TELEGRAM_MODEL=gpt-5.5
+CODEX_TELEGRAM_MODEL=
 CODEX_TELEGRAM_REASONING_EFFORT=high
 CODEX_TELEGRAM_SPEED=standard
 CODEX_TELEGRAM_REPLY_STYLE=brief

INSTALL.md

@@ -0,0 +1,97 @@
+# Install
+
+Codex Mission Control is macOS-first and local-only.
+
+## Requirements
+
+- macOS
+- Codex Mac app installed and signed in
+- Python 3 available as `python3`
+- optional: Telegram bot token from `@BotFather` for phone control
+
+## Safe First Run
+
+```bash
+git clone https://github.com/dicnunz/codex-mission-control.git
+cd codex-mission-control
+./scripts/install.sh
+```
+
+The installer:
+
+1. checks macOS, Python, and Codex CLI,
+2. creates `~/Codex Mission Control`,
+3. discovers projects under standard Mac folders,
+4. links `cmc` into `~/.local/bin` when possible,
+5. previews project `AGENTS.md` adoption unless you choose to write it,
+6. optionally installs the Telegram Relay,
+7. runs doctor and writes the local dashboard.
+
+Mission Control does not move project folders. The hub stores symlinks, markdown ops files, lane locks, and outboxes.
+
+## Project Instructions
+
+Preview the exact project instruction blocks:
+
+```bash
+cmc adopt
+```
+
+Write them with backups:
+
+```bash
+cmc adopt --write
+```
+
+Existing `AGENTS.md` files are backed up as `AGENTS.md.cmc-backup-*`.
+
+## Dashboard
+
+```bash
+cmc dashboard
+```
+
+The dashboard is a private local HTML file under `~/Library/Application Support/CodexRelay/state/`.
+
+## Telegram Relay
+
+Install later with:
+
+```bash
+./cmc relay install
+```
+
+Relay is a private Telegram bot pointed at your Mac:
+
+```text
+Telegram -> LaunchAgent -> Codex CLI -> Mission Control
+```
+
+Treat it like SSH into your Mac through Telegram. Keep the bot token private.
+
+## Runtime Files
+
+```text
+~/Codex Mission Control
+~/Library/Application Support/CodexRelay
+~/Library/LaunchAgents/com.codexrelay.agent.plist
+```
+
+The `CodexRelay` runtime name is kept for upgrade compatibility.
+
+## Verify
+
+```bash
+cmc status
+cmc doctor
+cmc lanes
+./scripts/doctor.sh
+```
+
+## Uninstall Relay
+
+```bash
+./scripts/uninstall.sh
+```
+
+This removes the LaunchAgent plist. Runtime files remain so you can inspect or delete them manually.

LAUNCH.md

@@ -46,6 +46,8 @@ mac-first
 no hosted account
 
 github.com/dicnunz/codex-mission-control
+
+looking for 10 Codex-heavy Mac users to try the install and tell me the first blocker
 ```
 
 Attach `assets/social-card.png` or the 45-second demo video.
@@ -76,6 +78,7 @@ cd codex-mission-control
 it sets up the local hub first
 telegram is optional
 projects stay where they are
+AGENTS.md adoption is preview-first
 ```
 
 Relay:
@@ -116,7 +119,7 @@ Keep it under 45 seconds:
 5. Try a second BROWSER claim and show held: BROWSER.
 6. Open the local dashboard.
 7. Run cmc packet.
-8. Show Telegram /mission status.
+8. Show Telegram /mission status if Relay is installed.
 ```
 
 No theory. No architecture talk. Prove the collision layer.