docs: remove hyphens from auto-X compounds per Microsoft.Auto style

Fixed 72 hyphenated 'auto-X' compounds across the docs by deleting
the hyphen to match Microsoft style guide (autogenerated, autoregistration,
autodiscovery, etc). Preserved original capitalization throughout.

Covered 26 documentation files in docs/, including README.md, agent-lifecycle,
integrations, scheduler, networking, process, tools, trust-boundary,
turn-loop, and web-ui sections.

docs/agent-lifecycle/agent-hierarchy.md

@@ -150,7 +150,7 @@ Manager}` switch picks the MCP tool allow-list claude sees. Both are
   manager-only overrides exist across `hive-c0re` today: loose-ends
   visibility (manager sees hive-wide, sub-agents only their own),
   `destroy` refusing to act on the manager, and crash-watch skipping
-  the manager (it auto-restarts via systemd instead of going through
+  the manager (it autorestarts via systemd instead of going through
   the crash-watch loop). Each is planned to become an
   ancestor/descendant check instead of a manager-name check — see the
   module docs for `loose_ends.rs`, `stores/broker.rs`, `actions.rs`,
@@ -225,7 +225,7 @@ uid 0 and have the setuid bit set."
 - `Restart = on-failure`, `RestartSec = 2` — keeps the harness
   resilient across transient crashes without thundering retries.
 - `RuntimeDirectory = "hive-config"` → `/run/hive-config/` owned by
-  `User=`, auto-cleared on stop. The harness writes regenerated
+  `User=`, autocleared on stop. The harness writes regenerated
   `claude-{mcp-config,settings,system-prompt}` files there
   (`paths::config_dir`). Deliberately separate from `/run/hive`, which
   the host bind-mounts in root-owned and which holds hive-c0re's

docs/agent-lifecycle/approvals.md

@@ -340,7 +340,7 @@ Single-phase variants exist for paths without
 rollback semantics: `meta::lock_update_for_rebuild(name)` for
 the manual `↻ R3BU1LD` button (commits if the lock changed)
 and `meta::lock_update_hyperhive()` for the
-auto-update flake-rev bump (one shot before per-agent
+autoupdate flake-rev bump (one shot before per-agent
 rebuilds, commits if the lock changed).
 
 `meta::sync_agents(hive: &HiveEnv, agents: &[AgentSpec])` — `hive`
@@ -644,7 +644,7 @@ hive-c0re-vouched commit sha. Optional `tag` carries the deploy
 bookkeeping tag — `deployed/<id>` on a successful build or
 `failed/<id>` on a failed one, planted by the `MergeConfigPr` deploy.
 Both fields are `Option`: `None` on the paths that don't deploy a new
-commit (spawn / init_config / meta-update / deny, and the auto-update
+commit (spawn / init_config / meta-update / deny, and the autoupdate
 sweep's `job_queue::templates::rebuild` reapplying the existing main,
 or the dashboard `↻ R3BU1LD` button when the lock didn't move). When set,
 `git show <sha>` against `/applied/<n>/.git` inside the
@@ -657,7 +657,7 @@ message-event list. If it's "FYI, check when convenient," call
 `push_todo`/`push_todo_submitter` directly instead — no new wire type
 needed.
 
-## Auto-update on startup
+## Autoupdate on startup
 
 `hive-c0re serve` runs `auto_update::run` in a background task right
 after opening the coordinator. It enumerates managed containers and
@@ -668,7 +668,7 @@ one — sub-agents and the root agent go through the same
 "Rev" = canonical filesystem path of `cfg.hyperhiveFlake`. Marker
 file: `/var/lib/hyperhive/applied/.<name>.hyperhive-rev`. If the
 flake input has no canonical path (for example a `github:` URL),
-auto-update is a no-op — rebuild manually.
+autoupdate is a no-op — rebuild manually.
 
 The dashboard surfaces pending updates per agent: a clickable
 "needs update ↻" badge appears whenever the marker differs from

docs/agent-lifecycle/persistence.md

@@ -439,7 +439,7 @@ On a btrfs host, a brand-new agent's state root is created as a
 **btrfs subvolume** instead of a plain directory (progressive
 enhancement — see the #1762 lane). This is a no-op fallback on
 non-btrfs hosts and for any agent whose root already exists, so
-nothing is auto-migrated: existing agents keep their plain dirs
+nothing is automigrated: existing agents keep their plain dirs
 until an explicit opt-in upgrade.
 
 - **Creation:** `lifecycle::ensure_agent_state_subvolume` runs before
@@ -548,7 +548,7 @@ streamable-http (`hyperhive.mcp.matrixHttpPort`, no stdio bridge —
 same shape as `hive-bash-daemon`), emits hyperhive wake signals
 on incoming room events via `/run/hive/mcp.sock`. Conditional on
 `hyperhive.matrix.enable` (which both the daemon AND the
-auto-injected `extraMcpServers.matrix` entry read).
+autoinjected `extraMcpServers.matrix` entry read).
 
 **First-boot ordering**: hive-c0re provisions the matrix token AFTER
 agent containers come up. Without the path-trigger sibling