Public repository baseline fails cargo fmt --all -- --check

Summary

The public repository baseline does not pass its documented Rust formatter.

At 4ac3025d0d15b765181e0fc120d9d1323ead752c — 2026-08-17 17:19 PDT — More runtime refactorin, the following command reports diffs in 59 tracked Rust files:

cargo fmt --all -- --check

The repository pins nightly-2026-06-28, which resolves to rustfmt 1.9.0-nightly (13f1859f2f 2026-06-27), and contains a root rustfmt.toml. Both the root CONTRIBUTING.md and crates/convex/CONTRIBUTING.md direct Rust contributors to use cargo fmt.

Reproduction

git clone https://github.com/get-convex/convex-backend.git
cd convex-backend
git checkout 4ac3025d0d15b765181e0fc120d9d1323ead752c
cargo fmt --all -- --check

Representative affected files include:

• crates/application/src/scheduled_jobs/mod.rs
• crates/authentication/src/application_auth.rs
• crates/aws_s3/src/storage.rs
• crates/common/src/auth.rs
• crates/common/src/bootstrap_model/components/definition.rs

The diffs are mechanical rustfmt output: import grouping, collapsing empty implementations and tuple variants, removing stray blank lines, and restoring missing final newlines.

Question

Is the public repository expected to use the checked-in rustfmt.toml with the pinned toolchain, or does the internal/public-export workflow use a different canonical formatting command or configuration?

If the checked-in configuration is authoritative, would you prefer to run a workspace-wide format upstream, or would you accept a mechanical formatting PR? A clean upstream baseline would also let downstream forks enforce cargo fmt --all -- --check without carrying a long-lived formatting-only divergence.