# $99 implementation pilot — public handoff specimen

Status: Latchshot-authored worked specimen, not customer work, a testimonial, or evidence of a paid engagement.

This document shows the shape of the fixed-scope handoff before a buyer sends a repository. A real pilot follows the target repository's names, test conventions, and approved acceptance sample. No payment, customer repository, private source, production credential, or customer data was used to create this specimen.

## 1. Scope lock

- Repository: one public GitHub repository controlled by the requester.
- Call site: one Node.js backend function that captures a social card.
- Current contract: a trusted backend sends one public URL and receives synchronous PNG bytes.
- Required behavior: 1200×630 PNG; application-owned storage remains unchanged.
- Approved sample: a maintainer-selected public HTTP/HTTPS page on port 80 or 443.
- Excluded: login state, cookies, selectors, scripts, proxy choice, provider storage, hosted artifact URLs, async delivery, and application redesign.

If the real call depends on any excluded behavior, the fit check stops the pilot before payment or code changes.

## 2. Focused replacement

The specimen implementation is downloadable as [`implementation-pilot-capture.mjs`](https://latchshot.fly.dev/examples/implementation-pilot-capture.mjs).

The replacement:

- sends the credential only in the Bearer header;
- posts an explicit synchronous PNG request to `POST /v1/render`;
- keeps the 1200×630 artifact contract visible in code;
- verifies `image/png` before returning bytes;
- returns render, navigation, and remaining-quota diagnostics to application code; and
- treats a non-2xx response as a bounded error rather than silently retrying.

The surrounding application still decides where to store the returned bytes, how to name the file, and when to run the job.

## 3. Focused test evidence

The exact runnable test is [`implementation-pilot-capture.test.mjs`](https://latchshot.fly.dev/examples/implementation-pilot-capture.test.mjs). It uses an injected local response and makes no network request.

```sh
node --test public/examples/implementation-pilot-capture.test.mjs
```

The test proves that the replacement:

1. sends the exact endpoint, method, Bearer header, and request body;
2. keeps the key out of the request URL;
3. returns synchronous bytes and named diagnostics;
4. rejects a successful response with the wrong content type; and
5. surfaces a `401` once without an unbounded retry loop.

These contract tests do not pretend that four signature bytes are a visual acceptance render. The real pilot separately exercises the approved public page with the buyer's existing or Free-plan key.

## 4. Acceptance record template

The completed customer handoff records, without secrets:

| Check | Evidence recorded |
| --- | --- |
| Focused repository checks | exact command and pass/fail result |
| Approved public sample | hostname or public fixture agreed by the maintainer |
| Artifact contract | HTTP status, `image/png`, 1200×630 dimensions, non-zero bytes |
| Render diagnostics | render time, navigation state, quota remaining |
| Application behavior | existing application-owned write path still receives the bytes |
| Residual differences | fonts, consent banners, lazy content, timing, or provider-only behavior |

No production key, authorization header, private URL, signed URL, customer data, or sensitive artifact belongs in this record.

## 5. Cutover and rollback note

1. Keep the former provider configuration available during acceptance.
2. Run both paths against the maintainer-approved public sample.
3. Confirm the focused checks, artifact type, dimensions, and application-owned write path.
4. Move only the agreed call site to `LATCHSHOT_API_KEY` after maintainer review.
5. Roll back the focused patch and restore the former provider variable if the agreed acceptance check fails.

The buyer reviews, merges, deploys, cuts over, and rolls back. The pilot never requests repository credentials or production access.

## Boundary

This specimen makes the deliverable inspectable; it does not claim a customer, payment, completed paid pilot, production cutover, savings result, or endorsement. API usage is separate from the one-time $99 implementation service. Fit, exact scope, payment, and start are confirmed by the owner before any customer-repository work begins.