repomatic 8.2.0__tar.gz → 8.3.1__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 (713) hide show
  1. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/.claude-plugin/plugin.json +1 -1
  2. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/agents/sphinx-docs.md +5 -3
  3. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/babysit-ci/SKILL.md +12 -12
  4. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/babysit-ci/references/failure-patterns.md +5 -3
  5. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/file-bug-report/SKILL.md +6 -2
  6. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/probe-workflow/SKILL.md +2 -1
  7. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/repomatic-changelog/SKILL.md +2 -1
  8. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/repomatic-ship/SKILL.md +17 -11
  9. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/repomatic-ship/references/findings-in-repomatic.md +2 -0
  10. repomatic-8.3.1/.claude/skills/repomatic-ship/references/short-ship.md +13 -0
  11. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/repomatic-upgrade/SKILL.md +47 -18
  12. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.claude}/skills/sphinx-docs-sync/SKILL.md +1 -1
  13. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/upstream-audit/SKILL.md +10 -7
  14. {repomatic-8.2.0 → repomatic-8.3.1}/.claude-plugin/marketplace.json +2 -2
  15. {repomatic-8.2.0 → repomatic-8.3.1}/.github/workflows/_release-build.yaml +4 -4
  16. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/_release-engine.yaml +18 -18
  17. {repomatic-8.2.0 → repomatic-8.3.1}/.github/workflows/autofix.yaml +39 -39
  18. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/autolock.yaml +1 -1
  19. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/cancel-runs.yaml +1 -1
  20. {repomatic-8.2.0 → repomatic-8.3.1}/.github/workflows/changelog.yaml +11 -11
  21. {repomatic-8.2.0 → repomatic-8.3.1}/.github/workflows/debug.yaml +1 -1
  22. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/docs.yaml +8 -7
  23. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/labels.yaml +5 -5
  24. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/lint.yaml +11 -11
  25. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/metrics.yaml +2 -2
  26. {repomatic-8.2.0 → repomatic-8.3.1}/.github/workflows/release.yaml +1 -1
  27. {repomatic-8.2.0 → repomatic-8.3.1}/.github/workflows/self-maintenance.yaml +3 -3
  28. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/tests.yaml +2 -2
  29. {repomatic-8.2.0/repomatic/data → repomatic-8.3.1/.github/workflows}/unsubscribe.yaml +1 -1
  30. {repomatic-8.2.0 → repomatic-8.3.1}/PKG-INFO +2 -2
  31. {repomatic-8.2.0 → repomatic-8.3.1}/changelog.md +57 -3
  32. {repomatic-8.2.0 → repomatic-8.3.1}/docs/agent-skills.md +3 -3
  33. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/binaries.csv +12 -0
  34. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/dependencies.mmd +1 -1
  35. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/help-dark-screen.svg +6 -6
  36. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/help-light-screen.svg +6 -6
  37. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/virustotal-scans.csv +12 -0
  38. {repomatic-8.2.0 → repomatic-8.3.1}/docs/binaries.md +1 -1
  39. {repomatic-8.2.0 → repomatic-8.3.1}/docs/claude-code-plugin.md +4 -4
  40. {repomatic-8.2.0 → repomatic-8.3.1}/docs/conf.py +9 -8
  41. {repomatic-8.2.0 → repomatic-8.3.1}/docs/configuration.md +1 -1
  42. {repomatic-8.2.0 → repomatic-8.3.1}/docs/install.md +6 -6
  43. {repomatic-8.2.0 → repomatic-8.3.1}/docs/operation-contracts.md +1 -1
  44. {repomatic-8.2.0 → repomatic-8.3.1}/docs/security.md +2 -2
  45. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tool-runner.md +5 -15
  46. {repomatic-8.2.0 → repomatic-8.3.1}/docs/upstream-development.md +1 -1
  47. {repomatic-8.2.0 → repomatic-8.3.1}/docs/upstream.md +7 -8
  48. {repomatic-8.2.0 → repomatic-8.3.1}/docs/workflows.md +9 -8
  49. {repomatic-8.2.0 → repomatic-8.3.1}/pyproject.toml +9 -12
  50. {repomatic-8.2.0 → repomatic-8.3.1}/pyproject.toml.orig +20 -17
  51. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/__init__.py +2 -2
  52. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cache.py +14 -2
  53. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/ci.py +13 -7
  54. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/github.py +109 -0
  55. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/main.py +1 -0
  56. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/repo.py +14 -11
  57. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/config.py +11 -6
  58. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/_release-engine.yaml +18 -18
  59. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/agent-sphinx-docs.md +5 -3
  60. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/autofix.yaml +39 -39
  61. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/autolock.yaml +1 -1
  62. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/.github/contributing.md +2 -2
  63. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/.github/contributing.zh.md +2 -2
  64. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/cancel-runs.yaml +1 -1
  65. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/changelog.yaml +11 -11
  66. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/debug.yaml +1 -1
  67. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/docs.yaml +8 -7
  68. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/labels.yaml +5 -5
  69. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/lint.yaml +11 -11
  70. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/metrics.yaml +2 -2
  71. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/octicons.toml +2 -0
  72. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/release.yaml +1 -1
  73. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/babysit-ci/SKILL.md +12 -12
  74. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/babysit-ci/references/failure-patterns.md +5 -3
  75. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/file-bug-report/SKILL.md +6 -2
  76. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/probe-workflow/SKILL.md +2 -1
  77. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/repomatic-changelog/SKILL.md +2 -1
  78. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/repomatic-ship/SKILL.md +17 -11
  79. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/repomatic-ship/references/findings-in-repomatic.md +2 -0
  80. repomatic-8.3.1/repomatic/data/skills/repomatic-ship/references/short-ship.md +13 -0
  81. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/repomatic-upgrade/SKILL.md +47 -18
  82. {repomatic-8.2.0/.claude → repomatic-8.3.1/repomatic/data}/skills/sphinx-docs-sync/SKILL.md +1 -1
  83. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/upstream-audit/SKILL.md +10 -7
  84. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/tests.yaml +2 -2
  85. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/typos.toml +4 -0
  86. {repomatic-8.2.0/.github/workflows → repomatic-8.3.1/repomatic/data}/unsubscribe.yaml +1 -1
  87. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/cooldown.py +37 -13
  88. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/lockfile.py +40 -0
  89. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/pins.py +83 -9
  90. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/provenance.py +48 -22
  91. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/report.py +22 -15
  92. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/file_inventory.py +4 -4
  93. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/git_ops.py +77 -2
  94. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/ci_status.py +128 -21
  95. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/event.py +18 -0
  96. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/gh.py +112 -21
  97. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/issue.py +4 -1
  98. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/outputs.py +8 -0
  99. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/pr.py +15 -10
  100. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/releases.py +30 -24
  101. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/init/local_edits.py +12 -10
  102. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/init/run.py +122 -17
  103. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/init/upgrade.py +73 -51
  104. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_changelog.py +2 -2
  105. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/roster.py +36 -1
  106. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/site.py +6 -5
  107. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/tool_config.py +77 -0
  108. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/matrix/model.py +6 -2
  109. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metadata/matrix.py +4 -2
  110. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/pypi.py +103 -41
  111. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/virustotal.py +2 -1
  112. repomatic-8.3.1/repomatic/templates/upgrade-invite.md +12 -0
  113. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/tooling/registry.py +29 -29
  114. {repomatic-8.2.0 → repomatic-8.3.1}/tests/cli-test-suite.toml +6 -0
  115. {repomatic-8.2.0 → repomatic-8.3.1}/tests/conftest.py +33 -0
  116. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_awesome_template.py +29 -0
  117. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_broken_links.py +0 -1
  118. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_cache.py +21 -0
  119. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_ci_status.py +153 -3
  120. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_cli.py +0 -4
  121. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_docstrings.py +4 -4
  122. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_event.py +31 -0
  123. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_gh.py +103 -2
  124. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_git_ops.py +54 -0
  125. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_init_project.py +292 -20
  126. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_issue.py +94 -0
  127. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_labels.py +45 -2
  128. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_lint_changelog.py +2 -4
  129. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_lint_repo.py +99 -2
  130. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_matrix.py +14 -0
  131. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_metadata.py +8 -7
  132. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_pr.py +2 -0
  133. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_provenance.py +237 -53
  134. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_releases.py +13 -9
  135. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_uv.py +79 -28
  136. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_version_sync.py +94 -0
  137. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_virustotal.py +1 -0
  138. {repomatic-8.2.0 → repomatic-8.3.1}/uv.lock +267 -187
  139. repomatic-8.2.0/.claude/skills/repomatic-ship/references/short-ship.md +0 -15
  140. repomatic-8.2.0/repomatic/data/skills/repomatic-ship/references/short-ship.md +0 -15
  141. repomatic-8.2.0/repomatic/templates/upgrade-invite.md +0 -12
  142. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/agents/grunt-qa.md +0 -0
  143. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/agents/qa-engineer.md +0 -0
  144. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/av-false-positive/SKILL.md +0 -0
  145. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/awesome-triage/SKILL.md +0 -0
  146. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/benchmark-update/SKILL.md +0 -0
  147. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/brand-assets/SKILL.md +0 -0
  148. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/github-housekeeping/SKILL.md +0 -0
  149. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/repomatic-deps/SKILL.md +0 -0
  150. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/repomatic-init/SKILL.md +0 -0
  151. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/repomatic-ship/references/deep-pass.md +0 -0
  152. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/repomatic-test-matrix/SKILL.md +0 -0
  153. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/repomatic-topics/SKILL.md +0 -0
  154. {repomatic-8.2.0 → repomatic-8.3.1}/.claude/skills/translation-sync/SKILL.md +0 -0
  155. {repomatic-8.2.0 → repomatic-8.3.1}/.github/ISSUE_TEMPLATE/bug-report.yml +0 -0
  156. {repomatic-8.2.0 → repomatic-8.3.1}/.github/actions/publish-pypi/action.yaml +0 -0
  157. {repomatic-8.2.0 → repomatic-8.3.1}/.github/code-of-conduct.md +0 -0
  158. {repomatic-8.2.0 → repomatic-8.3.1}/.github/funding.yml +0 -0
  159. {repomatic-8.2.0 → repomatic-8.3.1}/.gitignore +0 -0
  160. {repomatic-8.2.0 → repomatic-8.3.1}/.mailmap +0 -0
  161. {repomatic-8.2.0 → repomatic-8.3.1}/AGENTS.md +0 -0
  162. {repomatic-8.2.0 → repomatic-8.3.1}/docs/404.html +0 -0
  163. {repomatic-8.2.0 → repomatic-8.3.1}/docs/_redirects +0 -0
  164. {repomatic-8.2.0 → repomatic-8.3.1}/docs/_static/custom.css +0 -0
  165. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/banner-social-dark.png +0 -0
  166. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/banner-social-light.png +0 -0
  167. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/banner-social.svg +0 -0
  168. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/config-snippet-screen.svg +0 -0
  169. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/desktop-autosync-warning.png +0 -0
  170. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/desktop-plugin-agents.png +0 -0
  171. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/desktop-plugin-contents.png +0 -0
  172. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/desktop-plugin-skills.png +0 -0
  173. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/favicon.svg +0 -0
  174. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/icon.icns +0 -0
  175. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/icon.ico +0 -0
  176. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/icon.png +0 -0
  177. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/logo-banner-dark.png +0 -0
  178. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/logo-banner-light.png +0 -0
  179. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/logo-banner.svg +0 -0
  180. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/logo-square-dark.png +0 -0
  181. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/logo-square-light.png +0 -0
  182. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/logo-square.svg +0 -0
  183. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/matrix-grid-screen.svg +0 -0
  184. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/metrics.csv +0 -0
  185. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/star-history-compared.svg +0 -0
  186. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/star-history.svg +0 -0
  187. {repomatic-8.2.0 → repomatic-8.3.1}/docs/assets/sync-deps-trail-screen.svg +0 -0
  188. {repomatic-8.2.0 → repomatic-8.3.1}/docs/benchmark.md +0 -0
  189. {repomatic-8.2.0 → repomatic-8.3.1}/docs/changelog-archive.md +0 -0
  190. {repomatic-8.2.0 → repomatic-8.3.1}/docs/changelog.md +0 -0
  191. {repomatic-8.2.0 → repomatic-8.3.1}/docs/cli.md +0 -0
  192. {repomatic-8.2.0 → repomatic-8.3.1}/docs/cloudflare.md +0 -0
  193. {repomatic-8.2.0 → repomatic-8.3.1}/docs/code-of-conduct.md +0 -0
  194. {repomatic-8.2.0 → repomatic-8.3.1}/docs/commit-messages.md +0 -0
  195. {repomatic-8.2.0 → repomatic-8.3.1}/docs/contributing.md +0 -0
  196. {repomatic-8.2.0 → repomatic-8.3.1}/docs/dependencies.md +0 -0
  197. {repomatic-8.2.0 → repomatic-8.3.1}/docs/docs_update.py +0 -0
  198. {repomatic-8.2.0 → repomatic-8.3.1}/docs/history.md +0 -0
  199. {repomatic-8.2.0 → repomatic-8.3.1}/docs/index.md +0 -0
  200. {repomatic-8.2.0 → repomatic-8.3.1}/docs/license.md +0 -0
  201. {repomatic-8.2.0 → repomatic-8.3.1}/docs/man.md +0 -0
  202. {repomatic-8.2.0 → repomatic-8.3.1}/docs/nuitka.md +0 -0
  203. {repomatic-8.2.0 → repomatic-8.3.1}/docs/packaging.md +0 -0
  204. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.awesome_toc.md +0 -0
  205. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.broken_links.md +0 -0
  206. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.bundle.md +0 -0
  207. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cache.md +0 -0
  208. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.changelog.md +0 -0
  209. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.checks.md +0 -0
  210. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.claude_plugin.md +0 -0
  211. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.ci.md +0 -0
  212. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.deps.md +0 -0
  213. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.github.md +0 -0
  214. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.main.md +0 -0
  215. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.md +0 -0
  216. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.release.md +0 -0
  217. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.repo.md +0 -0
  218. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.site.md +0 -0
  219. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cli.tools.md +0 -0
  220. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cloudflare.api.md +0 -0
  221. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cloudflare.md +0 -0
  222. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cloudflare.pages.md +0 -0
  223. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cloudflare.r2.md +0 -0
  224. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.cloudflare.redirects.md +0 -0
  225. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.components.md +0 -0
  226. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.config.md +0 -0
  227. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.data.awesome_template.md +0 -0
  228. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.data.md +0 -0
  229. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.audit.md +0 -0
  230. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.cooldown.md +0 -0
  231. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.graph.md +0 -0
  232. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.lockfile.md +0 -0
  233. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.md +0 -0
  234. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.pins.md +0 -0
  235. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.policy.md +0 -0
  236. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.provenance.md +0 -0
  237. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.report.md +0 -0
  238. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.requirements.md +0 -0
  239. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.shippable.md +0 -0
  240. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.sources.md +0 -0
  241. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.sync.md +0 -0
  242. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.deps.uv.md +0 -0
  243. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.docs.md +0 -0
  244. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.file_inventory.md +0 -0
  245. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.file_ops.md +0 -0
  246. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.frontmatter.md +0 -0
  247. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.git_ops.md +0 -0
  248. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.caches.md +0 -0
  249. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.ci_status.md +0 -0
  250. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.dev_release.md +0 -0
  251. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.event.md +0 -0
  252. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.gh.md +0 -0
  253. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.issue.md +0 -0
  254. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.job_timings.md +0 -0
  255. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.labels.md +0 -0
  256. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.md +0 -0
  257. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.outputs.md +0 -0
  258. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.pr.md +0 -0
  259. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.pr_body.md +0 -0
  260. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.release_sync.md +0 -0
  261. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.releases.md +0 -0
  262. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.runs.md +0 -0
  263. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.sponsor.md +0 -0
  264. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.status.md +0 -0
  265. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.threads.md +0 -0
  266. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.token.md +0 -0
  267. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.unsubscribe.md +0 -0
  268. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.urls.md +0 -0
  269. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.workflow_files.md +0 -0
  270. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.github.workflow_sync.md +0 -0
  271. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.gitignore.md +0 -0
  272. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.hashing.md +0 -0
  273. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.http.md +0 -0
  274. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.humanize.md +0 -0
  275. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.images.md +0 -0
  276. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.init.local_edits.md +0 -0
  277. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.init.md +0 -0
  278. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.init.removed_assets.md +0 -0
  279. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.init.run.md +0 -0
  280. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.init.tool_config.md +0 -0
  281. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.init.upgrade.md +0 -0
  282. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_changelog.md +0 -0
  283. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.context.md +0 -0
  284. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.md +0 -0
  285. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.pins.md +0 -0
  286. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.repo.md +0 -0
  287. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.roster.md +0 -0
  288. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.settings.md +0 -0
  289. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.site.md +0 -0
  290. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.tool_config.md +0 -0
  291. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.lint_repo.workflows.md +0 -0
  292. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.mailmap.md +0 -0
  293. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.markdown.md +0 -0
  294. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.matrix.axes.md +0 -0
  295. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.matrix.md +0 -0
  296. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.matrix.model.md +0 -0
  297. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.matrix.runner_sync.md +0 -0
  298. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.matrix.runners.md +0 -0
  299. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.md +0 -0
  300. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metadata.core.md +0 -0
  301. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metadata.env.md +0 -0
  302. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metadata.git.md +0 -0
  303. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metadata.matrix.md +0 -0
  304. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metadata.md +0 -0
  305. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metadata.output.md +0 -0
  306. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metadata.project.md +0 -0
  307. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metrics.chart.md +0 -0
  308. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metrics.forge.md +0 -0
  309. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metrics.md +0 -0
  310. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.metrics.store.md +0 -0
  311. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.npm.md +0 -0
  312. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.pypi.md +0 -0
  313. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.pyproject.md +0 -0
  314. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.attestation.md +0 -0
  315. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.binaries_page.md +0 -0
  316. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.binary.md +0 -0
  317. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.manpages.md +0 -0
  318. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.md +0 -0
  319. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.prepare_release.md +0 -0
  320. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.protocol.md +0 -0
  321. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.self_pin.md +0 -0
  322. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.verify.md +0 -0
  323. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.release.virustotal.md +0 -0
  324. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.setup_guide.md +0 -0
  325. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.skills.md +0 -0
  326. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.tabular.md +0 -0
  327. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.templates.md +0 -0
  328. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.templating.md +0 -0
  329. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.tooling.binaries.md +0 -0
  330. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.tooling.checksums.md +0 -0
  331. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.tooling.md +0 -0
  332. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.tooling.nuitka.md +0 -0
  333. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.tooling.registry.md +0 -0
  334. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.tooling.runner.md +0 -0
  335. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.upstream.md +0 -0
  336. {repomatic-8.2.0 → repomatic-8.3.1}/docs/repomatic.versions.md +0 -0
  337. {repomatic-8.2.0 → repomatic-8.3.1}/docs/robots.txt +0 -0
  338. {repomatic-8.2.0 → repomatic-8.3.1}/docs/subagent-grunt-qa.md +0 -0
  339. {repomatic-8.2.0 → repomatic-8.3.1}/docs/subagent-qa-engineer.md +0 -0
  340. {repomatic-8.2.0 → repomatic-8.3.1}/docs/subagent-sphinx-docs.md +0 -0
  341. {repomatic-8.2.0 → repomatic-8.3.1}/docs/subagents.md +0 -0
  342. {repomatic-8.2.0 → repomatic-8.3.1}/docs/test-matrix.md +0 -0
  343. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.conftest.md +0 -0
  344. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.md +0 -0
  345. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_attestation.md +0 -0
  346. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_awesome_template.md +0 -0
  347. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_awesome_toc.md +0 -0
  348. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_binaries.md +0 -0
  349. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_binaries_page.md +0 -0
  350. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_binary.md +0 -0
  351. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_broken_links.md +0 -0
  352. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_cache.md +0 -0
  353. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_changelog.md +0 -0
  354. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_checks.md +0 -0
  355. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_checksums.md +0 -0
  356. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_ci_status.md +0 -0
  357. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_claude_assets.md +0 -0
  358. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_cli.md +0 -0
  359. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_cloudflare.md +0 -0
  360. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_cloudflare_r2.md +0 -0
  361. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_config.md +0 -0
  362. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_coverage_floor.md +0 -0
  363. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_dep_graph.md +0 -0
  364. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_dep_policy.md +0 -0
  365. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_dep_report.md +0 -0
  366. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_dep_sources.md +0 -0
  367. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_dev_release.md +0 -0
  368. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_docs.md +0 -0
  369. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_docstrings.md +0 -0
  370. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_event.md +0 -0
  371. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_file_ops.md +0 -0
  372. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_forge.md +0 -0
  373. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_frontmatter.md +0 -0
  374. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_gh.md +0 -0
  375. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_git_ops.md +0 -0
  376. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_github_caches.md +0 -0
  377. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_gitignore.md +0 -0
  378. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_hashing.md +0 -0
  379. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_help.md +0 -0
  380. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_http.md +0 -0
  381. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_humanize.md +0 -0
  382. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_images.md +0 -0
  383. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_imports.md +0 -0
  384. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_init_project.md +0 -0
  385. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_issue.md +0 -0
  386. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_job_timings.md +0 -0
  387. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_labels.md +0 -0
  388. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_lint_changelog.md +0 -0
  389. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_lint_repo.md +0 -0
  390. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_mailmap.md +0 -0
  391. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_manpages.md +0 -0
  392. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_markdown.md +0 -0
  393. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_matrix.md +0 -0
  394. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_metadata.md +0 -0
  395. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_metadata_git.md +0 -0
  396. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_metrics.md +0 -0
  397. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_npm.md +0 -0
  398. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_nuitka.md +0 -0
  399. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_outputs.md +0 -0
  400. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_pages_redirects.md +0 -0
  401. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_platform_keys.md +0 -0
  402. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_plugin.md +0 -0
  403. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_plugin_update_detection.md +0 -0
  404. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_pr.md +0 -0
  405. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_pr_body.md +0 -0
  406. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_prepare_release.md +0 -0
  407. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_protocol.md +0 -0
  408. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_provenance.md +0 -0
  409. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_pypi.md +0 -0
  410. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_pyproject.md +0 -0
  411. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_readme.md +0 -0
  412. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_release_sync.md +0 -0
  413. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_release_workflow_steps.md +0 -0
  414. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_releases.md +0 -0
  415. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_runner_catalog.md +0 -0
  416. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_runner_sync.md +0 -0
  417. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_runs.md +0 -0
  418. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_self_pin.md +0 -0
  419. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_setup_guide.md +0 -0
  420. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_skills.md +0 -0
  421. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_sphinx_crossrefs.md +0 -0
  422. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_sponsor.md +0 -0
  423. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_status.md +0 -0
  424. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_suite_hygiene.md +0 -0
  425. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_sync_ops.md +0 -0
  426. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_tabular.md +0 -0
  427. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_templating.md +0 -0
  428. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_threads.md +0 -0
  429. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_todolist.md +0 -0
  430. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_token.md +0 -0
  431. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_tool_runner.md +0 -0
  432. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_unsubscribe.md +0 -0
  433. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_upstream.md +0 -0
  434. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_urls.md +0 -0
  435. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_uv.md +0 -0
  436. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_verify.md +0 -0
  437. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_version_sync.md +0 -0
  438. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_versions.md +0 -0
  439. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_virustotal.md +0 -0
  440. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_vulnerable_deps.md +0 -0
  441. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_workflow_files.md +0 -0
  442. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_workflow_sync.md +0 -0
  443. {repomatic-8.2.0 → repomatic-8.3.1}/docs/tests.test_workflows.md +0 -0
  444. {repomatic-8.2.0 → repomatic-8.3.1}/docs/todolist.md +0 -0
  445. {repomatic-8.2.0 → repomatic-8.3.1}/license +0 -0
  446. {repomatic-8.2.0 → repomatic-8.3.1}/readme.md +0 -0
  447. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/__main__.py +0 -0
  448. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/awesome_toc.py +0 -0
  449. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/broken_links.py +0 -0
  450. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/bundle.py +0 -0
  451. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/changelog.py +0 -0
  452. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/checks.py +0 -0
  453. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/claude_plugin.py +0 -0
  454. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/__init__.py +0 -0
  455. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/deps.py +0 -0
  456. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/release.py +0 -0
  457. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/site.py +0 -0
  458. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cli/tools.py +0 -0
  459. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cloudflare/__init__.py +0 -0
  460. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cloudflare/api.py +0 -0
  461. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cloudflare/pages.py +0 -0
  462. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cloudflare/r2.py +0 -0
  463. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/cloudflare/redirects.py +0 -0
  464. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/components.py +0 -0
  465. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/__init__.py +0 -0
  466. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/action-publish-pypi.yaml +0 -0
  467. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/actionlint-matcher.json +0 -0
  468. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/actionlint.yaml +0 -0
  469. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/agent-grunt-qa.md +0 -0
  470. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/agent-qa-engineer.md +0 -0
  471. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/.github/ISSUE_TEMPLATE/config.yml +0 -0
  472. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/.github/ISSUE_TEMPLATE/new-link.yaml +0 -0
  473. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/.github/code-of-conduct.md +0 -0
  474. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/.github/funding.yml +0 -0
  475. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/.github/pull_request_template.md +0 -0
  476. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/__init__.py +0 -0
  477. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/awesome_template/license +0 -0
  478. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/bumpversion.toml +0 -0
  479. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/coverage.toml +0 -0
  480. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/labels.toml +0 -0
  481. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/lychee.toml +0 -0
  482. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/mdformat.toml +0 -0
  483. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/mypy.toml +0 -0
  484. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/pytest.toml +0 -0
  485. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/ruff.toml +0 -0
  486. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/av-false-positive/SKILL.md +0 -0
  487. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/awesome-triage/SKILL.md +0 -0
  488. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/benchmark-update/SKILL.md +0 -0
  489. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/brand-assets/SKILL.md +0 -0
  490. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/github-housekeeping/SKILL.md +0 -0
  491. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/repomatic-deps/SKILL.md +0 -0
  492. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/repomatic-init/SKILL.md +0 -0
  493. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/repomatic-ship/references/deep-pass.md +0 -0
  494. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/repomatic-test-matrix/SKILL.md +0 -0
  495. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/repomatic-topics/SKILL.md +0 -0
  496. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/skills/translation-sync/SKILL.md +0 -0
  497. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/uv.toml +0 -0
  498. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/vt-trend-chart.js +0 -0
  499. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/yamllint.yaml +0 -0
  500. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/data/zizmor.yaml +0 -0
  501. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/__init__.py +0 -0
  502. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/audit.py +0 -0
  503. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/graph.py +0 -0
  504. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/policy.py +0 -0
  505. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/requirements.py +0 -0
  506. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/shippable.py +0 -0
  507. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/sources.py +0 -0
  508. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/sync.py +0 -0
  509. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/deps/uv.py +0 -0
  510. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/docs.py +0 -0
  511. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/file_ops.py +0 -0
  512. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/frontmatter.py +0 -0
  513. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/__init__.py +0 -0
  514. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/caches.py +0 -0
  515. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/dev_release.py +0 -0
  516. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/job_timings.py +0 -0
  517. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/labels.py +0 -0
  518. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/pr_body.py +0 -0
  519. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/release_sync.py +0 -0
  520. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/runs.py +0 -0
  521. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/sponsor.py +0 -0
  522. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/status.py +0 -0
  523. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/threads.py +0 -0
  524. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/token.py +0 -0
  525. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/unsubscribe.py +0 -0
  526. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/urls.py +0 -0
  527. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/workflow_files.py +0 -0
  528. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/github/workflow_sync.py +0 -0
  529. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/gitignore.py +0 -0
  530. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/hashing.py +0 -0
  531. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/http.py +0 -0
  532. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/humanize.py +0 -0
  533. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/images.py +0 -0
  534. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/init/__init__.py +0 -0
  535. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/init/removed_assets.py +0 -0
  536. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/init/tool_config.py +0 -0
  537. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/__init__.py +0 -0
  538. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/context.py +0 -0
  539. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/pins.py +0 -0
  540. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/repo.py +0 -0
  541. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/settings.py +0 -0
  542. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/lint_repo/workflows.py +0 -0
  543. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/mailmap.py +0 -0
  544. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/markdown.py +0 -0
  545. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/matrix/__init__.py +0 -0
  546. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/matrix/axes.py +0 -0
  547. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/matrix/runner_sync.py +0 -0
  548. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/matrix/runners.py +0 -0
  549. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metadata/__init__.py +0 -0
  550. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metadata/core.py +0 -0
  551. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metadata/env.py +0 -0
  552. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metadata/git.py +0 -0
  553. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metadata/output.py +0 -0
  554. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metadata/project.py +0 -0
  555. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metrics/__init__.py +0 -0
  556. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metrics/chart.py +0 -0
  557. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metrics/forge.py +0 -0
  558. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/metrics/store.py +0 -0
  559. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/npm.py +0 -0
  560. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/py.typed +0 -0
  561. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/pyproject.py +0 -0
  562. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/__init__.py +0 -0
  563. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/attestation.py +0 -0
  564. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/binaries_page.py +0 -0
  565. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/binary.py +0 -0
  566. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/manpages.py +0 -0
  567. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/prepare_release.py +0 -0
  568. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/protocol.py +0 -0
  569. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/self_pin.py +0 -0
  570. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/release/verify.py +0 -0
  571. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/setup_guide.py +0 -0
  572. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/skills.py +0 -0
  573. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/tabular.py +0 -0
  574. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/__init__.py +0 -0
  575. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/available-admonition.md +0 -0
  576. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/broken-links-issue.md +0 -0
  577. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/bump-version.md +0 -0
  578. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/development-warning.md +0 -0
  579. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/fix-changelog.md +0 -0
  580. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/fix-typos.md +0 -0
  581. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/fix-vulnerable-deps.md +0 -0
  582. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/format-images.md +0 -0
  583. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/format-json.md +0 -0
  584. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/format-markdown.md +0 -0
  585. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/format-pyproject.md +0 -0
  586. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/format-python.md +0 -0
  587. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/format-shell.md +0 -0
  588. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/generated-footer.md +0 -0
  589. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/github-releases.md +0 -0
  590. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/immutable-releases.md +0 -0
  591. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/pr-metadata.md.noformat +0 -0
  592. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/prepare-release.md.noformat +0 -0
  593. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/refresh-tip.md +0 -0
  594. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/release-notes.md +0 -0
  595. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/release-sync-report.md.noformat +0 -0
  596. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sample-metrics.md +0 -0
  597. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/scan-virustotal.md +0 -0
  598. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-branch-ruleset.md +0 -0
  599. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-cloudflare-pages.md +0 -0
  600. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-cloudflare-r2.md +0 -0
  601. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-dependabot.md +0 -0
  602. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-fork-pr-approval.md +0 -0
  603. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-notifications-pat.md +0 -0
  604. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-pages-source.md +0 -0
  605. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-pypi-trusted-publisher.md +0 -0
  606. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-sha-pinning-required.md +0 -0
  607. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-token.md +0 -0
  608. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-verify.md +0 -0
  609. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide-virustotal.md +0 -0
  610. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/setup-guide.md +0 -0
  611. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/squashed-release.md +0 -0
  612. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-action-pins.md +0 -0
  613. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-bumpversion.md +0 -0
  614. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-dep-sources.md +0 -0
  615. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-gitignore.md +0 -0
  616. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-mailmap.md +0 -0
  617. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-repomatic-upgrade.md +0 -0
  618. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-repomatic.md +0 -0
  619. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-runner-images.md +0 -0
  620. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-tool-versions.md +0 -0
  621. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-uv-lock.md +0 -0
  622. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/sync-workflow-pins.md +0 -0
  623. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/unavailable-admonition.md +0 -0
  624. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/unsubscribe-report.md +0 -0
  625. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/update-dep-graph.md +0 -0
  626. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/update-docs.md +0 -0
  627. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templates/yanked-admonition.md +0 -0
  628. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/templating.py +0 -0
  629. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/tooling/__init__.py +0 -0
  630. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/tooling/binaries.py +0 -0
  631. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/tooling/checksums.py +0 -0
  632. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/tooling/nuitka.py +0 -0
  633. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/tooling/runner.py +0 -0
  634. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/upstream.py +0 -0
  635. {repomatic-8.2.0 → repomatic-8.3.1}/repomatic/versions.py +0 -0
  636. {repomatic-8.2.0 → repomatic-8.3.1}/tests/__init__.py +0 -0
  637. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_attestation.py +0 -0
  638. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_awesome_toc.py +0 -0
  639. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_binaries.py +0 -0
  640. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_binaries_page.py +0 -0
  641. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_binary.py +0 -0
  642. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_changelog.py +0 -0
  643. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_checks.py +0 -0
  644. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_checksums.py +0 -0
  645. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_claude_assets.py +0 -0
  646. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_cloudflare.py +0 -0
  647. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_cloudflare_r2.py +0 -0
  648. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_config.py +0 -0
  649. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_coverage_floor.py +0 -0
  650. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_dep_graph.py +0 -0
  651. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_dep_policy.py +0 -0
  652. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_dep_report.py +0 -0
  653. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_dep_sources.py +0 -0
  654. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_dev_release.py +0 -0
  655. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_docs.py +0 -0
  656. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_file_ops.py +0 -0
  657. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_forge.py +0 -0
  658. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_frontmatter.py +0 -0
  659. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_github_caches.py +0 -0
  660. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_gitignore.py +0 -0
  661. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_hashing.py +0 -0
  662. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_help.py +0 -0
  663. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_http.py +0 -0
  664. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_humanize.py +0 -0
  665. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_images.py +0 -0
  666. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_imports.py +0 -0
  667. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_job_timings.py +0 -0
  668. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_mailmap.py +0 -0
  669. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_manpages.py +0 -0
  670. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_markdown.py +0 -0
  671. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_metadata_git.py +0 -0
  672. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_metrics.py +0 -0
  673. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_npm.py +0 -0
  674. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_nuitka.py +0 -0
  675. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_outputs.py +0 -0
  676. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_pages_redirects.py +0 -0
  677. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_platform_keys.py +0 -0
  678. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_plugin.py +0 -0
  679. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_plugin_update_detection.py +0 -0
  680. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_pr_body.py +0 -0
  681. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_prepare_release.py +0 -0
  682. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_protocol.py +0 -0
  683. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_pypi.py +0 -0
  684. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_pyproject.py +0 -0
  685. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_readme.py +0 -0
  686. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_release_sync.py +0 -0
  687. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_release_workflow_steps.py +0 -0
  688. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_runner_catalog.py +0 -0
  689. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_runner_sync.py +0 -0
  690. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_runs.py +0 -0
  691. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_self_pin.py +0 -0
  692. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_setup_guide.py +0 -0
  693. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_skills.py +0 -0
  694. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_sphinx_crossrefs.py +0 -0
  695. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_sponsor.py +0 -0
  696. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_status.py +0 -0
  697. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_suite_hygiene.py +0 -0
  698. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_sync_ops.py +0 -0
  699. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_tabular.py +0 -0
  700. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_templating.py +0 -0
  701. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_threads.py +0 -0
  702. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_todolist.py +0 -0
  703. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_token.py +0 -0
  704. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_tool_runner.py +0 -0
  705. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_unsubscribe.py +0 -0
  706. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_upstream.py +0 -0
  707. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_urls.py +0 -0
  708. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_verify.py +0 -0
  709. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_versions.py +0 -0
  710. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_vulnerable_deps.py +0 -0
  711. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_workflow_files.py +0 -0
  712. {repomatic-8.2.0 → repomatic-8.3.1}/tests/test_workflow_sync.py +0 -0
  713. {repomatic-8.2.0 → repomatic-8.3.1}/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.1"
