Store API snapshot JSON for people table #8
Description
Context
Follow-up to #179 (raw JSON storage for documents). The same rationale applies to all synced entities: when the API adds new fields, we lose data we didn't model.
Scope
Add an api_snapshot column (TEXT) to the people table. During sync, store the complete serialized API response for each person.
Measured sizes (from live API):
- 6 people total
- Per-person: 0.5–1.7 KB (mean ~1 KB)
- Total: ~6 KB
No redaction needed — data is small enough to store verbatim.
Related
- #179 — documents table (same pattern)