Use the system Bash 3.2 and native macOS tools. Submit focused changes with fixture coverage and an explanation of observable behavior. Run bash tests/run.sh and syntax checks for all shell files. ShellCheck is optional for contributors, never a runtime dependency.
Never test removal against real host registrations. Tests must create isolated fixtures and replace service-control commands. Changes to mutation scope require a written safety analysis, failure-path tests, and disposable-machine manual validation. Do not add malware labels from filenames or treat vendor recognition as a trust decision.
Do not commit reports, backups, device output, credentials, usernames, or private paths. Review staged changes and .gitignore before publishing. Use GitHub issues for reproducible, redacted non-sensitive bugs; see SECURITY.md for vulnerabilities.