refactor!: rename project to bot-bottle

Assisted-by: Codex

docs/research/bash-vs-python-vs-go.md

@@ -1,6 +1,6 @@
 # Implementation language: bash vs. Python vs. Go
 
-Research into which runtime claude-bottle should be implemented in, given
+Research into which runtime bot-bottle should be implemented in, given
 where the project is today (~1250 lines, Python, mostly orchestration of
 `docker` / `flyctl` / `ssh`). The project started in bash and was rewritten
 to Python; this note evaluates whether either of the other two options
@@ -10,7 +10,7 @@ would be a better fit going forward.
 
 Stay on Python. Switch to Go if and when distribution friction becomes the
 dominant pain — i.e., when bug reports about Python interpreter / venv
-behavior start outweighing bug reports about claude-bottle itself. Bash is
+behavior start outweighing bug reports about bot-bottle itself. Bash is
 not the right tool at the project's current size; reverting would be a
 regression.
 
@@ -54,7 +54,7 @@ The relevant criteria, in roughly the order they bite:
 
 ## Bash
 
-Right tool *if the project stays under ~500 lines*. claude-bottle has
+Right tool *if the project stays under ~500 lines*. bot-bottle has
 already crossed that threshold (~1250 lines), and the orchestration is no
 longer "stitch CLIs together" — it has manifest validation, env-var
 resolution, network and sidecar lifecycle, and SSH provisioning. Bash
@@ -119,7 +119,7 @@ Costs:
 
 Stay on Python. The signal to watch for, before reconsidering, is bug
 reports about Python interpreter or venv behavior outnumbering bug reports
-about claude-bottle's actual logic. Until that pattern shows up, the Go
+about bot-bottle's actual logic. Until that pattern shows up, the Go
 rewrite isn't paying for itself.
 
 Independent of language: invest in the backend abstraction now. A clean