repomatic 8.2.0__tar.gz → 8.3.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 (711) hide show
  1. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/.claude-plugin/plugin.json +1 -1
  2. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/agents/sphinx-docs.md +1 -0
  3. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.claude}/skills/babysit-ci/SKILL.md +12 -12
  4. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.claude}/skills/babysit-ci/references/failure-patterns.md +2 -0
  5. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.claude}/skills/file-bug-report/SKILL.md +5 -1
  6. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.claude}/skills/probe-workflow/SKILL.md +2 -1
  7. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-ship/SKILL.md +8 -6
  8. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.claude}/skills/repomatic-upgrade/SKILL.md +47 -18
  9. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/upstream-audit/SKILL.md +10 -7
  10. {repomatic-8.2.0 → repomatic-8.3.0}/.claude-plugin/marketplace.json +2 -2
  11. {repomatic-8.2.0 → repomatic-8.3.0}/.github/workflows/_release-build.yaml +4 -4
  12. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/_release-engine.yaml +18 -18
  13. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/autofix.yaml +39 -39
  14. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/autolock.yaml +1 -1
  15. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/cancel-runs.yaml +1 -1
  16. {repomatic-8.2.0 → repomatic-8.3.0}/.github/workflows/changelog.yaml +11 -11
  17. {repomatic-8.2.0 → repomatic-8.3.0}/.github/workflows/debug.yaml +1 -1
  18. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/docs.yaml +8 -7
  19. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/labels.yaml +5 -5
  20. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/lint.yaml +11 -11
  21. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/metrics.yaml +2 -2
  22. {repomatic-8.2.0 → repomatic-8.3.0}/.github/workflows/release.yaml +1 -1
  23. {repomatic-8.2.0 → repomatic-8.3.0}/.github/workflows/self-maintenance.yaml +3 -3
  24. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/tests.yaml +2 -2
  25. {repomatic-8.2.0/repomatic/data → repomatic-8.3.0/.github/workflows}/unsubscribe.yaml +1 -1
  26. {repomatic-8.2.0 → repomatic-8.3.0}/PKG-INFO +2 -2
  27. {repomatic-8.2.0 → repomatic-8.3.0}/changelog.md +32 -0
  28. {repomatic-8.2.0 → repomatic-8.3.0}/docs/agent-skills.md +3 -3
  29. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/binaries.csv +6 -0
  30. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/dependencies.mmd +1 -1
  31. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/help-dark-screen.svg +6 -6
  32. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/help-light-screen.svg +6 -6
  33. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/virustotal-scans.csv +6 -0
  34. {repomatic-8.2.0 → repomatic-8.3.0}/docs/binaries.md +1 -1
  35. {repomatic-8.2.0 → repomatic-8.3.0}/docs/claude-code-plugin.md +4 -4
  36. {repomatic-8.2.0 → repomatic-8.3.0}/docs/conf.py +1 -0
  37. {repomatic-8.2.0 → repomatic-8.3.0}/docs/install.md +6 -6
  38. {repomatic-8.2.0 → repomatic-8.3.0}/docs/operation-contracts.md +1 -1
  39. {repomatic-8.2.0 → repomatic-8.3.0}/docs/security.md +2 -2
  40. {repomatic-8.2.0 → repomatic-8.3.0}/docs/upstream-development.md +1 -1
  41. {repomatic-8.2.0 → repomatic-8.3.0}/docs/upstream.md +3 -6
  42. {repomatic-8.2.0 → repomatic-8.3.0}/docs/workflows.md +7 -6
  43. {repomatic-8.2.0 → repomatic-8.3.0}/pyproject.toml +10 -7
  44. {repomatic-8.2.0 → repomatic-8.3.0}/pyproject.toml.orig +20 -12
  45. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/__init__.py +2 -2
  46. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/ci.py +11 -6
  47. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/github.py +109 -0
  48. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/main.py +1 -0
  49. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/repo.py +14 -11
  50. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/config.py +7 -5
  51. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/_release-engine.yaml +18 -18
  52. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/agent-sphinx-docs.md +1 -0
  53. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/autofix.yaml +39 -39
  54. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/autolock.yaml +1 -1
  55. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/.github/contributing.md +2 -2
  56. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/.github/contributing.zh.md +2 -2
  57. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/cancel-runs.yaml +1 -1
  58. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/changelog.yaml +11 -11
  59. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/debug.yaml +1 -1
  60. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/docs.yaml +8 -7
  61. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/labels.yaml +5 -5
  62. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/lint.yaml +11 -11
  63. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/metrics.yaml +2 -2
  64. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/octicons.toml +1 -0
  65. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/release.yaml +1 -1
  66. {repomatic-8.2.0/.claude → repomatic-8.3.0/repomatic/data}/skills/babysit-ci/SKILL.md +12 -12
  67. {repomatic-8.2.0/.claude → repomatic-8.3.0/repomatic/data}/skills/babysit-ci/references/failure-patterns.md +2 -0
  68. {repomatic-8.2.0/.claude → repomatic-8.3.0/repomatic/data}/skills/file-bug-report/SKILL.md +5 -1
  69. {repomatic-8.2.0/.claude → repomatic-8.3.0/repomatic/data}/skills/probe-workflow/SKILL.md +2 -1
  70. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-ship/SKILL.md +8 -6
  71. {repomatic-8.2.0/.claude → repomatic-8.3.0/repomatic/data}/skills/repomatic-upgrade/SKILL.md +47 -18
  72. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/upstream-audit/SKILL.md +10 -7
  73. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/tests.yaml +2 -2
  74. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/typos.toml +4 -0
  75. {repomatic-8.2.0/.github/workflows → repomatic-8.3.0/repomatic/data}/unsubscribe.yaml +1 -1
  76. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/cooldown.py +37 -13
  77. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/lockfile.py +40 -0
  78. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/provenance.py +48 -22
  79. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/report.py +22 -15
  80. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/git_ops.py +77 -2
  81. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/ci_status.py +116 -16
  82. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/event.py +18 -0
  83. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/issue.py +4 -1
  84. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/outputs.py +8 -0
  85. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/init/local_edits.py +12 -10
  86. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/init/run.py +122 -17
  87. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/init/upgrade.py +45 -24
  88. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/roster.py +20 -1
  89. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/site.py +6 -5
  90. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/tool_config.py +42 -0
  91. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/pypi.py +103 -41
  92. repomatic-8.3.0/repomatic/templates/upgrade-invite.md +12 -0
  93. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/tooling/registry.py +13 -13
  94. {repomatic-8.2.0 → repomatic-8.3.0}/tests/cli-test-suite.toml +6 -0
  95. {repomatic-8.2.0 → repomatic-8.3.0}/tests/conftest.py +12 -0
  96. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_awesome_template.py +29 -0
  97. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_broken_links.py +0 -1
  98. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_ci_status.py +137 -3
  99. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_cli.py +0 -4
  100. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_event.py +31 -0
  101. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_git_ops.py +54 -0
  102. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_init_project.py +269 -3
  103. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_issue.py +94 -0
  104. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_labels.py +45 -2
  105. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_lint_repo.py +43 -2
  106. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_metadata.py +0 -5
  107. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_provenance.py +237 -53
  108. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_uv.py +79 -28
  109. {repomatic-8.2.0 → repomatic-8.3.0}/uv.lock +24 -24
  110. repomatic-8.2.0/repomatic/templates/upgrade-invite.md +0 -12
  111. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/agents/grunt-qa.md +0 -0
  112. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/agents/qa-engineer.md +0 -0
  113. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/av-false-positive/SKILL.md +0 -0
  114. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/awesome-triage/SKILL.md +0 -0
  115. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/benchmark-update/SKILL.md +0 -0
  116. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/brand-assets/SKILL.md +0 -0
  117. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/github-housekeeping/SKILL.md +0 -0
  118. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-changelog/SKILL.md +0 -0
  119. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-deps/SKILL.md +0 -0
  120. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-init/SKILL.md +0 -0
  121. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-ship/references/deep-pass.md +0 -0
  122. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-ship/references/findings-in-repomatic.md +0 -0
  123. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-ship/references/short-ship.md +0 -0
  124. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-test-matrix/SKILL.md +0 -0
  125. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/repomatic-topics/SKILL.md +0 -0
  126. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/sphinx-docs-sync/SKILL.md +0 -0
  127. {repomatic-8.2.0 → repomatic-8.3.0}/.claude/skills/translation-sync/SKILL.md +0 -0
  128. {repomatic-8.2.0 → repomatic-8.3.0}/.github/ISSUE_TEMPLATE/bug-report.yml +0 -0
  129. {repomatic-8.2.0 → repomatic-8.3.0}/.github/actions/publish-pypi/action.yaml +0 -0
  130. {repomatic-8.2.0 → repomatic-8.3.0}/.github/code-of-conduct.md +0 -0
  131. {repomatic-8.2.0 → repomatic-8.3.0}/.github/funding.yml +0 -0
  132. {repomatic-8.2.0 → repomatic-8.3.0}/.gitignore +0 -0
  133. {repomatic-8.2.0 → repomatic-8.3.0}/.mailmap +0 -0
  134. {repomatic-8.2.0 → repomatic-8.3.0}/AGENTS.md +0 -0
  135. {repomatic-8.2.0 → repomatic-8.3.0}/docs/404.html +0 -0
  136. {repomatic-8.2.0 → repomatic-8.3.0}/docs/_redirects +0 -0
  137. {repomatic-8.2.0 → repomatic-8.3.0}/docs/_static/custom.css +0 -0
  138. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/banner-social-dark.png +0 -0
  139. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/banner-social-light.png +0 -0
  140. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/banner-social.svg +0 -0
  141. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/config-snippet-screen.svg +0 -0
  142. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/desktop-autosync-warning.png +0 -0
  143. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/desktop-plugin-agents.png +0 -0
  144. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/desktop-plugin-contents.png +0 -0
  145. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/desktop-plugin-skills.png +0 -0
  146. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/favicon.svg +0 -0
  147. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/icon.icns +0 -0
  148. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/icon.ico +0 -0
  149. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/icon.png +0 -0
  150. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/logo-banner-dark.png +0 -0
  151. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/logo-banner-light.png +0 -0
  152. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/logo-banner.svg +0 -0
  153. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/logo-square-dark.png +0 -0
  154. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/logo-square-light.png +0 -0
  155. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/logo-square.svg +0 -0
  156. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/matrix-grid-screen.svg +0 -0
  157. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/metrics.csv +0 -0
  158. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/star-history-compared.svg +0 -0
  159. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/star-history.svg +0 -0
  160. {repomatic-8.2.0 → repomatic-8.3.0}/docs/assets/sync-deps-trail-screen.svg +0 -0
  161. {repomatic-8.2.0 → repomatic-8.3.0}/docs/benchmark.md +0 -0
  162. {repomatic-8.2.0 → repomatic-8.3.0}/docs/changelog-archive.md +0 -0
  163. {repomatic-8.2.0 → repomatic-8.3.0}/docs/changelog.md +0 -0
  164. {repomatic-8.2.0 → repomatic-8.3.0}/docs/cli.md +0 -0
  165. {repomatic-8.2.0 → repomatic-8.3.0}/docs/cloudflare.md +0 -0
  166. {repomatic-8.2.0 → repomatic-8.3.0}/docs/code-of-conduct.md +0 -0
  167. {repomatic-8.2.0 → repomatic-8.3.0}/docs/commit-messages.md +0 -0
  168. {repomatic-8.2.0 → repomatic-8.3.0}/docs/configuration.md +0 -0
  169. {repomatic-8.2.0 → repomatic-8.3.0}/docs/contributing.md +0 -0
  170. {repomatic-8.2.0 → repomatic-8.3.0}/docs/dependencies.md +0 -0
  171. {repomatic-8.2.0 → repomatic-8.3.0}/docs/docs_update.py +0 -0
  172. {repomatic-8.2.0 → repomatic-8.3.0}/docs/history.md +0 -0
  173. {repomatic-8.2.0 → repomatic-8.3.0}/docs/index.md +0 -0
  174. {repomatic-8.2.0 → repomatic-8.3.0}/docs/license.md +0 -0
  175. {repomatic-8.2.0 → repomatic-8.3.0}/docs/man.md +0 -0
  176. {repomatic-8.2.0 → repomatic-8.3.0}/docs/nuitka.md +0 -0
  177. {repomatic-8.2.0 → repomatic-8.3.0}/docs/packaging.md +0 -0
  178. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.awesome_toc.md +0 -0
  179. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.broken_links.md +0 -0
  180. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.bundle.md +0 -0
  181. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cache.md +0 -0
  182. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.changelog.md +0 -0
  183. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.checks.md +0 -0
  184. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.claude_plugin.md +0 -0
  185. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.ci.md +0 -0
  186. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.deps.md +0 -0
  187. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.github.md +0 -0
  188. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.main.md +0 -0
  189. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.md +0 -0
  190. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.release.md +0 -0
  191. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.repo.md +0 -0
  192. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.site.md +0 -0
  193. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cli.tools.md +0 -0
  194. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cloudflare.api.md +0 -0
  195. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cloudflare.md +0 -0
  196. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cloudflare.pages.md +0 -0
  197. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cloudflare.r2.md +0 -0
  198. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.cloudflare.redirects.md +0 -0
  199. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.components.md +0 -0
  200. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.config.md +0 -0
  201. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.data.awesome_template.md +0 -0
  202. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.data.md +0 -0
  203. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.audit.md +0 -0
  204. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.cooldown.md +0 -0
  205. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.graph.md +0 -0
  206. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.lockfile.md +0 -0
  207. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.md +0 -0
  208. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.pins.md +0 -0
  209. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.policy.md +0 -0
  210. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.provenance.md +0 -0
  211. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.report.md +0 -0
  212. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.requirements.md +0 -0
  213. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.shippable.md +0 -0
  214. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.sources.md +0 -0
  215. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.sync.md +0 -0
  216. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.deps.uv.md +0 -0
  217. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.docs.md +0 -0
  218. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.file_inventory.md +0 -0
  219. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.file_ops.md +0 -0
  220. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.frontmatter.md +0 -0
  221. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.git_ops.md +0 -0
  222. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.caches.md +0 -0
  223. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.ci_status.md +0 -0
  224. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.dev_release.md +0 -0
  225. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.event.md +0 -0
  226. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.gh.md +0 -0
  227. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.issue.md +0 -0
  228. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.job_timings.md +0 -0
  229. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.labels.md +0 -0
  230. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.md +0 -0
  231. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.outputs.md +0 -0
  232. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.pr.md +0 -0
  233. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.pr_body.md +0 -0
  234. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.release_sync.md +0 -0
  235. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.releases.md +0 -0
  236. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.runs.md +0 -0
  237. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.sponsor.md +0 -0
  238. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.status.md +0 -0
  239. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.threads.md +0 -0
  240. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.token.md +0 -0
  241. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.unsubscribe.md +0 -0
  242. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.urls.md +0 -0
  243. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.workflow_files.md +0 -0
  244. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.github.workflow_sync.md +0 -0
  245. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.gitignore.md +0 -0
  246. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.hashing.md +0 -0
  247. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.http.md +0 -0
  248. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.humanize.md +0 -0
  249. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.images.md +0 -0
  250. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.init.local_edits.md +0 -0
  251. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.init.md +0 -0
  252. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.init.removed_assets.md +0 -0
  253. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.init.run.md +0 -0
  254. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.init.tool_config.md +0 -0
  255. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.init.upgrade.md +0 -0
  256. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_changelog.md +0 -0
  257. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.context.md +0 -0
  258. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.md +0 -0
  259. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.pins.md +0 -0
  260. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.repo.md +0 -0
  261. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.roster.md +0 -0
  262. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.settings.md +0 -0
  263. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.site.md +0 -0
  264. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.tool_config.md +0 -0
  265. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.lint_repo.workflows.md +0 -0
  266. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.mailmap.md +0 -0
  267. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.markdown.md +0 -0
  268. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.matrix.axes.md +0 -0
  269. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.matrix.md +0 -0
  270. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.matrix.model.md +0 -0
  271. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.matrix.runner_sync.md +0 -0
  272. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.matrix.runners.md +0 -0
  273. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.md +0 -0
  274. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metadata.core.md +0 -0
  275. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metadata.env.md +0 -0
  276. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metadata.git.md +0 -0
  277. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metadata.matrix.md +0 -0
  278. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metadata.md +0 -0
  279. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metadata.output.md +0 -0
  280. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metadata.project.md +0 -0
  281. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metrics.chart.md +0 -0
  282. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metrics.forge.md +0 -0
  283. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metrics.md +0 -0
  284. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.metrics.store.md +0 -0
  285. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.npm.md +0 -0
  286. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.pypi.md +0 -0
  287. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.pyproject.md +0 -0
  288. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.attestation.md +0 -0
  289. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.binaries_page.md +0 -0
  290. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.binary.md +0 -0
  291. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.manpages.md +0 -0
  292. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.md +0 -0
  293. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.prepare_release.md +0 -0
  294. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.protocol.md +0 -0
  295. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.self_pin.md +0 -0
  296. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.verify.md +0 -0
  297. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.release.virustotal.md +0 -0
  298. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.setup_guide.md +0 -0
  299. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.skills.md +0 -0
  300. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.tabular.md +0 -0
  301. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.templates.md +0 -0
  302. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.templating.md +0 -0
  303. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.tooling.binaries.md +0 -0
  304. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.tooling.checksums.md +0 -0
  305. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.tooling.md +0 -0
  306. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.tooling.nuitka.md +0 -0
  307. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.tooling.registry.md +0 -0
  308. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.tooling.runner.md +0 -0
  309. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.upstream.md +0 -0
  310. {repomatic-8.2.0 → repomatic-8.3.0}/docs/repomatic.versions.md +0 -0
  311. {repomatic-8.2.0 → repomatic-8.3.0}/docs/robots.txt +0 -0
  312. {repomatic-8.2.0 → repomatic-8.3.0}/docs/subagent-grunt-qa.md +0 -0
  313. {repomatic-8.2.0 → repomatic-8.3.0}/docs/subagent-qa-engineer.md +0 -0
  314. {repomatic-8.2.0 → repomatic-8.3.0}/docs/subagent-sphinx-docs.md +0 -0
  315. {repomatic-8.2.0 → repomatic-8.3.0}/docs/subagents.md +0 -0
  316. {repomatic-8.2.0 → repomatic-8.3.0}/docs/test-matrix.md +0 -0
  317. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.conftest.md +0 -0
  318. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.md +0 -0
  319. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_attestation.md +0 -0
  320. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_awesome_template.md +0 -0
  321. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_awesome_toc.md +0 -0
  322. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_binaries.md +0 -0
  323. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_binaries_page.md +0 -0
  324. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_binary.md +0 -0
  325. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_broken_links.md +0 -0
  326. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_cache.md +0 -0
  327. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_changelog.md +0 -0
  328. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_checks.md +0 -0
  329. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_checksums.md +0 -0
  330. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_ci_status.md +0 -0
  331. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_claude_assets.md +0 -0
  332. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_cli.md +0 -0
  333. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_cloudflare.md +0 -0
  334. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_cloudflare_r2.md +0 -0
  335. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_config.md +0 -0
  336. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_coverage_floor.md +0 -0
  337. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_dep_graph.md +0 -0
  338. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_dep_policy.md +0 -0
  339. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_dep_report.md +0 -0
  340. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_dep_sources.md +0 -0
  341. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_dev_release.md +0 -0
  342. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_docs.md +0 -0
  343. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_docstrings.md +0 -0
  344. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_event.md +0 -0
  345. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_file_ops.md +0 -0
  346. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_forge.md +0 -0
  347. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_frontmatter.md +0 -0
  348. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_gh.md +0 -0
  349. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_git_ops.md +0 -0
  350. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_github_caches.md +0 -0
  351. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_gitignore.md +0 -0
  352. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_hashing.md +0 -0
  353. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_help.md +0 -0
  354. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_http.md +0 -0
  355. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_humanize.md +0 -0
  356. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_images.md +0 -0
  357. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_imports.md +0 -0
  358. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_init_project.md +0 -0
  359. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_issue.md +0 -0
  360. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_job_timings.md +0 -0
  361. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_labels.md +0 -0
  362. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_lint_changelog.md +0 -0
  363. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_lint_repo.md +0 -0
  364. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_mailmap.md +0 -0
  365. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_manpages.md +0 -0
  366. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_markdown.md +0 -0
  367. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_matrix.md +0 -0
  368. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_metadata.md +0 -0
  369. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_metadata_git.md +0 -0
  370. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_metrics.md +0 -0
  371. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_npm.md +0 -0
  372. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_nuitka.md +0 -0
  373. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_outputs.md +0 -0
  374. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_pages_redirects.md +0 -0
  375. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_platform_keys.md +0 -0
  376. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_plugin.md +0 -0
  377. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_plugin_update_detection.md +0 -0
  378. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_pr.md +0 -0
  379. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_pr_body.md +0 -0
  380. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_prepare_release.md +0 -0
  381. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_protocol.md +0 -0
  382. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_provenance.md +0 -0
  383. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_pypi.md +0 -0
  384. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_pyproject.md +0 -0
  385. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_readme.md +0 -0
  386. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_release_sync.md +0 -0
  387. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_release_workflow_steps.md +0 -0
  388. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_releases.md +0 -0
  389. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_runner_catalog.md +0 -0
  390. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_runner_sync.md +0 -0
  391. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_runs.md +0 -0
  392. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_self_pin.md +0 -0
  393. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_setup_guide.md +0 -0
  394. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_skills.md +0 -0
  395. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_sphinx_crossrefs.md +0 -0
  396. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_sponsor.md +0 -0
  397. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_status.md +0 -0
  398. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_suite_hygiene.md +0 -0
  399. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_sync_ops.md +0 -0
  400. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_tabular.md +0 -0
  401. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_templating.md +0 -0
  402. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_threads.md +0 -0
  403. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_todolist.md +0 -0
  404. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_token.md +0 -0
  405. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_tool_runner.md +0 -0
  406. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_unsubscribe.md +0 -0
  407. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_upstream.md +0 -0
  408. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_urls.md +0 -0
  409. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_uv.md +0 -0
  410. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_verify.md +0 -0
  411. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_version_sync.md +0 -0
  412. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_versions.md +0 -0
  413. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_virustotal.md +0 -0
  414. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_vulnerable_deps.md +0 -0
  415. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_workflow_files.md +0 -0
  416. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_workflow_sync.md +0 -0
  417. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tests.test_workflows.md +0 -0
  418. {repomatic-8.2.0 → repomatic-8.3.0}/docs/todolist.md +0 -0
  419. {repomatic-8.2.0 → repomatic-8.3.0}/docs/tool-runner.md +0 -0
  420. {repomatic-8.2.0 → repomatic-8.3.0}/license +0 -0
  421. {repomatic-8.2.0 → repomatic-8.3.0}/readme.md +0 -0
  422. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/__main__.py +0 -0
  423. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/awesome_toc.py +0 -0
  424. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/broken_links.py +0 -0
  425. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/bundle.py +0 -0
  426. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cache.py +0 -0
  427. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/changelog.py +0 -0
  428. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/checks.py +0 -0
  429. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/claude_plugin.py +0 -0
  430. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/__init__.py +0 -0
  431. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/deps.py +0 -0
  432. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/release.py +0 -0
  433. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/site.py +0 -0
  434. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cli/tools.py +0 -0
  435. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cloudflare/__init__.py +0 -0
  436. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cloudflare/api.py +0 -0
  437. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cloudflare/pages.py +0 -0
  438. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cloudflare/r2.py +0 -0
  439. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/cloudflare/redirects.py +0 -0
  440. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/components.py +0 -0
  441. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/__init__.py +0 -0
  442. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/action-publish-pypi.yaml +0 -0
  443. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/actionlint-matcher.json +0 -0
  444. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/actionlint.yaml +0 -0
  445. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/agent-grunt-qa.md +0 -0
  446. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/agent-qa-engineer.md +0 -0
  447. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/.github/ISSUE_TEMPLATE/config.yml +0 -0
  448. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/.github/ISSUE_TEMPLATE/new-link.yaml +0 -0
  449. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/.github/code-of-conduct.md +0 -0
  450. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/.github/funding.yml +0 -0
  451. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/.github/pull_request_template.md +0 -0
  452. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/__init__.py +0 -0
  453. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/awesome_template/license +0 -0
  454. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/bumpversion.toml +0 -0
  455. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/coverage.toml +0 -0
  456. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/labels.toml +0 -0
  457. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/lychee.toml +0 -0
  458. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/mdformat.toml +0 -0
  459. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/mypy.toml +0 -0
  460. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/pytest.toml +0 -0
  461. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/ruff.toml +0 -0
  462. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/av-false-positive/SKILL.md +0 -0
  463. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/awesome-triage/SKILL.md +0 -0
  464. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/benchmark-update/SKILL.md +0 -0
  465. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/brand-assets/SKILL.md +0 -0
  466. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/github-housekeeping/SKILL.md +0 -0
  467. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-changelog/SKILL.md +0 -0
  468. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-deps/SKILL.md +0 -0
  469. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-init/SKILL.md +0 -0
  470. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-ship/references/deep-pass.md +0 -0
  471. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-ship/references/findings-in-repomatic.md +0 -0
  472. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-ship/references/short-ship.md +0 -0
  473. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-test-matrix/SKILL.md +0 -0
  474. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/repomatic-topics/SKILL.md +0 -0
  475. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/sphinx-docs-sync/SKILL.md +0 -0
  476. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/skills/translation-sync/SKILL.md +0 -0
  477. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/uv.toml +0 -0
  478. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/vt-trend-chart.js +0 -0
  479. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/yamllint.yaml +0 -0
  480. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/data/zizmor.yaml +0 -0
  481. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/__init__.py +0 -0
  482. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/audit.py +0 -0
  483. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/graph.py +0 -0
  484. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/pins.py +0 -0
  485. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/policy.py +0 -0
  486. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/requirements.py +0 -0
  487. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/shippable.py +0 -0
  488. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/sources.py +0 -0
  489. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/sync.py +0 -0
  490. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/deps/uv.py +0 -0
  491. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/docs.py +0 -0
  492. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/file_inventory.py +0 -0
  493. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/file_ops.py +0 -0
  494. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/frontmatter.py +0 -0
  495. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/__init__.py +0 -0
  496. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/caches.py +0 -0
  497. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/dev_release.py +0 -0
  498. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/gh.py +0 -0
  499. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/job_timings.py +0 -0
  500. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/labels.py +0 -0
  501. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/pr.py +0 -0
  502. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/pr_body.py +0 -0
  503. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/release_sync.py +0 -0
  504. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/releases.py +0 -0
  505. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/runs.py +0 -0
  506. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/sponsor.py +0 -0
  507. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/status.py +0 -0
  508. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/threads.py +0 -0
  509. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/token.py +0 -0
  510. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/unsubscribe.py +0 -0
  511. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/urls.py +0 -0
  512. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/workflow_files.py +0 -0
  513. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/github/workflow_sync.py +0 -0
  514. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/gitignore.py +0 -0
  515. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/hashing.py +0 -0
  516. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/http.py +0 -0
  517. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/humanize.py +0 -0
  518. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/images.py +0 -0
  519. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/init/__init__.py +0 -0
  520. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/init/removed_assets.py +0 -0
  521. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/init/tool_config.py +0 -0
  522. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_changelog.py +0 -0
  523. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/__init__.py +0 -0
  524. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/context.py +0 -0
  525. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/pins.py +0 -0
  526. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/repo.py +0 -0
  527. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/settings.py +0 -0
  528. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/lint_repo/workflows.py +0 -0
  529. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/mailmap.py +0 -0
  530. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/markdown.py +0 -0
  531. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/matrix/__init__.py +0 -0
  532. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/matrix/axes.py +0 -0
  533. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/matrix/model.py +0 -0
  534. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/matrix/runner_sync.py +0 -0
  535. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/matrix/runners.py +0 -0
  536. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metadata/__init__.py +0 -0
  537. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metadata/core.py +0 -0
  538. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metadata/env.py +0 -0
  539. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metadata/git.py +0 -0
  540. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metadata/matrix.py +0 -0
  541. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metadata/output.py +0 -0
  542. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metadata/project.py +0 -0
  543. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metrics/__init__.py +0 -0
  544. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metrics/chart.py +0 -0
  545. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metrics/forge.py +0 -0
  546. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/metrics/store.py +0 -0
  547. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/npm.py +0 -0
  548. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/py.typed +0 -0
  549. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/pyproject.py +0 -0
  550. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/__init__.py +0 -0
  551. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/attestation.py +0 -0
  552. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/binaries_page.py +0 -0
  553. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/binary.py +0 -0
  554. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/manpages.py +0 -0
  555. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/prepare_release.py +0 -0
  556. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/protocol.py +0 -0
  557. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/self_pin.py +0 -0
  558. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/verify.py +0 -0
  559. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/release/virustotal.py +0 -0
  560. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/setup_guide.py +0 -0
  561. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/skills.py +0 -0
  562. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/tabular.py +0 -0
  563. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/__init__.py +0 -0
  564. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/available-admonition.md +0 -0
  565. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/broken-links-issue.md +0 -0
  566. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/bump-version.md +0 -0
  567. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/development-warning.md +0 -0
  568. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/fix-changelog.md +0 -0
  569. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/fix-typos.md +0 -0
  570. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/fix-vulnerable-deps.md +0 -0
  571. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/format-images.md +0 -0
  572. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/format-json.md +0 -0
  573. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/format-markdown.md +0 -0
  574. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/format-pyproject.md +0 -0
  575. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/format-python.md +0 -0
  576. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/format-shell.md +0 -0
  577. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/generated-footer.md +0 -0
  578. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/github-releases.md +0 -0
  579. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/immutable-releases.md +0 -0
  580. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/pr-metadata.md.noformat +0 -0
  581. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/prepare-release.md.noformat +0 -0
  582. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/refresh-tip.md +0 -0
  583. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/release-notes.md +0 -0
  584. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/release-sync-report.md.noformat +0 -0
  585. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sample-metrics.md +0 -0
  586. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/scan-virustotal.md +0 -0
  587. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-branch-ruleset.md +0 -0
  588. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-cloudflare-pages.md +0 -0
  589. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-cloudflare-r2.md +0 -0
  590. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-dependabot.md +0 -0
  591. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-fork-pr-approval.md +0 -0
  592. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-notifications-pat.md +0 -0
  593. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-pages-source.md +0 -0
  594. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-pypi-trusted-publisher.md +0 -0
  595. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-sha-pinning-required.md +0 -0
  596. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-token.md +0 -0
  597. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-verify.md +0 -0
  598. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide-virustotal.md +0 -0
  599. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/setup-guide.md +0 -0
  600. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/squashed-release.md +0 -0
  601. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-action-pins.md +0 -0
  602. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-bumpversion.md +0 -0
  603. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-dep-sources.md +0 -0
  604. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-gitignore.md +0 -0
  605. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-mailmap.md +0 -0
  606. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-repomatic-upgrade.md +0 -0
  607. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-repomatic.md +0 -0
  608. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-runner-images.md +0 -0
  609. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-tool-versions.md +0 -0
  610. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-uv-lock.md +0 -0
  611. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/sync-workflow-pins.md +0 -0
  612. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/unavailable-admonition.md +0 -0
  613. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/unsubscribe-report.md +0 -0
  614. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/update-dep-graph.md +0 -0
  615. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/update-docs.md +0 -0
  616. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templates/yanked-admonition.md +0 -0
  617. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/templating.py +0 -0
  618. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/tooling/__init__.py +0 -0
  619. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/tooling/binaries.py +0 -0
  620. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/tooling/checksums.py +0 -0
  621. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/tooling/nuitka.py +0 -0
  622. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/tooling/runner.py +0 -0
  623. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/upstream.py +0 -0
  624. {repomatic-8.2.0 → repomatic-8.3.0}/repomatic/versions.py +0 -0
  625. {repomatic-8.2.0 → repomatic-8.3.0}/tests/__init__.py +0 -0
  626. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_attestation.py +0 -0
  627. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_awesome_toc.py +0 -0
  628. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_binaries.py +0 -0
  629. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_binaries_page.py +0 -0
  630. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_binary.py +0 -0
  631. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_cache.py +0 -0
  632. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_changelog.py +0 -0
  633. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_checks.py +0 -0
  634. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_checksums.py +0 -0
  635. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_claude_assets.py +0 -0
  636. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_cloudflare.py +0 -0
  637. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_cloudflare_r2.py +0 -0
  638. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_config.py +0 -0
  639. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_coverage_floor.py +0 -0
  640. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_dep_graph.py +0 -0
  641. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_dep_policy.py +0 -0
  642. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_dep_report.py +0 -0
  643. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_dep_sources.py +0 -0
  644. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_dev_release.py +0 -0
  645. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_docs.py +0 -0
  646. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_docstrings.py +0 -0
  647. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_file_ops.py +0 -0
  648. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_forge.py +0 -0
  649. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_frontmatter.py +0 -0
  650. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_gh.py +0 -0
  651. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_github_caches.py +0 -0
  652. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_gitignore.py +0 -0
  653. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_hashing.py +0 -0
  654. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_help.py +0 -0
  655. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_http.py +0 -0
  656. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_humanize.py +0 -0
  657. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_images.py +0 -0
  658. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_imports.py +0 -0
  659. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_job_timings.py +0 -0
  660. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_lint_changelog.py +0 -0
  661. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_mailmap.py +0 -0
  662. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_manpages.py +0 -0
  663. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_markdown.py +0 -0
  664. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_matrix.py +0 -0
  665. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_metadata_git.py +0 -0
  666. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_metrics.py +0 -0
  667. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_npm.py +0 -0
  668. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_nuitka.py +0 -0
  669. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_outputs.py +0 -0
  670. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_pages_redirects.py +0 -0
  671. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_platform_keys.py +0 -0
  672. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_plugin.py +0 -0
  673. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_plugin_update_detection.py +0 -0
  674. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_pr.py +0 -0
  675. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_pr_body.py +0 -0
  676. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_prepare_release.py +0 -0
  677. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_protocol.py +0 -0
  678. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_pypi.py +0 -0
  679. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_pyproject.py +0 -0
  680. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_readme.py +0 -0
  681. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_release_sync.py +0 -0
  682. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_release_workflow_steps.py +0 -0
  683. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_releases.py +0 -0
  684. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_runner_catalog.py +0 -0
  685. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_runner_sync.py +0 -0
  686. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_runs.py +0 -0
  687. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_self_pin.py +0 -0
  688. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_setup_guide.py +0 -0
  689. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_skills.py +0 -0
  690. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_sphinx_crossrefs.py +0 -0
  691. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_sponsor.py +0 -0
  692. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_status.py +0 -0
  693. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_suite_hygiene.py +0 -0
  694. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_sync_ops.py +0 -0
  695. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_tabular.py +0 -0
  696. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_templating.py +0 -0
  697. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_threads.py +0 -0
  698. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_todolist.py +0 -0
  699. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_token.py +0 -0
  700. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_tool_runner.py +0 -0
  701. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_unsubscribe.py +0 -0
  702. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_upstream.py +0 -0
  703. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_urls.py +0 -0
  704. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_verify.py +0 -0
  705. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_version_sync.py +0 -0
  706. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_versions.py +0 -0
  707. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_virustotal.py +0 -0
  708. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_vulnerable_deps.py +0 -0
  709. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_workflow_files.py +0 -0
  710. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_workflow_sync.py +0 -0
  711. {repomatic-8.2.0 → repomatic-8.3.0}/tests/test_workflows.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.2.0"
