comments: replace law idiom with the mechanism it encoded

Every comment that cited a named law, an incident date, or an
internal nickname now states the underlying mechanism and why it
matters, generically: curl exit-0 artifacts and byte-count gates,
argv-in-/proc secret exposure, tag mutability vs digest pinning,
shape-specialized kernels refusing uncompiled slot counts, MTP heads
as file tensors no flag can supply, drafter/slot coupling as an
engine property, pkill -f matching its invoker, pinned-RAM pairing
with LimitMEMLOCK, one-encoding-per-table, the short-run first-token
noise floor, and the protected-expert rule. No behavior change:
comment/string text only; suite green (371 tests).

scripts/probe-frank-archon-kv.py

@@ -9,7 +9,8 @@ No scratch container, no mask: the service under test is the service.
 Four probes, in increasing cost:
   A  decode at depth — one ~51k-token chat completion, 512 tokens, greedy.
      Reports the engine's own `timings` (prefill, decode, draft acceptance).
-     The bench law applies: >=128 generated tokens, greedy, real text.
+     Measurement discipline: generate at least 128 tokens (a short run
+     measures first-token noise, not the server), greedy, real text.
   B  the capacity contract — as many CONCURRENT chats of ~197k prompt tokens as
      the deployed `FRANK_ARCHON_MAX_SEQS` (read from the repo env file on this
      host), each carrying a unique marker at its head. All must answer their own