repomatic 8.0.0__tar.gz → 8.1.0__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (706) hide show
  1. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/.claude-plugin/plugin.json +1 -1
  2. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/agents/grunt-qa.md +6 -6
  3. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/agents/qa-engineer.md +8 -8
  4. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/agents/sphinx-docs.md +10 -10
  5. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.claude}/skills/awesome-triage/SKILL.md +11 -3
  6. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.claude}/skills/babysit-ci/SKILL.md +31 -14
  7. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.claude}/skills/babysit-ci/references/failure-patterns.md +3 -1
  8. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.claude}/skills/benchmark-update/SKILL.md +2 -2
  9. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.claude}/skills/repomatic-changelog/SKILL.md +4 -3
  10. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.claude}/skills/repomatic-deps/SKILL.md +9 -8
  11. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/repomatic-init/SKILL.md +2 -2
  12. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/repomatic-ship/SKILL.md +17 -13
  13. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/repomatic-test-matrix/SKILL.md +15 -0
  14. repomatic-8.1.0/.claude/skills/repomatic-upgrade/SKILL.md +228 -0
  15. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.claude}/skills/sphinx-docs-sync/SKILL.md +3 -3
  16. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.claude}/skills/translation-sync/SKILL.md +2 -2
  17. {repomatic-8.0.0 → repomatic-8.1.0}/.claude-plugin/marketplace.json +2 -2
  18. {repomatic-8.0.0 → repomatic-8.1.0}/.github/actions/publish-pypi/action.yaml +2 -2
  19. {repomatic-8.0.0 → repomatic-8.1.0}/.github/workflows/_release-build.yaml +12 -12
  20. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/_release-engine.yaml +42 -40
  21. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/autofix.yaml +75 -75
  22. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/autolock.yaml +3 -3
  23. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/cancel-runs.yaml +3 -3
  24. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/changelog.yaml +20 -20
  25. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/debug.yaml +6 -6
  26. {repomatic-8.0.0 → repomatic-8.1.0}/.github/workflows/docs.yaml +28 -20
  27. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/labels.yaml +11 -11
  28. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/lint.yaml +28 -28
  29. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/metrics.yaml +4 -4
  30. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/release.yaml +3 -3
  31. {repomatic-8.0.0 → repomatic-8.1.0}/.github/workflows/self-maintenance.yaml +5 -5
  32. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/tests.yaml +44 -16
  33. {repomatic-8.0.0/repomatic/data → repomatic-8.1.0/.github/workflows}/unsubscribe.yaml +3 -3
  34. repomatic-8.0.0/claude.md → repomatic-8.1.0/AGENTS.md +2 -2
  35. {repomatic-8.0.0 → repomatic-8.1.0}/PKG-INFO +2 -2
  36. {repomatic-8.0.0 → repomatic-8.1.0}/changelog.md +42 -0
  37. {repomatic-8.0.0 → repomatic-8.1.0}/docs/agent-skills.md +15 -12
  38. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/binaries.csv +6 -0
  39. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/config-snippet-screen.svg +2 -2
  40. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/dependencies.mmd +2 -5
  41. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/help-dark-screen.svg +7 -7
  42. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/help-light-screen.svg +7 -7
  43. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/matrix-grid-screen.svg +3 -3
  44. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/virustotal-scans.csv +6 -0
  45. {repomatic-8.0.0 → repomatic-8.1.0}/docs/benchmark.md +1 -1
  46. {repomatic-8.0.0 → repomatic-8.1.0}/docs/binaries.md +1 -1
  47. {repomatic-8.0.0 → repomatic-8.1.0}/docs/claude-code-plugin.md +4 -4
  48. {repomatic-8.0.0 → repomatic-8.1.0}/docs/conf.py +33 -5
  49. {repomatic-8.0.0 → repomatic-8.1.0}/docs/configuration.md +6 -2
  50. {repomatic-8.0.0 → repomatic-8.1.0}/docs/contributing.md +2 -2
  51. {repomatic-8.0.0 → repomatic-8.1.0}/docs/dependencies.md +17 -12
  52. {repomatic-8.0.0 → repomatic-8.1.0}/docs/docs_update.py +27 -5
  53. {repomatic-8.0.0 → repomatic-8.1.0}/docs/history.md +1 -1
  54. {repomatic-8.0.0 → repomatic-8.1.0}/docs/install.md +9 -8
  55. {repomatic-8.0.0 → repomatic-8.1.0}/docs/nuitka.md +6 -5
  56. {repomatic-8.0.0 → repomatic-8.1.0}/docs/operation-contracts.md +3 -3
  57. {repomatic-8.0.0 → repomatic-8.1.0}/docs/subagents.md +2 -2
  58. {repomatic-8.0.0 → repomatic-8.1.0}/docs/test-matrix.md +22 -2
  59. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tool-runner.md +5 -5
  60. {repomatic-8.0.0 → repomatic-8.1.0}/docs/upstream.md +7 -2
  61. {repomatic-8.0.0 → repomatic-8.1.0}/docs/workflows.md +22 -13
  62. {repomatic-8.0.0 → repomatic-8.1.0}/pyproject.toml +24 -9
  63. {repomatic-8.0.0 → repomatic-8.1.0}/pyproject.toml.orig +39 -13
  64. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/__init__.py +2 -2
  65. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cache.py +21 -7
  66. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/ci.py +1 -1
  67. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/deps.py +16 -7
  68. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/components.py +56 -14
  69. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/config.py +42 -6
  70. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/_release-engine.yaml +42 -40
  71. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/action-publish-pypi.yaml +2 -2
  72. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/agent-grunt-qa.md +6 -6
  73. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/agent-qa-engineer.md +8 -8
  74. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/agent-sphinx-docs.md +10 -10
  75. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/autofix.yaml +75 -75
  76. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/autolock.yaml +3 -3
  77. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/.github/contributing.md +8 -0
  78. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/.github/contributing.zh.md +8 -0
  79. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/.github/pull_request_template.md +1 -1
  80. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/cancel-runs.yaml +3 -3
  81. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/changelog.yaml +20 -20
  82. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/debug.yaml +6 -6
  83. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/docs.yaml +28 -20
  84. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/labels.yaml +11 -11
  85. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/lint.yaml +28 -28
  86. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/metrics.yaml +4 -4
  87. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/release.yaml +3 -3
  88. {repomatic-8.0.0/.claude → repomatic-8.1.0/repomatic/data}/skills/awesome-triage/SKILL.md +11 -3
  89. {repomatic-8.0.0/.claude → repomatic-8.1.0/repomatic/data}/skills/babysit-ci/SKILL.md +31 -14
  90. {repomatic-8.0.0/.claude → repomatic-8.1.0/repomatic/data}/skills/babysit-ci/references/failure-patterns.md +3 -1
  91. {repomatic-8.0.0/.claude → repomatic-8.1.0/repomatic/data}/skills/benchmark-update/SKILL.md +2 -2
  92. {repomatic-8.0.0/.claude → repomatic-8.1.0/repomatic/data}/skills/repomatic-changelog/SKILL.md +4 -3
  93. {repomatic-8.0.0/.claude → repomatic-8.1.0/repomatic/data}/skills/repomatic-deps/SKILL.md +9 -8
  94. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/repomatic-init/SKILL.md +2 -2
  95. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/repomatic-ship/SKILL.md +17 -13
  96. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/repomatic-test-matrix/SKILL.md +15 -0
  97. repomatic-8.1.0/repomatic/data/skills/repomatic-upgrade/SKILL.md +228 -0
  98. {repomatic-8.0.0/.claude → repomatic-8.1.0/repomatic/data}/skills/sphinx-docs-sync/SKILL.md +3 -3
  99. {repomatic-8.0.0/.claude → repomatic-8.1.0/repomatic/data}/skills/translation-sync/SKILL.md +2 -2
  100. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/tests.yaml +44 -16
  101. {repomatic-8.0.0/.github/workflows → repomatic-8.1.0/repomatic/data}/unsubscribe.yaml +3 -3
  102. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/lockfile.py +69 -2
  103. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/policy.py +40 -5
  104. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/shippable.py +87 -11
  105. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/sync.py +1 -1
  106. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/git_ops.py +29 -2
  107. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/ci_status.py +29 -10
  108. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/pr.py +46 -3
  109. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/workflow_sync.py +1 -1
  110. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/http.py +64 -9
  111. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/init/run.py +18 -8
  112. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_changelog.py +1 -1
  113. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/repo.py +54 -2
  114. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/roster.py +19 -3
  115. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/tool_config.py +60 -5
  116. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/workflows.py +20 -3
  117. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metadata/core.py +25 -3
  118. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/binaries_page.py +16 -1
  119. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/skills.py +7 -4
  120. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-repomatic.md +1 -1
  121. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/upgrade-invite.md +1 -1
  122. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/tooling/nuitka.py +12 -96
  123. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/tooling/registry.py +75 -30
  124. {repomatic-8.0.0 → repomatic-8.1.0}/tests/conftest.py +5 -4
  125. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_cache.py +32 -35
  126. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_ci_status.py +92 -2
  127. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_claude_assets.py +163 -47
  128. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_dep_policy.py +73 -0
  129. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_dep_sources.py +180 -5
  130. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_docstrings.py +1 -1
  131. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_git_ops.py +11 -1
  132. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_http.py +63 -0
  133. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_imports.py +1 -1
  134. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_init_project.py +65 -39
  135. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_lint_changelog.py +1 -1
  136. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_lint_repo.py +152 -0
  137. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_metadata.py +11 -1
  138. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_nuitka.py +3 -107
  139. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_pr.py +44 -0
  140. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_readme.py +73 -0
  141. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_sphinx_crossrefs.py +4 -1
  142. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_suite_hygiene.py +1 -1
  143. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_todolist.py +1 -1
  144. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_tool_runner.py +49 -0
  145. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_uv.py +88 -0
  146. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_workflows.py +64 -1
  147. {repomatic-8.0.0 → repomatic-8.1.0}/uv.lock +181 -244
  148. repomatic-8.0.0/.claude/skills/repomatic-audit/SKILL.md +0 -182
  149. repomatic-8.0.0/.claude/skills/repomatic-upgrade/SKILL.md +0 -90
  150. repomatic-8.0.0/repomatic/data/skills/repomatic-audit/SKILL.md +0 -182
  151. repomatic-8.0.0/repomatic/data/skills/repomatic-upgrade/SKILL.md +0 -90
  152. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/av-false-positive/SKILL.md +0 -0
  153. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/brand-assets/SKILL.md +0 -0
  154. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/file-bug-report/SKILL.md +0 -0
  155. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/github-housekeeping/SKILL.md +0 -0
  156. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/probe-workflow/SKILL.md +0 -0
  157. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/repomatic-ship/references/findings-in-repomatic.md +0 -0
  158. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/repomatic-ship/references/short-ship.md +0 -0
  159. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/repomatic-topics/SKILL.md +0 -0
  160. {repomatic-8.0.0 → repomatic-8.1.0}/.claude/skills/upstream-audit/SKILL.md +0 -0
  161. {repomatic-8.0.0 → repomatic-8.1.0}/.github/ISSUE_TEMPLATE/bug-report.yml +0 -0
  162. {repomatic-8.0.0 → repomatic-8.1.0}/.github/code-of-conduct.md +0 -0
  163. {repomatic-8.0.0 → repomatic-8.1.0}/.github/funding.yml +0 -0
  164. {repomatic-8.0.0 → repomatic-8.1.0}/.gitignore +0 -0
  165. {repomatic-8.0.0 → repomatic-8.1.0}/.mailmap +0 -0
  166. {repomatic-8.0.0 → repomatic-8.1.0}/docs/404.html +0 -0
  167. {repomatic-8.0.0 → repomatic-8.1.0}/docs/_redirects +0 -0
  168. {repomatic-8.0.0 → repomatic-8.1.0}/docs/_static/custom.css +0 -0
  169. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/banner-social-dark.png +0 -0
  170. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/banner-social-light.png +0 -0
  171. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/banner-social.svg +0 -0
  172. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/desktop-autosync-warning.png +0 -0
  173. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/desktop-plugin-agents.png +0 -0
  174. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/desktop-plugin-contents.png +0 -0
  175. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/desktop-plugin-skills.png +0 -0
  176. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/favicon.svg +0 -0
  177. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/icon.icns +0 -0
  178. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/icon.ico +0 -0
  179. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/icon.png +0 -0
  180. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/logo-banner-dark.png +0 -0
  181. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/logo-banner-light.png +0 -0
  182. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/logo-banner.svg +0 -0
  183. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/logo-square-dark.png +0 -0
  184. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/logo-square-light.png +0 -0
  185. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/logo-square.svg +0 -0
  186. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/metrics.csv +0 -0
  187. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/star-history-compared.svg +0 -0
  188. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/star-history.svg +0 -0
  189. {repomatic-8.0.0 → repomatic-8.1.0}/docs/assets/sync-deps-trail-screen.svg +0 -0
  190. {repomatic-8.0.0 → repomatic-8.1.0}/docs/changelog-archive.md +0 -0
  191. {repomatic-8.0.0 → repomatic-8.1.0}/docs/changelog.md +0 -0
  192. {repomatic-8.0.0 → repomatic-8.1.0}/docs/cli.md +0 -0
  193. {repomatic-8.0.0 → repomatic-8.1.0}/docs/cloudflare.md +0 -0
  194. {repomatic-8.0.0 → repomatic-8.1.0}/docs/code-of-conduct.md +0 -0
  195. {repomatic-8.0.0 → repomatic-8.1.0}/docs/commit-messages.md +0 -0
  196. {repomatic-8.0.0 → repomatic-8.1.0}/docs/index.md +0 -0
  197. {repomatic-8.0.0 → repomatic-8.1.0}/docs/license.md +0 -0
  198. {repomatic-8.0.0 → repomatic-8.1.0}/docs/man.md +0 -0
  199. {repomatic-8.0.0 → repomatic-8.1.0}/docs/packaging.md +0 -0
  200. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.awesome_toc.md +0 -0
  201. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.broken_links.md +0 -0
  202. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.bundle.md +0 -0
  203. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cache.md +0 -0
  204. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.changelog.md +0 -0
  205. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.checks.md +0 -0
  206. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.claude_plugin.md +0 -0
  207. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.ci.md +0 -0
  208. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.deps.md +0 -0
  209. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.github.md +0 -0
  210. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.main.md +0 -0
  211. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.md +0 -0
  212. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.release.md +0 -0
  213. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.repo.md +0 -0
  214. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.site.md +0 -0
  215. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cli.tools.md +0 -0
  216. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cloudflare.api.md +0 -0
  217. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cloudflare.md +0 -0
  218. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cloudflare.pages.md +0 -0
  219. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cloudflare.r2.md +0 -0
  220. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.cloudflare.redirects.md +0 -0
  221. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.components.md +0 -0
  222. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.config.md +0 -0
  223. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.data.awesome_template.md +0 -0
  224. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.data.md +0 -0
  225. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.audit.md +0 -0
  226. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.cooldown.md +0 -0
  227. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.graph.md +0 -0
  228. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.lockfile.md +0 -0
  229. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.md +0 -0
  230. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.pins.md +0 -0
  231. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.policy.md +0 -0
  232. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.provenance.md +0 -0
  233. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.report.md +0 -0
  234. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.requirements.md +0 -0
  235. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.shippable.md +0 -0
  236. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.sources.md +0 -0
  237. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.sync.md +0 -0
  238. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.deps.uv.md +0 -0
  239. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.docs.md +0 -0
  240. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.file_inventory.md +0 -0
  241. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.file_ops.md +0 -0
  242. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.frontmatter.md +0 -0
  243. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.git_ops.md +0 -0
  244. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.caches.md +0 -0
  245. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.ci_status.md +0 -0
  246. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.dev_release.md +0 -0
  247. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.event.md +0 -0
  248. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.gh.md +0 -0
  249. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.issue.md +0 -0
  250. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.job_timings.md +0 -0
  251. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.labels.md +0 -0
  252. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.md +0 -0
  253. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.outputs.md +0 -0
  254. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.pr.md +0 -0
  255. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.pr_body.md +0 -0
  256. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.release_sync.md +0 -0
  257. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.releases.md +0 -0
  258. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.runs.md +0 -0
  259. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.sponsor.md +0 -0
  260. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.status.md +0 -0
  261. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.threads.md +0 -0
  262. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.token.md +0 -0
  263. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.unsubscribe.md +0 -0
  264. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.urls.md +0 -0
  265. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.workflow_files.md +0 -0
  266. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.github.workflow_sync.md +0 -0
  267. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.gitignore.md +0 -0
  268. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.hashing.md +0 -0
  269. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.http.md +0 -0
  270. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.humanize.md +0 -0
  271. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.images.md +0 -0
  272. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.init.md +0 -0
  273. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.init.removed_assets.md +0 -0
  274. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.init.run.md +0 -0
  275. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.init.tool_config.md +0 -0
  276. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.init.upgrade.md +0 -0
  277. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_changelog.md +0 -0
  278. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.context.md +0 -0
  279. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.md +0 -0
  280. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.pins.md +0 -0
  281. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.repo.md +0 -0
  282. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.roster.md +0 -0
  283. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.settings.md +0 -0
  284. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.site.md +0 -0
  285. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.tool_config.md +0 -0
  286. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.lint_repo.workflows.md +0 -0
  287. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.mailmap.md +0 -0
  288. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.markdown.md +0 -0
  289. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.matrix.axes.md +0 -0
  290. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.matrix.md +0 -0
  291. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.matrix.model.md +0 -0
  292. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.matrix.runner_sync.md +0 -0
  293. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.matrix.runners.md +0 -0
  294. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.md +0 -0
  295. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metadata.core.md +0 -0
  296. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metadata.env.md +0 -0
  297. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metadata.git.md +0 -0
  298. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metadata.matrix.md +0 -0
  299. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metadata.md +0 -0
  300. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metadata.output.md +0 -0
  301. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metadata.project.md +0 -0
  302. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metrics.chart.md +0 -0
  303. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metrics.forge.md +0 -0
  304. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metrics.md +0 -0
  305. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.metrics.store.md +0 -0
  306. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.npm.md +0 -0
  307. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.pypi.md +0 -0
  308. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.pyproject.md +0 -0
  309. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.attestation.md +0 -0
  310. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.binaries_page.md +0 -0
  311. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.binary.md +0 -0
  312. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.manpages.md +0 -0
  313. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.md +0 -0
  314. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.prepare_release.md +0 -0
  315. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.protocol.md +0 -0
  316. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.self_pin.md +0 -0
  317. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.verify.md +0 -0
  318. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.release.virustotal.md +0 -0
  319. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.setup_guide.md +0 -0
  320. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.skills.md +0 -0
  321. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.tabular.md +0 -0
  322. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.templates.md +0 -0
  323. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.templating.md +0 -0
  324. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.tooling.binaries.md +0 -0
  325. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.tooling.checksums.md +0 -0
  326. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.tooling.md +0 -0
  327. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.tooling.nuitka.md +0 -0
  328. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.tooling.registry.md +0 -0
  329. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.tooling.runner.md +0 -0
  330. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.upstream.md +0 -0
  331. {repomatic-8.0.0 → repomatic-8.1.0}/docs/repomatic.versions.md +0 -0
  332. {repomatic-8.0.0 → repomatic-8.1.0}/docs/robots.txt +0 -0
  333. {repomatic-8.0.0 → repomatic-8.1.0}/docs/security.md +0 -0
  334. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.conftest.md +0 -0
  335. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.md +0 -0
  336. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_attestation.md +0 -0
  337. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_awesome_template.md +0 -0
  338. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_awesome_toc.md +0 -0
  339. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_binaries.md +0 -0
  340. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_binaries_page.md +0 -0
  341. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_binary.md +0 -0
  342. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_broken_links.md +0 -0
  343. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_cache.md +0 -0
  344. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_changelog.md +0 -0
  345. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_checks.md +0 -0
  346. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_checksums.md +0 -0
  347. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_ci_status.md +0 -0
  348. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_claude_assets.md +0 -0
  349. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_cli.md +0 -0
  350. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_cloudflare.md +0 -0
  351. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_cloudflare_r2.md +0 -0
  352. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_config.md +0 -0
  353. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_coverage_floor.md +0 -0
  354. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_dep_graph.md +0 -0
  355. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_dep_policy.md +0 -0
  356. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_dep_report.md +0 -0
  357. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_dep_sources.md +0 -0
  358. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_dev_release.md +0 -0
  359. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_docs.md +0 -0
  360. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_docstrings.md +0 -0
  361. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_event.md +0 -0
  362. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_file_ops.md +0 -0
  363. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_forge.md +0 -0
  364. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_frontmatter.md +0 -0
  365. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_gh.md +0 -0
  366. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_git_ops.md +0 -0
  367. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_github_caches.md +0 -0
  368. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_gitignore.md +0 -0
  369. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_hashing.md +0 -0
  370. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_help.md +0 -0
  371. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_http.md +0 -0
  372. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_humanize.md +0 -0
  373. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_images.md +0 -0
  374. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_imports.md +0 -0
  375. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_init_project.md +0 -0
  376. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_issue.md +0 -0
  377. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_job_timings.md +0 -0
  378. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_labels.md +0 -0
  379. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_lint_changelog.md +0 -0
  380. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_lint_repo.md +0 -0
  381. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_mailmap.md +0 -0
  382. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_manpages.md +0 -0
  383. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_markdown.md +0 -0
  384. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_matrix.md +0 -0
  385. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_metadata.md +0 -0
  386. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_metadata_git.md +0 -0
  387. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_metrics.md +0 -0
  388. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_npm.md +0 -0
  389. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_nuitka.md +0 -0
  390. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_outputs.md +0 -0
  391. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_pages_redirects.md +0 -0
  392. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_platform_keys.md +0 -0
  393. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_plugin.md +0 -0
  394. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_plugin_update_detection.md +0 -0
  395. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_pr.md +0 -0
  396. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_pr_body.md +0 -0
  397. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_prepare_release.md +0 -0
  398. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_protocol.md +0 -0
  399. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_provenance.md +0 -0
  400. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_pypi.md +0 -0
  401. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_pyproject.md +0 -0
  402. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_readme.md +0 -0
  403. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_release_sync.md +0 -0
  404. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_release_workflow_steps.md +0 -0
  405. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_releases.md +0 -0
  406. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_runner_catalog.md +0 -0
  407. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_runner_sync.md +0 -0
  408. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_runs.md +0 -0
  409. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_self_pin.md +0 -0
  410. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_setup_guide.md +0 -0
  411. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_skills.md +0 -0
  412. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_sphinx_crossrefs.md +0 -0
  413. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_sponsor.md +0 -0
  414. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_status.md +0 -0
  415. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_suite_hygiene.md +0 -0
  416. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_sync_ops.md +0 -0
  417. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_tabular.md +0 -0
  418. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_templating.md +0 -0
  419. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_threads.md +0 -0
  420. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_todolist.md +0 -0
  421. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_token.md +0 -0
  422. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_tool_runner.md +0 -0
  423. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_unsubscribe.md +0 -0
  424. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_upstream.md +0 -0
  425. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_urls.md +0 -0
  426. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_uv.md +0 -0
  427. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_verify.md +0 -0
  428. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_version_sync.md +0 -0
  429. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_versions.md +0 -0
  430. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_virustotal.md +0 -0
  431. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_vulnerable_deps.md +0 -0
  432. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_workflow_files.md +0 -0
  433. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_workflow_sync.md +0 -0
  434. {repomatic-8.0.0 → repomatic-8.1.0}/docs/tests.test_workflows.md +0 -0
  435. {repomatic-8.0.0 → repomatic-8.1.0}/docs/todolist.md +0 -0
  436. {repomatic-8.0.0 → repomatic-8.1.0}/docs/upstream-development.md +0 -0
  437. {repomatic-8.0.0 → repomatic-8.1.0}/license +0 -0
  438. {repomatic-8.0.0 → repomatic-8.1.0}/readme.md +0 -0
  439. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/__main__.py +0 -0
  440. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/awesome_toc.py +0 -0
  441. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/broken_links.py +0 -0
  442. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/bundle.py +0 -0
  443. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/changelog.py +0 -0
  444. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/checks.py +0 -0
  445. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/claude_plugin.py +0 -0
  446. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/__init__.py +0 -0
  447. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/github.py +0 -0
  448. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/main.py +0 -0
  449. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/release.py +0 -0
  450. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/repo.py +0 -0
  451. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/site.py +0 -0
  452. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cli/tools.py +0 -0
  453. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cloudflare/__init__.py +0 -0
  454. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cloudflare/api.py +0 -0
  455. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cloudflare/pages.py +0 -0
  456. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cloudflare/r2.py +0 -0
  457. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/cloudflare/redirects.py +0 -0
  458. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/__init__.py +0 -0
  459. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/actionlint-matcher.json +0 -0
  460. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/actionlint.yaml +0 -0
  461. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/.github/ISSUE_TEMPLATE/config.yml +0 -0
  462. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/.github/ISSUE_TEMPLATE/new-link.yaml +0 -0
  463. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/.github/code-of-conduct.md +0 -0
  464. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/.github/funding.yml +0 -0
  465. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/__init__.py +0 -0
  466. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/awesome_template/license +0 -0
  467. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/bumpversion.toml +0 -0
  468. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/coverage.toml +0 -0
  469. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/labels.toml +0 -0
  470. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/lychee.toml +0 -0
  471. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/mdformat.toml +0 -0
  472. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/mypy.toml +0 -0
  473. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/pytest.toml +0 -0
  474. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/ruff.toml +0 -0
  475. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/av-false-positive/SKILL.md +0 -0
  476. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/brand-assets/SKILL.md +0 -0
  477. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/file-bug-report/SKILL.md +0 -0
  478. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/github-housekeeping/SKILL.md +0 -0
  479. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/probe-workflow/SKILL.md +0 -0
  480. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/repomatic-ship/references/findings-in-repomatic.md +0 -0
  481. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/repomatic-ship/references/short-ship.md +0 -0
  482. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/repomatic-topics/SKILL.md +0 -0
  483. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/skills/upstream-audit/SKILL.md +0 -0
  484. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/typos.toml +0 -0
  485. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/uv.toml +0 -0
  486. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/vt-trend-chart.js +0 -0
  487. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/yamllint.yaml +0 -0
  488. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/data/zizmor.yaml +0 -0
  489. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/__init__.py +0 -0
  490. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/audit.py +0 -0
  491. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/cooldown.py +0 -0
  492. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/graph.py +0 -0
  493. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/pins.py +0 -0
  494. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/provenance.py +0 -0
  495. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/report.py +0 -0
  496. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/requirements.py +0 -0
  497. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/sources.py +0 -0
  498. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/deps/uv.py +0 -0
  499. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/docs.py +0 -0
  500. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/file_inventory.py +0 -0
  501. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/file_ops.py +0 -0
  502. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/frontmatter.py +0 -0
  503. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/__init__.py +0 -0
  504. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/caches.py +0 -0
  505. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/dev_release.py +0 -0
  506. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/event.py +0 -0
  507. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/gh.py +0 -0
  508. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/issue.py +0 -0
  509. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/job_timings.py +0 -0
  510. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/labels.py +0 -0
  511. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/outputs.py +0 -0
  512. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/pr_body.py +0 -0
  513. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/release_sync.py +0 -0
  514. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/releases.py +0 -0
  515. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/runs.py +0 -0
  516. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/sponsor.py +0 -0
  517. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/status.py +0 -0
  518. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/threads.py +0 -0
  519. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/token.py +0 -0
  520. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/unsubscribe.py +0 -0
  521. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/urls.py +0 -0
  522. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/github/workflow_files.py +0 -0
  523. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/gitignore.py +0 -0
  524. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/hashing.py +0 -0
  525. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/humanize.py +0 -0
  526. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/images.py +0 -0
  527. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/init/__init__.py +0 -0
  528. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/init/removed_assets.py +0 -0
  529. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/init/tool_config.py +0 -0
  530. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/init/upgrade.py +0 -0
  531. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/__init__.py +0 -0
  532. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/context.py +0 -0
  533. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/pins.py +0 -0
  534. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/settings.py +0 -0
  535. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/lint_repo/site.py +0 -0
  536. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/mailmap.py +0 -0
  537. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/markdown.py +0 -0
  538. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/matrix/__init__.py +0 -0
  539. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/matrix/axes.py +0 -0
  540. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/matrix/model.py +0 -0
  541. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/matrix/runner_sync.py +0 -0
  542. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/matrix/runners.py +0 -0
  543. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metadata/__init__.py +0 -0
  544. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metadata/env.py +0 -0
  545. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metadata/git.py +0 -0
  546. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metadata/matrix.py +0 -0
  547. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metadata/output.py +0 -0
  548. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metadata/project.py +0 -0
  549. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metrics/__init__.py +0 -0
  550. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metrics/chart.py +0 -0
  551. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metrics/forge.py +0 -0
  552. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/metrics/store.py +0 -0
  553. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/npm.py +0 -0
  554. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/py.typed +0 -0
  555. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/pypi.py +0 -0
  556. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/pyproject.py +0 -0
  557. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/__init__.py +0 -0
  558. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/attestation.py +0 -0
  559. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/binary.py +0 -0
  560. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/manpages.py +0 -0
  561. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/prepare_release.py +0 -0
  562. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/protocol.py +0 -0
  563. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/self_pin.py +0 -0
  564. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/verify.py +0 -0
  565. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/release/virustotal.py +0 -0
  566. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/setup_guide.py +0 -0
  567. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/tabular.py +0 -0
  568. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/__init__.py +0 -0
  569. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/available-admonition.md +0 -0
  570. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/broken-links-issue.md +0 -0
  571. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/bump-version.md +0 -0
  572. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/development-warning.md +0 -0
  573. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/fix-changelog.md +0 -0
  574. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/fix-typos.md +0 -0
  575. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/fix-vulnerable-deps.md +0 -0
  576. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/format-images.md +0 -0
  577. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/format-json.md +0 -0
  578. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/format-markdown.md +0 -0
  579. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/format-pyproject.md +0 -0
  580. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/format-python.md +0 -0
  581. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/format-shell.md +0 -0
  582. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/generated-footer.md +0 -0
  583. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/github-releases.md +0 -0
  584. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/immutable-releases.md +0 -0
  585. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/pr-metadata.md.noformat +0 -0
  586. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/prepare-release.md.noformat +0 -0
  587. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/refresh-tip.md +0 -0
  588. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/release-notes.md +0 -0
  589. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/release-sync-report.md.noformat +0 -0
  590. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sample-metrics.md +0 -0
  591. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/scan-virustotal.md +0 -0
  592. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-branch-ruleset.md +0 -0
  593. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-cloudflare-pages.md +0 -0
  594. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-cloudflare-r2.md +0 -0
  595. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-dependabot.md +0 -0
  596. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-fork-pr-approval.md +0 -0
  597. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-notifications-pat.md +0 -0
  598. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-pages-source.md +0 -0
  599. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-pypi-trusted-publisher.md +0 -0
  600. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-sha-pinning-required.md +0 -0
  601. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-token.md +0 -0
  602. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-verify.md +0 -0
  603. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide-virustotal.md +0 -0
  604. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/setup-guide.md +0 -0
  605. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/squashed-release.md +0 -0
  606. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-action-pins.md +0 -0
  607. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-bumpversion.md +0 -0
  608. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-dep-sources.md +0 -0
  609. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-gitignore.md +0 -0
  610. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-mailmap.md +0 -0
  611. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-repomatic-upgrade.md +0 -0
  612. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-runner-images.md +0 -0
  613. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-tool-versions.md +0 -0
  614. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-uv-lock.md +0 -0
  615. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/sync-workflow-pins.md +0 -0
  616. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/unavailable-admonition.md +0 -0
  617. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/unsubscribe-report.md +0 -0
  618. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/update-dep-graph.md +0 -0
  619. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/update-docs.md +0 -0
  620. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templates/yanked-admonition.md +0 -0
  621. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/templating.py +0 -0
  622. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/tooling/__init__.py +0 -0
  623. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/tooling/binaries.py +0 -0
  624. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/tooling/checksums.py +0 -0
  625. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/tooling/runner.py +0 -0
  626. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/upstream.py +0 -0
  627. {repomatic-8.0.0 → repomatic-8.1.0}/repomatic/versions.py +0 -0
  628. {repomatic-8.0.0 → repomatic-8.1.0}/tests/__init__.py +0 -0
  629. {repomatic-8.0.0 → repomatic-8.1.0}/tests/cli-test-suite.toml +0 -0
  630. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_attestation.py +0 -0
  631. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_awesome_template.py +0 -0
  632. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_awesome_toc.py +0 -0
  633. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_binaries.py +0 -0
  634. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_binaries_page.py +0 -0
  635. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_binary.py +0 -0
  636. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_broken_links.py +0 -0
  637. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_changelog.py +0 -0
  638. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_checks.py +0 -0
  639. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_checksums.py +0 -0
  640. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_cli.py +0 -0
  641. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_cloudflare.py +0 -0
  642. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_cloudflare_r2.py +0 -0
  643. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_config.py +0 -0
  644. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_coverage_floor.py +0 -0
  645. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_dep_graph.py +0 -0
  646. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_dep_report.py +0 -0
  647. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_dev_release.py +0 -0
  648. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_docs.py +0 -0
  649. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_event.py +0 -0
  650. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_file_ops.py +0 -0
  651. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_forge.py +0 -0
  652. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_frontmatter.py +0 -0
  653. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_gh.py +0 -0
  654. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_github_caches.py +0 -0
  655. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_gitignore.py +0 -0
  656. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_hashing.py +0 -0
  657. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_help.py +0 -0
  658. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_humanize.py +0 -0
  659. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_images.py +0 -0
  660. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_issue.py +0 -0
  661. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_job_timings.py +0 -0
  662. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_labels.py +0 -0
  663. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_mailmap.py +0 -0
  664. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_manpages.py +0 -0
  665. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_markdown.py +0 -0
  666. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_matrix.py +0 -0
  667. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_metadata_git.py +0 -0
  668. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_metrics.py +0 -0
  669. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_npm.py +0 -0
  670. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_outputs.py +0 -0
  671. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_pages_redirects.py +0 -0
  672. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_platform_keys.py +0 -0
  673. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_plugin.py +0 -0
  674. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_plugin_update_detection.py +0 -0
  675. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_pr_body.py +0 -0
  676. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_prepare_release.py +0 -0
  677. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_protocol.py +0 -0
  678. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_provenance.py +0 -0
  679. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_pypi.py +0 -0
  680. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_pyproject.py +0 -0
  681. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_release_sync.py +0 -0
  682. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_release_workflow_steps.py +0 -0
  683. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_releases.py +0 -0
  684. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_runner_catalog.py +0 -0
  685. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_runner_sync.py +0 -0
  686. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_runs.py +0 -0
  687. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_self_pin.py +0 -0
  688. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_setup_guide.py +0 -0
  689. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_skills.py +0 -0
  690. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_sponsor.py +0 -0
  691. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_status.py +0 -0
  692. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_sync_ops.py +0 -0
  693. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_tabular.py +0 -0
  694. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_templating.py +0 -0
  695. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_threads.py +0 -0
  696. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_token.py +0 -0
  697. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_unsubscribe.py +0 -0
  698. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_upstream.py +0 -0
  699. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_urls.py +0 -0
  700. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_verify.py +0 -0
  701. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_version_sync.py +0 -0
  702. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_versions.py +0 -0
  703. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_virustotal.py +0 -0
  704. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_vulnerable_deps.py +0 -0
  705. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_workflow_files.py +0 -0
  706. {repomatic-8.0.0 → repomatic-8.1.0}/tests/test_workflow_sync.py +0 -0
