Context:
Every fetch writes to content-ingest-volume at /clients with no backup and no mirror. Railway volumes are strictly single-service, so the backup job has to run inside content-ingest — a sidecar cannot mount it. Already recorded under Known Gaps in DEPLOYMENT.md; this closes it. Phase 1 is a one-off railway run -- tar snapshot that doubles as the volume's first backup.
Context:
Every fetch writes to
content-ingest-volumeat/clientswith no backup and no mirror. Railway volumes are strictly single-service, so the backup job has to run insidecontent-ingest— a sidecar cannot mount it. Already recorded under Known Gaps inDEPLOYMENT.md; this closes it. Phase 1 is a one-offrailway run -- tarsnapshot that doubles as the volume's first backup.