v2 UI: pull all 27 UX Pilot designs into the repo and map FR coverage

[pseudoseed]

The v2 requirements were written against 2 designs. The design of record holds 27.

The gap

Design of record: UX Pilot page SXl8jE8uNyYLwBsG6vsL
https://uxpilot.ai/a/ui-design?page=SXl8jE8uNyYLwBsG6vsL

27 designs across 8 groups:

Group	Designs	In repo
Porch Site Mobile Redesign	9	no
Find Node Screen Flow	5	no
Porch Gate Interaction Design	5	no
Add Machine To Porch	5	no
Group with Porch - Gate Queue Sheet	1	no
Group with Porch - Split Terminals	1	no
Group with Porch - Terminal Soft Keyboard	1	no
Design a bespoke control surfa (parent)	0	—

codev/research/v2-mockups/ carries 2 of them as HTML (01-site.html, 02-gate.html) plus PNGs. tokens.css says so in its own header: "extracted from the approved UX Pilot mockups."

FR-1 through FR-48 were written against those 2 screens. Five groups currently have no requirements at all, and the consequences have already shown up: the dark palette (#63) was scoped to 2 screens, and the iPad tiling spike (#62) was scoped to a tiling surface that may not be how the mobile redesign works.

The work

1. Pull all 27 designs into the repo. Use the uxpilot MCP tools: get_page_context for the manifest, then get_design with includeHtml per design.

   Land at codev/research/v2-mockups/uxpilot/<group-slug>/<design-id>.html, with the preview PNG beside each.

   Fetch and write one design at a time. These responses are large and holding them all will exhaust context.

2. Write codev/research/v2-mockups/uxpilot/MANIFEST.md mapping each design to its group, title, and the FR numbers it bears on.

3. Report the coverage gap. Which of the 8 groups have no FR in codev/research/codev-v2-ui-frd.md, and which existing FRs describe a surface no design covers. That list is the deliverable that matters most — the HTML is just the evidence under it.

Constraints

• Do not restyle, reformat, or improve anything pulled. It is source material and it is the design of record. Extraction is what caused this gap; do not repeat it.
• Do not apply the dark palette to the pulled designs. Getting them in is this issue; theming them is not.
• Do not modify 01-site.html, 02-gate.html, tokens.css or tokens-dark.css. They stay as they are.
• Additive only. No production code.

Reference

• FRD rev. 7, Part 6b — codev/research/codev-v2-ui-frd.md
• Dark palette, covering 2 designs: PR [Experiment 63] v2 dark palette (designed, not derived) #68