/goal Refine the existing two free-video and two challenge landing variants into clear mobile pages that look like Komplex, fulfil the ads' promises and make the next step feel worthwhile and manageable.

# Contract 02-landings, revision 1: Four persuasive, coherent landing pages

## Goal
Refine the existing two free-video and two challenge landing variants into clear mobile pages that look like Komplex, fulfil the ads' promises and make the next step feel worthwhile and manageable.

## 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: **landing/** · assets/landing/****. You also own `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/handoffs/02-landings/`, `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/evidence/02-landings/`, and `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/reports/02-landings.md`. Other agents share the workspace; preserve their edits. The old executor and the immutable baseline are read-only.

## Authoritative inputs and fixed decisions
Use the four existing Gemini-generated pages, their generation receipts, seven existing visuals, real brand references, the saved 28-layout kit, the current layout map and Rita's Figma comment report. Inspect all four complete pages before deciding what needs editing. Invoke /impeccable for this UI refinement.

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 `free-a.html`, `free-b.html`, `challenge-a.html`, `challenge-b.html` plus `cta-alternatives.html`. Retain seven relevant custom visuals. Provide three complete main-CTA section alternatives per offer, six total, with copy and working destination. A/B variants differ in the persuasive emphasis and sequence, not the service facts.

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
### LP1. Each page answers the visitor's buying questions in order

Criteria:
- The first mobile viewport identifies who the offer is relevant to, the useful outcome and the next action in plain Hungarian. Free pages make free personal video feedback clear; paid pages make the 14-day guided-practice offer clear. A reader should not need Matt's explanation.
- Reading down the actual rendered page answers: what will I do, what do I receive, why trust this, what effort is involved, what happens next, and what remains outside the programme. Each section has a job; remove repetitive filler while preserving relevant template coverage.
- Use real identity and source-supported explanation as proof. Do not invent testimonials, results, recordings or urgency. Show daily feedback consistently with the current pilot proposal, while keeping unresolved commercial facts distinguishable from accepted commitments.

### LP2. The brand, variants and template work as one design

Criteria:
- All four pages use the live Komplex visual identity, real logo/portrait and consistent typography, spacing, controls and image treatment. At 360/390/430 no clipping, tiny explanatory copy, broken media or conflicting sticky controls prevent reading or clicking.
- Preserve purposeful coverage of the supplied 28 layouts across the family using the existing layout map, not 28 sections on every page. Log any changed interpretation. Preserve Gemini 3.1 Pro design provenance; small copy/CSS fixes do not require regenerating a whole page.
- The A/B and six CTA-section alternatives are full rendered sections that can be compared at the same scale. State one plausible test hypothesis for each pair. Do not produce multiple incompatible prices, feedback cadences or guarantees as variants.

### LP3. A clear CTA leads to a clear next screen

Criteria:
- Every principal free CTA opens `../flow/free-upload.html?variant=free-a` or `free-b`. Every principal paid CTA opens `../flow/checkout.html?variant=challenge-a` or `challenge-b`. No empty anchors, old deployment links or nonfunctional fake buttons remain.
- At the paid decision point the visitor understands the proposed once-only price, the daily work/support and the final consultation. Free signup does not unexpectedly become a payment request. Each form/checkout destination fulfils the exact CTA wording.
- An independent Luna reviewer reads all four actual pages and records the strongest remaining objection, any out-of-context sentence and each concrete usability defect. Fix material defects and inspect fresh captures, not just DOM counts.

## Verification and evidence
For all four pages, capture readable semantic sections, tall-section segments and overlapping 3–4-section runs at the three mobile widths. Luna must see the hero-to-offer narrative, rhythm, image relevance, objections, price context and CTA destination. Include each of the six complete CTA alternatives and meaningful expanded FAQ content. Never multiply every FAQ state by every unrelated CTA variant.

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 rewrite ads or checkout, redesign the brand, invent approved proof, or expand every page merely to satisfy a layout quota.

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/02-landings/manifest.json` using the small shared schema and your concise report at `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/reports/02-landings.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.