[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 9a14279 (the v1.0.0 tag).

Root Cargo.lock

Crate	Old	New	Reached through
bit-set	0.8.0	0.11.1	proptest, fancy-regex
bit-vec	0.8.0	0.10.1	bit-set, proptest
cc	1.6.0	1.8.0	aws-lc-sys, bolero-afl, bolero-libfuzzer, cmake, psm, ring, stacker (build dependency)
indoc	2.0.7	2.0.8	instability, ratatui-widgets
mac_address	1.2.0	1.2.1	wezterm-blob-leases
nix	0.30.1	removed	was reached only through mac_address; nix 0.29.0 and 0.31.3 stay
pest, pest_derive, pest_generator, pest_meta	2.9.2	2.9.3	termwiz (under ratatui-termwiz and ratatui)
proptest	1.11.0	1.12.0	dev-dependency of agentd, microvms-app, microvms-domain; also const-hex
psm	not present	0.1.24 (new)	pest, stacker
rand_xorshift	0.4.0	0.5.0	proptest
serde_json	1.0.151	1.0.154	every workspace crate, axum, schemars and others
smallvec	1.16.2	1.16.3	hyper, icu_normalizer, icu_segmenter, idna, parking_lot_core, tracing-subscriber
stacker	not present	0.1.25 (new)	pest
syn	3.0.6	3.0.8	agentd and the derive crates (clap_derive, serde_derive and others)
tokio-util	0.7.19	0.7.20	agentd, h2, reqwest
unicode-ident	1.0.26	1.0.27	proc-macro2, syn, wasm-bindgen-shared
uuid	1.27.0	1.28.0	aws-runtime, wezterm-blob-leases
zopfli	0.8.3	0.8.4	zip

In the root, proptest 1.12.0 now resolves rand 0.10.3, chacha20 0.10.2 and core_detect 1.0.0, which this lockfile already carried for other crates, and drops its edges to rand 0.9.5 and rand_chacha 0.9.0, which stay for their other dependents.

crates/agentd/fuzz/Cargo.lock

Crate	Old	New	Reached through
cc	1.6.0	1.8.0	libfuzzer-sys
chacha20	not present at 0.10	0.10.2 (new)	proptest (chacha20poly1305 keeps its own version)
core_detect	not present	1.0.0 (new)	proptest
proptest	1.11.0	1.12.0	const-hex
rand	not present at 0.10	0.10.3 (new)	proptest, tungstenite (rand 0.9.5 stays)
rand_xorshift	0.4.0	0.5.0	proptest
serde_json	1.0.151	1.0.154	agentd, axum, microvms-protocol, schemars, tracing-subscriber
smallvec	1.16.2	1.16.3	hyper, tracing-subscriber
syn	3.0.6	3.0.8	the derive crates
tokio-util	0.7.19	0.7.20	agentd
unicode-ident	1.0.26	1.0.27	proc-macro2, syn

The three crates new to the fuzz lockfile are the versions the root lockfile already carries.

Release checks

Every new version above was checked on crates.io as not yanked, on 2026-10-12 at about 08:05Z. The newest, unicode-ident 1.0.27, was published 2026-10-12 04:20Z by its maintainer and adds no crate. pest 2.9.3 was held from the 2026-10-09 rollup (#538) for one night because it was 31 minutes old and adds stacker and psm; it has now been public for three days and is still unyanked. stacker 0.1.25 and psm 0.1.24 are MIT OR Apache-2.0, and cargo deny's license check passes with them. psm stays at 0.1.24 because pest pins it exactly (=0.1.24); psm's newest release is 0.1.32.

proptest 1.12.0 lists rand 0.10, rand_xorshift 0.5 and bit-set 0.11 as breaking changes for code that exchanges rand or bit-set values with proptest; this workspace compiles and its property tests pass against it with no source change. Its changelog says the switch from rand_chacha to chacha20 keeps the seed format and the seeded RNG output (proptest-rs/proptest#664). Unverified: whether the two persisted seed files (crates/agentd/tests/proptest_tar.proptest-regressions and crates/microvms-core/proptest-regressions/cost.txt) still regenerate the same inputs under rand 0.10's samplers. Both suites pass, which shows the seeds load, not that they replay the original cases.

Held back

cargo update --dry-run --verbose lists these behind latest because of a requirement, so nothing is offered to bump: bolero 0.13.7 and its family, generic-array 0.14.9, matchit 0.8.6, psm 0.1.32 (pest's =0.1.24), 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.2 by our own zip = "8.6" requirement.

Transport stack

tokio-util (used by agentd, h2 and reqwest) and smallvec (under hyper) moved, and uuid moved under aws-runtime. These are patch releases in the tokio family and in dependencies of the HTTP and AWS crates; no hyper, tower, tokio, rustls or aws-* crate moved. Verified offline only: the live conformance suite was not run.

Evidence

• mise run check, run bare on this tree: EXIT=0 in 460 s, 69 test result: lines, 1799 passed, 0 failed, [security] advisories ok, bans ok, licenses ok, sources ok, and prose:check reports 0 errors. 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, prose:check and the aarch64-musl release build.
• mise run vuln on this tree: EXIT=0 in 44 s with the gitignored examples/background-coding-agent/infra/.terraform/ moved aside, which is the tree CI's SBOM and vulnerability scans job sees: grype reports "No vulnerabilities found", and osv-scanner filters GHSA-vfj7-8cjw-p6xm and reports "No issues found". With that directory present (it holds terraform-provider-aws_v6.65.0_x5, which background:check's terraform init downloads), the same task exits 2: grype now rates GO-2026-6604 and GO-2026-6612 Critical and GO-2026-6603, -6605, -6607 to -6611 and -6613 High in that binary's stdlib go1.26.6 and golang.org/x/net v0.59.0. The local SBOM places every one of those rows in that file, and a clean checkout has no such file.
• mise exec -- osv-scanner scan source -r . (the way vuln runs it since fix(deps): clear Scorecard's vulnerability and pinning findings #547): EXIT=0, "No issues found"; it filters GHSA-vfj7-8cjw-p6xm through site/osv-scanner.toml.
• mise run pr-body:check -- --body <this body>: EXIT=0.
• Live conformance run: not run.

Parity

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

Guards

None: this adds no guard.

Follow-ups

• Whether the two persisted proptest seeds still replay their original failing inputs under proptest 1.12.0 is unverified (see "Release checks").
• mise run vuln fails locally after any mise run check, because the sbom task's syft excludes (.config/mise/tasks/security.toml:47-48) skip conformance/infra/.terraform but not examples/background-coding-agent/infra/.terraform, where background:check puts a Terraform provider binary whose Go modules now carry High and Critical advisories. CI is unaffected.

Platform claims

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

Scope

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