Strengthen split target conformance consumption

docs/eve-migration-roadmap.md

@@ -280,6 +280,13 @@ Exit criteria:
 
 Recently cut:
 
+- Split-target conformance consumption now verifies graduation state instead of
+  only split-target presence. The generic consumer supports
+  `--expect-split-target-status`, `--expect-split-target-blocker`, and
+  `--expect-split-target-proof`; the parity harness runs
+  `scripts/run-split-target-conformance-consumer-smoke.ps1`; and EveFlutter /
+  EveUnity consumers can now prove that the targets remain incubating for named
+  blockers while their current split-readiness proofs stay passed.
 - Runtime owner conformance consumption now verifies runtime target health
   instead of only runtime presence. The generic consumer supports
   `--expect-runtime-status`, `--expect-runtime-feature`,

docs/parity-testing-harness.md

@@ -120,6 +120,18 @@ That script runs the export consumer from `flutter/eve_parity` and asserts the
 runtime pack, Sai provider fixture, Flutter runtime targets, and `EveFlutter`
 split target without reading `tools/parity/parity-manifest.json`.
 
+Split-target consumer smoke:
+
+```powershell
+powershell -ExecutionPolicy Bypass -File .\scripts\run-split-target-conformance-consumer-smoke.ps1
+```
+
+That script asserts that EveFlutter and EveUnity are exported as incubating
+split targets, that their current split-readiness proofs are passed, and that
+their graduation blockers remain visible to consumers. A target being present
+is not enough; future owner repos must be able to consume why it is or is not
+ready to leave Eve incubation.
+
 The Flutter widget smoke also exercises `EveProviderCatalog` and
 `EveProviderPicker` against a conformance-export-shaped provider list. That is
 the runtime-side provider picker proof; it consumes provider entries and plugin