manage-skills

1## Before doing anything
2 
31. **Resolve the CLI first, then use the path it prints.** Run this once (POSIX
4   shell):
5 
6   ```bash
7   D="$HOME/.skills-manager/bin"
8   B="$D/skills-manager-cli"; [ -e "$B" ] || B="$B.exe"   # .exe on Windows
9   if [ -s "$D/.version" ] && [ -x "$B" ]; then
10     echo "$B"
11   elif [ -s "$D/.version" ] || [ -e "$B" ]; then
12     echo BRIDGE_BROKEN
13   else
14     P="$(command -v skills-manager-cli 2>/dev/null || true)"
15     [ -x "$P" ] && echo "$P"
16   fi
17   ```
18 
19   **Substitute the printed path into every command below**, wherever the
20   examples write `$SM`. Do not carry `$SM` as a shell variable: each command
21   you run is a new shell, so an assignment made here is gone by the next one.
22 
23   The three outcomes:
24 
25   - **A path under `~/.skills-manager/bin`** — the desktop app published this
26     copy, and the `.version` stamp appears only after it has been verified, so
27     it always matches the app the user is running. Use it.
28   - **`BRIDGE_BROKEN`** — something the app left behind is here but does not
29     add up: an unstamped binary, or a stamp with no binary beside it. Either is
30     what a copy that failed half-way leaves. **Stop.** Do not go looking
31     for another CLI: that binary may predate a safety fix, and the machine has
32     a desktop app whose version nothing here can match. Ask the user to open
33     the Skills Manager app once, which republishes it.
34   - **A path from PATH** — nothing was ever published here, so there is no
35…