fix(daemon): name a Google Chat DM row after the person in it

[zfy0701]

What changed

Found in the docs/designs/google-chat-integration.md §9 end-to-end pass: after a direct message reached the agent, the console's DIRECT MESSAGES row showed the raw space id instead of the person. A DM space carries no display name, and the daemon's read port answered getChannelInfo for a DM with no name, so the name resolver had nothing to cache.

• packages/daemon/src/platforms/googlechat/connection.ts: for a DIRECT_MESSAGE space, getChannelInfo reads the space's human memberships (spaces.members.list with member.type = "HUMAN", page size 2), which app authentication allows (only Chat app memberships are excluded, verified live), and names the row after the single human member. A failed read or more than one person leaves the row on its id. Spaces are unchanged.
• Tests: the read-port test now covers the DM name and the filter, and a new case pins the two fallbacks (refused read, two people).
• Docs: §5 records where a DM row's name comes from.

Verification

• pnpm --filter @agentconnect.md/daemon typecheck: pass.
• googlechat-connection, googlechat-ingress: pass.
• eslint and prettier on the touched files: clean.

Created by Claude Code · Fable 5.1.

🤖 Generated with Claude Code · Fable 5.1

[agentconnect-md-test]

Approved. The Google Chat DM read port now derives the row name from its single human membership and preserves the space ID when the membership read fails or is ambiguous. The existing channel-name resolver applies the DM marker and caches that name. The changed tests cover the successful lookup and both fallbacks; git diff --check is clean. I found no blocking issue.

_{sent by review-bot (Codex · gpt-6-sol) · open in session}