24
24
  }
@@ -571,6 +571,7 @@ Every top-level page heading uses an `{octicon}` icon for visual scanning: `` #
571
571
  | {octicon}`beaker` `beaker` | `test-suite.md` |
572
572
  | {octicon}`book` `book` | `man.md`, `sphinx.md` |
573
573
  | {octicon}`broadcast` `broadcast` | `telemetry.md` |
574
+ | {octicon}`bug` `bug` | `bug-report.md` |
574
575
  | {octicon}`checklist` `checklist` | `operation-contracts.md` |
575
576
  | {octicon}`chevron-right` `chevron-right` | `carapace.md`, `shells.md` |
576
577
  | {octicon}`circle-slash` `circle-slash` | `unsupported.md` |
@@ -605,6 +606,7 @@ Every top-level page heading uses an `{octicon}` icon for visual scanning: `` #
605
606
  | {octicon}`globe` `globe` | `infrastructure.md` |
606
607
  | {octicon}`history` `history` | `changelog-archive.md`, `cooldown.md` |
607
608
  | {octicon}`image` `image` | `snippets.md` |
609
+ | {octicon}`inbox` `inbox` | `formats.md` |
608
610
  | {octicon}`iterations` `iterations` | `version.md` |
609
611
  | {octicon}`key` `key` | `sudo.md` |
