Synchronize project documentation and remove obsolete state files

[Sekiph82]

Purpose

Bring all project documentation to one authoritative current state after the Etsy compliance deployment, retention automation, and first successful scheduled cleanup.

Changes

• Synchronized current production status into PROJECT_STATUS.md (202 -> 47 lines): production/environment status, blockers, owner actions, next action only.
• Reduced TASKS.md (734 -> 50 lines) to active work only, classified Blocked Externally / Pending Owner Action / Deferred / Recently Completed.
• Simplified HANDOFF.md (795 -> 38 lines) to a single next-session resume point — critical environment facts, the merge=deploy warning, current branch/PR state, exact next step, safety constraints. The 9 stacked full session transcripts are superseded by CHANGELOG_AI.md (full detail, unchanged) and DECISIONS.md (durable decisions) — cross-checked first; one real gap found and fixed (the third-session Stripe account-deletion resolution had never been recorded as its own DECISIONS.md entry).
• Updated README.md: added a Production URLs section, corrected the sprint count, corrected the Cache/Queue row (no Celery worker is actually deployed — scheduled/background tasks run inline or as DigitalOcean Scheduled Jobs).
• Synchronized every Etsy compliance doc (ETSY_COMPLIANCE_AUDIT.md, ETSY_FEATURE_MATRIX.md, ETSY_PRODUCTION_READINESS.md, ETSY_DATA_RETENTION.md) with current-status banners: Option A retention confirmed live (first real execution succeeded 2026-07-15, 0 rows deleted, no errors), 982 tests as the authoritative count, appeal drafted but explicitly not submitted.
• Trimmed ETSY_APPEAL_CHECKLIST.md to only the pre-submission owner actions that are still genuinely open; repointed its draft-message reference at ETSY_FINAL_APPEAL_DRAFT.md.
• Fixed a real active-contradiction: docs/operations/DEPLOYMENT.md, DNS_SSL.md, and DIGITALOCEAN_DEPLOY.md all presented "Vercel + Render" as the current chosen hosting, when production has run on DigitalOcean App Platform + Cloudflare since 2026-07-06. VERCEL_RENDER_DEPLOY.md and PRODUCTION_SMOKE_TEST.md are marked superseded/historical-reference rather than deleted (the plan was real, just abandoned before it was ever provisioned).
• docs/operations/WORKERS.md: recorded the retention-cleanup job's first real execution.
• DECISIONS.md: added the missing Stripe account-deletion decision entry, and a new standing rule that Private Beta stays enabled until Etsy's ban is resolved regardless of engineering readiness.
• CHANGELOG.md: replaced stale present-tense "moving to DigitalOcean" language with rollup entries for the 2026-07-06 launch and 2026-07-14 Etsy-compliance/retention arc.
• CHANGELOG_AI.md: added a one-line role banner — it's the designated full-engineering-history archive the three trimmed files now defer to, not deleted or merged away.

Deleted files

None. Every file initially considered for deletion had either unique compliance-audit value, or (in ETSY_SUPPORT_QUESTIONS.md's case) was a live anchor target: its Q1/Q2/Q3 question numbering is cited by name in 5 production code comments (config.py, ai_tools.py, listing_health.py, featurePages.ts, EtsySeoSection.tsx) as the pending-clarification pointer for the ALLOW_ETSY_DATA_TO_AI gate. Deleting or renumbering it would orphan those comments, and fixing the comments is a code change out of scope for a docs-only branch. It's marked superseded-in-prose (use ETSY_FINAL_APPEAL_DRAFT.md instead) but kept byte-stable.

Preserved history

All sprint-by-sprint build detail (Sprint 0 through Sprint 27) remains fully intact in CHANGELOG_AI.md — nothing was deleted, only de-duplicated out of the three current-state files that used to repeat it.

Validation

• Repo-wide grep for stale claims (old test counts 975/971/968/964 presented as current, "Option B", "PR Etsy compliance hardening and production-readiness fixes #56/Automate daily retention cleanup in production #58 open", "appeal submitted", "Private Beta disabled", the broken --component retention-cleanup doctl syntax) — zero hits outside dated historical narrative that already self-annotates as superseded.
• No secrets, no EV[...] DigitalOcean placeholders, no application code touched — documentation-only diff.
• No broken references — the one real code-comment dependency (ETSY_SUPPORT_QUESTIONS.md) was identified and the file kept rather than deleted.