plugin-box

Placement	compiled-in (in-process)
Source	github.com/opencharly/plugin-box/candy/plugin-box
Version	2026.194.0000
Candy	plugin-box

This plugin is listed in charly/charly.yml’s compiled_plugins:, so its providers are compiled into the charly binary and register in-process.

Providers

The reserved words this plugin serves:

• build — command class
• feature — command class
• generate — command class
• inspect — command class
• labels — command class
• list — command class
• load — command class
• merge — command class
• new — command class
• pull — command class
• reconcile — command class
• validate — command class

What it does

The build-mode charly box … verb HANDLERS relocated into a COMPILED-IN command plugin candy (P15, K5). charly box is a SHARED command group whose subcommands have different owners: the core BoxCmd keeps only the grammar spine (a bare kong.Plugins holder, no retained verb) and candy/plugin-authoring contributes the authoring words, while THIS candy contributes twelve NESTED command providers under the box parent (each command: with CommandParent()==“box”): generate, validate, new, pull, build, inspect, list, labels, load, merge, reconcile, feature. COMPILED-IN, each dispatches IN-PROC via Invoke(OpRun) (kong-parse its sub-grammar), so the handlers own charly’s real stdio. generate renders the .build/ tree by InvokeProvider’ing the peer build:generate word (candy/plugin-build), which drives HostBuild(“build-resolve”, GenerateOnly); new (candy/project/box) calls the sdk/kit scaffold engine directly (kit.ScaffoldCandy/ScaffoldProject/AddBox), no core reentry; validate fetches the error-TOLERANT resolved-project envelope (HostBuild(“validate-project”)) and runs the whole per-kind/op rule engine + the deploykit resolution-graph checks IN-PLUGIN over it, merging the host’s CUE-conformance / tunable / base⊻from diagnostics for the verdict; load streams a host image into a RUNNING pod venue’s nested podman store over deploykit.TransferImageToVenue — the container twin of charly vm cp-box, needing no host reentry at all; inspect and list read the generic spec.ResolvedProject envelope (InvokeProvider(“build”,“project”)) — inspect’s default JSON is snake_case canonical — with the deploy-overlay formats (inspect tunnel/bind_mounts) + store-live list tags reaching the hidden core __box-inspect-overlay / __box-list-tags reentries. Their data still needs the fully-resolved project / deploy overlay / podman store the plugin cannot compute pre-K1. It imports only the sdk module, never charly core. Placement-invisible (F8): the SAME provider compiles into charly or serves out-of-process.

---

See also the candy reference for this candy’s install surface.