Let WorkflowEnvironment mock Nexus service calls #198

Delivered in Python SDK 2.10.0

WorkflowEnvironment supports canned and callable Nexus operation mocks and typed failure delivery.

PyPI 2.10.0 is published at exact qualified source 4f853f396dba5a530ef0815509b16bfddaa9ebc3. Normal registry acceptance passes 334 controls, all 37 source files and all 50 hashed RECORD entries. Docs #212 merged at e530e33ec1303530779f91a0d249666c9f9aca16; its actual Pages deployment and all five affected routes were verified at 16:09 UTC. Current guidance states the minimum version.

Earlier failed observations remain failed. Separate #175/#215 source is outside this release.

Original report and earlier qualification

Current package delivery gate — October 23

The complete 2.10.0 candidate is 4f853f396dba5a530ef0815509b16bfddaa9ebc3, merged as 38b5a639262bebcf3fd0e67c6ec42ab16bc3a966 with the same tree. Fresh exact artifact hashes and installation proof: all 17 applicable normal gates, both distributions' smoke/metadata checks, 37 installed source/RECORD matches, 272 controls and actual console acceptance/refusal pass. The earlier 12b5f372 proof remains its own retained earlier cohort; the complete new candidate supersedes it only after all fresh proof passed.

Untagged and unpublished: existing #197 Trusted Publisher account setup remains required. No token fallback or repeated human account request. Actual registry installation and consumer acceptance remain open; draft #212 prepares versioned guidance and stays draft until those real delivery gates pass. Security-only 2.9.1/2da02a7a remains separate. No protocol-floor, major or automatic runtime/Cloud adoption follows.

Problem

WorkflowEnvironment can't run a workflow that calls a Nexus service operation, so that workflow can't be unit-tested. The Python guide says the harness dispatches yielded commands against registered mocks, but there is no mock for service calls.

• Workflow code calls ctx.call_nexus_service or ctx.start_nexus_operation, which yield a NexusServiceCall.
• The harness handles activities, timers, children, side effects, search attributes and version markers and raises TypeError for anything else.
• Its mock registration covers activities and child workflows only.

Reproduced on published 2.9.0. A workflow that yields ctx.call_nexus_service("billing", "invoices", "create", ["a"]) makes execute_workflow raise TypeError: unsupported command in test harness: NexusServiceCall(...).

Acceptance criteria

• Tests can register a result, or a callable, for a service operation by endpoint, service and operation name, and the workflow receives it the way a real call resolves.
• Tests can make a mocked operation fail, and workflow code sees the same failure type a real failed operation produces.
• An unmocked service call fails with a message that names the endpoint, service and operation and says how to register a mock.
• The Python guide's testing section shows mocking a service call.

Current delivery state

Source delivered through PR #204, merged at fdde735c53e5bf2cf8a509a8d29a7c1a86ec7874 on October 23 at 09:18:53 UTC. Its tree exactly matches candidate caf853ac; all 18 normal checks pass, including supported Python versions, actual integration and target qualification. Final Sonar has zero OPEN/CONFIRMED findings. The completed remote head is deleted and independently absent.

Result and synchronous callable mocks are keyed by endpoint/service/operation. Production replay delivers completion, acceptance or NexusOperationFailed; guidance covers typed failure and compensation, with real-Server limits. Original 18 failures and exact parent/local qualification remain in the delivery record.

Remaining: compatible publication and normally installed acceptance after the existing #197 Trusted Publisher account setup. Source guidance explicitly marks these APIs unreleased; remove that notice only after publication. Fresh-main CI 39930960615 is independent and currently pending. No package version or tag has changed.