feat(WP-0008): reassessment, task-status canon, archive hygiene

- Post-WP-0007 reassessment and SCOPE/README updates
- AGENTS.md + workplan-convention task status canon migration
- examples/warden.production.example.yaml for production OpenBao
- Archive WP-0004 through WP-0007 to workplans/archived/260617-*
- WP-0008 T1/T3/T4 done; T2/T5 wait on operator/flex-auth

.claude/rules/workplan-convention.md

@@ -25,4 +25,24 @@ Ecosystem todos from other agents arrive as `[repo:ops-warden]` hub tasks —
 visible at session start. Pick one up by creating the workplan file, then registering
 the workstream.
 
+**Task block format** (one per `##` section in workplan files):
+
+```
+## Task Title
+
+```task
+id: WARDEN-WP-NNNN-T01
+status: wait | todo | progress | done | cancel
+priority: high | medium | low
+state_hub_task_id: "<uuid>"   # written by fix-consistency — do not edit
+```
+
+Task description text.
+```
+
+Canonical task statuses (State Hub InfoTechCanon): `wait`, `todo`, `progress`,
+`done`, `cancel`. Use `wait` for tasks blocked on external dependencies (not
+`blocked` — that alias maps to `wait` during migration). Progression:
+`todo` → `progress` → `done`.
+
 <!-- Ralph Loop rules and HEUREKA sequence: ~/.claude/CLAUDE.md — do not duplicate here -->