Assert runtime lifecycle in conformance export

docs/eve-migration-roadmap.md

@@ -280,6 +280,13 @@ Exit criteria:
 
 Recently cut:
 
+- Runtime-owner conformance consumption now asserts EveUnity lifecycle stage
+  evidence directly. The generic consumer supports
+  `--expect-runtime-lifecycle-status` and
+  `--expect-runtime-lifecycle-pending`; the runtime-owner smoke verifies the
+  Unity UI Toolkit release/test/capture statuses plus the tagged UPM release,
+  batchmode runner, and capture artifact pending proofs from the exported
+  runtime record.
 - Plugin manifests and advertisements now carry a runtime-independent sidecar
   ABI boundary. Sai, Norn, and TeX declare `invocationModel:
   executable-sidecar`, `gamecult.eve.plugin_abi.v1`, CultMesh/stdio transports,

docs/parity-testing-harness.md

@@ -115,7 +115,9 @@ The runtime conformance pack is evidence-shaped, not fixture-shaped. Its
 `packs/runtime.json` document includes `runtimeTargets` so runtime repos can
 consume status, supported features, plugin support, command schema, lifecycle,
 capture status, and missing evidence without reading Eve's local parity
-manifest.
+manifest. The runtime-owner consumer smoke asserts EveUnity lifecycle stage
+status and pending release/test/capture proofs from the exported runtime record,
+so split blockers stay machine-readable instead of hiding in handoff prose.
 
 After generating the parity report, `run-parity-harness.ps1` copies
 `artifacts/conformance/latest` into