airflow-dagsmith 0.1.0__tar.gz

airflow_dagsmith-0.1.0/.github/FUNDING.yml

@@ -0,0 +1,2 @@
+# Shown as the "Sponsor" button on the public GitHub repository.
+buy_me_a_coffee: byteway

airflow_dagsmith-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,44 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  backend:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Install backend (without Airflow — unit tests run standalone)
+        run: |
+          python -m pip install --upgrade pip
+          pip install fastapi httpx pytest sqlalchemy alembic pydantic libcst ruff
+          pip install -e . --no-deps
+      - name: Ruff
+        run: ruff check src tests
+      - name: Pytest
+        run: pytest -q
+
+  frontend:
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: frontend
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "22"
+          cache: npm
+          cache-dependency-path: frontend/package-lock.json
+      - run: npm ci
+      - name: Typecheck
+        run: npm run lint
+      - name: Unit tests
+        run: npm test
+      - name: Build bundle
+        run: npm run build

airflow_dagsmith-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,55 @@
+name: Release to PyPI
+
+# Publishes via PyPI Trusted Publishing (OIDC) — no API tokens stored anywhere.
+# Triggered by pushing a version tag, e.g.:  git tag v0.1.0 && git push --tags
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: "22"
+          cache: npm
+          cache-dependency-path: frontend/package-lock.json
+      - name: Build the UI bundle
+        working-directory: frontend
+        run: |
+          npm ci
+          npm run build
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+      - name: Build sdist + wheel
+        run: |
+          python -m pip install --upgrade build
+          python -m build
+      - name: Verify the wheel contains the UI bundle
+        run: |
+          python -m zipfile -l dist/*.whl | grep "dagsmith/static/dagsmith.js" \
+            || { echo "UI bundle missing from the wheel!"; exit 1; }
+
+      - uses: actions/upload-artifact@v4
+        with:
+          name: dist
+          path: dist/
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write   # required for PyPI Trusted Publishing (OIDC)
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: dist
+          path: dist/
+      - uses: pypa/gh-action-pypi-publish@release/v1

airflow_dagsmith-0.1.0/.gitignore

@@ -0,0 +1,30 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.venv/
+dist/
+build/
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+
+# Frontend
+frontend/node_modules/
+frontend/dist/
+
+# Built frontend bundle (committed only on release)
+src/dagsmith/static/*
+!src/dagsmith/static/.gitkeep
+
+# Dev environment
+dev/pgdata/
+dev/logs/
+# runtime sandbox: DagSmith deploys here and it is its own git repo
+# (git-on-deploy testing); seed it from dev/seed-dags/
+dev/dags/
+
+# OS / editors
+.DS_Store
+.idea/
+.vscode/

airflow_dagsmith-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.

airflow_dagsmith-0.1.0/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.4
+Name: airflow-dagsmith
+Version: 0.1.0
+Summary: Visual block-based and code DAG editor inside the Apache Airflow 3 UI
+Project-URL: Homepage, https://github.com/byteway-pl/DagSmith
+Project-URL: Issues, https://github.com/byteway-pl/DagSmith/issues
+Author: Adrian Galik
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+Classifier: Framework :: Apache Airflow
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.10
+Requires-Dist: alembic>=1.13
+Requires-Dist: apache-airflow>=3.1.0
+Requires-Dist: libcst>=1.1
+Requires-Dist: pydantic>=2.0
+Requires-Dist: sqlalchemy>=1.4
+Provides-Extra: dev
+Requires-Dist: httpx>=0.27; extra == 'dev'
+Requires-Dist: mypy>=1.10; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Requires-Dist: testcontainers[postgres]>=4; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# DagSmith
+
+**A visual, block-based DAG editor for Apache Airflow 3 — right inside the Airflow UI.**
+
+DagSmith is an Airflow plugin (Airflow ≥ 3.1) that adds a full DAG editor to the
+Airflow web UI:
+
+- 🧱 **Visual editor** — build DAGs from blocks: drag operators from a searchable
+  palette onto a canvas, connect them with dependency edges (tasks *and* TaskGroups),
+  configure parameters in typed forms (key:value editors for dicts, a rich-text editor
+  for HTML fields, connection pickers for `conn_id`s, a cron builder for schedules).
+- ✍️ **Code editor** — edit the `.py` files in CodeMirror with syntax and import
+  validation before anything is deployed.
+- 🔁 **Two-way sync, code is the source of truth** — canvas edits are applied to your
+  file as *minimal, surgical changes* (via [libcst](https://github.com/Instagram/LibCST));
+  comments and formatting you didn't touch stay byte-for-byte identical. Editing the
+  code updates the canvas. Dynamic constructs (loops, `.partial().expand()`) appear as
+  code-only blocks instead of breaking the parser.
+- 🧰 **Auto-generated operator palette** — installed provider packages are introspected
+  (operators, sensors, their `__init__` signatures across the class hierarchy), so
+  hundreds of blocks with typed parameter forms appear without any manual definitions.
+- 💾 **Draft → Deploy** — work-in-progress is saved as versioned drafts in the Airflow
+  metadata database (with autosave, history, diffs and restore). The live `.py` file
+  changes **only** when you hit Deploy, after validation, with a backup and conflict
+  detection. The scheduler never sees half-finished work.
+- 👥 **Teams** — give each team a directory in a DAG bundle and a git repository:
+  members-only editing, per-DAG reassignment by admins, team-tagged DAGs, and a
+  *Commit & push* button (GitHub/GitLab) plus optional push-on-deploy.
+- 🔒 **Safety by default** — deploy is disabled until explicitly enabled, all endpoints
+  are authorized through the Airflow Auth Manager, user code is only ever executed in
+  an isolated subprocess, every path is confined to the bundle root, and every deploy
+  is audit-logged.
+
+## Requirements
+
+| Component | Version |
+|---|---|
+| Apache Airflow | **≥ 3.1** (uses the `react_apps` + `fastapi_apps` plugin APIs; no Airflow 2.x support) |
+| Python | ≥ 3.10 |
+| Metadata DB | PostgreSQL recommended (DagSmith stores drafts in its own `dagsmith_*` tables) |
+| File access | to deploy, the Airflow api-server needs write access to the DAG bundle directory; working on drafts needs no file access at all |
+
+## Installation
+
+```bash
+pip install airflow-dagsmith   # in the environment running the Airflow api-server
+```
+
+The plugin registers itself via the `airflow.plugins` entry point — don't copy anything
+into `$AIRFLOW_HOME/plugins`. After restarting the api-server, **DagSmith** appears in
+the Airflow navigation. Its `dagsmith_*` tables are created automatically on startup
+(or run `python -m dagsmith db upgrade` manually).
+
+### Enabling deploy
+
+For safety, writing `.py` files is **off by default** — without it DagSmith works in
+read-and-draft mode. Enable it consciously:
+
+```ini
+[dagsmith]
+deploy_enabled = True
+# optional hardening / team split:
+# editors   = data-platform-team     # who can create and edit drafts
+# deployers = admin                  # who can write .py files
+# admins    = admin                  # who manages teams
+# git_commit = True                  # commit to the bundle checkout on deploy
+```
+
+(or `AIRFLOW__DAGSMITH__DEPLOY_ENABLED=True` etc.)
+
+> ⚠️ **Security note:** deploying DAGs from the UI is equivalent to executing arbitrary
+> code in your Airflow environment — exactly like shipping a DAG file any other way.
+> Enable `deploy_enabled` only with proper access control on the Airflow UI. Import
+> validation executes the file's top level in an isolated, time-limited subprocess.
+
+## How it works
+
+```
+Airflow UI ─▶ react_app "DagSmith" (React Flow canvas + CodeMirror)
+                    │  REST /dagsmith/api/v1 (Airflow JWT)
+                    ▼
+             FastAPI app inside the api-server
+                    │  parse (libcst) / codegen / validation (subprocess)
+       ┌────────────┴────────────┐
+  Save / autosave           Deploy (validated)
+       ▼                        ▼
+ Airflow metadata DB       .py files in the DAG bundle
+ (draft versions,          (atomic write, backup,
+  canvas layout)            conflict detection, git)
+```
+
+Three tiers of support for existing code:
+
+1. **DAGs created in DagSmith** — full visual editing with remembered layout.
+2. **Typical hand-written DAGs** (`with DAG(...)`, `@dag`, `@task`, `>>`, `chain()`,
+   nested TaskGroups, edge `Label`s) — full visual editing without touching your
+   formatting.
+3. **Dynamic constructs** (task-generating loops, `.expand()`) — shown on the canvas as
+   read-only blocks, editable in the code view.
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest                                # backend (incl. byte-exact round-trip corpus)
+cd frontend && npm install
+npm run build                         # UMD bundle -> src/dagsmith/static/
+npm test && npm run lint
+```
+
+The frontend follows Airflow's AIP-68 react-plugin contract (single UMD bundle, host
+provides React); everything ships inside the bundle — no CDNs.
+
+## Support the project
+
+If DagSmith saves you time, you can [buy me a coffee](https://buymeacoffee.com/byteway) ☕
+
+## License
+
+[Apache-2.0](LICENSE)

airflow_dagsmith-0.1.0/README.md

@@ -0,0 +1,120 @@
+# DagSmith
+
+**A visual, block-based DAG editor for Apache Airflow 3 — right inside the Airflow UI.**
+
+DagSmith is an Airflow plugin (Airflow ≥ 3.1) that adds a full DAG editor to the
+Airflow web UI:
+
+- 🧱 **Visual editor** — build DAGs from blocks: drag operators from a searchable
+  palette onto a canvas, connect them with dependency edges (tasks *and* TaskGroups),
+  configure parameters in typed forms (key:value editors for dicts, a rich-text editor
+  for HTML fields, connection pickers for `conn_id`s, a cron builder for schedules).
+- ✍️ **Code editor** — edit the `.py` files in CodeMirror with syntax and import
+  validation before anything is deployed.
+- 🔁 **Two-way sync, code is the source of truth** — canvas edits are applied to your
+  file as *minimal, surgical changes* (via [libcst](https://github.com/Instagram/LibCST));
+  comments and formatting you didn't touch stay byte-for-byte identical. Editing the
+  code updates the canvas. Dynamic constructs (loops, `.partial().expand()`) appear as
+  code-only blocks instead of breaking the parser.
+- 🧰 **Auto-generated operator palette** — installed provider packages are introspected
+  (operators, sensors, their `__init__` signatures across the class hierarchy), so
+  hundreds of blocks with typed parameter forms appear without any manual definitions.
+- 💾 **Draft → Deploy** — work-in-progress is saved as versioned drafts in the Airflow
+  metadata database (with autosave, history, diffs and restore). The live `.py` file
+  changes **only** when you hit Deploy, after validation, with a backup and conflict
+  detection. The scheduler never sees half-finished work.
+- 👥 **Teams** — give each team a directory in a DAG bundle and a git repository:
+  members-only editing, per-DAG reassignment by admins, team-tagged DAGs, and a
+  *Commit & push* button (GitHub/GitLab) plus optional push-on-deploy.
+- 🔒 **Safety by default** — deploy is disabled until explicitly enabled, all endpoints
+  are authorized through the Airflow Auth Manager, user code is only ever executed in
+  an isolated subprocess, every path is confined to the bundle root, and every deploy
+  is audit-logged.
+
+## Requirements
+
+| Component | Version |
+|---|---|
+| Apache Airflow | **≥ 3.1** (uses the `react_apps` + `fastapi_apps` plugin APIs; no Airflow 2.x support) |
+| Python | ≥ 3.10 |
+| Metadata DB | PostgreSQL recommended (DagSmith stores drafts in its own `dagsmith_*` tables) |
+| File access | to deploy, the Airflow api-server needs write access to the DAG bundle directory; working on drafts needs no file access at all |
+
+## Installation
+
+```bash
+pip install airflow-dagsmith   # in the environment running the Airflow api-server
+```
+
+The plugin registers itself via the `airflow.plugins` entry point — don't copy anything
+into `$AIRFLOW_HOME/plugins`. After restarting the api-server, **DagSmith** appears in
+the Airflow navigation. Its `dagsmith_*` tables are created automatically on startup
+(or run `python -m dagsmith db upgrade` manually).
+
+### Enabling deploy
+
+For safety, writing `.py` files is **off by default** — without it DagSmith works in
+read-and-draft mode. Enable it consciously:
+
+```ini
+[dagsmith]
+deploy_enabled = True
+# optional hardening / team split:
+# editors   = data-platform-team     # who can create and edit drafts
+# deployers = admin                  # who can write .py files
+# admins    = admin                  # who manages teams
+# git_commit = True                  # commit to the bundle checkout on deploy
+```
+
+(or `AIRFLOW__DAGSMITH__DEPLOY_ENABLED=True` etc.)
+
+> ⚠️ **Security note:** deploying DAGs from the UI is equivalent to executing arbitrary
+> code in your Airflow environment — exactly like shipping a DAG file any other way.
+> Enable `deploy_enabled` only with proper access control on the Airflow UI. Import
+> validation executes the file's top level in an isolated, time-limited subprocess.
+
+## How it works
+
+```
+Airflow UI ─▶ react_app "DagSmith" (React Flow canvas + CodeMirror)
+                    │  REST /dagsmith/api/v1 (Airflow JWT)
+                    ▼
+             FastAPI app inside the api-server
+                    │  parse (libcst) / codegen / validation (subprocess)
+       ┌────────────┴────────────┐
+  Save / autosave           Deploy (validated)
+       ▼                        ▼
+ Airflow metadata DB       .py files in the DAG bundle
+ (draft versions,          (atomic write, backup,
+  canvas layout)            conflict detection, git)
+```
+
+Three tiers of support for existing code:
+
+1. **DAGs created in DagSmith** — full visual editing with remembered layout.
+2. **Typical hand-written DAGs** (`with DAG(...)`, `@dag`, `@task`, `>>`, `chain()`,
+   nested TaskGroups, edge `Label`s) — full visual editing without touching your
+   formatting.
+3. **Dynamic constructs** (task-generating loops, `.expand()`) — shown on the canvas as
+   read-only blocks, editable in the code view.
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest                                # backend (incl. byte-exact round-trip corpus)
+cd frontend && npm install
+npm run build                         # UMD bundle -> src/dagsmith/static/
+npm test && npm run lint
+```
+
+The frontend follows Airflow's AIP-68 react-plugin contract (single UMD bundle, host
+provides React); everything ships inside the bundle — no CDNs.
+
+## Support the project
+
+If DagSmith saves you time, you can [buy me a coffee](https://buymeacoffee.com/byteway) ☕
+
+## License
+
+[Apache-2.0](LICENSE)

airflow_dagsmith-0.1.0/frontend/index.html

@@ -0,0 +1,12 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <title>DagSmith (dev)</title>
+  </head>
+  <body>
+    <div id="root"></div>
+    <script type="module" src="/src/dev.tsx"></script>
+  </body>
+</html>