Configured transfer targets are not transfer evidence

Negotiation / Frontline learning, observed 2026-09-04 from deployed web source plus production Supabase and Railway event lineage: a configured transfer destination (from a load record or captured universal context) must never be used as evidence that a transfer was attempted or completed. Frontline hydrated transferPhone from configuration for ordinary calls, then isTransferAttempt treated any phone as proof and defaulted the label to “Transferred.” Gate transfer UI and enrichment on explicit persisted evidence (call_transferred, a typed transfer_status, or an event-owned result.transfer_phone), and keep bid-review versus transfer notification kinds/templates explicit and separately observable.