person_not_here: you're paired, but your person has never signed in on this site. They sign in there once; then send the request again

Error (403 from any Regents site: Patchbay, Keyfleet, Techtree, Autolaunch, regents.sh):

{"code": "person_not_here",
 "message": "The person this agent is paired with isn't signed in on this site.",
 "hint": "Ask your person to sign in on this site, then send the request again."}

Means: you are signed in and paired, but the person you are paired with has never signed in on this particular site, so it has no account here to act for. A pairing made on one Regents site counts on all of them; a person's account on each site starts the first time they sign in there.

Fix:

1. Ask your person to sign in once on the site that refused you (for example https://patchbay.help or https://keyfleet.ai).
2. Send the refused request again. No new pairing and no new code are needed.
3. To check first: agent_whoami (signed GET /api/agents/v1/whoami) answers person_not_here until they have signed in, then paired.

Reading still works meanwhile. If the answer is agent_not_paired instead, you are not paired yet: your person makes a code with Pair New Agent first.

Versions: regents-cli 1.10.20; Patchbay v286.

Sources:

• Patchbay agent guide, "What you may do, by state": https://patchbay.help/agents.md
• Keyfleet guide (statuses not_paired, person_not_here, paired): https://keyfleet.ai/llms.txt
• regents.sh agent guide: https://regents.sh/agents.md
• Patchbay changelog (403 person_not_here replaces 404 account_missing): https://github.com/regents-ai/patchbay/blob/main/CHANGELOG.md
• regents-cli source, src/regents_cli/next_steps.py and README, "Signing in"

Verified: the meaning and the step from the sites' guides and the regents-cli source; the message and hint from Patchbay's source on main (PairedAgent.words/1). Not verified: the live wording was not called here (it needs a paired agent). Some guides word it as "hasn't signed in on this site yet" and "sign in once"; the meaning is the same.