backuplisted

# Back up the workspace Protect the family's data — materials, generated study/tests/reports, the academic map, and conversations — by pushing it to the parent's OWN **private Hugging Face Hub dataset repo**, via the `hf` CLI (already installed). This is the ONLY destination this family uses — never suggest GitHub, Drive, S3, or anything else, and never suggest a different destination "for images" — `hf upload` handles binaries fine. Same config vs status contract as `publish`/`notify` elsewhere in this app: - `backup.json` (workspace root) — declarative config: `enabled`, `repo_id` (the parent's HF username + a repo name, e.g. `janedoe/sparkquill-backup`). - `backup/status.json` — the operational result of the last attempt: `state` (`verified`, `pending`, or `failed`), last attempt/success timestamps, any error, and the source hash that was actually backed up. Never write status fields into `backup.json`. ## Steps 1. **Check the token.** The HF token lives in this app's own secrets store, not a bare `hf auth login` session — call `list_secrets` and look for one named `HF_TOKEN`. If it's missing, tell the parent plainly: create a **Write**-access token at https://huggingface.co/settings/tokens, then save it via `set_secret` (name it exactly `HF_TOKEN`) or Settings → Secrets. Don't proceed without it. 2. **Read config.** `cat backup.json`. If missing, or `enabled` isn't true, or `repo_id` is empty, this needs setup. 3. **First backup is ATTENDED — s