dcmassist 0.1.15__tar.gz

dcmassist-0.1.15/.github/workflows/ci.yml

@@ -0,0 +1,155 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  workflow_dispatch:
+    inputs:
+      release_notes:
+        description: "Text to prepend to the GitHub release notes"
+        required: false
+        default: ""
+
+jobs:
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+    runs-on: ${{ matrix.os }}
+
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v8.1.0
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        run: uv python install ${{ matrix.python-version }}
+
+      - name: Install dependencies
+        run: uv sync --all-extras --python ${{ matrix.python-version }}
+
+      - name: Ruff format
+        run: uv run --python ${{ matrix.python-version }} ruff format --check src/ tests/
+
+      - name: Ruff check
+        run: uv run --python ${{ matrix.python-version }} ruff check src/ tests/
+
+      - name: Run tests
+        run: uv run --python ${{ matrix.python-version }} pytest tests/ -v
+
+  build:
+    needs: test
+    runs-on: ubuntu-latest
+    outputs:
+      version: ${{ steps.stamp.outputs.version }}
+
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v8.1.0
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        run: uv python install 3.12
+
+      - name: Install dependencies
+        run: uv sync --all-extras
+
+      - name: Stamp version
+        id: stamp
+        env:
+          RUN_NUMBER: ${{ github.run_number }}
+        run: |
+          python - <<'PY'
+          import os, re, pathlib
+          path = pathlib.Path("pyproject.toml")
+          text = path.read_text()
+          match = re.search(r'^version = "(\d+\.\d+)"', text, re.MULTILINE)
+          if not match:
+              raise SystemExit("pyproject.toml must contain 'version = \"MAJOR.MINOR\"'")
+          base = match.group(1)
+          full = f'{base}.{os.environ["RUN_NUMBER"]}'
+          path.write_text(
+              re.sub(
+                  r'^version = "\d+\.\d+"',
+                  f'version = "{full}"',
+                  text,
+                  count=1,
+                  flags=re.MULTILINE,
+              )
+          )
+          print(f"Stamped version: {full}")
+          with open(os.environ["GITHUB_OUTPUT"], "a") as fh:
+              fh.write(f"version={full}\n")
+          PY
+
+      - name: Build sdist and wheel
+        run: uv build
+
+      - name: Upload build artifacts
+        uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+
+  publish:
+    needs: build
+    if: github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+
+    steps:
+      - name: Download build artifacts
+        uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+
+      - name: Publish to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1
+
+  release:
+    needs: [build, publish]
+    if: github.event_name == 'workflow_dispatch'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Download build artifacts
+        uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+
+      - name: Create GitHub release
+        env:
+          GH_TOKEN: ${{ github.token }}
+          VERSION: ${{ needs.build.outputs.version }}
+          RELEASE_NOTES: ${{ inputs.release_notes }}
+        run: |
+          pypi_line="Published to PyPI: https://pypi.org/project/dcmassist/${VERSION}/"
+          if [ -n "${RELEASE_NOTES}" ]; then
+            notes="${RELEASE_NOTES}"$'\n\n'"${pypi_line}"
+          else
+            notes="${pypi_line}"
+          fi
+          gh release create "v${VERSION}" \
+            --target "${GITHUB_SHA}" \
+            --title "v${VERSION}" \
+            --notes "${notes}" \
+            dist/*

dcmassist-0.1.15/.gitignore

@@ -0,0 +1,224 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+# dcmassist default output folder
+out/
+
+# Claude Code local settings
+.claude/

dcmassist-0.1.15/.pre-commit-config.yaml

@@ -0,0 +1,17 @@
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.11
+    hooks:
+      - id: ruff-format
+        args: [src/, tests/]
+      - id: ruff
+        args: [--fix, src/, tests/]
+
+  - repo: local
+    hooks:
+      - id: mypy
+        name: mypy
+        entry: uv run mypy src/
+        language: system
+        types: [python]
+        pass_filenames: false

dcmassist-0.1.15/.python-version

@@ -0,0 +1 @@
+3.12

dcmassist-0.1.15/CLAUDE.md

@@ -0,0 +1,75 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project
+
+`dcmassist` is a CLI that exports Snowflake object definitions (tables, views, schemas, stages, …) into the on-disk layout expected by a Snowflake DCM (Declarative Change Management) project: `manifest.yml`, `Makefile`, `sources/definitions/<type>.sql`, and optionally `sources/macros/<type>.sql`.
+
+The exported DDL is committed to a DCM project (i.e. git). Stage DDL is synthesized from `DESC STAGE` and **must never include AWS credentials** — credentials belong to the storage integration, not the stage.
+
+## Commands
+
+The project uses `uv` for everything; do not invoke `pip` or `python` directly.
+
+| Task | Command |
+|------|---------|
+| Run the CLI | `uv run dcmassist export --database <DB> [--force]` |
+| Run all tests | `uv run pytest` |
+| Run one file | `uv run pytest tests/test_orchestrator.py -v` |
+| Run one test | `uv run pytest tests/test_orchestrator.py::test_export_writes_full_layout -v` |
+| Lint | `uv run ruff check src tests` |
+| Format check | `uv run ruff format --check src tests` |
+| Type check | `uv run mypy src` |
+
+A pre-commit hook runs `ruff format`, `ruff` (with `--fix`), and `mypy src` across the whole tree on every commit. **Never bypass it with `--no-verify`** — if a hook fails, fix the underlying issue. If a refactor breaks a different file's call site, that's a sign two changes need to land in one commit (this has happened before with the orchestrator/render and orchestrator/status pairs).
+
+The hook does NOT run pytest — run it manually before committing.
+
+## Architecture
+
+### Pipeline (orchestrator-driven)
+
+`cli.py` builds a frozen `Config`, then `orchestrator.export(cfg)` runs the entire pipeline:
+
+1. `resolve_objects_per_file()` — read `DCMASSIST_EXPORT_OBJECTS_PER_FILE` BEFORE touching the output folder (a bad value must not blow away the user's directory).
+2. `prepare_out_folder()` — refuse non-empty unless `--force`; clear and recreate.
+3. Open `RunLog` at `<out>/dcmassist.log` and dump every Config field so users see (and discover) available options.
+4. Inside a `StatusDashboard` (Rich `Live` panel), connect to Snowflake and iterate `filter_types(cfg)`.
+5. For each type, dispatch to its plugin: `discover()` → per-FQN `get_ddl()` → `to_define_and_invocation()`.
+6. Chunk per-type blocks via `chunk_blocks()` into `dict[filename, body]` keyed by FULL filename (`table.sql`, `table2.sql`, …). The first chunk keeps the unsuffixed name so small exports look identical to before chunking existed.
+7. `write_outputs()` writes the dict to disk. It is mechanical — naming logic lives in the orchestrator; macros are still keyed by slug.
+
+Exit codes: `0` ok, `4` exported nothing but had errors, `5` config/setup error (bad env var or non-empty out folder).
+
+### Plugin system (`src/dcmassist/objects/`)
+
+Plugins are auto-discovered: `objects/__init__.py:build_registry()` imports every non-underscore module and calls `registry.register(module.plugin)`. `_unimplemented.py` is a special case that registers a list of stub plugins for types DCM supports but dcmassist doesn't yet handle.
+
+To add a new v1 type: create `objects/<type>.py`, subclass `V1ObjectPlugin` from `_base.py`, set `type_name`, `file_slug`, `SHOW_FORM`, `GET_DDL_TYPE`, `MACRO_BODY`, instantiate as module-level `plugin`. Add the canonical name to `V1_TYPES` in `types.py`.
+
+`V1ObjectPlugin` (`objects/_base.py`) implements the standard recipe: schema-iterated `SHOW` discovery, `GET_DDL(<TYPE>, <quoted_fqn>, TRUE)`, and a rewrite chain (`create_to_define` → `inject_comment_if_missing` → `parameterise_database`). Override only what's special. `Schema` and `Stage` synthesize their DDL directly from `SHOW`/`DESC STAGE` rows (see `_schema_ddl.py`, `_stage_ddl.py`) because `GET_DDL` either hangs (recursive Schema) or is unsupported (Stage).
+
+### Snowflake quirks worth knowing
+
+- `SHOW … IN DATABASE` is capped at 10K rows. Use `paginated_show()` from `objects/_show_paging.py`, which appends `LIMIT N FROM '<last_name>'`.
+- The cursor is forced to `DictCursor` in `connection.py`; `_rows_to_fqns` rejects non-dict rows defensively.
+- Identifiers must be quoted in `GET_DDL`/`DESC STAGE` (see `FQN.quoted` in `types.py`) — leading-digit and lowercase names break otherwise.
+- `GET_DDL(..., TRUE)` returns fully-qualified names; `parameterise_database` then rewrites the literal database to `{{ database }}` so the same export can be run against multiple environments.
+- The error string `002003 / "does not exist or not authorized"` is treated as a non-fatal `skipped_missing` count — common in shared databases where the role lacks privileges on a few objects.
+- `Database` is intentionally NOT in `V1_TYPES` — DCM rejects `DEFINE DATABASE` for the project's parent database. The Makefile prints an analogous warning for the parent schema (which the exporter can't auto-detect).
+
+### Status & logging split
+
+- `StatusDashboard` (`status.py`) — Rich `Live` panel on stderr, transient (disappears at end). Silent on non-TTY, `NO_COLOR=1`, or `DCMASSIST_NO_STATUS=1`. `.log()` writes above the panel; falls back to plain stderr when disabled so warnings still surface in CI.
+- `RunLog` (`log.py`) — per-run timestamped log file at `<out-folder>/dcmassist.log`. Truncated on each run. This is what users tail when something goes wrong.
+
+The dashboard answers "what's happening right now"; the log answers "what happened to which object and why".
+
+## Conventions
+
+- Default to no comments. Add one only when the **why** is non-obvious (a Snowflake quirk, a hidden invariant, a workaround for a specific error). Don't comment what well-named code already shows.
+- Module docstrings should explain why the module exists, not list its contents.
+- Don't add backwards-compatibility shims, dead defensive code, or feature flags for hypothetical futures. The codebase is pre-1.0 and prefers clean breaks over migration scaffolding.
+- Plans and specs live under `docs/superpowers/plans/` and `docs/superpowers/specs/` and are written via the `superpowers:writing-plans` and `superpowers:brainstorming` skills.
+- The tool was renamed from `dcmexporter` → `dcmassist`. Older plans/specs under `docs/superpowers/` still use the old name (they're snapshots) — don't update them retroactively.

dcmassist-0.1.15/CONTRIBUTING.md

@@ -0,0 +1,132 @@
+# Contributing to dcmassist
+
+Thanks for your interest in contributing. This document covers everything you need to make a clean, mergeable change.
+
+## Setup
+
+Requires Python ≥ 3.10 and [`uv`](https://docs.astral.sh/uv/).
+
+```bash
+git clone https://github.com/jamiekt/dcmassist
+cd dcmassist
+uv sync                         # installs runtime + dev deps + the package itself, editable
+uv run pre-commit install       # wires the pre-commit hook
+```
+
+`uv` is the only supported tool — please don't introduce `pip`, `python -m venv`, or `poetry` into the workflow.
+
+## Common commands
+
+| Task | Command |
+|------|---------|
+| Run the CLI | `uv run dcmassist export --database <DB>` |
+| Run all tests | `uv run pytest` |
+| Run one file | `uv run pytest tests/test_orchestrator.py -v` |
+| Run one test | `uv run pytest tests/test_orchestrator.py::test_export_writes_full_layout -v` |
+| Lint | `uv run ruff check src tests` |
+| Format check | `uv run ruff format --check src tests` |
+| Auto-fix | `uv run ruff check --fix src tests && uv run ruff format src tests` |
+| Type check | `uv run mypy src` |
+
+## Pre-commit hook
+
+The pre-commit hook runs `ruff format`, `ruff --fix`, and `mypy src` across the whole tree on every commit.
+
+- **Never bypass it with `--no-verify`.** If the hook fails, fix the underlying issue.
+- The hook does **not** run pytest. Run `uv run pytest` manually before pushing.
+- If a refactor breaks a different file's call site, that's a sign two changes need to land in one commit.
+
+## Workflow
+
+1. Open an issue describing what you want to change (skip for small fixes).
+2. Branch from `main`.
+3. TDD where it makes sense — write the test, watch it fail, write the code, watch it pass.
+4. Keep commits focused. Frequent small commits beat one giant one.
+5. Run the full test suite (`uv run pytest`) before pushing.
+6. Open a PR. Reference any related issue.
+
+## Code conventions
+
+These are enforced by review (and partly by tooling):
+
+- **Default to no comments.** Add one only when the *why* is non-obvious — a Snowflake quirk, a hidden invariant, a workaround for a specific error. Don't comment what well-named code already shows.
+- **Module docstrings explain why the module exists**, not what it contains.
+- **No backwards-compatibility shims, dead defensive code, or feature flags for hypothetical futures.** The codebase is pre-1.0 and prefers clean breaks over migration scaffolding.
+- **No mocking the database in tests that exercise the orchestrator end-to-end.** Use the cursor-mocking pattern in `tests/test_orchestrator.py`.
+- **Quote Snowflake identifiers** in any DDL you generate — leading-digit and lowercase names break otherwise.
+- **Never include credentials in synthesized DDL**, especially stage DDL. Credentials belong on storage integrations.
+
+## Architecture overview
+
+### Pipeline
+
+`cli.py` builds a frozen `Config`, then `orchestrator.export(cfg)` runs the entire pipeline:
+
+1. `resolve_objects_per_file()` — read `DCMASSIST_EXPORT_OBJECTS_PER_FILE` *before* touching the output folder (a bad value must not blow away the user's directory).
+2. `prepare_out_folder()` — refuse non-empty unless `--force`; clear and recreate.
+3. Open `RunLog` at `<out>/dcmassist.log` and dump every Config field so users see (and discover) available options.
+4. Inside a `StatusDashboard` (Rich `Live` panel), connect to Snowflake and iterate `filter_types(cfg)`.
+5. For each type, dispatch to its plugin: `discover()` → per-FQN `get_ddl()` → `to_define_and_invocation()`.
+6. Chunk per-type blocks via `chunk_blocks()` into `dict[filename, body]` keyed by full filename (`table.sql`, `table2.sql`, …). The first chunk keeps the unsuffixed name so small exports look identical to before chunking existed.
+7. `write_outputs()` writes the dict to disk. It is mechanical — naming logic lives in the orchestrator.
+
+Exit codes: `0` ok, `4` exported nothing but had errors, `5` config/setup error.
+
+### Plugin system
+
+Plugins live in `src/dcmassist/objects/` and are auto-discovered: `objects/__init__.py:build_registry()` imports every non-underscore module and calls `registry.register(module.plugin)`.
+
+To add a new v1 type:
+
+1. Create `src/dcmassist/objects/<type>.py`.
+2. Subclass `V1ObjectPlugin` from `_base.py`.
+3. Set `type_name`, `file_slug`, `SHOW_FORM`, `GET_DDL_TYPE`, `MACRO_BODY`.
+4. Instantiate as a module-level `plugin`.
+5. Add the canonical name to `V1_TYPES` in `types.py`.
+6. Write tests in `tests/test_objects/test_<type>.py`.
+
+`V1ObjectPlugin` implements the standard recipe: schema-iterated `SHOW` discovery, `GET_DDL(<TYPE>, <quoted_fqn>, TRUE)`, and a rewrite chain (`create_to_define` → `inject_comment_if_missing` → `parameterise_database`). Override only what's special.
+
+`Schema` and `Stage` synthesize their DDL directly from `SHOW`/`DESC STAGE` rows because `GET_DDL` either hangs (recursive Schema) or is unsupported (Stage).
+
+### Snowflake quirks
+
+- `SHOW … IN DATABASE` is capped at 10K rows. Use `paginated_show()` from `objects/_show_paging.py`, which appends `LIMIT N FROM '<last_name>'`.
+- The cursor is forced to `DictCursor` in `connection.py`; `_rows_to_fqns` rejects non-dict rows defensively.
+- Identifiers must be quoted in `GET_DDL`/`DESC STAGE` (see `FQN.quoted` in `types.py`).
+- `GET_DDL(..., TRUE)` returns fully-qualified names; `parameterise_database` rewrites the literal database to `{{ database }}`.
+- The error string `002003 / "does not exist or not authorized"` is treated as a non-fatal `skipped_missing` — common in shared databases where the role lacks privileges on a few objects.
+- `Database` is intentionally NOT in `V1_TYPES` — DCM rejects `DEFINE DATABASE` for the project's parent database.
+
+### Status & logging split
+
+- **`StatusDashboard`** (`status.py`) — Rich `Live` panel on stderr, transient. Silent on non-TTY, `NO_COLOR=1`, or `DCMASSIST_NO_STATUS=1`. `.log()` writes above the panel; falls back to plain stderr when disabled so warnings still surface in CI.
+- **`RunLog`** (`log.py`) — per-run timestamped log file at `<out>/dcmassist.log`. Truncated on each run. This is what users tail when something goes wrong.
+
+The dashboard answers "what's happening right now"; the log answers "what happened to which object and why".
+
+## Testing notes
+
+- Tests in `tests/test_orchestrator.py` mock the Snowflake cursor end-to-end via the pattern in `_cfg()` and `execute_side_effect`. Reuse that pattern for new orchestrator-level tests.
+- Plugin-level tests (`tests/test_objects/test_*.py`) test discovery and rewrite chains in isolation, with no cursor at all where possible.
+- `tmp_path` from pytest is fine for output-folder fixtures.
+- If you're adding a new env var, write a test that sets it via `monkeypatch.setenv` and confirm both the success path and an invalid value.
+
+## Plans and specs
+
+Larger features start with a spec in `docs/superpowers/specs/` and a plan in `docs/superpowers/plans/`, written via the [superpowers](https://github.com/anthropics/superpowers) `brainstorming` and `writing-plans` skills. You don't need superpowers to contribute — short PRs can skip the doc — but for anything non-trivial please open an issue or draft PR first so the design can be discussed before code lands.
+
+## Reporting bugs
+
+Open an issue at [github.com/jamiekt/dcmassist/issues](https://github.com/jamiekt/dcmassist/issues) with:
+
+- The command you ran.
+- The relevant section of `dcmassist.log`.
+- Snowflake account region (if reproducible only on certain regions).
+- Whether the same export works against a different database / role.
+
+Don't paste DDL that contains real customer data or credentials.
+
+## License
+
+By contributing, you agree your contributions will be licensed under the project's MIT license.

dcmassist-0.1.15/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jamie Thomson
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.