PLAN: refresh stale Current block; slip MS19 + cascade MS20/MS21

Current block pointed at MS19 Phase 1 (closed); update to Phase 3
active (LLC), Phases 1/2/4 done, 5–8 pending, and refresh the
last-updated stamp.

Slip MS19 end 7/18 -> 8/01 to fit full LLC formation (subsidiary
publication runs into August), and cascade the tail off the old
overlapping windows into clean gaps: MS20 8/03–8/13, MS21 8/15–8/25
(open beta ~2 weeks later). Sync .ics, PLAN targets + release-target
line, and the 19.3 timing note. Local consistency test passes.

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

Author: n8bar

docs/PLAN.md

@@ -1,5 +1,5 @@
 # PLAN
-_Last updated: 2026-05-08_
+_Last updated: 2026-06-19_
 
 This is the human-facing execution dashboard for Release Candidate work.
 
@@ -16,21 +16,21 @@ Use [`docs/BACKLOG.md`](BACKLOG.md) for post-MVP work only.
 
 ## Current
 - Active milestone:
-  - **MS19 - Open Beta Hardening & Ops** — in progress; Phase 1 (notification coverage audit & verification) underway, later phases pre-flight.
+  - **MS19 - Open Beta Hardening & Ops** — in progress; Phases 1, 2, and 4 complete. Active phase: **Phase 3 (LLC formation)** — CyberCreek LLC (parent) approved 2026-06-17; CryptoZing subsidiary filing next. Phases 5–8 (Legal Layer, Content Promises Reconciliation, Contributor Docs, 2FA) pending.
 - Status: `active`
-- Next action: MS19 Phase 1 — notification coverage verification (Claude).
+- Next action: MS19 Phase 3 — complete LLC formation (parent publication, EINs, business bank account, CryptoZing subsidiary). Phase 5 (Legal Layer) runs as a parallel track.
 - Primary next doc: [`docs/milestones/19_OB_HARDENING_OPS.md`](milestones/19_OB_HARDENING_OPS.md)
 - Most recently completed milestone doc: [`docs/milestones/x18_PRERELEASE_CONTENT_SEO.md`](milestones/x18_PRERELEASE_CONTENT_SEO.md)
 
 ## Published Release Target
-- **First public release: mid-to-late 2027.** The open beta milestone timeline (MS21, targeting 2026-08-11) covers the open beta. The published release target accounts for post-open-beta work needed before an official first release.
+- **First public release: mid-to-late 2027.** The open beta milestone timeline (MS21, targeting 2026-08-25) covers the open beta. The published release target accounts for post-open-beta work needed before an official first release.
 
 ## Active and Upcoming Milestones
 | Status | ID | Milestone | Short intent | Target | Primary doc |
 |---|---|---|---|---|---|
-| [ ] | 19 | Open Beta Hardening & Ops | Open beta hardening before mainnet cutover: notification coverage audit; auth/password policy hardening (419-to-login redirect, session expiry logout); LLC formation (entity, EIN, bank account, operating agreement); legal layer (ToS, Privacy Policy, disclaimers, monetization-neutral copy review, UI placement); content promises reconciliation; contributor docs refresh; 2FA (email baseline, opportunistic TOTP). | 2026-07-18 | [`docs/milestones/19_OB_HARDENING_OPS.md`](milestones/19_OB_HARDENING_OPS.md) |
-| [ ] | 20 | Mainnet Cutover Preparation | Define and rehearse env flips, wallet validation, mail sanity checks, and backout steps for mainnet cutover. | 2026-07-30 | [`docs/milestones/20_MAINNET_CUTOVER_PREP.md`](milestones/20_MAINNET_CUTOVER_PREP.md) |
-| [ ] | 21 | CryptoZing.app Deployment (Open Beta) | Deploy the open beta under `cryptozing.app`, replace the GitHub Pages placeholder at `/` with the live app landing page without breaking the SEO baseline established in MS15, remove temporary mail aliasing, and complete rollout verification. | 2026-08-11 | [`docs/milestones/21_OB_DEPLOYMENT.md`](milestones/21_OB_DEPLOYMENT.md) |
+| [ ] | 19 | Open Beta Hardening & Ops | Open beta hardening before mainnet cutover: notification coverage audit; auth/password policy hardening (419-to-login redirect, session expiry logout); LLC formation (entity, EIN, bank account, operating agreement); legal layer (ToS, Privacy Policy, disclaimers, monetization-neutral copy review, UI placement); content promises reconciliation; contributor docs refresh; 2FA (email baseline, opportunistic TOTP). | 2026-08-01 | [`docs/milestones/19_OB_HARDENING_OPS.md`](milestones/19_OB_HARDENING_OPS.md) |
+| [ ] | 20 | Mainnet Cutover Preparation | Define and rehearse env flips, wallet validation, mail sanity checks, and backout steps for mainnet cutover. | 2026-08-13 | [`docs/milestones/20_MAINNET_CUTOVER_PREP.md`](milestones/20_MAINNET_CUTOVER_PREP.md) |
+| [ ] | 21 | CryptoZing.app Deployment (Open Beta) | Deploy the open beta under `cryptozing.app`, replace the GitHub Pages placeholder at `/` with the live app landing page without breaking the SEO baseline established in MS15, remove temporary mail aliasing, and complete rollout verification. | 2026-08-25 | [`docs/milestones/21_OB_DEPLOYMENT.md`](milestones/21_OB_DEPLOYMENT.md) |
 
 ## Completed Milestones
 | Status | ID | Milestone | Short intent | Primary doc |

