Intel source-build notes for v3.4.0 (A1707/OCLP; unofficial experiment)

[sidosea]

I understand that upstream does not plan to support Intel Macs, as discussed in #43 and #523. This is a source-build experiment for people who want to investigate it themselves, not a request to reopen that decision. I am also aware that other Intel forks already exist; I am sharing my own reproducibility notes, not claiming to be the first to build it.

Source branch: https://github.com/sidosea/vorssaint-utils/tree/community/intel-build-3.4.0

The branch is based on v3.4.0, not v3.4.1. It contains Intel build changes, a portable opt-in workaround for duplicate SwiftBridging maps in my Command Line Tools installation, English/Korean build instructions, and a test record. It creates a separately identified local app called Intel Build Lab, with its own icon and bundle ID, ad-hoc signing, and official self-updates disabled. No app/DMG binary or release is uploaded.

My earlier private build was tested on a MacBook Pro A1707 with OCLP and macOS Sequoia 15.8. I manually checked launch/relaunch, Korean UI/settings persistence, idle behavior, window layout, clipboard, audio adjustment, sleep/wake and quitting, without an obvious issue in those checks. Battery percentages differed between the app, macOS and RunCat; the cause is unknown. Screenshots and several hardware/permission cases remain untested, and the exact OCLP version was not recorded.

The public branch has additional identity/build-script changes. Its build/package checks are documented separately from those earlier GUI observations:
https://github.com/sidosea/vorssaint-utils/blob/community/intel-build-3.4.0/docs/INTEL-TESTING.md

This is not a claim of full Intel compatibility, a warning-free build, an Apple-notarized app, or a security audit. Fan-helper certificate checks are retained; hardware fan control is not claimed to work. The independent identity requires fresh settings/permissions, and official updater compatibility is not assumed.

If these notes help you, please report experiment-specific findings on my fork rather than treating them as upstream Intel support requests. There is no promise of ongoing maintenance. Thanks to the original project and previous Intel experimenters for their work.