23
+ "version": "8.3.0"
24
24
  }
@@ -605,6 +605,7 @@ Every top-level page heading uses an `{octicon}` icon for visual scanning: `` #
605
605
  | {octicon}`globe` `globe` | `infrastructure.md` |
606
606
  | {octicon}`history` `history` | `changelog-archive.md`, `cooldown.md` |
607
607
  | {octicon}`image` `image` | `snippets.md` |
608
+ | {octicon}`inbox` `inbox` | `formats.md` |
608
609
  | {octicon}`iterations` `iterations` | `version.md` |
609
610
  | {octicon}`key` `key` | `sudo.md` |
610
611
  | {octicon}`law` `law` | `license.md` |
@@ -117,7 +117,7 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
117
117
  $ <cmd> ci-status --branch=<BRANCH> --wait --no-fatal
118
118
  ```
119
119
 
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`.
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), and prints each run whose verdict changed. It returns on the first run that blocks a merge, like one with a failed or cancelled required job, 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, unless a required job in it was cancelled, like one no runner picked up, which the command names instead; 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`, while a cancelled required job in a run on the tip blocks, since no newer push stopped it.
121
121
 
122
122
  `ci-status` reads runs through the same `head_sha` endpoint, commit by commit back from the branch tip, and says when the tip has no run yet. A workflow that ran no job on the tip, like `tests.yaml` on a version-bump commit, is read on an earlier commit, and the command names it. A `cancelled` or `skipped` verdict is not a pass: see [§ When supersession never lets a run conclude](#when-supersession-never-lets-a-run-conclude). A workflow with no run on the newest commits falls back to its own run listing, filtered by creation date. Re-read a surprising red or green once before acting on it.
123
123
 
@@ -131,15 +131,7 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
131
131
 
132
132
  **Never hand-roll a poll loop around `gh`.** A loop with no delay fires thousands of requests per minute and exhausts the REST quota (5,000/hour) within minutes. Exhaustion does not just blind your own polling: workflows authenticating with the same PAT start failing server-side with misleading errors (see [§ GitHub API rate-limit exhaustion](references/failure-patterns.md#github-api-rate-limit-exhaustion)).
133
133
 
134
- 4. **On any CI failure**, cancel the branch's remaining runs to free runners:
135
-
136
- ```shell-session
137
- $ <cmd> cancel-runs --branch=<BRANCH>
138
- ```
139
-
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`.
141
-
142
- Then fetch the logs of **all** failed required jobs across the workflows (logs are retained after cancellation):
134
+ 4. **On any CI failure**, fetch the logs of **all** failed required jobs across the workflows:
143
135
 
