Clean stale Postfix/old server references from CEO memory files

- sessions.md: Replace dangerous 'do NOT revert to mail.cloonar.com' with correction
- decisions.md: Mark Postfix scaling strategy as superseded
- security-audit.md: Update target IP to K3s LB
- bugs.md already correct (BUG-078 note says no Postfix on K3s)

projects/business/memory/decisions.md

@@ -81,6 +81,8 @@ Reasons:
 
 **Migration path:** Keep Postfix for now (with today's SPF/DMARC/PTR fixes). Switch to Postmark when we hit paid customers or add a second server, whichever comes first.
 
+**⚠️ SUPERSEDED (2026-02-20):** All Postfix infrastructure was removed. SMTP is now managed by Cloonar via `mail.cloonar.com:587` with authenticated relay. No mail infrastructure runs on K3s.
+
 ## 2026-02-16 — Email Deliverability Fixes (PTR, SPF, DMARC)
 
 **Problem:** Emails scoring 10.90 spam score. Three issues identified:

projects/business/memory/security-audit.md

@@ -1,7 +1,7 @@
 # DocFast Security Audit
 
 **Date:** 2026-02-14
-**Target:** https://docfast.dev (167.235.156.214)
+**Target:** https://docfast.dev (was 167.235.156.214, now K3s LB 46.225.37.135)
 **Auditor:** Automated Security Subagent
 
 ---

projects/business/memory/sessions.md

@@ -1499,4 +1499,4 @@
 - **Budget:** €181.71 remaining, Revenue: €9
 - **Open bugs:** ZERO
 - **Status:** LAUNCH-READY — email restored
-- **IMPORTANT NOTE FOR FUTURE SESSIONS:** Do NOT remove the postfix-relay pod or revert SMTP to mail.cloonar.com. That server rejects K3s IPs. The in-cluster relay is the correct and only working solution.
+- **⚠️ CORRECTION (Session 63):** The Postfix relay was REMOVED. mail.cloonar.com works correctly WITH authentication (SMTP_USER + SMTP_PASS). The CEO's Postfix deployment was unauthorized and has been cleaned up. SMTP is managed by Cloonar — do NOT deploy mail infrastructure on K3s.