docs: no internet consult egress in M6

The M6b device check talks to a loopback dummy. A live URL later is its own row.

Co-Authored-By: Grok 4.6 <noreply@x.ai>

docs/egress.md

@@ -13,6 +13,7 @@ allowed.
 | Run time (M4a) | `gatewayd` | the owner's Mattermost at `https://straylight.scylla-hammerhead.ts.net` (tailnet) | REST calls and one WebSocket: the owner's messages in, Boxmaker's answers out. Mattermost stores messages unencrypted in its database; the server is the owner's |
 | Run time (M5c) | `memoryd`, through `roncho` | the owner's Honcho at `[honcho] url` (rift: `http://rift.scylla-hammerhead.ts.net:8000`, tailnet) | Finished turns (the speaker's message and the final reply), conclusions mirroring trusted memory writes and untrusted notes, deletions of those conclusions; from M5c-2, searches and dialectic questions, from a session of any class (queries are not stored; see the M5c spec, section 8). Nothing written to it from a `secret` session or above `private`. Honcho runs its own models on the owner's hosts to derive conclusions (none on the fleet workspace); its server counts telemetry events but sends none (`telemetry_events_emitted_total`, 0 on 2026-09-27) |
 | Development (M5c) | the design model, planning M5c-1 | rift's Honcho | Recording real responses for the tests' fake server, in the throwaway workspace `boxmaker-plan-probe` only, deleted afterwards |
+| Development (M6b) | the M6b device check | a loopback OpenAI-compatible dummy the check starts on straylight (`127.0.0.1`) | One chat-completions POST per allowed `consult`; the check diffs the audit body against a captured request. No internet consult in M6. A live URL later is its own row, grant, and secret |
 
 The two run-time rows for M2a and M3b were missing until 2026-09-23; they were added with the M4a
 spec.