Plugins get a private key/value store that survives between sessions.
What's wrong with this entry?
Plugins can read and write a private JSON store that survives across sessions, kept in one file per plugin and guarded by a lock so two processes cannot corrupt it.
- The file name comes from a sanitized plugin id, falling back to a hashed name when the id will not sanitize cleanly.
- Writes go through a per-plugin queue and take a file lock with 10 retries, warning if the lock is compromised.
- Keys have a length limit and the store as a whole has a character limit; a write that would exceed it is refused.
- A store file that is unreadable or is not a JSON object raises an error naming the file.
- Behind the tengu_plugin_hooks_modules rollout flag.
is malformed (the JSON is not an object)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.