docs: sync docs with encrypted settings store (VA-33) #31
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/encrypted-settings-store-VA-33"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Documentation-only. Syncs the docs with the encrypted local-settings store that landed in VA-33 (PR #30, now on main). No code changes.
Why
VA-33 replaced the plaintext
.mshconfig with an encrypted<stem>.vssstore, but README/ROADMAP still described the old.mshsurface, and the README linked todocs/local-settings-store.md, which only existed on the unmerged VA-29 branch (dangling link on main).Changes
--checkand self-update bullets, theServerIDpinning note, and the local-data-store design decision to describe the encrypted.vssstore and the sled identity store separately. Added aConfigurationsection covering--settings/--secret-file, theconfig show/get/set/sealsubcommands, automatic.mshmigration, and the install flow. Addedsettingsto the listed library modules.vervain-agent-mcp) and recorded the VA-33 delta.Implementation notessection reconciling what shipped against the plan (whole-file AEAD not SQLite,--settingsis a directory, kept the.msh.templatename, read-only--check). Original design body preserved as rationale.Note
This supersedes PR #29 (the VA-29 design-doc deliverable): the same doc is included here with its status updated, so #29 can be closed.
a85eb3ae40c4078300f8