chore: move to rumdl instead of prettier

Signed-off-by: Henry Schreiner <henryfs@princeton.edu>

Author: henryiii

.pre-commit-config.yaml

@@ -32,7 +32,7 @@ repos:
     rev: "v0.15.14"
     hooks:
       - id: ruff-check
-        args: ["--fix", "--show-fixes"]
+        args: ["--fix"]
       - id: ruff-format
 
   - repo: https://github.com/pre-commit/pygrep-hooks
@@ -63,8 +63,13 @@ repos:
     rev: "v3.8.3"
     hooks:
       - id: prettier
-        types_or: [yaml, markdown, html, css, scss, javascript, json]
-        args: [--prose-wrap=always]
+        types_or: [yaml, html, css, scss, javascript, json]
+
+  - repo: https://github.com/rvben/rumdl-pre-commit
+    rev: v0.2.0
+    hooks:
+      - id: rumdl
+        args: [--no-exclude] # Disable all exclude patterns
 
   - repo: https://github.com/crate-ci/typos
     rev: "v1.46.3"

AGENTS.md

@@ -1,6 +1,8 @@
 # Agent Guide for scientific-python/cookie
 
-This repo has three distinct concerns: a **cookiecutter/copier template** for new Python projects (`{{cookiecutter.project_name}}/`), a **repo-review plugin** (`src/sp_repo_review/`), and a **Jekyll-based developer guide** (`docs/`).
+This repo has three distinct concerns: a **cookiecutter/copier template** for
+new Python projects (`{{cookiecutter.project_name}}/`), a **repo-review plugin**
+(`src/sp_repo_review/`), and a **Jekyll-based developer guide** (`docs/`).
 
 ## Key commands
 
@@ -17,46 +19,69 @@ Important: tests run with `PYTHONWARNDEFAULTENCODING=1`.
 
 ### Cookie template validation
 
-The noxfile generates temporary projects for **all 9 backends** × **vcs on/off** × **3 docs engines** (sphinx/mkdocs/zensical). These are slow.
+The noxfile generates temporary projects for **all 9 backends** × **vcs on/off**
+× **3 docs engines** (sphinx/mkdocs/zensical). These are slow.
 
 - `nox -s "tests(hatch)"` — run generated project tests for a single backend
 - `nox -s "lint(hatch)"` — run pre-commit (`prek`) on generated project
 - `nox -s "dist(hatch)"` — verify build output includes LICENSE
 - `nox -s "native(hatch)"` — test hatch/pdm/poetry native test runners
-- `nox -s compare_copier` — verify cookiecutter and copier produce identical files
+- `nox -s compare_copier` — verify cookiecutter and copier produce identical
+  files
 - `nox -s compare_cruft` — verify cookiecutter and cruft produce identical files
 - `nox -s gha_bump` — bump GitHub Actions versions across docs and templates
 - `nox -s pc_bump` — bump pre-commit hook versions across docs and templates
 
 ## Architecture notes
 
-- **Template directory**: `{{cookiecutter.project_name}}/` contains the cookiecuttter template. Copier reads `copier.yml`; cookiecutter reads `cookiecutter.json`. Keep them in sync; `compare_copier` checks this.
-- **Entry points**: `sp_repo_review` registers `repo-review` checks/families/fixtures via `[project.entry-points]` in `pyproject.toml`.
-- **Generated docs**: The README check list (line ~300+) is a cog block. Do not edit it by hand; run `nox -s readme` or cog will fail in CI.
-- **Cookie template `.pre-commit-config.yaml`** uses `prek` (a Rust-based pre-commit alternative), not `pre-commit`.
-- **Ruff hook ID**: `.pre-commit-config.yaml` uses `ruff-check` as the hook id (not `ruff`), for pre-commit 4.x compatibility.
+- **Template directory**: `{{cookiecutter.project_name}}/` contains the
+  cookiecuttter template. Copier reads `copier.yml`; cookiecutter reads
+  `cookiecutter.json`. Keep them in sync; `compare_copier` checks this.
+- **Entry points**: `sp_repo_review` registers `repo-review`
+  checks/families/fixtures via `[project.entry-points]` in `pyproject.toml`.
+- **Generated docs**: The README check list (line ~300+) is a cog block. Do not
+  edit it by hand; run `nox -s readme` or cog will fail in CI.
+- **Cookie template `.pre-commit-config.yaml`** uses `prek` (a Rust-based
+  pre-commit alternative), not `pre-commit`.
+- **Ruff hook ID**: `.pre-commit-config.yaml` uses `ruff-check` as the hook id
+  (not `ruff`), for pre-commit 4.x compatibility.
 
 ## Style and conventions
 
