docs: fix Microsoft.Foreign hits (e.g./i.e. -> for example/that is)

Substitutes 'for example' for 'e.g.' and 'that is' for 'i.e.' per
Microsoft style, with no comma after the replacement -- this repo
never puts a comma after e.g./i.e. either, so the substituted phrase
matches that house style instead of vale's literal 'for example,'
suggestion.

Covers all 77 real hits (72 from the initial vale pass + 5 more of the
same pattern found on a follow-up vale run). None of the flagged
instances were sentence-initial, so there's no capitalization concern
here.

Verified via a fresh vale run: 0 remaining Microsoft.Foreign hits.
Full accounting in /agents/iris/state/haiku-batches/foreign-report.md.

docs/process/conventions.md

@@ -26,7 +26,7 @@ Four env vars cover the identity surface, read by
 - `HYPERHIVE_HIVE_DOMAIN` — the hive's canonical DNS domain (e.g.
   `darkest.space`), set by `nix/host-modules/hive-c0re/environment.nix`
   from `services.hyperhive.domain`. When configured, `qualified_label()`
-  returns `${label}@${domain}` (e.g. `iris@darkest.space`); when
+  returns `${label}@${domain}` (for example `iris@darkest.space`); when
   unset (single-hive deployments, dev/test) it degrades to just
   the short label so existing callers see no change. The
   qualified form surfaces in the per-agent web UI title, the
@@ -47,7 +47,7 @@ can share a swarm name. Humans want both: the address
 still use the domain-based convention untouched.
 
 `qualify(label)` is the same shape as `qualified_label()` but
-applies to an arbitrary label the caller already has (e.g. a peer
+applies to an arbitrary label the caller already has (for example a peer
 name from the broker); it's the right surface when rendering a
 peer's name when the caller knows it's hive-local.
 
@@ -509,7 +509,7 @@ check derivations they don't:
 When local clippy/fmt/test pass but CI's `nix flake check` fails,
 **don't assume a transient builder problem** — reproduce the real
 gate locally: `nix flake check` (shares the build farm, use
-sparingly) or build just the suspect check, e.g. `nix build
+sparingly) or build just the suspect check, for example `nix build
 .#checks.x86_64-linux.hivectl-docs`.
 
 ## Best-effort oneshot services

docs/process/gotchas.md

@@ -309,7 +309,7 @@ nix develop -c cargo run -p hive-c0re --bin hivectl -- <args>
 ```
 
 This is also how you regenerate committed generated docs locally —
-e.g. `docs/tools/hivectl-cli.md` via the `hivectl markdown-docs`
+for example `docs/tools/hivectl-cli.md` via the `hivectl markdown-docs`
 subcommand (its `hivectl-docs` flake check otherwise only fails in
 CI on drift).
 
@@ -389,7 +389,7 @@ connects to the compositor at `127.0.0.1:<vnc_port>`.
   fixed `/run/gui` (systemd `RuntimeDirectory=gui`, `0700`,
   `RuntimeDirectoryPreserve=yes` so it survives weston restarts for the
   wayland client sharing the `/run/gui/wayland-0` socket). Wayland
-  clients in the agent's config (e.g. bitburner electron) must run as the
+  clients in the agent's config (for example bitburner electron) must run as the
   same user with `XDG_RUNTIME_DIR=/run/gui`.
 - **One shared D-Bus session bus (`gui-dbus.service`)**: a single
   persistent `dbus-daemon --session` bound at `/run/gui/bus`, run as the

docs/process/pr-review-gate.md

@@ -31,7 +31,7 @@ is someone else's call.
 Submit `hive-forge pr-reviews <pr> --approve` or `--request-changes`
 as soon as you've finished checking the diff — don't hold it back
 waiting for CI to go green first. Mention CI's current state in the
-review body if it's relevant (e.g. "approving; `nix flake check` is
+review body if it's relevant (for example "approving; `nix flake check` is
 still running"), but don't gate the formal verdict on it: CI isn't a
 signal a reviewer waits on, it's a separate condition that resolves
 independently.