datalex-cli 1.1.1__tar.gz → 1.3.0__tar.gz

{datalex_cli-1.1.1 → datalex_cli-1.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: datalex-cli
-Version: 1.1.1
+Version: 1.3.0
 Summary: Git-native data modeling for dbt users
 Author-email: DuckCode AI Labs <hello@duckcode.ai>
 License: MIT
@@ -88,7 +88,7 @@ with contracts, lineage, ERDs, and clean round-trip back to dbt.
 ## Quickstart — two commands
 
 ```bash
-pip install 'datalex-cli[serve]'       # CLI + bundled Node — one command, no prereqs
+pip install -U 'datalex-cli[serve]'    # CLI + bundled Node — one command, no prereqs
 datalex serve                          # opens http://localhost:3030
 ```
 
@@ -110,16 +110,20 @@ original `.yml` files — `git status` shows real diffs.
 **Build your first ER diagram:**
 
 1. Click **Import dbt repo → Local folder** → pick your project root
-2. In the Explorer, right-click any folder → **New diagram here…**
-   (or use the Explorer toolbar's **New Diagram** button for the
-   default `datalex/diagrams/` location)
-3. Open the new `.diagram.yaml` and click **Add Entities** on the
-   canvas toolbar — multi-select with search + domain filter, then
-   confirm. Entities auto-layout via ELK on add. You can also drag
-   any `schema.yml` / `.model.yaml` from the Explorer onto the canvas
-   as an alternative — FK edges from `tests: - relationships:` render
-   automatically.
-4. Drag to reposition → **Save All** → positions persist in the
+2. Click **New modeling asset** and choose Conceptual, Logical, or
+   Physical. New assets use the domain-first structure
+   `DataLex/<domain>/<conceptual|logical|physical>/...`.
+3. Open the new `.diagram.yaml`. Conceptual and logical diagrams can
+   create boxes directly; physical diagrams are dbt-first, so drag any
+   `schema.yml` / `.model.yaml` from the Explorer onto the canvas.
+   Relationship handles on each card create business, logical, or
+   physical relationships for the active layer.
+4. Open **Ask AI** from the right panel, canvas, Explorer, validation
+   row, or selected object when you want the agent to explain the model,
+   reverse-engineer business concepts, or propose YAML changes. AI
+   proposals are approval-gated; use **Review plan** to inspect the full
+   context and proposed YAML before applying.
+5. Drag to reposition → **Save All** → positions persist in the
    diagram file; `git commit` picks them up. Save All is merge-safe:
    multiple in-memory docs targeting the same `schema.yml` are merged
    through the core-engine `merge_models_preserving_docs` helper
@@ -195,11 +199,21 @@ streaming-safe for 10K+ entities), it gives you:
   Databricks, MySQL, SQL Server, Redshift. Same source, all dialects.
 - **`datalex datalex diff`** — semantic diff with explicit rename tracking
   (`previous_name:`), breaking-change gate for CI.
+- **`datalex datalex mesh check <repo> --strict`** — verifies dbt mesh
+  Interface readiness for shared models declared with
+  `meta.datalex.interface`. See [docs/mesh-interfaces.md](docs/mesh-interfaces.md).
 - **Cross-repo package imports** — pin `acme/warehouse-core@1.4.0` in
   `imports:`, lockfile + content hash drift detection, Git-or-path
   resolution, on-disk parse cache for large projects.
 - **Visual studio** — React Flow UI for editing entities, relationships,
   and metadata; same YAML files as the CLI.
+- **Agentic modeling assistant** — local-first AI workflow for explaining
+  selected objects, reverse-engineering dbt repos into conceptual/logical
+  views, proposing focused YAML patches, and applying approved changes
+  through the same guarded save APIs as manual edits. Context comes from
+  structured dbt/DataLex facts, manifest/catalog metadata, BM25 lexical
+  search, validation output, project memory, and team skills under
+  `DataLex/Skills/*.md`; no vector search is used for code/YAML retrieval.
 
 ## Supported warehouses
 
