docs: harness registration in README, install and hosts (document-release audit)

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

docs/hosts.md

@@ -18,7 +18,8 @@ registers with the harness it runs inside: OpenClaw (its exec tool sets
 `OPENCLAW_SHELL=exec`), Hermes (`HERMES_AGENT=true`) or a Dot (`HOME=/home/dot`
 on a Dot's computer), or a harness found among setup's parent processes. It
 prints every path it wrote and the command that removes them. An explicit
-`--host claude` (or any other host) never writes under a harness folder.
+`--host claude` (or any other host) never writes under a harness folder, and
+neither does `./setup --local`.
 `./setup --no-harness-auto` or `GSTACK_HARNESS_AUTO=0` turns the automatic step off.
 
 **What it writes.** Copies in the harness's own skills folder, never edits to

docs/install.md

@@ -2,7 +2,7 @@
 
 The README covers the two-step install. This page holds the details: what
 setup needs and how long it takes, the team-mode hook, the hooks setup
-registers in Claude Code, and how to remove gstack.
+registers in Claude Code, agent harness registration, and how to remove gstack.
 
 ## How long setup takes
 
@@ -51,9 +51,9 @@ writing a backup beside the file) only when it changed something.
 
 Run inside OpenClaw, Hermes or a Dot, `./setup` also registers gstack's skills
 with that harness, in the harness's own skills folder, and prints every path
-it wrote. It never does this when `--host` names another host. Turn it off
-with `./setup --no-harness-auto` or `GSTACK_HARNESS_AUTO=0`. Per-harness
-details, QM and any other harness: [hosts.md](hosts.md#agent-harnesses).
+it wrote. It never does this when `--host` names another host or with
+`--local`. Turn it off with `./setup --no-harness-auto` or
+`GSTACK_HARNESS_AUTO=0`. Per-harness details, QM and any other harness: [hosts.md](hosts.md#agent-harnesses).
 
 ## Uninstall