hyperbuild-4-5-feature-specslisted

# Step 4.5 — Feature specs (parallel, 3–5 authors) You are executing step 4.5 (feature-specs) of the hyperbuild pipeline. Step 4 froze the PRD — its MoSCoW list and canonical screen inventory; this step expands every must/should feature into a complete spec file that steps 6–8 (design + mockups) read for real content and flows, step 11 tasks cite by id (`features: [F-NN]`), and step 14 implementers treat as primary spec alongside the task file. **Gear gate:** runs for both gears. Cap: **15 feature files (standard) / 25 (premier)**. Every must/should gets a file; could-features get files only if the cap still allows. **Goal:** one `features/NN-<slug>.md` per must/should PRD feature plus `features/00-index.md`, every claim traceable into `research/`. A feature spec nobody evidenced is a requirement nobody asked for — the authors cite the vault, never their imagination. --- ## Inputs - `runs/<run_tag>/idea.md` — the verbatim app idea. GOSPEL. - `runs/<run_tag>/manifest.json` — `run_tag`, `gear`; confirm `steps["4"]` is `"done"` - `research/product-spec.md` — the PRD: MoSCoW feature list (with Evidence lines) + the canonical screen inventory. FROZEN — never rename a screen or feature here. - `research/01-product-and-market/` — the evidence vault the authors cite, in the four phases of `docs/RESEARCH-ARCHIVE.md`: `author/sentiment-synthesis.md` and `author/competitor-landscape.md` (the syntheses), `research/sentiment/*.md` and `research/competitors/*.md` (the verbatim quotes