yurli 0.1.0__tar.gz

yurli-0.1.0/.agents/skills/dependency-maintenance/SKILL.md

@@ -0,0 +1,29 @@
+---
+name: dependency-maintenance
+description: >-
+  Maintains Python and npm dependencies, developer tools, lockfiles, and prek hooks. Use
+  when adding, removing, or updating project dependencies, tool versions, or hook
+  revisions.
+---
+
+# Dependency maintenance
+
+Use the repository's declared dependency mechanisms and preserve consistency between
+metadata, lockfiles, CI, and hooks.
+
+- Manage Python dependencies with `uv` and declarations in `pyproject.toml`. Use
+  `uv add`, `uv remove`, or an intentional metadata edit followed by `uv lock`; commit
+  the resulting `uv.lock` changes.
+- Manage npm dependencies through npm commands and `package.json`. Regenerate and commit
+  `package-lock.json`; use `npm ci` to install the locked set.
+- When changing hook revisions in `prek.toml` or relevant Python tool versions, run the
+  configured `sync-with-uv` hook (`uv run prek run sync-with-uv`) and review any
+  resulting lockfile updates.
+- Check that versions agree across CI workflow setup, dependency declarations,
+  `uv.lock`, `package-lock.json`, and `prek.toml` where applicable. Prefer the existing
+  dependency-management mechanisms over duplicating version information.
+- Run relevant checks after changes. See `CONTRIBUTING.md` for `uv sync --locked`,
+  tests, `tools/linters.sh`, `tools/formatters.sh`, and `uv run prek run --all-files`.
+
+Do not add dependencies or weaken checks unless the requested change requires it.
+Document workflow changes in `CONTRIBUTING.md` or `README.md` as appropriate.

yurli-0.1.0/.agents/skills/release/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: release
+description: >-
+  Prepares and validates releases for this Python package template. Use when planning,
+  validating, or publishing a release, including version tags, distributions, GitHub
+  Releases, or PyPI trusted publishing.
+---
+
+# Release preparation and validation
+
+This template derives package versions from Git history and tags through hatch-vcs.
+Review the release workflow in `.github/workflows/publish.yml` and current packaging
+configuration before preparing a release.
+
+- Confirm the intended source commit and release version. Create a valid version tag
+  (optionally prefixed with `v`) only when explicitly authorized; the built package
+  version must match the tag after removing that prefix.
+- Run the relevant tests and coverage checks documented in `CONTRIBUTING.md`, then build
+  distributions with `uv build`.
+- Validate the distributions and confirm the version in package metadata matches the
+  intended tag. Follow the existing validation in `.github/workflows/publish.yml`.
+- If the project publishes to PyPI, confirm its trusted publisher and `pypi` GitHub
+  environment are configured for the repository and workflow. This template may be
+  adapted for projects that do not publish to PyPI; skip PyPI steps for those projects.
+- GitHub Release creation, tag creation, package upload, and other publishing are
+  external actions. Never create tags, publish releases, or upload packages without
+  explicit user authorization.

yurli-0.1.0/.agents/skills/update-from-template/HISTORY.md

@@ -0,0 +1,23 @@
+# Template update history
+
+Template-Source: `xozoid/python-template`
+
+Template-Revision: `c9a5cf91408da939219746d426f7ad92fc49ec5f`
+
+The revision is the full upstream template commit last fully applied to this project. It
+is not a commit from the target repository. Adoption sets the initial revision to the
+upstream commit used to create the project. During later updates, change this file only
+after the applicable migration succeeds and validation passes.
+
+## Skipped template changes
+
+Record each intentional skip with the target template revision where it was first
+skipped, affected path or behavior, a short description, and the reason. At each later
+update, check whether changes touch or depend on a recorded skip. Review template
+evolution from that skip revision through the new target revision; determine whether
+later changes build on, replace, or invalidate the skipped change, and reconsider the
+local adaptation accordingly. Do not treat a skip as permanent. After a successful
+migration, update the entry with its current disposition or remove it if it is resolved
+or no longer relevant.
+
+- None recorded.