144
136
  ```shell-session
145
137
  $ <cmd> ci-status --branch=<BRANCH> --no-fatal --failed-logs <DIR>
@@ -147,7 +139,7 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
147
139
 
148
140
  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.
149
141
 
150
- So the diagnosis is minutes away, not an hour: harvest every failed cell as it lands and keep the run alive for the cells still to report. Cancelling to read logs is never the reason: logs survive cancellation, but they never needed it. **Make the run terminal only when you have a fix**, per the batch-and-push rule above: the stale run has no verification value left once superseded.
142
+ So the diagnosis is minutes away, not an hour: harvest every failed cell as it lands and keep the run alive for the cells still to report. Cancelling to read logs is never the reason: logs survive cancellation, but they never needed it. **Make the run terminal only when you have a fix**: step 7 cancels it right before the push, since the stale run has no verification value left once superseded.
151
143
 
152
144
  5. **Fix the root cause** using the combined picture from CI logs and local results. Fix the codebase, not the tests, unless the tests are genuinely wrong. Address mypy and ruff failures together (see [§ mypy/ruff fix oscillation](references/failure-patterns.md#mypy-ruff-fix-oscillation)).
153
145
 
@@ -175,7 +167,15 @@ After fixing (step 5-7), the loop restarts from the top: push, run all three cha
175
167
 
176
168
  If any open autofix PR already contains your fix — a `format-python` branch (ruff's own autofixes), a `sync-repomatic`/`sync-workflow-pins` branch (a bumped workflow pin, or a spliced-in `--exclude-newer-package repomatic=P0D` cooldown exemption carrying no version bump at all — that one is the whole fix when the `metadata` job cannot resolve its own pin), or another `sync-*`/`fix-*` branch — prefer merging it over authoring your own commit: GitHub signs the merge commit server-side, so this sidesteps a local hardware-key signing prompt entirely. If it resolves the failure, merge it (`gh pr merge <n> --squash --delete-branch`), pull, and rebase your fix before pushing — or skip your own commit if the merge is the whole fix. If `gh pr merge` is denied outright (a standing `permissions.deny` on the verb, not a retryable prompt), see [§ PR-merge permission wall](references/failure-patterns.md#pr-merge-permission-wall).
177
169
 
178
- 7. **Commit the fix** with a clear message describing what changed and why, then `git push`.
170
+ 7. **Commit the fix** with a clear message describing what changed and why. Before a push that goes out at once, cancel the branch's remaining runs to free runners, then `git push`:
171
+
172
+ ```shell-session
173
+ $ <cmd> cancel-runs --branch=<BRANCH>
174
+ ```
175
+
176
+ 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`.
177
+
178
+ After the cancel, `ci-status` reports each required job it stopped on the tip as `required job cancelled`, with a `gh run rerun` command. Do not run that command: your cancel stopped the job, and your fix push moves the tip past that run.
179
179
 
