fix(sdk): link resumed polling operations correctly

[zhongkechen]

Fixes #963.

A resumed wait-for-condition operation omitted its link to the initial operation segment, while its first polling attempt received that link even though it was not a continuation. This broke cross-invocation navigation and the existing invocation-view case-9 contract.

Use the same continuation links as other replayed STEP/CONTEXT operations: initial operation, then Workflow. Each attempt keeps its operation parent and links only to Workflow. Preserve IDs, sampling, checkpoints, replay behavior and plugin APIs.

Validation: explicit/global-provider regressions reproduce the two incorrect link shapes before the fix. The unchanged public local wait-for-condition handler succeeds with result 2; all shared case-9 telemetry assertions pass on its seven exported spans. Full OTel tests, ESM/CJS/type builds and Biome pass; existing conformance assertions are unchanged. Pin the requirements to published shared revision a628f5589bbf067a441696c792ab3023c0d0899b, matching the reusable workflow and its current continuation-link contract; this revision contains cases 1–20 and requires no companion handler changes. Deployed cross-SDK validation is coordinated in #960.

This branch carries the separately reviewed CI deployment repair from #959; merge #959 first, then update this branch from main to remove that shared diff. The live-clock correction is tracked separately in #962.

Shared CI prerequisites include the validated callback/promise-any history test corrections from #959; independently delivered wakeups change invocation grouping, while operation counts and final outcomes remain strict.

[github-actions]

Codex AI review

No actionable findings. Residual risk: tests were not executed, and the newly pinned external conformance revisions could not be inspected under the review constraints.

Reviewed commit 101779cdf0c09af07dfd11126ab93177fa29168c. Workflow run