Add UI knowledge: notification recall Id and Page Management document routing

Two ui articles with compiled good/bad samples:
- notification-recall-needs-known-id: a notification that the code also
  recalls needs a fixed Id (single instance; recall before re-send) or
  per-record tracking through codeunit "Notification Lifecycle Mgt."
  (SendNotification[WithAdditionalContext] / RecallNotificationsForRecord,
  HandleDelayedInsert semantics). Never-recalled notifications are exempt.
- list-page-document-routing-uses-page-management: open documents from a
  mixed-type list with PageManagement.PageRun(Rec) instead of a hand-written
  case "Document Type" / Page.Run; register new tables through
  OnConditionalCardPageIDNotFound. Single-type opens and tables Page
  Management does not route are exempt.

Wired into al-ui-review (entry gate now covers notification send/recall
outside pages, tokens, high-signal mappings) and registered both pairs in
the ui review-fixtures override.

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

evaluation/review-fixtures.json

@@ -165,7 +165,9 @@
         "default-descending-sort-on-historical-pages",
         "page-design-must-match-bc-page-type-conventions",
         "page-client-expression-must-not-use-in-list",
-        "rolecenter-permission-gating-must-use-accessbypermission"
+        "rolecenter-permission-gating-must-use-accessbypermission",
+        "notification-recall-needs-known-id",
+        "list-page-document-routing-uses-page-management"
       ]
     },
     "upgrade": {