Mac Intel compatibility release 0.9.72 / build84

This archive preserves every file from the previously published Windows0.9.86 / Mac0.9.71 / iPad0.9.51 / Android0.2.13 source baseline. The 100 Mac Swift source files for this compatibility build are byte-identical to that baseline. Build the Mac project with MARKETING_VERSION=0.9.72 CURRENT_PROJECT_VERSION=84 ARCHS="arm64 x86_64" ONLY_ACTIVE_ARCH=NO and MACOSX_DEPLOYMENT_TARGET=14.0. The normalized JSON command uses caller-provided SOURCE_ROOT, DERIVED_DATA, SODIUM_INSTALL and PACKAGE_CACHE directories. Existing IPA71 and receiver protocol are unchanged; this is not the separate private96 LAN-auth/audio/traffic development branch. Intel hardware validation is pending user feedback.

The arm64 assistant host remains the previous published binary. Build its x86_64 peer from shared/side-screen-assistant/src/Assistant.Host/Assistant.Host.csproj using .NET10: dotnet publish -c Release -r osx-x64 --self-contained true -p:PublishSingleFile=true -p:IncludeNativeLibrariesForSelfExtract=true. Ship the original arm64 host as side-screen-host-arm64 and this osx-x64 output as side-screen-host-x86_64; install the included uname dispatcher as side-screen-host with executable permission. Never lipo .NET single-file executables because appended assemblies would be destroyed. Original source/license/provenance notes still apply.

Driver source used for the universal Audio-v6 package is included at mac/audio-v6.1 for microphone and speaker. Both BlackHole.xcodeproj targets build with xcodebuild -target BlackHole -configuration Release ARCHS="arm64 x86_64" ONLY_ACTIVE_ARCH=NO CODE_SIGNING_ALLOWED=NO MACOSX_DEPLOYMENT_TARGET=14.0. Original driver licenses, notices and project settings are retained. Native Swift runtime, Apple frameworks, Sparkle, Rust, .NET and libsodium dependencies retain their own original licenses; existing baseline includes available dependency sources and provenance. Exact frozen legacy binary provenance limitations from the original README remain applicable.

No signing identity, private key, provisioning profile, user pairing, credentials, log or screenshot is included. Rebuilds use the builder's own signing identity. No Developer ID notarization or Intel hardware test is claimed.
