docs: migrate work tracking to Redmine system of record

Replace STATUS.md checklists with a Redmine ticket index. All work
status, completion tracking, and issue management now lives in Redmine
(version: Potential to Kinetic Ready, due 2026-09-30). AGENTS.md gains
a Redmine Tracking Policy section with rules for ticket references,
closing procedures, and STATUS.md's new read-only role.

AGENTS.md

@@ -1,8 +1,9 @@
 # Agent Guidelines
 
 **Top-level files:** [`README.md`](README.md) (project overview),
-[`STATUS.md`](STATUS.md) (living status, agent-maintained),
-[`docs/docmap.md`](docs/docmap.md) (documentation index). Everything else
+[`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.
 
 ## Repository Layout
@@ -54,12 +55,34 @@ vendor/             Vendored KNELShellFramework
    justification. A script that emits any diagnostic is a protocol violation.
    Non-bash scripts (PHP with `.sh` shebang `#!/usr/bin/php`, etc.) are exempt.
 
+## Redmine Tracking Policy
+
+**Redmine is the system of record for all work.** Do not track status,
+checklists, or TODOs in repo files. Use Redmine tickets instead.
+
+- **URL:** https://projects.knownelement.com
+- **Version:** Potential to Kinetic Ready (due 2026-09-30)
+- **Project:** Known Element Enterprises - Technology & Facility Services (id 55)
+
+### Rules
+1. **Every piece of work** (feature, fix, deployment, config change) gets a
+   Redmine ticket. If one doesn't exist, create it.
+2. **Reference tickets in docs and commits** using `[#NNN]` notation.
+   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.
+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
 
 **Docs and code must be kept in sync.** After any work session, an agent MUST:
 
-1. **Update [`STATUS.md`](STATUS.md)** — reflect completed work, new issues,
-   changed infrastructure state. This file is human read-only; agents own it.
+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.
@@ -104,5 +127,6 @@ vendor/             Vendored KNELShellFramework
 
 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 current state and
-[`proxmox/docs/PROJECT.md`](proxmox/docs/PROJECT.md) for the fleet report.
+[`STATUS.md`](STATUS.md) 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).