[devSejung]

Related: #4

What Problem This Solves

PlatformClaw browser authentication could reserve a personal-agent binding, but the deployable runtime did not assemble the employee-auth stack or create the matching OpenClaw agent through a stable boundary.

Why This Change Was Made

Adds the browser-auth runtime assembly and a bounded authenticated Admin HTTP RPC client. Personal agents are created or adopted only through existing agents.list and agents.create methods, with exact canonical ID and workspace verification. OpenClaw core and Gateway protocol remain unchanged; atomic USER.md seeding is deliberately deferred.

AI-assisted implementation; operator reviewed the architecture and policy decisions.

User Impact

A successful employee login can provision the reserved personal OpenClaw agent and workspace while keeping PlatformClaw-specific logic isolated from upstream core.

Evidence

• 16 focused browser-auth/control-plane tests passed.
• 12 focused RPC/provisioner tests passed after response-boundary hardening.
• @platformclaw/control-plane tsdown build passed.
• git diff --check passed.
• Fresh autoreview passed with no accepted/actionable findings.
• Full downstream CI runs in GitHub Actions.