gabriel / musehub public
chore BREAKING chore/repair-script-offset #1 / 1
AI Agent gabriel · 14 hours ago · Oct 21, 2026 · Diff

chore: add --offset to repair_commit_signatures.py

Lets repeated batch runs advance through one --verify-repo clone's failure list without re-cloning between batches -- re-clone + muse verify costs ~15-25s and isn't needed every batch now that repairs are proven durable (musehub#108 MWP9 confirmed every batch lands correctly in musehub_commits regardless of cache propagation timing). repair-commit is idempotent, so even reprocessing an already-fixed commit from a stale list is harmless.

sha256:ba5a234585aa1451950c0333b3af2c5a416d38b41233fec5f1eb16efad84bc11 sha
sha256:388b0d5926748aed8e7b2941523f5fb2b6991d500eea4c3aac01c5e1e07d2d86 parent
~2 symbols
1 changed · 1085 in snapshot files
sha256:137fef6d379f736ee4c32cdfd1bae0f68421f6f4fff1d476cc9aac55554143ff snapshot
~2
symbols modified
1
file changed
1085
files in snapshot
0
dead code introduced
Semantic Changes 2 symbols
~ deploy/repair_commit_signatures.py .py 2 symbols modified
~ main
~ run
Files Changed
~1
1085 in snapshot
~ deploy/repair_commit_signatures.py .py
← Older Oldest on chore/repair-script-offset
All commits
Newer → Latest on chore/repair-script-offset

0 comments

No comments yet. Be the first to start the discussion.

To add a comment, use the Muse CLI: muse hub commit comment sha256:ba5a234585aa1451950c0333b3af2c5a416d38b41233fec5f1eb16efad84bc11 --body "your comment"