ARCHI2: production cutover and repository consolidation

[niakw]

Goal

Make ARCHI2 the single production control plane without dropping the proven provider-repair capabilities accumulated in the existing pipeline.

Current cutover scope

• canonical provider_catalog.json as committed provider truth (92 general / 27 VF at bootstrap)
• deterministic general/VF projections with path normalization
• catalog preservation gate for staging/LKG
• unified quick/deep orchestration in sync.yml
• quick refresh is repair-first and publish-capable; deep remains the broad rebuild/strict evidence mode
• compatibility promoter output is imported into the canonical catalog before manifests are rendered and published
• V2 validation now includes catalog/manifests

Safety

• no provider is removed by the catalog migration
• VF projection metadata must match general metadata except for the intentional ../providers/ path
• LKG/published baselines are required during staging
• identity/duration/media gates remain fail-closed

This PR remains in progress while duplicate workflows/docs/branches are audited and the native client proofs are rerun on the final HEAD.