610
612
  | {octicon}`law` `law` | `license.md` |
@@ -679,7 +681,7 @@ Default-pruning rule:
679
681
 
680
682
  - If a setting equals its Sphinx (or extension) default, delete it. Don't comment it out — `git blame` already records intent.
681
683
  - If you keep a setting that *looks* default for documentation purposes, add a one-line comment explaining why ("explicit so future readers see we considered it").
682
- - On every Sphinx or extension upgrade, run `sphinx-build -W -b html docs docs/_build/html`. Treat every `RemovedInSphinxX.YWarning`, `DeprecationWarning`, and `application.ExtensionError` as cleanup work, not noise. Fix them in the same PR as the upgrade.
684
+ - On every Sphinx or extension upgrade, run `sphinx-build -W -b {builder} docs docs/_build/{builder}`, with `{builder}` the `[tool.repomatic] sphinx.builder` value (`html` by default). Treat every `RemovedInSphinxX.YWarning`, `DeprecationWarning`, and `application.ExtensionError` as cleanup work, not noise. Fix them in the same PR as the upgrade.
683
685
  - **Match the deployed builder, which is not always `html`.** `[tool.repomatic] sphinx.builder` is what the Docs workflow passes to `sphinx-build -b`, and a project serving extension-less URLs sets it to `dirhtml` (`page/index.html` instead of `page.html`). Read it before assuming a local `-b html` reproduces CI. The builder is chosen on the command line, so `conf.py` cannot carry it: never "fix" its absence there. `sphinx.fail-on-warning` is the same kind of setting: it adds `--fail-on-warning` to the CI build.
