Align runtime with relationship governance semantics

[SarashaElion]

Summary

Build 022 closes two remaining Core/Runtime consistency gaps.

Relationship governance consistency

• runtime lifecycle evaluation now uses the governance engine attached to the Relationship
• caller-supplied governance behavior is no longer bypassed by constructing a fresh default engine inside Runtime
• tests prove injected runtime governance is respected

PAUSE vs BLOCK audit semantics

• lifecycle PAUSE now records InvocationResolved.status = "PAUSED"
• lifecycle BLOCK records InvocationResolved.status = "BLOCKED"
• paused relationships remain semantically distinct from prohibited or dissolved relationships

Conformance

• adds runtime governance consistency tests
• adds conformance semantics and fixture
• documents the runtime/core boundary

Architectural intent

A relationship must have one governance reality. Runtime should execute against the same governance semantics that Core uses, and its audit trail should preserve the distinction between temporary pause and prohibition.

This is Core/Runtime consistency work. It does not change the event schema, projection version, or bundle format.