chartwright 0.1.0__tar.gz

chartwright-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

chartwright-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+Chartwright
+Copyright 2026 Debabrata Saha
+
+This product includes software developed as part of the Chartwright project
+(https://github.com/debabsah/chartwright).

chartwright-0.1.0/PKG-INFO

@@ -0,0 +1,189 @@
+Metadata-Version: 2.4
+Name: chartwright
+Version: 0.1.0
+Summary: Build, verify, and maintain Apache Superset dashboards from small spec files.
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/debabsah/chartwright
+Project-URL: Documentation, https://github.com/debabsah/chartwright/tree/main/docs
+Project-URL: Issues, https://github.com/debabsah/chartwright/issues
+Keywords: superset,apache-superset,dashboards,dashboards-as-code,business-intelligence
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Visualization
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: pydantic>=2.7
+Requires-Dist: requests>=2.31
+Requires-Dist: pyyaml>=6.0
+Provides-Extra: dev
+Requires-Dist: pytest>=8; extra == "dev"
+Provides-Extra: mcp
+Requires-Dist: mcp>=1.0; extra == "mcp"
+Dynamic: license-file
+
+# Chartwright
+
+A dashboard compiler for Apache Superset. Describe the dashboard once, in a
+small text file called a spec, and the `chartwright` command line creates it,
+verifies it, and keeps it that way.
+
+![An operations dashboard over NYC yellow-taxi data: KPI cards with unit subtitles, daily trend charts, an hour-by-weekday demand heatmap, a payment donut, borough and zone rankings, and a trip-distance histogram, behind a three-filter bar](https://raw.githubusercontent.com/debabsah/chartwright/main/docs/images/nyc-taxi-operations.png)
+
+*3.9 million yellow-taxi trips (NYC TLC trip records, May 2026), 11 verified
+charts, three filters, one `chartwright apply`. An AI wrote
+[the spec](https://github.com/debabsah/chartwright/blob/main/examples/nyc_taxi_operations.json) from a one-paragraph request:
+[the request and rebuild steps](https://github.com/debabsah/chartwright/blob/main/examples/README.md).*
+
+A dashboard that lives in a file gets the workflow code already has: review it
+in a pull request, rebuild it identically, diff it against what is live, and
+bring it back after a bad change. Write the spec yourself or ask an AI for one;
+either way, every dataset, column, and metric the spec names is confirmed to
+exist before anything is built, and every chart is checked to load with data
+after.
+
+## What a spec looks like
+
+```json
+{
+  "spec_version": "1",
+  "dashboard": {"title": "Sales Overview", "slug": "sales-overview"},
+  "charts": [
+    {
+      "name": "Total Sales",
+      "type": "big_number_total",
+      "dataset": {"database": "examples", "table": "cleaned_sales_data"},
+      "metric": "SUM(sales)"
+    },
+    {
+      "name": "Sales Over Time",
+      "type": "timeseries_line",
+      "dataset": {"database": "examples", "table": "cleaned_sales_data"},
+      "metrics": ["SUM(sales)"],
+      "time_column": "order_date"
+    }
+  ],
+  "layout": {"rows": [["Total Sales"], ["Sales Over Time"]]}
+}
+```
+
+`chartwright apply` on this file signs in to your Superset, confirms the
+`cleaned_sales_data` table and the `sales` and `order_date` columns exist,
+builds a KPI card above a line chart, and finishes by running each chart's
+query once to prove it shows data. A misspelled column or a missing table is a
+clear error naming the problem, before anything is created.
+
+## Quick start
+
+```bash
+pip install chartwright
+```
+
+Python 3.11 or newer; three dependencies; Windows, macOS, and Linux.
+
+Create `~/.config/chartwright/profiles.toml` pointing at your Superset:
+
+```toml
+[prod]
+base_url = "https://superset.your-company.com"
+username = "your-username"
+password_env = "CHARTWRIGHT_PROD_PASSWORD"
+```
+
+Point the example spec's `dataset` lines at a table your Superset already
+knows, save it as `sales_overview.json`, then:
+
+```bash
+chartwright check sales_overview.json --profile prod   # read-only: verify every reference
+chartwright apply sales_overview.json --profile prod   # build, import, verify
+```
+
+No Superset to point at? Clone this repo: `sandbox/up.sh` boots a disposable
+Superset 6.1.0 with example data on `localhost:8098` (Docker required;
+sign-in is admin/admin), and `tests/fixtures/kitchen_sink.json` applies to it
+as-is.
+
+## What you get
+
+- **Deterministic dashboards**: the same spec always produces the identical
+  dashboard. Diff it in git, review it in a PR.
+- **Verified at every step**: every reference is checked before anything is
+  written, and every chart's query runs once to prove it shows data; failures
+  say what went wrong and where.
+- **Dashboards as code, in both directions**: `chartwright decompile` turns any live
+  dashboard into a spec; `chartwright plan` shows what differs between the spec and
+  the live dashboard, ready as a CI gate; `chartwright compile` builds the import
+  bundle offline, no server needed.
+- **Safety built in**: every apply backs up the previous state first; a failed
+  apply restores it automatically; the tool only ever overwrites dashboards it
+  created, and a hand-built dashboard is adopted by decompiling it into a spec
+  first.
+- **The full design surface**: 14 chart types, metrics as you write them,
+  per-chart filters, a native filter bar, tabs, markdown notes, and layouts
+  you can draw as ASCII sketches.
+- **Environment promotion**: specs name their data (connection, schema,
+  table), so the same file applies to dev, staging, and production unchanged.
+
+Every capability, with the CLI verb reference: [docs/FEATURES.md](https://github.com/debabsah/chartwright/blob/main/docs/FEATURES.md).
+
+## Creating dashboards with AI
+
+- **Claude Code skill**: from a clone of this repo, `python install-skill.py`,
+  then ask for a dashboard in plain words; the AI writes the spec, and the
+  tool verifies and builds it.
+- **MCP server**: `chartwright-mcp` (installed with `pip install "chartwright[mcp]"`)
+  exposes six tools covering the whole lifecycle, usable from any MCP client.
+- **Open contract**: `chartwright schema` prints the spec's JSON Schema, so any LLM or
+  tool can generate valid specs.
+- **Guardrails**: the AI proposes; the tool verifies, using your own Superset
+  login. Verification reads names (datasets, columns, metrics), not rows.
+
+## Drawing layouts as text
+
+The spec's `sketch` is the dashboard's shape, drawn with characters that you
+and a model can both write: each letter is a chart, and repeating a sketch
+line makes its charts taller.
+
+```text
+KKKK LLLLLLLL
+.... LLLLLLLL
+```
+
+![A short chart beside one twice as tall](https://raw.githubusercontent.com/debabsah/chartwright/main/docs/images/sketches/taller.svg)
+
+`L` spans both lines, so it renders twice as tall as `K`; the dots keep the
+space under `K` deliberately empty. Every rule, drawn and explained:
+[docs/LAYOUT-GUIDE.md](https://github.com/debabsah/chartwright/blob/main/docs/LAYOUT-GUIDE.md).
+
+## Testing and evidence
+
+Every push runs 125 tests on Linux and Windows, plus the full pipeline (apply,
+lifecycle soak, stale-tab adversary, fault injection) against real Superset
+4.1.4, 5.0.0, and 6.1.0 containers. Chart options are checked against
+Superset's own source for every supported version, so a Superset change is
+caught in our tests before it reaches your dashboards.
+
+Full evidence: [docs/VERIFICATION.md](https://github.com/debabsah/chartwright/blob/main/docs/VERIFICATION.md). Source citations
+for every Superset behavior the tool relies on:
+[docs/CONTRACTS.md](https://github.com/debabsah/chartwright/blob/main/docs/CONTRACTS.md).
+
+## Documentation
+
+- [docs/FEATURES.md](https://github.com/debabsah/chartwright/blob/main/docs/FEATURES.md): every capability, with the CLI verb
+  reference
+- [docs/LAYOUT-GUIDE.md](https://github.com/debabsah/chartwright/blob/main/docs/LAYOUT-GUIDE.md): drawing layouts as text,
+  every rule illustrated
+- [docs/VERIFICATION.md](https://github.com/debabsah/chartwright/blob/main/docs/VERIFICATION.md): what is tested, what it
+  caught, and how to reproduce it
+- [docs/CONTRACTS.md](https://github.com/debabsah/chartwright/blob/main/docs/CONTRACTS.md): the Superset behaviors the tool
+  depends on, cited to source at each supported version
+
+---
+
+Apache Superset, Superset, and the Superset logo are trademarks of the Apache
+Software Foundation. No endorsement by the ASF is implied.

chartwright-0.1.0/README.md

@@ -0,0 +1,160 @@
+# Chartwright
+
+A dashboard compiler for Apache Superset. Describe the dashboard once, in a
+small text file called a spec, and the `chartwright` command line creates it,
+verifies it, and keeps it that way.
+
+![An operations dashboard over NYC yellow-taxi data: KPI cards with unit subtitles, daily trend charts, an hour-by-weekday demand heatmap, a payment donut, borough and zone rankings, and a trip-distance histogram, behind a three-filter bar](https://raw.githubusercontent.com/debabsah/chartwright/main/docs/images/nyc-taxi-operations.png)
+
+*3.9 million yellow-taxi trips (NYC TLC trip records, May 2026), 11 verified
+charts, three filters, one `chartwright apply`. An AI wrote
+[the spec](https://github.com/debabsah/chartwright/blob/main/examples/nyc_taxi_operations.json) from a one-paragraph request:
+[the request and rebuild steps](https://github.com/debabsah/chartwright/blob/main/examples/README.md).*
+
+A dashboard that lives in a file gets the workflow code already has: review it
+in a pull request, rebuild it identically, diff it against what is live, and
+bring it back after a bad change. Write the spec yourself or ask an AI for one;
+either way, every dataset, column, and metric the spec names is confirmed to
+exist before anything is built, and every chart is checked to load with data
+after.
+
+## What a spec looks like
+
+```json
+{
+  "spec_version": "1",
+  "dashboard": {"title": "Sales Overview", "slug": "sales-overview"},
+  "charts": [
+    {
+      "name": "Total Sales",
+      "type": "big_number_total",
+      "dataset": {"database": "examples", "table": "cleaned_sales_data"},
+      "metric": "SUM(sales)"
+    },
+    {
+      "name": "Sales Over Time",
+      "type": "timeseries_line",
+      "dataset": {"database": "examples", "table": "cleaned_sales_data"},
+      "metrics": ["SUM(sales)"],
+      "time_column": "order_date"
+    }
+  ],
+  "layout": {"rows": [["Total Sales"], ["Sales Over Time"]]}
+}
+```
+
+`chartwright apply` on this file signs in to your Superset, confirms the
+`cleaned_sales_data` table and the `sales` and `order_date` columns exist,
+builds a KPI card above a line chart, and finishes by running each chart's
+query once to prove it shows data. A misspelled column or a missing table is a
+clear error naming the problem, before anything is created.
+
+## Quick start
+
+```bash
+pip install chartwright
+```
+
+Python 3.11 or newer; three dependencies; Windows, macOS, and Linux.
+
+Create `~/.config/chartwright/profiles.toml` pointing at your Superset:
+
+```toml
+[prod]
+base_url = "https://superset.your-company.com"
+username = "your-username"
+password_env = "CHARTWRIGHT_PROD_PASSWORD"
+```
+
+Point the example spec's `dataset` lines at a table your Superset already
+knows, save it as `sales_overview.json`, then:
+
+```bash
+chartwright check sales_overview.json --profile prod   # read-only: verify every reference
+chartwright apply sales_overview.json --profile prod   # build, import, verify
+```
+
+No Superset to point at? Clone this repo: `sandbox/up.sh` boots a disposable
+Superset 6.1.0 with example data on `localhost:8098` (Docker required;
+sign-in is admin/admin), and `tests/fixtures/kitchen_sink.json` applies to it
+as-is.
+
+## What you get
+
+- **Deterministic dashboards**: the same spec always produces the identical
+  dashboard. Diff it in git, review it in a PR.
+- **Verified at every step**: every reference is checked before anything is
+  written, and every chart's query runs once to prove it shows data; failures
+  say what went wrong and where.
+- **Dashboards as code, in both directions**: `chartwright decompile` turns any live
+  dashboard into a spec; `chartwright plan` shows what differs between the spec and
+  the live dashboard, ready as a CI gate; `chartwright compile` builds the import
+  bundle offline, no server needed.
+- **Safety built in**: every apply backs up the previous state first; a failed
+  apply restores it automatically; the tool only ever overwrites dashboards it
+  created, and a hand-built dashboard is adopted by decompiling it into a spec
+  first.
+- **The full design surface**: 14 chart types, metrics as you write them,
+  per-chart filters, a native filter bar, tabs, markdown notes, and layouts
+  you can draw as ASCII sketches.
+- **Environment promotion**: specs name their data (connection, schema,
+  table), so the same file applies to dev, staging, and production unchanged.
+
+Every capability, with the CLI verb reference: [docs/FEATURES.md](https://github.com/debabsah/chartwright/blob/main/docs/FEATURES.md).
+
+## Creating dashboards with AI
+
+- **Claude Code skill**: from a clone of this repo, `python install-skill.py`,
+  then ask for a dashboard in plain words; the AI writes the spec, and the
+  tool verifies and builds it.
+- **MCP server**: `chartwright-mcp` (installed with `pip install "chartwright[mcp]"`)
+  exposes six tools covering the whole lifecycle, usable from any MCP client.
+- **Open contract**: `chartwright schema` prints the spec's JSON Schema, so any LLM or
+  tool can generate valid specs.
+- **Guardrails**: the AI proposes; the tool verifies, using your own Superset
+  login. Verification reads names (datasets, columns, metrics), not rows.
+
+## Drawing layouts as text
+
+The spec's `sketch` is the dashboard's shape, drawn with characters that you
+and a model can both write: each letter is a chart, and repeating a sketch
+line makes its charts taller.
+
+```text
+KKKK LLLLLLLL
+.... LLLLLLLL
+```
+
+![A short chart beside one twice as tall](https://raw.githubusercontent.com/debabsah/chartwright/main/docs/images/sketches/taller.svg)
+
+`L` spans both lines, so it renders twice as tall as `K`; the dots keep the
+space under `K` deliberately empty. Every rule, drawn and explained:
+[docs/LAYOUT-GUIDE.md](https://github.com/debabsah/chartwright/blob/main/docs/LAYOUT-GUIDE.md).
+
+## Testing and evidence
+
+Every push runs 125 tests on Linux and Windows, plus the full pipeline (apply,
+lifecycle soak, stale-tab adversary, fault injection) against real Superset
+4.1.4, 5.0.0, and 6.1.0 containers. Chart options are checked against
+Superset's own source for every supported version, so a Superset change is
+caught in our tests before it reaches your dashboards.
+
+Full evidence: [docs/VERIFICATION.md](https://github.com/debabsah/chartwright/blob/main/docs/VERIFICATION.md). Source citations
+for every Superset behavior the tool relies on:
+[docs/CONTRACTS.md](https://github.com/debabsah/chartwright/blob/main/docs/CONTRACTS.md).
+
+## Documentation
+
+- [docs/FEATURES.md](https://github.com/debabsah/chartwright/blob/main/docs/FEATURES.md): every capability, with the CLI verb
+  reference
+- [docs/LAYOUT-GUIDE.md](https://github.com/debabsah/chartwright/blob/main/docs/LAYOUT-GUIDE.md): drawing layouts as text,
+  every rule illustrated
+- [docs/VERIFICATION.md](https://github.com/debabsah/chartwright/blob/main/docs/VERIFICATION.md): what is tested, what it
+  caught, and how to reproduce it
+- [docs/CONTRACTS.md](https://github.com/debabsah/chartwright/blob/main/docs/CONTRACTS.md): the Superset behaviors the tool
+  depends on, cited to source at each supported version
+
+---
+
+Apache Superset, Superset, and the Superset logo are trademarks of the Apache
+Software Foundation. No endorsement by the ASF is implied.

chartwright-0.1.0/chartwright/__init__.py

@@ -0,0 +1,7 @@
+"""Superset Dashboard Compiler.
+
+Typed spec -> deterministic compiler -> guaranteed-correct Superset dashboard.
+The LLM is an untrusted parser at the edge; the guarantee lives in typed code.
+"""
+
+__version__ = "0.1.0"

chartwright-0.1.0/chartwright/absorb.py

@@ -0,0 +1,93 @@
+"""Absorb UI height polish back into the spec file: the scalpel to
+decompile's bulldozer.
+
+Workflow this serves (the owner's ruling, 2026-07-11): the sketch gets a
+dashboard 90-95% built in one shot; the last few percent of fine-grain sizing
+happens by hand in the Superset UI. Without absorb, the next `chartwright apply`
+rebuilds the layout from the spec and destroys that polish. `chartwright absorb`
+reads the LIVE dashboard's geometry and patches ONLY per-chart heights into
+the existing spec file; sketch, legend, metrics, structure untouched.
+
+Heights only, by design: Superset widths ARE twelfths, so the UI cannot
+express any width the sketch can't; width changes belong in the drawing.
+Width drift is therefore REPORTED as advice, never written. Heights are where
+the UI has finer resolution (8px) than the sketch quantum (40px); absorbed
+values are written as fractional 40px units in 0.2 steps (8px), so the
+polished geometry round-trips EXACTLY through the next apply.
+"""
+
+from __future__ import annotations
+
+import copy
+from dataclasses import asdict, dataclass, field
+
+from . import ids
+from .compiler import ROW_UNITS_PER_SPEC_UNIT, _position
+from .spec import DashboardSpec
+
+
+@dataclass
+class AbsorbReport:
+    ok: bool
+    absorbed: list[dict] = field(default_factory=list)      # {chart, from_px, to_px, height}
+    width_advice: list[dict] = field(default_factory=list)  # {chart, spec_width, live_width}
+    unmatched_live: list[str] = field(default_factory=list)
+    detail: str | None = None
+
+    def to_json(self) -> str:
+        return json.dumps({"stage": "absorb", **asdict(self)}, indent=2)
+
+
+def _exact_units(row_units: int) -> float | int:
+    """Superset row units (8px) -> spec units (40px), exactly representable."""
+    units = row_units / ROW_UNITS_PER_SPEC_UNIT
+    return int(units) if units.is_integer() else round(units, 1)
+
+
+def absorb_heights(spec: DashboardSpec, spec_data: dict, live_position: dict) -> tuple[dict, AbsorbReport]:
+    """Pure core: returns (patched copy of spec_data, report). spec_data is the
+    raw JSON the spec file holds; only charts[*].height values are touched."""
+    report = AbsorbReport(ok=True)
+    slug = spec.dashboard.slug
+
+    compiled = {
+        v["meta"]["uuid"]: v["meta"]
+        for v in _position(spec).values()
+        if isinstance(v, dict) and v.get("type") == "CHART"
+    }
+    live = {
+        v["meta"]["uuid"]: v["meta"]
+        for v in live_position.values()
+        if isinstance(v, dict) and v.get("type") == "CHART" and (v.get("meta") or {}).get("uuid")
+    }
+    report.unmatched_live = sorted(
+        (m.get("sliceName") or u) for u, m in live.items() if u not in compiled
+    )
+
+    out = copy.deepcopy(spec_data)
+    charts_by_name = {c["name"]: c for c in out.get("charts", [])}
+
+    for chart in spec.charts:
+        u = str(ids.chart_uuid(slug, chart.name))
+        live_meta = live.get(u)
+        if live_meta is None:
+            continue  # chart not on the live board (e.g. never applied); nothing to absorb
+        want, have = compiled[u], live_meta
+        if have.get("width") != want["width"]:
+            report.width_advice.append({
+                "chart": chart.name,
+                "spec_width": want["width"],
+                "live_width": have.get("width"),
+                "note": "widths are twelfths; redraw the sketch line (absorb writes heights only)",
+            })
+        live_h = have.get("height")
+        if not isinstance(live_h, int) or live_h == want["height"]:
+            continue
+        charts_by_name[chart.name]["height"] = _exact_units(live_h)
+        report.absorbed.append({
+            "chart": chart.name,
+            "from_px": want["height"] * 8,
+            "to_px": live_h * 8,
+            "height": charts_by_name[chart.name]["height"],
+        })
+    return out, report