# codex-utils-cargo-bin runfiles strategy

We disable the directory-based runfiles strategy and rely on the manifest
strategy across all platforms. This avoids Windows path length issues and keeps
behavior consistent in local and remote builds on all platforms. Bazel sets
`RUNFILES_MANIFEST_FILE`, and the `codex-utils-cargo-bin` helpers use the
`runfiles` crate to resolve runfiles via that manifest.

Function behavior:

- `cargo_bin`: reads `CARGO_BIN_EXE_*` environment variables (set by Cargo or
  Bazel) and resolves them via the runfiles manifest when `RUNFILES_MANIFEST_FILE`
  is present. When not under runfiles, it only accepts absolute paths from
  `CARGO_BIN_EXE_*` and returns an error otherwise.
- `find_resource!`: used by tests to locate fixtures relative to the calling
  package. Bazel compiles this helper with `codex_bazel`, selecting runfiles
  lookup without embedding the build worker's Cargo source directory. Missing
  runfiles produce an error. Cargo builds retain the `CARGO_MANIFEST_DIR`-relative
  fallback when runfiles are unavailable.
- `resolve_cargo_runfile`: retains source-directory lookup for Cargo builds;
  Bazel builds return an unsupported-operation error. This also prevents
  `repo_root` from falling back to a build worker's source directory.

Background:

- https://bazel.build/docs/runfiles
- https://bazel.build/docs/runfiles#runfiles-manifest