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

Author: durable-workflow-ops

CHANGELOG.md

@@ -7,6 +7,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 
 ### Added
+- `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
+  setup, protocol traces, no-PHP-assumption audit, concrete artifact versions,
+  and complete capability table are all present.
 - `Client.delete_namespace()` now exercises the namespace lifecycle cleanup
   control-plane surface and returns the server's per-table cleanup counts on
   `NamespaceDescription.deleted`.

CONFORMANCE.md

@@ -40,12 +40,42 @@ The fixtures in this repo are exercised today by:
 - `tests/test_replay.py`
 - `tests/test_golden_history_replay.py`
 - `scripts/check-cli-parity.py`
+- `durable-workflow-python-conformance --manifest`
 - the `cli-parity` job in `.github/workflows/ci.yml`
 
 These are the per-repo gates that already enforce the contract; the
 public conformance harness, when it lands, will read the same fixtures
 from this repo's declared paths.
 
+## Published-artifact Python parity contract
+
+The package ships a machine-readable contract in
+`durable_workflow.python_conformance` and exposes it through the
+`durable-workflow-python-conformance` console script. Host conformance
+runners use this contract to distinguish a Python worker smoke test from
+the full published-artifact property.
+
+The result gate requires one result for every scenario below, all marked
+`pass`, before the Python SDK conformance property can pass:
+
+- `published_artifact_install_only`
+- `official_cli_install_start_result_path`
+- `cold_first_user_setup`
+- `python_worker_registration`
+- `activity_backed_workflow_execution`
+- `workflow_result_surface`
+- `worker_restart_activity_and_signal_state`
+- `protocol_trace_capture`
+- `php_assumption_audit`
+- `capability_table_complete`
+
+A passing result must also record concrete artifact versions for
+`server`, `cli`, `sdk-python`, `workflow`, and `waterline`; run
+timestamps; protocol traces; a no-PHP-assumption audit; and the complete
+capability table. Any omitted scenario, placeholder artifact version,
+runner-blocked cell, unsupported public surface, or non-pass scenario
+without linked findings is nonconforming.
+
 ## Release gate
 
 A release of `durable_workflow` (PyPI) must produce a passing harness
@@ -56,7 +86,7 @@ result document before tag, with the conformance level at `full` or
 | --- | --- |
 | Required claimed targets | `official_sdk`, `worker_protocol_implementation` |
 | Required suite version | `PlatformConformanceSuite::VERSION` (currently `8`, mirrored at `/platform-conformance-contract.json`) |
-| CI job | `platform-conformance` (lands when the harness reference implementation publishes; until then `cli-parity` and `test_history_event_contract.py` cover the same ground) |
+| CI job | `platform-conformance` (lands when the harness reference implementation publishes; until then `cli-parity`, `test_history_event_contract.py`, and `durable-workflow-python-conformance --evaluate` cover the same ground) |
 | Block on `nonconforming` | yes |
 | Artifact attached to release | harness result document, schema `durable-workflow.v2.platform-conformance.result` |
 

README.md

@@ -262,6 +262,21 @@ bundle simulation does not execute workflow code in Python, a clean
 integrity-only simulation recommends `review_before_promote` rather than
 `safe_to_promote`.
 
+## Python conformance gate
+
+The package includes the Python SDK published-artifact parity contract used by
+host conformance runners:
+
+```bash
+durable-workflow-python-conformance --manifest --pretty
+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.
+
 ## External payload storage
 
 Large payload offload is opt-in. `serializer.external_storage_envelope(...)`

pyproject.toml

@@ -59,6 +59,7 @@ Issues = "https://github.com/durable-workflow/sdk-python/issues"
 [project.scripts]
 durable-workflow-replay-verify = "durable_workflow.replay_verify:main"
 durable-workflow-history-bundle-verify = "durable_workflow.history_bundle_verify:main"
+durable-workflow-python-conformance = "durable_workflow.python_conformance:main"
 
 [tool.setuptools.packages.find]
 where = ["src"]

scripts/smoke-built-package.py

@@ -89,6 +89,7 @@ def completed(result):
     "durable_workflow.external_task_result",
     "durable_workflow.invocable",
     "durable_workflow.metrics",
+    "durable_workflow.python_conformance",
     "durable_workflow.retry_policy",
     "durable_workflow.serializer",
     "durable_workflow.sync",