@@ -223,10 +237,10 @@ per-dialect over time).
 **For users** — from [PyPI](https://pypi.org/project/datalex-cli/):
 
 ```bash
-pip install 'datalex-cli[serve]'                 # CLI + UI (recommended)
-pip install 'datalex-cli[serve,postgres]'        # add a warehouse driver
-pip install 'datalex-cli[serve,all]'             # every driver + UI
-pip install datalex-cli                          # CLI-only, no UI
+pip install -U 'datalex-cli[serve]'                 # CLI + UI (recommended)
+pip install -U 'datalex-cli[serve,postgres]'        # add a warehouse driver
+pip install -U 'datalex-cli[serve,all]'             # every driver + UI
+pip install -U datalex-cli                          # CLI-only, no UI
 ```
 
 Available extras: `serve`, `duckdb`, `postgres`, `mysql`, `snowflake`,
@@ -234,6 +248,23 @@ Available extras: `serve`, `duckdb`, `postgres`, `mysql`, `snowflake`,
 
 **Prereqs:** Python 3.9+ and Git. That's it — `[serve]` bundles Node.
 
+Verify the installed package:
+
+```bash
+datalex --version
+```
+
+Configure AI providers in **Settings → AI**. DataLex supports local
+fallback responses plus OpenAI, Anthropic, Gemini, and Ollama-compatible
+endpoints. Provider keys are stored locally in the browser; generated YAML
+is never written until you approve an explicit proposal.
+
+For the local DuckDB-based example repo, install the matching driver too:
+
+```bash
+pip install -U 'datalex-cli[serve,duckdb]'
+```
+
 **For contributors** — from source:
 
 ```bash
@@ -304,6 +335,8 @@ dbt parse
 - **[Pull a warehouse schema](docs/tutorials/warehouse-pull.md)** —
   7-minute live-connection flow with inferred PKs/FKs and streaming
   progress.
+- **[Agentic AI modeling](docs/ai-agentic-modeling.md)** — how Ask AI,
+  skills, memory, search/indexing, proposal review, and auto-refresh work.
 - **[CLI dbt-sync tutorial](docs/tutorial-dbt-sync.md)** — original
   CLI-only jaffle_shop walkthrough.
 

{datalex_cli-1.1.1 → datalex_cli-1.3.0}/README.md

@@ -33,7 +33,7 @@ with contracts, lineage, ERDs, and clean round-trip back to dbt.
 ## Quickstart — two commands
 
 ```bash
-pip install 'datalex-cli[serve]'       # CLI + bundled Node — one command, no prereqs
+pip install -U 'datalex-cli[serve]'    # CLI + bundled Node — one command, no prereqs
 datalex serve                          # opens http://localhost:3030
 ```
 
@@ -55,16 +55,20 @@ original `.yml` files — `git status` shows real diffs.
 **Build your first ER diagram:**
 
 1. Click **Import dbt repo → Local folder** → pick your project root
-2. In the Explorer, right-click any folder → **New diagram here…**
-   (or use the Explorer toolbar's **New Diagram** button for the
-   default `datalex/diagrams/` location)
-3. Open the new `.diagram.yaml` and click **Add Entities** on the
-   canvas toolbar — multi-select with search + domain filter, then
-   confirm. Entities auto-layout via ELK on add. You can also drag
-   any `schema.yml` / `.model.yaml` from the Explorer onto the canvas
-   as an alternative — FK edges from `tests: - relationships:` render
-   automatically.
-4. Drag to reposition → **Save All** → positions persist in the
+2. Click **New modeling asset** and choose Conceptual, Logical, or
+   Physical. New assets use the domain-first structure
+   `DataLex/<domain>/<conceptual|logical|physical>/...`.
+3. Open the new `.diagram.yaml`. Conceptual and logical diagrams can
+   create boxes directly; physical diagrams are dbt-first, so drag any
+   `schema.yml` / `.model.yaml` from the Explorer onto the canvas.
+   Relationship handles on each card create business, logical, or
+   physical relationships for the active layer.
+4. Open **Ask AI** from the right panel, canvas, Explorer, validation
+   row, or selected object when you want the agent to explain the model,
+   reverse-engineer business concepts, or propose YAML changes. AI
+   proposals are approval-gated; use **Review plan** to inspect the full
+   context and proposed YAML before applying.
+5. Drag to reposition → **Save All** → positions persist in the
    diagram file; `git commit` picks them up. Save All is merge-safe:
    multiple in-memory docs targeting the same `schema.yml` are merged
    through the core-engine `merge_models_preserving_docs` helper
@@ -140,11 +144,21 @@ streaming-safe for 10K+ entities), it gives you:
   Databricks, MySQL, SQL Server, Redshift. Same source, all dialects.
 - **`datalex datalex diff`** — semantic diff with explicit rename tracking
   (`previous_name:`), breaking-change gate for CI.
+- **`datalex datalex mesh check <repo> --strict`** — verifies dbt mesh
+  Interface readiness for shared models declared with
+  `meta.datalex.interface`. See [docs/mesh-interfaces.md](docs/mesh-interfaces.md).
 - **Cross-repo package imports** — pin `acme/warehouse-core@1.4.0` in
   `imports:`, lockfile + content hash drift detection, Git-or-path
   resolution, on-disk parse cache for large projects.
 - **Visual studio** — React Flow UI for editing entities, relationships,
   and metadata; same YAML files as the CLI.
+- **Agentic modeling assistant** — local-first AI workflow for explaining
+  selected objects, reverse-engineering dbt repos into conceptual/logical
+  views, proposing focused YAML patches, and applying approved changes
+  through the same guarded save APIs as manual edits. Context comes from
+  structured dbt/DataLex facts, manifest/catalog metadata, BM25 lexical
+  search, validation output, project memory, and team skills under
+  `DataLex/Skills/*.md`; no vector search is used for code/YAML retrieval.
 
 ## Supported warehouses
 
@@ -168,10 +182,10 @@ per-dialect over time).
 **For users** — from [PyPI](https://pypi.org/project/datalex-cli/):
 
 ```bash
-pip install 'datalex-cli[serve]'                 # CLI + UI (recommended)
-pip install 'datalex-cli[serve,postgres]'        # add a warehouse driver
-pip install 'datalex-cli[serve,all]'             # every driver + UI
-pip install datalex-cli                          # CLI-only, no UI
+pip install -U 'datalex-cli[serve]'                 # CLI + UI (recommended)
+pip install -U 'datalex-cli[serve,postgres]'        # add a warehouse driver
+pip install -U 'datalex-cli[serve,all]'             # every driver + UI
+pip install -U datalex-cli                          # CLI-only, no UI
 ```
 
 Available extras: `serve`, `duckdb`, `postgres`, `mysql`, `snowflake`,
@@ -179,6 +193,23 @@ Available extras: `serve`, `duckdb`, `postgres`, `mysql`, `snowflake`,
 
 **Prereqs:** Python 3.9+ and Git. That's it — `[serve]` bundles Node.
 
+Verify the installed package:
+
+```bash
+datalex --version
+```
+
+Configure AI providers in **Settings → AI**. DataLex supports local
+fallback responses plus OpenAI, Anthropic, Gemini, and Ollama-compatible
+endpoints. Provider keys are stored locally in the browser; generated YAML
+is never written until you approve an explicit proposal.
+
+For the local DuckDB-based example repo, install the matching driver too:
+
+```bash
+pip install -U 'datalex-cli[serve,duckdb]'
+```
+
 **For contributors** — from source:
 
 ```bash
@@ -249,6 +280,8 @@ dbt parse
 - **[Pull a warehouse schema](docs/tutorials/warehouse-pull.md)** —
   7-minute live-connection flow with inferred PKs/FKs and streaming
   progress.
+- **[Agentic AI modeling](docs/ai-agentic-modeling.md)** — how Ask AI,
+  skills, memory, search/indexing, proposal review, and auto-refresh work.
 - **[CLI dbt-sync tutorial](docs/tutorial-dbt-sync.md)** — original
   CLI-only jaffle_shop walkthrough.
 

{datalex_cli-1.1.1 → datalex_cli-1.3.0}/datalex_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: datalex-cli
-Version: 1.1.1
+Version: 1.3.0
 Summary: Git-native data modeling for dbt users
 Author-email: DuckCode AI Labs <hello@duckcode.ai>
 License: MIT
@@ -88,7 +88,7 @@ with contracts, lineage, ERDs, and clean round-trip back to dbt.
 ## Quickstart — two commands
 
 ```bash
-pip install 'datalex-cli[serve]'       # CLI + bundled Node — one command, no prereqs
+pip install -U 'datalex-cli[serve]'    # CLI + bundled Node — one command, no prereqs
 datalex serve                          # opens http://localhost:3030
 ```
 
@@ -110,16 +110,20 @@ original `.yml` files — `git status` shows real diffs.
 **Build your first ER diagram:**
 
 1. Click **Import dbt repo → Local folder** → pick your project root
-2. In the Explorer, right-click any folder → **New diagram here…**
-   (or use the Explorer toolbar's **New Diagram** button for the
-   default `datalex/diagrams/` location)
-3. Open the new `.diagram.yaml` and click **Add Entities** on the
-   canvas toolbar — multi-select with search + domain filter, then
-   confirm. Entities auto-layout via ELK on add. You can also drag
-   any `schema.yml` / `.model.yaml` from the Explorer onto the canvas
-   as an alternative — FK edges from `tests: - relationships:` render
-   automatically.
-4. Drag to reposition → **Save All** → positions persist in the
+2. Click **New modeling asset** and choose Conceptual, Logical, or
+   Physical. New assets use the domain-first structure
+   `DataLex/<domain>/<conceptual|logical|physical>/...`.
+3. Open the new `.diagram.yaml`. Conceptual and logical diagrams can
+   create boxes directly; physical diagrams are dbt-first, so drag any
+   `schema.yml` / `.model.yaml` from the Explorer onto the canvas.
+   Relationship handles on each card create business, logical, or
+   physical relationships for the active layer.
+4. Open **Ask AI** from the right panel, canvas, Explorer, validation
+   row, or selected object when you want the agent to explain the model,
+   reverse-engineer business concepts, or propose YAML changes. AI
+   proposals are approval-gated; use **Review plan** to inspect the full
+   context and proposed YAML before applying.
+5. Drag to reposition → **Save All** → positions persist in the
    diagram file; `git commit` picks them up. Save All is merge-safe:
    multiple in-memory docs targeting the same `schema.yml` are merged
    through the core-engine `merge_models_preserving_docs` helper
@@ -195,11 +199,21 @@ streaming-safe for 10K+ entities), it gives you:
   Databricks, MySQL, SQL Server, Redshift. Same source, all dialects.
 - **`datalex datalex diff`** — semantic diff with explicit rename tracking
   (`previous_name:`), breaking-change gate for CI.
+- **`datalex datalex mesh check <repo> --strict`** — verifies dbt mesh
+  Interface readiness for shared models declared with
+  `meta.datalex.interface`. See [docs/mesh-interfaces.md](docs/mesh-interfaces.md).
 - **Cross-repo package imports** — pin `acme/warehouse-core@1.4.0` in
   `imports:`, lockfile + content hash drift detection, Git-or-path
   resolution, on-disk parse cache for large projects.
 - **Visual studio** — React Flow UI for editing entities, relationships,
   and metadata; same YAML files as the CLI.
+- **Agentic modeling assistant** — local-first AI workflow for explaining
+  selected objects, reverse-engineering dbt repos into conceptual/logical
+  views, proposing focused YAML patches, and applying approved changes
+  through the same guarded save APIs as manual edits. Context comes from
+  structured dbt/DataLex facts, manifest/catalog metadata, BM25 lexical
+  search, validation output, project memory, and team skills under
+  `DataLex/Skills/*.md`; no vector search is used for code/YAML retrieval.
 
 ## Supported warehouses
 
@@ -223,10 +237,10 @@ per-dialect over time).
 **For users** — from [PyPI](https://pypi.org/project/datalex-cli/):
 
 ```bash
-pip install 'datalex-cli[serve]'                 # CLI + UI (recommended)
-pip install 'datalex-cli[serve,postgres]'        # add a warehouse driver
-pip install 'datalex-cli[serve,all]'             # every driver + UI
-pip install datalex-cli                          # CLI-only, no UI
+pip install -U 'datalex-cli[serve]'                 # CLI + UI (recommended)
+pip install -U 'datalex-cli[serve,postgres]'        # add a warehouse driver
+pip install -U 'datalex-cli[serve,all]'             # every driver + UI
+pip install -U datalex-cli                          # CLI-only, no UI
 ```
 
 Available extras: `serve`, `duckdb`, `postgres`, `mysql`, `snowflake`,
@@ -234,6 +248,23 @@ Available extras: `serve`, `duckdb`, `postgres`, `mysql`, `snowflake`,
 
 **Prereqs:** Python 3.9+ and Git. That's it — `[serve]` bundles Node.
 
+Verify the installed package:
+
+```bash
+datalex --version
+```
+
+Configure AI providers in **Settings → AI**. DataLex supports local
+fallback responses plus OpenAI, Anthropic, Gemini, and Ollama-compatible
+endpoints. Provider keys are stored locally in the browser; generated YAML
+is never written until you approve an explicit proposal.
+
+For the local DuckDB-based example repo, install the matching driver too:
+
+```bash
+pip install -U 'datalex-cli[serve,duckdb]'
+```
+
 **For contributors** — from source:
 
 ```bash
@@ -304,6 +335,8 @@ dbt parse
 - **[Pull a warehouse schema](docs/tutorials/warehouse-pull.md)** —
   7-minute live-connection flow with inferred PKs/FKs and streaming
   progress.
+- **[Agentic AI modeling](docs/ai-agentic-modeling.md)** — how Ask AI,
+  skills, memory, search/indexing, proposal review, and auto-refresh work.
 - **[CLI dbt-sync tutorial](docs/tutorial-dbt-sync.md)** — original
   CLI-only jaffle_shop walkthrough.
 

{datalex_cli-1.1.1 → datalex_cli-1.3.0}/datalex_cli.egg-info/SOURCES.txt

@@ -20,6 +20,7 @@ packages/core_engine/src/datalex_core/generators.py
 packages/core_engine/src/datalex_core/importers.py
 packages/core_engine/src/datalex_core/issues.py
 packages/core_engine/src/datalex_core/loader.py
+packages/core_engine/src/datalex_core/mesh.py
 packages/core_engine/src/datalex_core/migrate.py
 packages/core_engine/src/datalex_core/modeling.py
 packages/core_engine/src/datalex_core/packages.py
@@ -28,12 +29,15 @@ packages/core_engine/src/datalex_core/resolver.py
 packages/core_engine/src/datalex_core/schema.py
 packages/core_engine/src/datalex_core/semantic.py
 packages/core_engine/src/datalex_core/_schemas/datalex/common.schema.json
+packages/core_engine/src/datalex_core/_schemas/datalex/data_type.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/diagram.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/domain.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/entity.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/model.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/policy.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/project.schema.json
+packages/core_engine/src/datalex_core/_schemas/datalex/relationship.schema.json
+packages/core_engine/src/datalex_core/_schemas/datalex/semantic_model.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/snippet.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/source.schema.json
 packages/core_engine/src/datalex_core/_schemas/datalex/term.schema.json
@@ -1027,79 +1031,77 @@ packages/core_engine/src/datalex_core/_server/node_modules/which/which.js
 packages/core_engine/src/datalex_core/_server/node_modules/which/bin/node-which
 packages/core_engine/src/datalex_core/_webapp/DataLex.png
 packages/core_engine/src/datalex_core/_webapp/index.html
-packages/core_engine/src/datalex_core/_webapp/assets/ApplyDdlDialog-DeDlKGei.js
-packages/core_engine/src/datalex_core/_webapp/assets/BulkRenameColumnDialog-BjtRMgMY.js
-packages/core_engine/src/datalex_core/_webapp/assets/ColumnsView-BhnWhe2A.js
-packages/core_engine/src/datalex_core/_webapp/assets/CommitDialog-C6PiPK3b.js
-packages/core_engine/src/datalex_core/_webapp/assets/ConnectionsManager-CnN39D8E.js
-packages/core_engine/src/datalex_core/_webapp/assets/ConnectorLogo-CPWisvbI.js
-packages/core_engine/src/datalex_core/_webapp/assets/DictionaryPanel-BdVZE6jj.js
-packages/core_engine/src/datalex_core/_webapp/assets/DiffPanel-D5L77mQX.js
-packages/core_engine/src/datalex_core/_webapp/assets/EntityPanel-YgmAtcx9.js
-packages/core_engine/src/datalex_core/_webapp/assets/EntityPickerDialog-BSD7GGg1.js
-packages/core_engine/src/datalex_core/_webapp/assets/EnumsView-Beuc8Zrp.js
-packages/core_engine/src/datalex_core/_webapp/assets/ExportDdlDialog-BxoyCx4F.js
-packages/core_engine/src/datalex_core/_webapp/assets/GitBranchDialog-iShlzaUE.js
-packages/core_engine/src/datalex_core/_webapp/assets/HistoryPanel-ZEmwOGw0.js
-packages/core_engine/src/datalex_core/_webapp/assets/ImpactPanel-Dofxhm_7.js
-packages/core_engine/src/datalex_core/_webapp/assets/ImportDbtRepoDialog-DvtbXjwm.js
-packages/core_engine/src/datalex_core/_webapp/assets/IndexesView-C6Z9zVzn.js
-packages/core_engine/src/datalex_core/_webapp/assets/LibrariesPanel-BhOnURKo.js
-packages/core_engine/src/datalex_core/_webapp/assets/ModelGraphPanel-BARbMjXH.js
-packages/core_engine/src/datalex_core/_webapp/assets/ModelerPanel-CRfloXxN.js
-packages/core_engine/src/datalex_core/_webapp/assets/NewRelationshipDialog-DqYMhQ-U.js
-packages/core_engine/src/datalex_core/_webapp/assets/OnboardingWelcomeDialog-3oQIqYRE.js
-packages/core_engine/src/datalex_core/_webapp/assets/PanelDialog-Dvb_BpM1.js
-packages/core_engine/src/datalex_core/_webapp/assets/RelationsView-z4nnARvn.js
-packages/core_engine/src/datalex_core/_webapp/assets/SettingsDialog-BdJYb-4a.js
-packages/core_engine/src/datalex_core/_webapp/assets/ShareBundleDialog-DaMY9Qfi.js
-packages/core_engine/src/datalex_core/_webapp/assets/SnapshotsDialog-BlvfDSBd.js
-packages/core_engine/src/datalex_core/_webapp/assets/SqlView-Bo_tbPN8.js
-packages/core_engine/src/datalex_core/_webapp/assets/SubjectAreasPanel-aU-lM6KM.js
-packages/core_engine/src/datalex_core/_webapp/assets/TableView-CsSE54uX.js
-packages/core_engine/src/datalex_core/_webapp/assets/ValidationPanel-DAvm64ZY.js
-packages/core_engine/src/datalex_core/_webapp/assets/ViewerWelcome-BXq_se6L.js
-packages/core_engine/src/datalex_core/_webapp/assets/ViewsView-BjrNzF-C.js
-packages/core_engine/src/datalex_core/_webapp/assets/YamlEditor-CFjXUp_B.js
-packages/core_engine/src/datalex_core/_webapp/assets/YamlEditorShell-r4R7TtLU.js
-packages/core_engine/src/datalex_core/_webapp/assets/arrow-right-left-Bk-uJALr.js
-packages/core_engine/src/datalex_core/_webapp/assets/arrow-right-sqy1wK0v.js
-packages/core_engine/src/datalex_core/_webapp/assets/boxes-BrTfrmOc.js
-packages/core_engine/src/datalex_core/_webapp/assets/bulkRefactor-Cp7hY8JC.js
-packages/core_engine/src/datalex_core/_webapp/assets/check-DVOOJviZ.js
-packages/core_engine/src/datalex_core/_webapp/assets/chevron-down-CulwODFE.js
-packages/core_engine/src/datalex_core/_webapp/assets/chevron-right-C9jyd0J3.js
-packages/core_engine/src/datalex_core/_webapp/assets/cloud-upload-BPG3Jgg1.js
-packages/core_engine/src/datalex_core/_webapp/assets/compass-DLVmPSHf.js
-packages/core_engine/src/datalex_core/_webapp/assets/dbtLint-z6e8DpYG.js
-packages/core_engine/src/datalex_core/_webapp/assets/download-CmJigawr.js
-packages/core_engine/src/datalex_core/_webapp/assets/elkLayout-DeVaxgJf.js
-packages/core_engine/src/datalex_core/_webapp/assets/eye-B_f5CKJB.js
-packages/core_engine/src/datalex_core/_webapp/assets/eye-off-CdiOy7l5.js
-packages/core_engine/src/datalex_core/_webapp/assets/file-code-corner-CHUsRnUK.js
-packages/core_engine/src/datalex_core/_webapp/assets/file-diff-DRzJ9oy-.js
-packages/core_engine/src/datalex_core/_webapp/assets/file-text-CxySe2xy.js
-packages/core_engine/src/datalex_core/_webapp/assets/folder-open-BU5fWmHP.js
-packages/core_engine/src/datalex_core/_webapp/assets/gauge-BlFXRClN.js
-packages/core_engine/src/datalex_core/_webapp/assets/index--y4EFCgj.js
-packages/core_engine/src/datalex_core/_webapp/assets/index-ARp1fkia.css
+packages/core_engine/src/datalex_core/_webapp/assets/AiAssistantDialog-BPabpzJ4.js
+packages/core_engine/src/datalex_core/_webapp/assets/AiAssistantSurface-D0puHHUO.js
+packages/core_engine/src/datalex_core/_webapp/assets/ApplyDdlDialog-Cfw_YYZK.js
+packages/core_engine/src/datalex_core/_webapp/assets/BulkRenameColumnDialog-Ch7i85xl.js
+packages/core_engine/src/datalex_core/_webapp/assets/ColumnsView-BL0zMdE3.js
+packages/core_engine/src/datalex_core/_webapp/assets/CommitDialog-CNeLNXa3.js
+packages/core_engine/src/datalex_core/_webapp/assets/ConceptDetailsView-BZjVN_Ep.js
+packages/core_engine/src/datalex_core/_webapp/assets/ConnectionsManager-GBrvCnz6.js
+packages/core_engine/src/datalex_core/_webapp/assets/ConnectorLogo-VU558Ttu.js
+packages/core_engine/src/datalex_core/_webapp/assets/DbtYamlPickerDialog-DFQ2RZna.js
+packages/core_engine/src/datalex_core/_webapp/assets/DictionaryPanel-6ypCaImj.js
+packages/core_engine/src/datalex_core/_webapp/assets/DiffPanel-DxX3lMVS.js
+packages/core_engine/src/datalex_core/_webapp/assets/EntityPickerDialog-KfKFYrgO.js
+packages/core_engine/src/datalex_core/_webapp/assets/EnumsView-DrZL54U8.js
+packages/core_engine/src/datalex_core/_webapp/assets/ExportDdlDialog-B0BkM1jP.js
+packages/core_engine/src/datalex_core/_webapp/assets/GitBranchDialog-NLVF7ntd.js
+packages/core_engine/src/datalex_core/_webapp/assets/HistoryPanel-Dpl_v_9Z.js
+packages/core_engine/src/datalex_core/_webapp/assets/ImportDbtRepoDialog-Leau8yBx.js
+packages/core_engine/src/datalex_core/_webapp/assets/IndexesView-DwL1LFMd.js
+packages/core_engine/src/datalex_core/_webapp/assets/LogicalDetailsView-dKXN6lSB.js
+packages/core_engine/src/datalex_core/_webapp/assets/ModelerPanel-CujN8kpE.js
+packages/core_engine/src/datalex_core/_webapp/assets/NewConceptDialog-DCcN8m1o.js
+packages/core_engine/src/datalex_core/_webapp/assets/NewLogicalEntityDialog-hbiYqqCv.js
+packages/core_engine/src/datalex_core/_webapp/assets/NewRelationshipDialog-BX0O73Di.js
+packages/core_engine/src/datalex_core/_webapp/assets/OnboardingWelcomeDialog-JnmVH09a.js
+packages/core_engine/src/datalex_core/_webapp/assets/PanelDialog-BsE2hAlf.js
+packages/core_engine/src/datalex_core/_webapp/assets/RelationsView-sIJl50dJ.js
+packages/core_engine/src/datalex_core/_webapp/assets/SelectionSummaryPanel-C6SrkCve.js
+packages/core_engine/src/datalex_core/_webapp/assets/SettingsDialog-Dw1ROzz-.js
+packages/core_engine/src/datalex_core/_webapp/assets/ShareBundleDialog-Dy7JPv6G.js
+packages/core_engine/src/datalex_core/_webapp/assets/SnapshotsDialog-BNb8ec7h.js
+packages/core_engine/src/datalex_core/_webapp/assets/SqlView-CYPuB4xh.js
+packages/core_engine/src/datalex_core/_webapp/assets/TableView-CscnIKx4.js
+packages/core_engine/src/datalex_core/_webapp/assets/ValidationPanel-DP5Jy16J.js
+packages/core_engine/src/datalex_core/_webapp/assets/ViewerWelcome-DaX8o_XX.js
+packages/core_engine/src/datalex_core/_webapp/assets/ViewsView-afvRT6pQ.js
+packages/core_engine/src/datalex_core/_webapp/assets/YamlEditor-6zRrydSC.js
+packages/core_engine/src/datalex_core/_webapp/assets/YamlEditorShell-C6TPECb9.js
+packages/core_engine/src/datalex_core/_webapp/assets/arrow-right-DNJdjhrt.js
+packages/core_engine/src/datalex_core/_webapp/assets/arrow-right-left-Q0URo3Wa.js
+packages/core_engine/src/datalex_core/_webapp/assets/check-CZeBDOb-.js
+packages/core_engine/src/datalex_core/_webapp/assets/chevron-down-Dqg2CuXx.js
+packages/core_engine/src/datalex_core/_webapp/assets/chevron-right-DrHt2R7K.js
+packages/core_engine/src/datalex_core/_webapp/assets/cloud-upload-D8VhHr1i.js
+packages/core_engine/src/datalex_core/_webapp/assets/dbtLint-BzXUVFHT.js
+packages/core_engine/src/datalex_core/_webapp/assets/ddl-Ca_0jM2y.js
+packages/core_engine/src/datalex_core/_webapp/assets/download-Dt3trXko.js
+packages/core_engine/src/datalex_core/_webapp/assets/elkLayout-Dw2BM1Pu.js
+packages/core_engine/src/datalex_core/_webapp/assets/eye-NJ1nAV7k.js
+packages/core_engine/src/datalex_core/_webapp/assets/eye-off-DlDCythw.js
+packages/core_engine/src/datalex_core/_webapp/assets/file-diff-F6DZk7x8.js
+packages/core_engine/src/datalex_core/_webapp/assets/file-text-BiSh-2QX.js
+packages/core_engine/src/datalex_core/_webapp/assets/folder-open-Iy6Fym5-.js
+packages/core_engine/src/datalex_core/_webapp/assets/folder-tree-BgENW9g9.js
+packages/core_engine/src/datalex_core/_webapp/assets/forwardSql-BPerjtAz.js
+packages/core_engine/src/datalex_core/_webapp/assets/gauge-PgCIEW0u.js
+packages/core_engine/src/datalex_core/_webapp/assets/index-CqHF_Jep.css
+packages/core_engine/src/datalex_core/_webapp/assets/index-D1q0JJvu.js
 packages/core_engine/src/datalex_core/_webapp/assets/index-xVp0PEHv.js
-packages/core_engine/src/datalex_core/_webapp/assets/key-BmqP8rmf.js
-packages/core_engine/src/datalex_core/_webapp/assets/layers-DGswqILk.js
-packages/core_engine/src/datalex_core/_webapp/assets/link-2-Bthk81j2.js
-packages/core_engine/src/datalex_core/_webapp/assets/list-ordered-DliwSQmZ.js
-packages/core_engine/src/datalex_core/_webapp/assets/loader-circle-AL2i1LPv.js
-packages/core_engine/src/datalex_core/_webapp/assets/modelQuality-V_E0VNUs.js
-packages/core_engine/src/datalex_core/_webapp/assets/play-BMkQIcaU.js
-packages/core_engine/src/datalex_core/_webapp/assets/plug-BRkbuTIQ.js
-packages/core_engine/src/datalex_core/_webapp/assets/replace-KqK92NWV.js
-packages/core_engine/src/datalex_core/_webapp/assets/search-xtsSjiY8.js
-packages/core_engine/src/datalex_core/_webapp/assets/shield-C400fwDk.js
-packages/core_engine/src/datalex_core/_webapp/assets/sparkles-Dh0UZ_2J.js
-packages/core_engine/src/datalex_core/_webapp/assets/square-wc5HzqXx.js
-packages/core_engine/src/datalex_core/_webapp/assets/table-2-1DjVIJ09.js
-packages/core_engine/src/datalex_core/_webapp/assets/tag-BAgPIdvs.js
-packages/core_engine/src/datalex_core/_webapp/assets/upload-CfR7oCFE.js
+packages/core_engine/src/datalex_core/_webapp/assets/key-DO14m8Cj.js
+packages/core_engine/src/datalex_core/_webapp/assets/key-round-CvWNSD69.js
+packages/core_engine/src/datalex_core/_webapp/assets/link-2-DFcc013V.js
+packages/core_engine/src/datalex_core/_webapp/assets/list-ordered-BaQXhg8q.js
+packages/core_engine/src/datalex_core/_webapp/assets/loader-circle-Be3t8kpx.js
+packages/core_engine/src/datalex_core/_webapp/assets/modelQuality-DQy9cEom.js
+packages/core_engine/src/datalex_core/_webapp/assets/plug-DzAK2bWE.js
+packages/core_engine/src/datalex_core/_webapp/assets/replace-DSAf6Slx.js
+packages/core_engine/src/datalex_core/_webapp/assets/search-sq0YPMDd.js
+packages/core_engine/src/datalex_core/_webapp/assets/sparkles-DBRh1_GW.js
+packages/core_engine/src/datalex_core/_webapp/assets/tag-DeV4t9F7.js
+packages/core_engine/src/datalex_core/_webapp/assets/upload-Saisv89G.js
 packages/core_engine/src/datalex_core/connectors/__init__.py
 packages/core_engine/src/datalex_core/connectors/base.py
 packages/core_engine/src/datalex_core/connectors/bigquery.py

{datalex_cli-1.1.1 → datalex_cli-1.3.0}/packages/cli/src/datalex_cli/datalex_cli.py

@@ -3,6 +3,7 @@
 Subcommands:
   migrate to-datalex-layout <v3-model.yaml>   split legacy v3 model into DataLex tree
   validate <project-root>                     load + validate a DataLex project
+  mesh check <project-root>                   check dbt mesh Interface standards
   emit ddl <project-root> --dialect ...       emit per-dialect DDL for every physical entity
   diff <old-root> <new-root>                  semantic diff with explicit rename tracking
   info <project-root>                         print a summary (entity/term/domain counts)
@@ -25,6 +26,7 @@ import datalex_core.dialects  # noqa: F401  — side-effect registers built-in d
 from datalex_core.dialects.registry import get_dialect, known_dialects
 from datalex_core.dbt import emit_dbt, import_manifest, write_import_result
 from datalex_core.dbt.sync import sync_dbt_project, report_to_json
+from datalex_core.mesh import mesh_issues, mesh_report
 from datalex_core.packages import PackageResolveError, load_imports_for, resolve_imports
 
 
@@ -76,6 +78,26 @@ def register_datalex(parent_sub: argparse._SubParsersAction) -> None:
     )
     validate_parser.set_defaults(func=_cmd_validate)
 
+    # mesh
+    mesh_parser = dsub.add_parser("mesh", help="dbt mesh Interface standards")
+    mesh_sub = mesh_parser.add_subparsers(dest="mesh_command", required=True)
+    mesh_check = mesh_sub.add_parser(
+        "check",
+        help="Check DataLex/dbt Interface metadata and readiness standards",
+    )
+    mesh_check.add_argument("root", help="Project root or dbt repo root")
+    mesh_check.add_argument(
+        "--strict",
+        action="store_true",
+        help="Treat Interface readiness blockers as errors for CI",
+    )
+    mesh_check.add_argument(
+        "--output-json",
+        action="store_true",
+        help="Emit machine-readable results for CI annotations",
+    )
+    mesh_check.set_defaults(func=_cmd_mesh_check)
+
     # emit ddl
     emit_parser = dsub.add_parser("emit", help="Emit artifacts from a DataLex project")
     esub = emit_parser.add_subparsers(dest="emit_command", required=True)
@@ -317,6 +339,49 @@ def _cmd_validate(args: argparse.Namespace) -> int:
     return 1 if project.errors.has_errors() else 0
 
 
+def _cmd_mesh_check(args: argparse.Namespace) -> int:
+    try:
+        project = load_project(args.root, strict=False)
+    except DataLexLoadError as e:
+        if args.output_json:
+            print(json.dumps({"errors": [err.to_dict() for err in e.errors]}, indent=2))
+        else:
+            for err in e.errors:
+                print(str(err), file=sys.stderr)
+        return 1
+
+    report = mesh_report(project, strict=args.strict)
+    issues = mesh_issues(project, strict=args.strict)
+    load_errors = project.errors.to_list()
+
+    if args.output_json:
+        payload = {
+            **report,
+            "load_diagnostics": load_errors,
+        }
+        print(json.dumps(payload, indent=2))
+    else:
+        print(f"DataLex mesh Interface check: {project.root}")
+        print(f"  strict: {'yes' if args.strict else 'no'}")
+        if not issues:
+            print("  interfaces: ready")
+        else:
+            print(f"  diagnostics: {len(issues)}")
+            for issue in issues:
+                print(f"  [{issue.severity.upper()}] {issue.code} {issue.path}: {issue.message}")
+        if load_errors:
+            print(f"\n  load diagnostics: {len(load_errors)}")
+            for err in load_errors:
+                sev = str(err.get("severity") or "error").upper()
+                code = err.get("code") or "LOAD"
+                path = err.get("location", {}).get("file") or project.root
+                msg = err.get("message") or ""
+                print(f"  [{sev}] {code} {path}: {msg}")
+
+    has_mesh_errors = any(issue.severity == "error" for issue in issues)
+    return 1 if has_mesh_errors or project.errors.has_errors() else 0
+
+
 def _cmd_emit_ddl(args: argparse.Namespace) -> int:
     try:
         project = load_project(args.root, strict=True)