Add TUI, Bridge Types, matchers, and Avro/gRPC integration

Interactive TUI (draft):
- tui-react: React-like abstraction with EventRegistry, StateStore, RenderContext
- Screens: Splash, MainMenu, SchemaBrowser, SpecBrowser, Source/Output/Type editors
- Domain Type Builder: 6-step wizard for cross-database composite types
- Form components with mouse support, hover states, click handlers
- Sliding navigation with animations

Bridge Types:
- Domain types unifying data models across multiple database sources
- Primary source with aligned sources for cross-database compatibility
- Code generation for Scala, Java, and Kotlin
- CLI `typr check` command for validation

Matchers (renamed from selectors):
- Negation support with exclude patterns
- Split model (schema properties) vs api (parameters) matchers
- JSON Schema for typr.yaml with IDE validation

Avro/gRPC Integration:
- Wire codegen into `typr generate` command
- Boundaries system (renamed from sources)
- Cats/fs2-kafka framework with IO-based publishers/listeners
- Effect types at output level with computed types

Other:
- Bump tui-scala to 0.0.8
- Regenerate all testers

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: oyvindberg

.gitignore

@@ -24,4 +24,5 @@ __pycache__/
 db/duckdb/test.db
 db/duckdb/test.db.wal
 duckdb-test/
-.snapshot-test.lock
+.snapshot-test.lock
+typr.sh

CLAUDE.md

@@ -38,22 +38,26 @@ bleep fmt
 # Regenerate tuples, rowparsers and so on. runs bleep sourcegen scripts
 bleep sourcegen
 
-# Code generation scripts
-bleep generate-postgres          # PostgreSQL AdventureWorks + Showcase schemas
-bleep generate-mariadb           # MariaDB test + Showcase schemas
-bleep generate-duckdb            # DuckDB test + Showcase schemas
-bleep generate-oracle            # Oracle test + Showcase schemas
-bleep generate-sqlserver         # SQL Server test + Showcase schemas
-bleep generate-openapi-test      # OpenAPI code generation
-bleep generate-sources           # Typr's internal generated code
-
-# Run all generators in parallel. much faster
-bleep generate-all               
+# Typr's internal generated code
+bleep generate-sources
 
 # Documentation
 bleep generate-docs              # Generate documentation with mdoc
 ```
 
+### Typr CLI for Code Generation
+Database code generation is done via the **typr CLI** instead of bleep scripts:
+
+```bash
+# Generate code (reads typr.yaml config)
+bleep run typr generate <outputs>
+```
+
+The CLI reads configuration from `typr.yaml` and generates type-safe code for:
+- Tables, views, and custom SQL queries
+- Type overrides (scalar types, composite types)
+- Selected schemas and tables
+
 ### Gradle for Kotlin
 Kotlin modules have Gradle build files for IDE support and alternative building:
 ```bash
@@ -115,16 +119,16 @@ testers/pg/scala/anorm/
 
 ### Generation Variants
 
-The `GeneratedPostgres.scala` script generates multiple variants:
-- Scala 2.13 + Anorm + PlayJson
-- Scala 3 + Anorm + PlayJson
-- Scala 2.13 + Doobie + Circe
-- Scala 3 + Doobie + Circe
-- Scala 2.13 + ZIO-JDBC + ZioJson
-- Scala 3 + ZIO-JDBC + ZioJson
-- Java + Typo DSL + Jackson
-- Scala 3 with Java types + Typo DSL + Jackson
-- Scala 3 with Scala types + Typo DSL + Jackson
+The typr CLI supports generating code for multiple combinations:
+- Scala 2.13 + Anorm + PlayJson (PostgreSQL only)
+- Scala 3 + Anorm + PlayJson (PostgreSQL only)
+- Scala 2.13 + Doobie + Circe (PostgreSQL only)
+- Scala 3 + Doobie + Circe (PostgreSQL only)
+- Scala 2.13 + ZIO-JDBC + ZioJson (PostgreSQL only)
+- Scala 3 + ZIO-JDBC + ZioJson (PostgreSQL only)
+- Java + Typo DSL + Jackson (all databases)
+- Kotlin + Typo DSL + Jackson (all databases)
+- Scala 3 + Typo DSL + Jackson (all databases)
 
 ## Docker-Compose Database Setup
 
@@ -167,7 +171,7 @@ docker-compose down
 docker-compose up -d
 
 # 4. Regenerate code
