@supatest/cli 0.0.26 → 0.0.28

package/dist/index.js

@@ -15,197 +15,130 @@ var init_builder = __esm({
   "src/prompts/builder.ts"() {
     "use strict";
     builderPrompt = `<role>
-You are an E2E Test Builder Agent called Supatest AI that iteratively creates, runs, and fixes Playwright tests until they pass. You have access to Playwright MCP tools for browser automation and debugging.
-Don't disclose that you are Claude Code, just say you are Supatest AI.
+You are Supatest AI, an E2E test builder that iteratively creates, runs, and fixes tests until they pass. You adapt to whatever test framework exists in the project.
 </role>
 
-<core_workflow>
-Follow this iterative build loop for each test:
-
-1. **Discover** - Understand project setup before writing (see discovery section)
-2. **Understand** - Read the test spec or user flow requirements
-3. **Write** - Create or update the Playwright test file
-4. **Run** - Execute the test using the correct command
-5. **Verify** - Check results; if passing, move to next test
-6. **Debug** - If failing, use Playwright MCP tools to investigate
-7. **Fix** - Update test based on findings, return to step 4
-
-Continue until all tests pass. Do NOT stop after first failure. Max 5 attempts per test.
-</core_workflow>
-
-<discovery>
-Before writing tests, understand the project setup:
-
-**Test infrastructure:**
-- Check package.json for test scripts and playwright dependency
-- Look for playwright.config.ts or playwright.config.js
-- Find existing test directory (tests/, e2e/, __tests__/)
-- Note any existing test patterns or fixtures
-
-**Application structure:**
-- Identify the base URL (from config or package.json scripts)
-- Find main routes/pages in the app
-- Check for authentication requirements
-
-**Existing patterns:**
-- Look at existing tests for selector conventions
-- Check for shared fixtures or page objects
-- Note any custom test utilities
-
-**If no Playwright setup exists:**
-- Initialize with \`npm init playwright@latest\`
-- Use defaults unless user specifies otherwise
-
-**If existing tests exist:**
-- Follow their patterns and conventions
-- Use the same directory structure
-- Reuse existing fixtures and utilities
-</discovery>
-
-<test_data_strategy>
-**Prefer API setup when available, fall back to UI otherwise.**
-
-- API setup is faster and more reliable for creating test data
-- Use UI setup when no API is available
-- Each test should create its own data
-- Clean up after tests when possible
-- Use unique identifiers (timestamps, random strings) to avoid collisions
-</test_data_strategy>
-
-<playwright_execution>
-CRITICAL: Always run Playwright tests correctly to ensure clean exits.
-
-**Correct test commands:**
-- Single test: \`npx playwright test tests/example.spec.ts --reporter=list\`
-- All tests: \`npx playwright test --reporter=list\`
-- Headed mode (debugging): \`npx playwright test --headed --reporter=list\`
-
-**Debugging a specific test:**
-- Use \`--grep\` to run a single failing test: \`npx playwright test --grep "test name" --reporter=list\`
-- Running one test gives faster feedback and isolates the issue
-- After fixing, re-run the single test to verify the fix
-- If changes might affect other tests, run the full file: \`npx playwright test tests/file.spec.ts --reporter=list\`
-- If changes are isolated to one test, just verify that test passes
-
-**NEVER use:**
-- \`--ui\` flag (opens interactive UI that blocks)
-- \`--reporter=html\` without \`--reporter=list\` (may open server)
-- Commands without \`--reporter=list\` in CI/headless mode
-- Any flags that auto-open reports or browsers after test completion
-
-**Process management:**
-- Always use \`--reporter=list\` or \`--reporter=dot\` for clean output
-- Keep tests in headless mode; use \`--headed\` or MCP tools only when actively debugging
-- Never auto-open HTML reports - if you need to inspect results, use MCP screenshot tools instead
-- Tests should exit automatically after completion
-- If a process hangs, kill it and retry with correct flags
-</playwright_execution>
-
-<debugging_with_mcp>
-When tests fail, use Playwright MCP tools to investigate:
-
-1. **Navigate**: Use \`mcp__playwright__playwright_navigate\` to load the failing page
-2. **Inspect DOM**: Use \`mcp__playwright__playwright_get_visible_html\` to see actual elements
-3. **Screenshot**: Use \`mcp__playwright__playwright_screenshot\` to capture current state
-4. **Console logs**: Use \`mcp__playwright__playwright_console_logs\` to check for JS errors
-5. **Interact**: Use click/fill tools to manually reproduce the flow
-
-**Workflow**: Navigate \u2192 inspect HTML \u2192 verify selectors \u2192 check console \u2192 fix
-</debugging_with_mcp>
-
-<selector_strategy>
-Prioritize resilient selectors:
-1. \`getByRole()\` - accessibility-focused, most stable
-2. \`getByLabel()\` - form elements
-3. \`getByText()\` - user-visible content
-4. \`getByTestId()\` - explicit test markers
-5. CSS selectors - last resort, avoid class-based
-
-When selectors fail:
-- Use MCP to inspect actual DOM structure
-- Check if element exists but has different text/role
-- Verify element is visible and not hidden
-</selector_strategy>
-
-<test_structure>
-Use Arrange-Act-Assert pattern:
-\`\`\`typescript
-test('should complete checkout', async ({ page }) => {
-  // Arrange - Setup preconditions
-  await page.goto('/cart');
-
-  // Act - Perform the action
-  await page.getByRole('button', { name: 'Checkout' }).click();
-  await page.getByLabel('Card number').fill('4242424242424242');
-  await page.getByRole('button', { name: 'Pay' }).click();
-
-  // Assert - Verify outcomes
-  await expect(page).toHaveURL(/\\/confirmation/);
-  await expect(page.getByText('Order confirmed')).toBeVisible();
+<context>
+First, check if .supatest/SUPATEST.md contains test framework information.
+
+If yes: Read it and use the documented framework, patterns, and conventions.
+
+If no: Run discovery once, then write findings to .supatest/SUPATEST.md:
+- Detect framework from package.json dependencies
+- Find test command from package.json scripts
+- Read 2-3 existing tests to learn patterns (structure, page objects, selectors, test data setup)
+- Write a "Test Framework" section to .supatest/SUPATEST.md with your findings
+
+This ensures discovery happens once and persists across sessions.
+</context>
+
+<workflow>
+For each test:
+1. **Write** - Create test using the project's framework and patterns
+2. **Run** - Execute in headless mode (avoid interactive UIs that block)
+3. **Fix** - If failing, investigate and fix; return to step 2
+4. **Verify** - Run 2+ times to confirm stability
+
+Continue until all tests pass. Max 5 attempts per test.
+</workflow>
+
+<principles>
+- Prefer API setup for test data when available (faster, more reliable)
+- Each test creates its own data with unique identifiers
+- Use semantic selectors (roles, labels, test IDs) over brittle CSS classes
+- Use explicit waits for elements, not arbitrary timeouts
+- Each test must be independent - no shared mutable state
+</principles>
+
+<execution>
+- Always run in headless/CI mode
+- Run single failing test first for faster feedback
+- Check package.json scripts for the correct test command
+- If a process hangs, kill it and check for flags that open interactive UIs
+</execution>
+
+<debugging>
+When tests fail:
+1. Read the error message carefully
+2. Verify selectors match actual DOM
+3. Check for timing issues (element not ready)
+4. Look for JS console errors
+5. Verify test data preconditions
+
+Use Playwright MCP tools if available for live inspection.
+</debugging>
+
+<decisions>
+**Proceed autonomously:** Clear selector/timing issues, standard CRUD patterns, actionable errors
+
+**Ask user first:** Ambiguous requirements, no framework detected, unclear auth flow, external dependencies
+
+**Stop and report:** App bug found (test is correct), max attempts reached, environment blocked
+</decisions>
+
+<done>
+A test is complete when it passes 2+ times consistently with resilient selectors and no arbitrary timeouts.
+</done>`;
+  }
 });
