refact(comments): state the mechanism, not the incident

Every comment that invoked a 'law' (50 word-boundary sites across 28
tracked files) now states what is going on and why, in terms that
transfer to any project: gate twins drift until one side greenlights
what the other refuses; a tag re-points while a digest pins; a
restrictive engine behavior belongs to the runtime that imposed it and
must be re-tested, not inherited; a speculative head is tensors in the
file, not a flag; snapshot links dangle where the container resolves
them; exit 0 is a clean stop to systemd, so a self-exiting daemon on
on-failure goes dark reporting success. Event narratives and dates are
gone from these comments; the mechanics carry the argument.

Behavior-identical: bash -n, py_compile, yaml parse, full bats suite
408/408 green. One symbol rename rides along (stack script local
scale_law -> scale_contract, with its log text).

scripts/probe-frank-archon-kv.py

@@ -9,7 +9,9 @@ No scratch container, no mask: the service under test is the service.
 Three 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.
+     Method: >=128 generated tokens (below that, first-token latency
+     dominates the decode rate), greedy (sampling noise is unattributable),
+     real text (synthetic text inflates draft acceptance).
   B  the capacity contract — TWO concurrent chats of ~197k prompt tokens
      (~394k tokens resident) each carrying a unique marker at its head. Both
      must answer their own marker. This is what a 2 x 200,000 endpoint owes:
@@ -17,11 +19,11 @@ Three probes, in increasing cost:
   C  prefix-cache restore — probe A's cold prompt again, so the disk tier has
      to give the blocks back (cache_n > 0, TTFT collapses).
 
-PROBE LAW (learned the hard way, twice): radiance routes the thinking block to
+PROBE PITFALL: radiance routes the thinking block to
 `reasoning_content`, so a chat request whose budget is spent inside
 `<think>` returns EMPTY `content` with `finish_reason: stop`. A probe that
-reads `content` alone scores 0/2 on a healthy server. Every request here sets
-chat_template_kwargs.enable_thinking=false and reads both fields.
+reads `content` alone scores 0/2 on a healthy server. Every request here
+sets chat_template_kwargs.enable_thinking=false and reads both fields.
 
 A/B method for a shape change (no scratch container): write a variant env file
 on the host, point a transient systemd drop-in at it