ai(claude[plugin]): move agents/commands/skills to project root for auto-discovery

why: Claude Code auto-discovers plugin components at the project root,
not inside .claude-plugin/. Agent wasn't showing up because it was
nested under .claude-plugin/agents/.
what:
- Move agents/, commands/, skills/ to project root
- Keep scripts/ in .claude-plugin/ (not auto-discovered)
- Remove custom path overrides from plugin.json
- Update cross-references between components

Author: tony

.claude-plugin/plugin.json

@@ -7,8 +7,5 @@
   },
   "repository": "https://github.com/tmux-python/libtmux",
   "license": "MIT",
-  "keywords": ["tmux", "parity", "analysis", "code-generation"],
-  "commands": "./.claude-plugin/commands",
-  "agents": "./.claude-plugin/agents",
-  "skills": "./.claude-plugin/skills"
+  "keywords": ["tmux", "parity", "analysis", "code-generation"]
 }

.claude-plugin/agents/parity-analyzer.md agents/parity-analyzer.md.claude-plugin/agents/parity-analyzer.md renamed to agents/parity-analyzer.md

@@ -129,4 +129,4 @@ Output a structured report:
 
 ## Reference Data
 
-The baseline command mapping is at `.claude-plugin/skills/tmux-parity/references/command-mapping.md`. Use this as a starting point, but always run the extraction scripts for the most current data.
+The baseline command mapping is at `skills/tmux-parity/references/command-mapping.md`. Use this as a starting point, but always run the extraction scripts for the most current data.

…ude-plugin/commands/implement-command.md commands/implement-command.md.claude-plugin/commands/implement-command.md renamed to commands/implement-command.md .claude-plugin/commands/implement-command.md renamed to commands/implement-command.md

@@ -18,7 +18,7 @@ Guide wrapping a tmux command in libtmux, following project coding standards fro
 
 Load the `tmux-parity` skill first for reference data and implementation patterns.
 
-If `$ARGUMENTS` is empty, ask the user which tmux command to wrap. Consult `.claude-plugin/skills/tmux-parity/references/command-mapping.md` for the "Not Wrapped" list to suggest candidates.
+If `$ARGUMENTS` is empty, ask the user which tmux command to wrap. Consult `skills/tmux-parity/references/command-mapping.md` for the "Not Wrapped" list to suggest candidates.
 
 ## Phase 1: Analyze the tmux Command
 
@@ -62,7 +62,7 @@ Search libtmux for a wrapped command with similar characteristics:
 - Similar flag pattern (boolean flags, value flags, creates objects, etc.)
 - Read that method as a template
 
-Consult `.claude-plugin/skills/tmux-parity/references/libtmux-patterns.md` for the five implementation patterns.
+Consult `skills/tmux-parity/references/libtmux-patterns.md` for the five implementation patterns.
 
 ## Phase 4: Design the Method Signature
 

.claude-plugin/commands/parity-audit.md commands/parity-audit.md.claude-plugin/commands/parity-audit.md renamed to commands/parity-audit.md

@@ -81,4 +81,4 @@ Load the `tmux-parity` skill first to access reference data and domain knowledge
    | Command | libtmux Method | Missing Flags |
    ```
 
-Consult `.claude-plugin/skills/tmux-parity/references/command-mapping.md` for the baseline mapping data. Run the extraction scripts for the most current data.
+Consult `skills/tmux-parity/references/command-mapping.md` for the baseline mapping data. Run the extraction scripts for the most current data.