docs: update documentation for bazelrc import depth, Bzlmod integrity, 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`.

docs/remote/bep.mdx

@@ -45,10 +45,11 @@ 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)
-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.
+more parent events. BEP events are written respecting parent-child ordering
+constraints, so a parent event is always published before its child events.
+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.
 
 The event graph's structure reflects the lifecycle of a command. Every BEP
 graph has the following characteristic shape:

docs/remote/caching.mdx

@@ -287,6 +287,12 @@ domain socket:
 
 This feature is unsupported on Windows.
 
+## Chunked uploads and downloads (CDC)
+
+Use the `--experimental_remote_cache_chunking` flag to read and write large
+blobs to and from the remote cache in chunks. This requires server-side support
+for content-defined chunking (CDC).
+
 ## Disk cache
 
 Bazel can use a directory on the file system as a remote cache. This is

docs/run/bazelrc.mdx

@@ -141,6 +141,12 @@ try-import-if-bazel-version ~1.2 %workspace%/configs/1.2_flags.rc
 try-import-if-bazel-version ~1 %workspace%/configs/v1_flags.rc
 ```
 
+A `.bazelrc` file may only import files recursively up to a depth of 512 imports.
+If you encounter a "Maximum import depth exceeded parsing config file" error,
+check whether your workspace needs import chains that long. If you cannot
+shorten your 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`.

site/en/remote/bep.md

@@ -46,10 +46,11 @@ 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)
-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.
+more parent events. BEP events are written respecting parent-child ordering
+constraints, so a parent event is always published before its child events.
+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.
 
 The event graph's structure reflects the lifecycle of a command. Every BEP
 graph has the following characteristic shape:

site/en/remote/caching.md

@@ -288,6 +288,12 @@ domain socket:
 
 This feature is unsupported on Windows.
 
+## Chunked uploads and downloads (CDC) {:#remote-cache-cdc}
+
+Use the `--experimental_remote_cache_chunking` flag to read and write large
+blobs to and from the remote cache in chunks. This requires server-side support
+for content-defined chunking (CDC).
+
 ## 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,12 @@ try-import-if-bazel-version ~1.2 %workspace%/configs/1.2_flags.rc
 try-import-if-bazel-version ~1 %workspace%/configs/v1_flags.rc
 ```
 
+A `.bazelrc` file may only import files recursively up to a depth of 512 imports.
+If you encounter a "Maximum import depth exceeded parsing config file" error,
+check whether your workspace needs import chains that long. If you cannot
+shorten your 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