examplestep-deploy-consumer
| Version | 2026.175.1200 |
| Repo | superproject |
Reference CONSUMER candy for the DEPLOY-context (verb-as-step deploy-execute)
leg of external plugin execution. Its plan carries a DEPLOY-context run:
step plugin: examplestep which, at LOCAL/VM deploy, charly lowers to an
ExternalPluginStep: the out-of-tree candy/plugin-example-step is host-built +
connected out-of-process (loadDeployPlugins), and its OpExecute is Invoked WITH
the live target executor stood up on the go-plugin broker (the E3b
ExecutorService reverse channel) — so the plugin writes
/tmp/charly-examplestep/examplestep-deploy/{applied,probe} on the TARGET venue
and returns a plugin-script reverse op the host records + replays at charly bundle del. The deploy-time counterpart of candy/examplestep-consumer (build
context). Compose it WITH candy/plugin-example-step (which provides the
examplestep verb); the deploy-context check below proves the marker landed.
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 |
|---|---|
run |
at LOCAL/VM deploy charly lowers this run-step to an ExternalPluginStep, Invoking the examplestep plugin’s OpExecute over the E3b reverse channel to write /tmp/charly-examplestep/examplestep-deploy/{applied,probe} on the target venue |
check |
the deploy-time examplestep OpExecute ran over the reverse channel — the probe marker is present on the target venue |