gossipper-runlisted

# gossipper-run — Scenario Execution Invoke Gossipper. Pinned to **Gossipper 0.1.60-rtcpmuxpatch2** (sipcapture/gossipper on `main`, audited 2026-05-18). ## When to use this skill - Run an existing scenario (one-shot CLI or long-running). - Pick transport mode, rate, concurrency, output flags, correlation IDs. - Author a 3PCC peer file (CSV `name;host:port`). - Convert a PCAP to scenarios via `gossipper pcap2scenario`. - Smoke-test a freshly authored scenario before the real run. - Build a run-profile JSON for systemd / long-running deployment. - Wire `-health_*` thresholds when given threshold values. - Interpret a Gossipper exit code at the operational level. ## When NOT to use this skill | Task | Owner | |---|---| | Write or modify a scenario XML | gossipper-build | | Decide what XML belongs in the scenario | gossipper-build | | Parse summary JSON, trace CSVs, call records | gossipper-analyze | | Classify failures (timeout / unexpected_sip / …) | gossipper-analyze | | Decide threshold *values* for `-health_*` | gossipper-analyze or user | | Cross-correlate with HEP/qryn production traffic | gossipper-analyze | This skill picks flags and runs the process. It does not decide what the scenario should do, and it does not interpret what came out beyond exit-code level (0 / 1 / 2). ## Inputs from gossipper-build Every scenario authored by gossipper-build starts with a top-of-file XML comment block. Read it — don't re-derive from message content. ```xml <!-- Scenario: