Garry's Opinionated OpenClaw/Hermes Agent Brain
TypeScript
chore: stamp v0.60.598.0 (provisional slot stamp)
garrytanca994b5638a9
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 88eed21864..51c995cd85 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -10,7 +10,7 @@ credits are retained; no result has been reassigned to another provider. Originaidentifiers and attribution are available in the pre-removal Git revision`6040075c6cb95be5881cc2e1b76ef7d71f4e5d29` (retained on 2026-09-23).-## [Unreleased]+## [0.60.598.0] - 2026-11-06**The brain owner can declare an email on a member and link a trusted system's canonical id to the member by that email, instead of looking up the member id first.** `gbrain access member add <id> --email <addr>` and `gbrain access member set <id> --email <addr>|none` declare or clear it, `member list` shows it, and `gbrain access member link --email <addr> --qm <id>` makes the same link `link <id> --qm <id>` makes. Over the running server, `gbrain mcp admin member-add --email`, `member-set` and `link --email` do the same through the owner-session routes. An email is stored lower-case, is unique per brain, and is cleared when a member is removed. An email no member declares is `not_found` and creates nothing. This changes no trust: the operator still makes every link, and no OAuth token, attested call or MCP tool can set an email or make a link. Members and emails are database state (migration v294), so a repo-less brain works the same.diff --git a/VERSION b/VERSIONindex 8027f62887..d7782b748c 100644--- a/VERSION+++ b/VERSION@@ -1 +1 @@-0.60.595.0+0.60.598.0diff --git a/package.json b/package.jsonindex e2a8c5db2d..dcb18389c1 100644--- a/package.json+++ b/package.json@@ -251,7 +251,7 @@"bun": ">=1.4.4"},"license": "MIT",- "version": "0.60.595.0",+ "version": "0.60.598.0","overrides": {"@ai-sdk/provider-utils": "4.0.56","@hono/node-server": "^2.0.5",