VSKI v0.15.6
Plugin process keys gain the workflows role. Safe upgrade from v0.15.5.
Plugin keys can signal pipeline runs
Section titled “Plugin keys can signal pipeline runs”- The per-process API key the plugin supervisor mints for every instance
now carries
workflowsalongsideplugin. Plugin functions already wrote collections with their role-scoped key; now they can also call the workflow API, which is what an ack-fast plugin needs to report back:ctx.client.workflow.send_signal(run_id, name, data)completes a pipeline run’s waitingsignalstep, so a pipeline that kicks a long background job can still finish (or fail) when the job actually lands. The docs MCP indexer uses exactly this loop: anindexstep acks in seconds, asignalstep parks the run while indexing runs in the plugin, and a final step re-raises the error payload so a failed pass fails the run. - The role grants the workflow endpoints generally (runs, events, queue), not only signal delivery. Plugins are admin-installed supervised processes; the role keeps them off the admin surface.
- Keys are minted fresh at every process start, so running instances pick the role up on their first restart after the upgrade. No migration, no configuration.