datacharter 0.2.0__tar.gz → 0.3.0__tar.gz

{datacharter-0.2.0 → datacharter-0.3.0}/.github/workflows/banned-terms.yml

@@ -14,7 +14,7 @@ jobs:
   scan:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v5
       - name: Scan for banned terms
         run: |
           set -e

{datacharter-0.2.0 → datacharter-0.3.0}/.github/workflows/release.yml

@@ -17,20 +17,20 @@ jobs:
   build:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: npm
           cache-dependency-path: ui/package-lock.json
-      - uses: astral-sh/setup-uv@v4
+      - uses: astral-sh/setup-uv@v7
       - name: Build UI into the package
         run: ./scripts/build_ui.sh
       - name: Build sdist + wheel
         run: uv build
       - name: Validate metadata and README rendering
         run: uvx twine check dist/*
-      - uses: actions/upload-artifact@v4
+      - uses: actions/upload-artifact@v7
         with:
           name: dist
           path: dist/
@@ -44,7 +44,7 @@ jobs:
     permissions:
       id-token: write # OIDC token for PyPI Trusted Publishing
     steps:
-      - uses: actions/download-artifact@v4
+      - uses: actions/download-artifact@v8
         with:
           name: dist
           path: dist/

{datacharter-0.2.0 → datacharter-0.3.0}/.github/workflows/test.yml

@@ -8,8 +8,8 @@ jobs:
   test:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v4
+      - uses: actions/checkout@v5
+      - uses: astral-sh/setup-uv@v7
       - name: Install
         run: uv venv && uv pip install -e ".[dev]"
       - name: Lint
@@ -44,8 +44,8 @@ jobs:
           --health-cmd "mysqladmin ping -h 127.0.0.1 -pcharter_test_pw -ucharter"
           --health-interval 2s --health-timeout 2s --health-retries 60
     steps:
-      - uses: actions/checkout@v4
-      - uses: astral-sh/setup-uv@v4
+      - uses: actions/checkout@v5
+      - uses: astral-sh/setup-uv@v7
       - name: Install
         run: uv venv && uv pip install -e ".[dev]"
       - name: Seed databases
@@ -61,8 +61,8 @@ jobs:
   ui:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: npm
@@ -75,15 +75,28 @@ jobs:
   package:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
+      - uses: actions/checkout@v5
+      - uses: actions/setup-node@v5
         with:
           node-version: 22
           cache: npm
           cache-dependency-path: ui/package-lock.json
-      - uses: astral-sh/setup-uv@v4
+      - uses: astral-sh/setup-uv@v7
       - name: Build UI into package
         run: ./scripts/build_ui.sh
+      - name: Fetch VidaiMock (e2e mock LLM; Apache-2.0, checksum-pinned)
+        run: |
+          ver=v0.2.9
+          base="https://github.com/vidaiUK/VidaiMock/releases/download/$ver"
+          curl -fsSL -o vm.tar.gz "$base/vidaimock-linux-x64.tar.gz"
+          curl -fsSL -o vm.sha256 "$base/vidaimock-linux-x64.sha256"
+          got=$(sha256sum vm.tar.gz | awk '{print $1}')
+          want=$(awk '{print $1}' vm.sha256)
+          test "$got" = "$want" || { echo "VidaiMock checksum mismatch: $got != $want"; exit 1; }
+          mkdir -p vidaimock-bin && tar -xzf vm.tar.gz -C vidaimock-bin
+          bin=$(find "$PWD/vidaimock-bin" -type f -name vidaimock | head -1)
+          chmod +x "$bin"
+          echo "VIDAIMOCK_BIN=$bin" >> "$GITHUB_ENV"
       - name: Install + e2e
         run: |
           uv venv

{datacharter-0.2.0 → datacharter-0.3.0}/CHANGELOG.md

@@ -5,6 +5,75 @@ Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
 
 ## [Unreleased]
 
+## [0.3.0] - 2026-07-24
+
+### Added
+
+- Agent view: a toggle on the results grid that masks the contract's PII columns
+  in place, showing exactly what the agent and MCP server see (the model never
+  sees raw PII) — right in the SQL editor, no LLM required.
+- Source tree: collapsible `+`/`−` disclosure on every source and table, and
+  expand a table to see its columns inline.
+- Instant SQL preview: results update live a beat after you stop typing (row-capped,
+  and errors stay silent until you press Run) — no Run click needed to see output.
+- Chart captions: auto-detected charts (results) and agent-emitted charts (chat)
+  now show a one-line plain-language caption of what they show — e.g. "bar of
+  revenue by customer_id".
+- `datacharter explain <sql>` — show a query's plan and row estimates without
+  running it: a pre-flight cost check that surfaces per-source scans and what
+  would push down.
+- `datacharter sample <relation>` — print a PII-masked CSV sample of a relation
+  (columns marked PII in the contract come back as `•••`), safe to paste into a
+  bug ticket or share.
+- Contract-scoped metrics: declare named `metrics:` in `charter.yaml` (a base
+  relation + an aggregate expression + optional dimensions); `datacharter metric
+  <name> [--by cols]` resolves each to one governed SELECT and runs it, so a
+  certified `revenue` always means the same thing. Joins across sources and time
+  grains are a later refinement.
+- NL→SQL cache: when the agent answers via a query, its SQL is cached against a
+  contract fingerprint; a repeat or normalized-reworded question re-runs the
+  cached SQL on current data and skips the LLM round-trip (fresh data, no stale
+  answers). Embedding-based semantic similarity is a follow-up.
+- `datacharter serve --offline` — no-egress mode: the LLM agent is disabled (no
+  data can reach any model endpoint) and connecting one at runtime is refused. It
+  prints and writes a no-egress attestation to `.datacharter/attestation.json`.
+- `datacharter snapshot <name> <sql>` and `datacharter recheck <name>` — save a
+  query's result as `local.<name>` alongside its SQL, then later re-run it and
+  diff against the saved result to answer "did this number change?". `recheck`
+  exits non-zero when the result has changed.
+- `datacharter drift` — report schema drift between the charter and the live
+  sources: declared tables or PII columns that no longer exist. A missing PII
+  column is a silent masking gap, so this is caught explicitly. Exits non-zero
+  when drift is found, for use in CI.
+- `datacharter scan` — introspect the configured sources and suggest PII columns
+  for `charter.yaml`, both by column name and by sampled values (catches an
+  email/SSN/IP column whose name gives nothing away). Turns "author a contract"
+  into "review a generated one" for the PII map. Prints suggestions, or `--write`
+  merges them into `charter.yaml` (round-trip; credential refs left untouched).
+- `datacharter diff <left> <right>` and `Engine.diff` — a full-row set difference
+  between two relations, across sources (postgres vs a file, prod vs staging, …)
+  via the federation engine. Reports rows only in each side plus the common count,
+  through the read-only guard. With `--key`, rows are matched by key and changed
+  rows (same key, differing values) are counted separately.
+- Per-query provenance: query results (API, agent tool results) now report the
+  source relations and columns the query read — plus column lineage, mapping each
+  output column to the input columns that feed it — parsed from the same AST the
+  read-only guard uses. This is the trust signal for an agent answer: it shows
+  which real columns an answer came from.
+- `datacharter mcp` — an MCP (Model Context Protocol) server over stdio that
+  exposes the four governed query tools (`list_sources`, `list_tables`,
+  `describe_table`, `query`) to any MCP client. The read-only guard, PII masking,
+  and credential scrubbing are inherited from the same toolbox the agent uses, so
+  an external agent can explore your data without seeing raw PII or being able to
+  write. Hand-rolled JSON-RPC 2.0, no new dependency.
+
+### Changed
+
+- Toolbar: **Snapshot** moved next to the query actions (away from the export
+  format menu); hover tooltips on Run/Snapshot/Export/Explain.
+- Demo workspace: bundled as one sqlite `store` contract holding `customers`
+  and `orders`, so the sidebar reads contract → table → columns.
+
 ## [0.2.0] - 2026-07-24
 
 ### Added

datacharter-0.3.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,72 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the maintainers privately through GitHub's private reporting on the
+repository (Security → Advisories, or a direct message to a maintainer). All
+complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
+
+[homepage]: https://www.contributor-covenant.org

datacharter-0.3.0/CONTRIBUTING.md

@@ -0,0 +1,124 @@
+# Contributing to DataCharter
+
+Thanks for your interest in DataCharter. Contributions of all kinds — bug
+reports, docs, tests, and code — are welcome. The project is licensed under
+[Apache-2.0](LICENSE); contributions are accepted under the same license.
+
+## Ways to contribute
+
+- **Report a bug or request a feature** — open an issue with steps to reproduce
+  or a clear description of the use case.
+- **Improve docs** — fixes to the guides under `docs/` and the README are always
+  welcome.
+- **Send a pull request** — for anything beyond a trivial fix, open (or comment
+  on) an issue first so we can agree on the approach before you invest the work.
+
+## Development setup
+
+DataCharter is one Python package with a bundled web UI. You need Python 3.11+
+and [uv](https://docs.astral.sh/uv/); UI work additionally needs Node.
+
+```sh
+# Python environment (creates .venv)
+uv sync
+
+# Run the app from source
+uv run datacharter serve
+
+# Web UI (only if you're changing the frontend)
+cd ui && npm ci && npm run build
+```
+
+## Tests and linting
+
+Every change lands with tests, and the working tree must be lint-clean. These
+are the same commands CI runs:
+
+```sh
+uv run pytest -q                 # unit tests (fast; the default set)
+uv run pytest -m integration -q  # integration tests (require Docker)
+uv run pytest -m e2e -q          # end-to-end (see below)
+uv run ruff check .              # lint
+cd ui && npm run build           # type-check + build the UI
+```
+
+The end-to-end agent test drives a real
+[VidaiMock](https://github.com/vidaiUK/VidaiMock) server (an Apache-2.0 mock LLM);
+it skips unless `VIDAIMOCK_BIN` points at the binary or `vidaimock` is on `PATH`.
+
+Write tests that describe behavior, keep unit tests fast, and put anything that
+needs Docker or a live server behind the `integration` / `e2e` markers so the
+default run stays quick.
+
+## Commit and pull-request conventions
+
+- **[Conventional Commits](https://www.conventionalcommits.org/)**:
+  `feat:`, `fix:`, `docs:`, `chore:`, `test:`, `refactor:`. Keep the subject
+  under ~72 characters, imperative mood.
+- Small, focused commits over large omnibus ones. Every commit should build and
+  pass tests so history stays bisectable.
+- Never commit secrets, tokens, or real hostnames — in code, tests, or fixtures.
+- Keep the PR scoped to one change; describe the "why," not just the "what."
+
+## Developer Certificate of Origin (sign-off required)
+
+DataCharter uses the **Developer Certificate of Origin (DCO)** instead of a CLA.
+Every commit must be signed off, certifying that you wrote the change (or
+otherwise have the right to submit it under Apache-2.0). This is a lightweight,
+one-time habit — no separate agreement to sign.
+
+Add the sign-off automatically with the `-s` flag:
+
+```sh
+git commit -s -m "fix: correct off-by-one in row cap"
+```
+
+That appends a line matching your configured `git` name and email:
+
+```
+Signed-off-by: Jane Developer <jane@example.com>
+```
+
+Use your real name and a valid email. If you forget the sign-off on your last
+commit, amend it with `git commit --amend -s`; for a whole branch, use
+`git rebase --signoff <base>`. PRs whose commits are not signed off cannot be
+merged.
+
+By signing off, you agree to the DCO, version 1.1:
+
+```
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+    have the right to submit it under the open source license
+    indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+    of my knowledge, is covered under an appropriate open source
+    license and I have the right under that license to submit that
+    work with modifications, whether created in whole or in part
+    by me, under the same open source license (unless I am
+    permitted to submit under a different license), as indicated
+    in the file; or
+
+(c) The contribution was provided directly to me by some other
+    person who certified (a), (b) or (c) and I have not modified
+    it.
+
+(d) I understand and agree that this project and the contribution
+    are public and that a record of the contribution (including all
+    personal information I submit with it, including my sign-off) is
+    maintained indefinitely and may be redistributed consistent with
+    this project or the open source license(s) involved.
+```

{datacharter-0.2.0 → datacharter-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: datacharter
-Version: 0.2.0
+Version: 0.3.0
 Summary: Charter your data — contract-governed local data exploration, powered by DuckDB
 Project-URL: Homepage, https://github.com/datacharter/datacharter
 Project-URL: Repository, https://github.com/datacharter/datacharter
@@ -46,12 +46,20 @@ Description-Content-Type: text/markdown
 
 > Explore all your data locally, in one place — contract-governed data exploration, powered by DuckDB
 
+[![PyPI](https://img.shields.io/pypi/v/datacharter)](https://pypi.org/project/datacharter/)
+[![Python](https://img.shields.io/pypi/pyversions/datacharter)](https://pypi.org/project/datacharter/)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue)](LICENSE)
+
 Contract-governed local data exploration, **powered by [DuckDB](https://duckdb.org)**.
 Define your sources as data contracts
 ([ODCS](https://bitol-io.github.io/open-data-contract-standard/)-compatible YAML),
 query them through DuckDB's SQL federation engine with real source pushdowns,
-explore in a local web UI — charts, profiling, SQL editor — and optionally ask
-questions in plain language with a fully local model.
+and explore in a local web UI — SQL editor with live preview, auto-charts,
+profiling. Every answer shows which source columns it read; ask questions in
+plain language or serve the whole thing to an AI agent over [MCP](docs/mcp.md),
+with PII masked from the model — all on your machine.
+
+![DataCharter — live SQL preview, auto-charts, per-query provenance, and PII masking](https://raw.githubusercontent.com/datacharter/datacharter/main/brand/demo.gif)
 
 **Status: pre-release.** V1 in development.
 
@@ -97,6 +105,21 @@ Drop a CSV, Parquet, or JSON file onto the window to query it instantly.
   `.env.example` — commit it, clone it, `datacharter serve`. Your team's whole
   exploration environment travels as a repo; secrets and local state never do.
 
+## More than a viewer
+
+DataCharter governs and audits your data, not just displays it — see the
+[CLI reference](docs/cli.md) for the full command set:
+
+- **Governed MCP server** — `datacharter mcp` exposes read-only, PII-masked query
+  tools to any MCP client (Cursor, Cline, or your own agent).
+- **Contracts you can check** — `datacharter drift` exits non-zero when a declared
+  table or PII column disappears; `datacharter scan` detects PII columns to add.
+- **Answers that show their work** — every result reports the source columns it
+  read; `datacharter diff` compares relations across sources; `datacharter metric`
+  runs governed metric definitions.
+- **Privacy-first** — `serve --offline` runs with no outbound network, and the
+  model never sees raw PII (flip **Agent view** in the UI to see exactly what it does).
+
 ## Built on
 
 DataCharter stands on excellent open-source foundations:
@@ -105,8 +128,16 @@ DataCharter stands on excellent open-source foundations:
   federation (`ATTACH`), file formats, Iceberg/Delta, encryption, autocomplete.
 - **[Open Data Contract Standard](https://bitol-io.github.io/open-data-contract-standard/)** /
   [datacontract.com](https://datacontract-specification.com/) — the contract format `charter.yaml` speaks.
+- **[Model Context Protocol](https://modelcontextprotocol.io)** — the open protocol
+  the `datacharter mcp` server speaks to agents and MCP clients.
 - **[Vega-Lite](https://vega.github.io/vega-lite/)** — declarative charting.
 - **[Monaco Editor](https://microsoft.github.io/monaco-editor/)** — the SQL editor.
+- **[TanStack Table & Virtual](https://tanstack.com/)** — the virtualized results grid.
+- And the Python & React ecosystems — FastAPI, pydantic, httpx, keyring, and
+  ruamel.yaml on the backend; React and Vite on the front.
+
+Testing uses **[VidaiMock](https://github.com/vidaiUK/VidaiMock)**, an
+Apache-2.0 mock LLM server, as the offline agent endpoint in CI.
 
 DuckDB is a trademark of the DuckDB Foundation. DataCharter is an independent
 project and is not affiliated with or endorsed by the DuckDB Foundation.

{datacharter-0.2.0 → datacharter-0.3.0}/README.md

@@ -2,12 +2,20 @@
 
 > Explore all your data locally, in one place — contract-governed data exploration, powered by DuckDB
 
+[![PyPI](https://img.shields.io/pypi/v/datacharter)](https://pypi.org/project/datacharter/)
+[![Python](https://img.shields.io/pypi/pyversions/datacharter)](https://pypi.org/project/datacharter/)
+[![License: Apache-2.0](https://img.shields.io/badge/License-Apache_2.0-blue)](LICENSE)
+
 Contract-governed local data exploration, **powered by [DuckDB](https://duckdb.org)**.
 Define your sources as data contracts
 ([ODCS](https://bitol-io.github.io/open-data-contract-standard/)-compatible YAML),
 query them through DuckDB's SQL federation engine with real source pushdowns,
-explore in a local web UI — charts, profiling, SQL editor — and optionally ask
-questions in plain language with a fully local model.
+and explore in a local web UI — SQL editor with live preview, auto-charts,
+profiling. Every answer shows which source columns it read; ask questions in
+plain language or serve the whole thing to an AI agent over [MCP](docs/mcp.md),
+with PII masked from the model — all on your machine.
+
+![DataCharter — live SQL preview, auto-charts, per-query provenance, and PII masking](https://raw.githubusercontent.com/datacharter/datacharter/main/brand/demo.gif)
 
 **Status: pre-release.** V1 in development.
 
@@ -53,6 +61,21 @@ Drop a CSV, Parquet, or JSON file onto the window to query it instantly.
   `.env.example` — commit it, clone it, `datacharter serve`. Your team's whole
   exploration environment travels as a repo; secrets and local state never do.
 
+## More than a viewer
+
+DataCharter governs and audits your data, not just displays it — see the
+[CLI reference](docs/cli.md) for the full command set:
+
+- **Governed MCP server** — `datacharter mcp` exposes read-only, PII-masked query
+  tools to any MCP client (Cursor, Cline, or your own agent).
+- **Contracts you can check** — `datacharter drift` exits non-zero when a declared
+  table or PII column disappears; `datacharter scan` detects PII columns to add.
+- **Answers that show their work** — every result reports the source columns it
+  read; `datacharter diff` compares relations across sources; `datacharter metric`
+  runs governed metric definitions.
+- **Privacy-first** — `serve --offline` runs with no outbound network, and the
+  model never sees raw PII (flip **Agent view** in the UI to see exactly what it does).
+
 ## Built on
 
 DataCharter stands on excellent open-source foundations:
@@ -61,8 +84,16 @@ DataCharter stands on excellent open-source foundations:
   federation (`ATTACH`), file formats, Iceberg/Delta, encryption, autocomplete.
 - **[Open Data Contract Standard](https://bitol-io.github.io/open-data-contract-standard/)** /
   [datacontract.com](https://datacontract-specification.com/) — the contract format `charter.yaml` speaks.
+- **[Model Context Protocol](https://modelcontextprotocol.io)** — the open protocol
+  the `datacharter mcp` server speaks to agents and MCP clients.
 - **[Vega-Lite](https://vega.github.io/vega-lite/)** — declarative charting.
 - **[Monaco Editor](https://microsoft.github.io/monaco-editor/)** — the SQL editor.
+- **[TanStack Table & Virtual](https://tanstack.com/)** — the virtualized results grid.
+- And the Python & React ecosystems — FastAPI, pydantic, httpx, keyring, and
+  ruamel.yaml on the backend; React and Vite on the front.
+
+Testing uses **[VidaiMock](https://github.com/vidaiUK/VidaiMock)**, an
+Apache-2.0 mock LLM server, as the offline agent endpoint in CI.
 
 DuckDB is a trademark of the DuckDB Foundation. DataCharter is an independent
 project and is not affiliated with or endorsed by the DuckDB Foundation.

datacharter-0.3.0/SECURITY.md

@@ -0,0 +1,38 @@
+# Security Policy
+
+DataCharter treats several of its boundaries as security-critical: the
+parser-based read-only guard, contract-driven PII masking, credential scrubbing
+on every error path, and encrypted local spill/state. We appreciate reports that
+help keep those boundaries sound.
+
+## Reporting a vulnerability
+
+Please report security issues **privately** through GitHub's private vulnerability
+reporting — open the repository's **Security → Advisories → Report a vulnerability**.
+Do not open a public issue for a security report.
+
+We aim to acknowledge a report within three business days and to keep you updated
+as we investigate and ship a fix.
+
+## Supported versions
+
+DataCharter is pre-1.0; security fixes land on the latest release. Please run the
+most recent version (`pip install -U datacharter`).
+
+## Scope
+
+In scope:
+
+- Bypasses of the read-only guard — any way to run a write, DDL/DML, or a
+  filesystem/remote function through a query.
+- PII-mask bypasses — surfacing a masked column's raw values through the agent
+  tools or the MCP server.
+- Credential leakage in error messages, logs, or on disk.
+- The HTTP surface of `datacharter serve` — DNS-rebinding (Host header) or
+  cross-site (CSRF) weaknesses.
+
+Out of scope:
+
+- Issues that require an already-compromised local machine or account.
+- The behavior or vulnerabilities of the third-party sources you choose to
+  connect to.

datacharter-0.3.0/THIRD-PARTY-NOTICES.md

@@ -0,0 +1,56 @@
+# Third-party notices
+
+DataCharter is distributed under [Apache-2.0](LICENSE). It depends on, and its
+wheel bundles a pre-built web UI that includes, third-party open-source software.
+Each component remains under its own license; the copyright and license notices
+below are provided in acknowledgement. Full license texts are available in each
+project's repository.
+
+## Python runtime dependencies
+
+| Component | License |
+| --- | --- |
+| [DuckDB](https://github.com/duckdb/duckdb) | MIT |
+| [PyYAML](https://github.com/yaml/pyyaml) | MIT |
+| [pydantic](https://github.com/pydantic/pydantic) | MIT |
+| [FastAPI](https://github.com/fastapi/fastapi) | MIT |
+| [Starlette](https://github.com/encode/starlette) (via FastAPI) | BSD-3-Clause |
+| [uvicorn](https://github.com/encode/uvicorn) | BSD-3-Clause |
+| [httpx](https://github.com/encode/httpx) | BSD-3-Clause |
+| [python-dotenv](https://github.com/theskumar/python-dotenv) | BSD-3-Clause |
+| [python-multipart](https://github.com/Kludex/python-multipart) | Apache-2.0 |
+| [keyring](https://github.com/jaraco/keyring) | MIT |
+| [ruamel.yaml](https://sourceforge.net/projects/ruamel-yaml/) | MIT |
+
+Optional extra (`datacharter[snowflake]`):
+
+| Component | License |
+| --- | --- |
+| [snowflake-connector-python](https://github.com/snowflakedb/snowflake-connector-python) | Apache-2.0 |
+
+DuckDB extensions (BigQuery, SQL Server, Iceberg, Delta, httpfs, etc.) are fetched
+by DuckDB at runtime from its extension repositories and are not bundled here.
+
+## Bundled web UI (included in the wheel)
+
+| Component | License |
+| --- | --- |
+| [React](https://github.com/facebook/react) / react-dom | MIT |
+| [Monaco Editor](https://github.com/microsoft/monaco-editor) | MIT |
+| [@monaco-editor/react](https://github.com/suren-atoyan/monaco-react) | MIT |
+| [TanStack Table](https://github.com/TanStack/table) | MIT |
+| [TanStack Virtual](https://github.com/TanStack/virtual) | MIT |
+| [Vega](https://github.com/vega/vega) | BSD-3-Clause |
+| [Vega-Lite](https://github.com/vega/vega-lite) | BSD-3-Clause |
+| [vega-embed](https://github.com/vega/vega-embed) | BSD-3-Clause |
+
+## Development and CI tools (not distributed)
+
+Build and test tooling — Vite, TypeScript, pytest, pytest-asyncio, ruff, and
+[VidaiMock](https://github.com/vidaiUK/VidaiMock) (Apache-2.0, the mock LLM server
+used by the end-to-end tests) — is used to develop and test DataCharter and is
+not included in the distributed package.
+
+> A complete, auto-generated license bundle (with full texts) can be produced at
+> build time from `pip-licenses` and the npm `license-checker`; this file is the
+> curated summary.

{datacharter-0.2.0 → datacharter-0.3.0}/docs/_config.yml

@@ -15,4 +15,6 @@ exclude:
   - README.md
   - SECURITY_AUDIT.md
   - TUTORIAL_MODE.md
+  - ROADMAP-strategy.md
+  - LAUNCH.md
   - superpowers

{datacharter-0.2.0 → datacharter-0.3.0}/docs/about.md

@@ -3,7 +3,7 @@ title: About DataCharter
 description: Why contract-governed local data exploration exists.
 ---
 
-[Home](index.html) · [Quick start](quickstart.html) · [charter.yaml](charter-yaml.html) · [Sources](sources.html) · [Agent](agent.html) · [About](about.html) · [FAQ](faq.html)
+[Home](index.html) · [Quick start](quickstart.html) · [charter.yaml](charter-yaml.html) · [Sources](sources.html) · [Agent](agent.html) · [CLI](cli.html) · [MCP](mcp.html) · [About](about.html) · [FAQ](faq.html)
 
 ## The idea
 

{datacharter-0.2.0 → datacharter-0.3.0}/docs/agent.md

@@ -3,7 +3,7 @@ title: Agent modes
 description: Bring your own endpoint, run fully local, or skip the agent entirely.
 ---
 
-[Home](index.html) · [Quick start](quickstart.html) · [charter.yaml](charter-yaml.html) · [Sources](sources.html) · [Agent](agent.html) · [About](about.html) · [FAQ](faq.html)
+[Home](index.html) · [Quick start](quickstart.html) · [charter.yaml](charter-yaml.html) · [Sources](sources.html) · [Agent](agent.html) · [CLI](cli.html) · [MCP](mcp.html) · [About](about.html) · [FAQ](faq.html)
 
 DataCharter has an optional natural-language agent that turns a plain-language
 question into SQL against your sources. It is genuinely optional.