chore: refresh template README and trim nox variants

Clarify the template's role in the Copier stack, setup flow, and release guidance.
Disable the lowest resolution session to reduce unsupported dependency combinations in generated projects

Author: liblaf

README.md

@@ -1,133 +1,114 @@
-<div align="center"><a name="readme-top"></a>
+<div align="center" markdown>
 
-![copier-python](https://socialify.git.ci/liblaf/copier-python/image?custom_language=Python&description=1&forks=1&issues=1&language=1&logo=https%3A%2F%2Fraw.githubusercontent.com%2Fcopier-org%2Fcopier%2Frefs%2Fheads%2Fmaster%2Fimg%2Flogo.svg&name=1&owner=1&pattern=Transparent&pulls=1&stargazers=1&theme=Auto)
+![Copier Python](https://socialify.git.ci/liblaf/copier-python/image?custom_language=Python&description=1&forks=1&issues=1&language=1&logo=https%3A%2F%2Fraw.githubusercontent.com%2Fcopier-org%2Fcopier%2Frefs%2Fheads%2Fmaster%2Fimg%2Flogo.svg&name=1&owner=1&pattern=Transparent&pulls=1&stargazers=1&theme=Auto)
+
+**[Browse the template files »](https://github.com/liblaf/copier-python/tree/main/template)**
 
 [![Made with Copier](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/copier-org/copier/master/img/badge/badge-black.json)](https://github.com/copier-org/copier)
+[![MegaLinter](https://github.com/liblaf/copier-python/actions/workflows/mega-linter.yaml/badge.svg)](https://github.com/liblaf/copier-python/actions/workflows/mega-linter.yaml)
+[![Release PR](https://github.com/liblaf/copier-python/actions/workflows/release-pr.yaml/badge.svg)](https://github.com/liblaf/copier-python/actions/workflows/release-pr.yaml)
+[![Copier Update](https://github.com/liblaf/copier-python/actions/workflows/copier-update.yaml/badge.svg)](https://github.com/liblaf/copier-python/actions/workflows/copier-update.yaml)
 
-[Changelog](https://github.com/liblaf/copier-python/blob/main/CHANGELOG.md) · [Report Bug](https://github.com/liblaf/copier-python/issues) · [Request Feature](https://github.com/liblaf/copier-python/issues)
+[Changelog](https://github.com/liblaf/copier-python/blob/main/CHANGELOG.md) · [Template Files](https://github.com/liblaf/copier-python/tree/main/template) · [Report Bug](https://github.com/liblaf/copier-python/issues) · [Request Feature](https://github.com/liblaf/copier-python/issues)
 
-![Rule](https://raw.githubusercontent.com/andreasbm/readme/master/assets/lines/rainbow.png)
+![Rule](https://cdn.jsdelivr.net/gh/andreasbm/readme/assets/lines/rainbow.png)
 
 </div>
 
-## ✨ Features
-
-- 🐍 Bootstraps a modern Python project on a typed `src/` layout.
-- 🧱 Designed to layer on top of [`gh:liblaf/copier-shared`](https://github.com/liblaf/copier-shared) and [`gh:liblaf/copier-release`](https://github.com/liblaf/copier-release).
-- ⚡ Uses `uv` for dependency management and `mise` for repeatable local tasks.
-- ✅ Ships with `nox`, `pytest`, coverage, Ruff, import-linter, and shared repository defaults.
-- 📚 Generates docs with Zensical, MkDocs Material, mkdocstrings, GitHub Pages, and Read the Docs.
-- 🚀 Builds with Hatchling plus Hatch VCS and publishes to PyPI and GitHub Releases.
-- 🧪 Includes benchmark workflow wiring with CodSpeed.
+## 🐍 What Is `copier-python`?
 
-## 🧱 Template Stack
+`copier-python` is the Python layer in the `liblaf` Copier stack. It adds packaging, typed source layout, documentation, testing, benchmarking, and PyPI publishing on top of the shared repository and release foundations.
 
-This template is the Python layer of a three-template setup:
+> [!IMPORTANT]
+> This template depends on [`gh:liblaf/copier-shared`](https://github.com/liblaf/copier-shared) and [`gh:liblaf/copier-release`](https://github.com/liblaf/copier-release). Apply the stack in that order: shared → release → python.
 
-1. [`gh:liblaf/copier-shared`](https://github.com/liblaf/copier-shared)
-2. [`gh:liblaf/copier-release`](https://github.com/liblaf/copier-release)
-3. `gh:liblaf/copier-python`
+If you want the real source of truth for generated files, start in [`template/`](https://github.com/liblaf/copier-python/tree/main/template). This repository README documents the template itself; the generated project README comes from [`template/README.md.jinja`](https://github.com/liblaf/copier-python/blob/main/template/README.md.jinja).
 
-Apply them in that order. `copier-python` expects the shared project metadata and release automation from the first two templates to already exist.
+## ✨ What You Get
 
-## 🚀 Create a Project
+- 📦 A modern Python package layout under `src/`, including `py.typed`, version stubs, and lazy-loader-friendly package exports.
+- ⚙️ A `pyproject.toml` wired for PEP 621 metadata, `uv` dependency groups, Hatchling builds, and Hatch VCS versioning.
+- 🧪 A `noxfile.py` with multi-version test sessions, dependency resolution variants, and optional benchmark sessions.
+- 📚 Docs scaffolding with Zensical, MkDocs Material, mkdocstrings, GitHub-friendly Markdown, and Read the Docs configuration.
+- 🚀 Release automation that fits the rest of the `liblaf` Copier stack, including changelog generation, draft releases, and PyPI publishing through OIDC.
+- 🔁 Copier-friendly update paths so the generated repository can be refreshed later without redoing the whole setup by hand.
 
-```bash
-copier copy gh:liblaf/copier-shared .
-copier copy gh:liblaf/copier-release .
-copier copy gh:liblaf/copier-python .
-```
+## 🚀 Apply The Template
 
-To refresh the Python layer later:
+After applying the shared and release templates, add the Python layer with:
 
 ```bash
-copier recopy --answers-file '.config/copier/.copier-answers.python.yaml'
+copier copy --trust gh:liblaf/copier-python .
 ```
 
-The generated repository will also keep the answers files from the shared and release templates, so automated Copier update workflows can refresh the full stack.
-
-## 🧰 What You Get
+## 🔄 Update The Template
 
-- `pyproject.toml` with PEP 621 metadata, dependency groups, Hatchling packaging, and Hatch VCS versioning.
-- `noxfile.py` with reusable test sessions across declared Python versions plus tagged dependency-resolution variants.
-- `.config/mise/conf.d/50-python.toml` with ready-to-run tasks such as `install`, `lint`, `docs:build`, `docs:serve`, `gen:init`, and `upgrade`.
-- `zensical.toml`, `.readthedocs.yaml`, and Python-specific GitHub Actions workflows for docs, tests, benchmarks, and publishing.
-- A typed package skeleton under `src/` with `py.typed`, version stubs, and lazy-loader friendly `__init__.py` generation from `__init__.pyi`.
-
-## ⌨️ Local Development
-
-After generating a project from this template, the usual workflow is:
+To refresh the Python layer in an existing repository:
 
 ```bash
-mise run install
-mise run lint
-nox
-mise run docs:serve
+copier recopy --trust --answers-file '.config/copier/.copier-answers.python.yaml'
 ```
 
-Useful extra commands:
+The generated repository usually keeps separate Copier answers files for each layer, so scheduled update workflows can refresh the whole stack over time.
 
-- `mise run docs:build` to build the docs site locally.
-- `mise run gen:init` to regenerate `__init__.py` files from `__init__.pyi` stubs.
-- `mise run upgrade` to refresh dependencies from lockfiles.
-- `nox --tags bench` to run benchmark sessions when the project contains benchmarks.
+## 🧱 Template Stack
 
-## 🔄 Release Workflow
+- 🧰 [`gh:liblaf/copier-shared`](https://github.com/liblaf/copier-shared): repository hygiene, common automation, editor settings, and shared project metadata.
+- 🏷️ [`gh:liblaf/copier-release`](https://github.com/liblaf/copier-release): release PRs, changelog generation, Git tags, GitHub Releases, and publish orchestration.
+- 🐍 [`gh:liblaf/copier-python`](https://github.com/liblaf/copier-python): Python packaging, docs, tests, benchmarks, and PyPI workflow wiring.
 
-For repositories bootstrapped with `copier-release`, the default release flow is:
+## 🚢 Release Workflow
 
-1. Conventional Commits on `main` trigger `release-pr.yaml`, which opens a release PR with an updated changelog.
-2. Review and approve the release PR, or wait for the scheduled auto-review. [`mergery[bot]`](https://github.com/apps/mergery) merges the PR.
-3. After the release PR is merged, `release-draft.yaml` creates a draft release.
-4. `python-release.yaml` builds the package, publishes it to PyPI with OIDC, and uploads the release assets to the draft release.
-5. `release-publish.yaml` publishes the draft release after 6 hours, which gives the release jobs time to finish.
+In a generated project, the default release flow looks like this:
+
+1. Push commits using Conventional Commits.
+2. `release-pr.yaml` creates a release PR with the changelog and updated version.
+3. Merge the release PR yourself, or approve it and let [`mergery[bot]`](https://github.com/apps/mergery) merge it once the button is green.
+4. `release-draft.yaml` creates a draft release.
+5. `python-release.yaml` builds the package, publishes it to PyPI with GitHub OIDC, and uploads release assets to the draft release.
+6. `release-publish.yaml` publishes the draft release after 6 hours so the release jobs have enough time to finish.
 
 ## 🛠️ Post Setup
 
-### Read the Docs
+### 📚 Read the Docs
 
 1. Visit <https://app.readthedocs.org/dashboard/import/>.
-2. Follow the prompts to import the repository.
-3. In project settings, configure:
+2. Follow the prompts to import the generated repository.
+3. Configure these settings:
 
-| Location                             | Value                                         |
-| ------------------------------------ | --------------------------------------------- |
-| `Setup > Settings > Default version` | `stable`                                      |
-| `Setup > Settings`                   | Enable `Build pull requests for this project` |
-| `Setup > Addons > Analytics`         | Enable                                        |
-| `Setup > Addons > Link previews`     | Enable                                        |
-| `Building > Pull request builds`     | Enable `Build pull requests for this project` |
-| `Building > Pull request builds`     | Enable `Show build overview in a comment`     |
+| Location | Value |
+| --- | --- |
+| `Setup > Settings > Default version` | `stable` |
+| `Setup > Settings` | Enable `Build pull requests for this project` |
+| `Setup > Addons > Analytics` | Enable |
+| `Setup > Addons > Link previews` | Enable |
+| `Building > Pull request builds` | Enable `Build pull requests for this project` |
+| `Building > Pull request builds` | Enable `Show build overview in a comment` |
 
-4. Add an automation rule with:
+4. Add this automation rule:
 
-| Field          | Value                 |
-| -------------- | --------------------- |
-| `Description`  | `Semantic Versioning` |
-| `Match`        | `SemVer versions`     |
-| `Version type` | `Tag`                 |
-| `Action`       | `Activate version`    |
+| Field | Value |
+| --- | --- |
+| `Description` | `Semantic Versioning` |
+| `Match` | `SemVer versions` |
+| `Version type` | `Tag` |
+| `Action` | `Activate version` |
 
-### PyPI Publish
+### 📦 PyPI Trusted Publishing
 
 1. Visit <https://pypi.org/manage/account/publishing/>.
-2. Add a trusted publisher for the generated repository.
-3. Use the GitHub Actions workflow and environment from the generated release setup:
-
-| Field              | Value              |
-| ------------------ | ------------------ |
-| `Workflow name`    | `Python / Release` |
-| `Environment name` | `PyPI`             |
+2. Create a trusted publisher for the generated repository.
+3. Point it at the GitHub Actions release workflow created by this template stack.
 
-The remaining form fields should match the GitHub owner, repository, and PyPI project name generated for your package.
+This template publishes with GitHub OIDC, so you do not need a long-lived PyPI API token.
 
 ## 🤝 Contributing
 
-Contributions are welcome. If you want to improve the template, update the files under [`template/`](https://github.com/liblaf/copier-python/tree/main/template) and any shared helper files used during generation, then keep commit messages in Conventional Commits format so the release automation can do its job.
+To improve the template, edit the files under [`template/`](https://github.com/liblaf/copier-python/tree/main/template) and the small helper files around it, then keep commit messages in Conventional Commits format so the release automation can do its job cleanly.
 
 [![PR Welcome](https://img.shields.io/badge/%F0%9F%A4%AF%20PR%20WELCOME-%E2%86%92-ffcb47?labelColor=black&style=for-the-badge)](https://github.com/liblaf/copier-python/pulls)
 
-[![Contributors](https://contrib.nn.ci/api?repo=liblaf/copier-python)](https://github.com/liblaf/copier-python/graphs/contributors)
+[![Contributors](https://gh-contributors-gamma.vercel.app/api?repo=liblaf/copier-python)](https://github.com/liblaf/copier-python/graphs/contributors)
 
 ## 🔗 More Copier Templates
 

template/noxfile.py

@@ -22,7 +22,7 @@ def bench(s: nox.Session) -> None:
     "resolution",
     [
         nox.param(Resolution.HIGHEST, id="highest", tags=["highest"]),
-        nox.param(Resolution.LOWEST, id="lowest", tags=["lowest"]),
+        # nox.param(Resolution.LOWEST, id="lowest", tags=["lowest"]),
         nox.param(Resolution.LOWEST_DIRECT, id="lowest-direct", tags=["lowest-direct"]),
     ],
 )