-- `tool.pytest.ini_options.norecursedirs` excludes `{{cookiecutter.project_name}}` so pytest does not descend into the template directory.
-- `tool.ruff.extend-exclude` also excludes `\{\{cookiecutter.project_name\}\}` (double-escaped in TOML).
-- `tool.mypy.python_version = "3.10"`; the `sp_repo_review.*` override enforces `disallow_untyped_defs=True`.
-- `tool.pylint.master.ignore-paths` ignores `src/sp_repo_review/_version.py` (auto-generated by hatch-vcs).
-- Ruff selects `ALL` with many ignores; notable: `S101` (assert) and `D` (docstrings) are globally disabled.
+- `tool.pytest.ini_options.norecursedirs` excludes
+  `{{cookiecutter.project_name}}` so pytest does not descend into the template
+  directory.
+- `tool.ruff.extend-exclude` also excludes `\{\{cookiecutter.project_name\}\}`
+  (double-escaped in TOML).
+- `tool.mypy.python_version = "3.10"`; the `sp_repo_review.*` override enforces
+  `disallow_untyped_defs=True`.
+- `tool.pylint.master.ignore-paths` ignores `src/sp_repo_review/_version.py`
+  (auto-generated by hatch-vcs).
+- Ruff selects `ALL` with many ignores; notable: `S101` (assert) and `D`
+  (docstrings) are globally disabled.
 
 ## CI quirks
 
-- CI uses change detection to decide whether to run cookie tests or rr-tests. Both are required to pass for the `pass` job.
+- CI uses change detection to decide whether to run cookie tests or rr-tests.
+  Both are required to pass for the `pass` job.
 - rr-tests matrix runs on Python 3.10, 3.12, 3.14 across ubuntu/macos/windows.
 - Cookie tests reuse the same `reusable-cookie.yml` workflow.
 
 ## Docs site (MyST)
 
