# AI Editor RSP — Owner Repair Brief After QA_GO Rejection

Production: https://aieditorrsp.net
Repo: `/root/projects/aieditorrsp`
Rejected owner gate: `t_b05228f6`
Prior final Re-QA: `t_be0625aa`
Status: NOT launch-ready. Owner explicitly rejected current quality.

## Owner feedback / launch blockers

1. Login/payment are not actually supported. Preview-disabled mode is not acceptable as final launch quality for this iteration.
2. `/editor` has a heavy visual overlay; content is hard to read. The tool area is clipped/truncated. The left sidebar makes the page worse; remove it if needed.
3. `/library` has content appearing below the footer. Footer must be the last page section.
4. `/templates` has the same split/overlay/sidebar problem as `/editor`; header is inconsistent with the main site; pages feel visually fragmented.
5. Prior Final QA P1/P2 must also be fixed before launch:
   - non-home SEO duplicate H1
   - short meta descriptions
   - edge viewports with Generate below fold
   - GA4/Clarity runtime not verified
   - Lighthouse/LCP performance issue if still present

## Visual acceptance criteria

- Public/product pages use one unified main-site header/nav/CTA system.
- No app/dashboard sidebar on public `/editor`, `/library`, `/templates` unless it is demonstrably useful and does not steal space; owner specifically says better to remove sidebars than keep broken ones.
- No full-screen/large background overlay that reduces readability. Background imagery may remain only as subtle decorative art with sufficient contrast.
- Tool/editor panels are never clipped horizontally at 1366x768, 1440x900, 1280x800, 390x844, 430x932.
- Footer is the terminal section. No SEO/body content appears after footer.
- `/editor`, `/library`, `/templates`, pricing, legal pages feel like one product, not separate stitched prototypes.

## Auth/payment acceptance criteria

- Login entry works or is explicitly blocked with concrete external action. No fake success.
- Payment/checkout either works end-to-end with Stripe test/live evidence and correct Tax/checkout settings, or paid UI is clearly disabled and not claimed as supported. Owner feedback requests support, so workers should attempt real implementation/config verification first.
- `/api/credits`, pricing, CTAs, legal/refund copy must match actual launch mode.
- Secrets must never be written to reports/Kanban/chat; use `[REDACTED]`.

## Required pipeline

Product/Design repair contract → Backend auth/payment repair → Frontend visual + route repair → SEO P1/P2 + analytics/perf repair → Compliance recheck → Product acceptance → Final QA → Owner Review Gate.

Final QA must treat the old QA_GO as stale. Launch remains blocked until fresh QA_GO and owner confirmation.