Skipper — Codemagic trigger repo

Small helper repo used only as a build trigger on Codemagic, so we can test Skipper on a real Apple Silicon Mac (M2/M4) over VNC. Nothing is compiled here — the build is downloaded prebuilt and just launched.

Phase 0 — verify Codemagic + VNC

codemagic.yaml currently defines the vnc-smoke-test workflow, which just boots the Mac and keeps it alive so we can connect via VNC and confirm the whole path works.

Phase 1 — Skipper import/export (added later)

• download the Apple Silicon Skipper build (curl from our server),
• unpack and launch it,
• over VNC, import a test model and export the output,
• exported files are collected as artifacts: for download.

Connecting to Codemagic (manual URL / "Other")

1. Codemagic -> Add application -> Other (connect via URL).
2. Enter the repository URL: https://github.com/Atlantic18/SkipperArmTest.git (public, no key needed).
3. Start a build manually and connect over VNC.

Windows ARM64 TLS validation

skipper-arm-win-tls runs the standalone qt-trust-probe on windows-11-arm. It verifies the package SHA-256 and ARM64 PE headers, requires twelve rejected incident chains plus a successful HTTPS control, and saves the individual results and runtime-library hashes.

Build qt-trust-probe.pro with the release Qt SDK used by Skipper. Put qt-trust-probe.exe, its required runtime DLLs and Skipper's current curlCaCert.pem at the root of tls-probe.zip. Publish that diagnostic package to this repository's release assets, then dispatch the workflow with its release tag and exact SHA-256. Compare the recorded Qt DLL hashes with the application package.

The probe accepts a CA file as its first argument. With that argument omitted it examines default platform trust. Optional additional arguments select explicit HTTPS URLs; the default set is the twelve emSign G3 incident endpoints and https://example.com/. These checks require Internet access.