@ranger-testing/ranger-cli 2.4.5 → 2.4.7

package/build/skills/ranger/start.md

@@ -7,13 +7,13 @@ At the START of any coding session that touches the frontend or UI, check if the
 First, check what feature reviews exist:
 
 ```bash
-ranger list
+ranger-cli list
 ```
 
 Or filter to the current git branch:
 
 ```bash
-ranger list --current-branch
+ranger-cli list --current-branch
 ```
 
 This shows feature review names, IDs, status, and branch info.
@@ -23,7 +23,7 @@ This shows feature review names, IDs, status, and branch info.
 If you find a pertinent feature review to resume:
 
 ```bash
-ranger resume <id>
+ranger-cli resume <id>
 ```
 
 This command:
@@ -41,7 +41,7 @@ End the conversational turn by sharing the dashboard link whenever you resume a
 After resuming, view the full status:
 
 ```bash
-ranger show
+ranger-cli show
 ```
 
 This displays:
@@ -55,7 +55,7 @@ This displays:
 If any scenarios show comment badges (e.g., `[2 comments]`) or are at v2+, reviewer feedback needs to be addressed:
 
 ```bash
-ranger get-review
+ranger-cli get-review
 ```
 
 This shows the actual comment content, who wrote it, and the previous version description. **Read [feedback.md](./feedback.md) for the full feedback workflow.**
@@ -65,7 +65,7 @@ This shows the actual comment content, who wrote it, and the previous version de
 If you need to add new work to an existing feature review:
 
 ```bash
-ranger add-scenario "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"
+ranger-cli add-scenario "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 scenario to the active feature review. Use this when:
@@ -79,12 +79,12 @@ Scenarios should be **detailed, multi-step E2E flows** that can be verified in a
 
 **Bad (too vague):**
 ```bash
-ranger add-scenario "Profile editing works"
+ranger-cli add-scenario "Profile editing works"
 ```
 
 **Good (detailed flow):**
 ```bash
-ranger add-scenario "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'"
+ranger-cli add-scenario "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 scenarios while a review is in progress.
@@ -95,12 +95,12 @@ ranger add-scenario "User goes to /settings, clicks 'Edit Profile' button, chang
 Start Session
      │
      ▼
-ranger list
+ranger-cli list
      │
-     ├── Found pertinent feature review? ──▶ ranger resume <id>
+     ├── Found pertinent feature review? ──▶ ranger-cli resume <id>
      │                                         │
      │                                         ▼
-     │                                ranger show
+     │                                ranger-cli show
      │                                         │
      │                                         ▼
      │                                Scenarios have comments?
@@ -118,7 +118,7 @@ ranger list
 
 ```bash
 # Start of session - list feature reviews
-$ ranger list
+$ ranger-cli list
 
 Showing 3 of 3:
 
@@ -128,7 +128,7 @@ Showing 3 of 3:
    Branch: feature/auth
 
 # Resume the feature review
-$ ranger resume feat_abc123
+$ ranger-cli resume feat_abc123
 
 ✅ Resumed feature review: User Authentication (feat_abc123)
 

package/build/skills/ranger/verify.md

@@ -5,7 +5,7 @@ After implementing code for a scenario, verify it works in the browser. This cre
 ## Basic Command
 
 ```bash
-ranger go --scenario <N> --notes "<what to verify>"
+ranger-cli go --scenario <N> --notes "<what to verify>"
 ```
 
 The URL is derived from your active profile's `baseUrl` setting.
@@ -15,8 +15,8 @@ The URL is derived from your active profile's `baseUrl` setting.
 `go` requires an active feature review. If you don't have one:
 
 ```bash
-ranger list                # Find feature reviews to resume
-ranger resume <id>         # Resume a specific feature review
+ranger-cli list                # Find feature reviews to resume
+ranger-cli resume <id>         # Resume a specific feature review
 ```
 
 ## The Verification Flow
@@ -67,7 +67,7 @@ If your scenario has a detailed description, you can omit `--notes`:
 
 ```bash
 # Scenario 1: "User can log in with valid credentials - sees loading state - redirects to dashboard"
-ranger go --scenario 1
+ranger-cli go --scenario 1
 ```
 
 The scenario description becomes the task automatically.
@@ -92,8 +92,8 @@ Run multiple non-conflicting verifications in parallel using background executio
 Use Bash with `run_in_background: true`:
 
 ```
