Release 1.0.1

[MongLong0214]

Five fixes have been on main since v1.0.0 and none has reached anyone.

#683  the release workflow failing on a release that already exists
#684  hermes install refusing the config it wrote
#687  the skills root taken from the running bundle instead of --data-root
#688  an installed plugin treated as a reason to stop rather than upgrade
#690  claude-code wired by nothing, in neither hosts nor notDetected

All five are defects at the install and distribution boundary, and that boundary
has exactly one delivery mechanism.

Measured, not assumed

Re-installing with main's install.sh still left the plugin cache at 0.8.0
and claude-code out of both lists. The enumeration #690 fixed is compiled into
the binary being installed, and that binary is v1.0.0. Same for #684 and #687:
verified working from main's dist, still refused by the installed wrapper.

The bump

Thirty-eight pins across nine files. dist is unchanged and the canonical
digest is identical — c312755d. The version is read from package.json at
runtime rather than compiled in, so a bump moves no bytes; rebuilt through the
canonical builder and verified rather than assumed, as with v1.0.0.

The installers and READMEs carry the tag in URLs that resolve only once the tag
exists, so this is one commit and the tag goes on it.

First release under §6c

docs/RELEASE-GATE.md §6c asks for an upgrade over the previous version
rather than a fresh install, and a fresh host process that actually lists the
tools. The five fixes above are why that section exists — every one of them was
invisible to a suite that starts from nothing.

After publishing, the measurements that close #660:

install → does claude-code appear in hosts
        → does the plugin cache move to 1.0.1
        → does doctor's unusable count fall
        → does hermes report healthy

Each is a control for something measured today at v1.0.0.

Not in this release

#691 — install.sh carries seven has_/wire_ host pairs nothing calls, ~140
lines. A deletion that size does not belong immediately before a release.

[github-actions]

CommitLore — record lint

Trailers: clean — 1 commit in origin/main..366158052cf1143f4410c5410af6267de633fd8c
Active constraints: not read — commitlore: git log --follow accepts exactly one pathspec, so renames are not followed for 11 paths; query one path at a time to follow its rename chain (11 changed paths)

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}