interlaced 2.0.0a3__tar.gz → 2.0.2__tar.gz

interlaced-2.0.2/MANIFEST.in

@@ -0,0 +1,2 @@
+prune tests
+prune tasks

{interlaced-2.0.0a3 → interlaced-2.0.2}/PKG-INFO

@@ -1,11 +1,11 @@
 Metadata-Version: 2.4
 Name: interlaced
-Version: 2.0.0a3
+Version: 2.0.2
 Summary: Python/SQL-first data platform: transformation, built-in orchestration, and durable streaming ingestion
 Author-email: Mark <mark@interlace.sh>
 License-Expression: MIT
 Keywords: data,pipeline,orchestration,transformation,etl,streaming,dbt,sqlmesh,duckdb
-Classifier: Development Status :: 3 - Alpha
+Classifier: Development Status :: 5 - Production/Stable
 Classifier: Intended Audience :: Developers
 Classifier: Topic :: Software Development :: Build Tools
 Classifier: Programming Language :: Python :: 3.12
@@ -13,27 +13,31 @@ Classifier: Programming Language :: SQL
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: sqlglot<31.0,>=25.0
+Requires-Dist: sqlglot<29.0,>=25.0
 Requires-Dist: duckdb>=1.5.3
 Requires-Dist: pyarrow>=17.0
-Requires-Dist: msgspec<1.0,>=0.18
 Requires-Dist: pydantic<3.0,>=2.5
 Requires-Dist: typer<1.0,>=0.12
 Requires-Dist: rich<15.0,>=13.0
 Requires-Dist: cronsim<3.0,>=2.5
 Requires-Dist: tenacity<10.0,>=8.2
-Requires-Dist: structlog<26.0,>=24.0
 Requires-Dist: pyyaml<7.0,>=6.0
 Provides-Extra: service
 Requires-Dist: litestar<3.0,>=2.12; extra == "service"
 Requires-Dist: uvicorn<1.0,>=0.30; extra == "service"
-Requires-Dist: httpx<1.0,>=0.27; extra == "service"
-Requires-Dist: argon2-cffi<26.0,>=23.1; extra == "service"
-Requires-Dist: joserfc<2.0,>=1.0; extra == "service"
-Requires-Dist: watchfiles<2.0,>=0.22; extra == "service"
+Requires-Dist: msgspec<1.0,>=0.18; extra == "service"
 Provides-Extra: adbc
 Requires-Dist: adbc-driver-manager<2.0,>=1.2; extra == "adbc"
 Requires-Dist: adbc-driver-postgresql<2.0,>=1.2; extra == "adbc"
+Provides-Extra: adbc-snowflake
+Requires-Dist: interlaced[adbc]; extra == "adbc-snowflake"
+Requires-Dist: adbc-driver-snowflake<2.0,>=1.2; extra == "adbc-snowflake"
+Provides-Extra: adbc-bigquery
+Requires-Dist: interlaced[adbc]; extra == "adbc-bigquery"
+Requires-Dist: adbc-driver-bigquery<2.0,>=1.2; extra == "adbc-bigquery"
+Provides-Extra: spark
+Requires-Dist: pyspark<4.1,>=4.0; extra == "spark"
+Requires-Dist: delta-spark<4.1,>=4.0; extra == "spark"
 Provides-Extra: postgres
 Requires-Dist: psycopg[binary]<4.0,>=3.1; extra == "postgres"
 Provides-Extra: polars
@@ -44,6 +48,7 @@ Provides-Extra: all
 Requires-Dist: interlaced[adbc,polars,postgres,service]; extra == "all"
 Provides-Extra: dev
 Requires-Dist: pytest<10.0,>=8.0; extra == "dev"
+Requires-Dist: httpx<1.0,>=0.27; extra == "dev"
 Requires-Dist: pytest-asyncio<2.0,>=1.0; extra == "dev"
 Requires-Dist: ruff<1.0,>=0.6; extra == "dev"
 Requires-Dist: black<27.0,>=24.0; extra == "dev"
@@ -60,11 +65,12 @@ Models are `.sql` files or Python functions; state is versioned snapshots with v
 environments and a terraform-style plan/apply; everything runs in a single daemon on
 DuckDB + DuckLake by default.
 
