docs: migrate all documentation to Discourse wiki topics

All knowledge docs (architecture, runbooks, references, audits, policies)
have been migrated to community.turnsys.com as wiki topics in the VP
TechOps category. Discourse is now the canonical source of truth for
documentation; git edit history no longer serves as the doc changelog.

37 .md files converted to short pointers linking to their Discourse
topics. AGENTS.md updated with new documentation workflow policy.
Code (scripts, configs, playbooks) remains authoritative in git.

AGENTS.md

@@ -1,10 +1,32 @@
 # Agent Guidelines
 
-**Top-level files:** [`README.md`](README.md) (project overview),
-[`STATUS.md`](STATUS.md) (ticket index + infra summary),
-[`docs/docmap.md`](docs/docmap.md) (documentation index). All work is
-tracked in [Redmine](https://projects.knownelement.com). Everything else
-lives in subdirectories.
+## Documentation policy (IMPORTANT)
+
+**Discourse is the canonical source of truth for all knowledge documentation.**
+Knowledge docs (architecture, runbooks, references, audits, policies) have been
+migrated to [community.turnsys.com](https://community.turnsys.com/c/vp-techops)
+as wiki topics in the **VP TechOps** category.
+
+All `.md` files in this repo (except `AGENTS.md` and `LICENSE`) are now
+**pointers** that link to their corresponding Discourse topic. **Do not update
+documentation content in git** — edit the Discourse wiki topic instead. Git
+edit history no longer serves as the documentation changelog; Discourse
+preserves wiki edit history automatically.
+
+Code (scripts, configs, playbooks) still lives in git as the source of truth
+for executables. Only *documentation* moved to Discourse.
+
+## Top-level files
+
+All `.md` files now point to Discourse. The key pointers:
+
+| File | Points to | Discourse topic |
+|------|-----------|-----------------|
+| `README.md` | Project overview | [#296](https://community.turnsys.com/t/296) |
+| `STATUS.md` | Ticket index + infra summary | [#297](https://community.turnsys.com/t/297) |
+| `docs/docmap.md` | Documentation index | [#296](https://community.turnsys.com/t/296) |
+
+Work tracking stays in [Redmine](https://projects.knownelement.com).
 
 ## Repository Layout
 
@@ -71,37 +93,28 @@ checklists, or TODOs in repo files. Use Redmine tickets instead.
    Example: `[#367] Rebuilt k3s control plane after cnode wipe`.
 3. **When work completes**, update the ticket: set done ratio to 100%,
    add a note describing what was done and where the code lives, then close.
-4. **STATUS.md is a read-only snapshot** — it contains a ticket index and
-   infrastructure summary only. Do not add checklists or status items.
+4. **Operations Status** lives on Discourse ([topic #297](https://community.turnsys.com/t/297)) — update that wiki topic if the infrastructure summary needs refreshing. The `STATUS.md` file in git is now a pointer only.
 5. **Link code to tickets** — ticket descriptions and notes should reference
    the relevant file paths in this repo (e.g., `dcinfra/ups/`).
 
-## Automatic Gardening Protocol
+## Documentation Workflow
 
-**Docs and code must be kept in sync.** After any work session, an agent MUST:
+**Discourse is the source of truth for all knowledge docs.** After any work
+session, an agent MUST:
 
-1. **Update [`STATUS.md`](STATUS.md)** — update the ticket index table if
-   tickets were created or closed. This file is a read-only snapshot;
-   do not add inline status tracking (use Redmine).
-2. **Update [`docs/docmap.md`](docs/docmap.md)** — if a doc was added,
-   removed, or substantively changed, update the table and "Last Reviewed"
-   date.
-3. **Grep for stale paths** — `grep -rn 'old/path' --include='*.md'` after
-   any rename or restructure. Fix all references in the same commit.
-4. **Verify new docs are linked** — every new `.md` file must appear in
-   [`docs/docmap.md`](docs/docmap.md) and be linked from at least one other
-   doc.
-5. **If a new top-level directory was created, update ALL directory listings:**
-   - [`README.md`](README.md) → "Directory Structure" table
-   - [`AGENTS.md`](AGENTS.md) → "Repository Layout" code block
-   - [`AGENTS.md`](AGENTS.md) → "Key Scripts" table (if the directory has
-     an entrypoint script)
-   Missing any one of these is a protocol violation.
-6. **Self-audit before commit.** Before committing, run:
-   ```
-   grep -lE 'new_dir_name' README.md AGENTS.md docs/docmap.md STATUS.md
-   ```
-   Every new top-level directory must appear in all four files.
+1. **Update Discourse wiki topics** — if infrastructure facts changed (new
+   VM, IP change, host retired), edit the relevant wiki topic at
+   [community.turnsys.com/c/vp-techops](https://community.turnsys.com/c/vp-techops).
+2. **Update the Operations Status topic** ([#297](https://community.turnsys.com/t/297))
+   if tickets were opened or closed.
+3. **Grep for stale paths in code** — `grep -rn 'old/path' --include='*.sh'`
+   after any rename or restructure. Fix all references in the same commit.
+4. **If a new top-level directory was created**, update:
+   - `AGENTS.md` → "Repository Layout" code block
+   - `AGENTS.md` → "Key Scripts" table (if it has an entrypoint script)
+   - Create a new Discourse wiki topic for any documentation
+5. **Self-audit before commit.** Code changes must be internally consistent.
+   Documentation changes go to Discourse, not git.
 
 ## Key Scripts
 
@@ -121,12 +134,16 @@ checklists, or TODOs in repo files. Use Redmine tickets instead.
 
 ## Key Docs
 
-→ **See [`docs/docmap.md`](docs/docmap.md) for the full documentation index.**
+→ **All documentation lives on Discourse:**
+  [community.turnsys.com/c/vp-techops](https://community.turnsys.com/c/vp-techops)
+
+→ All `.md` files in this repo are pointers to Discourse topics.
 
 ## Project Context
 
 Solo-founder R&D Proxmox cluster in a private residence. Shoestring budget.
-Production lives on a Cloudron VPS in Reston VA. See
-[`STATUS.md`](STATUS.md) for the ticket index and infrastructure summary.
+Production lives on a Cloudron VPS in Reston VA. See the
+[Operations Status topic](https://community.turnsys.com/t/297) for the ticket
+index and infrastructure summary.
 All work is tracked in [Redmine](https://projects.knownelement.com)
 (version: Potential to Kinetic Ready, due 2026-09-30).