# Contributing

Use .NET 10 and keep changes focused. Run `dotnet build VxSound.slnx -c Release -m:1` and `dotnet run --project tests/VxSound.Tests -c Release --no-build` before submitting a change.

For DSP changes, verify actual signal behavior, stereo separation and bounded output. Keep file I/O, locks and allocation-heavy work outside the core render loop. Describe any change to latency or gain; distinguish measured results from targets.

For Windows integration, include the Windows version, actual device/connection, selected mix format and reproduction steps. Never claim hardware compatibility based on a successful compilation alone. Do not include local personal listening profiles, diagnostic logs containing unrelated paths, or credentials in pull requests.

Use official manufacturer sources for device specifications and updates. Preserve unknown values when information is unavailable. Imported preset files must stay data-only and receive new identifiers.

Record the origin and license of externally supplied presets, recordings and artwork before including them. Do not commit vendor databases, extracted factory catalogs or test recordings without a verified right to distribute them. A file marked as a custom preset is not proof of ownership. Generate synthetic fixtures for import tests and preserve required dependency notices in packages. See [licensing review](docs/LICENSING.md).