gh-slate 0.1.0__tar.gz

gh_slate-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2026-present, Nyakku Shigure
+
+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.

gh_slate-0.1.0/PKG-INFO

@@ -0,0 +1,260 @@
+Metadata-Version: 2.4
+Name: gh-slate
+Version: 0.1.0
+Summary: Manage named, data-backed dashboard comments on GitHub Issues and Pull Requests.
+Keywords: github,cli,dashboard,issues,pull-requests,markdown
+Author: Nyakku Shigure
+Author-email: Nyakku Shigure <sigure.qaq@gmail.com>
+License-Expression: MIT
+License-File: LICENSE
+Classifier: Environment :: Console
+Classifier: Operating System :: OS Independent
+Classifier: Typing :: Typed
+Classifier: Programming Language :: Python
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+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: Programming Language :: Python :: Implementation :: CPython
+Requires-Dist: jinja2>=3.1.6,<3.2
+Requires-Dist: jsonpatch>=1.33,<2
+Requires-Dist: jsonpointer>=3.1,<4
+Requires-Dist: jsonschema>=4.25,<5
+Requires-Dist: referencing>=0.36,<1
+Requires-Dist: regex>=2025.7.34,<2027
+Requires-Dist: tomli>=2.2,<3 ; python_full_version < '3.11'
+Requires-Python: >=3.10
+Project-URL: Homepage, https://github.com/ShigureLab/gh-slate
+Project-URL: Documentation, https://github.com/ShigureLab/gh-slate
+Project-URL: Repository, https://github.com/ShigureLab/gh-slate
+Project-URL: Issues, https://github.com/ShigureLab/gh-slate/issues
+Description-Content-Type: text/markdown
+
+# gh-slate
+
+Manage named, data-backed dashboard comments on GitHub Issues and Pull Requests.
+
+<p align="center">
+   <a href="https://python.org/" target="_blank"><img alt="PyPI - Python Version" src="https://img.shields.io/pypi/pyversions/gh-slate?logo=python&style=flat-square"></a>
+   <a href="https://pypi.org/project/gh-slate/" target="_blank"><img src="https://img.shields.io/pypi/v/gh-slate?style=flat-square" alt="pypi"></a>
+   <a href="https://pypi.org/project/gh-slate/" target="_blank"><img alt="PyPI - Downloads" src="https://img.shields.io/pypi/dm/gh-slate?style=flat-square"></a>
+   <a href="LICENSE"><img alt="LICENSE" src="https://img.shields.io/github/license/ShigureLab/gh-slate?style=flat-square"></a>
+   <br/>
+   <a href="https://github.com/astral-sh/uv"><img alt="uv" src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json&style=flat-square"></a>
+   <a href="https://github.com/astral-sh/ruff"><img alt="ruff" src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json&style=flat-square"></a>
+   <a href="https://gitmoji.dev"><img alt="Gitmoji" src="https://img.shields.io/badge/gitmoji-%20😜%20😍-FFDD67?style=flat-square"></a>
+</p>
+
+## Install
+
+Requirements:
+
+- Python 3.10 or newer;
+- `gh`, authenticated for the target host;
+- `uv` for the Python tool installation and, on supported Unix platforms, the
+  repository-backed GitHub CLI extension launcher.
+
+Until the first PyPI release, install the Python CLI from a checkout. This is
+also the supported development install on Windows:
+
+```bash
+git clone https://github.com/ShigureLab/gh-slate.git
+cd gh-slate
+uv tool install .
+gh-slate --help
+```
+
+After a release is published to PyPI, install the Python tool with:
+
+```bash
+uv tool install gh-slate
+gh-slate --help
+```
+
+The PyPI package and `gh-slate` Python CLI are runtime-tested on Linux, macOS,
+and Windows. On macOS/Linux or another Unix environment with Bash and `uv`, the
+repository can instead be installed as a GitHub CLI extension:
+
+```bash
+gh extension install ShigureLab/gh-slate
+gh slate --help
+```
+
+The current root extension launcher is a Bash script and is not a supported
+Windows entrypoint; use the Python CLI on Windows. On supported platforms both
+entrypoints expose the same parser. The public names are:
+
+```text
+PyPI distribution       gh-slate
+Python import package   gh_slate
+console script          gh-slate
+GitHub repository       gh-slate
+gh extension command    gh slate
+```
+
+### Install the agent skill separately
+
+The bundled skill teaches an agent the safe inspect/dry-run/mutate/verify
+workflow. Installing the CLI does not install the skill, and installing the
+skill does not install the CLI. With Node.js/npm available, install it through
+the cross-agent `skills` CLI:
+
+```bash
+npx skills add https://github.com/ShigureLab/gh-slate --skill gh-slate
+```
+
+GitHub CLI 2.96 or newer can install the same skill through its native,
+currently preview, skill command:
+
+```bash
+gh skill install ShigureLab/gh-slate gh-slate --agent codex --scope user
+```
+
+## Quick start
+
+Check authentication and local dependencies:
+
+```bash
+gh auth status
+gh slate doctor --json
+```
+
+Use the checked-in [CI, review, and benchmark profiles](examples/profiles).
+Preview a review locally, then against a real target before publishing:
+
+```bash
+gh slate render review --config examples/profiles/boards.toml --profile review --data examples/profiles/review-changes.json
+gh slate apply review --target https://github.com/OWNER/REPO/pull/42 --config examples/profiles/boards.toml --profile review --data examples/profiles/review-changes.json --dry-run --json
+gh slate apply review --target https://github.com/OWNER/REPO/pull/42 --config examples/profiles/boards.toml --profile review --data examples/profiles/review-changes.json --json
+```
+
+Replace the target URL before publishing. The examples contain synthetic data.
+Use `gh-slate` in place of `gh slate` with the Python CLI.
+
+Read the current data and revision, or switch to the approval layout by sending
+a new snapshot. Omitting the profile reuses the definition stored on GitHub:
+
+```bash
+gh slate view review --target https://github.com/OWNER/REPO/pull/42 --json
+gh slate apply review --target https://github.com/OWNER/REPO/pull/42 --data examples/profiles/review-approved.json --json
+gh slate list --target https://github.com/OWNER/REPO/pull/42 --json
+gh slate state export review --target https://github.com/OWNER/REPO/pull/42
+gh slate state verify review --target https://github.com/OWNER/REPO/pull/42 --json
+```
+
+The review profile maps `data.outcome` to `approved`, `changes_requested`, or
+`error`. Those names belong to the profile; the core only follows its JSON
+Pointer and exact view map. Missing or unknown outcomes fail before writing.
+Each view can have a different layout and schema branch.
+
+For a partial edit, use a standard RFC 6902 patch and the revision read from
+`view --json`. For example, while the review contains finding F17:
+
+```bash
+gh slate apply review --target https://github.com/OWNER/REPO/pull/42 --patch examples/profiles/resolve-finding.patch.json --if-revision 3 --dry-run --json
+```
+
+Replace `3` with the observed revision. The dry-run reports candidate data,
+Markdown, data changes, definition/meta changes, and view transitions. Remove
+`--dry-run` to publish. Patch and full data use the same writer; failure performs
+no write and a no-op preserves revision.
+
+## Definitions and templates
+
+Configuration is explicit: `--config FILE` overrides `GH_SLATE_CONFIG`.
+There is no default directory search or config merging. File paths are relative
+to the TOML file, and `--profile NAME` selects a definition:
+
+```toml
+
+[profiles.ci]
+schema = "ci.schema.json"
+template = "ci.md.j2"
+
+[profiles.review]
+schema = "review.schema.json"
+view_by = "/outcome"
+
+[profiles.review.views]
+approved = "approved.md.j2"
+changes_requested = "changes.md.j2"
+error = "error.md.j2"
+```
+
+Single-template definitions also work directly with `--template FILE` and
+optional `--schema FILE`. Profile and direct definition overrides are mutually
+exclusive. Pass `--profile` explicitly to reload a changed definition; normal
+data updates never read local config files.
+
+Templates receive business `data` and read-only `meta`:
+
+```jinja2
+## {{ meta.slate.name }}
+{% if meta.target is not none %}
+Target: {{ meta.repository.full_name | md_link(meta.target.url) }} #{{ meta.target.number }}
+{% endif %}
+
+{{ data.jobs | md_table(columns=["name", "status"]) }}
+{{ data.notes | md_list }}
+```
+
+Ordinary interpolated strings are escaped. Use `md_text`, `md_link`, `md_code`,
+`md_codeblock`, `md_table`, `md_list`, and `md_details` for composable Markdown.
+Sandbox limits bound template source, loops, output, and the complete comment.
+There is no include loader, filesystem access, or arbitrary Python call.
+
+`meta` contains host, repository identity, target kind/number/node ID/URL, and
+slate name. Apply obtains it from GitHub and stores the exact render snapshot.
+Local render sets host/repository/target to null unless given `--meta FILE`.
+Use `apply --dry-run` for a preview with real target metadata. An analyzed
+commit, run ID, or timestamp belongs in `data.source`; gh-slate never replaces
+it with a newer revision merely because the target changed.
+
+## Read and recover
+
+| Task                                             | Command                          |
+| ------------------------------------------------ | -------------------------------- |
+| Local or stored-state preview                    | `render`                         |
+| Publish a full snapshot or RFC 6902 patch        | `apply --data` / `apply --patch` |
+| Read current data, metadata, revision, and view  | `view --json`                    |
+| List managed comments                            | `list --json`                    |
+| Export the complete embedded definition and data | `state export`                   |
+| Verify integrity and reproduce rendering         | `state verify`                   |
+| Restore visible Markdown from state              | `repair --from-state`            |
+| Remove one managed comment                       | `delete --confirm NAME`          |
+| Check authentication and local dependencies      | `doctor`                         |
+
+```bash
+gh slate render review --target https://github.com/OWNER/REPO/pull/42
+gh slate view review --target https://github.com/OWNER/REPO/pull/42 --web
+gh slate repair review --target https://github.com/OWNER/REPO/pull/42 --from-state --if-revision 3 --json
+gh slate delete review --target https://github.com/OWNER/REPO/pull/42 --confirm review --json
+```
+
+## Publishing guarantees
+
+Names are scoped to target and controller; they match
+`[a-z0-9][a-z0-9._-]{0,63}` and cannot contain `--`. Default apply mode is `upsert`;
+`create` rejects an existing instance and `update` rejects a missing one.
+
+A managed comment is one state container. Decode, schema, rendering, identity,
+size, drift, duplicate-name, and revision checks run before publishing. An
+uncertain write response triggers readback and never automatically replays a
+patch. GitHub has no atomic compare-and-swap for comments: serialize publishers
+by target/name and refetch before a later update after a conflict.
+
+Visible Markdown is a projection. Manual edits produce drift and block normal
+updates; repair explicitly restores the stored projection. A state copied
+to a different target cannot be adopted for publishing. Embedded state is
+public to anyone who can read the comment, including template sources; keep
+credentials and private logs out of it.
+
+For automation, aggregate parallel jobs into one snapshot and publish through
+one writer. Use trusted templates and reducer code in privileged workflows.
+The [Actions examples](examples/actions) demonstrate current-resource refetch,
+serialization, and fork-safe reduction. gh-slate publishes ordinary comments;
+its local Markdown output can also feed a separate review workflow.
+
+Use `gh slate --help` and each subcommand's `--help` for the command reference.

