fix(gateway): open the main chat route before its first message (#201879)

* fix(gateway): open the main chat route before its first message

An agent's main session is stored with its first message. Until then the
authenticated session-entry handoff resolved /chat/<agent> to nothing and
answered 403 "Session unavailable", so a reload, bookmark or pasted link of
a new agent's main chat dead-ended behind an authenticating proxy, although
the app loaded at / opens the same conversation.

The resolver already gives the same answer for an absent main row and for a
main row hidden from the caller. For the main route, outside public reads,
that answer now selects the main key with the caller's authority as its only
condition, so the handoff serves the app for absent, hidden and visible main
alike. Unknown or refused agents, other missing sessions and the public
reader are unchanged.

* fix(gateway): require a client for the row-less main selection

Review follow-ups: the main-route fallback now also requires a client, so
a caller without one and without publicOnly gets no selection. The
resolver test shows the draft main row is really hidden from the
restricted profiles (literal route null) and visible to its creator, and
pins the client requirement. The URL docs say that /chat/<agentId> opens
before the agent's first message.