Same prompt. Five interpretations.

Build a complete marketing website for "Meridian", a fictional independent coffee roastery. This brief is fixed; your design interpretation of it is the test.

The site must include, at minimum:
1. A hero section introducing the brand.
2. A section presenting three coffee origins (invent the details: name, region, tasting notes, price).
3. A short "our philosophy" or about section.
4. A footer with fictional contact details and a newsletter signup (front-end only, no real backend needed). The footer must also display, in small text, the basename of the current working directory (the directory's name only, not the full path) as a build identifier — hardcode it into the footer at build time.

Rules:
1. You may use any languages, frameworks, libraries, or build tools you like.
2. All content must be self-contained: no external network requests at view time (no CDN links, no remote fonts, no hotlinked images). Inline SVG, locally bundled assets, and generated graphics are all fine.
3. The final deliverable must be a static site: a directory named `dist/` in the current working directory containing an index.html that renders fully when served locally. If you use a framework, run its build step yourself so dist/ is the finished output.
4. Include a README.md in the current working directory stating: your chosen tech stack, your aesthetic direction (3–5 lines), and the exact command to serve dist/ locally (e.g. a one-liner static server).
5. The site must be responsive and look intentional at 375px and 1280px widths.
6. Commit to a distinct aesthetic direction and execute it consistently. Generic template-like output will be judged as a failure of taste.

STRICT DIRECTIVE — SANDBOX BOUNDARY:
Work ONLY inside the current working directory. Do NOT read, list, access, or modify any parent directory or any sibling directory, under any circumstances. You may create and use temporary subdirectories inside the current working directory (including node_modules, build caches, etc.). Reading the NAME of the current working directory itself (e.g. via pwd/basename) is explicitly permitted and required for the footer identifier. Do not inspect the environment beyond what is required for this task.