docs: CLAUDE.md points at LIBS.md; ignore .boot.log

Two follow-ups to 8cd5805:

- CLAUDE.md's "Crema system" section now points at docs/LIBS.md (the
  generated catalog) as the primary lookup. Live manifest reference moved
  below as a fallback. Keeps the LLM's first hit at a compact, alpha-sorted
  table instead of the live JSON.
- The .boot.log file (created by my fresh-clone integration test) was
  accidentally committed in 8cd5805. Remove from tracking and ignore going
  forward.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

.boot.log

@@ -1,9 +0,0 @@
-
-> dev
-> react-router dev
-
-Port 5173 is in use, trying another one...
-  ➜  Local:   http://localhost:5174/
-  ➜  Network: use --host to expose
-6:37:06 pm [vite] (client) ✨ new dependencies optimized: lucide-react, @base-ui/react/button, class-variance-authority, @base-ui/react/input, @base-ui/react/avatar, @base-ui/react/dialog, clsx, tailwind-merge, @base-ui/react/menu, react-markdown
-6:37:06 pm [vite] (client) ✨ optimized dependencies changed. reloading

.gitignore

@@ -8,3 +8,4 @@
 
 .demo.log
 .demo.pid
+.boot.log

CLAUDE.md

@@ -41,14 +41,20 @@ There is no test runner configured. `package.json` has no `test` script and no v
 
 ## Crema system (authoritative)
 
-- **Manifest** (canonical catalog of all libs and themes) lives in the `crema-manifest` repo. The Gitea raw-file HTTP URL 404s, but the repo is publicly cloneable — fetch it with:
+- **Lib catalog:** see `docs/LIBS.md` for a snapshot of every `@crema/*-ui` lib
-  ```bash
+  (the ones wired into this project AND the ones available to add). Before
-  git clone --depth 1 https://git.sky-ai.com/CremaUIStudio/crema-manifest.git /tmp/crema-manifest && cat /tmp/crema-manifest/manifest.json
+  building any UI primitive, check there first — there's a good chance a lib
-  ```
+  already does it. Refresh the snapshot with `npm run sync-libs`.
-  Each entry has `name`, `alias` (`@crema/<name>`), `category`, `description`, `navLabel`, `navIcon`, and `demo.files[]`.
+- **Each `@crema/*-ui` lib is its own git repo** at
-  Check this before building any UI primitive — there's a good chance a `lib-*-ui` already does it. The per-lib `src/index.tsx` `// PURPOSE` / `// EXPORTS` header in the sibling repo is the same info at finer grain.
+  `https://git.sky-ai.com/CremaUIStudio/lib-<name>-ui`, cloned as a sibling
-- **Each `@crema/*-ui` lib is its own git repo** at `https://git.sky-ai.com/CremaUIStudio/lib-<name>-ui.git`, cloned as a sibling of this app. Edits to lib code commit to that lib's repo, not this one.
+  of this app. Edits to lib code commit to that lib's repo, not this one.
 - **Themes** (`lib-theme-*`) are CSS-only token files at the same Gitea org.
+- **Live manifest** (which `docs/LIBS.md` is generated from) is the
+  `crema-manifest` repo. Gitea's raw-file HTTP URL 404s; clone instead:
+  ```bash
+  git clone --depth 1 https://git.sky-ai.com/CremaUIStudio/crema-manifest.git /tmp/crema-manifest
+  cat /tmp/crema-manifest/manifest.json
+  ```
 
 ## Adding a lib after scaffold
 
@@ -65,6 +71,8 @@ Manual fallback (3 edits):
 2. `app/app.css` → add `@source "../../lib-<name>-ui/src";`
 3. `tsconfig.json` paths → add `"@crema/<name>-ui": ["../lib-<name>-ui/src/index.tsx"]` and the `/*` variant.
 
+Then run `npm run sync-libs` to refresh `docs/LIBS.md`.
+
 ## Theme convention
 
 - A single theme (`lib-theme-mightypix` by default) is loaded via `:root` in