feat(import): add design.md import reverse command

[zagi]

Generates a DESIGN.md from an existing Node.js project by statically
analyzing its design sources. No AI, no network — deterministic code
analysis that runs in ~5ms on a clean project.

Pipeline

  detect framework → scan sources → parse → merge → emit

What it reads

• package.json / README.md — project name, description, version, and first-paragraph intro. README H1 beats package.json.name; directory basename is the final fallback.
• Tailwind configs (tailwind.config.{js,ts,cjs,mjs}) — loaded via dynamic import (Bun handles TS natively); theme.extend is walked for colors, borderRadius, spacing, fontSize (incl. the [size, meta] tuple form), and fontFamily. Regex fallback on eval errors so malformed configs still surface their color block.
• CSS custom properties — both Tailwind v4 @theme { } blocks (with prefix-stripping: --color-primary → colors.primary, --spacing-md, --radius-lg, --font-*, --text-*, --leading-*, --tracking-*, --font-weight-*; --breakpoint-* skipped) and legacy :root { } blocks (name-heuristic classification).
• DTCG tokens (tokens.json, design-tokens.json, design_tokens.json, *.tokens.json) — walks $type/$value; only accepts tokens under colors / spacing / rounded / typography top-level sections so per-component dimensions don't pollute the scale.

Framework detection

Cosmetic, reported in the UI. Recognizes Next, Nuxt, Vite, SvelteKit,
Remix, Astro, Create React App, Gatsby, Angular, Vue CLI, and falls
back to generic Node / unknown. Meta-frameworks beat Vite on conflicts.

Scan hygiene

Bounded at depth 5. Skips node_modules, .git, .next, .nuxt, .output,
.svelte-kit, .turbo, build, coverage, dist. Also skips vendor trees
(public, static, vendor, vendors, third-party, third_party, bundles,
charting_library), minified/RTL stylesheets (*.min.css, .rtl.css),
and hashed bundler output (..css) — so e.g. a bundled
TradingView charting library's 40+ v-rhythm- tokens don't leak into
the project's own design system.

Merge

Precedence: CSS → Tailwind → DTCG (later wins because DTCG is most
structured). Rebuilds the flat symbolTable the linter expects so the
generated state can be round-tripped through lint/export.

Output

YAML frontmatter (name, description, colors, typography, rounded,
spacing) plus a markdown body: # Name heading, description, README
intro, ## Overview (framework + counts + source summary),
per-section bullet lists of the imported tokens, and a footer
inviting the team to edit the prose. The frontmatter alone
round-trips cleanly through lint and back through export.

CLI

  design.md import <project>              # writes <project>/DESIGN.md
  design.md import <project> --dryRun     # prints to stdout
  design.md import <project> --format json # NDJSON progress events

Pretty mode renders live via Ink, showing staged progress (◐/✓/⚠/✗)
for detect → scan → parse → merge → write. JSON mode emits one
ImportStep per line on stdout for scripts and CI.

Tests

275 passing. Unit tests cover every parser, the framework detector,
the source scanner's vendor filtering, the merger, the markdown
emitter, project metadata, and the Ink component. Integration tests
(VR-1, VR-2) round-trip examples/paws-and-paths, atmospheric-glass,
totality-festival, and three framework fixtures (Next, Vite, Nuxt)
through import → lint and assert zero linter errors.

Build

Marks ink, react, and react-devtools-core as --external so Ink 7's
devtools import doesn't break the bundler.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.