README exposes 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, the public Python SDK still points users at broader surfaces:

• CRUD endpoints for each catalog live under agent_platform.api.{memories,skills,environments,agents}
• package root exports CodeSandbox, MCP, Memory, memory records, etc.
• the generated API includes memory CRUD and code / mcp / memory environment schemas

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. That is especially confusing because the SDK is otherwise generated and fully typed, so these surfaces look intentionally supported.

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/agents 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.