# Scratch Exit Receipt: purchase and local use

Version 0.1.1 · USD 3.00 one time (300 cents) · Stripe MPP card.

Checkout is enabled in this publication. Recheck the current offer and exact signed challenge before authorizing. Read LICENSE.md and TERMS.md before approval.

## What MCP does

House MCP discovers this ware, explains its public metadata, and returns these purchase instructions. It does not inspect your filesystem, execute the CLI, hold your recovery key or buy this ware. The separate /mcp/payments tools are for Manifest Kit; they do not purchase Scratch Exit Receipt. Use a separately authorized buyer that supports Stripe MPP and Stripe-issued Shared Payment Tokens. This page does not collect card details or offer a general browser card-entry form.

## Purchase once

1. Read the exact product, license, terms and artifact digest. Obtain explicit buyer approval for USD 3.00 and check any buyer or issuer fees. A discovery request is not payment authorization.
2. Generate and durably save a private 256-bit recovery key encoded as 64 lowercase hexadecimal characters. Request GET https://lumenhouse.xyz/api/wares/scratch-exit-receipt-v1/purchase/card with X-Lumen-Recovery-Key and no Authorization header. A 402 challenge is not a charge.
3. Verify the response and WWW-Authenticate: Payment challenge: Stripe charge, USD 300 cents, canonical lumenhouse.xyz realm, matching order/externalId, current expiry, merchant profile, product scratch-exit-receipt-v1, version 0.1.1 and the artifact/terms digests. Do not submit if these disagree.
4. Use an authorized Stripe MPP client to obtain the scoped token. Save a local permanent submission marker. Submit the credential once to the same GET route with X-Lumen-Recovery-Key and Authorization: Payment <credential>. No token or recovery key belongs in a URL, public receipt, log, chat or email.
5. A confirmed response supplies the private download route. Verify the succeeded USD 300-cent receipt and product/version/digest; GET the returned /api/scratch-downloads/{order_id} URL with Authorization: Bearer <saved-key>. Verify 77198 bytes and SHA-256 fc33eeb218ac4cbe880aa826f34ed9d5199bc06e5b648106b3ab939350ed9286 before use. Save the license and customer terms alongside the ZIP.

## Recover an existing purchase

After a 202, timeout, lost response or uncertain submission, never authorize another payment to recover. GET https://lumenhouse.xyz/api/wares/scratch-exit-receipt-v1/purchase/card with Authorization: Bearer <saved-key> only. Omit X-Lumen-Recovery-Key and Payment credentials. Keep the original key even if no order ID was received. Existing paid recovery is separate from admission of new sales. A private download requires the matching key and confirmed entitlement; a public order ID, hash or payment proof is insufficient. On 429 respect Retry-After; pending or unavailable responses are not permission to pay again.

## Install and inspect locally

Extract the verified ZIP into your chosen directory. Read START_HERE.md, README.md and SKILL.md. Requires Python 3.9+ and Git on macOS or Linux; no runtime Python packages, API key or network are needed. Python venv/pip support must already be present for optional offline installation. Windows is unsupported and unverified.

Run from the extracted package:

```sh
sh bin/scratch-exit-receipt --help
sh bin/scratch-exit-receipt '/absolute/path/to/intended-report.md' --format json
```

Select outputs you actually intend to keep. Directory expansion is bounded and per-file; links are inventoried without following their targets. The inspector is read-only and makes no network calls. Saving a receipt requires a new user-selected output file. Its optional synthetic demo builder creates new demonstration files and local commits in a new chosen directory.

Exit 0: complete without flagged risks, not proof of backup. Exit 1: complete with risks. Exit 2: partial or unknown. Exit 3: input/output error. Remote-tracking references are local historical evidence, never a live server check. Later working-tree edits remain distinct from an earlier commit.

The receipt does not preserve the files. Decide and separately authorize any copying, commit, push or cleanup. Full receipts include sensitive paths and Git identifiers; use the included redact command and review its output before sharing.