docs/milestones.ics

@@ -13,21 +13,21 @@ UID:cz-ms18@cryptozing.app
 END:VEVENT
 BEGIN:VEVENT
 DTSTART;VALUE=DATE:20260508
-DTEND;VALUE=DATE:20260718
+DTEND;VALUE=DATE:20260801
 SUMMARY:MS19 — Open Beta Hardening & Ops
 DESCRIPTION:Open beta hardening: notification coverage, auth/password policy, LLC formation, legal layer (ToS, Privacy Policy, disclaimers, monetization-neutral copy), content promises reconciliation, contributor docs, 2FA (email baseline, optional TOTP).
 UID:cz-ms19@cryptozing.app
 END:VEVENT
 BEGIN:VEVENT
-DTSTART;VALUE=DATE:20260717
-DTEND;VALUE=DATE:20260730
+DTSTART;VALUE=DATE:20260803
+DTEND;VALUE=DATE:20260813
 SUMMARY:MS20 — Mainnet Cutover Preparation
 DESCRIPTION:Define and rehearse env flips, wallet validation, mail sanity, and backout steps for mainnet cutover.
 UID:cz-ms20@cryptozing.app
 END:VEVENT
 BEGIN:VEVENT
-DTSTART;VALUE=DATE:20260729
-DTEND;VALUE=DATE:20260811
+DTSTART;VALUE=DATE:20260815
+DTEND;VALUE=DATE:20260825
 SUMMARY:MS21 — CryptoZing.app Deployment (Open Beta)
 DESCRIPTION:Deploy the open beta under cryptozing.app, replace GitHub Pages placeholder, remove temporary mail aliasing, complete rollout verification.
 UID:cz-ms21@cryptozing.app

docs/strategies/19.3_LLC_FORMATION.md

@@ -13,7 +13,7 @@ CyberCreek LLC is formed **first**, then CryptoZing LLC is formed **with CyberCr
 
 Sequence is serial: CryptoZing's filing can't name CyberCreek as member until CyberCreek exists — which it now does (approved 2026-06-17). CryptoZing's Articles can be filed immediately; AZCC approved CyberCreek in ~9 days, so CryptoZing's approval (the MS21 name-lock) should land well ahead of the swap. CyberCreek's own publication runs in parallel on its 60-day clock (deadline 2026-08-07) and does not gate CryptoZing's filing.
 
-**Timing watch-item, not a blocker:** MS21 (deploy-time entity-name swap) is 2026-07-29 (moved out two weeks alongside the rest of MS19 to absorb LLC formation lead time). CryptoZing formation + ~3-week publication now lands ≈7/20, comfortably ahead of the swap. The swap needs the CryptoZing LLC name *locked* — i.e., AZCC Articles approved, which lands early in CryptoZing's window — not the full 3-week publication, which may finish after MS21 as a compliance step. The parallel-track design insulates MS19 regardless: Phase 5 drafts ToS/Privacy with placeholder names, and nothing in MS19 close waits on formation. If AZCC is slow approving CryptoZing's Articles, reconsider then; don't pre-slip.
+**Timing watch-item, not a blocker:** Full LLC formation must land within MS19 (by 2026-08-01); MS21's deploy-time entity-name swap starts 2026-08-15. File the CryptoZing subsidiary now: ~9-day AZCC approval + ~3-week publication lands its formation in early August — within the MS19 window and ahead of the swap. The swap only needs the CryptoZing LLC name *locked* (AZCC Articles approved), which lands well before 8/15; full publication can trail as a compliance step. The parallel-track design insulates MS19 regardless: Phase 5 drafts ToS/Privacy with placeholder names, and nothing in MS19 close waits on formation.
 
 ## Decisions made