gh_slate-0.1.0/README.md

@@ -0,0 +1,226 @@
+# gh-slate
+
+Manage named, data-backed dashboard comments on GitHub Issues and Pull Requests.
+
+<p align="center">
+   <a href="https://python.org/" target="_blank"><img alt="PyPI - Python Version" src="https://img.shields.io/pypi/pyversions/gh-slate?logo=python&style=flat-square"></a>
+   <a href="https://pypi.org/project/gh-slate/" target="_blank"><img src="https://img.shields.io/pypi/v/gh-slate?style=flat-square" alt="pypi"></a>
+   <a href="https://pypi.org/project/gh-slate/" target="_blank"><img alt="PyPI - Downloads" src="https://img.shields.io/pypi/dm/gh-slate?style=flat-square"></a>
+   <a href="LICENSE"><img alt="LICENSE" src="https://img.shields.io/github/license/ShigureLab/gh-slate?style=flat-square"></a>
+   <br/>
+   <a href="https://github.com/astral-sh/uv"><img alt="uv" src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/uv/main/assets/badge/v0.json&style=flat-square"></a>
+   <a href="https://github.com/astral-sh/ruff"><img alt="ruff" src="https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json&style=flat-square"></a>
+   <a href="https://gitmoji.dev"><img alt="Gitmoji" src="https://img.shields.io/badge/gitmoji-%20😜%20😍-FFDD67?style=flat-square"></a>
+</p>
+
+## Install
+
+Requirements:
+
+- Python 3.10 or newer;
+- `gh`, authenticated for the target host;
+- `uv` for the Python tool installation and, on supported Unix platforms, the
+  repository-backed GitHub CLI extension launcher.
+
+Until the first PyPI release, install the Python CLI from a checkout. This is
+also the supported development install on Windows:
+
+```bash
+git clone https://github.com/ShigureLab/gh-slate.git
+cd gh-slate
+uv tool install .
+gh-slate --help
+```
+
+After a release is published to PyPI, install the Python tool with:
+
+```bash
+uv tool install gh-slate
+gh-slate --help
+```
+
+The PyPI package and `gh-slate` Python CLI are runtime-tested on Linux, macOS,
+and Windows. On macOS/Linux or another Unix environment with Bash and `uv`, the
+repository can instead be installed as a GitHub CLI extension:
+
+```bash
+gh extension install ShigureLab/gh-slate
+gh slate --help
+```
+
+The current root extension launcher is a Bash script and is not a supported
+Windows entrypoint; use the Python CLI on Windows. On supported platforms both
+entrypoints expose the same parser. The public names are:
+
+```text
+PyPI distribution       gh-slate
+Python import package   gh_slate
+console script          gh-slate
+GitHub repository       gh-slate
+gh extension command    gh slate
+```
+
+### Install the agent skill separately
+
+The bundled skill teaches an agent the safe inspect/dry-run/mutate/verify
+workflow. Installing the CLI does not install the skill, and installing the
+skill does not install the CLI. With Node.js/npm available, install it through
+the cross-agent `skills` CLI:
+
+```bash
+npx skills add https://github.com/ShigureLab/gh-slate --skill gh-slate
+```
+
+GitHub CLI 2.96 or newer can install the same skill through its native,
+currently preview, skill command:
+
+```bash
+gh skill install ShigureLab/gh-slate gh-slate --agent codex --scope user
+```
+
+## Quick start
+
+Check authentication and local dependencies:
+
+```bash
+gh auth status
+gh slate doctor --json
+```
+
+Use the checked-in [CI, review, and benchmark profiles](examples/profiles).
+Preview a review locally, then against a real target before publishing:
+
+```bash
+gh slate render review --config examples/profiles/boards.toml --profile review --data examples/profiles/review-changes.json
+gh slate apply review --target https://github.com/OWNER/REPO/pull/42 --config examples/profiles/boards.toml --profile review --data examples/profiles/review-changes.json --dry-run --json
+gh slate apply review --target https://github.com/OWNER/REPO/pull/42 --config examples/profiles/boards.toml --profile review --data examples/profiles/review-changes.json --json
+```
+
+Replace the target URL before publishing. The examples contain synthetic data.
+Use `gh-slate` in place of `gh slate` with the Python CLI.
+
+Read the current data and revision, or switch to the approval layout by sending
+a new snapshot. Omitting the profile reuses the definition stored on GitHub:
+
+```bash
+gh slate view review --target https://github.com/OWNER/REPO/pull/42 --json
+gh slate apply review --target https://github.com/OWNER/REPO/pull/42 --data examples/profiles/review-approved.json --json
+gh slate list --target https://github.com/OWNER/REPO/pull/42 --json
+gh slate state export review --target https://github.com/OWNER/REPO/pull/42
+gh slate state verify review --target https://github.com/OWNER/REPO/pull/42 --json
+```
+
+The review profile maps `data.outcome` to `approved`, `changes_requested`, or
+`error`. Those names belong to the profile; the core only follows its JSON
+Pointer and exact view map. Missing or unknown outcomes fail before writing.
+Each view can have a different layout and schema branch.
+
+For a partial edit, use a standard RFC 6902 patch and the revision read from
+`view --json`. For example, while the review contains finding F17:
+
+```bash
+gh slate apply review --target https://github.com/OWNER/REPO/pull/42 --patch examples/profiles/resolve-finding.patch.json --if-revision 3 --dry-run --json
+```
+
+Replace `3` with the observed revision. The dry-run reports candidate data,
+Markdown, data changes, definition/meta changes, and view transitions. Remove
+`--dry-run` to publish. Patch and full data use the same writer; failure performs
+no write and a no-op preserves revision.
+
+## Definitions and templates
+
+Configuration is explicit: `--config FILE` overrides `GH_SLATE_CONFIG`.
+There is no default directory search or config merging. File paths are relative
+to the TOML file, and `--profile NAME` selects a definition:
+
+```toml
+
+[profiles.ci]
+schema = "ci.schema.json"
+template = "ci.md.j2"
+
+[profiles.review]
+schema = "review.schema.json"
+view_by = "/outcome"
+
+[profiles.review.views]
+approved = "approved.md.j2"
+changes_requested = "changes.md.j2"
+error = "error.md.j2"
+```
+
+Single-template definitions also work directly with `--template FILE` and
+optional `--schema FILE`. Profile and direct definition overrides are mutually
+exclusive. Pass `--profile` explicitly to reload a changed definition; normal
+data updates never read local config files.
+
+Templates receive business `data` and read-only `meta`:
+
+```jinja2
+## {{ meta.slate.name }}
+{% if meta.target is not none %}
+Target: {{ meta.repository.full_name | md_link(meta.target.url) }} #{{ meta.target.number }}
+{% endif %}
+
+{{ data.jobs | md_table(columns=["name", "status"]) }}
+{{ data.notes | md_list }}
+```
+
+Ordinary interpolated strings are escaped. Use `md_text`, `md_link`, `md_code`,
+`md_codeblock`, `md_table`, `md_list`, and `md_details` for composable Markdown.
+Sandbox limits bound template source, loops, output, and the complete comment.
+There is no include loader, filesystem access, or arbitrary Python call.
+
+`meta` contains host, repository identity, target kind/number/node ID/URL, and
+slate name. Apply obtains it from GitHub and stores the exact render snapshot.
+Local render sets host/repository/target to null unless given `--meta FILE`.
+Use `apply --dry-run` for a preview with real target metadata. An analyzed
+commit, run ID, or timestamp belongs in `data.source`; gh-slate never replaces
+it with a newer revision merely because the target changed.
+
+## Read and recover
+
+| Task                                             | Command                          |
+| ------------------------------------------------ | -------------------------------- |
+| Local or stored-state preview                    | `render`                         |
+| Publish a full snapshot or RFC 6902 patch        | `apply --data` / `apply --patch` |
+| Read current data, metadata, revision, and view  | `view --json`                    |
+| List managed comments                            | `list --json`                    |
+| Export the complete embedded definition and data | `state export`                   |
+| Verify integrity and reproduce rendering         | `state verify`                   |
+| Restore visible Markdown from state              | `repair --from-state`            |
+| Remove one managed comment                       | `delete --confirm NAME`          |
+| Check authentication and local dependencies      | `doctor`                         |
+
+```bash
+gh slate render review --target https://github.com/OWNER/REPO/pull/42
+gh slate view review --target https://github.com/OWNER/REPO/pull/42 --web
+gh slate repair review --target https://github.com/OWNER/REPO/pull/42 --from-state --if-revision 3 --json
+gh slate delete review --target https://github.com/OWNER/REPO/pull/42 --confirm review --json
+```
+
+## Publishing guarantees
+
+Names are scoped to target and controller; they match
+`[a-z0-9][a-z0-9._-]{0,63}` and cannot contain `--`. Default apply mode is `upsert`;
+`create` rejects an existing instance and `update` rejects a missing one.
+
+A managed comment is one state container. Decode, schema, rendering, identity,
+size, drift, duplicate-name, and revision checks run before publishing. An
+uncertain write response triggers readback and never automatically replays a
+patch. GitHub has no atomic compare-and-swap for comments: serialize publishers
+by target/name and refetch before a later update after a conflict.
+
+Visible Markdown is a projection. Manual edits produce drift and block normal
+updates; repair explicitly restores the stored projection. A state copied
+to a different target cannot be adopted for publishing. Embedded state is
+public to anyone who can read the comment, including template sources; keep
+credentials and private logs out of it.
+
+For automation, aggregate parallel jobs into one snapshot and publish through
+one writer. Use trusted templates and reducer code in privileged workflows.
+The [Actions examples](examples/actions) demonstrate current-resource refetch,
+serialization, and fork-safe reduction. gh-slate publishes ordinary comments;
+its local Markdown output can also feed a separate review workflow.
+
+Use `gh slate --help` and each subcommand's `--help` for the command reference.

