@haystackeditor/cli 0.6.0 → 0.7.1

package/dist/utils/detect.js

@@ -27,7 +27,12 @@ export async function detectProject(rootDir = process.cwd()) {
     }
     // Detect framework
     result.framework = await detectFramework(rootDir);
-    // Set suggestions based on framework
+    // Extract custom port from config if framework supports it
+    const customPort = await extractPortFromConfig(rootDir, result.framework);
+    if (customPort) {
+        result.suggestedPort = customPort;
+    }
+    // Set suggestions based on framework (won't override customPort if set)
     setSuggestions(result);
     // Detect auth bypass from .env.example
     result.suggestedAuthBypass = await detectAuthBypass(rootDir);
@@ -188,12 +193,14 @@ async function detectService(rootDir, servicePath) {
     else if (await hasFile(fullPath, 'vite.config.ts') || await hasFile(fullPath, 'vite.config.js')) {
         framework = 'vite';
         suggestedCommand = 'pnpm dev';
-        suggestedPort = 5173;
+        // Try to extract custom port from vite config, fallback to default
+        suggestedPort = await extractPortFromConfig(fullPath, 'vite') ?? 5173;
     }
     else if (await hasFile(fullPath, 'next.config.js') || await hasFile(fullPath, 'next.config.ts')) {
         framework = 'nextjs';
         suggestedCommand = 'pnpm dev';
-        suggestedPort = 3000;
+        // Try to extract custom port from next config, fallback to default
+        suggestedPort = await extractPortFromConfig(fullPath, 'nextjs') ?? 3000;
     }
     else if (scripts.dev) {
         suggestedCommand = 'pnpm dev';
@@ -280,6 +287,7 @@ async function detectAuthBypass(rootDir) {
 }
 /**
  * Set suggestions based on detected framework
+ * Note: This is sync, so custom port extraction happens in detectProject
  */
 function setSuggestions(result) {
     const frameworkDefaults = {
@@ -294,7 +302,8 @@ function setSuggestions(result) {
     };
     const defaults = result.framework ? frameworkDefaults[result.framework] : null;
     result.suggestedDevCommand = defaults?.command || `${result.packageManager} dev`;
-    result.suggestedPort = defaults?.port || 3000;
+    // suggestedPort may already be set from custom config extraction
+    result.suggestedPort = result.suggestedPort || defaults?.port || 3000;
     result.suggestedReadyPattern = defaults?.ready || 'ready|started|listening|Local:';
 }
 /**
@@ -309,6 +318,58 @@ async function hasFile(dir, file) {
         return false;
     }
 }
+/**
+ * Extract custom port from framework config files
+ *
+ * Parses vite.config.ts, next.config.js, etc. to find custom port settings
+ * Returns undefined if no custom port is configured (use framework default)
+ */
+async function extractPortFromConfig(rootDir, framework) {
+    if (!framework)
+        return undefined;
+    // Config files to check based on framework
+    const configFiles = {
+        vite: ['vite.config.ts', 'vite.config.js', 'vite.config.mjs'],
+        nextjs: ['next.config.js', 'next.config.ts', 'next.config.mjs'],
+        nuxt: ['nuxt.config.ts', 'nuxt.config.js'],
+        sveltekit: ['svelte.config.js', 'svelte.config.ts'],
+        astro: ['astro.config.mjs', 'astro.config.ts'],
+    };
+    const files = configFiles[framework];
+    if (!files)
+        return undefined;
+    let configContent = null;
+    for (const file of files) {
+        try {
+            configContent = await fs.readFile(path.join(rootDir, file), 'utf-8');
+            break;
+        }
+        catch {
+            // File not found, try next
+        }
+    }
+    if (!configContent)
+        return undefined;
+    // Patterns to match port configuration
+    // Vite: server: { port: 3000 } or server.port = 3000
+    // Next: env: { PORT: 3000 } or experimental.serverPort
+    const patterns = [
+        /server\s*:\s*\{[^}]*port\s*:\s*(\d+)/s, // server: { port: 3000 }
+        /server\s*\.\s*port\s*[=:]\s*(\d+)/, // server.port = 3000
+        /port\s*:\s*(\d+)/, // port: 3000 (generic)
+        /PORT\s*[=:]\s*['"]?(\d+)['"]?/, // PORT = 3000
+    ];
+    for (const pattern of patterns) {
+        const match = configContent.match(pattern);
+        if (match) {
+            const port = parseInt(match[1], 10);
+            if (port > 0 && port < 65536) {
+                return port;
+            }
+        }
+    }
+    return undefined;
+}
 /**
  * Detect proxy dependencies from vite.config.ts/js
  *

package/dist/utils/skill.js

@@ -50,7 +50,75 @@ Your flows should describe THIS journey, not just "pages load".
 
 ---
 
-## Step 3: Assess Data Needs
+## Step 3: Verify ALL Services Have Flows (CRITICAL)
+
+**Every service in \`.haystack.json\` must have at least one verification flow.** This is the most common mistake - adding services but forgetting to add flows that exercise them.
+
+### Check for Uncovered Services
+
+\`\`\`bash
+# List all services
+grep -A1 '"services"' .haystack.json | grep -E '^\\s+"[^"]+":' | sed 's/.*"\\([^"]*\\)".*/\\1/'
+
+# List all flows
+grep '"name":' .haystack.json
+
+# MANUAL CHECK: Does every service have a flow?
+\`\`\`
+
+### Types of Services
+
+| Service Type | How to Verify |
+|--------------|---------------|
+| **Web frontend** | UI flows (navigate, wait_for, screenshot) |
+| **API/Worker** | UI flows that hit API endpoints |
+| **CLI/Batch** | Backend flows with golden inputs |
+| **Analysis pipeline** | Backend flows with known PR input |
+
+### Backend Verification (CLI tools, analysis pipelines, batch jobs)
+
+**Not everything is a web page.** For CLI tools and batch processes, you need:
+
+1. **Golden input** - A known-good input that produces predictable output
+2. **Run command** - How to execute the service
+3. **Output assertion** - What to check in the output
+
+\`\`\`json
+{
+  "name": "Analysis pipeline - golden PR",
+  "description": "Run analysis on known PR to verify pipeline works",
+  "trigger": "on_change",
+  "watch_patterns": ["analysis/src/**", "analysis/package.json"],
+  "service": "haystack-analysis",
+  "type": "backend",
+  "steps": [
+    {
+      "action": "run",
+      "command": "pnpm start",
+      "env": { "PR_IDENTIFIER": "owner/repo#123" },
+      "timeout": 120
+    },
+    { "action": "assert_exit_code", "code": 0 },
+    { "action": "assert_output_contains", "pattern": "Analysis complete" }
+  ]
+}
+\`\`\`
+
+### Finding Golden Inputs
+
+For analysis/processing pipelines:
+- Pick a **small, stable PR** that won't change
+- Document what the expected output should be
+- Add it as a comment in the flow description
+
+\`\`\`bash
+# Find a good golden PR (small, merged, stable)
+gh pr list --state merged --limit 10 --json number,title,changedFiles | jq '.[] | select(.changedFiles < 5)'
+\`\`\`
+
+---
+
+## Step 4: Assess Data Needs
 
 \`\`\`bash
 # Find API calls
@@ -85,7 +153,7 @@ grep -r "https://" src/ --include="*.ts" --include="*.tsx" | grep -v node_module
 
 ---
 
-## Step 4: Write Flows
+## Step 5: Write Flows
 
 Flows tell the Planner about your app's routes, UI elements, and user journeys.
 
@@ -157,7 +225,7 @@ For flows that only matter when certain files change:
 
 ---
 
-## Step 5: Configure Fixtures (if needed)
+## Step 6: Configure Fixtures (if needed)
 
 Based on user's answer in Step 3:
 
@@ -189,7 +257,7 @@ fixtures:
 
 ---
 
-## Step 6: Commit
+## Step 7: Commit
 
 \`\`\`bash
 git add .haystack.json fixtures/

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@haystackeditor/cli",
-  "version": "0.6.0",
+  "version": "0.7.1",
   "description": "Set up Haystack verification for your project",
   "type": "module",
   "bin": {