Tracking: complete review-leaf coverage (one al-*-review per domain) #81

Goal — part of: complete the review skills

al-code-review composes one al-<domain>-review leaf per knowledge domain. This tracks that every domain — existing and future — has a matching review leaf. The structural R26 check enforces set-equality between the review folder's leaves and al-code-review's sub-skills registry, so every new leaf must be registered there.

Domains with a review leaf today (11) ✅

breaking-changes, error-handling, events, interfaces, performance, privacy, security, style, ui, upgrade, web-services

Open now — knowledge exists, leaf missing

• appsource — Add al-appsource-review leaf (wire into al-code-review) #70
• data-modeling — Add al-data-modeling-review leaf (wire into al-code-review) #72
• testing — tracked in Expand the testing domain (currently 1 file) into full AL test-authoring knowledge + test skills #39 (al-test-review)

Future — add the leaf when the domain's knowledge lands

• telemetry (knowledge Add a telemetry domain (signal emission + KQL), distinct from the privacy rules #37)
• functional domains — Finance / SCM / … (knowledge Add BC functional-domain knowledge and a standard application-object reference #35, pilot Add source-verified Finance knowledge and review domain #57)
• PowerShell + pipelines (knowledge Add pipeline/automation knowledge: PowerShell (BcContainerHelper) and AL-Go for GitHub #38) — review target is YAML/PS, may need a distinct shape
• power-platform (knowledge Add Power Platform integration knowledge domain #69)

Each leaf

• inputs: [pr-diff], outputs: [findings-report]; sources its microsoft/knowledge/<domain>/ folder; findings carry references[] back to the articles.
• Registered in al-code-review sub-skills (R26 set-equality). Validators green (0/0; index PASSED).

Part of the Epic (roadmap umbrella).