test
mwp-1
task/mwp-1-generation-authority
#2 / 11
test(mwp-1): Phase 5 — end-to-end regression proof (MWP1_14)
MWP1_14 proves the clone-after-push staleness is gone end-to-end:
1. Push C1/C2/C3 individually — each gets the correct generation. 2. Delete C3 from CommitGraph — simulates the RC-1 backfill gap that caused the staleness bug (parent in musehub_commits but absent from musehub_commit_graph). 3. Push C4 (parent C3) — Phase 2 backfill restores C3=gen 2, C4=gen 3. 4. Clone with want=[C4], have=[] — asserts all 4 commits (C1–C4) and C4's blob are in the assembled mpack.
WITHOUT the fix: C4 gets gen=0, the range scan (gen <= 0) misses C2 and C3, so the clone is incomplete. WITH the fix: C4 gets gen=3, all 4 commits are in the range and the clone is complete.
All 13 MWP1 tests GREEN.
sha256:1aca297eaa71ac4ab5bd77dcedeb4bf3bd1a1cb1a13fb058ade9fc3233d090a8
sha
+12
~2
symbols
sha256:91d8aa5faf9e468d106884294a77bb32fb1d2191010e16454b8709f5de994258
snapshot
+12
symbols added
~2
symbols modified
0
dead code introduced
Semantic Changes
14 symbols
+
test_mwp1_14_end_to_end_push_clone_push_clone
function
async_function test_mwp1_14_end_to_end_push_clone_push_clone L874–1041
~
select
Older
docs(mwp-1): mark Phase 4 complete (MWP1_12, MWP1_13)
sha256:3095b0e12423a6e4f90155d90aefe3f8330f4a42bf7dd81df5abf5b1598535b3
All commits
Newer
docs(mwp-1): mark Phase 5 complete, all acceptance criteria met …
sha256:da49a05fd62cda46a7d73ec53a8d0adc5835d2070f6f0c51b12233a673c2e109
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:1aca297eaa71ac4ab5bd77dcedeb4bf3bd1a1cb1a13fb058ade9fc3233d090a8 --body "your comment"
No comments yet. Be the first to start the discussion.