[qingyun-wu]

Priority

Level: medium
Reason: completes the multi-server routing of #5977; without it these clients still post with whatever token the process environment holds.

Closes

Follows #5977 and #5978 (both on main); origin/main is merged in, base is main.

Summary

Every gateway client outside room_ops/notify now asks connections.room_credential which connection to use: the room's own server (exact domain match, so a dev.s.space room never goes to s.space), the primary when there is no room. A room no connection serves is refused by name, never answered with another server's token. Installs with one connection keep their existing credential chains (the resolver answers None).

Caller	Change
src/owner_room_access.py, src/channel_credentials.py	New channel_credentials.room_env(url_vars, token_vars, room): the connection's url|secret in the capability's first token variable, every other credential variable blanked. resolve_credentials(cap, collab_url, room) uses it unless --collab-url is explicit. owner_routing reads the primary row's owner-routing.<instance>.json, falling back to the unsuffixed file. connections.primary_row is a read-only primary lookup (no import, no vault).
pending-questions room DB, crons_table.py	Pass the room they open to resolve_credentials.
ensure-cron-room.py, cron-notify.py	resolve_token(repo, room) asks the resolver first (room creation uses the primary; a cron-room post uses the room's server). A refusal skips creation / returns "not delivered" with the reason on stderr.
bee_actions.py	_gateway_creds(room); post-room resolves for the Bee room, register-room for the primary; a refusal exits 2.
health-check.py --notify-gateway	REMOTE_ALERT_ROOM is read from the primary's channel dir first (legacy dir as fallback), and _gateway_creds(room=...) routes by that room. The status readers are untouched.
skills/tutorial/scripts/getting_started.py	commons_env(script, room=...) uses room_env; connect_actions applies blanked variables so an outer token cannot shadow the routed one.
Context-first prompt (src/result_markers.py + vendored copy)	The fallback is now channel-env.sh <dir> --room <room>, so the file loaded is the room's own connection's. room_ops.py itself already resolves by room from env, channel file or vault. Golden fixture and requeue test updated.
room_ops verbs without a room	Documented, not changed: rooms, history, agents, resolve, events list|pull|stream act through the primary (help text, SKILL.md, docs/connections.md).

Before / after evidence

New suite tests/gateway-clients-room-routing.test.py (three connections: ag2.space legacy, s.space primary, dev.s.space; the real resolver end to end; the process's REMOTE_TASK_TOKEN is ag2.space's, so a client that skips the resolver gets the wrong server).

At the parent (04d88fb32, the test files copied in):

Ran 31 tests in 2.636s
FAILED (failures=11, errors=18)

(The two passing cases are the vendored-copy parity check and the room_ops no-room verbs, which #5977 already routes to the primary.)

At this head:

Ran 31 tests
OK

Test plan

• tests/gateway-clients-room-routing.test.py (new), plus room-ops-room-connection, connections-room-routing, channel-env-resolve, channel-env-order-contract, connections, cron-notify, bee-actions, health-check-notify-gateway, tutorial-getting-started, pending-questions-room-db, pending-questions-room-db-serve-process, pending-questions-single-store, pending-questions-send, ag2space-links, requeue-prelude-rebuild, gateway-task-envelope-golden, result-markers-golden, bridge-marker-no-leak, delivery-primitives-single-owner, codex-core-launcher, hermetic-env-structural, tests/skills/schedule-crons/crons-table.test.py, skills/agent-room-ops/test_room_ops.py: all pass.
• ruff check on changed files: clean. scripts/lint-hermetic-bridge-tests.py: ok. scripts/review-checks.sh on the diff: PASS.
• Diff coverage, measured locally on the changed non-test Python lines: 119/120 (the one miss is the sys.path.insert in ensure-cron-room.py when the core src/ is not yet on the path).

Left over

• pending_questions_room_db._db_link (a display link shown to the owner) still builds its URL from the capability's own order, not the room's connection.
• mention's handle lookup uses the primary's /v1/agents directory while it posts through the room's connection; unchanged here.

Checklist

• No other open PR on this topic (gh pr list --state open)
• Single concern: moving gateway clients onto the resolver
• Tests added; before/after pasted
• Stacked PR: parent fix(connections): room tools act through the connection serving the room's server #5977 landed; main merged in and suites re-run
• No host-specific paths added; fixtures under temp dirs

🤖 Generated with Claude Code

[github-actions]

@cla-assistant check