Make GOOSE values readable and keep the workspace lightweight

[masarray]

Root-cause audit

• Event row color was tied permanently to the semantic event type, so every historical state-change row stayed blue forever.
• DataSet badges were driven directly by the engine's raw bits(xx, unused=n) renderer, which is accurate protocol evidence but not beginner-readable.
• The adapter selector relied only on the Npcap description/name and became visually blank while disabled during capture; it did not resolve the corresponding Windows network-interface friendly name.
• The editable BPF expression occupied prime header space even though normal users should not change the mandatory GOOSE EtherType filter.
• The presentation layer raised count properties on every 100 ms idle tick and retained up to 1,000 timeline rows.

Corrections

• make state-change/warning row highlights transient and expire after 5 seconds
• make DataSet value highlights expire after 5 seconds
• decode compact one-bit values as true/false
• decode IEC 61850 two-bit position values as Open [01], Closed [10], Intermediate [00], or Invalid [11]
• keep the raw renderer value available in tooltips
• resolve adapter labels through Windows NetworkInterface identity by MAC/GUID and suppress accidental ArIED61850 labels
• keep the adapter text fully visible during capture while preventing selection changes
• remove the BPF textbox from the operator UI; retain the fixed GOOSE/VLAN filter internally to reduce capture and CPU load
• replace the active GOOSE view with a lean publisher/timeline/inspector workspace
• cap the meaningful timeline at 300 rows, pending events at 512, process at most 48 per UI flush, and remove idle property-change churn

Safety

The GOOSE subscriber remains receive-only. Npcap capture, ARIEC61850 parsing, sequence/TAL supervision, SCL/live-discovery binding, and command/control behavior are unchanged.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 61bcf334ac

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

Preserve value highlights across retransmission coalescing

When a GOOSE state change is followed by a fast retransmission before the 100 ms UI flush, _pendingGooseFrames keeps only the last snapshot for that stream; that retransmission normally has IsChanged == false, so this branch never starts the new 5-second highlight even though the current value changed. This makes the inspector miss highlights for normal GOOSE change/retransmit traffic; preserve the recent-change flag separately or drive the highlight from the non-coalesced timeline snapshots.

Useful? React with 👍 / 👎.