chore(verify): #18 live Pi↔VM scenarios A-D pass
Harness: /tmp/scenario18-harness.mjs (WS-level assertion, pattern matches #17's /tmp/call-test-harness.mjs). - A (Pi→VM logged-out callee, Path A zero-ringee): terminal dm_call_undeliverable reason=no_recipient peerOrigin=VM elapsed 212ms (budget 2s, pre-fix 60s) - B (VM→Pi logged-out callee, symmetric): elapsed 155ms, peerOrigin=Pi - C (Path B, DM deleted on VM): relay hits Path B after DB delete, Bob offline, elapsed 140ms, reason=no_recipient - D (group DM with online member, non-regression): VM accepted (Bob rung), no toast on caller Bob's dm_call_incoming arrived in 144ms All payloads correct: terminal:true, phase:'start', failures[0].reason 'no_recipient', correct peerOrigin. peerLabel empty because both instances' federation_peers.instance_name is NULL — pre-existing state, toast code already falls back to origin hostname (not a #18 concern). Cannot merge from agent per plan Task 10 Step 7 — coordinator's call.
This commit is contained in: