Resolve a single-use Try-Me token to its briefing manifest (POST form).

MNE-804 — the claim-first arc as the human FEELS it: exactly three one-click beats (name → authorize → Begin Sim). Everything else is a silent machine step under the grant from beat 2. The human twin of steps/state_machine (additive — those are untouched). Beat 2 (authorize) is host-native OAuth consent or a single one-click device-grant deep link (verification_uri_complete), NEVER a pasted URL, and carries the explicit 'waiting for signup' state (no premature timeout).

Birth credential — the agent presents this on key_header to be born + carry every gateway/model call. The ONLY credential handed to the agent. Under MNE-799 server-mediated birth this is a per-session BIRTH TOKEN (birth_token, mnbt_…) the gateway resolves server-side to the real key; identity is token-derived (first16hex(SHA256(birth_token))) and the agent_id is a server-minted mnm-… — NOT name-derived, and no shared provider key reaches the agent.

Authed dojo bind (post-mnemom login, owner-only) — the agent records its agent_id against this briefing so Begin Sim can resolve the dojo key by agent_id and spar it.

Human-handoff + CLI surfaces: the human takes ownership via the canonical /claim page, then the agent declares as the human via a mnemom login CLI session.

MNE-798 — the declarative flow as explicit states + transitions (the machine twin of steps), so an agent executes it deterministically across substrates. Each state carries the concrete next call to make and the signal that advances it.

MNE-798 — the owner-tier authorization affordances, declared so the agent negotiates by host capability: mcp_step_up (RFC 6750 insufficient_scope challenge — mid-session step-up), protection_grant (first-party one-time browser grant — the human approves the protection-card write), and device_grant (RFC 8628 device authorization grant — the headless fallback). The agent picks the one its host supports.