2.7.0

Adds optional execution tracing and scoped log correlation for workflow tasks and activity attempts. Applications own providers, propagators, sampling and exporters; the default installation does not require OpenTelemetry. Carrier propagation requires an actually advertised Server capability. Servers without that capability still support independent task/attempt traces.

This release also includes durable request IDs for signals and updates from #180 and preserves the existing entry-safety contract. No initial receipt RPC or longer lease is introduced by telemetry.

Normal protected publication and canonical PyPI installation pass. A normal installed consumer against immutable Server 2.9.11 passes through two independent workers, preserving the result/request ID and restoring scope. All 36 production modules match the release before and after execution. The default no-API installation also passes. Server 2.9.11 does not advertise carrier support, so this receipt does not establish durable caller propagation. The initial index-convergence publication failure and initial probe expectation failure remain recorded; the unchanged publisher and corrected probe subsequently pass.

See the execution telemetry guide and #182. Complete Server and cross-SDK delivery remains tracked in Workflow #773.

Full changelog.