deps: bump the production-dependencies group with 3 updates

[dependabot]

Bumps the production-dependencies group with 3 updates: agents, hono and zod.

Updates agents from 0.22.0 to 0.23.0

Release notes

Sourced from agents's releases.

agents@0.23.0

Minor Changes

• #2193 87bd594 Thanks @​mattzcarey! - Extract facet ("sub-agent") machinery into packages/agents/src/dynamic-agents/, add the this.dynamicAgents capability facade, and reposition facets as an isolation primitive rather than the recommended way to model many chat sessions.

  Agent's facet routing, WebSocket forwarding, virtual connections, and registry (~2,400 of index.ts's ~12,150 lines) move into a dedicated module registered as a Lifecycle capability (capabilityId: "dynamic-agents"); its hot paths stay composition-root wired since the capability-runner hook contract can't express request-rewrite-and-continue or post-claim WebSocket forwarding. No wire- or storage-visible identifier changes.

  The public surface gains this.dynamicAgents.{get,abort,delete,has,list} plus the DynamicAgentClass and DynamicAgentStub type names. SubAgentClass and SubAgentStub remain as compatibility aliases. subAgent() / abortSubAgent() / deleteSubAgent() / hasSubAgent() / listSubAgents() are unchanged in behavior and now delegate to the same capability — @deprecated in place, not removed. /sub/ URLs, useAgent({ sub }), parentAgent(), and onBeforeSubAgent are untouched.

  docs/agents/sub-agents.md is rewritten: verified workerd facet semantics (separate isolate, own SQLite, no independent alarms, bounded nesting depth, machine-pinned tree), a corrected claim about WebSocket frame forwarding (every frame wakes the root parent — it was never true that frames go directly to the child post-upgrade), and an explicit decision rule for facets vs. independent Durable Objects. Two new examples: examples/next/dynamic-agents (a supervisor running user-submitted Durable Object code as facets via Worker Loader — what facets are for) and examples/next/chats (one top-level DO per chat plus a per-user push-based index — the recommended many-chats pattern), both with a React + Vite UI and workers-pool tests.

• #2175 8ffb3ad Thanks @​mattzcarey! - Lifecycle owns a durable job queue, driven as an alarm event loop.

  The thing in the queue is a job: a serialisable callback address — the owning capability plus a function name — with a due time and a payload. Capabilities and the host push jobs through the scoped jobs surface; Lifecycle drives due jobs in timestamp order when the alarm fires, owns dispatch retries and platform-failure deferral, arms a deadman pre-alarm before driving so an isolate death mid-drive still wakes the object, and derives the physical alarm purely from queue state (queue mutations re-arm automatically; an exclusive job suppresses ordinary candidates).

  class Cleanup extends LifecycleCapability {
    async scheduleSweep(time: number) {
      await this.lifecycle.jobs.push({ id: "sweep", fn: "sweep", time });
    }
    onJob({ job }: LifecycleJobContext) {
      // drive result: nothing = complete, { rescheduleAt } = suspend,
      // "yield" = leave due and wake again immediately
    }
  }

  The pull-based alarm-contribution model is removed: capability getNextAlarm()/onAlarm(), host getNextAlarm(), LifecycleServices.alarms (rearm/disabled), and AlarmContribution are gone. Host onAlarm() remains and runs once per alarm invocation after due jobs are driven. Terminal application failures reach the owner's onJobError(), whose drive result decides advancement.

  The alarm memory-limit circuit breaker (#1825) moves from Agent.alarm() into the Lifecycle event loop, targeting the exact executing job; Agent contributes domain policy through the new onAlarmMemoryLimit() host hook, and Scheduler's __DO_NOT_USE_WILL_BREAK__handleAlarmMemoryLimit escape hatch is gone. After recording a strike the breaker now finishes by resetting the isolate with ctx.abort(reason, { retryAlarm: false }) (retry of the handled alarm suppressed; the backoff alarm owns the next wake), and Agent.destroy() uses the same no-retry abort so a completed teardown's alarm cannot be retried into a fresh constructor that recreates

... (truncated)

Changelog

Sourced from agents's changelog.

0.23.0

Minor Changes

• #2193 87bd594 Thanks @​mattzcarey! - Extract facet ("sub-agent") machinery into packages/agents/src/dynamic-agents/, add the this.dynamicAgents capability facade, and reposition facets as an isolation primitive rather than the recommended way to model many chat sessions.

  Agent's facet routing, WebSocket forwarding, virtual connections, and registry (~2,400 of index.ts's ~12,150 lines) move into a dedicated module registered as a Lifecycle capability (capabilityId: "dynamic-agents"); its hot paths stay composition-root wired since the capability-runner hook contract can't express request-rewrite-and-continue or post-claim WebSocket forwarding. No wire- or storage-visible identifier changes.

  The public surface gains this.dynamicAgents.{get,abort,delete,has,list} plus the DynamicAgentClass and DynamicAgentStub type names. SubAgentClass and SubAgentStub remain as compatibility aliases. subAgent() / abortSubAgent() / deleteSubAgent() / hasSubAgent() / listSubAgents() are unchanged in behavior and now delegate to the same capability — @deprecated in place, not removed. /sub/ URLs, useAgent({ sub }), parentAgent(), and onBeforeSubAgent are untouched.

  docs/agents/sub-agents.md is rewritten: verified workerd facet semantics (separate isolate, own SQLite, no independent alarms, bounded nesting depth, machine-pinned tree), a corrected claim about WebSocket frame forwarding (every frame wakes the root parent — it was never true that frames go directly to the child post-upgrade), and an explicit decision rule for facets vs. independent Durable Objects. Two new examples: examples/next/dynamic-agents (a supervisor running user-submitted Durable Object code as facets via Worker Loader — what facets are for) and examples/next/chats (one top-level DO per chat plus a per-user push-based index — the recommended many-chats pattern), both with a React + Vite UI and workers-pool tests.

