docs: name the identity server IAM in these comments

hanzoai/iam is Hanzo IAM — original, clean-room work; the vendor-derived server
was hanzoai/iam-v1, retired and in nothing we ship. The comments here named that
vendor for behavior that is IAM's own: get-account really does return the User
at the top level or under `data`, and add-organization really is entity CRUD
behind the authenticated Guard. Kept the facts, dropped the wrong name.

Comments and markdown only.

Co-authored-by: Hanzo Dev <[email protected]>

LLM.md

@@ -145,7 +145,7 @@ GitLab provider + vitest-unified test runner.)
   (get-app-login intercepted so web3 resolves): one "Connect Wallet" renders;
   click with no injected wallet → chooser shows Ethereum/EVM + Solana; click
   with an injected `window.ethereum` → NO chooser, straight into the EVM flow.
-- **Backend untouched.** Pure `id` SPA change (frontend), no IAM/casdoor edit.
+- **Backend untouched.** Pure `id` SPA change (frontend), no IAM edit.
   Ships as `ghcr.io/hanzoai/id:0.2.9`; deploy = bump the operator CR image
   (`universe/infra/k8s/operator/crs/id.yaml`) by hand (id not in the
   gitops-reconcile allowlist). NEVER restart ingress (TLS-outage hazard).

pkgs/auth/src/client.ts

@@ -192,7 +192,7 @@ export function createAuthClient(opts: AuthClientOptions): AuthClient {
 
   // Resolve the org of the user in the ambient IAM session (the `iam_session_id`
   // cookie), or null when there is no live session. Reads `/v1/iam/get-account`;
-  // the org is the `owner` field (Casdoor returns the User at the top level or
+  // the org is the `owner` field (IAM returns the User at the top level or
   // under `data`). Used to keep silent SSO from reusing a session that belongs
   // to a DIFFERENT org than the app being signed into.
   async function sessionOwner(): Promise<string | null> {

pkgs/onboarding/src/service/onboarding.ts

@@ -13,7 +13,7 @@
  *   linkWallet()  client-side wallet connect → IAM update-user (host-driven)
  *
  * Founding an org goes through `onboard`, NOT the `add-organization` admin verb.
- * They are different doors: add-organization is Casdoor entity CRUD behind IAM's
+ * They are different doors: add-organization is entity CRUD behind IAM's
  * authenticated Guard, filed under owner "admin", and a human may only write an
  * org row named after the org they are already in — so a person founding their
  * FIRST org is refused there by construction (403), and with no bearer at all the