684
686
  - **A warning count only covers the pages that build re-read.** Sphinx reuses cached doctrees, so an incremental rebuild reports the warnings of the changed pages alone, and reading that number against a cold build's count shows a drop nothing caused. A `conf.py` edit invalidates the whole cache, which is why the build right after one reports many more. Build into a clean `_build/` before comparing two counts.
685
687
  - **Compare two builds only when both hold the same dependency groups.** autodoc imports each module it documents. A build that lacks one group fails those imports, like the test group for a `tests` API page, and each reference into such a module then reports as unresolved. Build the baseline from an export of `HEAD` and the candidate from the working tree, both with `uv run --isolated --frozen --all-extras --all-groups`: neither touches the shared virtual environment.
@@ -711,8 +713,8 @@ Extensions list:
711
713
 
712
714
  MyST and theme config:
713
715
 
714
- - `myst_enable_extensions` stays alphabetized. Only enable what the docs actually use; each extension changes parsing rules and can mask MyST/reST mistakes.
715
- - `myst_heading_anchors = 6` paired with `myst_heading_slug_func = "docutils.nodes.make_id"` registers every heading as a resolvable cross-reference target, so in-page `[text](#anchor)` links resolve (and broken ones warn) at build time. Pinning the slug function to docutils' `make_id` keeps MyST anchors identical to the section IDs docutils already emits (`cache.dir` → `cache-dir`), so existing anchor URLs stay stable.
716
+ - `myst_enable_extensions` stays alphabetized. Only enable what the docs actually use; each extension changes parsing rules and can mask MyST/reST mistakes. Text a generator writes at build time counts as use, so prove a removal with a diff of two builds, not a grep of the sources.
717
+ - `myst_heading_anchors = 6` paired with `myst_heading_slug_func = "docutils"` registers every heading as a resolvable cross-reference target, so in-page `[text](#anchor)` links resolve (and broken ones warn) at build time. The `docutils` preset returns the IDs of docutils' `make_id`, so MyST anchors stay identical to the section IDs docutils already emits (`cache.dir` → `cache-dir`), and existing anchor URLs stay stable. The preset needs `myst-parser>=5.2` in the docs group: myst-parser `5.1` reads `"docutils"` as an import path and fails the build. On `5.1`, write the import path `"docutils.nodes.make_id"`, which gives the same IDs.
716
718
  - `html_theme_options` overrides only the values that differ from the theme default. When the theme upgrades and renames or removes an option, the warning appears under `-W`; remove the entry.
