docs: align wire-spec and mark implemented vs proposed

Keep the 45-byte pose frame consistent across docs, simulator, and
prototype, clarify MinIO is not peer sync, and state clearly that the
repo is a from-scratch platform sketch with options rather than mandates.

docs/adr/ADR-0004-sql-over-ssh-contract.md

@@ -32,10 +32,15 @@ wrapper, permissions, and output format a peer drone would use.
 
 ## Consequences
 
-- One access path is built, secured, and tested — "what you test is what
+- One access path is designed for flight and bench — "what you test is what
   flies".
-- The SQL gate is safety-critical and is covered by unit tests
-  (`simulator/tests/test_sql_gate.py`).
-- The explorer and the prototype's live mode are *just another read-only
-  consumer* of this same contract ([`../04-swarm-sync.md`](../04-swarm-sync.md)).
+- The statement gate in the PoC (`simulator/explorer/server.py`, covered by
+  `simulator/tests/test_sql_gate.py`) is a **first layer**: keyword allow/deny
+  over HTTP for the explorer. Production still needs the remaining layers in
+  [04 — Swarm sync](../04-swarm-sync.md) (forced-command key, read-only OS user,
+  engine hardening, resource caps) and a real SQL parser rather than keywords
+  alone.
+- The explorer and the prototype's live mode are *stand-in consumers* of the
+  same read-only contract over HTTP today; the proposed flight path is
+  SQL-over-SSH ([`../04-swarm-sync.md`](../04-swarm-sync.md)).
 - Design principles 7 and 8 in [`../../README.md`](../../README.md) restate this.