[masarray]

Goal

Prepare the public-facing repository for future releases without modifying validated SV/PTP firmware, merging divergent feature PRs, or hardcoding the next tag.

Changes

• README and Studio onboarding point to GitHub /releases/latest; historical M3.H measurements remain attributed to M3.H.
• Simple first steps for Windows and Linux in docs/INSTALL.md.
• SHA-256-verified interactive Windows installer bootstrap that discovers the actual Setup EXE from the latest stable GitHub release.
• Linux x86_64 AppImage build/packaging/GUI smoke workflow. PR builds are artifacts only; attaching to an existing release requires explicit workflow_dispatch with a release tag and builds that exact tag.
• Linux command-line installer fetches the latest stable AppImage only if it exists, checks the published SHA-256, and installs under the user's home directory.
• WinGet manifest generator with explicit installer type and package version. WinGet is not advertised as installed/available until microsoft/winget-pkgs has accepted the manifest.
• Public copy naming guard; commercial product names removed from selected public release docs.

Release boundary / non-claims

• No changes to source files for SV/PTP, embedded firmware, data model or network behavior.
• The Linux build must pass its own CI and release-attached assets must appear in /releases/latest before being advertised as available.
• Existing M3.H Windows binaries and SHA-256 remain untouched.
• Website and portal changes are handled in a separate PR in masarray/masarray.github.io.

Reviewer acceptance

• Confirm latest-release links and installer file selection.
• Execute Python naming guard and WinGet manifest script tests.
• Confirm Linux CI builds and probes AppImage.
• Confirm no current public tag/assets were altered.

[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	✅ Completed 2026-10-24T08:55:28.815593Z	647f808	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]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 647f808cc9

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use a runner compatible with the downloaded Qt binaries

The new AppImage workflow runs on Ubuntu 22.04 but installs the official Qt 6.10.3 gcc_64 binaries. Qt's supported-platform documentation states that these binaries are built on Ubuntu 24.04 with glibc 2.39 and require rebuilding from source on older glibc versions; Ubuntu 22.04 provides glibc 2.35. Consequently, the Qt build tools and linked Studio executable cannot run on this runner, preventing both PR artifact creation and release publication before packaging completes. Use Ubuntu 24.04 or build a compatible Qt distribution from source.

Useful? React with 👍 / 👎.

[masarray]

Independent M3.H release hygiene CI observation (2026-10-24)

The current #301 exact head 6ff68f229a260b5c9f054e6cbcfe8fcf93a8424d has an ARStack Studio Linux AppImage workflow failure: run 40080084205, job "Build and test Linux x86_64 package", step "Install Qt 6". The aqtinstall resolver for linux desktop 6.10.3 gcc_64 --modules qtserialport returned: "The packages ['qt_base', 'qtserialport'] were not found while parsing XML of package information!" The attach job was skipped.

Recommended exact-head fix: verify the published Qt version/architecture and module listing from the runner (aqt list-qt linux desktop --arch <version>, aqt list-qt linux desktop --modules <version> gcc_64), then pin an actually available supported Qt version and rerun AppImage packaging plus GUI smoke. Do not attach an unbuilt Linux asset or advertise Linux availability before PASS. This does not invalidate the existing Windows M3.H Stable release (five original binaries remain immutable).

M3.H mainline SMV PR cleanup is independently complete through #299 / #302 / #303; keep this forward-looking distribution PR separately gated.