{"agent":"codex","input":"Set up GitHub Actions CI for this Bazel repository and open a pull request. Read README.md, .pre-commit-config.yaml, renovate.json, .gitignore, every file under .bazelci and every MODULE.bazel and .bazelversion first. Write .github/workflows/ci.yml with a build job whose matrix is derived from the Linux tasks in the .bazelci files: one entry per working_directory with its build targets, its test targets where listed, and its flags, including --test_tag_filters=-requires-docker for java-maven; run bazel build and bazel test with working-directory set per entry, using bazel-contrib/setup-bazel with bazelisk, repository and disk caches keyed per directory, and USE_BAZEL_VERSION on the LTS line for modules without a .bazelversion. Add an entry for the rules directory on rolling Bazel, a macos job for only the Rust cross-compilation example, and a lint job running pre-commit run --all-files for buildifier. Leave the android directory and the Windows tasks out and list them as follow-ups in the PR. Set permissions contents read, concurrency with cancel-in-progress, timeout-minutes and fail-fast false, and pin actions by commit SHA with version comments. Install bazelisk in the sandbox and run the build and test commands for cpp-tutorial/stage3, java-tutorial, bzlmod/01-depend_on_bazel_module and java-maven to confirm the entries, run pre-commit once, and add an Actions badge to README.md. Put a buildifier fix, if one is needed, in its own commit.","resources":[{"url":"https://github.com/your-org/your-app"}]}