Production launch
NO-GO
F074 · beta feedback
Defines beta triage, UX polish, customer edge-case intake and accepted limitation gates.
Production launch
NO-GO
Scope
F074 report
Blocked phases
0
Warning phases
1
F074
Feedback workflow is documented; it starts only after a controlled beta customer install is browser-verified.
Bug triage workflow
Workflow exists as readiness; real beta intake source must be linked.
UX polish backlog
Backlog is open until browser/mobile QA is complete.
Accepted limitations
Known limitations must be explicitly accepted before production launch.
Frontend green gate
Run pnpm install/typecheck/lint/build/test/dev/test:e2e in local or staging.
Backend green gate
Run npm ci, prisma generate/validate, typecheck, lint, test, start/dev and migration check.
Browser/embed QA
Plain HTML, Next.js, WordPress-like, mobile, multi-widget and no-token checks require real browser evidence.
Security/observability evidence
Token redaction, CSP, iframe sandbox, postMessage allowlist and trace id propagation must be proven.
Release/docs evidence
Customer install guides, troubleshooting, known limitations and rollback docs need final review.
Run F066-F075 as a production-track readiness/handoff, then collect real local/staging frontend, backend and browser evidence before RC1 or production launch.