Conformance blocker: complete Python SDK parity coverage beyond smoke (#169)

Author: durable-workflow-ops

CHANGELOG.md

@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 ### Added
+- `durable-workflow-python-conformance` now exposes a host-evidence
+  composition contract and `--compose` mode so published-artifact runners can
+  turn raw observations into a complete Python parity result document before
+  evaluation.
 - `durable-workflow-python-conformance` now exposes the Python SDK
   published-artifact parity contract and evaluates host result documents,
   rejecting smoke-only evidence unless the official CLI path, cold first-user

CONFORMANCE.md

@@ -55,6 +55,20 @@ The package ships a machine-readable contract in
 runners use this contract to distinguish a Python worker smoke test from
 the full published-artifact property.
 
+Host runners should collect their published-artifact observations into the
+host-evidence shape exposed by:
+
+```bash
+durable-workflow-python-conformance --host-evidence --pretty
+durable-workflow-python-conformance --compose host-evidence.json --pretty > python-conformance-result.json
+durable-workflow-python-conformance --evaluate python-conformance-result.json --pretty
+```
+
+The composer materializes one row for every required scenario and capability.
+Rows with no recorded evidence are emitted as `not_covered`, preserving a
+non-passing result with focused gate failures instead of letting smoke-only
+evidence look complete.
+
 The result gate requires one result for every scenario below, all marked
 `pass`, before the Python SDK conformance property can pass:
 

README.md

@@ -269,13 +269,18 @@ host conformance runners:
 
 ```bash
 durable-workflow-python-conformance --manifest --pretty
+durable-workflow-python-conformance --host-evidence --pretty
+durable-workflow-python-conformance --compose host-evidence.json --pretty > python-conformance-result.json
 durable-workflow-python-conformance --evaluate python-conformance-result.json --pretty
 ```
 
 The evaluator rejects smoke-only evidence. A passing record must include the
 official CLI install/start/result path, cold first-user setup, concrete
 artifact versions, protocol traces, a no-PHP-assumption audit, and the complete
-Python capability table.
+Python capability table. Host runners can feed their raw published-artifact
+observations to `--compose`; omitted parity cells become explicit
+`not_covered` entries so the gate reports the remaining scenario or capability
+instead of accepting a smoke-only result.
 
 ## External payload storage