runner reference

Short-lived, isolated Linux sandboxes (Firecracker microVMs) behind an HTTP API. This tree documents what is shipped today. Anything not shipped is listed in coming-soon.md and nowhere else, so nothing here promises it.

Page	What
api.md	Every public HTTP route: auth, scopes, request and reply shapes
errors.md	The typed error codes, their HTTP statuses and remedies
cli.md	`runner`, the customer CLI
mcp.md	`runner-mcp`, the MCP server for AI assistants
../api/leases.md	Leases: deadlines, renewal, warnings, grace
coming-soon.md	SDKs and other features not shipped yet

Agents: ../SKILL.md is the Agent Skill, and ../llms.txt is the index for LLM crawlers.

Three surfaces call the same API with the same key, so the key's scopes are what each may do:

123runner (CLI)  ─┐
runner-mcp    ─┼─►  HTTP API  /v1/...   (Authorization: Bearer rk_...)
your code     ─┘

Not in this tree: runner-api, runnerctl and the other cmd/runner-* binaries. They are the operator's, not the customer's.