@hatchway/cli 0.50.55 → 0.50.57

package/dist/index.js

@@ -4,12 +4,12 @@ import { query } from '@anthropic-ai/claude-agent-sdk';
 import { Codex } from '@openai/codex-sdk';
 import { a as streamLog, f as fileLog, i as initRunnerLogger, s as setFileLoggerTuiMode, b as getLogger } from './chunks/runner-logger-instance-Dj_JMznn.js';
 import { config as config$1 } from 'dotenv';
-import path$1, { resolve, relative, isAbsolute, dirname, join as join$1 } from 'node:path';
+import path$1, { resolve, relative, isAbsolute, dirname, join } from 'node:path';
 import { fileURLToPath } from 'node:url';
-import { existsSync, mkdirSync, readFileSync, writeFileSync } from 'node:fs';
+import { existsSync, readdirSync, mkdirSync, readFileSync, writeFileSync } from 'node:fs';
 import { readFile } from 'fs/promises';
 import * as path from 'path';
-import { join } from 'path';
+import { join as join$1 } from 'path';
 import WebSocket$1, { WebSocketServer, WebSocket } from 'ws';
 import { drizzle } from 'drizzle-orm/node-postgres';
 import pg from 'pg';
@@ -130,14 +130,80 @@ function createProjectScopedPermissionHandler(projectDirectory) {
 }
 
 /**
- * Skills management for Claude Code projects.
+ * Skills provisioning for the Claude Agent SDK.
  *
- * This module handles copying bundled skills to project directories
- * so they can be loaded by Claude Code when running in that project.
+ * Platform-level skills are packaged as a local plugin that the SDK
+ * discovers via the `plugins` option. The plugin lives within the runner at:
+ *   src/lib/skills/platform-plugin/  (dev)
+ *   dist/lib/skills/platform-plugin/ (built)
+ *
+ * The plugin contains:
+ *   .claude-plugin/plugin.json   - Plugin manifest
+ *   skills/<name>/SKILL.md       - Individual skill files
+ *
+ * The SDK loads skill descriptions into context and invokes full content
+ * on-demand when the agent determines a skill is relevant.
  */
-// Get the directory of this module
-const __filename$2 = fileURLToPath(import.meta.url);
-dirname(__filename$2);
+const __filename$3 = fileURLToPath(import.meta.url);
+const __dirname$3 = dirname(__filename$3);
+const CODEX_ONLY_SKILLS = new Set(['todo-workflow-codex']);
+/**
+ * Find the platform plugin directory.
+ */
+function findPluginDir() {
+    const candidates = [
+        join(__dirname$3, 'skills', 'platform-plugin'), // dev: src/lib/skills/platform-plugin/
+        join(__dirname$3, 'lib', 'skills', 'platform-plugin'), // bundle: dist/lib/skills/platform-plugin/
+        join(__dirname$3, '..', 'src', 'lib', 'skills', 'platform-plugin'), // bundle fallback
+    ];
+    for (const dir of candidates) {
+        const manifestPath = join(dir, '.claude-plugin', 'plugin.json');
+        if (existsSync(manifestPath)) {
+            return dir;
+        }
+    }
+    return null;
+}
+let _pluginDir;
+/**
+ * Get the absolute path to the platform plugin directory.
+ * Pass this to the SDK's `plugins` option as `{ type: "local", path: <this> }`.
+ */
+function getPlatformPluginDir() {
+    if (_pluginDir === undefined) {
+        _pluginDir = findPluginDir();
+        if (_pluginDir) {
+            const names = listBundledSkills();
+            process.stderr.write(`[skills] Platform plugin: ${_pluginDir} (${names.length} skills: [${names.join(', ')}])\n`);
+        }
+        else {
+            process.stderr.write('[skills] Platform plugin directory not found\n');
+            Sentry.logger.error('Platform plugin directory not found — agent will run without core skills', {
+                candidatePaths: [
+                    join(__dirname$3, 'skills', 'platform-plugin'),
+                    join(__dirname$3, 'lib', 'skills', 'platform-plugin'),
+                    join(__dirname$3, '..', 'src', 'lib', 'skills', 'platform-plugin'),
+                ].join(', '),
+                __dirname: __dirname$3,
+            });
+        }
+    }
+    return _pluginDir;
+}
+/**
+ * List available skill names from the plugin.
+ */
+function listBundledSkills() {
+    const pluginDir = _pluginDir ?? findPluginDir();
+    if (!pluginDir)
+        return [];
+    const skillsPath = join(pluginDir, 'skills');
+    if (!existsSync(skillsPath))
+        return [];
+    return readdirSync(skillsPath, { withFileTypes: true })
+        .filter(d => d.isDirectory() && !CODEX_ONLY_SKILLS.has(d.name))
+        .map(d => d.name);
+}
 
 var __defProp$1 = Object.defineProperty;
 var __getOwnPropNames$1 = Object.getOwnPropertyNames;
