P3: versioned declarative SV profile manifests

[masarray]

Scope

This phase adds the safe, versioned manifest layer required before ArSubsv can accept source-backed multivendor profile definitions without hardcoded vendor branches.

Implemented

• arsvin.sv-profile-manifest/v1 JSON document model
• bounded JSON parser with enum-safe serialization
• structural and semantic profile validation
• case-insensitive duplicate-ID rejection
• explicit trust levels for external, reviewed, and repository-managed manifests
• evidence-maturity capping so untrusted JSON cannot self-assert VerifiedStandard, VerifiedCapture, or VerifiedLab
• manifest provenance added to every loaded profile
• deterministic built-in and external catalog composition
• fail-closed collision handling for built-in profile IDs
• trusted-repository-only override gate
• safe fixed-layout research example
• deterministic parser, trust, collision, and detector integration tests
• engineering and safety documentation

Validation at head 5a1634b

• CI: passed
• Publisher warnings-as-errors build: passed
• Subscriber warnings-as-errors build: passed
• test and coverage gates: passed
• dependency vulnerability checks: passed
• Windows portable and installer build: passed
• installer silent smoke test: passed
• SBOM, checksum, and release-artifact validation: passed
• GitHub Pages validation: passed
• CodeQL: passed

Safety boundary

This phase does not automatically activate external manifests in the live Subscriber. It builds and validates the engine contract first, so an unreviewed file cannot silently change payload decoding, scaling, or live health decisions.

Pending after this tranche

• ArSubsv runtime import and profile catalog selection UI
• repository-managed fixture packs for 9-2LE-style and IEC 61869-9 profiles
• byte-exact PCAP/SCL regression evidence
• measurement-context integration in the main Subscriber evidence bundle
• local capture-drop attribution
• SMU615 device-observed validation pack