[cross-repo from server#312] Conformance blocker: expand replay coverage beyond current smoke (#643)

Author: durable-workflow-ops

docs/architecture/platform-conformance-suite.md

@@ -17,7 +17,7 @@ The machine-readable mirror of this document is
 `Workflow\V2\Support\PlatformConformanceSuite`, exported by the
 standalone `workflow-server` from `GET /api/cluster/info` under
 `platform_conformance_suite`. Schema:
-`durable-workflow.v2.platform-conformance.suite`, version `3`.
+`durable-workflow.v2.platform-conformance.suite`, version `5`.
 
 ## Why one suite
 
@@ -89,8 +89,9 @@ they become required when promoted to `stable` in a later suite version.
 The `signal_query_runtime_contract` category is stable and load-bearing.
 It must run against published install channels only, pin the resolved
 artifact versions in the result, and name every required scenario as
-passed, failed, or unsupported with a linked finding. A smoke-only run is
-nonconforming even if the covered smoke scenarios pass.
+`pass`, `fail`, `unsupported`, `not_covered`, or `runner_blocked` with a
+linked finding. A smoke-only run is nonconforming even if the covered
+smoke scenarios pass.
 
 Required scenarios:
 
@@ -132,8 +133,9 @@ Required scenarios:
 The `history_replay_bundles` category is also stable and load-bearing.
 It must run against published install channels only, pin the resolved
 artifact versions in the result, and name every required replay scenario
-as passed, failed, or unsupported with a linked finding. A smoke-only
-run is nonconforming even when the smoke path passes.
+as `pass`, `fail`, `unsupported`, `not_covered`, or `runner_blocked` with
+a linked finding. A smoke-only run is nonconforming even when the smoke
+path passes.
 
 Required scenarios are published in the public replay scenario manifest
 at `static/platform-conformance/replay-runtime-scenarios.json` and
@@ -179,11 +181,13 @@ emits a structured result. The rules below are normative.
    release does not conform.
 
 5. **Stable runtime scenario coverage.** A stable runtime category such
-   as `signal_query_runtime_contract` or `history_replay_bundles` passes
-   only when every scenario it declares records a pass, fail, or
-   unsupported result with resolved artifact versions and linked
-   findings. A smoke-only subset or omitted scenario is nonconforming,
-   not provisional.
+   as `signal_query_runtime_contract` or `history_replay_bundles` must
+   report every scenario it declares with one of the statuses published
+   by its runtime scenario manifest: `pass`, `fail`, `unsupported`,
+   `not_covered`, or `runner_blocked`. Full conformance requires every
+   required scenario to pass. A smoke-only subset, omitted scenario,
+   unsupported public surface, uncovered cell, or runner-blocked cell is
+   nonconforming and must link the owning finding.
 
 6. **Provisional categories warn but do not fail.** A failed fixture in
    a provisional category emits a warning in the harness output. A

src/V2/Support/PlatformConformanceSuite.php

@@ -29,7 +29,7 @@ final class PlatformConformanceSuite
 {
     public const SCHEMA = 'durable-workflow.v2.platform-conformance.suite';
 
-    public const VERSION = 3;
+    public const VERSION = 5;
 
     public const RESULT_SCHEMA = 'durable-workflow.v2.platform-conformance.result';
 
@@ -408,7 +408,7 @@ private static function passFailRules(): array
                 'rule' => 'A release that claims a target must pass every required fixture category for that target. One failed required fixture means the release does not conform for that target.',
             ],
             'stable_runtime_scenario_coverage' => [
-                'rule' => 'A stable runtime fixture category passes only when every required scenario it declares records a pass, fail, or unsupported result with artifact versions and linked findings. A smoke-only subset or omitted scenario is nonconforming, not provisional.',
+                'rule' => 'A stable runtime fixture category must report every required scenario it declares with one of the statuses published by its runtime scenario manifest: pass, fail, unsupported, not_covered, or runner_blocked. Full conformance requires every required scenario to pass. A smoke-only subset, omitted scenario, unsupported public surface, uncovered cell, or runner-blocked cell is nonconforming and must link the owning finding.',
                 'applies_to_categories' => [
                     'signal_query_runtime_contract',
                     'history_replay_bundles',

tests/Unit/V2/PlatformConformanceSuiteTest.php

@@ -28,7 +28,7 @@ public function testManifestAdvertisesAuthorityIdentity(): void
         $manifest = PlatformConformanceSuite::manifest();
 
         $this->assertSame('durable-workflow.v2.platform-conformance.suite', $manifest['schema']);
-        $this->assertSame(3, $manifest['version']);
+        $this->assertSame(5, $manifest['version']);
         $this->assertSame(
             'https://github.com/durable-workflow/workflow/blob/v2/docs/architecture/platform-conformance-suite.md',
             $manifest['authority_doc'],
@@ -362,6 +362,16 @@ public function testPassFailRulesNameTheCoreContract(): void
             $rules['stable_runtime_scenario_coverage']['applies_to_categories'],
             'smoke-only replay coverage must not satisfy the stable runtime category',
         );
+        $this->assertStringContainsString(
+            'not_covered',
+            $rules['stable_runtime_scenario_coverage']['rule'],
+            'omitted runtime scenario cells must be representable without appearing green',
+        );
+        $this->assertStringContainsString(
+            'runner_blocked',
+            $rules['stable_runtime_scenario_coverage']['rule'],
+            'environment-blocked runtime scenarios must be distinct from product pass/fail evidence',
+        );
     }
 
     public function testHarnessContractRequiresStructuredResultDocument(): void