chore: add MVP planning backlog

backlog/tasks/task-18 - Add-MVP-quality-gates-and-operational-polish.md

@@ -0,0 +1,45 @@
+---
+id: TASK-18
+title: Add MVP quality gates and operational polish
+status: To Do
+assignee: []
+created_date: '2026-06-03 19:15'
+updated_date: '2026-06-03 19:15'
+labels:
+  - mvp
+  - quality
+  - ops
+dependencies:
+  - TASK-16
+  - TASK-17
+  - TASK-19
+references:
+  - PRD.md
+priority: medium
+ordinal: 18000
+---
+
+## Description
+
+<!-- SECTION:DESCRIPTION:BEGIN -->
+Add the final MVP quality layer: German UI consistency, i18n preparation, accessibility checks, run/error observability, secret hygiene, basic testing coverage, and deployment-readiness for Coolify. This task makes the MVP safe enough to use for real internal acquisition work.
+<!-- SECTION:DESCRIPTION:END -->
+
+## Acceptance Criteria
+<!-- AC:BEGIN -->
+- [ ] #1 Core UI text is German and organized so future i18n is feasible
+- [ ] #2 No secrets are stored in source code, dashboard-editable records, logs, prompts, or raw LLM history
+- [ ] #3 Dashboard surfaces integration errors for Google, PageSpeed, OpenRouter, Playwright, SMTP, Convex jobs, and Rybbit
+- [ ] #4 Critical user flows have basic tests or repeatable verification notes: login, campaign run, audit generation, approval, send, follow-up, analytics
+- [ ] #5 Coolify deployment notes cover required environment variables, Playwright browser dependencies, exposed port, and domain assumptions
+<!-- AC:END -->
+
+## Implementation Plan
+
+<!-- SECTION:PLAN:BEGIN -->
+1. Audit UI copy for German consistency and avoid hard-to-localize scattered strings where practical.
+2. Review secret handling and redact logs/prompts where needed.
+3. Add integration status/error surfaces in dashboard run details.
+4. Add smoke tests or documented verification flows for critical MVP paths.
+5. Document Coolify deployment requirements, env vars, Playwright dependencies, and operational caveats.
+<!-- SECTION:PLAN:END -->