tenant.openagents/omega

Send the proof harness's Sarah half the way the host actually reads it (omega#49)

Send the proof harness's Sarah half the way the host actually reads it (omega#49) `7bb06ca215` moved the harness off kind 14 and onto 44300 because the host subscribes to the Sarah record kinds. That made the events arrive — the exact event id the harness published started showing up in the host's quarantine map seconds later, where on kind 14 the host had no opinion about it at all — but it was the wrong destination. Kind 44300 is a `Turn`, whose body must be NIP-44 ciphertext of JSON. The harness sends prose, so `decrypt_record` failed and the reply was quarantined instead of projected. Kind 14 was right; publishing it bare was not. A conversation message reaches the host the same way the owner's own does — a NIP-59 gift wrap addressed to the host's custody key, carrying a kind-14 rumor, unwrapped into a `message` record. The harness was publishing the rumor naked to the relay, which no filter requests. So the reply arm of omega#46 exit 1 has never run: first the events were never delivered, then they were delivered and refused. Sarah's reply and the seeded greeting now go through `EventBuilder::gift_wrap` with tags from the production `conversation_tags` builder, so the rumor names exactly the owner and Sarah and satisfies `require_conversation_recipients` rather than approximating it. Two more defects the same run exposed, both of which made the harness prove less than it claimed: - The seeded engram was prose, but an engram body must be a JSON object with a `mem/…` slug. The host received it, refused the body, and quarantined it, so "inspect memory" never had a real source and the withheld-source count was partly measuring this bug. - The Sarah adapter held one socket for the life of the run. A reply sent minutes after seeding went down a connection the relay had already reset, and the harness reported it as Sarah failing to answer — outwardly identical to the host never producing a reply. It now reconnects and re-authenticates once, since a new socket is a new NIP-42 session. The deliberately unreadable quarantine source stays on 44300 with prose: that one is meant to be admitted and refused, and now genuinely is. Nothing in the shipped host changed in any of this. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>