docs: close STATE-WP-0080, move templating removal to STATE-WP-0079-T04

T01-T03 are done and T05-T08 were already handed to RMGR-WP-0004. T04's
gates (RMGR-WP-0004-T06, STATE-WP-0079-T04) remain open, and the task
always specified that removal land inside the 0079 strangler rather than
as an isolated breaking change. Cancel it here with a pointer, record the
inherited residual in 0079-T04, and mark the workplan finished.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

workplans/STATE-WP-0079-retirement-strangler.md

@@ -95,6 +95,14 @@ state_hub_task_id: "db5291f2-3801-40fa-abf2-ceb0e77687c9"
 Implement strangler handoffs coordinated with RMGR-WP-0001 and HUB-WP-0004.
 Compatibility tests for each dispositioned route family.
 
+**Inherited (2026-08-19) from `STATE-WP-0080-T04`:** this slice now also owns
+deletion of the templating path in `statehub_register.py` — `INTENT.md`
+generation, the `AGENTS.md` / `CLAUDE.md` / `.custodian-brief.md` templates,
+`project_rules/`, and bootstrap-workplan generation. The code is dead-but-present:
+project repos are already routed to `rmgr scaffold`. Gate the deletion on
+`RMGR-WP-0004-T06` proving byte-identical durable output and idempotent
+re-scaffolding.
+
 ## Retire legacy surfaces
 
 ```task

workplans/STATE-WP-0080-register-project-flavor-awareness.md

@@ -4,7 +4,7 @@ type: workplan
 title: "statehub register: stop repo scaffolding, hand off to repo-manager"
 domain: infotech
 repo: state-hub
-status: active
+status: finished
 owner: codex
 topic_slug: infotech
 created: "2026-08-16"
@@ -135,11 +135,11 @@ the boundary violation during cutover.
 `disposition: move`, `owner: repo-manager`, capability `repo-onboarding`.
 No inventory edit required.
 
-## Remove the templating path
+## Moved: remove the templating path
 
 ```task
 id: STATE-WP-0080-T04
-status: wait
+status: cancel
 priority: low
 state_hub_task_id: "342aa5e8-96d0-4832-be60-f48815a86f71"
 ```
@@ -161,6 +161,17 @@ now recorded done because T01/T02 above supply its project/`GOAL.md` adapter;
 the broader `STATE-WP-0079-T04` move/replace slice is still `todo`. Do not
 delete this path until both gates close.
 
+**Cancelled (2026-08-19) — moved to `STATE-WP-0079-T04`.** Both gates above are
+still open, and this task always specified that removal should land inside
+`STATE-WP-0079`'s strangler rather than as an isolated breaking change. Holding
+`STATE-WP-0080` open to wait on another workplan's slice adds no information:
+the removal is now recorded where it will actually be executed, alongside the
+other move/replace slices and their compatibility tests.
+
+The guard and the delegation — this workplan's own contribution — are live and
+unchanged. The templating code in `statehub_register.py` is dead-but-present
+until `RMGR-WP-0004-T06` proves byte-identical durable output.
+
 ## Moved: generated templates and briefs
 
 ```task
@@ -222,3 +233,21 @@ work; the decision settled that repository standards belong there regardless of
 timing, and `RMGR-WP-0004` now carries the whole implementation.
 
 Retained as the record of where the retarget originated.
+
+## Outcome
+
+Closed 2026-08-19. The defect is contained: `statehub register` no longer writes
+non-conformant files into project-flavor repositories, and fresh project repos
+are scaffolded by `rmgr scaffold` through the dual-run adapter. Repository
+standards and representation now sit with `repo-manager`, per decision
+`747011c6`.
+
+| Task | Disposition |
+| --- | --- |
+| T01 guard | done |
+| T02 delegation | done |
+| T03 inventory disposition | done (already correct) |
+| T04 templating removal | moved to `STATE-WP-0079-T04` |
+| T05–T08 | moved to `RMGR-WP-0004-T02/T04/T06`, or superseded |
+
+Nothing in this workplan remains executable here.