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/agent-lifecycle/agent-hierarchy.md

@@ -123,7 +123,7 @@ other agents don't:
   a root-only capability even post-milestone, not a topology rule.
   One exception: `Wake` (inject a `from: <X>` message into the
   caller's own inbox) isn't really privileged — every per-agent daemon
-  (e.g. `hive-forge-notify`) needs it, and sub-agents already have the
+  (for example `hive-forge-notify`) needs it, and sub-agents already have the
   equivalent on their own socket.
 - **Storage/mounts** — only the manager container gets
   `/var/lib/hyperhive/agents` bind-mounted RW at `/agents` (so it can

docs/agent-lifecycle/approvals.md

@@ -246,7 +246,7 @@ Transient broker errors (sqlite lock contention, etc.) get the same
 ### Reminder delivery: file-path semantics
 
 A reminder may carry a `file_path` (the agent-visible path inside its
-container, e.g. `/agents/<name>/state/foo.md`). On delivery hive-c0re:
+container, for example `/agents/<name>/state/foo.md`). On delivery hive-c0re:
 
 1. **Translates** the container path to the host path
    (`/var/lib/hyperhive/agents/<name>/state/foo.md`) so c0re can write
@@ -667,7 +667,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 (e.g. a `github:` URL),
+flake input has no canonical path (for example a `github:` URL),
 auto-update is a no-op — rebuild manually.
 
 The dashboard surfaces pending updates per agent: a clickable

docs/agent-lifecycle/persistence.md

@@ -337,7 +337,7 @@ A parent agent gets each direct child's `state` dir bind-mounted
 **read-write** and its `config` dir **read-only**
 (`bind_child_agent_dirs` in `lifecycle/host_config.rs`). The RW on
 `state` is deliberate, not an oversight: a parent manages its children,
-which includes writing into a child's state for recovery (e.g. seeding
+which includes writing into a child's state for recovery (for example seeding
 notes, clearing a stuck sentinel) as well as reading it.
 
 **`harness` isn't mounted at all.** It holds the child's own runtime