-> **Status: v2 pre-release.** This branch is a ground-up rebuild (the `interlace` package on
-> PyPI is the older 0.x line). APIs may still move. Requires Python 3.12+.
+> **Status: 1.0.** Requires Python 3.12+.
+> The package is published to PyPI as **`interlaced`**; the import name and CLI are `interlace`.
 
 ```bash
-uv pip install "interlaced[service]"  # or from source: "interlaced[service] @ git+https://github.com/interlace-sh/interlace@v2"
+pip install 'interlaced[service]'   # the CLI + daemon; core CLI only: pip install interlaced
+# more extras: [adbc] postgres/redshift · [spark] · [polars] · [all]
 ```
 
 ## Sixty seconds
@@ -73,7 +79,7 @@ uv pip install "interlaced[service]"  # or from source: "interlaced[service] @ g
 interlace init my-project && cd my-project
 interlace plan            # terraform-style preview: added / breaking / non-breaking / reuse
 interlace apply           # build changed models, run checks, promote the environment
-interlace serve           # the daemon: HTTP API + scheduler + stream ingestion, one process
+interlace serve           # the daemon: web UI (/ui) + HTTP API + scheduler + streams, one process
 ```
 
 Every model builds into a fingerprinted physical table (`interlace__main.orders__a1b2c3`);
@@ -89,7 +95,7 @@ prod; pass `--env dev` while developing.
 
 ```sql
 /* interlace:
-  strategy: scd_type_2
+  strategy: scd
   key: customer_id
   schedule: {cron: "0 * * * *"}
   checks:
@@ -105,7 +111,7 @@ SELECT customer_id, name, tier FROM raw_customers
 ```python
 from interlace import model
 
-@model(strategy="merge_by_key", key="order_id", cursor="updated_at")
+@model(strategy="merge", key="order_id", cursor="updated_at")
 def orders(cursor, this):
     """Incremental API extract: `cursor` is max(updated_at) already in the
     warehouse (None on first run); `this` is the previous materialisation."""
@@ -113,9 +119,9 @@ def orders(cursor, this):
     return pyarrow.Table.from_pylist(rows)     # or RecordBatchReader / generator of batches
 ```
 
-**Strategies:** `full`, `view`, `ephemeral` (CTE-inlined), `merge_by_key` (upsert),
+**Strategies:** `replace`, `view`, `ephemeral` (CTE-inlined), `merge` (upsert),
 `full_merge` (full-state source applied as a minimal diff), `incremental_by_time`
-(windowed, interval-ledger backfill/catchup), `scd_type_2` (history with validity windows).
+(windowed, interval-ledger backfill/catchup), `scd` (history with validity windows).
 
 ## Plan / apply
 
@@ -126,22 +132,31 @@ $ interlace plan
  order_stats   modified  non_breaking  reuse      <- output provably identical: not rebuilt
 ```
 
-- Changes classify **breaking / non-breaking / forward-only**; downstream models whose output
-  is provably identical **reuse their existing tables** instead of rebuilding (an improvement
-  over model-granular invalidation).
+- Changes classify **breaking / non-breaking / forward-only**; a plan with breaking changes
+  refuses to apply without `--force`. Downstream models whose output is provably identical
+  (column-pruned impact analysis) **reuse their existing tables** instead of rebuilding — an
+  improvement over model-granular invalidation.
 - `apply --forward-only` lets history-keeping models (scd2/merge/incremental) survive a
-  definition change: the new logic inherits the existing table and applies going forward.
+  definition change: the existing table is copied to the new version, the new logic applies to
+  the copy going forward, and checks gate before views move.
 - **Checks gate promotion**: 10 built-in types (not_null, unique, accepted_values, row_count,
   freshness, expression, relationships, pattern, range, sql) plus `@check` Python functions —
-  an error-severity failure blocks before the environment view moves.
-- `interlace gc` removes snapshots no environment references (reference-aware: tables shared
-  through reuse survive).
+  an error-severity failure blocks before the environment view moves. `interlace checks run`
+  re-runs them ad hoc against any environment's promoted tables.
+- **`--select state:modified`** scopes a plan/apply to models whose fingerprint drifted from the
+  target environment, plus everything downstream — the CI diff, one flag. **`interlace impact
+  model.column`** shows the column-level blast radius of a change.
+- **`interlace env rollback`** repoints an environment's views at any earlier promotion — nothing
+  rebuilds, the views move; every apply records a generation, so a bad deploy reverts in one
+  command. `interlace gc` removes snapshots no environment references (reference-aware: tables
+  shared through reuse survive).
 
 ## Streaming
 
-Declare a stream; POST to it; rows are durable before the 200, deduplicated by idempotency
-key, and materialized exactly-once into `streams.<name>` — where SQL models just read them.
-A flush triggers the models that consume the stream.
+Declare a stream; POST to it; rows are durable (SQLite WAL log) before the 200, deduplicated by
+idempotency key, and materialized exactly-once into `streams.<name>` — a micro-batch flusher
+commits the data and the watermark in one warehouse transaction, and SQL models just read the
+table. A flush triggers the models that consume the stream.
 
 ```python
 from interlace import stream
@@ -156,7 +171,8 @@ curl -X POST localhost:8000/streams/orders -d '{"order_id": "o1", "total": 49.5}
 ```
 
 Schema drift is yours to choose: `reject` (400), `evolve` (new columns appear), or
-`quarantine` (bad events divert to `<stream>__quarantine`).
+`quarantine` (bad events divert to `<stream>__quarantine`). When the warehouse falls behind,
+publishes get **429 backpressure** instead of unbounded backlog.
 
 ## Reverse ETL
 
@@ -170,18 +186,49 @@ attach:
 ```
 
 ```sql
-/* interlace: {export: {to: table, target: crm.public.accounts, mode: merge_by_key, key: id}} */
+/* interlace: {export: {to: table, target: crm.public.accounts, mode: merge, key: id}} */
 SELECT id, tier, lifetime_value FROM account_summary
 ```
 
-File exports (`to: parquet|csv|json`) work the same way.
+File exports (`to: parquet|csv|json`) work the same way. Sinks are **environment-gated**: by
+default the side effect fires only from prod — a dev apply never writes to a live external
+table (opt in with `environments: [dev, prod]`).
+
+## Multi-engine
+
+Models run on **named engines**: DuckDB/DuckLake by default, Postgres natively over ADBC
+(`pip install 'interlaced[adbc]'`), Spark (beta, `[spark]` extra), plus alpha adapters for
+MotherDuck, Redshift, Snowflake and BigQuery (wired and dialect-correct, not yet run against a
+live account), with per-model pinning:
+
+```yaml
+engines:
+  pg: {type: postgres, database: "${PG_DSN}"}
+```
+
+```sql
+/* interlace: {engine: pg, strategy: merge, key: id} */
+```
+
+Strategies execute *inside* the pinned engine (no DuckDB middleman); cross-engine dependencies
+appear as explicit **transfer** lines in the plan and move as Arrow (or a federated `ATTACH`
+fast lane when possible). Contract: `docs/architecture/MULTI_ENGINE.md`.
 
 ## The daemon
 
-`interlace serve` runs the HTTP API (Litestar + msgspec, OpenAPI at `/schema/scalar`), the
-scheduler (cron/interval triggers → durable run queue), stream ingestion, and retention in one
-process. Scoped API keys (`interlace apikey create ci --scope read`) lock it down; a durable
-event log backs `GET /events/stream` (SSE with replay).
+`interlace serve` runs everything in one process:
+
+- the **web UI** at `/ui` (in-package, zero build step) — ten views: overview, lineage canvas
+  with column-level tracing, models, plan/apply with SQL diffs, live runs, query console,
+  streams, checks, environments, and system — live over SSE;
+- the **HTTP API** (Litestar + msgspec, OpenAPI at `/schema/scalar`) with the same surface as
+  the CLI: plan/apply, runs, checks, streams, engines, schedules, lineage, query, gc;
+- the **scheduler**: cron/interval triggers enqueue onto a **durable run queue** (leases,
+  retries, cooperative cancellation — `interlace cancel <id>` or `POST /runs/{id}/cancel`);
+- **stream ingestion** and retention.
+
+Scoped API keys (`interlace apikey create ci --scope read`) lock it down; a durable event log
+backs `GET /events/stream` (SSE with `Last-Event-ID` replay).
 
 Add `--quack quack:localhost:4213` to serve the warehouse itself over DuckDB's quack protocol —
 other processes (CLI runs, ad-hoc DuckDB clients) then share it concurrently by setting
@@ -198,7 +245,7 @@ other processes (CLI runs, ad-hoc DuckDB clients) then share it concurrently by
   warehouse transaction — exactly-once without distributed coordination.
 - No Jinja, no pandas in core, no external orchestrator.
 
-The full design rationale lives in `docs/architecture/v2-design.md`.
+The full design rationale lives in `docs/architecture/architecture.md`.
 
 ## Development
 
@@ -208,9 +255,9 @@ Toolchain is pinned with [proto](https://moonrepo.dev/proto), tasks run via
 ```bash
 proto install
 moon run interlace:sync      # install deps
