Your skills and saved workflows can be read and written through a pluggable storage backend instead of local files.
Skill scanning and workflow saving accept a storageV5 backend; with none supplied everything stays on the filesystem.
What's wrong with this entry?
Skill scanning and workflow saving can route through a pluggable storage backend instead of the local filesystem, which is the groundwork for host-managed and remote storage sessions.
- The skill scanner takes an optional storageV5 backend; for the user skills directory it lists entries through the backend.
- For any other base directory it logs a warning and falls back to the filesystem scan.
- Directory listing for user settings routes through the backend the same way, and workflow saving writes via
userConfigDir("workflows", ...)with an ifAbsent precondition when not overwriting. - Inactive unless a storageV5 backend is handed in; without one everything stays on the raw filesystem path.
falling back to the raw scan
Strings lifted out of the shipped bundle, so the claim above can be checked against them.