zeekay 284d514ac7 hanzo: one crate for Dev's names, defaults, catalog, controller and version ...

Upstream crates read Dev's words and defaults from crates in hanzoai/dev,
by a path out of this tree. What they read is data and an interface, so it
moves here, into codex-rs/hanzo, which absorbs hanzo-version:

- the brand strings and the TUI's defaults (hanzo-tui's constants and
  input_background), read by codex-tui;
- API_BASE, DEFAULT_MODEL, is_hanzo and the model catalog (from
  hanzo-config), read by models-manager and model-provider;
- `model::pick`, the `/model <name>` match, pure over the catalog;
- the controller interface the agent loop consults (hanzo-loop: Controller,
  Handle, Verdict, Card, Request, Shortlist), read by codex-core;
- the version hook, now `hanzo::version`.

Dev's crates depend on this one from now on, never the reverse. Kai and the
Hanzo account are behaviour, and still named from here until the next two
commits turn them into hooks a binary fills.

2026-10-15 08:10:24 -07:00

..

src

hanzo: one crate for Dev's names, defaults, catalog, controller and version

2026-10-15 08:10:24 -07:00

BUILD.bazel

…

Cargo.toml

hanzo: one crate for Dev's names, defaults, catalog, controller and version

2026-10-15 08:10:24 -07:00