docs(coord-send): correct a false claim the fallback fix shipped with

v0.12.1's fix removed the ~/.claude/scripts fallback but its own commentary
still asserted the deployed copy was "real and intentional (the operator's
own terminal aliases point at it)". Checked directly with the operator:
they invoke coord-send and board only through their Skill front doors, never
a personal terminal alias. board.sh and route.sh never had a deployed copy
at all -- only the five coord-*.sh scripts did, and their one measured
effect was as an accidental fallback target for Claude sessions' own Bash
tool calls, the exact bug 0.12.1 fixed. With no owner and no remaining
function, the five files under ~/.claude/scripts/ have been deleted.

No behavior change -- coord-selftest.sh still 159/159.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YJMJanRHkUhEf9EYxMpbM5
This commit is contained in:
Kjell Tore Guttormsen 2026-07-31 18:41:34 +02:00
commit 6ffe089b68
2 changed files with 17 additions and 9 deletions

View file

@ -42,12 +42,14 @@ Coordination content is also private: it never belongs on a public surface.
There is no deployed copy anywhere else and no fallback path. A Bash tool call
never has `CLAUDE_PLUGIN_ROOT` set as a real shell variable — only this
skill's own rendering resolves the token — so a `${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}`
fallback silently wins every time the line above is actually executed,
routing through whatever the operator's personal `~/.claude/scripts/` copy
happens to be instead of the plugin's own bundled script. That copy is real
and intentional (the operator's own terminal aliases point at it) but it is
updated on its own schedule, so it can be stale. If this fails to resolve,
the fix is this expression — never a restored fallback.
fallback silently won every time the line above was actually executed,
routing through whatever happened to sit at `~/.claude/scripts/coord-send.sh`
instead of the plugin's own bundled script. That path was never a legitimate
parallel deployment — the operator invokes this skill only through its
natural-language front door, never a personal terminal alias — so the file
that sat there was a pure accident target with no owner keeping it current.
It has been deleted. If this fails to resolve, the fix is this expression —
never a restored fallback.
Interface (body comes from a quoted heredoc so nothing in it is shell-expanded):