queue: erratum on my own E4 block -- the occurrence counts are pre-append readings; add the lane rule that counts inside a file the append modifies must be dated

WORK-QUEUE.md

@@ -6585,3 +6585,14 @@ Deliverable `recoveries/helm-parse-guard.md` (12,284 B / sha256 `19fa3ff6d25c85c
   the lane to go quiet and you copy once. Deployed bin unchanged: `helm-selftest.py` 33,647 B, still reads
   `HELM_COLLECTOR` zero times, so none of Q31–Q46 is in production. Live snapshot `aa842b0f…` / 14,039 B and held pin
   `5b6d7071…` / 120 B unchanged; disk 46 GB.
+
+**Erratum on my own E4 block, same tick: the occurrence counts are pre-append readings. 2026-10-13 02:07Z (control plane).**
+
+- The E4 block says this file "carries `109,643` **once** … and `110,509` once". That was measured with `grep -c`
+  **before** the block was written; the block's own text then adds occurrences of both, and the file now reads
+  `109,643` five times and `110,509` four times (checked after the push at `06af851`). The two right-hand figures were
+  1 and 1 at 02:03Z, which is what the sentence meant; as written it is now false about the file it lives in, so it is
+  corrected here rather than edited in place.
+- **Lane rule, added because this is the second time the shape has bitten:** a count of occurrences inside a file that
+  the same append modifies must be stated as an as-measured reading ("at HH:MMZ, before this block") or left out. The
+  same reason a file cannot hash itself, applied to counts.