fix: Use tmux -L default to ensure correct socket resolution

When Claude Code runs in a different context (container, namespace, etc),
tmux may resolve to a different socket than the user's terminal. Using
-L default explicitly targets the default socket name, fixing the issue
where Claude sees different tmux sessions than the user.

plugins/plugin-dev/skills/plugin-settings/SKILL.md

@@ -230,8 +230,8 @@ Read from hooks to coordinate agents:
 AGENT_NAME=$(echo "$FRONTMATTER" | grep '^agent_name:' | sed 's/agent_name: *//')
 COORDINATOR=$(echo "$FRONTMATTER" | grep '^coordinator_session:' | sed 's/coordinator_session: *//')
 
-# Send notification to coordinator
-tmux send-keys -t "$COORDINATOR" "Agent $AGENT_NAME completed task" Enter
+# Send notification to coordinator (use -L default to ensure correct socket)
+tmux -L default send-keys -t "$COORDINATOR" "Agent $AGENT_NAME completed task" Enter
 ```
 
 ### Pattern 3: Configuration-Driven Behavior

plugins/plugin-dev/skills/plugin-settings/references/real-world-examples.md

@@ -76,10 +76,10 @@ fi
 # Send notification to coordinator
 NOTIFICATION="🤖 Agent ${AGENT_NAME} (Task ${TASK_NUMBER}, PR #${PR_NUMBER}) is idle."
 
-if tmux has-session -t "$COORDINATOR_SESSION" 2>/dev/null; then
-  tmux send-keys -t "$COORDINATOR_SESSION" "$NOTIFICATION" Enter
+if tmux -L default has-session -t "$COORDINATOR_SESSION" 2>/dev/null; then
+  tmux -L default send-keys -t "$COORDINATOR_SESSION" "$NOTIFICATION" Enter
   sleep 0.5
-  tmux send-keys -t "$COORDINATOR_SESSION" Enter
+  tmux -L default send-keys -t "$COORDINATOR_SESSION" Enter
 fi
 
 exit 0