denckring 0.1.0__tar.gz

denckring-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,37 @@
+name: Bug report
+description: A procedure gives the wrong answer, or something crashes
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        If a procedure disagrees with a literary authority about what a form requires,
+        that is a bug — please say which authority.
+  - type: input
+    id: procedure
+    attributes:
+      label: Procedure
+      placeholder: lipogram
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: What you ran
+      description: The command or the `check(...)` call, with the text and parameters.
+      render: python
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: What you expected, and what happened
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: "`denckring --version`, and whether `denckring[en]` is installed."
+    validations:
+      required: true

denckring-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: true

denckring-0.1.0/.github/ISSUE_TEMPLATE/new_procedure.yml

@@ -0,0 +1,49 @@
+name: New procedure
+description: Propose a writing procedure for the catalogue
+labels: [catalogue]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        The catalogue's value is that its entries are sourced. An entry with no source
+        is not one we can add.
+  - type: input
+    id: name
+    attributes:
+      label: Name of the procedure
+    validations:
+      required: true
+  - type: textarea
+    id: definition
+    attributes:
+      label: Definition
+      description: One or two sentences. What must a text do to satisfy it?
+    validations:
+      required: true
+  - type: input
+    id: source
+    attributes:
+      label: Source
+      description: "Author, work and year, or the reference work that documents it."
+    validations:
+      required: true
+  - type: dropdown
+    id: attribution
+    attributes:
+      label: How is that source established?
+      options:
+        - primary — a named author, work and year
+        - reference — attested in a standard reference, origin not traced
+        - traditional — classical or folk, no single origin
+    validations:
+      required: true
+  - type: dropdown
+    id: checkability
+    attributes:
+      label: Can a program decide it?
+      options:
+        - self — from the text and its parameters alone
+        - source — only against the text it was made from
+        - none — no computable acceptance criterion exists
+    validations:
+      required: true

denckring-0.1.0/.github/dependabot.yml

@@ -0,0 +1,39 @@
+version: 2
+
+# Each ecosystem opens ONE grouped pull request, not one per dependency.
+#
+# `ci.yml` is 9 jobs of which `test` is a 13-cell matrix, so every run is 21
+# runner-jobs — 13 Linux, 4 Windows, 4 macOS — and `pull_request` fires the whole
+# thing. Against a private repo's included minutes, where Windows counts double
+# and macOS tenfold, that is roughly 280 billable minutes per run, about 71% of
+# it macOS.
+#
+# Ungrouped, the default limit of five open PRs per ecosystem means up to ten
+# runs a month from Dependabot alone, ~2,800 minutes, which exceeds the whole
+# monthly allowance before any human pushes anything. That is not a projection:
+# on 2026-08-30 the first push opened eight PRs at once and the nine resulting
+# runs exhausted the quota, failing every job except `core-only`.
+#
+# Grouping costs bisectability — a red grouped PR does not say which member
+# broke it — which is why the two ecosystems stay in separate groups rather than
+# one. A lockfile bump and an Actions bump fail for entirely different reasons.
+updates:
+  - package-ecosystem: github-actions
+    directory: "/"
+    schedule:
+      interval: monthly
+    commit-message:
+      prefix: "chore"
+    groups:
+      github-actions:
+        patterns: ["*"]
+
+  - package-ecosystem: uv
+    directory: "/"
+    schedule:
+      interval: monthly
+    commit-message:
+      prefix: "chore"
+    groups:
+      python-packages:
+        patterns: ["*"]

denckring-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,18 @@
+## What this changes
+
+<!-- One or two sentences. -->
+
+## Checklist
+
+- [ ] `uv run pytest` passes
+- [ ] `uv run ruff check` and `uv run ruff format --check` pass
+- [ ] `uv run mypy --strict src tests packages/denckring-en-data/src` passes
+- [ ] `uv run denckring eval --all` is green
+
+If this adds a procedure:
+
+- [ ] One module, named for the procedure id
+- [ ] A catalogue row with a real source, an `attribution` and a `checkability`
+- [ ] Golden fixtures: at least one genuine instance and one counterexample
+- [ ] Hypothesis strategies under `tests/strategies/`
+- [ ] The catalogue definition claims no more than the checker verifies

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

