flutter-stack-templatelisted

# flutter-stack-template Return the template payload for the slug the caller names, per the stack-adapter contract. The valid slugs are **exactly** the ones `/flutter:flutter-stack-menu` lists, and nothing else. An unknown slug is an error: name the slugs that do exist and stop. > **`invocation` must stay `both`** — see `flutter-stack-menu`. ## How to answer 1. Read `${CLAUDE_PLUGIN_ROOT}/stacks/project/<slug>.md` — flat since format 22 — the template file, whose own `platforms:` frontmatter key is authoritative for which platforms it serves. Read that one file and nothing else; the deep Flutter doctrine lives in this plugin's `dart`, `pubspec`, `analysis-options` and `internationalization` skills and is loaded when it is needed, not here. 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: project platforms: <the file's own platforms: list> languages: [ <the file's languages:> ] optional_languages: [ <the file's optional_languages:> ] frameworks: [ <the file's frameworks:> ] dependencies: [ <the file's dependencies:> ] harness: # how THIS stack satisfies each vwf capability <capability>: { task: <name>, mechanism: <one line> } # or n/a conventions: | <the template's prose — layout, tooling, testing, the changelog and store-note discipline. Verbatim from the file; do not summarize it away.> ``` ## What belongs in `conventions`, and what does not