Placeholder follow-up, to be captured properly via /create-plan before or shortly after configured repos go lean (see the bundle-transport-lean-bodies item).
Why the stakes repriced: #84 accepted "no backups" while the tracker still held every item's full body + marker comments as the durable record. Once lean bodies land, the daemon VM's disk holds the only complete copy of each lean-published item's execution contract (tracker has frontmatter+summary only; ./tmp/ is uncommitted scratch), and an unreachable bundle is a hard stop for /do. #84's own wording names the shape: weekly copy to a storage bucket, or disk snapshots.
Not yet a ready work item — needs /create-plan capture (scope: backup mechanism, restore path, and whether the hard-stop gets a restore runbook).
Placeholder follow-up, to be captured properly via /create-plan before or shortly after configured repos go lean (see the bundle-transport-lean-bodies item).
Why the stakes repriced: #84 accepted "no backups" while the tracker still held every item's full body + marker comments as the durable record. Once lean bodies land, the daemon VM's disk holds the only complete copy of each lean-published item's execution contract (tracker has frontmatter+summary only; ./tmp/ is uncommitted scratch), and an unreachable bundle is a hard stop for /do. #84's own wording names the shape: weekly copy to a storage bucket, or disk snapshots.
Not yet a ready work item — needs /create-plan capture (scope: backup mechanism, restore path, and whether the hard-stop gets a restore runbook).