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/frank-zealot.env

@@ -16,7 +16,7 @@
 # custom-quant lock-in like the ROCmFPX era). NO nextn/mtp tensors exist, so
 # in-file MTP is impossible here; SPEC_TYPE=none is forced by the payload.
 #
-# KV rate law: 8 full layers × 4 KV heads × 256 dim = 8,192 elements per
+ # KV rate arithmetic: 8 full layers × 4 KV heads × 256 dim = 8,192 elements per
 # token per cache. f16 K + f16 V = 32,768 B/token = 32 KiB/token, so the
 # 401,408-token pool is 12.25 GiB. The 24 DeltaNet layers cost a fixed
 # recurrent state per SLOT (not per token) — that is why two 200k slots fit