docs: fix branch-state bug in MWP QA clone recipe
gabriel caught this running the guide himself: the push recipe's sibling-branch dedup test leaves the working tree on feature-b, but the clone recipe's 'push v2 then clone immediately' step committed v2 there without switching back to main first — so 'muse push staging main' correctly no-op'd (nothing new on main) and the diff check downstream would have silently passed on stale content. Added an explicit 'muse checkout main' so the recipe is correct regardless of what branch the previous section left the reader on. Verified end-to-end against staging: reproduced the exact bug, confirmed the fix converges.
sha256:80586889c3a5c555371d1e6616dcfd60de187f52fa1e568c87e9c3bf5b7a8dac
sha
~6
symbols
1 changed · 996 in snapshot
files
sha256:ebf12044a50b7472d4eec25cc0ca806566e0ce7ceb19509269cf3a380b4bd872
snapshot
~6
symbols modified
1
file changed
996
files in snapshot
0
dead code introduced
Semantic Changes
6 symbols
Files Changed
~1
996 in snapshot
~1
996 in snapshot
0 comments
To add a comment, use the Muse CLI:
muse hub commit comment sha256:80586889c3a5c555371d1e6616dcfd60de187f52fa1e568c87e9c3bf5b7a8dac --body "your comment"
No comments yet. Be the first to start the discussion.