• #2175 8ffb3ad Thanks @​mattzcarey! - Lifecycle owns a durable job queue, driven as an alarm event loop.

  The thing in the queue is a job: a serialisable callback address — the owning capability plus a function name — with a due time and a payload. Capabilities and the host push jobs through the scoped jobs surface; Lifecycle drives due jobs in timestamp order when the alarm fires, owns dispatch retries and platform-failure deferral, arms a deadman pre-alarm before driving so an isolate death mid-drive still wakes the object, and derives the physical alarm purely from queue state (queue mutations re-arm automatically; an exclusive job suppresses ordinary candidates).

  class Cleanup extends LifecycleCapability {
    async scheduleSweep(time: number) {
      await this.lifecycle.jobs.push({ id: "sweep", fn: "sweep", time });
    }
    onJob({ job }: LifecycleJobContext) {
      // drive result: nothing = complete, { rescheduleAt } = suspend,
      // "yield" = leave due and wake again immediately
    }
  }

  The pull-based alarm-contribution model is removed: capability getNextAlarm()/onAlarm(), host getNextAlarm(), LifecycleServices.alarms (rearm/disabled), and AlarmContribution are gone. Host onAlarm() remains and runs once per alarm invocation after due jobs are driven. Terminal application failures reach the owner's onJobError(), whose drive result decides advancement.

  The alarm memory-limit circuit breaker (#1825) moves from Agent.alarm() into the Lifecycle event loop, targeting the exact executing job; Agent contributes domain policy through the new onAlarmMemoryLimit() host hook, and Scheduler's __DO_NOT_USE_WILL_BREAK__handleAlarmMemoryLimit escape hatch is gone. After recording a strike the breaker now finishes by resetting the isolate with ctx.abort(reason, { retryAlarm: false }) (retry of the handled alarm suppressed; the backoff alarm owns the next wake), and Agent.destroy() uses the same no-retry abort so a completed

... (truncated)

Commits

• 5f7ad7e Version Packages (#2174)
• b9142be fix(agents): preserve sub-agent onConnect connection state (#2233)
• d5d250e perf(sessions,think): memoise the auto-compaction estimate and drop per-turn ...
• 8c8f86d feat(agents): move Voice and Channels into agents package (#2225)
• 0966a0b perf(think,sessions): stop re-reading the transcript during a turn (#2219)
• dcca089 fix(codemode): truncate structured results structurally and keep the call log...
• dd8bf90 perf(chat): derive the recovery progress marker from the stream log (#2223)
• dd09d44 feat(streams): rollover block log and atomic stream → session cutover (#2216)
• ec93caf feat(agents): move sessions into a Lifecycle capability (#2196)
• 6da4c44 refactor(chat): run recovery continuations on Tasks (#2194)
• Additional commits viewable in compare view

Updates hono from 4.13.7 to 4.13.8

Release notes

Sourced from hono's releases.

v4.13.8

What's Changed

• docs: fix typos in code comments and link third-party middleware section in honojs/hono#5343
• perf(jsx/dom): reduce lookup work for large keyed updates in honojs/hono#5340
• fix(aws-lambda): respect backpressure when streaming the response body in honojs/hono#5351
• fix(accepts, language): skip accept entries with quality 0 when matching in honojs/hono#5311
• fix(accept): treat the q parameter name as case-insensitive in honojs/hono#5349
• fix(accept): clamp a negative q to 0, not 1 in honojs/hono#5357
• fix(request): keep the request media type when reusing a cached body in honojs/hono#5366
• docs(combine): fix except() JSDoc param and add missing @​returns in honojs/hono#5346
• perf(jsx/dom): optimize matching-head child lookup during reconciliation in honojs/hono#5329

Full Changelog: honojs/hono@v4.13.7...v4.13.8

Commits

• 098e119 4.13.8
• e8c8c21 perf(jsx/dom): optimize matching-head child lookup during reconciliation (#5329)
• 8755b17 docs(combine): fix except() JSDoc param and add missing @​returns (#5346)
• edd138e fix(request): keep the request media type when reusing a cached body (#5366)
• 9b4e9c2 fix(accept): clamp a negative q to 0, not 1 (#5357)
• 65cff90 fix(accept): treat the q parameter name as case-insensitive (#5349)
• f147de5 fix(accepts, language): skip accept entries with quality 0 when matching (#5311)
• 90e1b94 fix(aws-lambda): respect backpressure when streaming the response body (#5351)
• 7792f5d perf(jsx/dom): reduce lookup work for large keyed updates (#5340)
• e7b38ee docs: fix typos in code comments and link third-party middleware section (#5343)
• See full diff in compare view

Updates zod from 4.6.2 to 4.6.5

Release notes

Sourced from zod's releases.

v4.6.5

Commits:

• d2b135cfb7a3582b9eb515756b9166bcb9521f4a docs: add the 4.6.x patch highlights to the 4.6 post
• f1448f7cee00df9fe1e9ad84a000aa1828cc8bc1 docs: fold the 4.6.x patch highlights into the 4.6 post's own sections
• de65a5cb39ed22a507fac935788f718fa88d104f docs: lead the properties section with the check and add a Zod Mini tab (#6598)
• 56222cd1532c07bcb91b67df529cab4c0a215330 feat(instanceof): key the .properties() shape off the instance type (#6600)
• ca0229a404818290e6cdcfefcd7eb2d04bcbb543 Revert "feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed weekly by CI (#6595)"
• cc4cd4ee9c52fcaa10964e48cc144541e41a5ed9 Revert "Revert "feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed weekly by CI (#6595)""
• 0f3f5ee3ca56c7574bf849e54f79e9a6e02562ee 4.6.5
• 59bbc03e10c636b9eb3c393dfeb552819774ec21 chore: re-pin the integration peers to the workspace zod after the 4.6.5 bump

v4.6.4

A patch on top of 4.6.3.

• d6bc1e30 feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed weekly by CI (#6595)
• ad32d751 perf: z.url() rejects an invalid URL with URL.canParse() instead of a throwing constructor, about 50x faster; fewer allocations on the validation path (#6588)
• 2bb08717 chore: re-pin the integration peers to the workspace zod after the 4.6.4 bump
• f6e1701a chore(deps): bump next to 15.5.25 and vite to 7.3.6 (#6153)

v4.6.3

A patch on top of 4.6.2.

• 413cce9a fix(v4): make z.properties() a check again (#6594) — removes the standalone z.properties() schema from 4.6.0; z.instanceof().properties() and .check(...z.properties()) are unchanged
• 75d63ee1 docs: show only the .properties() method form in the 4.6 post
• 46da9572 docs: match the error-message examples to what the parsers emit

Commits

• 59bbc03 chore: re-pin the integration peers to the workspace zod after the 4.6.5 bump
• 0f3f5ee 4.6.5
• cc4cd4e Revert "Revert "feat: add z.currencyCode() over a vendored ISO 4217 list, ref...
• ca0229a Revert "feat: add z.currencyCode() over a vendored ISO 4217 list, refreshed w...
• 56222cd feat(instanceof): key the .properties() shape off the instance type (#6600)
• de65a5c docs: lead the properties section with the check and add a Zod Mini tab (#6598)
• f1448f7 docs: fold the 4.6.x patch highlights into the 4.6 post's own sections
• d2b135c docs: add the 4.6.x patch highlights to the 4.6 post
• 2bb0871 chore: re-pin the integration peers to the workspace zod after the 4.6.4 bump
• 743aedb 4.6.4
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions