# 08F4Q QA Recheck - aieditorrsp.net all-page Stitch fidelity

- Task: t_94f97314
- Tenant: site-aieditorrsp-20260528
- Domain: https://aieditorrsp.net
- Repo: /root/projects/aieditorrsp
- Commit checked: bc24d4838a2d7274070bf3bbec177f5091a2e7c1
- Official Stitch design package: /root/.hermes/reports/site-aieditorrsp-20260528/design
- Verdict: QA_NO_GO

## Executive result

Do not release launch ops.

Production routes/build/SEO smoke are healthy, and the home page is materially close to the Stitch visual system. However the strict all-page Stitch fidelity rework fails on core non-home pages: `/ai-photo-prompt-editor`, `/prompt-library`, `/pricing`, and `/ai-photo-editing-prompts` render like partially raw Stitch HTML with missing/insufficient CSS normalization. Typography, icons, cards, sidebars, buttons, and image panels overlap or lose the intended material structure. This violates the owner NO-GO standard: not enough to look “kind of like Stitch”; all core pages must preserve original Stitch material/layout.

## Checks run

- `git rev-parse HEAD`: `bc24d4838a2d7274070bf3bbec177f5091a2e7c1`
- `git status --short`: clean
- `npm run verify`: PASS (`ok:true`, routes=11, hrefPlaceholders=0, forbiddenCopy=0)
- `npm run seo:audit`: PASS, no reported failures
- `npm run build`: PASS, 26 static pages generated, OpenNext bundle complete
- Production HTTP smoke with browser UA: PASS
  - `/`, `/ai-photo-prompt-editor`, `/ai-photo-editing-prompts`, `/chatgpt-photo-editing-prompts`, `/prompt-library`, `/pricing`, `/privacy`, `/terms`, `/cookie-policy`, `/refund`, `/contact`, `/robots.txt`, `/sitemap.xml`: all 200
- Browser visual QA: desktop homepage, desktop editor, desktop prompt library, desktop pricing, 390px editor/mobile pass
- Upload/editor state probe: injected 1x1 PNG into live file input; file state changed to `File ready`; clicking generate returned `LOGIN_REQUIRED / Generation blocked` because anonymous previews are exhausted or login is required. This is functional state handling, not the main blocker.

## Route fidelity matrix

| Route | Status | Evidence |
|---|---:|---|
| `/` | CONDITIONAL PASS | Dark graphite industrial studio, editor above fold, amber CTA, mint accents and performance comparison visuals present. But official home Stitch screenshot includes a Pricing & Credits preview and native FAQ module before footer; production jumps from safety into SEO expansion/FAQ, so home is not exact full-page parity. |
| `/ai-photo-prompt-editor` | FAIL P0 | Official Stitch page is a compact dashboard: dark header/sidebar, contained settings grid, right generated prompt card, small reference preview, clean support cards. Production desktop renders a huge background image under transparent controls, serif typography, overlapped panels, unreadable generated prompt, giant material icon names, and a live bridge appended far below. 390px mobile also shows the raw Stitch top section as visually broken before the live editor. |
| `/prompt-library` | FAIL P0 | Production desktop shows huge `RSP AI EDITOR` text, raw material icon names (`face`, `inventory_2`, `content_copy`), empty/dark card bodies, oversized columns, and sidebar/button misalignment. This is not usable as the Stitch library grid. |
| `/pricing` | FAIL P0 | Pricing cards are broken: Pro card consumes excessive height, buttons flatten into edges, quota floats away, user profiles overlap, FAQ/material icons show as text, footer links run together. Also production HTML still contains 2 external Google Stitch image refs. |
| `/ai-photo-editing-prompts` | FAIL P0/P1 | At 390px the page is mostly readable but not strict Stitch fidelity: left technical sidebar occupies the top, hero/title is clipped, cards are stacked with raw/uneven typography, material icon names appear as text. Needs desktop recheck after CSS fix; current mobile evidence already fails strict fidelity. |
| `/chatgpt-photo-editing-prompts` | NOT FULLY CLEARED | HTTP/assets smoke pass, but given the shared raw-design rendering issue across other imported Stitch pages, this page must be rechecked visually after CSS remediation before QA_GO. |
| `/privacy`, `/terms`, `/cookie-policy`, `/refund`, `/contact` | NOT BLOCKING FOR THIS FAIL | Routes are 200 and appear to reuse design-system/rawDesign pipeline, but core page P0 failures block before legal/contact can clear launch. |

