[masarray]

Purpose

Integrate the exact final verified M3.H SV/PTP Studio + ESP32-P4 source into main, using an explicit two-parent merge, while retaining main's post-release docs/landing/CI updates. Do not rebuild or replace the existing Stable release assets.

Proof of source identity and Git reconciliation

• Tested final M3.H source: a922e9bdba4e57a4e88406eb83344455dd8ff142 (10/10 exact-SHA workflows SUCCESS).
• Candidate two-parent merge: 7b8c72e6df1a22c8e44d5b05dc1cad0bd0e11245, parents 19c5f08fa3d7fac28c2587ee76639cec9732a4e3 (main) and a922e9bdba4e57a4e88406eb83344455dd8ff142.
• Guarded staging run SUCCESS: zero merge conflicts; implementation CMakeLists.txt, Studio, ESP32-P4, core include/src/tests/scripts/tools identical to tested baseline; all files changed on main after fork retained with exact blob SHA; PTP/SV CI workflow files retain tested source blob SHA; no force push.
• Release binary hashes unchanged: Setup 4902e8bf..., Portable ca01424e..., ESP32-P4 BIN 61c508e9... (source/build ID a922e9bdba4e57a4).
• 40.762934-second valid M3.H PCAP: 163,048 SV, 100% smpSynch=2, 0 missing/duplicate, 44 Announce, 43 each Sync/Follow_Up; 120-second endurance and real relay lock remain unverified, not prerequisites for a public isolated-lab simulator.

Merge gate

• Run all applicable main-bound PR CI before merge: C++ CI, ESP32-P4 injector + PTP, Embedded, PTP Core, Studio Qt/Windows/Native, Naming/Routing, relevant security/smoke.
• CI on PR candidate must pass, not simply reuse the old green baseline.
• Confirm final main head hasn't advanced unexpectedly. Merge only after checking newly run tests; use merge commit, not squash/rebase, preserving the original parented source history.
• Once main's tree contains exact shipped code, close superseded stacked PRs M3.A–D FAT repair: simulated Global GM on boot/fallback and lossless warm SV STOP/START #295–M3.H: Stop measured SV smpSynch flapping at PTP Follow_Up TX epochs #298 with a traceable note (not arbitrary issue closure). Triage sibling P0: restore relay-bench GM global SV sync + bounded STOP/START phase continuity #294 and broader source/feature issues separately.
• No post-acceptance firmware logic changes, no fake GPS/relay certification, and no changes to already-published Stable assets.

Refs: release, source audit.

Final Git ancestry provenance (release = main)

• Final reviewed head: c90a9798508fe5146d53cf3173b2980ded557198.
• Original source integration commit 7b8c72e6... merges main and the validated M3.H source exactly (source files untouched, current main files kept).
• A second documented, tree-identical metadata/lineage merge carries the official release tag commit a4b6e53d0dbbcababc55ba8a4ff97ade6f2a6200 as a Git parent. Its tree is exactly 19a1a9ce34d0b5f0f56fe2fbc56cd93726ef5ec5, identical to the verified source integration tree. The tag's five commits add historical release documentation and an old prerelease publishing workflow; their ancestry is retained without re-enabling obsolete publisher logic or replacing newer Stable docs from main. Compare release tag...candidate: ahead, 0 behind.
• CI gate for merge is the NEW exact candidate head c90a9798..., not the superseded first candidate 7b8c72e....