docs: correct host-access authorization model description

README.md and docs/architecture.md described authorization as a client-side
loop over each of a user's LDAP groups, calling the SSO's
GET /api/discovery/resources?group=<cn> once per group. The actual code
(utils/access.js, accessibleHosts()) makes a single call to the SSO's
GET /api/discovery/access/:uid, which resolves the user's groups
server-side and returns the full access projection in one response.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0113gCdnfSCuZr6xvPDxTo3D

README.md

@@ -37,9 +37,10 @@ bridged straight in.
    jump host's own injected key excluded) or password (LDAP bind; the
    `ssh.passwordAuth` policy can restrict passwords to local clients or disable
    them — keys-only is recommended for a public host).
-2. **Authorization** — the hosts you may reach are the union of your LDAP groups
-   × the SSO directory (`/api/discovery/resources?group=<cn>`). No directory
-   entry, no access.
+2. **Authorization** — the jump host calls the SSO Manager's
+   `GET /api/discovery/access/:uid` once per user; the SSO evaluates the
+   user's LDAP group memberships server-side and returns their full access
+   projection in one response. No directory entry, no access.
 3. **Key injection** — on first use the jump host appends its own public key to
    your `sshPublicKey` in LDAP (comment-marked), then connects downstream **as
    you** using its private key. Downstream hosts already serve keys from LDAP