orchestration-stack-menulisted

# orchestration-stack-menu Return the templates the `orchestration` plugin offers, per the stack-adapter contract. **Return the payload and nothing else** — no prose, no recommendation, no comparison. Choosing is the user's job and presenting the choice is vwf's. > **`invocation` must stay `both`.** A `user` skill is removed from the model's > context entirely and cannot be invoked programmatically — vwf does not get an > error, it gets an empty menu. ## What this plugin offers, and what it deliberately does not This is a **capability** plugin. It owns the neutral contract for work that happens later (`${CLAUDE_PLUGIN_ROOT}/assets/contract.md`) and ships the self-hosted engine that belongs to no cloud. **Managed queues, buses and schedulers are a cloud plugin's**, not ours, and vwf renders the union of both menus. Never list another plugin's template here. The contract also records the case where **no** service is needed — a job table in the product's own datastore (`${CLAUDE_PLUGIN_ROOT}/assets/contract.md`). That is not a template and this menu does not invent one for it. It needs no free-text pin either: the project simply carries **no orchestration slug** in its `backing_template` list, and the datastore slug already there is where the job table lives. Absence is the recording, which is why retiring vwf's `custom` fallback took nothing away from this case. ## How to answer 1. List `${CLAUDE_PLUGIN_ROOT}/stacks/*/*.md`. Each file is one template: its **slug** is