/goal Improve the existing twenty Facebook ad previews so a new visitor understands the situation, the offer and what happens after clicking, with coherent square images and natural Hungarian copy.

# Contract 01-ads, revision 1: Ads that earn the right click

## Goal
Improve the existing twenty Facebook ad previews so a new visitor understands the situation, the offer and what happens after clicking, with coherent square images and natural Hungarian copy.

## Scope and authority
Read `/Users/agency/Documents/Agty/KomplexLogopédia/plans/rita-ui-parallel-20261002/SHARED.md` first. Its product facts, ownership, routes, verification rules and completion boundaries are part of this goal. This is authorised frontend improvement when Matt launches this contract, not permission to launch the other contracts.

Work only under `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/site`. Your exclusive UI ownership: **ads/** · assets/ads/****. You also own `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/handoffs/01-ads/`, `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/evidence/01-ads/`, and `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/reports/01-ads.md`. Other agents share the workspace; preserve their edits. The old executor and the immutable baseline are read-only.

## Authoritative inputs and fixed decisions
Inspect all 20 existing `ads/ad-XX.html`, `ads/ads.json` and `assets/ads/ad-XX.png`. Reuse the prior copy critiques in `baseline/review/ad-copy/`. Read the two free and two challenge heroes before changing the ad promise.

The full existing site is already copied to the new work root. Do not rebuild from zero. The original snapshot and its hashes are at `/Users/agency/Documents/Agty/KomplexLogopédia/plans/rita-ui-parallel-20261002/baseline-manifest.json`. Follow the shared source hierarchy, brand, daily-feedback model and frontend-only boundary.

## Required deliverables
Keep 20 full Facebook-style previews and 20 real square images: 01–10 free-video, 11–20 challenge. Each preview includes image, on-image wording, matching primary text, headline, CTA and working offer destination. Supply a recommended pair per offer and concise reasoning for the remaining test angles, not a new persona workbook.

The acceptance owner is the canvas integrator for module handoff and Matt for the eventual client presentation. Final planned canvas URL: https://review.clientsflow.hu/komplex-rita-ui-canvas-2026-10-02-v1/ . This is a destination to create, not a claim that it is already published.

## End-state checklist
### AD1. Every ad makes sense without prior context

Criteria:
- A fresh Luna copy critic reads image text → primary text → headline → CTA for all 20, then states the offer and expected click outcome. Reject unexplained hooks, arbitrary USP lists, vague emotional language or a change of promise halfway through.
- A 390px Facebook preview shows a legible 1:1 image and readable Hungarian at actual display size. No Rita name appears on the creative or ad copy, and no fabricated engagement or endorsement is presented as real.
- For every changed caption, obtain a bounded Luna critique before regenerating its raster. Reuse a good existing image when the wording still matches; repair any stale baked-in text rather than hiding the mismatch in the caption.

### AD2. The ad leads into the same offer on the landing

Criteria:
- Click all 20 CTAs: free ads reach a free landing, paid ads reach a challenge landing. The first landing viewport repeats the same benefit, commitment and next action without requiring an explanation from Matt.
- Retain meaningful distinct angles across the set. Do not call colour swaps or synonyms new hypotheses. Recommend two per offer and explain what reader uncertainty each tests in one sentence.

### AD3. The assets are easy to compare and hand off

Criteria:
- Every ad has stable ID, destination and short keep/fix rationale in the module manifest. The canvas owner can embed previews and image URLs directly.
- Review the revised batch at 360/390/430 with actual image inspection, legibility and no clipped copy. Final deployed screenshots are coordinated by Agent05; do not publish your own competing batch.

## Verification and evidence
Show the full Facebook-style card at 390px, with the whole image and enough matching copy to judge the narrative. Luna must identify what caught attention, what is being offered, why the click is relevant, and any caption/image/landing mismatch. Show 360/430 views for readability and wrapping; no desktop ad QA.

Keep screenshots and findings in your assigned evidence directory. Link actual observations to the criterion IDs above. A screenshot placeholder is a pending check, never proof. Put useful UI first and evidence behind its concise handoff. Before declaring a route ready, use it in the rendered browser and read its entire unique copy. Use the required independent Luna process from SHARED.md, with bounded partitions and actual image inspection. Headless checks are allowed; do not open Matt's panels or leave task-owned tabs open.

## Constraints and rational changes
Do not set up Meta campaigns, research another twenty ideas from scratch, regenerate all images by default, or rewrite landing files.

If a verification criterion is objectively wrong, duplicated or tests the wrong outcome, record its original text, replacement, rationale and evidence in your report. Preserve the user's requested outcome and explicit constraints. An unfinished hard requirement cannot be converted into an optional one to claim DONE.

## Completion and blocked state
Write `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/handoffs/01-ads/manifest.json` using the small shared schema and your concise report at `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/reports/01-ads.md`, based on `/Users/agency/.agents/skills/launch-agent/report-template.md`. A manifest marked ready means this owned UI works and its local checks pass. The publisher performs the final deployed acceptance.

If no viable in-scope recovery remains, finish independent UI work and record the exact affected dependency, actual evidence and resume point. Do not manufacture blockers from optional polish. Return once in your final channel: DONE or STALLED, report path and the usable entry route. Native children use their normal completion channel back to parent `01a0c622-0f03-7480-9f24-003a441af4b3`. Separate visible tasks report through their own final response; do not send a second message to another task. No per-child wrap-up/audio.