docs: update documentation for .bazelrc import depth, Bzlmod integrity enforcement, remote cache CDC, and BEP ordering

docs/external/registry.mdx

@@ -94,12 +94,12 @@ field, which defaults to `archive`.
         extracted archive. The patch files are located under the
         `/modules/$MODULE/$VERSION/overlay` directory. The keys are the
         overlay file names, and the values are the integrity checksum of
-        the overlay files. The overlays are applied before the patch files.
+        the overlay files (must be non-empty). The overlays are applied before the patch files.
     *   `patches`: A JSON object containing patch files to apply to the
         extracted archive. The patch files are located under the
         `/modules/$MODULE/$VERSION/patches` directory. The keys are the
         patch file names, and the values are the integrity checksum of
-        the patch files. The patches are applied after the overlay files and in
+        the patch files (must be non-empty). The patches are applied after the overlay files and in
         the order they appear in `patches`.
     *   `patch_strip`: A number; the same as the `--strip` argument of Unix
         `patch`.
@@ -116,7 +116,7 @@ field, which defaults to `archive`.
         cloned repository. The patch files are located under the
         `/modules/$MODULE/$VERSION/patches` directory. The keys are the
         patch file names, and the values are the integrity checksum of
-        the patch files. The patches are applied in the order they appear in
+        the patch files (must be non-empty). The patches are applied in the order they appear in
         `patches`.
 *   If `type` is `local_path`, this module version is backed by a
     [`local_repository`](/rules/lib/repo/local#local_repository) repo rule;

docs/remote/bep.mdx

@@ -45,8 +45,9 @@ if the build aborted prematurely.
 
 All build events form a directed acyclic graph through their parent and child
 relationship. Every build event except for the initial build event has one or
-more parent events. Please note that not all parent events of a child event must
-necessarily be posted before it. When a build is complete (succeeded or failed)
+more parent events. BEP events are written respecting parent-child ordering
+constraints, ensuring that parent events are always posted before their
+children. When a build is complete (succeeded or failed)
 all announced events will have been posted. In case of a Bazel crash or a failed
 network transport, some announced build events may never be posted.
 

docs/remote/caching.mdx

@@ -287,6 +287,11 @@ domain socket:
 
 This feature is unsupported on Windows.
 
+### Chunked transfer
+
+Use the `--experimental_remote_cache_chunking` flag to read and write large
+blobs to/from the remote cache in chunks. This requires server support.
+
 ## Disk cache
 
 Bazel can use a directory on the file system as a remote cache. This is

docs/run/bazelrc.mdx

@@ -141,6 +141,11 @@ try-import-if-bazel-version ~1.2 %workspace%/configs/1.2_flags.rc
 try-import-if-bazel-version ~1 %workspace%/configs/v1_flags.rc
 ```
 
+Imports may be chained recursively up to a maximum depth of 512. If Bazel
+reports "Maximum import depth exceeded parsing config file", check for
+unexpectedly long import chains. Set the `BAZEL_UNLIMITED_IMPORT_DEPTH`
+environment variable to any value to disable this limit.
+
 Import precedence:
 
 -   Options in the imported file take precedence over options specified before

site/en/external/registry.md

@@ -97,12 +97,12 @@ field, which defaults to `archive`.
         extracted archive. The patch files are located under the
         `/modules/$MODULE/$VERSION/overlay` directory. The keys are the
         overlay file names, and the values are the integrity checksum of
-        the overlay files. The overlays are applied before the patch files.
+        the overlay files (must be non-empty). The overlays are applied before the patch files.
     *   `patches`: A JSON object containing patch files to apply to the
         extracted archive. The patch files are located under the
         `/modules/$MODULE/$VERSION/patches` directory. The keys are the
         patch file names, and the values are the integrity checksum of
-        the patch files. The patches are applied after the overlay files and in
+        the patch files (must be non-empty). The patches are applied after the overlay files and in
         the order they appear in `patches`.
     *   `patch_strip`: A number; the same as the `--strip` argument of Unix
         `patch`.
@@ -119,7 +119,7 @@ field, which defaults to `archive`.
         cloned repository. The patch files are located under the
         `/modules/$MODULE/$VERSION/patches` directory. The keys are the
         patch file names, and the values are the integrity checksum of
-        the patch files. The patches are applied in the order they appear in
+        the patch files (must be non-empty). The patches are applied in the order they appear in
         `patches`.
 *   If `type` is `local_path`, this module version is backed by a
     [`local_repository`](/rules/lib/repo/local#local_repository) repo rule;

site/en/remote/bep.md

@@ -46,8 +46,9 @@ if the build aborted prematurely.
 
 All build events form a directed acyclic graph through their parent and child
 relationship. Every build event except for the initial build event has one or
-more parent events. Please note that not all parent events of a child event must
-necessarily be posted before it. When a build is complete (succeeded or failed)
+more parent events. BEP events are written respecting parent-child ordering
+constraints, ensuring that parent events are always posted before their
+children. When a build is complete (succeeded or failed)
 all announced events will have been posted. In case of a Bazel crash or a failed
 network transport, some announced build events may never be posted.
 

site/en/remote/caching.md

@@ -288,6 +288,11 @@ domain socket:
 
 This feature is unsupported on Windows.
 
+### Chunked transfer {:#chunked-transfer}
+
+Use the `--experimental_remote_cache_chunking` flag to read and write large
+blobs to/from the remote cache in chunks. This requires server support.
+
 ## Disk cache {:#disk-cache}
 
 Bazel can use a directory on the file system as a remote cache. This is

site/en/run/bazelrc.md

@@ -142,6 +142,11 @@ try-import-if-bazel-version ~1.2 %workspace%/configs/1.2_flags.rc
 try-import-if-bazel-version ~1 %workspace%/configs/v1_flags.rc
 ```
 
+Imports may be chained recursively up to a maximum depth of 512. If Bazel
+reports "Maximum import depth exceeded parsing config file", check for
+unexpectedly long import chains. Set the `BAZEL_UNLIMITED_IMPORT_DEPTH`
+environment variable to any value to disable this limit.
+
 Import precedence:
 
 -   Options in the imported file take precedence over options specified before