fix: _short_id keeps sha256: prefix canonical; document deletion-staging trap
_short_id in both rebase.py and range_diff.py was stripping the sha256: prefix and returning bare hex. The prefix is canonical in Muse everywhere except on-disk shard paths — stripping it for display is wrong and loses algorithm provenance.
New behavior: _short_id('sha256:abcdef1234567890...') -> 'sha256:abcdef12' (range-diff, 8 hex) _short_id('sha256:abcdef1234567890...') -> 'sha256:abcdef123456' (rebase, 12 hex)
Tests updated accordingly: - TestShortId: inverted assertions — now verifies prefix is kept, hex truncated - test_text_short_id_has_sha256_prefix: expects sha256:<8-hex> tokens in output - test_text_short_ids_are_sha256_plus_8_hex: verifies 15-char total length - test_text_output_shows_sha256_short_id: expects sha256:<12-hex> in dry-run text - test_abort_text_shows_sha256_short_id: expects sha256:<12-hex> in abort text
Agent guide (docs/agent-guide.md + .muse/agent.md): muse code add <path> silently does nothing when the file no longer exists on disk. Added explicit note: use -u to stage tracked deletions, with a warning callout in the standard cycle block.
0 comments
muse hub commit comment sha256:8ed6bbcb858d9ff1cb3a15247039bc7a5c5d71a94935c0aa0fe4ab63adb7a72d --body "your comment"
No comments yet. Be the first to start the discussion.