feat(onset): the host keeps what landings make as deltas

Radin committed …

⧉2fe4c9c6f778

Author

Radin · radin@coline.appOct 31, 2026 at 23:53

Committer

Radin · radin@coline.appOct 31, 2026 at 23:53

Parents

429eadbb299a

feat(onset): the host keeps what landings make as deltas

Each land wrote every folder on its paths again, whole: a folder of 256
agents' files was 13 KB a land, twice for edits made on an older version.
Now what a landing makes over an object already stored (each folder, a
file it edited, a merged file) is kept as a delta on it:

- onset-core: delta::encode (git's delta format, every run in common, not
  just a shared start and end); edits and merges say what each new folder
  and file replaced; bundles have a DELTA codec (2) that only a host's own
  storage reads (read_stored). Uploads with one are refused.
- The host keeps a delta when it's under half the object and its base is
  stored, or made by the same landing; chains stop 32 deep. Objects get
  base and depth columns.
- Reading loads a delta's chain into the core's cache first. Downloads and
  everything that reads frames (git view, big files' lists, purge) get
  them whole, so CLIs never see one. Purge makes whole what leans on an
  object it deletes.

Land bench, 3,000 lands: 1.8 KiB stored a land (256 agents, one folder)
and 1.2 KiB (32), from 13-26 KB, at the same CPU. hosted.sh reads every
version of a file landed on 40 times, before and after a restart (with
the chains compacted to storage), and checks the host kept deltas;
project check counts them.

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