Polish landing preview and clean portable release package

Author: masarray

.github/workflows/release-package.yml

@@ -25,7 +25,7 @@ on:
       release_notes_file:
         description: 'Markdown file used as release body'
         required: true
-        default: 'docs/RELEASE_NOTES_v1.2.0.md'
+        default: 'docs/RELEASE_NOTES_v1.2.6.md'
   push:
     tags:
       - 'v*'
@@ -103,8 +103,8 @@ jobs:
           $zip = "artifacts/release/ProcessBusInsight-v$version-win-x64-portable.zip"
           $sha = "artifacts/release/SHA256SUMS.txt"
           $notesFile = '${{ github.event.inputs.release_notes_file }}'
-          if ([string]::IsNullOrWhiteSpace($notesFile)) { $notesFile = 'docs/RELEASE_NOTES_v1.2.0.md' }
-          if (-not (Test-Path $notesFile)) { $notesFile = 'docs/RELEASE_NOTES_v1.2.0.md' }
+          if ([string]::IsNullOrWhiteSpace($notesFile)) { $notesFile = 'docs/RELEASE_NOTES_v1.2.6.md' }
+          if (-not (Test-Path $notesFile)) { $notesFile = 'docs/RELEASE_NOTES_v1.2.6.md' }
           if (-not (Test-Path $notesFile)) { throw "Release notes file not found: $notesFile" }
 
           $releaseArgs = @('release','create',$tag,$zip,$sha,'--title',"Process Bus Insight $tag",'--notes-file',$notesFile,'--target','${{ github.sha }}')

AGENTS.md

@@ -264,4 +264,4 @@ scripts/verify-release-package.ps1
 .github/workflows/release-package.yml
 ```
 
-The package should contain the published app, quick-start note, license, notice files, third-party notices, and a convenience launcher only when it helps desktop users run the app.
+The package should contain the published app, quick-start note, license, notice files, third-party notices, and documents needed by desktop users.

CONTRIBUTING.md

@@ -28,7 +28,7 @@ Before opening a pull request:
 
 1. Build the solution in Release mode.
 2. Confirm the app still starts on Windows.
-3. Keep README and docs user-facing.
+3. Keep README and docs clear for engineers using the application.
 4. Add or update validation notes when behavior changes.
 5. Avoid committing `bin`, `obj`, `artifacts`, captures, logs, or local settings.
 

README.md

@@ -1,4 +1,4 @@
-# Process Bus Insight (DigSubAnalyzer) — IEC 61850 SV, GOOSE & PTP Analyzer for Windows
+# Process Bus Insight (DigSubAnalyzer) - IEC 61850 SV, GOOSE & PTP Analyzer for Windows
 
 [![CI](https://github.com/masarray/DigSubAnalyzer/actions/workflows/ci.yml/badge.svg)](https://github.com/masarray/DigSubAnalyzer/actions/workflows/ci.yml)
 [![GitHub Pages](https://github.com/masarray/DigSubAnalyzer/actions/workflows/pages.yml/badge.svg)](https://github.com/masarray/DigSubAnalyzer/actions/workflows/pages.yml)
@@ -81,7 +81,7 @@ ProcessBusInsight-v1.2.0-public-beta-win-x64-portable.zip
 SHA256SUMS.txt
 ```
 
-The portable package contains a self-contained single-file Windows EXE in the `app` folder, quick-start notes, license files, third-party notices, and a small launcher batch file for convenience. Visual Studio and a separate .NET runtime installation are not required to run the portable release package.
+The portable package contains a clean single-file Windows EXE at the package root, Quick Start PDF, User Manual PDF, license file, and third-party notices. Visual Studio and a separate .NET runtime installation are not required to run the portable release package.
 
 Runtime notes:
 
@@ -141,13 +141,13 @@ Create a local portable package:
 
 ## Documentation
 
-- [`docs/QUICK_START.md`](docs/QUICK_START.md) — first run and field checklist.
-- [`docs/TROUBLESHOOTING.md`](docs/TROUBLESHOOTING.md) — adapter, Npcap, empty traffic, and timing interpretation issues.
-- [`docs/VALIDATION_MATRIX.md`](docs/VALIDATION_MATRIX.md) — practical validation scope for SV, GOOSE, PTP, SCL, and evidence.
-- [`docs/RELEASE_PACKAGING.md`](docs/RELEASE_PACKAGING.md) — portable release package design.
-- [`docs/DEPLOYMENT.md`](docs/DEPLOYMENT.md) — GitHub Pages and release automation notes.
-- [`docs/ROADMAP.md`](docs/ROADMAP.md) — user-facing product roadmap.
-- [`THIRD_PARTY_NOTICES.md`](THIRD_PARTY_NOTICES.md) — runtime and redistribution notes.
+- [`docs/QUICK_START.md`](docs/QUICK_START.md) / [`docs/QUICK_START.pdf`](docs/QUICK_START.pdf) - first run and field checklist.
+- [`docs/TROUBLESHOOTING.md`](docs/TROUBLESHOOTING.md) - adapter, Npcap, empty traffic, and timing interpretation issues.
+- [`docs/VALIDATION_MATRIX.md`](docs/VALIDATION_MATRIX.md) - practical validation scope for SV, GOOSE, PTP, SCL, and evidence.
+- [`docs/RELEASE_PACKAGING.md`](docs/RELEASE_PACKAGING.md) - portable release package design.
+- [`docs/DEPLOYMENT.md`](docs/DEPLOYMENT.md) - GitHub Pages and release automation notes.
+- [`docs/ROADMAP.md`](docs/ROADMAP.md) - product roadmap.
+- [`THIRD_PARTY_NOTICES.md`](THIRD_PARTY_NOTICES.md) - runtime and redistribution notes.
 
 ## Roadmap / Planned improvements
 

