T

zeekayandHanzo AI d9eb4f38be Fetch secrets from the Hanzo KMS, not the Infisical API

The KMS fetch steps called `/api/v1/auth/universal-auth/login` and
`/api/v3/secrets/raw?workspaceSlug=...` — the Infisical surface. We do not run
Infisical; kms.hanzo.ai serves the Hanzo-native door and 404s those paths, so
every secret fetch failed and the build died at "KMS auth failed".

Rewritten to the canonical contract the working repos use:
`/v1/kms/auth/login` returning `.accessToken`, then
`/v1/kms/secrets/ci/<name>?env=prod` returning `.value`. The org is read from
the credential, so the `zoo-platform` workspace slug is gone.

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

2026-09-07 21:45:04 -07:00

.github

Fetch secrets from the Hanzo KMS, not the Infisical API

2026-09-07 21:45:04 -07:00

architecture

docs(arch): desktop stack decomposition + brand-variant build flow

2026-05-04 11:28:31 -07:00

configs/genesis

chore: sync working tree

2026-07-26 10:16:32 -07:00

deploy

Drop the zoo-computer architecture pin

2026-09-06 05:05:46 -07:00

e2e

Zoo asks luxd for chains where luxd serves them

2026-09-03 21:32:56 -07:00

infra/k8s

iam: zoo.vote signs in with the tenant's issuer

2026-09-04 09:15:42 -07:00

k8s

feat(universe): update chain endpoints to /v1/chain

2026-09-04 14:39:18 -07:00

manifests

Zoo asks luxd for chains where luxd serves them

2026-09-03 21:32:56 -07:00

scripts/ci

ci: a deploy is a commit, so stop applying to the cluster

2026-09-03 21:32:59 -07:00

.gitignore

universe: full DX collapse — kill dead auth subnet, SQLite + Litestream, fix CI drift

2026-06-03 11:12:00 -07:00

.npmrc

Route npm through our own registry

2026-09-03 11:04:58 -07:00

AGENTS.md

chore: symlink AGENTS.md and CLAUDE.md to LLM.md

2026-04-01 14:10:32 -07:00

chain.yaml

Zoo asks luxd for chains where luxd serves them

2026-09-03 21:32:56 -07:00

CLAUDE.md

chore: symlink AGENTS.md and CLAUDE.md to LLM.md

2026-04-01 14:10:32 -07:00

compose.yml

Zoo asks luxd for chains where luxd serves them

2026-09-03 21:32:56 -07:00

GEMINI.md

chore: symlink AGENTS.md + GEMINI.md + CLAUDE.md -> LLM.md

2026-09-02 01:53:57 -07:00

LICENSE

chore: add Apache-2.0 LICENSE

2026-02-14 05:27:03 -08:00

LLM.md

docs: chain routes are /v1/chain

2026-09-03 21:32:55 -07:00

Makefile

feat(iam): Zoo's own app graph — 5 clients, one issuer, proven end to end

2026-07-26 19:02:15 -07:00

package-lock.json

universe: full DX collapse — kill dead auth subnet, SQLite + Litestream, fix CI drift

2026-06-03 11:12:00 -07:00

package.json

universe: full DX collapse — kill dead auth subnet, SQLite + Litestream, fix CI drift

2026-06-03 11:12:00 -07:00

playwright.config.ts

Zoo asks luxd for chains where luxd serves them

2026-09-03 21:32:56 -07:00

README.md

retire: name the canonical universe at this tip

2026-08-20 17:33:59 -07:00

tsconfig.json

chore: sync local changes

2026-03-26 22:45:36 -07:00

README.md

Zoo Universe — retired

Read-only from here. Canonical: https://git.hanzo.ai/zoo/universe

This tip is an ancestor of canonical main, so no commit reachable from this branch is unique to it — the canonical repo is a strict superset. Nothing was lost by stopping here.

Two universes for one org is a split brain: a push lands somewhere real, reports success, and never reaches a cluster, because CD reconciles the other one (deploy/applicationset.yaml names the canonical URL). One repo per org means that failure cannot happen.