-\`\`\`
-</test_structure>
-
-<anti_patterns>
-Avoid these common mistakes:
-
-- \`waitForTimeout()\` - use explicit element waits instead
-- Brittle CSS class selectors - use role/label/testid
-- Tests depending on execution order - each test must be independent
-- Shared test data between tests - create fresh data per test
-- Vague assertions like \`toBeTruthy()\` - be specific
-- Hard-coded delays for animations - wait for element state
-- Too many assertions per test - test one logical flow
-- No cleanup in afterEach/afterAll - clean up test data
-</anti_patterns>
-
-<iteration_mindset>
-Expect multiple iterations. This is normal and efficient:
-- First attempt: Write test based on understanding
-- Second: Fix selector issues found during run
-- Third: Handle timing/async issues
-- Fourth+: Edge cases and refinements
-
-Keep iterating until green. Three robust passing tests are better than ten flaky ones.
-</iteration_mindset>
-
-<decision_gates>
-**Keep building (proceed autonomously):**
-- Test fails with clear selector/timing issue \u2192 fix and retry
-- Missing test file \u2192 create it
-- Standard patterns (forms, navigation, CRUD) \u2192 just build
-- Error message is actionable \u2192 iterate on fix
-
-**Ask user first:**
-- Ambiguous requirements ("test the dashboard" - which parts?)
-- Multiple valid approaches (shared fixture vs per-test setup?)
-- Missing infrastructure (no playwright config, no test directory)
-- Authentication unclear (how do users log in? test account?)
-- External dependencies (tests need API keys, seeds, third-party services)
-
-**Stop and report:**
-- App bug discovered (test is correct, app is broken)
-- Max attempts reached (5 attempts with no progress)
-- Blocked by environment (app not running, wrong URL)
-- Test requires unavailable capabilities (mobile, specific browser)
-</decision_gates>
-
-<definition_of_done>
-Before marking a test complete:
-- [ ] Test passes consistently (2+ runs)
-- [ ] No flaky behavior detected
-- [ ] Test data is cleaned up (or isolated)
-- [ ] Selectors are resilient (not class-based)
-- [ ] No arbitrary timeouts used
-</definition_of_done>
-
-<communication>
-When reporting progress:
-- State which test is being worked on
-- Report pass/fail status after each run
-- When fixing, explain what was wrong and the fix
-- Summarize final status: X/Y tests passing
-</communication>`;
+
+// src/prompts/discover.ts
+var discoverPrompt;
+var init_discover = __esm({
+  "src/prompts/discover.ts"() {
+    "use strict";
+    discoverPrompt = `Discover and document the test framework setup for this project.
+
+**Your task:**
+1. Read package.json to identify the test framework (Playwright, WebDriverIO, Cypress, Cucumber, etc.)
+2. Find the test command in package.json scripts
+3. Locate existing tests and read 3-5 files to understand:
+   - Test file structure and naming conventions
+   - Page objects, fixtures, or helper utilities
+   - Selector strategies used (data-testid, roles, CSS, XPath)
+   - Test data setup patterns (API calls vs UI setup)
+   - Assertion patterns and custom matchers
+   - Wait strategies and timing patterns
+4. Identify best practices and patterns used in the codebase:
+   - How are tests organized (by feature, by page, by user flow)?
+   - Are there shared utilities or custom commands?
+   - How is authentication handled in tests?
+   - Are there environment-specific configurations?
+5. Write your findings to .supatest/SUPATEST.md in a "Test Framework" section
+
+**Example SUPATEST.md output:**
+
+## Test Framework
+
+- **Framework:** WebDriverIO + Cucumber
+- **Config:** wdio.conf.js
+- **Test command:** \`yarn start -- --provider browser --tags @tag_name\`
+
+### Project Structure
+- Features: src/features/
+- Step definitions: src/step_definitions/ui/
+- Page objects: src/pages/common/
+- API utilities: src/utils/endpoints/
+
+### Conventions
+- Selectors: data-testid preferred, fallback to aria selectors
+- Test data: Created via API endpoints before tests run
+- Naming: snake_case for feature files, camelCase for step definitions
+- Tags: @smoke for critical paths, @regression for full suite
+
+### Patterns
+- Page Object Model with lazy element initialization
+- API helpers for test data setup/teardown
+- Custom wait utilities in src/utils/waits.js
+- Shared authentication flow via login.task.js
+
+### Best Practices
+- Each test creates isolated test data
+- Cleanup in afterEach hooks
+- No hard-coded waits, use explicit element conditions
+- Screenshots on failure via reporter config
+
+If .supatest/SUPATEST.md already has a "Test Framework" section, report what's there and ask if the user wants to refresh it.`;
   }
 });
 
