imccyu 1a9c1596b8 test(web): cover workspace UI branches 1 mesiac pred
..
storage 9eb9c70a8a feat(web): add workspace-aware session flow 1 mesiac pred
storage-domain 1a9c1596b8 test(web): cover workspace UI branches 1 mesiac pred
storage-json 9eb9c70a8a feat(web): add workspace-aware session flow 1 mesiac pred
storage-sqlite 9eb9c70a8a feat(web): add workspace-aware session flow 1 mesiac pred
README.md 9eb9c70a8a feat(web): add workspace-aware session flow 1 mesiac pred

README.md

storage/ — non-session storage family

The storage family persists everything that is not a session event log: a hub where named backends and typed data forms meet. Design record: domain KV storage Agent Note.

Package Role ctx key
storage/ The hub: named backend registry + merge-extensible data-form mounts, backend facet vocabulary, shared conformance suite ctx.storage
storage-json/ JSON backend: one human-readable file per unit, atomic whole-file rewrite registers backend json
storage-sqlite/ SQLite backend: one database hosting all routed units, document-per-row registers backend sqlite
domain/ Domain data form: zod-validated records, per-domain write chain, domain/changed events, backend routing by configuration ctx.storageDomain + ctx.storage.domain

Backends own one medium each and expose data-shape facets (kv today; an append-log facet is reserved for the future session-backend migration). Each backend plugin publishes an internal lifecycle service after registration; the domain plugin injects every configured backend key before exposing its own service, so config-tree row order carries no startup semantics. Consumers never touch backends directly — they inject storageDomain and open declared domains through it.