@@ -20,5 +20,5 @@
20
20
  "license": "GPL-2.0-or-later",
21
21
  "name": "repomatic",
22
22
  "repository": "https://github.com/kdeldycke/repomatic",
23
- "version": "8.0.0"
23
+ "version": "8.1.0"
24
24
  }
@@ -1,31 +1,31 @@
1
1
  ---
2
2
  name: grunt-qa
3
- description: Hands-on QA worker that enforces CLAUDE.md. Fixes obvious issues, enforces style and ordering, and reports deeper findings to qa-engineer.
3
+ description: Hands-on QA worker that enforces AGENTS.md. Fixes obvious issues, enforces style and ordering, and reports deeper findings to qa-engineer.
4
4
  tools: Read, Grep, Glob, Bash, Edit, Write
5
5
  model: sonnet
6
6
  ---
7
7
 
8
- You are "grunt-qa." Before doing anything, read `CLAUDE.md` and your own `.claude/agents/grunt-qa.md` end to end. `CLAUDE.md` defines the rules. The codebase and GitHub are what you measure against those rules.
8
+ You are "grunt-qa." Before doing anything, read `AGENTS.md` and your own `.claude/agents/grunt-qa.md` end to end. `AGENTS.md` defines the rules. The codebase and GitHub are what you measure against those rules.
9
9
 
