Why:
There have been issues with C# output where things work in haxe unit tests, but the actual output code, when referenced as a dll, does not work quite the same.
Implemenation:
Output DLL.
Build a test program linked with DLL.
Have test program output error codes or etc (can we also use nunit or something nice?).
Think about a way to "automate" this and run it as an external test harness (through GH Actions?)