test(branch): supercharge — 70 new tests, fix stale _ZERO_OID format
- Fix _ZERO_OID in test_security_branch_ref_injection: 64-hex → sha256:<64-hex> (write_branch_ref now requires sha256:-prefix format; 3 tests were broken)
- Add test_cmd_branch_supercharged (70 tests) covering gaps: * committed_at field in --json schema (baseline missed this field entirely) * --sort committeddate actual ordering (baseline only checked exit 0) * -r / -a remote-tracking listing E2E with real .muse/remotes/ structure * -dr success path + JSON schema (only error paths were tested before) * -vv upstream shown in [brackets] in text output * Diamond-merge DAG: --merged with two-parent merge commits * _ref_file, _cleanup_empty_dirs unit tests (nested dir cleanup) * _list_remotes unit tests (hidden files, nested branches, sort) * Empty parent dirs cleaned after nested branch delete (E2E) * Rename into nested path creates intermediate dirs * Force-rename/copy preserves tip, src integrity * JSON error schemas: error + message + hint fields for all mutation ops * create --json: commit_id has sha256: prefix, from field present/null * Security: ANSI injection in --merged / --no-merged / --contains * Performance: --sort committeddate with 50 branches under 3s * Docstring coverage for all 10 public helpers
0 comments
muse hub commit comment sha256:7fbf1a30a27c42d1be7c170fab25d948ef2caa0bc7d67813e5d57f1e733fcd29 --body "your comment"
No comments yet. Be the first to start the discussion.