chore(deps): nightly rollup 2026-10-09

[bonk-ai]

What and why

Nightly dependency rollup: a semver-compatible lockfile refresh at the root and in crates/agentd/fuzz. No Dependabot PR is open, no Cargo.toml requirement changed, and no source file changed. The branch starts from main at cae2ec7.

Root Cargo.lock

Crate	Old	New	Reached through
toml	1.1.7+spec-1.1.0	1.1.8+spec-1.1.0	microvms-cli, microvms-core
toml_edit	0.25.16+spec-1.1.0	0.25.17+spec-1.1.0	proc-macro-crate (under bolero-generator-derive and borsh-derive)
toml_parser	1.1.4+spec-1.1.0	1.1.5+spec-1.1.0	toml, toml_edit
zerocopy	0.8.61	0.8.62	ahash (under stateright), ppv-lite86 (under rand_chacha)
zerocopy-derive	0.8.61	0.8.62	zerocopy

crates/agentd/fuzz/Cargo.lock

zerocopy and zerocopy-derive 0.8.61 -> 0.8.62 (under ppv-lite86), the same versions as the root.

Every new version above was checked on crates.io as not yanked. The toml family was published 2026-10-09 02:46Z by its maintainer, and zerocopy 0.8.62 on 2026-10-08 10:04Z through trusted publishing.

Left out

• pest 2.9.3 and its family (pest_derive, pest_generator, pest_meta), which cargo update also offers. It was published 2026-10-09 07:33Z, 31 minutes before this branch was built, and its default std feature now pulls in two crates the graph does not carry yet: stacker 0.1.25 and psm, exact-pinned at =0.1.24 (a 2024 release; psm's newest is 0.1.32). The release notes name the cause, "Limit parse depth" (Limit parse depth pest-parser/pest#1212). pest reaches this workspace only through termwiz, under ratatui-termwiz and ratatui. The bump is held for one night so the release has a day for a yank or a follow-up patch, and the next nightly picks it up.
• Held back by a requirement (cargo update --dry-run --verbose): bolero 0.13.7 and its family, generic-array 0.14.9, matchit 0.8.6, toml_datetime 0.6.11 and toml_edit 0.20.7 by upstream requirements (generic-array and matchit also in the fuzz lockfile), and zip 9.0.0 (published 2026-10-09 04:48Z) by our own zip = "8.6" requirement in crates/microvms-core/Cargo.toml and crates/microvms-app/Cargo.toml.

None of these crates is part of the daemon's transport stack (hyper, tower, tokio, rustls) or an aws-* crate.

Evidence

• mise run check, run bare on this tree: EXIT=0 in 164 s, 64 test result: lines, 1742 passed, 0 failed, [security] advisories ok, bans ok, licenses ok, sources ok. That task runs fmt, clippy with -D warnings, the Rust tests, the schema, stubs, manifest, dts and core-api checks, cargo deny, actionlint, background:check and the aarch64-musl release build.
• mise run vuln on this tree: EXIT=0 in 120 s. trivy reports 0 vulnerabilities in both Cargo lockfiles, both uv lockfiles and site/pnpm-lock.yaml, and osv-scanner reports "No issues found". This is the step CI's SBOM and vulnerability scans job runs. (grype's table lists Go advisories of Unknown severity in stdlib go1.26.6, golang.org/x/net and golang.org/x/crypto. The local SBOM places all three in one file, the terraform-provider-aws_v6.65.0_x5 binary that background:check's terraform init downloads into the gitignored examples/background-coding-agent/infra/.terraform/; a clean checkout has no such file, and grype's --fail-on high ignores Unknown severity.)
• mise exec -- osv-scanner scan source -r . --config osv-scanner.toml: EXIT=0, "No issues found".
• mise run pr-body:check -- --body <this body>: EXIT=0.
• Live conformance run: not run, and not needed for these crates.

Parity

• No public name changed on any surface (core, CLI commands, microvms.pyi, index.d.ts).

Guards

None: this adds no guard.

Follow-ups

• pest 2.9.3, with stacker and psm, goes into the next nightly rollup if it is still unyanked.

Platform claims

• Not applicable: this changes no claim about AWS behavior.

Scope

• This is not an orchestrator, a fork implementation, or AgentCore parity work
  (see docs/STRATEGY.md).