fix: move hooks and skills to root to avoid EXDEV error

Move hooks/ and skills/ directories from .claude-plugin/ to repository root
and update marketplace.json source field accordingly. This resolves cross-device
link errors on Linux systems where /tmp is on a separate filesystem.

Remove unnecessary README symlink from skill reference and update all
corresponding file paths in configuration and tests.

Author: max-sixty

.claude-plugin/CLAUDE.md

@@ -1,35 +1,28 @@
 # Claude Code Plugin Guidelines
 
-## Skills Directory Location
+## Plugin Structure
 
-**Working solution**: Using `source: "./.claude-plugin"` in `marketplace.json` allows skills to remain in `.claude-plugin/skills/` ✅
+This plugin uses `source: "./"` in `marketplace.json`, which means:
+- `marketplace.json` and `plugin.json` live in `.claude-plugin/`
+- `hooks/` and `skills/` directories are at the repository root
 
-Configuration in `marketplace.json`:
+Configuration in `.claude-plugin/marketplace.json`:
 ```json
 {
-  "source": "./.claude-plugin",
+  "source": "./",
   "skills": ["./skills/worktrunk"]
 }
 ```
 
-Configuration in `plugin.json`:
+Configuration in `.claude-plugin/plugin.json`:
 ```json
 {
   "hooks": "./hooks/hooks.json",
   "skills": ["./skills/worktrunk"]
 }
 ```
 
-**Path resolution**:
-- Source base: `./.claude-plugin`
-- Skills: `./.claude-plugin + ./skills/worktrunk = ./.claude-plugin/skills/worktrunk` ✅
-- Hooks: `./.claude-plugin + ./hooks/hooks.json = ./.claude-plugin/hooks/hooks.json` ✅
-
-This approach keeps all Claude Code components organized together in `.claude-plugin/` and avoids root directory clutter.
-
-**Note**: The official Claude Code documentation states "All other directories (commands/, agents/, skills/, hooks/) must be at the plugin root" but using the `source` field to point to `./.claude-plugin` makes paths relative to that directory, allowing this organizational structure.
-
-**Why this works**: The `source` field in `marketplace.json` changes the base directory for path resolution. When `source: "./"` (the default), skills paths are resolved from the plugin root. When `source: "./.claude-plugin"`, skills paths are resolved from `.claude-plugin/`, allowing the entire plugin to be self-contained in one directory.
+**Why this structure**: Using `source: "./.claude-plugin"` caused EXDEV (cross-device link) errors on Linux systems where `/tmp` is on a separate filesystem (Ubuntu 21.04+, Fedora, Arch). See https://github.com/anthropics/claude-code/issues/14799 for details. Once that upstream bug is fixed, we could consolidate back to `.claude-plugin/` if desired.
 
 ## Known Limitations
 

.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
     {
       "name": "worktrunk",
       "description": "Worktrunk is a git worktree management CLI that streamlines multi-branch development. This plugin provides Claude Code integration with two features: (1) A configuration skill guiding you through LLM-powered commit message generation, project automation hooks (post-create, pre-merge), and worktree path customization. (2) Automatic activity tracking that displays 🤖 (working) and 💬 (waiting) indicators in `wt list`, showing which branches have active Claude sessions. Use when setting up Worktrunk configuration, automating project workflows, or monitoring AI activity across branches.",
-      "source": "./.claude-plugin",
+      "source": "./",
       "strict": false,
       "skills": [
         "./skills/worktrunk"

.claude-plugin/skills/worktrunk/reference/README.md

@@ -20,7 +20,7 @@ allow-branch = ["*"]
 consolidate-commits = true
 pre-release-replacements = [
     # Update skill version marker
-    { file = ".claude-plugin/skills/worktrunk/SKILL.md", search = "worktrunk-skill-version: [0-9.]+", replace = "worktrunk-skill-version: {{version}}" },
+    { file = "skills/worktrunk/SKILL.md", search = "worktrunk-skill-version: [0-9.]+", replace = "worktrunk-skill-version: {{version}}" },
 ]
 
 [package.metadata.cargo-udeps.ignore]