ui-reverse-engineering

# UI Reverse Engineering Reverse-engineer a live website into a **React + Tailwind** component. ## Hard Done Criteria - **Build pass is not done.** It proves only that the app starts. - **Spot check is not done.** Manual screenshots cannot replace measurements. - **Pipeline verify PASS** is required for clean completion. - **Missing artifact is failure.** Report it as `INCOMPLETE`; never substitute notes, placeholder JSON, HTTP 200, page titles, or source strings. ## Desktop-first scope and iteration Implement the source responsive structure from the start, regardless of verification scope. Preserve local source CSS media/container queries, fluid sizing expressions, and responsive layout/visibility variants; retain original fixed values where authored. A captured computed pixel value is a measurement, not an authored sizing rule. Desktop-first limits detailed verification, not the CSS or component architecture. See `component-generation.md` for the responsive implementation contract. Unless the user already requests all responsive layouts, start verification with desktop scope. Generate the verification plan with `--scope=desktop` (default). Infer the desktop band from captured CSS breakpoints and confirm it with live reference/implementation boundary probes. Detailed verification uses the representative desktop viewport; cheap probes cover narrower and wider widths within that layout band. Use `--scope=all` when the user explicitly requests all responsive layouts. Bu...