Build a Website Clone as a Dineway Site

Reverse-engineer the explicitly supplied source URLs and rebuild them as a pixel-faithful Dineway Site.

Treat this as a foreman workflow, not a two-phase inspect-then-build handoff. Inspect each section, write its specification to disk, and dispatch a focused builder as soon as the shared foundation is ready. Keep extraction meticulous and every implementation decision auditable.

Scope Defaults

Unless the user overrides them, use these defaults:

• Fidelity: Pixel-faithful colors, spacing, typography, motion, interactions, and responsive behavior
• Discovery: Each explicit URL plus one same-origin link layer discovered directly from each explicit page
• In scope: Visual layout, component structure, interactions, responsive design, source content, source assets, Astro SSR routes, and Dineway-managed editable content
• Out of scope: Reproducing the source backend, source authentication, payments, real-time services, inaccessible private content, SEO strategy rewrites, and accessibility audits
• Dineway boundary: Astro owns presentation and interaction; Dineway owns editable identity, navigation, editorial copy, editorial media, and repeatable content
• Customization: None; emulate the source unless the user requests changes

Dineway's required SEO and discovery plumbing remains in scope even though an SEO strategy rewrite is not.