[P1] Release workflow's macOS binary build has failed on every tagged release (v0.1.0-v0.4.0) — ctest finds no built test executable #13

The release.yml workflow's "Build release binaries (macos-14)" job has failed on every single tagged release run since v0.1.0 (confirmed: v0.1.0, v0.2.0, v0.3.0, and now v0.4.0 all show conclusion: failure for this job in Actions history — gh run list --workflow=release.yml).

Failure mode (from the v0.4.0 run, https://github.com/SoundMatt/cpp-LIN/actions/runs/30284990416):

Deployment/cpplin_tests_NOT_BUILT-b12d07c ...***Not Run   0.00 sec
0% tests passed, 1 tests failed out of 1

The _NOT_BUILT sentinel test name is CMake/CTest's standard signal that the actual test target was never compiled before ctest ran — consistent with an Xcode-multi-config-generator quirk on macOS (the "Deployment"/"Development" config names in the log are Xcode defaults, not the Debug/Release CMake normally uses), where the release job's build step likely does not pass a --config matching what its ctest invocation expects, or skips building the test target on this generator.

Downstream effect: because this job fails, the ubuntu-22.04 and windows-2022 release-binary jobs get cancelled as a dependency, and the "Create GitHub Release" job (which is gated on all three OS builds) is skipped entirely. Every release tag (v0.1.0 through v0.4.0) has shipped with a manually-created GitHub Release object with zero attached binary assets, rather than the intended automated multi-platform binaries.

Suggested fix direction: inspect the macOS job's cmake configure/build invocation in .github/workflows/release.yml — likely needs an explicit generator (-G Ninja or -G "Unix Makefiles") instead of the Xcode default, or a --config Release flag on both the build and ctest steps so they agree on which config was actually built.

Filed during the 2026-07-27 backlog-fix pass — pre-existing, not introduced by PR #12 (v0.4.0).