zeekayandHanzo Dev d3181e7aad fix: one x.com handle for Hanzo, pinned in all three sources ...

Hanzo's identity is written in three places and all three disagreed:
brand.json said x.com/hanaboroshi, the registry said x.com/hanzoai, and
brandConfig still pointed at the dead twitter.com domain. It is hanzoai, which
is also what every sibling does — luxdefi, zoo_labs, parsnetwork.

The consistency test pinned six fields and none of the socials, so this drifted
in silence. It now pins twitter and github across brand.json, the registry AND
brandConfig, and asserts the host is x.com. Verified it catches the old value:
restoring hanaboroshi fails two tests, exit 1.

Folded into the unpublished 1.4.5 rather than bumping again.

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

2026-07-27 22:43:38 -07:00

..

brand-json-consistency.test.mjs

fix: one x.com handle for Hanzo, pinned in all three sources

2026-07-27 22:43:38 -07:00

registry.test.mjs

brand: harden the white-label host resolver (FQDN root dot + fuzz suite)

2026-07-21 10:57:32 -07:00