wave-setuplisted

# wave-setup Bootstrap flotilla for a consumer repo by producing the `wave.config.json` that every other wave skill reads. This is a one-time setup per consumer repo (re-run to change the store, eligibility set, verify profile, or engine binding). Everything goes through the engine — the skill writes the local config file, proves it loads via `config validate`, then **runs both preflights** — the **store-preflight** (`store-preflight`, tracker facts) and the **host-preflight** (`host-pr preflight`, code-host posture) — to confirm the live preconditions actually hold before any wave is planned (ADR-0023 amendment: tracker facts and code-host facts have separate owners). It also **authors the `engine.cli` invocation binding** (ADR-0032) — the pinned local install for a Node consumer, a minimal tracked manifest for a non-Node one — so every downstream skill reads a single configured command instead of choosing among invocation forms, and **scaffolds the per-project credential lookup command** (ADR-0029) — a keychain item, a `<VAR>_CMD` entry in the tracked settings env block, and the matching `permissions.deny` entry — so a fresh consumer never has to reach for a global shell-profile export to get a wave running. Your job is the **judgment** — interviewing the three config concerns (store, eligibility, verify), composing the right JSON, and knowing which options apply to the consumer's situation. The CLI plumbing (the `config validate` / `store-preflight` / `host-pr preflight`