[masarray]

Goal

Finish ARStack's user-facing P1/P2 without WinGet or a separate Microsoft package-manager account.

P1 — approachable open source

• Add practical SCL import troubleshooting for users whose SV ID/MAC fields do not appear.
• Link GitHub-first support, community interoperability experiment reports and discoverable reports index.
• Extend README, Getting Started, website footer and Support navigation.
• Use GitHub Issues as the working community channel; no dependence on enabling Discussions.

P2 — direct downloads, no external package manager

• Remove the WinGet generator and corresponding workflow; remove WinGet from public README and installation guide.
• Create a new M3.H.1 cross-platform packaging release, only after all PR CI passes and merge to main.
• Package exact original tested M3.H Windows Setup, Portable and firmware bytes, with a previously accepted, exact-tag Linux AppImage from successful run #40089029880.
• Check the original 5 M3.H release asset digests, source commit, Linux acceptance run identity and Linux checksum before creating the new release.
• Publish 7 assets: Windows Setup, Windows Portable, matched firmware, firmware manifest, combined checksum file, Linux AppImage and Linux checksum.
• Confirm original M3.H five asset IDs/digests remain unchanged; do not touch the frozen original release.

Scope

No SV/PTP servo, timing, firmware source, Studio runtime, external relay claim or vendor-specific engineering changes. Packaging-only next release uses existing code/binaries.

Checks

Product Naming Guard, public navigation and CI routing on PR; release publication job will not run in PR, only on merge to main after release/latest and artifact guards.

[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-24T12:37:41.421969Z	d526062	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.