tenant.openagents/omega

Let one Omega host prove two device surfaces at once (omega#49)

Let one Omega host prove two device surfaces at once (omega#49) The device-proof harness admitted exactly one device key, so an iOS result and an Android result could only ever be two separate runs against two separate hosts. omega#49 asks for a result on both, and a host that can only hold one grant proves the fan-out by assertion rather than by running it. `OMEGA_DEVICE_PROOF_DEVICE_PUBKEY` is now a list, and one host pump fans its projections out to every grant it holds. Two things the harness could not previously say, both of which cost this issue a wrong diagnosis: - **Whether a seeded source reached a given grant.** "The host admits the engram and never projects it" was read off a device surface and recorded on the issue. The host had projected it — to both grants — and the device had it decrypted in hand. `source_was_projected` is now printed per grant per seeded source, so the host states this rather than leaving it to be inferred from a screenshot. - **The record id of Sarah's own messages.** `sarah_conversation_wrap` returned only the gift wrap, whose id is not the id anything downstream uses: the host stores the rumor under its own id and projects that id to the device. The harness was logging an identifier that appears nowhere else in the system. Proven on `ios-simulator (iPhone 17 Pro, iOS 26.5)` and `android-emulator (khala_test, Android 15 / API 35)` against deployed `wss://relay.openagents.com`: two devices paired to one host, each send projected to both, and both grants revoked in one pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>