Sandbox config opens up, and Claude Code runtime moves to ACP

Changelog

Everything that shipped across Apr 6-10.

• -Added `cpuCount` and `memoryMB` to `agent.config.ts`, so sandbox size is pinned at deploy time instead of being patched after first boot. Picked up by the CLI bundler and the relay sandbox factory.
• -Added `timeoutMs`, `networkAllowOut`, and `networkDenyOut` runtime overrides on `SandboxClient.create()` in `@21st-sdk/node` and the Python SDK — each call can narrow TTL and outbound networking without redeploying the agent.
• -Template-backed files now travel with the deploy artifact: files and values listed in the agent template are baked into the built sandbox instead of being written in after boot.
• -Moved Claude Code sessions onto a persistent ACP runtime path inside the sandbox. Warm follow-ups reuse the same ACP session instead of booting a fresh transformer each turn; legacy sandboxes keep working through a fallback path.
• -Relay now selects the stream transformer from the `streamId` prefix, unifying the Claude Code path with whatever runtime ships next.
• -Billing events emitted by relay are now tagged with `runtime`, so Claude Code usage is separable from other runtimes on the invoice.
• -Shipped `/agents/new` quickstart wizard (alpha): guided bundle upload and no-code deploy, backed by new `/api/agents/wizard` and `/api/agents/deploy-nocode` routes.
• -Shipped the Agent Templates registry at `/community/agents`: browse, search, publish, and bookmark. Replaces the earlier "Community Agents" naming.
• -Added category, tag, and MCP-specific discovery pages under `/community/agents`.
• -Added mobile action bars and improved focus-ring contrast on agent config export buttons.