feat(status): operator-status SSoT (patchwarden status + status.html) + auto-heal + drift-guard #97

Merged

pdurlej merged 1 commit from claude/keystone-operator-status-ssot into main

2026-06-22 23:48:30 +02:00

claude commented

2026-06-22 23:13:03 +02:00

Collaborator

What (docs-maturity keystone — merge first)

Lands the operator-facing status surface as the canonical "what is live today" source — the keystone fix from the 2026-06-16 docs-maturity audit (one drift-guarded source instead of the same fact restated in ~8 docs that each rot independently).

src/patchwarden/operator_status.py (+ docs/status.html, tests/test_status_html.py, tests/test_cli_status.py) — generated, tested status map; patchwarden status [--format json] [--output] wired into cli.py. Extracted from codex's integration-branch working tree (was uncommitted) — attribution via Co-Authored-By: codex.
ADDED auto-heal to the status data + status.html ("OpenClaw auto-heal gate", active) — the live gate (Slice C, 2026-06-10) was absent from the operator status surface (the gap I flagged when you pointed me at status.html).
docs/architecture.md — L4 status note (gate live; OSS extraction still D4-future), removed the stale "(when reviewer lanes land in #37 + #28-#30)" qualifier, and added a complete L2 module inventory (18 modules — 4+ shipped modules were missing).
tests/test_docs_module_inventory.py — NEW drift-guard: every src/patchwarden module must be named in docs/architecture.md (docs sibling of the D20 lint). Stops the "feature ships, docs rot" pattern.

Merge order / conflicts

Merge this before claude/cloud-review-enforcement (both touch cli.py, different regions).
Independent of the schema + docs-sweep PRs (disjoint files).

Safety

312 tests green; stdlib-only; status surface is read-only, no network, never merges. patchwarden status + --format json smoke-confirmed (auto-heal gate present).

From the docs-maturity wave (items #1 + #2). Do not merge automatically — operator merge only.

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

## What (docs-maturity keystone — merge first) Lands the operator-facing status surface as the **canonical "what is live today" source** — the keystone fix from the 2026-06-16 docs-maturity audit (one drift-guarded source instead of the same fact restated in ~8 docs that each rot independently). - **`src/patchwarden/operator_status.py`** (+ `docs/status.html`, `tests/test_status_html.py`, `tests/test_cli_status.py`) — generated, tested status map; **`patchwarden status [--format json] [--output]`** wired into `cli.py`. Extracted from codex's integration-branch working tree (was uncommitted) — attribution via `Co-Authored-By: codex`. - **ADDED auto-heal to the status data + status.html** ("OpenClaw auto-heal gate", active) — the live gate (Slice C, 2026-06-10) was absent from the operator status surface (the gap I flagged when you pointed me at status.html). - **`docs/architecture.md`** — L4 status note (gate live; OSS extraction still D4-future), removed the stale "(when reviewer lanes land in #37 + #28-#30)" qualifier, and added a complete **L2 module inventory** (18 modules — 4+ shipped modules were missing). - **`tests/test_docs_module_inventory.py`** — NEW **drift-guard**: every `src/patchwarden` module must be named in `docs/architecture.md` (docs sibling of the D20 lint). Stops the "feature ships, docs rot" pattern. ## Merge order / conflicts - **Merge this before** `claude/cloud-review-enforcement` (both touch `cli.py`, different regions). - Independent of the schema + docs-sweep PRs (disjoint files). ## Safety - **312 tests green**; stdlib-only; status surface is read-only, no network, never merges. `patchwarden status` + `--format json` smoke-confirmed (auto-heal gate present). From the docs-maturity wave (items #1 + #2). **Do not merge automatically — operator merge only.** Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Rows
Columns