docs(worktrees): document all three id spellings and probe .name

The contract comment said "both are read" while the implementation accepts
three (.worktree_id, .worktreeId, .name). Name all three, and write down that
.name rests on one captured payload rather than a guaranteed contract — an
unrelated .name lands on the regex guard below and fails loudly, which is the
intended floor. Restore .base_path to the documented-but-unused field list
(dropped in the rewrite, not deliberately), and show a .name payload in the
SKILL.md verify probe so the fallback is discoverable without reading the
script.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jwc9FFroR3mTZ4hLiSkkX3

Author: thecodedrift

.agents/skills/worktrees-pnpm/SKILL.md

@@ -109,8 +109,15 @@ printf '{"hook_event_name":"WorktreeCreate","cwd":"%s","worktree_id":"probe"}' "
   | .agents/skills/worktrees-pnpm/scripts/worktree-create.sh
 # expect: <repo>/worktrees/probe on stdout, git chatter on stderr, exit 0
 
+# The id field is not stable across callers, so .worktreeId and .name are read
+# too — `.name` is what a background agent's payload actually carries.
+printf '{"hook_event_name":"WorktreeCreate","cwd":"%s","name":"probe-name"}' "$PWD" \
+  | .agents/skills/worktrees-pnpm/scripts/worktree-create.sh
+# expect: <repo>/worktrees/probe-name
+
 printf '{"hook_event_name":"WorktreeRemove","worktree_path":"%s"}' "$PWD/worktrees/probe" \
   | .agents/skills/worktrees-pnpm/scripts/worktree-remove.sh
+# ...and the same for worktrees/probe-name
 ```
 
 **2. Add the ignores** described in the next section. Skipping this is the single most common way

.agents/skills/worktrees-pnpm/scripts/worktree-create.sh

@@ -18,12 +18,17 @@
 # Layout: /path/to/<repo>  ->  /path/to/<repo>/worktrees/<worktree_id>
 #
 # Contract (docs: code.claude.com/docs/en/hooks):
-#   stdin  - JSON identifying the worktree, plus .cwd, .session_id, ...
+#   stdin  - JSON identifying the worktree, plus .base_path, .cwd, .session_id, ...
 #            The id field is NOT stable across callers: a background agent's
 #            payload carries `.name` (e.g. "agent-a5e1de46e730bdfd7") and no
-#            `.worktree_id` at all, so both are read. Accepting only one of them
+#            `.worktree_id` at all, so all three spellings are read
+#            (.worktree_id, .worktreeId, .name). Accepting only one of them
 #            fails worktree creation outright with a message that reads like the
-#            harness sent nothing.
+#            harness sent nothing. `.name` is the weakest of the three — it is
+#            justified by one captured payload, not a guaranteed contract — so a
+#            caller that sends an unrelated `.name` while genuinely lacking both
+#            id fields lands on the validation below and fails loudly, which is
+#            the intended floor rather than an accident.
 #   stdout - the absolute path of the created worktree, plain text, REQUIRED
 #   exit   - non-zero, or zero with empty stdout, fails worktree creation
 # This hook replaces the default logic entirely, so it must run `git worktree add`.