feat: initial commit — crema-app-aifirst-template

Hybrid traditional + AI-first webapp scaffold. Sibling to crema-app-template,
adds the AI assistant surface, command bus, scripts dialog, and virtual
cursor.

What's pre-wired:
- 6 routes: Overview, Resources, Activity, Assistant, Library, Settings
- Collapsible rail + appbar + avatar dropdown shell (template code, not a lib)
- Mobile sheet at <md
- /assistant: streaming chat via @crema/llm-ui, mock fallback, model selector,
  token meter, retry probe, stop-while-streaming, persistent UI Control toggle
- /settings: editable LM Studio endpoint + context window + response cap, with
  test-connection button
- Markdown rendering for assistant replies; ```action``` blocks rendered as a
  small "Ran N actions" pill
- ⌘⇧P script runner dialog + Play icon in the appbar
- Two demo scripts in public/scripts/
- mightypix theme as default, scoped via <AppShell theme="mightypix">

Libs wired in tsconfig + app.css:
- @crema/action-bus (the bus, parser, runner, cursor, provider, ws, llm-bridge)
- @crema/llm-ui, @crema/chat-ui, @crema/aifirst-ui, @crema/notification-ui
- lib-theme-mightypix

Docs:
- README.md — pitch + quick start + structure
- docs/AI_FIRST.md — full system tour (data-action contract, bus, DSL, scripts,
  cursor, LLM integration)
- app/components/layout/THEME_CONTRACT.md — every CSS variable a theme must declare
- CLAUDE.md — orientation for an LLM working in the repo

Genericized from comfy-cloud (the original prototype):
- Brand defaults to "App" / Sparkles icon (override via app/lib/identity.ts)
- User defaults to a stub (swap useUser() for real auth)
- localStorage namespace is "crema.*" (was "comfy.*")

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

app/components/README.md

@@ -0,0 +1,31 @@
+# components/
+
+Component layers in this project.
+
+```
+ui/          shadcn primitives — token-driven, reskinnable per design system
+forms/       composed form widgets
+data/        data display (tables, filters, empty states)
+layout/      app shell, page chrome, navigation wrappers
+marketing/   landing and marketing blocks
+[system]/    design-system-specific components (e.g. m3/, apple/)
+```
+
+## The one rule
+
+**Custom components import *from* `ui/`, never the reverse.**
+
+`ui/` is the primitive layer. It must stay reskinnable by swapping tokens in
+`app/themes/*.css` alone. If a component can't be expressed that way (M3
+ripple, Apple segmented control, etc.), it belongs in a system-specific
+folder — not `ui/` and not the shared folders above.
+
+## Tokens, not values
+
+Every custom component should reference semantic tokens:
+
+- Colors: `bg-primary`, `text-muted-foreground`, `border-border`
+- Radius: `rounded-md`, `rounded-lg`
+- Fonts: `font-sans`, `font-heading`
+
+Hardcoded hex, oklch, or px values are a bug — they break theming.