Files
zooqueenandhanzo-dev 2f273e2a07
deploy / build (push) Successful in 1m35s
docs: say IAM, not the vendor name it was never derived from
Hanzo IAM (hanzoai/iam) is original clean-room work — its LICENSE says so.
The third-party-derived identity server was hanzoai/iam-v1, and that is
retired. Comments here named the old vendor as if it were the IAM we ship,
which was simply false.

Every hit was a comment or doc. The behavior each one describes is real and
still described; only the name changed:

- envelope shape {status, msg, data} and status:"error"-at-HTTP-200 are
  attributed to IAM, which is what the fakes actually emulate
- the phone-normalization probe still explains why three shapes are tried
- the /v1 vs /api/* mount notes now state the rule directly: /v1 is Base's
  one external prefix. Outbound /api/* calls to the IAM server are its
  contract and are untouched.
- hanzo.id not accepting HTTP Basic is stated on its own

No identifiers, routes, env vars or wire fields changed.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-28 17:12:32 -07:00
..
2026-06-10 13:59:55 -07:00