Add adoption onboarding and field-proof evidence

[masarray]

P3 — Adoption & Field Proof

• add bilingual Quick Start, FAQ, Compatibility Evidence and Guided Demo routes
• expand the site registry to 54 pages, 53 indexable URLs, 17 Indonesian pages and 17 reciprocal hreflang pairs
• turn the homepage and Download Center into an adoption path rather than a binary-only funnel
• publish a machine-readable service-level compatibility registry with two anonymized evidence profiles and zero named device claims
• add local-only symptom search and category filters to both Guide hubs
• generate responsive WebP screenshot variants, validated srcset/sizes, and responsive hero preloads
• add structured issue forms for compatibility, connection, reporting, file transfer, GOOSE, installation and feature requests
• generate an SPDX 2.3 package inventory during the primary Windows release workflow and attest exact installer/portable build outputs
• keep an explicit manual checksum-verified backfill workflow for existing tags without duplicating the primary release workflow
• preserve the current stable release boundary: no retroactive SBOM, provenance, signing, vendor or conformance claim

Evidence boundaries

• the guided demo uses real screenshots but is not a simulated relay session or time-to-value claim
• compatibility is stated per service, date and condition; verified is not IEC 61850 conformance certification
• no vendor, model, site, customer or firmware identity is publicly named in the initial registry
• guide search text remains inside the browser and is not emitted as an analytics event
• issue forms require sanitization of credentials and confidential project/device evidence
• primary supply-chain attestations apply to exact release build outputs; manual backfill applies only after exact published assets pass their checksums
• SPDX packageVerificationCode follows the SPDX 2.3 SHA-1 file-code algorithm while individual files also carry SHA-256

Validation

• deterministic 54-page product build and 53-URL sitemap: passed
• 17 Indonesian pages and 17 reciprocal hreflang pairs: passed
• seven-step bilingual Quick Start: passed
• twelve-question bilingual visible FAQ and FAQPage schema: passed
• two bounded anonymized evidence profiles and zero named-device claims: passed
• seven-step bilingual guided demo using real screenshots: passed
• eleven locally filterable troubleshooting cards in both languages: passed
• responsive WebP image and hero-preload candidates: passed
• structured issue-form and sanitization contracts: passed
• primary release attestations and explicit manual backfill separation: passed
• SPDX generator and packageVerificationCode fixture: passed
• existing SEO, release trust, privacy, measurement, authority, indexing and public-boundary gates: passed
• internal links and fragments: passed
• search-growth and measurement contracts: passed
• ARSAS source, premium UX, GOOSE and SAS invariants: passed
• ARIEC61850 API compatibility: passed
• .NET restore, Windows compile and portable x64 publish: passed
• installer compile, silent install/uninstall smoke test, checksums and artifact upload: passed

After merge, the Pages workflow deploys and attests the four adoption pairs, guide filtering, compatibility registry and responsive media before notifying search engines.