codeloop 0.1.8 → 0.1.9

package/dist/templates/claude-agents.d.ts

@@ -1,5 +1,5 @@
 export declare const CODELOOP_LOOP_MD = "You are a QA loop runner. Use CodeLoop MCP tools to verify code quality.\n\nComplete lifecycle for every development session:\n1. Call codeloop_verify to run all checks\n2. Call codeloop_diagnose to classify failures\n3. Fix only confirmed issues\n4. Repeat verification until all checks pass (AUTOMATIC \u2014 do NOT ask user between loops)\n5. For UI projects: capture screenshots (codeloop_capture_screenshot for every page)\n   then run codeloop_visual_review to analyze them\n6. For UI projects: codeloop_start_recording \u2192 use codeloop_interact with EVERY element\n   (click, type, fill forms, test auth flows, validate errors, scroll, hover, drag) \u2192\n   codeloop_stop_recording \u2192 codeloop_interaction_replay\n   The video MUST show active interaction with every element, never a static page.\n7. Call codeloop_gate_check to evaluate completion (require confidence >= 94%)\n   If gate returns \"continue_fixing\", LOOP BACK to step 1 immediately \u2014 do NOT ask user.\n   Maximum 15 loops before escalation.\n8. MANDATORY: Call codeloop_generate_dev_report and write docs/DEVELOPMENT_LOG.md\n9. Stop when all gates pass at >= 94% or escalation is needed\n\nNever mark a task complete without evidence from CodeLoop.\nNever skip the development log \u2014 it is the final deliverable proving CodeLoop powered the process.\nNever ask the user between loop iterations \u2014 the auto-fix loop is fully automatic.\n";
 export declare const CODELOOP_QA_MD = "You are a QA verification specialist. Run CodeLoop visual review,\nvideo capture, and design comparison. Report structured issues with severity,\nevidence, and fix hints.\n\nFor UI projects, you MUST always perform ALL three:\n1. Screenshot review (codeloop_capture_screenshot for every page + codeloop_visual_review) \u2014 static per-page correctness\n2. Video capture review \u2014 codeloop_start_recording \u2192 use codeloop_interact to interact with EVERY\n   element on every page (click, type, fill forms, test auth, validate errors, scroll, hover, drag)\n   \u2192 codeloop_stop_recording \u2192 codeloop_interaction_replay \u2014 dynamic flow, transitions, animations\n3. Development log generation \u2014 codeloop_generate_dev_report \u2192 docs/DEVELOPMENT_LOG.md\n\nThe video MUST show the app changing state through active interaction using codeloop_interact.\nA recording of a static page is NOT valid evidence. The gate_check will REJECT static videos.\n\nUse codeloop_interact for ALL interactions \u2014 do NOT use raw osascript/PowerShell/xdotool.\ncodeloop_interact works on all platforms: macOS, Windows, Linux, browser (Playwright),\nAndroid emulator (adb), iOS Simulator (simctl), and supports Maestro flow generation.\n\nCRITICAL \u2014 WINDOW FOCUS (especially on single-monitor setups):\n- codeloop_capture_screenshot: ALWAYS pass app_name so the app is brought to front for capture\n- codeloop_start_recording: ALWAYS pass app_name (required) \u2014 brings app to front\n- codeloop_interact: AUTOMATICALLY brings the app to front before each interaction \u2014 this ensures\n  interactions always hit the app window, NOT the IDE, even when the IDE regains focus between calls\n- codeloop_stop_recording: AUTOMATICALLY restores the IDE to front after recording stops\nWithout these focus switches, on single-monitor setups the IDE stays in front and all\nscreenshots/interactions capture the IDE instead of the app.\n";
 export declare const CODELOOP_ADVISOR_MD = "You are an infrastructure and tooling advisor. Use CodeLoop\nrecommendation tools to suggest the best tools based on the\nproject stack, budget, and constraints. Always explain your\nreasoning and include tradeoffs.\n";
