fix: complete TechLog migration evidence

docs/accessibility/manual-checklist.md

@@ -1,12 +1,11 @@
 # Manual accessibility review checklist
 
 Automated axe checks do not establish WCAG conformance. A human reviewer must
-review all six route records in `artifacts/tests/a11y-manual/` against one
-release candidate and sign them. The required scope is derived from the route
-registry: `APP_HOME`, `EXAMPLES_UI`, `EXAMPLES_STATES`, `EXAMPLES_AUTH`,
-`REFERENCE_RESOURCE_LIST`, and `NOT_FOUND`. Copy the template fields exactly; the
-gate rejects blank identity/timestamp/signature fields, pending verdicts,
-mismatched release IDs, or missing routes.
+review all 27 route records in `artifacts/tests/a11y-manual/` against one
+release candidate and sign them. The required TechLog Public and Studio scope is
+derived from the installed route registry, so the gate rejects stale, missing,
+or additional route records as well as blank identity/timestamp/signature
+fields, pending verdicts, and mismatched release IDs.
 
 Allowed item verdicts:
 
@@ -17,7 +16,7 @@ Required record:
 
 ```text
 Status: reviewed
-Route ID: APP_HOME
+Route ID: <exact installed route ID>
 Release ID: <immutable release ID>
 Reviewer: <human reviewer identity>
 Reviewed at: <RFC 3339 timestamp>
@@ -45,7 +44,8 @@ The reviewer must verify:
 - M7: non-essential motion is suppressed with reduced-motion preference
 - Screen reader: headings, live regions, errors, and actions are announced once
 
-`EXAMPLES_UI` requires real M4 modal and M5 field-error review; those items must
-not be marked not-applicable on that route. Passing automated evidence means
+Routes with dialogs or form errors require real M4 modal-focus or M5
+error-association review; those items must not be marked not-applicable when the
+reviewed route exposes the relevant behavior. Passing automated evidence means
 only that tested pages had no critical or serious axe findings under the
-recorded Chromium, Firefox, and WebKit runs.
+recorded browser runs.