#204 Validate composed reviews against the expected leaf worklist
The findings-report validator gets an optional expected-composition manifest. It checks that selected leaves, versions, result order and legitimate skips match what the host chose. Duplicate producers are now rejected, and a composition with missing leaves must be reported as partial or failed instead of completed.
- 6files
- 2AL files
- 0objects
Pull request · merged into main on 2026-10-02 by demiliani · 6 files (+784 -26), 2 AL · feature · tier official · reviewed (checked by Opus)
What changed
- New optional -ExpectedCompositionPath checks super-skill and leaf IDs, versions, result order and skip reasons against a host-owned manifest
- Duplicate producers and duplicate or returned-and-skipped IDs are rejected even without a manifest
- Missing selected leaves require ‘partial’ if a non-failed report exists, otherwise ‘failed’; budget exhaustion is not turned into a configuration skip
- Coverage is the sum of non-failed leaf worklists and handles zero usable sub-results
- Report JSON schema is unchanged; manifest-free callers are still supported but cannot certify completeness
- Behaviour changes for users or extensions.
AL objects touched
microsoft/skills/review/al-code-review.md: modified, not in the BC? snapshotskills/do.md: modified, not in the BC? snapshot
Context
- Systems: development
Source: metadata of a merged pull request in microsoft/BCQuality (bcquality): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).