10
10
  Your teammate is "qa-engineer." Not your boss — you work side-by-side. You spot details and ground truth; they think in concepts and architecture. If qa-engineer is not deployed in this repo, do your own job in full and skip the cross-agent reporting steps.
11
11
 
12
12
  ## Prime directive
13
13
 
14
- Every file you touch must comply with `CLAUDE.md`. When you find a violation — fix it. No exceptions, no judgment calls. If there is something you cannot fix, report it to qa-engineer with the specific `CLAUDE.md` rule it violates; if qa-engineer is unavailable, document the unfixed violation in your final response so the user can act on it.
14
+ Every file you touch must comply with `AGENTS.md`. When you find a violation — fix it. No exceptions, no judgment calls. If there is something you cannot fix, report it to qa-engineer with the specific `AGENTS.md` rule it violates; if qa-engineer is unavailable, document the unfixed violation in your final response so the user can act on it.
15
15
 
16
16
  Work beyond the local repository: check issues, PRs, and CI runs on GitHub. Fix violations in the working tree only: never commit, push, open a pull request, or post to GitHub without explicit approval.
17
17
 
18
18
  ## Tools of the trade
19
19
 
20
20
  - `gh issue list`, `gh pr list`, `gh pr view`, `gh run view`
21
- - `repomatic ci-status`, `repomatic lint-repo`, `repomatic show-metadata`, and every other subcommand. Inside `kdeldycke/repomatic` itself (a `repomatic/__init__.py` exists) reach it as `uv run repomatic`; anywhere else it is not a project dependency, so use `uvx --exclude-newer '{window}' --exclude-newer-package repomatic=P0D -- repomatic`. Read `{window}` from the `UV_EXCLUDE_NEWER` value of any `.github/workflows/*.yaml`, which `repomatic init` renders from `[tool.repomatic] minimum-release-age`. The command holds the dependency tree to that supply-chain cooldown while keeping a fresh repomatic release installable. A bare `uv run repomatic` downstream dies on `Failed to spawn: repomatic`.
21
+ - `repomatic ci-status`, `repomatic lint-repo`, `repomatic show-metadata`, and every other subcommand. Inside `kdeldycke/repomatic` itself (a `repomatic/__init__.py` exists) reach it as `uv run --frozen repomatic`; anywhere else it is not a project dependency, so use `uvx --exclude-newer '{window}' --exclude-newer-package repomatic=P0D --from 'repomatic=={version}' -- repomatic`. Read `{window}` from the `UV_EXCLUDE_NEWER` value of any `.github/workflows/*.yaml`, which `repomatic init` renders from `[tool.repomatic] minimum-release-age`. Read `{version}` from the `# vX.Y.Z` comment that ends a `uses: kdeldycke/repomatic/...@{sha}` line in those files. Drop the `--from` clause when no line pins one. The pin keeps the tool registry, and so the `ruff` and `mypy` versions, identical to what CI runs. The command holds the dependency tree to that supply-chain cooldown while keeping a fresh repomatic release installable. A bare `uv run repomatic` downstream dies on `Failed to spawn: repomatic`.
22
22
  - Tests, type checking, linting
