feat(vcs): vcs check and vcs rollback

Radin committed …

⧉5e2c5951f573

Author

Radin · radin@coline.appOct 28, 2026 at 02:18

Committer

Radin · radin@coline.appOct 28, 2026 at 02:18

Parents

db9b785686d6

feat(vcs): vcs check and vcs rollback

- vcs check: every object this machine keeps against its ID (in
  parallel), and the host's check of its copy: each version's ID against
  its contents and the one before it, and that every file, folder and
  part of a big file main needs is stored. Exits 1 on damage. Upstream's
  host and vcs-server both answer it (21,178 versions: 0.6 s live).
- vcs rollback --to <time> (owners): Upstream's host puts the whole
  project back as it was, from the 30 days of history Durable Objects
  keep, and answers a bookmark; --undo <bookmark> reverses it. A project
  with a git view pauses it (a note outside the restored state, since
  that state can't know), so git main's later commits don't come back in;
  vcs git resume keeps them in git's history as a second parent.
- Workspaces follow a rollback: refresh drops versions the host no
  longer has, and sync moves the change onto the rolled-back main.

Tried live: a land, a rollback past it, the undo, a second rollback; and
on a project with a git view, rollback, pause, resume and a merge commit
keeping the rolled-back commit in git's history.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>