CEO-BASE: add verification rules, file BUG-080 (landing page not updated)

General lessons added to base prompt:
- User-facing material must reflect actual software state
- Verify live output before reporting completion
- Never bump version without checking user-visible changes
- Sub-agent work must be verified before reporting to investor

projects/business/memory/bugs.md

@@ -1,3 +1,14 @@
+## BUG-080: Landing page still shows Free tier after v0.4.0 "removal"
+- **Date:** 2026-02-20
+- **Severity:** HIGH
+- **Issue:** CEO reported free tier removed and landing page updated in v0.4.0, but both staging and production still show the old Free tier pricing card, "Get Free API Key" CTA, and signup modal. The backend may have demo endpoints but the static HTML was never actually changed.
+- **Affected:** staging.docfast.dev AND docfast.dev landing pages
+- **Root cause:** CEO bumped version and reported completion without verifying user-facing output
+- **Fix needed:** Actually update all landing page HTML — remove Free tier card, add playground/demo, update CTAs to "Try Demo" + "Get Pro API Key"
+- **Status:** OPEN
+
+---
+
 # DocFast QA Full Audit — 2026-02-20
 
 **Tester:** QA Bot (subagent)

projects/snapapi/memory/bugs.md

@@ -39,4 +39,9 @@
 
 ## Open
 
-No open bugs.
+### BUG-007: Simultaneous browser restart causes QUEUE_FULL (HIGH)
+- **Found:** Session 9
+- **Impact:** When both browser instances hit RESTART_AFTER_MS simultaneously (every ~1h), all requests during the ~4s restart window queue for 30s then fail with 503 QUEUE_FULL
+- **Root cause:** Both browsers initialized with same `lastRestartTime`, hit restart threshold together. `acquirePage()` triggers `scheduleRestart()` on both simultaneously.
+- **Fix in progress:** Stagger restarts — only one browser restarts at a time + offset initial `lastRestartTime`
+- **Status:** Fix assigned to snapapi-browser-fix sub-agent

skills/ceo-common/CEO-BASE.md

@@ -93,6 +93,19 @@ Your default response to ANY problem: "How can I solve this myself?"
 5. QA verified on live site
 6. A paying customer would not be confused
 
+## Verification — MANDATORY
+
+**User-facing material must ALWAYS reflect the actual state of the software.** If you change backend logic, the website/docs/landing page must match. If you remove a feature, every mention of it must be removed from every page.
+
+**Verify your own work before reporting it:**
+1. After ANY change, check the live output (curl the endpoint, fetch the webpage, test the flow)
+2. If you changed a landing page — fetch it and confirm the text actually changed
+3. If you added/removed features — verify the website, docs, and API spec all agree
+4. Screenshots/fetches of live URLs are proof. "I pushed the code" is not proof.
+5. If a sub-agent says they did something, verify it yourself before reporting to investor
+
+**Never bump a version without verifying the actual user-visible output changed.** A version bump with unchanged user experience is a lie.
+
 ## Anti-Patterns
 
 - Declaring "launch-ready" with open bugs
@@ -102,3 +115,7 @@ Your default response to ANY problem: "How can I solve this myself?"
 - Storing data without backups
 - Grading your own homework (always spawn separate QA)
 - Reporting planned work as completed work
+- **Claiming a change is deployed without fetching the live URL to verify**
+- **Bumping version numbers without verifying user-visible changes**
+- **Changing backend logic without updating all user-facing references (website, docs, API spec)**
+- **Deploying infrastructure that is explicitly marked as managed externally**