Land Phase 0 launch chain: SSH -> desktop Terminal -> claude -> phone

Phase 0 proven by hand (N=3) across multiple rooms.

- scripts/gui-launch.sh: open a desktop Terminal via osascript so claude runs in
  the GUI session (login Keychain + real TTY), avoiding a long-lived token (D11).
- scripts/launch-claude.sh: name the session `claude -n "<repo> - <topic>"` so
  Remote Control's phone conversation index is readable.
- .env.example: bot credential schema (real .env stays gitignored).
- AGENTS.md / ROADMAP.md: D11, Phase 0 results, Phase 1 carry-overs.

scripts/launch-claude.sh

@@ -21,4 +21,17 @@ fi
 # Fail loud on a bad directory — never launch Claude in the wrong place.
 cd "$repo_dir" || { print -u2 "launch-claude: no such repo dir: $repo_dir"; exit 1; }
 
-exec claude "$prompt"
+# Name the session "<repo> - <topic>" so it's identifiable in Remote Control's
+# conversation index on the phone. Topic defaults to a trimmed slice of the message;
+# the Phase-1 bot can override it with a curated topic via $MB_SESSION_NAME.
+repo_name="${${repo_dir%/}:t}"
+if [[ -n "$MB_SESSION_NAME" ]]; then
+  session_name="$MB_SESSION_NAME"
+else
+  topic="${prompt//$'\n'/ }"          # collapse newlines to keep the name one line
+  topic="${topic[1,60]}"              # cap length for a tidy index entry
+  [[ ${#prompt} -gt 60 ]] && topic="${topic}…"
+  session_name="${repo_name} - ${topic}"
+fi
+
+exec claude -n "$session_name" "$prompt"