bazel

# Bazel Bazel for C/C++ projects: BUILD files, Bzlmod dependencies, toolchain registration, remote execution, dependency graph queries, and sandbox debugging. Grounded against Bazel 9.2.0, where Bzlmod is always enabled, all WORKSPACE logic is removed, and every C++ rule loads from `@rules_cc`. ## Contract | Field | Bound contract | |---|---| | Trigger | The task writes or debugs Bazel BUILD files, `cc_library`/`cc_binary`/`cc_test` rules, Bzlmod dependencies, toolchain registration, remote execution, sandbox failures, or `bazel query`/`cquery`/`aquery` dependency graphs. | | Authority | Reversible local: writes only BUILD files, `MODULE.bazel`, `.bzl` files, and Bazel output directories (`bazel-out`, `bazel-bin`); rollback is version control plus `bazel clean`. No remote mutation. | | Side effect | Local builds write to the Bazel output base; remote execution and remote cache flags contact a user-supplied endpoint. | | Done | The requested targets build or test with `bazel build`/`bazel test`, or the blocker is reported with the failing command and output. | ## Inputs - Project layout (required): the source tree and where BUILD files should live. - Bazel version (required if not inferrable): run `bazel version`. Bazel 9 removed WORKSPACE and the native C++ rules; instructions below assume Bazel 9. - External dependencies (optional): library names; versions come from the Bazel Central Registry. - Remote execution endpoint (optional): a user-supplied remote execution or c...