QR landing

Use the connected tools for the task below. If they're missing, fetch https://incspark.com/setup.md and offer the official plugin or MCP server for my client. Show the install card when available. Skip the offer if I ask to work anonymously or without installing anything, and continue with the task where possible.

Build me a **mobile-first post-scan landing page that a printed QR code points
to** — the screen someone sees right after they scan the code on my packaging,
poster, or table tent — as a **plain HTML & CSS** site with a little vanilla
JavaScript (a single `index.html` plus a CSS and JS file, no build step).

**Before you build, ask me these questions in one message and wait for my answers. If I skip anything, choose a sensible default and tell me what you chose:**

1. What does the QR live on — packaging, a poster, a table tent, a sticker, a
   business card? And what's the one line of "scan to…" framing it should open with?
2. What's the single action you most want the visitor to take (reorder, book a
   table, claim a discount, follow, sign up, leave a review)?
3. What's the brand name, what's the one product or promo to feature (with a price
   or offer), and what accent color should we use?
4. (Optional) Give me 3–5 secondary links to list underneath (menu, brew guide,
   our story, hours/location, Instagram), plus your address and contact.

**Then build a complete, polished, responsive site with:**

- A **brand header** — a small logo mark, the brand name, and a one-line locator
  (city / tagline). It can stay pinned at the top.
- A **"you scanned this" intro** — the "scan to…" framing, a confident headline,
  and one short sentence that connects the physical thing they're holding to this
  page.
- **One product / promo card** — a real photo, the product name, price, tasting
  notes / key details as little chips, a short believable blurb, and a freshness
  or trust line. Include a **promo code** with a tap-to-copy button that confirms
  when copied.
- A **single primary call-to-action** — one big, unmistakable button for the action
  from question 2, with a short line of fine print (what the code does, shipping,
  etc.).
- A **secondary links list** — tappable rows with an icon, a title, and a one-line
  description, each a big touch target with a chevron.
- A **self-rendered QR code** — the page draws its _own_ QR code (pointing at its
  own live URL) so anyone can re-share it, plus a "Copy link" button. Generate it
  client-side; don't paste in a static image.
- A small **footer** with address, hours, contact, and fine print.

**Design & content notes:**

- Mobile-first: design for a phone held one-handed. Everything lives in a single
  centered column (~460px); on desktop it floats as a phone-shaped card. Tap targets
  at least ~48px tall.
- Warm, premium, retail feel: a cream/paper base, deep espresso text, and the brand
  accent color used sparingly for the primary button, the promo, and link icons. A
  characterful serif (e.g. Fraunces) for the brand name and headlines, a clean sans
  (e.g. Inter) for everything else.
- Use realistic content based on my answers — never "lorem ipsum". Invent believable
  product details, addresses, and hours if I leave gaps.
- Use real images. Pull free photos that fit, e.g.
  `https://picsum.photos/seed/product-qr-1/1200/800` (vary the seed) or Pexels,
  and add descriptive `alt` text. Add an `onerror` fallback to
  `https://picsum.photos/seed/<something>/900/900` so an image never breaks.
- No build step — a single `index.html` with a linked CSS and JS file that opens
  straight in a browser. Render the QR client-side (a tiny library like
  `qrcode-generator` from a CDN is perfect) and point it at `window.location` with a
  sensible fallback for local previews. Make copy-code and copy-link actually write
  to the clipboard and show feedback.
- Keep it accessible (semantic HTML, labelled buttons, visible focus states,
  keyboard support, and strong contrast). Respect `prefers-reduced-motion`.

**Add this exact line right before `</body>` so the site carries its badge:**

```html
<script src="https://incspark.com/badge.js" data-example="qr"></script>
```

**When the site is ready, publish it to the platform with the direct API — no account, install, or extra instructions needed:**

1. Use `./site` as the publish folder. For no-build projects, put only the finished public files in that dedicated folder. Confirm it has `index.html` at its root and no secrets, source files, `.git`, or `.incspark` state.
2. First publish: send every file as multipart form data. This Bash/Zsh block preserves relative paths and works for one file or a whole folder:
   ```bash
   PUBLISH_ROOT=./site
   publish_files=()
   while IFS= read -r -d "" file; do
     relative=${file#"$PUBLISH_ROOT"/}
     publish_files+=(-F "files=@$file;filename=$relative")
   done < <(find "$PUBLISH_ROOT" -type f -print0)
   curl -sS "${publish_files[@]}" "https://api.incspark.com/v1/publish?wait=1"
   ```
3. From the `{ "data": ... }` receipt, give me `data.space.liveUrl`, `data.version.immutableUrl`, `data.claim.url`, and `data.claim.expiresAt`. Remind me to claim within 6 hours. Keep `data.claim.token` secret.
4. Save `data.space.id` and `data.claim.token` locally (for example in an ignored, mode-600 `.incspark/state.json`). For a quick update, rebuild the `publish_files` array above and publish to the same space:
   ```bash
   INCSPARK_SPACE_ID=<saved-space-id>
   INCSPARK_TOKEN=<saved-claim-token-or-access-token>
   curl -sS -H "Authorization: Bearer $INCSPARK_TOKEN" \
     -F "spaceId=$INCSPARK_SPACE_ID" "${publish_files[@]}" \
     "https://api.incspark.com/v1/publish?wait=1"
   ```
   If an update after claiming returns `space_claimed_credential_available`, exchange the saved claim token once at `POST https://api.incspark.com/v1/anonymous-claim/exchange`, save `data.credential.accessToken`, and retry with that access token.

**Optional shortcuts and reference only:** if the `inc` CLI is already installed, `inc publish ./site --wait` does the same job. A zip of the publish folder is also supported, but neither the CLI nor a zip is required. Docs: [direct agent/API publishing](https://my.incspark.com/start) · [files and folders](/faq) · [claiming](/faq) · [updates and rollback](/dashboard/start)