Making the audio driver's foundations explicit

Open-source driver work starts with other people's foundations, and those foundations should be easy to find. The March 3 update added explicit WDK and Windows Driver Samples attribution, including the Sysvad audio sample lineage and the third-party license notice.

That helps anyone trying to understand or extend the project. You can separate the original application work from the sample-derived code, find the relevant Microsoft material and see which notices need to travel with a distributed copy.

It also gives us a more accurate way to describe what this product is. The Virtual Audio Driver is a Windows driver project exposing virtual audio endpoints. It is separate from the macOS suite's Core Audio HAL cables, even though both can help with audio workflows. The implementation, installation and validation requirements differ.

The latest local and GitLab default heads matched at this attribution commit during the review. There wasn't a newer source revision in that comparison that would restore the removed effects experiment or establish a fresh production-signed release.

The next useful work is practical: reconcile the README with the actual format declarations, test which streams applications can open, measure delivery through the intended workflow and verify installation and removal on the target Windows systems. The existing beta warning stays relevant until the exact package has its own stronger evidence.

This is a smaller update than adding another device mode, but it makes the project easier to build on responsibly. If someone learns from this driver or incorporates parts of it into another tool, the origin and obligations of the sample code should be right there with the implementation.