R-284: report a wrong figure as a wrong figure, and read the right entry

R-283 left the intact-sentence-wrong-number case falling through to omission, so
the guard said BESTIARY "does not state" a rating the page was stating. reads()
now has a shape tier between strict and loose: the strict pattern with its value
slot loosened, reporting which of the two numbers moved.

Scoped the per-creature rules while adding it. They read the whole page, and each
is the only rule of its kind today, so a page-wide match found the right line by
luck; a second attackFactor creature would have let the courier's rule match that
creature's sentence and report the courier correct. They now read the creature's
own "### Name" entry -- proved by deleting the courier's line and planting an
identical one under the redcap: still omission, where before it would have passed.

Five discriminations plus the decoy, proved in a worktree with the message read.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/REVIEW_LOG.md

@@ -6637,3 +6637,28 @@ digits; reword the statblock too and this degrades to OMISSION, the safe directi
 Four discriminations proved in a worktree, message read in each: reword kept → REWORD;
 line deleted → OMISSION; wrong number, right wording → mismatch naming both figures; redcap
 back on the ladder → the R-282 contradiction, unchanged.
+
+## R-284 — the third tier: a figure that moved is not a sentence that went
+
+R-283 left a case falling through to the omission branch: the sentence intact, the number
+inside it wrong. The message said BESTIARY "does not state the rating the simulator actually
+uses" about a page that was stating one. It named the right figures, so it pointed at the
+fix, but it described a document that does not exist — the same class of confidently-wrong
+report R-283 was written to remove, one case further in.
+
+`reads` now runs four tiers: **strict** (the sentence as it stands) passes; **shape** — the
+strict pattern with its value slot loosened — reports a MISMATCH and says which of the two
+numbers moved; **loose** reports a REWORD; nothing reports the OMISSION. The mismatch text
+is the sharpest of the four on purpose: *a figure the page states and the harness
+contradicts is worse than one it omits, because a GM can act on it.*
+
+**Scoped while adding it.** The rules read `page`, and every one of them is the only rule of
+its kind today, so a page-wide match found the right line by luck. Wire a second
+`attackFactor` creature and the courier's rule would have matched that creature's sentence
+and reported the courier correct — a guard passing on someone else's evidence. Per-creature
+rules now read the creature's own `### Name` entry. Proved by deleting the courier's line and
+planting an identical one in the redcap's entry: still OMISSION, where before scoping it
+would have passed.
+
+Five cases proved in a worktree, message read in each: effective rating wrong, base rating
+wrong, both wrong, reworded with the numbers kept, deleted. Plus the decoy above.