-moon run interlace:test      # 240+ tests
+moon run interlace:test      # 350+ tests
 moon run interlace:check     # black + ruff (CI equivalent)
-moon run interlace:typecheck # mypy --strict
+moon run interlace:typecheck # mypy
 ```
 
 MIT licensed.

{interlaced-2.0.0a3 → interlaced-2.0.2}/README.md

@@ -8,11 +8,12 @@ Models are `.sql` files or Python functions; state is versioned snapshots with v
 environments and a terraform-style plan/apply; everything runs in a single daemon on
 DuckDB + DuckLake by default.
 
-> **Status: v2 pre-release.** This branch is a ground-up rebuild (the `interlace` package on
-> PyPI is the older 0.x line). APIs may still move. Requires Python 3.12+.
+> **Status: 1.0.** Requires Python 3.12+.
+> The package is published to PyPI as **`interlaced`**; the import name and CLI are `interlace`.
 
 ```bash
-uv pip install "interlaced[service]"  # or from source: "interlaced[service] @ git+https://github.com/interlace-sh/interlace@v2"
+pip install 'interlaced[service]'   # the CLI + daemon; core CLI only: pip install interlaced
+# more extras: [adbc] postgres/redshift · [spark] · [polars] · [all]
 ```
 
 ## Sixty seconds
@@ -21,7 +22,7 @@ uv pip install "interlaced[service]"  # or from source: "interlaced[service] @ g
 interlace init my-project && cd my-project
 interlace plan            # terraform-style preview: added / breaking / non-breaking / reuse
 interlace apply           # build changed models, run checks, promote the environment
-interlace serve           # the daemon: HTTP API + scheduler + stream ingestion, one process
+interlace serve           # the daemon: web UI (/ui) + HTTP API + scheduler + streams, one process
 ```
 
 Every model builds into a fingerprinted physical table (`interlace__main.orders__a1b2c3`);
