typing/typing.start fails for chats with 'any;-;' guid prefix

[chunwu-us]

Description

imsg typing and the RPC typing.start/typing.stop methods fail to find chats whose DB guid uses the any;-; prefix instead of iMessage;-;.

Steps to reproduce

1. Have a chat in chat.db with guid any;-;user@example.com
2. Run: imsg typing --chat-id 1 --duration 5s
3. Or via RPC: {"jsonrpc":"2.0","method":"typing.start","params":{"to":"user@example.com"},"id":1}

Expected

Typing indicator is sent (or a clear error about IMCore limitations).

Actual

typingIndicatorFailed("Chat not found for identifier: iMessage;-;user@example.com. Make sure Messages.app has an active conversation with this contact.")

The CLI/RPC constructs iMessage;-; as the identifier prefix, but the actual DB guid is any;-;. The --chat-id path also fails because it resolves to any;-; from the DB and then searches for it in IMCore using a mismatched format.

Environment

• imsg 0.5.0 (Homebrew)
• macOS 15 (Sequoia), Apple Silicon VM (Lume)
• Messages.app signed in and running

DB state

SELECT ROWID, guid, chat_identifier FROM chat;
-- 1|any;-;user@example.com|user@example.com

Possibly related to self-messaging or VM-specific iMessage routing where the service type isn't resolved to iMessage or SMS.