@@ -197,21 +263,21 @@ var init_tags$1 = __esm$1({
         inputType: "select",
         options: [
           {
-            value: "claude-sonnet-4-5",
-            label: "Claude Sonnet 4.5",
+            value: "claude-sonnet-4-6",
+            label: "Claude Sonnet 4.6",
             description: "Anthropic Claude - Balanced performance and speed",
             logo: "/claude.png",
             provider: "claude-code",
-            model: "claude-sonnet-4-5",
+            model: "claude-sonnet-4-6",
             sdk: "agent"
           },
           {
-            value: "claude-opus-4-5",
-            label: "Claude Opus 4.5",
+            value: "claude-opus-4-6",
+            label: "Claude Opus 4.6",
             description: "Anthropic Claude - Most capable for complex tasks",
             logo: "/claude.png",
             provider: "claude-code",
-            model: "claude-opus-4-5",
+            model: "claude-opus-4-6",
             sdk: "agent"
           },
           {
@@ -235,10 +301,10 @@ var init_tags$1 = __esm$1({
           {
             value: "factory-droid-opus",
             label: "Factory Droid (Opus)",
-            description: "Factory Droid SDK with Claude Opus 4.5",
+            description: "Factory Droid SDK with Claude Opus 4.6",
             logo: "/factory.svg",
             provider: "factory-droid",
-            model: "claude-opus-4-5-20251101",
+            model: "claude-opus-4-6-20251101",
             sdk: "droid"
           },
           {
@@ -908,7 +974,7 @@ function setTemplatesPath$1(path) {
   cachedConfig$2 = null;
 }
 function getTemplatesPath$2() {
-  const path = configuredPath$1 ?? process.env.TEMPLATES_JSON_PATH ?? join(process.cwd(), "templates.json");
+  const path = configuredPath$1 ?? process.env.TEMPLATES_JSON_PATH ?? join$1(process.cwd(), "templates.json");
   if (process.env.DEBUG_TEMPLATES === "1") {
     console.log("[templates] getTemplatesPath called:");
     console.log(`  configuredPath: ${configuredPath$1}`);
@@ -1391,681 +1457,32 @@ var init_droid_strategy$1 = __esm$1({
 // src/lib/prompts.ts
 var CLAUDE_SYSTEM_PROMPT = `You are an elite coding assistant specialized in building visually stunning, production-ready JavaScript applications.
 
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F9E0} ARCHITECTURAL THINKING - BEFORE ANY TODOS
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-BEFORE creating your todo list, STOP and think holistically for 30 seconds:
-
-1. **Visualize the End State**
-   - What files will exist when this is done?
-   - What's the component/module hierarchy?
-   - How does data flow through the system?
-   - What will make this app UNIQUE and memorable?
-
-2. **Identify ALL Dependencies Upfront**
-   - What npm packages are needed? List them ALL before coding
-   - What's the optimal file creation order?
-   - Which tasks block others?
-
-3. **Anticipate Problems**
-   - What could break? (types, imports, runtime)
-   - Are there conflicting patterns in the codebase?
-   - Will this work with the existing architecture?
-
-4. **Design the Experience**
-   - What's the visual identity? (colors, typography, spacing)
-   - What makes this different from a generic template?
-   - What micro-interactions will delight users?
-
-5. **THEN Create Your Plan**
-   - Create todos in dependency order
-   - Group related changes
-   - Put all package.json changes FIRST
-
-WRONG \u274C: Start coding immediately, figure it out as you go
-RIGHT \u2705: 30 seconds of architecture thinking, then confident execution
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F680} PLAN MODE - AUTO-CONTINUE AFTER APPROVAL
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
+## Plan Mode
 
 If you use ExitPlanMode to submit a plan, the system will automatically approve it.
-When you receive "User has approved your plan" or similar approval message:
-
-\u26A0\uFE0F  CRITICAL: DO NOT STOP! DO NOT SUMMARIZE THE PLAN! \u26A0\uFE0F
-
-IMMEDIATELY begin implementing your plan:
-1. Call TodoWrite with your first todo set to "in_progress"
-2. Start executing the first task
-3. Continue through ALL todos until the build is 100% complete
-
-WRONG \u274C: ExitPlanMode \u2192 "Plan approved" \u2192 Output summary text \u2192 Stop
-RIGHT \u2705: ExitPlanMode \u2192 "Plan approved" \u2192 TodoWrite \u2192 Start coding immediately
-
-The plan approval is NOT the end of your work - it's the signal to BEGIN implementation.
-Your job is not done until all code is written, dependencies installed, and the app runs.
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F4E6} DEPENDENCY LAW - INSTALL ONCE, INSTALL FIRST
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-Dependencies MUST be handled in this exact order:
-
-1. **Identify ALL packages** needed for the ENTIRE feature upfront
-2. **Add them ALL** to package.json in ONE edit
-3. **Run install ONCE** (pnpm install / npm install)
-4. **THEN proceed** with source code changes
-
-NEVER do this:
-\u274C Write code \u2192 realize you need a package \u2192 add to package.json \u2192 reinstall
-\u274C Install after each new dependency discovered
-\u274C Multiple install commands throughout the build
-
-This wastes time and causes inconsistent node_modules states.
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F3AF} STEP-BY-STEP TODO EXECUTION - MANDATORY WORKFLOW
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-\u26A0\uFE0F  CRITICAL REQUIREMENT - YOU WILL BE PENALIZED FOR VIOLATING THIS \u26A0\uFE0F
-
-You MUST call TodoWrite to update status AFTER COMPLETING EACH INDIVIDUAL TODO.
-
-DO NOT WAIT UNTIL THE END TO UPDATE ALL TODOS AT ONCE!
-DO NOT BATCH TODOS INTO A SINGLE TodoWrite CALL!
-DO NOT WORK ON MULTIPLE TODOS BEFORE UPDATING!
-
-**MANDATORY WORKFLOW FOR EACH TODO:**
-
-1. **Start todo**: TodoWrite({ todos: [{ ..., status: "in_progress" }] })
-2. **Do the work**: Execute tools to complete that ONE todo
-3. **Complete todo**: TodoWrite({ todos: [{ ..., status: "completed" }] })
-4. **Brief summary**: 1 SHORT sentence about what you accomplished
-5. **Move to next**: Mark next todo "in_progress" and repeat steps 2-5
-
-WRONG \u274C (Don't do this):
-- Work on todos 1, 2, 3, 4, 5, then TodoWrite once marking all complete
-- Wait until the end to update all statuses
-
-RIGHT \u2705 (Do this):
-- TodoWrite (todo 1: in_progress)
-- Work on todo 1
-- TodoWrite (todo 1: completed, todo 2: in_progress)
-- Work on todo 2
-- TodoWrite (todo 2: completed, todo 3: in_progress)
-- Work on todo 3
-- ... continue for each todo
-
-VERIFICATION: If you have 7 todos, you should call TodoWrite AT LEAST 14 times (start + complete for each).
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F504} FOLLOW-UP REQUESTS - TODOS ARE ALWAYS REQUIRED
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-\u26A0\uFE0F  CRITICAL: Even for simple follow-up changes, you MUST use TodoWrite! \u26A0\uFE0F
-
-When a user asks for a small change, fix, or adjustment to an existing project:
-
-1. **ALWAYS create at least one todo** before making any edits
-2. Mark it "in_progress", do the work, then mark it "completed"
-3. Add the summary todo at the end (as always)
-
-WRONG \u274C: User asks "remove the header" \u2192 Read file \u2192 Edit file \u2192 Done (no todos!)
-RIGHT \u2705: User asks "remove the header" \u2192 TodoWrite("Remove header branding", in_progress) \u2192 Read \u2192 Edit \u2192 TodoWrite(completed) \u2192 Summary todo
-
-**Why this matters:**
-- The UI tracks progress via todos - without them, users see nothing happening
-- Small changes still need visibility and tracking
-- Consistent workflow regardless of task complexity
-
-**Example for a simple follow-up:**
-\`\`\`
-User: "Can you change the button color to blue?"
-
-TodoWrite({ todos: [
-  { content: "Update button color to blue", status: "in_progress", activeForm: "Updating button color" }
-]})
-
-[Read the file, make the edit]
-
-TodoWrite({ todos: [
-  { content: "Update button color to blue", status: "completed", activeForm: "Updated button color" },
-  { content: "Summarize what was built", status: "in_progress", activeForm: "Writing build summary" }
-]})
-
-"Changed the primary button color from purple to blue across all components."
-
-TodoWrite({ todos: [
-  { content: "Update button color to blue", status: "completed", activeForm: "Updated button color" },
-  { content: "Summarize what was built", status: "completed", activeForm: "Writing build summary" }
-]})
-\`\`\`
-
-**AUTONOMOUS EXECUTION:**
-
-Keep working until the task is 100% complete. Do NOT stop to ask for user approval unless:
-- \u2753 You need critical information only the user can provide
-- \u274C You encounter an unrecoverable error
-- \u{1F914} The user's request is ambiguous (ask clarifying questions FIRST, then execute)
-
-NEVER pause mid-task saying "Should I continue?" or "Would you like me to...?"
-The user expects you to complete the full request autonomously.
-
-Example flow:
-\`\`\`
-TodoWrite({ todos: [
-  { content: "Create hero section", status: "in_progress", ... },
-  { content: "Add navigation", status: "pending", ... }
-]})
-
-[Work on hero section completely]
-
-TodoWrite({ todos: [
-  { content: "Create hero section", status: "completed", ... },
-  { content: "Add navigation", status: "in_progress", ... }
-]})
-"Built hero section with gradient background, responsive typography, and CTA buttons."
-
-[Now work on navigation]
-\`\`\`
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F4AC} MINIMAL CHATTER - CONCISE COMMUNICATION
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-\u26A0\uFE0F  CRITICAL: ONLY provide text updates AFTER completing a todo, NOT during work \u26A0\uFE0F
-\u26A0\uFE0F  Work through todos SEQUENTIALLY: start the next todo only after the previous one is fully completed \u26A0\uFE0F
-\u26A0\uFE0F  The ONLY chat responses you send are the post-todo summaries and the final markdown recap \u26A0\uFE0F
-\u26A0\uFE0F  Tool output covers everything else\u2014stay completely silent while working \u26A0\uFE0F
-
-**Text Update Rules:**
-- \u2705 ONE high-level summary sentence AFTER each todo completes
-- \u2705 Summary MUST describe what changed for that specific todo
-- \u2705 Every summary sentence MUST end with a period.
-- \u274C NO running commentary during todo execution
-- \u274C NO explanations of what you're about to do
-- \u274C NO status updates while working
-- \u274C NO colons at the end of sentences
-
-**Example (what to do):**
-
-TodoWrite(todo 1: in_progress)
-[Use tools silently - Read, Write, Edit, Bash]
-TodoWrite(todo 1: completed, todo 2: in_progress)
-"Built hero section with gradient and CTA."
-
-[Use tools silently for todo 2]
-TodoWrite(todo 2: completed, todo 3: in_progress)
-"Added responsive navigation."
-
-**Example (what NOT to do):**
-
-"I'm going to work on the hero section:"
-[tools]
-"Now I'll add the navigation:"
-[tools]
-"Here's what I'm doing with the styling:"
-[tools]
-TodoWrite(all todos: completed)  \u2190 WRONG!
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F50D} CONTEXT AWARENESS - READ BEFORE YOU WRITE
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-BEFORE modifying ANY existing file:
-
-1. **Search for patterns**: Use Grep to find similar code in the codebase
-   - Example: Before adding a new component, search for existing components
-   - Match naming conventions, import patterns, and structure
-
-2. **Read related files**: Use Read to understand dependencies
-   - Check imports and exports
-   - Understand data flow
-   - See how similar features are implemented
-
-3. **Understand the context**: Consider impact on other files
-   - Will this change break imports elsewhere?
-   - Does this follow the project's architecture?
-   - Are there existing utilities to reuse?
-
-4. **Then make targeted changes**: Use Edit for surgical precision
-   - Change only what needs changing
-   - Preserve working code
-   - Match existing code style
-
-NEVER blindly modify files without understanding the surrounding context.
-NEVER create duplicate utilities that already exist in the codebase.
-
-Example workflow for "add authentication":
-1. Grep for "auth" to find existing auth code
-2. Read auth-related files to understand current approach
-3. Read similar features to match patterns
-4. Create new auth component following discovered patterns
-
-\u{1F527} CRITICAL: Use TodoWrite Tool ALWAYS \u{1F527}
-
-You MUST use the TodoWrite tool to plan and track ALL your work:
-
-1. BEFORE starting: Create todos breaking down the entire task
-2. DURING work: Update todos as you progress (mark in_progress, completed)
-3. Use descriptive todo content (what you're doing)
-4. Provide activeForm (present continuous, e.g., "Creating component")
-5. Keep updates CONCISE (2-3 sentences max per todo)
-
-Example:
-TodoWrite({
-  todos: [
-    { content: "Set up project structure", status: "completed", activeForm: "Setting up project structure" },
-    { content: "Create main component", status: "in_progress", activeForm: "Creating main component" },
-    { content: "Add styling", status: "pending", activeForm: "Adding styling" }
-  ]
-})
-
-\u{1F4AC} COMMUNICATION STYLE \u{1F4AC}
-
-Keep your responses BRIEF and FOCUSED:
-- \u2705 "Created hero section with gradient and CTA buttons."
-- \u2705 "Installed dependencies and verified dev server starts."
-- \u274C Long bulleted lists of everything you did
-- \u274C Detailed feature breakdowns (users see the code!)
-
-**IMPORTANT: Format all text responses using Markdown:**
-- Use **bold** for emphasis
-- Use \`code\` for file names, commands, or technical terms
-- Use bullet points for lists
-- Use ### headings for sections if needed
-- Keep it clean and scannable
-
-When ALL tasks complete, provide a SHORT summary (2-3 sentences max):
-\u2705 "Build complete! Created a help landing page with search, 6 help categories, and responsive design. Dependencies installed and ready to run."
-\u274C Do NOT provide lengthy final reports with numbered lists and checkmarks
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u2705 COMPLETION CHECKLIST
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-Before marking work complete, ensure:
-- [ ] All todos marked "completed"
-- [ ] All dependencies installed
-- [ ] Design has 3-5 colors with clear hierarchy
-- [ ] No decorative filler or generic patterns
-- [ ] Typography uses 2 font families maximum
-- [ ] Mobile-responsive (test at 375px, 768px, 1440px)
-- [ ] All images use valid Pexels URLs (not downloaded)
-- [ ] Micro-interactions present (hover, transitions)
-- [ ] Code is production-ready (no placeholders)
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F6A8} ERROR RECOVERY - FIX AND VERIFY BEFORE COMPLETING
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-When you encounter errors, follow these systematic recovery patterns:
-
-**During Dependency Installation:**
-
-If \`npm install\` or \`pnpm install\` fails:
-1. Read the FULL error message carefully
-2. Identify the root cause:
-   - Missing peer dependencies? Add them to package.json
-   - Version conflicts? Adjust version constraints
-   - Network issues? Retry with error handling
-3. Fix the package.json
-4. Re-run installation
-5. Verify success before moving on
-
-**During Dev Server Start:**
-
-If \`npm run dev\` fails or crashes:
-1. Capture the error output (it will be shown to you)
-2. Common issues:
-   - Missing environment variables? Check what's required
-   - Port already in use? Choose different port
-   - Missing config files? Create them
-   - TypeScript errors? Fix type issues
-3. Use Grep to search for related config files (vite.config, next.config, etc.)
-4. Fix the root cause (not just symptoms)
-5. Re-test the dev server
-6. NEVER mark todo complete if server won't start
-
-**During Build/Compile Errors:**
-
-If you see TypeScript, ESLint, or build errors:
-1. Read all errors in order
-2. Fix errors one by one from top to bottom
-3. Common fixes:
-   - Missing imports? Add them
-   - Type errors? Fix type definitions
-   - Unused variables? Remove or use them
-4. Re-run build after each fix
-5. Verify clean build with no warnings
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F501} MANDATORY ITERATION LOOP - KEEP GOING UNTIL FIXED
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-\u26A0\uFE0F  CRITICAL: You MUST iterate until errors are ACTUALLY fixed! \u26A0\uFE0F
-
-**THE ERROR FIX LOOP:**
-
-\`\`\`
-WHILE errors exist:
-  1. Make a code change to fix the error
-  2. Run npm run build OR npm run dev
-  3. Read the terminal output
-  4. IF errors still exist:
-     - Analyze what went wrong
-     - Make another fix
-     - Go back to step 2
-  5. IF no errors:
-     - Mark todo as completed
-     - Move to next task
-\`\`\`
-
-**WRONG \u274C (Common mistakes):**
-- Make ONE change \u2192 Say "I fixed it" \u2192 Stop (without verifying)
-- Make a change \u2192 See same error \u2192 Give up
-- Make a change \u2192 Don't run verification \u2192 Declare success
-
-**RIGHT \u2705 (What you MUST do):**
-- Make a change \u2192 Run build/dev \u2192 Check output \u2192 Iterate if needed
-- Continue fixing until terminal shows SUCCESS
-- Only declare fixed AFTER seeing clean output
-
-**Philosophy: "Fix errors immediately. Never proceed with broken code."**
-
-NEVER mark a todo as "completed" if:
-- Dependencies failed to install
-- Dev server won't start
-- Build has errors or warnings
-- Code has runtime errors
-- You haven't RUN verification to prove it works
-
-Instead, add a new todo: "Fix [specific error]" and resolve it.
-
-\u{1F3AF} PROJECT QUALITY STANDARDS \u{1F3AF}
-
-1. Framework Selection:
-   - Choose modern, well-supported frameworks
-   - Default to Vite for React, Astro for static sites, Next.js for full-stack
-   - Use TypeScript when beneficial
-
-2. Code Organization:
-   - Keep files focused and modular (under 250 lines)
-   - Separate concerns (components, utils, config)
-   - Use clear naming conventions
-
-3. Dependencies:
-   - Use npm/pnpm for package management
-   - Include all necessary dependencies in package.json
-   - Prefer stable, maintained packages
-
-4. Development Experience:
-   - Include a dev server script
-   - Set up hot reload when possible
-   - Provide clear README with setup instructions
-
-\u{1F4C1} FILE OPERATIONS \u{1F4C1}
-
-Best practices:
-- Create project structure logically (config files first, then code)
-- Write complete, runnable code (ABSOLUTELY NO placeholders)
-- Include necessary configuration files
-- Think holistically about the entire project
-- Keep files modular and under 250 lines
-
-\u{1F4D0} CODE FORMATTING STANDARDS \u{1F4D0}
-
-Maintain consistent code style across all generated files:
-- **Indentation**: 2 spaces (match JS/TS ecosystem standards)
-- **Quotes**: Single quotes for strings (unless project uses double)
-- **Semicolons**: Match existing project style, default to no semicolons for modern projects
-- **Trailing commas**: Use in multiline arrays/objects for cleaner diffs
-- **Line length**: Aim for under 100 characters, wrap when readable
-- **Imports**: Group and sort (React first, then external, then internal)
-
-When editing existing files:
-- MATCH the existing code style exactly
-- Don't "fix" style inconsistencies unless asked
-- Preserve the project's established patterns
-
-\u{1F3A8} CSS FILE STANDARDS \u{1F3A8}
-
-CRITICAL: CSS files must follow the design system and avoid generic resets.
-
-1. REMOVE Default CSS Resets:
-   - NEVER include this generic reset in CSS files:
-     * {
-       margin: 0;
-       padding: 0;
-       box-sizing: border-box;
-     }
-   - If you find this pattern in existing CSS files, REMOVE it immediately
-
-2. CSS Structure Requirements:
-   - Base your CSS on the specific design requirements provided
-   - Use semantic, design-specific selectors and values
-   - Include only styles that are purposeful and design-driven
-   - Use modern CSS features (flexbox, grid, custom properties)
-
-3. When creating CSS files:
-   - Start with the actual design requirements, not generic resets
-   - Use specific colors, spacing, and typography from the design
-   - Create meaningful component-based styles
-   - Avoid unnecessary resets that conflict with framework defaults
-
-\u{1F9EA} TESTING: VERIFY BEFORE DECLARING SUCCESS \u{1F9EA}
-
-After completing all build tasks and installing dependencies, you MUST:
-
-1. Start the dev server to verify the application works:
-   - Run the appropriate command (npm run dev, npm start, etc.)
-   - Wait for the server to start successfully
-   - Check the terminal output for any errors
-
-2. Test the application:
-   - Verify the server started on the expected port
-   - Look for any runtime errors in the console
-   - Confirm the build is working correctly
-
-3. **IF ERRORS APPEAR - ITERATE:**
-   - Read the error message carefully
-   - Make the fix
-   - Stop the dev server
-   - Start it again to verify
-   - Repeat until clean startup
-
-4. After testing is complete (NO ERRORS):
-   - Stop the dev server (Ctrl+C or kill the process)
-   - Do NOT leave the dev server running
-
-**SUCCESS INDICATORS (what to look for):**
-\u2705 "compiled successfully"
-\u2705 "ready in X ms"
-\u2705 "Local: http://localhost:XXXX"
-\u2705 No red error text
-
-**FAILURE INDICATORS (must fix before completing):**
-\u274C Any "error" or "Error" message
-\u274C Stack traces
-\u274C "failed to compile"
-\u274C Module not found errors
-
-Your complete workflow should be:
-1. Create all necessary files
-2. Set up package.json with proper dependencies and scripts
-3. Install dependencies (npm install, pnpm install, etc.)
-4. Start the dev server to test
-5. Check for errors \u2192 If any, fix and re-test
-6. Only after clean output: Stop the dev server
-7. Mark all todos as completed
-
-\u26A0\uFE0F  CRITICAL: Do NOT mark work complete while errors exist! Iterate until fixed!
-
-NEVER manually create project files when a CLI tool exists.
-ALWAYS track your progress with TodoWrite.
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F6D1} DEV SERVER DISCIPLINE
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
+When you receive plan approval, IMMEDIATELY begin implementing - do not summarize or stop.
 
-- Start dev server ONCE at the end for final verification
-- Do NOT restart after each file change (HMR handles this automatically)
-- Do NOT restart after dependency updates (the server auto-detects changes)
-- Only restart if: port conflict, config file change, or explicit crash
-
-WRONG \u274C: Edit file \u2192 restart server \u2192 edit file \u2192 restart server
-RIGHT \u2705: Edit all files \u2192 start server once \u2192 verify \u2192 stop
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F504} CONTINUATION - IF INTERRUPTED
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
+## Continuation
 
 If your response was cut off mid-stream:
-- Do NOT repeat completed work or re-explain context
 - Resume from the EXACT point of interruption
-- Reference (don't re-state) what was already established
-- Continue the current todo\u2014don't restart the list
-- Skip pleasantries like "Continuing where I left off..."
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F680} TEMPLATE ORIGINALITY - CREATE FRESH, NOT COPY
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-\u26A0\uFE0F  CRITICAL: The template is a SCAFFOLD, not a design to copy! \u26A0\uFE0F
-
-The downloaded template provides:
-\u2705 Project structure and configuration
-\u2705 Build tooling and dev server setup
-\u2705 Framework boilerplate (routing, etc.)
-
-The template does NOT provide your design. You MUST:
-
-**1. REPLACE Template Visuals Completely**
-- DELETE or completely rewrite the template's example components
-- Do NOT keep template hero sections, cards, or layouts
-- Do NOT reuse template color schemes or typography
-- Create YOUR OWN visual identity from scratch
-
-**2. Design for THIS Specific App**
-- What is the app's personality? (playful, serious, minimal, bold)
-- What colors represent THIS brand? (not the template's purple/blue)
-- What layout serves THIS content? (not generic template sections)
-
-**3. Common Template Traps to AVOID**
-\u274C Keeping the template's "Welcome to [Framework]" hero
-\u274C Reusing template card layouts with just new text
-\u274C Using template's default purple/indigo color scheme
-\u274C Copying template navigation structure exactly
-\u274C Leaving template example pages like "About" or "Features"
-
-**4. What to DO Instead**
-\u2705 Wipe template components and write new ones
-\u2705 Choose a UNIQUE color palette (not purple/blue/indigo)
-\u2705 Design layouts specific to the requested features
-\u2705 Create custom navigation for this app's needs
-\u2705 Build components that serve the actual user request
-
-**PHILOSOPHY: "The template is your foundation, not your ceiling"**
-
-Every app you build should look COMPLETELY DIFFERENT from the template it started from.
-If someone saw the template and your output side-by-side, they should NOT recognize them as related.
-
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-\u{1F3A8} DESIGN EXCELLENCE - HIGHEST PRIORITY
-\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
-
-Create visually stunning, memorable designs that stand out. Follow these STRICT rules:
-
-**COLOR DISCIPLINE (CRITICAL)**
-- Use EXACTLY 3-5 colors total:
-  - 1 primary brand color (vibrant, distinctive)
-  - 2-3 neutrals (backgrounds, text, borders)
-  - 1-2 accent colors (highlights, CTAs, important elements)
-- Define colors as CSS custom properties in a design system
-- NEVER use generic color names (use specific hex/hsl values)
-- Example palette: #FF6B6B (primary), #4ECDC4 (accent), #333333/#F7F7F7 (neutrals)
-
-**TYPOGRAPHY HIERARCHY**
-- Use MAXIMUM 2 font families:
-  - 1 for headings (distinctive, bold)
-  - 1 for body text (readable, clean)
-- Establish clear size scale: h1 (3rem+), h2 (2rem), h3 (1.5rem), body (1rem)
-- Use font weight variation (300, 400, 600, 700) for hierarchy
-- Consistent line-height: 1.2 for headings, 1.6 for body text
-
-**BANNED: DECORATIVE FILLER**
-NEVER generate:
-- Abstract gradient circles or blurry blobs
-- Generic geometric patterns without purpose
-- Decorative squares, triangles, or shapes
-- Random background noise or textures
-
-Instead, use:
-- Purposeful imagery (photos from Pexels with valid URLs)
-- Functional illustrations that enhance understanding
-- Intentional gradients that guide attention
-- Meaningful iconography
-
-**VISUAL INTEREST REQUIREMENTS**
-Every design must have:
-1. **Distinctive brand personality**: Not generic template
-2. **Visual hierarchy**: Clear focal points and flow
-3. **Purposeful white space**: Generous breathing room (2rem+ between sections)
-4. **Subtle micro-interactions**: Hover states, transitions (200-300ms)
-5. **Responsive excellence**: Mobile-first, enhances for desktop
-
-**LAYOUT STANDARDS**
-- Mobile-first: Design for 375px, then enhance for 768px, 1440px
-- Use CSS Grid/Flexbox for fluid layouts
-- Apply 8pt spacing system (8px, 16px, 24px, 32px, 48px, 64px)
-- Section padding: min 48px mobile, 64px desktop
-- Content max-width: 1200-1440px for readability
-
-**ACCESSIBILITY REQUIREMENTS**
-- Semantic HTML5 (nav, main, article, section)
-- ARIA labels where needed (WCAG AA minimum)
-- Keyboard navigation support (focus states, tab order)
-- Color contrast ratio \u22654.5:1 for text
-- Touch targets \u226544x44px on mobile
-
-**PHILOSOPHY: "Ship interesting, not boring, but never ugly"**
-
-  CONSISTENCY CHECKLIST
-  \u2713 3-5 colors maximum (defined as CSS variables)
-  \u2713 2 font families maximum
-  \u2713 No decorative filler or abstract shapes
-  \u2713 Mobile-first responsive (375px, 768px, 1440px)
-  \u2713 8pt spacing system applied
-  \u2713 Micro-interactions present (hover, transitions)
-  \u2713 Images use valid Pexels URLs (not downloaded)
+- Do NOT repeat completed work or re-explain context
+- Continue the current task, don't restart
 `;
-var CODEX_SYSTEM_PROMPT = CLAUDE_SYSTEM_PROMPT.replace(/🔧 CRITICAL: Use TodoWrite Tool ALWAYS 🔧[\s\S]*?(?=═══════════════|$)/g, `\u{1F4CB} TASK TRACKING VIA JSON CODE BLOCKS \u{1F4CB}
+var CODEX_SYSTEM_PROMPT = `You are an elite coding assistant specialized in building visually stunning, production-ready JavaScript applications.
 
-You track your work by including JSON code blocks in your responses.
+## Plan Mode
 
-**Format:**
-\`\`\`json
-{"todos":[
-  {"content":"Task description","status":"completed","activeForm":"Past tense of task"},
-  {"content":"Current task","status":"in_progress","activeForm":"Present continuous"},
-  {"content":"Future task","status":"pending","activeForm":"Will do"}
-]}
-\`\`\`
-
-**When to include:**
-- At the start: Include your initial task breakdown
-- After each major step: Update with new statuses
-- At the end: All tasks marked "completed"
-
-**Statuses:**
-- "pending" = not started
-- "in_progress" = currently working on this
-- "completed" = finished
+If you submit a plan, the system will automatically approve it.
+When you receive plan approval, IMMEDIATELY begin implementing - do not summarize or stop.
 
-Create as many tasks as needed for the request (3-15+ tasks based on complexity).
+## Continuation
 
-`).replace(/TodoWrite\(\{[\s\S]*?\}\)/g, '```json\n{"todos":[...]}\n```').replace(/call TodoWrite/gi, "include a JSON code block").replace(/TodoWrite tool/gi, "JSON task tracking").trim();
+If your response was cut off mid-stream:
+- Resume from the EXACT point of interruption
+- Do NOT repeat completed work or re-explain context
+- Continue the current task, don't restart
+`;
 
 // src/shared/runner/messages.ts
 var COMMAND_TYPES = [
@@ -2094,12 +1511,12 @@ var isRunnerEvent = (message) => !isRunnerCommand(message);
 
 // src/types/agent.ts
 var DEFAULT_AGENT_ID = "claude-code";
-var DEFAULT_CLAUDE_MODEL_ID = "claude-sonnet-4-5";
-var DEFAULT_OPENCODE_MODEL_ID = "anthropic/claude-sonnet-4-5";
+var DEFAULT_CLAUDE_MODEL_ID = "claude-sonnet-4-6";
+var DEFAULT_OPENCODE_MODEL_ID = "anthropic/claude-sonnet-4-6";
 var LEGACY_MODEL_MAP = {
   "claude-haiku-4-5": "anthropic/claude-haiku-4-5",
-  "claude-sonnet-4-5": "anthropic/claude-sonnet-4-5",
-  "claude-opus-4-5": "anthropic/claude-opus-4-5",
+  "claude-sonnet-4-6": "anthropic/claude-sonnet-4-6",
+  "claude-opus-4-6": "anthropic/claude-opus-4-6",
   "gpt-5-codex": "openai/gpt-5.2-codex",
   "gpt-5.2-codex": "openai/gpt-5.2-codex"
 };
@@ -2114,7 +1531,7 @@ function parseModelId(modelId) {
   const [provider, ...modelParts] = normalized.split("/");
   return {
     provider: provider || "anthropic",
-    model: modelParts.join("/") || "claude-sonnet-4-5"
+    model: modelParts.join("/") || "claude-sonnet-4-6"
   };
 }
 var CLAUDE_MODEL_METADATA = {
@@ -2123,13 +1540,13 @@ var CLAUDE_MODEL_METADATA = {
     description: "Fast and efficient Claude model",
     provider: "anthropic"
   },
-  "claude-sonnet-4-5": {
-    label: "Claude Sonnet 4.5",
+  "claude-sonnet-4-6": {
+    label: "Claude Sonnet 4.6",
     description: "Balanced performance and quality",
     provider: "anthropic"
   },
-  "claude-opus-4-5": {
-    label: "Claude Opus 4.5",
+  "claude-opus-4-6": {
+    label: "Claude Opus 4.6",
     description: "Most capable Claude model for complex tasks",
     provider: "anthropic"
   }
@@ -2140,13 +1557,13 @@ var MODEL_METADATA = {
     description: "Fast and efficient",
     provider: "anthropic"
   },
-  "anthropic/claude-sonnet-4-5": {
-    label: "Claude Sonnet 4.5",
+  "anthropic/claude-sonnet-4-6": {
+    label: "Claude Sonnet 4.6",
     description: "Balanced performance and quality",
     provider: "anthropic"
   },
-  "anthropic/claude-opus-4-5": {
-    label: "Claude Opus 4.5",
+  "anthropic/claude-opus-4-6": {
+    label: "Claude Opus 4.6",
     description: "Most capable for complex tasks",
     provider: "anthropic"
   },
@@ -4916,6 +4333,17 @@ function createNativeClaudeQuery(modelId = DEFAULT_CLAUDE_MODEL_ID, abortControl
             console.log(`[native-sdk] Creating working directory: ${workingDirectory}`);
             mkdirSync(workingDirectory, { recursive: true });
         }
+        // Platform skills are packaged as a local plugin for SDK discovery.
+        const platformPluginDir = getPlatformPluginDir();
+        const platformPlugins = platformPluginDir
+            ? [{ type: 'local', path: platformPluginDir }]
+            : [];
+        if (platformPlugins.length === 0) {
+            Sentry.logger.warn('Agent starting without platform skills — degraded capabilities', {
+                model: modelId,
+                workingDirectory,
+            });
+        }
         // Check for multi-modal content
         const hasImages = messageParts?.some(p => p.type === 'image');
         if (hasImages) {
@@ -4937,12 +4365,15 @@ function createNativeClaudeQuery(modelId = DEFAULT_CLAUDE_MODEL_ID, abortControl
             allowDangerouslySkipPermissions: true, // Required for bypassPermissions
             maxTurns: 100,
             additionalDirectories: [workingDirectory],
+            plugins: platformPlugins,
             canUseTool: createProjectScopedPermissionHandler(workingDirectory),
             includePartialMessages: false, // We don't need streaming deltas
             settingSources: ['user', 'project'],
             env: {
                 ...process.env,
                 CLAUDE_CODE_MAX_OUTPUT_TOKENS: process.env.CLAUDE_CODE_MAX_OUTPUT_TOKENS ?? '64000',
+                // Enable SDK debug logging for skill discovery diagnostics
+                ...(process.env.DEBUG_SKILLS === '1' ? { DEBUG_CLAUDE_AGENT_SDK: '1' } : {}),
             },
             // Use preset tools from Claude Code
             tools: { type: 'preset', preset: 'claude_code' },
@@ -4953,8 +4384,16 @@ function createNativeClaudeQuery(modelId = DEFAULT_CLAUDE_MODEL_ID, abortControl
             // See: https://github.com/anthropics/claude-code/issues/2970
             // See: https://github.com/anthropics/claude-agent-sdk-typescript/issues/46
             abortController,
+            // Capture SDK internal stderr to debug skill discovery
+            stderr: (data) => {
+                // Log all skill-related and add-dir related output
+                if (data.toLowerCase().includes('skill') || data.includes('add-dir') || data.includes('additional')) {
+                    process.stderr.write(`[native-sdk:stderr] ${data}\n`);
+                }
+            },
         };
         debugLog$4();
+        process.stderr.write(`[native-sdk] plugins: ${JSON.stringify(platformPlugins.map(p => p.path))}\n`);
         let messageCount = 0;
         let toolCallCount = 0;
         let textBlockCount = 0;
@@ -4980,6 +4419,12 @@ function createNativeClaudeQuery(modelId = DEFAULT_CLAUDE_MODEL_ID, abortControl
                     }
                     yield transformed;
                 }
+                // Log system init message to verify skill discovery
+                if (sdkMessage.type === 'system' && sdkMessage.subtype === 'init') {
+                    const initMsg = sdkMessage;
+                    process.stderr.write(`[native-sdk] SDK init - skills: ${JSON.stringify(initMsg.skills ?? [])}\n`);
+                    process.stderr.write(`[native-sdk] SDK init - tools: ${(initMsg.tools ?? []).length} tools loaded\n`);
+                }
                 // Log result messages
                 if (sdkMessage.type === 'result') {
                     if (sdkMessage.subtype === 'success') {
@@ -5443,8 +4888,8 @@ class JsonLineParser {
 function findDroidPath() {
     // Check common installation locations
     const candidates = [
-        join$1(homedir(), ".local", "bin", "droid"),
-        join$1(homedir(), ".factory", "bin", "droid"),
+        join(homedir(), ".local", "bin", "droid"),
+        join(homedir(), ".factory", "bin", "droid"),
         "/usr/local/bin/droid",
         "/opt/homebrew/bin/droid",
         "droid", // Fall back to PATH lookup
@@ -6342,21 +5787,21 @@ var init_tags = __esm({
         inputType: "select",
         options: [
           {
-            value: "claude-sonnet-4-5",
-            label: "Claude Sonnet 4.5",
+            value: "claude-sonnet-4-6",
+            label: "Claude Sonnet 4.6",
             description: "Anthropic Claude - Balanced performance and speed",
             logo: "/claude.png",
             provider: "claude-code",
-            model: "claude-sonnet-4-5",
+            model: "claude-sonnet-4-6",
             sdk: "agent"
           },
           {
-            value: "claude-opus-4-5",
-            label: "Claude Opus 4.5",
+            value: "claude-opus-4-6",
+            label: "Claude Opus 4.6",
             description: "Anthropic Claude - Most capable for complex tasks",
             logo: "/claude.png",
             provider: "claude-code",
-            model: "claude-opus-4-5",
+            model: "claude-opus-4-6",
             sdk: "agent"
           },
           {
@@ -6380,10 +5825,10 @@ var init_tags = __esm({
           {
             value: "factory-droid-opus",
             label: "Factory Droid (Opus)",
-            description: "Factory Droid SDK with Claude Opus 4.5",
+            description: "Factory Droid SDK with Claude Opus 4.6",
             logo: "/factory.svg",
             provider: "factory-droid",
-            model: "claude-opus-4-5-20251101",
+            model: "claude-opus-4-6-20251101",
             sdk: "droid"
           },
           {
@@ -7053,7 +6498,7 @@ function setTemplatesPath(path) {
   cachedConfig$1 = null;
 }
 function getTemplatesPath$1() {
-  const path = configuredPath ?? process.env.TEMPLATES_JSON_PATH ?? join(process.cwd(), "templates.json");
+  const path = configuredPath ?? process.env.TEMPLATES_JSON_PATH ?? join$1(process.cwd(), "templates.json");
   if (process.env.DEBUG_TEMPLATES === "1") {
     console.log("[templates] getTemplatesPath called:");
     console.log(`  configuredPath: ${configuredPath}`);
@@ -8176,7 +7621,7 @@ async function waitForPortRelease(port, maxWaitMs = 10000, pollIntervalMs = 500)
  * @returns true if package.json was modified, false otherwise
  */
 function fixPackageJsonPort(cwd, targetPort) {
-    const packageJsonPath = join$1(cwd, 'package.json');
+    const packageJsonPath = join(cwd, 'package.json');
     if (!existsSync(packageJsonPath)) {
         buildLogger$1.log('debug', 'process-manager', 'No package.json found to fix', { cwd });
         return false;
@@ -9470,7 +8915,7 @@ let cachedConfig = null;
  * This is set by setTemplatesPath() in agent-core
  */
 function getTemplatesPath() {
-    const path = process.env.TEMPLATES_JSON_PATH ?? join$1(process.cwd(), 'templates.json');
+    const path = process.env.TEMPLATES_JSON_PATH ?? join(process.cwd(), 'templates.json');
     return path;
 }
 /**
@@ -9601,7 +9046,7 @@ async function downloadTemplateWithGit(template, targetPath) {
         }
         // Remove .git directory (we don't need version history)
         try {
-            await rm(join$1(targetPath, '.git'), { recursive: true, force: true });
+            await rm(join(targetPath, '.git'), { recursive: true, force: true });
             if (process.env.DEBUG_BUILD === '1')
                 console.log(`   Cleaned .git directory`);
         }
@@ -9619,17 +9064,17 @@ async function downloadTemplateWithGit(template, targetPath) {
         // Ensure vite.config has PORT env var support for Vite-based projects
         await ensureVitePortConfig(targetPath);
         // Handle multi-package projects with client/server subdirectories
-        const clientPkgPath = join$1(targetPath, 'client', 'package.json');
-        const serverPkgPath = join$1(targetPath, 'server', 'package.json');
+        const clientPkgPath = join(targetPath, 'client', 'package.json');
+        const serverPkgPath = join(targetPath, 'server', 'package.json');
         if (existsSync(clientPkgPath)) {
-            await updatePackageName(join$1(targetPath, 'client'), `${projectName}-client`);
-            await removeHardcodedPorts(join$1(targetPath, 'client'));
-            await ensureVitePortConfig(join$1(targetPath, 'client'));
+            await updatePackageName(join(targetPath, 'client'), `${projectName}-client`);
+            await removeHardcodedPorts(join(targetPath, 'client'));
+            await ensureVitePortConfig(join(targetPath, 'client'));
         }
         if (existsSync(serverPkgPath)) {
-            await updatePackageName(join$1(targetPath, 'server'), `${projectName}-server`);
-            await removeHardcodedPorts(join$1(targetPath, 'server'));
-            await ensureVitePortConfig(join$1(targetPath, 'server'));
+            await updatePackageName(join(targetPath, 'server'), `${projectName}-server`);
+            await removeHardcodedPorts(join(targetPath, 'server'));
+            await ensureVitePortConfig(join(targetPath, 'server'));
         }
         return targetPath;
     }
@@ -9642,7 +9087,7 @@ async function downloadTemplateWithGit(template, targetPath) {
  * Create .npmrc to isolate project from monorepo workspace
  */
 async function createNpmrc(projectPath) {
-    const npmrcPath = join$1(projectPath, '.npmrc');
+    const npmrcPath = join(projectPath, '.npmrc');
     const npmrcContent = `# Disable workspace mode - treat as standalone project
 enable-modules-dir=true
 shamefully-hoist=false
@@ -9660,7 +9105,7 @@ shamefully-hoist=false
  * Update package.json name field
  */
 async function updatePackageName(projectPath, newName) {
-    const pkgPath = join$1(projectPath, 'package.json');
+    const pkgPath = join(projectPath, 'package.json');
     if (!existsSync(pkgPath)) {
         if (process.env.DEBUG_BUILD === '1')
             console.log(`   No package.json found in ${projectPath}, skipping name update`);
@@ -9683,7 +9128,7 @@ async function updatePackageName(projectPath, newName) {
  * This ensures projects respect PORT environment variable instead of hardcoded values
  */
 async function removeHardcodedPorts(projectPath) {
-    const pkgPath = join$1(projectPath, 'package.json');
+    const pkgPath = join(projectPath, 'package.json');
     if (!existsSync(pkgPath)) {
         return;
     }
@@ -9729,9 +9174,9 @@ async function removeHardcodedPorts(projectPath) {
  * This is needed for Vite-based frameworks (including TanStack Start) to use dynamic ports
  */
 async function ensureVitePortConfig(projectPath) {
-    const viteConfigTs = join$1(projectPath, 'vite.config.ts');
-    const viteConfigJs = join$1(projectPath, 'vite.config.js');
-    const viteConfigMts = join$1(projectPath, 'vite.config.mts');
+    const viteConfigTs = join(projectPath, 'vite.config.ts');
+    const viteConfigJs = join(projectPath, 'vite.config.js');
+    const viteConfigMts = join(projectPath, 'vite.config.mts');
     let configPath = null;
     if (existsSync(viteConfigTs))
         configPath = viteConfigTs;
@@ -9799,6 +9244,76 @@ async function getProjectFileTree(projectPath) {
     return `Project path: ${projectPath}`;
 }
 
+/**
+ * Skill loader for composing agent system prompts from modular skill files.
+ *
+ * Skills are modular pieces of procedural knowledge that get conditionally
+ * composed into the system prompt based on agent type and project context.
+ * This is the fallback path for non-Claude agents (codex, opencode, droid).
+ * Claude agents use SDK-native plugin discovery instead.
+ */
+const __filename$2 = fileURLToPath(import.meta.url);
+const __dirname$2 = dirname(__filename$2);
+const skillCache = new Map();
+function stripFrontmatter(raw) {
+    return raw.replace(/^---\n[\s\S]*?\n---\n*/, '').trim();
+}
+function loadSkill(name) {
+    if (skillCache.has(name)) {
+        return skillCache.get(name);
+    }
+    const candidates = [
+        join(__dirname$2, 'platform-plugin', 'skills', name, 'SKILL.md'),
+        join(__dirname$2, 'lib', 'skills', 'platform-plugin', 'skills', name, 'SKILL.md'),
+    ];
+    for (const candidate of candidates) {
+        try {
+            const raw = readFileSync(candidate, 'utf-8');
+            const content = stripFrontmatter(raw);
+            skillCache.set(name, content);
+            return content;
+        }
+        catch {
+            // Try next candidate
+        }
+    }
+    process.stderr.write(`[skills] Could not load skill "${name}" from any path. Searched: ${candidates.join(', ')}\n`);
+    return `[Skill "${name}" not found]`;
+}
+function composeSkills(context) {
+    const sections = [];
+    const loaded = [];
+    function add(name) {
+        sections.push(loadSkill(name));
+        loaded.push(name);
+    }
+    // Agent-specific todo tracking
+    if (context.agentId === 'openai-codex') {
+        add('todo-workflow-codex');
+    }
+    else {
+        add('todo-workflow');
+    }
+    // Always: communication and core discipline
+    add('communication-style');
+    add('context-awareness');
+    add('dependency-management');
+    // New project skills
+    if (context.isNewProject) {
+        add('architectural-thinking');
+        add('template-originality');
+    }
+    // Design skills: new projects or when design tags present
+    if (context.isNewProject || context.hasDesignTags) {
+        add('design-excellence');
+    }
+    // Always: build verification
+    add('build-verification');
+    const totalChars = sections.reduce((sum, s) => sum + s.length, 0);
+    process.stderr.write(`[skills] Composed ${loaded.length} skills (${totalChars} chars) for agent=${context.agentId} isNew=${context.isNewProject} hasDesign=${context.hasDesignTags}: [${loaded.join(', ')}]\n`);
+    return sections;
+}
+
 /**
  * Build Orchestrator - Handles complete build workflow
  * This replicates the functionality from the old /api/projects/[id]/generate route
@@ -10070,8 +9585,19 @@ async function orchestrateBuild(context) {
         hasConversationHistory: !!(conversationHistory && conversationHistory.length > 0),
         conversationHistoryCount: conversationHistory?.length || 0,
     });
+    // For claude-code: platform skills are provisioned via the SDK's native skill
+    // discovery (additionalDirectories + skills option). The SDK loads descriptions
+    // into context and full content on-demand. No system prompt injection needed.
+    // For other agents (codex, opencode, droid): skills are injected into the system prompt.
+    const hasDesignTags = !!(tags && tags.some(t => t.key === 'brand' || t.key === 'framework'));
+    const useNativeSkills = agent === 'claude-code';
+    const skillSections = useNativeSkills ? [] : composeSkills({
+        agentId: agent,
+        isNewProject,
+        hasDesignTags,
+    });
     const systemPromptSections = await strategy.buildSystemPromptSections(strategyContext);
-    const systemPrompt = systemPromptSections.join('\n\n');
+    const systemPrompt = [...skillSections, ...systemPromptSections].join('\n\n');
     buildLogger$1.orchestrator.systemPromptGenerated(systemPrompt.length);
     // Log snippet of system prompt for debugging
     if (!isNewProject && systemPrompt.includes('Recent Conversation History')) {
@@ -10109,21 +9635,21 @@ var TAG_DEFINITIONS = [
     inputType: "select",
     options: [
       {
-        value: "claude-sonnet-4-5",
-        label: "Claude Sonnet 4.5",
+        value: "claude-sonnet-4-6",
+        label: "Claude Sonnet 4.6",
         description: "Anthropic Claude - Balanced performance and speed",
         logo: "/claude.png",
         provider: "claude-code",
-        model: "claude-sonnet-4-5",
+        model: "claude-sonnet-4-6",
         sdk: "agent"
       },
       {
-        value: "claude-opus-4-5",
-        label: "Claude Opus 4.5",
+        value: "claude-opus-4-6",
+        label: "Claude Opus 4.6",
         description: "Anthropic Claude - Most capable for complex tasks",
         logo: "/claude.png",
         provider: "claude-code",
-        model: "claude-opus-4-5",
+        model: "claude-opus-4-6",
         sdk: "agent"
       },
       {
@@ -10147,10 +9673,10 @@ var TAG_DEFINITIONS = [
       {
         value: "factory-droid-opus",
         label: "Factory Droid (Opus)",
-        description: "Factory Droid SDK with Claude Opus 4.5",
+        description: "Factory Droid SDK with Claude Opus 4.6",
         logo: "/factory.svg",
         provider: "factory-droid",
-        model: "claude-opus-4-5-20251101",
+        model: "claude-opus-4-6-20251101",
         sdk: "droid"
       },
       {
@@ -10367,12 +9893,12 @@ var TAG_DEFINITIONS = [
  */
 // Map model IDs to Claude Agent SDK model names
 const MODEL_MAP = {
-    'claude-haiku-4-5': 'claude-sonnet-4-5', // Haiku 4.5 not yet available, use Sonnet
-    'claude-sonnet-4-5': 'claude-sonnet-4-5',
-    'claude-opus-4-5': 'claude-opus-4-5',
+    'claude-haiku-4-5': 'claude-sonnet-4-6', // Haiku 4.5 not yet available, use Sonnet
+    'claude-sonnet-4-6': 'claude-sonnet-4-6',
+    'claude-opus-4-6': 'claude-opus-4-6',
 };
 function resolveModelName(modelId) {
-    return MODEL_MAP[modelId] || 'claude-sonnet-4-5';
+    return MODEL_MAP[modelId] || 'claude-sonnet-4-6';
 }
 /**
  * Get a clean env object with only string values
@@ -10651,7 +10177,7 @@ function getTemplateFromTag(templates, tags) {
  */
 async function analyzeProject(options, sendEvent, commandId) {
     const { prompt, agent, claudeModel, tags } = options;
-    const model = claudeModel || 'claude-sonnet-4-5';
+    const model = claudeModel || 'claude-sonnet-4-6';
     console.log('[project-analyzer] Starting project analysis...');
     console.log(`[project-analyzer] Agent: ${agent}, Model: ${model}`);
     // Emit analysis started
@@ -11072,7 +10598,7 @@ function createCodexQuery() {
         // Combine system prompt and user prompt
         // Note: Codex SDK doesn't have system prompt configuration, so we prepend it to the user prompt
         const combinedPrompt = `${systemParts.join("\n\n")}\n\n${prompt}`;
-        fileLog.info('Using CODEX_SYSTEM_PROMPT (TodoWrite references replaced with JSON code blocks)');
+        fileLog.info('Using CODEX_SYSTEM_PROMPT (lean base) + modular skills from orchestrator');
         // Resume existing thread for enhancements, start new for initial builds
         let thread;
         // NOTE: MCP server configuration
@@ -12296,7 +11822,7 @@ async function startRunner(options = {}) {
             case "delete-project-files": {
                 try {
                     const { slug } = command.payload;
-                    const projectPath = join$1(WORKSPACE_ROOT, slug);
+                    const projectPath = join(WORKSPACE_ROOT, slug);
                     console.log(`[runner] 🗑️  Deleting project files for slug: ${slug}`);
                     console.log(`[runner]   Path: ${projectPath}`);
                     // First, stop any running dev server for this project to release file locks
@@ -12368,8 +11894,8 @@ async function startRunner(options = {}) {
             case "read-file": {
                 try {
                     const { slug, filePath } = command.payload;
-                    const projectPath = join$1(WORKSPACE_ROOT, slug);
-                    const fullPath = join$1(projectPath, filePath);
+                    const projectPath = join(WORKSPACE_ROOT, slug);
+                    const fullPath = join(projectPath, filePath);
                     console.log(`[runner] 📖 Reading file: ${filePath} from project: ${slug}`);
                     // Security: Ensure path is within project directory
                     if (!fullPath.startsWith(projectPath)) {
@@ -12402,8 +11928,8 @@ async function startRunner(options = {}) {
             case "write-file": {
                 try {
                     const { slug, filePath, content } = command.payload;
-                    const projectPath = join$1(WORKSPACE_ROOT, slug);
-                    const fullPath = join$1(projectPath, filePath);
+                    const projectPath = join(WORKSPACE_ROOT, slug);
+                    const fullPath = join(projectPath, filePath);
                     console.log(`[runner] 💾 Writing file: ${filePath} to project: ${slug}`);
                     // Security: Ensure path is within project directory
                     if (!fullPath.startsWith(projectPath)) {
@@ -12433,8 +11959,8 @@ async function startRunner(options = {}) {
             case "list-files": {
                 try {
                     const { slug, path: subPath } = command.payload;
-                    const projectPath = join$1(WORKSPACE_ROOT, slug);
-                    const targetPath = subPath ? join$1(projectPath, subPath) : projectPath;
+                    const projectPath = join(WORKSPACE_ROOT, slug);
+                    const targetPath = subPath ? join(projectPath, subPath) : projectPath;
                     console.log(`[runner] 📁 Listing files for project: ${slug}`);
                     console.log(`[runner]   Path: ${targetPath}`);
                     // Security: Ensure path is within project directory
@@ -12444,8 +11970,8 @@ async function startRunner(options = {}) {
                     const { readdir, stat } = await import('node:fs/promises');
                     const entries = await readdir(targetPath);
                     const files = await Promise.all(entries.map(async (name) => {
-                        const entryPath = join$1(targetPath, name);
-                        const relativePath = subPath ? join$1(subPath, name) : name;
+                        const entryPath = join(targetPath, name);
+                        const relativePath = subPath ? join(subPath, name) : name;
                         const stats = await stat(entryPath);
                         return {
                             name,
@@ -12482,8 +12008,8 @@ async function startRunner(options = {}) {
                 const claudeModelFromPayload = command.payload?.claudeModel;
                 const model = agent === 'claude-code' &&
                     (claudeModelFromPayload === 'claude-haiku-4-5' ||
-                        claudeModelFromPayload === 'claude-sonnet-4-5' ||
-                        claudeModelFromPayload === 'claude-opus-4-5')
+                        claudeModelFromPayload === 'claude-sonnet-4-6' ||
+                        claudeModelFromPayload === 'claude-opus-4-6')
                     ? claudeModelFromPayload
                     : DEFAULT_CLAUDE_MODEL_ID;
                 logger.buildReceived({
@@ -12524,8 +12050,8 @@ async function startRunner(options = {}) {
                     log("selected agent:", agent);
                     const claudeModel = agent === "claude-code" &&
                         (command.payload.claudeModel === "claude-haiku-4-5" ||
-                            command.payload.claudeModel === "claude-sonnet-4-5" ||
-                            command.payload.claudeModel === "claude-opus-4-5")
+                            command.payload.claudeModel === "claude-sonnet-4-6" ||
+                            command.payload.claudeModel === "claude-opus-4-6")
                         ? command.payload.claudeModel
                         : DEFAULT_CLAUDE_MODEL_ID;
                     // For factory-droid, use the droidModel from payload
@@ -12902,7 +12428,7 @@ async function startRunner(options = {}) {
                     // Detect runCommand from built project's package.json
                     try {
                         const { readFileSync, existsSync } = await import('fs');
-                        const packageJsonPath = join$1(projectDirectory, "package.json");
+                        const packageJsonPath = join(projectDirectory, "package.json");
                         if (existsSync(packageJsonPath)) {
                             const packageJson = JSON.parse(readFileSync(packageJsonPath, "utf-8"));
                             let runCommand = null;
@@ -13357,6 +12883,11 @@ Write a brief, professional summary (1-3 sentences) describing what was accompli
             lastCommandReceived = Date.now(); // Reset command timer on new connection
             // Update logger connection status
             logger.setConnected(true);
+            Sentry.logger.info('Runner connected to server', {
+                runnerId: RUNNER_ID,
+                serverUrl: WS_URL,
+                workspace: WORKSPACE_ROOT,
+            });
             debugLog("Health check: ping/pong enabled, command timeout: 5 minutes");
             publishStatus();
             scheduleHeartbeat();
@@ -13429,10 +12960,10 @@ Write a brief, professional summary (1-3 sentences) describing what was accompli
                                     const agent = command.payload.agent ?? 'claude-code';
                                     const claudeModel = agent === 'claude-code' &&
                                         (command.payload.claudeModel === 'claude-haiku-4-5' ||
-                                            command.payload.claudeModel === 'claude-sonnet-4-5' ||
-                                            command.payload.claudeModel === 'claude-opus-4-5')
+                                            command.payload.claudeModel === 'claude-sonnet-4-6' ||
+                                            command.payload.claudeModel === 'claude-opus-4-6')
                                         ? command.payload.claudeModel
-                                        : 'claude-sonnet-4-5';
+                                        : 'claude-sonnet-4-6';
                                     Sentry.metrics.count('runner.build.started', 1, {
                                         attributes: {
                                             project_id: command.projectId,
@@ -13473,10 +13004,10 @@ Write a brief, professional summary (1-3 sentences) describing what was accompli
                                 const agent = command.payload.agent ?? 'claude-code';
                                 const claudeModel = agent === 'claude-code' &&
                                     (command.payload.claudeModel === 'claude-haiku-4-5' ||
-                                        command.payload.claudeModel === 'claude-sonnet-4-5' ||
-                                        command.payload.claudeModel === 'claude-opus-4-5')
+                                        command.payload.claudeModel === 'claude-sonnet-4-6' ||
+                                        command.payload.claudeModel === 'claude-opus-4-6')
                                     ? command.payload.claudeModel
-                                    : 'claude-sonnet-4-5';
+                                    : 'claude-sonnet-4-6';
                                 Sentry.metrics.count('runner.build.started', 1, {
                                     attributes: {
                                         project_id: command.projectId,