180
180
  When the fix corrects a *user-facing* bug, add a `changelog.md` entry **only when the bug reached a released version**. Blame the changed line against the last release tag (`git blame`, or `git log -S`): a bug introduced *and* fixed within the current unreleased cycle never shipped, so it gets no entry; a bug that predates the last tag is a real regression and does. Making this call here keeps a parent `/repomatic-ship` run from having to add or drop entries afterward.
181
181
 
@@ -38,6 +38,8 @@ Not all CI failures are code bugs:
38
38
 
39
39
  - **Runner timeouts or OOM kills**: the log ends abruptly or shows `The runner has received a shutdown signal`. Re-run; do not change code.
40
40
  - **A runner that died mid-step**: the step runs far past its baseline, and a cancel does not stop it. A live runner kills a cancelled step within ten seconds and keeps its partial log. A cancel does not apply to a job whose `if:` holds `always()`, so read that condition first. Any other job still `in_progress` a minute after the cancel has lost its runner: the server closes it at the five-minute [cancellation timeout](https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-cancellation), and no log survives, neither at the job's log endpoint (`BlobNotFound`) nor in the run's log archive. A 404 from a job that is still running proves nothing, since every running job returns one. Re-run with `--failed`: there is nothing to diagnose.
41
+ - **A required job `cancelled` with no runner and no steps**: its check run carries the annotation `The job was not acquired by Runner of type hosted even after multiple attempts`, because the hosted pool for its label had no capacity, often macOS arm64. The run concludes `failure` with no failed job and no job log. Re-run with `--failed`.
42
+ - **A required job `cancelled` at its `timeout-minutes`**: its check run carries the annotation `The job has exceeded the maximum execution time of 30m0s`, and the run concludes `cancelled`, like a run a newer push stopped. No newer push stopped a run on the tip, so `ci-status` reads it there as `1 required job(s) cancelled` and blocks. Compare the step's duration with the last green run: a step that ran far past it hung. Re-run with `--failed`.
41
43
  - **Action version mismatches**: `Unable to resolve action`, deprecated-runtime errors. Fix the workflow YAML, not the Python.
42
44
  - **Network/registry flakiness**: `uv`/`pip` timeouts, PyPI 503s, `ConnectionResetError`. Re-run.
43
45
  - **A wall-clock budget assertion** (`assert elapsed_ms < N`) failing on a shared runner: infrastructure is the *trigger*, but the defect is the test, which took one sample and so measured that runner's worst moment rather than the code. A re-run only re-rolls the dice, and the tell that it has been re-rolled before is a budget already ratcheted upward in an earlier cycle for the same runner class. Assert on the fastest of several samples instead: a real regression slows every sample, a scheduling stall slows one. Raising the budget again is the fix that stops working.
@@ -173,9 +173,10 @@ If a matching open issue exists, report it to the user and stop. Do not offer a
173
173
 
174
174
  A matching issue closed for lack of a reproducer is not a dead end: cite it, because that closure is part of the record, and supply what it lacked.
175
175
 
176
- A keyword search over issues is not enough. Run these four checks too before you report the result to the user:
176
+ A keyword search over issues is not enough. Run these five checks too before you report the result to the user:
177
177
 
178
178
  - **Pull requests.** Run the same keywords through `gh search prs`: a fix under review answers the report before it is filed.
179
+ - **The code at the default branch.** Blame the lines the bug runs through at the tip of `main`, and read every commit that changed them after the release you measured: a fix can sit there behind an issue whose title shares no word with your symptom. Then check the stable branches for a backport.
179
180
  - **Everything since the behavior appeared.** List the issues and pull requests created since the commit that introduced it, and read every title. A body search is noisy, because pasted logs hold the tool's own vocabulary.
180
181
  - **Branches and release notes.** Read the development branches and the release notes for a fix in progress, and for the maintainer's own words on the topic.
181
182
  - **Overlap.** Name the threads that share the theme without being duplicates. Cross-reference in the report the ones a reader can confuse with it.
@@ -277,7 +278,10 @@ What happens instead, with exact error output in code blocks.
277
278
  - Include exact error messages in code blocks, not paraphrases.
278
279
  - If multiple distinct failures exist, group them under numbered sub-sections but keep them in one report if they share a root cause. File separate issues if root causes differ.
279
280
  - File a second finding as its own issue, cross-referenced, never by broadening the first one's title. The title must still name the fix that closes it.
281
+ - When two new drafts link each other, put the link only in the draft to post second, and name the posting order in the hand-off: a placeholder for the other number gets posted as is when the order flips.
282
+ - When the user sends a posted URL, diff the posted body against the draft before deleting the draft. A hand edit made before posting can break a code span or a link: name the line to fix.
280
283
  - Keep reproduction steps minimal: strip everything not needed to trigger the bug.
284
+ - Match the depth of the reports the maintainer already accepted: read two or three closed reports of the same kind with their replies, and leave out the checks the maintainer runs themselves. Evidence they would redo only lengthens the report.
281
285
  - Link to CI runs or logs when available.
282
286
  - Do not speculate about fixes unless the root cause is clear from the evidence.
283
287
  - Do not use em dashes; use colons for inline elaboration.
@@ -14,7 +14,7 @@ Reach for one when:
14
14
  - A feature's flagship scenario has only ever run against mocks or a stand-in host.
15
15
  - A CI failure depends on runner-image state that local reproduction cannot fake (preinstalled tools, filesystem ACLs, service accounts).
16
16
 
17
- Do not reach for one when a local test, a container run on the development machine, or reading the tool's source answers the question faster.
17
+ Do not reach for one when a local test, a container run on the development machine, a local VM running the same release, or reading the tool's source answers the question faster. Check the VMs the machine already runs before you offer a probe.
18
18
 
19
19
  ## Invocation
20
20
 
@@ -24,6 +24,7 @@ The loop commits and pushes on every iteration. Get the user's explicit go-ahead
24
24
 
