Document the agent host in the repository map and MCP bindings

Add the agenthost row to the repository map and state, where the effective MCP bindings are described, that an agent-host view's gateway holds HTTP binding credentials.

Author: SaladDay

contracts/agents-api/environments.md

@@ -367,7 +367,7 @@ Environment MCP needs enabled network. Duplicate server identities are rejected.
 
 ### Effective bindings
 
-The Runtime resolves public HTTP declarations and installed Plugin MCP through `agent.ResolveMCPBindings` before adapter projection. Each transient binding keeps its connection origin, transport, nullable tool allowlist, required flag, credential authority and installed stdio identity. Bindings are never persisted or logged; duplicate identities and unavailable selected credentials are rejected. MiniMax reads its session-private native runtime-name registry for exact first-frame identities and cross-checks completed native results for both transports; adapters never fabricate a delayed start event or guess identities.
+The Runtime resolves public HTTP declarations and installed Plugin MCP through `agent.ResolveMCPBindings` before adapter projection. Each transient binding keeps its connection origin, transport, nullable tool allowlist, required flag, credential authority and installed stdio identity. Bindings are never persisted or logged; duplicate identities and unavailable selected credentials are rejected. MiniMax reads its session-private native runtime-name registry for exact first-frame identities and cross-checks completed native results for both transports; adapters never fabricate a delayed start event or guess identities. In an agent-host view, the Session's [credential gateway](model-execution.md#credential-gateway) holds each HTTP binding's bearer token and headers, and the Harness receives credential-free loopback URLs ([Endpoints and proxy](harness-onboarding.md#endpoints-and-proxy)).
 
 ### Public MCP connection origin
 

docs/development.md

@@ -73,6 +73,7 @@ For frontend development, run `pnpm dev:web` using the fixture or Core connectio
 | `apps/sandboxio` | Sandbox I/O service binary `oac-sandbox-io` and its Linux protocol services | [Sandbox bootstrap](sandbox-bootstrap.md#responsibilities-and-readiness), [File access protocol](file-access-protocol.md#the-linux-service), [Process protocol](process-protocol.md#implement-a-service), [Network protocol](sandbox-network-protocol.md#implement-a-service) |
 | `apps/daemon/internal/dispatch` | Runtime preparation, Executor reuse, Turn and cleanup ownership | [Harness lifecycle](../contracts/agents-api/harness-onboarding.md#required-adapter-interfaces) |
 | `apps/daemon/internal/agent` | Native harness adapters | [Native references](../contracts/agents-api/harness-onboarding.md#native-references) |
+| `apps/daemon/internal/agenthost` | Agent-host Sessions: admission, Session directory, Link attachment, views and teardown | [Run in an agent-host view](../contracts/agents-api/harness-onboarding.md#run-in-an-agent-host-view) |
 | `services/core/internal/sandbox` | Provider interfaces and managed compute lifecycle | [Provider onboarding](sandbox-provider.md) |
 | `services/web` | Console login and the server-side management proxy | [Console server](web/console-server.md) |
 | `apps/web` and `packages/agents-client` | Console UI and typed clients | [Web guide](../apps/web/README.md) |