Integrate AgentKit Host

Wire an always-on host so it can act as a named user through AgentKit. Then stop.

A host is a long-lived agent process (OpenClaw or Hermes). It is not this git repo.

Guardrails

• MUST wait for dashboard credential values. MUST NOT invent them.
• MUST pass the exact dashboard Connection Name. Never invent a slug.
• MUST put only Scalekit client credentials on the host. Provider tokens stay in Scalekit.

Gotchas

• Read SCALEKIT_ENVIRONMENT_URL, SCALEKIT_CLIENT_ID, SCALEKIT_CLIENT_SECRET, and SCALEKIT_IDENTIFIER. OpenClaw also accepts TOOL_* aliases. Never SCALEKIT_ENV_URL.
• A connection already exists from setup-agentkit. This skill starts there.
• The Slack gateway bot is a channel. It is not the named user.
• Do not run hermes mcp login against Scalekit. Do not mint a Virtual MCP session token for another end user inside this host. A single-operator host may hold one operator bearer. See https://docs.scalekit.com/agentkit/hermes/
• Default host is OpenClaw. Hermes is references/hermes.md.