docs(gazelle): Clarify manifest paths in subdirectories (#4397)

My agent pointed out that #3133 is not actually a bug put just a user
error. Gazelle resolves the root manifest paths relative to each `BUILD`
file, so the directives in #3133 example need a `../` prefix.

This documents the path base and relative manifest lookup.

Closes #3133.

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
diff --git a/gazelle/docs/directives.md b/gazelle/docs/directives.md
index 60f948e..5d3ddf7 100644
--- a/gazelle/docs/directives.md
+++ b/gazelle/docs/directives.md
@@ -229,9 +229,14 @@
 (directive-python-manifest-file-name)=
 ## `python_manifest_file_name`
 
-:::{error}
-Detailed docs are not yet written.
-:::
+Sets the manifest used to resolve third-party imports in this directory and its
+subdirectories (default: `gazelle_python.yaml`). Paths are relative to the `BUILD`
+file containing the directive. For example, in `a/BUILD.bazel`, select a manifest
+at the repository root with:
+
+```starlark
+# gazelle:python_manifest_file_name ../gazelle_python_a.yaml
+```
 
 
 (directive-python-ignore-files)=