feat: scaffold SvelteKit project with Tailwind, TypeScript, ESLint, Prettier

Initialize the llm-multiverse-ui project with:
- SvelteKit + Svelte 5 (runes mode enabled)
- Tailwind CSS v4 via @tailwindcss/vite plugin
- TypeScript strict mode
- ESLint 9 flat config with svelte and typescript-eslint plugins
- Prettier with svelte plugin
- Directory structure: src/lib/components/, src/lib/services/
- All required scripts: dev, build, preview, lint, format, check

Closes #1

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/commands/auto-dev.md

@@ -10,6 +10,7 @@ You are the **Auto Dev Orchestrator**. You run the full development pipeline in
 ## Auto-Merge Eligibility
 
 An issue is **auto-merge eligible** (no user approval needed) if ALL of these are true:
+
 - The issue does NOT have a `workflow:manual-review` label
 - All quality gates pass
 - Code review by the review agent returns APPROVE (no critical/major findings)
@@ -35,6 +36,7 @@ Run the story selection logic (same as `/project:select-story`):
 7. Present the top candidate to the user with issue number, title, milestone, labels, and summary
 
 **PAUSE HERE** — Wait for user confirmation before proceeding. The user may:
+
 - Confirm the selection
 - Pick a different issue number
 - Say "stop" to end the loop
@@ -87,6 +89,7 @@ Run the code review logic autonomously (same as `/project:code-review`):
 Based on verification AND code review results:
 
 **On PASS (verification passes AND code review APPROVE):**
+
 1. Update plan status to `COMPLETED`
 2. Push the feature branch to origin
 3. Create a Gitea pull request targeting `main`
@@ -103,11 +106,13 @@ Based on verification AND code review results:
 8. Loop back to Phase 1
 
 **On FAIL (attempt 1):**
+
 1. Update plan status to `RETRY`
 2. Append retry instructions to the plan (what failed and how to fix it)
 3. Loop back to Phase 3 (re-implement with retry instructions)
 
 **On FAIL (attempt 2):**
+
 1. Update plan status to `BLOCKED`
 2. Add `workflow:manual` label to the Gitea issue
 3. Inform the user: "Story #NNN blocked after 2 attempts. Marked for manual review."
@@ -116,6 +121,7 @@ Based on verification AND code review results:
 ### Phase 7 — MILESTONE CHECK
 
 After each completed story, check if all issues in the story's milestone are now closed. If so:
+
 1. Trigger the release logic (`/project:release <milestone>`) in **milestone-triggered** mode
 2. The release PR is created but NOT merged — it awaits user approval
 3. Inform the user: "All issues in <milestone> completed. Release PR created for your approval."
@@ -124,6 +130,7 @@ After each completed story, check if all issues in the story's milestone are now
 ### Phase 8 — PERIODIC REFACTORING CHECK
 
 After every 5 completed stories (tracked by the `completed` counter):
+
 1. Run the refactoring review logic (`/project:refactor-review`)
 2. Create refactoring issues as needed
 3. Close resolved tech debt issues
@@ -133,11 +140,13 @@ After every 5 completed stories (tracked by the `completed` counter):
 ## Stop Conditions
 
 Stop the loop when any of these occur:
+
 - The user says "stop"
 - No eligible issues remain (all are completed, blocked, or have unmet dependencies)
 - 3 consecutive stories are BLOCKED
 
 When stopping, display a summary of work completed:
+
 - Stories completed (with PR links)
 - Stories auto-merged vs awaiting review
 - Stories blocked (with failure reasons)
@@ -149,6 +158,7 @@ When stopping, display a summary of work completed:
 ## Tracking
 
 Maintain a running tally during the session:
+
 - `completed`: list of issue numbers with PR links
 - `auto_merged`: list of issue numbers that were auto-merged
 - `awaiting_review`: list of issue numbers with PRs awaiting manual review