treefmt: apply prettier

Pure `nix fmt` output from the commit before this one — no hand edits.
203 files: 52 md, 42 tsx, 32 js, 32 css, 21 ts, 13 html, 8 json, 3 mjs.

Reproduce with `nix develop -c nix fmt` on the parent commit; the result
should be byte-identical to this tree.

None of the 13 `.prettierignore` entries appears here — verified by
intersecting the changed-file list against the ignore file, with a
control proving the intersection finds a match when one exists.

docs/turn-loop/claude-invocation.md

@@ -73,7 +73,7 @@ percentage-of-window ctx badge.
 harness-owned session title (`turn::session_title()`, default
 `hive-session`, override `HIVE_SESSION_TITLE`). The durable
 `hive_claude::InfiniteSession` (built once by the serve loop via
-`turn::make_session`, then reused) `--resume <title>`s it; the *first* use
+`turn::make_session`, then reused) `--resume <title>`s it; the _first_ use
 (bootstrap, post-archive, post-purge) misses and the session re-runs the
 same prompt once with `--name <title>` to mint it. That single self-heal
 rule is the whole identity system — there is **no** scraped session-id
@@ -85,7 +85,7 @@ context (it won't carry our title). claude stores sessions in
 `~/.claude/projects/<cwd-slug>/<uuid>.jsonl` (bind-mounted persistently);
 `--name` writes the title into the file as a `custom-title` event, which
 is what `--resume <title>` resolves against. We never pass bare
-`--continue` (it resumes the *latest* session in the cwd — the hijack
+`--continue` (it resumes the _latest_ session in the cwd — the hijack
 vector). Auto-compact, auto-memory, and dynamic workflows (the `/workflows`
 feature) are disabled via the managed settings at
 `/etc/claude-code/managed-settings.json`: hyperhive owns compaction
@@ -94,12 +94,12 @@ feature) are disabled via the managed settings at
 harness's autonomous turns.
 
 **Session reset** is available via `POST /api/new-session` (or
-`/new-session` slash command). It does *not* touch the session inline —
+`/new-session` slash command). It does _not_ touch the session inline —
 that would race a mid-write claude process. Instead `Bus::request_session_reset()`
 sets a one-shot flag consumed at the next turn boundary by `drive_turn`,
 which **archives** the current session: the backing `<uuid>.jsonl` is
 renamed to `<uuid>.jsonl.archived` (dropped out of claude's `*.jsonl`
-resolution glob, history preserved on disk, only the file carrying *our*
+resolution glob, history preserved on disk, only the file carrying _our_
 title — any `choom` session sharing the cwd is left alone). The next
 turn's `--resume <title>` then misses and self-heals into a fresh session.
 
@@ -111,19 +111,19 @@ at `/etc/claude-code/managed-settings.json`); hyperhive owns it. The
 window with two triggers baked into its `run`:
 
 - **Reactive** — claude-code prints `Prompt is too long`. The session is
-  *already* past the window, so no turn can run on it — the session
+  _already_ past the window, so no turn can run on it — the session
   `/compact`s straight away and retries the same wake-up prompt once. No
   notes-checkpoint turn is possible here: the detail is gone. If the retry
-  *still* overflows, `run` surfaces `Error::PromptTooLong`; `drive_turn`
+  _still_ overflows, `run` surfaces `Error::PromptTooLong`; `drive_turn`
   then archives the session (session lifecycle stays hive-side) and the
   serve loop requeues the message so it redelivers into a fresh session
   (see [Turn outcomes](README.md#turn-outcomes) — the wake prompt itself is tiny, so
   the overflow was the accumulated context the archive clears).
 - **Proactive** — a turn finishes cleanly but the last inference's context
   size crossed the policy watermark. While the session is still healthy it
-  runs one synthetic *notes-checkpoint* turn (`CHECKPOINT_PROMPT` —
+  runs one synthetic _notes-checkpoint_ turn (`CHECKPOINT_PROMPT` —
   "context is filling up, flush durable state into `/state` now") and
-  *then* `/compact`s, so the agent can persist in-flight state before the
+  _then_ `/compact`s, so the agent can persist in-flight state before the
   detail collapses into a summary.
 
 The **when** is a `hive_claude::CompactionPolicy` injected by the harness:
@@ -166,7 +166,7 @@ still applies.
   session (same mechanism as the operator reset — rename `<uuid>.jsonl` →
   `.archived`) so the next turn's `--resume <title>` misses and starts
   fresh. Unlike proactive compaction the session is dropped entirely, not
-  compacted — and *no* preceding checkpoint turn runs, because any turn
+  compacted — and _no_ preceding checkpoint turn runs, because any turn
   before the reset would just re-warm the cache and defeat the purpose.
   Set `HIVE_AUTO_RESET_WATERMARK_TOKENS=0` to disable. Auto-reset and the
   operator reset are mutually exclusive per turn (both archive → fresh
@@ -236,11 +236,11 @@ needs to `chown` a bind mount), once at startup:
 
   **`hive_identity` / `swarm_identity` shape.** Each carries a
   leading space + backticked name (` on hive \`pr1ma\``,
-  ` in swarm \`constellat1on\``) when the corresponding env var
-  is set, otherwise empty string. The independence lets the
-  template drop one or both into the opener prose without
-  breaking single-hive deployments that never set the option;
-  the renderer also treats `Some("")` from a caller as `None` so
+` in swarm \`constellat1on\``) when the corresponding env var
+is set, otherwise empty string. The independence lets the
+template drop one or both into the opener prose without
+breaking single-hive deployments that never set the option;
+the renderer also treats `Some("")`from a caller as`None` so
   empty-string env vars and missing env vars round-trip the
   same way.
 
@@ -251,4 +251,3 @@ telemetry-to-bus bridge — lives in `hive-agent`'s `turn` module; see its
 The actual claude spawn, stream classification, and the
 reactive/proactive compaction loop are in the `hive-claude` crate.
 Login-wait lives in `hive-agent`'s `login` module.
-