Expand description
SCC plugin host: discovery, loading, permissions, execution, diagnostics.
Process plugins (spec section 15): a scc-plugin.toml manifest plus a
command speaking JSON over stdio. One request per process spawn (simple,
crash-isolated, no lingering children); timeout_ms + failure_policy
bound every call. Grants are checked before spawn — a plugin never
executes code it was not granted (spec 21).
Structs§
Enums§
Constants§
Functions§
- apply_
grants - call
- Execute one plugin operation in a spawned child (crash-isolated). Grants are enforced: state read/write ops need the matching grant; everything else needs at least discovery (the plugin is enabled).
- check_
lockfile - Verify the live plugin set against the lockfile: version or artifact drift fails loudly with the drifted ids named — never silently answers from a moved plugin set.
- discover
- lock_
entry - lockfile_
path - Project plugin lockfile (§29):
.scc/plugins.lockrecords the resolved plugin set so behavior reproduces across machines. - provider_
for - read_
lockfile - write_
lockfile