refactor!: rename project to bot-bottle

Assisted-by: Codex

docs/prds/0025-bottle-extends.md

@@ -28,7 +28,7 @@ silently absent from `staging` until someone notices.
 
 Issue #88 proposed inlining a `bottle_config:` block in agent files
 that would merge with (and override) the referenced bottle. That
-design lets a `$CWD/.claude-bottle/agents/<name>.md` file from a
+design lets a `$CWD/.bot-bottle/agents/<name>.md` file from a
 cloned repo redeclare egress routes, env mappings, and git remotes
 — breaking the existing security model where bottles are
 `$HOME`-only specifically so cloned repos can't influence them
@@ -93,7 +93,7 @@ egress:
 
 `extends:` is a string — the name of another bottle (without the
 `.md`). Required to be one of the bottles loaded from
-`$HOME/.claude-bottle/bottles/`. Self-reference (`extends: self`
+`$HOME/.bot-bottle/bottles/`. Self-reference (`extends: self`
 in `self.md`) and longer cycles die at parse.
 
 ### Merge rules
@@ -163,7 +163,7 @@ the full chain so operators can find the offending file.
 
 ### Trust boundary preservation
 
-Bottles continue to be loaded from `$HOME/.claude-bottle/bottles/`
+Bottles continue to be loaded from `$HOME/.bot-bottle/bottles/`
 only (`Manifest.from_md_dirs` is unchanged). The `extends:` field
 references another file in that same directory. No cwd-readable
 file gains the ability to declare or modify bottle config — the