Release 0.3.1 — collections as first-class DB entity

[tylernash01]

Summary

• Promotes collections from localStorage-only strings to a first-class DB entity with full CRUD API
• Empty collections now appear in the CLI picker (skillnote-pick) at session start
• Auto-migrates existing localStorage-meta entries to the API on first load of /collections

Root cause

The CLI picker fetches /v1/collections, which was implemented as SELECT unnest(collections) FROM skills ... GROUP BY name — a collection only surfaced once ≥1 skill referenced it. NewCollectionModal wrote only to browser localStorage, so newly-created empty collections were invisible to the CLI picker. Adding one skill would suddenly make the collection appear.

What changed

Backend (9 commits):

• Migration 0011_collections_table: new collections table keyed by name, with description + timestamps
• Collection SQLAlchemy model + CollectionCreate/Update/Detail/ListItem Pydantic schemas
• validate_collection_name — free-form text (to preserve "lp assessment"), max 128 chars, non-empty, no newlines/XML
• GET /v1/collections now UNIONs skill-derived names with empty rows from the table; response gains an additive description field (CLI keeps working)
• POST /v1/collections (409 on duplicate), PUT /v1/collections/{name} (description-only; no rename in 0.3.1), DELETE /v1/collections/{name} (409 if any skill still references it)
• Fix: replaced fragile db.refresh(col) after commit with explicit re-query — db.refresh fails intermittently under connection-pool reuse (same latent pattern exists in skills.py:318, out of scope)

Frontend (4 commits):

• src/lib/api/collections.ts — typed API client
• NewCollectionModal POSTs to the API, falling back to localStorage + error toast on network failure
• /collections page reads from the API and auto-migrates stale skillnote:collections-meta entries (POST missing ones, then clear on success; retry next page load on partial failure)
• Inline CollectionPicker (skill editor) fetches from the API with localStorage fallback

Test plan

• pytest tests/unit/test_collection_validator.py — 8/8 passing
• pytest tests/integration/test_collections_api.py — 11/11 passing (covers shape, POST + dup + validation + whitespace, PUT + 404, DELETE + 404 + 409 skill-ref)
• 50-cycle POST→PUT→DELETE stress test on a long-running container — 50/50 passing after the db.refresh fix
• API smoke: POST empty collection → appears in GET with count: 0, description → CLI picker's fetch_collections() sees it → DELETE returns 204
• Edge-case matrix: validation 422s (empty, whitespace, XML, newline), duplicate 409, 404s, skill-ref 409, GET shape — all green
• npx tsc --noEmit — no new errors in `src/` (pre-existing `cli/` errors unrelated)
• UI smoke: create empty collection in web UI on a deployed build → appears in CLI picker at next `claude` session start (requires rebuilding the web container; recommended as a deploy step)

Notes

• No auth changes (still disabled per migration 0004)
• No rename support in 0.3.1 (YAGNI — PUT updates description only)
• `deriveCollections()` in `src/lib/derived.ts` preserved for now; `deriveCollectionsFromApi()` added alongside

🤖 Generated with Claude Code