-- Migrated from Jekyll to [MyST](https://mystmd.org) (JupyterBook 2.0) using the `scientific-python-myst-theme`.
-- Node/Bun-based; from `docs/`, run `bun install` then `bun run build` to build the site.
-- Config: `docs/myst.yml` (TOC, project settings), `docs/config/scientific-python.yml` (theme options).
-- Custom plugin: `docs/rr-role.mjs` — provides `{rr}` inline role for repo-review badge spans.
+- Migrated from Jekyll to [MyST](https://mystmd.org) (JupyterBook 2.0) using the
+  `scientific-python-myst-theme`.
+- Node/Bun-based; from `docs/`, run `bun install` then `bun run build` to build
+  the site.
+- Config: `docs/myst.yml` (TOC, project settings),
+  `docs/config/scientific-python.yml` (theme options).
+- Custom plugin: `docs/rr-role.mjs` — provides `{rr}` inline role for
+  repo-review badge spans.
 - Custom CSS: `docs/assets/css/site.css` — only `.rr-btn` badge styling remains.
-- Docs pages in `docs/pages/` contain cog blocks that auto-generate config examples from the template.
-- The repo-review interactive page uses an `{iframe}` pointing to the WASM app at `https://scientific-python.github.io/repo-review/`.
-- Tab-sets use `:sync: <tab-name>` for cross-page tab synchronization, where the sync key is the tab label itself (e.g., `sphinx`, `mkdocs`, `trusted-publishing`, `scikit-build-core`).
+- Docs pages in `docs/pages/` contain cog blocks that auto-generate config
+  examples from the template.
+- The repo-review interactive page uses an `{iframe}` pointing to the WASM app
+  at `https://scientific-python.github.io/repo-review/`.
+- Tab-sets use `:sync: <tab-name>` for cross-page tab synchronization, where the
+  sync key is the tab label itself (e.g., `sphinx`, `mkdocs`,
+  `trusted-publishing`, `scikit-build-core`).

README.md

@@ -42,38 +42,38 @@ hand, from `{{cookiecutter.project_name}}/`).
 
 During generation you can select from the following backends for your package:
 
-1.  [hatch][]: This uses hatchling, a modern builder with nice file inclusion,
-    extendable via plugins, and good error messages. **(Recommended for pure
-    Python projects)**
-2.  [uv][]: The `uv_build` backend is written in Rust and is integrated into'
-    `uv`, meaning it can build without downloading anything extra and can even
-    avoid running Python at all when building, making it the fastest backend for
-    simple packages. No dynamic metadata support.
-3.  [flit][]: A modern, lightweight [PEP 621][] build system for pure Python
-    projects. Replaces setuptools, no MANIFEST.in, setup.py, or setup.cfg. Low
-    learning curve. Easy to bootstrap into new distributions. Difficult to get
-    the right files included, little dynamic metadata support.
-4.  [pdm][]: A modern, less opinionated all-in-one solution to pure Python
-    projects supporting standards. Replaces setuptools, venv/pipenv, pip, wheel,
-    and twine. Supports [PEP 621][].
-5.  [poetry][]: An all-in-one solution to pure Python projects. Replaces
-    setuptools, venv/pipenv, pip, wheel, and twine. Higher learning curve, but
-    is all-in-one. Makes some bad default assumptions for libraries.
-6.  [setuptools][]: The classic build system, but with the new standardized
-    configuration.
-7.  [pybind11][]: This is setuptools but with an C++ extension written in
-    [pybind11][] and wheels generated by [cibuildwheel][].
-8.  [scikit-build][]: A scikit-build (CMake) project also using pybind11, using
-    scikit-build-core. **(Recommended for C++ projects)**
-9.  [meson-python][]: A Meson project also using pybind11. (No VCS versioning)
+1. [hatch][]: This uses hatchling, a modern builder with nice file inclusion,
+   extendable via plugins, and good error messages. **(Recommended for pure
+   Python projects)**
+2. [uv][]: The `uv_build` backend is written in Rust and is integrated into'
+   `uv`, meaning it can build without downloading anything extra and can even
+   avoid running Python at all when building, making it the fastest backend for
+   simple packages. No dynamic metadata support.
+3. [flit][]: A modern, lightweight [PEP 621][] build system for pure Python
+   projects. Replaces setuptools, no MANIFEST.in, setup.py, or setup.cfg. Low
+   learning curve. Easy to bootstrap into new distributions. Difficult to get
+   the right files included, little dynamic metadata support.
+4. [pdm][]: A modern, less opinionated all-in-one solution to pure Python
+   projects supporting standards. Replaces setuptools, venv/pipenv, pip, wheel,
+   and twine. Supports [PEP 621][].
+5. [poetry][]: An all-in-one solution to pure Python projects. Replaces
+   setuptools, venv/pipenv, pip, wheel, and twine. Higher learning curve, but
+   is all-in-one. Makes some bad default assumptions for libraries.
+6. [setuptools][]: The classic build system, but with the new standardized
+   configuration.
+7. [pybind11][]: This is setuptools but with an C++ extension written in
+   [pybind11][] and wheels generated by [cibuildwheel][].
+8. [scikit-build][]: A scikit-build (CMake) project also using pybind11, using
+   scikit-build-core. **(Recommended for C++ projects)**
+9. [meson-python][]: A Meson project also using pybind11. (No VCS versioning)
 10. [maturin][]: A [PEP 621][] builder for Rust binary extensions. (No VCS
     versioning) **(Recommended for Rust projects)**
 
 Currently, the best choice is probably hatch for pure Python projects, and
 scikit-build (such as the scikit-build-core + pybind11 choice) for binary
 projects.
 
-#### To use (copier version)
+### To use (copier version)
 
 Install `copier` and `copier-templates-extensions`. Using [uv][], that's:
 
@@ -132,7 +132,7 @@ There are a few example dependencies and a minimum Python version of 3.10, feel
 free to change it to whatever you actually need/want. There is also a basic
 backports structure with a small typing example.
 
-#### Contained components:
+#### Contained components
 
 - GitHub Actions runs testing for the generation itself
   - Uses nox so cookie development can be checked locally
@@ -160,7 +160,7 @@ backports structure with a small typing example.
 - A README
 - Code coverage reporting with automatic uploads to Codecov after tests run
 
-#### For developers:
+#### For developers
 
 You can test locally with [nox][]:
 
@@ -196,8 +196,6 @@ A lot of the guide, cookiecutter, and repo-review started out as part of
 [Scikit-HEP][]. These projects were merged, generalized, and combined with the
 [NSLS-II][] guide during the 2023 Scientific-Python Developers Summit.
 
-<!-- prettier-ignore-start -->
-
 [actions-badge]: https://github.com/scientific-python/cookie/actions/workflows/ci.yml/badge.svg
 [actions-link]: https://github.com/scientific-python/cookie/actions
 [cibuildwheel]: https://cibuildwheel.readthedocs.io
@@ -227,8 +225,6 @@ A lot of the guide, cookiecutter, and repo-review started out as part of
 [setuptools]: https://setuptools.readthedocs.io
 [uv]: https://docs.astral.sh/uv
 
-<!-- prettier-ignore-end -->
-
 ---
 
 ## sp-repo-review
@@ -302,7 +298,7 @@ CLI requirements are included.
 
 ## List of checks
 
-<!-- prettier-ignore-start -->
+<!-- rumdl-disable MD013 -->
 
 <!-- [[[cog
 import itertools
@@ -440,4 +436,4 @@ Will not show up if no `setup.cfg` file is present.
 [conda-badge]: https://img.shields.io/conda/vn/conda-forge/sp-repo-review
 [conda-link]: https://github.com/conda-forge/sp-repo-review-feedstock
 
-<!-- prettier-ignore-end -->
+<!-- rumdl-enable MD013 -->

action.yml

@@ -26,7 +26,6 @@ runs:
         python-version: "3.13"
         update-environment: false
 
-    # prettier-ignore
     - name: Run repo-review
       shell: bash
       run: >

docs/_partials/pyproject.md

@@ -1,4 +1,4 @@
-## pyproject.toml: project table
+# pyproject.toml: project table
 
 <!-- [[[cog
 from cog_helpers import code_fence, render_cookie, TOMLMatcher
@@ -13,7 +13,7 @@ The metadata is specified in a [standards-based][metadata] format:
 with code_fence("toml"):
     print(pyproject.get_source("project"))
 ]]] -->
-<!-- prettier-ignore-start -->
+<!-- rumdl-disable MD013 -->
 ```toml
 [project]
 name = "package"
@@ -50,7 +50,7 @@ Homepage = "https://github.com/org/package"
 Discussions = "https://github.com/org/package/discussions"
 Changelog = "https://github.com/org/package/releases"
 ```
-<!-- prettier-ignore-end -->
+<!-- rumdl-enable MD013 -->
 <!-- [[[end]]] -->
 
 In this example, `"package"` is the name of the thing you are working on. You
@@ -64,7 +64,7 @@ special, and replaces the old url setting.
 If you use the above configuration, you need `README.md` and `LICENSE` files,
 since they are explicitly specified.
 
-### License
+## License
 
 The license can be done one of two ways.
 
@@ -145,7 +145,7 @@ example:
 with code_fence("toml"):
     print(pyproject.get_source("dependency-groups"))
 ]]] -->
-<!-- prettier-ignore-start -->
+<!-- rumdl-disable MD013 -->
 ```toml
 [dependency-groups]
 test = [
@@ -163,7 +163,7 @@ docs = [
   "furo>=2023.08.17",
 ]
 ```
-<!-- prettier-ignore-end -->
+<!-- rumdl-enable MD013 -->
 <!-- [[[end]]] -->
 
 You can include one dependency group in another. Most tools allow you to install