@@ -0,0 +1,293 @@
+name: CI
+
+on:
+  push:
+    branches: [main, master]
+  pull_request:
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+env:
+  UV_FROZEN: "1"
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync --extra en --extra de --extra de-wiktionary --extra de-frequency --extra fr
+      - run: uv run ruff check
+      - run: uv run ruff format --check
+
+  typecheck:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync --extra en --extra de --extra de-wiktionary --extra de-frequency --extra fr --extra mcp
+      - run: >-
+          uv run mypy --strict src tests packages/denckring-en-data/src
+          packages/denckring-de-data/src packages/denckring-de-wiktionary/src
+          packages/denckring-de-frequency/src
+
+  test:
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        python: ["3.11", "3.12", "3.13", "3.14"]
+        include:
+          # The free-threaded build, on one platform. Nothing here holds a lock
+          # or touches a C extension, so the claim costs one job to keep honest
+          # — and an unverified claim is worse than none.
+          - os: ubuntu-latest
+            python: "3.14t"
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+          python-version: ${{ matrix.python }}
+      - run: uv sync --extra en --extra de --extra de-wiktionary --extra de-frequency --extra fr
+      - run: uv run pytest -q
+
+  coverage:
+    # A floor, not a report. The README's badge states the same 97 this job
+    # enforces, so the badge cannot go stale upward-or-downward without CI
+    # going red — which is the only way a number in prose stays true here.
+    #
+    # Measured 97.1% on 2026-09-05: 6,015 of 6,194 statements. The margin over
+    # the floor is about seven statements, and hypothesis moves the last one or
+    # two between runs, so a drop that turns this red is a real drop. Raising
+    # the floor means raising the badge in the same commit.
+    #
+    # `--extra mcp` because the matrix runs without it and `pytest.importorskip`
+    # then skips every MCP test: measuring the suite that skips them would
+    # report `mcp/server.py` as uncovered code nobody had chosen not to cover.
+    #
+    # Scoped to `denckring` alone. The workspace data packages are vendored
+    # tables with a few lines of accessor each, and folding them in would move
+    # the figure without saying anything about the library.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: >-
+          uv sync --extra en --extra de --extra de-wiktionary
+          --extra de-frequency --extra fr --extra mcp
+      - run: uv run pytest -q --cov=denckring --cov-report=term-missing --cov-fail-under=97
+
+  eval:
+    # The acceptance criterion the project set itself for unattended runs. A
+    # passing test suite is a different claim from a green scoreboard, so this
+    # is a gate of its own.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync --extra en --extra de --extra de-wiktionary --extra de-frequency --extra fr
+      - run: uv run denckring eval --all
+      - run: uv run denckring status
+
+  mcp:
+    # The matrix runs without [mcp], so `pytest.importorskip` skips every MCP
+    # test there — the extra's own code would otherwise be tested nowhere. One
+    # job installs it and runs them for real. A skipped test reports green.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync --extra en --extra de --extra de-wiktionary --extra de-frequency --extra fr --extra mcp
+      - run: uv run pytest tests/test_mcp_tools.py -q
+      - name: The server starts and lists its four tools
+        run: |
+          uv run python -c "
+          import asyncio
+          from denckring.mcp.server import server
+          names = {t.name for t in asyncio.run(server.list_tools())}
+          assert names == {'list_procedures', 'describe_procedure', 'check_text', 'apply_procedure'}, names
+          print('mcp:', sorted(names))
+          "
+
+  core-only:
+    # Nothing else exercises the install without the data package, and that is
+    # the path most likely to break silently: a procedure quietly requiring a
+    # capability core does not have would pass every other job here.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - name: Install the core distribution alone
+        run: |
+          uv venv /tmp/core-only
+          VIRTUAL_ENV=/tmp/core-only uv pip install .
+      - name: The data-free procedures work
+        run: |
+          /tmp/core-only/bin/python -c "
+          from denckring import check
+          assert check('lipogram', 'aaa', forbidden='z').satisfied
+          assert check('pangram', 'Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich', lang='de').satisfied
+          print('core-only: data-free procedures OK')
+          "
+      - name: The data-dependent ones raise, naming the extra
+        run: |
+          /tmp/core-only/bin/python -c "
+          from denckring import check
+          from denckring.core.errors import MissingCapability
+          try:
+              check('iambic_pentameter', 'the cat can see the moon above the tree')
+          except MissingCapability as exc:
+              print('core-only: raised as expected —', exc)
+          else:
+              raise SystemExit('iambic_pentameter should require a capability core lacks')
+          "
+
+  german-without-pronunciations:
+    # `denckring[de]` is two distributions and either may be installed alone, so
+    # the lexical-only install is a real shape a user can have. ADR 0030 puts the
+    # choice between the two packs in one factory; this is the job that proves the
+    # factory picks the lexical one and that a phonetic row then refuses rather
+    # than guessing. Nothing in the suite covers it, because the suite runs with
+    # both installed.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - name: Install the lexical German data and not the phonetic
+        run: |
+          uv venv /tmp/de-lexical
+          VIRTUAL_ENV=/tmp/de-lexical uv pip install ".[de]"
+      - name: The lexical rows work and the phonetic ones name what is missing
+        run: |
+          /tmp/de-lexical/bin/python -c "
+          from denckring import check
+          from denckring.core.errors import MissingCapability
+          from denckring.lang import get_pack
+          pack = get_pack('de')
+          assert type(pack).__name__ == 'GermanDataPack', type(pack).__name__
+          assert check('charade', 'Tal', lang='de').satisfied is not None
+          try:
+              check('iambic_pentameter', 'der Wind bewegt die Blätter in der Nacht', lang='de')
+          except MissingCapability as exc:
+              assert 'stress' in str(exc), exc
+              print('de-lexical: raised as expected —', exc)
+          else:
+              raise SystemExit('iambic_pentameter needs stress, which this install lacks')
+          "
+
+  french-without-data:
+    # French ships in core with no data at all, which is a real install shape and
+    # the one the suite never runs: it always has `denckring[fr]`. ADR 0034 leaves
+    # 18 rows blocked in French — down from ADR 0032's 41, and all of them on
+    # `stress` — so every row this job exercises is one `denckring[fr]` unblocks,
+    # and each must refuse by naming what is missing rather than guessing.
+    #
+    # The `phonemes` assertion below has no other home. ADR 0034 gave French
+    # `phonemes`, so no installed pack lacks that capability any more, and
+    # `tests/test_prosody_robustness.py` had to move its refusal test to `stress`.
+    # A core-only install is now the only place a phonemes refusal runs at all.
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - name: Install the core distribution alone
+        run: |
+          uv venv /tmp/fr-core
+          VIRTUAL_ENV=/tmp/fr-core uv pip install .
+      - name: The data-free French rows work and the data-fed ones name what is missing
+        run: |
+          /tmp/fr-core/bin/python -c "
+          from denckring import check
+          from denckring.core.errors import MissingCapability
+          assert check('lipogram', 'aaa', forbidden='z', lang='fr').satisfied
+          try:
+              check('n_plus_7', 'la maison', lang='fr')
+          except MissingCapability as exc:
+              assert 'lexicon.nouns' in str(exc), exc
+              print('fr-core: lexical row raised as expected —', exc)
+          else:
+              raise SystemExit('n_plus_7 needs lexicon.nouns, which this install lacks')
+          try:
+              check('alexandrine', 'le temps n\'est plus', lang='fr')
+          except MissingCapability as exc:
+              assert 'syllables' in str(exc), exc
+              print('fr-core: syllabic row raised as expected —', exc)
+          else:
+              raise SystemExit('alexandrine needs syllables, which this install lacks')
+          try:
+              check('rhyme_scheme', 'le chat dort\nle chien court', scheme='AA', lang='fr')
+          except MissingCapability as exc:
+              assert 'phonemes' in str(exc), exc
+              print('fr-core: rhyme row raised as expected —', exc)
+          else:
+              raise SystemExit('rhyme_scheme needs phonemes, which this install lacks')
+          "
+
+  docs:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync --extra en --extra de --extra de-wiktionary --extra de-frequency --extra fr
+      - name: Regenerate the gallery
+        run: uv run python scripts/build_docs.py
+      - name: Build the site
+        run: uv run mkdocs build --strict
+
+  explorer:
+    # A development tool, but a tested one: its own suite, which no other job in
+    # this workflow collects and which has never run in CI before this job.
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        # uv run --project apps/explorer still executes with the repo root as
+        # cwd, so pytest's rootdir search finds this repo's own testpaths
+        # config and collects ../../tests instead. Running inside the app's
+        # directory is what actually resolves its test paths.
+        working-directory: apps/explorer
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync
+      - run: uv run ruff check
+      - run: uv run ruff format --check
+      - run: uv run mypy --strict src tests
+      - run: uv run pytest -q
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv build --all-packages
+      - run: uvx twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: distributions
+          path: dist/

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

