datastore-stack-menulisted

# datastore-stack-menu Return the templates the `datastore` 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 datastore contract (`${CLAUDE_PLUGIN_ROOT}/assets/contract.md`) and ships the one provider that belongs to no cloud. **Managed flavours are a cloud plugin's**, not ours — a product on GCP gets Firestore and Cloud SQL from `gcp`, and 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: datastore note: This plugin ships the vendor-neutral datastore contract and the provider that needs no cloud. A managed datastore comes from the project's cloud plugin, which vwf asks separately. templates: - slug: <filename without .md> a