Repo cleanup: retire the served C0 probe and stale upstream-finding content

docs/consumers.md

@@ -105,7 +105,9 @@ honor it. webcrypto stays measurable indefinitely either way.
 
 Node is **not a consumer requirement.** Deno functionally substitutes across
 the whole consumer capability surface — verified empirically (2026-08-08,
-Deno 2.9.5/linux-arm64, `tools/probes/webrtc-deno/`):
+Deno 2.9.5/linux-arm64, via the C0 capability probe; served and retired
+2026-08-14, history: `git log -- tools/probes/webrtc-deno` — the living
+WebRTC coverage is `just test-webrtc`, node-datachannel under Deno):
 
 | Capability | Deno path | Status |
 |---|---|---|

ports/webrtc/src/webrtc.ts

@@ -1,8 +1,9 @@
 // Host-module port of `polymorph:webrtc-datachannels/connections@0.1.0` to
 // the embedder conventions (contracts/embedder-api.md), backed by the
-// Deno-verified WebRTC path (tools/probes/webrtc-deno/probe.mjs proved both
-// node-datachannel's Node-API addon and pure-TS werift pass full
-// data-channel loopbacks under this exact Deno).
+// Deno-verified WebRTC path (the retired C0 probe — see docs/consumers.md
+// "Deno substitutes for Node" — proved both node-datachannel's Node-API
+// addon and pure-TS werift pass full data-channel loopbacks under this
+// exact Deno).
 //
 // Ported from the browser-first reference
 // (`polymorph/polymorph-webrtc-datachannels/jco-impl/webrtc.js`, read-only

ports/webrtc/webrtc.test.ts

@@ -1,8 +1,9 @@
 // In-process loopback tests for the `ports/webrtc` host module: two
 // instantiations of the port's `PeerConnection`/`DataChannel` classes wired
 // directly to each other (no signaling server), following the
-// trickle-ICE-buffering discipline proven by
-// `tools/probes/webrtc-deno/probe.mjs`.
+// trickle-ICE-buffering discipline proven by the C0 capability probe
+// (`tools/probes/webrtc-deno/`, retired 2026-08-14 — its questions are
+// answered in docs/consumers.md; source via git history).
 //
 // Sanitizer note: `node-datachannel` keeps background native threads alive
 // across the whole process (proven by the probe, which calls `Deno.exit`
@@ -31,7 +32,7 @@ const NO_SANITIZE = { sanitizeResources: false, sanitizeOps: false };
 /**
  * Wire two freshly constructed `PeerConnection`s through a full offer/answer
  * + trickle-ICE exchange, in-process (no network signaling server) —
- * ported wiring discipline from tools/probes/webrtc-deno/probe.mjs:28-66
+ * ported wiring discipline from the retired probe's loopback
  * (buffer candidates until the peer has its remote description).
  */
 async function connectPair(): Promise<{ a: PeerConnection; b: PeerConnection }> {