docs(tmux-parity[plugin]): use console fences with $ prefix per AGENTS.md

why: AGENTS.md "Shell Command Formatting" requires command examples
in docs to use ```console with a "$ " prefix (not ```bash) and to
keep one command per code block so the prompt is unambiguous and
copy-pastable. The plugin docs added in this branch had multi-command
```bash blocks scattered across .claude/commands and
skills/tmux-parity references.

what:
- .claude/agents/parity-analyzer.md: 3 blocks → console+$.
- .claude/commands/version-diff.md: 2 blocks → console+$.
- .claude/commands/implement-command.md: split the 6-command
  verification block into 6 console+$ blocks.
- skills/tmux-parity/references/tmux-command-table.md: 2 blocks →
  console+$ (one of which had two ls invocations — split per
  AGENTS.md "one command per block").

Author: tony

.claude/agents/parity-analyzer.md

@@ -52,22 +52,27 @@ You are a tmux/libtmux feature parity analysis specialist. Analyze the gap betwe
 ### Step 1: Extract tmux commands
 
 Run the extraction script for current data:
-```bash
-bash .claude-plugin/scripts/extract-tmux-commands.sh ~/study/c/tmux
+
+```console
+$ bash .claude-plugin/scripts/extract-tmux-commands.sh ~/study/c/tmux
 ```
-This outputs `command|alias|getopt|target` for all ~88 tmux commands.
+
+This outputs `command|alias|getopt|target` for every tmux command.
 
 ### Step 2: Extract libtmux coverage
 
 Run the libtmux extraction:
-```bash
-bash .claude-plugin/scripts/extract-libtmux-methods.sh
+
+```console
+$ bash .claude-plugin/scripts/extract-libtmux-methods.sh
 ```
+
 This outputs the unique tmux command strings that libtmux invokes.
 
 Additionally, check mixin files for commands invoked via `tmux_cmd()`:
-```bash
-grep -rn '"set-environment"\|"show-environment"\|"set-hook"\|"set-option"\|"show-option"\|"capture-pane"\|"move-window"\|"select-layout"\|"kill-pane"' src/libtmux/*.py | grep -oP '"([a-z]+-[a-z-]+)"' | sort -u | tr -d '"'
+
+```console
+$ grep -rn '"set-environment"\|"show-environment"\|"set-hook"\|"set-option"\|"show-option"\|"capture-pane"\|"move-window"\|"select-layout"\|"kill-pane"' src/libtmux/*.py | grep -oP '"([a-z]+-[a-z-]+)"' | sort -u | tr -d '"'
 ```
 
 ### Step 3: Cross-reference

.claude/commands/implement-command.md

@@ -104,24 +104,28 @@ Add tests in `tests/test_{class}.py` (or a new file if warranted):
 
 Run the full verification workflow:
 
-```bash
-# Format
-uv run ruff format .
+```console
+$ uv run ruff format .
+```
 
-# Lint
-uv run ruff check . --fix --show-fixes
+```console
+$ uv run ruff check . --fix --show-fixes
+```
 
-# Type check
-uv run mypy src tests
+```console
+$ uv run mypy src tests
+```
 
-# Test the specific file
-uv run pytest tests/test_{class}.py -x -v
+```console
+$ uv run pytest tests/test_{class}.py -x -v
+```
 
-# Run doctests
-uv run pytest --doctest-modules src/libtmux/{class}.py -v
+```console
+$ uv run pytest --doctest-modules src/libtmux/{class}.py -v
+```
 
-# Full test suite
-uv run pytest
+```console
+$ uv run pytest
 ```
 
 All must pass before considering the implementation complete.

.claude/commands/version-diff.md

@@ -17,16 +17,19 @@ Compare tmux features between two versions using the source worktrees at `~/stud
 Extract `version1`, `version2`, and optional `command-name` from `$ARGUMENTS`.
 
 If no arguments provided, list available versions:
-```bash
-ls -d ~/study/c/tmux-*/ | sed 's|.*/tmux-||;s|/$||' | sort -V
+
+```console
+$ ls -d ~/study/c/tmux-*/ | sed 's|.*/tmux-||;s|/$||' | sort -V
 ```
+
 Then ask the user which two versions to compare.
 
 ## Validate Worktrees
 
 Verify both worktrees exist:
-```bash
-ls -d ~/study/c/tmux-{version1}/ ~/study/c/tmux-{version2}/ 2>/dev/null
+
+```console
+$ ls -d ~/study/c/tmux-{version1}/ ~/study/c/tmux-{version2}/ 2>/dev/null
 ```
 
 ## Single Command Comparison (when command-name given)

skills/tmux-parity/references/tmux-command-table.md

@@ -89,13 +89,18 @@ Compare against libtmux: `src/libtmux/formats.py`
 - 2.0 through 2.9, 2.9a
 - 3.0, 3.0a, 3.1 through 3.1c, 3.2, 3.2a, 3.3, 3.3a, 3.4, 3.5, 3.5a, 3.6, 3.6a
 
-To check if a command exists in a version:
-```bash
-ls ~/study/c/tmux-3.0/cmd-display-popup.c 2>/dev/null  # Not found = added later
-ls ~/study/c/tmux-3.3/cmd-display-popup.c 2>/dev/null  # Found = exists in 3.3
+To check if a command exists in a version (not-found = added later):
+
+```console
+$ ls ~/study/c/tmux-3.0/cmd-display-popup.c 2>/dev/null
+```
+
+```console
+$ ls ~/study/c/tmux-3.3/cmd-display-popup.c 2>/dev/null
 ```
 
 To diff a command across versions:
-```bash
-diff ~/study/c/tmux-3.0/cmd-send-keys.c ~/study/c/tmux-3.6a/cmd-send-keys.c
+
+```console
+$ diff ~/study/c/tmux-3.0/cmd-send-keys.c ~/study/c/tmux-3.6a/cmd-send-keys.c
 ```