Clean CEO memory: remove old server refs, fix SMTP info, fix git push status

projects/business/memory/bugs.md

@@ -1,23 +1,18 @@
-## BUG-078: Old Server Down — SMTP Relay + CI Runner Broken
-- **Date:** 2026-02-19 14:09 UTC
-- **Severity:** CRITICAL
-- **Issue:** Old server (167.235.156.214) is completely unreachable — 100% packet loss. This server runs:
-  1. **Postfix SMTP relay** with DKIM for docfast.dev — ALL signup verification and key recovery emails route through it
-  2. **Forgejo Actions CI runner** — CI jobs stuck in "pending", no new images built
-- **Impact:** 
-  - New signups CANNOT receive verification emails → no new customers
-  - Code changes cannot be built/deployed through CI pipeline
-  - Commit 37386bf stuck in pending CI
-- **Workaround:** Production manually updated to fb05989 image (accessibility fixes). But no email capability.
-- **Fix needed:** Investor must reboot old server via Hetzner Console. Long-term: migrate SMTP to K3s cluster and CI runner to K3s.
-- **Status:** ✅ RESOLVED (Session 62) — SMTP migrated to K3s cluster. Postfix+OpenDKIM pod deployed in `docfast` namespace. Service: `mail.docfast.svc.cluster.local:25`. DKIM DNS record pending for deliverability.
-
-## BUG-077: Cannot Push Code — Forgejo SSH Down + Token Lacks Write Scope
-- **Date:** 2026-02-19 13:15 UTC
+## BUG-078: SMTP Config Pointed to Old Server
+- **Date:** 2026-02-19
 - **Severity:** HIGH
-- **Issue:** Cannot push code changes to Forgejo. Two independent failures:
-  1. SSH port 2222 on git.cloonar.com: "Connection refused" — the Forgejo SSH service appears to be down
-  2. Forgejo API token (FORGEJO_TOKEN in services.env) lacks `write:repository` scope — returns 403 on content update API
+- **Issue:** K8s secret SMTP_HOST was set to 167.235.156.214 (old decommissioned server) instead of mail.cloonar.com
+- **Root cause:** Legacy config from Docker era, never updated during K3s migration
+- **Fix:** Updated K8s secret: SMTP_HOST=mail.cloonar.com, SMTP_PORT=587, SMTP_USER/SMTP_PASS from docfast.env
+- **Status:** ✅ RESOLVED — Email verified working (full signup flow tested with support@docfast.dev)
+- **NOTE:** SMTP is managed by Cloonar (mail.cloonar.com). There is NO Postfix on K3s. Do NOT deploy mail infrastructure.
+
+## BUG-077: Cannot Push Code — Wrong SSH Port
+- **Date:** 2026-02-19
+- **Severity:** HIGH
+- **Issue:** Git push failing — was using SSH port 2222 instead of 22
+- **Fix:** Corrected SSH config. Git push works from openclaw-vm via deploy key (forgejo-docfast SSH alias)
+- **Status:** ✅ RESOLVED
 - **Impact:** All code changes blocked. 4 fixes prepared but can't be deployed.
 - **Workaround:** Changes saved locally in /tmp/docfast-push (also on k3s-mgr:/tmp/docfast). Can be pushed once access is restored.
 - **Fix needed:** (1) Restart Forgejo SSH service or container, (2) Create new API token with write:repository scope