component-librarylisted

# Component Library Personal store for UI components the user builds or adapts, so they can be found and reused in any later project instead of rebuilt. The store is a shadcn-compatible folder (`registry.json` + `r/<name>.json` + `items/`) plus a flat `index.jsonl` the agent can grep cheaply even with hundreds of items. Companion to `expert-build-pack` (used at the end of buildout sessions to keep what was built). ## When to Use - User says "save this component", "keep this for later", "reuse X in my other project", "find something I built". - A component was built or meaningfully refined in a session and is worth keeping (offer to save at wrap-up). - Before hand-building UI from scratch — check the library first. ## Don't Use For - Third-party code with unverified provenance/license (MIT-only rule from `expert-build-pack`; record `--source` always). - One-off style snippets — store real components. ## How to Run ``` py scripts/library.py add --name <slug> --file <path> [--file ...] [--tags a,b] [--section pricing] [--source "built 2026-09-17 @ proj"] [--strict] [--force] py scripts/library.py find "<query>" [--limit 5] py scripts/library.py list py scripts/library.py show <name> py scripts/library.py copy <name> --to <dir> py scripts/library.py remove <name> ``` (On macOS/Linux use `python3`. Store location follows `EXPERT_BUILD_LIBRARY` if set.) ## Procedure 1. **Save.** Run `add` with every file of the component; keep files token-based (no raw hex — `--strict` en