Problem
The 2.0.0-rc.69 child-workflows published-artifact runner resolves every
exact public artifact, then stops before executing the runtime matrix. Its
synthetic workers call POST /worker/register at protocol 1.19 without the
required capability_manifest, and Server correctly rejects them with HTTP
422.
This is stale conformance-driver code, not evidence of a child-workflow product
failure. The same registration contract is already enforced by Server and
advertised by the released SDKs.
Acceptance
- The child-workflow runtime probe sends a complete structured refusal manifest
for local_activities, worker_sessions, and sticky_execution when its
synthetic workers do not advertise those capabilities.
- A focused source-contract test prevents this field from being omitted again.
- Relevant Server tests pass.
- The corrected immutable runner is executed against the unchanged frozen
2.0.0-rc.69 image and exact release tuple; a product release is not required
for a test-driver-only correction.
Tracks the release qualification in durable-workflow/.github#97.
Problem
The
2.0.0-rc.69child-workflows published-artifact runner resolves everyexact public artifact, then stops before executing the runtime matrix. Its
synthetic workers call
POST /worker/registerat protocol1.19without therequired
capability_manifest, and Server correctly rejects them with HTTP422.
This is stale conformance-driver code, not evidence of a child-workflow product
failure. The same registration contract is already enforced by Server and
advertised by the released SDKs.
Acceptance
for
local_activities,worker_sessions, andsticky_executionwhen itssynthetic workers do not advertise those capabilities.
2.0.0-rc.69image and exact release tuple; a product release is not requiredfor a test-driver-only correction.
Tracks the release qualification in durable-workflow/.github#97.