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>

server/src/llm/prompts.rs

@@ -18,7 +18,7 @@ You have the following tools available:
 
 YOUR WORKFLOW:
 When the user requests a feature or change:
-1.  **Understand:** Read `.storkit/README.md` if you haven't already to understand the development process
+1.  **Understand:** Read `.huskies/README.md` if you haven't already to understand the development process
 2.  **Explore:** Use `read_file` and `list_directory` to understand the current codebase structure
 3.  **Implement:** Use `write_file` to create or modify files directly
 4.  **Verify:** Use `exec_shell` to run tests, linters, or build commands to verify your changes work
@@ -100,7 +100,7 @@ Ask the user:
 - Who are the target users?
 - What are the core features or goals?
 
-Then use `write_file` to write `.storkit/specs/00_CONTEXT.md` with:
+Then use `write_file` to write `.huskies/specs/00_CONTEXT.md` with:
 - **High-Level Goal** — a clear, concise summary of what the project does
 - **Core Features** — 3-5 bullet points
 - **Domain Definition** — key terms and roles
@@ -114,7 +114,7 @@ Ask the user:
 - What test runner(s)? (e.g. cargo test, pytest, jest, pnpm test)
 - What linter(s)? (e.g. clippy, eslint, biome, ruff)
 
-Then use `write_file` to write `.storkit/specs/tech/STACK.md` with:
+Then use `write_file` to write `.huskies/specs/tech/STACK.md` with:
 - **Overview** of the architecture
 - **Core Stack** — languages, frameworks, build tools
 - **Coding Standards** — formatting, linting, quality gates
@@ -131,7 +131,7 @@ Based on the tech stack answers, use `write_file` to write `script/test` — a b
 The script must start with `#!/usr/bin/env bash` and `set -euo pipefail`.
 
 ## Step 4: Project Configuration
-The scaffold has written `.storkit/project.toml` with example `[[component]]` sections. You must replace these examples with real definitions that match the project's actual tech stack.
+The scaffold has written `.huskies/project.toml` with example `[[component]]` sections. You must replace these examples with real definitions that match the project's actual tech stack.
 
 First, inspect the project structure to identify the tech stack:
 - Use `list_directory(".")` to see top-level files and directories
@@ -139,9 +139,9 @@ First, inspect the project structure to identify the tech stack:
 - Check subdirectories like `frontend/`, `backend/`, `app/`, `web/` for nested stacks
 - If you find a `package.json`, check whether `pnpm-lock.yaml`, `yarn.lock`, or `package-lock.json` exists to determine the package manager
 
-Then use `read_file(".storkit/project.toml")` to see the current content, keeping the `[[agent]]` sections intact.
+Then use `read_file(".huskies/project.toml")` to see the current content, keeping the `[[agent]]` sections intact.
 
-Finally, use `write_file` to rewrite `.storkit/project.toml` with real `[[component]]` entries. Each component needs:
+Finally, use `write_file` to rewrite `.huskies/project.toml` with real `[[component]]` entries. Each component needs:
 - `name` — component identifier (e.g. "backend", "frontend", "app")
 - `path` — relative path from project root (use "." for root, "frontend" for a frontend subdirectory)
 - `setup` — list of setup commands that install dependencies and verify the build (e.g. ["pnpm install"], ["cargo check"])