threadwave-preflightlisted

# ThreadWave Preflight Own the single mandatory preflight, setup, and recovery contract. Every operation skill in the release-index roster calls this peer by name before any `tw` command. `threadwave-error-support` owns post-failure classification, solution search, and report generation. `greeting-balance` mode is the sole lightweight exception. It runs only the contract's fixed `tw credits --format json` lookup for the starter menu, skips update and readiness checks, and returns the balance or unavailable without repair. ## Mandatory Flow Read [references/preflight-contract.md](references/preflight-contract.md) completely. Unless the caller selected `greeting-balance` or issue-report-only mode, at the start of each new ThreadWave task, run its skill update check and regular CLI preflight. A receipt-aware CLI reuses its durable readiness/capability receipt while rolling inactivity is under 12 hours and performs the full check when stale or invalidated. A supported CLI result that omits `data.readiness_reuse` selects legacy full-check mode: regular preflight is already a full check, so never invoke `--force` in that mode. A review decision alone is not a new task boundary. Select and retain the contract's platform invocation adapter before the first CLI readiness call. A Windows packaged install uses the absolute system `cmd.exe` and canonical managed `tw.cmd` only for the fixed readiness templates; it never invokes a version-directory `tw.exe` or inserts user content int