refactor!: rename project to bot-bottle

Assisted-by: Codex
2026-05-28 17:56:14 -04:00
parent 8875d8cc17
commit c08b09dc9f
200 changed files with 1271 additions and 1271 deletions
@@ -10,7 +10,7 @@ Support Claude and Codex agent providers while keeping agent files provider-agno

 ## Problem

-Today claude-bottle is hard-wired around Claude Code assumptions. When Claude runs out or is otherwise unavailable, the operator cannot spin up an equivalent Codex-backed bottle from the dashboard or `start` path. Agent files should remain purpose/guidance documents, while bottle files define security boundaries and provider/runtime choices.
+Today bot-bottle is hard-wired around Claude Code assumptions. When Claude runs out or is otherwise unavailable, the operator cannot spin up an equivalent Codex-backed bottle from the dashboard or `start` path. Agent files should remain purpose/guidance documents, while bottle files define security boundaries and provider/runtime choices.

 ## Goals / Success Criteria

@@ -24,7 +24,7 @@ Today claude-bottle is hard-wired around Claude Code assumptions. When Claude ru

 - Do not implement support for providers beyond Claude and Codex.
 - Do not move security boundaries into agent files.
- Do not allow custom Dockerfiles to remove or bypass required claude-bottle infrastructure.
+- Do not allow custom Dockerfiles to remove or bypass required bot-bottle infrastructure.
 - Do not add new runtime dependencies unless the existing Docker/Codex tooling cannot satisfy the minimum cut.

 ## Scope
@@ -63,7 +63,7 @@ agent_provider:

 ### Existing code touched

- `claude_bottle/manifest.py` for provider schema and role validation.
+- `bot_bottle/manifest.py` for provider schema and role validation.
 - Docker and smolmachines prepare/launch/provision paths for provider-specific image, command, auth, and state behavior.
 - Dashboard/start display paths so the selected provider is visible and usable.
 - README and PRD docs for provider/template configuration.