@@ -37,7 +38,7 @@ prod; pass `--env dev` while developing.
 
 ```sql
 /* interlace:
-  strategy: scd_type_2
+  strategy: scd
   key: customer_id
   schedule: {cron: "0 * * * *"}
   checks:
@@ -53,7 +54,7 @@ SELECT customer_id, name, tier FROM raw_customers
 ```python
 from interlace import model
 
-@model(strategy="merge_by_key", key="order_id", cursor="updated_at")
+@model(strategy="merge", key="order_id", cursor="updated_at")
 def orders(cursor, this):
     """Incremental API extract: `cursor` is max(updated_at) already in the
     warehouse (None on first run); `this` is the previous materialisation."""
@@ -61,9 +62,9 @@ def orders(cursor, this):
     return pyarrow.Table.from_pylist(rows)     # or RecordBatchReader / generator of batches
 ```
 
-**Strategies:** `full`, `view`, `ephemeral` (CTE-inlined), `merge_by_key` (upsert),
+**Strategies:** `replace`, `view`, `ephemeral` (CTE-inlined), `merge` (upsert),
 `full_merge` (full-state source applied as a minimal diff), `incremental_by_time`
-(windowed, interval-ledger backfill/catchup), `scd_type_2` (history with validity windows).
+(windowed, interval-ledger backfill/catchup), `scd` (history with validity windows).
 
 ## Plan / apply
 
@@ -74,22 +75,31 @@ $ interlace plan
  order_stats   modified  non_breaking  reuse      <- output provably identical: not rebuilt
 ```
 
