Fix historical domain release metadata compatibility

[azurras]

What changed

• classify historical four-field release metadata from the exact executable JAR
• atomically backfill only the missing domainSchema field
• preserve the original timestamp scalar across PowerShell 7 and Windows PowerShell 5.1
• reject release paths outside the protected releases root and malformed scalar metadata

Why

The approved Mongo consolidation cutover stopped before effects because production releases were built before domainSchema was added to release.json. This compatibility boundary upgrades only validated historical metadata and keeps all malformed or ambiguous inputs fail-closed.

Validation

• focused orchestration Pester: PS7 72/72
• focused orchestration Pester: Windows PowerShell 5.1 / Pester 5.9 72/72
• full Windows production Pester: 694 passed, 0 failed, 28 guarded skips
• Node migration contracts: 9/9
• full :cbell-lib:test :website:check :website:bootJar --rerun-tasks: BUILD SUCCESSFUL
• independent review: APPROVED, 0 Critical / 0 Important / 0 Minor