ZS 2026-06-04 was an erroneous desk-carried earnings date seeded in the R15 cybersec-leg work. The official Zscaler IR date was 2026-05-26 (after market close), per Zscaler's 2026-05-07 press release, recorded in workflow/calendar-overrides.json (verified-official, verified_at: 2026-05-20) and verified in R23-E (2026-05-20-r23e-cybersec-catalyst-prep).

What this supersedes

The stale 2026-06-04 references live in dated, immutable artifacts; this event is the explicit corpus-wide supersession for all of them:

• 2026-05-20-r15-cybersec-cohort-parabolic-stacked-catalysts — "ZS next: 2026-06-04", review_at: 2026-06-04
• 2026-05-20-r17-cybersec-fundamentals-hardening — "ZS Q3 FY26 print 2026-06-04", review_at: 2026-06-04
• 2026-05-20-r15-cycle-insight-decisions, 2026-05-20-r17-cycle-insight-decisions.md — review_at: 2026-06-04 / "ZS Q3 FY26 fragility watch (2026-06-04)"
• 2026-05-20-r15-risk-on-tech-rotation-cybersec-leg-added — already corrected in place 2026-05-21 with correction_status: corrected + correction_notice (PUBLISH lane, deadline-gated)
• log 2026-05-20 entries — pre-correction lineage, kept as-is

Keep the dated artifacts as pre-correction lineage only. Consumers should treat this correction (and workflow/calendar-overrides.json) as the active calendar reconciliation. The corrected catalyst cluster: ZS 2026-05-26, PANW 2026-06-02, CRWD 2026-06-03 (all after close).