docs: move maintainer runbook out of the wiki

The Supabase Knowledge Search maintainer guide is operational documentation
(secret names, infra topology, ops CLIs) and does not belong on the public wiki.
Relocated to z-shell/.github/runbooks/supabase-knowledge-search.md. Updates the
content-root boundaries: community/ holds community content only; maintainer /
operational runbooks live in z-shell/.github/runbooks/. Refs ADR 0006.

Author: ss-o

.github/instructions/agent-docusaurus-writer.instructions.md

@@ -38,8 +38,10 @@ Invoke the `docusaurus-writer` agent and provide:
 
 Before creating a page, select the root:
 
-- Admin / tooling / operational / infrastructure → `community/`.
 - Zi plugin-manager user docs → `docs/`.
+- Community content (contributing, handbook, ZUnit) → `community/`.
 - Third-party ecosystem (annexes, packages, plugins) → `ecosystem/`.
+- Admin / tooling / operational / infrastructure → **not the wiki**; these are
+  runbooks for `z-shell/.github/runbooks/`.
 
-`docs/` is Zi user docs only — never put maintainer tooling there.
+Never put maintainer/operational documentation anywhere in the wiki.

.github/instructions/docs-authoring.instructions.md

@@ -9,15 +9,17 @@ applyTo: "{docs,community,ecosystem}/**/*.mdx"
 
 Choose the content root before writing. The roots are not interchangeable:
 
-| Content type                                       | Root                                            |
-| -------------------------------------------------- | ----------------------------------------------- |
-| Zi plugin-manager install / commands / usage       | `docs/`                                         |
-| Contributing, Zsh handbook, plugin standard, ZUnit | `community/`                                    |
-| Maintainer / operational / infrastructure guides   | `community/` (e.g. `community/10_maintainers/`) |
-| Third-party annexes, packages, plugins             | `ecosystem/`                                    |
+| Content type                                       | Root                                           |
+| -------------------------------------------------- | ---------------------------------------------- |
+| Zi plugin-manager install / commands / usage       | `docs/`                                        |
+| Contributing, Zsh handbook, plugin standard, ZUnit | `community/`                                   |
+| Maintainer / operational / infrastructure runbooks | **not the wiki** — `z-shell/.github/runbooks/` |
+| Third-party annexes, packages, plugins             | `ecosystem/`                                   |
 
 **Prohibition:** Never place maintainer, operational, or infrastructure
-documentation under `docs/`. `docs/` is Zi end-user documentation only.
+documentation anywhere in the wiki (neither `docs/` nor `community/`). It leaks
+ops surface and belongs in `z-shell/.github/runbooks/`. See ADR
+`decisions/0006-wiki-content-root-boundaries.md` in `z-shell/.github`.
 
 ## Frontmatter
 

AGENTS.md

@@ -20,12 +20,15 @@ This project follows the organization-wide [Z-Shell Organization Guidelines](htt
 - Docusaurus site with three independent docs content roots. Each root has a
   fixed scope — do not cross these boundaries:
   - `docs/` → `/docs` — **Zi plugin manager user documentation only**
-    (installation, commands, usage guides). Do NOT place maintainer,
-    operational, or infrastructure guides here.
+    (installation, commands, usage guides).
   - `community/` → `/community` — Z-Shell ecosystem community content:
-    contributing, the Zsh handbook/plugin standard, ZUnit, and **maintainer /
-    operational tooling guides** (e.g. `community/10_maintainers/`).
+    contributing, the Zsh handbook/plugin standard, and ZUnit.
   - `ecosystem/` → `/ecosystem` — third-party catalog: annexes, packages, plugins.
+- **Maintainer, operational, and infrastructure runbooks do not belong on the
+  public wiki.** They live in `z-shell/.github/runbooks/` (e.g.
+  `runbooks/supabase-knowledge-search.md`). Feature implementation code
+  (Edge Functions, migrations, scripts under `supabase/` and `scripts/`) still
+  lives here in the wiki repo.
 - Each content root uses the shared `sidebars.ts` (autogenerated from directory structure) plus local `_category_.json` files for ordering.
 - Site config, plugins, and routing: `docusaurus.config.ts`. See `.github/instructions/docusaurus-config.instructions.md` for config structure, feature flags, and constraints.
 - Docusaurus client API (components, hooks, theme imports): `.github/instructions/docusaurus-api.instructions.md` — prefer native Docusaurus components over raw HTML equivalents.