feat(range-diff): supercharge muse range-diff — fix sha256: bugs, add agent fields, rewrite tests
Bug fixes: - _resolve_ref: accept sha256:-prefixed commit IDs (strip prefix before hex fullmatch); previously all sha256:-prefixed commit IDs in ranges silently returned None, making all range expressions with commit IDs fail - _SAFE_REF_RE / _SAFE_RANGE_RE: allow ':' so sha256:-prefixed commit IDs pass input validation (previously rejected with 'Invalid ref' error) - _compute_patch_id: now returns (sha256:-prefixed patch_id, files_changed) tuple — patch_ids in JSON were bare hex, inconsistent with muse patch-id --json
New agent fields in JSON output: - old_count, new_count: commit counts for each range (no need to count pairs) - stable: reflects the --stable flag used for this comparison - creation_factor: the clamped value actually applied for pairing - files_changed: per-commit count in every pair's old/new commit info - duration_ms: wall-clock time in milliseconds - exit_code: 0 (trivially equivalent) or 1 (differences found), mirrored in JSON
Tests: - Delete tests/test_cmd_range_diff.py (19/24 failing, pre-sha256: helpers) - Add tests/test_range_diff_supercharge.py: 59 tests covering unit, integration, data integrity, performance, security, and stress tiers
0 comments
muse hub commit comment sha256:f4552a503d9c232c87d9cfd12091accacd50b86f6f2bc4cddd524f1cb71b4818 --body "your comment"
No comments yet. Be the first to start the discussion.