orchestration-stack-templatelisted

# orchestration-stack-template Return the template payload for the slug the caller names, per the stack-adapter contract. The valid slugs are **exactly** the ones `/orchestration:orchestration-stack-menu` lists, and nothing else. > **`invocation` must stay `both`** — see `orchestration-stack-menu`. An unknown slug is an **error**, not a guess. Name the slugs that do exist, and add that managed queues, buses and schedulers come from the project's cloud plugin rather than from here. Never answer a slug this plugin has not written from general queueing knowledge — a template it has not written is a template it does not offer. ## How to answer 1. Read `${CLAUDE_PLUGIN_ROOT}/stacks/<axis>/<slug>.md` — the template file, whose own `axis:` frontmatter key is authoritative for the axis. 2. Read `${CLAUDE_PLUGIN_ROOT}/assets/contract.md` only when the caller asks what the capability requires in general, or asks which of queue / bus / scheduler / workflow engine the product actually needs. A template payload does not carry it: the template already states how *this* engine satisfies it. 3. Return **only** the payload below, filled from the template file. No prose around it, no summary of what you read, no advice. ```yaml slug: <the requested slug> axis: <the file's own axis: key> capabilities: [] # capability-vocabulary tokens this engine realizes harness: # how THIS engine satisfies each vwf capability <capability>: { task: <name>, mechanism: <one line> } # or n/