Professionalize public release, installer, README, and landing page

[masarray]

What changed

• Reposition ARSVIN as a focused IEC 61850 Sampled Values suite with separate Publisher and ArSubsv Subscriber workflows.
• Rewrite the public README with clear capabilities, safety boundaries, release artifacts, build instructions, Apache-2.0 positioning, and real application screenshots.
• Add three optimized WebP captures from the actual Publisher and Subscriber applications, including SV Setup, waveform/phasor/RMS monitoring, and live channel analysis.
• Add a repeatable PowerShell release packager for two self-contained single-file Windows applications and a portable suite ZIP.
• Add an Inno Setup installer containing Publisher, Subscriber, documentation, samples, shortcuts, and an uninstaller.
• Replace the release workflow so tags create portable EXEs, installer, ZIP, and SHA-256 checksums.
• Harden local build scripts so failed external dotnet commands stop the build.
• Expand CI to build and check both Publisher and Subscriber.
• Redesign the GitHub Pages landing page with compact responsive styling, real product screenshots, direct latest-release links, structured SEO data, FAQ schema, and honest safety language.
• Refresh the web manifest, sitemap, legal notices, quick start, release documentation, documentation index, contribution guidance, and GitHub metadata guide.

Release assets

A tagged build is designed to publish:

• ARSVIN-Publisher-win-x64.exe
• ArSubsv-Subscriber-win-x64.exe
• ARSVIN-Suite-Setup-win-x64.exe
• ARSVIN-win-x64-portable.zip
• SHA256SUMS.txt

Safety and distribution

• Binaries remain unsigned; no paid code-signing dependency or placeholder secret is introduced.
• Npcap is not bundled or silently installed.
• The installer uses a per-user installation path and warns when Npcap is not detected.
• Live raw Ethernet usage remains explicitly limited to authorized, isolated laboratory networks.

Validation

• Windows CI previously passed for Publisher restore/build, Subscriber restore/build, unit tests, and dependency vulnerability reports; checks restart automatically after the screenshot commits.
• All three WebP assets were written to the PR branch and verified through the GitHub contents API.
• Landing-page structured data now declares the real screenshots through the SoftwareApplication.screenshot property.
• Release workflow paths, semantic-version handling, stable asset names, required installer inputs, and checksum generation were reviewed.
• CodeQL is handled by the repository's PR security workflow.
• The installer/release workflow itself still needs its first manual or tagged Actions run because it is not triggered by pull requests.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0eb0561a09

ℹ️ 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]

Avoid publishing a dead installer CTA

Since the Pages workflow deploys site/** on pushes to main, this landing page can go live before the tag-driven release workflow has created any assets; the public repository currently has no releases, so this /releases/latest/download/... URL sends users to a missing/non-download target. Until the first installer asset is guaranteed to exist, point the primary CTA at the releases page or gate this direct asset link behind the release.

Useful? React with 👍 / 👎.