docs: document the expected ~30s retry wait in the repeated-loop recipe
Ran the full guide end to end against real staging with diagnostic instrumentation after a prior session hit what looked like a 2-minute clone hang. Root-caused: it's the MWP-5 bounded 503-retry mechanism firing correctly — push-then-immediate-clone against real staging races the server's async fetch.mpack.prebuild job roughly half the time, producing a real 30s wait (server-issued Retry-After) before the retry succeeds. Not a bug, not a hang — the retry path from muse#63 Phase 1's 'never exercised against real staging' finding is now confirmed working correctly. Added an explicit note so a reader doesn't mistake the wait for a hang.
sha256:b5a156ef38b5592d3c43282e94aaa1b70ad012558befa0c3657edbeb1b8fb77a
sha
~2
symbols
1 changed · 996 in snapshot
files
sha256:2c27398157a8e9855f044e84faed991844009cad41062b76adba9fc91b8fb0fb
snapshot
~2
symbols modified
1
file changed
996
files in snapshot
0
dead code introduced
Semantic Changes
2 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:b5a156ef38b5592d3c43282e94aaa1b70ad012558befa0c3657edbeb1b8fb77a --body "your comment"
No comments yet. Be the first to start the discussion.