launch-directorieslisted

# launch-directories — submit a product to launch directories, with proof + audit Everything lives in `directories/`. The model is: **the loop (Claude) drives the captured boseclaw Camoufox session** through each directory's submit flow — no API-keyed daemon, no fresh logins (boseclaw is already signed into Google + GitHub; the session accumulates each new site's cookies so re-runs are "hot login"). Each directory is a **script**; each run leaves **proof**; an **audit** re-checks that listings actually went live. This is our repeatable GTM muscle — we run it for every product we ship (Principle 17, distribution-first). ## Layout - `engine.mjs` — Camoufox driver + action helpers `H` (goto/wait/waitFor/fill/type/click/clickIf/ select/upload/press/url/text/has/shot) + proof capture + ledger. Pre-downloads `kit.logo` → `kit.logoFile`. - `flows/<directory>.mjs` — one proven flow per directory: `export const meta = {directory, home, submitUrl}` and `export default async function launch({H, kit}) { … return {status, listingUrl, notes} }`. Statuses: `submitted | already-live | queued | blocked | failed`. Read `flows/peerpush.mjs` (OAuth + AI-autofill + logo upload + free-queue + decline-upsell), `flows/awesomeindie.mjs` (OAuth + form + tag-select), `flows/pitchwall.mjs` (dedup + AI-generate) as the templates. - `kits/<product>.json` — the reusable product data (name, url, tagline, summary, description, categories, pricing, logo, positioningRule). One per product; every