ctx-cc 3.4.2 → 3.4.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ctx-cc",
-  "version": "3.4.2",
+  "version": "3.4.3",
   "description": "CTX 3.3 (Continuous Task eXecution) - AI that learns your preferences. Learning system, predictive planning, self-healing deployments (Sentry/LogRocket), voice control for hands-free development.",
   "keywords": [
     "claude",

package/workflows/ctx-router.md

@@ -74,17 +74,116 @@ Execute /ctx:init inline (don't tell user to run it separately).
 Output:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
- CTX ► ANALYZING CODEBASE
+ CTX ► DEEP STUDY
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 I understood: "{{user_request}}"
 
-Let me analyze this codebase with 4 specialized mappers.
+Before I analyze, let me understand the scope.
+
+───────────────────────────────────────────────────────
+```
+
+**Step 0: Gather context with AskUserQuestion**
+
+Use the AskUserQuestion tool to ask:
+
+```
+AskUserQuestion({
+  questions: [
+    {
+      question: "What type of analysis do you need?",
+      header: "Scope",
+      options: [
+        { label: "Code only", description: "Analyze codebase structure, patterns, and quality" },
+        { label: "Code + Running app", description: "Also browse the running application in browser" },
+        { label: "Full system", description: "Code + App + API testing + Database inspection" }
+      ],
+      multiSelect: false
+    },
+    {
+      question: "Is the application running locally?",
+      header: "Environment",
+      options: [
+        { label: "Yes, running", description: "App is running at localhost or local URL" },
+        { label: "Not yet", description: "I'll start it or you can help me start it" },
+        { label: "Remote/Staging", description: "App is deployed to a remote environment" }
+      ],
+      multiSelect: false
+    }
+  ]
+})
+```
+
+**If user selects "Code + Running app" or "Full system":**
+
+Ask for credentials:
+```
+AskUserQuestion({
+  questions: [
+    {
+      question: "Do you have login credentials for the app?",
+      header: "Access",
+      options: [
+        { label: "Yes, I'll provide them", description: "I have username/password or API keys" },
+        { label: "No auth needed", description: "The app doesn't require login" },
+        { label: "OAuth/SSO only", description: "Login requires external provider" }
+      ],
+      multiSelect: false
+    }
+  ]
+})
+```
+
+**If user will provide credentials:**
+
+Output:
+```
+╔═══════════════════════════════════════════════════════╗
+║  LOGIN CREDENTIALS                                    ║
+╚═══════════════════════════════════════════════════════╝
+
+I'll detect the app URL from your config files.
+Please provide login credentials for browser testing:
+
+• Username/Email: _______________
+• Password: _______________
+
+───────────────────────────────────────────────────────
+→ Paste credentials or type "skip" to analyze code only
+───────────────────────────────────────────────────────
+```
+
+Store credentials in memory for browser testing (never write to files).
+
+**Detect app URL from codebase:**
+
+```bash
+# Check common locations for app URL
+grep -r "localhost\|127.0.0.1" .env* package.json 2>/dev/null | head -5
+grep -r "PORT\|port" .env* package.json 2>/dev/null | head -5
+```
+
+Extract URL like `http://localhost:3000` from config.
+
+**Step 1: Show analysis plan**
+
+Output:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► ANALYZING CODEBASE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Analysis scope: {{selected_scope}}
+Environment: {{selected_environment}}
+Access: {{access_level}}
+
+Starting analysis with 4 specialized mappers...
 
 ───────────────────────────────────────────────────────
 ```
 
-**Step 1: Create structure**
+**Step 2: Create structure**
 
 ```bash
 mkdir -p .ctx/codebase
@@ -150,7 +249,69 @@ cat .ctx/codebase/CONCERNS.md
 
 Write `.ctx/codebase/SUMMARY.md` with key findings from each document.
 
-**Step 7: Show completion banner**
+**Step 7: Browser testing (if scope includes running app)**
+
+If user selected "Code + Running app" or "Full system":
+
+Output:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ CTX ► BROWSER TESTING
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Now testing the running application...
+
+───────────────────────────────────────────────────────
+```
+
+Use Playwright MCP tools to:
+
+1. Navigate to app URL:
+```
+mcp__playwright__browser_navigate({ url: "{{app_url}}" })
+```
+
+2. Take snapshot of initial state:
+```
+mcp__playwright__browser_snapshot({})
+```
+
+3. If credentials provided, log in:
+```
+mcp__playwright__browser_type({ element: "email/username field", ref: "{{ref}}", text: "{{username}}" })
+mcp__playwright__browser_type({ element: "password field", ref: "{{ref}}", text: "{{password}}" })
+mcp__playwright__browser_click({ element: "login button", ref: "{{ref}}" })
+```
+
+4. Take snapshot after login:
+```
+mcp__playwright__browser_snapshot({})
+```
+
+5. Explore key pages based on codebase analysis:
+   - Navigate to pages identified in ARCH.md
+   - Take screenshots of main flows
+   - Check for console errors
+
+6. Write browser findings to `.ctx/codebase/BROWSER.md`:
+   - Pages tested
+   - UI issues found
+   - Console errors
+   - Accessibility observations
+   - Screenshots taken
+
+Output progress:
+```
+◆ Testing application...
+  → Navigating to {{app_url}}
+  → Logging in as {{username}}
+  → Exploring dashboard
+  → Checking user flows
+
+✓ Browser testing complete: BROWSER.md ({{N}} lines)
+```
+
+**Step 8: Show completion banner**
 
 Output:
 ```