@@ -0,0 +1,175 @@
+name: Release
+
+# Two entry points, and the second one is why this file changed before the first
+# release rather than after it.
+#
+# A `v*` tag publishes to PyPI for real. `workflow_dispatch` publishes to TestPyPI
+# instead, so the whole path — build, check, upload through Trusted Publishing —
+# can be walked once against a registry where a mistake is recoverable. PyPI
+# refuses a re-upload of a version that already exists, so without a rehearsal the
+# first genuine tag is also the first time this workflow has ever run end to end.
+on:
+  push:
+    tags: ["v*"]
+  workflow_dispatch:
+    inputs:
+      target:
+        description: Which index to publish to.
+        type: choice
+        default: testpypi
+        options: [testpypi, none]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv build --all-packages
+      - run: uvx twine check dist/*
+      - uses: actions/upload-artifact@v4
+        with:
+          name: distributions
+          path: dist/
+
+  # Before `publish`, not after it. This used to run last, so a docs failure left
+  # the release on PyPI and undocumented — and unrecoverable, because PyPI will not
+  # take the version again. It also fails outright on a private repository, where
+  # `gh-deploy` needs a paid plan, which meant the old order guaranteed that the
+  # first release would publish and then go red.
+  docs:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - run: uv sync --extra en
+      - run: uv run python scripts/build_docs.py
+      # A dispatch run rehearses the site build without deploying it: a rehearsal
+      # that pushed to gh-pages would not be a rehearsal.
+      - if: github.event_name == 'workflow_dispatch'
+        run: uv run mkdocs build --strict
+      - if: github.event_name == 'push'
+        run: uv run mkdocs gh-deploy --force --strict
+
+  rehearse:
+    # TestPyPI, from a manual run. One leg per distribution, for the reason the
+    # `publish` matrix below spells out.
+    if: github.event_name == 'workflow_dispatch' && inputs.target == 'testpypi'
+    needs: [build, docs]
+    runs-on: ubuntu-latest
+    strategy:
+      # Every leg is independent and each says something different: stopping the
+      # others on the first failure would hide which of the six are misconfigured,
+      # which is the whole question a rehearsal answers.
+      fail-fast: false
+      matrix:
+        include:
+          - {dist: denckring, files: "denckring-", environment: testpypi}
+          - {dist: denckring-en-data, files: "denckring_en_data-", environment: testpypi-en-data}
+          - {dist: denckring-de-data, files: "denckring_de_data-", environment: testpypi-de-data}
+          - {dist: denckring-de-wiktionary, files: "denckring_de_wiktionary-", environment: testpypi-de-wiktionary}
+          - {dist: denckring-de-frequency, files: "denckring_de_frequency-", environment: testpypi-de-frequency}
+          - {dist: denckring-fr-data, files: "denckring_fr_data-", environment: testpypi-fr-data}
+    environment: ${{ matrix.environment }}
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: distributions
+          path: all-dist/
+      - name: Take only this distribution's artefacts
+        run: |
+          mkdir -p dist
+          cp all-dist/${{ matrix.files }}* dist/
+          # An empty or over-full `dist/` is the failure this split can produce and
+          # the one an upload would not report: publishing nothing succeeds. Exactly
+          # a wheel and an sdist, or stop.
+          count=$(ls dist | wc -l)
+          test "$count" -eq 2 || {
+            echo "expected 2 artefacts for ${{ matrix.dist }}, found $count"; ls -l dist; exit 1;
+          }
+          ls -l dist
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          repository-url: https://test.pypi.org/legacy/
+          # Off here and on for the real thing: TestPyPI is periodically pruned,
+          # so an attestation made against it outlives what it attests to.
+          attestations: false
+          # A rehearsal that has been rehearsed before should not fail on that.
+          skip-existing: true
+
+  publish:
+    # All six distributions publish from one workflow because they must stay
+    # version-locked: denckring-en-data subclasses the core English pack,
+    # denckring-de-data carries the sole `de` entry point,
+    # denckring-de-wiktionary is the pack that entry point resolves to when it is
+    # installed, denckring-de-frequency adds `lexicon.graded_words` to that pack
+    # under its own licence (ADR 0038), and denckring-fr-data subclasses the core
+    # French pack (ADR 0032). `uv build --all-packages` picks up every workspace
+    # member, so the sixth needed no change here.
+    #
+    # One job per distribution, each with its own environment, and that is forced
+    # rather than chosen. PyPI requires a *pending* publisher to be unique on
+    # (owner, repository, workflow, environment), so six pending publishers sharing
+    # one environment cannot be registered at all — the second is refused with "a
+    # pending trusted publisher matching this configuration has already been
+    # registered for a different project name" (pypi/warehouse#16920). Environment
+    # is the only part of that tuple this workflow can vary, so it varies.
+    #
+    # The alternatives were worse: create the projects with API tokens and enrol
+    # publishers afterwards, or publish one distribution per release event until
+    # each pending publisher has been converted. The first reintroduces the upload
+    # token this whole arrangement exists to avoid; the second breaks the version
+    # lock these six are released under.
+    if: github.event_name == 'push'
+    needs: [build, docs]
+    runs-on: ubuntu-latest
+    strategy:
+      # A partial release is the failure mode here, and it is worth seeing whole:
+      # if one distribution's publisher is misconfigured, the remaining five should
+      # still report rather than be cancelled. PyPI will not re-take a version that
+      # landed, so the recovery is a version bump either way — knowing which legs
+      # succeeded is what makes that recovery short.
+      fail-fast: false
+      matrix:
+        include:
+          - {dist: denckring, files: "denckring-", environment: pypi}
+          - {dist: denckring-en-data, files: "denckring_en_data-", environment: pypi-en-data}
+          - {dist: denckring-de-data, files: "denckring_de_data-", environment: pypi-de-data}
+          - {dist: denckring-de-wiktionary, files: "denckring_de_wiktionary-", environment: pypi-de-wiktionary}
+          - {dist: denckring-de-frequency, files: "denckring_de_frequency-", environment: pypi-de-frequency}
+          - {dist: denckring-fr-data, files: "denckring_fr_data-", environment: pypi-fr-data}
+    environment: ${{ matrix.environment }}
+    permissions:
+      # Trusted Publishing. No API token is stored in repository secrets.
+      id-token: write
+      attestations: write
+    steps:
+      - uses: actions/download-artifact@v4
+        with:
+          name: distributions
+          path: all-dist/
+      - name: Take only this distribution's artefacts
+        run: |
+          mkdir -p dist
+          cp all-dist/${{ matrix.files }}* dist/
+          # `denckring-` is unambiguous because every other distribution builds with
+          # underscores — denckring_en_data-0.1.0 and so on — so the core's prefix
+          # cannot swallow its siblings. The count below is what actually enforces it.
+          count=$(ls dist | wc -l)
+          test "$count" -eq 2 || {
+            echo "expected 2 artefacts for ${{ matrix.dist }}, found $count"; ls -l dist; exit 1;
+          }
+          ls -l dist
+      - uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          attestations: true

denckring-0.1.0/.gitignore

@@ -0,0 +1,39 @@
+.venv/
+__pycache__/
+*.pyc
+.pytest_cache/
+.mypy_cache/
+.ruff_cache/
+.hypothesis/
+dist/
+*.egg-info/
+dist/
+
+# Generated docs and site build
+docs/gallery/
+docs/index.md
+docs/contributing.md
+docs/changelog.md
+site/
+
+# The explorer keeps its own environment
+apps/explorer/.venv/
+
+# Local secrets and paths for the explorer
+apps/explorer/.env
+
+# Claude Code session state, including worktrees
+.claude/
+
+# Subagent-driven-development scratch workspace (ledgers, briefs, review packages).
+.superpowers/
+
+# Node modules for the explorer's browser reproductions (apps/explorer/tests/browser).
+# The manifest and lockfile beside them ARE tracked, so `npm ci --prefix apps/explorer`
+# reinstalls exactly what those scripts were verified against; the 19MB tree is not.
+apps/explorer/node_modules/
+
+# pytest-cov writes this on every --cov run; the report is CI's, not the repo's.
+.coverage
+.coverage.*
+htmlcov/

denckring-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,31 @@
+# Mirrors the lint and typecheck jobs in .github/workflows/ci.yml, so a failure
+# here is a failure there.
+repos:
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.16.2
+    hooks:
+      - id: ruff-check
+        args: [--fix]
+      - id: ruff-format
+
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v5.0.0
+    hooks:
+      - id: check-yaml
+        exclude: ^mkdocs\.yml$
+      - id: check-toml
+      - id: end-of-file-fixer
+      - id: trailing-whitespace
+      - id: check-merge-conflict
+      - id: check-added-large-files
+        # The vendored pronouncing dictionary is 3.6 MB and belongs in the repo.
+        args: [--maxkb=4096]
+
+  - repo: local
+    hooks:
+      - id: mypy
+        name: mypy --strict
+        entry: uv run mypy --strict src tests packages/denckring-en-data/src
+        language: system
+        pass_filenames: false
+        types: [python]