mar-cf

This commit introduces **user span context propagation**, a **new capability** that ensures the trace context of user-defined spans is correctly carried across various execution boundaries within Workerd. It modifies **actor-state, HTTP subrequest, and I/O channel mechanisms** to pass `userSpanParent` or `traceId` through internal calls, such as `newSingleUseClient` and `startRequest`. The **tracing infrastructure** is updated to support this propagation, including refactoring `SpanContext` and `Tracer` components, and a new `AutogateKey` is added. This enables **end-to-end tracing for user-defined spans** across complex workflows, significantly enhancing **observability** and is verified by new **tail worker tests**.

This revert restores the previous behavior for JavaScript property handling within the `workerd` runtime, undoing changes to V8's `hasOwnProperty` and `resource.h`. This rollback likely addresses an issue or instability introduced by the original change.

This commit provides a **bug fix** by **refactoring lock acquisition** in two critical Workerd components to ensure **proper and safe lock handling**. Specifically, it addresses issues within the **CPU limit enforcer** by correcting lock acquisition for the `getCpuLimitNearlyExceededCallback` in `src/workerd/io/worker.c++`. Concurrently, it fixes lock handling for the `cache` within the `find` method of the **JavaScript compilation cache** in `src/workerd/jsg/compile-cache.c++`. By assigning exclusive locks to local variables, this change prevents potential race conditions and improves the **stability and correctness** of these core Workerd subsystems.

This is an isolated internal refactoring within the `HibernatableWebSocketCustomEvent` API in Workerd, extracting a helper function to improve code organization. It has no impact on external behavior or downstream services.

Isolated change to a comment in `CustomEvent::getEventInfo()` within `worker-interface.h`; this has no functional impact on the system.

Affects the `workerd` runtime's internal tracing system; this fix ensures tracing event information is accurately captured for requests, improving diagnostic capabilities.

This is an isolated internal fix within `workerd`'s I/O and worker entrypoint logic. It refines the management of worker tracers by correctly marking them unused for undelivered requests and avoiding redundant marking for duplicate alarms, improving internal resource cleanup without external impact.

This commit refactors the `workerd` I/O tracer module to periodically log warnings. This is an isolated internal change to improve observability and manage log output, with no direct impact on external functionality.

This fix resolves partial failures in `workerd`'s span reporting when actors abort with pending `waitUntil` tasks. It ensures more reliable and complete tracing data for requests, enhancing observability in complex asynchronous scenarios.

This change affects the `WorkerTracer` component within `workerd/io`, suppressing a warning for duplicate alarm requests. It's an isolated change to diagnostics, reducing log noise without altering core `workerd` functionality or user-facing behavior.

This is an isolated change within the Workerd tracing system, specifically adjusting how a span time warning is reported. It prevents this particular warning from being sent to Sentry, reducing noise in error monitoring without affecting core tracing functionality.

This commit fixes an internal unfulfilled promise error within `workerd`'s `worker-rpc` and `trace-stream` components, preventing crashes or unexpected behavior when `CustomEvent` objects are destroyed early.

Fixes an issue within `workerd`'s I/O tracing module, enabling proper 'tail stream capability drop' functionality. This improves the stability and correctness of `workerd`'s internal tracing streams.

This is an isolated fix within Workerd's R2 bucket API, resolving an internal issue with error type tagging. It has no direct user-facing impact.

Isolated change to test utilities; no production impact.

This commit fixes a robustness issue within `workerd`'s I/O and tracing components by explicitly handling invalid states during tail stream event processing. This prevents potential errors or crashes related to event handling, improving system stability.

This is an internal refactor within `workerd`'s I/O tracing subsystem, optimizing the tail stream handler without user-visible impact.

This commit fixes an error handling issue within Workerd's JavaScript Gateway (JSG) setup, specifically addressing an invalid `deferDestruction` queue state. This improves the stability and robustness of Workerd's JSG component by correctly handling a specific error condition.

This change refactors span lifecycle management within Workerd's tracing API, improving the correctness and reliability of tracing data collection.

This commit reverts previous changes to internal Cloudflare D1 and Images APIs, along with modifications to the `workerd` runtime's tracing module. The significance is the removal of previously introduced functionality or modifications within these core internal systems.