# Campaign Release Studio — current verification

Verified October 1, 2026. This report covers the reversible Studio upgrade and the final white/blue correction. The original `outputs/campaign-release-desk` remains separate. `BASELINE-QA.md` and the baseline pilot proposal describe the earlier product, not the current Studio.

## Automated results

- **138 passed, 0 failed**, across four Vitest test files. The original 52-test file is unchanged: SHA256 `c030f6961febdc17a895abb7fa98201ac90468028635feb11b0f4d0b01a3498f`.
- Typecheck and production build pass. Strict premium UI audit: **0 errors, 0 warnings**. DESIGN.md lint: **0 errors, 0 warnings**, one informational token summary.
- Original coverage remains: revision-specific approvals, invalid/stale records, source/copy/disclosure consistency, location routing, exact UTM identity, date/timezone/DST boundaries, exclusive expiry, persistence contracts, strict import/export, escaping and release gates.
- New coverage checks inquiry intent, actual local events and deduplication, theme/asset/option/department compatibility, bounded import/history, approval invalidation, self-contained creative bundles, and the loopback-only ZIP adapter, including unsafe origins, filenames, payloads and changed bytes.

## Rendered typography and layout

Actual CSS widths were measured at **320, 390, 768, 1280 and 1920 px**. The browser's existing 121% zoom was preserved; temporary emulation dimensions were compensated and the resulting CSS width was read before checks. Browser zoom is not a CSS font-size change.

| Coverage               | Actual observations                                                                                                                                          |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Primary routes         | Both customer themes, Studio brief, Measurement, Strategy/evidence and the preserved `/desk` module at all five widths: 30 route observations.               |
| Workflow and proofs    | Both themes, all four Studio tabs and all four creative formats at all five widths: 80 observations.                                                         |
| Nested dialogs         | Source editor, source review, variant editor, batch review, test clock, import, reset, direction detail and photo rights at 320 and 1280px: 18 observations. |
| Corrected narrow cases | Motion proof on both themes at all five widths and the desk menu at 320px: 11 targeted retests.                                                              |
| Downloaded proofs      | Final website/email/social/motion HTML from both actual ZIPs at all five widths: 40 observations, plus overlay containment checks for social/motion.         |

**No remaining text below 13px was found.** Main narrative/body text is 15px or larger; primary navigation, workflow/channel menus and storyboard selectors are 16px or larger. Secondary badges, revision numbers, helpers, supplied disclosure, independent-demo notices and source credits use 13px. Larger headings retain their hierarchy. Native inputs/selects are 16px on narrow screens.

The initial computed-style audit retained two legacy metadata paragraphs and a 13px navigation count badge; these are legitimate secondary text, not body/menu labels. Initial artifacts also retain the identified 320px desk overflow and the motion-frame containment issue. Targeted final retests supersede those findings.

No document-level horizontal overflow remains in the inspected cases. Tables with long event/tracking context intentionally scroll inside their containers. Mobile menus and workflow tabs reflow into two columns; captions wrap; social proofs become portrait compositions; the motion frame no longer gains an unwanted minimum width from its aspect ratio. Social/motion exported credits now occupy separate white strips, and every checked overlay child remains within its intended bounds.

Raw evidence: `typography-browser-audit.json`, `export-browser-audit.json`, the post-build `final-rendered-verification.json`, final desktop/mobile screenshots in `docs/screenshots`, and the actual inspected packages in `exports/reviewed`. The final pass remeasured both customer themes at all five widths, the source dialog at 320px, keyboard focus and close/opener restoration, and all eight persisted exported previews at 320/1280px. The fresh verification tab has no console warnings or errors. These are observed results, not conclusions inferred from CSS tokens.

## Working browser flows

| Flow                            | Verified outcome                                                                                                                                                                                                                                                                        |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Mobile inquiry after correction | Empty submit shows useful inline helper errors and focuses Fictional name. A fictional `.test` marine inquiry saves cruising direction, use case, timing, Lakeside, marine department and website channel.                                                                              |
| Handoff after correction        | Direct receipt action opens Handoff. Acknowledge then Resolve succeeds; reload retains the context and resolved status. Nothing is transmitted to the business; resolution is not a sale.                                                                                               |
| Image recovery after correction | All three Wrangler WebP sizes were temporarily made unavailable in the local built output. The useful fallback and Retry appeared while the inquiry form stayed enabled. Files were restored; Retry loaded the image successfully. The deliberate 404 is not an unresolved asset error. |
| Reduced motion after correction | Playback is disabled, animation/transform compute to none, and keyboard Enter on Frame 3 selects the static action frame.                                                                                                                                                               |
| Source/change review            | Earlier in this upgrade, changing the source r1→r2 invalidated source and nine channel approvals. Named source review, explicit generation and inspection of all nine variant snapshots restored all nine inquiry checks. No automatic approval occurred.                               |
| Concurrent editing              | Earlier in this upgrade, a source changed in another tab synchronized; saving the frozen first-tab draft was rejected and retained that draft. Same-revision import replacement risks are also covered by snapshot-fingerprint tests.                                                   |
| Expiry                          | Setting the clock to the exact campaign end blocks export and customer submission; resetting the demonstration restores the reviewed active fixtures. Original expiry/copy-drift cases remain available under `/desk`.                                                                  |
| Import/persistence              | Malformed JSON is rejected. An actually exported marine record file imported with its local intent/events/resolved state and survived reload. Final ZIP JSON is independently parsed and all nine release gates pass.                                                                   |
| Keyboard                        | Workflow arrow/Home behavior, modal focus/close behavior, option selection, first-error focus and manual storyboard frame selection were exercised. White focus rings are provided on blue/navy navigation, and a two-color ring protects photographic CTA contrast.                    |

No live lead, job application, advertisement, company contact or public deployment was performed.

## Actual downloads and package contents

Both final packages arrived in the Mac Downloads folder through the browser's supported file-download control. Filesystem existence, sizes, SHA256 hashes and ZIP contents were independently checked. Each ZIP has 25 safe unique entries: four self-contained creative HTML proofs, three embedded fonts, two selected images, eight license notices, source/channel records, release checklist/copy, local events, rights/readme and a generic theme adapter contract.

See `download-verification.json` for the exact final filenames, hashes, sizes and immutable loopback URLs. The prepared package UI states that a download is requested; it does not infer host receipt from a toast. Native embedded-browser download-event capture was unreliable during earlier testing, so the supported download control was used to verify actual receipt.

Final road records contain three observed local page-view events and no inquiries. Final marine records contain nine observed local events and one resolved fictional intent-complete inquiry. Counts are a test-session snapshot, not advertising analytics or commercial performance.

## Visual critique and remaining limits

The correction follows the actual Friendly Honda white/blue navigation and navy utility cues, while retaining original automotive/marine compositions, legally sourced type and illustrative photography. It does not claim that blue is an official group-wide specification. References and observed-versus-inferred decisions are documented in `BRAND-CORRECTION.md` and `STRATEGY.md`.

Remaining unverified checks: physical touchscreen interaction on an actual phone, manual screen-reader output, controlled slow-network performance and live CMS/CRM/advertising delivery. Direct touch-event automation is unsupported in this in-app browser; responsive mouse/keyboard interaction and touch-sized primary targets were inspected instead. Primary customer/footer actions and the dialog close target use a 44px CSS minimum, confirmed in rendered geometry with ordinary fractional-pixel rounding. No Lighthouse score or achieved business result is claimed.

All typography/layout defects discovered in this verification were corrected and retested. This is a local frontend theme demonstration, with fictional routing and unauthenticated named review; production integrations and public publication remain separate work requiring authorization.