23
23
 
24
24
  ## Checks
25
25
 
26
- 1. **`CLAUDE.md` compliance** — Read it, then grep the codebase for violations. Fix all of: typos, grammar, stale references, ordering violations, style issues, documentation sync issues. Remove content a reader could discover from the codebase: structural inventories, copied code examples, general programming knowledge.
26
+ 1. **`AGENTS.md` compliance** — Read it, then grep the codebase for violations. Fix all of: typos, grammar, stale references, ordering violations, style issues, documentation sync issues. Remove content a reader could discover from the codebase: structural inventories, copied code examples, general programming knowledge.
27
27
  2. **CLI health** — Run every subcommand's `--help`; fix docs if output diverges
28
- 3. **Documentation sync** — Inside `kdeldycke/repomatic` only, per `CLAUDE.md` § Documentation sync (upstream maintainers). Skip it elsewhere: the section is upstream-only and never reaches a downstream `claude.md`.
28
+ 3. **Documentation sync** — Inside `kdeldycke/repomatic` only, per `AGENTS.md` § Documentation sync (upstream maintainers). Skip it elsewhere: the section is upstream-only and never reaches a downstream `AGENTS.md`.
29
29
  4. **Quality checks** — Run the test suite, type checks and linters; fix simple issues, escalate complex ones
30
30
  5. **Release alignment** — Inside `kdeldycke/repomatic` only: the checklist lives in `docs/upstream-development.md` § Release checklist, and `/repomatic-ship` drives it. Downstream repos follow their own release process.
31
31
  6. **CI/CD failures** — Review recent failed runs, distinguish systematic from one-off
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: qa-engineer
3
- description: Senior QA engineer. Handles deep analysis, new automation and architectural decisions. Questions verbose prose and deduplicates content across CLAUDE.md and agent definitions.
3
+ description: Senior QA engineer. Handles deep analysis, new automation and architectural decisions. Questions verbose prose and deduplicates content across AGENTS.md and agent definitions.
4
4
  tools: Read, Grep, Glob, Bash, Edit, Write
5
5
  model: opus
6
6
  ---
@@ -35,14 +35,14 @@ When a specific bug is reported or fixed, treat it as a symptom of a possible sy
35
35
 
36
36
  ## Prose hygiene
37
37
 
38
- Question overly verbose prose in `CLAUDE.md` and `.claude/agents/*.md`:
38
+ Question overly verbose prose in `AGENTS.md` and `.claude/agents/*.md`:
39
39
 
40
- - Content duplicated between files — move to `CLAUDE.md`, replace with a reference
40
+ - Content duplicated between files — move to `AGENTS.md`, replace with a reference
41
41
  - Wordy explanations — tighten to a single sentence
42
42
  - Redundant examples or restated rules — cut them
43
- - **Discoverable content** — cut it. Structural inventories, code examples copied from source files, and general programming knowledge do not belong in `CLAUDE.md`.
43
+ - **Discoverable content** — cut it. Structural inventories, code examples copied from source files, and general programming knowledge do not belong in `AGENTS.md`.
44
44
  - **Misplaced knowledge** — move it to the audience that owns it. Lengthy "why" explanations in YAML workflows belong in Python docstrings; YAML gets a brief "what" + pointer. End-user setup details belong in `setup-guide.md`, not `readme.md`.
45
- - **Code-anchored rules** — move them beside the code. A rule in `CLAUDE.md` whose subject is one function, test, workflow, setting or page belongs in that docstring or comment, where it cannot drift unseen. Compare the two first: delete the rule when the code already states it, and read the code when they disagree. `CLAUDE.md` keeps a one-line pointer.
45
+ - **Code-anchored rules** — move them beside the code. A rule in `AGENTS.md` whose subject is one function, test, workflow, setting or page belongs in that docstring or comment, where it cannot drift unseen. Compare the two first: delete the rule when the code already states it, and read the code when they disagree. `AGENTS.md` keeps a one-line pointer.
46
46
 
47
47
  Prefer mechanical enforcement over prose. If a rule can be a test, autofix job, or lint check — implement it instead of writing it down.
48
48
 
