refactor!: rename project to bot-bottle

Assisted-by: Codex

scripts/demo-record.sh

@@ -11,8 +11,8 @@ if ! command -v vhs >/dev/null 2>&1; then
   exit 1
 fi
 
-if [ -z "${CLAUDE_BOTTLE_OAUTH_TOKEN:-}" ]; then
-  echo "demo-record: CLAUDE_BOTTLE_OAUTH_TOKEN is unset; claude inside the bottle will not auth" >&2
+if [ -z "${BOT_BOTTLE_OAUTH_TOKEN:-}" ]; then
+  echo "demo-record: BOT_BOTTLE_OAUTH_TOKEN is unset; claude inside the bottle will not auth" >&2
   exit 1
 fi
 

scripts/demo-setup.sh

@@ -1,8 +1,8 @@
 #!/usr/bin/env bash
 # Prepare the working directory to run the recorded demo via cli.py:
-#   - back up any existing claude-bottle.json so the user's real config
+#   - back up any existing bot-bottle.json so the user's real config
 #     isn't clobbered
-#   - install claude-bottle.demo.json as claude-bottle.json
+#   - install bot-bottle.demo.json as bot-bottle.json
 #   - create a dummy SSH identity at the path the demo manifest expects
 #   - pre-warm the bottle + git-gate images quietly so the recording
 #     doesn't spend its first 30s in BuildKit output
@@ -19,15 +19,15 @@ fi
 # Back up an existing local manifest (untouched if absent). Stored
 # alongside the manifest with a deterministic name so teardown can
 # find it without state files.
-if [ -f claude-bottle.json ]; then
-  cp claude-bottle.json claude-bottle.json.demo-backup
+if [ -f bot-bottle.json ]; then
+  cp bot-bottle.json bot-bottle.json.demo-backup
 fi
-cp claude-bottle.demo.json claude-bottle.json
+cp bot-bottle.demo.json bot-bottle.json
 
 # Dummy SSH identity — the git-gate validator wants a readable file at
 # the IdentityFile path. Contents don't matter for the demo: the
 # unreachable upstream means the gate never actually uses the key.
-fake_key_dir="$HOME/.cache/claude-bottle-demo"
+fake_key_dir="$HOME/.cache/bot-bottle-demo"
 mkdir -p "$fake_key_dir"
 chmod 700 "$fake_key_dir"
 printf 'not-a-real-key\n' > "$fake_key_dir/fake-key"
@@ -35,5 +35,5 @@ chmod 600 "$fake_key_dir/fake-key"
 
 # Build the image graph quietly so the recorded run shows only the
 # bottle launch and the four `!` probes, not BuildKit progress.
-docker build -q -t claude-bottle:latest . >/dev/null 2>&1 || true
-docker build -q -f Dockerfile.git-gate -t claude-bottle-git-gate:latest . >/dev/null 2>&1 || true
+docker build -q -f Dockerfile.claude -t bot-bottle-claude:latest . >/dev/null 2>&1 || true
+docker build -q -f Dockerfile.git-gate -t bot-bottle-git-gate:latest . >/dev/null 2>&1 || true

scripts/demo-teardown.sh

@@ -1,14 +1,14 @@
 #!/usr/bin/env bash
 # Undo what demo-setup.sh did. Restores any pre-existing
-# claude-bottle.json, removes the dummy SSH identity. Idempotent.
+# bot-bottle.json, removes the dummy SSH identity. Idempotent.
 
 set -euo pipefail
 
 cd "$(dirname "$0")/.."
 
-rm -f claude-bottle.json
-if [ -f claude-bottle.json.demo-backup ]; then
-  mv claude-bottle.json.demo-backup claude-bottle.json
+rm -f bot-bottle.json
+if [ -f bot-bottle.json.demo-backup ]; then
+  mv bot-bottle.json.demo-backup bot-bottle.json
 fi
 
-rm -rf "$HOME/.cache/claude-bottle-demo"
+rm -rf "$HOME/.cache/bot-bottle-demo"

scripts/demo.sh

@@ -14,9 +14,9 @@ set -euo pipefail
 
 cd "$(dirname "$0")/.."
 
-if [ -z "${CLAUDE_BOTTLE_OAUTH_TOKEN:-}" ]; then
+if [ -z "${BOT_BOTTLE_OAUTH_TOKEN:-}" ]; then
   cat <<'EOF' >&2
-demo: CLAUDE_BOTTLE_OAUTH_TOKEN is unset. The bottle launches claude,
+demo: BOT_BOTTLE_OAUTH_TOKEN is unset. The bottle launches claude,
 which needs the token to authenticate. Set it in your shell env (e.g.
 ~/.zshrc) — see README §Auth — then re-run.
 EOF