docs: mark secrets phase complete
This commit is contained in:
parent
958bfaa102
commit
d2e543ce56
|
|
@ -317,12 +317,15 @@ secrets.write-ui
|
|||
- доступ к secret-store должен идти через permissions;
|
||||
- плагины не получают `secrets.read` автоматически.
|
||||
|
||||
Текущий статус: platform contract defines the draft `secret-store`,
|
||||
`secrets.read-ui`, and `secrets.write-ui` capabilities plus dangerous
|
||||
`secrets.read` / `secrets.write` permissions in the SDK manifest contract.
|
||||
Desktop core now has a local AES-GCM secret store that keeps secret IDs and
|
||||
values out of plaintext files. The official UI-only Secrets plugin and
|
||||
workspace secret references are still future work.
|
||||
Текущий статус: platform contract defines `secret-store`, `secrets.read-ui`,
|
||||
and `secrets.write-ui` capabilities plus dangerous `secrets.read` /
|
||||
`secrets.write` permissions in the SDK manifest contract. Desktop core has a
|
||||
local AES-GCM secret store unlocked once per app session by master password.
|
||||
The official `verstak.secrets` plugin shows global and workspace-scoped
|
||||
secrets grouped by workspace, copies markdown secret links, and handles
|
||||
`secret` workbench resources. The default editor renders
|
||||
`verstak-secret://...` markdown links only when a secrets open-provider is
|
||||
enabled, and opens the Secrets plugin without inserting raw values into notes.
|
||||
|
||||
## 11. `official.templates`
|
||||
|
||||
|
|
|
|||
|
|
@ -189,8 +189,8 @@ Tasks:
|
|||
|
||||
- [x] define secret-store capability and permissions;
|
||||
- [x] implement encrypted local secret storage;
|
||||
- add UI-only official secrets plugin;
|
||||
- integrate secret references with workspaces without exposing raw values to
|
||||
- [x] add UI-only official secrets plugin;
|
||||
- [x] integrate secret references with workspaces without exposing raw values to
|
||||
unrelated plugins.
|
||||
|
||||
Verification:
|
||||
|
|
|
|||
Loading…
Reference in New Issue