brand: Zen login host is id.zenlm.org (we own zenlm.org, not zen.id)

zen.id is not a domain we control; use the id.<domain> pattern on the owned
domain (matches id.lux.network / id.zoo.network style). Zoo already correctly
uses zoolabs.id + api.zoo.ngo (no zoo.network).

forks/zen/README.md

@@ -7,7 +7,7 @@ npx @zenlm/helper
 ```
 
 The Zen-branded build of [`@hanzo/helper`](https://github.com/hanzoai/helper) —
-identical engine, Zen defaults (`zen.id`, `api.zenlm.org`, `zen-app`). One
+identical engine, Zen defaults (`id.zenlm.org`, `api.zenlm.org`, `zen-app`). One
 command does browser device login, mints your Zen API key, and points your
 coding tools at the Zen AI cloud.
 

forks/zen/bin/zen.js

@@ -3,7 +3,7 @@
  * @zenlm/helper — the Zen-branded build of @hanzo/helper.
  *
  * Same engine, Zen defaults. We set the brand before importing the CLI so the
- * shared code resolves zen.id / api.zenlm.org / zen-app. Any explicit
+ * shared code resolves id.zenlm.org / api.zenlm.org / zen-app. Any explicit
  * HANZO_IAM_URL / HANZO_API_URL / HANZO_CLIENT_ID still overrides.
  */
 process.env.HANZO_BRAND ??= 'zen';

src/lib/brand.ts

@@ -54,7 +54,7 @@ const BRANDS: Record<Brand['id'], Brand> = {
     id: 'zen',
     name: 'Zen',
     bin: 'zen',
-    iam: 'https://zen.id/v1/iam',
+    iam: 'https://id.zenlm.org/v1/iam',
     api: 'https://api.zenlm.org',
     clientId: 'zen-app',
   },