rdc-cli 0.3.5__tar.gz → 0.3.6__tar.gz

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rdc-cli
-Version: 0.3.5
+Version: 0.3.6
 Summary: CLI for RenderDoc .rdc captures
 Author: Jim
 License-Expression: MIT
@@ -74,17 +74,14 @@ python scripts/build_renderdoc.py     # needs cmake + Visual Studio Build Tools
 rdc doctor
 ```
 
-**PyPI — macOS** (remote replay recommended)
+**PyPI — macOS** (Split client only)
 
 ```bash
 pipx install rdc-cli
-# Remote replay (no local renderdoc needed):
-rdc remote connect linux-host:39920      # connect to a Linux/Windows target
-rdc remote list                          # list capturable apps
-rdc remote capture /path/to/app          # capture + pull .rdc file
-# Optional: local replay — run inside repo for auto-managed deps
-# pixi run setup-renderdoc  (installs cmake/ninja/autotools via pixi)
-# or: python scripts/build_renderdoc.py
+# Local replay on macOS is not supported right now.
+# Use Split mode and run replay on a Linux/Windows daemon:
+#   rdc open /tmp/frame.rdc --listen 0.0.0.0:54321   # on replay host
+#   rdc open --connect host:54321 --token TOKEN       # on macOS client
 rdc doctor
 ```
 
@@ -111,8 +108,8 @@ pixi run setup-renderdoc
 | Platform | Local capture/replay | Split client |
 |----------|----------------------|--------------|
 | Linux | ✅ | ✅ |
-| macOS | ✅ (`pixi run setup-renderdoc`) | ✅ (no local RenderDoc needed) |
-| Windows *(experimental, not tested in this PR)* | ⚠️ expected | ⚠️ expected |
+| macOS | ❌ (not supported yet) | ✅ (recommended) |
+| Windows (experimental) | ⚠️ expected | ⚠️ expected |
 
 ### RenderDoc bootstrap (all platforms)
 

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/README.md

@@ -45,17 +45,14 @@ python scripts/build_renderdoc.py     # needs cmake + Visual Studio Build Tools
 rdc doctor
 ```
 
-**PyPI — macOS** (remote replay recommended)
+**PyPI — macOS** (Split client only)
 
 ```bash
 pipx install rdc-cli
-# Remote replay (no local renderdoc needed):
-rdc remote connect linux-host:39920      # connect to a Linux/Windows target
-rdc remote list                          # list capturable apps
-rdc remote capture /path/to/app          # capture + pull .rdc file
-# Optional: local replay — run inside repo for auto-managed deps
-# pixi run setup-renderdoc  (installs cmake/ninja/autotools via pixi)
-# or: python scripts/build_renderdoc.py
+# Local replay on macOS is not supported right now.
+# Use Split mode and run replay on a Linux/Windows daemon:
+#   rdc open /tmp/frame.rdc --listen 0.0.0.0:54321   # on replay host
+#   rdc open --connect host:54321 --token TOKEN       # on macOS client
 rdc doctor
 ```
 
@@ -82,8 +79,8 @@ pixi run setup-renderdoc
 | Platform | Local capture/replay | Split client |
 |----------|----------------------|--------------|
 | Linux | ✅ | ✅ |
-| macOS | ✅ (`pixi run setup-renderdoc`) | ✅ (no local RenderDoc needed) |
-| Windows *(experimental, not tested in this PR)* | ⚠️ expected | ⚠️ expected |
+| macOS | ❌ (not supported yet) | ✅ (recommended) |
+| Windows (experimental) | ⚠️ expected | ⚠️ expected |
 
 ### RenderDoc bootstrap (all platforms)
 

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/docs/usage.md

@@ -10,9 +10,17 @@ rdc open capture.rdc     # start a session (launches daemon)
 rdc draws                # list draw calls
 rdc pipeline 142         # inspect pipeline state at EID 142
 rdc shader 142 ps        # view pixel shader disassembly