-export declare const CLAUDE_MD = "# CodeLoop Integration\n\nCodeLoop provides automated verification for AI-generated code via MCP tools. Follow these rules to ensure code quality.\n\n## After implementing or modifying any feature:\n1. Call codeloop_verify to run all checks on the current project\n2. Read the structured output carefully \u2014 trust deterministic results first, visual diffs second, model opinions third\n3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks\n4. Fix ONLY the confirmed issues listed in the repair tasks \u2014 do not guess or fix unrelated code\n5. After fixing, call codeloop_verify again to confirm the fixes worked\n6. Repeat until all failures are resolved or a blocker is identified\n\n## After codeloop_verify passes \u2014 MANDATORY visual review for UI projects:\nIf the project has a UI (Flutter, web app, mobile app, desktop app):\n\n### Step A: Screenshot review (static correctness)\n1. Write integration tests that OPERATE the app (tap buttons, navigate, interact)\n   - Flutter: golden tests with matchesGoldenFile() in test/\n   - Web: Playwright tests with page.screenshot()\n   - Mobile: Maestro flows (auto-capture screenshots)\n2. Run codeloop_verify \u2014 it runs integration tests and collects screenshots\n3. Call codeloop_visual_review to analyze ALL captured screenshots\n4. Fix any visual/UX issues found\n\n### Step B: Video capture review (dynamic correctness)\nAfter screenshots pass, record yourself OPERATING the app to catch transition,\nanimation, and real-world UX issues that static screenshots miss:\n1. Build and launch the app (if not already running)\n2. Call codeloop_start_recording with app_name \u2014 this brings the app to front and\n   starts recording in the background. The app window is un-minimized automatically.\n3. While recording is active, use codeloop_interact to interact with EVERY element in the app.\n   Do NOT use raw osascript/PowerShell/xdotool \u2014 use codeloop_interact for all interactions.\n   The video MUST show real interactions, not a still image. You must:\n   - Navigate to EVERY page/route in the app\n   - Click EVERY button, link, and navigation element\n   - Fill EVERY form field with test data and submit\n   - Open/close every modal, dropdown, menu, and accordion\n   - Test hover states, tooltips, and interactive components\n   - If auth screens exist: test login (test@example.com / TestPass123!), signup, change-password, logout\n   - Test form validation: submit empty forms, type invalid data, verify error messages\n   - Type+Save (edit \u2192 Cmd+S), Type+Submit (fill \u2192 Submit), Type+Search (query \u2192 Enter)\n   - Double-click, right-click, drag-and-drop, scroll every scrollable area\n   - Mobile: swipe, long-press, back button, deep links, permissions, rotate device\n   - Wait 1-2 seconds between each interaction so frames capture each state change\n4. Call codeloop_stop_recording \u2014 this finalizes the video and restores the IDE to the front.\n5. Call codeloop_interaction_replay with the run_id and expected_flow description\n6. Analyze the returned frame sequence for: broken transitions, stuck loading states,\n   window sizing issues, animation glitches, navigation dead-ends, and flow completion\n7. Fix any dynamic UX issues found\n8. ONLY THEN proceed to gate_check\n\nA video of a static idle app is NOT valid evidence. The video MUST show the app\nchanging state \u2014 buttons clicked, pages loaded, forms filled, navigation happening.\nWindow management is automatic \u2014 CodeLoop restores the IDE after capture.\nIf detection fails, it falls back to activating Cursor/VS Code/Terminal.\n\nDo NOT call gate_check for a UI project without BOTH screenshot AND video evidence.\n\n## THE CODELOOP AUTO-FIX LOOP (MANDATORY)\n\nThis is an AUTOMATIC loop. You do NOT ask the user for permission to continue.\nYou do NOT stop and report partial progress. You keep going until the gate passes.\n\nRULES:\n- If gate returns \"continue_fixing\": GO BACK TO codeloop_verify IMMEDIATELY.\n  Do NOT ask the user. Do NOT report partial results. Just fix and re-verify.\n- If gate returns \"escalate\": STOP and report blockers to the user.\n  Only escalate after 8 failed fix attempts OR a true blocker.\n- If gate returns \"ready_for_review\" with confidence >= 94%: proceed to dev report.\n- Maximum loop iterations: 15. After 15 loops without reaching 94%, escalate.\n\n## Before marking any task or feature as complete:\n1. Call codeloop_check_workflow to see which verification steps are still pending\n2. Complete ALL pending steps listed by codeloop_check_workflow\n3. Call codeloop_gate_check with the run_id, spec path, and acceptance path\n4. If the result says \"continue_fixing\", LOOP BACK to codeloop_verify immediately \u2014 do NOT ask the user\n5. If the result says \"escalate\", stop and report the blockers to the developer\n6. Only declare the task complete when gate_check returns \"ready_for_review\" with confidence >= 94%\n7. Call codeloop_check_workflow one final time to confirm everything is done\n\n## After the ENTIRE development loop is complete \u2014 MANDATORY development log:\nOnce all features are implemented, all gate checks pass, and the project is ready,\nyou MUST produce a full-scale development log. This is NOT optional.\n\n1. Call codeloop_generate_dev_report with the project name and description\n2. Use the returned data to generate a comprehensive development log at docs/DEVELOPMENT_LOG.md\n3. The report MUST include:\n   - Executive Summary \u2014 what was built, final confidence score, key metrics\n   - Development Timeline \u2014 chronological list of every CodeLoop verification run\n   - CodeLoop Verification Process \u2014 checks ran, platforms, issues caught\n   - Visual Verification Evidence \u2014 screenshots, videos, interaction testing\n   - Video Capture Sessions \u2014 recordings, interactions performed, issues found\n   - Quality Gates Passed \u2014 build, tests, visual regression, acceptance criteria\n   - Bugs Found & Fixed \u2014 every issue found by CodeLoop with severity and fix\n   - Cross-Platform Coverage \u2014 which OS and platform combinations were tested\n   - CodeLoop Value Highlights \u2014 automated verification, visual review, video capture\n   - \"Verified by CodeLoop\" badge with final confidence score and run IDs\n4. Present the report to the developer as the final deliverable alongside the working project\n\n## When you have attempted to fix an issue 2 or more times and tests still fail:\n- You MUST call codeloop_diagnose before making another fix attempt\n- Read the repair tasks carefully \u2014 the structured analysis is more reliable than guessing from raw output\n\n## For multi-section projects:\n- Call codeloop_section_status to see current progress and which section to work on next\n- If integration_due is true, run codeloop_verify with scope \"full\" first and fix any regressions\n- After ALL sections pass, run codeloop_release_readiness for a final quality assessment\n- Call codeloop_generate_dev_report to produce a comprehensive development log at docs/DEVELOPMENT_LOG.md\n\n## When choosing tools or infrastructure:\n- Call codeloop_recommend_tool with the relevant category and detected stack\n- Present results with reasoning, tradeoffs, and pricing\n- Always prefer CLI-based setup over web dashboard (e.g., `vercel login`, `heroku login`, `firebase login`)\n- Guide the user through CLI installation and authentication when needed\n- Verify CLI auth with a status command after login (e.g., `vercel whoami`, `heroku auth:whoami`)\n\n## After codeloop_gate_check returns \"ready_for_review\" with confidence >= 94%:\n- Generate or update the project README.md with:\n  - Project description and key features\n  - Prerequisites and setup instructions\n  - How to run locally\n  - How to run tests\n  - Architecture overview (key directories and files)\n  - CodeLoop verification: \"Verified by CodeLoop (run_id: {id}). Confidence: {score}%. Gates passed: {list}. Tests: {passed}/{total} passed.\"\n  - Deployment instructions (if applicable)\n  - Known issues (if any remain from codeloop_diagnose)\n\n## UI verification via integration tests + video capture:\nWrite integration tests that OPERATE the app and capture golden screenshots.\n- Flutter: matchesGoldenFile() captures each page/interaction state\n- Web: Playwright page.screenshot() per test\n- Mobile: Maestro auto-captures per flow\ncodeloop_verify runs these tests and collects all golden PNGs automatically.\ncodeloop_visual_review returns them as images for analysis.\n\nAfter screenshot review, actively operate the app while recording:\n- Call codeloop_start_recording with app_name and optional target_type (brings app to front, starts recording + log capture)\n- Use codeloop_interact for ALL interactions \u2014 each call automatically brings the app to front\n  before performing the interaction, ensuring it hits the app not the IDE:\n  clicks, typing, drawing/dragging, scrolling, right-click, key presses, etc.\n  Read source code to determine what interactions the app needs.\n- Do NOT use raw osascript/PowerShell/xdotool \u2014 always use codeloop_interact\n- Wait 1-2s between interactions; use codeloop_capture_screenshot (with app_name) to verify each worked\n- A static video is NOT valid \u2014 the video must show state changes\n- Call codeloop_stop_recording (finalizes video + logs, restores IDE to front)\n- Call codeloop_interaction_replay to extract frames, app logs, and analyze the flow\n  The AI correlates visual frames with runtime log errors for comprehensive analysis\n\n## Terminal authorization:\n- Common development commands (flutter, npm, git, brew, etc.) are pre-authorized via permissions.allow\n- If a command is blocked, check the allow-list in .claude/settings.local.json\n- For Cursor users: before running your first command, tell the user:\n  \"To avoid clicking 'Run' on every command, enable Cursor Auto-Run:\n  Cmd+Shift+J \u2192 Features \u2192 Terminal \u2192 Auto-Run Mode \u2192 Yolo\"\n- For service provider CLIs: install via the recommended package manager, then authenticate\n\n## Never:\n- Mark a task complete without evidence from codeloop_gate_check\n- Skip visual review (screenshots + video) for a project that has a user interface\n- Skip video capture \u2014 screenshots alone miss transitions, animations, and flow bugs\n- Skip the development log \u2014 codeloop_generate_dev_report MUST be called when the loop completes\n- Let a recording run idle \u2014 the video MUST show active interaction with every UI element\n- Ignore codeloop_verify results\n- Modify files outside the allowed_file_scope from repair tasks\n- Continue fixing after 8 failed repair attempts \u2014 escalate instead\n\n## Development lifecycle \u2014 complete workflow:\nEvery CodeLoop-powered development session follows this mandatory lifecycle:\n1. Implement \u2192 write/modify code\n2. Verify \u2192 codeloop_verify (tests, lint, build)\n3. Diagnose \u2192 codeloop_diagnose (if failures)\n4. Fix \u2192 repair confirmed issues only \u2192 LOOP BACK to step 2\n5. Screenshot \u2192 codeloop_capture_screenshot + codeloop_visual_review (all pages)\n6. Video \u2192 codeloop_start_recording \u2192 codeloop_interact with ALL elements \u2192 codeloop_stop_recording\n7. Replay \u2192 codeloop_interaction_replay (analyze frames + logs)\n8. Gate \u2192 codeloop_gate_check (confidence >= 94%) \u2014 if \"continue_fixing\", LOOP to step 2 automatically\n9. Report \u2192 codeloop_generate_dev_report \u2192 write docs/DEVELOPMENT_LOG.md\n10. Deliver \u2192 present working project + development log to developer\n\nSteps 5-7 are MANDATORY for any project with a UI. Step 9 is MANDATORY for every project.\nThe loop between steps 2-8 is AUTOMATIC. Do NOT ask the user between iterations.\n\n## Cross-Platform Video Capture Coverage:\nCodeLoop supports ALL developer operating systems and app types:\n\nmacOS:\n- Desktop (Flutter/native): ffmpeg avfoundation + multi-monitor detection, osascript interactions\n- Web: ffmpeg avfoundation + Playwright --headed video, Playwright interactions\n- iOS Simulator: xcrun simctl io recordVideo, Maestro/simctl interactions\n- Android Emulator: adb screenrecord, adb input interactions\n\nWindows:\n- Desktop (Flutter/.NET): ffmpeg gdigrab + window bounds, PowerShell user32.dll interactions\n- Web: ffmpeg gdigrab + Playwright --headed video, Playwright interactions\n- Android Emulator: adb screenrecord, adb input interactions\n\nLinux:\n- Desktop (Flutter/native): ffmpeg x11grab + window bounds, xdotool interactions\n- Web: ffmpeg x11grab + Playwright --headed video, Playwright interactions\n- Android Emulator: adb screenrecord, adb input interactions\n\nFor web apps: ALWAYS use npx playwright test --headed --workers=1 during ffmpeg recording\nso the developer can see the browser interaction happening on screen.\n";
+export declare const CLAUDE_MD = "# CodeLoop Integration\n\nCodeLoop provides automated verification for AI-generated code via MCP tools. Follow these rules to ensure code quality.\n\n## After implementing or modifying any feature:\n1. Call codeloop_verify to run all checks on the current project\n2. Read the structured output carefully \u2014 trust deterministic results first, visual diffs second, model opinions third\n3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks\n4. Fix ONLY the confirmed issues listed in the repair tasks \u2014 do not guess or fix unrelated code\n5. After fixing, call codeloop_verify again to confirm the fixes worked\n6. Repeat until all failures are resolved or a blocker is identified\n\n## After codeloop_verify passes \u2014 MANDATORY visual review for UI projects:\nIf the project has a UI (Flutter, web app, mobile app, desktop app):\n\n### Step A: Screenshot review (static correctness)\n1. Write integration tests that OPERATE the app (tap buttons, navigate, interact)\n   - Flutter: golden tests with matchesGoldenFile() in test/\n   - Web: Playwright tests with page.screenshot()\n   - Mobile: Maestro flows (auto-capture screenshots)\n2. Run codeloop_verify \u2014 it runs integration tests and collects screenshots\n3. Call codeloop_visual_review to analyze ALL captured screenshots\n4. Fix any visual/UX issues found\n\n### Step B: Video capture review (dynamic correctness)\nAfter screenshots pass, record yourself OPERATING the app to catch transition,\nanimation, and real-world UX issues that static screenshots miss:\n1. Build and launch the app (if not already running)\n2. Call codeloop_start_recording with app_name \u2014 this brings the app to front and\n   starts recording in the background. The app window is un-minimized automatically.\n3. While recording is active, use codeloop_interact to interact with EVERY element in the app.\n   Do NOT use raw osascript/PowerShell/xdotool \u2014 use codeloop_interact for all interactions.\n   The video MUST show real interactions, not a still image. Follow this MANDATORY checklist:\n\n   A. **Navigation** \u2014 visit EVERY page/route. After each navigation, verify the page loaded\n      (not 404). Use navigate_url action. Wait 2s between navigations.\n\n   B. **Form filling** \u2014 for EVERY input field on EVERY page:\n      - Click into the field (action: \"click\" with coordinates or selector)\n      - Type test data (action: \"type\" with text) \u2014 use realistic data:\n        Email: \"test@example.com\", Password: \"TestPass123!\", Name: \"Test User\"\n      - After filling ALL fields, click the submit/save button\n      - Verify: submit empty form first to test validation error messages\n      - Then fill with valid data and submit to test success path\n\n   C. **Auth flows** (if login/signup pages exist):\n      - Go to signup page \u2192 fill email + password + name \u2192 submit \u2192 check response\n      - Go to login page \u2192 try empty submit (validation) \u2192 fill credentials \u2192 submit\n      - Test password visibility toggle if present\n      - Test \"Forgot Password\" link if present\n\n   D. **Click EVERY interactive element:**\n      - All buttons, links, navigation items, tabs, toggles, dropdowns\n      - Scroll to bottom of every scrollable area (action: \"scroll\" direction: \"down\")\n      - Open and close every modal, drawer, accordion, tooltip\n\n   E. **404 detection** \u2014 after navigating to each page, take a screenshot or check the\n      page content. If any page shows 404/error/blank, report it as a critical issue.\n\n   F. **Compound patterns:** type+submit, type+search, copy+paste, keyboard shortcuts\n\n   G. **Mobile** (if applicable): swipe, long-press, back button, rotate, deep links\n\n   Wait 1-2 seconds between each interaction so frames capture each state change.\n4. Call codeloop_stop_recording \u2014 this finalizes the video and restores the IDE to the front.\n5. Call codeloop_interaction_replay with the run_id and expected_flow description\n6. Analyze the returned frame sequence for: broken transitions, stuck loading states,\n   window sizing issues, animation glitches, navigation dead-ends, and flow completion\n7. Fix any dynamic UX issues found\n8. ONLY THEN proceed to gate_check\n\nA video of a static idle app is NOT valid evidence. The video MUST show the app\nchanging state \u2014 buttons clicked, pages loaded, forms filled, navigation happening.\nWindow management is automatic \u2014 CodeLoop restores the IDE after capture.\nIf detection fails, it falls back to activating Cursor/VS Code/Terminal.\n\nDo NOT call gate_check for a UI project without BOTH screenshot AND video evidence.\n\n## THE CODELOOP AUTO-FIX LOOP (MANDATORY)\n\nThis is an AUTOMATIC loop. You do NOT ask the user for permission to continue.\nYou do NOT stop and report partial progress. You keep going until the gate passes.\n\nRULES:\n- If gate returns \"continue_fixing\": GO BACK TO codeloop_verify IMMEDIATELY.\n  Do NOT ask the user. Do NOT report partial results. Just fix and re-verify.\n- If gate returns \"escalate\": STOP and report blockers to the user.\n  Only escalate after 8 failed fix attempts OR a true blocker.\n- If gate returns \"ready_for_review\" with confidence >= 94%: proceed to dev report.\n- Maximum loop iterations: 15. After 15 loops without reaching 94%, escalate.\n\n## Before marking any task or feature as complete:\n1. Call codeloop_check_workflow to see which verification steps are still pending\n2. Complete ALL pending steps listed by codeloop_check_workflow\n3. Call codeloop_gate_check with the run_id, spec path, and acceptance path\n4. If the result says \"continue_fixing\", LOOP BACK to codeloop_verify immediately \u2014 do NOT ask the user\n5. If the result says \"escalate\", stop and report the blockers to the developer\n6. Only declare the task complete when gate_check returns \"ready_for_review\" with confidence >= 94%\n7. Call codeloop_check_workflow one final time to confirm everything is done\n\n## After the ENTIRE development loop is complete \u2014 MANDATORY development log:\nOnce all features are implemented, all gate checks pass, and the project is ready,\nyou MUST produce a full-scale development log. This is NOT optional.\n\n1. Call codeloop_generate_dev_report with the project name and description\n2. Use the returned data to generate a comprehensive development log at docs/DEVELOPMENT_LOG.md\n3. The report MUST include:\n   - Executive Summary \u2014 what was built, final confidence score, key metrics\n   - Development Timeline \u2014 chronological list of every CodeLoop verification run\n   - CodeLoop Verification Process \u2014 checks ran, platforms, issues caught\n   - Visual Verification Evidence \u2014 screenshots, videos, interaction testing\n   - Video Capture Sessions \u2014 recordings, interactions performed, issues found\n   - Quality Gates Passed \u2014 build, tests, visual regression, acceptance criteria\n   - Bugs Found & Fixed \u2014 every issue found by CodeLoop with severity and fix\n   - Cross-Platform Coverage \u2014 which OS and platform combinations were tested\n   - CodeLoop Value Highlights \u2014 automated verification, visual review, video capture\n   - \"Verified by CodeLoop\" badge with final confidence score and run IDs\n4. Present the report to the developer as the final deliverable alongside the working project\n\n## When you have attempted to fix an issue 2 or more times and tests still fail:\n- You MUST call codeloop_diagnose before making another fix attempt\n- Read the repair tasks carefully \u2014 the structured analysis is more reliable than guessing from raw output\n\n## For multi-section projects:\n- Call codeloop_section_status to see current progress and which section to work on next\n- If integration_due is true, run codeloop_verify with scope \"full\" first and fix any regressions\n- After ALL sections pass, run codeloop_release_readiness for a final quality assessment\n- Call codeloop_generate_dev_report to produce a comprehensive development log at docs/DEVELOPMENT_LOG.md\n\n## When choosing tools or infrastructure:\n- Call codeloop_recommend_tool with the relevant category and detected stack\n- Present results with reasoning, tradeoffs, and pricing\n- Always prefer CLI-based setup over web dashboard (e.g., `vercel login`, `heroku login`, `firebase login`)\n- Guide the user through CLI installation and authentication when needed\n- Verify CLI auth with a status command after login (e.g., `vercel whoami`, `heroku auth:whoami`)\n\n## After codeloop_gate_check returns \"ready_for_review\" with confidence >= 94%:\n- Generate or update the project README.md with:\n  - Project description and key features\n  - Prerequisites and setup instructions\n  - How to run locally\n  - How to run tests\n  - Architecture overview (key directories and files)\n  - CodeLoop verification: \"Verified by CodeLoop (run_id: {id}). Confidence: {score}%. Gates passed: {list}. Tests: {passed}/{total} passed.\"\n  - Deployment instructions (if applicable)\n  - Known issues (if any remain from codeloop_diagnose)\n\n## UI verification via integration tests + video capture:\nWrite integration tests that OPERATE the app and capture golden screenshots.\n- Flutter: matchesGoldenFile() captures each page/interaction state\n- Web: Playwright page.screenshot() per test\n- Mobile: Maestro auto-captures per flow\ncodeloop_verify runs these tests and collects all golden PNGs automatically.\ncodeloop_visual_review returns them as images for analysis.\n\nAfter screenshot review, actively operate the app while recording:\n- Call codeloop_start_recording with app_name and optional target_type (brings app to front, starts recording + log capture)\n- Use codeloop_interact for ALL interactions \u2014 each call automatically brings the app to front\n  before performing the interaction, ensuring it hits the app not the IDE:\n  clicks, typing, drawing/dragging, scrolling, right-click, key presses, etc.\n  Read source code to determine what interactions the app needs.\n- Do NOT use raw osascript/PowerShell/xdotool \u2014 always use codeloop_interact\n- Wait 1-2s between interactions; use codeloop_capture_screenshot (with app_name) to verify each worked\n- A static video is NOT valid \u2014 the video must show state changes\n- Call codeloop_stop_recording (finalizes video + logs, restores IDE to front)\n- Call codeloop_interaction_replay to extract frames, app logs, and analyze the flow\n  The AI correlates visual frames with runtime log errors for comprehensive analysis\n\n## Terminal authorization:\n- Common development commands (flutter, npm, git, brew, etc.) are pre-authorized via permissions.allow\n- If a command is blocked, check the allow-list in .claude/settings.local.json\n- For Cursor users: before running your first command, tell the user:\n  \"To avoid clicking 'Run' on every command, enable Cursor Auto-Run:\n  Cmd+Shift+J \u2192 Features \u2192 Terminal \u2192 Auto-Run Mode \u2192 Yolo\"\n- For service provider CLIs: install via the recommended package manager, then authenticate\n\n## Never:\n- Mark a task complete without evidence from codeloop_gate_check\n- Skip visual review (screenshots + video) for a project that has a user interface\n- Skip video capture \u2014 screenshots alone miss transitions, animations, and flow bugs\n- Skip the development log \u2014 codeloop_generate_dev_report MUST be called when the loop completes\n- Let a recording run idle \u2014 the video MUST show active interaction with every UI element\n- Ignore codeloop_verify results\n- Modify files outside the allowed_file_scope from repair tasks\n- Continue fixing after 8 failed repair attempts \u2014 escalate instead\n\n## Development lifecycle \u2014 complete workflow:\nEvery CodeLoop-powered development session follows this mandatory lifecycle:\n1. Implement \u2192 write/modify code\n2. Verify \u2192 codeloop_verify (tests, lint, build)\n3. Diagnose \u2192 codeloop_diagnose (if failures)\n4. Fix \u2192 repair confirmed issues only \u2192 LOOP BACK to step 2\n5. Screenshot \u2192 codeloop_capture_screenshot + codeloop_visual_review (all pages)\n6. Video \u2192 codeloop_start_recording \u2192 codeloop_interact with ALL elements \u2192 codeloop_stop_recording\n7. Replay \u2192 codeloop_interaction_replay (analyze frames + logs)\n8. Gate \u2192 codeloop_gate_check (confidence >= 94%) \u2014 if \"continue_fixing\", LOOP to step 2 automatically\n9. Report \u2192 codeloop_generate_dev_report \u2192 write docs/DEVELOPMENT_LOG.md\n10. Deliver \u2192 present working project + development log to developer\n\nSteps 5-7 are MANDATORY for any project with a UI. Step 9 is MANDATORY for every project.\nThe loop between steps 2-8 is AUTOMATIC. Do NOT ask the user between iterations.\n\n## Cross-Platform Video Capture Coverage:\nCodeLoop supports ALL developer operating systems and app types:\n\nmacOS:\n- Desktop (Flutter/native): ffmpeg avfoundation + multi-monitor detection, osascript interactions\n- Web: ffmpeg avfoundation + Playwright --headed video, Playwright interactions\n- iOS Simulator: xcrun simctl io recordVideo, Maestro/simctl interactions\n- Android Emulator: adb screenrecord, adb input interactions\n\nWindows:\n- Desktop (Flutter/.NET): ffmpeg gdigrab + window bounds, PowerShell user32.dll interactions\n- Web: ffmpeg gdigrab + Playwright --headed video, Playwright interactions\n- Android Emulator: adb screenrecord, adb input interactions\n\nLinux:\n- Desktop (Flutter/native): ffmpeg x11grab + window bounds, xdotool interactions\n- Web: ffmpeg x11grab + Playwright --headed video, Playwright interactions\n- Android Emulator: adb screenrecord, adb input interactions\n\nFor web apps: ALWAYS use npx playwright test --headed --workers=1 during ffmpeg recording\nso the developer can see the browser interaction happening on screen.\n";
 //# sourceMappingURL=claude-agents.d.ts.map

