feat: Add YOLO mode for rapid prototyping without browser testing

Add a new YOLO (You Only Live Once) mode that skips all browser testing
and regression tests for faster feature iteration during prototyping.

Changes made:

**Core YOLO Mode Implementation:**
- Add --yolo CLI flag to autonomous_agent_demo.py
- Update agent.py to accept yolo_mode parameter and select appropriate prompt
- Modify client.py to conditionally include Playwright MCP server (excluded in YOLO mode)
- Add coding_prompt_yolo.template.md with static analysis only verification
- Add get_coding_prompt_yolo() to prompts.py

**Server/API Updates:**
- Add AgentStartRequest schema with yolo_mode field
- Update AgentStatus to include yolo_mode
- Modify process_manager.py to pass --yolo flag to subprocess
- Update agent router to accept yolo_mode in start request

**UI Updates:**
- Add YOLO toggle button (lightning bolt icon) in AgentControl
- Show YOLO mode indicator when agent is running in YOLO mode
- Add useAgentStatus hook to track current mode
- Update startAgent API to accept yoloMode parameter
- Add YOLO toggle in SpecCreationChat completion flow

**Spec Creation Improvements:**
- Fix create-spec.md to properly replace [FEATURE_COUNT] placeholder
- Add REQUIRED FEATURE COUNT section to initializer_prompt.template.md
- Fix spec_chat_session.py to create security settings file for Claude SDK
- Delete app_spec.txt before spec creation to allow fresh creation

**Documentation:**
- Add YOLO mode section to CLAUDE.md with usage examples
- Add checkpoint.md slash command for creating detailed commits

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

.claude/commands/checkpoint.md

@@ -0,0 +1,40 @@
+---
+description: Create commit with detailed comment
+---
+
+Please create a comprehensive checkpoint commit with the following steps:
+
+1. **Initialize Git if needed**: Run `git init` if git has not been instantiated for the project yet.
+
+2. **Analyze all changes**:
+
+   - Run `git status` to see all tracked and untracked files
+   - Run `git diff` to see detailed changes in tracked files
+   - Run `git log -5 --oneline` to understand the commit message style of this repository
+
+3. **Stage everything**:
+
+   - Add ALL tracked changes (modified and deleted files)
+   - Add ALL untracked files (new files)
+   - Use `git add -A` or `git add .` to stage everything
+
+4. **Create a detailed commit message**:
+
+   - **First line**: Write a clear, concise summary (50-72 chars) describing the primary change
+     - Use imperative mood (e.g., "Add feature" not "Added feature")
+     - Examples: "feat: add user authentication", "fix: resolve database connection issue", "refactor: improve API route structure"
+   - **Body**: Provide a detailed description including:
+     - What changes were made (list of key modifications)
+     - Why these changes were made (purpose/motivation)
+     - Any important technical details or decisions
+     - Breaking changes or migration notes if applicable
+   - **Footer**: Include co-author attribution as shown in the Git Safety Protocol
+
+5. **Execute the commit**: Create the commit with the properly formatted message following this repository's conventions.
+
+IMPORTANT:
+
+- Do NOT skip any files - include everything
+- Make the commit message descriptive enough that someone reviewing the git log can understand what was accomplished
+- Follow the project's existing commit message conventions (check git log first)
+- Include the Claude Code co-author attribution in the commit message

.claude/commands/create-spec.md

@@ -459,10 +459,19 @@ Create a new file using this XML structure:
 If the output directory has an existing `initializer_prompt.md`, read it and update the feature count.
 If not, copy from `.claude/templates/initializer_prompt.template.md` first, then update.
 
-Update the feature count references to match the derived count from Phase 4L:
+**CRITICAL: You MUST update the feature count placeholder:**
 
-- Line containing "create ... test cases" - update to the derived feature count
-- Line containing "Minimum ... features" - update to the derived feature count
+1. Find the line containing `**[FEATURE_COUNT]**` in the "REQUIRED FEATURE COUNT" section
+2. Replace `[FEATURE_COUNT]` with the exact number agreed upon in Phase 4L (e.g., `25`)
+3. The result should read like: `You must create exactly **25** features using the...`
+
+**Example edit:**
+```
+Before: **CRITICAL:** You must create exactly **[FEATURE_COUNT]** features using the `feature_create_bulk` tool.
+After:  **CRITICAL:** You must create exactly **25** features using the `feature_create_bulk` tool.
+```
+
+**Verify the update:** After editing, read the file again to confirm the feature count appears correctly. If `[FEATURE_COUNT]` still appears in the file, the update failed and you must try again.
 
 **Note:** You do NOT need to update `coding_prompt.md` - the coding agent works through features one at a time regardless of total count.