[masarray]

Physical feedback / reproduction

User installed PR #262 through Studio. Firmware pane showed semantic version v0.1.1 and Device ready, hiding 16-digit bundled/observed build identifiers. Time Sync then displayed START FAILED, without the reason in GUI. Old capture report c959... predates new verified install and is not a reliable check of the current board identity. Screenshots alone do not prove PHY/MAC cause.

Root findings

• FirmwareManager and DeviceController already have exact expected/observed build IDs; FirmwarePanel displayed neither. Completion step was based on compatible protocol, not exact matching firmware.

• Native PTP startup has independently arriving positive role PTP2 and runtime STATUS readbacks. Immediate rejection upon an earlier STOPPED or stale role status is a false negative. Correct behavior must wait for BOTH positive signals within the existing absolute timeout; never fake a lock or skip STOP rollback.

• All distinct START errors were collapsed into a generic badge. The ESP32-P4 SOURCE already tracks actual Announce, Sync, Follow_Up, and TX failures but failed to report them at readiness timeout.

Implementation

• UI always displays bundled and observed build ID and exact MATCH/MISMATCH, keeps semantic product version, and fixes misleading bootloader target/reinstall labels.

• DeviceController retains specific START failure reason plus transaction stage across STOP rollback; native PTP status accepts positive PTP2 and STATUS evidence in either order while remaining bounded/fail-closed.

• SOURCE firmware logs concrete 4 counters (and readiness flag) ONLY at failed startup. On failed START, Ethernet diagnostics use the SAME ETH_EVENT FreeRTOS event bit already used by the 4kHz publisher to distinguish link DOWN vs link UP/role runtime invalid, with no polling task, no PHY ioctl and no hot-path changes.

• Time Sync shows concise fault text ONLY when needed; Copy diagnostics includes exact stage and detailed logs. No standalone scripts or external bench kit.

• Regression structural gates cover exact build UI, bounded runtime proof and single owner Ethernet link diagnostics. PTP SOURCE firmware, Qt, Native Preview, Windows Lifecycle CI must PASS on exact HEAD before artifact.

Not merged to main. Physical PTP TX/relay acceptance is still required; no software-only LOCK claims.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-20T11:06:27.412154Z	c9725e7	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[masarray]

M3.H release=main reconciliation — 2026-10-24

Verified product baseline is a922e9bdba4e57a4e88406eb83344455dd8ff142 (ESP32-P4 firmware Build ID a922e9bdba4e57a4); consolidated PR #299 is MERGED to main with 14/14 integration checks passing. The official M3.H Stable tag and tested source are ancestors of main.

This PR has a distinct historical/divergent change scope and is not part of the immutable shipped M3.H baseline. It remains DRAFT / NOT READY for merge; do not merge against an obsolete stacked base or count its tests as final M3.H acceptance. Reconcile only still-needed unique behavior into a fresh branch from current main, with implementation-level comparison, all affected CI tests, and targeted ESP32-P4 FAT where relevant. If superseded, close with an explicit feature-by-feature disposition instead of importing old firmware wholesale.

Canonical closure record: https://github.com/masarray/arstack61850/blob/main/docs/integration/M3H_MAINLINE_RELEASE_SOURCE_CLOSURE_2026-10-24.md .

[masarray]

PR archival decision — M3.H release hygiene (2026-10-24)

CLOSED as SUPERSEDED HISTORICAL IMPLEMENTATION — NOT MERGED and NOT marked as a completed feature.

• Historical PR head (preserved): 8d50911172d4f2c52fdf950f5c33f255e90ef351.
• Validated/shipped firmware+Studio commit: a922e9bdba4e57a4e88406eb83344455dd8ff142, integrated through merged Integrate tested M3.H Process Bus source into main without release drift #299 into main (14/14 integration CI PASS).
• Disposition: Legacy firmware pane/start recovery branch predates exact M3.H paired Build ID; compare missing UX behavior with current main before new patch.
• Canonical open acceptance owner(s): Post-M3.H Studio: firmware identity, guarded PTP recovery, USB and operator UX acceptance #300.

This branch diverges from current main; its unique changes have not passed the validated M3.H release gate. The old source and discussion stay reachable for traceability. Future implementation must be a new, narrowly scoped PR based on current main, with focused CI and hardware evidence where applicable. Closing the obsolete PR removes misleading release-ready queue items while preserving the unresolved feature requirements.

Evidence ledger: M3.H Mainline Source Closure.

[masarray]

Archived as superseded post-M3.H implementation (2026-10-24)

NOT MERGED, NOT accepted as complete. Historical branch head 8d50911172d4f2c52fdf950f5c33f255e90ef351 is preserved. The actual M3.H source a922e9bdba4e57a4e88406eb83344455dd8ff142 is already merged into main via PR #299, with 14/14 integration CI.

Legacy firmware pane/start recovery branch predates exact M3.H paired Build ID; compare missing UX with current main.

Outstanding feature acceptance lives in #300; old stacked branch cannot be merged safely. Re-implement missing behavior from current main, supported by focused regressions and hardware evidence, and release under a new tag. Closure ledger.