R-288: an empty cast declaration is fatal; a missing one still falls back

c0's point on R-286: the reader is unambiguous now, but the roster fallback that
made the failure look like success is still reachable. Narrowly closed -- sixteen
of the seventeen scenarios declare no cast and are rightly checked against the
whole roster, so only a marker that is PRESENT and names nobody is refused, with
its line named. Replacing the declaration with <!-- cast: --> passes before this
change and fails after it.

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

docs/REVIEW_LOG.md

@@ -6752,3 +6752,16 @@ sentences and there is no smaller slice that owns them, so it is left alone deli
 rather than overlooked. check-rules builds its covered-set from labels it generates, not from
 searching a document. check-lang, check-creatures, check-templates, check-kits and the
 baseline guards do no document matching at all.
+
+## R-288 — an empty declaration is not the same as no declaration
+
+c0's note on R-286: the reader is unambiguous now, but the fallback that made the failure
+look like success is still there. It is right, and the fix has to be narrow. **No marker at
+all is the ordinary case** — sixteen of the seventeen scenarios here declare no cast and are
+rightly checked against the whole duty roster. A marker that is present and names nobody is
+a different thing: somebody wrote a declaration, the guard read nothing out of it, and the
+fallback then widens the population silently, so a clue only Pollard can reach passes on the
+strength of an agent the scenario does not cast.
+
+Replacing CLEAN GROUND's declaration with `<!-- cast: -->` passes before this change and
+fails after it, naming the line. A scenario with no marker still falls back, unchanged.