+rdc shader ps            # view PS at current EID (after goto)
 rdc close                # end session (stops daemon)
 ```
 
+Render pass lookup accepts either a pass name or a 0-based pass index:
+
+```bash
+rdc pass 0               # first pass
+rdc pass GBuffer         # pass by name
+```
+
 ## Named sessions
 
 Run multiple sessions in parallel with `--session`:

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/docs-astro/src/layouts/Docs.astro

@@ -15,7 +15,6 @@ const currentPath = Astro.url.pathname.replace(/\/$/, '');
 const sidebar = [
   { label: 'Overview', href: `${base}docs/` },
   { label: 'Installation', href: `${base}docs/install/` },
-  { label: 'Windows Install', href: `${base}docs/install/windows/` },
   { label: 'Usage Patterns', href: `${base}docs/usage/` },
   { label: 'Commands', href: `${base}docs/commands/` },
   { label: 'Remote & Split', href: `${base}docs/remote/` },

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/docs-astro/src/pages/docs/install.astro

@@ -44,8 +44,8 @@ pixi run setup-renderdoc</code></pre>
       </tr>
       <tr>
         <td>macOS</td>
-        <td>Supported (<code>pixi run setup-renderdoc</code>)</td>
-        <td>Supported (no local RenderDoc needed)</td>
+        <td>Not supported yet</td>
+        <td>Supported (recommended)</td>
       </tr>
       <tr>
         <td>Windows (experimental)</td>
@@ -55,6 +55,24 @@ pixi run setup-renderdoc</code></pre>
     </tbody>
   </table>
 
+  <h2>macOS Split Mode</h2>
+  <p>
+    Local replay on macOS is not supported right now. Use macOS as a Split
+    client and run replay on a Linux/Windows daemon.
+  </p>
+  <pre><code># On Linux/Windows replay host
+rdc open /tmp/frame.rdc --listen 0.0.0.0:54321
+
+# On macOS client
+rdc open --connect host:54321 --token TOKEN</code></pre>
+
+  <h2>Windows Notes</h2>
+  <ul>
+    <li>Windows 10/11 64-bit</li>
+    <li>Python minor version must match renderdoc <code>.pyd</code></li>
+    <li>Visual Studio 2022 Build Tools with C++ workload</li>
+  </ul>
+
   <h2>RenderDoc Python Module</h2>
   <p>
     <code>rdc</code> requires the renderdoc Python module

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/docs-astro/tests/validate.mjs

@@ -134,8 +134,9 @@ console.log('\n\x1b[1mContent\x1b[0m');
 
 const indexHtml = readFileSync(join(DIST, 'index.html'), 'utf-8');
 
-test('landing page has typed.js script', () => {
-  assert(indexHtml.includes('typed-output'), 'Missing typed.js #typed-output element');
+test('landing page has terminal replay elements', () => {
+  assert(indexHtml.includes('replay-terminal'), 'Missing #replay-terminal element');
+  assert(indexHtml.includes('replay-lines'), 'Missing #replay-lines element');
 });
 
 test('landing page has GSAP ScrollTrigger bundle', () => {

rdc_cli-0.3.6/openspec/changes/2026-02-26-phase-r3-usability-fixes/proposal.md

@@ -0,0 +1,71 @@
+# Phase R3: Usability Fixes (B46-B51)
+
+## Motivation
+
+Manual CLI usage surfaced six high-friction bugs that break expected workflows,
+mainly around completion behavior, command argument ergonomics, and error
+messaging clarity. These issues reduce trust in basic interactive usage even
+when backend functionality is correct.
+
+This change focuses on predictable operator experience for the existing command
+surface, without introducing new feature scope.
+
+## Scope
+
+In scope:
+
+- B46: add capture-path completion for `rdc open`
+- B47: silence VFS completion errors when no active session/daemon
+- B48: support stage-only shader invocation after `goto`
+- B49: make `capture --list-apis` an explicit early-return mode
+- B50: report unreachable `remote list --url` as connection failure
+- B51: clarify 0-based index semantics for `pass`
+
+Out of scope:
+
+- Any new command beyond behavior fixes above
+- New completion features unrelated to B46/B47
+- Changes to replay/data query core semantics
+
+## Design
+
+### B46: `open` tab completion
+
+- Add capture-path completion for `rdc open` so `<TAB>` offers local `.rdc`
+  candidates from the filesystem.
+
+### B47: VFS completion with no session
+
+- Treat missing session / daemon-not-ready cases as completion-time no-result
+  conditions, not user-facing runtime errors.
+- Completion handlers return empty candidates on recoverable lookup failures.
+
+### B48: `shader` stage-only form after `goto`
+
+- Support `rdc shader <stage>` by resolving EID from session `current_eid`.
+- Preserve explicit form `rdc shader <eid> <stage>` with unchanged precedence.
+
+### B49: `capture --list-apis` execution path
+
+- Ensure `--list-apis` is handled as an early-return information mode.
+- Skip executable validation and injection-related flow when this flag is set.
+
+### B50: `remote list --url` unreachable endpoint
+
+- Separate transport/connectivity failures from valid-but-empty target lists.
+- Report unreachable endpoint as a connection error with actionable wording,
+  not "no targets found".
+
+### B51: pass index base clarity
+
+- Standardize user-facing wording to explicitly state pass indices are 0-based.
+- Align command help and docs text to remove ambiguity.
+
+## Risks
+
+- Completion-path changes may affect shell-specific completion adapters
+  (bash/zsh/fish) if output assumptions are inconsistent.
+- Mixed-form `shader` argument parsing can regress if dispatch order is not
+  strictly defined.
+- Refined `remote list` errors may require updates where tests assert exact
+  message strings.

rdc_cli-0.3.6/openspec/changes/2026-02-26-phase-r3-usability-fixes/tasks.md

@@ -0,0 +1,43 @@
+# Tasks
+
+## B46 - Add capture path completion for `rdc open`
+
+- [ ] Add a local filesystem completion helper for the `CAPTURE` argument in `src/rdc/commands/session.py`.
+- [ ] Wire the helper into `open_cmd` argument declaration so `rdc open <TAB>` suggests valid paths.
+- [ ] Filter completion output to directories and `.rdc` files, preserving shell-friendly path formatting.
+
+## B47 - Make VFS completion silent without a session
+
+- [ ] Harden `_complete_vfs_path` in `src/rdc/commands/vfs.py` to return empty completions on session/RPC failures.
+- [ ] Catch non-happy-path completion errors without surfacing runtime traces during TAB completion.
+- [ ] Keep normal command execution errors unchanged; scope behavior change to completion-only flow.
+
+## B48 - Support stage-only shader query after `goto`
+
+- [ ] Update `shader` argument parsing in `src/rdc/commands/pipeline.py` to accept stage-only invocation (`rdc shader ps`).
+- [ ] Resolve missing EID from session current event state before dispatching shader requests.
+- [ ] Keep explicit form (`rdc shader <eid> <stage>`) behavior intact for all existing flags and outputs.
+
+## B49 - Ensure `capture --list-apis` exits before capture flow
+
+- [ ] Verify/adjust command flow in `src/rdc/commands/capture.py` so `--list-apis` short-circuits before executable validation.
+- [ ] Ensure list mode does not enter split/local injection paths and does not require `-- EXECUTABLE` arguments.
+- [ ] Keep output contract for API listing stable in text and JSON modes.
+
+## B50 - Fix unreachable remote list error reporting
+
+- [ ] Update `src/rdc/commands/remote.py` to surface connection failures as explicit errors for `remote list --url ...`.
+- [ ] Restrict `no targets found` output to successful empty responses only.
+- [ ] Align split-mode and local-mode failure handling so both return actionable connection errors.
+
+## B51 - Clarify `pass` index base in help/docs
+
+- [ ] Update `pass` command help/docstring in `src/rdc/commands/resources.py` to state that numeric index is 0-based.
+- [ ] Update user-facing docs that reference pass lookup (for example `docs/usage.md` and `docs/index.md`) with 0-based wording.
+- [ ] Keep naming lookup behavior unchanged while clarifying index semantics in CLI help text.
+
+## Final validation
+
+- [ ] Run `pixi run lint`.
+- [ ] Run `pixi run test`.
+- [ ] Execute manual verification steps from `test-plan.md` on a real capture/daemon session.

rdc_cli-0.3.6/openspec/changes/2026-02-26-phase-r3-usability-fixes/test-plan.md

@@ -0,0 +1,190 @@
+# Test Plan: Phase R3 Usability Fixes (B46-B51)
+
+## Scope and Validation Strategy
+
+This plan covers behavioral regressions and expected UX semantics for:
+
+- B46: open path completion
+- B47: completion silence on no-session for VFS
+- B48: shader stage-only invocation after goto
+- B49: `capture --list-apis` behavior
+- B50: remote list unreachable error semantics
+- B51: pass help/docs index clarity
+
+Validation is split into:
+
+- unit tests (command-level and helper-level behavior)
+- CLI regression tests (stdout/stderr, exit code, and argument handling)
+- shell completion checks (bash/zsh/fish)
+- manual verification on a real capture workflow
+
+---
+
+## B46: `open` Path Completion
+
+### Unit tests to add/update
+
+- Add completion tests for `open` that validate path suggestions are produced for valid local paths.
+- Add tests that completion output is filtered by typed prefix and does not emit unrelated paths.
+- Add tests that directory candidates include the shell-appropriate trailing separator when required by completion framework.
+
+### CLI regression cases
+
+- `rdc open <TAB>` at repo root returns path candidates, no stack traces.
+- `rdc open tests/<TAB>` returns entries under `tests/` only.
+- Completing a non-existent prefix returns no candidates and no error text.
+
+### Shell completion matrix
+
+- **bash**: verify candidate emission format used by bash completion script.
+- **zsh**: verify candidate list is shown and remains prefix-filtered.
+- **fish**: verify completion descriptions (if present) do not break candidate parsing.
+
+### Acceptance criteria
+
+- Completion for `open` returns deterministic, prefix-filtered path candidates across bash/zsh/fish.
+- No stderr noise for normal completion flow.
+- Exit code `0` for completion invocation paths.
+
+---
+
+## B47: Completion Silence on No Session for VFS
+
+### Unit tests to add/update
+
+- Add tests for VFS-backed completion when no active session exists: completion returns empty results.
+- Add tests that no user-facing error message is emitted during completion when session is absent.
+- Add tests that unexpected internal exceptions still map to controlled completion behavior (no traceback output).
+
+### CLI regression cases
+
+- Invoke VFS completion on a fresh environment (no prior `open`/session): no candidates, no error text.
+- Re-run after opening a session: completion returns VFS candidates normally.
+
+### Shell completion matrix
+
+- **bash/zsh/fish**: same expected silent-empty behavior with no-session state.
+
+### Acceptance criteria
+
+- No-session completion path is silent (no stderr/stdout diagnostics) and returns zero candidates.
+- Completion invocation exits with code `0`.
+- Behavior is consistent across bash, zsh, and fish.
+
+---
+
+## B48: Shader Stage-Only Invocation After `goto`
+
+### Unit tests to add/update
+
+- Add tests for shader-related command invocation that provide only stage argument after `goto` selected event/context.
+- Add tests that stage-only invocation resolves against current event/pipeline context.
+- Add negative test: without required context (no event/session), command fails with clear usage/error semantics.
+
+### CLI regression cases
+
+- `rdc goto <event>` then shader command with stage only (e.g., `vs`/`ps`) succeeds and prints expected section header/output fragment.
+- Same stage-only invocation before `goto` fails with expected error message and non-zero exit.
+
+### Acceptance criteria
+
+- After valid `goto`, stage-only shader invocation succeeds with exit code `0`.
+- Without required context, command fails with stable, user-facing error and exit code `!= 0`.
+- No ambiguous argument parsing regressions introduced for existing full-form shader invocation.
+
+---
+
+## B49: `capture --list-apis` Behavior
+
+### Unit tests to add/update
+
+- Add tests that `capture --list-apis` returns supported API list without requiring capture target arguments.
+- Add tests that list output format is stable (one API per line or documented canonical format).
+- Add tests that `capture --list-apis --json` returns valid JSON and still bypasses executable validation.
+- Add tests that incompatible flag combinations produce deterministic error messaging.
+
+### CLI regression cases
+
+- `rdc capture --list-apis` prints API list and exits successfully.
+- `rdc capture --list-apis --json` prints valid JSON and exits successfully.
+- `rdc capture --list-apis` in environments with no active capture target still succeeds.
+- Invalid combo case returns non-zero exit and concise usage/error output.
+
+### Acceptance criteria
+
+- `capture --list-apis` is self-contained and exits `0` on success.
+- Output contains expected known API names (at least one canonical API token expected by docs).
+- `capture --list-apis --json` returns parseable JSON and exits `0`.
+- Invalid flag combinations exit `!= 0` with explicit error text.
+
+---
+
+## B50: `remote list` Unreachable Error Semantics
+
+### Unit tests to add/update
+
+- Add tests for network-unreachable daemon/host: command returns user-friendly connectivity error.
+- Add tests that unreachable errors are classified distinctly from empty remote list success cases.
+- Add tests that timeout/refused variants map to consistent exit code and message category.
+
+### CLI regression cases
+
+- `rdc remote list --url <unreachable-host:port>` returns non-zero exit and clear "unreachable/connection" wording.
+- `rdc remote list --url <reachable-host:port>` with no remotes returns success with empty-state output.
+
+### Acceptance criteria
+
+- Unreachable endpoint: exit code `!= 0`, no misleading empty-list success message.
+- Reachable but empty: exit code `0` with explicit empty-state output.
+- Error wording is actionable (indicates connectivity problem rather than data absence).
+
+---
+
+## B51: `pass` Help / Docs Index Clarity
+
+### Unit tests to add/update
+
+- Add tests for `rdc pass --help` content to ensure key usage lines and terminology are unambiguous.
+- Add tests for docs/help text references to explicitly state numeric pass indices are 0-based.
+- Add snapshot-style assertion for critical help fragment (`0-based`) to prevent wording regression.
+
+### CLI regression cases
+
+- `rdc pass --help` includes concise description and explicit `0-based` index wording.
+- Docs pages that mention `pass <index|name>` include explicit 0-based wording.
+
+### Acceptance criteria
+
+- Help output for `pass` is discoverable and clear for first-time users.
+- `pass` help/docs explicitly state index base (`0-based`).
+- Help commands exit with code `0` and do not emit stderr noise in normal flow.
+
+---
+
+## Cross-Cutting Manual Verification (Real Capture Workflow)
+
+Run on a real capture file and live daemon/session setup.
+
+```bash
+pixi run rdc open <real-capture.rdc>
+pixi run rdc goto <valid-event-id>
+pixi run rdc shader <stage-only>
+pixi run rdc capture --list-apis
+pixi run rdc capture --list-apis --json
+pixi run rdc remote list --url <reachable-host:port>
+pixi run rdc remote list --url <unreachable-host:port>
+pixi run rdc pass --help
+```
+
+Manual checks:
+
+- completion behavior for `open` and VFS paths under bash/zsh/fish
+- stage-only shader behavior before and after `goto`
+- clear distinction between unreachable remote errors and empty successful lists
+- help/docs wording clarity for `pass`
+
+Expected outcomes:
+
+- success paths return exit code `0`
+- connectivity/invalid-context failures return exit code `!= 0`
+- stderr is only used for true error conditions

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/pixi.toml

@@ -46,3 +46,7 @@ gen-commands = "bash -c 'uv run python scripts/gen-commands.py > docs-astro/src/
 check-commands = "bash -c 'diff <(uv run python scripts/gen-commands.py) docs-astro/src/data/commands.json'"
 verify = "bash scripts/verify-package.sh"
 e2e = "bash scripts/e2e-test.sh"
+docs-install = "npm --prefix docs-astro ci"
+docs-build = "npm --prefix docs-astro run build"
+docs-test = "npm --prefix docs-astro test"
+docs-dev = "npm --prefix docs-astro run dev"

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/scripts/e2e-test.sh

@@ -15,6 +15,8 @@ FAIL=0
 CAPTURE="tests/fixtures/hello_triangle.rdc"
 TMP_CAPTURE_BASE=""
 RDC="uv run rdc"
+OS_NAME=$(uname -s)
+REPLAY_READY=0
 
 if [ ! -f "$CAPTURE" ]; then
   echo -e "${RED}error: fixture not found: $CAPTURE${NC}"
@@ -22,7 +24,7 @@ if [ ! -f "$CAPTURE" ]; then
   exit 1
 fi
 
-if [ ! -f ".local/renderdoc/renderdoc.so" ]; then
+if [ ! -f ".local/renderdoc/renderdoc.so" ] && [ "$OS_NAME" != "Darwin" ]; then
   echo -e "${RED}error: renderdoc.so not found${NC}"
   echo "Run: pixi run setup-renderdoc"
   exit 1
@@ -90,7 +92,17 @@ check "rdc --help" $RDC --help
 # --- Doctor ---
 echo ""
 echo "=== Layer 1: Doctor ==="
-check "rdc doctor" $RDC doctor
+DOCTOR_OUTPUT=$($RDC doctor 2>&1 || true)
+if echo "$DOCTOR_OUTPUT" | grep -q "replay-support: renderdoc replay API surface found"; then
+  REPLAY_READY=1
+fi
+if echo "$DOCTOR_OUTPUT" | grep -q "replay-support:"; then
+  echo -e "  ${GREEN}✓${NC} rdc doctor"
+  PASS=$((PASS + 1))
+else
+  echo -e "  ${RED}✗${NC} rdc doctor"
+  FAIL=$((FAIL + 1))
+fi
 
 # --- Session lifecycle ---
 echo ""
@@ -102,13 +114,19 @@ check_output "rdc status" "capture:" $RDC status
 # --- Read-only queries ---
 echo ""
 echo "=== Layer 3: Read-only queries ==="
-check_nonzero "rdc info" $RDC info
-check_nonzero "rdc stats" $RDC stats
-check_nonzero "rdc events" $RDC events
-check_nonzero "rdc draws" $RDC draws
-check_nonzero "rdc passes" $RDC passes
-check_nonzero "rdc resources" $RDC resources
-check_nonzero "rdc shaders" $RDC shaders
+if [ "$REPLAY_READY" -eq 1 ]; then
+  check_nonzero "rdc info" $RDC info
+  check_nonzero "rdc stats" $RDC stats
+  check_nonzero "rdc events" $RDC events
+  check_nonzero "rdc draws" $RDC draws
+  check_nonzero "rdc passes" $RDC passes
+  check_nonzero "rdc resources" $RDC resources
+  check_nonzero "rdc shaders" $RDC shaders
+else
+  check_output "rdc info (no replay)" "no replay loaded" $RDC info
+  check_output "rdc stats (no replay)" "no replay loaded" $RDC stats
+  check_output "rdc draws (no replay)" "no replay loaded" $RDC draws
+fi
 
 # --- VFS ---
 echo ""
@@ -116,19 +134,31 @@ echo "=== Layer 4: VFS ==="
 check_nonzero "rdc ls /" $RDC ls /
 check_nonzero "rdc ls /draws" $RDC ls /draws
 check_nonzero "rdc tree / --depth 1" $RDC tree / --depth 1
-check_nonzero "rdc cat /info" $RDC cat /info
-check_nonzero "rdc cat /stats" $RDC cat /stats
+if [ "$REPLAY_READY" -eq 1 ]; then
+  check_nonzero "rdc cat /info" $RDC cat /info
+  check_nonzero "rdc cat /stats" $RDC cat /stats
+else
+  check_output "rdc cat /info (no replay)" "no replay loaded" $RDC cat /info
+  check_output "rdc cat /stats (no replay)" "no replay loaded" $RDC cat /stats
+fi
 
 # --- VFS completion ---
 echo ""
 echo "=== Layer 5: VFS completion ==="
 check_nonzero "complete /" $RDC _complete /
 check_nonzero "complete /d" $RDC _complete /d
-check_output "complete /d → /draws/" "/draws/" $RDC _complete /d
+if [ "$REPLAY_READY" -eq 1 ]; then
+  check_output "complete /d → /draws/" "/draws/" $RDC _complete /d
+else
+  check_output "complete /d (no replay)" "no replay loaded" $RDC _complete /d
+fi
 COMP_OUTPUT=$(env _RDC_COMPLETE=bash_complete COMP_WORDS="rdc ls /d" COMP_CWORD=2 $RDC 2>&1 || true)
-if echo "$COMP_OUTPUT" | grep -q "/draws/"; then
+if [ "$REPLAY_READY" -eq 1 ] && echo "$COMP_OUTPUT" | grep -q "/draws/"; then
   echo -e "  ${GREEN}✓${NC} click shell_complete /d → /draws/"
   PASS=$((PASS + 1))
+elif [ "$REPLAY_READY" -eq 0 ] && echo "$COMP_OUTPUT" | grep -q "no replay loaded"; then
+  echo -e "  ${GREEN}✓${NC} click shell_complete /d (no replay)"
+  PASS=$((PASS + 1))
 else
   echo -e "  ${RED}✗${NC} click shell_complete /d (got '$COMP_OUTPUT')"
   FAIL=$((FAIL + 1))

{rdc_cli-0.3.5 → rdc_cli-0.3.6}/src/rdc/_skills/references/commands-quick-ref.md

@@ -570,7 +570,7 @@ Create local default session and start daemon skeleton.
 
 ## `rdc pass`
 
-Show detail for a single render pass by index or name.
+Show detail for a single render pass by 0-based index or name.
 
 **Arguments:**
 
@@ -849,8 +849,8 @@ Show shader metadata for a stage at EID.
 
 | Name | Type | Required |
 |------|------|----------|
-| `eid` | integer | no |
-| `stage` | choice | no |
+| `first` | text | no |
+| `second` | text | no |
 
 **Options:**