observability-stack-menulisted

# observability-stack-menu Return the templates the `observability` 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 observability contract (`${CLAUDE_PLUGIN_ROOT}/assets/contract.md`) and ships the self-hosted sink that belongs to no cloud. **Managed backends are a cloud plugin's**, not ours — and they appear there as OTLP destinations, never as vendor SDKs. vwf renders the union of both menus; never list another plugin's template here. ## How to answer 1. List `${CLAUDE_PLUGIN_ROOT}/stacks/*/*.md`. Each file is one template: its **slug** is the filename without `.md`, its **axis** is that file's `axis:` frontmatter key, and its `name` + summary line come from the same frontmatter and the file's opening prose. 2. Return the payload below — `note` included, on every answer. ```yaml plugin: observability note: This plugin ships the vendor-neutral observability contract and the self-hosted sink. A managed backend comes from the project's cloud plugin, which vwf asks separately, and terminates the same OTLP the pr