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/connectors.md

@@ -36,8 +36,8 @@ uv add --editable ../../fluksio-connector-mydevice
 ```
 
 Editing your connector's **code** then takes effect on the next engine restart,
-with no reinstall. Changing its **metadata** — the entry point, the version,
-the package name — needs `uv sync` to regenerate the installed metadata before
+with no reinstall. Changing its **metadata** (the entry point, the version,
+the package name) needs `uv sync` to regenerate the installed metadata before
 a restart picks it up.
 
 Two things to know about this:
@@ -84,7 +84,7 @@ class MyDevice(ConnectorNode):
 
 Then, on the canvas: place the node, set `poll_interval` to how often the
 device should be read, pick the API key from the secrets store, and add output
-ports named `temperature` and `humidity`. The port names are the wiring — any
+ports named `temperature` and `humidity`. The port names are the wiring: any
 node consuming those messages is downstream of this one.
 
 ## If the device is told rather than asked
@@ -102,7 +102,7 @@ message drives the device. Set `idempotent = False` on the class: a write is a
 command, and a redelivery after a crash should not undo a newer one.
 
 Keep the first version off the wire. A boolean setting the code checks before
-it sends — `artnet`'s `transmit` is the example — lets a flow be built and
+it sends (`artnet`'s `transmit` is the example) lets a flow be built and
 watched in the logs before anything physically moves.
 
 ## If the reading is bytes
@@ -117,8 +117,8 @@ A camera or a microphone publishes a reference rather than the bytes:
 
 Place the node with an `image`-typed output port and a Media widget draws each
 frame as it lands. `fluksio-connector-test-media` publishes test frames and
-tones this way, so the whole path can be wired up with no camera in the room —
-copy it if yours is a media device.
+tones this way, so the whole path can be wired up with no camera in the room.
+Copy it if yours is a media device.
 
 ## Try it without a device