# Raw platform captures — local only, never committed

This whole directory is gitignored (see `.gitignore`). Nothing in here should
ever be staged.

## What lives here

Real authenticated API responses, captured by hand from the operator's own
browser session, kept as the ground truth a characterization note gets
re-checked against. Re-capturing is manual and requires re-authenticating, so
these are worth keeping locally even though they can't be committed.

They carry live account data. The Patreon members capture, for example,
contains the operator's creator list, pledge amounts, and — inside the `card`
resources the web app's include set pulls — the account's own email address.
That is exactly why the directory is ignored wholesale rather than by filename.

## What does NOT live here

**Sanitized fixtures belong in git**, under `tests/fixtures/`, not in this
directory. A fixture with the account data stripped is the thing tests should
load; the raw capture is only for deriving it and for re-checking a
characterization when a platform's shape is suspected to have drifted.

## Current contents expected

| file | characterized in | step |
|---|---|---|
| `patreon_members_<YYYYMMDD>.json` | Scribe note #3886 | milestone 387 C0 |

## How to (re-)capture the Patreon members response

1. Log in, go to `patreon.com/settings/memberships`.
2. DevTools -> Network, filter `api`, reload.
3. Find the `members?include=...` request (it self-identifies: its query string
   ends `members_request_source=settings_memberships`).
4. Right-click the request -> **Save Response As...** -> save it here.

Save the response, not a HAR: a HAR bundles the request headers, which means
the session cookie ends up in the file.

Note that the response's own `links.first` is built WITHOUT the `/api/` prefix
and is not a usable URL — see note #3886 before writing a client against it.