rename: Hornet → Baudbot (#16)

Author: benvinegar

.env.schema

@@ -1,4 +1,4 @@
-# Hornet agent configuration schema
+# Baudbot agent configuration schema
 # See CONFIGURATION.md for details on each variable.
 #
 # Secrets live at ~/.config/.env (600 perms, never committed).
@@ -48,16 +48,16 @@ AGENTMAIL_API_KEY=
 
 # Agent's monitored email address
 # @sensitive=false @type=email
-HORNET_EMAIL=
+BAUDBOT_EMAIL=
 
 # Shared secret for email sender authentication
 # @type=string
-HORNET_SECRET=
+BAUDBOT_SECRET=
 
 # Comma-separated sender email allowlist
 # @sensitive=false @type=string
 # @example="you@example.com,teammate@example.com"
-HORNET_ALLOWED_EMAILS=
+BAUDBOT_ALLOWED_EMAILS=
 
 # ── Sentry (optional) ───────────────────────────────────────────────────────
 
@@ -91,15 +91,15 @@ KERNEL_API_KEY=
 
 # Unix username of the agent
 # @sensitive=false @type=string
-HORNET_AGENT_USER=hornet_agent
+BAUDBOT_AGENT_USER=baudbot_agent
 
 # Agent's home directory
 # @sensitive=false @type=string
-HORNET_AGENT_HOME=/home/hornet_agent
+BAUDBOT_AGENT_HOME=/home/baudbot_agent
 
 # Path to admin-owned source repo (enables source repo write protection)
 # @sensitive=false @type=string
-HORNET_SOURCE_DIR=
+BAUDBOT_SOURCE_DIR=
 
 # ── Bridge ───────────────────────────────────────────────────────────────────
 

.github/workflows/ci.yml

@@ -27,7 +27,7 @@ jobs:
 
       - name: ShellCheck
         run: |
-          find bin/ setup.sh start.sh -type f \( -name '*.sh' -o -name 'hornet-safe-bash' -o -name 'hornet-docker' \) \
+          find bin/ setup.sh start.sh -type f \( -name '*.sh' -o -name 'baudbot-safe-bash' -o -name 'baudbot-docker' \) \
             | xargs shellcheck -s bash -S warning
 
   test:

.github/workflows/integration.yml

@@ -58,12 +58,12 @@ jobs:
 
       - name: Upload source
         run: |
-          tar czf /tmp/hornet-src.tar.gz \
+          tar czf /tmp/baudbot-src.tar.gz \
             --exclude=node_modules --exclude=.git .
           scp -o StrictHostKeyChecking=no -o BatchMode=yes \
             -i ~/.ssh/ci_key \
-            /tmp/hornet-src.tar.gz \
-            "root@${{ steps.droplet.outputs.DROPLET_IP }}:/tmp/hornet-src.tar.gz"
+            /tmp/baudbot-src.tar.gz \
+            "root@${{ steps.droplet.outputs.DROPLET_IP }}:/tmp/baudbot-src.tar.gz"
 
       - name: Setup and test
         run: |

AGENTS.md

@@ -1,6 +1,6 @@
-# Hornet — Agent Guidelines
+# Baudbot — Agent Guidelines
 
-Hornet is hardened infrastructure for running always-on AI agents. Source is admin-owned; agents run from deployed copies.
+Baudbot is hardened infrastructure for running always-on AI agents. Source is admin-owned; agents run from deployed copies.
 
 ## Repo Layout
 
@@ -9,8 +9,8 @@ bin/                        security & operations scripts
   deploy.sh                 stages source → /tmp → agent runtime (run as admin)
   security-audit.sh         24-check security posture audit
   setup-firewall.sh         iptables per-UID egress allowlist
-  hornet-safe-bash          shell command deny list (installed to /usr/local/bin)
-  hornet-docker             Docker wrapper (blocks privilege escalation)
+  baudbot-safe-bash          shell command deny list (installed to /usr/local/bin)
+  baudbot-docker             Docker wrapper (blocks privilege escalation)
   harden-permissions.sh     filesystem hardening (runs on boot)
   scan-extensions.mjs       extension static analysis
   redact-logs.sh            secret scrubber for session logs
@@ -46,29 +46,29 @@ See [CONFIGURATION.md](CONFIGURATION.md) for all env vars and how to obtain them
 
 ## Architecture: Source / Runtime Separation
 
-The admin owns the source (`~/hornet/`). The agent (`hornet_agent` user) owns the runtime. The agent **cannot read the source repo** — admin home is `700`.
+The admin owns the source (`~/baudbot/`). The agent (`baudbot_agent` user) owns the runtime. The agent **cannot read the source repo** — admin home is `700`.
 
 Deploy is a one-way push:
 ```
-admin: ~/hornet/bin/deploy.sh
-  → stages to /tmp/hornet-deploy.XXXXXX (world-readable)
-  → copies as hornet_agent via sudo -u
-  → stamps hornet-version.json + hornet-manifest.json (SHA256 hashes)
+admin: ~/baudbot/bin/deploy.sh
+  → stages to /tmp/baudbot-deploy.XXXXXX (world-readable)
+  → copies as baudbot_agent via sudo -u
+  → stamps baudbot-version.json + baudbot-manifest.json (SHA256 hashes)
   → cleans up staging dir
 ```
 
 Agent runtime layout:
 ```
-/home/hornet_agent/
+/home/baudbot_agent/
 ├── runtime/
 │   ├── start.sh                deployed launcher
 │   ├── bin/                    harden-permissions.sh, redact-logs.sh
 │   └── slack-bridge/           deployed bridge
 ├── .pi/agent/
 │   ├── extensions/             deployed extensions
 │   ├── skills/                 agent-owned (can modify freely)
-│   ├── hornet-version.json     deploy version (git SHA, timestamp)
-│   └── hornet-manifest.json    SHA256 hashes of all deployed files
+│   ├── baudbot-version.json     deploy version (git SHA, timestamp)
+│   └── baudbot-manifest.json    SHA256 hashes of all deployed files
 ├── workspace/                  project repos + git worktrees
 └── .config/.env                secrets (600 perms)
 ```
@@ -77,18 +77,18 @@ Agent runtime layout:
 
 ```bash
 # First-time install (interactive — handles everything)
-sudo ~/hornet/install.sh
+sudo ~/baudbot/install.sh
 
-# Edit source files directly in ~/hornet/
+# Edit source files directly in ~/baudbot/
 
 # Deploy to agent runtime
-~/hornet/bin/deploy.sh
+~/baudbot/bin/deploy.sh
 
 # Launch agent
-sudo -u hornet_agent ~/runtime/start.sh
+sudo -u baudbot_agent ~/runtime/start.sh
 
 # Or in tmux
-tmux new-window -n hornet 'sudo -u hornet_agent ~/runtime/start.sh'
+tmux new-window -n baudbot 'sudo -u baudbot_agent ~/runtime/start.sh'
 ```
 
 ## Running Tests
@@ -136,8 +136,8 @@ eval "$(bin/ci/droplet.sh create my-test 217410218 /tmp/ci_key.pub)"
 
 # Wait for SSH, upload source, run a CI script
 bin/ci/droplet.sh wait-ssh "$DROPLET_IP" /tmp/ci_key
-tar czf /tmp/hornet-src.tar.gz --exclude=node_modules --exclude=.git .
-scp -i /tmp/ci_key /tmp/hornet-src.tar.gz "root@$DROPLET_IP:/tmp/"
+tar czf /tmp/baudbot-src.tar.gz --exclude=node_modules --exclude=.git .
+scp -i /tmp/ci_key /tmp/baudbot-src.tar.gz "root@$DROPLET_IP:/tmp/"
 bin/ci/droplet.sh run "$DROPLET_IP" /tmp/ci_key bin/ci/setup-ubuntu.sh
 
 # Or SSH in for manual poking
@@ -153,9 +153,9 @@ The CI scripts (`bin/ci/setup-ubuntu.sh`, `bin/ci/setup-arch.sh`) run `install.s
 
 ## Security Notes
 
-- `tool-guard.ts` blocks: writes outside `/home/hornet_agent/`, writes to source repo, writes to protected runtime files, dangerous bash patterns (reverse shells, fork bombs, rm -rf /, etc.), credential exfiltration.
-- `hornet-safe-bash` (root-owned, `/usr/local/bin/`) is a second layer that blocks the same patterns at the shell level.
-- The firewall (`setup-firewall.sh`) restricts `hornet_agent`'s network egress to an allowlist.
+- `tool-guard.ts` blocks: writes outside `/home/baudbot_agent/`, writes to source repo, writes to protected runtime files, dangerous bash patterns (reverse shells, fork bombs, rm -rf /, etc.), credential exfiltration.
+- `baudbot-safe-bash` (root-owned, `/usr/local/bin/`) is a second layer that blocks the same patterns at the shell level.
+- The firewall (`setup-firewall.sh`) restricts `baudbot_agent`'s network egress to an allowlist.
 - `/proc` is mounted with `hidepid=2` — agent can only see its own processes.
 - Secrets in `~/.config/.env` are `600` perms, never committed.
 - Session logs are auto-redacted of API keys/tokens on boot.

CONFIGURATION.md

@@ -1,10 +1,10 @@
 # Configuration
 
-All secrets and configuration live in `~/.config/.env` on the agent's home directory (`/home/hornet_agent/.config/.env`). This file is `600` permissions and never committed to the repo.
+All secrets and configuration live in `~/.config/.env` on the agent's home directory (`/home/baudbot_agent/.config/.env`). This file is `600` permissions and never committed to the repo.
 
 ## Schema Validation
 
-Hornet uses [Varlock](https://varlock.dev) to validate environment variables at startup. The schema (`.env.schema`) is committed to the repo and deployed to `~/.config/.env.schema` alongside the secrets file. It defines types, required/optional status, and sensitivity for each variable.
+Baudbot uses [Varlock](https://varlock.dev) to validate environment variables at startup. The schema (`.env.schema`) is committed to the repo and deployed to `~/.config/.env.schema` alongside the secrets file. It defines types, required/optional status, and sensitivity for each variable.
 
 `start.sh` runs `varlock load` to validate before launching — the agent won't start with missing or malformed variables. The bridge uses `varlock run` to inject validated env vars. Varlock must be installed on the agent system (`brew install dmno-dev/tap/varlock` or `curl -sSfL https://varlock.dev/install.sh | sh -s`).
 
@@ -37,9 +37,9 @@ The agent also uses an SSH key (`~/.ssh/id_ed25519`) for git push. Setup generat
 | Variable | Description | How to get it |
 |----------|-------------|---------------|
 | `AGENTMAIL_API_KEY` | AgentMail API key | [app.agentmail.to](https://app.agentmail.to) — sign up and create an API key |
-| `HORNET_EMAIL` | Agent's email address | The email address the control agent monitors (e.g. `your-agent@agentmail.to`). Create the inbox via the AgentMail dashboard or let the agent create it on startup. |
-| `HORNET_SECRET` | Shared secret for email authentication | Generate a random string: `openssl rand -hex 32`. Senders must include this in their email for it to be processed. |
-| `HORNET_ALLOWED_EMAILS` | Comma-separated sender allowlist | Email addresses allowed to send tasks. Example: `you@example.com,teammate@example.com` |
+| `BAUDBOT_EMAIL` | Agent's email address | The email address the control agent monitors (e.g. `your-agent@agentmail.to`). Create the inbox via the AgentMail dashboard or let the agent create it on startup. |
+| `BAUDBOT_SECRET` | Shared secret for email authentication | Generate a random string: `openssl rand -hex 32`. Senders must include this in their email for it to be processed. |
+| `BAUDBOT_ALLOWED_EMAILS` | Comma-separated sender allowlist | Email addresses allowed to send tasks. Example: `you@example.com,teammate@example.com` |
 
 ## Optional Variables
 
@@ -67,18 +67,18 @@ The agent also uses an SSH key (`~/.ssh/id_ed25519`) for git push. Setup generat
 
 | Variable | Description | Default |
 |----------|-------------|---------|
-| `HORNET_AGENT_USER` | Unix username of the agent | `hornet_agent` |
-| `HORNET_AGENT_HOME` | Agent's home directory | `/home/$HORNET_AGENT_USER` |
-| `HORNET_SOURCE_DIR` | Path to admin-owned source repo | *(empty — set this to enable source repo write protection)* |
+| `BAUDBOT_AGENT_USER` | Unix username of the agent | `baudbot_agent` |
+| `BAUDBOT_AGENT_HOME` | Agent's home directory | `/home/$BAUDBOT_AGENT_USER` |
+| `BAUDBOT_SOURCE_DIR` | Path to admin-owned source repo | *(empty — set this to enable source repo write protection)* |
 
 ### Git Identity
 
 Set during `setup.sh` via env vars (or edit `~/.gitconfig` after):
 
 | Variable | Description | Default |
 |----------|-------------|---------|
-| `GIT_USER_NAME` | Git commit author name | `hornet-agent` |
-| `GIT_USER_EMAIL` | Git commit author email | `hornet-agent@users.noreply.github.com` |
+| `GIT_USER_NAME` | Git commit author name | `baudbot-agent` |
+| `GIT_USER_EMAIL` | Git commit author email | `baudbot-agent@users.noreply.github.com` |
 
 ### Bridge
 
@@ -104,9 +104,9 @@ SENTRY_CHANNEL_ID=C0987654321
 
 # Email
 AGENTMAIL_API_KEY=...
-HORNET_EMAIL=my-agent@agentmail.to
-HORNET_SECRET=<openssl rand -hex 32>
-HORNET_ALLOWED_EMAILS=you@example.com
+BAUDBOT_EMAIL=my-agent@agentmail.to
+BAUDBOT_SECRET=<openssl rand -hex 32>
+BAUDBOT_ALLOWED_EMAILS=you@example.com
 
 # Sentry (optional)
 SENTRY_AUTH_TOKEN=sntrys_...
@@ -116,7 +116,7 @@ SENTRY_ORG=my-org
 KERNEL_API_KEY=...
 
 # Tool guard
-HORNET_SOURCE_DIR=/home/your_username/hornet
+BAUDBOT_SOURCE_DIR=/home/your_username/baudbot
 ```
 
 ## Applying Configuration
@@ -125,8 +125,8 @@ After editing `~/.config/.env`:
 
 ```bash
 # Restart the agent to pick up changes
-sudo -u hornet_agent pkill -u hornet_agent
-sudo -u hornet_agent ~/runtime/start.sh
+sudo -u baudbot_agent pkill -u baudbot_agent
+sudo -u baudbot_agent ~/runtime/start.sh
 ```
 
 The bridge and all sub-agents load `~/.config/.env` on startup. If varlock is installed, variables are validated against `.env.schema` before injection.