frontend-replica-acceptance

# Frontend Replica acceptance ## Default fidelity contract When the current operator does not state a numeric similarity or fidelity requirement, require at least 80% (0.80) overall rendered visual fidelity across the accepted desktop replica surface. A numeric requirement explicitly stated by the current operator replaces this default for that Task; preserve the explicit requirement exactly. Evaluate the requirement from fresh source-to-target rendered evidence for the accepted desktop surface. Cover information architecture, region and module order, layout and geometry, spacing and density, typography, colors and materials, assets and icons, content, component and interaction states, layering, and required desktop behavior. Bind every finding to the exact source region, target surface, and current screenshot or Browser evidence. The percentage is an acceptance target, not permission to invent a score. Report a numeric comparison only when current comparison evidence provides a defensible measurement. Otherwise report the concrete dimension evidence and leave the numeric requirement unresolved as a verification blocker. An aggregate result cannot compensate for a missing visible source region, incorrect information architecture, reordered module, broken required interaction, placeholder or fabricated content, blank filler geometry, unreadable evidence, or an unavailable current rendered comparison. Any such defect remains a blocker until repaired and reverified. Do not turn this contract into a Host gate, state machine, automatic retry rule, or global Structural Similarity Index Measure threshold. The Orchestrator makes the visible acceptance decision from the complete current Requirements, implementation, Visual Quality Assurance, integrity, and Browser evidence.