backuplisted

# Back up the workspace Protect the family's data — materials, generated study/tests/reports, the academic map, and conversations. **Choosing the destination — this workspace is IMAGE-HEAVY** (photos/scans of homework). Do NOT recommend GitHub as the main backup: git keeps every version of every binary, so an image-heavy repo bloats fast, and GitHub rejects large files. Prefer, in order: 1. **Google Drive via the `gws` CLI (recommended — already set up).** The parent has the Google Workspace CLI installed and authenticated, so upload the workspace straight to their Drive with `gws drive +upload` (run `gws drive +upload --help` for the exact flags). Ideal for image-heavy content, and it's the parent's own storage. 2. An **object store** — Cloudflare R2 / S3 / Backblaze B2 — via `rclone sync`, if the parent set one up. 3. A **synced folder** — Dropbox / iCloud — copy the workspace into it. A git repo is only a good fit for the small TEXT/config (family profile, generated .md/.html) — not the images — and local git is a temporary checkpoint at best. Config and status are SEPARATE files (same contract as AgentWorks): - `backup.json` (at the workspace root) — the declarative config: `enabled`, `mode`, and `destinations`. - `backup/status.json` — the operational result of the last attempt (state, timestamps, per-destination results, errors, and the current source hash). Never write status fields into `backup.json`. ## Steps 1. **Read config.** `cat backup.j