omk-sitelisted

# Site implementation and verification ## Bound the change Inspect the existing repository instructions, package manifest, lockfile, routes, design tokens and target page before editing. Preserve the current framework, version pins and component conventions. Do not replace the application just to match a familiar stack. Define the requested pages, interactions, responsive breakpoints and acceptance checks. Treat a reference site as design evidence, not permission to copy private assets or credentials. Use the existing local build and preview commands. Bind previews to loopback unless a public preview was approved. Do not install dependencies, launch paid cloud browsers or publish a service merely because a skill recommends them. External APIs, images and fonts need an approved source and reproducible configuration; never invent keys or environment values. ## Implement a complete vertical slice Make the smallest complete change covering data input, validation, loading, success, empty and error states. Reuse shared tokens and accessible components. Keep controls keyboard reachable, labels associated with inputs, focus visible, and layout usable at narrow widths. Validate untrusted input on the authoritative server boundary as well as in the interface where relevant. Write targeted tests for the changed behavior. Run the actual repository lint/typecheck/build commands within the approved scope. Record command, exit status and artifact path. A successful compiler does not p