README/types expose non-web-agent surfaces during remote web-agent beta

[abai-Hcompany]

Problem

The first-release guidance says beta testers should focus on the remote web-agent only, with desktop/local support coming later and related endpoints/setups intentionally out of docs.

From an external user's first read of packages/sdk/README.md and exported types, the public TypeScript SDK still appears to cover broader surfaces:

• README says the client covers sessions, agents, memories, skills, and environments
• exported/generated types include CodeSandbox, Mcp, Memory, and code / mcp / memory environment variants
• generated SDK exposes memory CRUD operations

Why it matters

A beta tester can easily spend time trying to evaluate memories, skills, MCP, or code sandbox flows instead of the supported remote web-agent path. Because these are typed exports, they look like part of the intended public beta surface.

Expected

For the first release, the README should make the supported path unmistakable:

• lead with a minimal remote web-agent session (agent: "h/web" or the supported catalog id)
• mark memories/skills/environments and non-web environments as internal/coming soon if they are not part of the beta
• avoid advertising local/desktop/code/MCP setup paths until they are supported for external testers

Found during an external-user Agent API DX pass.