/goal Assemble the improved modules into one polished, public, outer-commentable left-to-right journey canvas that Matt can review quickly and then present to Rita without explaining missing links.

# Contract 05-canvas, revision 1: One Rita-ready canvas and final integration

## Goal
Assemble the improved modules into one polished, public, outer-commentable left-to-right journey canvas that Matt can review quickly and then present to Rita without explaining missing links.

## 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: **root canvas files · review/** · sole publisher**. You also own `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/handoffs/05-canvas/`, `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/evidence/05-canvas/`, and `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/reports/05-canvas.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 existing CC Klíma-derived canvas, immutable baseline, shared routes and the four module manifests. Use `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/handoffs/01-ads`, `02-landings`, `03-flow`, `04-course` after each owner declares ready. Do not inspect their task transcripts, supervise progress or overwrite active ownership.

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
Deliver the final canvas at the intended stable URL, every actual interface in journey order, a compact recommended path and accessible A/B alternatives, meaningful customer-facing flow labels, asset-level reviewer rationale and an unsent Hungarian Rita email draft linking the real sections. Reuse existing persona/analysis and tighten it. No new evidence-dashboard project.

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
### CAN1. The canvas is the entire customer journey at a glance

Criteria:
- Show two understandable entry branches: free-video ad→free landing→upload/receipt/feedback→useful email→challenge, and direct ad→challenge. They converge at checkout→confirmation/access→overview→all14 days→final clip→consultation. Show relevant service/marketing email interfaces beside the transition they support, not one disconnected email bucket.
- Place all14 Rita screens on a second row directly below their matching participant days, with stable day IDs and clear submission/feedback links. All20 ads,4 landings,6 CTA alternatives,58 email topics/116 versions,7 landing visuals and56 daily alternatives are reachable without cluttering the recommended route.
- Preserve the actual CC Klíma pan, anchored zoom, fit, stage jump and expanded-view behaviour. A full mobile screen is readable in the inspector and closing it restores the previous canvas position. The index lists all deliverable interfaces, not private evidence files.

### CAN2. The review helps Rita evaluate a coherent proposal

Criteria:
- The opening orientation says what the participant gets, the two entry paths, the daily-feedback pilot and which commercial/service facts remain proposals. Use a clean presentation mode with actual screens and a review mode for comparisons/analysis. Do not flood customer screens with status tables, developer controls or backend explanations.
- For every asset/stage, use existing analysis as a short outside-the-screen card: before-view mindset, attention, interpretation order, likely objection, intended next action and reason to try it. Identify weak existing copy and explain the concrete correction. Apply the value-equation reasoning naturally, without invented numeric scores. Keep A/B alternatives side by side at equal scale and state a hypothesis, not a winner.
- Only the outer canvas owns the comment layer, using stable asset targets. Users can comment on the ad, landing/section, day or Rita screen from the outer surface and return to the same asset. Embedded pages do not each inject a second toolbar. Publish through the canonical shared host skill and preserve unrelated host routes.

### CAN3. The assembled prototype is ready to present

Criteria:
- Run both complete entry paths from ad to consultation, including checkout cancel/retry, optional consent, previous-day return and one complete participant/Rita loop. Verify all14 day-pair links/source mappings and every visible CTA, plus refresh and back navigation. No old-host detours, broken media or unintended actual transactions/sends remain.
- Coordinate independent Luna section QA and fresh deployed screenshots for all unique pages, mobile360/390/430 for customer UI and desktop only for the outer canvas. Resolve real flow/copy/visual defects with their exclusive owner. Keep one concise result table; no claim of verified based merely on generated captures or an existing report.
- Publish one public assembled canvas at the intended URL and verify anonymous readback, index/reachability, functional review controls and comment persistence on a disposable test document. Provide a short unsent Rita email: what each real URL/section shows, what feedback is wanted, and what still awaits agreement. Explicitly label this frontend proposal, not a live campaign/system or client approval.

## Verification and evidence
Capture the entire two-branch canvas at overview scale, a readable expanded landing, an A/B comparison, all14 aligned participant/Rita pairs, a full free-to-paid path and a paid-to-consultation path. The independent reviewer must see how every screen connects and whether a real visitor would understand the next action. The postdeployment captures must be from the actual final URL/build; do not relabel local evidence as live.

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 publish while a sibling is mutating the release files, silently rewrite their module, declare finished with missing interfaces, or turn final review into another open-ended research/evidence system.

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/05-canvas/manifest.json` using the small shared schema and your concise report at `/Users/agency/Documents/Agty/KomplexLogopédia/outputs/rita-ui-parallel-20261002/reports/05-canvas.md`, based on `/Users/agency/.agents/skills/launch-agent/report-template.md`. Your ready manifest and DONE require CAN1–CAN3 to pass against the released build, including actual independent postdeployment review and outer-comment persistence readback. A locally working assembly is not completion for the sole publisher. Reconcile final lesson/email hashes and same-participant feedback destinations before release.

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.

## Sole-publisher release boundary
Build the canvas framework in parallel while modules retain baseline routes. Release only from declared-ready, stable module handoffs. Freeze the release snapshot and record included manifest hashes before deploying. Agent05 owns the publication lease and exact rollback snapshot. Use `/Users/agency/.agents/skills/comment-html-review-host/SKILL.md`, stable document `komplex-rita-ui-canvas-20261002`, slug `komplex-rita-ui-canvas-2026-10-02-v1`. Check the current live manifest and preserve every unrelated route. The previous task's verified-host snapshot is a recovery reference, not automatically current. Do not force a partial mirror deployment.

The old executor may still be active on its separate outputs and shared host. Do not edit or terminate it. Shared-host publication must respect the existing lock `/tmp/clientsflow-review-host.lock` and recheck the live manifest under that lock. Runtime permissions still apply. Publish once a complete preview is usable, then fix and recheck actual defects without repeatedly building a new evidence product. Deliver the Rita email draft as an unsent review artifact, not an external message.