yurli-0.1.0/.agents/skills/update-from-template/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: update-from-template
+description: >-
+  Updates a project adopted from xozoid/python-template while preserving
+  project-specific code, configuration, and intentional deviations.
+---
+
+# Update from template
+
+Read `.agents/skills/update-from-template/HISTORY.md` for the template source, last
+applied revision, and persistent list of intentionally skipped changes. Keep that file
+as the only template tracking record. Do not edit this `SKILL.md` during an update.
+
+## Update workflow
+
+1. Read the source and last applied full commit SHA from `HISTORY.md`. Resolve the
+   template repository's default branch and its current full commit SHA. Fetch the
+   upstream template and verify that the recorded revision exists there.
+2. Compare the recorded revision with the current default-branch revision. If they are
+   identical, report that no update is needed and leave `HISTORY.md` unchanged. If the
+   target revision does not descend from the recorded revision, report divergence and
+   stop before applying changes.
+3. Review the template changes between the recorded and target revisions. Compare the
+   affected files with the project, then apply relevant changes in context. Preserve
+   project-specific code, metadata, dependencies, configuration, CI customizations, and
+   intentional deviations. Never overwrite uncommitted changes or discard local edits.
+4. For intentionally skipped changes, record the affected paths, the template revision
+   where each change was first skipped, a short description, and the reason in
+   `HISTORY.md`. During every later update, check whether new changes touch the same
+   paths or behavior, or depend on a skipped change. Review the template evolution from
+   the recorded skip revision through the new target revision to see whether later work
+   builds on, replaces, or invalidates the skip. Reconsider the local adaptation when
+   needed; do not treat a skip as a permanent instruction to ignore that area. Update
+   the history entry with the result after a successful migration.
+5. Run relevant tests, linting, formatting, dependency locking, and pre-commit
+   synchronization checks. Review generated changes and resolve conflicts with the
+   project's conventions.
+6. Only after the applicable migration is complete and checks succeed, update
+   `HISTORY.md` with the full target template SHA and any intentional skips. Do not
+   automatically commit changes unless the user explicitly requests a commit.
+
+## Finding an initial revision
+
+If the revision in `HISTORY.md` is unset or still contains a placeholder, compare the
+project's initial state with the template's history and use file contents and timestamps
+only as supporting evidence. Do not select a revision solely because it looks like the
+closest match. If the origin cannot be identified confidently, describe the candidate
+revisions and ask the user to confirm before updating.
+
+## Report
+
+Report the target template revision, applied changes, skipped changes and reasons,
+conflicts, and validation results. State clearly when no update was needed or when
+divergence or an ambiguous starting revision prevented an update. If a commit is
+requested, use a clear summary. Update `HISTORY.md` only when a template migration has
+completed successfully; leave it unchanged for a no-op, failed, or incomplete update.

yurli-0.1.0/.gitattributes

@@ -0,0 +1,2 @@
+# Force LF checkout for source files.
+* text=auto eol=lf

yurli-0.1.0/.github/dependabot.yml

@@ -0,0 +1,15 @@
+version: 2
+updates:
+  - package-ecosystem: npm
+    directory: /
+    schedule:
+      interval: weekly
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+  - package-ecosystem: uv
+    directory: /
+    schedule:
+      interval: weekly
+    versioning-strategy: increase

yurli-0.1.0/.github/rulesets/main-squash-only.json

@@ -0,0 +1,32 @@
+{
+  "bypass_actors": [],
+  "conditions": {
+    "ref_name": {
+      "exclude": [],
+      "include": ["refs/heads/main"]
+    }
+  },
+  "enforcement": "active",
+  "name": "Main - squash merges only",
+  "rules": [
+    {
+      "type": "deletion"
+    },
+    {
+      "type": "non_fast_forward"
+    },
+    {
+      "parameters": {
+        "allowed_merge_methods": ["squash"],
+        "dismiss_stale_reviews_on_push": false,
+        "require_extra_approval_for_unattributed_changes": true,
+        "require_last_push_approval": false,
+        "required_approving_review_count": 0,
+        "required_review_thread_resolution": true,
+        "required_reviewers": []
+      },
+      "type": "pull_request"
+    }
+  ],
+  "target": "branch"
+}

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

