Address review feedback: restore Diataxis, fix paths

- Restore Diataxis framework reference as the underlying authoring
  model (it still applies, just not to folder structure)
- Remove reference to transient restructuring plan document
- Add docs/toolhive/ base path to all folder references so
  contributors place files correctly

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: danbarr

.claude/skills/docs-review/SKILL.md

@@ -65,9 +65,9 @@ Watch for these telltale signs of AI-generated docs that need human intervention
 
 ### Section Structure and Navigation
 
-The docs follow a product-area-based information architecture. Check:
+The docs follow a product-area-based information architecture under `docs/toolhive/`. Check:
 
-- **Self-contained sections**: Product-specific content belongs in its product section (`guides-ui/`, `guides-cli/`, `guides-k8s/`, `guides-vmcp/`, `guides-registry/`), not in a shared section.
+- **Self-contained sections**: Product-specific content belongs in its product section (`docs/toolhive/guides-ui/`, `guides-cli/`, `guides-k8s/`, `guides-vmcp/`, `guides-registry/`), not in a shared section.
 - **Quickstarts in product sections**: Quickstarts live inside their product section, not in a separate top-level section.
 - **Integration placement**: Third-party integration guides (ngrok, Vault, OpenTelemetry, Okta, etc.) belong in `integrations/`, not in a product section.
 - **Next steps section**: Every how-to guide and tutorial page must end with a "Next steps" section containing 1-3 forward links. Missing "Next steps" is a primary issue.

.claude/skills/upstream-release-docs/SKILL.md

@@ -124,12 +124,12 @@ Apply the approved changes:
 
 2. **Create new pages** for new features that lack existing documentation. Default to documenting new features rather than skipping them:
 
-   **Page placement** — the docs are organized by product area. Place new content in the correct section:
-   - **Product-specific guides** go in the relevant product section (`guides-ui/`, `guides-cli/`, `guides-k8s/`, `guides-vmcp/`, `guides-registry/`).
-   - **Third-party integration guides** go in `integrations/`.
-   - **Cross-cutting concepts** go in `concepts/`.
-   - **Per-MCP-server usage guides** go in `guides-mcp/`.
-   - **Reference material** goes in `reference/`.
+   **Page placement** — the docs are organized by product area under `docs/toolhive/`. Place new content in the correct section:
+   - **Product-specific guides** go in the relevant product section (`docs/toolhive/guides-ui/`, `guides-cli/`, `guides-k8s/`, `guides-vmcp/`, `guides-registry/`).
+   - **Third-party integration guides** go in `docs/toolhive/integrations/`.
+   - **Cross-cutting concepts** go in `docs/toolhive/concepts/`.
+   - **Per-MCP-server usage guides** go in `docs/toolhive/guides-mcp/`.
+   - **Reference material** goes in `docs/toolhive/reference/`.
    - Check the project's CLAUDE.md "Information architecture" section for the full placement rules.
 
    **Diataxis separation** — create separate pages per document type, not one combined page:

AGENTS.md

@@ -80,7 +80,9 @@ The documentation should be accessible to a wide range of technical users, inclu
 
 ## Information architecture
 
-The docs are organized by **product area**, with each section self-contained so a reader can complete their journey without leaving it. Cross-cutting content lives in dedicated shared sections. The authoritative restructuring plan is in `/docs-restructuring/1-docs-restructuring-plan.md`.
+This project follows the [Diataxis framework](https://diataxis.fr/) for documentation authoring - each page is a tutorial, how-to guide, reference, or explanation. The site is organized by **product area**, with each section self-contained so a reader can complete their journey without leaving it. Cross-cutting content lives in dedicated shared sections.
+
+All documentation lives under `docs/toolhive/`. Folder paths below are relative to that root.
 
 ### Design principles