hyperbuild-1-intakelisted

# Step 1 — Intake You are executing step 1 (intake) of the hyperbuild pipeline. Nothing has run before you — the user just typed `/hyperbuild <idea>` and the router invoked this skill; step 2 (market recon) consumes the artifacts you write here, and EVERY subsequent step and subagent re-reads `idea.md` as gospel. **Gear gate:** runs for both gears — this step DETECTS the gear. **Goal:** turn one prompt into a durable run workspace: gospel idea file, run_tag, platform decision, gear, manifest, scaffold, and a seeded todo list — so that a crash at any later point resumes from disk, never from memory. **Verify-then-create:** the router's bootstrap may have already produced some of these artifacts before invoking you. For EACH artifact below: if it already exists and is valid, verify it and move on; create it only if missing. NEVER re-mint a run_tag when `runs/` already contains a workspace for this idea with an incomplete manifest — resume that workspace instead. --- ## Inputs - The user's idea prompt — everything after the `/hyperbuild ` command token, byte-for-byte. This is the ONLY input that exists yet. - (If the router already bootstrapped) `runs/<run_tag>/idea.md`, `runs/<run_tag>/manifest.json`, `runs/<run_tag>/scaffold.md` — verify rather than recreate. --- ## Procedure 1. **Capture the verbatim idea FIRST.** The canonical idea is everything the user typed after `/hyperbuild `, unmodified: keep their wording, their typos, their ordering, the word "premier" if p