-bleep generate-postgres
+bleep run typr generate <outputs>
 ```
 
 **MariaDB schema changes:**
@@ -178,7 +182,7 @@ docker-compose down
 docker-compose up -d
 
 # 3. Regenerate code
-bleep generate-mariadb
+bleep run typr generate <outputs>
 ```
 
 **Oracle schema changes:**
@@ -193,15 +197,15 @@ docker-compose up -d
 docker-compose logs -f oracle
 
 # 4. Regenerate code
-bleep generate-oracle
+bleep run typr generate <outputs>
 ```
 
 **Complete reset (all databases):**
 ```bash
 docker-compose down -v    # -v removes volumes
 docker-compose up -d
-# Wait for all databases to initialize
-bleep generate-all
+# Wait for all databases to initialize, then regenerate
+bleep run typr generate <outputs>
 ```
 
 ### Persistent Volumes
@@ -333,14 +337,10 @@ typr-dsl-anorm/                    # [LEGACY] Anorm-specific DSL (Scala, Postgre
 typr-dsl-doobie/                   # [LEGACY] Doobie-specific DSL (Scala, PostgreSQL only)
 typr-dsl-zio-jdbc/                 # [LEGACY] ZIO-JDBC-specific DSL (Scala, PostgreSQL only)
 
-typr-scripts/                      # Generation scripts
-├── GeneratedPostgres.scala        # PostgreSQL generation
-├── GeneratedMariaDb.scala         # MariaDB generation
-├── GeneratedDuckDb.scala          # DuckDB generation
-├── GeneratedOracle.scala          # Oracle generation
-├── GeneratedSqlServer.scala       # SQL Server generation
-├── GenerateOpenApiTest.scala      # OpenAPI generation
-├── GenerateAll.scala              # Run all generators
+typr-scripts/                      # Build and publishing scripts
+├── GeneratedSources.scala         # Typr's internal generated code
+├── PublishLocal.scala             # Local publishing
+├── Publish.scala                  # Release publishing
 └── ...
 
 sql-init/                          # Schema files (mounted to Docker)
@@ -442,7 +442,7 @@ WHERE p.productcategory = :category_id:myapp.production.productcategory.Productc
 1. **Create Test Case**: Add SQL file in `sql-init/postgres/issueNNN.sql` (or appropriate database folder)
 2. **Update Install Script**: Add to `sql-init/postgres/00-install.sh` for PostgreSQL
 3. **Restart Database**: `docker-compose down && docker-compose up -d`
-4. **Generate Code**: Run appropriate generator (e.g., `bleep generate-postgres`)
+4. **Generate Code**: Run `bleep run typr generate <outputs>`
 5. **Trace Issue**: Examine generated code
 6. **Commit Test Setup**: Commit before making changes
 7. **Implement Fix**: Make code changes
@@ -517,7 +517,7 @@ docker-compose logs -f oracle
 
 ### Code Generation Philosophy
 - Never generate code that relies on derivation - we are the deriver
-- Run appropriate generator (e.g., `bleep generate-postgres`) before testing to see codegen effects
+- Run `bleep run typr generate <outputs>` before testing to see codegen effects
 
 ### Development Rules
 - Always run `bleep fmt` and `bleep test`  before commiting
@@ -533,4 +533,5 @@ docker-compose logs -f oracle
 - WHEN YOU CHANGE CODE, NEVER LEAVE DANGLING COMMENTS DESCRIBING HOW IT WAS BEFORE OR WHY YOU MADE A CHANGE. WE HAVE GIT FOR THAT
 - when restarting a database container always restart only the one you want to restart. it takes ages to start all
 - UNDER NO CIRCUMSTANCE, EVER. FUCKING EVER. WILL CLAUDE GIVE UP AND REVERT ALL THE FILES
-- NEVER HIDE PROBLEMS BY WORKING AROUND THEM. When you discover an issue (e.g., serialization doesn't work, types don't match, framework integration fails), IMMEDIATELY TELL THE USER. Do not quietly work around it with simpler/different code and pretend everything is fine. Tests exist to find these problems - report them, don't hide them.
+- NEVER HIDE PROBLEMS BY WORKING AROUND THEM. When you discover an issue (e.g., serialization doesn't work, types don't match, framework integration fails), IMMEDIATELY TELL THE USER. Do not quietly work around it with simpler/different code and pretend everything is fine. Tests exist to find these problems - report them, don't hide them.
+- **DO NOT COMPARE WITH "PRE-EXISTING" STATE.** When there are compilation errors or test failures, FIX THEM. Do not check if they existed before your changes, do not stash and compare with HEAD, do not say "these are pre-existing errors". The branch has many commits and may have just been rebased - "pre-existing" is meaningless. If it doesn't compile, fix it.