717
719
  - Hard-coded HTML strings (announcement banners, footer text) belong in `html_theme_options` only when the theme requires it. If they're long, build them up with f-strings using `project_id`/`github_user` constants defined at the top of `conf.py` so renames stay in one place.
718
720
 
@@ -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. Five 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 finished job can keep the `status` `in_progress` after GitHub set its `conclusion`, so the command reads the conclusion first; 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
 
@@ -37,7 +37,9 @@ When a test passes locally but fails in CI, check platform differences before ch
37
37
  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
- - **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.
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` with no `conclusion` 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.
@@ -60,7 +62,7 @@ For infrastructure, re-run the failed jobs (`gh run rerun <RUN_ID> --failed`) an
60
62
  Heavy polling from this loop spends the same REST quota (5,000 requests/hour) as every workflow authenticating as the same user (`REPOMATIC_PAT`). Exhaustion produces two failure shapes that look unrelated to quotas:
61
63
 
62
64
  - Local `gh` calls fail with `HTTP 403: API rate limit exceeded`.
63
- - Workflows fail with *permission-shaped* errors: `lint-repo` reports the PAT lacks `Contents`/`Dependabot`/`Workflows` scopes, or a `Sync pull request` step (`repomatic pr-sync`) stalls on the GitHub API until its `timeout-minutes` or the concurrency group kills the run.
65
+ - Workflows fail with *permission-shaped* errors: `lint-repo` reports the PAT lacks `Contents`/`Dependabot`/`Workflows` scopes, or a `Sync pull request` step (`repomatic pr-sync`) stalls on the GitHub API until `repomatic` stops the `gh` call after five minutes, or the concurrency group kills the run.
64
66
 
65
67
  Diagnose with `gh api rate_limit` **before** touching token settings: `remaining: 0` on the `core` bucket confirms it. Recovery: wait for the printed `reset` epoch, then re-run the failed workflows unchanged (`gh run rerun <RUN_ID> --failed`); they go green with no commit. While waiting, degrade to the channels that stay live: the GraphQL bucket is metered separately (`gh api graphql` for a commit's check suites, refs, and releases; `gh pr list` / `gh pr view`), and `git fetch` over SSH covers branch and commit verification.
66
68
 
@@ -84,7 +86,7 @@ The matrix is slow: let `tests.yaml` and `lint.yaml` set the loop cadence, but a
84
86
 
85
87
  **On a release run, a red build cell means that version ships short, permanently.** When the run belongs to a release push, whose head commit is the `[changelog] Post-release bump` that follows `[changelog] Release vX.Y.Z`, `publish-release` sits at the end of that same run and flips the draft to published once the asset jobs settle, locking the asset list. Whatever the matrix failed to produce by then is missing from that version forever: no re-run, no later upload.
86
88
 
87
- **This is by design, so do not try to stop it.** Publishing a release short beats holding it, and the recovery is the next version, not a draft the maintainer has to babysit. Keep doing exactly what you do for any stable red: fix the cause, push, and let the fix ride the next release. The one addition is reporting: name the platforms that version lost, so the maintainer knows the gap exists and can note it in the release. A short ship also leaves the changelog section, the release body and `docs/install.md` still advertising binaries that are not there (the `repomatic-ship` skill's § Repairing a short ship covers the cleanup); flag it rather than fixing it silently mid-loop.
89
+ **This is by design, so do not try to stop it.** Publishing a release short beats holding it, and the recovery is the next version, not a draft the maintainer has to babysit. Keep doing exactly what you do for any stable red: fix the cause, push, and let the fix ride the next release. The one addition is reporting: name the platforms that version lost, so the maintainer knows the gap exists. A short ship also leaves `docs/install.md` linking binaries that are not there (the `repomatic-ship` skill's § Repairing a short ship covers the cleanup); flag it rather than fixing it silently mid-loop.
88
90
 
89
91
  ## Autofix job failures (autofix.yaml)
90
92
 
@@ -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.
@@ -303,7 +307,7 @@ The report will be pasted into a GitHub issue (or PR body). Write for GitHub's r
303
307
  Before including any error output, tracebacks, or logs in the report, scrub them for readability and privacy:
304
308
 
305
309
  - **Strip local paths**: replace long absolute paths (`/Users/kde/code/project/venv/lib/python3.12/site-packages/...`) with short relative equivalents (`site-packages/...` or `.venv/.../`). The maintainer does not need the user's home directory or filesystem layout.
306
- - **Remove private information**: usernames, home directory names, hostnames, IP addresses, API keys, tokens, internal domain names, email addresses. Scan the entire output before pasting.
310
+ - **Remove private information**: usernames, home directory names, hostnames, IP addresses, API keys, tokens, internal domain names, email addresses. Scan the entire output before pasting. A private channel like a vendor's support email is no exception. Name a third party's account by its role, and let the user give the address if support asks.
307
311
  - **Trim repetitive frames**: if a traceback has dozens of recursive or repetitive stack frames, keep the top few, the bottom few, and replace the middle with `... (N frames omitted) ...`. The diagnostic value is in the entry point and the crash site, not 40 identical recursion frames.
308
312
  - **Collapse verbose logs**: if CI output is hundreds of lines, extract only the relevant section. Use `<details><summary>Full log</summary>` blocks for longer context the maintainer might need but should not have to scroll past.
309
313
  - **Preserve error messages verbatim**: sanitize paths and private data, but never paraphrase or reword the actual error string. Maintainers grep their codebase for exact error messages.
@@ -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.
@@ -49,7 +49,7 @@ Entries accumulate during development as features are built incrementally. Befor
49
49
  05. **Keep distinct user-facing changes as separate entries.** A breaking config key change and a new CLI command are separate features even if they landed in the same development cycle.
50
50
  06. **Keep the names users need, shed the rest.** Tool names, config keys, CLI options, and breaking-change notes stay explicit. But consolidation cuts per-entry *length*, not just bullet count: a merged entry is one short sentence naming the feature, not a paragraph stacking every mechanism and rationale from the bullets it replaced. Target ~10-25 words; push implementation detail and "why" to the commit, PR, code comment, or `docs/`.
51
51
  07. **Remove implementation details** that don't affect users: internal refactors, helper functions, test additions. Also strip upstream issue commentary: trailing prose that links to upstream tickets and narrates their status ("Click does not ship an equivalent: the upstream conversation is in `pallets/click#NNNN` (open)…", "mirrors the upstream fix in PR `…#NNNN`"). The status rots within days and the prose duplicates what the linked thread already says. A bare upstream link is acceptable on a direct backport entry; longer rationale belongs in a code comment, docstring, or PR body.