-- Changes classify **breaking / non-breaking / forward-only**; downstream models whose output
-  is provably identical **reuse their existing tables** instead of rebuilding (an improvement
-  over model-granular invalidation).
+- Changes classify **breaking / non-breaking / forward-only**; a plan with breaking changes
+  refuses to apply without `--force`. Downstream models whose output is provably identical
+  (column-pruned impact analysis) **reuse their existing tables** instead of rebuilding — an
+  improvement over model-granular invalidation.
 - `apply --forward-only` lets history-keeping models (scd2/merge/incremental) survive a
-  definition change: the new logic inherits the existing table and applies going forward.
+  definition change: the existing table is copied to the new version, the new logic applies to
+  the copy going forward, and checks gate before views move.
 - **Checks gate promotion**: 10 built-in types (not_null, unique, accepted_values, row_count,
   freshness, expression, relationships, pattern, range, sql) plus `@check` Python functions —
-  an error-severity failure blocks before the environment view moves.
-- `interlace gc` removes snapshots no environment references (reference-aware: tables shared
-  through reuse survive).
+  an error-severity failure blocks before the environment view moves. `interlace checks run`
+  re-runs them ad hoc against any environment's promoted tables.
+- **`--select state:modified`** scopes a plan/apply to models whose fingerprint drifted from the
+  target environment, plus everything downstream — the CI diff, one flag. **`interlace impact
+  model.column`** shows the column-level blast radius of a change.
+- **`interlace env rollback`** repoints an environment's views at any earlier promotion — nothing
+  rebuilds, the views move; every apply records a generation, so a bad deploy reverts in one
+  command. `interlace gc` removes snapshots no environment references (reference-aware: tables
+  shared through reuse survive).
 
 ## Streaming
 
-Declare a stream; POST to it; rows are durable before the 200, deduplicated by idempotency
-key, and materialized exactly-once into `streams.<name>` — where SQL models just read them.
-A flush triggers the models that consume the stream.
+Declare a stream; POST to it; rows are durable (SQLite WAL log) before the 200, deduplicated by
+idempotency key, and materialized exactly-once into `streams.<name>` — a micro-batch flusher
+commits the data and the watermark in one warehouse transaction, and SQL models just read the
+table. A flush triggers the models that consume the stream.
 
 ```python
 from interlace import stream
@@ -104,7 +114,8 @@ curl -X POST localhost:8000/streams/orders -d '{"order_id": "o1", "total": 49.5}
 ```
 
 Schema drift is yours to choose: `reject` (400), `evolve` (new columns appear), or
-`quarantine` (bad events divert to `<stream>__quarantine`).
+`quarantine` (bad events divert to `<stream>__quarantine`). When the warehouse falls behind,
+publishes get **429 backpressure** instead of unbounded backlog.
 
 ## Reverse ETL
 
@@ -118,18 +129,49 @@ attach:
 ```
 
 ```sql
