dotCooCoo c629753af1 Plug-ins: settings and the cache total stay in memory between storage calls ...

A settings get no longer reads and parses settings.json each time. The
parsed settings are kept per plug-in folder and read again only when the
file's size or modified time changes. A set to the value a key already
has writes nothing, and every other change is written with an atomic
write before the call returns. plugin.remove drops the kept copy.

cacheBytes in plugin.list, plugin.info and plugin.install comes from a
total kept while the cache folder keeps its modified time, instead of a
listing of up to 8,192 items per call. A cache write still lists the
folder to enforce the caps.

docs/plugins.md states what a run counts and that a cache call moves a
whole entry in one step. docs/plugins.md and docs/mcp.md now say when a
later plugin.remove retries a leftover .removed folder.

2026-11-08 17:17:34 -08:00

..

example

…

src

Plug-ins: settings and the cache total stay in memory between storage calls

2026-11-08 17:17:34 -08:00

tests

Plug-ins: a plug-in keeps settings and a cache of its own

2026-11-09 02:54:33 +07:00

Cargo.toml

Plug-ins: API level 2 lets a plug-in report progress, see Cancel and write log lines

2026-11-08 13:21:15 +07:00