Harris Hancock

This commit introduces a new **automation** for managing the `opencode-ai` dependency version across the project. A new Python script, `tools/update_opencode_version.py`, fetches the latest `opencode-ai` version from npm and updates the `opencode_version` field within all **Bonk workflow files**. This **maintenance** enhancement is integrated into the weekly `.github/workflows/deps-updater.yml` workflow, ensuring regular updates, and is also available for manual execution via `just update-opencode`. This streamlines dependency management for `opencode-ai`, with CI failures serving as a safeguard against incomplete or problematic dependency releases.

This commit implements a **multi-pronged fix** to prevent merge conflicts and stabilize CI workflows related to the **Bonk auto-reviewer** and **`opencode` integration**. It **pins the `opencode` version** to `1.2.27` across all Bonk workflows (`bigbonk.yml`, `bonk.yml`, `new-pr-review.yml`) to eliminate `package.json` modifications caused by version drift. Additionally, the **root `.gitignore` is updated** to permanently ignore auto-generated `opencode` artifacts like `.opencode/package.json` and `bun.lock`, and the auto-reviewer's token permissions are explicitly set to `NO_PUSH` in `new-pr-review.yml`. This comprehensive **bug fix** resolves issues with unexpected file changes in PRs and enhances the robustness of the CI/CD pipeline.

This change fixes module resolution failures within the `.opencode` tools by adding a missing dependency. It enables the `.opencode` tools to function correctly, resolving a critical issue that prevented their use.

This change permanently applies an 8 KiB external memory adjustment to all subrequests (fetch, Cache API, etc.) within IoContext, removing previous conditional logic. This ensures consistent resource allocation for these operations across the system.

This commit adds new tests to the `workerd` API test suite, specifically verifying the visibility of `logWarning()` messages in streaming tail workers. This is an isolated change to the test infrastructure, improving test coverage without affecting production code or behavior.

This fix significantly improves observability for the `workerd` runtime by ensuring `logWarning()` messages are correctly emitted to streaming tail workers and `--verbose` stderr. It resolves a silent warning suppression issue across various API modules, making previously hidden warnings visible.

This fix revives a critical warning in `workerd`'s HTTP body processing, ensuring that users are now correctly alerted when `FormData` is used with a custom `Content-Type` header. It also removes a problematic MIME type comparison operator, preventing potential future bugs in content type validation.

Affects all services utilizing concurrency-limited subrequests (e.g., fetch, KV, R2, Cache); centralizes and increases external memory adjustment when a specific autogate is enabled, impacting resource accounting and potential performance.

This is an isolated documentation update for the `jsg` module, clarifying the usage of `JSG_TRY` and `JSG_CATCH` for developers. It has no impact on runtime behavior or production systems.

This refactoring affects the internal exception handling of several Workerd API modules, migrating them to use new `JSG_TRY/JSG_CATCH` macros. This is an internal code consistency improvement with no expected change in external behavior or downstream impact.

This commit introduces new exception handling macros (JSG_TRY/JSG_CATCH) within the JSG subsystem, providing a cleaner syntax for converting JavaScript and KJ exceptions to `jsg::Value`. This is a significant new capability that improves developer experience for JSG code and lays the groundwork for future coroutine support.

This commit **updates the documentation** by adding a new entry to the **Workers release notes**. Specifically, it records the **V8 version 14.5 update** in the `src/content/release-notes/workers.yaml` file. This **maintenance task** ensures that users are informed about the underlying engine changes affecting the **Workers platform**. The update provides transparency regarding the platform's evolution and is a crucial part of the **release process**.

Affects `workerd` services utilizing `fetch()`; this change, controlled by an autogate, increases the estimated external memory overhead for `fetch()` operations, leading to more accurate memory accounting and potentially improved resource stability.

This is an isolated change to a test utility that enforces compatibility dates to fall on mid-week workdays. It prevents future operational issues by ensuring better team availability for default behavior changes, with no direct production impact.

This commit primarily **updates documentation and release notes** for the **Workers and Durable Objects** platforms, detailing several recent enhancements. It documents the **V8 runtime update to version 14.2**, significant **JSON.parse() optimization**, and the new behavior where **console warnings are now routed to tail Workers**, improving observability. Crucially, it highlights the **increased WebSocket message size limit from 1 MiB to 32 MiB**, impacting both Workers and Durable Objects utilizing WebSocket communication. This **maintenance update** ensures users are informed of these **performance improvements, debugging enhancements, and expanded platform capabilities**.

Removes an autogate for the 32MB WebSocket message size limit within the `workerd` runtime. This is a cleanup and stabilization change, as the feature has already been fully rolled out to production, signifying its permanent enablement.

This commit reverts a previous change to the `workerd` HTTP API's handling of body input streams, restoring its prior behavior. The impact depends on what the original change addressed, potentially reintroducing a bug or removing a new capability related to HTTP request body processing.

This change significantly increases the maximum WebSocket message size limit to 32MiB, directly impacting all services and clients that utilize WebSockets by enabling much larger data transfers. It introduces a new capability that will be rolled out gradually via an autogate.

This change removes obsolete code from Workerd's Pyodide integration and JavaScript Glue (JSG) system. It is an internal cleanup that improves maintainability and reduces technical debt, with no impact on current functionality or external systems.

This is an isolated documentation update to `v8-updates.md`, clarifying information for users or developers. It has no production impact.