Migrate current ARSVIN releases to GPL with commercial licensing

[masarray]

Licensing model

• preserves the final Apache-2.0 revision at 9440f08b6909ef2dc93dd483cfdcb4e1e86077d0 on archive/apache-2.0-final
• changes current community source and later public release packages to GPL-3.0-or-later only
• adds a separate negotiated commercial path for proprietary integration, OEM or white-label distribution, closed-source redistribution, private branches, support, training, and engineering services
• states that COMMERCIAL-LICENSE.md is an invitation to negotiate, not an executed license, and grants no additional rights by itself
• adds copyright, trademark, CLA, DCO, licensing-transition, and provenance records

Wording and public presentation

• audits and updates README, release documentation, operational wording, repository guidance, landing page, JSON-LD, manifest, generated documentation, and SEO guidance
• separates Publisher evidence, Subscriber evidence, and external IED behavior
• removes unqualified conformance, calibration, deterministic timing, functional-safety, cybersecurity, switching-authority, and IED-consumption implications
• restricts external software to lawful black-box interoperability use and requires synthetic, contributor-owned, or documented authorized fixtures

Packaging and automation

• packages the GPL text and required current notices in installer and portable releases
• excludes the historical Apache license from current GPL packages
• adds current-license, provenance, package, and public-wording verification to build, CI, and Pages workflows
• preserves actual third-party notices, locked dependencies, SBOM, checksums, and release-attestation boundaries

Validation expected

• current-license and public-wording verification
• public terminology neutrality verification
• static documentation site build and validation
• locked restore
• Publisher and Subscriber Release builds
• deterministic tests and coverage gates
• release packaging, installer smoke test, SBOM, checksums, and artifact validation

Legal scope

The repository records support the intended licensing model but do not by themselves resolve employment, invention-assignment, confidentiality, customer, trademark, or other off-repository obligations. A significant commercial agreement still requires review of the exact rights and deliverables involved.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.