Locus setup

Use this when the user asks to install, connect, authenticate, or repair Locus. The request is not complete merely because SKILL.md was saved. Select one execution adapter from the actual host capabilities and the user's explicit choice, install and authenticate it, deliver all three released skill trees, verify a free readiness operation, and check discovery in a fresh session. MCP and the official generated CLI are peer adapters; never prefer one without host evidence. The full plugin may preconfigure an adapter, while a skill-only install still needs the selected adapter's own setup.

When a bootstrap led here, this installed skill is the operating procedure. The live compatibility record remains authoritative for environment and adapter availability; the bootstrap only locates and pins this released tree.

The account flow is separate from adapter selection. A person with browser or device consent uses a human-owned account by default. Use an agent-owned account only when requested or when the runtime is truly headless, and involve the user for explicit approvals, AgentMail verification, and funding.