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).

tests/llm_deploy_gates.bats

@@ -35,8 +35,8 @@ teardown() { sandbox_teardown; }
 }
 
 @test "the dragoon handler refuses a symlinked tokenizer file" {
-    # The flat-tokenizer law: a HuggingFace cache snapshot links its
-    # members, and the link dangles inside the container mount.
+    # Snapshot layouts link their members into place, and the link dangles
+    # inside the container mount — only regular files are servable.
     rm "$STAGE/models/tokenizer/vocab.json"
     ln -s /nowhere/vocab.json "$STAGE/models/tokenizer/vocab.json"
     run_handler dankclaw frank-dragoon