fix substitution in bug-hunt slash command

Author: sohankshirsagar

.claude/commands/bug-hunt.md

@@ -12,7 +12,7 @@ $ARGUMENTS - The library name, optionally followed by focus context.
 - `/bug-hunt redis focus on pub sub interactions` — prioritize pub/sub patterns
 - `/bug-hunt psycopg2 focus on async cursors and connection pooling` — prioritize those areas
 
-**Parsing**: The first word is always the library name. Everything after it is the optional focus context.
+**Parsing**: The first word of `$ARGUMENTS` is always the library name. Everything after it is the optional focus context. All references to `<library>` below mean this parsed first word — NOT the raw `$ARGUMENTS` string.
 
 ## Library-to-GitHub-Repo Mapping
 
@@ -185,11 +185,11 @@ Produce a prioritized list of potential bugs to investigate.
 Create `BUG_TRACKING.md` in the e2e test directory:
 
 ```bash
-# Path: drift/instrumentation/$ARGUMENTS/e2e-tests/BUG_TRACKING.md
+# Path: drift/instrumentation/<library>/e2e-tests/BUG_TRACKING.md
 ```
 
 ```markdown
-# $ARGUMENTS Instrumentation Bug Tracking
+# <library> Instrumentation Bug Tracking
 
 Generated: <current date and time>
 
@@ -218,7 +218,7 @@ For each potential bug, follow this workflow:
 Navigate to the e2e test directory:
 
 ```bash
-cd drift/instrumentation/$ARGUMENTS/e2e-tests/
+cd drift/instrumentation/<library>/e2e-tests/
 ```
 
 Build and start Docker containers:
@@ -426,14 +426,14 @@ rm -rf /tmp/*-source
 Commit the changes:
 
 ```bash
-git add drift/instrumentation/$ARGUMENTS/e2e-tests/
-git commit -m "bug-hunt($ARGUMENTS): add e2e tests exposing instrumentation bugs"
+git add drift/instrumentation/<library>/e2e-tests/
+git commit -m "bug-hunt(<library>): add e2e tests exposing instrumentation bugs"
 ```
 
 Push the branch (skip if in Claude Code Web where the session handles this):
 
 ```bash
-git push origin bug-hunt/$ARGUMENTS-$(date +%Y-%m-%d)
+git push origin bug-hunt/<library>-$(date +%Y-%m-%d)
 ```
 
 ---

docs/environment-variables.md

@@ -11,7 +11,7 @@ The `TUSK_DRIFT_MODE` environment variable controls how the SDK operates in your
 | Mode       | Description                                          | When to Use                                                                                  |
 | ---------- | ---------------------------------------------------- | -------------------------------------------------------------------------------------------- |
 | `RECORD`   | Records traces for all instrumented operations       | Set this in environments where you want to capture API traces (e.g., staging, production)    |
-| `REPLAY`   | Replays previously recorded traces                   | Automatically set by the Tusk CLI when running `tusk run` - you should NOT set this manually |
+| `REPLAY`   | Replays previously recorded traces                   | Automatically set by the Tusk CLI when running `tusk drift run` - you should NOT set this manually |
 | `DISABLED` | Disables all instrumentation and recording           | Use when you want to completely disable Tusk with no performance impact                      |
 | Unset      | Same as `DISABLED` - no instrumentation or recording | Default state when the variable is not set                                                   |
 
@@ -25,7 +25,7 @@ The `TUSK_DRIFT_MODE` environment variable controls how the SDK operates in your
 
 **Replaying Traces:**
 
-- `TUSK_DRIFT_MODE` is automatically set to `REPLAY` by the Tusk CLI when you run `tusk run`
+- `TUSK_DRIFT_MODE` is automatically set to `REPLAY` by the Tusk CLI when you run `tusk drift run`
 - **Do NOT** manually set `TUSK_DRIFT_MODE=REPLAY` in your application startup commands
 - The start command specified in your `.tusk/config.yaml` should NOT cause `TUSK_DRIFT_MODE` to be set to anything - the CLI handles this automatically
 
@@ -61,7 +61,7 @@ start_command: "python app.py" # Do NOT include TUSK_DRIFT_MODE here
 
 ```bash
 # The CLI automatically sets TUSK_DRIFT_MODE=REPLAY
-tusk run
+tusk drift run
 ```
 
 **Disabling Tusk:**
@@ -99,7 +99,7 @@ Your Tusk Drift API key, required when using Tusk Cloud for storing and managing
 - Can be set as an environment variable:
 
   ```bash
-  TUSK_API_KEY=your-api-key-here tusk run
+  TUSK_API_KEY=your-api-key-here tusk drift run
   ```
 
 - Or use the Tusk CLI login command (recommended):

docs/quickstart.md

@@ -56,7 +56,7 @@ Need to install the Tusk CLI? See [CLI installation guide](https://github.com/Us
 Replay the recorded test:
 
 ```bash
-tusk run
+tusk drift run
 ```
 
 You should see an output similar to:

drift/instrumentation/README-e2e-tests.md

@@ -184,7 +184,7 @@ The e2e tests follow a **Docker entrypoint-driven architecture** where the Pytho
 │   - Stop app, verify traces created     │
 │                                         │
 │  Phase 3: Run Tests                     │
-│   - Execute `tusk run` CLI              │
+│   - Execute `tusk drift run` CLI        │
 │   - Parse JSON test results             │
 │                                         │
 │  Phase 4: Check Instrumentation Warnings│

drift/instrumentation/e2e_common/base_runner.py

@@ -296,12 +296,12 @@ def run_tests(self):
             check=False,
         )
 
-        # Debug: show what tusk run returned
-        self.log(f"tusk run exit code: {result.returncode}", Colors.YELLOW)
+        # Debug: show what tusk drift run returned
+        self.log(f"tusk drift run exit code: {result.returncode}", Colors.YELLOW)
         if result.stdout:
-            self.log(f"tusk run stdout:\n{result.stdout}", Colors.YELLOW)
+            self.log(f"tusk drift run stdout:\n{result.stdout}", Colors.YELLOW)
         if result.stderr:
-            self.log(f"tusk run stderr:\n{result.stderr}", Colors.YELLOW)
+            self.log(f"tusk drift run stderr:\n{result.stderr}", Colors.YELLOW)
 
         # Parse JSON results
         self.parse_test_results(result.stdout)
@@ -429,7 +429,7 @@ def check_socket_instrumentation_warnings(self):
         else:
             self.log("✓ No socket instrumentation warnings found.", Colors.GREEN)
 
-        # Verify trace files exist (double-check after tusk run)
+        # Verify trace files exist (double-check after tusk drift run)
         trace_files = list(traces_dir.glob("*.jsonl")) if traces_dir.exists() else []
         if trace_files:
             self.log(f"✓ Found {len(trace_files)} trace file(s).", Colors.GREEN)