A reviewer role reads the requirements and recommendations against the Checks
when the Target architecture is first submitted. Three runs of case 03: it did
not stop the validator sending the design back, and the designs it reviewed
ended with 87 and 93 Checks against 52, so they cost more. It stays behind
DESIGN_COVERAGE_REVIEW, off (iteration 6 step 13).
Also: the schema review no longer reads `true` or `false` in backticks as a
setting name.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>