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

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 --compose` now accepts nested host
+  runner evidence tables, resolved artifact/source aliases, boolean `passed`
+  result cells, nested protocol trace planes, and no-PHP audit check aliases
+  when composing full published-artifact Python conformance results.
 - `durable-workflow-python-conformance --compose` now normalizes runbook-style
   scenario and capability identifiers such as `server-up` and
   `result-returned`, plus common status, trace-plane, and no-PHP audit aliases,

CONFORMANCE.md

@@ -77,6 +77,10 @@ accepted as input to the composer; they are normalized into the canonical
 result fields before evaluation. Scenario and capability IDs may use the
 canonical snake_case names or the runbook-style hyphenated names such as
 `server-up`, `python-worker-connects`, and `result-returned`.
+Nested runner tables such as `capabilityTable.rows`, resolved artifact/source
+fields, boolean `passed` cells, nested `protocolTraces.controlPlane` /
+`protocolTraces.workerProtocol` captures, and no-PHP audit check aliases are
+also normalized before evaluation.
 For CLI result-path evidence, host runners should use the actual published
 CLI surfaces that return terminal workflow output: `workflow:start --wait`,
 `workflow:describe`, or `workflow:show-run --follow`.

README.md

@@ -282,8 +282,10 @@ 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. The composer accepts canonical
 snake_case IDs and runbook-style hyphenated IDs such as `server-up` and
-`result-returned`. CLI result-path evidence should come from the actual
-published commands that return terminal workflow output: `workflow:start --wait`,
+`result-returned`, nested runner tables, resolved artifact/source aliases,
+boolean `passed` cells, nested protocol trace planes, and no-PHP audit check
+aliases. CLI result-path evidence should come from the actual published
+commands that return terminal workflow output: `workflow:start --wait`,
 `workflow:describe`, or `workflow:show-run --follow`.
 
 ## External payload storage