@@ -52,9 +52,9 @@ When grunt-qa reports repetitive patterns (or when you notice them yourself in s
52
52
 
53
53
  ## Agent definition gatekeeper
54
54
 
55
- You own `.claude/agents/*.md`. When grunt-qa (or your own analysis) surfaces new tools or techniques, decide what gets added to agent definitions and what belongs in `CLAUDE.md` instead.
55
+ You own `.claude/agents/*.md`. When grunt-qa (or your own analysis) surfaces new tools or techniques, decide what gets added to agent definitions and what belongs in `AGENTS.md` instead.
56
56
 
57
- The roster is `grunt-qa`, `qa-engineer`, and `sphinx-docs`. The last one carries Sphinx-and-MyST documentation conventions (`{click:run}` directives, `configuration.md`/`cli.md`/`install.md` recipes, `conf.py` hygiene, the standard page roster). Route doc-specific findings there; route cross-cutting Python and project conventions to `CLAUDE.md`.
57
+ The roster is `grunt-qa`, `qa-engineer`, and `sphinx-docs`. The last one carries Sphinx-and-MyST documentation conventions (`{click:run}` directives, `configuration.md`/`cli.md`/`install.md` recipes, `conf.py` hygiene, the standard page roster). Route doc-specific findings there; route cross-cutting Python and project conventions to `AGENTS.md`.
58
58
 
59
59
  ## Session history mining
60
60
 
@@ -63,7 +63,7 @@ Periodically analyze prompt logs for recurring patterns, frustrations, and blind
63
63
  - `~/.claude/history.jsonl`: one line per prompt, across all sessions and projects. Filter for this project's working directory.
64
64
  - `~/.claude/projects/<project_name>/*.jsonl`: full conversation transcripts, one file per session.
65
65
 
66
- Look for: repeated fix requests (something keeps breaking), recurring CI debugging sessions (a workflow is fragile), documentation sync failures (the same docs go stale), and design-alternative discussions (the user keeps questioning a pattern). Distill findings into local `CLAUDE.md` rules or new automation. If the pattern is generic and would benefit other repos using `repomatic`, file an upstream proposal at [`kdeldycke/repomatic`](https://github.com/kdeldycke/repomatic/issues).
66
+ Look for: repeated fix requests (something keeps breaking), recurring CI debugging sessions (a workflow is fragile), documentation sync failures (the same docs go stale), and design-alternative discussions (the user keeps questioning a pattern). Distill findings into local `AGENTS.md` rules or new automation. If the pattern is generic and would benefit other repos using `repomatic`, file an upstream proposal at [`kdeldycke/repomatic`](https://github.com/kdeldycke/repomatic/issues).
67
67
 
68
68
  ## Coordination
69
69
 
@@ -5,7 +5,7 @@ tools: Read, Grep, Glob, Bash, Edit, Write
5
5
  model: sonnet
6
6
  ---
7
7
 
8
- You are "sphinx-docs." You own everything under `docs/` for projects that build their site with Sphinx + MyST. Read `CLAUDE.md` and this file end to end before touching any documentation.
8
+ You are "sphinx-docs." You own everything under `docs/` for projects that build their site with Sphinx + MyST. Read `AGENTS.md` and this file end to end before touching any documentation.
9
9
 
10
10
  Your teammates are `grunt-qa` and `qa-engineer`. When they aren't deployed, absorb their feedback loop: do the mechanical fixes yourself and surface architectural findings in your final report.
11
11
 
@@ -168,7 +168,7 @@ Anti-pattern: any `render`-family block that takes more than a second or two to
168
168
 
169
169
  **Hard prerequisite — the generator must be importable from the installed package.** The mirror refresher and the `source-read` rebuild both `exec` each block with a bare namespace and no `sys.path` setup, so a mirror block may only import from the installed distribution (`from {package}.x import ...`), never a docs-local helper under `docs/`. A block that does `from docs_update import ...` raises `ModuleNotFoundError` under `click-extra refresh-directives` run from the repo root (verified in extra-platforms), which fails that whole refresh phase.
170
170
 
171
- If the generators are docs-only tooling you don't want in the public API, ship them in a **private** package module — a leading-underscore name keeps them out of the public surface while still installed and importable. Extra-platforms moved its table/diagram generators from `docs/docs_update.py` into `extra_platforms/_docs.py`; the `:mirror:` blocks do `from extra_platforms._docs import generate_trait_table`. Two things to get right when a docs-only dep is involved: keep the package's runtime clean by never importing the private module from `__init__` (extra_platforms stays dependency-free at import; `_docs` pulls `click_extra.table` only when a docs build calls it), and add a mypy override (`[[tool.mypy.overrides]] module = "click_extra.*" ignore_missing_imports = true`) because the type-check venv (`uv run` with no `--group docs`) lacks the docs dependency. `docs/docs_update.py` then keeps only what can't be a mirror block: the `readme.md` mindmaps (a `:mirror:` block would expose the generator's `{python:render}` fence on the user-facing README) and the reST `{eval-rst}` autodoc regions (autodoc can't be a Markdown mirror). Update those marker regions through click-extra's own `update_blocks(paths, rewrite, *, check=False)` — the walk/write/dry-run primitive behind `:mirror:` and `{matrix}` — instead of a hand-rolled `wcmatch` loop; it hands you a `--check` mode for CI drift detection for free. It is public API in `click_extra.blocks` since click-extra `8.8.0`, which `click_extra.sphinx` also re-exports.
171
+ If the generators are docs-only tooling you don't want in the public API, ship them in a **private** package module — a leading-underscore name keeps them out of the public surface while still installed and importable. Extra-platforms moved its table/diagram generators from `docs/docs_update.py` into `extra_platforms/_docs.py`; the `:mirror:` blocks do `from extra_platforms._docs import generate_trait_table`. Two things to get right when a docs-only dep is involved: keep the package's runtime clean by never importing the private module from `__init__` (extra_platforms stays dependency-free at import; `_docs` pulls `click_extra.table` only when a docs build calls it), and add a mypy override (`[[tool.mypy.overrides]] module = "click_extra.*" ignore_missing_imports = true`) because the type-check venv (`uv run` with no `--group docs`) lacks the docs dependency. `docs/docs_update.py` then keeps only what can't be a mirror block: the `readme.md` mindmaps (a `:mirror:` block would expose the generator's `{python:render}` fence on the user-facing README) and the reST `{eval-rst}` autodoc regions (autodoc can't be a Markdown mirror). Update those marker regions through click-extra's own `update_blocks(paths, rewrite, *, check=False)` — the walk/write/dry-run primitive behind `:mirror:` and `{matrix}` — instead of a hand-rolled `wcmatch` loop; it hands you a `--check` mode for CI drift detection for free. It is public API since click-extra `8.8.0`. Import it from `click_extra.markdown.blocks` since `10.0.0`, and from `click_extra.blocks` or `click_extra.sphinx` before.
172
172
 
173
173
  ### `:emphasize-lines:` vs `:emphasize-result-lines:`
174
174
 
@@ -351,7 +351,7 @@ Standard `myst_enable_extensions`, alphabetized (omit only when the project demo
351
351
 
352
352
  For `pyproject.toml` schemas, CLI command lists, and tool registries, generate the markdown from the source of truth. The pattern: a `docs/docs_update.py` script writes between named auto-region markers, invoked by the upstream `autofix.yaml` workflow's `update-docs` job via `repomatic update-docs`. It sits there rather than in `docs.yaml` because it commits a fix like every other autofix job; `docs.yaml` only builds and deploys.
353
353
 
354
- **Marker naming convention.** Name each auto-region descriptively as `{feature}-{kind}` and wrap it in click-extra's `<!-- {feature}-{kind} --> / <!-- {feature}-{kind}-end -->` marker grammar: the grammar of `click_extra.blocks.replace_region` and of click-extra's own `{matrix}` and `mirror` markers. Never use generic bare `<!-- start -->`/`<!-- end -->`. Rationale: a single doc page often holds two or three auto-regions (a summary table, a Mermaid graph, an autodata block). Generic markers force the regenerator to use index-based dispatch and break the moment a region is reordered or removed; named markers stay correct under any rearrangement and grep cleanly. Examples:
354
+ **Marker naming convention.** Name each auto-region descriptively as `{feature}-{kind}` and wrap it in click-extra's `<!-- {feature}-{kind} --> / <!-- {feature}-{kind}-end -->` marker grammar: the grammar of click-extra's `replace_region` and of its own `{matrix}` and `mirror` markers. `replace_region` is exported from the `click_extra` root since `10.0.0`, and from `click_extra.blocks` before. Never use generic bare `<!-- start -->`/`<!-- end -->`. Rationale: a single doc page often holds two or three auto-regions (a summary table, a Mermaid graph, an autodata block). Generic markers force the regenerator to use index-based dispatch and break the moment a region is reordered or removed; named markers stay correct under any rearrangement and grep cleanly. Examples:
355
355
 
356
356
  - `<!-- binaries-chart -->` / `<!-- binaries-chart-end -->` (a VirusTotal detections chart on the binaries page).
357
357
  - `<!-- managers-sankey -->` / `<!-- managers-sankey-end -->` (a Mermaid sankey of supported managers).
@@ -500,7 +500,7 @@ Agent tooling toctree, in this order. Drop the whole block when the project ship
500
500
 
501
501
  Maintainer-facing pages, and when a project carries one:
502
502
 
503
- 01. `contributing` — Setup, dev loop, code-style pointers (or `{include} ../contributing.md` if the root file already exists). The one home of developer setup: `readme.md` and `claude.md` link to it.
503
+ 01. `contributing` — Setup, dev loop, code-style pointers (or `{include} ../contributing.md` if the root file already exists). The one home of developer setup: `readme.md` and `AGENTS.md` link to it.
504
504
  02. `commit-messages` — Only when automation reads or writes the project's commit subjects, which makes the subject a shared namespace rather than free text: the reserved-prefix rules, who else parses a message, and how to write a subject and body.
505
505
  03. `upstream-development` — Project-internal release process. Mark `(upstream maintainers only)` in the page heading so readers know this is not for consumers.
506
506
  04. `operation-contracts` — Optional, for projects with formal automated-operation contracts.
@@ -643,7 +643,7 @@ Skills and subagents pages (when shipped):
643
643
  Pages that **don't** belong in the roster:
644
644
 
645
645
  - A "FAQ" page. FAQ entries are usually conventions or trade-offs that belong in the relevant feature page, or troubleshooting guides that belong in the issue tracker.
646
- - A "Glossary" page. Inline definitions next to first use are easier to maintain. If a term appears project-wide, record its spelling in `CLAUDE.md` instead.
646
+ - A "Glossary" page. Inline definitions next to first use are easier to maintain. If a term appears project-wide, record its spelling in `AGENTS.md` instead.
647
647
  - "Tutorials" separate from feature pages. Each feature page should carry its own walkthrough; a separate tutorial section bit-rots fast.
648
648
 
649
649
  ## Guide pages carry the prose, API pages carry the API
@@ -671,7 +671,7 @@ Default-pruning rule:
671
671
  - If a setting equals its Sphinx (or extension) default, delete it. Don't comment it out — `git blame` already records intent.
672
672
  - If you keep a setting that *looks* default for documentation purposes, add a one-line comment explaining why ("explicit so future readers see we considered it").
673
673
  - On every Sphinx or extension upgrade, run `sphinx-build -W -b html docs docs/_build/html`. Treat every `RemovedInSphinxX.YWarning`, `DeprecationWarning`, and `application.ExtensionError` as cleanup work, not noise. Fix them in the same PR as the upgrade.
674
- - **Match the deployed builder, which is not always `html`.** `[tool.repomatic] sphinx.builder` is what the Docs workflow passes to `sphinx-build -b`, and a project serving extension-less URLs sets it to `dirhtml` (`page/index.html` instead of `page.html`). Read it before assuming a local `-b html` reproduces CI. The builder is chosen on the command line, so it is the one Sphinx setting `conf.py` cannot carry: never "fix" its absence there.
674
+ - **Match the deployed builder, which is not always `html`.** `[tool.repomatic] sphinx.builder` is what the Docs workflow passes to `sphinx-build -b`, and a project serving extension-less URLs sets it to `dirhtml` (`page/index.html` instead of `page.html`). Read it before assuming a local `-b html` reproduces CI. The builder is chosen on the command line, so `conf.py` cannot carry it: never "fix" its absence there. `sphinx.fail-on-warning` is the same kind of setting: it adds `--fail-on-warning` to the CI build.
675
675
  - **A warning count only covers the pages that build re-read.** Sphinx reuses cached doctrees, so an incremental rebuild reports the warnings of the changed pages alone, and reading that number against a cold build's count shows a drop nothing caused. A `conf.py` edit invalidates the whole cache, which is why the build right after one reports many more. Build into a clean `_build/` before comparing two counts.
676
676
  - **Compare two builds only when both hold the same dependency groups.** autodoc imports each module it documents. A build that lacks one group fails those imports, like the test group for a `tests` API page, and each reference into such a module then reports as unresolved. Build the baseline from an export of `HEAD` and the candidate from the working tree, both with `uv run --isolated --frozen --all-extras --all-groups`: neither touches the shared virtual environment.
677
677
  - **Run `sphinx-build` with the command sandbox off.** Inside the Claude Code sandbox (`2.1.284`, macOS, 2026-10-02), `sphinx_sitemap` aborts the build at `builder-inited` with `PermissionError: [Errno 1] Operation not permitted`. Intersphinx also fails to fetch its inventories there. Neither failure says anything about the docs.
@@ -766,13 +766,13 @@ When introducing a new doc convention worth defending mechanically (e.g., "every
766
766
 
767
767
  When you receive a new "rule" about how to write or maintain docs, ask where it belongs. Each piece of knowledge has one home, chosen by audience:
768
768
 
769
- - A convention every doc must follow → `claude.md`.
769
+ - A convention every doc must follow → `AGENTS.md`.
770
770
  - A pattern only the upstream package itself uses (e.g., `docs/docs_update.py` internals, release-only artifacts) → `docs/upstream-development.md`.
771
771
  - A pattern downstream Sphinx repos benefit from → this agent definition.
772
772
 
773
- State a rule that belongs here inline, never as a pointer to a `claude.md` section. This file ships to repositories that do not receive repomatic's `claude.md`.
773
+ State a rule that belongs here inline, never as a pointer to an `AGENTS.md` section. This file ships to repositories that do not receive repomatic's `AGENTS.md`.
774
774
 
775
- When a user-driven instruction explicitly conflicts with a `claude.md` or global tropes rule (e.g., the install.md compatibility-matrix range labels use a `→` arrow, which conflicts with the global `Unicode Decoration` anti-pattern), the explicit instruction takes precedence. Note the conflict in your reply so the user can confirm or override, but apply the instruction.
775
+ When a user-driven instruction explicitly conflicts with an `AGENTS.md` or global tropes rule (e.g., the install.md compatibility-matrix range labels use a `→` arrow, which conflicts with the global `Unicode Decoration` anti-pattern), the explicit instruction takes precedence. Note the conflict in your reply so the user can confirm or override, but apply the instruction.
776
776
 
777
777
  ## Documentation sync
778
778
 
@@ -795,7 +795,7 @@ Watch for these every pass:
795
795
  - A `{toctree}` that outgrew the ~12-entry threshold and is still flat, or a captioned section left holding a single entry after pages moved around it. See § Grouping pages into sidebar sections.
796
796
  - An `automodule` block on a narrative page, repeating what the module's own API page already documents. Every such pair costs a duplicate object description per member and buries the guide's message; see § Guide pages carry the prose, API pages carry the API.
797
797
  - Stale `.rst` files in `docs/` left over from package renames or earlier `sphinx-apidoc` runs that reference modules or packages no longer in the source tree. They build silently (autodoc skips missing modules with a warning, not an error) but pollute search results and the modindex. Sweep with `git status` after `update-docs`; delete orphans in the same PR.
798
- - Developer setup held in `readme.md` (a `## Development` section) or in `claude.md`. Setup, dev loop and test commands belong on the `contributing` page of the roster, where a contributor looks for them. `claude.md` loads into every agent session, so it keeps conventions and links to that page. A second copy creates two places to update.
798
+ - Developer setup held in `readme.md` (a `## Development` section) or in `AGENTS.md`. Setup, dev loop and test commands belong on the `contributing` page of the roster, where a contributor looks for them. `AGENTS.md` loads into every agent session, so it keeps conventions and links to that page. A second copy creates two places to update.
799
799
  - A `packaging.md` page whose embedded Mermaid graph hasn't been regenerated since the last `uv lock` change. The graph stays in sync only if `repomatic update-dep-graph` is wired into a workflow job; manual regeneration drifts. Upstream that job lives in `autofix.yaml` and runs on every push, so a graph lagging `pyproject.toml` means its pull request is still open, not drift. With `[tool.repomatic] dependency-graph.update = false`, the command writes no graph and the job opens no pull request.
800
800
  - `pyproject.toml` declaring a docs dependency that's no longer imported by `conf.py` (or vice-versa: importing one not declared). The mismatch passes Sphinx but trips a fresh `uv sync --group docs` run on a CI runner.
801
801
  - `click_extra.sphinx.myst_docstrings` listed in `extensions` without `click-extra[sphinx]` declared in `[dependency-groups] docs`. Builds work on the maintainer's machine if the package is installed globally, then break in CI.
@@ -55,7 +55,7 @@ This is not covered by `contributing.md`. Look for these signals. **Any two, dra
55
55
  - The PR body or issue text reads as LLM output (generic phrasing, no specific knowledge of the list's content, template-like structure beyond the actual template).
56
56
  - The PR explicitly discloses AI generation (e.g., "Generated with Claude Code", "Created by Copilot").
57
57
  - The linked resource's content appears auto-generated (generic copy, placeholder text, stock descriptions, no voice or editorial specificity).
58
- - The product is not launched (coming soon pages, empty repos, placeholder domains on Vercel/Netlify).
58
+ - The product is not launched (coming soon pages, empty repos). A temporary address is a separate hard check: see §8.
59
59
  - The proposed description is a rewrite of the resource's meta description or first paragraph without editorial judgment.
60
60
 
61
61
  See also §9 for contributor and repo provenance signals — these often reinforce the surface-level slop tells above.
@@ -88,6 +88,12 @@ Check the diff (for PRs) against `contributing.md` §§ Formatting and Editorial
88
88
  #### 8. Resource quality
89
89
 
90
90
  - **Launched and functional**: The product or article must exist and be accessible.
91
+ - **Production URL**: The link must resolve, after redirects, to the permanent home of the resource. Content, code, products and services at a temporary, development or preproduction address fail this check, whatever their quality. These addresses count as temporary:
92
+ - A subdomain that a hosting platform assigns by default, like `*.pages.dev`, `*.workers.dev`, `*.vercel.app`, `*.netlify.app`, `*.surge.sh`, `*.onrender.com`, `*.herokuapp.com`, `*.fly.dev` or `*.web.app`.
93
+ - A staging marker in the hostname or path (`staging`, `preprod`, `dev`, `preview`, `test`, `qa`, `uat`), `localhost`, or a bare IP address.
94
+ - A tunnel (`*.ngrok-free.app`, `*.trycloudflare.com`), or a playground link (StackBlitz, CodeSandbox, Replit) in place of a repository.
95
+ - **Permanent docs hosts**: GitHub Pages, GitLab Pages and Read the Docs are the permanent home of many open-source projects. Accept them for the documentation or the articles of a project, but not for a commercial product.
96
+ - **Canonical address**: When a temporary address is the only failed check, ask the contributor for the canonical one on their own domain. Suggest the source repository instead when it meets the baseline in `contributing.md`.
91
97
  - **Maintained**: For GitHub repos, check if the project is archived, when the last commit was. Archived or abandoned projects are candidates for removal (contributing.md FAQ "Why removes inactive GitHub projects?"). Check for forks or reboots before recommending deletion.
92
98
  - **Generic, not product-specific**: Articles applicable to only one product are not generic enough for inclusion (contributing.md "Why my link was rejected?").
93
99
  - **Original, not a rehash of its own sources**: Trace the candidate to its primary source before scoring it. Look for a republication notice ("Originally published at ..."), then diff the body against whatever it links under "further reading" or references. A page that paraphrases Wikipedia row by row without citing it adds an unstable hop and no data: prefer the primary source, and write the software framing into the description yourself, which `contributing.md` section Formatting licenses as "smart editorializing". Same test picks the canonical URL: the author's own domain beats a syndication, an aggregator or a mirror.
@@ -116,7 +122,7 @@ This is not covered by `contributing.md`. Use to filter vibe-coded throwaway pro
116
122
 
117
123
  **Cross-checks**:
118
124
 
119
- - Demo URLs on disposable hosts (`*.surge.sh`, `*.vercel.app`, `*.netlify.app`, GitHub Pages) as **the product domain** itself, not just a docs deploy.
125
+ - Product domain on a temporary or platform-assigned host (§8 "Production URL"). Besides the hard reject, it counts as one signal toward the §3 two-signal bar.
120
126
  - Future-dated "verified" / "as of" stamps in the resource content that don't match the git history.
121
127
  - Numerical claims in the PR body (counts of supported items, languages, integrations) that don't match the actual product page — inconsistencies are a generation-time tell, not a copywriting choice.
122
128
 
@@ -134,7 +140,7 @@ After running all checks, provide one of:
134
140
 
135
141
  - **ACCEPT**: All checks pass. Suggest merging (possibly with minor formatting fixes).
136
142
  - **ACCEPT WITH CHANGES**: Value is there but formatting, description, or placement needs work. List the specific changes needed.
137
- - **REJECT**: Fails one or more hard criteria (duplicate, AI slop, not launched, paywalled, no value-add, section saturation, competitive context mismatch). Draft a rejection comment.
143
+ - **REJECT**: Fails one or more hard criteria (duplicate, AI slop, not launched, temporary URL, paywalled, no value-add, section saturation, competitive context mismatch). Draft a rejection comment.
138
144
  - **NEEDS DISCUSSION**: Borderline case where maintainer judgment is required. Summarize the arguments for and against.
139
145
 
140
146
  After the verdict, propose 2-3 short, ready-to-post comments that the maintainer can copy-paste to explain the decision to the author. Each comment should reference the specific reason (criterion name, `contributing.md` section, or precedent PR) so the author understands the rationale without needing to read the full triage analysis.
@@ -153,6 +159,8 @@ When drafting a rejection or request-for-changes comment:
153
159
 
154
160
  - For AI slop: keep it brief. State the specific tells (e.g., "the site content appears auto-generated", "the product does not appear to be launched yet").
155
161
 
162
+ - For a temporary URL: name the address type (a platform default or preview domain). Ask for the canonical address only when no other check failed, so the contributor does not resubmit for nothing.
163
+
156
164
  - When a section is saturated, suggest the contributor identify weaker existing entries that could be replaced, turning an addition into a curation improvement.
157
165
 
158
166
  - **Always close a declined commercial or self-promotional submission with this exact phrase, verbatim, as the last line of the comment**, whether or not the affiliation was disclosed:
@@ -8,6 +8,12 @@ compatibility: 'Designed for Claude Code. Recommended model: Sonnet.'
8
8
 
9
9
  Monitor the `tests.yaml`, `lint.yaml`, `autofix.yaml`, `docs.yaml`, and `release.yaml` (Nuitka binary matrix, on projects that enable it) workflows in a fix-verify loop until all stable matrix variations pass and type-checking is clean.
10
10
 
11
+ ## Context
12
+
13
+ !`[ -f repomatic/__init__.py ] && echo "CANONICAL_REPO" || echo "DOWNSTREAM"`
14
+
15
+ !`grep -rhoE 'kdeldycke/repomatic/[^@ ]+@[0-9a-f]{40} # v[0-9.]+' .github/workflows 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+$' | sort -u | sed 's/^/WORKFLOW_PIN=/'`
16
+
11
17
  ## Invocation
12
18
 
13
19
  This skill involves repeated `gh`, `git`, `uv run pytest`, `git commit`, and `git push` calls. Run with `--dangerously-skip-permissions` to avoid manual approval on each step. Sonnet is recommended: the task is mechanical (fetch logs, match patterns, edit code, commit) and doesn't need deep reasoning:
@@ -19,10 +25,17 @@ $ claude --dangerously-skip-permissions --model sonnet /babysit-ci
19
25
  > [!WARNING]
20
26
  > `--dangerously-skip-permissions` bypasses every permission prompt for the whole session: only use it in an environment you trust, ideally a sandbox or disposable checkout, never against an unfamiliar repository or untrusted input.
21
27
 
22
- Because this loop runs autonomously without human review, **every commit carries a `Co-Authored-By: Claude <noreply@anthropic.com>` trailer by default** so unattended changes stay traceable, including where a project `CLAUDE.md` or a global `~/.claude/CLAUDE.md` says nothing about commit attribution. The default yields to one thing: an explicit standing rule from the repository's maintainer against AI attribution, which outranks it because the trailer lands in their permanent history. A parent skill (like `/repomatic-ship`) spawning this loop does not by itself relax the requirement, but an exemption that skill passes down does, and it binds every commit made from that point on.
28
+ Because this loop runs autonomously without human review, **every commit carries a `Co-Authored-By: Claude <noreply@anthropic.com>` trailer by default** so unattended changes stay traceable, including where a project `AGENTS.md` or a global `~/.claude/CLAUDE.md` says nothing about commit attribution. The default yields to one thing: an explicit standing rule from the repository's maintainer against AI attribution, which outranks it because the trailer lands in their permanent history. A parent skill (like `/repomatic-ship`) spawning this loop does not by itself relax the requirement, but an exemption that skill passes down does, and it binds every commit made from that point on.
23
29
 
24
30
  Keep the message itself short: an imperative subject naming the fix, under 72 characters, and **no body at all** unless the commit meets one of three cases. It bundles orthogonal work, a public record holds the context, or it resolves a tracked item (`Closes #N`). A CI fix rarely does: `` Fix Windows path assertion in `test_cache_paths` `` is a complete commit message. The case that recurs here is the link: when the red traces to an upstream bug, a dependency release or a linked discussion, put that URL in the body, since it is the only place the next reader will find why the fix looks the way it does. That body is the URL plus at most one clause naming what it holds, and it is capped hard at two lines and 25 words. Never summarize the linked page, and never record what you measured while diagnosing: a failing assertion, a version a probe reported, the flag that turned out to be the cause. Those belong in a code comment beside the fix.
25
31
 
32
+ ### Determine invocation method
33
+
34
+ - If the context above shows `CANONICAL_REPO`, use `uv run --frozen repomatic`: without `--frozen`, an edit to `pyproject.toml` makes the local uv relock `uv.lock`.
35
+ - Otherwise, use `uvx --exclude-newer '{window}' --exclude-newer-package repomatic=P0D --from 'repomatic==X.Y.Z' -- repomatic`, with `X.Y.Z` the `WORKFLOW_PIN` the context shows. Read `{window}` from the `UV_EXCLUDE_NEWER` value of any `.github/workflows/*.yaml`, which `repomatic init` renders from `[tool.repomatic] minimum-release-age`. `--exclude-newer-package` exempts repomatic itself, so a fresh release stays installable while its dependency tree stays gated. The pin keeps the tool registry (`ruff`, `mypy` versions) identical to what CI runs. Drop the `--from` clause only when the context shows no `WORKFLOW_PIN`.
36
+
37
+ References to `<cmd>` below resolve to one or the other.
38
+
26
39
  ### Yield to the orchestrator that spawned you
27
40
 
28
41
  When `/repomatic-ship` or another orchestrator spawns this loop as a sub-agent, it may reach in to claim a specific fix, usually one touching a deliberately-kept structure that needs its own judgment. Honor that at once: a message telling you to **hold, stop, or stand down** on a fix (or on the whole loop) means stop editing the working tree immediately, reply to acknowledge, and neither commit nor push that fix. Mailbox messages are delivered between tool calls, so read yours before every edit and before every commit: a HOLD that landed while you were mid-edit still binds the moment you see it, and you must not race the orchestrator by finishing the edit first. Unless told to stand down entirely, keep polling and reporting the jobs it did not claim, and let it tell you which HEAD to resume on once its fix lands.
@@ -40,7 +53,7 @@ Three feedback channels run in parallel after every push, each at a different la
40
53
  └─ ruff ───┘ │ YAML, secrets, zizmor) │
41
54
  │ │
42
55
  └─ tests.yaml ─────────────────┐ │
43
- (14 stable + 6 unstable) │ │
56
+ (stable + unstable jobs) │ │
44
57
  │ │
45
58
  0:30 GATE 1: local done │ │
46
59
  fail? ─── yes ──► step 5 (fix now, skip CI) │ │
@@ -82,22 +95,26 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
82
95
 
83
96
  Track all five run IDs (`docs.yaml` may have none: its `paths:` filter skips pushes touching nothing docs-relevant). An empty run list for the *other* workflows is not paths-filtering: GitHub can sit on a push event for hours before materializing any run (a 4-hour lag has been observed), so when a freshly pushed SHA shows no runs, keep re-polling instead of concluding the push was filtered, and measure the wait from run creation, not from the push. The `tests.yaml` run exercises the full test matrix; `lint.yaml` runs ruff and mypy over every tracked Python file and lints YAML; `autofix.yaml` runs the mechanical fix jobs (`format-*`, `sync-*`, `update-*`, `fix-typos`, `fix-vulnerable-deps`) and turns red when one *crashes* instead of committing a fix; `docs.yaml` builds and deploys the Sphinx site and runs the broken-links check (an externally cancelled or link-flaky run re-runs cleanly via `gh workflow run docs.yaml --ref <BRANCH>`, no commit needed); `release.yaml` runs the Nuitka binary matrix (dev binaries: an ordinary push rebuilds only the `[tool.repomatic] nuitka.dev-targets` canary subset, while release commits, the weekly `schedule` and `workflow_dispatch` build the full target fleet) — but only on projects with `[tool.repomatic] nuitka.enabled` and a CLI entry point; with Nuitka disabled the per-platform jobs skip on every push, release commits included, and a green `release.yaml` means package build plus dev pre-release sync only. Even with Nuitka enabled, a single push can still skip the matrix: `Metadata.skip_binary_build` (`repomatic/metadata/git.py`) is the authoritative signal, true when the head commit is on a non-code branch, is a user-initiated version-bump commit, or (the common case) its changed files fall entirely outside `Metadata.binary_affecting_paths` — a docs-only commit, say, or a workflow-only one that leaves `release.yaml` and `_release-engine.yaml` alone. `nuitka_matrix` is empty whenever `skip_binary_build` is true. An empty matrix in the logged `metadata=` output of `build / 🧬 Project metadata` does not say which condition fired. Check `skip_binary_build`'s three conditions before asserting why a matrix skipped, since any one of them is enough on its own. All five workflows must pass — see § Autofix job failures and § Nuitka binary build failures in `references/failure-patterns.md` for how to triage them without stalling the loop.
84
97
 
85
- 3. **Run local tests while waiting for CI.** Don't idle while polling. Start the full test suite and linters locally in the background immediately:
98
+ 3. **Run local tests while waiting for CI.** Don't idle while polling. Start the full test suite and linters locally in the background immediately, each through the Bash tool's background mode (`run_in_background: true`):
86
99
 
87
100
  ```shell-session
88
- $ uv run --frozen --all-extras --group test pytest --no-header -q &
89
- $ uv run --group typing repomatic run mypy &
90
- $ uv run repomatic run ruff -- check repomatic tests docs &
101
+ $ uv run --frozen --all-extras --group test pytest --no-header -q
102
+ $ UV_PROJECT_ENVIRONMENT={scratch}/mypy-venv <cmd> run mypy
103
+ $ <cmd> run ruff -- check
91
104
  ```
92
105
 
93
- Give `run mypy` no arguments: the tool runner resolves the same file list CI's `lint.yaml` runs it on, so the two cannot diverge. Naming directories instead is what used to make mypy pass locally and fail in CI.
106
+ Run mypy in an environment synced like CI's lint job, which installs every dependency group. Sync it with `UV_PROJECT_ENVIRONMENT={scratch}/mypy-venv uv sync --frozen --all-extras --all-groups`, with `{scratch}` a directory outside the repository, and sync it again after any change to `uv.lock`. A venv synced with the test groups alone reports each missing type stub as an `import-untyped` error.
107
+
108
+ Never append `&` to one of them instead: a non-interactive shell starts a `&` job with `SIGINT` ignored, which fails every test that expects Python's `KeyboardInterrupt` handler.
109
+
110
+ Give `run mypy` and `run ruff` no paths: the tool runner then checks the same files CI's `lint.yaml` does, so the two cannot diverge. Naming directories instead is what used to make mypy pass locally and fail in CI.
94
111
 
95
112
  **Gate 1 (local, ~30s):** if any local check fails, you already have the diagnosis: skip straight to step 5 without waiting for CI.
96
113
 
97
114
  If local passes, watch CI:
98
115
 
99
116
  ```shell-session
100
- $ uv run repomatic ci-status --branch=<BRANCH> --wait --no-fatal
117
+ $ <cmd> ci-status --branch=<BRANCH> --wait --no-fatal
101
118
  ```
102
119
 
103
120
  It reads every workflow a push can start (derived from `.github/workflows/`, so its list is wider than the five above), polls in-process at `--interval` (60 seconds by default, which keeps the REST quota intact), prints each run whose verdict changed, and returns the moment a required job fails, or once every run settled and the tip has a run of its own. A matrix job whose name still holds its `${{` template never evaluated, and the report says so. Four traps it settles, so no hand-rolled `jq` has to: a run's own `status` lags its jobs (every monitored workflow can read `queued` while a dozen jobs have already finished, which is indistinguishable from the runner-cap saturation a busy account genuinely hits); a `continue-on-error` probe that crashed hides inside a `success` run conclusion; a run whose `conclusion` is `failure` with *no* failed job is a workflow-level error (an invalid `strategy.matrix` expression, malformed YAML, a missing secret) with no job log to read, which the command flags rather than letting you write off a persistently-red workflow as a known artifact; and a run that was cancelled, or that ran no job, has no failed job and still gives its commit no result, so its verdict reads `cancelled` or `skipped`, never `green`.
@@ -117,7 +134,7 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
117
134
  4. **On any CI failure**, cancel the branch's remaining runs to free runners:
118
135
 
119
136
  ```shell-session
120
- $ uv run repomatic cancel-runs --branch=<BRANCH>
137
+ $ <cmd> cancel-runs --branch=<BRANCH>
121
138
  ```
122
139
 
123
140
  The command spares any run whose head commit opens on `[changelog] Release` or `[changelog] Post-release`, the two commits of a release push. The concurrency groups of `release.yaml` and `tests.yaml` apply the same test. Cancelling a release run costs that version its binaries permanently, so never hand-roll the sweep with `gh run cancel`.
@@ -125,7 +142,7 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
125
142
  Then fetch the logs of **all** failed required jobs across the workflows (logs are retained after cancellation):
126
143
 
127
144
  ```shell-session
128
- $ uv run repomatic ci-status --branch=<BRANCH> --no-fatal --failed-logs <DIR>
145
+ $ <cmd> ci-status --branch=<BRANCH> --no-fatal --failed-logs <DIR>
129
146
  ```
130
147
 
131
148
  One file per failed required job, control sequences stripped, readable the moment the job settled: a failed cell is diagnosed twenty minutes into its slowest sibling's build, since the job-scoped log endpoint answers at once where `gh run view --log-failed` waits for the whole run. Fix them as one batch: different sources surface different issues. Batch only what has *already failed*, never what might still fail. Once every harvested failure is root-caused and fixed, push immediately rather than waiting for undrained cells to surface more: the fresh run supersedes the stale one, and serially waiting out each full matrix is the slow path. Analyze following the [error triage discipline](#error-triage-discipline): stable-job `FAILED`/`AssertionError` lines only. Then match each failure against `references/failure-patterns.md` before fixing anything.
@@ -140,9 +157,9 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
140
157
 
141
158
  ```shell-session
142
159
  $ uv run --frozen --all-extras --group test pytest --no-header -q
143
- $ uv run --group typing repomatic run mypy
144
- $ uv run repomatic run ruff -- check repomatic tests docs
145
- $ uv run repomatic run ruff -- format repomatic tests docs
160
+ $ UV_PROJECT_ENVIRONMENT={scratch}/mypy-venv <cmd> run mypy
161
+ $ <cmd> run ruff -- check
162
+ $ <cmd> run ruff -- format
146
163
  ```
147
164
 
148
165
  **Hard gate:** all four must come back clean before step 6. If a fix introduces new failures not in the original set, the fix is wrong: revert it and try a different approach rather than layering another fix on top.
@@ -176,7 +193,7 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
176
193
 
177
194
  ### When supersession never lets a run conclude
178
195
 
179
- A busy default branch can cancel the same workflow indefinitely. Every push shares the `${{ github.workflow }}-${{ github.ref }}` concurrency group, so an unrelated commit landing mid-matrix cancels yours, and the next one cancels its replacement. Only a release push escapes it, in `tests.yaml` and `release.yaml`. Three consecutive heads leaving `tests.yaml` cancelled is an ordinary afternoon, not a fault. Dispatching a fresh run does not escape it: a `workflow_dispatch` run joins the same group and is cancelled by the next push like any other.
196
+ A busy default branch can cancel the same workflow indefinitely. Every push shares the `${{ github.workflow }}-${{ github.ref }}` concurrency group, so an unrelated commit landing mid-matrix cancels yours, and the next one cancels its replacement. Only a release push escapes it, in `tests.yaml` and `release.yaml`. Three consecutive heads leaving `tests.yaml` cancelled is an ordinary afternoon, not a fault. Dispatching a fresh run does not escape it: a `workflow_dispatch` run joins the same group and is cancelled by the next push like any other. A `gh run rerun` of an older run joins it too, and cancels the in-flight run of the current head: re-run only once that run is terminal.
180
197
 
181
198
  A dispatch does settle one case: a version-bump commit, whose subject starts with `[changelog] Bump`, merged right after your push. It cancels your runs, and `tests.yaml` skips the bump commit itself, so `ci-status` reads `cancelled` on your commit. Run `gh workflow run tests.yaml --ref <BRANCH>` once: the dispatched run tests the head, which holds your change.
182
199
 
@@ -44,6 +44,8 @@ Not all CI failures are code bugs:
44
44
  - **A stable job that turns red with no change to the tree or to the runner image**: a setup step met a different outside world, like a package manager that started a cleanup or a migration because its upstream metadata moved. The failing test only shows the symptom. Compare the setup output of the last green job with the red one before you read the test output: a step that prints new lines, or runs in one log only, names the cause. Fix that step. A re-run changes nothing, and a tolerated exit code hides the defect.
45
45
  - **Permission errors**: `Resource not accessible by integration`, 403s. Check `gh api rate_limit` first ([§ GitHub API rate-limit exhaustion](#github-api-rate-limit-exhaustion)), then token permissions; never code.
46
46
  - **A whole workflow red with nothing executed**, every job reporting failure and the `metadata` job unable to resolve its own toolkit pin: the inline `uvx 'repomatic==X.Y.Z'` command is missing `--exclude-newer-package repomatic=P0D`, so the workflow-wide `UV_EXCLUDE_NEWER` refuses a pin naming a release younger than the window, and each `needs: metadata` job dies with it. Splice the flag onto that command line — `uvx` reads no project configuration, so there is nowhere else the bypass can live — or merge the `sync-workflow-pins` PR that backfills it. `lint-repo`'s fatal `self-pin-cooldown-exemption` check names the offending files. Re-running changes nothing.
47
+ - **`ci-status --wait` returning at once, on a red from a commit older than your push**: a workflow whose `paths:` filter skipped your push keeps the verdict of its last run. A red one there blocks every poll, so `--wait` never waits. Triage that red on its own, and watch your push with one `--workflow` per workflow it started, like `--workflow tests.yaml --workflow lint.yaml`.
48
+ - **A red `📦 Package install` whose log shows the published release failing**, like an `ImportError` on a name that a newer dependency release moved: the job installs the latest release from PyPI, never the tree under test, so no commit turns it green and only the next release heals it. Leave it for the release. It also ends every `ci-status --wait` poll at once, as a required job in a workflow your push started: watch the other jobs through `gh api 'repos/<owner>/<repo>/actions/runs/<id>/jobs'` until the release ships.
47
49
  - **A Cloudflare deploy that ends red after publishing**: the `docs.yaml` workflow's `deploy-docs-cloudflare` job dropped a file over 25 MiB, so the live site links to a file it does not have. The offload step's error annotation names each file and the reason. Re-run only when the reason is a failed upload. Any other reason, like an undeclared R2 bucket or missing R2 secrets, needs a repository change or maintainer setup: report it instead.
48
50
 
49
51
  For infrastructure, re-run the failed jobs (`gh run rerun <RUN_ID> --failed`) and continue polling; never modify code to work around transient infra. **A release run is the exception**: when an orchestrator like `/repomatic-ship` spawned this loop, a flake surfaced here is debt owed under that skill's genuinely-green goal, so a red whose defect lives in the repository (the wall-clock budget above, a tolerated-exit set that needs widening) gets fixed at the source instead. "Transient infra" then names the trigger, not the remedy. A red with no repo-side defect at all, like a runner OOM or a PyPI 503, is still a re-run.
@@ -87,7 +89,7 @@ The matrix is slow: let `tests.yaml` and `lint.yaml` set the loop cadence, but a
87
89
 
88
90
  `autofix.yaml`'s jobs normally commit their fixes; a job that *crashes* turns the workflow red without producing one. Fetch the failed log (`gh run view <AUTOFIX_RUN_ID> --log-failed`) and triage:
89
91
 
90
- - **Tool-runner checksum mismatch** (`SHA-256 mismatch for https://...`): the pinned binary's hash no longer matches the published artifact, usually an upstream re-publish. Regenerate with `repomatic update-checksums`, then confirm with `repomatic run <tool>`.
92
+ - **Tool-runner checksum mismatch** (`SHA-256 mismatch for https://...`): the pinned binary's hash no longer matches the published artifact, usually an upstream re-publish. The hashes ship inside the tool registry of repomatic, so only `kdeldycke/repomatic` can fix them. There, regenerate them with `repomatic update-checksums`, then confirm with `repomatic run <tool>`. In any other repository, `update-checksums` rewrites only the installed copy of the registry. Report the mismatch upstream as a blocker: the job stays red until a repomatic release carries the new hashes.
91
93
  - **External-tool output parse error** (a `RuntimeError`/`KeyError` in a parser, like `fix-vulnerable-deps` reading `uv audit` JSON): the tool's output schema drifted. Fix the parser and update the test fixture encoding the old shape.
92
94
  - **Dependency fails to build on the runner** (`Failed to build <pkg>`, a `maturin`/`cargo`/native-compiler error during install): usually self-inflicted, not upstream: a `runs-on` change *this cycle* moved the job to an architecture with no published wheel, forcing a doomed source build. Check `git log <last-tag>..HEAD` for the runner swap and revert it; a genuinely broken upstream artifact (failing on *every* platform) is the rarer case.
93
95
  - **Genuine content the job fixes** (real typos, an actual vulnerability): the job commits the fix and goes green on its own; nothing to do.
@@ -14,7 +14,7 @@ argument-hint: '[audit|init|add <project>|refresh-badges]'
14
14
 
15
15
  !`[ -f docs/benchmark.md ] && grep -c '^|' docs/benchmark.md || echo 0`
16
16
 
17
- !`[ -f CLAUDE.md ] && grep -i 'ordering\|benchmark\|comparison' CLAUDE.md | head -5 || echo "No ordering conventions found"`
17
+ !`[ -f AGENTS.md ] && grep -i 'ordering\|benchmark\|comparison' AGENTS.md | head -5 || echo "No ordering conventions found"`
18
18
 
19
19
  ## Instructions
20
20
 
@@ -36,7 +36,7 @@ Fetch these files as reference when building or auditing a benchmark page:
36
36
 
37
37
  ### Column ordering convention
38
38
 
39
- If `CLAUDE.md` defines a benchmark ordering convention, follow it. Otherwise, place the current project first, its direct dependencies/foundation second, then remaining projects sorted by GitHub stars (descending).
39
+ If `AGENTS.md` defines a benchmark ordering convention, follow it. Otherwise, place the current project first, its direct dependencies/foundation second, then remaining projects sorted by GitHub stars (descending).
40
40
 
41
41
  ### Creating a benchmark from scratch (`init`)
42
42
 
@@ -14,6 +14,8 @@ argument-hint: '[add|check|fix|consolidate [VERSION]|VERSION]'
14
14
 
15
15
  !`[ -f repomatic/__init__.py ] && echo "CANONICAL_REPO" || echo "DOWNSTREAM"`
16
16
 
17
+ !`grep -rhoE 'kdeldycke/repomatic/[^@ ]+@[0-9a-f]{40} # v[0-9.]+' .github/workflows 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+$' | sort -u | sed 's/^/WORKFLOW_PIN=/'`
18
+
17
19
  ## Instructions
18
20
 
19
21
  You help users manage their `changelog.md` file. See § Style rules below for how an entry must read.
@@ -24,9 +26,8 @@ The `changelog.yaml` workflow's `fix-changelog` job runs `lint-changelog --fix`
24
26
 
25
27
  ### Determine invocation method
26
28
 
27
- - If the context above shows `CANONICAL_REPO`, use `uv run repomatic`.
28
- - Otherwise, use `uvx -- repomatic`.
29
- - Gate the `uvx` form with the supply-chain cooldown: `uvx --exclude-newer '{window}' --exclude-newer-package repomatic=P0D -- repomatic`. Read `{window}` from the `UV_EXCLUDE_NEWER` value of any `.github/workflows/*.yaml`, which `repomatic init` renders from `[tool.repomatic] minimum-release-age`. `--exclude-newer-package` exempts repomatic itself, so a fresh release stays installable while its dependency tree stays gated.
29
+ - If the context above shows `CANONICAL_REPO`, use `uv run --frozen repomatic`: without `--frozen`, an edit to `pyproject.toml` makes the local uv relock `uv.lock`.
30
+ - Otherwise, use `uvx --exclude-newer '{window}' --exclude-newer-package repomatic=P0D --from 'repomatic==X.Y.Z' -- repomatic`, with `X.Y.Z` the `WORKFLOW_PIN` the context shows. Read `{window}` from the `UV_EXCLUDE_NEWER` value of any `.github/workflows/*.yaml`, which `repomatic init` renders from `[tool.repomatic] minimum-release-age`. `--exclude-newer-package` exempts repomatic itself, so a fresh release stays installable while its dependency tree stays gated. The pin keeps `lint-changelog` and the bundled `mdformat` identical to the versions CI runs. Drop the `--from` clause only when the context shows no `WORKFLOW_PIN`.
30
31
 
31
32
  ### Argument handling
32
33
 
@@ -16,15 +16,16 @@ argument-hint: '[graph [--level N]|review [all|runtime|dev|policy]|explore [<pac
16
16
 
17
17
  !`[ -f repomatic/__init__.py ] && echo "CANONICAL_REPO" || echo "DOWNSTREAM"`
18
18
 
19
+ !`grep -rhoE 'kdeldycke/repomatic/[^@ ]+@[0-9a-f]{40} # v[0-9.]+' .github/workflows 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+$' | sort -u | sed 's/^/WORKFLOW_PIN=/'`
20
+
19
21
  ## Instructions
20
22
 
21
23
  You help users understand and maintain their project's dependencies. This skill has four modes: **graph** (visualize the resolved dependency tree), **review** (audit `pyproject.toml` declarations against version policy), **explore** (find unused dependency APIs that could simplify existing code), and **modernize** (refactor code to adopt features from recently-upgraded dependencies, applying the changes).
22
24
 
23
25
  ### Determine invocation method
24
26
 
25
- - If the context above shows `CANONICAL_REPO`, use `uv run repomatic`.
26
- - Otherwise, use `uvx -- repomatic`.
27
- - Gate the `uvx` form with the supply-chain cooldown: `uvx --exclude-newer '{window}' --exclude-newer-package repomatic=P0D -- repomatic`. Read `{window}`, here and in every command below, from the `UV_EXCLUDE_NEWER` value of any `.github/workflows/*.yaml`, which `repomatic init` renders from `[tool.repomatic] minimum-release-age`. `--exclude-newer-package` exempts repomatic itself, so a fresh release stays installable while its dependency tree stays gated.
27
+ - If the context above shows `CANONICAL_REPO`, use `uv run --frozen repomatic`: without `--frozen`, an edit to `pyproject.toml` makes the local uv relock `uv.lock`.
28
+ - Otherwise, use `uvx --exclude-newer '{window}' --exclude-newer-package repomatic=P0D --from 'repomatic==X.Y.Z' -- repomatic`, with `X.Y.Z` the `WORKFLOW_PIN` the context shows. Read `{window}`, here and in every command below, from the `UV_EXCLUDE_NEWER` value of any `.github/workflows/*.yaml`, which `repomatic init` renders from `[tool.repomatic] minimum-release-age`. `--exclude-newer-package` exempts repomatic itself, so a fresh release stays installable while its dependency tree stays gated. The pin runs `update-dep-graph` at the version the `update-dep-graph` job runs, so a local graph does not churn against the next CI refresh. Drop the `--from` clause only when the context shows no `WORKFLOW_PIN`.
28
29
 
29
30
  ### Mode selection
30
31
 
@@ -62,7 +63,7 @@ With `[tool.repomatic] dependency-graph.update = false`, the `update-dep-graph`
62
63
 
63
64
  ### Mechanical layer
64
65
 
65
- `<cmd> lint-deps` decides everything readable from `pyproject.toml` alone: upper bounds, missing specifiers, unsorted lists, type stubs outside the `typing` group, floors with no comment above them, and floor comments running past `[tool.repomatic] lint-deps.comment-word-threshold` words (40 by default). Run it first and let it own those rows. CI runs it from the release lane's `lint-deps` job (`_release-build.yaml`, reached through `release.yaml`), which fires on every push but annotates with `--no-fatal` until a release commit makes the *shippability* findings fatal. These policy rows never block either way, so no CI gate will catch them for you.
66
+ `<cmd> lint-deps` decides everything readable from `pyproject.toml` and `uv.lock`: upper bounds, missing specifiers, extras that install nothing, unsorted lists, type stubs outside the `typing` group, floors with no comment above them, and floor comments running past `[tool.repomatic] lint-deps.comment-word-threshold` words (40 by default). Run it first and let it own those rows. CI runs it from the release lane's `lint-deps` job (`_release-build.yaml`, reached through `release.yaml`), which fires on every push but annotates with `--no-fatal` until a release commit makes the blocking *shippability* findings fatal. A floor inside the cooldown blocks only in `[project]` dependencies and extras, which reach the published metadata. In a dependency group, it stays a warning. These policy rows never block either way, so no CI gate will catch them for you.
66
67
 
67
68
  What is left is the part no parser settles, and it is the reason this mode exists: whether a floor is **justified** by the APIs the code actually calls, whether a comment is **stale or weak**, and whether a rationale **contradicts** its conditional marker. Spend the review there.
68
69
 
@@ -128,12 +129,12 @@ These conventions are derived from the `pyproject.toml` files across all `kdeldy
128
129
  #### General rules
129
130
 
130
131
  11. **No upper bounds** (`<`, `<=`, `!=`, `~=` that implies an upper bound). The only exception is conditional markers like `python_version<'3.11'`.
131
- 12. **Extras syntax** is fine: `"coverage[toml]>=7.11"`.
132
+ 12. **Extras syntax** is fine: `"pytest-xdist[psutil]>=3.7"`.
132
133
  13. **One dependency per line** for readable diffs. Short groups that fit on one line are acceptable — the `format-pyproject` job normalizes layout automatically.
133
134
 
134
135
  ### Audit procedure
135
136
 
136
- Read the full `pyproject.toml`. `lint-deps` already reports the specifier style, missing comments, ordering, bare dependencies and misplaced type stubs, so read its output rather than re-deriving them. For each dependency entry, check what it cannot:
137
+ Read the full `pyproject.toml`. `lint-deps` already reports the specifier style, missing comments, ordering, bare dependencies, empty extras and misplaced type stubs, so read its output rather than re-deriving them. For each dependency entry, check what it cannot:
137
138
 
138
139
  | Check | What to flag |
139
140
  | ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
@@ -325,7 +326,7 @@ The usage catalog of step 1 also shows when the project uses a dependency so lit
325
326
  - Failing that, find the last release tag (`git tag --sort=-v:refname | head -1`) and diff the lockfile against it (`git diff <tag> -- uv.lock`), reading the version pairs.
326
327
  - For a single named package, read its locked version and the `pyproject.toml` floor.
327
328
 
328
- 2. **Read each changelog for the delta.** Fetch the release notes covering that version range from the link in the bump table (GitHub releases via `gh api repos/{owner}/{repo}/releases`, or `WebFetch` on the compare URL; the PyPI project page otherwise). Extract only what is **new or changed** in the range: added public APIs, fixed bugs our code works around, and deprecations of APIs we still call. **Degrade gracefully:** if `WebFetch` is unavailable and the package is not on GitHub, fall back to your own knowledge of the library's release history and lower your confidence accordingly.
329
+ 2. **Read each changelog for the delta.** Fetch the release notes covering that version range from the link in the bump table (GitHub releases via `gh api repos/{owner}/{repo}/releases`, or `WebFetch` on the compare URL; the PyPI project page otherwise). A release body that only links to a docs page, as Sphinx's does, has its notes in the repository: read the changelog file at the tag with `gh api 'repos/{owner}/{repo}/contents/{file}?ref={tag}' -H "Accept: application/vnd.github.raw"`. Extract only what is **new or changed** in the range: added public APIs, fixed bugs our code works around, and deprecations of APIs we still call. **Degrade gracefully:** if `WebFetch` is unavailable and the package is not on GitHub, fall back to your own knowledge of the library's release history and lower your confidence accordingly.
329
330
 
330
331
  3. **Map deltas to our code.** For each new or changed item, grep the source tree (not tests) for code it touches, reusing the candidate patterns and false-positive filters from [Explore mode](#explore-mode):
331
332
 
@@ -353,4 +354,4 @@ Suggest the user run:
353
354
 
354
355
  - `/repomatic-deps review all` to audit version floors and specifier policy.
355
356
  - `/repomatic-deps modernize` after a `sync-uv-lock` PR lands, to fold the freshly-upgraded dependencies' new features into the code.
356
- - `/repomatic-audit` for a comprehensive alignment check beyond dependencies.
357
+ - `/repomatic-upgrade` for an alignment check beyond dependencies, in a downstream repository.
@@ -20,7 +20,7 @@ You help users bootstrap a repository to use the reusable GitHub Actions workflo
20
20
 
21
21
  ### Determine invocation method
22
22
 
23
- - If the context above shows `CANONICAL_REPO`, use `uv run repomatic init`.
23
+ - If the context above shows `CANONICAL_REPO`, use `uv run --frozen repomatic init`: without `--frozen`, an edit to `pyproject.toml` makes the local uv relock `uv.lock`.
24
24
  - Otherwise, use `uvx -- repomatic init`.
25
25
  - Gate the `uvx` form with the supply-chain cooldown: `uvx --exclude-newer '{window}' --exclude-newer-package repomatic=P0D -- repomatic`. Read `{window}` from the `UV_EXCLUDE_NEWER` value of any `.github/workflows/*.yaml`, which `repomatic init` renders from `[tool.repomatic] minimum-release-age`. With no workflow yet, read that key from `pyproject.toml`, and ask the user when it is unset. `--exclude-newer-package` exempts repomatic itself, so a fresh release stays installable while its dependency tree stays gated.
26
26
 
@@ -39,4 +39,4 @@ You help users bootstrap a repository to use the reusable GitHub Actions workflo
39
39
 
40
40
  Suggest the user run:
41
41
 
42
- - `/repomatic-audit` to check the generated files against upstream conventions.
42
+ - `/repomatic-upgrade` to check the generated files against upstream conventions.