-/* interlace: {export: {to: table, target: crm.public.accounts, mode: merge_by_key, key: id}} */
+/* interlace: {export: {to: table, target: crm.public.accounts, mode: merge, key: id}} */
 SELECT id, tier, lifetime_value FROM account_summary
 ```
 
-File exports (`to: parquet|csv|json`) work the same way.
+File exports (`to: parquet|csv|json`) work the same way. Sinks are **environment-gated**: by
+default the side effect fires only from prod — a dev apply never writes to a live external
+table (opt in with `environments: [dev, prod]`).
+
+## Multi-engine
+
+Models run on **named engines**: DuckDB/DuckLake by default, Postgres natively over ADBC
+(`pip install 'interlaced[adbc]'`), Spark (beta, `[spark]` extra), plus alpha adapters for
+MotherDuck, Redshift, Snowflake and BigQuery (wired and dialect-correct, not yet run against a
+live account), with per-model pinning:
+
+```yaml
+engines:
+  pg: {type: postgres, database: "${PG_DSN}"}
+```
+
+```sql
+/* interlace: {engine: pg, strategy: merge, key: id} */
+```
+
+Strategies execute *inside* the pinned engine (no DuckDB middleman); cross-engine dependencies
+appear as explicit **transfer** lines in the plan and move as Arrow (or a federated `ATTACH`
+fast lane when possible). Contract: `docs/architecture/MULTI_ENGINE.md`.
 
 ## The daemon
 
-`interlace serve` runs the HTTP API (Litestar + msgspec, OpenAPI at `/schema/scalar`), the
-scheduler (cron/interval triggers → durable run queue), stream ingestion, and retention in one
-process. Scoped API keys (`interlace apikey create ci --scope read`) lock it down; a durable
-event log backs `GET /events/stream` (SSE with replay).
+`interlace serve` runs everything in one process:
+
+- the **web UI** at `/ui` (in-package, zero build step) — ten views: overview, lineage canvas
+  with column-level tracing, models, plan/apply with SQL diffs, live runs, query console,
+  streams, checks, environments, and system — live over SSE;
+- the **HTTP API** (Litestar + msgspec, OpenAPI at `/schema/scalar`) with the same surface as
+  the CLI: plan/apply, runs, checks, streams, engines, schedules, lineage, query, gc;
+- the **scheduler**: cron/interval triggers enqueue onto a **durable run queue** (leases,
+  retries, cooperative cancellation — `interlace cancel <id>` or `POST /runs/{id}/cancel`);
+- **stream ingestion** and retention.
+
+Scoped API keys (`interlace apikey create ci --scope read`) lock it down; a durable event log
+backs `GET /events/stream` (SSE with `Last-Event-ID` replay).
 
 Add `--quack quack:localhost:4213` to serve the warehouse itself over DuckDB's quack protocol —
 other processes (CLI runs, ad-hoc DuckDB clients) then share it concurrently by setting
@@ -146,7 +188,7 @@ other processes (CLI runs, ad-hoc DuckDB clients) then share it concurrently by
   warehouse transaction — exactly-once without distributed coordination.
 - No Jinja, no pandas in core, no external orchestrator.
 
-The full design rationale lives in `docs/architecture/v2-design.md`.
+The full design rationale lives in `docs/architecture/architecture.md`.
 
 ## Development
 
@@ -156,9 +198,9 @@ Toolchain is pinned with [proto](https://moonrepo.dev/proto), tasks run via
 ```bash
 proto install
 moon run interlace:sync      # install deps
-moon run interlace:test      # 240+ tests
+moon run interlace:test      # 350+ tests
 moon run interlace:check     # black + ruff (CI equivalent)
