huskies: rename project from storkit to huskies

Rename all references from storkit to huskies across the codebase:
- .storkit/ directory → .huskies/
- Binary name, Cargo package name, Docker image references
- Server code, frontend code, config files, scripts
- Fix script/test to build frontend before cargo clippy/test
  so merge worktrees have frontend/dist available for RustEmbed

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

README.md

@@ -1,37 +1,37 @@
-# Storkit
+# Huskies
 
 A story-driven development server that manages work items, spawns coding agents, and runs them through a pipeline from backlog to done. Ships as a single Rust binary with an embedded React frontend.
 
 ## Getting started with Claude Code
 
-1. Download the storkit binary (or build from source — see below).
+1. Download the huskies binary (or build from source — see below).
 
 2. From your project directory, scaffold and start the server:
 
 ```bash
-storkit init --port 3000
+huskies init --port 3000
 ```
 
-This creates a `.storkit/` directory with the pipeline structure, `project.toml`, and `.mcp.json`. The `.mcp.json` file lets Claude Code discover storkit's MCP tools automatically.
+This creates a `.huskies/` directory with the pipeline structure, `project.toml`, and `.mcp.json`. The `.mcp.json` file lets Claude Code discover huskies' MCP tools automatically.
 
 3. Open a Claude Code session in the same project directory. Claude will pick up the MCP tools from `.mcp.json`.
 
-4. Tell Claude: "help me set up this project with storkit." Claude will walk you through the setup wizard — generating project context, tech stack docs, and test/release scripts. Review each step and confirm or ask to retry.
+4. Tell Claude: "help me set up this project with huskies." Claude will walk you through the setup wizard — generating project context, tech stack docs, and test/release scripts. Review each step and confirm or ask to retry.
 
 Once setup is complete, Claude can create stories, start agents, check status, and manage the full pipeline via MCP tools — no commands to memorize.
 
 ## Web UI
 
-Storkit also ships an embedded React frontend. Once the server is running, open `http://localhost:3000` to see the pipeline board, agent status, and chat interface.
+Huskies also ships an embedded React frontend. Once the server is running, open `http://localhost:3000` to see the pipeline board, agent status, and chat interface.
 
 ## Chat transports
 
-Storkit can be controlled via bot commands in **Matrix**, **WhatsApp**, and **Slack**. Configure a transport in `.storkit/bot.toml` — see the example files:
+Huskies can be controlled via bot commands in **Matrix**, **WhatsApp**, and **Slack**. Configure a transport in `.huskies/bot.toml` — see the example files:
 
-- `.storkit/bot.toml.matrix.example`
-- `.storkit/bot.toml.whatsapp-meta.example`
-- `.storkit/bot.toml.whatsapp-twilio.example`
-- `.storkit/bot.toml.slack.example`
+- `.huskies/bot.toml.matrix.example`
+- `.huskies/bot.toml.whatsapp-meta.example`
+- `.huskies/bot.toml.whatsapp-twilio.example`
+- `.huskies/bot.toml.slack.example`
 
 ## Prerequisites
 
@@ -46,7 +46,7 @@ Storkit can be controlled via bot commands in **Matrix**, **WhatsApp**, and **Sl
 cargo build --release
 ```
 
-The release binary embeds the frontend via `rust-embed`. Output: `target/release/storkit`.
+The release binary embeds the frontend via `rust-embed`. Output: `target/release/huskies`.
 
 For a static Linux binary (musl, zero dynamic deps):
 
@@ -73,7 +73,7 @@ cargo run -- --port 3000
 cd frontend && npm install && npm run dev
 ```
 
-Configuration lives in `.storkit/project.toml`. See `.storkit/bot.toml.*.example` for transport setup.
+Configuration lives in `.huskies/project.toml`. See `.huskies/bot.toml.*.example` for transport setup.
 
 ## Releasing