docs: note how to check an existing dashboard session
credential means the harness holds a user credential, not that the browser is
signed in. Document the per-endpoint token probe an agent can run in a tab on
the deployment origin.
The harness dashboard helper returns a signed /connect URL that signs the
integrated browser in with the user credential the harness already holds. Say so
in the widget guide, and keep the one-shot secret rule: open it immediately,
never print it, and never reuse it.
Document the `/w/...` widget routes and the `/connect` handoff for agents and
users: the surface table with query parameters, when to connect versus going
direct, and the rule that the SQL console inserts a query by default and
executes only on an explicit request.
Add screenshots of a filtered collection, the signal inbox with a parked run,
and the SQL console with an unexecuted query.