docs/QUICK_START.md

@@ -34,10 +34,10 @@ C:\Tools\ProcessBusInsight
 Open the extracted folder and run:
 
 ```text
-app\ProcessBusInsight.exe
+ProcessBusInsight.exe
 ```
 
-The default release package publishes the app payload as a self-contained single EXE. The package also includes `Start-ProcessBusInsight.bat` as a convenience launcher.
+The default release package publishes the app as a self-contained single EXE at the package root. The package also includes Quick Start PDF and User Manual PDF documents for offline field use.
 
 ## 4. Start a safe capture workflow
 

docs/RELEASE_NOTES_v1.2.0.md

@@ -1,11 +1,11 @@
 # Release Notes — v1.2.0-public-beta
 
-This public beta hardens Process Bus Insight as a user-facing open-source Windows tool for IEC 61850 Process Bus visibility.
+This public beta prepares Process Bus Insight as an open-source Windows tool for IEC 61850 Process Bus visibility.
 
 ## Highlights
 
-- User-facing README with clear download, run, build, documentation, and contribution guidance.
-- SEO-ready GitHub Pages landing page with screenshots, FAQ, social preview metadata, and structured data.
+- README with clear download, run, build, documentation, and contribution guidance.
+- GitHub Pages landing page with screenshots, FAQ, social preview metadata, and structured data.
 - Windows portable release automation for GitHub Actions with a self-contained single-EXE app payload.
 - Local PowerShell scripts to publish and verify the portable package.
 - GitHub repository setup script for description, homepage, topics, and repository feature settings.

docs/RELEASE_NOTES_v1.2.6.md

@@ -0,0 +1,38 @@
+# Release Notes - v1.2.6
+
+Process Bus Insight v1.2.6 improves the download experience, portable package layout, and product landing page for engineers who want to try the tool quickly on a Windows machine.
+
+## What's new
+
+- Cleaner GitHub Pages landing page with smaller typography, smoother navigation, and a more polished product preview.
+- Clickable screenshots with fullscreen preview, blurred background, and simple close behaviour.
+- Updated screenshot gallery and trailer section for first-time users evaluating the tool.
+- Refined FAQ for substation automation engineers preparing to use the app during FAT, SAT, commissioning, or lab troubleshooting.
+- Portable release package now opens directly from `ProcessBusInsight.exe`.
+- Release ZIP now includes `Quick Start.pdf` and `User Manual.pdf` for offline use.
+
+## Download
+
+Use the Windows x64 portable package from GitHub Releases:
+
+```text
+ProcessBusInsight-v1.2.6-win-x64-portable.zip
+SHA256SUMS.txt
+```
+
+After extracting the ZIP, run:
+
+```text
+ProcessBusInsight.exe
+```
+
+## Included documents
+
+- `Quick Start.pdf` - first-run checklist and safe capture setup.
+- `User Manual.pdf` - practical guide for SV, GOOSE, PTP, SCL validation, evidence, and timing limitations.
+
+## Runtime scope
+
+Process Bus Insight is receive-only and raw-passive. It decodes observed SV, GOOSE, and PTP traffic and helps compare live traffic against SCL engineering expectation. It does not send control commands and does not replace certified timing or relay test equipment.
+
+Npcap is required on the target machine and is not bundled in this repository.

docs/RELEASE_PACKAGING.md

@@ -1,10 +1,10 @@
-# Release Packaging — Process Bus Insight
+# Release Packaging - Process Bus Insight
 
-The release workflow creates a Windows x64 portable package for users who want to try the app without Visual Studio. By default, the application payload is published as a self-contained single EXE.
+The release workflow creates a Windows x64 portable package for users who want to try the app without Visual Studio. The application is published as a self-contained single EXE.
 
 ## Output files
 
-A release package contains:
+A release creates:
 
 ```text
 ProcessBusInsight-v<version>-win-x64-portable.zip
@@ -14,21 +14,25 @@ SHA256SUMS.txt
 The ZIP contains:
 
 ```text
