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/scheduler/ci.md

@@ -26,7 +26,7 @@ Two things worth knowing before you rely on it:
   host's NixOS config (not optional if you plan to actually use this).
 
 Everything below this point is implementation detail: exact
-auto-registration internals, container design, and the full security
+autoregistration internals, container design, and the full security
 writeup.
 
 ## CI checks
@@ -105,7 +105,7 @@ build can't hold the runner's single slot indefinitely).
 - **Sandbox fallback**: nspawn containers can't create user-namespaces, so nix's sandboxing would always fail. Module sets `nix.settings.sandbox-fallback = true` in the container — nix builds run unsandboxed (safe because the container is already isolated). See `docs/process/gotchas.md`.
 - **Credential isolation**: the forge admin token (`forge-core-token`) never enters the container. hive-c0re holds it and performs all forge API calls (runner validation + registration-token mint, in `forge/ci_runner.rs`); via hive-priv it writes only the runner registration token to the host env-file `/run/hive-ci/runner-token`, which the container bind-mounts read-only.
 
-## Auto-registration flow
+## Autoregistration flow
 
 Registration is **off the container's boot-critical path** — hive-c0re owns
 it and runs it out of band, so a slow forge or core-token never delays the
@@ -135,7 +135,7 @@ Gated on `HYPERHIVE_FORGE_CI_ENABLED` (the nix module sets it on `hive-c0re.serv
 
 ## Actions checkout mirror
 
-When `deploy.forgejo.ci.enable` is set, hive-c0re auto-seeds an
+When `deploy.forgejo.ci.enable` is set, hive-c0re autoseeds an
 `actions/checkout` pull-mirror on the local forge and sets Forgejo's
 `DEFAULT_ACTIONS_URL` to point at the local instance. This means CI
 `uses: actions/checkout@vN` steps resolve entirely on loopback — no
@@ -163,7 +163,7 @@ Each entry is created as a real Forgejo pull-mirror — not a one-off
 clone. Forgejo re-syncs the mirror on every pull (`git-upload-pack`
 request), so a DNS blip during that sync will propagate back to the
 runner as a hard `git clone` failure. The
-`<owner>` org in `dest` is auto-created. Keep mirror dests out of the
+`<owner>` org in `dest` is autocreated. Keep mirror dests out of the
 hive-c0re-managed namespaces (`config/`, `shared/`, `agents/`, `core/`)
 to avoid provisioning collisions.
 
@@ -248,6 +248,6 @@ builder — disk-pressure collection at least runs while nothing is mid-copy.
 
 ## References
 
-- `nix/host-modules/hive-ci.nix`: runner configuration, auto-registration script, container setup.
+- `nix/host-modules/hive-ci.nix`: runner configuration, autoregistration script, container setup.
 - `.forgejo/workflows/ci.yml`: workflow definition.
 - `docs/process/gotchas.md`: nix sandboxing limitations in containers.

docs/scheduler/coordinator.md

@@ -158,7 +158,7 @@ reparent(moves):   Reparent(moves)   (no rebuild — topology.json is read live)
 Notable collapses:
 
 - **`rebuild` is one uniform shape** — no `was_running` branch.
-  `StopForUpdate` noops when already down; the tail `Reconcile` auto-noops the
+  `StopForUpdate` noops when already down; the tail `Reconcile` autanoops the
   start when `wanted = Offline` (a rebuild of a deliberately-stopped agent
   leaves it stopped).
 - **The swap-failure recovery-start is structural**: `Reconcile` deps on
@@ -479,7 +479,7 @@ flags → `systemctl daemon-reload` → `start`.
 
 ### Prebuild attr path
 
-`nix build` doesn't auto-resolve `meta#<name>` against `nixosConfigurations` the
+`nix build` doesn't autoresolve `meta#<name>` against `nixosConfigurations` the
 way `nixos-container` does internally. The explicit attr path
 `<flake-root>#nixosConfigurations.<name>.config.system.build.toplevel` is required;
 using the bare `meta#<name>` ref would make nix look in `packages`, `legacyPackages`,