create-forge 0.2.0__tar.gz

create_forge-0.2.0/.gitignore

@@ -0,0 +1,220 @@
+# 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
+*.lcov
+.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/*
+!.pixi/config.toml
+
+# 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

create_forge-0.2.0/CHANGELOG.md

@@ -0,0 +1,67 @@
+# Changelog
+
+Generated by git-cliff from Conventional Commits.
+## [0.2.0] - 2026-08-30
+
+### Documentation
+
+- Mark v0.1.0 released in CLAUDE.md
+- Sync cross-repository dependency matrix
+- Link canonical Forge terminology
+- Link canonical Foundation scope
+- Link canonical Python support policy
+- Define cross-repository integration policy
+- Close roadmap stage 00
+- Define CLI UX and prompting conventions
+- Document cross-repository contributor workflow
+- Link canonical editor integration strategy
+- Link canonical configuration ownership
+- Link canonical environment-variable conventions
+- Link canonical structured logging contract
+- Define template-engine source and version resolution
+- Define template-engine dependency update policy
+- Link canonical GitHub Action pinning policy
+- Link canonical ProjectSpec protocol
+- Link canonical component manifest contract
+- Link stable template-engine API
+- Link generated-project validation
+- Link canonical Library archetype contract
+- Link canonical CLI application archetype contract
+
+### Features
+
+- Report engine and version diagnostics in doctor
+- Build the canonical ProjectSpec behind one engine adapter (#79)
+- Implement component discovery adapter
+- Implement the shared create pipeline behind an opt-in engine flag (#83)
+- Stage and finalise generation without leaving partials (#84)
+- Expose the CLI Application archetype through the engine path (#89)
+- Publish to PyPI and assign the first bounded engine range
+
+### Testing
+
+- Add cross-repository engine contract
+- Generate and check a real project end to end (#86)
+## [0.1.0] - 2026-08-22
+
+### Bug Fixes
+
+- Drop unasked task_runner prompt, add missing license prompt
+- Fall back to ASCII markers when the console can't encode check marks (#22)
+- Update always failed -- missing overwrite=True (#24)
+
+### Documentation
+
+- Add Architecture Decision Records (Phase 6) (#21)
+
+### Features
+
+- Wire config.py into cli.py
+
+### Refactor
+
+- Extract helpers from cli.new() (#27)
+
+### Testing
+
+- Add test suite and copier.yml drift guard (#13)

create_forge-0.2.0/LICENSE

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

create_forge-0.2.0/PKG-INFO

@@ -0,0 +1,207 @@
+Metadata-Version: 2.5
+Name: create-forge
+Version: 0.2.0
+Summary: Scaffold modern Python projects from maintained templates.
+Project-URL: Homepage, https://github.com/Sandsy09/create-forge
+Project-URL: Repository, https://github.com/Sandsy09/create-forge
+Project-URL: Issues, https://github.com/Sandsy09/create-forge/issues
+Project-URL: Changelog, https://github.com/Sandsy09/create-forge/blob/main/CHANGELOG.md
+Author: Alex
+License-Expression: MIT
+License-File: LICENSE
+Keywords: cookiecutter,copier,project,scaffold,template
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Requires-Dist: copier<10,>=9.4
+Requires-Dist: pydantic>=2.10
+Requires-Dist: questionary>=2.0
+Requires-Dist: rich>=13.9
+Requires-Dist: typer>=0.15
+Provides-Extra: engine
+Requires-Dist: forge-template<0.4,>=0.3.1; extra == 'engine'
+Description-Content-Type: text/markdown
+
+# create-forge
+
+[![CI](https://github.com/Sandsy09/create-forge/actions/workflows/ci.yml/badge.svg)](https://github.com/Sandsy09/create-forge/actions/workflows/ci.yml)
+
+Scaffold modern Python projects from maintained templates — and pull template
+improvements back into projects you generated months ago.
+
+```bash
+uvx create-forge new
+```
+
+No install step. Requires [uv](https://docs.astral.sh/uv/) and git.
+
+## Why
+
+Most project generators are fire-and-forget: you scaffold once, and from that
+moment your project drifts away from the template. Six months later the template
+has better lint rules, a security fix in CI, and a newer toolchain — and no path
+to get any of it into projects already in the wild.
+
+create-forge is built on [Copier](https://copier.readthedocs.io/), which does a
+three-way merge between the template version your project was generated from and
+the latest one. Local edits survive; template changes arrive.
+
+```bash
+uvx create-forge update
+```
+
+## What you get
+
+Every generated project ships with:
+
+- **[uv](https://docs.astral.sh/uv/)** for packaging and dependency management
+- **[Ruff](https://docs.astral.sh/ruff/)** for linting and formatting
+- **mypy** or **pyright** (or both) for type checking
+- **pytest** with coverage
+- **pre-commit** hooks, including Conventional Commits enforcement
+- **GitHub Actions** CI, with a test matrix across your supported Python versions
+- **Renovate** or **Dependabot** for dependency updates
+- `README`, `CONTRIBUTING`, `SECURITY`, `CHANGELOG`, issue and PR templates
+- Optionally: a MkDocs documentation site and ADR scaffolding
+
+Choices you make at scaffold time — build backend, versioning strategy, license,
+type checker — are remembered, so updates respect them.
+
+## Usage
+
+```bash
+# Interactive
+uvx create-forge new
+
+# Named up front
+uvx create-forge new "Credit Risk Utils"
+
+# Non-interactive, for scripts and CI
+uvx create-forge new "My Lib" --yes \
+  --data build_backend=hatchling \
+  --data versioning=vcs \
+  --data type_checking=both
+```
+
+| Command | What it does |
+| --- | --- |
+| `new` | Create a project |
+| `list` | Show available templates |
+| `update` | Pull template changes into an existing project |
+| `doctor` | Check your environment can scaffold and update |
+| `config` | Inspect or initialise your saved configuration |
+
+Useful flags on `new`: `--template/-t`, `--path/-p`, `--data/-d`, `--yes/-y`,
+`--ref`, `--dry-run`.
+
+## Configuration
+
+Optional. Saves retyping the same answers:
+
+```toml
+# ~/.config/create-forge/config.toml
+author_name = "Your Name"
+author_email = "you@example.com"
+github_org = "your-org"
+default_template = "library"
+```
+
+`create-forge config init` writes a commented starter file at that path
+without overwriting one that already exists. `create-forge config show`
+prints the resolved values and where each came from.
+
+`github_org` pre-fills its prompt — you're still asked, just with the answer
+already typed in. `author_name` and `author_email` aren't prompted for at all,
+so a configured value is applied directly. `default_template` picks which
+template `new` offers first, interactively or under `--yes`.
+
+Every key can be overridden with an environment variable —
+`FORGE_GITHUB_ORG` and so on — or a command line flag. Precedence is
+config < environment < `--data` < an interactive answer.
+
+## Templates
+
+Run `create-forge list` for what your installed version offers. The registry is
+bundled with each release, so new templates arrive when you update the tool.
+
+To use your own template:
+
+```bash
+uvx create-forge new --template-url https://github.com/you/your-template
+```
+
+This describes the released v0.1.x architecture. Forge has accepted a future
+[public-engine integration contract](docs/integration-contract.md) in which a
+versioned `forge-template` package owns discovery and rendering. Its strict
+[ProjectSpec protocol v1](https://github.com/Sandsy09/forge-template/blob/main/docs/project-spec.md)
+and [component manifest protocol v1](https://github.com/Sandsy09/forge-template/blob/main/docs/component-manifests.md)
+are now implemented behind the canonical
+[stable template-engine API](https://github.com/Sandsy09/forge-template/blob/main/docs/template-engine-api.md)
+([ADR 0029](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0029-stable-template-engine-api.md)).
+The accepted
+[Library archetype contract](https://github.com/Sandsy09/forge-template/blob/main/docs/library-archetype.md)
+defines the first production component, implemented on `forge-template/main`
+and released at `0.3.0`. The accepted
+[CLI Application archetype contract](https://github.com/Sandsy09/forge-template/blob/main/docs/cli-application-archetype.md)
+selects the optionless engine-owned `cli` archetype and derives its console
+command from `ProjectSpec.project.repository_name`;
+[FT-08.04](https://github.com/Sandsy09/forge-template/issues/4) implemented
+it in the same `0.3.0` release, and
+[CF-08.02](https://github.com/Sandsy09/create-forge/issues/10) exposes both
+archetypes behind the hidden `new --engine-preview` flag's `--archetype`
+option. Neither change alters this CLI's default `new` answers, registry, or
+released dependency surface.
+The engine now also defines in-memory
+[generated-project validation](https://github.com/Sandsy09/forge-template/blob/main/docs/generated-project-validation.md)
+([ADR 0030](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0030-generated-project-validation.md))
+before rendered output is returned; `render_project` already calls it before
+`--engine-preview` receives a result.
+This repository now depends on a real, released `forge-template` range —
+`>=0.3.1,<0.4`, published to PyPI as the optional `engine` extra
+(`pip install 'create-forge[engine]'`; [#9](https://github.com/Sandsy09/create-forge/issues/9),
+[ADR 0018](docs/adr/0018-pypi-distribution-and-the-first-engine-range.md)) —
+rather than a development-only pin. That range is reachable only behind
+`--engine-preview`; the current registry and `--template-url` behaviour
+remain unchanged until the complete, tested cutover is released — at which
+point `--engine-source`/`--engine-ref` (see the
+[engine resolution contract](docs/engine-resolution.md)) take over this role,
+not `--template-url`.
+
+## Security
+
+**create-forge executes code from the template it clones.** Copier templates can
+declare post-generation tasks, and this tool runs them — that is how a generated
+project arrives already git-initialised with hooks installed.
+
+The template addresses are compiled into each release rather than fetched at
+runtime or read from user configuration, so the only code trusted by default is
+code published alongside the tool. `--template-url` bypasses that, and prompts
+for confirmation before doing so. Point it only at repositories you trust.
+
+Report vulnerabilities per [SECURITY.md](SECURITY.md) rather than in a public
+issue.
+
+## Using this at work
+
+In v0.1.x, organisations needing custom executable templates can fork this
+repository, point the bundled registry at their own templates, and maintain it
+internally. The accepted target makes a downstream client of the
+`forge-template` public engine the preferred route for organisation defaults
+and constraints. Forks remain appropriate for genuinely custom executable
+template content; see the [integration contract](docs/integration-contract.md).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md). Issues and pull requests welcome.
+Significant design decisions are recorded in [docs/adr/](docs/adr/).
+
+## License
+
+MIT — see [LICENSE](LICENSE).

create_forge-0.2.0/README.md

@@ -0,0 +1,176 @@
+# create-forge
+
+[![CI](https://github.com/Sandsy09/create-forge/actions/workflows/ci.yml/badge.svg)](https://github.com/Sandsy09/create-forge/actions/workflows/ci.yml)
+
+Scaffold modern Python projects from maintained templates — and pull template
+improvements back into projects you generated months ago.
+
+```bash
+uvx create-forge new
+```
+
+No install step. Requires [uv](https://docs.astral.sh/uv/) and git.
+
+## Why
+
+Most project generators are fire-and-forget: you scaffold once, and from that
+moment your project drifts away from the template. Six months later the template
+has better lint rules, a security fix in CI, and a newer toolchain — and no path
+to get any of it into projects already in the wild.
+
+create-forge is built on [Copier](https://copier.readthedocs.io/), which does a
+three-way merge between the template version your project was generated from and
+the latest one. Local edits survive; template changes arrive.
+
+```bash
+uvx create-forge update
+```
+
+## What you get
+
+Every generated project ships with:
+
+- **[uv](https://docs.astral.sh/uv/)** for packaging and dependency management
+- **[Ruff](https://docs.astral.sh/ruff/)** for linting and formatting
+- **mypy** or **pyright** (or both) for type checking
+- **pytest** with coverage
+- **pre-commit** hooks, including Conventional Commits enforcement
+- **GitHub Actions** CI, with a test matrix across your supported Python versions
+- **Renovate** or **Dependabot** for dependency updates
+- `README`, `CONTRIBUTING`, `SECURITY`, `CHANGELOG`, issue and PR templates
+- Optionally: a MkDocs documentation site and ADR scaffolding
+
+Choices you make at scaffold time — build backend, versioning strategy, license,
+type checker — are remembered, so updates respect them.
+
+## Usage
+
+```bash
+# Interactive
+uvx create-forge new
+
+# Named up front
+uvx create-forge new "Credit Risk Utils"
+
+# Non-interactive, for scripts and CI
+uvx create-forge new "My Lib" --yes \
+  --data build_backend=hatchling \
+  --data versioning=vcs \
+  --data type_checking=both
+```
+
+| Command | What it does |
+| --- | --- |
+| `new` | Create a project |
+| `list` | Show available templates |
+| `update` | Pull template changes into an existing project |
+| `doctor` | Check your environment can scaffold and update |
+| `config` | Inspect or initialise your saved configuration |
+
+Useful flags on `new`: `--template/-t`, `--path/-p`, `--data/-d`, `--yes/-y`,
+`--ref`, `--dry-run`.
+
+## Configuration
+
+Optional. Saves retyping the same answers:
+
+```toml
+# ~/.config/create-forge/config.toml
+author_name = "Your Name"
+author_email = "you@example.com"
+github_org = "your-org"
+default_template = "library"
+```
+
+`create-forge config init` writes a commented starter file at that path
+without overwriting one that already exists. `create-forge config show`
+prints the resolved values and where each came from.
+
+`github_org` pre-fills its prompt — you're still asked, just with the answer
+already typed in. `author_name` and `author_email` aren't prompted for at all,
+so a configured value is applied directly. `default_template` picks which
+template `new` offers first, interactively or under `--yes`.
+
+Every key can be overridden with an environment variable —
+`FORGE_GITHUB_ORG` and so on — or a command line flag. Precedence is
+config < environment < `--data` < an interactive answer.
+
+## Templates
+
+Run `create-forge list` for what your installed version offers. The registry is
+bundled with each release, so new templates arrive when you update the tool.
+
+To use your own template:
+
+```bash
+uvx create-forge new --template-url https://github.com/you/your-template
+```
+
+This describes the released v0.1.x architecture. Forge has accepted a future
+[public-engine integration contract](docs/integration-contract.md) in which a
+versioned `forge-template` package owns discovery and rendering. Its strict
+[ProjectSpec protocol v1](https://github.com/Sandsy09/forge-template/blob/main/docs/project-spec.md)
+and [component manifest protocol v1](https://github.com/Sandsy09/forge-template/blob/main/docs/component-manifests.md)
+are now implemented behind the canonical
+[stable template-engine API](https://github.com/Sandsy09/forge-template/blob/main/docs/template-engine-api.md)
+([ADR 0029](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0029-stable-template-engine-api.md)).
+The accepted
+[Library archetype contract](https://github.com/Sandsy09/forge-template/blob/main/docs/library-archetype.md)
+defines the first production component, implemented on `forge-template/main`
+and released at `0.3.0`. The accepted
+[CLI Application archetype contract](https://github.com/Sandsy09/forge-template/blob/main/docs/cli-application-archetype.md)
+selects the optionless engine-owned `cli` archetype and derives its console
+command from `ProjectSpec.project.repository_name`;
+[FT-08.04](https://github.com/Sandsy09/forge-template/issues/4) implemented
+it in the same `0.3.0` release, and
+[CF-08.02](https://github.com/Sandsy09/create-forge/issues/10) exposes both
+archetypes behind the hidden `new --engine-preview` flag's `--archetype`
+option. Neither change alters this CLI's default `new` answers, registry, or
+released dependency surface.
+The engine now also defines in-memory
+[generated-project validation](https://github.com/Sandsy09/forge-template/blob/main/docs/generated-project-validation.md)
+([ADR 0030](https://github.com/Sandsy09/forge-template/blob/main/docs/adr/0030-generated-project-validation.md))
+before rendered output is returned; `render_project` already calls it before
+`--engine-preview` receives a result.
+This repository now depends on a real, released `forge-template` range —
+`>=0.3.1,<0.4`, published to PyPI as the optional `engine` extra
+(`pip install 'create-forge[engine]'`; [#9](https://github.com/Sandsy09/create-forge/issues/9),
+[ADR 0018](docs/adr/0018-pypi-distribution-and-the-first-engine-range.md)) —
+rather than a development-only pin. That range is reachable only behind
+`--engine-preview`; the current registry and `--template-url` behaviour
+remain unchanged until the complete, tested cutover is released — at which
+point `--engine-source`/`--engine-ref` (see the
+[engine resolution contract](docs/engine-resolution.md)) take over this role,
+not `--template-url`.
+
+## Security
+
+**create-forge executes code from the template it clones.** Copier templates can
+declare post-generation tasks, and this tool runs them — that is how a generated
+project arrives already git-initialised with hooks installed.
+
+The template addresses are compiled into each release rather than fetched at
+runtime or read from user configuration, so the only code trusted by default is
+code published alongside the tool. `--template-url` bypasses that, and prompts
+for confirmation before doing so. Point it only at repositories you trust.
+
+Report vulnerabilities per [SECURITY.md](SECURITY.md) rather than in a public
+issue.
+
+## Using this at work
+
+In v0.1.x, organisations needing custom executable templates can fork this
+repository, point the bundled registry at their own templates, and maintain it
+internally. The accepted target makes a downstream client of the
+`forge-template` public engine the preferred route for organisation defaults
+and constraints. Forks remain appropriate for genuinely custom executable
+template content; see the [integration contract](docs/integration-contract.md).
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md). Issues and pull requests welcome.
+Significant design decisions are recorded in [docs/adr/](docs/adr/).
+
+## License
+
+MIT — see [LICENSE](LICENSE).