Kenton Varda

This commit **fixes a Windows build issue** within the **`workerd/server` alarm scheduling mechanism**. It addresses a problem with evaluation order during alarm insertion by introducing an explicit actor reference in the `loadAlarmsFromDb` function. This **bug fix** ensures that `workerd` can be successfully compiled and run on Windows platforms, resolving a critical cross-platform compatibility problem related to alarm scheduling.

This commit **reverts** a previous change, thereby **restoring the original behavior** where calling `abortAllDurableObjects()` (or `abortAllActors`) **does not delete all scheduled alarms** for Durable Objects. It removes the `deleteAllAlarms` function from the **Durable Objects alarm scheduling system** within `src/workerd/server/alarm-scheduler.c++` and `src/workerd/server/alarm-scheduler.h`, along with its invocation in `src/workerd/server/server.c++`. This **maintenance** change ensures that Durable Object alarms will now persist even if all Durable Objects are aborted, significantly impacting their lifecycle management. The associated test case `test_abort_all_durable_objects_alarms` and its setup in `src/workerd/server/tests/unsafe-module/` are also removed.

This commit performs **documentation maintenance** by updating the project's primary `README.md` file. It **removes an outdated beta warning**, signifying the project's maturity beyond a beta phase. Additionally, the commit **removes the code coverage section** to keep the top-level documentation concise and **tweaks other sections** for improved clarity and relevance. This refinement ensures the `README.md` provides current and essential information to users, improving the initial onboarding experience.

This commit introduces and **enforces new limits** on **Durable Object facet names** and their **nesting depth** within the **Workerd** runtime. Specifically, facet names are now capped at **256 characters**, and the maximum nesting depth, including the root, is set to **4**. This **feature enhancement** modifies the `DurableObjectFacets` methods in `src/workerd/api/actor-state.c++` to validate these constraints, and adds a `getDepth` method to the `Worker::Actor` interface and `Server::WorkerService` to support depth calculation. The change aims to improve system robustness and prevent excessive resource usage by imposing reasonable boundaries on facet structure. New test cases in `src/workerd/server/server-test.c++` validate the correct enforcement of these new limits.

This commit **introduces a new method**, `getType()`, to the `IoChannelCapTableEntry` class within the **I/O channel management subsystem**. This **enhancement**, defined in `src/workerd/io/io-channels.h`, allows internal components to **retrieve the specific type of an I/O channel entry**. The addition of `IoChannelCapTableEntry::getType()` provides a new capability for introspection, enabling other parts of the codebase to query channel types directly. This change is a targeted **feature addition** to satisfy a specific internal dependency.

This commit introduces a **new capability** by adding the `WorkerLoader::load()` method to the **`workerd` API**, providing a simplified way to instantiate one-off workers directly from code. This method streamlines the creation of temporary worker instances, offering a direct alternative to `LOADER.get(null, () => code)`. To ensure correct behavior when the worker loading callback is invoked multiple times, significant **refactoring** was undertaken to implement `clone()` methods across various **worker source structures** within `src/workerd/io`, such as `DynamicWorkerSource` and `WorkerSource`, enabling robust refcounting. This enhancement simplifies worker instantiation while maintaining internal consistency and resource safety, with new tests verifying its functionality.

This commit **refactors** the **`worker-loader` API** within `workerd` by extracting the conversion logic from `WorkerCode` to `DynamicWorkerSource` into a new, dedicated helper function named `toDynamicWorkerSource`. This change improves code organization and maintainability in `src/workerd/api/worker-loader.c++`, as the `get` method now leverages this helper for preparing worker sources. This is a pure internal code move, ensuring no functional impact on how workers are loaded or executed.

Update capnproto with HTTP CVE fixes.

This commit **adds documentation** for **tail worker support** within the **`worker-loader` binding**, specifically updating the `src/content/docs/workers/runtime-apis/bindings/worker-loader.mdx` file. It details how developers can leverage tail workers to observe critical debug information such as `console.log()`s, errors, and metrics from their loaded workers. The update also includes information regarding the `WorkerEntrypoint` class, providing comprehensive guidance for this feature. This **documentation enhancement** significantly improves the developer experience by clarifying how to effectively debug and monitor `worker-loader` instances.

This commit **updates documentation** for the **Workers** subsystem by adding a new page for the `rpc_params_dup_stubs` **compatibility flag**. The new documentation clarifies the flag's purpose and its impact on **RPC stub ownership semantics**. This **maintenance** task ensures developers have a clear understanding of how this flag affects **RPC parameter handling**, improving clarity and reducing potential confusion for users interacting with the Workers runtime.

Fixes flakiness in `workerd`'s channel token tests by improving the byte corruption method. This is an isolated change to test utilities with no production impact.

Update Cap'n Proto to get CapabilityServerSet::tryGetLocalServerSync().

Adds a missing test case to `js-rpc-test` within `workerd` to ensure correct `e-order` behavior when embedding complex externals. This is an isolated change to test utilities with no production impact.

This commit introduces a new capability to the `workerd` runtime, specifically affecting its API and I/O mechanisms. It enables the serialization of `AbortSignal` via `ExternalPusher`, allowing cancellable operations to be propagated across external boundaries within the `workerd` environment.

This commit introduces a new capability within `workerd` by enabling `ReadableStream` serialization via `ExternalPusher`, affecting the streams API and core I/O layer. This allows for new patterns in handling and transferring stream data within the system.

This commit introduces foundational infrastructure for a new ExternalPusher mechanism within `workerd`'s RPC system, controlled by an autogate. This new capability lays the groundwork for future RPC protocols and will require coordinated rollout across services to enable.

This commit introduces a new `JsValue.ExternalPusher` interface within `workerd`'s core RPC and IO systems, establishing a foundational new capability for more efficient and simpler stream handling. This change sets the stage for a future architectural shift, intended to replace the existing `StreamSink` design and improve overall system performance and maintainability.

Affects `workerd`'s RPC system; a new compatibility flag changes how stub parameters are handled, preventing ownership transfer and instead duplicating them. This resolves an interoperability bug with Cap'n Web, ensuring correct stub lifetime management for cross-system communication.

Fixes a bug in the `workerd` server's channel token decoding, improving robustness when handling malformed or unusual channel tokens.

This commit fixes a rare but critical stability issue within the `workerd` I/O system, preventing V8 fatal errors caused by callbacks outliving their isolate. It also improves resource cleanup for `IoContext` callbacks.