gcp-stack-templatelisted

# gcp-stack-template Return the template payload for the slug the caller names, per the stack-adapter contract. Valid slugs are the ones `/gcp:gcp-stack-menu` lists: `firebase`, `cloud-sql`, `cloud-run`, `gke`. An unknown slug is an error, not a guess. > **`disable-model-invocation` must stay `false`** — see `gcp-stack-menu`. ## How to answer 1. Read `${CLAUDE_PLUGIN_ROOT}/stacks/<axis>/<slug>.md` — the template file. 2. Return **only** the payload below, filled from it. No prose around it, no summary of what you read, no advice. ```yaml slug: <the requested slug> axis: backing | deploy capabilities: [] # backing only — capability-vocabulary tokens it realizes artifact: <token> # deploy only harness: # how THIS stack satisfies each vwf capability <capability>: { task: <name>, mechanism: <one line> } # or n/a conventions: | <the template's prose — layout, wiring, placement, the decisions plan and execute need. Verbatim from the file; do not summarize it away.> ``` ## What belongs in `conventions`, and what does not The payload carries **judgment**, not API surface. vwf's callers have Context7 for the second kind and will fetch it themselves. | Include | Leave out | | -------------------------------------------------------------- | ----------------------------------- | | Which service to reach for, and when it stops being the answer | `gcloud` flags, SDK call signatures | | Cost mo