docs(04-08): complete harden-clean-up-optional plan 04-08 — STATE.md advance to 6/7

State counter advance after Plan 04-08 closure:
- progress.completed_plans: 27 -> 28
- Current Plan position: 5 -> 6 (Plan 04-05 fetch+XHR queued next)
- last_updated timestamp + last_activity bumped to 2026-05-22

Note: the human-readable "Plan: 6 of 7" line in Current Position reflects the
original Phase 4 plan-count of 7; the ROADMAP-side phase tracker now shows
5/8 (Plan 04-08 inserted Wave 5.5 per debug session-2 verdict authorization).
This is a known cosmetic gap in the SDK's state.advance-plan handler; the
frontmatter total_plans=31 / completed_plans=28 are correct.

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

.planning/STATE.md

@@ -4,8 +4,8 @@ milestone: v2.0.0
 milestone_name: milestone
 status: executing
 stopped_at: "Completed 04-08-PLAN.md (methodology reframe; A33 lands; ROADMAP SC #1 CLOSED via video-file MediaStream + SYNC install + LAZY first-frame; spike re-run 1.8MB vs 8505; UAT 34/34 + vitest 184/184 GREEN; architecture UNCHANGED per debug session-2)"
-last_updated: "2026-05-22T09:06:10.449Z"
-last_activity: 2026-05-21
+last_updated: "2026-05-22T09:07:54.692Z"
+last_activity: 2026-05-22
 progress:
   total_phases: 4
   completed_phases: 3
@@ -29,9 +29,9 @@ no server, no password leaks.
 
 Phase: 04 (harden-clean-up-optional) — EXECUTING
 Phase 4 of 4 (Hardening — optional) — Plan 04-01 closed (audit P1 polish 3/3); 6 plans remain (04-02 build hygiene queued NEXT in Wave 1)
-Plan: 5 of 7
+Plan: 6 of 7
 Status: Ready to execute
-Last activity: 2026-05-21
+Last activity: 2026-05-22
 
 Progress: [█████████░] 90%