refactor!: rename project to bot-bottle

Assisted-by: Codex

docs/prds/0020-start-and-attach-from-dashboard.md

@@ -63,7 +63,7 @@ captures full-merged logs per bottle (PRD 0018). It already
    → restore`, matching the existing editor-flow pattern.
 3. On launch success, the dashboard performs a handoff (option
    1 from the research doc): `curses.endwin()` → `docker exec
-   -it claude-bottle-<slug> claude --dangerously-skip-permissions`
+   -it bot-bottle-<slug> claude --dangerously-skip-permissions`
    → on exit, `stdscr.refresh()` and re-render with the new
    bottle in the agents pane.
 4. The bottle's lifetime is owned by the dashboard process, NOT
@@ -268,7 +268,7 @@ dashboard started this session, the dashboard holds the
 `bottle.exec_claude(...)`. For an agent it discovered via
 `list_active_slugs` (previous-dashboard or external start),
 the dashboard synthesizes a one-shot `DockerBottle` from the
-slug — container name is `claude-bottle-<slug>`, no prompt
+slug — container name is `bot-bottle-<slug>`, no prompt
 path because the agent's claude config already has `--append-
 system-prompt-file` baked in from the original launch —
 and runs the same exec. Either way, Enter drops to
@@ -284,7 +284,7 @@ agents pane.
 `x` on a non-owned agent (discovered via `list_active_slugs`
 but not in `bottles` dict): no-op with status hint pointing
 at `./cli.py cleanup` (the existing path that tears down
-ANY claude-bottle compose project plus reaps state dirs).
+ANY bot-bottle compose project plus reaps state dirs).
 
 ### Dashboard quit
 
@@ -392,5 +392,5 @@ Sized for one PR each.
 - `docs/research/claude-code-pane-in-dashboard.md` — option 1
   (handoff) is what `attach_claude` implements here; options 2
   / 3 are out of scope for this PRD
-- `claude_bottle/cli/start.py:_launch_bottle` — the function
+- `bot_bottle/cli/start.py:_launch_bottle` — the function
   chunk 1 extracts the prepare + attach pieces out of