A Storage file defines typed shared client state and optional API loaders for Components.
Property: Identity · Current behavior: files below storage/
Property: Workspace · Current behavior: Storage Manager and API Loader
Property: Persistence · Current behavior: Memory, Session, or Local per schema
Property: Component use · Current behavior: mount-data-source with kind storage
Property: MCP · Current behavior: get/manage schemas, fields, persistence, and attached APIs
Property: Security · Current behavior: browser state, not a secret vault or server database
Create, rename, and delete schemas; add typed state fields/defaults; choose persistence; and attach API files. Mounted logic can read/write state and observe API request, response, loading, and error values.
Persistence keys use the file UUID and schema name. Fingerprints reconcile schema changes so incompatible changed fields can reset without necessarily discarding unrelated saved values.
Use get-storage, schema/state operations, persistence selection, shared field operations, and API loader add/delete. Mount through Component logic and verify runtime values.
Definitions are persisted and undoable. Forget saved value clears browser runtime data and reloads defaults; it is not a project edit and is not file-undoable.
Schema names must be unique. API references must resolve. Origin/profile-specific Session/Local data is not shared database storage and should not contain sensitive secrets.