package/dist/templates/claude-agents.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"claude-agents.d.ts","sourceRoot":"","sources":["../../src/templates/claude-agents.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB,85CAsB5B,CAAC;AAEF,eAAO,MAAM,cAAc,45DA0B1B,CAAC;AAEF,eAAO,MAAM,mBAAmB,8NAI/B,CAAC;AAEF,eAAO,MAAM,SAAS,qrZA2MrB,CAAC"}
+{"version":3,"file":"claude-agents.d.ts","sourceRoot":"","sources":["../../src/templates/claude-agents.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,gBAAgB,85CAsB5B,CAAC;AAEF,eAAO,MAAM,cAAc,45DA0B1B,CAAC;AAEF,eAAO,MAAM,mBAAmB,8NAI/B,CAAC;AAEF,eAAO,MAAM,SAAS,+nbA+NrB,CAAC"}

package/dist/templates/claude-agents.js

@@ -85,18 +85,38 @@ animation, and real-world UX issues that static screenshots miss:
    starts recording in the background. The app window is un-minimized automatically.
 3. While recording is active, use codeloop_interact to interact with EVERY element in the app.
    Do NOT use raw osascript/PowerShell/xdotool — use codeloop_interact for all interactions.
-   The video MUST show real interactions, not a still image. You must:
-   - Navigate to EVERY page/route in the app
-   - Click EVERY button, link, and navigation element
-   - Fill EVERY form field with test data and submit
-   - Open/close every modal, dropdown, menu, and accordion
-   - Test hover states, tooltips, and interactive components
-   - If auth screens exist: test login (test@example.com / TestPass123!), signup, change-password, logout
-   - Test form validation: submit empty forms, type invalid data, verify error messages
-   - Type+Save (edit → Cmd+S), Type+Submit (fill → Submit), Type+Search (query → Enter)
-   - Double-click, right-click, drag-and-drop, scroll every scrollable area
-   - Mobile: swipe, long-press, back button, deep links, permissions, rotate device
-   - Wait 1-2 seconds between each interaction so frames capture each state change
+   The video MUST show real interactions, not a still image. Follow this MANDATORY checklist:
+
+   A. **Navigation** — visit EVERY page/route. After each navigation, verify the page loaded
+      (not 404). Use navigate_url action. Wait 2s between navigations.
+
+   B. **Form filling** — for EVERY input field on EVERY page:
+      - Click into the field (action: "click" with coordinates or selector)
+      - Type test data (action: "type" with text) — use realistic data:
+        Email: "test@example.com", Password: "TestPass123!", Name: "Test User"
+      - After filling ALL fields, click the submit/save button
+      - Verify: submit empty form first to test validation error messages
+      - Then fill with valid data and submit to test success path
+
+   C. **Auth flows** (if login/signup pages exist):
+      - Go to signup page → fill email + password + name → submit → check response
+      - Go to login page → try empty submit (validation) → fill credentials → submit
+      - Test password visibility toggle if present
+      - Test "Forgot Password" link if present
+
+   D. **Click EVERY interactive element:**
+      - All buttons, links, navigation items, tabs, toggles, dropdowns
+      - Scroll to bottom of every scrollable area (action: "scroll" direction: "down")
+      - Open and close every modal, drawer, accordion, tooltip
+
+   E. **404 detection** — after navigating to each page, take a screenshot or check the
+      page content. If any page shows 404/error/blank, report it as a critical issue.
+
+   F. **Compound patterns:** type+submit, type+search, copy+paste, keyboard shortcuts
+
+   G. **Mobile** (if applicable): swipe, long-press, back button, rotate, deep links
+
+   Wait 1-2 seconds between each interaction so frames capture each state change.
 4. Call codeloop_stop_recording — this finalizes the video and restores the IDE to the front.
 5. Call codeloop_interaction_replay with the run_id and expected_flow description
 6. Analyze the returned frame sequence for: broken transitions, stuck loading states,

package/dist/templates/claude-agents.js.map

@@ -1 +1 @@
-{"version":3,"file":"claude-agents.js","sourceRoot":"","sources":["../../src/templates/claude-agents.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsB/B,CAAC;AAEF,MAAM,CAAC,MAAM,cAAc,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;CA0B7B,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;CAIlC,CAAC;AAEF,MAAM,CAAC,MAAM,SAAS,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA2MxB,CAAC"}
+{"version":3,"file":"claude-agents.js","sourceRoot":"","sources":["../../src/templates/claude-agents.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,gBAAgB,GAAG;;;;;;;;;;;;;;;;;;;;;;CAsB/B,CAAC;AAEF,MAAM,CAAC,MAAM,cAAc,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;CA0B7B,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;CAIlC,CAAC;AAEF,MAAM,CAAC,MAAM,SAAS,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+NxB,CAAC"}

package/dist/templates/cursor-rules.d.ts

@@ -1,4 +1,4 @@
-export declare const CORE_MDC = "---\ndescription: CodeLoop core verification rules for all projects\nglobs: [\"**/*\"]\n---\n\n# CodeLoop Verification Rules\n\n## FIRST: Before running any terminal commands, show this to the user:\n\nBefore you run your first terminal command in this session, display this\nmessage to the user in the chat:\n\n\"\u26A1 **CodeLoop Quick Setup** \u2014 To avoid clicking 'Run' on every terminal\ncommand, enable Cursor Auto-Run (one-time):\n**Cmd+Shift+J** \u2192 Features \u2192 Terminal \u2192 Auto-Run Mode \u2192 **Yolo**\n(or 'Auto-Run with Allowlist' for safer mode)\"\n\nOnly show this once per session. If the user has already enabled Auto-Run,\nthey can ignore this message.\n\n## After implementing or modifying any feature:\n1. Call codeloop_verify to run all checks on the current project\n2. Read the structured output carefully \u2014 trust deterministic results first, visual diffs second, model opinions third\n3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks\n4. Fix ONLY the confirmed issues listed in the repair tasks \u2014 do not guess or fix unrelated code\n5. After fixing, call codeloop_verify again to confirm the fixes worked\n6. Repeat until all failures are resolved or a blocker is identified\n\n## After codeloop_verify passes \u2014 MANDATORY visual review for UI projects:\nIf the project has a UI (Flutter, web app, mobile app, desktop app):\n\n### Step A: Screenshot review (static correctness)\n1. Build and run the app\n2. Call codeloop_discover_screens to find all routes/pages from source code\n3. Navigate to each page and call codeloop_capture_screenshot for each one\n4. Explore buttons, tabs, menus, and links to find additional pages\n5. Call codeloop_visual_review to analyze ALL captured screenshots\n6. Fix any visual/UX issues found (layout, sizing, responsiveness, usability)\n\n### Step B: Video capture review (dynamic correctness)\nAfter screenshots pass, record yourself OPERATING the app to catch transition,\nanimation, and real-world UX issues that static screenshots miss:\n1. Build and launch the app (if not already running)\n2. Call codeloop_start_recording with app_name \u2014 this brings the app to front and\n   starts recording in the background. The app window is un-minimized automatically.\n3. While recording is active, use codeloop_interact to interact with EVERY element in the app.\n   Do NOT use raw osascript/PowerShell/xdotool \u2014 use codeloop_interact for all interactions.\n   The video MUST show real interactions, not a still image. You must:\n   - Navigate to EVERY page/route in the app\n   - Click EVERY button, link, and navigation element\n   - Fill EVERY form field with test data and submit\n   - Open/close every modal, dropdown, menu, and accordion\n   - Test hover states, tooltips, and interactive components\n   - If auth screens exist: test login (test@example.com / TestPass123!), signup, change-password, logout\n   - Test form validation: submit empty forms, type invalid data, verify error messages\n   - Type+Save (edit \u2192 Cmd+S), Type+Submit (fill \u2192 Submit), Type+Search (query \u2192 Enter)\n   - Double-click, right-click, drag-and-drop, scroll every scrollable area\n   - Mobile: swipe, long-press, back button, deep links, permissions, rotate device\n4. Wait 1-2 seconds between each interaction so frames capture each state change.\n5. Call codeloop_stop_recording \u2014 this finalizes the video and restores the IDE to the front.\n6. Call codeloop_interaction_replay with the run_id and expected_flow description\n7. Analyze the returned frame sequence for: broken transitions, stuck loading states,\n   window sizing issues, animation glitches, navigation dead-ends, and flow completion\n8. Fix any dynamic UX issues found\n9. ONLY THEN proceed to gate_check\n\n### How to operate the app during recording:\n\nUse the codeloop_interact tool for ALL interactions. Do NOT use raw osascript,\nPowerShell, xdotool, adb, or simctl commands directly. codeloop_interact\nhandles all platforms automatically:\n\n**Available actions:** click, double_click, right_click, hover, type, keystroke,\nhotkey, scroll, drag_drop, long_press, type_and_submit, type_and_tab, fill_form,\nselect_option, toggle, upload_file, navigate_url, navigate_back, wait, swipe,\nback_button, home_button, deep_link, grant_permission, rotate_device,\nbiometric_auth, launch_app, clear_app_data, mock_location, simulate_network,\nmaestro_flow, win_ui_inspect, win_ui_automate, sequence.\n\n**Examples:**\n- Click a button: `codeloop_interact(action: \"click\", x: 200, y: 300)`\n- Click browser element: `codeloop_interact(action: \"click\", target_type: \"browser\", selector: \"#submit-btn\")`\n- Type in field: `codeloop_interact(action: \"type\", target_type: \"browser\", selector: \"#email\", text: \"test@example.com\")`\n- Fill form + submit: `codeloop_interact(action: \"fill_form\", target_type: \"browser\", fields: [{selector: \"#email\", value: \"test@example.com\"}, {selector: \"#password\", value: \"TestPass123!\"}], submit_selector: \"#login-btn\")`\n- Scroll down: `codeloop_interact(action: \"scroll\", direction: \"down\", amount: 300)`\n- Press Enter: `codeloop_interact(action: \"keystroke\", key: \"enter\")`\n- Save with hotkey: `codeloop_interact(action: \"hotkey\", keys: \"cmd+s\")`\n- Type and search: `codeloop_interact(action: \"type_and_submit\", selector: \"#search\", text: \"query\")`\n- Android tap: `codeloop_interact(action: \"click\", target_type: \"android_emulator\", x: 540, y: 960)`\n- Android swipe: `codeloop_interact(action: \"swipe\", target_type: \"android_emulator\", x: 540, y: 1200, x2: 540, y2: 600)`\n- iOS deep link: `codeloop_interact(action: \"deep_link\", target_type: \"ios_simulator\", url: \"myapp://profile\")`\n- Maestro flow: `codeloop_interact(action: \"maestro_flow\", maestro_steps: [\"tap on \\\"Login\\\"\", \"type \\\"hello\\\"\", \"tap on \\\"Submit\\\"\"])`\n\n**Mandatory interaction depth during recording:**\n- Navigate to EVERY page/route\n- Click EVERY button, link, nav element\n- Fill EVERY form field with test data and submit\n- Test auth flows if present: login, signup, change-password, logout\n- Test form validation: empty submissions, invalid data, error messages\n- Test compound patterns: type+save, type+submit, type+search, copy+paste, undo+redo\n- Open/close every modal, dropdown, accordion, tooltip\n- Scroll to bottom of every scrollable area\n- Test double-click, right-click, hover, drag-and-drop if applicable\n- Mobile: swipe, long-press, back button, rotate device, deep links\n\n**App logs:** CodeLoop automatically captures app runtime logs during video recording:\n- Flutter apps: flutter logs output\n- Android: adb logcat filtered to the app\n- iOS Simulator: simctl log stream\n- Native macOS: log stream --process\n- Web: browser console events via Playwright\n- Backend: dev server stdout/stderr\nThese logs are included in the interaction_replay analysis so you can correlate\nvisual frames with runtime errors, warnings, and exceptions.\n\nWindow management: CodeLoop automatically brings the app to front before capture\n(even if minimized) and restores the IDE back to front after capture completes.\nIf the IDE is not restored, CodeLoop falls back to activating Cursor/VS Code/Terminal.\n\nDo NOT call gate_check for a UI project without BOTH screenshot AND video evidence.\nScreenshots catch per-page layout issues. Video catches cross-page flow issues,\ntransitions, animations, real window behavior, and interaction bugs that static\nscreenshots miss entirely (e.g., wrong window size, broken navigation, stuck modals).\n\n## THE CODELOOP AUTO-FIX LOOP (MANDATORY)\n\nThis is an AUTOMATIC loop. You do NOT ask the user for permission to continue.\nYou do NOT stop and report partial progress. You keep going until the gate passes.\n\nLoop: Verify \u2192 Diagnose \u2192 Fix \u2192 Verify \u2192 ... \u2192 Screenshots \u2192 Video+Interact \u2192 Replay \u2192 Gate\n\nRULES:\n- If gate returns \"continue_fixing\": GO BACK TO codeloop_verify IMMEDIATELY.\n  Do NOT ask the user. Do NOT report partial results. Just fix and re-verify.\n- If gate returns \"escalate\": STOP and report blockers to the user.\n  Only escalate after 8 failed fix attempts OR a true blocker (missing dependency, etc.)\n- If gate returns \"ready_for_review\" with confidence >= 94%: proceed to dev report.\n- The user only sees the final result AFTER the gate passes at >= 94%.\n- Maximum loop iterations: 15. After 15 loops without reaching 94%, escalate.\n\n## Before marking any task or feature as complete:\n1. Call codeloop_check_workflow to see which verification steps are still pending\n2. Complete ALL pending steps listed by codeloop_check_workflow\n3. Call codeloop_gate_check with the run_id, spec path, and acceptance path\n4. If the result says \"continue_fixing\", LOOP BACK to codeloop_verify immediately \u2014 do NOT ask the user\n5. If the result says \"escalate\", stop and report the blockers to the developer\n6. Only declare the task complete when gate_check returns \"ready_for_review\" with confidence >= 94%\n7. Call codeloop_check_workflow one final time to confirm everything is done\n\n## After the ENTIRE development loop is complete \u2014 MANDATORY development log:\nOnce all features are implemented, all gate checks pass, and the project is ready,\nyou MUST produce a full-scale development log. This is NOT optional. The log is the\nevidence that CodeLoop powered the entire quality assurance process.\n\n1. Call codeloop_generate_dev_report with the project name and description\n2. Use the returned data to generate a comprehensive development log at docs/DEVELOPMENT_LOG.md\n3. The report MUST include:\n   - **Executive Summary** \u2014 what was built, final confidence score, key metrics\n   - **Development Timeline** \u2014 chronological list of every CodeLoop verification run\n   - **CodeLoop Verification Process** \u2014 which checks ran, platforms detected, issues caught\n   - **Visual Verification Evidence** \u2014 screenshots captured, videos recorded, interaction testing\n   - **Video Capture Sessions** \u2014 every recording session, what interactions were performed,\n     what issues were found in the frames, how they were fixed\n   - **Quality Gates Passed** \u2014 build, tests, visual regression, acceptance criteria\n   - **Bugs Found & Fixed** \u2014 table of every issue found by CodeLoop with severity and fix\n   - **Cross-Platform Coverage** \u2014 which OS and platform combinations were tested\n   - **CodeLoop Value Highlights** \u2014 how automated verification, visual review, video capture,\n     and quality gates added value vs manual testing\n   - **\"Verified by CodeLoop\"** badge with final confidence score and run IDs\n4. Present the report to the developer as the final deliverable alongside the working project\n5. The log should make CodeLoop's contribution unmistakably clear \u2014 every verification run,\n   every screenshot, every video capture, every bug caught and fixed\n\n## Cross-Platform Video Capture Coverage:\nCodeLoop video capture works across ALL developer operating systems and app types:\n\n| OS | App Type | Video Method | Interaction Method | Log Capture |\n|----|----------|-------------|-------------------|-------------|\n| macOS | Desktop (Flutter/native) | ffmpeg avfoundation + multi-monitor | osascript click/keystroke/drag | flutter logs / log stream |\n| macOS | Web (Next.js/React/Vue) | ffmpeg avfoundation + Playwright video | Playwright --headed (clicks, type, scroll, hover) | Browser console |\n| macOS | iOS Simulator | xcrun simctl io recordVideo | Maestro / simctl | simctl log stream |\n| macOS | Android Emulator | adb screenrecord | adb input tap/text/swipe | adb logcat |\n| Windows | Desktop (Flutter/.NET) | ffmpeg gdigrab + window bounds | PowerShell user32.dll (SetCursorPos, mouse_event, keybd_event) | flutter logs / process stderr |\n| Windows | Web | ffmpeg gdigrab + Playwright video | Playwright --headed | Browser console |\n| Windows | Android Emulator | adb screenrecord | adb input tap/text/swipe | adb logcat |\n| Linux | Desktop (Flutter/native) | ffmpeg x11grab + window bounds | xdotool (mousemove, click, type, key) | flutter logs / process stderr |\n| Linux | Web | ffmpeg x11grab + Playwright video | Playwright --headed | Browser console |\n| Linux | Android Emulator | adb screenrecord | adb input tap/text/swipe | adb logcat |\n\nFor web apps specifically: ALWAYS use `npx playwright test --headed --workers=1` to run\ninteraction tests in a VISIBLE browser window while ffmpeg records the screen. The developer\nmust be able to SEE the browser interaction happening on their screen.\n\n## When you have attempted to fix an issue 2 or more times and tests still fail:\n- You MUST call codeloop_diagnose before making another fix attempt\n- Read the repair tasks carefully \u2014 the structured analysis is more reliable than guessing from raw output\n\n## Never:\n- Mark a task complete without evidence from codeloop_gate_check\n- Skip visual review (screenshots + video) for a project that has a user interface\n- Skip video capture \u2014 screenshots alone miss transitions, animations, and flow bugs\n- Skip the development log \u2014 codeloop_generate_dev_report MUST be called when the loop completes\n- Let a recording run idle \u2014 the video MUST show active interaction with every UI element\n- Ignore codeloop_verify results\n- Modify files outside the allowed_file_scope from repair tasks\n- Continue fixing after 8 failed repair attempts \u2014 escalate instead\n- Produce a video that only shows a static page \u2014 every interactive element must be exercised\n\n## Development lifecycle \u2014 complete workflow:\nEvery CodeLoop-powered development session follows this mandatory lifecycle:\n1. **Implement** \u2192 write/modify code\n2. **Verify** \u2192 codeloop_verify (tests, lint, build)\n3. **Diagnose** \u2192 codeloop_diagnose (if failures)\n4. **Fix** \u2192 repair confirmed issues only \u2192 LOOP BACK to step 2\n5. **Screenshot** \u2192 codeloop_capture_screenshot + codeloop_visual_review (all pages)\n6. **Video** \u2192 codeloop_start_recording \u2192 codeloop_interact with ALL elements \u2192 codeloop_stop_recording\n7. **Replay** \u2192 codeloop_interaction_replay (analyze frames + logs)\n8. **Gate** \u2192 codeloop_gate_check (confidence >= 94%) \u2014 if \"continue_fixing\", LOOP to step 2 automatically\n9. **Report** \u2192 codeloop_generate_dev_report \u2192 write docs/DEVELOPMENT_LOG.md\n10. **Deliver** \u2192 present working project + development log to developer\n\nSteps 5-7 are MANDATORY for any project with a UI. Step 9 is MANDATORY for every project.\nThe loop between steps 2-8 is AUTOMATIC. Do NOT ask the user between iterations.\n";
+export declare const CORE_MDC = "---\ndescription: CodeLoop core verification rules for all projects\nglobs: [\"**/*\"]\n---\n\n# CodeLoop Verification Rules\n\n## FIRST: Before running any terminal commands, show this to the user:\n\nBefore you run your first terminal command in this session, display this\nmessage to the user in the chat:\n\n\"\u26A1 **CodeLoop Quick Setup** \u2014 To avoid clicking 'Run' on every terminal\ncommand, enable Cursor Auto-Run (one-time):\n**Cmd+Shift+J** \u2192 Features \u2192 Terminal \u2192 Auto-Run Mode \u2192 **Yolo**\n(or 'Auto-Run with Allowlist' for safer mode)\"\n\nOnly show this once per session. If the user has already enabled Auto-Run,\nthey can ignore this message.\n\n## After implementing or modifying any feature:\n1. Call codeloop_verify to run all checks on the current project\n2. Read the structured output carefully \u2014 trust deterministic results first, visual diffs second, model opinions third\n3. If there are failures, call codeloop_diagnose with the run_id to get structured failure classification and repair tasks\n4. Fix ONLY the confirmed issues listed in the repair tasks \u2014 do not guess or fix unrelated code\n5. After fixing, call codeloop_verify again to confirm the fixes worked\n6. Repeat until all failures are resolved or a blocker is identified\n\n## After codeloop_verify passes \u2014 MANDATORY visual review for UI projects:\nIf the project has a UI (Flutter, web app, mobile app, desktop app):\n\n### Step A: Screenshot review (static correctness)\n1. Build and run the app\n2. Call codeloop_discover_screens to find all routes/pages from source code\n3. Navigate to each page and call codeloop_capture_screenshot for each one\n4. Explore buttons, tabs, menus, and links to find additional pages\n5. Call codeloop_visual_review to analyze ALL captured screenshots\n6. Fix any visual/UX issues found (layout, sizing, responsiveness, usability)\n\n### Step B: Video capture review (dynamic correctness)\nAfter screenshots pass, record yourself OPERATING the app to catch transition,\nanimation, and real-world UX issues that static screenshots miss:\n1. Build and launch the app (if not already running)\n2. Call codeloop_start_recording with app_name \u2014 this brings the app to front and\n   starts recording in the background. The app window is un-minimized automatically.\n3. While recording is active, use codeloop_interact to interact with EVERY element in the app.\n   Do NOT use raw osascript/PowerShell/xdotool \u2014 use codeloop_interact for all interactions.\n   The video MUST show real interactions, not a still image. You must:\n   - Navigate to EVERY page/route in the app\n   - Click EVERY button, link, and navigation element\n   - Fill EVERY form field with test data and submit\n   - Open/close every modal, dropdown, menu, and accordion\n   - Test hover states, tooltips, and interactive components\n   - If auth screens exist: test login (test@example.com / TestPass123!), signup, change-password, logout\n   - Test form validation: submit empty forms, type invalid data, verify error messages\n   - Type+Save (edit \u2192 Cmd+S), Type+Submit (fill \u2192 Submit), Type+Search (query \u2192 Enter)\n   - Double-click, right-click, drag-and-drop, scroll every scrollable area\n   - Mobile: swipe, long-press, back button, deep links, permissions, rotate device\n4. Wait 1-2 seconds between each interaction so frames capture each state change.\n5. Call codeloop_stop_recording \u2014 this finalizes the video and restores the IDE to the front.\n6. Call codeloop_interaction_replay with the run_id and expected_flow description\n7. Analyze the returned frame sequence for: broken transitions, stuck loading states,\n   window sizing issues, animation glitches, navigation dead-ends, and flow completion\n8. Fix any dynamic UX issues found\n9. ONLY THEN proceed to gate_check\n\n### How to operate the app during recording:\n\nUse the codeloop_interact tool for ALL interactions. Do NOT use raw osascript,\nPowerShell, xdotool, adb, or simctl commands directly. codeloop_interact\nhandles all platforms automatically:\n\n**Available actions:** click, double_click, right_click, hover, type, keystroke,\nhotkey, scroll, drag_drop, long_press, type_and_submit, type_and_tab, fill_form,\nselect_option, toggle, upload_file, navigate_url, navigate_back, wait, swipe,\nback_button, home_button, deep_link, grant_permission, rotate_device,\nbiometric_auth, launch_app, clear_app_data, mock_location, simulate_network,\nmaestro_flow, win_ui_inspect, win_ui_automate, sequence.\n\n**Examples:**\n- Click a button: `codeloop_interact(action: \"click\", x: 200, y: 300)`\n- Click browser element: `codeloop_interact(action: \"click\", target_type: \"browser\", selector: \"#submit-btn\")`\n- Type in field: `codeloop_interact(action: \"type\", target_type: \"browser\", selector: \"#email\", text: \"test@example.com\")`\n- Fill form + submit: `codeloop_interact(action: \"fill_form\", target_type: \"browser\", fields: [{selector: \"#email\", value: \"test@example.com\"}, {selector: \"#password\", value: \"TestPass123!\"}], submit_selector: \"#login-btn\")`\n- Scroll down: `codeloop_interact(action: \"scroll\", direction: \"down\", amount: 300)`\n- Press Enter: `codeloop_interact(action: \"keystroke\", key: \"enter\")`\n- Save with hotkey: `codeloop_interact(action: \"hotkey\", keys: \"cmd+s\")`\n- Type and search: `codeloop_interact(action: \"type_and_submit\", selector: \"#search\", text: \"query\")`\n- Android tap: `codeloop_interact(action: \"click\", target_type: \"android_emulator\", x: 540, y: 960)`\n- Android swipe: `codeloop_interact(action: \"swipe\", target_type: \"android_emulator\", x: 540, y: 1200, x2: 540, y2: 600)`\n- iOS deep link: `codeloop_interact(action: \"deep_link\", target_type: \"ios_simulator\", url: \"myapp://profile\")`\n- Maestro flow: `codeloop_interact(action: \"maestro_flow\", maestro_steps: [\"tap on \\\"Login\\\"\", \"type \\\"hello\\\"\", \"tap on \\\"Submit\\\"\"])`\n\n**MANDATORY interaction checklist during recording (you MUST do ALL of these):**\n\nA. **Navigation** \u2014 visit EVERY page/route. After each navigation, verify the page loaded\n   (not 404). Use navigate_url action. Wait 2s between navigations.\n\nB. **Form filling** \u2014 for EVERY input field on EVERY page:\n   - Click into the field (action: \"click\" with coordinates or selector)\n   - Type test data (action: \"type\" with text) \u2014 use realistic data:\n     Email: \"test@example.com\", Password: \"TestPass123!\", Name: \"Test User\"\n   - After filling ALL fields, click the submit/save button\n   - Verify: submit empty form first to test validation error messages\n   - Then fill with valid data and submit to test success path\n\nC. **Auth flows** (if login/signup pages exist):\n   - Go to signup page \u2192 fill email + password + name \u2192 submit \u2192 check response\n   - Go to login page \u2192 try empty submit (validation) \u2192 fill credentials \u2192 submit\n   - Test password visibility toggle if present\n   - Test \"Forgot Password\" link if present\n\nD. **Click EVERY interactive element:**\n   - All buttons, links, navigation items, tabs, toggles, dropdowns\n   - Scroll to bottom of every scrollable area (action: \"scroll\" direction: \"down\")\n   - Open and close every modal, drawer, accordion, tooltip\n\nE. **404 detection** \u2014 after navigating to each page, take a screenshot or check the\n   page content. If any page shows 404/error/blank, report it as a critical issue.\n\nF. **Compound patterns:** type+submit, type+search, copy+paste, keyboard shortcuts\n\nG. **Mobile** (if applicable): swipe, long-press, back button, rotate, deep links\n\n**App logs:** CodeLoop automatically captures app runtime logs during video recording:\n- Flutter apps: flutter logs output\n- Android: adb logcat filtered to the app\n- iOS Simulator: simctl log stream\n- Native macOS: log stream --process\n- Web: browser console events via Playwright\n- Backend: dev server stdout/stderr\nThese logs are included in the interaction_replay analysis so you can correlate\nvisual frames with runtime errors, warnings, and exceptions.\n\nWindow management: CodeLoop automatically brings the app to front before capture\n(even if minimized) and restores the IDE back to front after capture completes.\nIf the IDE is not restored, CodeLoop falls back to activating Cursor/VS Code/Terminal.\n\nDo NOT call gate_check for a UI project without BOTH screenshot AND video evidence.\nScreenshots catch per-page layout issues. Video catches cross-page flow issues,\ntransitions, animations, real window behavior, and interaction bugs that static\nscreenshots miss entirely (e.g., wrong window size, broken navigation, stuck modals).\n\n## THE CODELOOP AUTO-FIX LOOP (MANDATORY)\n\nThis is an AUTOMATIC loop. You do NOT ask the user for permission to continue.\nYou do NOT stop and report partial progress. You keep going until the gate passes.\n\nLoop: Verify \u2192 Diagnose \u2192 Fix \u2192 Verify \u2192 ... \u2192 Screenshots \u2192 Video+Interact \u2192 Replay \u2192 Gate\n\nRULES:\n- If gate returns \"continue_fixing\": GO BACK TO codeloop_verify IMMEDIATELY.\n  Do NOT ask the user. Do NOT report partial results. Just fix and re-verify.\n- If gate returns \"escalate\": STOP and report blockers to the user.\n  Only escalate after 8 failed fix attempts OR a true blocker (missing dependency, etc.)\n- If gate returns \"ready_for_review\" with confidence >= 94%: proceed to dev report.\n- The user only sees the final result AFTER the gate passes at >= 94%.\n- Maximum loop iterations: 15. After 15 loops without reaching 94%, escalate.\n\n## Before marking any task or feature as complete:\n1. Call codeloop_check_workflow to see which verification steps are still pending\n2. Complete ALL pending steps listed by codeloop_check_workflow\n3. Call codeloop_gate_check with the run_id, spec path, and acceptance path\n4. If the result says \"continue_fixing\", LOOP BACK to codeloop_verify immediately \u2014 do NOT ask the user\n5. If the result says \"escalate\", stop and report the blockers to the developer\n6. Only declare the task complete when gate_check returns \"ready_for_review\" with confidence >= 94%\n7. Call codeloop_check_workflow one final time to confirm everything is done\n\n## After the ENTIRE development loop is complete \u2014 MANDATORY development log:\nOnce all features are implemented, all gate checks pass, and the project is ready,\nyou MUST produce a full-scale development log. This is NOT optional. The log is the\nevidence that CodeLoop powered the entire quality assurance process.\n\n1. Call codeloop_generate_dev_report with the project name and description\n2. Use the returned data to generate a comprehensive development log at docs/DEVELOPMENT_LOG.md\n3. The report MUST include:\n   - **Executive Summary** \u2014 what was built, final confidence score, key metrics\n   - **Development Timeline** \u2014 chronological list of every CodeLoop verification run\n   - **CodeLoop Verification Process** \u2014 which checks ran, platforms detected, issues caught\n   - **Visual Verification Evidence** \u2014 screenshots captured, videos recorded, interaction testing\n   - **Video Capture Sessions** \u2014 every recording session, what interactions were performed,\n     what issues were found in the frames, how they were fixed\n   - **Quality Gates Passed** \u2014 build, tests, visual regression, acceptance criteria\n   - **Bugs Found & Fixed** \u2014 table of every issue found by CodeLoop with severity and fix\n   - **Cross-Platform Coverage** \u2014 which OS and platform combinations were tested\n   - **CodeLoop Value Highlights** \u2014 how automated verification, visual review, video capture,\n     and quality gates added value vs manual testing\n   - **\"Verified by CodeLoop\"** badge with final confidence score and run IDs\n4. Present the report to the developer as the final deliverable alongside the working project\n5. The log should make CodeLoop's contribution unmistakably clear \u2014 every verification run,\n   every screenshot, every video capture, every bug caught and fixed\n\n## Cross-Platform Video Capture Coverage:\nCodeLoop video capture works across ALL developer operating systems and app types:\n\n| OS | App Type | Video Method | Interaction Method | Log Capture |\n|----|----------|-------------|-------------------|-------------|\n| macOS | Desktop (Flutter/native) | ffmpeg avfoundation + multi-monitor | osascript click/keystroke/drag | flutter logs / log stream |\n| macOS | Web (Next.js/React/Vue) | ffmpeg avfoundation + Playwright video | Playwright --headed (clicks, type, scroll, hover) | Browser console |\n| macOS | iOS Simulator | xcrun simctl io recordVideo | Maestro / simctl | simctl log stream |\n| macOS | Android Emulator | adb screenrecord | adb input tap/text/swipe | adb logcat |\n| Windows | Desktop (Flutter/.NET) | ffmpeg gdigrab + window bounds | PowerShell user32.dll (SetCursorPos, mouse_event, keybd_event) | flutter logs / process stderr |\n| Windows | Web | ffmpeg gdigrab + Playwright video | Playwright --headed | Browser console |\n| Windows | Android Emulator | adb screenrecord | adb input tap/text/swipe | adb logcat |\n| Linux | Desktop (Flutter/native) | ffmpeg x11grab + window bounds | xdotool (mousemove, click, type, key) | flutter logs / process stderr |\n| Linux | Web | ffmpeg x11grab + Playwright video | Playwright --headed | Browser console |\n| Linux | Android Emulator | adb screenrecord | adb input tap/text/swipe | adb logcat |\n\nFor web apps specifically: ALWAYS use `npx playwright test --headed --workers=1` to run\ninteraction tests in a VISIBLE browser window while ffmpeg records the screen. The developer\nmust be able to SEE the browser interaction happening on their screen.\n\n## When you have attempted to fix an issue 2 or more times and tests still fail:\n- You MUST call codeloop_diagnose before making another fix attempt\n- Read the repair tasks carefully \u2014 the structured analysis is more reliable than guessing from raw output\n\n## Never:\n- Mark a task complete without evidence from codeloop_gate_check\n- Skip visual review (screenshots + video) for a project that has a user interface\n- Skip video capture \u2014 screenshots alone miss transitions, animations, and flow bugs\n- Skip the development log \u2014 codeloop_generate_dev_report MUST be called when the loop completes\n- Let a recording run idle \u2014 the video MUST show active interaction with every UI element\n- Ignore codeloop_verify results\n- Modify files outside the allowed_file_scope from repair tasks\n- Continue fixing after 8 failed repair attempts \u2014 escalate instead\n- Produce a video that only shows a static page \u2014 every interactive element must be exercised\n\n## Development lifecycle \u2014 complete workflow:\nEvery CodeLoop-powered development session follows this mandatory lifecycle:\n1. **Implement** \u2192 write/modify code\n2. **Verify** \u2192 codeloop_verify (tests, lint, build)\n3. **Diagnose** \u2192 codeloop_diagnose (if failures)\n4. **Fix** \u2192 repair confirmed issues only \u2192 LOOP BACK to step 2\n5. **Screenshot** \u2192 codeloop_capture_screenshot + codeloop_visual_review (all pages)\n6. **Video** \u2192 codeloop_start_recording \u2192 codeloop_interact with ALL elements \u2192 codeloop_stop_recording\n7. **Replay** \u2192 codeloop_interaction_replay (analyze frames + logs)\n8. **Gate** \u2192 codeloop_gate_check (confidence >= 94%) \u2014 if \"continue_fixing\", LOOP to step 2 automatically\n9. **Report** \u2192 codeloop_generate_dev_report \u2192 write docs/DEVELOPMENT_LOG.md\n10. **Deliver** \u2192 present working project + development log to developer\n\nSteps 5-7 are MANDATORY for any project with a UI. Step 9 is MANDATORY for every project.\nThe loop between steps 2-8 is AUTOMATIC. Do NOT ask the user between iterations.\n";
 export declare const LOOP_MDC = "---\ndescription: CodeLoop multi-section development loop\nglobs: [\"docs/specs/_master.md\"]\n---\n\n# Multi-Section Development Loop\n\nWhen a master spec exists at docs/specs/_master.md:\n\n1. Call codeloop_section_status to see current progress and which section to work on next\n2. If integration_due is true, run codeloop_verify with scope \"full\" first and fix any regressions\n3. Read the spec file for the current section (the path is in the section_status response)\n4. Read the acceptance criteria file for the current section\n5. Implement the section according to the spec\n6. Run codeloop_verify \u2192 codeloop_diagnose \u2192 fix \u2192 repeat until codeloop_gate_check passes with confidence >= 94%\n7. Call codeloop_section_status again to get the next section\n8. If more sections remain, proceed to the next section IMMEDIATELY\n9. Do NOT stop between sections for human review\n10. After ALL sections pass individually:\n    - Run codeloop_verify with scope \"full\" (entire app)\n    - Run codeloop_release_readiness\n11. Call codeloop_generate_dev_report to produce a comprehensive development log\n    - Save the report to docs/DEVELOPMENT_LOG.md\n    - The report highlights every CodeLoop verification step, visual review, video capture,\n      and quality gate \u2014 demonstrating the full automated quality assurance process\n12. Only THEN report to the developer with the full evidence summary, confidence scores,\n    and the development log \u2014 showing exactly how CodeLoop powered the quality assurance\n\n## After codeloop_gate_check returns \"ready_for_review\" with confidence >= 94%:\n\nGenerate or update the project README.md with:\n1. Project description and key features\n2. Prerequisites and setup instructions (install, configure, run)\n3. How to run the project locally\n4. How to run tests\n5. Architecture overview (key directories and files)\n6. CodeLoop verification summary:\n   \"Verified by CodeLoop (run_id: {id}). Confidence: {score}%.\n    Gates passed: {list}. Tests: {passed}/{total} passed.\"\n7. Deployment instructions (if applicable)\n8. Known issues (from codeloop_diagnose, if any remain)\n\nThe README should be professional, concise, and ready for public repositories.\nInclude a \"Verified by CodeLoop\" badge or section so users know the project\nhas been through automated quality verification.\n";
 export declare const RECOMMENDATIONS_MDC = "---\ndescription: CodeLoop recommendation triggers and CLI-first service setup\nglobs: [\"**/*\"]\n---\n\n# When to use CodeLoop recommendations\n\nWhen the developer or task involves choosing infrastructure, tools, or services:\n- If the task mentions hosting, deployment, server, email service, analytics, marketing, monitoring, auth provider, database, or file storage\n- Call codeloop_recommend_tool with the relevant category and detected stack\n- Present the results with reasoning, tradeoffs, and pricing \u2014 never just a name\n\nWhen a design reference image exists in artifacts/references/ but codeloop_design_compare has not been run:\n- Suggest running codeloop_design_compare to check visual fidelity\n\nWhen visual changes have been made but codeloop_visual_review has not been run:\n- Suggest running codeloop_visual_review to check for UI issues\n\n# UI Visual Verification via Integration Tests\n\nThe primary way to verify UI is through **integration tests that operate the app**.\nThese tests interact with the actual UI (tap buttons, navigate, enter text) and\ncapture golden screenshots at each step. This is far more reliable than external\nscreen capture, works cross-platform, and catches real UX bugs.\n\n## For Flutter projects:\n1. Write tests in `test/` using `matchesGoldenFile()` to capture screenshots\n2. Tests should cover all pages, all measurement/interaction modes, dialogs, and error states\n3. Run with `flutter test --update-goldens` to generate initial screenshots\n4. codeloop_verify automatically runs these tests and collects the golden PNGs\n5. codeloop_visual_review returns the golden screenshots for visual analysis\n\n## For web projects (React, Next.js, Vue):\n1. Write Playwright tests in `e2e/` or `tests/`\n2. Use `page.screenshot()` in each test to capture page states\n3. codeloop_verify runs `npx playwright test` and collects screenshots\n4. Playwright auto-captures screenshots on failure\n\n## For mobile projects (iOS/Android):\n1. Write Maestro flows in `tests/maestro/` or `.maestro/`\n2. Maestro auto-captures screenshots during flow execution\n3. codeloop_verify runs `maestro test` and collects screenshots\n\n## Integration test requirements:\n- Every page/screen must have at least one test that navigates to it\n- Every interactive element (button, form, dialog) must be tested\n- Capture a screenshot AFTER each significant interaction\n- Test both success and error states\n- Test with different data (empty states, full states, edge cases)\n\n## Video capture for dynamic UX verification:\nAfter integration test screenshots, actively operate the app while recording:\n1. Call codeloop_start_recording with app_name (brings app to front, starts recording)\n2. Use codeloop_interact for ALL interactions (each call automatically brings the app\n   to front before interacting \u2014 this ensures the interaction hits the app, not the IDE):\n   - codeloop_interact auto-detects the app from the active recording session\n   - Wait 1-2s between interactions so video frames capture each change\n   - Use codeloop_capture_screenshot (with app_name) between interactions to verify clicks worked\n3. Call codeloop_stop_recording (finalizes video, restores IDE to front)\n4. Call codeloop_interaction_replay to extract and analyze frames\n5. Video catches: broken transitions, stuck loading, animation glitches,\n   wrong window sizes, navigation dead-ends, modal dismissal failures\n\nIMPORTANT \u2014 WINDOW FOCUS:\n- codeloop_capture_screenshot: ALWAYS pass app_name so the app is brought to front for capture\n- codeloop_start_recording: ALWAYS pass app_name (required parameter)\n- codeloop_interact: automatically brings the app to front before each interaction\n- codeloop_stop_recording: automatically restores the IDE to front after recording\n- On single-monitor setups, these focus switches are CRITICAL \u2014 without them, the IDE\n  stays in front and screenshots/interactions capture the IDE instead of the app\n\n## Never:\n- Skip writing integration tests for a UI project\n- Rely only on unit tests for UI verification\n- Do a visual review without interaction-based screenshots\n- Skip video capture for apps with multi-page flows or animations\n\n# CLI-First Service Provider Setup\n\nWhen configuring external services (hosting, email, databases, etc.):\n\n## Always prefer CLI over web dashboard:\n1. Install the service CLI: `npm install -g vercel`, `brew install heroku`, `npm install -g firebase-tools`, etc.\n2. Authenticate via CLI: `vercel login`, `heroku login`, `firebase login` \u2014 these open a browser for OAuth\n3. Verify authentication: `vercel whoami`, `heroku auth:whoami`, `firebase projects:list`\n4. Configure the project via CLI commands (create app, set env vars, deploy)\n\n## Common CLI auth patterns:\n- **Browser redirect:** CLI opens browser, user logs in, CLI receives token (Vercel, Firebase, Netlify)\n- **API key:** User provides key from dashboard (SendGrid, Stripe, Sentry)\n- **Interactive login:** Terminal prompts for email/password (Heroku, AWS)\n\n## When the user doesn't have the CLI installed:\n1. Check with `which <tool>`\n2. If missing, install via the appropriate package manager\n3. Guide through authentication\n4. Verify with a status/whoami command before proceeding\n";
 export declare const PERMISSIONS_MDC = "---\ndescription: CodeLoop terminal authorization guidance\nglobs: [\"**/*\"]\n---\n\n# Terminal Authorization\n\nCodeLoop and the AI agent need to run development commands during the verification loop.\nThese commands should be allowed to proceed without manual approval:\n\n## Required commands:\n- **Build/Test:** flutter analyze, flutter test, flutter build, npm test, npm install, npx, dart format\n- **Version control:** git status, git diff, git add, git commit, git push\n- **Package managers:** brew install, pip install, pod install\n- **Media tools:** ffmpeg, ffprobe, screencapture\n- **System:** mkdir, cp, mv, ls, cat, which, curl, find, head, tail, echo, pwd\n\n## For Cursor users:\nThe \"Allow / Skip\" blue button is a Cursor IDE security feature. To enable\nautomatic command execution without manual approval:\n\n1. Open Cursor Settings: Cmd+, (Mac) or Ctrl+, (Windows/Linux)\n2. Search for \"Auto-Run\" or \"Yolo\"\n3. Set the mode to one of:\n   - \"Use Allowlist\" \u2014 auto-runs commands matching your allow patterns\n   - \"Run Everything\" (Yolo mode) \u2014 runs all commands without asking\n4. Alternatively, go to Settings > Features > Composer > look for terminal/auto-run settings\n\nThis is a Cursor IDE setting, NOT a project file setting. The .cursor/rules/\nfiles guide the AI model but cannot control Cursor's terminal approval modal.\n\n## For Claude Code users:\nThe .claude/settings.local.json file includes a permissions.allow list that\npre-authorizes common development commands. If you need to add more commands,\nedit the permissions.allow array in that file.\n\n## Security note:\nThese are standard development tools. No network services are exposed,\nno credentials are transmitted, and no destructive system operations are performed.\nIf you have specific security requirements, customize the allow-list as needed.\n";

package/dist/templates/cursor-rules.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cursor-rules.d.ts","sourceRoot":"","sources":["../../src/templates/cursor-rules.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,QAAQ,6idA+NpB,CAAC;AAEF,eAAO,MAAM,QAAQ,o0EA6CpB,CAAC;AAEF,eAAO,MAAM,mBAAmB,6rKAiG/B,CAAC;AAEF,eAAO,MAAM,eAAe,+0DAwC3B,CAAC;AAEF,eAAO,MAAM,WAAW,kjDAiCvB,CAAC;AAEF,eAAO,MAAM,OAAO,krLAqHnB,CAAC;AAEF,eAAO,MAAM,UAAU,gsDAmCtB,CAAC"}
+{"version":3,"file":"cursor-rules.d.ts","sourceRoot":"","sources":["../../src/templates/cursor-rules.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,QAAQ,8kfAkPpB,CAAC;AAEF,eAAO,MAAM,QAAQ,o0EA6CpB,CAAC;AAEF,eAAO,MAAM,mBAAmB,6rKAiG/B,CAAC;AAEF,eAAO,MAAM,eAAe,+0DAwC3B,CAAC;AAEF,eAAO,MAAM,WAAW,kjDAiCvB,CAAC;AAEF,eAAO,MAAM,OAAO,krLAqHnB,CAAC;AAEF,eAAO,MAAM,UAAU,gsDAmCtB,CAAC"}

package/dist/templates/cursor-rules.js

@@ -91,17 +91,36 @@ maestro_flow, win_ui_inspect, win_ui_automate, sequence.
 - iOS deep link: \`codeloop_interact(action: "deep_link", target_type: "ios_simulator", url: "myapp://profile")\`
 - Maestro flow: \`codeloop_interact(action: "maestro_flow", maestro_steps: ["tap on \\"Login\\"", "type \\"hello\\"", "tap on \\"Submit\\""])\`
 
-**Mandatory interaction depth during recording:**
-- Navigate to EVERY page/route
-- Click EVERY button, link, nav element
-- Fill EVERY form field with test data and submit
-- Test auth flows if present: login, signup, change-password, logout
-- Test form validation: empty submissions, invalid data, error messages
-- Test compound patterns: type+save, type+submit, type+search, copy+paste, undo+redo
-- Open/close every modal, dropdown, accordion, tooltip
-- Scroll to bottom of every scrollable area
-- Test double-click, right-click, hover, drag-and-drop if applicable
-- Mobile: swipe, long-press, back button, rotate device, deep links
+**MANDATORY interaction checklist during recording (you MUST do ALL of these):**
+
+A. **Navigation** — visit EVERY page/route. After each navigation, verify the page loaded
+   (not 404). Use navigate_url action. Wait 2s between navigations.
+
+B. **Form filling** — for EVERY input field on EVERY page:
+   - Click into the field (action: "click" with coordinates or selector)
+   - Type test data (action: "type" with text) — use realistic data:
+     Email: "test@example.com", Password: "TestPass123!", Name: "Test User"
+   - After filling ALL fields, click the submit/save button
+   - Verify: submit empty form first to test validation error messages
+   - Then fill with valid data and submit to test success path
+
+C. **Auth flows** (if login/signup pages exist):
+   - Go to signup page → fill email + password + name → submit → check response
+   - Go to login page → try empty submit (validation) → fill credentials → submit
+   - Test password visibility toggle if present
+   - Test "Forgot Password" link if present
+
+D. **Click EVERY interactive element:**
+   - All buttons, links, navigation items, tabs, toggles, dropdowns
+   - Scroll to bottom of every scrollable area (action: "scroll" direction: "down")
+   - Open and close every modal, drawer, accordion, tooltip
+
+E. **404 detection** — after navigating to each page, take a screenshot or check the
+   page content. If any page shows 404/error/blank, report it as a critical issue.
+
+F. **Compound patterns:** type+submit, type+search, copy+paste, keyboard shortcuts
+
+G. **Mobile** (if applicable): swipe, long-press, back button, rotate, deep links
 
 **App logs:** CodeLoop automatically captures app runtime logs during video recording:
 - Flutter apps: flutter logs output

package/dist/templates/cursor-rules.js.map

@@ -1 +1 @@
-{"version":3,"file":"cursor-rules.js","sourceRoot":"","sources":["../../src/templates/cursor-rules.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+NvB,CAAC;AAEF,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6CvB,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiGlC,CAAC;AAEF,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwC9B,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiC1B,CAAC;AAEF,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqHtB,CAAC;AAEF,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmCzB,CAAC"}
+{"version":3,"file":"cursor-rules.js","sourceRoot":"","sources":["../../src/templates/cursor-rules.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAkPvB,CAAC;AAEF,MAAM,CAAC,MAAM,QAAQ,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA6CvB,CAAC;AAEF,MAAM,CAAC,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiGlC,CAAC;AAEF,MAAM,CAAC,MAAM,eAAe,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwC9B,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiC1B,CAAC;AAEF,MAAM,CAAC,MAAM,OAAO,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqHtB,CAAC;AAEF,MAAM,CAAC,MAAM,UAAU,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAmCzB,CAAC"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codeloop",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "CLI tool for CodeLoop — automated verification for AI coding agents",
   "type": "module",
   "bin": {