52
- 08. **Never leave the section empty.** A heading with no bullets reads as broken to whoever scans the release notes. When rules 02-07 collapse the unreleased section to zero bullets and the net cycle is genuinely mechanical, backfill one generic bullet naming what moved — e.g. "Sync CI tooling, workflow pins and dependency floors with the latest repomatic release." This is a fallback for an empty net cycle, not a substitute for drafting: it fires only after `add` has had its own chance to draft real entries from `git log`. As the section's sole bullet it needs no category ordering. The `prepare-release` job opens no release pull request while the section is empty, so this bullet is what unblocks a mechanical release.
52
+ 08. **Never leave the section empty.** A heading with no bullets reads as broken to whoever scans the release notes. When rules 02-07 collapse the unreleased section to zero bullets and the net cycle is genuinely mechanical, backfill one generic bullet naming what moved — e.g. "Sync CI tooling, workflow pins and dependency floors with the latest repomatic release." This is a fallback for an empty net cycle, not a substitute for drafting: it fires only after `add` has had its own chance to draft real entries from `git log`. It never fires when `git log` since the last tag lists only the post-release bump: nothing moved, and the bullet would cut a release with no change. As the section's sole bullet it needs no category ordering. The `prepare-release` job opens no release pull request while the section is empty, so this bullet is what unblocks a mechanical release.
53
53
  09. **Order entries by category, breaking changes first:** lead with `**Breaking:**` entries, then `**Deprecated:**` entries, then new features, then broad/global changes, then bug fixes, then documentation and testing. Breaking changes are what a reader scans for before upgrading, so they go at the top of the block. `**Deprecated:**` marks a surface that still resolves but warns and is slated for removal in a named future release.
54
54
  10. **Apply directly.** Write the consolidated section to `changelog.md` without asking for approval. Summarize what was merged, dropped, or reordered after writing.
55
55
  11. **Validate after writing.** A bulk rewrite can introduce malformed markup, silently drop structure, or leave entries over-long. Run `<cmd> lint-changelog`, which measures the bullet lengths against `changelog.bullet-word-threshold` — gate on what it reports, not on a delegated agent's self-report of how much it compressed. Then run `<cmd> run mdformat --verify -- <file>`, which reports what the write path would change without touching the file; a bare `mdformat`/`mdformat --with mdformat-myst` diverges on MyST directive colon-options like a `{list-table}`'s `:header-rows:`, so gate on the pinned runner. Confirm by eye what neither tool measures: rule 08 (its empty-section check covers *released* sections only, and deliberately skips the unreleased one you just consolidated, which is legitimately empty for most of a cycle), no doubled list markers (a stray `- -`), and the `## [...]` heading count and availability-admonition count unchanged from before the edit.
@@ -59,6 +59,7 @@ Entries accumulate during development as features are built incrementally. Befor
59
59
  - **One bullet per user-facing change**, one sentence of ~10-25 words, saying what changed rather than how it was built or why. A second sentence only flags a breaking change or a migration step.
60
60
  - **Cut what the user cannot act on.** Mechanism goes to the commit or PR; rationale goes to a code comment or `docs/`.
61
61
  - **Mark a change breaking when a surface the reader uses is gone**, so their code, invocation, config or workflow must change to keep working.
62
+ - **Warn about the version, never about one of its assets.** A section takes no admonition about a missing binary or another release file: the release page lists the assets that shipped.
62
63
 
63
64
  ### Next steps
64
65
 
@@ -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
@@ -59,6 +59,10 @@ The sweep agents (step 1) and the babysitter (step 6) all follow these rules. Re
59
59
 
60
60
  A release materializes the **net state since the last tag**, not the path taken to reach it. Reconcile the changelog, the code and the docs against `git diff v<last>..HEAD`. Order matters: the changelog *describes* the net change, so reconcile the substance first (code and docs in parallel), then summarize it (changelog). A change introduced and then reverted before release is a no-op for users: no changelog entry, no scaffolding, no docs mention.
61
61
 
