@ranger-testing/ranger-cli 1.0.14 → 1.1.0

package/build/skills/ranger/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: ranger
+description: "Ranger's core development workflow for building e2e features. Use this skill for ANY feature development, implementation, or code changes that touches UI. Automatically tracks progress with checklist items, verifies implementations in the browser, and generates completion reports with evidence. Start every coding task by checking for existing features to resume."
+---
+
+# Ranger Skill
+
+This skill covers three workflows for Ranger feature tracking:
+
+## Supported Workflows
+
+| Workflow | When to Use | Required Reading |
+|----------|-------------|------------------|
+| **Resuming a Feature** | Starting a session | **MUST read [start.md](./start.md)** |
+| **Creating a Feature** | Starting new UI work | **MUST read [create.md](./create.md)** |
+| **Verifying a Feature** | After implementing UI changes | **MUST read [verify.md](./verify.md)** |
+
+---
+
+# Workflow 1: Resuming a Feature
+
+**MANDATORY: Read [start.md](./start.md) at the start of any session.**
+
+Use this workflow when:
+- Starting a new coding session
+- Returning to existing work
+- Before creating a new feature (always check first!)
+
+### Quick Start
+
+```bash
+# List features to find one to resume
+ranger feature list
+
+# Resume a specific feature by ID
+ranger feature resume <id>
+
+# Add a checklist item if scope expanded (be detailed!)
+ranger feature add-checklist-item "User navigates to /settings, clicks 'Edit Profile', updates display name, clicks Save, sees success toast, refreshes page, and confirms the new name persists"
+```
+
+---
+
+# Workflow 2: Creating a Ranger Feature
+
+**MANDATORY: Read [create.md](./create.md) before creating any feature.**
+
+Use this workflow when:
+- Starting new feature development
+- Planning UI changes
+- `ranger feature show` found no match
+- The feature you are developin is not found in `ranger feature list`
+
+### Quick Start
+
+```bash
+ranger feature create "<name>" \
+  --description "<description>" \
+  -c "<E2E checklist item 1>" \
+  -c "<E2E checklist item 2>"
+```
+
+### Critical: Checklist Items Are E2E Tests
+
+Checklist items are **E2E test scenarios**, NOT implementation tasks.
+
+❌ **WRONG:** `"Add login form validation"` (implementation task)
+❌ **WRONG:** `"API returns 200"` (backend task)
+✅ **RIGHT:** `"User can log in with valid credentials and see dashboard"` (E2E flow)
+
+**You MUST read [create.md](./create.md) for full guidance on writing checklist items.**
+
+---
+
+# Workflow 3: Verifying a Ranger Feature
+
+**MANDATORY: Read [verify.md](./verify.md) before verifying any checklist item.**
+
+Use this workflow when:
+- You've implemented code for a checklist item
+- Ready to verify the implementation works in a browser
+
+### Quick Start
+
+```bash
+# Verify a checklist item
+ranger verify-feature --task "<description of what to verify>"
+```
+
+The verification agent will:
+1. Execute the task in a real browser
+2. Evaluate if the checklist item is satisfied
+3. Mark the item as verified, partial, blocked, or failed
+4. Capture evidence (screenshots, traces)
+
+**You MUST read [verify.md](./verify.md) for full guidance on verification.**
+
+---
+
+# Finally Report
+
+Once you're done verifying, and just before stopping the session, share the feature review link with the user:
+
+> Feature explored! All checklist items have been tested.
+> **Link to feature review:** https://dashboard.ranger.net/features/{feature_id}
+
+---
+
+# Development Cycle
+
+```
+┌───────────────────────────────────────┐
+│  1. RESUME OR CREATE FEATURE          │  ◀── MUST READ start.md, create.md
+│     • ranger feature list             │
+│     • ranger feature resume <id>      │
+│     • OR ranger feature create        │
+└───────────────────┬───────────────────┘
+                    │
+                    ▼
+        ┌───────────────────────┐
+        │                       │
+        │   ┌───────────────┐   │
+        │   │ 2. IMPLEMENT  │   │  ◀── You write code
+        │   │    in code    │   │
+        │   └───────┬───────┘   │
+        │           │           │
+        │           ▼           │
+        │   ┌───────────────┐   │
+        │   │  3. VERIFY    │   │  ◀── MUST READ verify.md
+        │   │  in browser   │   │
+        │   └───────┬───────┘   │
+        │           │           │
+        │           ▼           │
+        │     More items?       │
+        │       YES ─┘          │
+        │                       │
+        └───────────┬───────────┘
+                    │ NO (all verified)
+                    ▼
+        ┌───────────────────────┐
+        │   Feature complete    │
+        └───────────────────────┘
+```
+
+---
+
+# Quick Reference
+
+| Command | Purpose |
+|---------|---------|
+| `ranger feature list` | List features (check before creating) |
+| `ranger feature resume <id>` | Resume a specific feature |
+| `ranger feature show` | Show current feature status |
+| `ranger feature create` | Create new feature with checklist |
+| `ranger feature add-checklist-item` | Add a checklist item to active feature |
+| `ranger verify-feature` | Verify checklist item in browser |
+
+# Key Principles
+
+1. **Read the docs first** - start.md before resuming, create.md before creating, verify.md before verifying
+2. **Always list first** - Run `ranger feature list` at session start before creating new features
+3. **Checklist items are E2E tests** - Not TODO lists, not backend tasks. BE DESCRIPTIVE and unambiguous when detailing the flow to cover. 
+4. **Verify after implementing** - Don't skip browser verification
+5. **Link to dashboard** - Whenever you are mentioning a feature, send out the full URL instead of just the feature ID (e.g. https://dashboard.ranger.net/features/{feature_id})

package/build/skills/ranger/create.md

@@ -0,0 +1,151 @@
+# Creating a New Feature
+
+Create a feature when starting new work that doesn't have an existing feature to resume.
+
+## Basic Command
+
+```bash
+ranger feature create "<feature name>" \
+  --description "<description>" \
+  -c "<checklist item 1>" \
+  -c "<checklist item 2>"
+```
+
+Use multiple `-c` flags for multiple checklist items. Each item can contain commas.
+
+## What Gets Captured Automatically
+
+When you create a feature, the CLI automatically captures:
+- **Git repo URL** - From `git remote get-url origin`
+- **Git branch** - From current branch name
+- **Created timestamp**
+- **Your organization** - From API token
+
+This enables `ranger feature list` to filter features by git context later.
+
+## Writing Good Checklist Items
+
+**CRITICAL: Checklist items are E2E test scenarios, NOT a TODO list.**
+
+Ranger verifies checklist items by running them in a real browser. Each item must describe a **complete user journey** that can be tested through the UI.
+
+### Key Principles
+
+1. **E2E flows only** - Each item is a test a QA engineer would run in the browser
+2. **Must be UI-testable** - No backend-only work, no code changes, no infrastructure tasks
+3. **Happy path focus** - Describe the successful user journey, not edge cases
+4. **Keep it minimal** - Prefer 1-2 items; only add more for genuinely distinct flows
+
+### What Checklist Items Are NOT
+
+❌ **NOT a TODO list** - Don't list implementation tasks
+```
+Bad: "Add validation to form"
+Bad: "Write unit tests"
+Bad: "Refactor auth module"
+```
+
+❌ **NOT backend features** - Must be verifiable through UI
+```
+Bad: "API returns correct response"
+Bad: "Database migration runs"
+Bad: "Caching layer works"
+```
+
+❌ **NOT granular UI checks** - Don't check individual elements
+```
+Bad: "Button is visible"
+Bad: "Form has 3 fields"
+Bad: "Error message is red"
+```
+
+### What Checklist Items ARE
+
+✅ **Complete E2E user flows** that a QA tester would execute:
+
+```
+Good: "User can log in with valid credentials and see the dashboard"
+Good: "User can add item to cart, proceed to checkout, and complete purchase"
+Good: "User can create a new project, invite a team member, and see them in the members list"
+```
+
+### Examples
+
+**Bad - implementation tasks:**
+```
+1. Add login endpoint
+2. Create session storage
+3. Build login form component
+4. Add form validation
+```
+
+**Good - E2E flow:**
+```
+1. User can log in with valid email/password and see their dashboard
+```
+
+**Bad - granular checks:**
+```
+1. Export button appears on Reports page
+2. Clicking button opens modal
+3. Modal has format dropdown
+4. Selecting CSV triggers download
+```
+
+**Good - single flow:**
+```
+1. User can navigate to Reports, click Export, select CSV format, and download the file
+```
+
+### When to Use Multiple Items
+
+Only split into multiple items for **genuinely distinct user journeys**:
+
+- Adding a button? **1 item** - the complete flow of using it
+- Login + signup? **2 items** - separate user journeys
+- Full CRUD? **3-4 items** - create, read, update, delete are distinct flows
+
+## Complete Example
+
+**Simple feature (1 item):**
+```bash
+ranger feature create "Add Export Button" \
+  --description "Add export functionality to the reports page" \
+  -c "Navigate to Reports page, click the new Export button, select CSV format, and verify the file downloads"
+```
+
+**Larger feature (multiple items):**
+```bash
+ranger feature create "User Authentication" \
+  --description "Login and signup flows for the web app" \
+  -c "Go to login page and sign in with valid credentials, verify redirect to dashboard" \
+  -c "Go to signup page and create new account, verify welcome email and successful login"
+```
+
+## Output
+
+```
+Creating feature...
+
+✅ Feature created: feat_01abc123
+
+🔄 User Authentication (feat_01abc123)
+   Status: in_progress
+   Description: Login and signup flows...
+   Repository: github.com/myorg/myapp
+   Branch: feature/auth
+   Created: 1/21/2026, 10:30:00 AM
+
+   Checklist:
+   1. ⬜ Go to login page and sign in...
+   2. ⬜ Go to signup page and create...
+
+➡️  Set as active feature
+```
+
+## After Creation
+
+The new feature is automatically set as the active feature. You can now:
+
+1. Start implementing the first checklist item
+2. View status with `ranger feature show`

package/build/skills/ranger/start.md

@@ -0,0 +1,122 @@
+# Starting a Feature Session
+
+At the START of any coding session, check if there's an existing feature to resume before creating a new one.
+
+## List Features
+
+First, check what features exist:
+
+```bash
+ranger feature list
+```
+
+Or filter to the current git branch:
+
+```bash
+ranger feature list --current-branch
+```
+
+This shows feature names, IDs, status, and branch info.
+
+## Resume a Feature
+
+If you find a pertinent feature to resume:
+
+```bash
+ranger feature resume <id>
+```
+
+This command:
+1. Sets the feature as active
+2. Starts the session if it's in `ready` status
+3. Displays the feature with its checklist
+
+## Check Current Status
+
+After resuming, view the full status:
+
+```bash
+ranger feature show
+```
+
+This displays:
+- Feature name and ID
+- Current status (in_progress, blocked, completed)
+- Git context (repo, branch)
+- Checklist with item statuses
+
+## Add Checklist Items
+
+If you need to add new work to an existing feature:
+
+```bash
+ranger feature add-checklist-item "User navigates to /settings, clicks 'Edit Profile', updates their display name, clicks Save, sees success toast, refreshes the page, and confirms the new name persists"
+```
+
+This adds a new pending checklist item to the active feature. Use this when:
+- The scope of work has expanded
+- You discover additional scenarios to verify
+- A review requested additional coverage
+
+### Writing Good Checklist Items
+
+Checklist items should be **detailed, multi-step E2E flows** that can be verified in a browser:
+
+**Bad (too vague):**
+```bash
+ranger feature add-checklist-item "Profile editing works"
+```
+
+**Good (detailed flow):**
+```bash
+ranger feature add-checklist-item "User goes to /settings, clicks 'Edit Profile' button, changes display name to 'Test User', clicks Save, sees 'Profile updated' success message, refreshes the page, and verifies the name still shows 'Test User'"
+```
+
+**Note:** You cannot add checklist items while a review is in progress.
+
+## Decision Tree
+
+```
+Start Session
+     │
+     ▼
+ranger feature list
+     │
+     ├── Found pertinent feature? ──▶ ranger feature resume <id>
+     │                                         │
+     │                                         ▼
+     │                                ranger feature show
+     │                                         │
+     │                                         ▼
+     │                                Continue working
+     │
+     └── None exist? ──▶ See create.md
+```
+
+## Example
+
+```bash
+# Start of session - list features
+$ ranger feature list
+
+Showing 3 of 3:
+
+🔄 User Authentication
+   ID: feat_abc123
+   Dev Status: In Progress
+   Branch: feature/auth
+
+# Resume the feature
+$ ranger feature resume feat_abc123
+
+✅ Resumed feature: User Authentication (feat_abc123)
+
+🔄 User Authentication (feat_abc123)
+   Dev Status: In Progress
+   Branch: feature/auth
+
+   Checklist:
+   1. ✅ Login flow works
+   2. ⬜ Signup creates account
+   3. ⬜ Password reset sends email
+```

package/build/skills/{feature-tracker → ranger}/verify.md

@@ -15,8 +15,8 @@ The URL is derived from your active environment's `baseUrl` setting.
 `verify-feature` requires an active feature. If you don't have one:
 
 ```bash
-ranger feature resume   # or
-ranger feature use <id>
+ranger feature list                # Find features to resume
+ranger feature resume <id>         # Resume a specific feature
 ```
 
 ## The Verification Flow
@@ -71,6 +71,36 @@ After verification, the agent evaluates if the result satisfies the checklist it
 | **Blocked** | Bug or error prevents completion | 🛑 Blocked |
 | **Failed** | Task couldn't be executed | ⬜ Pending (issues documented) |
 
+## Parallel Verification
+
+Run multiple non-conflicting verifications in parallel using background execution.
+
+### How to Run
+
+Use Bash with `run_in_background: true`:
+
+```
+[Bash: ranger verify-feature --item 1, run_in_background: true] → task_abc
+[Bash: ranger verify-feature --item 2, run_in_background: true] → task_def
+```
+
+Poll with TaskOutput, report results as they complete.
+
+### Safe to Parallelize
+
+- Viewing pages, checking UI elements, navigation tests
+- Read-only operations that don't modify shared state
+
+### Do NOT Parallelize
+
+- Logout tests (affects auth state for other sessions)
+- Create/delete operations on shared data
+- Tests with dependencies on each other
+
+### CRITICAL: No Code Edits During Verification
+
+File watchers (Next.js, Vite) will restart the dev server and break active browser sessions. Finish all code changes before running verifications.
+
 ## Examples
 
 ### Basic Verification
@@ -127,7 +157,7 @@ Access evidence via the report or dashboard.
 ## Troubleshooting
 
 ### "No active feature"
-Run `ranger feature resume` or `ranger feature use <id>` first.
+Run `ranger feature list` to find features, then `ranger feature resume <id>` to resume one.
 
 ### "No active environment"
 Run `ranger use <env-name>` to set an environment with browser access.

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@ranger-testing/ranger-cli",
-    "version": "1.0.14",
+    "version": "1.1.0",
     "type": "module",
     "bin": {
         "ranger": "./build/cli.js",

package/build/commands/postEditHook.js

@@ -1,25 +0,0 @@
-/**
- * PostToolUse (Write/Edit) hook handler for Claude Code plugin
- *
- * This command is invoked automatically after Write or Edit tools are used.
- * It reminds Claude to verify features with Ranger before stopping the session.
- */
-export async function postEditHook() {
-    try {
-        // Output reminder as JSON with additionalContext
-        const response = {
-            additionalContext: `REMINDER: You just edited a file. Before stopping this session:
-1. If you haven't already, create a Ranger feature: \`ranger feature create "..." -c "..."\`
-2. Verify your changes in the browser: \`ranger verify-feature --task "..."\`
-
-The user expects you to NOT stop the session until the feature is fully verified with Ranger.
-Use /feature-tracker for the complete workflow.`,
-        };
-        console.log(JSON.stringify(response));
-    }
-    catch {
-        // Silently fail - don't interrupt the user's workflow
-        // Hooks should be non-blocking
-    }
-}
-//# sourceMappingURL=postEditHook.js.map

package/build/commands/postEditHook.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"postEditHook.js","sourceRoot":"","sources":["../../src/commands/postEditHook.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,MAAM,CAAC,KAAK,UAAU,YAAY;IAC9B,IAAI,CAAC;QACD,iDAAiD;QACjD,MAAM,QAAQ,GAAG;YACb,iBAAiB,EAAE;;;;;gDAKiB;SACvC,CAAC;QAEF,OAAO,CAAC,GAAG,CAAC,IAAI,CAAC,SAAS,CAAC,QAAQ,CAAC,CAAC,CAAC;IAC1C,CAAC;IAAC,MAAM,CAAC;QACL,sDAAsD;QACtD,+BAA+B;IACnC,CAAC;AACL,CAAC"}

package/build/commands/preCompactHook.js

@@ -1,85 +0,0 @@
-import { execSync } from 'child_process';
-import { getActiveFeatureId } from './feature.js';
-import { getFeature } from './utils/featureApi.js';
-import { getToken } from './utils/keychain.js';
-import { getFeatureTrackerSkillContent } from './utils/skillContent.js';
-/**
- * Get the current git branch
- */
-function getGitBranch() {
-    try {
-        return execSync('git rev-parse --abbrev-ref HEAD', {
-            encoding: 'utf-8',
-            stdio: ['pipe', 'pipe', 'pipe'],
-        }).trim();
-    }
-    catch {
-        return undefined;
-    }
-}
-/**
- * PreCompact hook handler for Claude Code plugin
- *
- * This command is invoked automatically before Claude Code compacts the conversation.
- * It reminds Claude to preserve Ranger workflow context in the compaction summary.
- */
-export async function preCompactHook() {
-    try {
-        // Check if Ranger is configured
-        const token = await getToken();
-        if (!token) {
-            // Silently exit if Ranger isn't configured
-            return;
-        }
-        // Check for active feature and compare git branches
-        const featureId = await getActiveFeatureId();
-        if (featureId) {
-            try {
-                const feature = await getFeature(featureId);
-                const currentBranch = getGitBranch();
-                // If branches don't match, this feature isn't relevant to current work
-                if (feature.gitBranch &&
-                    currentBranch &&
-                    feature.gitBranch !== currentBranch) {
-                    return;
-                }
-            }
-            catch {
-                // Feature may have been deleted or API error, continue with reminder
-            }
-        }
-        const skillContent = getFeatureTrackerSkillContent();
-        // Output reminder for compaction summary - mirrors sessionStartHook structure
-        console.log('='.repeat(60));
-        console.log('RANGER FEATURE TRACKER - INCLUDE IN COMPACTION SUMMARY');
-        console.log('='.repeat(60));
-        console.log();
-        console.log('IMPORTANT: For ANY feature work that touches UI, you MUST use');
-        console.log('the /feature-tracker skill to create a feature with a checklist');
-        console.log('and verify each item in the browser before completion.');
-        console.log();
-        console.log('--- SKILL.md START ---');
-        console.log(skillContent);
-        console.log('--- SKILL.md END ---');
-        console.log();
-        console.log('=== RANGER FEATURE TRACKING - REQUIRED FOR UI WORK ===');
-        console.log();
-        console.log('For ANY feature work that touches UI, you MUST create a Ranger feature and verify it.');
-        console.log();
-        console.log('**IF YOU ARE IN PLAN MODE:**');
-        console.log('Before you start making the rest of the plan, add instructions to use Ranger');
-        console.log('to verify the feature, assuming the feature requested impacts the UI in some way.');
-        console.log();
-        console.log('**IF YOU ARE NOT IN PLAN MODE:**');
-        console.log('Resume the feature by running: ranger feature resume && ranger feature show');
-        console.log('This will find the in-progress feature matching the current git branch');
-        console.log('and display the checklist status so you can continue.');
-        console.log();
-        console.log('=== END RANGER INSTRUCTIONS ===');
-    }
-    catch {
-        // Silently fail - don't interrupt compaction
-        // Hooks should be non-blocking
-    }
-}
-//# sourceMappingURL=preCompactHook.js.map

package/build/commands/preCompactHook.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"preCompactHook.js","sourceRoot":"","sources":["../../src/commands/preCompactHook.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,QAAQ,EAAE,MAAM,eAAe,CAAC;AACzC,OAAO,EAAE,kBAAkB,EAAE,MAAM,cAAc,CAAC;AAClD,OAAO,EAAE,UAAU,EAAE,MAAM,uBAAuB,CAAC;AACnD,OAAO,EAAE,QAAQ,EAAE,MAAM,qBAAqB,CAAC;AAC/C,OAAO,EAAE,6BAA6B,EAAE,MAAM,yBAAyB,CAAC;AAExE;;GAEG;AACH,SAAS,YAAY;IACjB,IAAI,CAAC;QACD,OAAO,QAAQ,CAAC,iCAAiC,EAAE;YAC/C,QAAQ,EAAE,OAAO;YACjB,KAAK,EAAE,CAAC,MAAM,EAAE,MAAM,EAAE,MAAM,CAAC;SAClC,CAAC,CAAC,IAAI,EAAE,CAAC;IACd,CAAC;IAAC,MAAM,CAAC;QACL,OAAO,SAAS,CAAC;IACrB,CAAC;AACL,CAAC;AAED;;;;;GAKG;AACH,MAAM,CAAC,KAAK,UAAU,cAAc;IAChC,IAAI,CAAC;QACD,gCAAgC;QAChC,MAAM,KAAK,GAAG,MAAM,QAAQ,EAAE,CAAC;QAC/B,IAAI,CAAC,KAAK,EAAE,CAAC;YACT,2CAA2C;YAC3C,OAAO;QACX,CAAC;QAED,oDAAoD;QACpD,MAAM,SAAS,GAAG,MAAM,kBAAkB,EAAE,CAAC;QAC7C,IAAI,SAAS,EAAE,CAAC;YACZ,IAAI,CAAC;gBACD,MAAM,OAAO,GAAG,MAAM,UAAU,CAAC,SAAS,CAAC,CAAC;gBAC5C,MAAM,aAAa,GAAG,YAAY,EAAE,CAAC;gBAErC,uEAAuE;gBACvE,IACI,OAAO,CAAC,SAAS;oBACjB,aAAa;oBACb,OAAO,CAAC,SAAS,KAAK,aAAa,EACrC,CAAC;oBACC,OAAO;gBACX,CAAC;YACL,CAAC;YAAC,MAAM,CAAC;gBACL,qEAAqE;YACzE,CAAC;QACL,CAAC;QAED,MAAM,YAAY,GAAG,6BAA6B,EAAE,CAAC;QAErD,8EAA8E;QAC9E,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;QAC5B,OAAO,CAAC,GAAG,CAAC,wDAAwD,CAAC,CAAC;QACtE,OAAO,CAAC,GAAG,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC,CAAC;QAC5B,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CACP,+DAA+D,CAClE,CAAC;QACF,OAAO,CAAC,GAAG,CACP,iEAAiE,CACpE,CAAC;QACF,OAAO,CAAC,GAAG,CAAC,wDAAwD,CAAC,CAAC;QACtE,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,wBAAwB,CAAC,CAAC;QACtC,OAAO,CAAC,GAAG,CAAC,YAAY,CAAC,CAAC;QAC1B,OAAO,CAAC,GAAG,CAAC,sBAAsB,CAAC,CAAC;QACpC,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,wDAAwD,CAAC,CAAC;QACtE,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CACP,uFAAuF,CAC1F,CAAC;QACF,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,8BAA8B,CAAC,CAAC;QAC5C,OAAO,CAAC,GAAG,CACP,8EAA8E,CACjF,CAAC;QACF,OAAO,CAAC,GAAG,CACP,mFAAmF,CACtF,CAAC;QACF,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,kCAAkC,CAAC,CAAC;QAChD,OAAO,CAAC,GAAG,CACP,6EAA6E,CAChF,CAAC;QACF,OAAO,CAAC,GAAG,CACP,wEAAwE,CAC3E,CAAC;QACF,OAAO,CAAC,GAAG,CAAC,uDAAuD,CAAC,CAAC;QACrE,OAAO,CAAC,GAAG,EAAE,CAAC;QACd,OAAO,CAAC,GAAG,CAAC,iCAAiC,CAAC,CAAC;IACnD,CAAC;IAAC,MAAM,CAAC;QACL,6CAA6C;QAC7C,+BAA+B;IACnC,CAAC;AACL,CAAC"}

package/build/commands/sessionStartHook.js

@@ -1,64 +0,0 @@
-import { getFeatureTrackerSkillContent } from './utils/skillContent.js';
-import { getToken } from './utils/keychain.js';
-/**
- * SessionStart hook handler for Claude Code plugin
- *
- * This command is invoked automatically when a new Claude Code session starts.
- * It loads and displays the feature-tracker skill context to help Claude understand the workflow.
- */
-export async function sessionStartHook() {
-    // Check if CLI is configured (has token)
-    const token = await getToken();
-    if (!token) {
-        console.log('='.repeat(60));
-        console.log('RANGER SETUP REQUIRED');
-        console.log('='.repeat(60));
-        console.log();
-        console.log('The Ranger CLI is not configured. To get started:');
-        console.log();
-        console.log('1. Install the CLI (in a regular terminal):');
-        console.log('   npm install -g @ranger-testing/ranger-cli');
-        console.log();
-        console.log('2. Get your API token: https://dashboard.ranger.net/cli');
-        console.log();
-        console.log('3. Initialize Ranger (in a regular terminal):');
-        console.log('   ranger start <your-token>');
-        console.log();
-        console.log('After setup, restart your Claude Code session.');
-        console.log('='.repeat(60));
-        return;
-    }
-    const skillContent = getFeatureTrackerSkillContent();
-    console.log('='.repeat(60));
-    console.log('RANGER FEATURE TRACKER - READ THIS CAREFULLY');
-    console.log('='.repeat(60));
-    console.log();
-    console.log('IMPORTANT: For ANY feature work that touches UI, you MUST use');
-    console.log('the /feature-tracker skill to create a feature with a checklist');
-    console.log('and verify each item in the browser before completion.');
-    console.log();
-    console.log('--- SKILL.md START ---');
-    console.log(skillContent);
-    console.log('--- SKILL.md END ---');
-    console.log();
-    console.log('='.repeat(60));
-    console.log();
-    console.log('=== RANGER FEATURE TRACKING - REQUIRED FOR UI WORK ===');
-    console.log();
-    console.log('For ANY feature work that touches UI, you MUST create a Ranger feature and verify it.');
-    console.log();
-    console.log('**IF YOU ARE IN PLAN MODE:**');
-    console.log('Before you start making the rest of the plan, add instructions to use Ranger');
-    console.log('to verify the feature, assuming the feature requested impacts the UI in some way.');
-    console.log();
-    console.log('**IF YOU ARE NOT IN PLAN MODE:**');
-    console.log('ALWAYS create the Ranger feature FIRST with `ranger feature create` before');
-    console.log('starting any development work. This way you can track progress and come back to it.');
-    console.log('After implementing, verify each item with `ranger verify-feature --task "..."`.');
-    console.log();
-    console.log('=== END RANGER INSTRUCTIONS ===');
-    // TODO: Re-enable active feature context display when ready
-    // const featureId = await getActiveFeatureId();
-    // if (featureId) { ... }
-}
-//# sourceMappingURL=sessionStartHook.js.map