# Receipt paste (customer after pay)

Give the buyer this block. It **is** the product surface.

```text
You are installing DevTune into this project.

1. Run exactly:
   npx devtune init
   npx devtune doctor

2. Read the files under .devtune/ai/ (AGENTS.md first, then STACK.md + PACKS.md).

3. Copy scaffold and build / remould this game so it is born-owned:
   - Copy .devtune/scaffold → games/<your-name>/ (or your existing three.js game)
   - Import packs from .devtune/medium OR rely on serve mounts at /medium/...
   - String-literal thing() ids + object-literal settings at the call site
   - Never bind(id, this.group) for the whole world

4. Run (both required — verify alone is not enough):
   npx devtune verify games/<your-name>
   npx devtune smoke games/<your-name>
   npx devtune serve games/<your-name> --shell

5. Open the URL it prints (usually http://127.0.0.1:5430/).
   I will paint feel (**C** Design) and Keep (**K**). **P** returns to Play.
   Optional: Ctrl+Shift+S export feel JSON · Ctrl+Shift+O import · then K.

6. If any command fails, stop. Do not work around it.
   Paste me the full output of the failing command.

Cadence for long builds:
- After every build chunk: npx devtune verify
- Every 30–60 minutes: npx devtune verify && npx devtune smoke
- Never delete or skip doctor/verify/smoke to stay green
- Do not invent a second physics engine
```

## Forbidden

- **Never tell a buyer there is a licence key.** There isn't one. `npx devtune init` is the whole
  command, and checkout is a Stripe Payment Link, which cannot mint anything per buyer.
- Proof of purchase is Stripe's emailed receipt. Do not invent a second artefact for it.

## Offline / no registry yet

```bash
# from a machine that has the tarball
npm install /path/to/devtune-0.1.0.tgz
npx devtune init
# …same receipt steps
```