refactor!: rename project to bot-bottle

Assisted-by: Codex

docs/research/git-secret-scanning-hardening.md

@@ -1,6 +1,6 @@
 # Git secret scanning as further hardening
 
-Research into whether claude-bottle should add a secret-scanning step to
+Research into whether bot-bottle should add a secret-scanning step to
 its git workflow — both on the host repo and (potentially) inside
 bottles — and what tools exist for it. Motivated by the threat model
 below: a secret accidentally `git push`ed to a public remote is
@@ -14,7 +14,7 @@ of defense-in-depth that doesn't replace any existing control
 (`.gitignore`, environment-variable hygiene, network egress guards) but
 catches the one case where everything else fails: a credential ending
 up in a tracked file or commit message and being pushed to a public
-remote. For claude-bottle specifically, `gitleaks` is the clearest fit
+remote. For bot-bottle specifically, `gitleaks` is the clearest fit
 — Go binary, MIT, scans full history including commit messages, runs
 fully offline, and integrates with the existing `.githooks/` directory
 without adding a new runtime.
@@ -83,12 +83,12 @@ suspicious, let me close without merging," the bytes that mattered are
 already on the attacker's box. Detection has to be at *commit* time
 (or *push* time at the latest), not at review time.
 
-### Why this matters for claude-bottle
+### Why this matters for bot-bottle
 
 Two surfaces are exposed:
 
-1. **The claude-bottle repo itself.** Development happens on a host
-   with `CLAUDE_BOTTLE_OAUTH_TOKEN`, Gitea tokens, and other
+1. **The bot-bottle repo itself.** Development happens on a host
+   with `BOT_BOTTLE_OAUTH_TOKEN`, Gitea tokens, and other
    credentials in the environment. A fixture, test snapshot, log
    capture, or pasted-in debug output could carry one of them into a
    tracked file. The repo's Gitea remote is private, but mirrors or
@@ -209,7 +209,7 @@ it with a separate message-scanning step.
 
 ## Recommended path forward
 
-In priority order, for the host claude-bottle repo:
+In priority order, for the host bot-bottle repo:
 
 1. **One-time retro scan** with gitleaks:
    `gitleaks detect --source . --log-opts="--all" --redact`.