-moon run interlace:typecheck # mypy --strict
+moon run interlace:typecheck # mypy
 ```
 
 MIT licensed.

{interlaced-2.0.0a3 → interlaced-2.0.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "interlaced"
-version = "2.0.0a3"
+version = "2.0.2"
 description = "Python/SQL-first data platform: transformation, built-in orchestration, and durable streaming ingestion"
 readme = "README.md"
 requires-python = ">=3.12"
@@ -14,7 +14,7 @@ authors = [
 ]
 keywords = ["data", "pipeline", "orchestration", "transformation", "etl", "streaming", "dbt", "sqlmesh", "duckdb"]
 classifiers = [
-    "Development Status :: 3 - Alpha",
+    "Development Status :: 5 - Production/Stable",
     "Intended Audience :: Developers",
     "Topic :: Software Development :: Build Tools",
     "Programming Language :: Python :: 3.12",
@@ -22,18 +22,16 @@ classifiers = [
 ]
 
 # Core: the IR + engine + state + plan spine (Phase 1). Everything is Arrow- and
-# sqlglot-native. See docs/architecture/v2-design.md.
+# sqlglot-native. See docs/architecture/architecture.md.
 dependencies = [
-    "sqlglot>=25.0,<31.0",        # canonical IR, transpilation, semantic diff, column lineage
+    "sqlglot>=25.0,<29.0",        # canonical IR, transpilation, semantic diff, column lineage
     "duckdb>=1.5.3",              # default engine + federation hub; DuckLake storage + quack serving
     "pyarrow>=17.0",              # the wire format: RecordBatchReader everywhere
-    "msgspec>=0.18,<1.0",         # ingest validation + fast (de)serialisation
     "pydantic>=2.5,<3.0",         # config + manifest validation (cold paths only)
     "typer>=0.12,<1.0",           # CLI
     "rich>=13.0,<15.0",           # display, strictly an event subscriber
     "cronsim>=2.5,<3.0",          # cron parsing for the trigger engine
     "tenacity>=8.2,<10.0",        # retries (tasks, DuckLake commit conflicts, transfers)
-    "structlog>=24.0,<26.0",      # structured logging
     "pyyaml>=6.0,<7.0",           # project config (config + env overlays)
 ]
 
@@ -45,22 +43,26 @@ interlace = "interlace.cli.main:main"
 service = [
     "litestar>=2.12,<3.0",
     "uvicorn>=0.30,<1.0",
-    "httpx>=0.27,<1.0",
-    "argon2-cffi>=23.1,<26.0",
-    "joserfc>=1.0,<2.0",
-    "watchfiles>=0.22,<2.0",
+    "msgspec>=0.18,<1.0",  # the wire types (litestar serialises msgspec structs natively)
 ]
-# Remote engines via Arrow-native transfer (Phase 4).
+# Remote engines via Arrow-native ADBC transfer. postgres (+ redshift, same wire)
+# are the tested transport; snowflake/bigquery are ALPHA (wired, not run live).
 adbc = [
     "adbc-driver-manager>=1.2,<2.0",
     "adbc-driver-postgresql>=1.2,<2.0",
 ]
+adbc-snowflake = ["interlaced[adbc]", "adbc-driver-snowflake>=1.2,<2.0"]
+adbc-bigquery = ["interlaced[adbc]", "adbc-driver-bigquery>=1.2,<2.0"]
+# Spark engine: PySpark session transport (Arrow-native), Delta for mutating strategies.
+# Pinned to the Spark 4.0 / Delta 4.0 pair (Delta lags the latest Spark minor).
+spark = ["pyspark>=4.0,<4.1", "delta-spark>=4.0,<4.1"]
 postgres = ["psycopg[binary]>=3.1,<4.0"]
 polars = ["polars>=1.0,<2.0"]
 pandas = ["pandas>=2.0,<4.0"]
 all = ["interlaced[service,adbc,postgres,polars]"]
 dev = [
     "pytest>=8.0,<10.0",
+    "httpx>=0.27,<1.0",  # litestar's TestClient transport
     "pytest-asyncio>=1.0,<2.0",
     "ruff>=0.6,<1.0",
     "black>=24.0,<27.0",
@@ -71,7 +73,7 @@ dev = [
 where = ["src"]
 
 [tool.setuptools.package-data]
-interlace = ["py.typed"]
+interlace = ["py.typed", "service/ui/*", "service/ui/**/*"]
 
 [tool.black]
 line-length = 120
@@ -116,6 +118,10 @@ module = [
     "sqlglot.*",
     "pyarrow.*",
     "yaml",
+    "adbc_driver_snowflake.*",  # optional 'adbc-snowflake' extra — absent in the base env
+    "adbc_driver_bigquery.*",  # optional 'adbc-bigquery' extra — absent in the base env
+    "pyspark.*",  # optional 'spark' extra — absent in the base env
+    "delta.*",  # optional 'spark' extra (delta-spark) — absent in the base env
 ]
 ignore_missing_imports = true
 

interlaced-2.0.2/src/interlace/__init__.py

@@ -0,0 +1,26 @@
+"""Interlace — Python/SQL-first data platform.
+
+Transformation (sqlmesh-grade snapshots, virtual environments, plan/apply),
+built-in orchestration (durable work queue + unified triggers), and durable
+streaming ingestion — in one process. See docs/architecture/architecture.md.
+
+The public surface is the ``@model`` / ``@stream`` / ``@check`` decorators.
+"""
+
+from __future__ import annotations
+
+from importlib.metadata import PackageNotFoundError, version
+
+from interlace.dsl.decorators import check, model, stream
+
+try:
+    __version__ = version("interlaced")
+except PackageNotFoundError:  # running from a source tree without an install
+    __version__ = "0+unknown"
+
+__all__ = [
+    "__version__",
+    "check",
+    "model",
+    "stream",
+]