[jcelerier]

Changes

• Resolve application-test static plug-in links after add-on discovery, and use that path for the state tests and ObjectGallery.
• Make the generated static plug-in initializer inline, and export/link ImportedUi rather than compiling duplicate implementation and moc definitions into its test.
• Share production resource initialization with minimal application fixtures; register process resources once and fonts for each QApplication lifetime, using QPointer to handle address reuse.
• Fix Windows near/far/Polygon collisions, Winsock socket handling, glibc-only heap perturbation calls and portable aligned allocation in affected tests.
• Document the CLANG64 test environment and static debug-build storage requirements.

Verification

• Full default build passed in the MSYS2 CLANG64 shell after rebasing onto upstream master and its updated Avendish pin.
• Focused CTest run: 21 passed, 3 graphics executables skipped under the offscreen platform. Native Windows reruns of those graphics executables passed; one Linux-specific high-DPI subprocess case remained skipped because /proc/self/exe is unavailable.
• After the upstream update, all 9 selected tracking/application-fixture regressions passed.
• Rebuilt score executed a startup script requesting exit code 17 and returned 17; ObjectGallery --list completed successfully.

Cross-repository context

• ble: make asynchronous adapter discovery reusable score-addon-ble#14 fixes the invalid-future crash exposed when BLE is loaded by repeated application fixtures. Merge that fix first for configurations enabling this add-on.
• Tracking protocol coverage was exercised with protocols: fix device compatibility and tracking packet conformance score-addon-trackingprotocols#8.
• The configured full build also included node: unify frame production and embed the engine builder score-addon-librediffusion#28 and its linked dependency PR.

Scope

Only the 20 session-modified tracked files are included. No unrelated untracked files or dependency edits are included. The machine-local test-PDB suppression policy and generated build artifacts are deliberately excluded; repository debug defaults and enabled tests are unchanged.

---

Also here: the OSC type tags test, recovered from #2322

#2322 was closed because it pinned
3rdparty/libossia to the pull request branch of ossia/libossia#957 rather than
to a commit on libossia's master, so it could never be merged. The test itself
was fine and was the only thing left of that work, so it rides here rather than
in a PR of its own.

tests/integration/MapperDatagramProtocolsTest.cpp gains one case for the
three-argument osc(address, values, typetags): the /spat/serv shape with
"sifffff", one argument per supported tag, a message with no tag string at
all, and a tag string shorter than the argument list. It asserts the exact
datagram bytes against hand-written OSC fixtures — address and type tag strings
padded to four bytes, network-order IEEE-754 payloads — so nothing libossia
encodes is its own oracle, and it reads the tag string back out of the packet
with its own padding arithmetic.

The libossia pin moves from 15a6c68801 to d94955801, which is that change on
libossia master. It deliberately stops there instead of at master's head: the
three geometry commits after it belong with the score-side shading work in
#2326, and one of them changes the default
ambient colour from 0.03 to 0, which has no business landing through a test PR.

Not built locally — the integration tests are not configured in the build tree
I have here, so this one case is on CI to compile and run.

---

And: the AppImage build needs no FUSE whichever workflow calls it

This is what sat-mtl/livepose#83 one failing job was
dying of, and the same hazard sits under every tool repo's packaging job.

ci/appimage.build.sh runs appimagetool, which is itself an AppImage, so it
needs either FUSE or APPIMAGE_EXTRACT_AND_RUN. FUSE is unavailable under
rootless docker on the self-hosted host — which is exactly why appimage.yml
sets the variable on the job, and why appimage.deps.sh says in so many words
that libfuse2 is therefore not required. The tool repositories reach the same
script through ossia/actions/custom-score-build, which does not set it, so
they die at the one place that depends on it:

/usr/bin/fusermount3: mount failed: Operation not permitted
Cannot mount AppImage, please check your FUSE setup.
open dir error: No such file or directory
##[error]Process completed with exit code 127.

The real fix is in the action — ossia/actions#29 —
because the tool repos pin ossia/actions/...@master and build score from
score's master, so a change living only here reaches none of them until this
PR merges. That PR also covers package-custom-app, which runs
tools/create-app-linux.sh for the app's own AppImage: livepose never got
that far, so fixing only score's script would have moved the failure instead of
removing it. The ${VAR:-1} default kept here is for anyone running the script
by hand on a machine without FUSE.

Reproduced and verified locally — appimagetool on a minimal AppDir with no
fusermount on $PATH:

	exit	result
variable unset	127	open dir error: No such file or directory, no AppImage — the CI failure, verbatim
APPIMAGE_EXTRACT_AND_RUN=1	0	AppImage written (948 KB)

[coveralls]

Coverage is 47.78% — fix/clang64-static-test-build into master. No base build found for master.

[jcelerier]

Merged into #2326 (gfx/shading-tiers) at 7f22521. libossia resolved to master 3e7ee8462e (same tree as c5d5ed307b). Closing in favour of #2326.