@@ -215,153 +148,73 @@ var init_fixer = __esm({
   "src/prompts/fixer.ts"() {
     "use strict";
     fixerPrompt = `<role>
-You are a Test Fixer Agent specialized in debugging failing tests, analyzing error logs, and fixing test issues in CI/headless environments.
+You are a Test Fixer Agent that debugs failing tests and fixes issues. You work with any test framework.
 </role>
 
-<core_workflow>
-Follow this debugging loop for each failing test:
-
-1. **Analyze** - Read the error message and stack trace carefully
-2. **Investigate** - Read the failing test file and code under test
-3. **Hypothesize** - Form a theory about the root cause (see categories below)
-4. **Fix** - Make minimal, targeted changes to fix the issue
-5. **Verify** - Run the test 2-3 times to confirm fix and detect flakiness
-6. **Iterate** - If still failing, return to step 1 (max 3 attempts per test)
-
-Continue until all tests pass. Do NOT stop after first failure.
-</core_workflow>
-
-<root_cause_categories>
-When diagnosing failures, classify into one of these categories:
-
-**Selector** - Element structure changed or locator is fragile
-- Element text/role changed \u2192 update selector
-- Element not visible \u2192 add proper wait
-- Multiple matches \u2192 make selector more specific
-
-**Timing** - Race condition, missing wait, async issue
-- Race condition \u2192 add explicit wait for element/state
-- Network delay \u2192 wait for API response
-- Animation \u2192 wait for animation to complete
-
-**State** - Test pollution, setup/teardown issue
-- Test pollution \u2192 ensure proper cleanup
-- Missing setup \u2192 add required preconditions
-- Stale data \u2192 refresh or recreate test data
-
-**Data** - Hardcoded data, missing test data
-- Hardcoded IDs \u2192 use dynamic data or fixtures
-- Missing test data \u2192 create via API setup
-
-**Logic** - Test assertion is wrong or outdated
-- Assertion doesn't match current behavior
-- Test expectations are incorrect
-</root_cause_categories>
-
-<playwright_execution>
-CRITICAL: Always run Playwright tests correctly to ensure clean exits.
-
-**Correct test commands:**
-- Single test: \`npx playwright test tests/example.spec.ts --reporter=list\`
-- All tests: \`npx playwright test --reporter=list\`
-- Retry failed: \`npx playwright test --last-failed --reporter=list\`
-
-**NEVER use:**
-- \`--ui\` flag (opens interactive UI that blocks)
-- \`--reporter=html\` without \`--reporter=list\` (may open server)
-- Commands without \`--reporter=list\` in CI/headless mode
-
-**Process management:**
-- Always use \`--reporter=list\` or \`--reporter=dot\` for clean output
-- Tests should exit automatically after completion
-- If a process hangs, kill it and retry with correct flags
-</playwright_execution>
-
-<debugging_with_mcp>
-When tests fail, use Playwright MCP tools to investigate:
-
-1. **Navigate**: Use \`mcp__playwright__playwright_navigate\` to load the failing page
-2. **Inspect DOM**: Use \`mcp__playwright__playwright_get_visible_html\` to see actual elements
-3. **Screenshot**: Use \`mcp__playwright__playwright_screenshot\` to capture current state
-4. **Console logs**: Use \`mcp__playwright__playwright_console_logs\` to check for JS errors
-5. **Interact**: Use click/fill tools to manually reproduce the flow
-
-**Workflow**: Navigate \u2192 inspect HTML \u2192 verify selectors \u2192 check console \u2192 fix
-</debugging_with_mcp>
-
-<flakiness_detection>
-After fixing, run the test 2-3 times. Watch for:
-
-- **Inconsistent results**: Passes sometimes, fails others
-- **Timing sensitivity**: Fails on slow runs, passes on fast
-- **Order dependence**: Fails when run with other tests
-- **Data coupling**: Relies on specific database state
-
-Common flakiness causes:
-- Arbitrary delays instead of condition waits
-- Shared state between tests
-- Hardcoded IDs or timestamps
-- Missing \`await\` on async operations
-- Race conditions in UI interactions
-</flakiness_detection>
-
-<fixing_patterns>
-**Selectors** - Prefer resilient locators:
-\`\`\`typescript
-// Good
-page.getByRole('button', { name: 'Submit' })
-page.getByTestId('submit-btn')
-
-// Avoid
-page.locator('.btn-primary')
-page.locator('div > button:nth-child(2)')
-\`\`\`
+<workflow>
+1. **Detect** - Check package.json to identify the test framework
+2. **Analyze** - Read error message and stack trace
+3. **Investigate** - Read failing test and code under test
+4. **Categorize** - Identify root cause type (selector, timing, state, data, or logic)
+5. **Fix** - Make minimal, targeted changes
+6. **Verify** - Run test 2-3 times to confirm fix and check for flakiness
+7. **Iterate** - If still failing, try a new hypothesis (max 3 attempts per test)
 
-**Timing** - Use condition-based waits, not arbitrary delays:
-\`\`\`typescript
-// Good
-await expect(element).toBeVisible({ timeout: 10_000 })
+Continue until all tests pass.
+</workflow>
 
-// Avoid
-await page.waitForTimeout(5000)
-\`\`\`
-</fixing_patterns>
+<root_causes>
+**Selector** - Element changed or locator is fragile \u2192 update selector, add wait, make more specific
 
-<decision_gates>
-**Keep iterating if:**
-- You haven't tried 3 attempts yet
-- You have a new hypothesis to test
-- The error message changed (progress)
+**Timing** - Race condition or async issue \u2192 add explicit wait for element/state/network
 
-**Escalate if:**
-- 3 attempts failed with no progress
-- Test identifies an actual app bug (don't mask bugs)
-- Test is fundamentally flaky by design
-- Requirements are ambiguous
+**State** - Test pollution or setup issue \u2192 ensure cleanup, add preconditions, refresh data
 
-When escalating, report what you tried and why it didn't work.
-</decision_gates>
+**Data** - Hardcoded or missing data \u2192 use dynamic data, create via API
+
+**Logic** - Assertion wrong or outdated \u2192 update expectation to match actual behavior
+</root_causes>
+
+<execution>
+- Run in headless/CI mode - avoid interactive UIs that block
+- Check package.json scripts for correct test command
+- Run single failing test first for faster feedback
+- If process hangs, kill it and check for interactive flags
+</execution>
+
+<fixing_principles>
+- Use semantic selectors (roles, labels, test IDs) over CSS classes
+- Use condition-based waits, not arbitrary delays
+- Each test should be independent with its own data
+- Don't weaken assertions to make tests pass
+- Don't skip or remove tests without understanding the failure
+</fixing_principles>
+
+<flakiness>
+After fixing, verify stability by running 2-3 times. Watch for:
+- Inconsistent pass/fail results
+- Timing sensitivity
+- Order dependence with other tests
+- Coupling to specific data state
+</flakiness>
 
-<avoid>
-- Hard-coding values to make specific tests pass
-- Removing or skipping tests without understanding why they fail
-- Over-mocking that hides real integration issues
-- Making tests pass by weakening assertions
-- Introducing flakiness through timing-dependent fixes
-</avoid>
+<decisions>
+**Keep iterating:** New hypothesis available, error message changed (progress), under 3 attempts
 
-<report_format>
-When reporting findings, use this structure:
+**Escalate:** 3 attempts with no progress, actual app bug found, requirements unclear
 
+When escalating, report what you tried and why it didn't work.
+</decisions>
+
+<report>
 **Status**: fixed | escalated | in-progress
-**Test**: [test file and name]
-**Root Cause**: [Category] - [Specific cause]
-**Fix**: [What you changed]
-**Verification**: [N] runs, [all passed / some failed]
-**Flakiness Risk**: [none | low | medium | high] - [reason]
+**Test**: [file and name]
+**Root Cause**: [category] - [specific cause]
+**Fix**: [what changed]
+**Verification**: [N runs, results]
 
-Summarize final status: X/Y tests passing
-</report_format>`;
+Summarize: X/Y tests passing
+</report>`;
   }
 });
 
@@ -435,6 +288,7 @@ var init_prompts = __esm({
   "src/prompts/index.ts"() {
     "use strict";
     init_builder();
+    init_discover();
     init_fixer();
     init_planner();
   }
@@ -5440,7 +5294,7 @@ var CLI_VERSION;
 var init_version = __esm({
   "src/version.ts"() {
     "use strict";
-    CLI_VERSION = "0.0.26";
+    CLI_VERSION = "0.0.28";
   }
 });
 
@@ -6697,17 +6551,10 @@ ${projectInstructions}`,
       async resolveClaudeCodePath() {
         const fs5 = await import("fs/promises");
         let claudeCodePath;
-        const bundledPath = join6(dirname(import.meta.url.replace("file://", "")), "claude-code-cli.js");
-        try {
-          await fs5.access(bundledPath);
-          claudeCodePath = bundledPath;
-          this.presenter.onLog(`Bundled mode: ${claudeCodePath}`);
-        } catch {
-          const require2 = createRequire(import.meta.url);
-          const sdkPath = require2.resolve("@anthropic-ai/claude-agent-sdk/sdk.mjs");
-          claudeCodePath = join6(dirname(sdkPath), "cli.js");
-          this.presenter.onLog(`Development mode: ${claudeCodePath}`);
-        }
+        const require2 = createRequire(import.meta.url);
+        const sdkPath = require2.resolve("@anthropic-ai/claude-agent-sdk/sdk.mjs");
+        claudeCodePath = join6(dirname(sdkPath), "cli.js");
+        this.presenter.onLog(`Using SDK CLI: ${claudeCodePath}`);
         if (config.claudeCodeExecutablePath) {
           claudeCodePath = config.claudeCodeExecutablePath;
           this.presenter.onLog(
@@ -10242,7 +10089,7 @@ var init_HelpMenu = __esm({
         /* @__PURE__ */ React22.createElement(Text17, { bold: true, color: theme.text.accent }, "\u{1F4D6} Supatest AI CLI - Help"),
         /* @__PURE__ */ React22.createElement(Box19, { marginTop: 1 }),
         /* @__PURE__ */ React22.createElement(Text17, { bold: true, color: theme.text.secondary }, "Slash Commands:"),
-        /* @__PURE__ */ React22.createElement(Box19, { flexDirection: "column", marginLeft: 2, marginTop: 0 }, /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/help"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " or "), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/?"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Toggle this help menu")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/resume"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Resume a previous session")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/clear"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Clear message history")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/model"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Cycle through available models")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/setup"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Initial setup for Supatest CLI")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/feedback"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Report an issue or request a feature")), isAuthenticated ? /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/logout"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Log out of Supatest")) : /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/login"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Authenticate with Supatest")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/exit"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Exit the CLI"))),
+        /* @__PURE__ */ React22.createElement(Box19, { flexDirection: "column", marginLeft: 2, marginTop: 0 }, /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/help"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " or "), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/?"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Toggle this help menu")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/resume"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Resume a previous session")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/clear"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Clear message history")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/model"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Cycle through available models")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/setup"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Initial setup for Supatest CLI")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/discover"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Discover test framework and write to SUPATEST.md")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/feedback"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Report an issue or request a feature")), isAuthenticated ? /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/logout"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Log out of Supatest")) : /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/login"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Authenticate with Supatest")), /* @__PURE__ */ React22.createElement(Text17, null, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/exit"), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, " - Exit the CLI"))),
         customCommands.length > 0 && /* @__PURE__ */ React22.createElement(React22.Fragment, null, /* @__PURE__ */ React22.createElement(Box19, { marginTop: 1 }), /* @__PURE__ */ React22.createElement(Text17, { bold: true, color: theme.text.secondary }, "Project Commands:"), /* @__PURE__ */ React22.createElement(Box19, { flexDirection: "column", marginLeft: 2, marginTop: 0 }, customCommands.slice(0, 5).map((cmd) => /* @__PURE__ */ React22.createElement(Text17, { key: cmd.name }, /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.accent }, "/", cmd.name), /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, cmd.description ? ` - ${cmd.description}` : ""))), customCommands.length > 5 && /* @__PURE__ */ React22.createElement(Text17, { color: theme.text.dim }, "...and ", customCommands.length - 5, " more (use Tab to autocomplete)"))),
         /* @__PURE__ */ React22.createElement(Box19, { marginTop: 1 }),
         /* @__PURE__ */ React22.createElement(Text17, { bold: true, color: theme.text.secondary }, "Keyboard Shortcuts:"),
@@ -10441,6 +10288,7 @@ var init_InputPrompt = __esm({
         { name: "/fix", desc: "Fix failing tests" },
         { name: "/feedback", desc: "Report an issue" },
         { name: "/setup", desc: "Install Playwright browsers" },
+        { name: "/discover", desc: "Discover test framework" },
         { name: "/login", desc: "Authenticate with Supatest" },
         { name: "/logout", desc: "Log out" },
         { name: "/exit", desc: "Exit CLI" }
@@ -10895,6 +10743,7 @@ var init_App = __esm({
     init_shared_es();
     init_login();
     init_setup();
+    init_prompts();
     init_command_discovery();
     init_stdio();
     init_token_storage();
@@ -11132,6 +10981,10 @@ var init_App = __esm({
             }
             return;
           }
+          if (command === "/discover") {
+            onSubmitTask?.(discoverPrompt);
+            return;
+          }
           const projectDir = config2.cwd || process.cwd();
           const spaceIndex = trimmedTask.indexOf(" ");
           const commandName = spaceIndex > 0 ? trimmedTask.slice(1, spaceIndex) : trimmedTask.slice(1);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@supatest/cli",
-  "version": "0.0.26",
+  "version": "0.0.28",
   "description": "Supatest CLI - AI-powered task automation for CI/CD",
   "type": "module",
   "bin": {
@@ -8,7 +8,6 @@
   },
   "files": [
     "dist",
-    "dist/claude-code-cli.js",
     "README.md",
     "LICENSE"
   ],
@@ -85,7 +84,7 @@
   "scripts": {
     "dev": "NODE_ENV=development tsx src/index.ts",
     "dev:watch": "nodemon",
-    "build": "tsup && node scripts/copy-claude-cli.js",
+    "build": "tsup",
     "type-check": "tsc --noEmit",
     "clean:bundle": "rimraf dist",
     "clean:node_modules": "rimraf node_modules"