chore: update documentation from upstream Bazel repo

Generated by GitHub Actions workflow from upstream Bazel repository.
This commit includes transformed documentation files ready for Mintlify deployment.

Author: github-actions[bot]

release/index.mdx

@@ -16,7 +16,7 @@ information about Bazel's release model.
 | ----------- | ------------- | -------------- | -------------- |
 | Bazel 9 | Rolling| [Check rolling release page](/release/rolling) | N/A |
 | Bazel 8 | Active| [8.4.2](https://github.com/bazelbuild/bazel/releases/tag/8.4.2) | December 2027 |
-| Bazel 7 | Maintenance| [7.7.0](https://github.com/bazelbuild/bazel/releases/tag/7.7.0) | Dec 2026 |
+| Bazel 7 | Maintenance| [7.6.2](https://github.com/bazelbuild/bazel/releases/tag/7.6.2) | Dec 2026 |
 | Bazel 6 | Maintenance | [6.5.0](https://github.com/bazelbuild/bazel/releases/tag/6.5.0) | Dec 2025 |
 | Bazel 5 | Deprecated | [5.4.1](https://github.com/bazelbuild/bazel/releases/tag/5.4.1) | Jan 2025 |
 | Bazel 4 | Deprecated | [4.2.4](https://github.com/bazelbuild/bazel/releases/tag/4.2.4) | Jan 2024 |

rules/bzl-style.mdx

@@ -143,7 +143,7 @@ not instantiated by that macro), follow these best practices:
 *   A macro should take a `name` argument and define a target with that name.
     That target becomes that macro's *main target*.
 *   Generated targets, that is all other targets defined by a macro, should:
-    *   Have their names prefixed by `<name>`. For example, using
+    *   Have their names prefixed by `<name>` or `_<name>`. For example, using
         `name = '%s_bar' % (name)`.
     *   Have restricted visibility (`//visibility:private`), and
     *   Have a `manual` tag to avoid expansion in wildcard targets (`:all`,