stop
| plugin-pod — Served by | plugin-pod |
| plugin-pod — Placement | compiled-in (in-process) |
| plugin-pod — Version | 2026.201.0000 |
| plugin-pod — Served by | plugin-pod |
| plugin-pod — Placement | compiled-in (in-process) |
| plugin-pod — Version | 2026.201.0000 |
stop is a command word served by 2 plugin candies — plugin-pod and plugin-pod — at different points in the command tree. Both are real invocations; charly --help prints which is which.
About plugin-pod, which serves it
Section titled “About plugin-pod, which serves it”The charly start/stop/restart/config/shell/service/logs/remove/cp/
volume pod-lifecycle CLI — a COMMAND-class charly plugin (github.com/opencharly/sdk),
the CLI sibling of candy/plugin-deploy-pod (which keeps deploy:pod out-of-process,
untouched — mirroring the candy/plugin-vm / candy/plugin-deploy-vm split). Each command
word is INDEPENDENT (no shared parent). charly restart is pure sdk/kit + sdk/deploykit
logic (deploykit.RestartPodService) with zero host coupling. The registry-bound commands
(start/stop/…) forward their authored flags, as sdk/spec wire requests, to a per-command
HostBuild seam — the host reconstructs the original core orchestration struct and runs
its Run() logic VERBATIM (mirroring candy/plugin-fleet’s deploy-add/deploy-del seams),
because the provider REGISTRY (ResolveTarget, the plugin loader) is a core Mechanism a
plugin cannot import or hold. COMPILED-IN, it dispatches IN-PROC via Invoke(OpRun), so the
handlers run in charly’s own process and inherit real stdio/TTY natively. Placement of
THIS candy is independent of candy/plugin-deploy-pod’s placement.
About plugin-pod, which serves it
Section titled “About plugin-pod, which serves it”The charly start/stop/restart/config/shell/service/logs/remove/cp/
volume pod-lifecycle CLI — a COMMAND-class charly plugin (github.com/opencharly/sdk),
the CLI sibling of candy/plugin-deploy-pod (which keeps deploy:pod out-of-process,
untouched — mirroring the candy/plugin-vm / candy/plugin-deploy-vm split). Each command
word is INDEPENDENT (no shared parent). charly restart is pure sdk/kit + sdk/deploykit
logic (deploykit.RestartPodService) with zero host coupling. The registry-bound commands
(start/stop/…) forward their authored flags, as sdk/spec wire requests, to a per-command
HostBuild seam — the host reconstructs the original core orchestration struct and runs
its Run() logic VERBATIM (mirroring candy/plugin-fleet’s deploy-add/deploy-del seams),
because the provider REGISTRY (ResolveTarget, the plugin loader) is a core Mechanism a
plugin cannot import or hold. COMPILED-IN, it dispatches IN-PROC via Invoke(OpRun), so the
handlers run in charly’s own process and inherit real stdio/TTY natively. Placement of
THIS candy is independent of candy/plugin-deploy-pod’s placement.
charly --help prints the command tree, including where each stop is invoked and under which parent.