abilian-astero 0.1.0__tar.gz

abilian_astero-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Stefane Fermigier
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

abilian_astero-0.1.0/PKG-INFO

@@ -0,0 +1,163 @@
+Metadata-Version: 2.4
+Name: abilian-astero
+Version: 0.1.0
+Summary: astero: declared grammars for ASTs and IRs, and the transformations derived from them.
+Keywords: compiler,ast,grammar,transpiler,code-generation
+Author: Stefane Fermigier
+Author-email: Stefane Fermigier <sf@abilian.com>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Classifier: Development Status :: 3 - Alpha
+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 :: Compilers
+Classifier: Topic :: Software Development :: Code Generators
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Project-URL: Documentation, https://astero.lab.abilian.com
+Description-Content-Type: text/markdown
+
+# astero
+
+**Write compilers, transpilers and code analysers without hand-maintaining the tables they depend on.**
+
+Every program that transforms code needs to know the same structural facts about its language: which positions introduce a variable, which read one, which fields a traversal must enter, how tightly each operator binds. Most projects write those facts out by hand, once per pass. They drift. When they drift the symptom is wrong output, not a crash.
+
+astero takes one declaration of your syntax tree and computes those facts on demand. Python's grammar ships with the library, so for Python source there is nothing to declare.
+
+```bash
+pip install abilian-astero        # or: uv add abilian-astero
+```
+
+The distribution is called **abilian-astero**, because PyPI already had `astero`. The import name is `astero`:
+
+```python
+from astero.lang_py import PY, VARS
+```
+
+Python 3.11 through 3.15. No runtime dependencies. Apache-2.0.
+
+## The problem it solves
+
+Fifteen positions in Python can hold a variable name. Here are four of them:
+
+```python
+def f(x):                      # a parameter
+    import os as x             # an import alias
+    try:
+        pass
+    except E as x:             # an exception name
+        pass
+    return [x for x in xs]     # a comprehension target
+```
+
+A renamer written with `ast.NodeTransformer` and a `visit_Name` method reaches one. That is not a hypothetical: it is the shape of a defect found in three separate compilers, and none of the three crashed. One never bound `**kwargs`, one inlined a function so that `[99 for 99 in xs]` came out, one set an assignment context by hand and produced JavaScript that computed `NaN` where Python gave `5`.
+
+With astero the list is a query, and the same query serves every pass that needs it:
+
+```python
+from astero.hygiene import rename
+from astero.lang_py import PY, VARS
+
+rename(tree, {"x": "y"}, PY, VARS)      # reaches all fifteen
+```
+
+The set changes between Python releases. Version 3.12 added three positions. Code written against the query follows the language without being edited.
+
+## What you get
+
+Declare a **role** for each field of each production: whether it introduces a name, refers to one, or holds a subtree. Six modules read that declaration.
+
+| module | what it gives you |
+| --- | --- |
+| `grammar` | which fields bind a name, which read one, which hold a bare identifier, which a traversal must enter, which productions can appear |
+| `rewriting` | tree rewriting from `pattern => result` rules, with every `Name`'s context recomputed for you |
+| `scopes` | the scope tree of a module, and the names each scope binds |
+| `hygiene` | renaming, and substitution that cannot capture a name |
+| `emit_rules` | a code generator written as templates, with brackets derived from a precedence table |
+| `coverage` | a test that fails when your dispatch table misses a production |
+
+Add a binding form to your language, edit the declaration, and all six follow.
+
+### Rewriting, without touching contexts
+
+A rule is one string with `=>` between pattern and replacement:
+
+```python
+from astero import Pass, rules
+
+fold = Pass("fold", rules("""
+    _x + 0 => _x
+    _x * 1 => _x
+"""))
+```
+
+Identifiers spelled `_name` are metavariables, `_` matches anything without binding, and `*_xs` splices the rest of a list. Rules never mention `ctx` or source positions, because both are recomputed from the shape of the result. That is what makes the `AugAssign` defect above impossible to write.
+
+### Your own IR, not just Python's
+
+A grammar carries each production's constructor, so a rewrite builds your node classes. If your AST is generated from CPython's, the whole declaration is one line:
+
+```python
+PRESCRYPT = lang_py.build(module=prescrypt.front.ast.ast, name="prescrypt")
+```
+
+If your IR is annotated dataclasses, `from_dataclasses` reads the fields and sorts off the annotations, leaving you only the roles to write. The [PL/0 tutorial](https://astero.lab.abilian.com/tutorial-pl0/) builds a complete compiler that way, for a language with no relationship to Python.
+
+## Why you can rely on it
+
+Every derivation is compared against an independent source of truth, over the whole Python standard library, on Python 3.11 through 3.15.
+
+| derived | compared against | result |
+| --- | --- | --- |
+| assignment contexts | what CPython's parser produces | every position in the standard library, no disagreements |
+| scopes and their names | CPython's `symtable` | 99.98% of blocks agree |
+| emitted source | reparsing the emitted text | 1,797 modules, 2,266,043 expressions |
+| operand positions of an SSA IR | that compiler's own declaration | exact match |
+
+For assignment contexts that is ten authored role entries reconstructing all 1,457,931 positions across the 1,761 files of the 3.13 standard library. The tests hold the ratio, not the number. A regression fails; an improvement does not have to be chased.
+
+The rewrite engine was first validated by reimplementing all six of [latexify_py](https://github.com/google/latexify_py)'s tree transformations as rule sets. Differential testing against the originals found 121 output differences, **every one a latent bug in the hand-written version**.
+
+Three compilers are built on it: a Python-to-C compiler, a Python-to-WebAssembly compiler, and a Python-to-JavaScript transpiler.
+
+## What astero is not
+
+- **Not a parser.** Bring your own AST. astero starts from a tree.
+- **Not a code generator you run.** Nothing is written to disk, and there is no build step. Every entry point is a function call at run time.
+- **Not a framework.** It does not own your pipeline, your IR, or your `main`. Adopt one query in one function and leave the rest alone.
+
+Lowering and cost models stay yours. astero answers questions about a declaration; it does not decide what your compiler should do with the answers.
+
+## Documentation
+
+- **[Getting started](https://astero.lab.abilian.com/getting-started/)**: install it and run three queries against real code.
+- **[TinyPy tutorial](https://astero.lab.abilian.com/tutorial/)**: a working compiler for a Python subset, with two back ends, in about 170 lines.
+- **[PL/0 tutorial](https://astero.lab.abilian.com/tutorial-pl0/)**: the same, for a language that is not Python.
+- **[User guide](https://astero.lab.abilian.com/guides/user-guide/)**: every module, its API, and when to reach for it.
+- **[Adopting astero](https://astero.lab.abilian.com/guides/adopting/)**: fitting it into a compiler you already have.
+- **[API reference](https://astero.lab.abilian.com/api/grammar/)**: generated from the source.
+
+## Status
+
+Version 0.1.x. The API may still change between minor versions; the changelog says what moved. Every derivation is checked against CPython on five interpreters, and three compilers are built on it.
+
+## Development
+
+```bash
+make test     # pytest
+make lint     # ruff, ruff format, ty, pyrefly, zuban, mypy
+make docs     # build the documentation site
+```
+
+This code is version-sensitive, so a green run on one interpreter says little about the others. `nox` runs the suite on each:
+
+```bash
+nox -s tests            # 3.11 through 3.15
+nox -s check            # everything `make lint` runs
+```
+
+Contributions are welcome. `docs/src/guides/developer-guide.md` describes how the library is organised and what a new derivation has to prove before it lands.

abilian_astero-0.1.0/README.md

@@ -0,0 +1,141 @@
+# astero
+
+**Write compilers, transpilers and code analysers without hand-maintaining the tables they depend on.**
+
+Every program that transforms code needs to know the same structural facts about its language: which positions introduce a variable, which read one, which fields a traversal must enter, how tightly each operator binds. Most projects write those facts out by hand, once per pass. They drift. When they drift the symptom is wrong output, not a crash.
+
+astero takes one declaration of your syntax tree and computes those facts on demand. Python's grammar ships with the library, so for Python source there is nothing to declare.
+
+```bash
+pip install abilian-astero        # or: uv add abilian-astero
+```
+
+The distribution is called **abilian-astero**, because PyPI already had `astero`. The import name is `astero`:
+
+```python
+from astero.lang_py import PY, VARS
+```
+
+Python 3.11 through 3.15. No runtime dependencies. Apache-2.0.
+
+## The problem it solves
+
+Fifteen positions in Python can hold a variable name. Here are four of them:
+
+```python
+def f(x):                      # a parameter
+    import os as x             # an import alias
+    try:
+        pass
+    except E as x:             # an exception name
+        pass
+    return [x for x in xs]     # a comprehension target
+```
+
+A renamer written with `ast.NodeTransformer` and a `visit_Name` method reaches one. That is not a hypothetical: it is the shape of a defect found in three separate compilers, and none of the three crashed. One never bound `**kwargs`, one inlined a function so that `[99 for 99 in xs]` came out, one set an assignment context by hand and produced JavaScript that computed `NaN` where Python gave `5`.
+
+With astero the list is a query, and the same query serves every pass that needs it:
+
+```python
+from astero.hygiene import rename
+from astero.lang_py import PY, VARS
+
+rename(tree, {"x": "y"}, PY, VARS)      # reaches all fifteen
+```
+
+The set changes between Python releases. Version 3.12 added three positions. Code written against the query follows the language without being edited.
+
+## What you get
+
+Declare a **role** for each field of each production: whether it introduces a name, refers to one, or holds a subtree. Six modules read that declaration.
+
+| module | what it gives you |
+| --- | --- |
+| `grammar` | which fields bind a name, which read one, which hold a bare identifier, which a traversal must enter, which productions can appear |
+| `rewriting` | tree rewriting from `pattern => result` rules, with every `Name`'s context recomputed for you |
+| `scopes` | the scope tree of a module, and the names each scope binds |
+| `hygiene` | renaming, and substitution that cannot capture a name |
+| `emit_rules` | a code generator written as templates, with brackets derived from a precedence table |
+| `coverage` | a test that fails when your dispatch table misses a production |
+
+Add a binding form to your language, edit the declaration, and all six follow.
+
+### Rewriting, without touching contexts
+
+A rule is one string with `=>` between pattern and replacement:
+
+```python
+from astero import Pass, rules
+
+fold = Pass("fold", rules("""
+    _x + 0 => _x
+    _x * 1 => _x
+"""))
+```
+
+Identifiers spelled `_name` are metavariables, `_` matches anything without binding, and `*_xs` splices the rest of a list. Rules never mention `ctx` or source positions, because both are recomputed from the shape of the result. That is what makes the `AugAssign` defect above impossible to write.
+
+### Your own IR, not just Python's
+
+A grammar carries each production's constructor, so a rewrite builds your node classes. If your AST is generated from CPython's, the whole declaration is one line:
+
+```python
+PRESCRYPT = lang_py.build(module=prescrypt.front.ast.ast, name="prescrypt")
+```
+
+If your IR is annotated dataclasses, `from_dataclasses` reads the fields and sorts off the annotations, leaving you only the roles to write. The [PL/0 tutorial](https://astero.lab.abilian.com/tutorial-pl0/) builds a complete compiler that way, for a language with no relationship to Python.
+
+## Why you can rely on it
+
+Every derivation is compared against an independent source of truth, over the whole Python standard library, on Python 3.11 through 3.15.
+
+| derived | compared against | result |
+| --- | --- | --- |
+| assignment contexts | what CPython's parser produces | every position in the standard library, no disagreements |
+| scopes and their names | CPython's `symtable` | 99.98% of blocks agree |
+| emitted source | reparsing the emitted text | 1,797 modules, 2,266,043 expressions |
+| operand positions of an SSA IR | that compiler's own declaration | exact match |
+
+For assignment contexts that is ten authored role entries reconstructing all 1,457,931 positions across the 1,761 files of the 3.13 standard library. The tests hold the ratio, not the number. A regression fails; an improvement does not have to be chased.
+
+The rewrite engine was first validated by reimplementing all six of [latexify_py](https://github.com/google/latexify_py)'s tree transformations as rule sets. Differential testing against the originals found 121 output differences, **every one a latent bug in the hand-written version**.
+
+Three compilers are built on it: a Python-to-C compiler, a Python-to-WebAssembly compiler, and a Python-to-JavaScript transpiler.
+
+## What astero is not
+
+- **Not a parser.** Bring your own AST. astero starts from a tree.
+- **Not a code generator you run.** Nothing is written to disk, and there is no build step. Every entry point is a function call at run time.
+- **Not a framework.** It does not own your pipeline, your IR, or your `main`. Adopt one query in one function and leave the rest alone.
+
+Lowering and cost models stay yours. astero answers questions about a declaration; it does not decide what your compiler should do with the answers.
+
+## Documentation
+
+- **[Getting started](https://astero.lab.abilian.com/getting-started/)**: install it and run three queries against real code.
+- **[TinyPy tutorial](https://astero.lab.abilian.com/tutorial/)**: a working compiler for a Python subset, with two back ends, in about 170 lines.
+- **[PL/0 tutorial](https://astero.lab.abilian.com/tutorial-pl0/)**: the same, for a language that is not Python.
+- **[User guide](https://astero.lab.abilian.com/guides/user-guide/)**: every module, its API, and when to reach for it.
+- **[Adopting astero](https://astero.lab.abilian.com/guides/adopting/)**: fitting it into a compiler you already have.
+- **[API reference](https://astero.lab.abilian.com/api/grammar/)**: generated from the source.
+
+## Status
+
+Version 0.1.x. The API may still change between minor versions; the changelog says what moved. Every derivation is checked against CPython on five interpreters, and three compilers are built on it.
+
+## Development
+
+```bash
+make test     # pytest
+make lint     # ruff, ruff format, ty, pyrefly, zuban, mypy
+make docs     # build the documentation site
+```
+
+This code is version-sensitive, so a green run on one interpreter says little about the others. `nox` runs the suite on each:
+
+```bash
+nox -s tests            # 3.11 through 3.15
+nox -s check            # everything `make lint` runs
+```
+
+Contributions are welcome. `docs/src/guides/developer-guide.md` describes how the library is organised and what a new derivation has to prove before it lands.

abilian_astero-0.1.0/pyproject.toml

@@ -0,0 +1,149 @@
+[project]
+name = "abilian-astero"
+version = "0.1.0"
+description = "astero: declared grammars for ASTs and IRs, and the transformations derived from them."
+readme = "README.md"
+authors = [
+    { name = "Stefane Fermigier", email = "sf@abilian.com" }
+]
+requires-python = ">=3.11"
+dependencies = []
+license = "Apache-2.0"
+license-files = ["LICENSE"]
+keywords = ["compiler", "ast", "grammar", "transpiler", "code-generation"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Topic :: Software Development :: Compilers",
+    "Topic :: Software Development :: Code Generators",
+    "Typing :: Typed",
+]
+
+[project.urls]
+Documentation = "https://astero.lab.abilian.com"
+
+
+[build-system]
+requires = ["uv_build>=0.11.33,<0.12.0"]
+build-backend = "uv_build"
+
+[tool.uv.build-backend]
+# The distribution is `abilian-astero` because PyPI would not give up
+# `astero`, but the import name is and stays `astero`. Without this the
+# backend derives the module path from the project name and looks for
+# `src/abilian_astero/`.
+module-name = "astero"
+
+[dependency-groups]
+docs = [
+    # Zensical's published versions are 0.0.x, and it needs a recent Python.
+    # This project's floor is 3.11, so the group is marked rather than pinned:
+    # `make docs` on an older interpreter is the only thing it affects.
+    "zensical>=0.0.54; python_version >= '3.13' and python_version < '3.15'",
+    # The API reference is generated from the source's own docstrings, so it
+    # cannot drift. Zensical shims the mkdocs plugin.
+    "mkdocstrings[python]>=0.27; python_version >= '3.13' and python_version < '3.15'",
+]
+# What running the suite needs, and nothing else. Separate from `dev`
+# because the version matrix installs it on every supported interpreter, and
+# `pre-commit` pulls in `pyyaml`, which does not build on 3.15.
+test = [
+    "pytest>=9.1.1",
+    "pytest-cov>=7.1.0",
+]
+dev = [
+    { include-group = "test" },
+    # postpile's own dependency, and the only thing standing between the SSA
+    # oracles and running. It does not make postpile a dependency: those
+    # tests still locate a checkout (`POSTPILE_SRC`, or a sibling directory)
+    # and skip when there is none. Without this they skipped on the import
+    # instead, so the oracle never ran and nothing said so.
+    "postyp>=0.3.0",
+    "mypy>=2.3.0",
+    "nox>=2026.7.11",
+    "pre-commit>=4.6.1",
+    "pyrefly>=1.2.0",
+    "ruff>=0.16.2",
+    "ty>=0.0.69",
+    "zuban>=0.9.1",
+    # tepyd needs 3.12; this project's floor is 3.11, so the marker keeps the
+    # lock resolvable there. Same shape as the `docs` group's zensical pin.
+    "tepyd; python_version >= '3.12'",
+]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+markers = [
+    "unit: fast, isolated unit tests",
+    "integration: component-interaction tests",
+    "e2e: end-to-end tests",
+]
+
+[tool.ty.environment]
+# The two worked examples are standalone programs, not packages: their modules
+# import each other by bare name (`import syntax`), and the tests put the
+# directory on `sys.path` to run them. That is the shape a reader copies, so
+# the type checker is told where to look rather than the examples being made
+# into packages nobody would write.
+extra-paths = ["examples/pl0", "examples/tinypy"]
+
+
+[tool.mypy]
+# zuban reads mypy's configuration. `mypy_path` is the same fact as
+# `[tool.ty.environment] extra-paths` and pyrefly's `search-path`: the worked
+# examples import each other by bare name. `make lint` runs mypy over `src`
+# only, so this changes nothing for it and everything for zuban.
+mypy_path = "src:examples/pl0:examples/tinypy"
+
+[[tool.mypy.overrides]]
+# zuban reads `operator.mod` as returning `None`, which typeshed does not
+# say and mypy does not agree with. Scoped to the one rule and the one
+# module rather than worked around in the code.
+module = ["vm"]
+disable_error_code = ["dict-item"]
+
+[tool.pyrefly]
+project-includes = [
+    "**/*.py*",
+    "**/*.ipynb",
+]
+# Same reason as `[tool.ty.environment]` above: the worked examples are
+# standalone programs whose modules import each other by bare name.
+search-path = ["src", "examples/pl0", "examples/tinypy"]
+
+[tool.tepyd]
+# Generated by `tepyd init` — review and adjust.
+src_root = "src/astero"
+src_package = "astero"
+units = ["*.py"]
+# counter = "internal"   # or "cloc"
+
+# Source units to exclude from analysis (a reason is required):
+# [tool.tepyd.exclude]
+# faker = "why this is not tested"
+
+# Tiers, cheapest first. Add `expects = [...]` to a tier to scope it to
+# the source units it should test (glob patterns over unit names); units
+# outside the scope are reported n/a, not as gaps. Use it when layers map
+# to tiers — e.g. integration `expects = ["repositories/*", "infra/*"]`,
+# e2e `expects = ["web/*"]`. Omit it and the tier is checked against all.
+
+[[tool.tepyd.tiers]]
+name = "a_unit"
+root = "tests/a_unit"
+label = "unit"
+target_share = 0.6
+
+[[tool.tepyd.tiers]]
+name = "b_integration"
+root = "tests/b_integration"
+label = "integration"
+
+[[tool.tepyd.tiers]]
+name = "c_e2e"
+root = "tests/c_e2e"
+label = "e2e"