# feat: the web build keeps its files in OPFS · clo/snowbound

[View on GitCafe](https://git.cafe/clo/snowbound/commit/a37218b17ff30f35310862f62150db6f4a6dca04)

Repository: [clo/snowbound](https://git.cafe/clo/snowbound)

Visibility: public

Requested revision: a37218b17ff30f35310862f62150db6f4a6dca04

Requested commit: a37218b17ff30f35310862f62150db6f4a6dca04

Commit: a37218b17ff30f35310862f62150db6f4a6dca04

Tree: 92524f427ee40144bea0e7dfe76d81d93f7ab0f2

Author: clover caruso

Committer: clover caruso

## Message

```
feat: the web build keeps its files in OPFS

The browser's notebooks, replicas and settings move from IndexedDB to
the origin's private file system. A storage worker owns OPFS's
synchronous handles, which only workers get, and writes the byte ranges
each burst changed in place: notebook::fs now tracks what was written
since the host last asked, so a commit writes its appended revision and
the header rather than the whole section, and SQLite its pages. The app
itself stays on the main thread, where the shared code's synchronous
dialogs work. IndexedDB's files, and the first web build's sections,
move over once.

Assisted-by: claude-opus-5.5

```

## Parents

- [563a6671858bb6446fcc24546f424b3e379f9063](https://git.cafe/clo/snowbound/commit/563a6671858bb6446fcc24546f424b3e379f9063?format=markdown)

[Source at this commit](https://git.cafe/clo/snowbound/tree/a37218b17ff30f35310862f62150db6f4a6dca04?format=markdown)