Prod consolidation — measured state + what moved + what waits for Tam

Young, 2026-10-13: Tam + Mira to consolidate Docs-website to match the LAB vault (Pulse + Docs), clean up prod vault and .solos\docs\vault, clean up eva_rerender_backup. Work with Tam.

1. Vault→prod sync path: HEALTHY, no action needed

Mechanism: /home/ubuntu/vault-sync.sh every 30 min — git pull --ff-only the clone + rclone sync to gdrive:vault (with backup-dir). The vault and the prod docs already match at the repo level.

2. DONE by mira — eva_rerender mp3s archived (not deleted)

22 files eva_rerender_backup_episode-*.mp3 (Aug 24–Sep 28, 21 MB) sat orphaned in /home/ubuntu/. Verified before moving:

• Not referenced anywhere on pulse-site (grep over content/public/server: zero hits).
• Irreplaceable: pulse-site public/podcast/ holds 13 files, ALL October. These 22 are the only September copies — deletion would have destroyed the Sep archive.

Moved (same host, reversible): /home/ubuntu/ → /home/ubuntu/archive/podcast-2026-08-09/. Verified: 22 in archive, 0 remaining in home.

3. HELD for Tam — /home/ubuntu/vault (212 MB, not git)

Lowercase /home/ubuntu/vault is a separate working tree, not a clone: pulse/ (189 MB) + _archive/ (23 MB, incl. solos-20261005-224441.tar.gz) + _conflicts-solos

• _migration + _recovered-from-gdrive. It differs structurally from the git clone. Nothing in code or cron reads it (cron uses .solos/docs/vault), but its shape — conflicts, migration, recovered-from-gdrive — reads like an agent's working area, possibly Tam's. Not touched.

Also untouched: prod clone's untracked solos/ (40 KB) + Pulse/probe/vault-sync-probe.md (a liveness timestamp) — tiny, possibly Tam's; leave for her to claim or drop.

4. Tam contact: A2A attempted, no reply — reached via group instead

message/send to Tam (192.168.4.34:8443) held past timeout with no reply (TASK_STATE_FAILED, "agent did not reply in time"). Questions for Tam are in Young's group message; she reads there via @SolOSTam_bot.

Questions for Tam:

1. Is /home/ubuntu/vault (lowercase, 212 MB) hers — archive it, or working state?
2. Her prod crons tam-vault-sync / pulse-publish-prod paused since 2026-10-05 on the tam_vault_key permission bug — repair the key (durable fix) or keep one-offs?
3. Archive location for the mp3s OK (/home/ubuntu/archive/podcast-2026-08-09/), or move them under pulse-site?
4. Confirm no mid-edit on docs-site content/ before the next sync.