-app/ProcessBusInsight.exe     single self-contained Windows application
-Start-ProcessBusInsight.bat   simple launcher
-README_QUICK_START.txt        user-facing run instructions
-LICENSE
-NOTICE
+ProcessBusInsight.exe        single self-contained Windows application
+Quick Start.pdf              first-run checklist for Windows users
+User Manual.pdf              practical user guide for IEC 61850 capture workflow
+README.txt                   short package note
+LICENSE.txt
+NOTICE.txt
 THIRD_PARTY_NOTICES.md
 ```
 
+The portable ZIP keeps startup clean: users run `ProcessBusInsight.exe` directly.
+
 ## Local packaging
 
 Run from the repository root:
 
 ```powershell
-.\scripts\publish-windows-portable.ps1 -Version "1.2.0-public-beta"
-.\scripts\verify-release-package.ps1 -PackageZip ".\artifacts\release\ProcessBusInsight-v1.2.0-public-beta-win-x64-portable.zip"
+.\scripts\publish-windows-portable.ps1 -Version "1.2.6"
+.\scriptserify-release-package.ps1 -PackageZip ".rtifacts
+elease\ProcessBusInsight-v1.2.6-win-x64-portable.zip"
 ```
 
 ## GitHub release workflow
@@ -37,11 +41,11 @@ The release workflow can be started manually from the GitHub Actions tab. It als
 
 Manual inputs:
 
-- `version` — release version label, for example `1.2.0-public-beta`.
-- `publish_release` — when `true`, create or update a GitHub Release.
-- `prerelease` — mark release as prerelease.
-- `draft` — create a draft release.
-- `release_notes_file` — markdown file used as release body.
+- `version` - release version label, for example `1.2.6`.
+- `publish_release` - when `true`, create or update a GitHub Release.
+- `prerelease` - mark release as prerelease.
+- `draft` - create a draft release.
+- `release_notes_file` - markdown file used as release body.
 
 ## Runtime prerequisite
 

docs/USER_MANUAL.md

@@ -0,0 +1,68 @@
+# User Manual - Process Bus Insight
+
+Process Bus Insight is a receive-only Windows analyzer for IEC 61850 Process Bus visibility. It helps substation automation engineers observe Sampled Values, GOOSE, PTP timing context, and SCL expected-vs-observed validation during FAT, SAT, commissioning, and troubleshooting.
+
+## Product boundary
+
+- Receive-only and raw-passive.
+- Does not send IEC 61850 control commands.
+- Does not publish GOOSE or Sampled Values.
+- Does not replace certified relay test sets or timing instruments.
+- Uses Windows/Npcap capture timestamps for screening and troubleshooting.
+
+## Before you start
+
+Use a safe capture path such as a TAP, mirror port, or isolated engineering test switch. Avoid connecting an unverified PC directly into a protection-critical path. Install Npcap when raw Ethernet frame capture is required.
+
+## Running the portable package
+
+1. Download the latest Windows x64 portable ZIP from GitHub Releases.
+2. Extract it to a local folder, for example `C:\Tools\ProcessBusInsight`.
+3. Run `ProcessBusInsight.exe`.
+4. Select the physical Ethernet adapter connected to the Process Bus traffic.
+5. Start capture.
+
+## Main workflow
+
+1. Confirm the selected adapter is correct.
+2. Observe live Sampled Values streams.
+3. Inspect GOOSE publishers and event changes.
+4. Check PTP traffic presence and timing context when available.
+5. Load SCL when available.
+6. Compare expected objects against observed live traffic.
+7. Copy findings only after checking adapter, timestamp, and capture path confidence.
+
+## Sampled Values view
+
+Use the SV workspace to check stream identity, APPID, svID, VLAN, source MAC, continuity counters, waveform, phasor, and metering context. Treat missing stream or mismatch indications as investigation leads, not final protection conclusions until the network capture path is confirmed.
+
+## GOOSE inspector
+
+Use the GOOSE workspace to inspect publisher identity, state changes, stNum, sqNum, typed dataset values, and event history. This is useful when troubleshooting interlocking, trip, alarm, or binary status behaviour during testing.
+
+## PTP timing context
+
+Use PTP visibility to confirm timing traffic presence, transport, domain, and timing source context. Timing results from normal Windows capture are useful for screening, but not for certification-grade jitter proof.
+
+## SCL validation
+
+Load SCD, ICD, or CID files when engineering files are available. The app can compare expected APPID, VLAN, MAC, DataSet, confRev, and stream identity against observed traffic. This helps identify missing, unexpected, weak, mismatched, or conflicted objects.
+
+## Troubleshooting no traffic
+
+Common causes:
+
+- Wrong adapter selected.
+- Npcap is not installed or capture permission is restricted.
+- Switch mirror port is not configured correctly.
+- VLAN traffic is not forwarded to the capture port.
+- PC is connected to the wrong network segment.
+- Traffic is not actually present from the publisher.
+
+## Evidence guidance
+
+Good FAT/SAT evidence should include adapter name, capture path, APPID, VLAN, source MAC, svID or GOOSE identity, timing context, SCL expected field, observed field, and confidence wording. Avoid overclaiming timing performance from software timestamps.
+
+## Safety note
+
+Process Bus Insight is a visibility tool. Always follow site safety rules, commissioning procedures, protection engineering sign-off, and customer test requirements.