Sync upstream rust-v0.142.0

.codex/skills/path-types/SKILL.md

@@ -9,10 +9,35 @@ Apply this guidance when defining new types. Change existing code only when expl
 and keep edits minimal and proportional. Treat these rules as the target state of an ongoing
 migration; if compliance is difficult, ask the user how to proceed.
 
-- In app-server protocol types, use `ApiPathString` for backwards compatibility during the URI
+- In app-server protocol types, use `LegacyAppPathString` for backwards compatibility during the URI
   migration. At the protocol boundary, convert it to `PathUri` and use `PathUri` internally. For
   host-local logic, such as some config values, use `AbsolutePathBuf` or `PathBuf` instead.
 - In exec-server protocol types, use `PathUri`. Internally, use `PathUri` or `AbsolutePathBuf` as
   appropriate.
 - In dependencies shared by both servers, use `PathUri` or separate APIs that decouple their use
   cases.
+- Tool call arguments that the model is expected to generate should be deserialized as regular
+  `String`s with feature-specific path handling code.
+
+## Migration requirements
+
+Keep these requirements in mind while migrating code to conform with the above guidelines:
+
+* existing app-server clients keep sending and receiving legacy native-path strings
+* app-server can retain and manipulate foreign-platform path URIs
+* exec-server APIs use file:// URIs
+* local-only operation must not change model-visible text
+* model tool arguments may contain raw relative or absolute paths for any OS
+* path reasoning must work before the related environment has come online
+* URIs cannot explicitly encode the executor’s path convention or operating system
+* users must not configure the environment’s OS/path convention explicitly
+* URIs should not yet be stored in rollouts, databases, or other persistent storage
+* path conversion errors: fail-closed for security-relevant paths, fail-open for UI/diagnostics
+* prefer small focused methods on `PathUri` or `LegacyAppPathString` over local helpers
+* represent `PathUri` values as URIs in diagnostics
+
+It is OK if the conversion between paths and URIs is somewhat lossy as long as it will do the right
+thing for real users.
+
+Migrating to URIs should not add significant new failure modes. We will need to surface errors in
+some places that were previously infallible but it should be kept to a minimum.

.github/workflows/bazel.yml

@@ -23,6 +23,8 @@ jobs:
     # Upstream PRs also use the sharded Windows cross-compiled test jobs below.
     # Post-merge pushes to main run the native Windows test job for broader
     # Windows signal without putting PR latency back on the critical path.
+    # Code-mode unit tests run on every Bazel target. When authenticated RBE
+    # is available, the Windows-cross shards exercise the source-built V8 path.
     timeout-minutes: 30
     strategy:
       fail-fast: false
@@ -118,10 +120,6 @@ jobs:
             # path. V8 consumers under `//codex-rs/...` still participate
             # transitively through `//...`.
             -//third_party/v8:all
-            # Keep V8-backed code-mode tests out of the ordinary macOS/Linux
-            # legs; authenticated Windows-cross shards below exercise the
-            # source-built gnullvm V8 path.
-            -//codex-rs/code-mode:code-mode-unit-tests
             -//codex-rs/v8-poc:v8-poc-unit-tests
           )
 
@@ -329,9 +327,6 @@ jobs:
             # path. V8 consumers under `//codex-rs/...` still participate
             # transitively through `//...`.
             -//third_party/v8:all
-            # Keep this job broad and cheap; authenticated Windows-cross jobs
-            # add source-built V8-backed code-mode coverage.
-            -//codex-rs/code-mode:code-mode-unit-tests
             -//codex-rs/v8-poc:v8-poc-unit-tests
           )
 

AGENTS.md

@@ -105,6 +105,7 @@ Codex maintains a context (history of messages) that is sent to the model in inf
 Search for breaking changes in external integration surfaces:
 
 - app-server APIs
+- raw response item events (`rawResponseItem/*`), even while experimental
 - CLI parameters
 - configuration loading
 - resuming sessions from existing rollouts

MODULE.bazel

@@ -2,18 +2,17 @@ module(name = "codex")
 
 bazel_dep(name = "bazel_skylib", version = "1.9.0")
 bazel_dep(name = "platforms", version = "1.0.0")
-bazel_dep(name = "llvm", version = "0.7.1")
+bazel_dep(name = "llvm", version = "0.7.9")
 
-# The upstream LLVM archive contains a few unix-only symlink entries and is
-# missing a couple of MinGW compatibility archives that windows-gnullvm needs
-# during extraction and linking, so patch it until upstream grows native support.
+# Patch hermetic LLVM for Codex's custom libc++ and Windows gnullvm runtime
+# needs that have not landed upstream.
 single_version_override(
     module_name = "llvm",
     patch_strip = 1,
     patches = [
         "//patches:llvm_rusty_v8_custom_libcxx.patch",
         "//patches:llvm_windows_arm64_powl.patch",
-        "//patches:llvm_windows_symlink_extract.patch",
+        "//patches:llvm_windows_mingw_compat.patch",
     ],
 )
 
@@ -80,7 +79,7 @@ use_repo(osx, "macos_sdk")
 
 # Needed to disable xcode...
 bazel_dep(name = "apple_support", version = "2.1.0")
-bazel_dep(name = "rules_cc", version = "0.2.16")
+bazel_dep(name = "rules_cc", version = "0.2.18")
 single_version_override(
     module_name = "rules_cc",
     patch_strip = 1,