@@ -0,0 +1,141 @@
+name: CI
+on:
+  workflow_call:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  workflow_dispatch:
+permissions:
+  contents: read
+jobs:
+  pytest:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.12", "3.13", "3.14", "3.15"]
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: ${{ matrix.python-version }}
+          enable-cache: true
+      - run: uv sync --locked --no-default-groups --group test
+      - run: uv run --no-sync pytest
+  minimum-runtime-dependencies:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: "3.12"
+          enable-cache: true
+      - name: Resolve minimum runtime dependencies
+        run: |
+          uv venv --python 3.12 .venv-minimum
+          uv pip install --python .venv-minimum/bin/python --resolution lowest-direct .
+          uv pip freeze --python .venv-minimum/bin/python > /tmp/minimum-constraints.txt
+      - name: Install locked pytest
+        run: |
+          PYTEST_VERSION=$(python -c "
+          import tomllib
+          with open('uv.lock', 'rb') as f:
+              lock = tomllib.load(f)
+          print(next(p['version'] for p in lock['package'] if p['name'] == 'pytest'))
+          ")
+          uv pip install --python .venv-minimum/bin/python --constraint /tmp/minimum-constraints.txt "pytest==$PYTEST_VERSION"
+      - name: Verify minimum dependencies were preserved
+        run: |
+          uv pip freeze --python .venv-minimum/bin/python > /tmp/after.txt
+          grep -Fxf /tmp/minimum-constraints.txt /tmp/after.txt | diff - /tmp/minimum-constraints.txt
+      - name: Run tests
+        run: .venv-minimum/bin/python -m pytest
+  ruff:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: "3.15"
+          enable-cache: true
+      - run: uv sync --locked --no-default-groups --group lint
+      - run: uv run --no-sync ruff check .
+  types:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: "3.15"
+          enable-cache: true
+      - run: uv sync --locked --no-default-groups --group types
+      - run: uv run --no-sync basedpyright
+  formatting:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: "3.15"
+          enable-cache: true
+      - uses: actions/setup-node@v7
+        with:
+          node-version: 24
+          cache: npm
+      - run: uv sync --locked --no-default-groups --group format
+      - run: npm ci
+      - run: uv run --no-sync ruff format --check .
+      - run: npm exec --no -- prettier --check .
+      - run: uv run --no-sync taplo fmt --check '*.toml'
+      - run: uv run --no-sync prek run yamlfmt --all-files
+  sync-with-uv:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+      - run: uv sync --locked --no-default-groups --only-group prek --no-install-project
+      - run: uv run --no-sync prek run --all-files sync-with-uv
+      - run: git diff --exit-code
+  spelling:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: "3.15"
+          enable-cache: true
+      - run: uv sync --locked --no-default-groups --group spell
+      - run: uv run --no-sync codespell --skip=node_modules .
+  coverage:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: "3.15"
+          enable-cache: true
+      - run: uv sync --locked --no-default-groups --group coverage
+      - run: uv run --no-sync coverage run -m pytest
+      - run: uv run --no-sync coverage report
+      - uses: actions/upload-artifact@v7
+        if: always()
+        with:
+          name: coverage-data
+          path: .coverage
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: "3.15"
+          enable-cache: true
+      - run: uv build
+      - run: uv venv --no-project /tmp/wheel-test
+      - run: uv pip install --python /tmp/wheel-test/bin/python dist/*.whl
+      - name: Verify installed wheel import
+        run: |
+          tmpdir=$(mktemp -d)
+          cd "$tmpdir"
+          /tmp/wheel-test/bin/python -c "import yurli"

yurli-0.1.0/.github/workflows/docs-ci.yml

@@ -0,0 +1,34 @@
+name: Docs CI
+on:
+  pull_request:
+    branches: [main]
+    paths:
+      - README.md
+      - CONTRIBUTING.md
+permissions:
+  contents: read
+jobs:
+  vale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v7
+      - name: Install Vale
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          url=$(gh api repos/vale-cli/vale/releases/latest \
+            --jq '.assets[] | select(.name | endswith("_Linux_64-bit.tar.gz")) | .browser_download_url')
+          curl -fsSL "$url" | sudo tar -xz -C /usr/local/bin vale
+          vale --version
+      - name: Sync Vale styles
+        run: |
+          attempt=0
+          until vale sync; do
+            attempt=$((attempt + 1))
+            if [ "$attempt" -ge 5 ]; then
+              exit 1
+            fi
+            sleep "$((attempt * 5))"
+          done
+      - name: Lint documentation
+        run: vale README.md CONTRIBUTING.md

yurli-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,44 @@
+name: Publish to PyPI
+on:
+  release:
+    types: [published]
+permissions:
+  contents: read
+jobs:
+  validate:
+    uses: ./.github/workflows/ci.yml
+  publish:
+    needs: validate
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/p/yurli
+    permissions:
+      id-token: write
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0
+      - uses: astral-sh/setup-uv@v7
+        with:
+          python-version: "3.15"
+      - run: uv build
+      - name: Verify release tag matches package version
+        env:
+          RELEASE_TAG: ${{ github.event.release.tag_name }}
+        run: |
+          python - <<'PY'
+          from email import message_from_bytes
+          from os import environ
+          from pathlib import Path
+          from zipfile import ZipFile
+
+          wheel = next(Path("dist").glob("*.whl"))
+          with ZipFile(wheel) as archive:
+              metadata_path = next(path for path in archive.namelist() if path.endswith(".dist-info/METADATA"))
+              version = message_from_bytes(archive.read(metadata_path))["Version"]
+          tag = environ["RELEASE_TAG"]
+          if tag.removeprefix("v") != version:
+              raise SystemExit(f"Release tag {tag!r} does not match package version {version!r}")
+          PY
+      - uses: pypa/gh-action-pypi-publish@release/v1

yurli-0.1.0/.gitignore

@@ -0,0 +1,29 @@
+# Local environments and secrets
+.venv/
+.env*
+
+# Python bytecode and caches
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.basedpyright/
+
+# Vale's downloaded style packages and scratch data
+.vale/styles/*
+!.vale/styles/config
+
+# Coverage output
+.coverage
+.coverage.*
+coverage.xml
+coverage.json
+htmlcov/
+
+# JavaScript dependencies
+node_modules/
+
+# Build and packaging output
+dist/
+build/
+*.egg-info/

yurli-0.1.0/.prettierignore

@@ -0,0 +1,15 @@
+# Version control metadata
+.git
+
+# Local environments and dependencies
+.venv
+node_modules
+
+# Generated Vale styles
+.vale/styles
+
+# Build output
+dist
+
+# Dependency lockfile
+uv.lock

yurli-0.1.0/.prettierrc

@@ -0,0 +1,4 @@
+{
+  "printWidth": 88,
+  "proseWrap": "always"
+}

yurli-0.1.0/.vale/styles/config/vocabularies/LocalProject/accept.txt

@@ -0,0 +1,6 @@
+Coverage.py
+Dependabot('s)?
+new-project
+pytest
+uv
+yurli

yurli-0.1.0/.vale.ini

@@ -0,0 +1,14 @@
+StylesPath = .vale/styles
+MinAlertLevel = error
+Packages = Microsoft, proselint, write-good
+Vocab = LocalProject
+
+[*.{md,rst,adoc,txt}]
+BasedOnStyles = Vale, Microsoft, proselint, write-good
+
+# Agent instructions are operational text for coding agents, not user-facing prose.
+[AGENTS.md]
+BasedOnStyles = NONE
+
+[.agents/skills/**]
+BasedOnStyles = NONE

yurli-0.1.0/AGENTS.md

@@ -0,0 +1,35 @@
+# Agent instructions
+
+## Project structure
+
+This repository is a Python package named `yurli`. The import package lives in `yurli/`,
+tests live in `tests/`, project and tool configuration lives in `pyproject.toml`, and
+GitHub Actions workflows live in `.github/workflows/`. Keep the established architecture
+unless a change is explicitly requested. Prefer focused changes and avoid unnecessary
+dependencies or abstractions.
+
+## Tooling
+
+- Use `uv` for Python dependencies and environments. `pyproject.toml` declares Hatchling
+  and `hatch-vcs`; package versions come from Git tags.
+- Ruff handles Python linting, formatting, and import sorting. Its configuration is in
+  `pyproject.toml`.
+- `basedpyright` runs in strict mode, configured in `pyproject.toml`.
+- Tests use pytest. Coverage runs with branch measurement and enforces the configured
+  minimum in `pyproject.toml`.
+- `tools/linters.sh`, `tools/formatters.sh`, and `tools/env.sh` provide the documented
+  local workflows. `prek.toml` defines hooks, including Ruff, basedpyright,
+  `sync-with-uv`, Vale, and Prettier.
+- Vale is intentionally disabled for agent-facing instruction files through `.vale.ini`;
+  keep other writing checks active.
+
+## Changes and checks
+
+When modifying code, add or update focused tests for the changed behavior. Run relevant
+checks after modifications, using the commands in `CONTRIBUTING.md` and the applicable
+CI jobs in `.github/workflows/ci.yml`. Update documentation when workflows or
+contributor instructions change. Never silently weaken linting, type checking, or
+coverage requirements.
+
+In your report, state which checks you actually ran, their results, any failures, and
+any checks you could not run.

yurli-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,106 @@
+# Contributing
+
+## Environment and dependencies
+
+Install Git, Python 3.12 or later, `uv`, Node.js 24 or later with npm, and Vale. Run
+`tools/env.sh` from any directory in the repository to sync the locked Python
+dependencies, install `prek` Git hooks, fetch Vale styles, run `npm ci`, and create
+`.env` and `.env.leave` if they aren't present. The script installs Vale when needed
+through a supported package manager. Use `tools/env.sh --upgrade` to upgrade Python
+dependencies before setup.
+
+Add Python development dependencies to the appropriate group in `pyproject.toml`
+(`lint`, `spell`, `test`, `coverage`, `types`, `format`, `prek`, or the aggregate `dev`
+group). Pin each development dependency to the exact version resolved in `uv.lock`, then
+update and commit `uv.lock`:
+
+```sh
+uv add --dev package-name
+uv lock
+uv lock --check
+uv sync --locked --all-groups
+uv run --no-sync prek run --all-files sync-with-uv
+```
+
+Use `uv add --group <group> package-name` for another dependency group, or edit the
+project metadata and run `uv lock` when needed. Set the exact pin to the version
+selected by the lockfile. Leave runtime dependencies in `[project.dependencies]`
+unpinned. The `dev` group includes all groups for the complete local environment. The
+`format` group includes `prek` for its `yamlfmt` hook; CI selects only the groups each
+independent job needs. Update npm development dependencies with
+`npm install --save-dev package-name` and commit both `package.json` and
+`package-lock.json`. Dependabot also checks uv, npm, and GitHub Actions dependencies
+weekly.
+
+## Tests and checks
+
+Run tests and coverage from the repository root:
+
+```sh
+uv run pytest
+uv run coverage run -m pytest
+uv run coverage report
+```
+
+The coverage report enforces the configured 85% minimum. `tools/linters.sh` runs Ruff,
+`basedpyright`, `codespell`, and Vale (errors only). `tools/formatters.sh` runs Ruff
+format, Prettier, `Taplo`, and `yamlfmt`. These scripts apply formatting changes; review
+the resulting diff.
+
+`uv run prek run --all-files` runs the configured hooks against all files. The hooks
+include Ruff lint and format, `codespell`, `Taplo`, `basedpyright`, `yamlfmt`, standard
+file checks, Vale, and Prettier. `tools/env.sh` installs the Git hooks so `prek` runs on
+commits. The `sync-with-uv` hook keeps hook revisions aligned with Python packages in
+`uv.lock`; run it after changing hook revisions or relevant dependencies, then review
+and commit the lockfile changes.
+
+Dependabot's weekly uv updates cover exact-pinned development dependencies. Its
+`increase` versioning strategy advances the manifest constraint, while the uv updater
+resolves and records the update in `uv.lock`. CI runs `sync-with-uv` on every pull
+request, including Dependabot pull requests. It installs the `prek` group, runs the
+hook, and fails if the hook would modify tracked files. If an update changes a tool
+revision represented in `prek.toml`, run `uv run prek run --all-files sync-with-uv` and
+commit the generated change with the lockfile update. Dependabot doesn't provide an
+arbitrary post-update script in `dependabot.yml`; its
+[options reference](https://docs.github.com/en/code-security/reference/supply-chain-security/dependabot-options-reference)
+documents the supported update behavior.
+
+## Agent instructions and skills
+
+Persistent repository guidance lives in the root `AGENTS.md`. Focused, task-specific
+Agent Skills live under `.agents/skills/`; each skill has a `SKILL.md` with metadata
+that helps compatible agents discover when to use it. `AGENTS.md` describes project-wide
+expectations, while skills provide checklists for particular tasks. Contributors can
+extend or maintain skills by adding a narrowly scoped directory and a valid `SKILL.md`,
+then updating its instructions when project workflows change. See the
+[Agent Skills specification](https://agentskills.io/specification) for the format.
+
+Projects created from this template should set the `Template-Revision` field in
+`.agents/skills/update-from-template/HISTORY.md` to the full upstream commit SHA used at
+adoption. For later updates, compare and migrate template changes while preserving local
+customizations, run the relevant checks above, and update that history file only after
+the migration succeeds. It also keeps the persistent record of intentionally skipped
+changes; the skill instructions remain unchanged.
+
+## Pull requests and CI
+
+Open a pull request against `main`. CI keeps checks in separate jobs: pytest on Python
+3.12 through 3.15, pytest against the lowest compatible runtime dependencies on Python
+3.12, Ruff, `basedpyright`, formatting (Ruff, Prettier, `Taplo`, `yamlfmt`), spelling,
+Vale, coverage, and build/import validation. Run the relevant local commands and ensure
+CI passes. Update tests and documentation when behavior or contributor instructions
+change.
+
+## Releases
+
+`hatch-vcs` reads the package version from Git tags. Create and publish a GitHub Release
+with a version tag such as `1.2.3` or `v1.2.3`; the optional `v` is removed for
+comparison with the package version. The published-release event starts
+`.github/workflows/publish.yml`. It runs CI first, builds the distribution, verifies
+that the release tag matches the built version, then publishes to PyPI through trusted
+publishing.
+
+Before releasing, ensure the tag resolves to the intended source commit, the matching
+PyPI project exists, and trusted publishing is configured for this repository's `pypi`
+GitHub environment. A tag that doesn't match the package version fails validation and
+isn't published.

yurli-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Project Authors
+
+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.