cmux-testinglisted

# cmux Testing ## Choose the first check Run repository commands only from a [trusted checkout](../../docs/contributor-verification.md#trust-boundary); even `verify-local.py --help` and `--list` load repository code. | Task | Command | | --- | --- | | Choose checks and parse changed Swift | `python3 scripts/verify-local.py` | | Run the full CI static recipe | `python3 scripts/verify-local.py --all` | | Parse current Swift edits | `python3 scripts/verify-local.py --only swift-syntax --swift-changed` | | Check new Swift test-file wiring | `python3 scripts/verify-local.py --only test-wiring` | | See what a UI test did, one frame per action | `scripts/ui-test ClassName` or `scripts/ui-test <run URL>` ([guide](references/ui-test-frames.md)) | Add a base ref after `--swift-changed` to include committed changes. Use `--list` to find other checks and `--help` for options. Parsing checks syntax; it doesn't typecheck or run tests. Read the [command guide](../../docs/verification-receipts.md) for piped paths or JSON receipts. Use the [validation guide](references/local-vs-ci-validation.md) to choose package, native, web or runtime checks. Docs and portable tooling use their scoped checks. ## Reproduce and repair Keep a focused command that fails on the reported symptom, then rerun it after the repair. Setup failures and zero executed tests don't demonstrate the bug. Exercise one behavior at a time so a failure identifies what needs fixing. Keep two commits: first the failing beh