v1.1.2

Patch release fixing where the bundled CLI writes files.

Fixed

npx @babelize/elements add <component> wrote to the wrong directories.
components.json stores aliases as import specifiers (@/components), and the CLI
turned one into a path by stripping the @/ prefix. In a Next.js project — where
@/* maps to ./src/* — files landed a level too high:

./components/ui/navbar.tsx     instead of  ./src/components/ui/navbar.tsx
./lib/utils.ts                 instead of  ./src/lib/utils.ts

and the @/lib/utils imports inside them then resolved to nothing. The CLI reported
success either way.

Alias resolution now reads compilerOptions.paths from your tsconfig.json or
jsconfig.json, prefers the most specific pattern, honours baseUrl, and tolerates
the comments and trailing commas that tsconfig allows.

The npx shadcn@latest add @elements/<component> path was unaffected — shadcn's CLI
already resolved aliases correctly.

Also

• Dropped nine unused Google Font families from the docs site, removing a
  render-blocking third-party stylesheet request.
• Added ARCHITECTURE.md for contributors: how the library, registry and docs site
  relate, the conventions every component follows, and the files a new component
  touches.

No changes to the components themselves; upgrading from 1.1.1 is safe.