feat(meizu-m8): add Windows CE device support

[doodlewind]

Summary

• add a pinned Windows CE 6 / ARM build profile, QuickJS and GDI host, and touch demo for the Meizu M8/M8SE
• add a macOS libusb-to-ActiveSync bridge plus PPP, SynCE DCCM, RAPI deployment, status, acceptance, and framebuffer capture tooling
• add build-ID-qualified executables and runtime receipts so historical processes cannot overwrite current evidence

Validation

• bunx tsc --noEmit
• bun test tests/meizu-m8-profile.test.ts tests/platform-contracts.test.ts tests/npm-package.test.ts (39 passed)
• strict C syntax check for the libusb bridge and sh -n for all Meizu scripts
• bun meizu-m8 build: WinCE ARM PE produced from pinned inputs
• real M8SE over mini-USB: Windows CE 6.0.3122, ARM CPU 2934, PPP and SynCE RAPI connected
• current build abec49b1394a0f971af25fc791c33a4d: state=running, boot_stage=10, guest frames 60 to 120, GDI composites 33 to 53, capture_successes=1, capture_error=0
• captured 320x480 framebuffer SHA-256 d9a1715ed955c65561df05c226aee56c4fdf2a1e791c16ffabe29ed63e8c51e4 and visually checked the rendered demo
• real touchscreen path recorded hero_tap 16 times on the preceding diagnostic build; the final build changed only receipt path isolation and deployment cleanup after that interaction proof

Known validation environment issue

The full suite completed 389/391. Two unrelated temporary Mach-O helpers (iPhone 2G transaction and Symbian scan-matrix tests) timed out while macOS held them at dyld_start for minutes; their assertions did not fail, and all Meizu tests passed.