project-adoptlisted

# project-adopt The one-time inception pass for a product that **already exists as code** — the brownfield sibling of `project-init`. Input: an existing codebase (a path, a git URL, or the drop dir). Output: a product brief reverse-engineered from the observed product, a **migration map** carrying the parity contract and disposition table, and a regenerated status doc + banded backlog whose completion is *a surface-identical app on the target foundation — every carried feature working, proven by the port's parity specs and carried suites at the adopting repo's enforced thresholds — with the foundation features that pass the meaningful-improvement bar (§3) baked in* — then the lifecycle pipeline begins at row 1. Adapter: `.claude/ai-dev-kit.config.json` (`init.productBrief` default `docs/PRODUCT.md`, `init.migrationMap` default `docs/MIGRATION.md`, `init.sourceDir` drop dir default `intake/source/`, `init.scaffold` — `{name}` → the app name, `docs` block); a missing field → derive it from the repo and say so. Flags: `--deep` (survey fan-out), `--name <app-name>`. "The foundation" below = the template/boilerplate the port lands on. **No foundation heritage** (adopting into a plain scaffold or bare repo)? The survey and parity contract run unchanged; in §3 the product surface defaults keep-theirs as usual, replace-with/light-up buckets exist only where the chosen stack actually ships a counterpart, and everything else becomes port-onto rows against that stack. Shared inceptio