fix(.claude/skills): add --instance parameter to scenario run examples

Ensures consistency with other otdf-local commands (up, down, status, logs)
that already show the --instance parameter. While scenario run has a default
that reads from the YAML, explicitly including --instance makes examples
self-documenting and prevents confusion.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: dmihalcik-virtru

.claude/skills/scenario-matrix/SKILL.md

@@ -78,7 +78,7 @@ Bail (delete the just-written files) if any cell fails validation — partial ma
     uv run otdf-sdk-mgr install scenario "$f"
     uv run otdf-local instance init "$name" --from-scenario "$f"
     uv run otdf-local --instance "$name" up
-    uv run otdf-local scenario run "$f"
+    uv run otdf-local scenario run --instance "$name" "$f"
     uv run otdf-local --instance "$name" down
   done
   ```

.claude/skills/scenario-run/SKILL.md

@@ -18,7 +18,7 @@ Invoke the pytest selection declared by the scenario's `suite` block against the
 ### Step 1 — Invoke the runner
 
 ```bash
-uv run otdf-local scenario run xtest/scenarios/<id>.yaml
+uv run otdf-local scenario run --instance <id> xtest/scenarios/<id>.yaml
 ```
 
 This translates the scenario's `suite.targets` (list — each entry becomes a positional pytest arg), `suite.containers` (list — joined into a single whitespace-separated `--containers` value), `suite.kexpr`, `suite.markers`, and `sdks.{encrypt,decrypt}` into the equivalent `pytest <targets…> --sdks-encrypt … --sdks-decrypt … --containers …` invocation under `xtest/` with `OTDF_LOCAL_INSTANCE_NAME` set. SDK tokens are emitted in xtest's `sdk@version` form; the resolved version names come from the sibling `<scenario>.installed.json`.