Resolve linker errors

Resolve the linker errors blocking the build so the integration test can run. Find the undefined symbol and missing library, update the linker inputs in the build setup to link the correct static or shared library, ensure symbol visibility rules are respected, and rebuild producing a clean link on Linux and Windows. Commit the minimal change and document why the link failed.

Before I change the linker inputs, make it easy for reviewers to accept. Surface the undefined symbol and which object or library it should come from, explain whether to prefer static or shared linking here and why, and flag backward-compatibility risks if we change symbol visibility or turn on link-time optimization.

After I merged a new rendering module, the link step now reports undefined references to functions that used to link fine. I don't know whether the build reordered libraries, the new module needs a missing dependency, or symbol visibility changed. What sequence of checks will quickly diagnose whether this is a linker ordering issue, a missing library in the linker line, or a symbol-export problem, and what is the minimal corrective action to unblock the CI run today?

Over time our team loses credibility because new modules often link locally but fail in CI or on target platforms due to different link orders, missing transitive libraries, and accidental hidden symbols. Recommend one auditing habit and one change to the build system that will reduce these cross-environment linker breakages going forward.