Make the docs state things rather than argue them

The site read as a design journal: rationale paragraphs, hedges
("deliberately", "on purpose", "genuinely"), meta-commentary about the docs
themselves, and one em-dash every ten lines carrying an aside.

Roughly twenty rationale blocks are gone or reduced to what a reader needs
in order to use the thing. Em-dashes go from 507 to 135, and what is left is
structural rather than prose: list and definition separators, table cells,
and four inside code blocks that quote what the CLI actually prints.

Also: api.example.com becomes api.fluksio.com (the emails stay, since
bootstrap.py really defaults to admin@example.com and RFC 2606 reserves it);
the mqtt table gains the two settings it had drifted behind on and inject's
wording matches the engine; llms.txt lists the two connector pages that were
in the nav but not in it; and the two device/device_policy notes now agree.

Builds clean under `zensical build --strict`.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015YrQnKV3bnQd4K342y8tKj

docs/code/api.md

@@ -1,7 +1,7 @@
 # The HTTP API
 
 Everything the browser does, the API does first. The dashboard is a generated
-client of this schema, not a privileged path into the engine — so anything you
+client of this schema, not a privileged path into the engine, so anything you
 can click, you can script.
 
 Base URL: `https://api.${DOMAIN}/api/v1`, or `http://127.0.0.1:8000/api/v1` for
@@ -24,7 +24,7 @@ A bearer token, valid for eight days. `POST /login/test-token` checks one.
 Password recovery and reset are `POST /password-recovery/{email}` and
 `POST /reset-password/`.
 
-Agents authenticate differently — see [Agents over MCP](agents.md).
+Agents authenticate differently; see [Agents over MCP](agents.md).
 
 !!! tip "The interactive schema"
 
@@ -33,9 +33,8 @@ Agents authenticate differently — see [Agents over MCP](agents.md).
     `/api/v1/openapi.json`. That is the authoritative reference; this page is
     the tour.
 
-    It is closed in production on purpose: the schema enumerates every endpoint
-    the instance serves, including the paths webhook nodes mounted at
-    runtime.
+    It is closed in production: the schema enumerates every endpoint the
+    instance serves, including paths webhook nodes mounted at runtime.
 
 ## Flows
 
@@ -81,8 +80,8 @@ shared sources and which flows use each.
 | `POST` | `/flows/{name}/nodes/{id}/acknowledge` | clear the failure the canvas is marking |
 
 `POST /flows/{name}/run` on a **batch** flow submits a run instead, because
-that is what running one means — the parameters, the series and the result are
-the point, and a call that quietly did something else would be a trap.
+that is what running one means: the parameters, the series and the result are
+the point.
 
 ## Messages
 
@@ -95,7 +94,7 @@ curl -s $FLUKSIO/messages/house.temperature/history -H "Authorization: Bearer $T
 
 `GET /messages/` is the catalogue: every message any published flow declares,
 with its last value. Publishing puts a value into the graph exactly as a
-dashboard control does — which means only a message some flow *declares* can be
+dashboard control does, which means only a message some flow *declares* can be
 published to. Flows own the namespace; everything else is a client of it.
 
 ## Runs
@@ -113,8 +112,8 @@ published to. Flows own the namespace; everything else is a client of it.
 | `GET` | `/runs/{id}/metrics?name=&stride=` | one metric's series, in step order; every series of the run without `name` |
 | `GET` | `/runs/series/compare?ids=a,b,c&metric=&x=` | that metric across several runs. `x` is what to plot against: nothing or `step`, `time` (seconds since each run's own first reading), or another metric's name, joined on the step the two share |
 
-Submitting answers immediately with a `queued` run. Wrong parameters — an
-undeclared name, a value of the wrong type — come back as a 422 naming the
+Submitting answers immediately with a `queued` run. Wrong parameters (an
+undeclared name, a value of the wrong type) come back as a 422 naming the
 problem, before anything executes.
 
 `?digest=` filters by the hash of the parameters, which is how you find "every
@@ -122,13 +121,13 @@ run that used exactly this configuration".
 
 `?before=` is how a long history is paged: rows come newest first, so handing
 back the last row's `created_at` reads the next page whatever landed
-meanwhile — which `?offset=` cannot, since a run submitted between two pages
+meanwhile, which `?offset=` cannot, since a run submitted between two pages
 shifts every row down one. `?since=` is inclusive and bounds the other end.
 
 Both exports stream `csv` (the default) or `jsonl`, and take the selection the
 history takes plus `?ids=a,b,c`, `?since=` and `?until=`. `export/runs` puts
-the inputs that *vary* across the selection in `param.` columns — the sweep
-axis — unless `?params=` names them, and the run's numbers in `metric.`
+the inputs that *vary* across the selection in `param.` columns (the sweep
+axis) unless `?params=` names them, and the run's numbers in `metric.`
 columns. Both are dotted paths into whatever a node returned, so
 `?metrics=final_metrics.train_loss` selects a field of a record and the
 defaults reach every number inside one. The run id is on every row of both, which is what makes an exported
@@ -239,4 +238,4 @@ stored version moved past the one you were editing. Re-read, merge, save again.
 
 The frontend's TypeScript client is generated from the OpenAPI schema
 (`make generate-client`). Any OpenAPI generator will do the same for your
-language — point it at `/api/v1/openapi.json` on a non-production instance.
+language: point it at `/api/v1/openapi.json` on a non-production instance.