Problem
The current protocol catalog and the active Platform Conformance fixture publish durable-workflow.v2.worker-protocol-api@catalog-16 with different bytes. The catalog URL serves the lifecycle-neutral release-candidate wording, while the conformance fixture resolver still pins an older copy that describes responses as Durable Workflow 2.0 beta responses. Readers who move from Platform Protocol Specs to its immediate Platform Conformance neighbor therefore encounter the obsolete lifecycle signal, and machine consumers cannot treat the shared artifact identity as a unique byte authority.
Acceptance criteria
- Advance the Workflow-owned conformance authority and its docs projection so the active worker-protocol fixture resolves lifecycle-neutral OpenAPI bytes. If the prior binding must remain immutable history, retain it under an explicitly historical identity and introduce a new current artifact/catalog or suite identity instead of serving divergent bytes under
@catalog-16.
- Ensure the current protocol catalog and active conformance manifest do not publish different content under the same public artifact identity; every resolver hash must validate against the bytes it names.
- Keep the protocol version at
1.13 and preserve all wire shapes and behavior.
- Keep stable 1.x as the default docs line and describe 2.0 only as a prerelease; do not imply a stable 2.0 release.
- Keep the Platform Protocol Specs and Platform Conformance pages connected in a coherent consumer path whose current links resolve to the current lifecycle-neutral authority, while historical evidence remains clearly historical.
- Validate OpenAPI structure, public identity, and resolver hashes without making exact prose or heading text a brittle test contract.
Delete when
Delete when the current catalog and active conformance authority resolve one unambiguous lifecycle-neutral worker-protocol artifact identity, all public hashes and routes validate, and any older beta-worded evidence is exposed only as explicit history.
Required source targets
durable-workflow/durable-workflow.github.io@main
durable-workflow/workflow@v2
Problem
The current protocol catalog and the active Platform Conformance fixture publish
durable-workflow.v2.worker-protocol-api@catalog-16with different bytes. The catalog URL serves the lifecycle-neutral release-candidate wording, while the conformance fixture resolver still pins an older copy that describes responses as Durable Workflow 2.0 beta responses. Readers who move from Platform Protocol Specs to its immediate Platform Conformance neighbor therefore encounter the obsolete lifecycle signal, and machine consumers cannot treat the shared artifact identity as a unique byte authority.Acceptance criteria
@catalog-16.1.13and preserve all wire shapes and behavior.Delete when
Delete when the current catalog and active conformance authority resolve one unambiguous lifecycle-neutral worker-protocol artifact identity, all public hashes and routes validate, and any older beta-worded evidence is exposed only as explicit history.
Required source targets
durable-workflow/durable-workflow.github.io@main
durable-workflow/workflow@v2