Address PR #942 review comments + buildifier fix

.aspect/workflows/config.yaml

@@ -22,13 +22,15 @@ tasks:
         flags: ["--test_tag_filters=-skip-on-bazel8"]
       env:
         USE_BAZEL_VERSION: 8.x
+      queue: aspect-large
   - test:
       name: Bazel 9
       id: bazel-9
       bazel:
         flags: ["--test_tag_filters=-skip-on-bazel9"]
       env:
         USE_BAZEL_VERSION: 9.*
+      queue: aspect-large
 
   - buildifier:
       queue: aspect-small

.bazelrc

@@ -23,6 +23,14 @@ common --repo_env=BAZEL_NO_APPLE_CPP_TOOLCHAIN=1
 
 common:ci --toolchain_resolution_debug='@@bazel_tools//tools/cpp:toolchain_type'
 
+# rules_rs experimental toolchains require @llvm//constraints/libc:gnu.2.28 on the target
+# platform for gnu Linux targets. The auto-detected host platform doesn't include it, so we
+# use a custom platform that inherits host cpu/os constraints and adds gnu.2.28. This works
+# on both x86_64 and aarch64 Linux builders.
+# --enable_platform_specific_config (in defaults.bazelrc) makes this activate automatically on Linux.
+common:linux --platforms=//bazel/platforms:linux_gnu
+common:linux --host_platform=//bazel/platforms:linux_gnu
+
 common:release --build_tag_filters=release
 common:release --stamp
 common:release --compilation_mode=opt

CONTRIBUTING.md

@@ -36,6 +36,44 @@ echo "common $OVERRIDE" >> ~/.bazelrc
 
 This means that any usage of `@aspect_rules_py` on your system will point to this folder.
 
+## Running `uv` from the Bazel-managed toolchain
+
+`MODULE.bazel` registers a hermetic `uv` via `uv_bin.toolchain(version = "…")`,
+so there's no need to install `uv` globally. Two ways to invoke it:
+
+### Ad-hoc: `bazel run`
+
+```sh
+bazel run @uv -- lock
+bazel run @uv -- add --no-workspace requests
+```
+
+`@uv` is an alias that resolves to the host-platform UV binary for the
+version configured in `MODULE.bazel`.
+
+### On your `$PATH` via `bazel_env.bzl`
+
+`//tools:bazel_env` maps `uv` (and `cargo`, `rustc`, `rustfmt`, multitool
+binaries) to Bazel labels and materializes them into
+`bazel-out/bazel_env-opt/bin/tools/bazel_env/bin/`. Pair it with
+[direnv](https://direnv.net/):
+
+1. `bazel run //tools:bazel_env` once (and again whenever versions change).
+2. Create a `.envrc` next to `MODULE.bazel`:
+
+   ```sh
+   watch_file bazel-out/bazel_env-opt/bin/tools/bazel_env/bin
+   PATH_add bazel-out/bazel_env-opt/bin/tools/bazel_env/bin
+   if [[ ! -d bazel-out/bazel_env-opt/bin/tools/bazel_env/bin ]]; then
+     log_error "Run 'bazel run //tools:bazel_env'"
+   fi
+   ```
+
+3. `direnv allow`.
+
+Now `uv lock`, `uv add`, etc. resolve to the Bazel-managed binary anywhere in
+the workspace.
+
 ## Releasing
 
 1. Determine the next release version, following semver (could automate in the future from changelog)

Cargo.toml

@@ -23,7 +23,6 @@ clap = { version = "4.5.20", features = ["derive"] }
 itertools = "0.13.0"
 miette = { version = "7.2", features = ["fancy"] }
 tempfile = "3.13.0"
-thiserror = "1.0.64"
 uv-cache = { git = "https://github.com/astral-sh/uv", rev = "855c1917e1e0e2b48c38de71bebc845af016afae" }
 uv-distribution-filename = { git = "https://github.com/astral-sh/uv.git", rev = "855c1917e1e0e2b48c38de71bebc845af016afae" }
 uv-extract = { git = "https://github.com/astral-sh/uv.git", rev = "855c1917e1e0e2b48c38de71bebc845af016afae" }