docs: fix phase references after M6->M7 re-sequencing

The re-sequence renamed the cleanup phase M6->M7 and inserted the fold at M6.
Three references still meant the old M6: §2 "After M6" end-state, the cleanup
task's "M1-M6 are complete" note, and §10 "M1-M6 migration is complete".
Updated to the final phase / M1-M7 so the plan-of-record is internally
consistent.

Constraint: docs only; corrects dangling phase references introduced by the re-sequence; no code change
Tested: docs validator 0 errors
Confidence: high
Roadmap-Status: unchanged

Author: johnteee

docs/generated/docs-inventory.md

@@ -414,7 +414,7 @@ Do not edit this file manually — regenerate instead.
 | `ops/security-hardening.md` | working | 11733 | `0a385c7dab82` |
 | `ops/troubleshooting.md` | working | 9127 | `4921b6d50f5c` |
 | `permission-and-approval-playbook.md` | working | 6560 | `813bc74bb156` |
-| `plans/adr-0032-m1-m6-work-plan-2026-06-13.md` | archive | 46121 | `a6ed90c9c72f` |
+| `plans/adr-0032-m1-m6-work-plan-2026-06-13.md` | archive | 46234 | `6d6c5a383472` |
 | `plans/agent-ecosystem-acceptance-roadmap-2026-05-31.md` | archive | 29099 | `7c4a4972cfeb` |
 | `plans/community-pain-points-response-plan-2026-06-05.md` | archive | 7276 | `571d010133ad` |
 | `plans/competitive-positioning-plan-2026-05-31.md` | archive | 8726 | `d16dfd2bdd99` |

docs/plans/adr-0032-m1-m6-work-plan-2026-06-13.md

@@ -35,7 +35,8 @@ Current read as of 2026-06-13:
 
 ## 2. Target Shape
 
-After M6, TeaAgent should have one run-lifecycle event spine:
+After the final phase (M7 post re-sequencing — see §5/§14), TeaAgent should
+have one run-lifecycle event spine:
 
 ```text
 AgentRunner emits typed RunEvents
@@ -703,8 +704,8 @@ commit once Slice A is green.
 - Acceptance Criteria:
   - No orphaned eventing validator errors.
   - Full acceptance tier passes.
-  - ADR 0032 receives a supersession/update note that M1-M6 are complete or
-    lists remaining compatibility shims.
+  - ADR 0032 receives a supersession/update note that all phases (M1-M7 post
+    re-sequencing) are complete or lists remaining compatibility shims.
 - Tests:
   - Full acceptance tier.
   - Docs consistency.
@@ -789,7 +790,7 @@ python3 scripts/run_acceptance_tier.py --tier all
 
 ## 10. Definition of Done
 
-The ADR 0032 M1-M6 migration is complete only when:
+The ADR 0032 migration (M1-M7 post re-sequencing, §14) is complete only when:
 
 - All milestone exit criteria in section 7 are met.
 - `AuditLogger.record()` remains as a compatibility API but runner-owned audit