polished-app-gate

Run a UI polish audit by applying a gate:polish label to your PR and providing screenshot plus frozen rendered DOM context. The audit checks kid-visible surfaces and emits a ship, ship-with-backlog, or do-not-ship verdict.

A polished UI avoids prototype-like micro-states, copy issues, and visual cadence problems. Aesthetic reviews enforce axis-based checks across P1–P5 levels, with optional P6 for command surfaces, to distinguish production-ready interfaces from unfinished prototypes.

Enforce phase-0 bake-off readiness by running opt-in polish verdicts on targeted kid-visible routes. The gate requires device-profile resolution and screenshot evidence to validate that the UI meets aesthetic standards before shipping.

Yes, aesthetic reviews require a configured single gate model, screenshot evidence, and frozen rendered DOM context for the targeted routes. You must freeze device screenshots and DOM context for the updated surfaces before running the audit.

Yes, the UI audit applies to both kid-visible lanes and office-facing command surfaces like TheSpine. It evaluates prototype-like micro-states and copy/cadence issues across these scoped surfaces to determine if they feel polished.

Polish verdicts cannot run without screenshot and frozen rendered DOM context evidence. The gate enforces this requirement to ensure accurate axis-based aesthetic checks and device-profile resolution before emitting a valid JSON verdict.