## Asset localization

Production asset count check:

| Route | `/stitch-assets/` refs | external Stitch Google refs |
|---|---:|---:|
| `/` | 10 | 0 |
| `/ai-photo-prompt-editor` | 10 | 0 |
| `/ai-photo-editing-prompts` | 10 | 0 |
| `/chatgpt-photo-editing-prompts` | 6 | 0 |
| `/prompt-library` | 2 | 0 |
| `/pricing` | 0 | 2 |

Pricing still includes external `lh3.googleusercontent.com/aida-public/...` references. Under the task requirement, Stitch HTML image URLs should be downloaded/localized or explicitly justified if replaced. No justification was found in the production page evidence, so this is a P1/P0-adjacent fidelity/asset hygiene failure on `/pricing`.

## Upload/editor state treatment

Observed on `/ai-photo-prompt-editor`:

- Live upload/editor bridge exists below the raw Stitch prompt-builder section.
- File input accepts a PNG via browser-injected DataTransfer and state changes from `Ready to edit` to `File ready`.
- Generate click returns `LOGIN_REQUIRED / Generation blocked` with login/upgrade links, which is a coherent quota/auth state.
- Main issue: the live editor is separated far below a visually broken raw Stitch top section. It does not compensate for the first-screen fidelity failure.

## Performance compare module

Home production includes `Performance Comparisons` with two localized visual cards and dark contact-sheet treatment, materially aligned with official Stitch direction. This module is not the blocker.

## Mobile 390px

- `/ai-photo-prompt-editor` measured no horizontal document overflow (`scrollWidth <= viewport width`).
- Usability still fails strict fidelity because the first raw Stitch prompt-builder section is visually broken: clipped title, overlapped controls, bottom nav crossing the generated prompt area, raw material icon text, and low-contrast/overlaid background image.
- The later live editor bridge is readable on mobile, but appears only after a long broken section.

## Blockers

| ID | Severity | Description | Owner |
|---|---|---|---|
| 08F4Q-P0-001 | P0 | Raw/imported Stitch pages are not receiving the complete Stitch/Tailwind material styling. `/ai-photo-prompt-editor`, `/prompt-library`, `/pricing`, and likely other rawDesign pages render with broken layout, icon text, overlap, and unusable cards. | Frontend |
| 08F4Q-P0-002 | P0 | `/ai-photo-prompt-editor` does not match official Stitch prompt editor layout/material. First screen is visually broken on desktop and mobile; live editor is appended below rather than preserving first-screen material quality. | Frontend |
| 08F4Q-P0-003 | P0 | `/prompt-library` and `/pricing` are visibly non-shippable under strict Stitch fidelity. Cards/sidebar/pricing/user profile sections are broken. | Frontend |
| 08F4Q-P1-001 | P1 | `/pricing` still references external Stitch Google image URLs instead of localized assets or a documented replacement rationale. | Frontend |
| 08F4Q-P1-002 | P1 | Home page is close but not exact full-page Stitch parity: pricing preview/native FAQ from official home screenshot are absent/replaced by SEO expansion flow. | Frontend/Product |

## Recommended fix path

1. Do not patch screenshots or SEO copy first. Fix the raw Stitch HTML styling pipeline.
2. Ensure all imported Stitch HTML classnames/material icon fonts/Tailwind arbitrary classes are either compiled, mapped, or converted into production CSS. The failure pattern looks like raw Tailwind/Stitch classes surviving into HTML without equivalent production styles.
3. Recheck `/ai-photo-prompt-editor`, `/prompt-library`, `/pricing`, `/ai-photo-editing-prompts`, `/chatgpt-photo-editing-prompts` visually at desktop and 390px.
4. Localize or explicitly replace the remaining `/pricing` external Stitch asset URLs.
5. Preserve SEO expansion below the design page, but not at the cost of breaking or replacing the Stitch material structure.

## Final verdict

QA_NO_GO. Production is accessible and builds successfully, but strict all-page Stitch fidelity is not met. Do not release launch ops until the P0 visual/fidelity blockers are fixed and re-QA passes.