Added
muster test: faults are named steps and time is a clock the scenario moves.test_redeploy_mock_serverreplaces a mock backend’s process behind its port – every MCP session forgotten, tools kept, no refused connection in between, the way a rolled pod takes over behind its Service;test_set_mock_server_auth: {required: true|false}flips a running mock between answering anonymously and 401-with-metadata, the rollover of a backend to an OAuth resource server (a mock with a token validator andoauth.required: falsestarts anonymous).test_advance_clock: {duration}movesmuster serve’s clock and every mock authorization server’s clock forward together: the reconnect backoff of a remote MCPServer, the orchestrator’s retry and health ticks and the age of the core catalogue now read a process clock (internal/clock) that the harness advances through a control socketMUSTER_TEST_CLOCKselects – a tick that has become due fires at once, nothing waits, and production binaries keep the system time.pre_configuration.intervals: productionleaves those timers on their production defaults (30 s initial backoff, 2 min cap, 30 s ticks, 5 min catalogue age) for scenarios that assert the production schedule; the defaultshortkeeps the seconds-long environment knobs. The fault steps and the clock are documented together in “Faults and time” ofdocs/contributing/testing/scenarios.md. Four scenarios: a backend redeployed behind the same port has its session recovered on the next call, no health probe in between (fails on v5.15.0, #999); on the production schedule a remote server whose gateway answers 504 four times waits 30 s, 1 min, 2 min and again 2 min – never 4 – and is connected within the cap once the gateway serves (fails on v5.9.10 with the clock, #1163); the core catalogue found older than its five-minute age is served as it is and rebuilt once in the background (fails on v5.19.13 with the clock, #1231); a forwardToken backend rolled over from an anonymous pod to a 401 pod and back is never registered globally and keeps serving the signed-in session (fails on v5.7.17, #1135). (#1238)