Documentation
¶
Overview ¶
Package main cmd/mux-probe-assert/main.go c2-net-routing Command mux-probe-assert consumes the tally emitted by ci_scripts/mux-route-probe.sh and enforces pass/fail thresholds against a recorded baseline. Designed to be piped:
mux-route-probe.sh <target_pk> | mux-probe-assert -baseline=ci_scripts/mux-baseline.json
Or with the tally captured to a file:
mux-route-probe.sh <target_pk> > tally.txt mux-probe-assert -baseline=... < tally.txt
Exit codes intentionally match the runner's (per the 2026-05-19 mux-test scope agreement) so a CI lane can use either tool's exit code without ambiguity:
0 success — all checks pass 1 usage / parse error 2 topology-degrade abort (routes_act < routes_req) 3 integrity failure (reserved; runner doesn't emit a checksum yet) 4 throughput regression (< 70% of baseline) 5 head-of-line correlation breach (reserved; needs per-msg data the bash runner doesn't emit yet)
Click to show internal directories.
Click to hide internal directories.