docs: disclose the update check fully and list every setup hook

The README privacy summary now names both GitHub requests the update check
makes and the version/OS report it adds with telemetry on, as the full text
it replaced did. docs/install.md's hooks section lists the team-mode
SessionStart hook and the AskUserQuestion PreToolUse/PostToolUse hooks beside
the timeline Stop hook.

README.md

@@ -256,7 +256,7 @@ On Windows without Developer Mode (MSYS2 / Git Bash), `setup` falls back to file
 
 ## Privacy & Telemetry
 
-gstack sends nothing about how you use it unless you opt in. Telemetry is off by default and asked about once; the update check (a `git ls-remote` against GitHub, on by default) turns off with `gstack-config set update_check false`; outside reviews send code to Codex or Claude Code under your own login and turn off with `gstack-config set codex_reviews disabled`. Every off-machine send writes a receipt you can audit with `gstack-egress list`. The full account, including the exact fields telemetry carries and the local state that is not telemetry: [docs/privacy.md](docs/privacy.md).
+gstack sends nothing about how you use it unless you opt in. Telemetry is off by default and asked about once; the update check (two GitHub requests, a `git ls-remote` and a fetch of `VERSION`; with telemetry on it also reports your gstack version and OS; on by default) turns off with `gstack-config set update_check false`; outside reviews send code to Codex or Claude Code under your own login and turn off with `gstack-config set codex_reviews disabled`. Every off-machine send writes a receipt you can audit with `gstack-egress list`. The full account, including the exact fields telemetry carries and the local state that is not telemetry: [docs/privacy.md](docs/privacy.md).
 
 ## Troubleshooting
 

docs/install.md

@@ -26,7 +26,9 @@ Swap `required` for `optional` if you'd rather nudge teammates than block them.
 
 ## Hooks that `./setup` registers
 
-`./setup` also registers one default-on Stop hook in `~/.claude/settings.json`:
+`./setup` registers up to three hook families in `~/.claude/settings.json`, every one pointing at the canonical install. In team mode it registers the `SessionStart` auto-update hook (`gstack-session-update`; `./setup --no-team` skips it). It asks before registering the AskUserQuestion `PreToolUse` (preference enforcement) and `PostToolUse` (deterministic answer capture) hooks that `/plan-tune` uses at runtime; `./setup` never writes them silently. `docs/uninstall.md` lists the same families when telling you what to remove by hand.
+
+`./setup` also registers one default-on Stop hook:
 `gstack-timeline-stop` (closes dangling session-timeline entries when a session
 is interrupted; fail-open — 2s internal budget, always exits 0, can never block
 a session). Opt out persistently with `./setup --no-timeline-stop-hook` — the