refactor!: rename project to bot-bottle

Assisted-by: Codex

docs/research/git-gate-commit-approval.md

@@ -13,7 +13,7 @@ wrong in the user-intent sense, and there is no way to say so.
 
 ## Summary
 
-No off-the-shelf dashboard fits the shape claude-bottle needs
+No off-the-shelf dashboard fits the shape bot-bottle needs
 (per-bottle, host-local, integrated into a pre-receive rejection
 with approval feeding back into the gate's own decision). Gitleaks
 itself is a CLI with no UI and was declared **feature-complete** in
@@ -49,9 +49,9 @@ baseline), and recommends a direction.
 
 ## Question 1: Existing dashboards and control surfaces
 
-### Inside claude-bottle today
+### Inside bot-bottle today
 
-`claude_bottle/cli/` has `_common, cleanup, edit, info, init, list,
+`bot_bottle/cli/` has `_common, cleanup, edit, info, init, list,
 start` — nothing gate-specific. The gate appears only as a sidecar
 in `bottle_plan.py`'s preflight rendering. Rejections are written
 to the pre-receive hook's stderr (`echo "git-gate: gitleaks
@@ -76,14 +76,14 @@ TOML allowlist, and a roadmap that includes LLM-assisted
 classification and automatic secret revocation via provider APIs.
 Still CLI-shaped — no dashboard either.
 
-Relevant to claude-bottle in two ways:
+Relevant to bot-bottle in two ways:
 
 - The upstream direction of travel is *toward* agent-driven
   scanners, which makes "the bottle invokes a scanner and reports
   findings up" a supported pattern rather than a hack.
 - CEL is a richer expression language for filter entries than
   gitleaks's selector struct, which loosens the design space for
-  Option B (below). If claude-bottle ever swaps gitleaks for
+  Option B (below). If bot-bottle ever swaps gitleaks for
   Betterleaks, the approval-flow design should be expressible in
   both.
 
@@ -107,7 +107,7 @@ false-positive in its UI, and tracks remediation state. Designed
 for org-scale: one DefectDojo instance covers many repos and
 scanners.
 
-Shape mismatch for claude-bottle:
+Shape mismatch for bot-bottle:
 
 - DefectDojo's review state is *informational* — marking a finding
   as accepted in DefectDojo does not write to gitleaks's allowlist
@@ -137,7 +137,7 @@ premise is sandbox isolation.
 
 ### Bottom line
 
-No off-the-shelf dashboard fits claude-bottle's shape: per-bottle,
+No off-the-shelf dashboard fits bot-bottle's shape: per-bottle,
 host-local, integrated into a pre-receive rejection with the
 approval feeding back into the gate's own decision-making. The
 nearest open-source analogue (DefectDojo) is post-hoc and
@@ -334,7 +334,7 @@ project, and the vendor-side benchmark numbers (98.6% recall vs
 gitleaks's 70.4% on CredData) have not been independently
 reproduced in published sources.
 
-### What Betterleaks would add for claude-bottle
+### What Betterleaks would add for bot-bottle
 
 - **Detection coverage on encoded secrets.** Native handling of
   doubly- and triply-encoded matches. This matters in the
@@ -434,6 +434,6 @@ redesign.
 - [AWS example access key (`AKIAIOSFODNN7EXAMPLE`)](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-quotas.html)
   — documented placeholder safe to use in examples without
   triggering most secret scanners.
-- `claude_bottle/git_gate.py` — pre-receive hook implementation.
+- `bot_bottle/git_gate.py` — pre-receive hook implementation.
   Today: `gitleaks git --log-opts="$log_opts" --no-banner
   --redact`; no `--config`, no `--baseline-path`.