25
25
  - **Mark it temporary in line one.** The workflow's first comment says `TEMPORARY probe workflow, to be deleted once <question> is answered`. Name the file `<subject>-probe.yaml`.
26
26
  - **Trigger on `push` with a `paths:` filter covering the workflow file AND the code under test.** A probe validating `mymodule.py` must re-run when `mymodule.py` changes, or code iterations silently test nothing.
27
+ - **Run on the runner label of the job the probe stands in for.** Images and architectures differ in network path and preinstalled tools, so a measurement taken on `ubuntu-26.04` can disagree with a job that runs on `ubuntu-26.04-arm`.
27
28
  - **Cooldown rules apply.** Installs from live registries carry the repository's cooldown (`UV_EXCLUDE_NEWER`, `NPM_CONFIG_MIN_RELEASE_AGE` in the workflow `env:`); distro archives (`apt-get`, `apk`) are out of scope by design. Pin actions by SHA and tools by version, copied from an existing workflow.
28
29
  - **Hard gates, not eyeballs.** Every claim becomes a `grep -q` (or `test -e`, exit-code check) against captured output: `command > out.txt 2>&1 || true` then grep. A step that only prints is a diagnostic, not a validation, and belongs in the run only while a question is open.
29
30
  - **Negative gates too.** Assert the behavior does NOT fire where it must not (`if grep -q ...; then exit 1; fi`), or the probe proves half the contract.
@@ -34,7 +34,7 @@ The release is push-driven: the `prepare-release` job in `changelog.yaml` runs `
34
34
 
35
35
  - **The review gate is the permission system, not a behavioral stop.** Normal runs prompt on each `git commit`, `git push`, and subagent write; step 4 shows the consolidated changelog diff *before* the first commit prompt, so approving that commit is the review gate and denying it stops the run. `--dangerously-skip-permissions` mutes the prompts so the full sequence runs autonomously; the skill cannot detect the mode.
36
36
  - **Invocation method.** When the context shows `CANONICAL_REPO`, use `uv run --frozen repomatic`: without `--frozen`, an edit to `pyproject.toml` makes the local uv relock `uv.lock`. 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`. This applies the supply-chain cooldown to repomatic's dependency tree while keeping a fresh release installable. The pin matters because the tool registry ships inside repomatic: a newer release pins newer `ruff`, `typos` or `mypy` than the ones CI runs, and a gate built on it stops reproducing CI. Drop the `--from` clause only when the context shows no `WORKFLOW_PIN`. References to `<cmd>` below resolve to one or the other.
37
- - **On the canonical repo, read skills by path.** The `Skill` tool can load an installed copy from the last release, older than `.claude/skills/`. Read the repository copy instead, and tell each spawned agent to do the same.
37
+ - **On the canonical repo, read skills by path.** The `Skill` tool can load an installed copy from the last release, older than `.claude/skills/`. Read the repository copy instead, and tell each spawned agent to do the same. This skill is no exception: its slash command can load the installed copy, so diff it against `.claude/skills/repomatic-ship/SKILL.md` and follow the repository copy.
38
38
  - **Delegate the substance edits, apply the changelog yourself.** The sweep agents own the code, docs and bundled-asset lanes, so leave those files to them even when you do hold `Edit`/`Write`. The changelog is the exception: a skill is instructions rather than an actor, and `/repomatic-changelog` tells whoever loaded it to apply the consolidation directly, so you write `changelog.md` inline.
39
39
 
40
40
  ### Sub-agent rules
@@ -69,6 +69,8 @@ A release materializes the **net state since the last tag**, not the path taken
69
69
 
70
70
  **Judge that diff against current `main`, not against the PR's head.** An open PR is pinned to the commit it branched from, so its diff can describe a file the maintainer has since fixed. Rewording is the third option beside allowlisting and reverting: dropping the trigger word also stops the job re-proposing, and a rule landed on top of it then allowlists a word that appears nowhere. So `git grep` the trigger before writing a rule for it, and when the maintainer already solved it their way, leave it alone. Closing or merging the PR is theirs to decide: surface it, land the rule-level fix **only while the trigger is still live in the tree**, and say either way in the step-7 report.
71
71
 
72
+ **Read the merged automation PRs too, for a follow-up their job left to a human.** A `sync-uv-lock` run that prunes an `exclude-newer-package` entry cannot rewrite the comment that justified it, so its PR body asks for that edit in a `> [!WARNING]`. The merge leaves the edit undone, and no later run asks again. List the cycle's candidates with `gh pr list --state merged --search 'merged:>=<last-tag date>' --limit 200 --json number,headRefName,body --jq '.[] | select(.body | test("\\[!WARNING\\]")) | [.number, .headRefName] | @tsv'`, then read each warning. Add every request still live in the tree to the brief of the lane that owns its file. The `prepare-release` body carries a squash warning, which asks for no edit.
73
+
72
74
  **Always read that run's `head_sha`, and treat a red as live only if nothing since it could have fixed it.** Most monitored workflows carry a `paths:` filter, so a commit that touches nothing in the filter triggers no run. When *that* commit is the one that fixed the red, the latest conclusive run stays pinned to the superseded parent and keeps reporting a failure that no longer exists. Before adding a red to the brief, run `git log --oneline <run head_sha>..HEAD` and check whether an intervening commit touched the failing area; when the answer is unclear, settle it for the cost of one dispatch (`gh workflow run <workflow> --ref main`, no commit, no PR churn) rather than reasoning about it.
73
75
 
74
76
  **A green conclusive run proves nothing when supersession cancelled every run between it and `HEAD`.** Walking back past `cancelled` runs to reach the newest conclusive one skips exactly the commits a busy cycle pushed most recently, so that `success` can predate every line the cycle added, and a false green ships the break. Before recording an empty red inventory, diff the gap: `git log --oneline <newest success head_sha>..HEAD`. When cycle commits sit inside it, the workflow has never run on them and the green is stale. Settle it with a dispatch (`gh workflow run <workflow> --ref main`, no commit, no PR churn) or by waiting out `HEAD`'s own run, never by recording "no reds".
