fix: harden domain cutover runtime recovery

[azurras]

What changed

• makes every Spring @Repository adapter proxy-compatible so candidate startup cannot fail on final classes
• makes no-ledger/no-stage prepublication recovery tolerate legitimate live legacy writes while keeping staged cleanup evidence-bound
• permits the exact historical legacy release during v2 rollback reconciliation when older metadata has no domainSchema
• refreshes the installed writer-start guard before restarting the legacy release

Why

The first guarded production cutover stopped safely during candidate startup. Recovery then exposed three independent compatibility gaps. This hotfix closes those gaps without weakening publication, evidence, or deletion checks.

Validation

• :website:test :website:bootJar — BUILD SUCCESSFUL
• full PowerShell 7 production suite — 701 passed, 0 failed, 28 guarded skips
• Windows PowerShell 5.1 changed-boundary suite — 292 passed, 0 failed, 2 guarded skips
• direct disposable Mongo migration matrix — 25 databases, 52 kinds, 126 indexes, 14 targets, 52 drops, 468 fault boundaries
• Node migration contracts — 9/9
• PowerShell parsing on PS7 and PS5.1; JavaScript syntax; git diff --check

Production is currently healthy on the restored legacy release. No legacy collection was deleted by the failed cutover.