62
+ **Fetch the tags before you read the cycle.** The context lists local tags, and the pipeline tags the freeze commit only after the merge. A checkout pulled before then lacks that tag. Its last tag is one release old, and `v<last>..HEAD` spans a cycle that already shipped. Run `git fetch --tags origin` first.
63
+
64
+ **Stop when nothing is left to ship.** That is the case when the unreleased section is empty and `git log v<last>..HEAD` lists only the post-release bump. Never backfill a bullet to cut an empty release: consolidation rule 08 covers a mechanical cycle, and the bump alone is no cycle. Check the last release against [§ What a complete release looks like](#what-a-complete-release-looks-like) instead. A release still in draft waits for its binaries, then publishes with whatever built. Follow its runs to the end with `<cmd> ci-status --branch main --wait --until-change --state-file <path>`, run again until every run settled: a plain `--wait` returns on the first red cell. Then report what the release lacks: a missing binary is a [short ship](#repairing-a-short-ship).
65
+
62
66
  **Before spawning, capture the unstaged diff** (`git diff` against `HEAD`): those lines are the maintainer's in-progress drafts, not cycle work. Pass both diffs to each agent with the rule: preserve every line present only in the unstaged set (a curated TODO, a scratch note in a docstring) unless the maintainer explicitly asked for cleanup. Without the guard an agent strips unstaged scratch as "cycle scaffolding". When in doubt, leave it.
63
67
 
64
68
  **Capture the job-level red inventory in the same breath**: the latest *conclusive* run of each monitored workflow on `main` (`gh api 'repos/<owner>/<repo>/actions/workflows/tests.yaml/runs?branch=main&created=>=<date>'`, then `gh run view <id> --json jobs`), listing every job at `conclusion == "failure"`, `⁉️` probes included: `continue-on-error` folds their crashes into a green run-level conclusion. Read `release.yaml`'s canary `✅ <os>, <sha> build` job too: its `Self-test binary` step runs the CLI test plan against the freshly compiled binary, and a toolchain pin bump upstream (a Nuitka release miscompiling a dependency) reddens it with no line of this repository changed. A push compiles only the `[tool.repomatic] nuitka.dev-targets` canary, so read the newest `schedule` or `workflow_dispatch` run of `release.yaml` as well: it alone builds every platform, and a break on one platform, like a Windows console that cannot encode a table, shows nowhere else. Under step 6's genuinely-green goal those reds are release work, and every one fixed before the first push saves a 40-90-minute babysit round-trip: seed the code agent's brief with the list.
@@ -69,6 +73,8 @@ A release materializes the **net state since the last tag**, not the path taken
69
73
 
70
74
  **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
75
 
76
+ **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.
77
+
72
78
  **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
79
 
74
80
  **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".
@@ -80,17 +86,17 @@ The three substance passes own disjoint lanes (code owns Python including docstr
80
86
  1. **Code**: an `Agent` that reviews every file changed since the last tag for reuse, quality, simplification, and deduplication, and fixes what it finds, simplifying before adding: existing code or a tool often already covers the case. Two layers: first strip scaffolding from reverted or superseded work within the cycle diff (abandoned workarounds, dead branches, WIP notes that never shipped); then harmonize what remains (collapse duplication, lift repeated literals to their canonical source, align new code with module patterns). Its constraints:
81
87
 
82
88
  - Every edit stays behavior-preserving: step 2 is the safety net, a failing test vetoes.
83
- - A defect in code the cycle added is the exception: it is release work. The agent fixes it in the pass, with a test that fails on the pre-fix lines. It never reached a release, so it takes no changelog entry. Write this into the brief: an agent told only to preserve behavior holds the fix back and asks, and the answer reaches it a full round later (sub-agent rules, trust the tree). It holds the fix back too when a test or a page of the same cycle states the defective behavior, so say that those are cycle work as well: the agent updates the test, and asks the lane that owns the page to update it. A defect that predates the cycle is reported instead.
89
+ - A defect in code the cycle added is the exception: it is release work. The agent fixes it in the pass, with a test that fails on the pre-fix lines. It never reached a release, so it takes no changelog entry. Write this into the brief: an agent told only to preserve behavior holds the fix back and asks, and the answer reaches it a full round later (sub-agent rules, trust the tree). It holds the fix back too when a test or a page of the same cycle states the defective behavior, so say that those are cycle work as well: the agent updates the test, and asks the lane that owns the page to update it. A defect that predates the cycle is reported instead, and on the canonical repo it becomes a step-8 finding.
84
90
  - That test must run in at least one CI cell. A test that skips without a dependency no CI test environment installs (an `importorskip` of Sphinx, where only the docs build installs it) guards nothing: test the fix where the suite runs, or keep the fix without the test and say so in the report.
85
91
  - Type checks use the CI-equivalent `<cmd> run mypy` (pinned version and `--python-version`), never a bare `mypy` whose newer interpreter raises false positives CI never sees. Pass it **no arguments**, exactly as step 2's Types gate does: the runner then resolves the same tracked-`*.py` list CI's lint job checks, `tests/` and `docs/conf.py` included. A downstream `AGENTS.md` "type checking" command is often the narrow dev-loop form scoped to the package only: do not inherit that scope, since a package-only run stays green on a `tests/` or `docs/` type error that reddens Lint post-push. Run it in the all-groups environment of step 2's Types gate: the shared `.venv` holds no type stubs.
86
92
  - Failures the pass believes pre-existing get *reported*, not silently scoped out: that verdict belongs to step 2's CI check.
87
93
  - **Modernize against the dependency versions the release already declares, and move none of them.** Run `/repomatic-deps modernize --no-bump` through the `Skill` tool. It adopts only what each declared floor provides, and it reaches past the cycle diff: a dependency the cycle moved has call sites in files the cycle never touched. It raises a floor only where the code already calls an API the floor lacks, and step 2's `lint-deps` then says whether the release waits. List each adoption that needs a higher floor in the report: step 7 passes it on, for a `modernize` run after the release. When the skill is excluded, apply that rule inline. On a split code lane, the orchestrator runs the pass once both halves join, since two halves would edit the same call sites.
88
94
  - On the canonical repo, workflow invocations reading `uv --no-progress run --frozen -- repomatic` are the intended unfrozen state (the freeze commit rewrites them to a `uvx 'repomatic=={version}'` PyPI pin at release): never flag the local form as a pin regression or downstream breakage. The invariant to check instead is that every `uv`-invoking job provisions `setup-uv` in its own steps. Do not "restore" an isolated `uvx --from .` here: an index resolution can be made unsatisfiable by the install cooldown while a lockfile cannot.
89
- - Docstring rendering belongs to this pass: build the docs and fix any broken cross-reference role a docstring introduced (the docs pass can surface but not fix them). Build in a separate environment, with `{scratch}` a directory outside the repository: `UV_PROJECT_ENVIRONMENT={scratch}/docs-venv uv run --frozen --all-extras --group docs -- sphinx-build --fresh-env -b html docs docs/_build/html`. The shared `.venv` then keeps the CI-matching groups, which the `docs` group would perturb (see step 2's `--all-groups` warning). `--fresh-env` re-reads every page: an incremental build reports warnings only from the pages it re-read. A checked-in `:mirror:` block whose cells embed source-line anchors is invalidated by every edit that moves a line in the anchored modules, docstring rewraps included: expect the `update-docs` autofix PR to refresh it after the push, and take that PR's file (`gh api 'repos/<owner>/<repo>/contents/<path>?ref=update-docs' -H 'Accept: application/vnd.github.raw'`) when a local regeneration would differ from CI's, as a terminal-dependent width does, or when `gh pr merge` is permission-walled. Build only into the gitignored `docs/_build`, never an ad-hoc path: a stray build tree pollutes `git status` and trips tool scans like `run typos`.
95
+ - Docstring rendering belongs to this pass: build the docs and fix any broken cross-reference role a docstring introduced (the docs pass can surface but not fix them). Build in a separate environment, with `{scratch}` a directory outside the repository: `UV_PROJECT_ENVIRONMENT={scratch}/docs-venv uv run --frozen --all-extras --group docs -- sphinx-build --fresh-env -b {builder} docs docs/_build/{builder}`, with `{builder}` the `[tool.repomatic] sphinx.builder` value that `docs.yaml` builds with (`html` by default). The shared `.venv` then keeps the CI-matching groups, which the `docs` group would perturb (see step 2's `--all-groups` warning). `--fresh-env` re-reads every page: an incremental build reports warnings only from the pages it re-read. A checked-in `:mirror:` block whose cells embed source-line anchors is invalidated by every edit that moves a line in the anchored modules, docstring rewraps included: expect the `update-docs` autofix PR to refresh it after the push, and take that PR's file (`gh api 'repos/<owner>/<repo>/contents/<path>?ref=update-docs' -H 'Accept: application/vnd.github.raw'`) when a local regeneration would differ from CI's, as a terminal-dependent width does, or when `gh pr merge` is permission-walled. A `<!-- matrix -->` region with a dependency axis goes stale with no edit in the tree when that dependency publishes during the sweep. Just before the commit, run `click-extra refresh-directives --check docs readme.md` behind the same docs-venv `uv run` prefix: the test groups lack the `click-extra[sphinx]` extra it needs. Refresh a stale matrix with the same command, without `--check`. Build only into the gitignored `docs/_build`, never an ad-hoc path: a stray build tree pollutes `git status` and trips tool scans like `run typos`.
90
96
  - **A docs build that already warns needs a baseline.** Without one, the pass cannot tell the cycle's warnings from older ones, and fixes them all. Build the last tag in a throwaway `git worktree`, then compare the two warning lists with their line numbers removed. A warning the tag build lacks is one the cycle added: fix it. A warning both builds hold predates the cycle: report one count per category, and leave it. The tag worktree resolves the tag's own lockfile, so the two builds also differ by the dependency bumps the cycle carries. A new warning a bump surfaced on a reference an earlier cycle wrote is bump fallout, not cycle work: report it with the pre-cycle counts instead of fixing the docstring in the reconciliation. Tell the two apart by grepping the cycle diff for the reference: one it never touched was resolving before the bump.
91
97
  - Shortening an over-long workflow line to satisfy yamllint's 120-char limit must not lift `hashFiles(...)` (or any `runner.*`) into a workflow-level `env:` var: that context exposes only `github`/`secrets`/`inputs`/`vars`, so the expression resolves to empty at run-init before checkout and silently breaks the value. Shorten the literal itself instead (trim a shared key prefix, say).
92
98
  - The red inventory from the pre-spawn capture is part of its brief: root-cause each repo-fixable red (a chronic platform break, a flaky live-registry install, a crashing `⁉️` probe) and fix it at the source per step 6's taxonomy, even when the failing file saw no change this cycle.
93
- - Diff the public surface against the last tag: for each module, list the top-level public names the cycle removed, added or gave a new value. A removed name keeps resolving through the project's deprecation mechanism, and gets a `**Breaking:**` bullet only when it cannot keep working. A name the deep pass removed or changed on purpose gets the bullet, never a revival. A public constant whose value changed gets its released value back, or a bullet. An added name that no unreleased bullet names goes in the report, for step 4. The commit trail hides all three: a deduplication pass drops a public constant as dead code, and its commit names no API change.
99
+ - Diff the public surface against the last tag: for each module, list the top-level public names the cycle removed, added or gave a new value, and each public class whose fields or signature changed. A removed name keeps resolving through the project's deprecation mechanism, and gets a `**Breaking:**` bullet only when it cannot keep working. A moved name can still resolve at its old address without a warning, through an import the old module keeps for its own use: give that address the warning too, or the removal release finds nothing to remove. A field inserted among the released ones of a named tuple breaks positional construction: append it with a default, and give the unpacking break a bullet. A name the deep pass removed or changed on purpose gets the bullet, never a revival. A public constant whose value changed gets its released value back, or a bullet. An added name that no unreleased bullet names goes in the report, for step 4. The commit trail hides each of these: a deduplication pass drops a public constant as dead code, and its commit names no API change.
94
100
  - Pending work the cycle introduced belongs in a ```` ```{todo} ```` admonition where Sphinx renders it, not in a bare `# TODO`/`XXX` comment: a comment never reaches the published todo list. This applies to **committed** cycle-diff lines only: a `# TODO` present only in the unstaged set is the maintainer's draft and stays untouched.
95
101
  - Retire a `{todo}` whose trigger fired, deleting the shim it guards in the same edit. Bound the check to what moved: `git diff v<last>..HEAD -- pyproject.toml uv.lock` plus the tool-version registry names the upstream releases this cycle actually adopted, and a todo naming one of them is the only kind worth re-reading. Read the trigger's own wording against that diff: a todo waiting on the dependency *floor* fires only when `pyproject.toml` raises it, never on a `uv.lock` bump that merely installs the release, and a shim the old floor still needs gets its todo re-scoped to that floor rather than deleted. Never poll every linked ticket, and leave a todo whose trigger has not fired alone.
96
102
  - A `{todo}` that schedules its work for the version this release cuts ("In `X.Y.Z`, ...") is due whatever moved. Grep the `{todo}` admonitions for that version, and report each match for step 7: its work lands before the merge, or the maintainer moves the todo to a later version. Never add a public name that such a todo asks for: that decision is the maintainer's.
@@ -110,7 +116,7 @@ The three substance passes own disjoint lanes (code owns Python including docstr
110
116
  - 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
117
  - 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
118
  - **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.
119
+ - 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
120
  - 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
121
  - 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
122
  - 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 +132,7 @@ The three substance passes own disjoint lanes (code owns Python including docstr
126
132
 
127
133
  **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
134
 
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.
135
+ 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
136
 
131
137
  ### If the sweep made no edits
132
138
 
@@ -164,7 +170,7 @@ The checks:
164
170
  - **Shippable deps**: `<cmd> lint-deps`. It reads `pyproject.toml` and `uv.lock`, and asks PyPI only about a floor below a locked release still inside the cooldown. It covers the one release failure nothing else in this gate can see: a `[tool.uv.sources]` override never reaches the published metadata, so tests, types, formatting and the build all pass on a tree whose wheel every user then fails to install. Run it even on a docs-only cycle, where a lockfile bump can still have moved a source. A blocker naming a git source paired with a `.dev` floor is the `sync-dep-sources` idiom mid-flight: wait for that swap PR, and do not edit `pyproject.toml` by hand. The release lane carries the same check as a hard gate, but it fires after the freeze commit is already on `main`, where the only recovery is to burn the version and ship the next one.
165
171
  - **Formatting**, reproduced with the **pinned** tools, never the dev-env `uv run ruff`:
166
172
  - **Run autopep8 over the cycle's changed Python files**: `git diff --name-only HEAD -- '*.py' | xargs <cmd> run autopep8 --`, which wraps long-line comments ruff leaves. Never pass a shell variable holding the space-separated list, which the runner takes as one literal path and rejects with `[Errno 2] No such file or directory: 'a.py b.py c.py '`.
167
- - **Then `<cmd> run ruff -- check` and `<cmd> run ruff -- format`, and read `git diff`.** Both write in place, but `check` only does so because the resolved ruff config sets `fix = true`: a repo carrying a `[tool.ruff]` section without that key gets a read-only `check` and an empty diff that means nothing. An empty diff past your reconciliation edits is green; fold a legitimate style fix into the reconciliation. Where the config does set it, that write is repo-wide rather than scoped to the cycle: a repo carrying pre-existing findings has them fixed in files this release never touched, and each one must be reversed before staging. Pass `--no-fix` when you only want to read the state. That write also runs *against* your own reconciliation: a compatibility re-export is exactly what `F401` deletes, because the old module's body never names it, and the diff then reads clean because the file is back to its committed state. A cycle that moves public symbols to a new module keeps them importable at the old address, so mark each such name `# noqa: F401` or list it in `__all__`, and confirm it survived by grepping for the name rather than by reading the diff.
173
+ - **Then `<cmd> run ruff -- check` and `<cmd> run ruff -- format`, and read `git diff`.** Both write in place, but `check` only does so because the resolved ruff config sets `fix = true`: a repo carrying a `[tool.ruff]` section without that key gets a read-only `check` and an empty diff that means nothing. An empty diff past your reconciliation edits is green; fold a legitimate style fix into the reconciliation. Where the config does set it, that write is repo-wide rather than scoped to the cycle: a repo carrying pre-existing findings has them fixed in files this release never touched, and each one must be reversed before staging. Pass `--no-fix` when you only want to read the state. That write also runs *against* your own reconciliation: a compatibility re-export is exactly what `F401` deletes, because the old module's body never names it, and the diff then reads clean because the file is back to its committed state. A cycle that moves public symbols to a new module routes each old address through the deprecation mechanism of step 1: a plain re-export resolves without a warning. A PEP 562 `__getattr__` alias warns, and holds no import for `F401` to delete. Confirm each old address still resolves and warns by importing it, not by reading the diff.
168
174
  - On a tree that holds uncommitted sweep edits, `git diff` shows them mixed with what the formatters wrote. Copy the changed files aside before the sequence, then compare each one against its copy: an empty comparison is the green. A per-tool `--verify` cannot replace this, since `<cmd> run autopep8 --verify` reports a rewrite that `ruff format` then reverts.
169
175
  - **For any Markdown the reconciliation touched (`changelog.md`, `docs/`), ask `<cmd> run mdformat --verify -- <file>`.** It reports what the write path would change without touching the tree. Never a bare `mdformat`/`mdformat --with mdformat-myst`, whose plugin set rewrites MyST directive colon-options (a `{list-table}`'s `:header-rows:`/`:widths:`) to `---` frontmatter form, diverging from CI's autofix.
170
176
  - Landmine: autopep8 relocates a trailing `# type: ignore[...]` off a >88-char line onto its own line, voiding the suppression (Lint red under `warn_unused_ignores`); ruff format usually reverts the relocation, so only wraps that survive the full pinned sequence are real formatting debt. Never commit the relocation: fix the line length at the source so the comment rides the opening line.
@@ -185,7 +191,7 @@ The checks:
185
191
  - **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
192
  - **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
193
  - **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.
194
+ - **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
195
  - **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
196
  - **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
197
 
@@ -243,7 +249,7 @@ Step 2 cleared every locally-reproducible failure and step 1's red inventory pre
243
249
 
244
250
  **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
251
 
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.
252
+ **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 once every run settled and the tip has a run of its own. Spawn the babysitter only when a required job turns red, and run the command again after each fix push.
247
253
 
248
254
  **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
255
 
@@ -256,7 +262,7 @@ Step 2 cleared every locally-reproducible failure and step 1's red inventory pre
256
262
  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
263
 
258
264
  - **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).
265
+ - **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, or once every run settled and the tip has a run of its own. 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
266
  - **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
267
  - **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
268
  - **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.
@@ -313,7 +319,7 @@ Do not merge the PR, and do not mark it ready yourself. That final human action
313
319
 
314
320
  #### Repairing a short ship
315
321
 
316
- When the binary matrix came up short, read `references/short-ship.md` before the report. It says what to report, lists the three follow-ups to name, and holds the upstream-only note on `Failed to spawn: repomatic`.
322
+ When the binary matrix came up short, read `references/short-ship.md` before the report. It says what to report, names the one follow-up, and holds the upstream-only note on `Failed to spawn: repomatic`.
317
323
 
318
324
  ### 8. Reflect and contribute back
319
325
 
@@ -11,4 +11,6 @@ Treat that commit as a reconciliation like any other, which means four things th
11
11
  - **Time the push by what it rebuilds** (step 6): a docs-only commit skips both matrices, and a `.claude/`-only one skips the binary matrix but runs Tests, since the test suite reads every bundled skill and agent. Either one still cancels an in-flight `release.yaml` on a binaries-enabled project. Hold it until the heavy matrices are terminal, or bundle it into the next source-affecting push.
12
12
  - **Re-verify after it lands.** The push starts a fresh round of CI and re-bases the PR, so every green you read before it is stale. Confirm each monitored workflow is green on the new HEAD and that `<cmd> ci-status --release-pr` reports the PR `0` commits behind `main` again before step 7, and never report a release green from a run that predates your own last commit.
13
13
 
14
+ **A pre-existing defect that a lane reports is a finding too.** Step 1 has each lane report a defect older than the cycle, so that the reconciliation itself stays behavior-preserving. Fix each such defect here, before the step-7 report, as release work like any other finding. Give it a test that fails on the old code. List for the maintainer only the defects that the bound below keeps out.
15
+
14
16
  **Keep the pass bounded to what the session actually surfaced.** A release is the wrong moment to land a refactor, so a finding needing more than a contained edit, or touching code the release itself depends on, stays an uncommitted diff plus a note in the step-7 report, exactly as the downstream path prescribes. The usable test is whether the gate you just ran can verify it; when it cannot, it is not a release-time change. The archetype: a session's own step-8 finding was left uncommitted under the downstream boundary, the maintainer committed it by hand as a separate change, and it missed the release it was learned in.
@@ -0,0 +1,13 @@
1
+ # Repairing a short ship
2
+
3
+ When the binary matrix came up short, say so in the step 7 report and name the platforms the version will lose. Publishing is what locks the asset list, so this is the last moment the gap is cheap to record; afterwards it is a permanent property of that version. Shipping short is intended behavior and never a reason to hold the release.
4
+
5
+ Name the missing platforms nowhere else. The changelog section and the GitHub release body describe the version, not each of its artifacts, so neither takes a `> [!WARNING]` about a missing binary.
6
+
7
+ One artifact still links binaries that are not there, and needs a hand *after* the merge: **`docs/install.md`**. In repomatic itself, the freeze pins its download URLs to the version being released, optimistically: the freeze commit is what triggers the build, so it cannot know whether the binaries will land. Re-point them at the last release that carries binaries via `PrepareRelease.freeze_install_download_urls`, and the next release's freeze ratchets them forward again. The freeze leaves a downstream repo's URLs alone. Those use the `latest/download/` form, which follows the newest release, so they 404 for the missing platforms until a later release ships them. There, the hand is a line in the report naming that gap, and no file changes. `lint-repo`'s `check_install_guide_downloads` reports the gap in both cases but never repairs it, since an automated rewrite driven by a single API read could downgrade a healthy install page on a flaky response.
8
+
9
+ Report it as a follow-up. Do not perform it: it lands after a merge this skill does not make.
10
+
11
+ ```{note}
12
+ Upstream only: the release PR is rebase-merged, so its freeze and unfreeze commits arrive in a single push, and GitHub Actions reads workflow files from that push's head. `kdeldycke/repomatic`'s own release lane therefore always runs the **unfrozen** workflow content, whatever the freeze wrote into the release commit. A job that assumes the frozen `uvx 'repomatic==X.Y.Z'` form is what executes (and drops its checkout on that basis) dies on `Failed to spawn: repomatic`. Only downstream repos, which call the reusable workflow at its tag, ever run the frozen form.
13
+ ```