@@ -110,7 +112,7 @@ The three substance passes own disjoint lanes (code owns Python including docstr
110
112
  - Correcting one description of a convention means correcting *every* description of it in the same pass: a rule restated in more than one place (an overview line and its worked example, two docs pages) drifts as a set, so grep for the sibling statements and align them together.
111
113
  - The same "align the siblings" rule governs *quantities*, not just wording. A cycle that measured the same thing twice ships two answers, so cross-check every timing, size, count and ratio a page states against the other statements of it, the changelog's copy included. Surrounding prose that quotes a ratio the tables no longer support is the tell. Report the contradiction with the conflicting values and which one the other statements corroborate, rather than silently re-deriving numbers on hardware that is not the maintainer's.
112
114
  - **Commit provenance decides whether a clashing figure is reported or fixed, and the two need opposite handling.** Blame each one (`git log -S`, or read the commit that introduced it). When the older figure entered *earlier in this same cycle* and a later commit measured the thing again, it is superseded intra-cycle scaffolding, which layer 1 of the code pass strips like any other. Replace it, and cite the surviving measurement's source beside it. Only when neither figure obsoletes the other are they independent measurements, and only then does the report-don't-touch rule above apply.
113
- - The docs build has a single owner, the code agent (which already builds for docstring cross-references), or the orchestrator when the code lane is split: verify prose against that build instead of launching a second `sphinx-build` into the same output dir.
115
+ - The docs build has a single owner, the code agent (which already builds for docstring cross-references), or the orchestrator when the code lane is split: verify prose against that build instead of launching a second `sphinx-build` into the same output dir. The docs pass's own edits render only in a later build: the orchestrator checks them in the last build of the owner, so the docs pass never waits on a rebuild.
114
116
  - A probe of the package runs through the same `uv run` form as the tests, group list included. Another group list re-resolves the shared environment, and a test parametrized over installed plugins then collects a different set.
115
117
  - Any docs-pass edit touching a `.py` file (typically `docs/conf.py`) is re-verified with a bare `<cmd> run mypy` before the agent returns: `docs/conf.py` may import from the docs group's higher Python floor while mypy checks the project minimum, and the break otherwise surfaces only in CI's lint job. Give it no arguments, per step 2's Types gate.
116
118
  - Changelog *released* sections (`## [X.Y.Z]` blocks) are immutable history: a command, option, or config key named there was correct for that release, so never flag or rewrite a since-renamed name in one. When the changelog seeds the checklist for a rename, reconcile only the unreleased section.
@@ -126,7 +128,7 @@ The three substance passes own disjoint lanes (code owns Python including docstr
126
128
 
127
129
  **Downstream, the lane covers only what the repository authors.** A skill named in `<cmd> list-skills`, or an agent that `repomatic init subagents` installs, is a synced copy: the next sync overwrites an edit to it, so report a stale claim in one for step 8 instead. When the repository tracks no skill or agent of its own, skip this lane and spawn the code and docs passes alone.
128
130
 
129
- 4. **Changelog**: once the substance passes settle, invoke `/repomatic-changelog consolidate` through the `Skill` tool, so the consolidated entries (and the version advisory reading them) reflect the reconciled tree, renames included. It collapses superseded values and drops intra-cycle reverts. Consolidation assumes the entries already exist: when the unreleased section under-represents the net cycle (a maintainer left one stub bullet for a multi-feature cycle), run `add` first, or the bare `/repomatic-changelog` default that runs `add` then `consolidate`. When both `add` and consolidation find nothing user-facing (a purely mechanical cycle), consolidation backfills one generic maintenance bullet rather than leaving the section empty (`/repomatic-changelog` consolidation rule 08). If the skill is excluded here, degrade gracefully (sub-agent rules). A long unreleased section needs each bullet checked against the last tag. Hand that read-only check to parallel agents while the substance lanes run: it does not depend on the sweep. An in-cycle bug fix, a removal of a name the last tag never had, and a stale path all surface there.
131
+ 4. **Changelog**: once the substance passes settle, invoke `/repomatic-changelog consolidate` through the `Skill` tool, so the consolidated entries (and the version advisory reading them) reflect the reconciled tree, renames included. It collapses superseded values and drops intra-cycle reverts. Consolidation assumes the entries already exist: when the unreleased section under-represents the net cycle (a maintainer left one stub bullet for a multi-feature cycle), run `add` first, or the bare `/repomatic-changelog` default that runs `add` then `consolidate`. When both `add` and consolidation find nothing user-facing (a purely mechanical cycle), consolidation backfills one generic maintenance bullet rather than leaving the section empty (`/repomatic-changelog` consolidation rule 08). If the skill is excluded here, degrade gracefully (sub-agent rules). A long unreleased section needs each bullet checked against the last tag. Hand that read-only check to parallel agents while the substance lanes run: it does not depend on the sweep. An in-cycle bug fix, a removal of a name the last tag never had, and a stale path all surface there. So does a change no bullet covers. On the canonical repo, the `sync-tool-versions` commits move the `repomatic run` pins and write no bullet, so the net registry diff needs one.
130
132
 
131
133
  ### If the sweep made no edits
132
134
 
@@ -185,7 +187,7 @@ The checks:
185
187
  - **A cooldown filter is not a resolution failure — check for it before declaring one.** `uvx` reads the *user-level* `~/.config/uv/uv.toml`, which on a maintainer's machine typically carries a supply-chain `exclude-newer`. A release that raises a dependency floor to a version published inside that window then fails to resolve **on the maintainer's machine only**. The tell is in uv's own output: a `hint: <pkg> was filtered by exclude-newer to only include packages uploaded before <date>. The latest version satisfying the requirement is vX, published at <later date>`. It is self-clearing: the same command passes once the dependency ages past the window. An install that also gates the release never meets it, since the release is newer than the floor it raised. One that exempts the release alone, as downstream workflows do for their `repomatic` pin, fails the same way until the dependency clears.
186
188
  - **Re-run with the cutoff lifted wholesale, and judge the gate on that result.** Use `uvx --no-progress --exclude-newer 2100-01-01 --from . <cmd-bare> --version`. Lifting it per-package (`--exclude-newer-package <pkg>=0d`) just surfaces the next floor in the chain, one round-trip at a time.
187
189
  - **A cooled run that resolves and then crashes is a floor bug, not the cooldown.** A cooldown artifact fails *during* resolution, and says so with the `hint:` above. A floor bug installs cleanly, then dies at runtime on the older version the cooldown fell back to: typically a `TypeError` naming an argument a newer release introduced. Lifting the cutoff hides it, so judging the lifted run alone passes the gate on a release that every cooled install will break. Downstream repos run the frozen `uvx 'repomatic==X.Y.Z'` under a workflow-level `UV_EXCLUDE_NEWER`, and `uvx` reads neither `uv.lock` nor `[tool.uv]`. Read the traceback before crediting the cutoff. When the older version is at fault, raise the floor to what the code needs, and let `lint-deps` say whether the release waits.
188
- - **Resolve the last published release the same way.** Run `uvx --no-progress --exclude-newer 2100-01-01 --from '{package}=={last version}' <cmd-bare> --version`. A dependency released after that tag can break what users install today, through a floor that sets no cap. No change to the tree fixes that install, so it does not block the release you prepare. Report the crash and the dependency at step 7: a yank or a capped patch release of the old version is the maintainer's call.
190
+ - **Resolve the last published release under the cooldown.** Run `uvx --no-progress --from '{package}=={last version}' <cmd-bare> --version`. A dependency released after that tag can break what users install today, through a floor that sets no cap. Never lift the cutoff for this check. `--version` imports every resolved package, so a lifted cutoff runs releases still young enough to be a compromise. The cooled run meets such a dependency once it clears the window. No change to the tree fixes that install, so it does not block the release you prepare. Report the crash and the dependency at step 7: a yank or a capped patch release of the old version is the maintainer's call.
189
191
  - **The `uv-build ... missing an upper bound` warning here is expected, never a resolution failure.** repomatic deliberately leaves `uv-build` uncapped across managed repos (rationale in repomatic's own `pyproject.toml` `[build-system]` comment), so never flag it or add a cap.
190
192
  - **Pinned repomatic on the release tree**, only in a repository repomatic itself depends on, like click-extra or extra-platforms. Install the working tree and the pinned `repomatic=={X.Y.Z}` into one scratch venv, then import every `repomatic` module. A failure breaks every repository pinned to that release once this version clears the cooldown: release the fixed repomatic first, and move the pin.
191
193
 
@@ -243,7 +245,7 @@ Step 2 cleared every locally-reproducible failure and step 1's red inventory pre
243
245
 
244
246
  **Time each push by what its diff rebuilds.** The immediate push above is for source-affecting fixes (`repomatic/**`, `tests/**`, `pyproject.toml`, `uv.lock`): the matrix they cancel was verifying an obsolete tree, and their own run rebuilds everything. A matrix-skipping commit (changelog-only, docs-only: paths outside `Metadata.binary_affecting_paths`) inverts the economics on a binaries-enabled project, because `release.yaml` runs on *every* push in a per-branch cancel-in-progress group: pushed mid-drain, it cancels an in-flight binary matrix that its own run then skips rebuilding (`skip_binary_build`), and the lost verification is only re-buyable with a full re-dispatch. That cost scales with what is in flight: an ordinary push builds only the `[tool.repomatic] nuitka.dev-targets` canary subset, and no push cancels a full fleet, since release commits, `schedule` and `workflow_dispatch` runs each sit in their own concurrency group. Hold such commits (the post-babysit changelog reconciliation below included) until the heavy matrices on the current tree are terminal, or bundle them into the next source-affecting push; with binaries off, or only a canary build in flight, push freely: a cancelled `release.yaml` re-runs in minutes, and a prose push does not even cancel `tests.yaml` (paths-filtered, so no new run enters its concurrency group).
245
247
 
246
- **Measure the cycle before you delegate it.** The Bash tool caps a foreground command at about 10 minutes. Read the runs of the previous `main` HEAD (`gh api 'repos/<owner>/<repo>/actions/runs?head_sha=<full-sha>'`) and subtract each run's `run_started_at` from its `updated_at`. When the slowest took under 10 minutes, skip the spawn and run `<cmd> ci-status --branch main --wait` yourself. A longer cycle needs no spawn either: run the same command as a background Bash task (`run_in_background: true`), which has no such cap and wakes you when it returns (Claude Code `2.1.284`). Either way, the command returns on the first failed required job, or when every run settled. Spawn the babysitter only when a required job turns red, and run the command again after each fix push.
248
+ **Measure the cycle before you delegate it.** The Bash tool caps a foreground command at about 10 minutes. Read the runs of the previous `main` HEAD (`gh api 'repos/<owner>/<repo>/actions/runs?head_sha=<full-sha>'`) and subtract each run's `run_started_at` from its `updated_at`. When the slowest took under 10 minutes, skip the spawn and run `<cmd> ci-status --branch main --wait` yourself. A longer cycle needs no spawn either: run the same command as a background Bash task (`run_in_background: true`), which has no such cap and wakes you when it returns (Claude Code `2.1.284`). Either way, the command returns on the first run that blocks a merge, like one with a failed or cancelled required job, or when every run settled. Spawn the babysitter only when a required job turns red, and run the command again after each fix push.
247
249
 
248
250
  **Spawn `Agent` on the `sonnet` model to run `/babysit-ci` to completion**, named so it stays addressable. The loop is mechanical: fetch logs, match patterns, fix, commit, push. If `/babysit-ci` is excluded here, the agent runs that same loop inline, and the sub-agent rules cover a failed spawn.
249
251
 
@@ -256,7 +258,7 @@ Step 2 cleared every locally-reproducible failure and step 1's red inventory pre
256
258
  Its prompt restates the sub-agent rules (the trailer and narrow staging especially: its commits are exactly the unattended ones those rules exist for) and adds:
257
259
 
258
260
  - **The loop condition, verbatim**: "re-poll after each push; do not return after a push without re-polling". The turn ends only when every monitored workflow on the latest `main` HEAD has `conclusion: success` (or `skipped` for benign reasons), or on a real blocker it cannot resolve. Terser phrasings get misread as "report after first fix".
259
- - **The poll**: `<cmd> ci-status --branch main --wait`, which polls in-process every 60 seconds and returns on the first failed required job. Never a hand-rolled loop around `gh`: a zero-delay spin exhausts the shared REST quota (5,000 requests/hour) in minutes, and the exhaustion resurfaces as PAT-permission-shaped workflow failures and `prepare-release` hangs (see babysit's `references/failure-patterns.md` § GitHub API rate-limit exhaustion).
261
+ - **The poll**: `<cmd> ci-status --branch main --wait`, which polls in-process every 60 seconds and returns on the first run that blocks a merge, like one with a failed or cancelled required job. Never a hand-rolled loop around `gh`: a zero-delay spin exhausts the shared REST quota (5,000 requests/hour) in minutes, and the exhaustion resurfaces as PAT-permission-shaped workflow failures and `prepare-release` hangs (see babysit's `references/failure-patterns.md` § GitHub API rate-limit exhaustion).
260
262
  - **Poll in-process; never detach a monitor**: `ci-status --wait` blocks inside the agent's turn, never a `run_in_background` Bash poller or a `Monitor`-tool stream the agent idles on awaiting notification. Name the `Monitor` tool in the prohibition: an agent told only "no background poller" does not classify `Monitor` as one. A spawn prompt with an "as a background task" aside overrides babysit's own rule, and a failure landing in the idle window then goes unhandled.
261
263
  - **Expect to take the loop over for a long matrix; this is structural, not agent failure.** The Bash tool caps a foreground command at ~10 minutes and auto-backgrounds it on expiry, which ends the agent's turn. A 40-90-minute Nuitka matrix therefore cannot be watched to completion by a sub-agent, and re-spawning or re-chasing does not fix it. Delegate babysitting for the fast workflows, and when the remaining wait is the binary matrix, **stop the agent and own the wait yourself** with a `Monitor`. Give that monitor a filter that emits only what you would act on (a failing stable job the moment it lands, and each run reaching a terminal state), since per-cell progress across a dozen cells will trip the event-volume cap.
262
264
  - **Interim status pings**: a message at startup (local gate result, which runs it watches) and on every state change (fix pushed, workflow landed, re-run triggered), not only at the end. A silent babysitter is indistinguishable from a dead one.
@@ -12,6 +12,8 @@ argument-hint: '[vOLD vNEW] [all|workflows|configs|upstream]'
12
12
 
13
13
  !`git diff HEAD -- .github 2>/dev/null | grep -E '^-.*kdeldycke/repomatic/.*v[0-9]+\.[0-9]+\.[0-9]+' | grep -oE 'v[0-9]+\.[0-9]+\.[0-9]+$' | sort -uV | head -1 | sed 's/^/PREVIOUS_PIN_UNCOMMITTED /'`
14
14
 
15
+ !`cat .git/repomatic/upgrade.json 2>/dev/null || echo "NO_UPGRADE_RECORD"`
16
+
15
17
  !`git log -1 --format='LAST_WORKFLOW_COMMIT %h %ad %s' --date=short -- .github/workflows 2>/dev/null`
16
18
 
17
19
  !`[ -d ../repomatic/.git ] && echo "SIBLING_CHECKOUT ../repomatic" || echo "NO_SIBLING_CHECKOUT"`
@@ -28,7 +30,7 @@ argument-hint: '[vOLD vNEW] [all|workflows|configs|upstream]'
28
30
 
29
31
  You bring a downstream repository in line with `kdeldycke/repomatic`, and you do it in two passes in one session. The first pass works the delta of a newer release. The second audits how far the repository has drifted from the tag it now pins. Both passes share one report.
30
32
 
31
- `repomatic init` prints the command launching this skill as its last next step when it moves the upstream pin. The `sync-repomatic` upgrade pull request invites the maintainer to run it, and so does the `sync-workflow-pins` one when a bump moves `repomatic`.
33
+ `repomatic init` prints the command launching this skill as its last next step when it moves the upstream pin. That run also writes the upgrade record the context prints. The `sync-repomatic` upgrade pull request invites the maintainer to run it, and so does the `sync-workflow-pins` one when a bump moves `repomatic`.
32
34
 
33
35
  **This skill is for downstream repos only.** If the context shows `CANONICAL_REPO`, tell the user this skill is not applicable.
34
36
 
@@ -42,15 +44,24 @@ Both values come from `$ARGUMENTS`, in any order, and neither constrains the oth
42
44
 
43
45
  - **The version pair** drives the first pass, which runs whenever a previous pin is known. Take it from the first source that carries it:
44
46
  1. A `vOLD vNEW` pair in `$ARGUMENTS`.
45
- 2. The uncommitted diff: the removed `uses:` lines carry the previous pin, the added ones the adopted pin. The context prints it as `PREVIOUS_PIN_UNCOMMITTED`.
46
- 3. The last upgrade commit: `git log -p -1 -- .github/workflows`, reading the previous pin off its removed `uses:` lines.
47
- 4. Nowhere: the first pass has no delta to review. Skip it and audit alone.
47
+ 2. The upgrade record, through its `previous_pin` and `adopted_pin` fields (§ Read the upgrade record).
48
+ 3. The uncommitted diff: the removed `uses:` lines carry the previous pin, the added ones the adopted pin. The context prints it as `PREVIOUS_PIN_UNCOMMITTED`.
49
+ 4. The last upgrade commit: `git log -p -1 -- .github/workflows`, reading the previous pin off its removed `uses:` lines.
50
+ 5. Nowhere: the first pass has no delta to review. Skip it and audit alone.
48
51
  - **The scope** drives the second pass, and defaults to `all`:
49
52
  - `all`: run every audit area below.
50
53
  - `workflows`: audit workflow files only.
51
54
  - `configs`: audit non-workflow config files only.
52
55
  - `upstream`: identify downstream innovations that could be contributed back to `repomatic`.
53
56
 
57
+ ### Read the upgrade record
58
+
59
+ A `repomatic init` run that moves the upstream pin records itself in `.git/repomatic/upgrade.json`. It lists the paths the run wrote and deleted, the commit it started from as `head`, the paths already uncommitted then as `modified_before`, and the warnings it printed. The context prints the file, or `NO_UPGRADE_RECORD`. In a linked worktree, read it at the path `git rev-parse --git-path repomatic/upgrade.json` prints.
60
+
61
+ - **Use the record only when its `adopted_pin` is the `ADOPTED_PIN`.** The record writes each pin as a bare version, with no `v` prefix. Any other record describes an earlier move.
62
+ - **Take its findings as rows.** Each line of its `warnings` and each pair of its `removed_review` is one. Its `warnings` are the only record of the local edits `init` overwrote: no later run warns about them again.
63
+ - **Without a record, take the findings from the move itself.** Read the `repomatic init` output section of the `sync-repomatic` pull request that made it. Otherwise, find them as the sections below describe.
64
+
54
65
  ### Read upstream at the adopted tag
55
66
 
56
67
  Fetch every reference file at the `ADOPTED_PIN` tag, never at the tip of `main`:
@@ -76,6 +87,23 @@ Before flagging an issue, verify that the gap isn't **deliberate** or covered by
76
87
 
77
88
  When in doubt, search the upstream codebase to confirm whether a behavior is intentional. Read `[tool.repomatic]` in the local `pyproject.toml` carefully before declaring anything missing.
78
89
 
90
+ ### Commit the upgrade first
91
+
92
+ The upgrade gets a commit of its own, before the review changes any file. § Run the machinery first then reads the upgraded `HEAD`, so each hunk it finds is real drift. Skip this section when the context shows no `PREVIOUS_PIN_UNCOMMITTED`: the upgrade is committed already.
93
+
94
+ 1. **List the paths of the upgrade.** Take the `created`, `updated` and `deleted` lists of the record when its `head` is `HEAD`. Leave out a `deleted` path that `git ls-files` does not list, like an empty folder: git never tracked it, and a pathspec naming it fails the whole command. Without such a record, show `git status --short` and ask the user which paths belong to the upgrade.
95
+
96
+ 2. **Ask before you commit a path the record lists under `modified_before`.** It held uncommitted work before the upgrade, which the commit would take along: show its diff first.
97
+
98
+ 3. **Commit those paths alone.** Another session can share the working tree and its index, so never run `git commit --all`, and never commit the whole index:
99
+
100
+ ```shell-session
101
+ $ git add --all -- {paths}
102
+ $ git commit --message 'Upgrade `repomatic` to `vNEW`' -- {paths}
103
+ ```
104
+
105
+ The subject is the title of the `sync-repomatic` pull request, so the history reads the same whichever way the upgrade came.
106
+
79
107
  ### Run the machinery first
80
108
 
81
109
  The adopted release checks most of the integration on its own. Run it before any comparison by hand, and report what it finds as rows.
@@ -92,7 +120,7 @@ The adopted release checks most of the integration on its own. Run it before any
92
120
 
93
121
  An empty diff with no untracked file means every thin caller, each header-only workflow header and each `[tool.X]` section already present under ongoing sync equals what that release generates. Any hunk is `DRIFT` that the `sync-repomatic` job would rewrite. An untracked file is a managed file the repository lacks, which `git diff` never lists: `MISSING`, unless § Distinguishing real drift from intended absence explains it. Keep `--directory`: `--output-dir` alone writes into the copy but reads `[tool.repomatic]` from the directory the command started in. A managed file that looks wrong but leaves no hunk is what the generator writes: fix it upstream (§ Apply, step 4), never by hand.
94
122
 
95
- 2. **Run `<cmd> lint-repo --repo {owner}/{repo}`.** Without `--repo`, a local run has no `$GITHUB_REPOSITORY`, so every API-backed check drops out. A local run cannot read the repository secrets either, so `lint-repo` reports each of them as missing. Pass the flag of each secret `gh secret list --repo {owner}/{repo}` names: `--has-cloudflare-api-token`, `--has-cloudflare-r2-keys` for the two R2 keys, `--has-notifications-pat` and `--has-virustotal-key`. Its checks already cover thin-caller triggers and pins, the `setup-uv` version pin, inline upstream pins and their cooldown exemption, seeded tool-config entries, the funding file and runner images. Compare one of those by hand only when `lint-repo` reports it skipped.
123
+ 2. **Run `<cmd> lint-repo --repo {owner}/{repo}`.** Without `--repo`, a local run has no `$GITHUB_REPOSITORY`, so every API-backed check drops out. A local run cannot read the repository secrets either, so `lint-repo` reports each of them as missing. Pass the flag of each secret `gh secret list --repo {owner}/{repo}` names: `--has-cloudflare-api-token`, `--has-cloudflare-r2-keys` for the two R2 keys, `--has-notifications-pat` and `--has-virustotal-key`. Its checks already cover thin-caller triggers and pins, the `setup-uv` version pin, inline upstream pins and their cooldown exemption, seeded tool-config entries, the rule set of `[tool.gitleaks]`, the funding file and runner images. Compare one of those by hand only when `lint-repo` reports it skipped.
96
124
 
97
125
  The generator does not read hand-owned jobs, the comment beside a synced key, or an entry only the local file carries. Pass 2 compares those.
98
126
 
@@ -112,10 +140,10 @@ For each bullet outside the skip bin, find what it touches here. Grep the source
112
140
  - **A new job, skill or subagent.** Check `[tool.repomatic] exclude` before proposing it: an excluded component is a decision, not a gap.
113
141
  - **A dropped or renamed surface.** Grep `tests.yaml`, any other header-only workflow, and local scripts for the old name.
114
142
  - **An upstream fix.** Search comments and workflow steps for the workaround it retires: `work around`, `XXX`, `TODO`, version-guarded branches, and inline pins of the tool it fixed.
115
- - **A generator change**, like a thin caller gaining a trigger or a header gaining `paths:`. Read `git diff HEAD -- .github/workflows` against the changelog, so a diff the release explains is never reported as drift. When the upgrade is already committed, that diff is empty: the generator run (§ Run the machinery first) then proves the commit regenerated every managed file instead of moving the pins by hand.
143
+ - **A generator change**, like a thin caller gaining a trigger or a header gaining `paths:`. Read the diff of the upgrade commit, `git log -p -1 -- .github/workflows`, against the changelog, so a diff the release explains is never reported as drift. The generator run (§ Run the machinery first) then proves the commit regenerated every managed file instead of moving the pins by hand.
116
144
  - **A shifted test matrix axis.** Run `show-metadata --output-format json test_matrix test_matrix_pr` at both pins and compare the cells. A pin before `8.0.0` spells that option `--format`. A `[tool.repomatic] test-matrix.exclude` entry names a literal version, so a release that moves the Python axis can make it drop the new stable version and keep the old floor.
117
145
  - **A changed job.** Before you report it as adopted, call the released code on this repository's real inputs. An open pull request from that job shows only what its last run did, and that run can predate the adopted pin. A job that reads a file from another project also stops working when that file moves. A change to the binary build shows only in the self-test of the binaries `Build & release` compiles, which the Tests workflow never runs. A push to `main` compiles one target only, so run `gh workflow run release.yaml --ref main`, which builds every target, and read the self-test of each.
118
- - **A synced skill or subagent.** `repomatic init` rewrites every bundled copy verbatim, so the upgrade also reverts each local commit made to one since the last sync. Take every copy under `skills.location` and `subagents.location` as it stood before the upgrade. That is `HEAD` while the upgrade is uncommitted, and the upgrade commit's parent once it landed. Compare it with upstream's `.claude/skills/{name}/SKILL.md` or `.claude/agents/{name}.md` at `vOLD`. Read those paths, not `repomatic/data/skills/`: its entries are symlinks, and `git show` returns their target path. A copy that matches neither `vOLD` nor any upstream commit between the two tags carries local edits. Upstream holds them already when they were ported before the release. To know, write the three states to files and run `git merge-file -p {vNEW copy} {vOLD copy} {local copy}`. An output equal to the `vNEW` copy means the upgrade drops nothing. Any other output holds edits that the upgrade drops, so report them as a `breaking` row. Then read the same path on upstream `main`, which decides the action and never the status. Edits `main` already holds ship with the next release, so the row only asks to leave the `sync-repomatic` pull request unmerged until then. Port the edits it lacks.
146
+ - **A synced skill or subagent.** `repomatic init` rewrites every bundled copy verbatim, so the upgrade also reverts each local commit made to one since the last sync. When the record's `warnings` hold no `Could not read` line, check only the copies its `overwritten_edits` lists: `init` matched every other one against a file `vOLD` bundled. Take each copy under `skills.location` and `subagents.location` as it stood before the upgrade: at the record's `head`, or else at the parent of the upgrade commit. Compare it with upstream's `.claude/skills/{name}/SKILL.md` or `.claude/agents/{name}.md` at `vOLD`. Read those paths, not `repomatic/data/skills/`: its entries are symlinks, and `git show` returns their target path. A copy that matches neither `vOLD` nor any upstream commit between the two tags carries local edits. Upstream holds them already when they were ported before the release. To know, write the three states to files and run `git merge-file -p {vNEW copy} {vOLD copy} {local copy}`. An output equal to the `vNEW` copy means the upgrade drops nothing. Any other output holds edits that the upgrade drops, so report them as a `breaking` row. Then read the same path on upstream `main`, which decides the action and never the status. Edits `main` already holds ship with the next release, so the row only asks to leave the upgrade commit unpushed until then. Once the `sync-repomatic` pull request is merged, § Apply, step 2 keeps the local edits instead. Port the edits `main` lacks.
119
147
  - **A new `lint-repo` check.** Read its line in the `lint-repo` output: a check that passes here offers nothing.
120
148
  - **A seeded tool config that lacks a bundled template entry.** `init` writes `[tool.ruff]`, `[tool.pytest]`, `[tool.coverage]`, `[tool.mypy]` and `[tool.mdformat]` once, and `lint-repo` names each entry such a section lacks. Copy the entry when it applies here. Record one that the repository leaves out on purpose under `[tool.repomatic] lint-repo.declined`, with the reason its instructions or comments give. The key is the tool, then the path of the entry in its section, like `mypy.warn_unreachable = "{reason}"`. For one member of a list, add the member as `lint-repo` prints it, like `pytest.addopts."--numprocesses=logical" = "{reason}"`. Ask the user when no reason is stated. Never copy an entry only to silence the warning.
121
149
  - **A tool the registry bumped.** The changelog often leaves a tool version bump out. Run `<cmd> run mypy` and `<cmd> run ruff -- check --no-fix` once on the untouched tree, then the same two commands at `vOLD`. A finding that only the new pin reports is a row. When the release adds the gating job itself, every finding it fails on is a row, old ones included. A new `mypy` error is a `breaking` row: the `lint-types` job fails on it. So is a new `ruff` finding that no safe fix clears, which fails `lint-python`. A bumped pin still inside the cooldown is a `breaking` row too. `lint-repo` warns that `repomatic run` cannot install it before the date it names, and every job that runs the tool fails until then. For Nuitka that job is the binary build, so a release cut in that window ships without binaries. Admit the pin with the `[tool.uv] exclude-newer-package` entry the warning gives, or hold releases until that date.
@@ -153,13 +181,12 @@ A file can match its reference and still fail. Read the latest runs on the defau
153
181
 
154
182
  The generator run covers the `[tool.X]` sections under ongoing sync, and `lint-repo` the seeded ones. Check what neither reads:
155
183
 
156
- | File | What to check | Absence is OK when |
157
- | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
158
- | `pyproject.toml` `[tool.typos]` | Present at all: a bare `init` never adds the section, it only re-syncs one already there | Never: typos has no bundled fallback, so the canonical proper-noun map stays inactive. Recommend `repomatic init typos`. |
159
- | `.github/ISSUE_TEMPLATE/` | Filename conventions (hyphens, not underscores), missing labels | Personal/internal repo without external bug reporters. |
160
- | `.github/code-of-conduct.md` | Title-case headings vs upstream sentence case, plaintext email vs anti-scrape obfuscation, stale attribution URLs | Replace verbatim with upstream when divergence is detected. |
161
- | `.gitignore` | Must be a real file: git skips an in-tree `.gitignore` reached via symlink | Never: the `sync-gitignore` job owns its content. |
162
- | `pyproject.toml` `[tool.gitleaks]` | An allowlist alone replaces the built-in rules, so the scan finds nothing. It needs `extend.useDefault = true` | No `[tool.gitleaks]` section: gitleaks keeps its built-in rules. |
184
+ | File | What to check | Absence is OK when |
185
+ | ------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
186
+ | `pyproject.toml` `[tool.typos]` | Present at all: a bare `init` never adds the section, it only re-syncs one already there | Never: typos has no bundled fallback, so the canonical proper-noun map stays inactive. Recommend `repomatic init typos`. |
187
+ | `.github/ISSUE_TEMPLATE/` | Filename conventions (hyphens, not underscores), missing labels | Personal/internal repo without external bug reporters. |
188
+ | `.github/code-of-conduct.md` | Title-case headings vs upstream sentence case, plaintext email vs anti-scrape obfuscation, stale attribution URLs | Replace verbatim with upstream when divergence is detected. |
189
+ | `.gitignore` | Must be a real file: git skips an in-tree `.gitignore` reached via symlink | Never: the `sync-gitignore` job owns its content. |
163
190
 
164
191
  #### 3. Upstream contribution opportunities
165
192
 
@@ -194,17 +221,19 @@ Give every row and every list item an ID, so the user can answer "apply `F3`" or
194
221
 
195
222
  1. **Apply one row at a time, breaking rows first.** Keep each change readable on its own in `git diff`. Pass 2 findings wait until every pass 1 row is settled.
196
223
 
197
- 2. **Keep the local edits a synced copy carries.** Restore the file as it stood before the upgrade when upstream left it unchanged between the two tags. Otherwise keep that `git merge-file` output as the new copy, once its conflicts are resolved. To re-apply one local commit instead, `git apply -C1` gets past a context line upstream reworded. Then port the edits upstream `main` lacks, as step 4 describes, or the next sync reverts them again.
224
+ 2. **Keep the local edits a synced copy carries.** Restore the file as it stood before the upgrade when upstream left it unchanged between the two tags. Otherwise keep that `git merge-file` output as the new copy, once its conflicts are resolved. To re-apply one local commit instead, `git apply -C1` gets past a context line upstream reworded. Write the restored copy with your file-editing tool when a shell write fails: a sandbox can deny one to a skill or agent folder, `git checkout` and `git apply` included. Then port the edits upstream `main` lacks, as step 4 describes, or the next sync reverts them again.
198
225
 
199
226
  3. **Run the local checks after each row.** The project's tests, `mypy` and `ruff`, plus `<cmd> lint-repo --repo {owner}/{repo}` when the row touched `.github/` or `pyproject.toml`. After a row that touched a workflow, also run `<cmd> run actionlint`, which parses its `${{ }}` expressions. A failing check vetoes the row: revert it and note it in the report. Never loosen a test to pass.
200
227
 
201
228
  4. **Send generator problems upstream, as edits in the sibling checkout.** When a row needs a change in `repomatic` itself (a generator writing something unwanted, a missing knob, a docs gap, a lesson a synced copy carries) and the context shows `SIBLING_CHECKOUT`, implement it in `../repomatic`: the code, the tests it breaks, and a changelog bullet. Verify it there. `repomatic run typos` and `mdformat` rewrite files in place and print no findings, so judge them by `git diff`. Another session may share that checkout: edit only the files the row needs, and name them in the report so they can be committed by pathspec. Leave every change uncommitted. Without a sibling checkout, describe the change in the report instead.
202
229
 
203
- 5. **Never commit, push, or open an issue or pull request.** The user reviews the working tree and decides.
230
+ 5. **Commit the applied rows in one commit, after the upgrade commit.** Stage only the files the rows changed in this repository, as § Commit the upgrade first does: `git add --all -- {paths}`, then `git commit -- {paths}`. Name the changes in the subject, and add one body line per change only when the subject cannot name them all. A row a check vetoed stays out. When no upgrade commit exists, like after a first adoption, a row path that also holds uncommitted `init` output takes that output along: show the diff of that path before you commit it.
231
+
232
+ 6. **Never push, and never open an issue or pull request.** The user reviews the commits and decides.
204
233
 
205
- 6. **Close with two short lists.** Keep the tables as the record, then end the answer with two lists, a few words per item, in place of prose about what was applied or skipped. Start each item with its ID, then the row IDs it settles, like `- T1 Decide: (F4) …`:
234
+ 7. **Close with two short lists.** Keep the tables as the record, then end the answer with two lists, a few words per item, in place of prose about what was applied or skipped. Start each item with its ID, then the row IDs it settles, like `- T1 Decide: (F4) …`:
206
235
 
207
- - **Done**, numbered `D1`, `D2`, …: each applied row, with the files it changed, from either pass. A `breaking` row carries the detail it needs as sub-bullets here, and a row that needed no local edit stays in its table's closing line.
236
+ - **Done**, numbered `D1`, `D2`, …: each applied row, with the files it changed and the short SHA of its commit, from either pass. A `breaking` row carries the detail it needs as sub-bullets here, and a row that needed no local edit stays in its table's closing line.
208
237
  - **Left to do**, numbered `T1`, `T2`, …: each remaining action, ordered so it can be executed top to bottom, prefixed with one of these five labels and nothing else. Put `Decide:` items first, since an answer can add work below them.
209
238
  - `Decide:` a change this pass proposed and the user has not approved, or a choice between options. End the item with the answer you recommend.
210
239
  - `Implement:` code or a docs entry to write, naming the checkout when it is not this one.
@@ -146,12 +146,15 @@ Also check `docs/` and any changelog for upstream references.
146
146
  | PR | closed, not merged | Declined by upstream |
147
147
  | PR | open | Open upstream |
148
148
  | Issue | open or closed, this project still provides a workaround | Addressed by this project |
149
+ | Issue | closed as completed, no release ships the fix yet | Open upstream |
149
150
  | Issue | closed as completed | Upstreamed from this project |
150
151
  | Issue | closed as not planned | Declined by upstream |
151
152
  | Issue | open, no local workaround | Open upstream |
152
153
 
153
154
  The first matching row wins. List every issue the maintainer reported, even one closed with no local workaround ever needed. Skip a closed PR that its author withdrew, or that a later merged PR replaced: nobody declined it.
154
155
 
156
+ An issue kept in "Open upstream" after it closed names its fix: "closed by `project#N`, which no release carries yet". The fix is released once the newest release tag contains its merge commit: `gh api repos/{owner}/{repo}/compare/{tag}...{sha} --jq .status` then answers `behind` or `identical`.
157
+
155
158
  To determine whether the project has a workaround for an issue, search the codebase for references to that issue URL or number.
156
159
 
157
160
  #### 7. Build the page
@@ -179,17 +182,17 @@ For every GitHub URL in the document, check its current state via `gh`:
179
182
 
180
183
  Flag items that need to move:
181
184
 
182
- | Current section | New state | Action |
183
- | ------------------------- | ------------------------- | ----------------------------------------------------------------------------------- |
184
- | Open upstream | PR merged | Move to "Code contributed upstream" |
185
- | Open upstream | Issue closed as completed | Move to "Upstreamed" or "Addressed" depending on whether a local workaround existed |
186
- | Open upstream | Closed as not planned | Move to "Declined by upstream" |
187
- | Addressed by this project | Fixed upstream | Move to "Upstreamed from this project" |
185
+ | Current section | New state | Action |
186
+ | ------------------------- | ------------------------- | ------------------------------------------------------------------------------ |
187
+ | Open upstream | PR merged | Move to "Code contributed upstream" |
188
+ | Open upstream | Issue closed as completed | Move to "Addressed" if a workaround exists, else to "Upstreamed" once released |
189
+ | Open upstream | Closed as not planned | Move to "Declined by upstream" |
190
+ | Addressed by this project | Fixed upstream | Move to "Upstreamed from this project" |
188
191
 
189
192
  #### 2. Consistency checks
190
193
 
191
194
  - All items in "Code contributed upstream" are actually merged (not just closed).
192
- - All items in "Open upstream" are actually still open.
195
+ - All items in "Open upstream" are actually still open, or closed with a fix that no release carries yet.
193
196
  - No item appears in multiple sections.
194
197
  - Items within each project subsection are sorted by issue number (newest first).
195
198
 
@@ -14,7 +14,7 @@
14
14
  "name": "repomatic",
15
15
  "source": {
16
16
  "path": ".claude",
17
- "ref": "v8.2.0",
17
+ "ref": "v8.3.0",
18
18
  "source": "git-subdir",
19
19
  "url": "https://github.com/kdeldycke/repomatic"
20
20
  },
@@ -25,7 +25,7 @@
25
25
  "github-actions",
26
26
  "release-automation"
27
27
  ],
28
- "version": "8.2.0"
28
+ "version": "8.3.0"
29
29
  }
30
30
  ]
31
31
  }
@@ -79,7 +79,7 @@ jobs:
79
79
  - name: Open or update the squash-merge issue, then fail
80
80
  env:
81
81
  GH_TOKEN: ${{ github.token }}
82
- run: uvx --no-progress --exclude-newer-package repomatic=P0D 'repomatic==8.2.0' squashed-release
82
+ run: uvx --no-progress --exclude-newer-package repomatic=P0D 'repomatic==8.3.0' squashed-release
83
83
 
84
84
  metadata:
85
85
  name: 🧬 Project metadata
@@ -99,7 +99,7 @@ jobs:
99
99
  - name: Run repomatic show-metadata
100
100
  id: metadata
101
101
  run: >
102
- uvx --no-progress --exclude-newer-package repomatic=P0D 'repomatic==8.2.0' show-metadata
102
+ uvx --no-progress --exclude-newer-package repomatic=P0D 'repomatic==8.3.0' show-metadata
103
103
  --output-format github-json --output "$GITHUB_OUTPUT"
104
104
  binaries_sync cli_scripts current_version is_python_project is_release_push
105
105
  manpages_asset_name manpages_script new_commits_matrix nuitka_matrix package_name
@@ -129,7 +129,7 @@ jobs:
129
129
  version: "0.13.6"
130
130
  - name: Check dependency sources
131
131
  run: >
132
- uvx --no-progress --exclude-newer-package repomatic=P0D 'repomatic==8.2.0' lint-deps
132
+ uvx --no-progress --exclude-newer-package repomatic=P0D 'repomatic==8.3.0' lint-deps
133
133
  ${{ fromJSON(needs.metadata.outputs.metadata).release_commits_matrix
134
134
  && '--fatal' || '--no-fatal' }}
135
135
 
@@ -176,7 +176,7 @@ jobs:
176
176
  env:
177
177
  COMMIT: ${{ matrix.commit }}
178
178
  run: >
179
- uvx --no-progress 'click-extra==10.1.1'
179
+ uvx --no-progress 'click-extra==10.2.0'
180
180
  prebake field git_tag_sha "${COMMIT}"
181
181
  - name: Build package
182
182
  run: uv --no-progress build