• Migrate Rust build system from rules_rust to rules_rs
• Simplify Cargo dependency management without bazel lockfiles
• Remove manual cargo repinning task and workflow
• Add platform-specific constraints for Linux and Windows
• Update Bazel module dependencies and toolchain configuration

Update Bazel dependencies and Rust toolchain configuration

MODULE.bazel

Add platform definitions for Linux and Windows

BUILD.bazel

Update build configuration for platform-specific settings

.bazelrc

Description

The PR deletes the rust:update rake task, but Rakefile still invokes it in release_updates,
which will fail at runtime with an unknown task error. This breaks the release preparation workflow
when running rake release_updates.

Code

rake_tasks/rust.rake[L15-30]

-desc 'Update the rust lock files'
-task :update do
-  # The first repin after a version bump can fail due to a stale checksum in
-  # Cargo.Bazel.lock; a second run lets Bazel reconcile and succeeds.
-  puts 'pinning cargo versions'
-  begin
-    Bazel.execute('fetch', ['--repo_env=CARGO_BAZEL_REPIN=true'], '@crates//:all')
-  rescue RuntimeError
-    puts 'repin failed, retrying...'
-    Bazel.execute('fetch', ['--repo_env=CARGO_BAZEL_REPIN=true'], '@crates//:all')
-  end
-end
-
-desc 'Pin Rust dependencies'
-task pin: :update
-

Evidence

Rakefile still calls Rake::Task['rust:update'].invoke as part of release_updates, but
rake_tasks/rust.rake no longer defines any task :update (only
build/format/lint/changelogs/version remain). Therefore, rake release_updates will raise “Don't
know how to build task 'rust:update'”.

Rakefile[104-126]
rake_tasks/rust.rake[9-51]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`rake release_updates` invokes `rust:update`, but this PR removed the `rust:update` task definition from `rake_tasks/rust.rake`, so the release workflow will now fail with an unknown-task error.

### Issue Context
With the switch to `rules_rs`, there is no longer a Bazel-specific Rust lockfile repin step, so the old `rust:update` task was deleted. The top-level release task still expects it to exist.

### Fix Focus Areas
- Rakefile[112-122]
- rake_tasks/rust.rake[9-25]

### Suggested fix
Remove `Rake::Task['rust:update'].invoke` from the `release_updates` task (or reintroduce a `rust:update` task as a backward-compatible no-op if you still want the task name to exist).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The PR deletes the rust:update and rust:pin rake tasks without first providing a deprecation
shim/message pointing users to the new workflow. This can break existing contributor automation and
violates the requirement to deprecate public functionality before removal with clear alternatives.

Code

rake_tasks/rust.rake[L15-30]

-desc 'Update the rust lock files'
-task :update do
-  # The first repin after a version bump can fail due to a stale checksum in
-  # Cargo.Bazel.lock; a second run lets Bazel reconcile and succeeds.
-  puts 'pinning cargo versions'
-  begin
-    Bazel.execute('fetch', ['--repo_env=CARGO_BAZEL_REPIN=true'], '@crates//:all')
-  rescue RuntimeError
-    puts 'repin failed, retrying...'
-    Bazel.execute('fetch', ['--repo_env=CARGO_BAZEL_REPIN=true'], '@crates//:all')
-  end
-end
-
-desc 'Pin Rust dependencies'
-task pin: :update
-

Evidence

PR Compliance ID 7 requires public functionality to be deprecated (with a message pointing to
alternatives) before removal. The diff removes the desc 'Update the rust lock files' / `task
:update and desc 'Pin Rust dependencies' / task pin: :update` definitions entirely, with no
deprecation alias retained.

AGENTS.md
rake_tasks/rust.rake[15-30]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The rake tasks `rust:update` and `rust:pin` were removed without a deprecation period or a message pointing users to the new rules_rs-based workflow.

## Issue Context
Some contributors/automation may still call these tasks. The compliance requirement expects a deprecation step that clearly communicates the replacement.

## Fix Focus Areas
- rake_tasks/rust.rake[15-30]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools