plugin-pipeline
| Repo | box/github.com/opencharly/plugin-pipeline:v2026.282.2329 |
| Plugin | yes — see the plugin reference |
The workflow front-end — domain-neutral: resolve + validate a declared
kind:pipeline entity (spec.Pipeline, steps:), lower it with
sdk/workflowkit to the (workflow.lobster, charly.yml) pair, and dispatch
the pair to the workflow provider class as workflow-run. Also the bare
agent runtime (the standalone ‘charly pipeline agent’), deterministic
probe verbs, template/frontmatter rendering, and skills by @github candy
refs. Every stage kind is ALSO a reachable verb
(verb:agent/probe/ade/generate/emit/media/gate), so a stage body can be
driven as a <word>: <input> step from any plan. Execution/control flow
belongs to the workflow ENGINE, not this plugin.
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
check |
the pipeline-skill skill entity is present in this candy’s manifest (fails if the entity is removed) |
check |
the pipeline module ships (go.mod + the front-end + generated params) |