aleleba/vectorcraft
1
0
Fork 0
mirror of https://github.com/storytold/vectorcraft.git synced 2026-11-11 02:19:56 -06:00
Code Issues Packages Projects Releases Wiki Activity

Merge main into fix/plugin-grant-app-approval

Browse Source
This commit is contained in:
dotCooCoo
2026-11-08 23:53:57 -08:00
parent 0efd9a9ccc 4c37ca8597
commit eebbe496d4
14 changed files with 813 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/mcp.md
+4 -1
View File
@@ -6717,7 +6717,10 @@ flag lasts for that session only. In other sessions the approval, or a `grant` a
hash, counts as approved in later sessions and in the desktop app, and covers only that module: the
same bytes install again without one, also from a headless session that reads the same `grants.json`, and a module
with other bytes has `needsApproval: true` and needs a new one even when it lists the same permissions. `plugin.remove`
forgets the approval. A
forgets the approval, and so does installing a module that lists no permissions under that id: the earlier bytes then
need a new approval. A refused install keeps the grant. A failed write of the module to the plug-in store leaves the
grant in the store. A stored module that is disabled, or not read in Safe Mode, keeps the grant for its id. When
`plugin.remove` can't remove the grant from the plug-in store, it returns an error and the plug-in stays installed. A
filter without `doc.write` or `state` that returns output needing them gets an error and the document is unchanged.
A plug-in of API level 2 (`api: 2` in its entry) that lists `progress` may report its progress, see Cancel and write
log lines: `notifications/cancelled` makes its `vc_cancelled` return 1, and its log lines go to the server's log