gh_slate-0.1.0/pyproject.toml

@@ -0,0 +1,99 @@
+[project]
+name = "gh-slate"
+version = "0.1.0"
+description = "Manage named, data-backed dashboard comments on GitHub Issues and Pull Requests."
+readme = "README.md"
+requires-python = ">=3.10"
+dependencies = [
+    "jinja2>=3.1.6,<3.2",
+    "jsonpatch>=1.33,<2",
+    "jsonpointer>=3.1,<4",
+    "jsonschema>=4.25,<5",
+    "referencing>=0.36,<1",
+    "regex>=2025.7.34,<2027",
+    "tomli>=2.2,<3 ; python_full_version < '3.11'",
+]
+keywords = [
+    "github",
+    "cli",
+    "dashboard",
+    "issues",
+    "pull-requests",
+    "markdown",
+]
+license = "MIT"
+license-files = ["LICENSE"]
+classifiers = [
+    "Environment :: Console",
+    "Operating System :: OS Independent",
+    "Typing :: Typed",
+    "Programming Language :: Python",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Programming Language :: Python :: 3.14",
+    "Programming Language :: Python :: Implementation :: CPython",
+]
+
+[[project.authors]]
+name = "Nyakku Shigure"
+email = "sigure.qaq@gmail.com"
+
+[project.urls]
+Homepage = "https://github.com/ShigureLab/gh-slate"
+Documentation = "https://github.com/ShigureLab/gh-slate"
+Repository = "https://github.com/ShigureLab/gh-slate"
+Issues = "https://github.com/ShigureLab/gh-slate/issues"
+
+[project.scripts]
+gh-slate = "gh_slate.__main__:main"
+
+[dependency-groups]
+dev = [
+    "hypothesis>=6.167.1",
+    "pyyaml>=6.0.3,<7",
+    "ty>=0.0.78",
+    "ruff>=0.16.6",
+    "pytest>=9.1.1",
+    "pytest-rerunfailures>=16.6.1",
+    "tomli>=2.2,<3",
+]
+
+[tool.ruff]
+line-length = 120
+target-version = "py310"
+
+[tool.ruff.lint]
+select = [
+    "F",
+    "E",
+    "W",
+    "I",
+    "C4",
+    "T100",
+    "UP",
+    "PYI",
+    "B",
+    "PLE",
+    "SIM101",
+    "PTH",
+    "PGH004",
+    "TC",
+    "RSE",
+    "FURB",
+    "FA",
+    "RUF100",
+]
+ignore = ["E501"]
+future-annotations = true
+
+[tool.ruff.lint.isort]
+required-imports = ["from __future__ import annotations"]
+known-first-party = ["gh_slate"]
+combine-as-imports = true
+
+[build-system]
+requires = ["uv_build>=0.12.5,<0.13.0"]
+build-backend = "uv_build"