-[Bash: ranger go --scenario 1, run_in_background: true] → task_abc
-[Bash: ranger go --scenario 2, run_in_background: true] → task_def
+[Bash: ranger-cli go --scenario 1, run_in_background: true] → task_abc
+[Bash: ranger-cli go --scenario 2, run_in_background: true] → task_def
 ```
 
 Poll with TaskOutput, report results as they complete.
@@ -118,44 +118,31 @@ File watchers (Next.js, Vite) will restart the dev server and break active brows
 ### Basic Verification
 
 ```bash
-ranger go \
-  --scenario 1 \
-  --notes "Log in with test@example.com / password123, verify redirect to dashboard"
+ranger-cli go --scenario 1 --notes "Log in with test@example.com / password123, verify redirect to dashboard"
 ```
 
 ### Verify Specific Scenario
 
 ```bash
 # Skip the selection prompt, verify scenario 2 directly
-ranger go \
-  --notes "Complete signup flow with new email" \
-  --scenario 2
+ranger-cli go --notes "Complete signup flow with new email" --scenario 2
 ```
 
 ### Verify with Specific Profile
 
 ```bash
 # Use staging profile instead of active profile
-ranger go \
-  --profile staging \
-  --scenario 1 \
-  --notes "Verify login works in staging"
+ranger-cli go --profile staging --scenario 1 --notes "Verify login works in staging"
 ```
 
 ### Start on a Specific Page
 
 ```bash
 # Start verification at /settings instead of base URL
-ranger go \
-  --start-path /settings \
-  --scenario 1 \
-  --notes "Verify user can update their profile"
+ranger-cli go --start-path /settings --scenario 1 --notes "Verify user can update their profile"
 
 # Start at /admin/users
-ranger go \
-  --start-path /admin/users \
-  --scenario 2 \
-  --notes "Verify admin can see user list"
+ranger-cli go --start-path /admin/users --scenario 2 --notes "Verify admin can see user list"
 ```
 
 ## After Verification
@@ -163,7 +150,7 @@ ranger go \
 Check progress:
 
 ```bash
-ranger show
+ranger-cli show
 ```
 
 If all non-closed scenarios are verified, the feature review auto-completes:
@@ -184,7 +171,7 @@ Each verification creates:
 
 Access evidence via the report or dashboard.
 
-Always end the conversational turn by sharing the dashboard link whenever you run `ranger go`:
+Always end the conversational turn by sharing the dashboard link whenever you run `ranger-cli go ...`:
 
 > Here is the link to the Feature Review in Ranger. Leave comments in the dashboard and then resume the feature review in your agent.
 > https://dashboard.ranger.net/features/{feature_id}
@@ -192,10 +179,10 @@ Always end the conversational turn by sharing the dashboard link whenever you ru
 ## Troubleshooting
 
 ### "No active feature review"
-Run `ranger list` to find feature reviews, then `ranger resume <id>` to resume one.
+Run `ranger-cli list` to find feature reviews, then `ranger-cli resume <id>` to resume one.
 
 ### "No active profile"
-Run `ranger profile use <profile-name>` to set a profile with browser access.
+Run `ranger-cli profile use <profile-name>` to set a profile with browser access.
 
 ### Verification times out
 The agent has 59 minutes max. For very long flows, break into smaller scenarios.

package/package.json

@@ -1,9 +1,10 @@
 {
     "name": "@ranger-testing/ranger-cli",
-    "version": "2.4.5",
+    "version": "2.4.7",
     "type": "module",
     "bin": {
-        "ranger": "./build/cli.js"
+        "ranger": "./build/cli.js",
+        "ranger-cli": "./build/cli.js"
     },
     "scripts": {
         "build": "tsc && npm run obfuscate && cp -r src/skills build/ && chmod 755 build/cli.js",
@@ -35,6 +36,7 @@
         "typescript": "^5.0.0"
     },
     "overrides": {
-        "minimatch": "^10.2.3"
+        "minimatch": "^10.2.3",
+        "brace-expansion": "^5.0.5"
     }
 }

package/scripts/postinstall.js

@@ -2,7 +2,7 @@
 
 /**
  * Postinstall script for @ranger-testing/ranger-cli
- * Displays welcome message and setup instructions after npm install
+ * Displays welcome message and setup instructions after npm install.
  */
 
 console.log(`
@@ -12,6 +12,9 @@ Get started:
   1. Get your API token: https://dashboard.ranger.net/cli
   2. Run: ranger setup [token]
 
+If "ranger" conflicts with another program on your system, you can use
+"ranger-cli" or "npx ranger" instead.
+
 For Claude Code, install the plugin in Claude Code:
   /plugin marketplace add ranger-testing/trailhead
   /plugin install ranger@trailhead