The version in package.json had sat at 8.5.35 while CI published through
8.5.48 (the tag hanzoai/cloud pins today): a main push derives its number as
max(declared, published) + a patch, so the registry floor carried the series
alone and the manifest drifted fifteen patches behind it.
That matters for a hand-cut tag, because a tag build publishes the tag
VERBATIM with no monotonic check — cutting the next number after the last git
tag would have republished a semver that already exists, over different bytes,
and orphaned anything pinned to it. Saying the number here puts the human's
say-so back above the floor and makes the next release the one nobody is
holding.
Four defects, all measured on the live console with wire captures.
The completions request carried NO Authorization header at all. `streamChat`
reached for a bare `fetch` because a stream cannot go through the parsing
helpers that consume the body — and in doing so it left the one file where
identity is attached, so every send answered 401 while the identical
non-streaming call succeeded. So the client grows the door that was missing,
`restStream`: same `authedFetch`, same `baseHeaders`, raw `Response` back. The
gateway stream, text-to-speech and the guide's SSE step-runner all take it, and
a test drives the real path and reads the Bearer off the wire.
Preferences saved to `/v1/ai/preferences`, which is the AI gateway's casibase
handler and authenticates on a casibase SESSION — no Bearer can satisfy it, so
every save was refused "Please sign in first" while the user was signed in. They
now ride `/v1/prefs`, the per-user plane on cloud, which reads exactly the
credential the console already sends. That plane also SERVES a read, which the
old one never did: preferences were recovered from a snapshot of them carried in
the identity token, and a merge had to guess from two timestamps which side was
newer. Reading the document removes the guess, and the ordering machinery with
it.
The 401 card said "Your session expired" to people whose session was live. The
shared classifier can only see the status; whether this session is live is a
fact only the app holds, so the assistant decides it — a refusal with an
unexpired token reads as a surface that refused a signed-in caller, and "sign in
again" is kept for when it is true.
On a desktop the composer could not be clicked. Docking opened the sheet AND the
column and hid one with CSS, but the sheet is a modal dialog and hiding its
content does not stop it being modal: it covered the viewport, the column
painted inert beneath it, and every click landed on the dialog. The two shapes
now meet in one fact — the dock choice, a viewport that can hold a column, and a
page that is not already a composer — and exactly one of them mounts.
Also: the cross-app launcher sat in the lg-only topbar group, so on a phone the
grid of other Hanzo apps was unreachable. It moves to the account drawer, whose
trigger is on every viewport — one launcher, reachable everywhere.
Nothing here was ever a team. The referral, store, affiliate and author copy
called a customer organization "a team" ("when a new team signs up", "every
time a team runs your project"). The onboarding step called the tenant "your
workspace" in its title and "your team" in its blurb, while the org picker one
control away said "organization" — three words for one thing.
And Settings > Team was not a team either: its own description reads
"Organization members and roles", its index label already said "Members", and
the sibling button already said "Manage members". Only the nav label held out,
sitting in brand-scope as "Team, organization, and profile" — as if the two
were different things.
So: the tenant is an organization everywhere a human reads it, and the page
listing the people in it is Members.
Left alone: the `/team` route id (it is a link people already have), the `team`
plan tier, the helpdesk's HD Team doctype, and the tracker's real Team entity
whose boards are keyed ENG-1 — none of those are tenancy. "Teammate" and
"invite your team" stay too; those are people.
The observability footer offered Prev and Next and nothing else, so a reader 40
pages into a trace list reached page 1 by pressing Prev forty times. Pagination
from @hanzo/ui/product gives numbered jumps with an ellipsis. What stays in
Pager is the sentence only this surface can write — the row range — because only
it knows the shape of the meta its endpoints return.
ModelSelector's header said the package's selector was "the shadcn/Tailwind
build" and that the console, running Tamagui, could not use it. That stopped
being true: at 8.0.56 @hanzo/ui/models imports @hanzo/gui and
@hanzogui/lucide-icons-2, with no Radix and no class strings. Two real things
still block the swap and the comment now names them — the entry shape
(CatalogEntry vs ModelCatalogEntry, which decides family grouping) and the row
logos (this one draws curated brand marks through ui/ProviderLogo; the package's
draws none). A stale reason is worse than no reason: it retires a question that
is actually still open.
playground/ModelSelect had its import placed above 'use client' by the sweep
that moved it onto the package. Next reads the directive only as the first
statement, so the file had quietly stopped being a client module.
`secure` on a gui Input is React Native's spelling, and the WEB build drops it:
`secureTextEntry` becomes type="password" only in @hanzogui/core's native.cjs —
grep the esm/cjs builds and the prop is not there at all. So every field in this
console that asked to be masked rendered its value in plain text, and the prop
made it look handled.
Five of them were secrets:
AdminModule a user's initial password
KmsModule a KMS secret value
ConnectionsModule a provider API key
AccountsTab an AI provider key
platform-apps an app env secret — on a panel whose own caption promises
"never stored or shown in plaintext"
All five now use SecretInput from @hanzo/ui/product, which sets BOTH spellings
(`masked()` — neither alone is safe) and adds a deliberate reveal. ApiKeysModule
joins them: it printed a freshly minted key as bare selectable monospace, and
SecretInput's read-only mode copies while still masked, which removes the reason
to unmask at all.
The copy control was written seven times — sentry, code, git, webhooks,
Kubernetes, api-keys, playground, verify — each with its own confirmation window
(1200, 1400, 1500, 2000ms) and its own error behavior, one of which logged the
clipboard failure with the value in it. They are one import now. git/parts
re-exports it so its four views keep a single import site, and CopyRef stays as
the wrapper that knows how to spell a `repo file:line` reference.
The shared control also reports what was copied by LENGTH, never by content.
Typecheck clean; 3210 passing, 8 skipped.
src/components/ui/ was a ~30-file copy of components that were hoisted OUT of
this console into @hanzo/ui/product (hanzoai/ui#36). The hoist landed; the copy
never left. Both halves kept getting edits, so the console has been shipping the
half nobody else could see.
Twenty modules go back to the package, 278 call sites now import
'@hanzo/ui/product', and 2,311 lines leave the tree. Everything the package
gained while the copy sat here arrives with them — chiefly the interaction
instrumentation: DataTable, PrimaryButton, ConfirmDelete, EmptyState, Segmented
and SearchInput now report what a user did through @hanzogui/telemetry, which
console already depends on, with no wiring and no provider to mount.
BackendStateCard needs two effects a presentational layer cannot have — sign in
again (401) and add credits (402). The package asks its host for them, so
src/entry/host.tsx answers once at the dashboard root and all 106 cards below
render the right affordance unchanged. One answer, not 106.
The package's components name their CSS classes without the hz- prefix
(`skeleton`, `row`, `tnum`, `fade-up`, `drag`), so app/layout.tsx now imports
@hanzo/ui/styles/motion.css. Without it a DataTable's skeleton, row hover and
tabular figures render unstyled — the classes simply would not match. Console's
own hz- twins stay in globals.css; 250+ call sites in console markup still name
them.
Four things did NOT come back, because the package version is behind the copy
rather than ahead of it, and swapping them would ship a visible regression:
ProviderLogo — draws curated per-family brand marks (BRAND_MARK, inline
Slack/GitHub, brand-colored monograms). The package knows two providers and
renders initials for everything else.
ProductIcon — picks its glyph color with contrastText(). The package hardcodes
#ffffff, which is unreadable on 3 of console's 19 product accents and
invisible on #FAFAFA.
Donut, Metric, Charts — read console's theme: var(--color4/9/12) rather than
hardcoded dark hex, and the monochrome RAMP rather than the package's
eight-color SERIES. Swapping repaints every chart in the console.
SlideOver, Toast — take their layer from lib/z.ts. The package hardcodes
zIndex 1000 and 100000, which are two of the exact literals that ladder was
introduced to eliminate.
Field and Filters shrink to the part that is genuinely console's:
FieldOptionSelect (a value/label picker the package has no twin for) and the
Filters bar (it takes a List, so it is app-coupled by construction). color.ts
keeps only tileRadius, which encodes console's radius scale.
ThemeToggle and HanzoMark are deleted outright — nothing imported either; the
mark everything actually uses is ui/Loader's BrandMark.
Reorder.test.ts and combobox/filter.test.ts go with the code they tested: 3222
tests to 3210. Their assertions cannot follow the logic upstream, because
@hanzo/ui/product publishes no node-resolvable subpath for its pure functions —
importing the barrel drags @hanzogui/next-theme into vitest and fails on
next/script. A consumer therefore cannot guard the contract it now depends on.
Typecheck clean; 3210 passing, 8 skipped.
The console's own src/components/ui/ is a copy of components that were hoisted
into @hanzo/ui/product (hanzoai/ui#36) and never deleted here. 8.0.56 is the
release where every one of them lands published, so the copy has somewhere to
go. Typecheck clean and 3222 tests green on the bump alone — nothing in this
tree reaches an API that moved between 8.0.38 and 8.0.56.
The Models page listed every family in order but gave the user no way back to
the models they actually use: every visit started at the top of a long list.
A Recent + Suggested chip strip now sits above the families — recents are the
user's own trail (recorded where a model is genuinely exercised: a chat turn
sent, a catalog detail opened; account-persisted, so it follows them across
devices), suggestions are one live rung per pinned family, which puts the
house default first by construction. Both hide while a search owns the page,
and neither ever shows a fabricated chip.
The topbar slims to what navigation needs: status, docs, the cross-app
launcher, and the account drawer trigger — now on every viewport. The network
chip leaves the bar: production is the default environment, so switching is a
deliberate act you open the drawer for, not chrome you wear. The theme toggle
leaves too — the account menu already carries theme, and two controls for one
setting is one too many. Alerts stay at /alerts and in the drawer.
Chat's stale copy caught up with the Enso default: the surface no longer
greets you with the name of a family it stopped defaulting to.
Console had no way to reach another Hanzo surface. The two "switchers" in its
topbar are about where you are INSIDE console — ContextSwitcher picks the org
and project, ScopeSwitcher picks the network — and the LayoutGrid in the sidebar
lists console's own products. A fullscreen launcher existed once and was removed
as a duplicate of that product filter, which it was; nothing replaced the part
it was actually for.
@hanzogui/shell has shipped HanzoAppLauncher the whole time, and chat already
wears it. It is inline-styled and React-only, so it drops into a Tamagui topbar
untouched — no wrapper, no theme bridge. quickSwitchKey={false} because
CommandPalette.tsx:806 already binds ⌘K; the shell's prop doc names Console as
the reason that opt-out exists, so this integration was designed for and then
never landed.
Also takes shell to 8.1.1, where the panel is portalled out of its host's
stacking context. This topbar does not clip it today, but the version that
cannot be clipped by a container the component never sees is the one to pin.
The provider built its context value fresh on every render and passed it
straight to Provider. Its own state changes on every toast, so each toast
handed every useToast() consumer a new identity. An effect that both
depends on the toast api and raises a toast therefore re-triggered itself:
raising one rendered the provider, which handed the effect a new api,
which raised another. The OAuth return did exactly that and stacked twelve
identical cards down the viewport.
Stripping the query params could not have stopped it. router.replace is
asynchronous, so the params are still readable on every render in between
-- and the effect calls load(), which causes exactly those renders. The
integrations return now latches once per mount; stripping the params
covers the NEXT mount, which is the case it can actually address.
The callbacks were already stable, so memoizing the object is the whole
fix, and it makes depending on the toast api safe everywhere, not just
here.
Proven by render, since no unit test can see a render loop: reverted, the
new spec counts 12 toasts; fixed, it counts 1.
The console preselected zen5-flash and greeted you with 'Message
zen5-flash…' — the machine's model id where an invitation belongs, and
a stand-in family where Hanzo's own belongs. Enso left limited preview,
so the house family is what an unchosen caller should get: DEFAULT_MODEL
is enso-flash, the family's free rung, which keeps the property the old
default was chosen for (a trial or welcome balance still answers on the
first message). The placeholder now says what the box is for.
The preselect's fallback follows: the house family, then the first
model discovery offers.
Clicking "Sign in" on cloud.hanzo.ai appeared to do nothing. It was not a redirect
loop and nothing returned an error — every hop was HTTP 200, which is why the page
"looked fine".
console.hanzo.ai/ served a SECOND copy of the Hanzo Cloud marketing page, wearing the
byte-identical @hanzogui/shell header. So the journey was:
cloud.hanzo.ai [Sign in] -> console.hanzo.ai/ (same header, same "Sign in")
console.hanzo.ai [Sign in] -> /signin (one button, nothing else)
/signin [Log in with Hanzo Cloud] -> hanzo.id
Three clicks, and the first landed on a page indistinguishable from the one it left.
That reads as a re-render, and users stopped there.
The console is the APPLICATION; the marketing face of Hanzo Cloud is cloud.hanzo.ai.
Serving a third copy of it on the app host is what created the illusion. So `/` is no
longer a special surface: everything except the two auth routes is `guarded`, and a
definitively-anonymous visitor STARTS the authorize hop instead of being parked on an
interstitial that only asks "did you mean it?".
cloud.hanzo.ai [Sign in] -> hanzo.id
`startReauth()` is reused rather than `signinRedirect()`, so a deep link (/models)
returns to /models after login instead of dumping the user on the home.
SIGN-OUT IS PRESERVED, the one hazard here. Sign-out lands on /signin, which keeps its
button and never auto-authorizes -- IAM may still hold its own session, so authorizing
there would sign the user straight back in and make signing out impossible. A callback
failure lands on the same surface, so a broken hop cannot loop.
Removes PublicLanding + landing-surface, now unreachable (-269 lines net).
Tests: 258 files / 3211 assertions pass; tsc --noEmit clean.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The rescued gui8-props guard lands red here because origin fixed the same
line-height bug a different way and grew a shell the guard's fixtures predate.
Three corrections, none of them a weakened rule:
- gui8-props: blank out whole comment SPANS, not lines whose opener is `//`.
The module already says a doc comment must be free to name the bug it
documents; the fix comments at the call sites are multi-line `{/* … */}` JSX
blocks, so the continuation lines were still scanned and PitchHero's own
description of the bug counted as the bug.
- Charts: `lineHeight: 1.35` -> `'1.35'`. This one is a plain `<div>`, where
React already emits it unitless, so the CSS is unchanged — but the string form
is what the rule asks for and stays correct if it ever becomes a gui component.
- shell.test: `tracker` is a shell now (the rescued tracker pick), so the
descriptor table's expected ids include it.
tsc --noEmit: 0 errors. vitest: 3217 passed, 8 skipped, 0 failed.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
(cherry picked from commit 6ca6cc8fe1)
The 8.x dependency convergence was already done and building. What was left is
the half it cannot catch: @hanzo/gui accepts any prop and drops the ones it does
not recognise, so a gui 7 spelling type-checks, builds, ships, and does nothing.
Asked the renderer instead of the type-checker (scripts/gui-prop-probe.mjs
renders a prop and reads the host element and emitted class back out), which
settled the open `tag` vs `render` question the interrupted session left and
found four live defects:
tag="a" -> <div tag="a"> an inert link
style lineHeight: 1.1 -> line-height: 1.1px a ratio is not a length
- CloudflareModule's pages.dev/workers.dev URL chip and every ContactModule
channel card (mailto included) were <div>s. Both now render="a".
- PublicLanding's hero title, PitchHero's headline and the CodeSamples block
shipped line-height 1.1px/1.12px/1.6px — a wrapped title, and every line of a
code sample, drawn on one baseline. gui appends px to a bare number in `style`
as much as in a prop, so the ratio is now spelled as a string.
Because the type system provably cannot gate this class, the gate is the source
text: src/lib/gui8-props.ts holds the four verified rules and its suite runs them
over every file that imports gui (335 of them). Scoping by import is what keeps
it precise — a `{ tag: 'v1' }` image tag in a pure-logic module is out of scope
by construction, as are the rule module and its own fixtures.
Also: typescript stays on 5.x, and that is correct rather than a shortfall.
typescript@7.0.2 is genuinely the native Go compiler (its tsc is a statically
linked ELF from typescript-go/cmd/tsgo), but it ships only
{version, versionMajorMinor} on the main entry, while `next build` calls
ts.parseJsonConfigFileContent / ts.JsxEmit / ts.ModuleKind /
ts.ModuleResolutionKind — all undefined there. TS7 breaks Next exactly the way it
breaks tsup, for the same reason. @typescript/native-preview (7.0.0-dev, behind
stable) stays removed.
Verified: next build ✓ compiled successfully in 25.8s, 20/20 pages;
tsc --noEmit exit 0; vitest 2903 passed / 8 skipped (the pre-existing enso-bench
parity self-skip); build:embed ✓ static export ready, 30 handlers restored.
Zero tailwind/radix/shadcn, not even transitively.
(cherry picked from commit c9a4d92554fa8b8274801218a2c14a0044cf17bf)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
(cherry picked from commit 19e6d2e250)
@hanzo/ui/product's CommerceResource documents itself as what BOTH the console's
Store category and the standalone Commerce admin render. That was false while
this directory kept its own copy — the console imported the local one, so the two
surfaces could drift silently and the shared component's docstring lied.
The local fork is deleted and the import repointed at @hanzo/ui/product, which is
what the Commerce admin already renders. One component, two surfaces, and the
docstring is now a fact.
tsc --noEmit: exit 0, 0 errors.
(cherry picked from commit e9524b5c4588ca6664ca23c341863faadaa48141)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
(cherry picked from commit 4dbae2115d)
Rebuild the console Tracker into a SOTA, Linear-grade issue tracker over the
native cloud /v1/tracker surface, and give tracker.<brand> its own standalone
shell (the catalog chrome is stripped; the module's own views ARE the nav).
- Standalone shell: `tracker` ShellId + isTrackerHost + shellFromHost +
PRODUCT_SHELLS.tracker (indexLabel "Issues", home "tracker"). Registry entry
repointed to the native cloud backend with :view / :view/:sub routes and
subpages (My Issues, Teams, Cycles, Roadmap). Host-detected exactly like
billing./sentry./dns. — one image, one more face.
- Unified board: client-side cross-project merge (listAllIssues) → ONE filterable
board across every team AND every mirrored GitHub repo (the App-webhook lane's
GH mirror), with no second store. Group by status/priority/assignee/team,
filter (status/priority/kind/source/assignee/label/team), live search,
List <-> Board.
- Issue detail pane: one-click status, full edit, agent hand-off (assignee +
`agent` label -> the cloud coding seam opens a linked PR), the issue<->branch
<->PR chain (linkedPRs), git.hanzo.ai + upstream GitHub links, epic children.
- Keyboard-first: c=create, /=search, g-chord nav (g i/m/t/c/r), j/k/arrows/
Enter/e, and — standalone only — a capture-phase Cmd-K command palette that
never fights the console's global Cmd-K.
- Cycles (derived current iteration + progress) and Roadmap (epics + their
ExtRef children), both from real data — honest, never fabricated.
- Richer Issue type (kind/source/repo/extRef) so GitHub-mirrored + agent-PR rows
render distinctly; a "Sync GitHub" action triggers the org backfill.
Pure decisions decomplected to tracker/logic.ts (27 vitest green) + the shell
face test. Native @hanzo/gui v5 + React 19 — zero Svelte. Consumes the concurrent
App-webhook lane's GitHub mirror through the existing endpoints (no backend
duplication; the tracker data model + views + agent flow are owned here).
(cherry picked from commit 781db541e8476cb7e0bf1800c55f86f6d9162b50)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
(cherry picked from commit 613abbabb5)
app/design/ carried a verbatim vendor of @hanzo/design's tokens, synced by hand
on 2026-07-24 because the package wasn't on npm. It is now (0.4.6), and the
vendored copy had already drifted a full border rework behind it — pure-black
ground, solid #1f1f1f borders, grey destructive, the pre-0.4.x palette the rest
of the fleet just moved off of. index.css now imports the real dependency and
the seven vendored token files are deleted; the two console-only tokens they
added (--border-card, --border-hairline) were unused. The Tamagui theme layer
in globals.css derives --colorN from the neutral ladder, which is unchanged, so
only the semantic surfaces adopt the rework — the intended unification.
tsc 0 errors, 3157 tests pass, next build clean.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Move vendored MIT copyright notices out of LICENSE into NOTICE, and add the
full MIT permission text alongside them. LICENSE is reserved for this
project's own BSD-3-Clause grant.
cloud's per-product RED window and upstream o11y's metric-NAME CATALOG were both
answering GET /v1/o11y/metrics. Two different questions at one address, which is
why cloud had to suppress the module's real read to boot at all. cloud's moves to
/v1/o11y/product/metrics — the honest name for "one product's requests, error
rate and p95" — and the bare name goes back to the catalog it describes.
This is the read behind the platform-apps drawer, so it must land WITH the cloud
change (hanzoai/cloud fix/o11y-route-ownership): before it, this path 404s;
after it, the old path answers the catalog's shape instead of RED numbers.
`o11y` is still the allow-listed head in proxy-allow.ts, so the BFF is unchanged.
vitest 6/6 on the touched suite. tsc reports 3 errors in PublicLanding.tsx and
landing-surface.ts for a missing `@hanzogui/shell` — pre-existing here, present
on origin/main and untouched by this change, which edits only string literals.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The assistant's way in was the only shape of it this module did not own: two
small buttons in the topbar, wedged between the search box and the account
chrome, putting it in a third place and squeezing a 390px header to five
controls. Both move into one floating control bottom-right — the same
openChat/startVoice, the same surface, in the corner it actually appears in.
All products was a directory you could not walk. Each app rendered as a plain
DIV with role=null and cursor:auto — measured, not read — so the one place the
whole catalog is browsable had exactly one live control per row, the pin. The
row opens its app now, through the shared openProduct, and closes the pane
behind it; pin stays a separate control that stops the press from bubbling.
And a pin made after sign-in was thrown away on the next reload. Preferences
are read off the identity token's claims — a snapshot taken when that token was
minted — and once a user has saved anything the token CARRIES one, so the merge
let an hour-old snapshot beat a newer write. It is now told the ordering it was
missing: the token's own iat against a stamp written only when the server
acknowledges a save. A save that never landed earns nothing, so this orders two
real writes rather than inventing durability in localStorage. There is still no
GET for the document; the smallest seam is named in preferences-core.
Five white-filled buttons competed on the home, counted by computed background
luminance. Now one: the getting-started card's active step.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
console is NOT a fork -- its root commit is Hanzo's own and Hanzo is the
correct copyright holder. LICENSE is now a clean, canonical BSD-3-Clause
(verified against the SPDX text) naming Hanzo alone.
The seven retained MIT notices for vendored code (Tamagui, react-native-web,
Radix, Framer Motion, WorkOS et al) were attribution living in LICENSE. They
move to NOTICE, with the MIT permission notice reproduced so the obligation
travels with them.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
StepActions was the last child of a flex column, so its y was whatever the
step's content happened to add up to — Continue sat at a different height on
every step and a user clicking through had to re-aim each time.
It is a slot on StepShell now, above a content area with a reserved height:
one placement, decided in one place. Taller content still grows.
The workspace step also offered no way past it without naming the workspace,
which is optional — it skips now. Consent deliberately still has none:
accepting the Terms is not optional, so an affordance that skipped them would
be dishonest, and Continue stays disabled until the box is ticked.
Proven by geometry in a browser, because the JSX move is invisible to a unit
test: both shapes render the same button with the same label. Removing the
reserved height fails the spec; restoring it passes.
Hanzo-original work; BSD-3 is out of scope for hanzoai under HIP-0137.
LICENSE becomes the dual pointer, LICENSE-MIT / LICENSE-APACHE carry the
texts, and the upstream MIT copyright notices previously kept in LICENSE
are retained verbatim in LICENSE-MIT. README, LLM.md, NOTICE, Dockerfile
and package.json follow.
The `ml-pipelines` product (label "ML Pipelines", description "Orchestrated
training and evaluation pipelines (Kubeflow)", status enabled, slug aliases
`/kubeflow` and `/mlpipelines`) read nothing but Katib and Trainer: its three
sources were GET /v1/train/health, GET /v1/train/experiments (its "Pipelines")
and GET /v1/train/jobs (its "Runs"). Those CRDs are not served by the cluster and
cloud deleted the ops, so every one of them is now a 404 and the product's only
possible state is an error card. `KubeflowApi` had no other consumer.
There is nothing to repoint it at. Per-org model-shape SEARCH — the job Katib
was installed for — is /v1/risk/search, which runs natively in the org's own
sandbox and needs no CRD.
Also removed from the `/training` BFF allow-list: `train/jobs`,
`train/experiments`, `train/health`. An allow-list entry is a declaration that a
path exists; those three no longer do. `ml/models` (kserve, live and serving) and
the eight `finetune/*` broker heads stay exactly as they were.
STILL WIRED TO THE DELETED PATHS, deliberately left for its own change:
FinetuningModule's Jobs tab, its loss chart and NewTrainingPanel still call
TrainApi.listJobs/createJob/experiments. Gutting them would delete a product;
the right fix is to repoint them at the /v1/finetune/* broker — already
allow-listed two lines below in the same proxy, and a richer surface (presets, HF
pickers, cancel, deploy-to-serving). That is a payload-contract change with its
own verification, not a line to slip into a deletion.
Verified: match-core 37/37; the full suite is 3175/3175 on this tree, which is
pristine origin/main's 3177 minus exactly the two retired alias assertions, with
the same single pre-existing social.test.ts collection failure. tsc reports SIX
FEWER error files than pristine origin/main (413 vs 419 — the local
@hanzo/gui shorthand drift this box has either way) and not one error in a file
this change touches.
The callback screen said "Sign-in failed." to everyone. Cancel a Google consent
screen and the product told you it broke; return with a session the issuer would
not reuse and it said the same thing. Both are ordinary OIDC answers, not faults,
and the words were the only thing wrong with them.
The SDK is right to report them uniformly — it validates `state` before honouring
an error branch, because /callback?error=… is a plain GET anyone can hand a
victim, so nothing downstream may DECIDE from that code. But it may READ it: the
screen now classifies the code for WORDING only, with authority left where it was.
access_denied says the sign-in was cancelled; login_required / interaction_required
/ consent_required say the session ended and lead with Sign in — the action that
actually resolves them, rather than a Retry that repeats the same refusal. Anything
unrecognized prefers the issuer's own error_description, which names a real cause
far better than a generic line ever did.
Both strings arrive from a redirect, so both are bounded before they reach a
screen whose only job is to say what happened.
This also unblocks silent SSO: a top-level prompt=none attempt returns
error=login_required to the app, and until now that landed on "Sign-in failed."
— a wrong screen for the most ordinary outcome that flow has.
Pure classifier, tested apart from the browser: 9 cases covering each class, the
issuer's own words, the unbounded-description bound, and a malformed query, which
must not throw on the one screen a person cannot navigate away from.
The Profile card rendered `avatar` read-only and offered "Edit in IAM" — which
links to an IAM that cannot set one either: its only writers are federation (a
GitHub avatar_url, an OIDC picture claim) and SCIM. A user who signed up with a
password had a monogram and no way out of it.
Now the card has "Add photo" / "Change photo". It posts to cloud's new
POST /v1/avatar, which stores the image in S3 and writes the URL onto the IAM
user row, so the change is visible to every product rather than this tab —
`reload()` re-reads the session so the rest of this tab agrees too.
The photo is downscaled to 512px in the browser first. A phone original is
several MB and would be served to every viewer of every page showing that face;
512 is larger than any surface renders it. The server still caps the body — this
is the courtesy, not the guard — and a source the canvas cannot decode is sent
verbatim so the server's format check stays the authority.
postForm is the ONE upload door, added because `request` JSON-encodes its body
so a file cannot travel that way. It shares everything else: the same
authedFetch (bearer + refresh) and the same baseHeaders tenant stamp, so an
upload is org/project-scoped exactly like a read. Content-Type is deliberately
deleted rather than set — the browser must write it itself to carry the
multipart boundary.
A refusal shows the SERVER'S reason: "a profile photo must be a PNG, JPEG, GIF
or WebP image" is actionable where "Request failed" is not.
The previous commit dropped console's explicit `storage: sessionStorage` so the
session would be shared across tabs, and the build died on the next push:
Error occurred prerendering page "/auth/callback"
ReferenceError: sessionStorage is not defined
`^0.21.2` resolved to a build whose default was the bare global
`config.storage ?? sessionStorage`, evaluated in the IAM constructor. In a
browser that is merely the wrong lifetime; under Next's static export it runs in
Node, where the identifier does not exist at all, so the constructor threw and
the export exited. Passing `sessionStorage` explicitly had been masking it —
the callback page constructs the SDK at module scope, and the value it passed
was the client-side one Next never evaluates on the server.
0.21.6 resolves storage through a guarded probe (`typeof localStorage`, then an
actual write, since privacy modes expose the object and throw on setItem) and
falls back to an in-memory Storage. So prerender gets a real object, the browser
gets localStorage, and neither needs a caller to know which one it is.
The caret already permitted 0.21.6; the lockfile is what pinned 0.21.2, which is
why CI installed the broken one while a local `pnpm install` would not have.
Verified by running the export that failed: 13/13 static pages, /auth/callback
among them.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Reaching a login form took three clicks across two hosts: "Sign in" on
cloud.hanzo.ai landed here, "Sign in" here routed to /signin, and /signin's
entire content was one button that starts the authorize redirect. The middle
step asked "did you mean it?" about an answer already given one click earlier.
Both CTAs now call signinRedirect() directly. /signin is unchanged and is still
the one sign-in surface — the guarded entry sends anon visitors there, sign-out
lands there, and deep links resolve to it. It deliberately does NOT auto-redirect
on load: after an explicit sign-out IAM may still hold a session, so an automatic
authorize would sign the user straight back in and there would be no way to leave.
The button there means something; the hop to reach it did not.
The console passed `window.sessionStorage` to the IAM SDK explicitly, so the
session was scoped to the tab that established it. A middle-clicked link opened
signed out. Nothing here documented that as a security posture — the comment
merely restated the SDK's default — so this drops the override and lets the SDK
own the decision, where the other surfaces inherit the same one.
The hand-rolled `memoryStorage()` goes with it. It existed only because the SDK
used to touch a bare `sessionStorage` global that is undefined under SSR; the
SDK now falls back to memory itself, so the shim has no remaining job.
Worth naming: console already owns a stronger mechanism than either Web Storage
area — `src/lib/server/session.ts`'s AEAD-sealed httpOnly `hz_session`, written
precisely so a session "cannot lapse out from under a working tab". The client
half regressed off it onto the SDK's per-tab store. This change fixes the tab
bug; moving the credential itself out of script-readable storage is the separate,
larger piece of work that cookie was built for.
`hz_return_to` stays in sessionStorage on purpose: "come back to where I was" is
a property of the tab that navigated away, not of the session.
The e2e seeds move with the store. They forged tokens into sessionStorage, which
the SDK no longer reads — left alone, every primed spec would have started
signed out and the suite would have failed for a reason that had nothing to do
with what it was testing.
Reported: signing in led to a create-account flow, an organization named
"coffee cups", and a refusal read as "organization name taken". The name was
free — there is no org matching it anywhere in the IAM store.
What actually fired is the FIRST-RUN GATE (iam internal/oidc/provision.go:156):
onboarding MOVES the caller into the org it founds, so founding a second would
strip this account from — and orphan — the org it already admins, along with that
org's billing account. IAM refuses with 409 "you already have an organization".
The console renders the server's message verbatim, so the customer was told about
organizations immediately after typing a name, and read it as being about the name.
This screen is only ever rendered when the client resolved an EMPTY owner
(entry/scope.tsx: `if (!owner) return <OrgOnboarding />`) — and an owner that is
empty because a read failed is indistinguishable from a brand-new account. So the
refusal is the first RELIABLE signal that the session was wrong, and the only
honest thing to do with it is recover, not apologise: read the account, and offer
the way into the org this identity is actually in.
THE STATUS ALONE CANNOT DECIDE THAT, which is the part worth naming. /v1/iam/onboard
answers 409 for two opposite reasons — the first-run gate above, and a name
genuinely held by another tenant (provision.go:190). What separates them is whether
this account is itself in an org: only the first has somewhere to go. readOnboardRefusal
takes that reading and returns recover-or-report, so a customer who really did pick
a taken name still sees the accurate message and is not bounced into someone
else's org.
Recovery is offered, never automatic — re-authenticating on our own would loop
forever against whatever left the session ownerless in the first place.
24 tests pass in onboarding.test.ts, 4 of them new and covering both 409s.
NOT yet browser-verified: this needs a real signed-in account whose session
resolves without an owner, which is the state I cannot manufacture locally.
The topbar carried a search box reading "Search or jump to… ⌘K" and, directly
beside it, an "Apps" button. Both called the SAME `useCommandPalette().open`.
Two adjacent triggers for one surface read as two different destinations, and
"Apps" in particular implied an app directory that does not exist — the
palette is what opens either way.
The mobile drawer had the identical pair, so it goes there too; otherwise the
rule would hold on a laptop and not on a phone.
Nothing is lost: the remaining control is the one that SAYS what it does and
shows its shortcut. This is the fifth of the five switchers, and the count on
the Overview at 1440x900 is now three — one per question:
before project (top-right) · account (bottom-left) · network (top-right) · apps
after context (top-left) · account (bottom-left) · network (top-right)
Measured in a browser against the real shell, not counted by reading the JSX.
tsc --noEmit exit 0
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Five controls on one screen answered "who and where am I", and three of them
answered it from three different corners: the org mark top-left, the account
(which also switched tenant) bottom-left, and a project chip top-right beside
the network. Org and project are not two questions — they are "which tenant,
and which slice of it" — so they condense into ONE control at the top-left,
under the mark that already anchors the tenant.
Each question now has exactly one place:
WHERE ContextSwitcher, top-left org + project
WHO AccountMenu, foot of the rail identity, team, settings, balance, exit
MODE ScopeSwitcher, top-right network, with its tier dot
The network deliberately stays its own always-visible chip: it is a global
mode rather than a place, and the dot (mainnet green / testnet amber) is a
destructive-environment guard you must be able to READ without opening a menu.
There is still exactly ONE org switch. `org-scope.switchOrg` — the seam that
persists the scope and reloads so every module refetches under the new
`X-Org-Id`, and the seam tenant scoping and billing attribution hang off — is
imported, never reimplemented. The admin-gated, server-PAGED cross-tenant
search moved across whole rather than being reduced to a first page, so an
admin can still reach a tenant nobody is a member of. Verified against a
mocked cross-tenant list: typing "acme" narrows the org group to exactly
"Acme Industrial".
`adminOrgState` had no caller once the account menu stopped switching tenant,
so it is deleted rather than kept warm. The invariant it protected is now
pinned directly: `org-state.test.ts` scans every source file for `switchOrg(`
and asserts the caller set exactly. Mutation-tested — re-adding a switch to
AccountMenu turns it red, removing it turns it green.
One row, not two: the org/project/network menus rendered the same row shape
from two copies. That is `ui/MenuRow` now, so they cannot drift.
FINDING — a missing primitive, not worked around. A single-select list wants
ARIA `listbox`/`option`, and @hanzo/gui types `role` as React Native's
accessibility-role union: it admits `option` but NOT `listbox`, so an `option`
could never be given the parent ARIA requires. Used `radiogroup`/`radio`, the
single-select pair gui carries whole. @hanzo/gui should carry `listbox`.
`FieldText` grew an `ariaLabel`: a search field with no visible label had no
accessible name, and that is the console's own primitive to extend.
tsc --noEmit exit 0
vitest 3156 passed, 8 skipped (255 files)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
`deps: console onto gui 8.x` moved @hanzo/gui 7.3.0 -> ^8.0.0. gui 8 pulls
@hanzogui/lucide-icons-2@8.0.0, whose ESM build does
import { Svg, Path } from "react-native-svg"
while declaring react-native-svg in NEITHER `dependencies` NOR
`peerDependencies`. Nothing installs it, so webpack cannot resolve it, and
`next build` dies with a wall of "Module not found: Can't resolve
'react-native-svg'" — once per icon. The `react-native$: react-native-web`
alias in next.config.mjs does not cover it: `$` is an EXACT-match alias and
react-native-svg is a different package.
So console main has been UNBUILDABLE since that bump. That is why
ghcr.io/hanzoai/console has no v8.5.33, v8.5.34 or v8.5.35 — the tags were
cut, the images were never published, and universe's bump to v8.5.35 had to
be reverted to v8.5.32 to keep a pullable image. The three fixes riding those
tags (the 1px display line-box, the missing 404, @hanzo/iam 0.21.2) have been
finished in main and dark in production the whole time.
The estate already had the answer: every app on gui 8 carries this dependency
explicitly (hanzo.ai, hanzo.sh-std, app-std, console-std all pin 15.15.5),
and every app still on gui 7.3.0 does not need it. Console took the bump
without the companion. This restores the one established pairing.
Measured, not assumed:
before next build -> exit 1, "Can't resolve 'react-native-svg'"
after next build -> exit 0, 42 routes emitted
pnpm install --frozen-lockfile -> exit 0 (the Dockerfile's exact command)
Lockfile regenerated with the DECLARED pnpm 11.17.0 (node 22), not the pnpm 9
on PATH — pnpm 9 renormalizes peer-suffix keys and churns 1061 lines. This
diff is +96/-0, purely additive.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The guide headline said "100+ models. One OpenAI-compatible API." — wrong against
api.hanzo.ai, which serves 444 priced entries (and lists 107 callable ids). 400+
is true under the catalog reading and is what the rest of the estate now says.
Two comments carried counts they had no way to maintain — "85+ models across a
dozen families" and "~340 models" — each written when it was true and silently
wrong since. A comment that states a number the code does not compute is a comment
that will lie; both now describe the shape without asserting a size.
The console spoke of three key prefixes. IAM resolves two: sk- (secret,
same-tenant pinned) and pk- (publishable, refused at the auth door). An
hk- string is not a key, so nothing in a user-facing surface may offer it.
The one behavioural change is the workbench Inspector's prefix filter,
which routed hk-/sk-/pk- to the account key status; it now recognizes
sk-/pk- and refuses anything else, with the error text to match. The
pasted value is never sent — the Inspector reads the session's own key
status — so this narrows what the UI calls a key without touching auth.
The rest is copy: placeholders, Bearer examples, product Auth facts and
the guide step now name sk-, the credential the /keys route actually
mints. The workbench legend had sk- as a "provider key" and implied all
three ride the Authorization header; it now separates the secret that
authenticates from the publishable value that never does.
Commerce dropped the compound prefixes from its billing routes. The /v1/billing/
namespace already says "billing", so billing/payment-methods stuttered. Both
servers now register only the short names, and the live edge agrees:
/v1/billing/methods 401, /v1/billing/settings 403, /v1/billing/alerts 403, while
payment-methods, payment-config and spend-alerts are all 404.
The console never followed. Its card list, its card save, its card detach and its
Square-config read were all pointed at routes that no longer exist, which means a
new user could not add a card. This was the revenue path, broken in production.
Alerts had already been repointed, so the four dead call sites were the three
payment-methods ones and payment-config; they now build methods and settings.
No alias, no fallback — one name per concept.
The tests were part of the defect rather than the guard against it. Every suite
around payment methods stubbed a response body and asserted the normalization, so
a client aimed at a 404 stayed green; that is precisely how this survived. The URL
is now pinned where the request is made, including the two reads nothing had ever
asserted, and reverting any short name turns the suite red — checked, not assumed.
The two e2e specs that pinned dead URLs are corrected, and the isolation spec also
had the retired /billing/v1/ prefix.
POST /v1/billing/me/welcome is deleted rather than repointed, along with the type
and the module that fed it. Commerce removed that route deliberately: it was a
self-service mint, a browser could grant its own org $5, and commerce's own
api/billing/mint_gates_test.go calls it the TOCTOU double-mint. Credit is minted
only through the mint-gated POST /v1/billing/credit. The call was already failing
silently, so restoring it would have re-opened a closed money hole in exchange for
nothing. The trial credit still arrives — commerce grants it server-side when a
card is vaulted, and signup grants it server-side — and that path is untouched.
Scope was measured, not guessed. /v1/finance/payment-methods is still alive and
/v1/finance/methods is 404, so the finance ledger keeps the compound name; a
blanket repo-wide rename would have broken it. The Billing Center tab slugs are
console page URLs, not server routes, and are unchanged.
Two headlines blamed the wrong layer. "Card top-up isn't available on this
deployment yet" and "Adding a card isn't available on this deployment yet" both
fire when the organization has no Square applicationId or locationId — per-org
configuration, not a property of the deployment. Both now name the organization,
as does the onboarding step that had the same defect, and the stale endpoint hints
beneath them now read settings.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
identify() sent a user id and nothing else, so the warehouse held a population
of opaque subjects. Every funnel could count users and none could say which
user, and answering "who hit this" meant an IAM lookup per row — which is why
no user attribute is visible anywhere downstream.
Email and name are first-party facts about our own users, and they arrive in
the same IAM claims this file already decodes to get the id: accountFromClaims
projects them onto the Account and the bridge dropped them on the floor. The
SDK has taken traits since it took a person id; nothing new is collected, a
value already in the token is simply not discarded on the way past.
The scrubber does not touch this: capturePII gates error TEXT, and identify
traits ride build()'s `...extra` verbatim. Secret redaction is unconditional
and stays that way.
A key is omitted rather than sent undefined, so an absent claim cannot blank a
trait an earlier identify established. The org is still not sent — the tenant
is stamped server-side from the validated bearer, and a tenant the client can
name is a tenant the client can get wrong.
Two faults, one outcome: every console row landed in the $public tenant, a
partition no org can read, with no user attached. 498 rows, zero identified users.
CREDENTIAL. The client posted same-origin and trusted the first-party cookie to
carry the tenant. That cookie is the casibase session; cloud resolves a tenant from
a validated IAM bearer. A cookie-only POST carries no principal, and the door does
not refuse it — it takes the anonymous lane, which files rows under $public and
drops identify with a 200 receipt. Both ends look healthy. Pass the IAM access
token the console already holds; read it through a function, since the module is
built at import time when nobody is signed in yet.
No publishable key is passed instead, and the note in the file says why: a pk- maps
to one org while this image serves three brands resolved at runtime, and the SDK
resolves `ingestKey ?? token`, so a key would silently override each signed-in
user's own identity rather than supplement it.
IDENTIFIER. identify() sent `${owner}/${name}`, an org-relative reference in a
different id space from the IAM sub that hanzo.ai and hanzo.chat send — so one user
counted twice across surfaces, and the ref moves when an org or handle is renamed,
rewriting history. The sub was already decoded here and used only to back-derive
owner/name, then dropped; carry it through as Account.userId and identify by it.
Absent stays absent rather than falling back to the actor ref.
0.3.8 stops the client shipping a raw location on every event. The location is
stamped on all of them now, so an invite/reset/magic link — a JWT in the query,
an address in `?email=` — reached the warehouse in cleartext on the first click
and again on every later one. url, path and referrer now get the same redaction
the error plane has always applied to error text.
Console is the surface where that matters most and the one furthest behind: the
running bundle serves libraryVersion 0.3.0, six releases back, so it has no
error plane at all (sentry.ts did not exist yet) and never stamped a page onto
an event. The lockfile has been ahead of the image for a while — this bumps the
lockfile; the image has to be rebuilt and its pin moved for any of it to be
true in production.
Lock edited only where it names @hanzo/event, so an unrelated tree is not
re-resolved into a dependency bump. Integrity is the one npmjs serves for
0.3.8; `pnpm install --frozen-lockfile` accepts it on pnpm 11.17.0, the version
package.json pins and the Dockerfile installs via corepack.
Autocapture ($click/$input/$change) reaches the wire through capture(),
which supplied no location, so every $click landed with an empty url and
path and was unattributable to a page -- the one thing a heatmap needs.
0.3.5 stamps the page in build(), the single point every event is built,
placed ahead of the caller's fields so pageview()'s explicit path still
wins on the route changes that fire before window.location catches up.
The lockfile moves with the range here. What ships is the lockfile, not
the range, which is why production was serving 0.3.3 while the declared
range already read ^0.3.4. Resolves 0.3.6 (the 0.3.5 runtime plus a
test), deduped with @hanzo/observe and @hanzogui/telemetry.
cloud renamed /v1/o11y/annotation-queues[…] to /v1/o11y/reviews[…] — o11y's own
comment already called them human-review queues, so "queue" was the
implementation and "review" the resource.
lib/api/o11y.ts makes the three reads (list, detail, items) and must move or
the Annotation Queues board renders empty. The rest here is prose that named
the cloud address, including o11y.ts's "mirrors" note and next.config.mjs's
dev-proxy comment.
The console's own `annotation-queues` page — route id, label and docs link —
stays, for the same reason the score-configs page did: renaming a page id
without its heading and its documentation leaves a page that matches neither.
cloud nested dataset items inside the set that contains them
(/v1/evals/dataset-items -> /v1/evals/datasets/:name/items) and renamed score
configs to rubrics (/v1/evals/score-configs -> /v1/evals/rubrics).
The item change is a real contract change, not a path swap: the dataset was
always required — as a body field on POST and a query param on GET — and is now
a path segment. So EvalsApi.createDatasetItem takes it as its FIRST ARGUMENT
and CreateDatasetItemBody no longer carries datasetName; listDatasetItems
builds the nested URL. DatasetsModule passes the set it already had in hand.
Two comments here were wrong before this commit and are corrected rather than
merely renamed: registry.tsx, ScoreConfigsModule.tsx and o11y.ts all claimed
this surface was `/v1/o11y/score-configs`. o11y has never served it — o11y.ts's
own note says scores and their definitions STAY on /v1/evals — so the address
they named did not exist under either spelling.
DELIBERATELY NOT RENAMED: the console's own `score-configs` PAGE (its route id,
its "Score Configs" label and its ${DOCS}/score-configs link). That is product
copy plus an external docs URL, and moving the id without the label and the
docs page would leave a page whose name matches neither its own heading nor the
documentation it links to. It is a coordinated rename with hanzo-docs, not part
of an api sweep.
cloud renamed /v1/admin/spend-caps[/:id] to /v1/admin/caps[/:id] and
/v1/admin/block-storage to /v1/admin/volumes — under /v1/admin there is one
kind of cap, and what the storage board returns is a list of volumes.
TWO literal allowlists carry these names and both are load-bearing, so this
cannot land after cloud without breaking the admin boards:
- ADMIN_AGGREGATE_HEADS (src/lib/server/admin-aggregate.ts) — allowAdminSurface
admits `v1/admin/<head>[/...]`, so the head is what lets the :id sub-path
through at all.
- ADMIN_V1_HEADS (next.config.mjs) — the dev rewrite onto a real backend.
lib/api/admin-spend-caps.ts -> admin-caps.ts, with AdminSpendCapsApi ->
AdminCapsApi and the AdminSpendCap type -> AdminCap, so the module, the API
object, the type and the route all say one thing; its test moves with it.
storage-fleet.ts calls the volumes read. UsageCapsPromoModule.tsx, client.ts,
registry.tsx and the aggregate route's doc comments name these addresses in
prose and would otherwise document routes nobody serves.
e2e/storage-fleet.spec.ts intercepts the cloud call by URL, so its matcher moves
too or the fixture never binds and the board renders empty.
cloud renamed /v1/load-balancers[/:id] to /v1/balancers[/:id] — nesting under
/v1/networks was unavailable (apps/zt owns that prefix), so the flat single
noun is the one-way answer, matching its sibling /v1/vpcs.
proxy-allow.ts is the load-bearing edit: it is a literal FIRST-SEGMENT
allowlist, and `load-balancers` was a real entry, so without this every call
403s at the proxy before it ever reaches cloud. LoadBalancerModule.tsx calls
list/create/delete directly.
The admin Infra tab slug moves too — same concept, one name — while its visible
label stays "Load balancers", which is both what a person reads and what
e2e/admin-infra.spec.ts clicks. The response body is unchanged: cloud still
returns {loadBalancers:[…]}, DigitalOcean's own name for its own resource.
cloud renamed /v1/captable/share-classes[/:id] to /v1/captable/classes[/:id]
and /v1/captable/equity-plans to /v1/captable/plans: the captable prefix
already supplies "share" and "equity", so each member was repeating its group.
lib/api/captable.ts builds both URLs and must move or the Classes and Plans
panels 404. CapTableModule.tsx prints the address in a BackendStateCard hint,
which is only useful if it names the route that actually failed. proxy-allow.ts
admits by first segment, so `captable` is unchanged — only its comment, which
lists the sub-paths that head covers.
The ShareClass and EquityPlan TYPES keep their names: those are the domain
objects, and a share class is a share class wherever it is addressed.
cloud renamed POST /v1/webhooks/:id/rotate-secret to POST /v1/webhooks/:id/secret
— the endpoint has one signing secret and POST is what mints a new one, so the
verb belonged to the method, not the noun.
WebhooksModule.tsx calls the address directly, so it moves or the rotate button
404s. proxy-allow.ts needs no allowlist change (it admits by first segment, and
`webhooks` is unchanged); only its comment, which enumerates the sub-paths that
head covers, would otherwise name an address nobody serves.
@hanzo/canvas was declared "^0.1.0". A caret on a 0.x version pins the
MINOR, so console was locked to canvas 0.1.0 while 0.2.1 was current —
the same trap that froze @hanzogui/shell on 7.5.1. @hanzo/ui@8.0.38
peer-depends on canvas ">=0.1.0", which 0.1.0 satisfies, so nothing
warned. Silent freeze.
Six exact pins (dash, gui, and the four @hanzogui/* entry points) could
never take a patch either. Floated them to carets; 8.x is a stable major
so a caret is the correct expression.
Moved on install: brand 1.4.4->1.4.5, canvas 0.1.0->0.2.1,
data 1.2.1->1.2.2, logo 1.0.13->1.0.14, ui 8.0.20->8.0.38.
@hanzo/finance-ui stays on 0.1.1, now written "~0.1.1" so the range says
so. 0.2.1 declares peer "@hanzo/ui": ">=8.0.0" — satisfiable, so the peer
check passes — but its source imports DataTable, LineChart, Column,
ChartPoint and Sparkline from @hanzo/ui, and no published @hanzo/ui
exports them (verified against 8.0.20, 8.0.38 and ui-shadcn 5.9.1).
It publishes raw src/, so those errors land in the consumer's tsc.
A satisfiable-but-false peer range is worse than an unsatisfiable one:
it fails at build time in the consumer instead of at install.
tsc --noEmit clean; next build succeeds; 3152 tests pass.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The console sat on @hanzo/gui 7.3.0 / @hanzogui/shell 7.6.3 while the gui line
shipped 8.0.0, so every shell fix landed on main and stopped there: cloud.hanzo.ai
and console.hanzo.ai kept serving a header from a package that could not move.
What actually pinned it was a phantom peer. Every published @hanzogui/shell
declared `@hanzo/iam@^0.13.1` — a package it never imported — and for a 0.x range
the caret pins the minor, so once IAM reached 0.21.2 the range was unsatisfiable
and the 8.x line was uninstallable. Fixed at the source and released as
@hanzogui/shell@8.0.1 with zero dependencies.
typescript goes ^7.0.2 -> ^5.8.2 in the same commit because it has to: Next 15
does not support TS 7, and on 7.0.2 `next dev` fails to a bare
"Cannot read properties of undefined (reading 'endsWith')" after silently
installing a 5.x behind your back. Same fix hanzo.ai just made.
Verified on the real 8.x tree at 1440x900 and 390x844: Products opens as FIVE
columns with all ten categories visible and nothing clipped (it was four columns
with WEB3 + APPS below the fold), one "Sign in" pointing at /signin, one h1,
the hero primary a white 999px pill, and Terms inside the viewport with no
underline and no horizontal overflow.
rescue/stash-0: brandFromHost routes through normHost, which now trims
before stripping the port and drops the FQDN root dot. A padded, ported
or dotted host can no longer soften the suffix match and swap adminDomain
onto the default brand. Tests cover the padded/ported/dotted/lookalike cases.
The env var is read but is undefined in every shipped artifact, which
reads like an oversight and invites a build arg. It is not one.
A pk- resolves to exactly ONE org -- cloud stamps the tenant from the key
-- and this image is brand-agnostic: one build serves cloud.hanzo.ai,
cloud.lux.cloud and cloud.zoo.cloud with the brand resolved at runtime
from the request hostname. Baking a key would file every brand's traffic
into whichever org owns the key: wrong data, and a cross-tenant leak. It
is the same reason the Dockerfile bakes no NEXT_PUBLIC_*.
Signed-in traffic does not need one. host:'' posts same-origin, so the
first-party session rides along and cloud resolves the tenant from it at
full capability; identify and track already land correctly.
What is genuinely unattributed is the logged-out lane, which reaches
cloud with no credential and takes the anonymous lane -- pageview and
error stored, track/identify/group dropped, 200 either way. Closing it
needs a per-host key delivered at runtime over a channel both artifacts
share, which is recorded here so the next reader does not reach for the
build arg instead.
A merchant connecting THEIR Stripe account is a capability we offer; only
Hanzo's own charging is Square-only. Square leads the list because it is
the rail this platform bills on. The doc-comment cleanups stay: describing
a payload SHAPE by a vendor's name was always vague, whoever we charge on.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Square is the rail (via commerce), so the console says so: the payments
integration list drops Stripe, and every doc comment that reached for the
brand to describe a SHAPE — a nested subscription record, a seconds-vs-
millis period stamp, snake_case card fields, the developer-workbench
pattern — now describes the shape instead. No behavior change; the
normalizers still accept the same payloads, which is what the 25 billing
tests prove.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The count of a list envelope now reads the named field before Casdoor's
untyped second slot: total, then data2, then the rows themselves. ONE
helper (envelopeTotal in lib/api/client.ts) owns the order; getList,
iamList, makeIamClient and AuditApi.list all go through it, so the data2
fallback lives in exactly one place and dies with the legacy emitters.
e2e fixtures still emit data2 on purpose — they pin today's live wire
and flip only when the fallback is deleted.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The status and the counts field say signup (was signed_up / signedUp),
matching the cloud rename that migrates the store rows — the whole
platform now spells the concept one way.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
IAM v1.33.31 made org scoping honour-or-refuse (internal/authz/authz.go Scope):
a non-SuperAdmin asking about a foreign owner is REFUSED, not silently re-pointed
at its own org. The confidential `hanzo-console` client is exactly the principal
that starts earning 403s, and this module read every failure as `null`.
`iamGetData` returned null when unconfigured, null on a thrown fetch, and null on
`!res.ok || status !== 'ok' || data == null` — so a 403 refusal, an unreachable
IAM, and a malformed envelope were indistinguishable from "no such row". IAM's
own getHandler (internal/compat/aliases.go) answers three DIFFERENT things from
one endpoint:
hit 200 {status:"ok", data}
absence 200 {status:"error", msg:"the entity does not exist"} (httpx.Err)
refusal 403 {status:"error", msg:"forbidden: …"} (authz.Deny)
Collapsing them cost real behaviour, not just tidiness:
- getMember is the invite flow's identity read. A refusal became "this
invitation is no longer valid — the member was removed" (410), telling an
invitee their membership was revoked when IAM merely would not answer, and it
is the same null the single-use activation guard reads.
- getUserKey is the API-key state read. A refusal became "no key", which is the
exact regression its own docstring records: the page falls back to Create, the
live key is hidden, and the user mints a duplicate over a key they can no
longer revoke.
So: ONE transport (`iam`) that returns data or throws, carrying `absent` for the
one benign kind — the same contract and the same wire constants as the app's
client (ai-sdk lib/org/onboard.ts) and cloud's Go client (apps/account/iam.go
`do`), which is why `method` is explicit here: IAM has param-only POSTs. Over it
sit exactly two named policies: `iamGetOrAbsent` (absence is a legitimate answer
to null, everything else propagates) and `iamGetUser` (fail-SOFT, and safe
precisely because the admin gate admits only on positive evidence, so a lost
answer can only ever DENY). Soften where a lost answer closes a door, never where
it opens one.
That replaces FOUR transports — iamGetUser, iamCall, iamGetData, iamPostBody —
which had three different error conventions between them.
Also drops the org-onboarding half (getOrganization, createOrganization,
createUser, moveUserToOrg, IamOrganization): dead since onboarding moved server
side to cloud's POST /v1/iam/onboard (apps/account/account.go), which
OrgOnboarding.tsx calls via v1Url('iam/onboard'). Zero consumers — tsc --noEmit
over the whole app is the proof, not a grep. Deleted outright, no shim.
The one behaviour change beyond the above: the transport now refuses when the
confidential client is unconfigured instead of sending Basic Og== and letting IAM
401. Both throw; this one says why and skips the round-trip. Every route already
checks mintConfigured() first, so the three identity.test.ts cases that relied on
the old unguarded path now configure the client, which is the production
precondition they were always standing in for.
Tests: identity-refusal.test.ts pins all three answers plus the unreachable and
malformed cases for both live readers, and pins that a REFUSED claims read still
fails the admin gate CLOSED. 6 of its 11 fail against the code this replaces.
Suite 3141 passed / 8 skipped (was 3130 / 8); tsc --noEmit clean; next build
compiled successfully.
Every hit was a comment naming the wrong system. hanzoai/iam is Hanzo IAM —
original, clean-room work; the vendor-derived server was hanzoai/iam-v1, which
is retired and ships in nothing. Replaced the name with IAM and kept each
comment's fact intact: tokens really are ~3.6 KB full-user JWTs (hence the two
cookies and the chunking), IAM really does pack the full user object, and it
really does skip the client-secret check when the secret is empty.
Comments and markdown only — no identifier, cookie name, or wire field moved.
This file says "the cloud /zap WS face is NOT served (the edge returns SPA
HTML, 200 not a WS upgrade)". That was true when written and is not true
now. Measured 2026-07-28 on api.hanzo.ai, platform.hanzo.ai and
cloud.hanzo.ai: a WebSocket upgrade handshake returns 401 on all three —
not SPA HTML, not 200. A route that refuses an unauthenticated upgrade is
a route that exists.
Read as current, the paragraph says ZAP is unavailable when it is merely
gated, which is the kind of stale rationale that gets acted on. The REST
path it describes is still correct and still shipping, so nothing about
the code changes — only the reason.
Marked stale in place rather than deleted: the history explains why
Providers moved to REST, and removing it would lose that. The correction
names what was measured and where, so the next reader can re-check rather
than trust either version.
Found while sweeping for docs that actively mislead. The sibling case,
universe crs/console.yaml justifying replicas:2 with an admin.hanzo.ai
route that no longer exists, needs no fix — that CR has since been
retired with the standalone console.
Cloud folded /v1/paas into /v1/platform — paas was a second name for the same
product, and one product gets one name. The operator fleet/drift board now lives
at /v1/platform/fleet.
No functional change here, and that is the point: the `platform` allowlist head
already admits every /v1/platform sub-path, so the new route was reachable the
moment cloud shipped it. What was stale was the PROSE — three comments still
pointed readers at `/paas/apps`, a route that no longer exists, and the
allowlist's own sub-path list did not mention the board it admits. A comment
that names a dead route is worse than no comment: it sends the next reader to
look for a surface that was deleted.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The generic renderer had no realtime at all — zero EventSource, zero subscribe.
This adds the client half of the ONE mechanism the engine now serves:
changes.list(q) one page of the feed -> GET /v1/framework/changes
changes.subscribe(q,h) the same query held open as SSE -> /v1/framework/stream
presence.list(dt,name) the roster -> GET /v1/framework/presence
changeQuery is ONE function for the poll and the stream, because server-side
they are ONE query — the stream is that query in a loop. A view renders current
state from records.list, keeps the cursor it gets back, and applies changes from
there.
No credential and no org leaves the browser. subscribe opens a same-origin
EventSource through the console's existing /v1 bearer proxy, which already
streams res.body straight through; the proxy mints the short-lived user-bound
token and the engine resolves the org from its owner claim. There is nothing a
page could send to name another tenant, which is the reason to prefer SSE here
over a WebSocket that would need its own auth path.
Resume is the browser's job: each frame's id IS the change's seq, so a dropped
connection reconnects with Last-Event-ID and misses nothing. onReset fires when
the cursor fell behind the server's retention window — refetch, THEN resume,
never patch on top of a state you never had.
Passing watching: '<DocType>/<name>' additionally declares presence for as long
as the connection lives, which is why presence needs no client->server channel.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
@hanzo/ui 8.0.20 instruments itself — DataTable, PrimaryButton, SlideOver,
ConfirmDelete, the Field* editors, ComboBox, Segmented/SearchInput, MenuItemView,
OrgSwitcher, ThemeToggle, Toast and EmptyState now report what a user did. The
console renders all of them, so it gets the whole interaction vocabulary without
a line of app code — that is the point of instrumenting the component instead of
the app.
But those components emit through module-scope `track()`, which resolves an
AMBIENT client, and left alone that would have been a SECOND client: default host
api.hanzo.ai, no session cookie, its own anon id and its own batch. Cloud's
anonymous capability lane admits pageview and error only, so every component
event would have been DROPPED on arrival — a silent, plausible-looking nothing.
So `src/lib/event.ts` — the file that already declares itself the ONE console
client — registers `eventClient` as the ambient one. Now the provider's pageviews,
the error boundaries, and every shared component ride a single same-origin batch
that carries the session cookie, which is what makes their events CREDENTIALED and
attributable to the signed-in org. One client, one anon id, one stream, exactly as
that file's header always promised.
Also pins typescript back to 5.9.3. Under the 7.0.2 that main had taken, Next
15.5.19 stops honoring the tsconfig `paths` map and the build dies on every
alias — `Can't resolve '~/config'`, `'~/lib/event'`, `'~/components/ProductRoute'`
— i.e. main could not build at all, before and independent of this change. Adding
`baseUrl` does not help; only the TS pin does.
Build: 8.0.20 installs clean under pnpm 11 (8.0.19 could not — it shipped
`workspace:*`, fixed upstream) and `next build` completes.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
This workflow polled github.com every 10 minutes and fast-forwarded the forge
from it. It was written when which side was canonical was still open; it is not
open now, so a cron that reconciles two mains is a second answer to a settled
question. Removing it leaves exactly one way for code to move.
It was already inert by its own admission — the header notes it does nothing
while the GitHub repo is a pull mirror, because the forge overwrites main on its
own timer and rejects the push.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
CI fails at install, before anything is built:
[ERR_PNPM_OUTDATED_LOCKFILE] Cannot install with "frozen-lockfile"
specifiers in the lockfile don't match specifiers in package.json:
- @hanzo/ui (lockfile: ^8.0.11, manifest: ^8.0.17)
package.json was bumped without regenerating the lockfile, and `--frozen-lockfile`
refuses — correctly; that is what frozen means and the strictness is worth
keeping.
Resolves to 8.0.18, the newest release satisfying ^8.0.17.
Regenerated with pnpm 11.17.0, the version this repo declares in
`packageManager`, so the file matches what the builder's corepack will use. The
diff is large but it is not a format rewrite: lockfileVersion stays 9.0, the
change begins exactly at the @hanzo/ui specifier, and only 30 package entries
are added (2 removed) — lucide-react, sonner, tailwind-merge, react-remove-scroll
and friends, i.e. what @hanzo/ui pulls in between 8.0.11 and 8.0.18. The rest of
the churn is peer-hash suffixes on existing entries. packages and snapshots both
count 1060, so the file is self-consistent.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
`patches/@hanzo+iam+0.13.6.patch` added a fallback that reads the token's
`exp` claim when the server omits `expires_in`, so session expiry is still
learned. It was written against 0.13.6; the dep has since moved to 0.21.1,
so patch-package refused it — and, because a version mismatch is a
warning-class failure there, `postinstall` still exited 0. The patch had
silently stopped applying with nothing failing: verified absent from the
installed 0.21.1, so the console was running without the fallback.
Fixed upstream instead (hanzo-js/iam 08476b4, released as 0.21.2) where it
belongs — one implementation, every consumer — so the patch is now
genuinely unnecessary, which is what patch-package itself reported.
Verified: 0.21.2 installed, the fallback present in node_modules, and
postinstall clean ("No patch files found"). typecheck 0 errors; 3136 tests
pass.
Co-Authored-By: Hanzo Dev <dev@hanzo.ai>
gui.config.ts declared the console's type/radius/space ladder. It is not the
console's ladder — it is the ladder every @hanzo/ui/product component is drawn at,
and the dedicated Hanzo Social app renders those same components. A private copy
would have forked the moment either side tuned a size.
It now ships with the components (@hanzo/ui/gui-config, 8.0.17); this file is the
console's import path onto it, so `~/gui.config` call sites are unchanged.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The whole social product lived HERE — a 601-line SocialModule plus its own copy of
the /v1/social contract in src/lib/api/social.ts. That is fine while the console is
the only host, and it stopped being true: social.hanzo.ai gets a dedicated app, and
the only way for a second app to render Publish was to copy 800 lines and let them
drift.
So the product moved to @hanzo/ui/product/social (SocialResource + createSocialApi)
and the console keeps only what is genuinely the console's:
- src/lib/api/social.ts is now the TRANSPORT binding — the four verbs on
originV1Url('social/…'), through our own app/v1 user-bearer BFF — and re-exports
the contract so call sites keep one import path. It binds
@hanzo/ui/product/social/api, the React-free entry, so the console's data layer
(and its node tests) never load a component tree.
- SocialModule.tsx is the mount: hand SocialResource the bound client. 23 lines.
- The tests split the same way the code did: the contract's normalizers and paths
are tested in @hanzo/ui; what is tested here is what is ours — that a contract
path resolves to this origin's /v1/social/… .
817 lines of module + client become 77. Nothing about the surface, the routes, or
the tenant isolation changes: the org is still resolved SERVER-SIDE from the bearer
owner claim, and social.hanzo.ai still boots straight into this product.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
TypeScript 7 is the native Go compiler; the npm package is a shim resolving
a platform-specific native binary. The build is `next build`, so SWC does the
emit and tsc is typecheck-only — no built artifact changes.
Measured on this same config before and after: 0 errors on both tsc 5.9 and
tsc 7, so the compiler swap introduces nothing new.
Note: `pnpm install` exits non-zero here on an unrelated, pre-existing
postinstall failure — patches/@hanzo+iam+0.13.6.patch no longer applies
because the installed @hanzo/iam has moved past 0.13.6. That failure
reproduces with the previous package.json and is not caused by this change.
Co-Authored-By: Hanzo Dev <dev@hanzo.ai>
Cloud's KMS surface is /v1/kms/secrets now — URL-addressed orgs were removed
because a path that names a tenant is caller-selectable. The proxy keeps its
policy predicate exactly (brand org, or the SuperAdmin's ?org= switch) and
expresses the result where every other subsystem already reads it: X-Org-Id,
the acted-on org the identity boundary mints for a switched-in SuperAdmin.
The module footer stops advertising a route that no longer exists.
The gate had three names for one concept: the component was OperatorAccessRequired,
the headline said 'Operator access required', the body said 'an admin role', and the
predicate underneath was useIsSuperAdmin. Lux carried a fourth copy — its own
hardcoded 'Operator access required' whose body told a signed-in operator to
'sign in with an operator account', which this repo's own P1 rule forbids: a 403 is
signed-in-but-not-authorized, never a sign-in prompt.
The structure was already one-way — one component, one predicate across 27 call
sites. Only the naming forked. So: SuperAdminRequired, and the headline is a single
exported SUPERADMIN_REQUIRED that Lux's error card now shares, so the string cannot
drift again. The body states what the predicate actually tests — membership of the
reserved admin org.
Also adds an e2e for the research dashboard, written so it can fail. The console is
a SPA behind a catch-all: every path returns 200, so a status-code test passes after
the route is deleted. And /research is behind AuthGate, so an anonymous visitor sees
neither the dashboard nor the gate — measured, the body reads 'Sign in to your
account'. The two tests that run therefore prove the gate holds and that a nonsense
path renders no dashboard; each anchors on the shell having rendered first, because
an absence assertion is otherwise satisfied by a dead host. Verified: green against
cloud.hanzo.ai, both red against an unreachable one. Proving the dashboard paints
needs a SuperAdmin session, so that test is staged behind HANZO_PASSWORD rather than
faked green.
TypeScript 7 is the native Go compiler; the npm package is a thin shim
that resolves a platform-specific native binary.
Safe here because the build does not emit through tsc — the bundler does,
so tsc is typecheck-only and the built artifact is unaffected. Gated on a
measured comparison of both compilers against this same config: TS7
introduces no errors TS 5.9 did not already report.
typescript now 5.9.3
Co-Authored-By: Hanzo Dev <dev@hanzo.ai>
Cloud's Post has always had `media []string` (store.go, always serialized as an
array, never null) but the console type and normalizePost omitted it, so the
field was invisible here — and destructively so: updatePost rebuilds the row
from the request body with `Media: normMedia(body.Media)`, meaning any PUT that
round-tripped a console-normalized Post would wipe the post's media. Nothing
calls posts.update today, so this is latent rather than live.
- Post.media + normalizePost, via one `strs` coercion helper that
normalizeProviderCapability's inline duplicate now folds into.
- Show the URLs in the post detail drawer, so the data is visible rather than
parsed and discarded. No upload affordance: cloud has no media endpoint, and
inventing one would be dishonest.
- LLM.md: replace the stale "embed the Hanzo Social dashboard" TODO — it still
described the retired standalone social-frontend as live and listed
PostComposer as unextracted. It now records the cutover (social.hanzo.ai IS
this console in social-only shell mode), the @hanzo/ui/product/social parts,
and the exact publish blocker keeping SocialModule on its local copies.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
(cherry picked from commit eb1d7a6056aa7d2daec80ce17dc7d60794aaaca1)
generateMetadata already resolves the title from the request host — a
Lux console renders <title>Lux Cloud Console</title>. The description
beside it was a literal and shipped 'Unified admin console for Hanzo
Cloud and all cloud products.' to console.lux.cloud and
console.zoo.cloud.
The correct title is exactly why nobody caught it: the visible tab looked
white-labeled, so the head element behind it was never read.
Both strings now come from brandName. Every brand-visible value in this
function must; a literal here re-opens the leak.
Every node row on this route was silently 'not-reporting': luxd serves one
HTTP prefix and it is /v1. Measured 2026-07-27 against api.lux.network:
/ext/info -> 404 /v1/info -> 200 {"version":"luxd/1.36.2",...}
/ext/bc/P -> 404 /v1/bc/P -> 200
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
TypeScript 7 reports TS2882 for a side-effect import with no type
declaration; TS 5.x accepted them silently. Next.js resolves stylesheets
through its own loader, so `import './globals.css'` never reaches the
TypeScript module resolver — the ambient declaration tells the checker
they are legitimate rather than giving them a shape.
Closes the entire TS7 gap for this app:
before ts5.9 25 errors ts7 32 errors (7 unique to TS7, all TS2882)
after ts5.9 25 errors ts7 25 errors (0 unique to TS7)
No regression on 5.9. The remaining 25 are pre-existing on both compilers.
Co-Authored-By: Hanzo Dev <dev@hanzo.ai>
The first pass left three classes of config that BOTH tsc 5.9 and tsc 7
reject. Each was proven against both compilers before changing:
TS5090 A `paths` target must be relative once `baseUrl` is gone. The
first pass skipped the "./" prefix wherever baseUrl pointed at
the config's own directory, reasoning it was semantically
equivalent. It is not — without baseUrl a non-relative target
is rejected outright, by 5.9 as well as 7.
TS5110 `moduleResolution: node16` requires `module: node16`. The first
pass mapped commonjs projects to node16 resolution alone, which
BROKE those configs for the current toolchain. Both are now set.
TS5102 `downlevelIteration` is also removed in TS7; it was missing from
the dead-flag list.
Verified: repos that tsc 7 previously refused (base-studio, js-sdk, kv-js)
now report zero config errors on tsc 7 AND tsc 5.9.
Co-Authored-By: Hanzo Dev <dev@hanzo.ai>
TypeScript 7 is the native Go compiler and removes `baseUrl` and
`moduleResolution: node|node10`. Both appear here, so `tsc` from TS7
refuses the config outright (TS5102 / TS5108) and cannot typecheck.
`paths` targets resolve relative to `baseUrl` when it is set and relative
to the tsconfig file otherwise. Every `baseUrl` folded here already
pointed at the config's own directory, so dropping it moves nothing and
the targets are left byte-identical. Where a baseUrl pointed elsewhere,
each affected target was rewritten as join(baseUrl, target).
`moduleResolution` was chosen from the declared `module`: commonjs ->
node16, esnext/preserve -> bundler. Configs whose `module` is unset or
exotic were left alone rather than guessed at.
The result is accepted by BOTH toolchains, so nothing has to upgrade
TypeScript in lockstep. Verified on hanzo/chat packages/api: tsc 5.9
779 -> 778 errors (no regression), and tsc 7.0.2 now runs the project
in 2s where it previously refused the config.
Co-Authored-By: Hanzo Dev <dev@hanzo.ai>
Every string a user or operator reads should name the Hanzo product, not the
OSS project it is built on. Fourteen places still read the other way:
- Deploy (registry + GitOpsModule): the catalog description, the `gcp`
equivalence row, the page subtitle, and the empty-state bullet all said
"No ArgoCD". The `gcp` field renders as an "Equivalent to" row on six
surfaces, so an operator read "Deploy — Equivalent to: Cloud Deploy /
ArgoCD" (which is also wrong: ArgoCD is not a GCP product). Now: the Hanzo
operator reconciles.
- Functions overview: the health tile read "Fission health" — the same file
that renders the tab already documents the rule ("never the OSS name").
Now "Functions health".
- The three telemetry 501 cards (Metrics, Status, Lux Network) named the
telemetry engine as ours in operator-visible body text; the Lux one did it
on a Lux-branded surface. They now say "the telemetry store". The `VM_URL`
env var is UNCHANGED — something reads it.
- Vector empty states (collections + product landing): the index a collection
maps to is ours; it reads "Vector/Search index" now.
- App Store: provenance tags (`caprover`, `dokploy`, `casaos`, …) were kept
out of the quick chips but `availableTags` still handed them to the "All
tags" expander, so a customer browsing our store saw chips naming other
marketplaces. They are dropped from the browsable set — the set itself is
catalog-derived data and stays, and free-text search still matches it.
- admin-o11y doc comment: our own tables were described with the dead
`signoz_*` prefix, stale since the o11y debrand landed.
- The GitHub-sync workflow called our forge "this Gitea" twice; endpoints.md
called our backend "the casibase API".
- storage-fleet e2e fixture: `pvc-signoz` / service `signoz` were screenshotted
into e2e-shots inside a Hanzo operator board.
Attribution is untouched. NOTICE, LICENSE, the registry's `upstream` rows, and
every provenance comment (Gitea/Casdoor/Temporal/ArgoCD/PocketBase/SeaweedFS/
Fission/Langfuse lineage notes) are left exactly as they are — they explain
where a design came from and are legally load-bearing.
Not changed, deliberately: the Datastore "Connect" snippet still names
`clickhouse-client`. It is a command a customer copies and runs, and
packages.hanzo.ai does not serve a `datastore-client` yet — renaming it would
hand people a command they cannot install. That one needs the client published
first.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Follow-up to the scale/ladder pass. Every change here was found by RUNNING the
gate against the shell and reading what it caught, not by reading source.
THREE PANELS BECOME ONE. Adding a `Panel` for the settings surface made it the
third: `ui/Metric.tsx` had one for chart bodies (13 consumers) and
`overview/living/tiles.tsx` had a private one. Same concept — a rounded surface
with a quiet header — carrying three paddings, two title sizes and two names for
the header slot (`right` vs `actions`). Now one definition in `ui/Panel.tsx`,
one import path, one name per prop. The body is CONTENT (padded) or `rows`
(a `Row` list that pads and separates itself) — the flag names the content
shape, not a style, which is why it is a flag and not a fourth component.
That unification also fixed a real mobile bug. The tiles' `minW={340}` inside a
366px pane painted to x=432 at 390 wide, clipped with nothing to scroll it. A
pixel minimum bigger than its container is always wrong; `min(340px, 100%)` says
the actual intent — this wide, never wider than the space there is — with no
breakpoint to get backwards. Same class in the Resources header, where a bare
View is `flex-shrink: 0` so it held its 533px max-content width and never
wrapped: the v8.5.29 landing-footer defect, in a second place.
THE ACTIVE STEP MARKER WAS 3.36:1. White on `$color9` — below AA, and measured,
not eyeballed. On the monochrome ladder the CURRENT step should be the strongest
surface: `$color12` with `$color1` ink, ~18:1, and it reads as "you are here"
rather than as a mid grey.
`Monogram` (ui/Monogram.tsx) — an avatar's initials scale with their circle, so
they are a graphic, not app text, and the gate skips them. It has to be a real
DOM element: react-native-web DROPS unknown props, so `data-monogram` written
onto a Gui `<XStack>` looked applied in the source and was absent in the page.
It also has to sit around whole distributed components, because @hanzo/ui paints
the org mark itself — so the gate additionally requires text of at most three
characters, and a marker placed that widely still cannot exempt a label.
The product rail is now a real `<nav aria-label="Products">` landmark. It had no
role at all, so a screen-reader user could neither jump to the product list nor
skip past it. `display: contents` adds the landmark with zero layout effect.
GATE CORRECTIONS, each because the rule was wrong, never to make a failure go
away — every one is narrower or more truthful than what it replaced:
- a closed drawer parks off screen BY DESIGN (nav at -320, account at +390), so
an `aria-hidden` subtree is not content;
- a wide DataTable already scrolls inside its own container, so painting past
the edge only counts when nothing can scroll to it;
- the rail mixes rows and columns, so "tops never decrease" was simply false —
it now asserts every reachable row is inside the viewport;
- @hanzo/gui pins its portal host to a hardcoded 105001 that no console config
can reach. Excluded by its own class marker and REPORTED, rather than raising
the ceiling and quietly letting our own literals back in.
Gate: 6/6 green. It failed 6/6 before these fixes, and each failure was a real
defect — GET STARTED, the monogram, 3.36:1, the clipped tile.
The shell had three type scales, thirteen radius spellings, an odd-pixel
spacing ramp, and a stacking order expressed as literals up to 100002. This
makes each of those exactly one thing, and adds the gate that keeps them one.
THE ONE SCALE (gui.config.ts). app/design/typography.css declared the compact
register (11/13/14/15/17/21/26); the Tamagui $N ladder is what thousands of
call sites actually type; ten distinct sizes rendered. The ladder is precisely
why we do not edit the call sites — it is remapped once onto the declared
numbers, so every surface lands on the scale. Same for radius (four values:
6 control, 8 input/row, 12 panel, pill — the three spellings of "pill"
collapse to the $10 token) and spacing (the 4px ramp; $2/$3/$4 were landing on
7/13/18px, the three most-rendered paddings in the app).
The 16px leak was not the ladder: `body` never set a font-size, so everything
the ladder does not reach inherited the browser's 16px root. One declaration
in globals.css, sourced from --text-base, and the inherited size and the named
size finally agree.
ZERO ALL-CAPS. The hard rule. 26 `textTransform="uppercase"` sites deleted
across 15 files and 19 typed-in-caps strings re-cased — including GET STARTED,
which the audit missed and the gate caught. Where a label was carrying
hierarchy by shouting it gets it back the calm way: 11px, weight 500, muted.
Genuine acronyms (API, GPU, CIDR, …) are untouched and allow-listed.
THE Z LADDER (src/lib/z.ts). app/design/z.css has always declared it and was
read in zero places. Every literal now names a role instead: dropdown, modal,
popover, toast. Correcting the brief — @hanzo/brand 1.4.0 ships no --z-* at
all; the vendored z.css is the real ladder, so its numbers are used rather
than a third set invented to solve a problem about having too many sets.
PANEL + ROW (ui/Panel.tsx). The one primitive genuinely missing: a stack of
rounded panels whose rows are label + description left, control right. The
shared per-product Settings view is converted to it, which is every product's
Settings tab, and deletes a bespoke row in the process.
THE GATE (e2e/design-invariants.spec.ts). Asserts on computed style and
geometry, not source: zero uppercase and zero typed caps, membership in each
scale, every stacking layer from the ladder, overlays that actually paint and
sit on screen, WCAG contrast from the colours that painted, and no sideways
scroll at 1440 or 390. Two exemptions, both narrow and declared at the source:
a monogram scales with its circle (data-monogram) and chart axis text lives in
SVG. A rule that only lives in a review comes back.
Pin, sort, filter, search and act, as ONE mechanism each instead of three
duplicates and a broken write path. Every claim measured in a browser on
computed style and geometry (e2e/find-and-do.spec.ts, 7 tests).
BUG: every preference was lost on reload. Preferences treated the account as
authoritative for keys it had never mentioned, so each load replaced state AND
the write-through cache with the token's (empty) view — losing pins, pin groups,
product colours and open nav sections. The account now wins per key it CARRIES;
the cache fills the rest (preferences-core.mergePrefs, pure, tested).
ONE list view (src/lib/list): useList(id) persists a list's search, order and
facets under `list.<id>` in the same account store as pins. Its comparator,
reducer and predicate are promoted verbatim out of admin/infra's private copy,
which now re-exports them — one implementation, its 30 tests unchanged. `Filters`
is the one bar (search + facets + a Reset that exists only when something is
narrowed). Adopted by Models and Marketplace, dropping two bespoke search boxes.
Pins in search: pinnedFirst is the one "pinned leads" rule, shared by the sidebar
and the palette. Every result carries a right-edge pin — invisible until reached,
lit while pinned — and ⌥↵ pins the selection without closing.
BUG (introduced, then caught): pins must not outrank what you typed — floating
them over the ranked list made "billing" + ↵ open Models. Pins order the DEFAULT
view only; typing is decided by relevance. Locked by asserting where you land.
BUG: the resting pin painted at full strength — a plain .hz-pin lost to Gui's
compiled `:root ._ops-…` (0,2,0), then a broken CSS comment silently killed the
rule outright. Only the computed-style assertion caught either.
tsc clean; vitest 3121 passed (+35); find-and-do 7/7 with screenshots, incl.
4.5:1 contrast and zero horizontal body scroll at 390px. NOT verified on live
admin.hanzo.ai (auth-gated, no password typed).
The console had THREE places to answer "who am I and which org am I in": an org
switcher at the top of the sidebar, an account popover at the bottom, and a third
menu in the phone drawer — with four ways to sign out between them. They are now
one control, mounted where the CTO asked for it, and it is the shared
`@hanzo/iam` UserMenu rather than a fourth thing built here.
Deleted: OrgSwitcher.tsx (a wrapper around the retiring shadcn @hanzo/ui), the
account popover and its two private helpers, the drawer's own theme/profile/
sign-out rows, and the wallet's duplicate sign-out. The shell is 160 lines
lighter and the wallet is a wallet again.
REACH. The SDK's own org state reads the token's memberships claim, which cannot
express what an admin console does. `@hanzo/iam` 0.21.1 takes an optional
`findOrgs`, so the switcher searches the console's EXISTING lazy, server-paged
cross-tenant list — the same `IamAdminApi.organizations` the full-page picker
uses, gated to a super admin, unchanged. A regular user is never asked for it and
sees their own org exactly as before. The reach was extended in the SDK, not
forked here.
MONEY. `adminOrgState` is a pure adapter and passes `org-scope.switchOrg` BY
REFERENCE — the console's one switch, which persists the scope and reloads so
every module refetches under the new `X-Org-Id`. No second switch, no header, no
billing call is added, so the ledger rule sits exactly where it sat.
`org-state.test.ts` pins the identity so a second switch cannot creep in later,
and the render spec asserts the write to `hanzo.console.org` really is what a
selection produces.
Two z-indexes joined the ladder they were ignoring, because the account control
needs them: a SlideOver was pinned at a literal 1000 and the rail flyout at 1000,
both ABOVE the popover rung, so on a phone the menu opened inside the account
sheet and the sheet swallowed it — present, measurable, and unclickable. They are
now `--z-modal` and `--z-dropdown` from `app/design/z.css`, whose own comment
already said a popover anchored in a sheet paints over it. The remaining literals
(tour, toast, detail pane) are the shell lane's.
Proven by rendering, not by status codes: e2e/account-menu.spec.ts opens the
control in the real signed-in shell and measures an opaque background, Geist, a
body fully inside the viewport at 1440 AND 390, rows padded and at 4.5:1, a hover
state that actually differs, zero uppercase nodes, the menu hit-testing to itself
over the sheet — and finds "Acme Industrial", a tenant that is nobody's
membership. tsc clean; 3093 unit tests green; next build and build:embed green.
Clicking into a product revealed its options twice: the sidebar drilled in and
rendered the product's sub-nav from the registry, and the module ALSO rendered a
private `const TABS` strip. The two lists were written independently and
disagreed — /models showed eight rows in the rail and four tabs in the content,
and they did not agree on what the index is called ("Overview" vs "Catalog").
Eight products declared no sub-pages at all, so their real tabs lived only in the
content strip and the rail hid them.
The registry is the one source now. `CatalogEntry.indexLabel` names a product's
own index where it is a named surface (Models → Catalog, Tasks → Workflows, Team
→ Members); the eight missing `subpages` sets are declared, and the icons the
strips carried moved onto the declarations. `components/ui/SubNav.tsx` renders
that same declaration for the viewports where the sidebar is a drawer and hides
itself at lg+ where DrillNav owns level 2 — one declaration, two mounts.
Level is the URL and nothing else: `activeSubpage` reads it back, `subpageHref`
writes one URL per screen, and `subpageSlug` validates a segment against the
declaration (so a hand-typed tab cannot light a view the module does not render,
and an admin-only sub-page is never offered to a customer). 18 modules lost their
`TABS` plus their bespoke TabButton/TabBar/nav/path helpers.
Functions had two indexes — its '' route was a living-overview while the module
carried an older OverviewTab reachable only via a bogus URL, and the index
therefore had no level-2 nav on a phone. One component owns the product at every
level now; the dead OverviewTab is deleted. /crm/companies was a duplicate URL
for the screen /crm already renders; the index IS Companies.
Render-proven (e2e/level-2-nav.spec.ts, 5/5): at 1440 the content strip's
computed display is none while the rail is drilled; at 390 the strip is the one
nav, lists the same labels, every tab has a painted box inside the viewport, and
the body does not scroll sideways; a reload of /models/blend lands on Blend; Back
moves the level without dropping the drill or the account-backed pins; and a
sweep asserts all 18 converted products paint no second nav.
vitest 3093 passed (+9). tsc adds zero errors — the one it reports
(src/lib/event.ts `dsn`) is pre-existing local dep drift and reproduces on a
clean origin/main tree.
Superseded: the Hanzo GitHub App pushes a webhook, so the forge tracks GitHub
without a per-repo workflow. This file called git.hanzo.ai/api/v1/.../mirror-sync
— a Gitea API for a system we no longer drive — and would sit inert in every repo.
One mechanism, in one place, instead of ~350 copies of a cron.
Two rendering contracts were silently not applying. Both found by measuring
computed styles in a real browser, not by reading code.
The product-guide headline had a 1px line box. PitchHero set
`style={{ lineHeight: 1.12 }}` — a correct ratio in plain React, whose unitless
allow-list includes lineHeight. React Native Web's does not, so under @hanzo/gui
it compiled to `line-height: 1.12px`: a 30px/900 headline in a 1px box, a 29px
overflow that dropped its descenders into the subhead and clipped the GET STARTED
eyebrow. It now wears `hz-display`, the class this app already added for exactly
this (PublicLanding, v8.5.24) — one way, one rule, every token and breakpoint.
Measured after: 30px on 33px leading at desktop, clean two-line wrap at 390px.
e2e/leading.spec.ts pins the invariant rather than the call site: no visible text
node on /models, /agents or /playground may compute a line-height smaller than its
own font-size. It fails on the unfixed tree and catches the next numeric lineHeight
anyone writes without their knowing about RNW's allow-list.
No overlay was wearing the elevation ladder. Gui compiles its shadow props to an
atomic rule injected at runtime as `:root ._bxsh-…` — specificity (0,2,0). The
design-token utilities were plain `.hz-paper` (0,1,0) and lost, so the command
palette, app launcher, floating chat and three menus rendered Gui's
`0 12px 24px rgba(0,0,0,.33)` instead of ring + top highlight + --hz-elevation-3.
On the true-black canvas that shadow is nearly invisible — the sheets did not lift
off the page. The utilities are now `:root .hz-x.hz-x` (0,3,0): deterministic in
either stylesheet order, no !important.
And every anchored overlay now wears ONE surface. Eleven Popover.Content sites
passed Gui's `elevate` while three wore `hz-paper` — one concept, two depths, plus
the same bordered/bg/borderColor triple repeated fourteen times. All fourteen now
spread ~/components/ui/paper, which holds the surface, the token elevation and the
opacity-only hz-menu-in entrance in one place.
Verified by rendering: scope switcher, network picker, model selector, save-prompt
popover and the ⌘K palette all opaque, correctly anchored, ring visible, nothing
occluded. 3,086 unit tests pass; leading spec green.
admin.hanzo.ai could show what we BILL but not what we RUN. The nodes, the
volumes, the load balancers were visible only in the DO console, with no
cross-reference to what Kubernetes actually mounts — so "is this orphaned?" had no
answer anyone could act on. `/v1/admin/infra` (already live in cloud) is that
answer; this is its UI.
IT REPLACES A SECOND BOARD RATHER THAN JOINING IT. While this sat on a branch,
`block-storage` shipped: the same DO volumes, listed with fill % beside this one's
inventory of them. One noun, two boards. The two BACKENDS genuinely answer
different questions about the same object — /v1/admin/infra knows what is
REFERENCED (and therefore safe to delete), /v1/admin/block-storage knows how FULL
it is — so the volumes tab now reads both and shows ONE row with a Fill column.
The block-storage catalog entry and its module are retired; its client survives as
the fill source. Two reads for one row is fine. Two boards for one noun is not.
The delete control is deliberately timid. It shows WHY something is or is not
deletable rather than only whether, because the honest answer is usually "not", and
it defaults to snapshot-first. The server re-proves deletability from a FRESH
cross-cluster scan before acting, so the button is a request, never a verdict — a
client that lied would still be refused. That check is the reason this exists: the
naive "no k8s tag" test would have proposed deleting 4.39 TiB of live cluster data,
and one unreachable cluster freezes every deletion rather than degrading.
Sorting went into the SHARED DataTable, so every admin board gets it — opt-in per
column, caller-owned comparator, `aria-sort` on the headers.
Applied to current main rather than merged: the branch is 843 commits behind, and
the three conflicts were a fused registry entry, a `tracker` id belonging to an
unrelated commit on the same old branch, and an aggregate-head list that simply
wanted both heads.
Typecheck adds ZERO errors (29 before, 29 after — all pre-existing). 3058 tests
pass, up from 3022; the 2 failures are pre-existing on main.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
hanzoai/ai replaced ~213 flat compound routes with one namespaced REST surface
generated from a single table, and DELETED the old ones. These are the console's
callers.
get-stores -> GET /v1/ai/stores
get-store -> GET /v1/ai/stores/{owner}/{name}
add-store -> POST /v1/ai/stores
update-store -> PATCH /v1/ai/stores/{owner}/{name}
delete-store -> DELETE /v1/ai/stores/{owner}/{name}
get-cloud-usages -> GET /v1/ai/usages/cloud
get-providers -> GET /v1/ai/providers
…
Applied fresh to main rather than rebased. The branch this was developed on is 843
commits behind, and replaying a stale UI diff across that much drift would have
been guesswork; the migration is small and mechanical, so it is re-derived against
what main actually calls today.
Two things beyond the renames.
The identity moved from a query param into the path, as TWO segments. Every object
is keyed by the pair (owner, name), so `?id=acme/my-store` becomes
`/ai/stores/acme/my-store` with each part encoded separately (`memberOf`). Encoding
the pair as ONE segment does not work — the server decodes %2F back into a
separator before routing, so it would never match. There is a test for exactly that.
Updates are PATCH and deletes are DELETE, so client.ts gains `patch`/`del` and the
`cloudPatch`/`cloudDelete` twins, mirroring the existing helpers.
CLOUD_HEADS drops eight individual ROUTES (get-stores, add-store, …) for one
SERVICE head: `ai`. That is what a head-based allow-list is supposed to mean; it
enumerated routes only because the surface had no namespace to enumerate.
That collapse would have quietly widened one thing, so it does not. The
cross-tenant store listing was explicitly refused before, and granting `ai` would
have admitted it — REFUSED_SUBPATHS keeps that one refusal, scoped to that path and
NOT a blanket rule over every `global` sub-path (the Providers board really does
read its cross-tenant catalog, so a blanket rule would break a live surface while
claiming to preserve a property that never covered it).
Left alone on purpose: projects.ts, team.ts and admin.ts go through iamList/iamOne,
which prefix `iam/` — those are the IAM service's own routes under its own naming.
Typecheck adds ZERO errors (29 before, 29 after — all pre-existing). 3021 tests
pass; the 3 failures are pre-existing on main (oss-apps, store/logic) or flaky
(invite AEAD, passes 5/5 in isolation).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
This job has been red on every push, with no steps and no log, because it never
got scheduled: it asks for a GitHub-hosted runner, this repo is private, and
private repos bill hosted minutes against a limit the org has reached. Public
repos are unaffected, which is why the identical workflow in hanzoai/world is
green — the difference is billing, not the file.
It is one 20-second curl. Our own pool runs it for nothing and sits inside the
network it is calling.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
npm could never run `npm ci` here. The Dockerfile said so in a comment: @hanzo/gui
pulls a react-native tree whose platform and optional packages resolve differently
between npm versions, so a lockfile written by one npm failed under another, and
the build ran `npm install` — resolving the tree fresh every time and using the
committed lockfile as a suggestion. A lockfile nobody installs from is decoration,
which is how it drifted far enough that `npm ci` was already dead on main before
this change (react-native-worklets missing from the tree it claimed to describe).
pnpm records every platform in the lockfile, so the build installs exactly what is
committed and fails loudly rather than quietly resolving something else. Both
Dockerfiles now `corepack enable && pnpm install --frozen-lockfile`, corepack takes
the version from `packageManager`, and package-lock.json is gone. .gitignore is
reversed accordingly: pnpm-lock.yaml is the tracked one and every other manager's
lockfile is ignored, so a stray `npm install` cannot leave a second source of truth.
pnpm-workspace.yaml carries the two settings this needs, both documented in place.
Install scripts are denied unless named, and esbuild and sharp are named because the
app does not build without them. The release-age gate is excluded by SCOPE for
@hanzo/* rather than by version, because pnpm rewrites a per-version entry on every
bump, and a file that rewrites itself during install makes --frozen-lockfile fail in
CI — the exact determinism this change exists to get.
Verified on pnpm 11.17.0: frozen-lockfile install clean, tsc 0 errors, 3056 tests
passing, `pnpm build` compiles, and `pnpm build:embed` emits the real bundle cloud
fail-hards on (367KB index.html, 5.5M _next). node_modules stays self-contained —
every symlink is relative into node_modules/.pnpm — so the runner stage's
COPY --from=build of node_modules still resolves.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
0.3.4 carries the product -> DSN registry, so `product: 'console'` resolves the
hanzo-console project with no env var and no build argument. This is the release
that actually makes console.hanzo.ai report errors.
Lockfile edited SURGICALLY (4 lines: the range, version, resolved, integrity).
Do NOT regenerate it here: both `npm install` and `npm install --package-lock-only`
drop the optional-peer block `node_modules/expo/node_modules/react-native-worklets`,
which `npm ci` then needs — that removal is what broke CI once already and had to be
restored by hand. npm ci verified green against this lockfile.
tsc clean; 3048 tests pass.
git.hanzo.ai mirrors this repo by PULL on a ~10-minute interval, and arcd runs
CI/CD there — so every push waited out that interval before anything built.
This asks Gitea to pull HEAD immediately.
Latency only: the repo already mirrors via the App webhook, so a missing
HANZO_GIT_TOKEN or a failed curl is non-fatal and never fails the push.
Idempotent (mirror-sync just pulls HEAD) and concurrency-coalesced.
Apps and command search are one surface now — the launcher was folded into the
palette and its component is gone. The prose did not follow: thirty-seven places
still listed "nav/launcher/palette" as three things to gate, and CommandPalette
still named a launcher hook among the chrome hooks it composes, which no longer
exists.
Read literally, those comments send someone looking for a second surface to keep
in sync with this one. There isn't a second surface; that was the point of the
change.
Comments only — every changed line is inside a comment, tsc is clean, the suite is
3056 passing, and next build compiles.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
npm ci refused to install at all:
npm error Missing: react-native-worklets@0.8.3 from lock file
expo depends on it, but the nested entry was absent from package-lock.json, so
the lockfile no longer described a complete tree and the reproducible-install
path was dead for everyone.
Image builds were unaffected, which is why this went unnoticed: the Dockerfile
runs npm install, which re-resolves and papers over the gap. Only npm ci — the
one command that installs exactly what is written down — could see it.
npm install writes back exactly the missing entry: 28 lines, one package added,
none removed, no version moved. npm ci now completes; tsc is clean, the suite is
3056 passing, and next build compiles.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The console reported ZERO errors. Two independent reasons, both silent:
1. @hanzo/event was pinned ^0.3.1 — the version with NO envelope code at
all. captureError() collected and dropped.
2. createAnalytics() was never passed a dsn. The error plane authenticates
independently of the event stream; with no dsn it is inert by design
(fail-safe), so even 0.3.3 would have stayed dark.
This file also asserted the failure into existence: it documented /v1/event as
being lensed server-side into 'error tracking'. There is no such fan-out. That
claim is why nobody looked. Corrected to state the two-plane reality and the
no-dsn => inert contract explicitly.
dsn comes from NEXT_PUBLIC_HANZO_EVENT_DSN, the convention hanzoai/app and
hanzoai/hanzo.ai already use. Publishable by design — it ships in the bundle.
Still dark until a DSN is set: NEXT_PUBLIC_HANZO_EVENT_DSN is set on zero CRs
fleet-wide, and no 'console' Sentry project exists yet
(/v1/sentry/console/envelope/ -> 404). This makes the surface correct so the
plane lights up on config alone, with no further code change.
tsc clean; 3048 tests pass.
Same drift as cloud and iam: git.hanzo.ai held 133 commits GitHub did not, so the
sync could never fast-forward. Merging the forge in from this side needs no forge
credentials and makes that push a fast-forward again.
Two files conflicted, and both resolve to GitHub's side because GitHub is the newer
one: parseBlueprint and fetchOssApps were lifted into @hanzo/ui/oss and are
re-exported from here, while the forge still carries the inline copies. Taking the
forge's would put a second implementation of the compose reader back in the tree.
The merge also brings the forge's "unify Apps and command search" refactor, which
deletes AppLauncher and folds it into CommandPalette. That deletion arrives with the
CommandPalette and dashboard changes that stop calling useAppLauncher, so nothing is
left dangling — the merged tree has no reference to it.
tsc reports the same 24 errors as clean main and vitest the same 3028 passing with
the same 2 files failing to collect; both are the stale local @hanzo/ui (8.0.8
installed, ^8.0.11 required, which is where the /oss subpath lives). The merge adds
nothing to either count.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Two comments described the admin o11y board's generation stats as Langfuse's.
The backend surface is renamed to o11y_ai (hanzoai/cloud), and Langfuse is a
product we do not run; naming our own lens after it makes a reader carry that
history for nothing.
Restores the App Store detail work (lost when main was reset past it) and, this
time, builds it on @hanzo/ui/oss instead of a local copy.
Clicking a card opened nothing; the only affordance was Deploy, so choosing what
to run in your own cloud was a decision made from a 300px tile. Cards now open
/store/:id, which answers what actually decides it — which containers start,
which images they pull, what ports they publish, what configuration they expect
— read from the blueprint's own docker-compose.yml, not restated from the tile.
Env KEYS only; the values are routinely secrets.
The catalog shape, normalizer, URL builders and compose reader no longer live
here. They are @hanzo/ui/oss (v8.0.11), shared with platform and the public
oss.hanzo.ai gallery — three copies of one format collapsed to one, verified
against the real corpus (400/400 blueprints parse, 812 services). This module
keeps only what is genuinely console-specific: claimPath, which names a console
route. The import paths are unchanged, so no call site moved.
The maker payout hook repeated on all ~1030 tiles; it now appears once in the
banner, plus on the detail page of an app you are actually looking at. Reworded
off "Built one of these?", which conceded we built none of it. Authors moves
Web3 → Dev: the audience is open-source developers, and a wallet is how the
payout arrives, not what the product is about.
package-lock.json is the tracked lockfile and the Dockerfile runs npm install,
so a pnpm or yarn lockfile left by a stray install is drift no one reads. Also
recovered from the rescue lineage, where it was written and never carried over.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The guide work — the pitch hero, the product guide panel, the signal/spec/
registry/guard layer under lib/guide, and the chat, suggest and budget surface
on GuideModule — was written on the local main that predates the history
rewrite. That lineage survives only as origin/rescue/console-local-main, which
shares no ancestor with main, so nothing carried it across: of its 127 commits,
patch-id comparison finds 9 with no equivalent here, and this module is what
they add.
Taken as content rather than merged, because a merge has no base to work from
and a whole-tree diff would drag main backwards: main is newer on @hanzo/ui,
@hanzogui/shell, the sidebar workspace layout, BrandLogo, OrgSwitcher and two
e2e specs the rescue lineage never had. Only the additive side is here.
The eleven new files are additions main has nowhere. The five touched files
take the rescue version whole after confirming each one's diff is additive —
api/guide.ts is +104/-0, and GuideModule and guide/logic.ts each report one
deletion that is an import line being extended. dashboard.tsx is the exception
and got the three guide hunks by hand, leaving main's SidebarWorkspace alone.
Left behind deliberately: the upstream-attribution removal in
products/registry.tsx. Dropping an attribution field documented as carrying
license compliance is a decision of its own, not something to fold into landing
a feature.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Two defects in the cloud console's chrome, both fixed in the SHARED control
(@hanzo/ui 8.0.11) so every surface inherits them, not just this one.
The top-left mark showed the house H whenever an org had set no logo — a
customer's console showing OUR brand. It now renders `OrgMark` unconditionally:
the org's own logo when IAM carries one, else the org's MONOGRAM, the treatment
the account widget already gives a person. Never the house glyph, never the org
name as running text.
The org switcher was a caption beside a control. Its trigger is now the peer of
the account row — 44px tall, a 30px mark, the same type, the same hit area — and
`SidebarWorkspace` is a COLUMN so it stretches the sidebar's width the way the
account row does (a row container had shrunk it to its text).
One org-identity source: `useOrgLogo` (a URL) becomes `useOrgIdentity` (name,
display name, logo — one cached read), fed to BOTH the mark and the switcher's
new `current` prop, so the two slots can never disagree and a user with no
cross-tenant list still gets their own logo. The dead `BrandLogo` component,
a second copy of the same logo-else-mark decision, is gone.
`e2e/org-identity.spec.ts` measures it off the rendered boxes: without the change
the mark paints an SVG with no monogram and the switcher has no trigger to find.
The datastore connect command is the one string on this page a user copies and
runs on their own machine, so it has to name a binary they can install. Upstream
clickhouse-client is installable and speaks the unchanged native protocol, so it
connects to a datastore instance as-is.
Our own datastore-client exists as a package definition (hanzoai/datastore
packages/datastore-client.yaml installs /usr/bin/datastore-client) but has no
serving repo: packages.hanzo.ai/{,deb/,rpm/stable/} all return 404. Renaming the
string today would print a command that cannot be installed.
The comment records the condition to flip it, so the next naming pass does not
change it blind.
Clicking a card opened nothing; the only affordance was Deploy, so choosing
what to run in your own cloud was a decision made from a 300px tile. Cards now
open /store/:id, which answers what actually decides it — which containers
start, which images they pull, what ports they publish, what configuration
they expect — read from the blueprint's own docker-compose.yml rather than
restated from the tile.
parseBlueprint is a small structural reader, not a YAML implementation: it
walks the services block by indentation and pulls only the four keys the page
shows. Pure and total, so it is unit-tested and safe on untrusted CDN content.
What it cannot read is absent, never guessed — a blueprint without compose says
so instead of rendering an empty table that implies nothing starts. Env KEYS
only; the values are frequently secrets.
The maker payout hook repeated on all ~1030 tiles. Saying it 1000 times is not
1000 times more persuasive, so it now lives once in the banner (plus the detail
page of an app you are actually looking at). Reworded off "Built one of these?",
which conceded we built none of it and framed our own store as other people's
work — the subject is the reader's project and what they earn from it.
Authors moves Web3 → Dev: the audience is open-source developers shipping code.
A wallet is how the payout arrives, not what the product is about; filing it
under Web3 hid it from everyone it is meant for.
The forge resolves `uses:` only under WORKFLOW_DIRS (.hanzo/workflows), so
pointing at hanzoai/ci/.github/workflows/build.yml@v1 failed outright:
path ".github/workflows/build.yml" must be under a configured workflow directory
This repo has built NOTHING since that took effect. hanzoai/ci now publishes the
reusable from .hanzo/workflows/build.yml and tags it v2; a new tag rather than a
force-moved v1, because moving a floating tag is what desynced that repo's two
heads earlier today.
The forge resolves `uses:` only under WORKFLOW_DIRS (.hanzo/workflows), so
pointing at hanzoai/ci/.github/workflows/build.yml@v1 failed outright:
path ".github/workflows/build.yml" must be under a configured workflow directory
This repo has built NOTHING since that took effect. hanzoai/ci now publishes the
reusable from .hanzo/workflows/build.yml and tags it v2; a new tag rather than a
force-moved v1, because moving a floating tag is what desynced that repo's two
heads earlier today.
Assisted-by: Claude:claude-opus-5
Three defects found by a rendered-DOM audit (CDP + hit-testing) of the live
cloud.hanzo.ai at 390x844 and 1440x900. Measured before AND after, per defect.
FOOTER legal links were CLIPPED off-screen at 390px. The link clusters are Views
(`flex-shrink: 0`), so they held max-content width and their own `flex-wrap` never
engaged: Terms painted at x 397->435 on a 390px viewport, while
`html,body{overflow-x:clip}` keeps `documentElement.scrollWidth` at 390 — the
overflow is CLIPPED, not scrollable, so a legally-required link could not be
reached by any gesture. `ConsoleFooter`'s `flexShrink` already fixes that in this
line; production is BEHIND it (live still renders the hero as a SPAN, so it
predates the same commit), so rather than re-fix it this locks the geometry: at
390 the row wraps to two lines, Terms lands at x 149->187, every link hit-tests
to itself, and nothing on the page is painted past the right edge.
HEADER chrome rendered in a SYSTEM font while the body rendered Geist.
`@hanzogui/shell` sets its own stack as an INLINE style on its root
(`fontFamily: CHROME.font` = `ui-sans-serif, system-ui, -apple-system, "Segoe UI",
…`, which names no Geist) and its subtree inherits it — its buttons re-declare
`font-family: inherit`. Live: wordmark `Noto Sans:11:SYSTEM`, nav
`Noto Sans:9:SYSTEM`, hero `Geist:26:custom` — mixed typography on one screen.
Geist loads fine (self-hosted woff2), so this is a CASCADE problem and the font
loading is untouched. One rule in globals.css pins `[data-hanzo-shell]` and its
descendants to `var(--font-sans)`; `!important` is required because nothing else
beats an inline declaration, and `code/pre/kbd/samp` keep the mono face so the two
font invariants stay orthogonal. After: nav `Geist:9:custom`, Meet-Hanzo
`Geist:10:custom`, CTA `Geist:7:custom` — the body's own face. Deleting ONLY that
rule from the CSSOM on the same build reverts the header to `Noto Sans:9:SYSTEM`
with the old stack, so the rule is demonstrably the fix, in isolation.
The desktop logged-out header carried TWO "Sign in" affordances. `HanzoHeader`
renders its OWN account link whenever `account` is nullish
(`account ?? <DefaultAccount/>`) and `landingSurface` already relabels the primary
CTA "Sign in", so live read `[Get API key] [Sign in -> /signin] [Sign in ->
href="#"]` — the duplicate was also a dead link. `PublicLanding` now declines the
control explicitly (`account={false}`: not nullish, so the default never renders,
and React draws nothing — including the mobile sheet's identity row).
Also: `@hanzogui/shell` was pinned `^7.6.4`, which is not published (latest is
7.6.3) — `npm install`, which the Dockerfile runs, fails ETARGET on it, so no
image could build. Relaxed to `^7.6.3`, which still admits 7.6.4 the moment it
publishes; this tree compiles and passes against 7.6.3.
Verification: `next build` ✓ ("Compiled successfully", types + 20/20 static
pages); `tsc --noEmit` clean; `vitest` 3024/3024; `e2e/landing-chrome` 3/3 against
the PRODUCTION build on `next start`. Font evidence is CDP
`CSS.getPlatformFontsForNode` (real family + custom-vs-system) — never
`document.fonts.check()`, which answers true on a page with zero @font-face rules.
The fork moved its API off /api to /v1, so every call built against
${{ github.server_url }}/api/v1/... now 404s. Verified live with a control:
/v1/version 200, /api/v1/version 404, a nonsense path 404.
This is the build-dispatch in sync-from-github, so a fast-forward from GitHub
was landing commits and then silently failing to trigger the build.
The Dockerfile runs `npm install` and package-lock.json is the tracked
lockfile, but a stray pnpm-lock.yaml showed up untracked and unignored — a
second lockfile that drifts from the real one and keeps polluting git status.
Brings the Guide chat, next-quest suggestions and live budget surface into the
product module, and restores the type-check that the product guide panel broke.
The panel was rendered from the Dashboard shell with a pathname the shell no
longer holds, so the app did not type-check. It now reads the route in a leaf of
its own, the way the breadcrumb bar does, which keeps the shell inert across
navigation.
Takes the monochrome sweep, the design-token sheets and the self-hosted
typeface from main, and adopts them in the new surface: the budget, chat
and suggestion UI now reads its icon weights from the tone map instead of
the chromatic hexes it was written with, so the Guide matches the rest of
the console chrome.
OSS attribution belongs in the repo LICENSE and NOTICE, not the console UI,
so the overview spec no longer synthesizes an Upstream fact, the interstitial
no longer prints a forked-from line, and ProductUpstreamNote is removed.
Upstream stays catalog metadata.
Moves usePathname out of the Dashboard shell into a BreadcrumbsBar leaf, so a
navigation click re-renders the swapped page and the breadcrumb strip rather
than the whole shell.
Adds the suggest, chat and funnel wire types plus their normalizers to the
guide API client, the usd / automatableSuggestions / topSuggestion helpers
to the pure logic module, and the chat + next-quest UI to GuideModule.
Suggestions carry an automatable flag, so the module offers a run action on
exactly the quests the Business AI can execute.
Owner direction: "better pitch, not upstream attribution."
1) Remove the in-product OSS fork attribution. Delete ProductUpstreamNote
(rendered "Built on open source — forked from X (MIT)" under every product)
and every other surface that showed a "forked from … (license)" line:
- ProductUpstreamNote.tsx + its DashboardShell mount (replaced by the guide panel)
- ProductInterstitial's "Forked from X (license)." clause
- the "Upstream" key-fact injected by overview/resolve.ts
- the now-dead `upstream` catalog field + its 11 declarations in registry.tsx
OSS license compliance stays in each repo's NOTICE/LICENSE — this is UI only.
2) Native, dynamic, personalized pitch + getting-started guides + tours. One
subsystem, extending the existing OnboardingGate/OnboardingWizard, the
first-run GuidedTour, and LivingOverview (no 3rd-party like Appcues):
- src/lib/guide/: signals (real per-user facts: role, has-API-key, in-console
usage), spec (pitch + dynamic getting-started steps whose done-state reads a
REAL signal — never fabricated; unknown ⟹ not done), guard (per-product
dismissal), registry (curated pitches for the flagship products).
- src/components/guide/PitchHero + ProductGuidePanel: headline + value props
above a getting-started checklist that checks itself off, personalizes which
steps show (when-predicates), auto-hides once done/dismissed, and launches a
spotlight tour generated from the INCOMPLETE steps (reuses GuidedTour; zero
external scripts; works in the go:embed console under any CSP).
- Mounted once at the top of the console content column (DashboardShell) for
every product landing + the console home (replacing the standalone
GetApiKeyCta). FirstRunTour now personalizes CONSOLE_TOUR via resolveTour.
- Honest, accessible (@hanzo/gui v5 shorthands, reduced-motion-safe via FadeIn),
org/identity-scoped, skipped on the admin/operator host.
Tests: +25 vitest (signals/spec/guard/registry). tsc clean, vitest 2876 pass,
next build green.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The previous note guessed "~3 runs each (~1400 total)". Parsing on.push.tags
out of every workflow in every reachable tag tree gives the real shape over
646 tags (the forge holds 692): pipeline.yml 559, release.yml 547,
codespell.yml 263, build-image.yml 36, build-and-push.yml 21, cicd.yml 3 =
1429 runs, distributed 0:48 1:51 2:284 3:242 4:21 — so 2-3 per tag, not 3.
Also names the full set. The incident was reported as three workflows;
build-image.yml and build-and-push.yml are in those trees too, and a reader
scoping only the named three would still be surprised by 57 more runs.
Two comments in .hanzo/workflows were false or missing, and both misled a
diagnosis of the ~707-run flood that starved the shared runner queue.
sync-from-github.yml said it was "inert until hanzoai/console stops being a
Gitea pull mirror". That conversion happened — the forge reports mirror: false,
has_actions: true — so the cron is live and fast-forwarding main every 10
minutes. It moves refs/heads/main and nothing else; say so, because "never
tags" is what keeps it from replaying the flood.
cicd.yml kept tags: ['v*'] but never said why a bulk tag push is different
from a hand-cut one. The forge resolves workflows from the PUSHED REF's own
tree (WORKFLOW_DIRS = .hanzo,.github,.gitea), and this repo's history is a
minio/console fork whose old trees still carry .github/workflows/{release,
pipeline,codespell}.yml. Replaying the ~692 tags enqueues ~3 runs each. No
edit on main can prevent that — main's tree is not consulted for a tag push —
so the note gives the only lever that works: close has_actions first, push,
reopen. Tags already present never re-fire.
No trigger changed: cicd.yml still builds main, PRs and hand-cut v* tags.
With the paywall on, a gated route answers 402
{"error":"subscription_required"}. The console turned that into "Add credits"
and a button to /billing/credits — the wrong ask twice over. Credits do not
satisfy the paywall, so the next request 402s again and the user loops; and the
page that would actually fix it is never offered.
Two causes, both fixed:
The reason was thrown away before anyone could classify it. Both API clients
read only `msg` (the casibase envelope) and `message`/`msg` (Base), while the
plain-REST /v1 surfaces answer with `error`. So the message became "Request
failed (HTTP 402)" and the only signal left was the status — which the
classifier could read only as an unfunded balance.
And 402 was treated as one condition when it is two: no PLAN (subscribe) and no
BALANCE (top up). honestError now splits them on the machine-readable token, not
on prose, and ErrorState offers "See plans" -> /plans for the first while the
existing "Add credits" -> /billing/credits stays for the second.
Tests assert both branches and that a planless org is never offered credits.
Verified they catch the bug: against the previous classifier the two new
assertions fail and the four existing ones still pass. tsc clean; 1211 tests
across 96 files pass.
With the paywall on, a gated route answers 402
{"error":"subscription_required"}. The console turned that into "Add credits"
and a button to /billing/credits — the wrong ask twice over. Credits do not
satisfy the paywall, so the next request 402s again and the user loops; and the
page that would actually fix it is never offered.
Two causes, both fixed:
The reason was thrown away before anyone could classify it. Both API clients
read only `msg` (the casibase envelope) and `message`/`msg` (Base), while the
plain-REST /v1 surfaces answer with `error`. So the message became "Request
failed (HTTP 402)" and the only signal left was the status — which the
classifier could read only as an unfunded balance.
And 402 was treated as one condition when it is two: no PLAN (subscribe) and no
BALANCE (top up). honestError now splits them on the machine-readable token, not
on prose, and ErrorState offers "See plans" -> /plans for the first while the
existing "Add credits" -> /billing/credits stays for the second.
Tests assert both branches and that a planless org is never offered credits.
Verified they catch the bug: against the previous classifier the two new
assertions fail and the four existing ones still pass. tsc clean; 1211 tests
across 96 files pass.
Salvaged isolated fix — the Square card rendered an off-brand white box on the
dark console; use-square-card.ts styles the iframe (near-black field, legible
text, focus/error tones) and BillingCredits uses PrimaryButton (drops theme=light).
Salvaged isolated fix — the Square card rendered an off-brand white box on the
dark console; use-square-card.ts styles the iframe (near-black field, legible
text, focus/error tones) and BillingCredits uses PrimaryButton (drops theme=light).
Two places still drew the Hanzo mark on non-Hanzo hosts, breaking the
white-label invariant this codebase states in several comments ("a lux/zoo/
pars host NEVER renders the Hanzo mark").
Loader.tsx's BrandMark upgrades to the brand's animated SVG on mount, but its
static branch hardcoded Hanzo's five-path H with aria-label="Hanzo". That
branch is not just first paint: ANIMATED covers hanzo/lux/zoo only, so a pars
host never leaves it and showed the Hanzo mark PERMANENTLY, labelled "Hanzo",
beside Pars text. It now reads the mark from the shared @hanzo/brand registry
— which already carries one per brand, PARS_MARK included — using exactly the
fields BrandLogo's BrandMark reads. One source, not a copy. The local
MARK_PATHS copy of Hanzo's geometry is deleted with its last use.
OnboardingWizard imported the genuinely hardcoded ui/HanzoMark and rendered it
directly beside "Set up {config.brandName}" — the wrong mark next to the right
name on every lux/zoo/pars host. Swapped to the host-derived BrandMark that
SidebarBrand already uses.
Found while investigating why kms.pars.network serves Hanzo branding. That
host has a separate edge-level cause still open; this is the code half, and it
also fixes the Pars mark everywhere else in the console.
Two places still drew the Hanzo mark on non-Hanzo hosts, breaking the
white-label invariant this codebase states in several comments ("a lux/zoo/
pars host NEVER renders the Hanzo mark").
Loader.tsx's BrandMark upgrades to the brand's animated SVG on mount, but its
static branch hardcoded Hanzo's five-path H with aria-label="Hanzo". That
branch is not just first paint: ANIMATED covers hanzo/lux/zoo only, so a pars
host never leaves it and showed the Hanzo mark PERMANENTLY, labelled "Hanzo",
beside Pars text. It now reads the mark from the shared @hanzo/brand registry
— which already carries one per brand, PARS_MARK included — using exactly the
fields BrandLogo's BrandMark reads. One source, not a copy. The local
MARK_PATHS copy of Hanzo's geometry is deleted with its last use.
OnboardingWizard imported the genuinely hardcoded ui/HanzoMark and rendered it
directly beside "Set up {config.brandName}" — the wrong mark next to the right
name on every lux/zoo/pars host. Swapped to the host-derived BrandMark that
SidebarBrand already uses.
Found while investigating why kms.pars.network serves Hanzo branding. That
host has a separate edge-level cause still open; this is the code half, and it
also fixes the Pars mark everywhere else in the console.
Measured on cloud.hanzo.ai / console.hanzo.ai in a real browser.
The hero "Get started" computed to rgb(36,36,36) on rgb(204,204,204) -- dark
grey on black, LESS visual weight than the nav's white Sign in pill, so the
page's own primary action read as disabled. Beside it "Learn more" was
`chromeless`: no edge at all, not legibly a button. Both are now the house pill
pair -- white primary with dark text, hairline-bordered secondary, both
rounded-full. Measured after: rgb(242,242,242)/rgb(5,5,5) and a
1px rgb(56,56,56) border, radius 999px.
"The AI cloud, one platform" was a styled span; the primary product page had NO
h1 at all. It renders `h1` now -- same classes, byte-identical typography.
The footer's link clusters are Views, which are `flex-shrink: 0`, so they held
max-content width and their `flex-wrap` never engaged: at 390px "Terms" sat at
x 390->426 while documentElement clipped at 390, i.e. a legally-required link
that could not be scrolled to. They shrink now: body.scrollWidth 426 -> 390,
Terms lands at x 147. Those links were also the only underlined links on any
Hanzo surface -- now consistent.
Measured on cloud.hanzo.ai / console.hanzo.ai in a real browser.
The hero "Get started" computed to rgb(36,36,36) on rgb(204,204,204) -- dark
grey on black, LESS visual weight than the nav's white Sign in pill, so the
page's own primary action read as disabled. Beside it "Learn more" was
`chromeless`: no edge at all, not legibly a button. Both are now the house pill
pair -- white primary with dark text, hairline-bordered secondary, both
rounded-full. Measured after: rgb(242,242,242)/rgb(5,5,5) and a
1px rgb(56,56,56) border, radius 999px.
"The AI cloud, one platform" was a styled span; the primary product page had NO
h1 at all. It renders `h1` now -- same classes, byte-identical typography.
The footer's link clusters are Views, which are `flex-shrink: 0`, so they held
max-content width and their `flex-wrap` never engaged: at 390px "Terms" sat at
x 390->426 while documentElement clipped at 390, i.e. a legally-required link
that could not be scrolled to. They shrink now: body.scrollWidth 426 -> 390,
Terms lands at x 147. Those links were also the only underlined links on any
Hanzo surface -- now consistent.
A single GitHub ORG-level push webhook now posts to git.hanzo.ai/v1/sync for every
repo in the org (verified: real pushes to universe + gateway synced their mirrors
instantly), so a per-repo nudge is redundant.
It was also mostly theatre: HANZO_GIT_TOKEN exists on exactly ONE repo in the org
(hanzoai/app) and is not an org secret, so in every other repo this workflow hit its
fail-soft branch and did nothing while still reporting success.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
A single GitHub ORG-level push webhook now posts to git.hanzo.ai/v1/sync for every
repo in the org (verified: real pushes to universe + gateway synced their mirrors
instantly), so a per-repo nudge is redundant.
It was also mostly theatre: HANZO_GIT_TOKEN exists on exactly ONE repo in the org
(hanzoai/app) and is not an org secret, so in every other repo this workflow hit its
fail-soft branch and did nothing while still reporting success.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
.github/workflows now holds exactly one file: the sync nudge, which runs zero
CI. cicd.yml moved to .hanzo/workflows unchanged — it is a 7-line caller over
hanzo.yml, so no build logic moved with it, and hanzo.yml still declares BOTH
console images.
.hanzo/workflows/deploy.yml is deleted, not merged. It hand-built the server
image a SECOND time (hanzo.yml already declares it) and could not have built it
at all: `buildctl-daemonless.sh` is absent from the image this fleet serves for
`hanzo-build-linux-amd64` — every label in that pool maps to
catthehacker/ubuntu:act-24.04 (universe:infra/k8s/git-runner/statefulset.yaml) —
and its `secrets.GIT_CLONE_TOKEN` exists on neither the repo nor the org. Its
`kubectl patch app` was futile too: cd.hanzo.ai's selfHeal restores the CR from
the universe pin on the next poll. Rollout stays a reviewed tag pin in
hanzoai/universe.
sync.yml's "why this repo is not yet single-file" note is replaced by what the
blocker actually was, since it is the thing that must be flipped for this to be
live: hanzoai/console has the forge Actions UNIT disabled (`has_actions: false`,
zero runs ever). Enabling the unit is the whole unblock — a pull-mirror sync DOES
fire Actions (hanzoai/git: services/mirror/mirror_pull.go calls
notify_service.SyncPushCommits; services/actions/notifier.go turns that into a
run) — so converting the mirror to canonical is a separate question about who
owns main, not a precondition for CI.
The cost of getting that order wrong is already on the record here: build-image.yml
was neutralized in favour of a native pipeline that could not run, and v8.5.23 /
8.5.24 shipped no image at all.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
.github/workflows now holds exactly one file: the sync nudge, which runs zero
CI. cicd.yml moved to .hanzo/workflows unchanged — it is a 7-line caller over
hanzo.yml, so no build logic moved with it, and hanzo.yml still declares BOTH
console images.
.hanzo/workflows/deploy.yml is deleted, not merged. It hand-built the server
image a SECOND time (hanzo.yml already declares it) and could not have built it
at all: `buildctl-daemonless.sh` is absent from the image this fleet serves for
`hanzo-build-linux-amd64` — every label in that pool maps to
catthehacker/ubuntu:act-24.04 (universe:infra/k8s/git-runner/statefulset.yaml) —
and its `secrets.GIT_CLONE_TOKEN` exists on neither the repo nor the org. Its
`kubectl patch app` was futile too: cd.hanzo.ai's selfHeal restores the CR from
the universe pin on the next poll. Rollout stays a reviewed tag pin in
hanzoai/universe.
sync.yml's "why this repo is not yet single-file" note is replaced by what the
blocker actually was, since it is the thing that must be flipped for this to be
live: hanzoai/console has the forge Actions UNIT disabled (`has_actions: false`,
zero runs ever). Enabling the unit is the whole unblock — a pull-mirror sync DOES
fire Actions (hanzoai/git: services/mirror/mirror_pull.go calls
notify_service.SyncPushCommits; services/actions/notifier.go turns that into a
run) — so converting the mirror to canonical is a separate question about who
owns main, not a precondition for CI.
The cost of getting that order wrong is already on the record here: build-image.yml
was neutralized in favour of a native pipeline that could not run, and v8.5.23 /
8.5.24 shipped no image at all.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The console's `/paas` BFF forwarded to `platform.hanzo.ai/v1/paas/*`. That host
has no such route: the platform Next app's own surface is /v1/apps, /v1/runner,
/v1/git-webhook … and it answers 401 uniformly for EVERY /v1/* path, nonsense
included — so the failure was invisible and the PaaS board could never load.
The PaaS control plane is `/v1/paas/*` on the unified backend:
api.hanzo.ai/v1/paas/health 200 {"crd":true,"k8s":true,"service":"paas"}
api.hanzo.ai/v1/paas/apps 403 (auth required)
api.hanzo.ai/v1/paas/zzz 404 <- a real routing table
platform.hanzo.ai/v1/paas/health 401
platform.hanzo.ai/v1/zzz-nonsense 401 <- auth-first catch-all
So the proxy now reads `CLOUD_API_URL` — the SAME server-side base every other
console BFF route already uses (in-cluster in prod, api.hanzo.ai everywhere
else). It no longer reads PLATFORM_URL, so the stale deploy-time override
pointing at platform.hanzo.ai is inert rather than silently authoritative.
Also repointed the remaining per-service API hosts to the ONE endpoint:
- resource `provisionSnippet` emitted `curl -X POST cloud.hanzo.ai/v1/<kind>`;
a copied snippet now targets api.hanzo.ai (verified routed: /v1/kv → 403
"X-Org-Id required").
- SearchModule's SSR origin fallback, .env.example, README, and the api/train/
tenants/platform-apps doc comments (`api.cloud.hanzo.ai`, `platform.hanzo.ai/v1/*`).
NEXT_PUBLIC_PLATFORM_URL stays: it is a FRONTEND deep-link host, not an API base.
Verified: pnpm typecheck clean; vitest 242 files / 3013 tests pass.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The console's `/paas` BFF forwarded to `platform.hanzo.ai/v1/paas/*`. That host
has no such route: the platform Next app's own surface is /v1/apps, /v1/runner,
/v1/git-webhook … and it answers 401 uniformly for EVERY /v1/* path, nonsense
included — so the failure was invisible and the PaaS board could never load.
The PaaS control plane is `/v1/paas/*` on the unified backend:
api.hanzo.ai/v1/paas/health 200 {"crd":true,"k8s":true,"service":"paas"}
api.hanzo.ai/v1/paas/apps 403 (auth required)
api.hanzo.ai/v1/paas/zzz 404 <- a real routing table
platform.hanzo.ai/v1/paas/health 401
platform.hanzo.ai/v1/zzz-nonsense 401 <- auth-first catch-all
So the proxy now reads `CLOUD_API_URL` — the SAME server-side base every other
console BFF route already uses (in-cluster in prod, api.hanzo.ai everywhere
else). It no longer reads PLATFORM_URL, so the stale deploy-time override
pointing at platform.hanzo.ai is inert rather than silently authoritative.
Also repointed the remaining per-service API hosts to the ONE endpoint:
- resource `provisionSnippet` emitted `curl -X POST cloud.hanzo.ai/v1/<kind>`;
a copied snippet now targets api.hanzo.ai (verified routed: /v1/kv → 403
"X-Org-Id required").
- SearchModule's SSR origin fallback, .env.example, README, and the api/train/
tenants/platform-apps doc comments (`api.cloud.hanzo.ai`, `platform.hanzo.ai/v1/*`).
NEXT_PUBLIC_PLATFORM_URL stays: it is a FRONTEND deep-link host, not an API base.
Verified: pnpm typecheck clean; vitest 242 files / 3013 tests pass.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
LUX_QUERIES described the fleet only in relative terms — who is up, who is at what
height, who has peers. A fleet that has STOPPED satisfies every one of them: same
height, same hash, five up, four peers each. The Lux board therefore rendered a
full row of green over a chain that had not produced a block in two days.
Adds the twins of the four absolute cloud allowlist entries — tip age (measured
against our own clock, so it climbs while the chain sits still), height spread,
distinct-hash count at one height, and the number of validators reporting Ready
while their RPC is dead — plus the live firing alert set.
The alert set comes from vmalert's own remote-written state rather than being
re-derived in the UI, so the board cannot quietly disagree with what is actually
paging, and it arrives over the VM proxy that already exists instead of a second
data path.
Byte-for-byte drift guard extended to all five; 10/10 tests pass.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
LUX_QUERIES described the fleet only in relative terms — who is up, who is at what
height, who has peers. A fleet that has STOPPED satisfies every one of them: same
height, same hash, five up, four peers each. The Lux board therefore rendered a
full row of green over a chain that had not produced a block in two days.
Adds the twins of the four absolute cloud allowlist entries — tip age (measured
against our own clock, so it climbs while the chain sits still), height spread,
distinct-hash count at one height, and the number of validators reporting Ready
while their RPC is dead — plus the live firing alert set.
The alert set comes from vmalert's own remote-written state rather than being
re-derived in the UI, so the board cannot quietly disagree with what is actually
paging, and it arrives over the VM proxy that already exists instead of a second
data path.
Byte-for-byte drift guard extended to all five; 10/10 tests pass.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Every rule in the app asks for Geist. On live console.hanzo.ai `document.fonts.size`
was **0**: the two `@import url('https://cdn.jsdelivr.net/npm/geist@1.3.1/…')` were
refused by the browser as cross-origin (ERR_BLOCKED_BY_ORB), so every customer read
the entire product in system-ui. The import ORDER was already fixed once for this
same symptom — the remaining cause was the CDN itself, which is a dependency we do
not control sitting on our own critical render path.
Now served from public/fonts. One VARIABLE file per family spans weights 100-900, so
eighteen static cuts collapse to two requests (56K + 58K) and any weight the design
reaches for already exists — no second place to add a face.
Verified on the real `build:embed` export, not asserted: fonts 0 -> 2,
"Geist 100 900: loaded", document.fonts.check('16px Geist') true, woff2 served 200.
(Geist Mono reports unloaded on the landing page because nothing there sets mono —
correct lazy behaviour.)
Every rule in the app asks for Geist. On live console.hanzo.ai `document.fonts.size`
was **0**: the two `@import url('https://cdn.jsdelivr.net/npm/geist@1.3.1/…')` were
refused by the browser as cross-origin (ERR_BLOCKED_BY_ORB), so every customer read
the entire product in system-ui. The import ORDER was already fixed once for this
same symptom — the remaining cause was the CDN itself, which is a dependency we do
not control sitting on our own critical render path.
Now served from public/fonts. One VARIABLE file per family spans weights 100-900, so
eighteen static cuts collapse to two requests (56K + 58K) and any weight the design
reaches for already exists — no second place to add a face.
Verified on the real `build:embed` export, not asserted: fonts 0 -> 2,
"Geist 100 900: loaded", document.fonts.check('16px Geist') true, woff2 served 200.
(Geist Mono reports unloaded on the landing page because nothing there sets mono —
correct lazy behaviour.)
The heading directly above it already reads `config.brandName`, resolved from the host,
so the same screen said "Lux Cloud" and then offered "Log in with Hanzo" — a white-label
leak on every non-Hanzo console (lux.id, zoolabs.id, pars). The button now reads the
same value the heading does: one brand fact, one source, no second place to drift.
Rescued from feat/hanzo-appbar, which is otherwise superseded — its app-switcher landed
on main long ago and it carried a /zach personal page that is not a product surface.
Branch deleted; this was the only unmerged value on it.
The heading directly above it already reads `config.brandName`, resolved from the host,
so the same screen said "Lux Cloud" and then offered "Log in with Hanzo" — a white-label
leak on every non-Hanzo console (lux.id, zoolabs.id, pars). The button now reads the
same value the heading does: one brand fact, one source, no second place to drift.
Rescued from feat/hanzo-appbar, which is otherwise superseded — its app-switcher landed
on main long ago and it carried a /zach personal page that is not a product surface.
Branch deleted; this was the only unmerged value on it.
The first Sync to Hanzo Git run failed before executing a step: "The job was
not started because recent account payments have failed or your spending limit
needs to be increased." GitHub-hosted minutes are refused for this org, so a
nudge on ubuntu-latest is a coin flip on an invoice. Our ARC pool is free,
in-cluster, and demonstrably running this org's CI right now — and the nudge is
one bounded curl.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The first Sync to Hanzo Git run failed before executing a step: "The job was
not started because recent account payments have failed or your spending limit
needs to be increased." GitHub-hosted minutes are refused for this org, so a
nudge on ubuntu-latest is a coin flip on an invoice. Our ARC pool is free,
in-cluster, and demonstrably running this org's CI right now — and the nudge is
one bounded curl.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
console's Next.js server image (admin.hanzo.ai, operator CR crs/console.yaml)
has not been built since 2026-07-24, when build-image.yml was neutralized in
favour of a native pipeline that cannot execute: measured against the live
forge, hanzoai/console is a Gitea PULL MIRROR with Actions DISABLED
(`mirror: true`, `has_actions: false`, zero runs ever). Two releases shipped no
image — v8.5.23 and the current 8.5.24 — while the CR still pins v8.5.22.
hanzo.yml declares BOTH images now (console-embed + console), so
the ONE config drives whichever runner executes it. The
SOURCE_COMMIT build arg is not carried over: it defaults
to "" in the Dockerfile and no source reads it.
cicd.yml + `tags: ['v*']` — a hand-cut tag must produce its image
or it is a receipt for nothing, the precise drift the
retired workflow existed to prevent.
sync.yml new: nudge git.hanzo.ai, and state the blocker where the
next agent will look before "fixing" the law violation.
.hanzo/…/sync-from-github.yml new: the 10-min fast-forward, inert until the
forge copy stops being a mirror.
build-image.yml DELETED — it had been reduced to echoing a sentence.
deploy.yml runs-on → hanzo-build-linux-amd64, the label the runners
demonstrably answer to (same fix hanzoai/cloud took).
Tag shape changes with the builder, deliberately: the shared builder publishes
`sha-<sha7>-amd64` per main push plus the bare semver on a v* tag, not the
`:v<X.Y.Z>` receipt. Pin the CR to the sha tag — that is what hanzoai/cloud
does, and an immutable content tag cannot be re-pushed to different bytes the
way `:v8.4.118` once was.
cicd.yml stays on GitHub until the forge copy is converted (one act, no code
change: hanzoai/.github scripts/forge-migrate.sh convert --repo
hanzoai/console). It is a 7-line caller over hanzo.yml, so that move is a file
rename and nothing else.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
console's Next.js server image (admin.hanzo.ai, operator CR crs/console.yaml)
has not been built since 2026-07-24, when build-image.yml was neutralized in
favour of a native pipeline that cannot execute: measured against the live
forge, hanzoai/console is a Gitea PULL MIRROR with Actions DISABLED
(`mirror: true`, `has_actions: false`, zero runs ever). Two releases shipped no
image — v8.5.23 and the current 8.5.24 — while the CR still pins v8.5.22.
hanzo.yml declares BOTH images now (console-embed + console), so
the ONE config drives whichever runner executes it. The
SOURCE_COMMIT build arg is not carried over: it defaults
to "" in the Dockerfile and no source reads it.
cicd.yml + `tags: ['v*']` — a hand-cut tag must produce its image
or it is a receipt for nothing, the precise drift the
retired workflow existed to prevent.
sync.yml new: nudge git.hanzo.ai, and state the blocker where the
next agent will look before "fixing" the law violation.
.hanzo/…/sync-from-github.yml new: the 10-min fast-forward, inert until the
forge copy stops being a mirror.
build-image.yml DELETED — it had been reduced to echoing a sentence.
deploy.yml runs-on → hanzo-build-linux-amd64, the label the runners
demonstrably answer to (same fix hanzoai/cloud took).
Tag shape changes with the builder, deliberately: the shared builder publishes
`sha-<sha7>-amd64` per main push plus the bare semver on a v* tag, not the
`:v<X.Y.Z>` receipt. Pin the CR to the sha tag — that is what hanzoai/cloud
does, and an immutable content tag cannot be re-pushed to different bytes the
way `:v8.4.118` once was.
cicd.yml stays on GitHub until the forge copy is converted (one act, no code
change: hanzoai/.github scripts/forge-migrate.sh convert --repo
hanzoai/console). It is a 7-line caller over hanzo.yml, so that move is a file
rename and nothing else.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
LIVE BUG, found by rendering the production landing at 390px: the hero headline
wraps to two lines on a phone and the lines OVERPRINTED each other — the front
door of console.hanzo.ai, unreadable on mobile. Desktop was fine (one line), which
is exactly why it survived: it is invisible until the text wraps.
Cause: a Gui font-size token ships a line-height tuned for ONE line. Nothing set a
line-height for the wrapped case, so the line boxes collided.
The fix must live in CSS, not a style prop. React Native Web reads a bare numeric
`lineHeight` in a style object as PIXELS — I tried `lineHeight: 1.1` there first
and it made the crush WORSE (1.1px leading), which is the tell. Unitless in real
CSS is relative to the element's own font-size, so ONE rule holds at $11 and $13
and every breakpoint: `.hz-display` in globals.css, worn via className (which
forwards to the DOM node on web) — the same mechanism as .hz-mono/.hz-tnum.
Verified by RENDERING, not by reading: 390/768/1280/1680 all pass with no
horizontal overflow, and the mobile screenshot shows 'The AI cloud, / one platform'
cleanly on two lines. tsc 0 errors; build:embed green. → v8.5.24
LIVE BUG, found by rendering the production landing at 390px: the hero headline
wraps to two lines on a phone and the lines OVERPRINTED each other — the front
door of console.hanzo.ai, unreadable on mobile. Desktop was fine (one line), which
is exactly why it survived: it is invisible until the text wraps.
Cause: a Gui font-size token ships a line-height tuned for ONE line. Nothing set a
line-height for the wrapped case, so the line boxes collided.
The fix must live in CSS, not a style prop. React Native Web reads a bare numeric
`lineHeight` in a style object as PIXELS — I tried `lineHeight: 1.1` there first
and it made the crush WORSE (1.1px leading), which is the tell. Unitless in real
CSS is relative to the element's own font-size, so ONE rule holds at $11 and $13
and every breakpoint: `.hz-display` in globals.css, worn via className (which
forwards to the DOM node on web) — the same mechanism as .hz-mono/.hz-tnum.
Verified by RENDERING, not by reading: 390/768/1280/1680 all pass with no
horizontal overflow, and the mobile screenshot shows 'The AI cloud, / one platform'
cleanly on two lines. tsc 0 errors; build:embed green. → v8.5.24
Cuts the semver for the waves already on main:
- chrome: white-label org logo, floating chat circle -> topbar brand-H + voice mic
opening the right sidebar, freely resizable Developers dock, live Create-key
- fix: the landing's 'Open Console' was a self-link (read as 'login is broken');
both header CTAs now resolve to the one sign-in surface (landing-surface.ts)
- monochrome: one semantic map (ui/tone.ts) across 3 passes; 15+ per-module colour
ladders deleted; categorical scale split out (lib/theme/ramp.ts); vendor brand
identity deliberately preserved. Exposed + fixed two real bugs: health identified
by colour equality (degraded counted as healthy) and drifted vendor hues.
- proof: voice unit tests, chrome render spec, landing-surface + tone contracts.
tsc 0 errors; vitest 3013 passed / 8 skipped; build:embed green.
Cuts the semver for the waves already on main:
- chrome: white-label org logo, floating chat circle -> topbar brand-H + voice mic
opening the right sidebar, freely resizable Developers dock, live Create-key
- fix: the landing's 'Open Console' was a self-link (read as 'login is broken');
both header CTAs now resolve to the one sign-in surface (landing-surface.ts)
- monochrome: one semantic map (ui/tone.ts) across 3 passes; 15+ per-module colour
ladders deleted; categorical scale split out (lib/theme/ramp.ts); vendor brand
identity deliberately preserved. Exposed + fixed two real bugs: health identified
by colour equality (degraded counted as healthy) and drifted vendor hues.
- proof: voice unit tests, chrome render spec, landing-surface + tone contracts.
tsc 0 errors; vitest 3013 passed / 8 skipped; build:embed green.
Third and final pass. The chrome now expresses state by WEIGHT, ICON and LABEL;
hue is reserved for the one thing it legitimately carries — a third party's own
identity.
ONE MODULE (job 1). `tone-var.ts` was a second place to look for one idea, so
`toneVar` folds into `tone.ts` beside the ladder it is derived from — change the
emphasis order once and both the `$colorN` token and the `var(--colorN)` CSS form
move together. 37 importers repointed; `tone.ts` stays pure and node-testable.
`statusVar` had zero callers and is deleted rather than carried.
ONE CATEGORICAL SCALE. `tone` answers "what does this STATE mean"; a donut slice,
a graph node kind and a funding class ask a different question — "how do I tell N
categories apart". That scale already existed as `Charts.CHART_PALETTE` but lived
inside a React component, so `provider-billing.ts` had hand-copied four of its
steps and `graph-logic.ts` had invented a hue ladder of its own. Extracted to the
pure `lib/theme/ramp` (`RAMP`/`OTHER`) and shared: one scale, no copies, and a
canvas or SVG mark can reach it without importing React.
THE REMAINING HUES (job 2). ~30 chromatic hexes plus the rgba() and vendor-colour
duplicates the hex grep missed, across 91 files: greens → positive, reds →
critical, ambers → warning, blues/cyans → neutral, slate → muted. Every local
ladder is deleted and repointed (agents STATUS_HEX, machines STATUS_HEX, code
TIER_HEX, railway GREEN/RED, knowledge NODE/EDGE_COLORS, growth STAGE_META). Every
icon and label is kept — in monochrome they are what carries the meaning, which is
also why the Cloudflare orange could go: a Cloud glyph beside the word "Cloudflare"
was never relying on the hue.
Two fixes fall out of the sweep rather than being bolted on: a white glyph on a
user-chosen accent now asks `contrastText` instead of assuming white, and the
select chevron — byte-identical in two files — becomes one asset.
VENDOR IDENTITY PRESERVED. `brand-marks`/`brand`/`ProviderLogo` are untouched:
Anthropic coral, Qwen violet, NVIDIA green are those vendors' marks, not our
chrome. `ai-accounts` had re-declared two of them by hand and drifted (its OpenAI
green vs the brand map's black), so it now RESOLVES through the same
`brandForModel` the avatars use — identity kept, the copy gone.
Colour is never compared to decide identity: `positive` and `warning` share a
token deliberately. The graph test now asserts the property that actually holds —
distinct steps on a zero-saturation scale — instead of pinning an indigo hex.
Residual `#rrggbb` in src/ is 248 → 101, and 74 of those are the vendor brand maps
and their tests. What is left is a data: URI where var() cannot resolve, a
cross-origin payment iframe that cannot read our tokens, hex-input placeholders,
prose, and the two greyscale scales themselves.
typecheck 0 errors · vitest 3013 passed / 8 skipped · build:embed green
Third and final pass. The chrome now expresses state by WEIGHT, ICON and LABEL;
hue is reserved for the one thing it legitimately carries — a third party's own
identity.
ONE MODULE (job 1). `tone-var.ts` was a second place to look for one idea, so
`toneVar` folds into `tone.ts` beside the ladder it is derived from — change the
emphasis order once and both the `$colorN` token and the `var(--colorN)` CSS form
move together. 37 importers repointed; `tone.ts` stays pure and node-testable.
`statusVar` had zero callers and is deleted rather than carried.
ONE CATEGORICAL SCALE. `tone` answers "what does this STATE mean"; a donut slice,
a graph node kind and a funding class ask a different question — "how do I tell N
categories apart". That scale already existed as `Charts.CHART_PALETTE` but lived
inside a React component, so `provider-billing.ts` had hand-copied four of its
steps and `graph-logic.ts` had invented a hue ladder of its own. Extracted to the
pure `lib/theme/ramp` (`RAMP`/`OTHER`) and shared: one scale, no copies, and a
canvas or SVG mark can reach it without importing React.
THE REMAINING HUES (job 2). ~30 chromatic hexes plus the rgba() and vendor-colour
duplicates the hex grep missed, across 91 files: greens → positive, reds →
critical, ambers → warning, blues/cyans → neutral, slate → muted. Every local
ladder is deleted and repointed (agents STATUS_HEX, machines STATUS_HEX, code
TIER_HEX, railway GREEN/RED, knowledge NODE/EDGE_COLORS, growth STAGE_META). Every
icon and label is kept — in monochrome they are what carries the meaning, which is
also why the Cloudflare orange could go: a Cloud glyph beside the word "Cloudflare"
was never relying on the hue.
Two fixes fall out of the sweep rather than being bolted on: a white glyph on a
user-chosen accent now asks `contrastText` instead of assuming white, and the
select chevron — byte-identical in two files — becomes one asset.
VENDOR IDENTITY PRESERVED. `brand-marks`/`brand`/`ProviderLogo` are untouched:
Anthropic coral, Qwen violet, NVIDIA green are those vendors' marks, not our
chrome. `ai-accounts` had re-declared two of them by hand and drifted (its OpenAI
green vs the brand map's black), so it now RESOLVES through the same
`brandForModel` the avatars use — identity kept, the copy gone.
Colour is never compared to decide identity: `positive` and `warning` share a
token deliberately. The graph test now asserts the property that actually holds —
distinct steps on a zero-saturation scale — instead of pinning an indigo hex.
Residual `#rrggbb` in src/ is 248 → 101, and 74 of those are the vendor brand maps
and their tests. What is left is a data: URI where var() cannot resolve, a
cross-origin payment iframe that cannot read our tokens, hex-input placeholders,
prose, and the two greyscale scales themselves.
typecheck 0 errors · vitest 3013 passed / 8 skipped · build:embed green
The console chrome is monochrome: globals.css defines ONE greyscale ramp
(--color1…--color12, zero saturation) and StatusTag has always expressed
status by WEIGHT. Two prior passes converted most of the app; ~270 hardcoded
semantic hexes survived across 77 files, so a "failed" pill was still red on
one screen and greyscale on the next.
Sweep them all onto the ONE map (src/components/ui/tone.ts):
greens -> positive · reds -> critical · ambers -> warning
blues -> neutral · greys -> muted
WHY weight and not hue: an AlertTriangle beside "Degraded" and a CheckCircle
beside "Healthy" are already unambiguous, so colour only has to carry
EMPHASIS. Every icon and label is unchanged — only the colour moved.
- Deleted every per-module hex ladder and repointed it at the one map:
affiliates/authors/referrals statusTone, gitops health+sync, sentry level/
status/log-level, guide step state, budgets meter, inference phase,
resource lifecycle, apm error rate, ai-accounts headroom, living-overview
status/health/severity, tasks status, provider funding, Metric utilColor.
- ErrorsModule carried a byte-identical copy of sentry's LEVEL_COLOR +
statusTone; deleted it and imported the one definition.
- Metric.tsx SERIES was still the old 8-hue rainbow while Charts.tsx had
already gone monochrome. SERIES is now CHART_PALETTE itself — one
categorical ramp, one place.
- The domain helpers that returned a colour but were named statusTone are
now statusTone -> Tone + statusColor -> token, matching tone.ts's own
vocabulary (a Tone is a meaning; a colour is an appearance).
New: src/components/ui/tone-var.ts. tone.ts speaks Tamagui tokens ($color12),
which a color=/bg= prop wants; a raw style={{…}} object and an SVG attribute
are plain CSS and need var(--color12). This is an ADAPTER over tone.ts, not a
second ladder — the emphasis order still lives in exactly one place.
BUG this exposed (living/logic.ts): healthTally identified a healthy row by
COLOUR EQUALITY (healthColor(h) === OK). Positive and warning deliberately
share $color11, so every degraded service started counting as healthy.
Split the vocabulary from the appearance — healthTone() is the semantic
decision, healthColor() is toneVar(healthTone()) — and the tally now asks the
tone. Colour is not an identity key in a monochrome system.
Vendor identity is untouched and stays chromatic: brand-marks.ts, brand.ts,
ProviderLogo.tsx are the MODEL VENDOR's own colours (Anthropic coral, Qwen
violet, Meta blue), shown on every brand host — that is their identity, not
our chrome. products/colors.ts (already greyscale) is likewise untouched.
Contract changes in tests, all deliberate: "distinct colour per verdict"
(budgets) and the per-hex tone assertions (affiliates/authors/referrals/
gitops/sentry/apm/links) no longer hold — a monochrome map shares tokens by
design. They now assert what actually matters: every tone is greyscale, and
the emphasis order is correct (critical outranks positive, unknown is never
dressed as failure).
tsc --noEmit clean · vitest 3011 passed (243 files) · build:embed green ·
zero target hexes left in src.
The console chrome is monochrome: globals.css defines ONE greyscale ramp
(--color1…--color12, zero saturation) and StatusTag has always expressed
status by WEIGHT. Two prior passes converted most of the app; ~270 hardcoded
semantic hexes survived across 77 files, so a "failed" pill was still red on
one screen and greyscale on the next.
Sweep them all onto the ONE map (src/components/ui/tone.ts):
greens -> positive · reds -> critical · ambers -> warning
blues -> neutral · greys -> muted
WHY weight and not hue: an AlertTriangle beside "Degraded" and a CheckCircle
beside "Healthy" are already unambiguous, so colour only has to carry
EMPHASIS. Every icon and label is unchanged — only the colour moved.
- Deleted every per-module hex ladder and repointed it at the one map:
affiliates/authors/referrals statusTone, gitops health+sync, sentry level/
status/log-level, guide step state, budgets meter, inference phase,
resource lifecycle, apm error rate, ai-accounts headroom, living-overview
status/health/severity, tasks status, provider funding, Metric utilColor.
- ErrorsModule carried a byte-identical copy of sentry's LEVEL_COLOR +
statusTone; deleted it and imported the one definition.
- Metric.tsx SERIES was still the old 8-hue rainbow while Charts.tsx had
already gone monochrome. SERIES is now CHART_PALETTE itself — one
categorical ramp, one place.
- The domain helpers that returned a colour but were named statusTone are
now statusTone -> Tone + statusColor -> token, matching tone.ts's own
vocabulary (a Tone is a meaning; a colour is an appearance).
New: src/components/ui/tone-var.ts. tone.ts speaks Tamagui tokens ($color12),
which a color=/bg= prop wants; a raw style={{…}} object and an SVG attribute
are plain CSS and need var(--color12). This is an ADAPTER over tone.ts, not a
second ladder — the emphasis order still lives in exactly one place.
BUG this exposed (living/logic.ts): healthTally identified a healthy row by
COLOUR EQUALITY (healthColor(h) === OK). Positive and warning deliberately
share $color11, so every degraded service started counting as healthy.
Split the vocabulary from the appearance — healthTone() is the semantic
decision, healthColor() is toneVar(healthTone()) — and the tally now asks the
tone. Colour is not an identity key in a monochrome system.
Vendor identity is untouched and stays chromatic: brand-marks.ts, brand.ts,
ProviderLogo.tsx are the MODEL VENDOR's own colours (Anthropic coral, Qwen
violet, Meta blue), shown on every brand host — that is their identity, not
our chrome. products/colors.ts (already greyscale) is likewise untouched.
Contract changes in tests, all deliberate: "distinct colour per verdict"
(budgets) and the per-hex tone assertions (affiliates/authors/referrals/
gitops/sentry/apm/links) no longer hold — a monochrome map shares tokens by
design. They now assert what actually matters: every tone is greyscale, and
the emphasis order is correct (critical outranks positive, unknown is never
dressed as failure).
tsc --noEmit clean · vitest 3011 passed (243 files) · build:embed green ·
zero target hexes left in src.
LIVE BUG (found by driving the real site headless): console.hanzo.ai renders the
anon marketing landing, whose shared @hanzogui/shell header carried the canonical
cloud.hanzo.ai CTAs — primary 'Open Console' -> https://console.hanzo.ai. Right
from anywhere else; from the console itself it is a SELF-LINK, so clicking it
re-rendered the same anonymous page. Nothing happened. To a signed-out visitor
that reads as 'login is broken'.
The header braids two orthogonal things: IDENTITY (brand, local nav, the Products
taxonomy) and NAVIGATION (its two CTAs). Identity was already correct, so only the
actions are re-pointed — at the ONE sign-in surface this page owns. Signing in IS
how you open the console, and a key is minted once you are in, so both CTAs have
exactly one honest destination and the page has one way in (the duplicate
sign-in button is dropped — it was a second control for the same thing).
Done as a pure value transform (src/lib/products/landing-surface.ts, base injected,
type-only import) rather than a fork, a new prop, or a second header: the shared
header keeps ONE definition, and the derivation is node-testable on its own. No env,
no flag, no branch — the same code path for every visitor.
landing-surface.test.ts (5) locks it: both CTAs land on /signin, neither is
cross-origin or external (the dead-button class can't come back), the primary is
labelled for what it does here, IDENTITY is untouched, and the canonical surface is
never mutated.
tsc --noEmit clean; vitest 5/5; npm run build:embed OK (static export, 30 route
handlers + 2 dynamic pages restored).
LIVE BUG (found by driving the real site headless): console.hanzo.ai renders the
anon marketing landing, whose shared @hanzogui/shell header carried the canonical
cloud.hanzo.ai CTAs — primary 'Open Console' -> https://console.hanzo.ai. Right
from anywhere else; from the console itself it is a SELF-LINK, so clicking it
re-rendered the same anonymous page. Nothing happened. To a signed-out visitor
that reads as 'login is broken'.
The header braids two orthogonal things: IDENTITY (brand, local nav, the Products
taxonomy) and NAVIGATION (its two CTAs). Identity was already correct, so only the
actions are re-pointed — at the ONE sign-in surface this page owns. Signing in IS
how you open the console, and a key is minted once you are in, so both CTAs have
exactly one honest destination and the page has one way in (the duplicate
sign-in button is dropped — it was a second control for the same thing).
Done as a pure value transform (src/lib/products/landing-surface.ts, base injected,
type-only import) rather than a fork, a new prop, or a second header: the shared
header keeps ONE definition, and the derivation is node-testable on its own. No env,
no flag, no branch — the same code path for every visitor.
landing-surface.test.ts (5) locks it: both CTAs land on /signin, neither is
cross-origin or external (the dead-button class can't come back), the primary is
labelled for what it does here, IDENTITY is untouched, and the canonical surface is
never mutated.
tsc --noEmit clean; vitest 5/5; npm run build:embed OK (static export, 30 route
handlers + 2 dynamic pages restored).
Reverts 445b9d4008. Per the CTO's host split:
- platform.hanzo.ai (this console) = per-org management dash — the per-org PaaS
deploy home (PlatformHome: deploy hero + App Store + Containers/Functions/Usage
+ your projects). So the platform shell goes back to the single-product face
(rootId/home = 'platform').
- admin.hanzo.ai = the FULL fleet admin — served by the separate operator SPA
(hanzoai/admin, the 'Admin Console'), whose Infrastructure god-view already reads
the /v1/paas apps drift board (every app's declared/running/drift). The fleet
control plane belongs there, not on the customer-facing platform host.
A super-admin still reaches the fleet boards on console.hanzo.ai (the admin:true
nav), and the operator SPA owns the dedicated fleet-admin surface.
Reverts 90adc1a602. Per the CTO's host split:
- platform.hanzo.ai (this console) = per-org management dash — the per-org PaaS
deploy home (PlatformHome: deploy hero + App Store + Containers/Functions/Usage
+ your projects). So the platform shell goes back to the single-product face
(rootId/home = 'platform').
- admin.hanzo.ai = the FULL fleet admin — served by the separate operator SPA
(hanzoai/admin, the 'Admin Console'), whose Infrastructure god-view already reads
the /v1/paas apps drift board (every app's declared/running/drift). The fleet
control plane belongs there, not on the customer-facing platform host.
A super-admin still reaches the fleet boards on console.hanzo.ai (the admin:true
nav), and the operator SPA owns the dedicated fleet-admin surface.
The platform face was a single-product shell (rootId/home = 'platform' → the
per-org PaaS deploy home, PlatformModule). Per the CTO call — and the FOLLOW-UP the
OSS App Store commit explicitly flagged ('upgrade the platform face from
single-product to a MULTI-product nav … a separate CTO call') — platform.<brand> is
the fleet CONTROL PLANE: it must show every deployment of every app + manage all
services.
Retarget the platform shell to a full-catalog control-plane shape:
rootId: 'platform' → null (full admin nav — a global admin sees Deploy,
Applications, Clusters, Kubernetes, Tenants, Storage,
… every service; not a single-product scope)
home: 'platform' → 'gitops' (boots into the Deploy fleet map — every operator
App CR's declared/running/latest/drift + builds/logs/
rollback), not the customer home.
Additive to the concurrent OSS-store work: the per-org deploy home (the 'platform'
product / PlatformHome) stays reachable as one nav item among many; only the LANDING
moves. isProductShell stays false for platform (a home alone never scopes the nav —
only a rootId does), so nav rendering is the full catalog exactly like console.
Auth unchanged (brand cloud app; a global admin resolves owner==='admin' on this
go:embed host exactly as on cloud.<brand>, so the admin fleet board works).
tsc clean; shell.test + config/index.test green (56); build:embed ✓ (go:embed gate).
The platform face was a single-product shell (rootId/home = 'platform' → the
per-org PaaS deploy home, PlatformModule). Per the CTO call — and the FOLLOW-UP the
OSS App Store commit explicitly flagged ('upgrade the platform face from
single-product to a MULTI-product nav … a separate CTO call') — platform.<brand> is
the fleet CONTROL PLANE: it must show every deployment of every app + manage all
services.
Retarget the platform shell to a full-catalog control-plane shape:
rootId: 'platform' → null (full admin nav — a global admin sees Deploy,
Applications, Clusters, Kubernetes, Tenants, Storage,
… every service; not a single-product scope)
home: 'platform' → 'gitops' (boots into the Deploy fleet map — every operator
App CR's declared/running/latest/drift + builds/logs/
rollback), not the customer home.
Additive to the concurrent OSS-store work: the per-org deploy home (the 'platform'
product / PlatformHome) stays reachable as one nav item among many; only the LANDING
moves. isProductShell stays false for platform (a home alone never scopes the nav —
only a rootId does), so nav rendering is the full catalog exactly like console.
Auth unchanged (brand cloud app; a global admin resolves owner==='admin' on this
go:embed host exactly as on cloud.<brand>, so the admin fleet board works).
tsc clean; shell.test + config/index.test green (56); build:embed ✓ (go:embed gate).
platform.hanzo.ai now lands on a REAL deploy platform, not the generic catalog:
- App Store product (store, Platform): browses the LIVE 1000+-app templates.hanzo.ai
catalog fetched straight from the browser (open CORS, no BFF -> works in go:embed);
search-first + Load-more (DOM capped), monogram logo fallback.
- One-click deploy reuses the console's REAL PaaS path (PaasApi -> /v1/platform/*):
ensure project -> createApp{source:git} -> deploy; honest build/live states. No new
backend.
- Maker Earn-20% hook -> in-console /authors (parsed from links.github).
- PlatformHome: deploy hero + tiles (App Store/Containers/Functions/Usage) + featured
OSS strip + your projects; PlatformModule '' renders it.
- Home Deploy-OSS tile -> native /store (was an external link-out).
- Additive only: the committed single-product platform shell is untouched.
tsc clean; vitest +24 green; next build + build:embed green; render-proven
(e2e/platform-store.spec.ts).
platform.hanzo.ai now lands on a REAL deploy platform, not the generic catalog:
- App Store product (store, Platform): browses the LIVE 1000+-app templates.hanzo.ai
catalog fetched straight from the browser (open CORS, no BFF -> works in go:embed);
search-first + Load-more (DOM capped), monogram logo fallback.
- One-click deploy reuses the console's REAL PaaS path (PaasApi -> /v1/platform/*):
ensure project -> createApp{source:git} -> deploy; honest build/live states. No new
backend.
- Maker Earn-20% hook -> in-console /authors (parsed from links.github).
- PlatformHome: deploy hero + tiles (App Store/Containers/Functions/Usage) + featured
OSS strip + your projects; PlatformModule '' renders it.
- Home Deploy-OSS tile -> native /store (was an external link-out).
- Additive only: the committed single-product platform shell is untouched.
tsc clean; vitest +24 green; next build + build:embed green; render-proven
(e2e/platform-store.spec.ts).
shellFromHost had no `platform` case, so platform.hanzo.ai fell through to the
default `console` shell — the product-catalog home (the monochrome "provider
grid"), instead of the embedded PaaS control-plane (apps table / deploys / drift,
the `platform` module). console.hanzo.ai and platform.hanzo.ai are the SAME
cloud-served SPA (byte-identical HTML, title-only white-label), so the face is
chosen client-side by shellFromHost(window.location.hostname) — and platform had
no entry.
Add `platform` as a ShellId face, mirroring dns.<brand> exactly:
- isPlatformHost — strict `platform.` prefix predicate
- shellFromHost — the branch + NEXT_PUBLIC_PRODUCT_SHELL override
- PRODUCT_SHELLS — descriptor (rootId/home = 'platform' → boots into PlatformModule,
the PaaS control plane); wordmark "Platform", indexes on Overview
platform.hanzo.ai is a Platform-faced alias of console.hanzo.ai (one shared cloud
backend, two entry points); console.hanzo.ai keeps Platform as one product among many.
tsc --noEmit clean (0 errors, whole project); shell.test.ts + config/index.test.ts
green (55 tests). Ships to platform.hanzo.ai via the next hanzoai/cloud release
embedding console@main (go:embed; CONSOLE_REF=main).
shellFromHost had no `platform` case, so platform.hanzo.ai fell through to the
default `console` shell — the product-catalog home (the monochrome "provider
grid"), instead of the embedded PaaS control-plane (apps table / deploys / drift,
the `platform` module). console.hanzo.ai and platform.hanzo.ai are the SAME
cloud-served SPA (byte-identical HTML, title-only white-label), so the face is
chosen client-side by shellFromHost(window.location.hostname) — and platform had
no entry.
Add `platform` as a ShellId face, mirroring dns.<brand> exactly:
- isPlatformHost — strict `platform.` prefix predicate
- shellFromHost — the branch + NEXT_PUBLIC_PRODUCT_SHELL override
- PRODUCT_SHELLS — descriptor (rootId/home = 'platform' → boots into PlatformModule,
the PaaS control plane); wordmark "Platform", indexes on Overview
platform.hanzo.ai is a Platform-faced alias of console.hanzo.ai (one shared cloud
backend, two entry points); console.hanzo.ai keeps Platform as one product among many.
tsc --noEmit clean (0 errors, whole project); shell.test.ts + config/index.test.ts
green (55 tests). Ships to platform.hanzo.ai via the next hanzoai/cloud release
embedding console@main (go:embed; CONSOLE_REF=main).
Follow-up to the design-token adoption: the remaining chromatic accents were
Tamagui theme TOKENS ($blue10/$blue11 links + icons, $blue3/$blue4 badge fills,
$orange10 severity), which the first pass's hex-focused sweep missed.
- $blue10 → $color11, $blue11 → $color12, $blue3/$blue4 → $color3/$color4
(neutral ladder) across StorageModule, SearchModule, ContactModule, Tracker,
embeddings, providers, platform-hub, StartupsModule and 8 more.
- $orange10 → $yellow10: severity/priority/waitlist states keep a sanctioned
amber CAUTION hue (the design's allowed semantic), not a decorative orange.
Console chrome now uses zero chromatic accents — only the neutral ladder plus the
three permitted semantics (green/amber/red). tsc clean, next build ok.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Follow-up to the design-token adoption: the remaining chromatic accents were
Tamagui theme TOKENS ($blue10/$blue11 links + icons, $blue3/$blue4 badge fills,
$orange10 severity), which the first pass's hex-focused sweep missed.
- $blue10 → $color11, $blue11 → $color12, $blue3/$blue4 → $color3/$color4
(neutral ladder) across StorageModule, SearchModule, ContactModule, Tracker,
embeddings, providers, platform-hub, StartupsModule and 8 more.
- $orange10 → $yellow10: severity/priority/waitlist states keep a sanctioned
amber CAUTION hue (the design's allowed semantic), not a decorative orange.
Console chrome now uses zero chromatic accents — only the neutral ladder plus the
three permitted semantics (green/amber/red). tsc clean, next build ok.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Multi-network validators (Lux primary/testnet/devnet + Pars/Osage/L2 coming-soon),
node/pod memory, 16 lux-* service health — real VM-hub telemetry via the gated
proxy, honest 0.0000-uptime note (tracker bug), zero cross-brand leak. Only on
console.lux.cloud. 10/10 shaper + 174 registry tests, tsc 0 errors. 8.4.156→8.4.157.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Wire the Hanzo Design System (hanzoai/design) into the console as the styling
source of truth and convert the whole surface to true-black MONOCHROME
(Linear/Vercel-grade), keeping only the genuine semantic hues (green live/success ·
amber caution · red error).
- Vendor the design token layer (color/type/space/radius/elevation/motion/z) into
app/design/ — @hanzo/design is unpublished, and its README contract is copy-1:1 —
and import it before globals.css so the Tamagui theme derives from the design
neutral ladder.
- colors.ts: retire the per-product/category rainbow. Product + category icons now
read ONE neutral (design --neutral-300); legacy chromatic prefs still resolve but
only to greyscale. Public API + persisted keys unchanged.
- Charts CHART_PALETTE → monochrome descending-lightness ramp (was a purple-led
rainbow); grid/axis neutralized.
- Primary actions (Deploy Endpoint / landing CTA) → theme-aware white-on-black
monochrome (was purple #7c5cff).
- Purge #a371f7 / #c084fc / #3aa0ff / #7c5cff / #8b5cf6 / #5E6AD2 house accents
across 30 modules → design neutrals; router / mission-control / scope / hero /
railway / crm accents monochromized; hero + template-tile gradients → neutral.
- Tests enforce the monochrome guarantee (every swatch greyscale; legacy keys never
reintroduce a hue). 2953 unit tests green, tsc clean, next build ok.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Wire the Hanzo Design System (hanzoai/design) into the console as the styling
source of truth and convert the whole surface to true-black MONOCHROME
(Linear/Vercel-grade), keeping only the genuine semantic hues (green live/success ·
amber caution · red error).
- Vendor the design token layer (color/type/space/radius/elevation/motion/z) into
app/design/ — @hanzo/design is unpublished, and its README contract is copy-1:1 —
and import it before globals.css so the Tamagui theme derives from the design
neutral ladder.
- colors.ts: retire the per-product/category rainbow. Product + category icons now
read ONE neutral (design --neutral-300); legacy chromatic prefs still resolve but
only to greyscale. Public API + persisted keys unchanged.
- Charts CHART_PALETTE → monochrome descending-lightness ramp (was a purple-led
rainbow); grid/axis neutralized.
- Primary actions (Deploy Endpoint / landing CTA) → theme-aware white-on-black
monochrome (was purple #7c5cff).
- Purge #a371f7 / #c084fc / #3aa0ff / #7c5cff / #8b5cf6 / #5E6AD2 house accents
across 30 modules → design neutrals; router / mission-control / scope / hero /
railway / crm accents monochromized; hero + template-tile gradients → neutral.
- Tests enforce the monochrome guarantee (every swatch greyscale; legacy keys never
reintroduce a hue). 2953 unit tests green, tsc clean, next build ok.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- SidebarBrand: the selected org's OWN logo leads the top-left chrome (useOrgLogo,
cached, shared with BrandLogo); the Hanzo H is only the fallback (hanzo org's
logo IS the Hanzo mark). White-label — a tenant sees their brand front and center.
- FloatingChat: removed the big floating circle that covered page content. The
assistant now opens from the topbar: a SMALL brand-H (openChat → the right sidebar
/ dock on desktop, the sheet on phones) + a mic 'talk to Hanzo' (startVoice).
- Voice (new src/lib/voice.ts): a feature-detected Web Speech wrapper (SpeechRecognition
STT + speechSynthesis TTS), SSR-safe, strict-clean. Wired INTO the one chat binding
(AiApi.ragChatStream) — a mic in the composer (renders only when supported) + a
voiceSignal from the topbar; a completed utterance sends a turn and the reply is
spoken back. No new backend, nothing leaves the browser.
- Workbench: the Developers dock is now FREELY drag-resizable (top handle → any
height, persisted per-user) instead of a binary toggle; the maximize button is a
tall/compact preset. Overview tab: a live 'Create key' button mints the real hk-
Cloud API key inline (KeysApi.create), shown once with a copy affordance.
- AuthorsModule: dropped the public 'earn 20%' number from every hero/CTA/badge; the
real rate stays as ONE muted 'Your rate' dashboard detail (per CTO — no public %).
- SystemStatusBadge: degrade 'Checking…' → neutral 'Status' after the first probe
returns nothing (the go:embed build prunes /system-status), never a permanent spinner.
tsc --noEmit clean; npm run build:embed ✓ (static export + 30 handlers restored).
- SidebarBrand: the selected org's OWN logo leads the top-left chrome (useOrgLogo,
cached, shared with BrandLogo); the Hanzo H is only the fallback (hanzo org's
logo IS the Hanzo mark). White-label — a tenant sees their brand front and center.
- FloatingChat: removed the big floating circle that covered page content. The
assistant now opens from the topbar: a SMALL brand-H (openChat → the right sidebar
/ dock on desktop, the sheet on phones) + a mic 'talk to Hanzo' (startVoice).
- Voice (new src/lib/voice.ts): a feature-detected Web Speech wrapper (SpeechRecognition
STT + speechSynthesis TTS), SSR-safe, strict-clean. Wired INTO the one chat binding
(AiApi.ragChatStream) — a mic in the composer (renders only when supported) + a
voiceSignal from the topbar; a completed utterance sends a turn and the reply is
spoken back. No new backend, nothing leaves the browser.
- Workbench: the Developers dock is now FREELY drag-resizable (top handle → any
height, persisted per-user) instead of a binary toggle; the maximize button is a
tall/compact preset. Overview tab: a live 'Create key' button mints the real hk-
Cloud API key inline (KeysApi.create), shown once with a copy affordance.
- AuthorsModule: dropped the public 'earn 20%' number from every hero/CTA/badge; the
real rate stays as ONE muted 'Your rate' dashboard detail (per CTO — no public %).
- SystemStatusBadge: degrade 'Checking…' → neutral 'Status' after the first probe
returns nothing (the go:embed build prunes /system-status), never a permanent spinner.
tsc --noEmit clean; npm run build:embed ✓ (static export + 30 handlers restored).
The OSS author overview fallback (normalizeOverview) and the treasury policy
copy defaulted to 5% (500 bps). Align to the ONE canonical creator share, 20%
(2000 bps), matching cloud's authors.defaultShareBps and the treasury policy
default: a missing defaultShareBps now falls back to 2000, and the revenue-share
form hint/examples read 20%. Test updated for the 2000 fallback.
The OSS author overview fallback (normalizeOverview) and the treasury policy
copy defaulted to 5% (500 bps). Align to the ONE canonical creator share, 20%
(2000 bps), matching cloud's authors.defaultShareBps and the treasury policy
default: a missing defaultShareBps now falls back to 2000, and the revenue-share
form hint/examples read 20%. Test updated for the 2000 fallback.
Build+push of ghcr.io/hanzoai/console now lives in .hanzo/workflows/deploy.yml
(in-cluster BuildKit -> operator reconcile). GitHub Actions is mirror-only for
the app image. cicd.yml (distinct console-embed artifact) is left untouched.
Build+push of ghcr.io/hanzoai/console now lives in .hanzo/workflows/deploy.yml
(in-cluster BuildKit -> operator reconcile). GitHub Actions is mirror-only for
the app image. cicd.yml (distinct console-embed artifact) is left untouched.
Additive completion on top of the committed single-file Webhooks product (997b93a4a):
- webhooks/verify.ts — pure, unit-tested signature-verification reference: the exact
scheme (X-Webhook-Signature: t=<unix>,v1=hex(hmac_sha256(secret,"<t>.<body>"))) plus
constant-time Node (node:crypto) + Go (crypto/hmac) verifiers and the live subject list.
- webhooks/VerifyCard.tsx — renders the scheme, the three delivery headers, and the
copy-paste Node/Go snippets; wired into WebhooksModule with one import + one render.
- WebhooksModule: live-subjects helper (commerce.order.* · commerce.checkout.* · commerce.>,
"more streams coming") under the create form's Events field.
- ConsoleFooter: brand-aware Developers cluster (Docs · API · Webhooks) — Webhooks opens
the in-console product route, API/Docs point at the brand docs site.
tsc --noEmit clean; vitest 2953 passed / 8 skipped (+5 verify tests).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Additive completion on top of the committed single-file Webhooks product (997b93a4a):
- webhooks/verify.ts — pure, unit-tested signature-verification reference: the exact
scheme (X-Webhook-Signature: t=<unix>,v1=hex(hmac_sha256(secret,"<t>.<body>"))) plus
constant-time Node (node:crypto) + Go (crypto/hmac) verifiers and the live subject list.
- webhooks/VerifyCard.tsx — renders the scheme, the three delivery headers, and the
copy-paste Node/Go snippets; wired into WebhooksModule with one import + one render.
- WebhooksModule: live-subjects helper (commerce.order.* · commerce.checkout.* · commerce.>,
"more streams coming") under the create form's Events field.
- ConsoleFooter: brand-aware Developers cluster (Docs · API · Webhooks) — Webhooks opens
the in-console product route, API/Docs point at the brand docs site.
tsc --noEmit clean; vitest 2953 passed / 8 skipped (+5 verify tests).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add a first-class Webhooks product (category Dev) over the live /v1/webhooks API,
mirroring the VpcModule/LoadBalancerModule idiom (restGet/restPost/restPatch/
restDelete + cloudProxyV1Url, PlatformError handling, enc() id-escaping):
- List: endpoints table — url, event chips, active/disabled status, 7d
deliveries/failures usage (when present), row actions.
- Create: HTTPS url + comma/pattern events (* / commerce.> / agent.run.*) +
description; reveal-once signing secret in a copyable callout.
- Enable/disable: inline PATCH {status} toggle.
- Security: rotate secret (confirm → reveal-once) + the X-Webhook-Signature
HMAC-SHA256 scheme shown inline.
- Test: per-endpoint sync test-send, inline delivered/httpStatus/durationMs result
(works while disabled).
- Logs: per-endpoint deliveries (expand + :view deep-link), newest-first, failed-
only filter, manual refresh.
Sub-features (test/deliveries/rotate/usage counters) still landing from the cloud
lane DEGRADE GRACEFULLY — a 404 hides that one affordance, never an error card.
Register one CatalogEntry (routes '' + :view); the shell/router derive from the
catalog. Add the `webhooks` head to proxy-allow CLOUD_HEADS so the standalone /v1
bearer proxy forwards /v1/webhooks[/:id/{deliveries,test,rotate-secret}] (org from
the token owner); the go:embed console hits cloud /v1/webhooks natively. Retire the
workbench Webhooks stub to a read-only glance that deep-links into the product (one
place owns CRUD). Add a mocked-network Playwright render spec.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Add a first-class Webhooks product (category Dev) over the live /v1/webhooks API,
mirroring the VpcModule/LoadBalancerModule idiom (restGet/restPost/restPatch/
restDelete + cloudProxyV1Url, PlatformError handling, enc() id-escaping):
- List: endpoints table — url, event chips, active/disabled status, 7d
deliveries/failures usage (when present), row actions.
- Create: HTTPS url + comma/pattern events (* / commerce.> / agent.run.*) +
description; reveal-once signing secret in a copyable callout.
- Enable/disable: inline PATCH {status} toggle.
- Security: rotate secret (confirm → reveal-once) + the X-Webhook-Signature
HMAC-SHA256 scheme shown inline.
- Test: per-endpoint sync test-send, inline delivered/httpStatus/durationMs result
(works while disabled).
- Logs: per-endpoint deliveries (expand + :view deep-link), newest-first, failed-
only filter, manual refresh.
Sub-features (test/deliveries/rotate/usage counters) still landing from the cloud
lane DEGRADE GRACEFULLY — a 404 hides that one affordance, never an error card.
Register one CatalogEntry (routes '' + :view); the shell/router derive from the
catalog. Add the `webhooks` head to proxy-allow CLOUD_HEADS so the standalone /v1
bearer proxy forwards /v1/webhooks[/:id/{deliveries,test,rotate-secret}] (org from
the token owner); the go:embed console hits cloud /v1/webhooks natively. Retire the
workbench Webhooks stub to a read-only glance that deep-links into the product (one
place owns CRUD). Add a mocked-network Playwright render spec.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Two first-class primary-action tiles on the post-signin dashboard home
(app/(dashboard)/page.tsx), rendered through ONE new presentational,
prop-driven PrimaryActionTile primitive — the bespoke GetApiKeyCta card is
folded into it, so the three top actions share one card definition (DRY).
- Deploy OSS -> opens the one-click OSS template catalog in a new tab
(config.templatesUrl, default platform.hanzo.ai/templates, override
NEXT_PUBLIC_TEMPLATES_URL). No in-console fetch: the 1000+-app catalog
never touches the dashboard's first paint; it loads only on press.
- Earn from your OSS -> the EXISTING /authors OSS revenue-share program
(reused, not duplicated): 20% of the compute margin your project drives,
paid to your Hanzo wallet (SidebarWallet balance). Honest copy, no
fabricated amounts.
Reuses the shared ProductIcon + product-color system (colorOf) for the icon
tiles; adds shared, env-overridable config.templatesUrl.
Verify: tsc 0 new errors; vitest 2948 pass; ~0.5KB gzipped on /, no new deps.
Two first-class primary-action tiles on the post-signin dashboard home
(app/(dashboard)/page.tsx), rendered through ONE new presentational,
prop-driven PrimaryActionTile primitive — the bespoke GetApiKeyCta card is
folded into it, so the three top actions share one card definition (DRY).
- Deploy OSS -> opens the one-click OSS template catalog in a new tab
(config.templatesUrl, default platform.hanzo.ai/templates, override
NEXT_PUBLIC_TEMPLATES_URL). No in-console fetch: the 1000+-app catalog
never touches the dashboard's first paint; it loads only on press.
- Earn from your OSS -> the EXISTING /authors OSS revenue-share program
(reused, not duplicated): 20% of the compute margin your project drives,
paid to your Hanzo wallet (SidebarWallet balance). Honest copy, no
fabricated amounts.
Reuses the shared ProductIcon + product-color system (colorOf) for the icon
tiles; adds shared, env-overridable config.templatesUrl.
Verify: tsc 0 new errors; vitest 2948 pass; ~0.5KB gzipped on /, no new deps.
Edge + ServiceMesh each hand-rolled the identical rows/loading/error +
restGet(originV1Url) + interpretPlatformError boilerplate. Fold it into ONE
composable hook (useResourceList<T>(path, key)) over the canonical REST client
and PlatformError model. Modules become a one-line data seam; the hook is
reusable by any future /v1 collection view (Networks legacy raw-fetch is a
follow-up convert). Typecheck clean; behavior identical (empty+typed-error on
failure, never a blank page).
Edge + ServiceMesh each hand-rolled the identical rows/loading/error +
restGet(originV1Url) + interpretPlatformError boilerplate. Fold it into ONE
composable hook (useResourceList<T>(path, key)) over the canonical REST client
and PlatformError model. Modules become a one-line data seam; the hook is
reusable by any future /v1 collection view (Networks legacy raw-fetch is a
follow-up convert). Typecheck clean; behavior identical (empty+typed-error on
failure, never a blank page).
console.hanzo.ai login was stuck on /auth/callback with 'Sign-in failed.' The
OAuth code is single-use and @hanzo/iam removes the PKCE verifier before the token
fetch, so React StrictMode's double-invoke (reactStrictMode:true) — or any
handleCallback identity change re-running the effect — fired a SECOND exchange that
found the code consumed / verifier gone and threw, surfacing the failure even though
the first exchange succeeded. Add a useRef run-once guard so the exchange fires once
per page load. Also drop the vestigial @hanzo/iam-js-sdk dep (unused; one way = @hanzo/iam).
console.hanzo.ai login was stuck on /auth/callback with 'Sign-in failed.' The
OAuth code is single-use and @hanzo/iam removes the PKCE verifier before the token
fetch, so React StrictMode's double-invoke (reactStrictMode:true) — or any
handleCallback identity change re-running the effect — fired a SECOND exchange that
found the code consumed / verifier gone and threw, surfacing the failure even though
the first exchange succeeded. Add a useRef run-once guard so the exchange fires once
per page load. Also drop the vestigial @hanzo/iam-js-sdk dep (unused; one way = @hanzo/iam).
The SuperAdmin operator view (admin.hanzo.ai) that makes the whole growth-OS
backend observable AND editable at a glance, over the live cloud clients/guide
`/v1/guide/*` contracts (the `guide` head on the /v1 user-bearer BFF).
- src/lib/guide/client.ts — GuideBlueprintApi, modeled on lib/framework/client.ts:
restGet/restPut/restPatch over cloudProxyV1Url('guide/...'), typed + defensively
normalized to the blueprint/strategies/profile/suggest contracts. The core client
already exposes restPatch (the plain-REST partial-edit seam), so the {enabled:false}
lever rides the existing verb — no new seam. Pure strategyQuery shaping + normalizers
unit-tested (client.test.ts, 12 tests).
- GrowthModule.tsx — three sections, a UI to SCAN and OPERATE (summary before detail,
state encoded in form; semantic stage/on-track color separate from the brand accent):
· Blueprint — the 64 archetype principles (hexagram + Sun Tzu concept + domain, each
expandable to its tactics) and the journey (sections → steps, tool + deps), every
item with a live enable/disable toggle (PATCH) + inline edit; version chip +
Publish version + history.
· Corpus — browse/filter the ~888 tactics by category/stage/workload + search, a
count + category-coverage donut (the genome made legible), blog why/how/case-study.
· Live state — the org's dogfood read: stage indicator (formed→launched→activated→
scaling), signals, key metrics + funnel sparkline, and the ranked next-best moves
(leverage/unlocks + automatable). <GrowthOrgOverview> is the drop-in seam for the
future cross-org macro table.
Registered as catalog id `growth` (Observe, admin: true) in registry.tsx; the module
also gates on useIsSuperAdmin() over the authoritative server-side gate. Operator copy
+ toasts that say exactly what happened; honest loading/empty/error states, no fabrication.
Green: tsc --noEmit 0 errors; vitest 2945/2945 (234 files, +12); next build ✓;
build:embed ✓ (go:embed gate).
The SuperAdmin operator view (admin.hanzo.ai) that makes the whole growth-OS
backend observable AND editable at a glance, over the live cloud clients/guide
`/v1/guide/*` contracts (the `guide` head on the /v1 user-bearer BFF).
- src/lib/guide/client.ts — GuideBlueprintApi, modeled on lib/framework/client.ts:
restGet/restPut/restPatch over cloudProxyV1Url('guide/...'), typed + defensively
normalized to the blueprint/strategies/profile/suggest contracts. The core client
already exposes restPatch (the plain-REST partial-edit seam), so the {enabled:false}
lever rides the existing verb — no new seam. Pure strategyQuery shaping + normalizers
unit-tested (client.test.ts, 12 tests).
- GrowthModule.tsx — three sections, a UI to SCAN and OPERATE (summary before detail,
state encoded in form; semantic stage/on-track color separate from the brand accent):
· Blueprint — the 64 archetype principles (hexagram + Sun Tzu concept + domain, each
expandable to its tactics) and the journey (sections → steps, tool + deps), every
item with a live enable/disable toggle (PATCH) + inline edit; version chip +
Publish version + history.
· Corpus — browse/filter the ~888 tactics by category/stage/workload + search, a
count + category-coverage donut (the genome made legible), blog why/how/case-study.
· Live state — the org's dogfood read: stage indicator (formed→launched→activated→
scaling), signals, key metrics + funnel sparkline, and the ranked next-best moves
(leverage/unlocks + automatable). <GrowthOrgOverview> is the drop-in seam for the
future cross-org macro table.
Registered as catalog id `growth` (Observe, admin: true) in registry.tsx; the module
also gates on useIsSuperAdmin() over the authoritative server-side gate. Operator copy
+ toasts that say exactly what happened; honest loading/empty/error states, no fabrication.
Green: tsc --noEmit 0 errors; vitest 2945/2945 (234 files, +12); next build ✓;
build:embed ✓ (go:embed gate).
Greeting 'How can I help?' -> 'What do you want to build?'. Suggested prompts are
now declarative {label, fill|href}: 'Build an app ->' LAUNCHES the hanzo.app
builder (config.appUrl/dev — the canonical cross-surface action, not a dead-end
chat prompt); the rest fill the composer with grounded, capability-showcasing
questions (launch a GPU, deploy an agent, pick a model, pricing).
Greeting 'How can I help?' -> 'What do you want to build?'. Suggested prompts are
now declarative {label, fill|href}: 'Build an app ->' LAUNCHES the hanzo.app
builder (config.appUrl/dev — the canonical cross-surface action, not a dead-end
chat prompt); the rest fill the composer with grounded, capability-showcasing
questions (launch a GPU, deploy an agent, pick a model, pricing).
- PublicLanding hero: drop the unitless style lineHeight:1.1 — on a Tamagui/RNW
<Text> a bare number is coerced to 1.1px, collapsing the 60px headline onto a
1px line so the two wrap-lines overlapped into garbled text. Same trap fixed in
CodeSamples (1.6 -> '1.6em').
- Geist fonts: the CDN @import lived in globals.css and was emitted AFTER the
reset rules in the compiled bundle, so per spec it was invalid and dropped ->
the app fell back to system-ui. Moved the two @imports to app/fonts.css imported
FIRST in layout, so they lead the bundle and Geist Sans/Mono load. Verified: the
compiled CSS now begins with the @import.
- PublicLanding hero: drop the unitless style lineHeight:1.1 — on a Tamagui/RNW
<Text> a bare number is coerced to 1.1px, collapsing the 60px headline onto a
1px line so the two wrap-lines overlapped into garbled text. Same trap fixed in
CodeSamples (1.6 -> '1.6em').
- Geist fonts: the CDN @import lived in globals.css and was emitted AFTER the
reset rules in the compiled bundle, so per spec it was invalid and dropped ->
the app fell back to system-ui. Moved the two @imports to app/fonts.css imported
FIRST in layout, so they lead the bundle and Geist Sans/Mono load. Verified: the
compiled CSS now begins with the @import.
The ⌘K palette collapsed to a ~2-row sliver when few results matched
(desktop body minH:120/maxH:420). Raise it to minH:340/maxH:560 so it reads
as a real command surface with room to breathe and shows more results before
scrolling. Footer/legend stays pinned (separate row); mobile full-screen
unchanged.
The ⌘K palette collapsed to a ~2-row sliver when few results matched
(desktop body minH:120/maxH:420). Raise it to minH:340/maxH:560 so it reads
as a real command surface with room to breathe and shows more results before
scrolling. Footer/legend stays pinned (separate row); mobile full-screen
unchanged.
Shell re-render (decomplect the route subscription):
- Dashboard no longer calls usePathname(); the route subscription is confined to
the leaves that depend on it (SidebarNav for the active highlight, a new
BreadcrumbsBar). A navigation click now re-renders only the swapped page content
and those leaves — the topbar and sidebar chrome stay put (no flicker/lost state).
Upstream notices:
- Remove the per-product "Built on open source — forked from X" surfaces from the
UI (the content-column note, the interstitial OSS-card clause, the overview
"Upstream" fact). OSS attribution belongs in the repo LICENSE/NOTICE, not the
product surface; permissive/copyleft licenses require the notice in source, not
in-product. Upstream provenance stays catalog metadata for NOTICE generation.
- Delete the now-unused ProductUpstreamNote component.
- Drop the LibreChat upstream from the chat entry: the in-console chat is a native
widget over /v1/chat/completions, not a LibreChat fork.
v8.4.154.
Shell re-render (decomplect the route subscription):
- Dashboard no longer calls usePathname(); the route subscription is confined to
the leaves that depend on it (SidebarNav for the active highlight, a new
BreadcrumbsBar). A navigation click now re-renders only the swapped page content
and those leaves — the topbar and sidebar chrome stay put (no flicker/lost state).
Upstream notices:
- Remove the per-product "Built on open source — forked from X" surfaces from the
UI (the content-column note, the interstitial OSS-card clause, the overview
"Upstream" fact). OSS attribution belongs in the repo LICENSE/NOTICE, not the
product surface; permissive/copyleft licenses require the notice in source, not
in-product. Upstream provenance stays catalog metadata for NOTICE generation.
- Delete the now-unused ProductUpstreamNote component.
- Drop the LibreChat upstream from the chat entry: the in-console chat is a native
widget over /v1/chat/completions, not a LibreChat fork.
v8.4.154.
- fmtValue: at abs>=100 toFixed(0) yields a dotless integer string; the naive
trailing-zero trim ate its real zeros (150.4 -> '15', 1000.4 -> '1'). Guard
the trim on a decimal point + group the rounded integer like the integer path
(1000.4 -> '1,000'). Extracted to a pure research-fmt.ts (no JSX) so the
honesty-critical formatter is unit-testable; 3 regression tests.
- verdict: trim before clamping so 'refuted ' still counts as refuted (was
silently dropping from the Refuted KPI + refutations panel).
- rowKey: fall back to subject:task so id-less rows don't collide on key ''
(expand-all bug).
- fmtDate: guard NaN date. Build + typecheck + 10 tests green.
- fmtValue: at abs>=100 toFixed(0) yields a dotless integer string; the naive
trailing-zero trim ate its real zeros (150.4 -> '15', 1000.4 -> '1'). Guard
the trim on a decimal point + group the rounded integer like the integer path
(1000.4 -> '1,000'). Extracted to a pure research-fmt.ts (no JSX) so the
honesty-critical formatter is unit-testable; 3 regression tests.
- verdict: trim before clamping so 'refuted ' still counts as refuted (was
silently dropping from the Refuted KPI + refutations panel).
- rowKey: fall back to subject:task so id-less rows don't collide on key ''
(expand-all bug).
- fmtDate: guard NaN date. Build + typecheck + 10 tests green.
Per the tenancy IA (Account → Workspace → Project → Environment): switching the
workspace changes everything beneath it, so it leads the sidebar. Split the old
bottom SidebarIdentity cluster into SidebarWorkspace (the OrgSwitcher, rendered at
the TOP just under SidebarBrand) + SidebarAccount (the user/account row, unchanged
at the bottom). A user no longer confuses 'who I am' (bottom) with 'which workspace
I'm acting in' (top). Applied across all sidebar layouts (persistent desktop, flyout,
mobile drawer); the collapsed icon-rail omits it (SidebarWorkspace returns null when
collapsed — workspace switching happens in the expanded flyout). No OrgSwitcher logic
change, only position. tsc clean; next build + build:embed green.
Per the tenancy IA (Account → Workspace → Project → Environment): switching the
workspace changes everything beneath it, so it leads the sidebar. Split the old
bottom SidebarIdentity cluster into SidebarWorkspace (the OrgSwitcher, rendered at
the TOP just under SidebarBrand) + SidebarAccount (the user/account row, unchanged
at the bottom). A user no longer confuses 'who I am' (bottom) with 'which workspace
I'm acting in' (top). Applied across all sidebar layouts (persistent desktop, flyout,
mobile drawer); the collapsed icon-rail omits it (SidebarWorkspace returns null when
collapsed — workspace switching happens in the expanded flyout). No OrgSwitcher logic
change, only position. tsc clean; next build + build:embed green.
Follows the cloud endpoint rename (/v1/admin/storage → /v1/admin/block-storage,
cloud 9a51bffbc) so /v1/admin/storage stays free for the operator's S3
object-buckets view. Client (storage-fleet.ts) + the ADMIN_AGGREGATE_HEADS /
ADMIN_V1_HEADS allow-lists + the e2e mock all move to the block-storage head; the
registry entry id was already block-storage. The real admin.hanzo.ai Block Storage
view lives in hanzoai/admin apps/operator (this console board is the super-admin
twin on console.hanzo.ai).
NOTE: main is RED from a PRE-EXISTING unrelated error — src/lib/event.ts:55 passes
`ingestKey` to createAnalytics but the installed @hanzo/event AnalyticsConfig has no
such field (another agent's 8.4.152 analytics work; needs a @hanzo/event bump).
This repoint is green on its own; the event.ts RED blocks the shared build:embed
gate until that lane fixes it.
Follows the cloud endpoint rename (/v1/admin/storage → /v1/admin/block-storage,
cloud 9a51bffbc) so /v1/admin/storage stays free for the operator's S3
object-buckets view. Client (storage-fleet.ts) + the ADMIN_AGGREGATE_HEADS /
ADMIN_V1_HEADS allow-lists + the e2e mock all move to the block-storage head; the
registry entry id was already block-storage. The real admin.hanzo.ai Block Storage
view lives in hanzoai/admin apps/operator (this console board is the super-admin
twin on console.hanzo.ai).
NOTE: main is RED from a PRE-EXISTING unrelated error — src/lib/event.ts:55 passes
`ingestKey` to createAnalytics but the installed @hanzo/event AnalyticsConfig has no
such field (another agent's 8.4.152 analytics work; needs a @hanzo/event bump).
This repoint is green on its own; the event.ts RED blocks the shared build:embed
gate until that lane fixes it.
Surface the /v1/research R&D corpus (HIP-0512) in the console so the
experiments logged to the evidence plane are visible to platform admins.
- src/lib/api/research.ts: typed plain-REST client for the evidence plane
(experiment ledger + totals/by-kind), read through the user-bearer BFF and
org-scoped by the Bearer owner. Defensive normalizers parse the free-form
meta frame (hypothesis/predict/verdict/because/log) and degrade a missing
field to ''/0/[] rather than fabricate one. Reads via restGet because the
endpoints speak bare JSON, not the casibase envelope.
- src/components/products/ResearchModule.tsx: the board — totals band, a
per-kind facet, the verdict ledger (colored pills, expandable scientific
frame), and a refutation highlight (a refutation is a first-class result).
Renders OperatorAccessRequired for a non-super-admin client.
- src/lib/products/registry.tsx: one CatalogEntry (id research, Observe
category, admin) mapping to ResearchModule.
- src/lib/server/proxy-allow.ts: admit the org-scoped `research` head on the
/v1 user-bearer BFF so /v1/research/* reaches cloud.
Tests: client normalizers against the real Go/Rust wire shape; proxy-allow
admits the experiments/totals/projects sub-paths. typecheck + next build green.
Surface the /v1/research R&D corpus (HIP-0512) in the console so the
experiments logged to the evidence plane are visible to platform admins.
- src/lib/api/research.ts: typed plain-REST client for the evidence plane
(experiment ledger + totals/by-kind), read through the user-bearer BFF and
org-scoped by the Bearer owner. Defensive normalizers parse the free-form
meta frame (hypothesis/predict/verdict/because/log) and degrade a missing
field to ''/0/[] rather than fabricate one. Reads via restGet because the
endpoints speak bare JSON, not the casibase envelope.
- src/components/products/ResearchModule.tsx: the board — totals band, a
per-kind facet, the verdict ledger (colored pills, expandable scientific
frame), and a refutation highlight (a refutation is a first-class result).
Renders OperatorAccessRequired for a non-super-admin client.
- src/lib/products/registry.tsx: one CatalogEntry (id research, Observe
category, admin) mapping to ResearchModule.
- src/lib/server/proxy-allow.ts: admit the org-scoped `research` head on the
/v1 user-bearer BFF so /v1/research/* reaches cloud.
Tests: client normalizers against the real Go/Rust wire shape; proxy-allow
admits the experiments/totals/projects sub-paths. typecheck + next build green.
Upgrade @hanzo/event ^0.2.0 -> ^0.3.1 — the ONE telemetry client that POSTs
every signal (pageview · product event · identify · error) as one batched
stream to the ONE Hanzo Cloud front door /v1/event, lensed server-side into
web analytics, product insights, and error tracking (subsumes @sentry). The
0.2.0 client posted the deprecated /v1/analytics + /v1/tracker.
- ONE shared client (src/lib/event.ts): createAnalytics({ product:'console',
host:'' (same-origin), ingestKey }). host:'' posts to the console's own
/v1/event so the first-party session cookie rides along (go:embed cloud
native; standalone BFF forwards as the signed-in user); the client NEVER
sends an org — Cloud stamps the tenant from the validated session.
- The provider references the shared client; the three existing error
boundaries (product, dashboard, global) report React render errors via
reportError() to the same stream — including the provider-less global-error
boundary, the reason the client is shared. Auto error capture (window.onerror
+ unhandledrejection) + beacon-on-unload are on by default.
- Consent + PII: PII-free by construction (anon id + the stable owner/name
actor id, never an email; org never sent) and honors an explicit GPC /
Do-Not-Track opt-out — the consent layer for logged-out/public views.
Logged-out pageviews + errors ingest with an optional publishable key
(NEXT_PUBLIC_EVENT_INGEST_KEY).
- Product moments: + AGENT_CREATED, CHAT_STARTED/CHAT_MESSAGE_SENT,
SIGNUP_COMPLETED (atop the existing PROJECT_CREATED, API_KEY_CREATED,
PRICING_VIEWED/PLAN_CLICKED/CHECKOUT_STARTED, APP_CREATED/DEPLOY_STARTED,
FIRST_ACTION).
- proxy-allow: add the `event` head so the standalone BFF forwards /v1/event.
tsc clean; vitest 2933/2933; next build + build:embed green.
Upgrade @hanzo/event ^0.2.0 -> ^0.3.1 — the ONE telemetry client that POSTs
every signal (pageview · product event · identify · error) as one batched
stream to the ONE Hanzo Cloud front door /v1/event, lensed server-side into
web analytics, product insights, and error tracking (subsumes @sentry). The
0.2.0 client posted the deprecated /v1/analytics + /v1/tracker.
- ONE shared client (src/lib/event.ts): createAnalytics({ product:'console',
host:'' (same-origin), ingestKey }). host:'' posts to the console's own
/v1/event so the first-party session cookie rides along (go:embed cloud
native; standalone BFF forwards as the signed-in user); the client NEVER
sends an org — Cloud stamps the tenant from the validated session.
- The provider references the shared client; the three existing error
boundaries (product, dashboard, global) report React render errors via
reportError() to the same stream — including the provider-less global-error
boundary, the reason the client is shared. Auto error capture (window.onerror
+ unhandledrejection) + beacon-on-unload are on by default.
- Consent + PII: PII-free by construction (anon id + the stable owner/name
actor id, never an email; org never sent) and honors an explicit GPC /
Do-Not-Track opt-out — the consent layer for logged-out/public views.
Logged-out pageviews + errors ingest with an optional publishable key
(NEXT_PUBLIC_EVENT_INGEST_KEY).
- Product moments: + AGENT_CREATED, CHAT_STARTED/CHAT_MESSAGE_SENT,
SIGNUP_COMPLETED (atop the existing PROJECT_CREATED, API_KEY_CREATED,
PRICING_VIEWED/PLAN_CLICKED/CHECKOUT_STARTED, APP_CREATED/DEPLOY_STARTED,
FIRST_ACTION).
- proxy-allow: add the `event` head so the standalone BFF forwards /v1/event.
tsc clean; vitest 2933/2933; next build + build:embed green.
The admin.hanzo.ai realtime block-storage view, so we can watch the analytics
datastore fill and scale DO storage before it runs out. One read:
StorageFleetApi.snapshot() -> GET /v1/admin/storage (the global-admin-gated
aggregate; storage added to ADMIN_AGGREGATE_HEADS + ADMIN_V1_HEADS).
- StorageFleetModule (Observe, admin:true): fleet KPIs (volumes / provisioned /
used / monthly $), the analytics datastore highlighted with a green/amber/red
fill bar + near-full badge, near-full alerts, and the full volume list.
- Honest by construction: DO gives capacity + attachment but NOT fill %, so a
volume's used/pct render an em-dash "—", never a fabricated number; the
datastore card shows only when a filesystem source (system.disks) reported fill.
- e2e (storage-fleet.spec.ts): renders the datastore (200 GiB), fleet KPIs
(295 volumes / $1,309), a 91% near-full alert, and the honest "—" — passes.
Ships to admin.hanzo.ai via the next hanzoai/cloud release embedding console@main.
Pairs with cloud GET /v1/admin/storage (DO volume inventory + system.disks fill).
The admin.hanzo.ai realtime block-storage view, so we can watch the analytics
datastore fill and scale DO storage before it runs out. One read:
StorageFleetApi.snapshot() -> GET /v1/admin/storage (the global-admin-gated
aggregate; storage added to ADMIN_AGGREGATE_HEADS + ADMIN_V1_HEADS).
- StorageFleetModule (Observe, admin:true): fleet KPIs (volumes / provisioned /
used / monthly $), the analytics datastore highlighted with a green/amber/red
fill bar + near-full badge, near-full alerts, and the full volume list.
- Honest by construction: DO gives capacity + attachment but NOT fill %, so a
volume's used/pct render an em-dash "—", never a fabricated number; the
datastore card shows only when a filesystem source (system.disks) reported fill.
- e2e (storage-fleet.spec.ts): renders the datastore (200 GiB), fleet KPIs
(295 volumes / $1,309), a 91% near-full alert, and the honest "—" — passes.
Ships to admin.hanzo.ai via the next hanzoai/cloud release embedding console@main.
Pairs with cloud GET /v1/admin/storage (DO volume inventory + system.disks fill).
Company module: the 8-step formation wizard over /v1/company (the cloud
formation state machine). Renders the panel for the formation's CURRENT
stage — the backend is the source of truth — and advances through the
guarded transition door; KYC / e-sign / state-filing report an honest
"pending — manual review" while those providers are stubs, and a founder
is shown verified only when the backend records it.
Cap Table module: the ownership dashboard over /v1/captable — the computed
summary (fully-diluted totals + ownership donut + per-class issued/authorized),
stakeholders, issued shares, share classes, and fundraising (SAFEs + rounds),
with forms to add a stakeholder, issue shares, create a class, record a SAFE,
and open a round. The cap-table math is computed server-side (the summary
route), never in the client.
Both follow the existing product-module pattern: a thin /v1 API client with
pure, unit-tested logic + defensive normalizers, a *Module.tsx over the shared
UI primitives, and one registry entry each. company + captable are added to
CLOUD_HEADS (the /v1 bearer BFF) and to ALWAYS_ON_PRODUCTS so they appear for
every logged-in org. Adds one Field primitive (FieldOptionSelect) for
entity-reference pickers.
Tests: company.test.ts + captable.test.ts (stage mapping, cap-table view
derivation, validators, normalizers) + canonical-path assertions. tsc clean,
vitest 2933/2933, next build + build:embed green.
Company module: the 8-step formation wizard over /v1/company (the cloud
formation state machine). Renders the panel for the formation's CURRENT
stage — the backend is the source of truth — and advances through the
guarded transition door; KYC / e-sign / state-filing report an honest
"pending — manual review" while those providers are stubs, and a founder
is shown verified only when the backend records it.
Cap Table module: the ownership dashboard over /v1/captable — the computed
summary (fully-diluted totals + ownership donut + per-class issued/authorized),
stakeholders, issued shares, share classes, and fundraising (SAFEs + rounds),
with forms to add a stakeholder, issue shares, create a class, record a SAFE,
and open a round. The cap-table math is computed server-side (the summary
route), never in the client.
Both follow the existing product-module pattern: a thin /v1 API client with
pure, unit-tested logic + defensive normalizers, a *Module.tsx over the shared
UI primitives, and one registry entry each. company + captable are added to
CLOUD_HEADS (the /v1 bearer BFF) and to ALWAYS_ON_PRODUCTS so they appear for
every logged-in org. Adds one Field primitive (FieldOptionSelect) for
entity-reference pickers.
Tests: company.test.ts + captable.test.ts (stage mapping, cap-table view
derivation, validators, normalizers) + canonical-path assertions. tsc clean,
vitest 2933/2933, next build + build:embed green.
Renders every admin-only view as super-admin (primeSession owner:admin) against a
mocked local server and asserts: monochrome in dark AND forced-light (the hue-220
fix — no blue cast), org search reachable, and all 28 admin views render their
shell without an error-boundary/pageerror. Screenshot per view (e2e-shots/admin-audit).
All green locally.
Renders every admin-only view as super-admin (primeSession owner:admin) against a
mocked local server and asserts: monochrome in dark AND forced-light (the hue-220
fix — no blue cast), org search reachable, and all 28 admin views render their
shell without an error-boundary/pageerror. Screenshot per view (e2e-shots/admin-audit).
All green locally.
The light theme (html:root.t_light) built its whole color scale on hsl(220 …)
— hue 220 is blue — so every surface in light mode read blue-tinted (the 'weird
blue tinge' on admin.hanzo.ai). Zeroed the saturation → pure grayscale (same
lightness ladder), and neutralized the blue-tinted (16,24,40) shadows to pure
black alpha. Dark theme was already monochrome. Now monochrome in both modes.
The light theme (html:root.t_light) built its whole color scale on hsl(220 …)
— hue 220 is blue — so every surface in light mode read blue-tinted (the 'weird
blue tinge' on admin.hanzo.ai). Zeroed the saturation → pure grayscale (same
lightness ladder), and neutralized the blue-tinted (16,24,40) shadows to pure
black alpha. Dark theme was already monochrome. Now monochrome in both modes.
- gpus-connect: BYO GB10 surfaces via /v1/fleet/workers (not /v1/machines, which
excludes provider=byo); assert Connect+Deploy CTAs + the 'hanzo gpu connect' drawer.
- entitlement-sidebar: assert the real gating contract (enabled shown / non-entitled
hidden / catalog affordance present+enabled); the AddProductPanel DetailPane is a
separate concern. Both PASS locally.
- gpus-connect: BYO GB10 surfaces via /v1/fleet/workers (not /v1/machines, which
excludes provider=byo); assert Connect+Deploy CTAs + the 'hanzo gpu connect' drawer.
- entitlement-sidebar: assert the real gating contract (enabled shown / non-entitled
hidden / catalog affordance present+enabled); the AddProductPanel DetailPane is a
separate concern. Both PASS locally.
GPU_MIN_HOURS 24 -> 1: launching a cloud GPU charges the first hour
upfront to the card instead of a 24-hour block. Card-required prepay
semantics are unchanged (commerce-enforced); only the console-owned
minimum changes. Copy + tests updated in lockstep.
GPU_MIN_HOURS 24 -> 1: launching a cloud GPU charges the first hour
upfront to the card instead of a 24-hour block. Card-required prepay
semantics are unchanged (commerce-enforced); only the console-owned
minimum changes. Copy + tests updated in lockstep.
The Base product (Bases manager + Records) went dark in the go:embed console
(console.hanzo.ai): its client hit the retired /v1/superbase BFF prefix, which
build:embed prunes, so the call fell through to the SPA shell (or 404). Point the
Base data client at same-origin '/v1' so it calls /v1/collections/* — the path
cloud now serves (clients/base/collections.go, forwarded to the managed Base) and
which the embed's webui.go routes to the cloud router. And attach the caller's PKCE
Bearer + X-Org-Id in BaseDataApi (the embed has no BFF to inject a token
server-side; cloud validates the Bearer and forwards it to the Base, which scopes
per-user/per-collection). Add 'collections' to CLOUD_HEADS so the standalone /v1
BFF forwards it too. No IS_EMBED gating needed — collections is a normal cloud head
(unlike iam/paas), reached the same way from both the embed and standalone.
Verified: tsc clean (my files); proxy-allow 34/34; base-data/bases-logic 33/33.
The Base product (Bases manager + Records) went dark in the go:embed console
(console.hanzo.ai): its client hit the retired /v1/superbase BFF prefix, which
build:embed prunes, so the call fell through to the SPA shell (or 404). Point the
Base data client at same-origin '/v1' so it calls /v1/collections/* — the path
cloud now serves (clients/base/collections.go, forwarded to the managed Base) and
which the embed's webui.go routes to the cloud router. And attach the caller's PKCE
Bearer + X-Org-Id in BaseDataApi (the embed has no BFF to inject a token
server-side; cloud validates the Bearer and forwards it to the Base, which scopes
per-user/per-collection). Add 'collections' to CLOUD_HEADS so the standalone /v1
BFF forwards it too. No IS_EMBED gating needed — collections is a normal cloud head
(unlike iam/paas), reached the same way from both the embed and standalone.
Verified: tsc clean (my files); proxy-allow 34/34; base-data/bases-logic 33/33.
/agents showed empty Status/Logs/Metrics despite agents + runs existing: the product
only owned the '' (Overview) route, so those base slugs fell to the shared subpage system
which reads o11y (not wired for agents) + the usage ledger (no product:agents-tagged spend)
→ honest-empty. But the data IS there in /v1/agents (invocations, health, activity).
Agents now OWNS Status/Logs/Metrics (registry subpages + :tab route, same pattern as
Inference). AgentsModule renders a focused slice per tab from its OWN derived data:
Metrics = counts + invocation trend + resource usage; Status = health donut + agents table;
Logs = the invocation activity feed; Overview = all. Settings stays the shared subpage.
tsc clean (my files); the AppLauncher/brands tsc errors are pre-existing main, not this.
/agents showed empty Status/Logs/Metrics despite agents + runs existing: the product
only owned the '' (Overview) route, so those base slugs fell to the shared subpage system
which reads o11y (not wired for agents) + the usage ledger (no product:agents-tagged spend)
→ honest-empty. But the data IS there in /v1/agents (invocations, health, activity).
Agents now OWNS Status/Logs/Metrics (registry subpages + :tab route, same pattern as
Inference). AgentsModule renders a focused slice per tab from its OWN derived data:
Metrics = counts + invocation trend + resource usage; Status = health donut + agents table;
Logs = the invocation activity feed; Overview = all. Settings stays the shared subpage.
tsc clean (my files); the AppLauncher/brands tsc errors are pre-existing main, not this.
All our code in ONE place. The former Git (repo host, /v1/git) and Code
(intelligence, /v1/code HIP-0302) Dev products fold into a single "Code" hub —
one nav entry, DRY, brand-agnostic (org-scoped SERVER-SIDE, no cross-brand leak).
- Repositories face (git/RepoList): every repo the caller can see, GROUPED by org
(header only when >1), a ReDoS-safe LITERAL filter, "Last synced"
(repoView.updatedAt — advances on every mirror fast-forward, the honest freshness
signal), default branch + size; rows open the repo browser. Honest empty/error.
- Search + Ask faces (code/IntelligenceFaces): hybrid cross-repo retrieval + cited
answers over the EXISTING /v1/code engine (reuse, not a new /v1/git/search — one
search engine, one way). A hit or a citation DEEP-LINKS into the file in the repo
browser (the search->browse seam). Empty state states index-on-push truthfully.
- Repo browser (git/RepoBrowser + CodeView) rebased under /code/repos/:name, plus
AGENTIC handoffs: repo-level Ask AI · Edit · Chat, file-level Ask AI — reusing the
canonical cross-surface deep links (hanzo.app/dev?project= , hanzo.chat/?project=)
and the built-in assistant (useFloatingChat().ask seeds the composer with repo/file
context; never auto-sends).
- Registry: `code` -> hub (subpages repos/search/ask; routes ''/:tab/repos/:name);
standalone `git` entry removed and aliased git->code (no legacy 404). GitModule
deleted (folded).
Pure logic in code/hub-logic.ts (filter/group/deep-links/seed prompts) with tests.
tsc clean · vitest 2856 green · next build ok · build:embed ok (out/ + index.html).
All our code in ONE place. The former Git (repo host, /v1/git) and Code
(intelligence, /v1/code HIP-0302) Dev products fold into a single "Code" hub —
one nav entry, DRY, brand-agnostic (org-scoped SERVER-SIDE, no cross-brand leak).
- Repositories face (git/RepoList): every repo the caller can see, GROUPED by org
(header only when >1), a ReDoS-safe LITERAL filter, "Last synced"
(repoView.updatedAt — advances on every mirror fast-forward, the honest freshness
signal), default branch + size; rows open the repo browser. Honest empty/error.
- Search + Ask faces (code/IntelligenceFaces): hybrid cross-repo retrieval + cited
answers over the EXISTING /v1/code engine (reuse, not a new /v1/git/search — one
search engine, one way). A hit or a citation DEEP-LINKS into the file in the repo
browser (the search->browse seam). Empty state states index-on-push truthfully.
- Repo browser (git/RepoBrowser + CodeView) rebased under /code/repos/:name, plus
AGENTIC handoffs: repo-level Ask AI · Edit · Chat, file-level Ask AI — reusing the
canonical cross-surface deep links (hanzo.app/dev?project= , hanzo.chat/?project=)
and the built-in assistant (useFloatingChat().ask seeds the composer with repo/file
context; never auto-sends).
- Registry: `code` -> hub (subpages repos/search/ask; routes ''/:tab/repos/:name);
standalone `git` entry removed and aliased git->code (no legacy 404). GitModule
deleted (folded).
Pure logic in code/hub-logic.ts (filter/group/deep-links/seed prompts) with tests.
tsc clean · vitest 2856 green · next build ok · build:embed ok (out/ + index.html).
console.hanzo.ai/cloud.hanzo.ai serve the go:embed console inside the cloud binary,
whose webui.go serves the SPA index (HTTP 200 HTML) for any non-/v1/ path. build-embed
stashes the Next BFF route handlers, so the OrgSwitcher (/admin/iam) and Observe->Status
(/paas) client calls fell through to the SPA shell and threw 'Invalid response from
server (HTTP 200)' -> missing switcher + 'Could not reach the platform'.
Cloud already serves the equivalents natively at /v1/iam/* and /v1/paas/*, so in the
embed (IS_EMBED) the IAM-admin client uses client.ts iamList/iamOne/iamMutate and the
PaaS inventory uses cloudProxyV1Url('paas/...'). Standalone console2/admin.hanzo.ai are
UNCHANGED (their /v1 BFF deliberately excludes iam/* and paas/*). Scoping unchanged.
tsc clean (2 files); vitest 109 baseline + 3 new embed-path assertions.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
console.hanzo.ai/cloud.hanzo.ai serve the go:embed console inside the cloud binary,
whose webui.go serves the SPA index (HTTP 200 HTML) for any non-/v1/ path. build-embed
stashes the Next BFF route handlers, so the OrgSwitcher (/admin/iam) and Observe->Status
(/paas) client calls fell through to the SPA shell and threw 'Invalid response from
server (HTTP 200)' -> missing switcher + 'Could not reach the platform'.
Cloud already serves the equivalents natively at /v1/iam/* and /v1/paas/*, so in the
embed (IS_EMBED) the IAM-admin client uses client.ts iamList/iamOne/iamMutate and the
PaaS inventory uses cloudProxyV1Url('paas/...'). Standalone console2/admin.hanzo.ai are
UNCHANGED (their /v1 BFF deliberately excludes iam/* and paas/*). Scoping unchanged.
tsc clean (2 files); vitest 109 baseline + 3 new embed-path assertions.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Collapse the six-deep AuthGate → WaitlistGate → OrgGate → ScopeProvider → … →
OnboardingGate → DashboardShell chain into ONE pure resolver, one flat switch, and a
flat provider list. The whole entry decision is now a VALUE, rendered once.
- src/entry/resolve.ts: pure resolve(session) → signin|waitlist|org|onboard|ready. No JSX,
unit-tested (resolve.test.ts). Fail-closed lives here: `ready` (the app + its data) is
reachable ONLY for a loaded, authenticated, org-ENTERED session — proven by exhaustive
sweeps that resolve NEVER yields ready for a loading/anon/org-less session.
- src/entry/entry.tsx: gathers the session with hooks, resolves ONE stage, renders exactly
one surface via a flat switch.
- Self-contained stage views (no cross-imports): auth.tsx, waitlist.tsx, scope.tsx,
onboard.tsx, dashboard.tsx.
- src/entry/providers.tsx: the ready-only app-shell context as ONE flat ordered list
(reduceRight), mounted only at `ready`. Preferences + Toast (read by the resolver / the
onboard wizard / every module) sit above the switch.
- Drop compound suffixes (hooks unchanged): AuthGate→Auth, WaitlistGate→Waitlist,
OrgGate+ScopeProvider→Scope, OnboardingGate→Onboard, DashboardShell→Dashboard,
AppLauncherProvider→Launcher, PreferencesProvider→Preferences, CommandPaletteProvider→Palette,
FloatingChatProvider→Chat, ToastProvider→Toast, DetailPaneProvider→DetailPane.
- Delete the dead gate components; sweep stale names from comments. Same auth/waitlist/org/
onboard semantics + white-label brand-per-host intact — structure + names only.
tsc --noEmit clean; vitest 2868/2868; next build ✓ (compiled + type-checked).
Collapse the six-deep AuthGate → WaitlistGate → OrgGate → ScopeProvider → … →
OnboardingGate → DashboardShell chain into ONE pure resolver, one flat switch, and a
flat provider list. The whole entry decision is now a VALUE, rendered once.
- src/entry/resolve.ts: pure resolve(session) → signin|waitlist|org|onboard|ready. No JSX,
unit-tested (resolve.test.ts). Fail-closed lives here: `ready` (the app + its data) is
reachable ONLY for a loaded, authenticated, org-ENTERED session — proven by exhaustive
sweeps that resolve NEVER yields ready for a loading/anon/org-less session.
- src/entry/entry.tsx: gathers the session with hooks, resolves ONE stage, renders exactly
one surface via a flat switch.
- Self-contained stage views (no cross-imports): auth.tsx, waitlist.tsx, scope.tsx,
onboard.tsx, dashboard.tsx.
- src/entry/providers.tsx: the ready-only app-shell context as ONE flat ordered list
(reduceRight), mounted only at `ready`. Preferences + Toast (read by the resolver / the
onboard wizard / every module) sit above the switch.
- Drop compound suffixes (hooks unchanged): AuthGate→Auth, WaitlistGate→Waitlist,
OrgGate+ScopeProvider→Scope, OnboardingGate→Onboard, DashboardShell→Dashboard,
AppLauncherProvider→Launcher, PreferencesProvider→Preferences, CommandPaletteProvider→Palette,
FloatingChatProvider→Chat, ToastProvider→Toast, DetailPaneProvider→DetailPane.
- Delete the dead gate components; sweep stale names from comments. Same auth/waitlist/org/
onboard semantics + white-label brand-per-host intact — structure + names only.
tsc --noEmit clean; vitest 2868/2868; next build ✓ (compiled + type-checked).
isAdminHost(host) gate: the operator cockpit keeps its silent-SSO bounce; only
consumer hosts (cloud/console/tenant) show the marketing landing at / for anon.
isAdminHost(host) gate: the operator cockpit keeps its silent-SSO bounce; only
consumer hosts (cloud/console/tenant) show the marketing landing at / for anon.
Unauthenticated visitors at / get a marketing page (gather interest + explain the
product) instead of a bounce to /signin — served by the SAME one cloud binary that
serves the signed-in console (no separate marketing service). AuthGate gains a
'landing' surface: anon-at-/ → PublicLanding, signed-in-at-/ → console. Landing
content is derived from the real taxonomy (categoriesForBrand + CATEGORY_SUMMARY),
brand-scoped via getBrand, with the ONE sign-in CTA (/signin).
Unauthenticated visitors at / get a marketing page (gather interest + explain the
product) instead of a bounce to /signin — served by the SAME one cloud binary that
serves the signed-in console (no separate marketing service). AuthGate gains a
'landing' surface: anon-at-/ → PublicLanding, signed-in-at-/ → console. Landing
content is derived from the real taxonomy (categoriesForBrand + CATEGORY_SUMMARY),
brand-scoped via getBrand, with the ONE sign-in CTA (/signin).
Expand the bottom Developers dock from 3 tabs to the full developer surface,
each org-scoped, wired to REAL data or an honest empty/coming/runtime state,
each mounted only while active (lazy):
- Overview enhanced: request volume + error rate + tokens/spend (charged
ledger) + the account Cloud API key (KeysApi) + API v1 + dev-resource links.
- Logs filterable + row -> JSON detail (real usage ledger).
- Events platform-event stream projected from the same real ledger.
- Webhooks event destinations: real rows when the endpoint API is live, else
the honest create-first-destination state (forward-compatible).
- Health Alerts/Errors/Insights from the o11y runtime (ApmApi + o11y rules;
honest RuntimeNotice when o11y isn't routed for the org).
- Inspector fetch any object by id -> JSON + related ledger activity.
- Traces the existing TracesModule embedded.
- Shell enhanced: resource picker + show-code (curl/CLI).
Tab bodies live in tabs.tsx; Workbench.tsx is the dock shell owning the shared
usage fetch. Preserves the collapse/expand + Developers bar affordance and the
existing e2e contract (bar text, Overview/Logs/Shell labels, shell aria-label).
Expand the bottom Developers dock from 3 tabs to the full developer surface,
each org-scoped, wired to REAL data or an honest empty/coming/runtime state,
each mounted only while active (lazy):
- Overview enhanced: request volume + error rate + tokens/spend (charged
ledger) + the account Cloud API key (KeysApi) + API v1 + dev-resource links.
- Logs filterable + row -> JSON detail (real usage ledger).
- Events platform-event stream projected from the same real ledger.
- Webhooks event destinations: real rows when the endpoint API is live, else
the honest create-first-destination state (forward-compatible).
- Health Alerts/Errors/Insights from the o11y runtime (ApmApi + o11y rules;
honest RuntimeNotice when o11y isn't routed for the org).
- Inspector fetch any object by id -> JSON + related ledger activity.
- Traces the existing TracesModule embedded.
- Shell enhanced: resource picker + show-code (curl/CLI).
Tab bodies live in tabs.tsx; Workbench.tsx is the dock shell owning the shared
usage fetch. Preserves the collapse/expand + Developers bar affordance and the
existing e2e contract (bar text, Overview/Logs/Shell labels, shell aria-label).
Extend the workbench logic (node-testable, no React/gui imports):
- inspectorRoute(id): id-prefix (agent_/fn_/flow_/run_/prompt_/trace_, hk-/sk-/pk-)
or raw resource/name path -> the same-origin /v1 GET; URL/traversal refused.
- curlFor/hanzoCli: the same read as curl (Bearer hk-) and the Hanzo CLI.
- eventsFrom(records): project the real usage ledger into a platform-event stream.
+8 tests.
Extend the workbench logic (node-testable, no React/gui imports):
- inspectorRoute(id): id-prefix (agent_/fn_/flow_/run_/prompt_/trace_, hk-/sk-/pk-)
or raw resource/name path -> the same-origin /v1 GET; URL/traversal refused.
- curlFor/hanzoCli: the same read as curl (Bearer hk-) and the Hanzo CLI.
- eventsFrom(records): project the real usage ledger into a platform-event stream.
+8 tests.
'Apps button / ⌘K doesn't show all apps.' ROOT: both browse-all surfaces were braided
with entitlement — AppLauncher passed the org's `enabled` set to visibleCatalogByCategory
and filterEntitled, and ⌘K passed it to searchDestinations, so a non-superadmin org only
saw its always-on + enabled subset (the launcher 'mirrored the sidebar scope').
DECOMPLECT: the Apps launcher and ⌘K are DISCOVERY surfaces — 'browse ALL apps' means the
WHOLE catalog. Entitlement is a property of USING a product (the sidebar = your workspace
nav, and the product page's honest 'enable for your org' state), NOT of SEEING it in the
directory. So both now render visibleCatalogByCategory(showAdmin, null) / searchDestinations
(query, showAdmin, null) — full catalog, admin-gated only (internal operator surfaces stay
behind showAdmin). The sidebar + product-use remain entitlement-scoped, unchanged.
tsc clean; 180 product/entitlement tests green (the filterEntitled/entitledSet functions are
untouched — still used by the sidebar; only the discovery callers stop scoping).
'Apps button / ⌘K doesn't show all apps.' ROOT: both browse-all surfaces were braided
with entitlement — AppLauncher passed the org's `enabled` set to visibleCatalogByCategory
and filterEntitled, and ⌘K passed it to searchDestinations, so a non-superadmin org only
saw its always-on + enabled subset (the launcher 'mirrored the sidebar scope').
DECOMPLECT: the Apps launcher and ⌘K are DISCOVERY surfaces — 'browse ALL apps' means the
WHOLE catalog. Entitlement is a property of USING a product (the sidebar = your workspace
nav, and the product page's honest 'enable for your org' state), NOT of SEEING it in the
directory. So both now render visibleCatalogByCategory(showAdmin, null) / searchDestinations
(query, showAdmin, null) — full catalog, admin-gated only (internal operator surfaces stay
behind showAdmin). The sidebar + product-use remain entitlement-scoped, unchanged.
tsc clean; 180 product/entitlement tests green (the filterEntitled/entitledSet functions are
untouched — still used by the sidebar; only the discovery callers stop scoping).
AppLauncher's cross-surface tiles now come from the ONE @hanzo/ui surfaces list
(otherSurfaces('console') = every surface but this one), each with a distinct
icon — replacing the hardcoded team+billing pair. Bumps @hanzo/ui to 8.0.6.
AppLauncher's cross-surface tiles now come from the ONE @hanzo/ui surfaces list
(otherSurfaces('console') = every surface but this one), each with a distinct
icon — replacing the hardcoded team+billing pair. Bumps @hanzo/ui to 8.0.6.
hanzo-build-linux-amd64 arc pool is repaired (recreated scale-set cleared the stuck
GitHub message session that was thrashing runners; restored the custom runner image
and the shared arc-github-secret). Drop the temporary hanzo-deploy override.
hanzo-build-linux-amd64 arc pool is repaired (recreated scale-set cleared the stuck
GitHub message session that was thrashing runners; restored the custom runner image
and the shared arc-github-secret). Drop the temporary hanzo-deploy override.
console.hanzo.ai silent-SSO-looped: the hanzo-cloud IAM app issues tokens with no
configured lifetime, so the token response omits expires_in. @hanzo/iam@0.13.6
storeTokens() only writes hanzo_iam_expires_at WHEN expires_in is present (no else),
so isTokenExpired() returns true forever → getValidAccessToken() returns null → a
freshly-minted token reads as expired → endless authorize redirects (~128/min).
patch-package adds the missing else to all 6 SDK bundles: when expires_in is absent,
fall back to the access token's own JWT exp claim (RFC 7519) — authoritative for IAM's
JWTs, correct on the initial exchange AND every refresh. + patch-package postinstall so
CI applies it on npm ci. (SDK repo is badly diverged from the published 0.13.6, so a
republish would regress; patching the exact published bundle is the zero-regression fix.)
console.hanzo.ai silent-SSO-looped: the hanzo-cloud IAM app issues tokens with no
configured lifetime, so the token response omits expires_in. @hanzo/iam@0.13.6
storeTokens() only writes hanzo_iam_expires_at WHEN expires_in is present (no else),
so isTokenExpired() returns true forever → getValidAccessToken() returns null → a
freshly-minted token reads as expired → endless authorize redirects (~128/min).
patch-package adds the missing else to all 6 SDK bundles: when expires_in is absent,
fall back to the access token's own JWT exp claim (RFC 7519) — authoritative for IAM's
JWTs, correct on the initial exchange AND every refresh. + patch-package postinstall so
CI applies it on npm ci. (SDK repo is badly diverged from the published 0.13.6, so a
republish would regress; patching the exact published bundle is the zero-regression fix.)
hanzo-build-linux-amd64 runners are stuck (empty-image drift on the live
AutoscalingRunnerSet + a duplicate listener; ephemeral runners churn Pending
without consuming the queued jobs), wedging every hanzoai build on that label.
Point the console CI/CD at the healthy hanzo-deploy-linux-amd64 pool so the
console-embed artifact (carrying the login-loop fix 975bb1729) rebuilds now.
Temporary — revert to the default pool once hanzo-build is repaired.
hanzo-build-linux-amd64 runners are stuck (empty-image drift on the live
AutoscalingRunnerSet + a duplicate listener; ephemeral runners churn Pending
without consuming the queued jobs), wedging every hanzoai build on that label.
Point the console CI/CD at the healthy hanzo-deploy-linux-amd64 pool so the
console-embed artifact (carrying the login-loop fix e24869c3f) rebuilds now.
Temporary — revert to the default pool once hanzo-build is repaired.
The @hanzo/iam SDK's getValidAccessToken() returns null when the token-exchange
response carried no `expires_in` (the hanzo-cloud IAM app has no token lifetime set)
and no refresh token was issued — it flags the freshly-minted token expired even
though IAM accepts it (userinfo 200). That null dead-ended AccountApi.session() ->
account=null and looped /signin (~128 POST /login/oauth per minute). Fall back to the
raw stored token at the wrapper boundary; account.ts and the refresh timer are
unchanged (expiry still derived from the token's own exp).
The @hanzo/iam SDK's getValidAccessToken() returns null when the token-exchange
response carried no `expires_in` (the hanzo-cloud IAM app has no token lifetime set)
and no refresh token was issued — it flags the freshly-minted token expired even
though IAM accepts it (userinfo 200). That null dead-ended AccountApi.session() ->
account=null and looped /signin (~128 POST /login/oauth per minute). Fall back to the
raw stored token at the wrapper boundary; account.ts and the refresh timer are
unchanged (expiry still derived from the token's own exp).
console.hanzo.ai is a Next static export served as an SPA shell — the Go embed
serves the / route's index.html (the (dashboard) tree, guarded by <AuthGate/>)
for EVERY path (/, /signin, /auth/callback are byte-identical). A hard nav to
/auth/callback?code=… therefore mounts <AuthGate/>, NOT app/auth/callback/page —
AuthGate special-cased /signin but not the callback, so it fired
router.replace('/signin') before the PKCE code→token exchange could run. The
?code was discarded and sign-in dead-looped (the console-login P0).
Extend the existing /signin SPA-fallback pattern to the callback: AuthGate now
renders <AuthCallback/> for /auth/callback, completing handleCallback() BEFORE the
guard. Callback logic is extracted into one shared component used by both the
route and the gate (no duplication).
Fixes console.hanzo.ai login never completing.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
console.hanzo.ai is a Next static export served as an SPA shell — the Go embed
serves the / route's index.html (the (dashboard) tree, guarded by <AuthGate/>)
for EVERY path (/, /signin, /auth/callback are byte-identical). A hard nav to
/auth/callback?code=… therefore mounts <AuthGate/>, NOT app/auth/callback/page —
AuthGate special-cased /signin but not the callback, so it fired
router.replace('/signin') before the PKCE code→token exchange could run. The
?code was discarded and sign-in dead-looped (the console-login P0).
Extend the existing /signin SPA-fallback pattern to the callback: AuthGate now
renders <AuthCallback/> for /auth/callback, completing handleCallback() BEFORE the
guard. Callback logic is extracted into one shared component used by both the
route and the gate (no duplication).
Fixes console.hanzo.ai login never completing.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
iamSdk().getUserInfo() returns null on a 200 in the deployed SDK, so AccountApi.session()
dead-ended before accountFromClaims and looped /signin for everyone. Decode the account
from the access-token JWT directly (always carries >= sub); userinfo is now only a
fallback. Combined with the owner/config-org fallback, a valid token can't dead-end.
iamSdk().getUserInfo() returns null on a 200 in the deployed SDK, so AccountApi.session()
dead-ended before accountFromClaims and looped /signin for everyone. Decode the account
from the access-token JWT directly (always carries >= sub); userinfo is now only a
fallback. Combined with the owner/config-org fallback, a valid token can't dead-end.
Backend (hanzoai/ai) renamed the router-config routes to resource-oriented
nouns and DROPPED the old compound routes (no aliases, no backwards compat).
Move every console caller in lockstep so nothing 404s after ship:
GET /v1/get-router-policy -> GET /v1/router/policy
POST /v1/update-router-policy -> PUT /v1/router/policy (verb -> PUT)
GET /v1/get-routing-defaults -> GET /v1/router/defaults
GET /v1/get-org-settings -> GET /v1/org/settings
POST /v1/update-org-settings -> PUT /v1/org/settings (upsert, PATCH-merge)
POST /v1/delete-org-settings -> DELETE /v1/org/settings
GET /v1/get-org-settings-list -> GET /v1/org/settings/list
- api/router.ts: RouterPolicyApi.get->originGet('router/policy'),
save->originPut('router/policy') (PUT, not POST).
- api/org-settings.ts + api/org-blend.ts: originGet('org/settings'),
originPut/originDelete; the read-modify-write still sends the full row
(safe under the backend's new PATCH-merge PUT).
- next.config.mjs: drop the dead get-/update- heads; 'router' head already
covers /v1/router/*; TARGETED /v1/org/settings* rewrites (an 'org' head would
hijack platform /v1/org/{org}/cluster).
- app/ai/[...path] ALLOWED: swap old exact paths for router/policy +
org/settings + org/settings/list.
- ai-accounts/routing-defaults route: UPSTREAM_PATH -> v1/router/defaults.
- e2e/router-config.spec.ts: GET+PUT dispatched on the one /v1/router/policy
noun; models-surfaces mock -> /v1/org/settings. Doc/hint sweep.
tsc --noEmit clean; next build + build:embed green.
Backend (hanzoai/ai) renamed the router-config routes to resource-oriented
nouns and DROPPED the old compound routes (no aliases, no backwards compat).
Move every console caller in lockstep so nothing 404s after ship:
GET /v1/get-router-policy -> GET /v1/router/policy
POST /v1/update-router-policy -> PUT /v1/router/policy (verb -> PUT)
GET /v1/get-routing-defaults -> GET /v1/router/defaults
GET /v1/get-org-settings -> GET /v1/org/settings
POST /v1/update-org-settings -> PUT /v1/org/settings (upsert, PATCH-merge)
POST /v1/delete-org-settings -> DELETE /v1/org/settings
GET /v1/get-org-settings-list -> GET /v1/org/settings/list
- api/router.ts: RouterPolicyApi.get->originGet('router/policy'),
save->originPut('router/policy') (PUT, not POST).
- api/org-settings.ts + api/org-blend.ts: originGet('org/settings'),
originPut/originDelete; the read-modify-write still sends the full row
(safe under the backend's new PATCH-merge PUT).
- next.config.mjs: drop the dead get-/update- heads; 'router' head already
covers /v1/router/*; TARGETED /v1/org/settings* rewrites (an 'org' head would
hijack platform /v1/org/{org}/cluster).
- app/ai/[...path] ALLOWED: swap old exact paths for router/policy +
org/settings + org/settings/list.
- ai-accounts/routing-defaults route: UPSTREAM_PATH -> v1/router/defaults.
- e2e/router-config.spec.ts: GET+PUT dispatched on the one /v1/router/policy
noun; models-surfaces mock -> /v1/org/settings. Doc/hint sweep.
tsc --noEmit clean; next build + build:embed green.
The deployed OIDC /v1/iam/userinfo omits `owner` and `sub` is the user UUID, so
accountFromClaims returned null for every valid session and looped /signin. Resolve
owner: owner/organization claim -> sub-prefix -> config.iamOrgName. Also fall back
name to email. A valid IAM session can no longer dead-end.
The deployed OIDC /v1/iam/userinfo omits `owner` and `sub` is the user UUID, so
accountFromClaims returned null for every valid session and looped /signin. Resolve
owner: owner/organization claim -> sub-prefix -> config.iamOrgName. Also fall back
name to email. A valid IAM session can no longer dead-end.
accountFromClaims required an `owner` claim, but OIDC /v1/iam/userinfo only
returns sub/preferred_username/name/email (no owner). Every login resolved to
account=null and looped back to /signin. `sub` is `owner/name`, so derive owner
from it exactly as `name` already is.
accountFromClaims required an `owner` claim, but OIDC /v1/iam/userinfo only
returns sub/preferred_username/name/email (no owner). Every login resolved to
account=null and looped back to /signin. `sub` is `owner/name`, so derive owner
from it exactly as `name` already is.
Re-run scripts/sync-benchmarks.mjs so the checked-in corpus fixture picks up the
enso family (enso-ultra/enso/enso-flash, hanzo-measured) and the provider-reported
relabel from priors/leaderboard.json.
Leaderboard gains a Source filter (All / Hanzo-measured / Vendor-reported) over a
pure sourceClass() classifier in the one reader, badges every row by class
(Enso / Hanzo-measured / reported), and shows the three Enso tiers side by side —
monotonic Ultra 92.9 > Pro 87.9 > Flash 75.8 GPQA, priced from the same corpus.
Honest by construction: enso ranks on merit (never floated to #1), tiers render
only when the corpus carries them, unscored rows stay omitted.
Re-run scripts/sync-benchmarks.mjs so the checked-in corpus fixture picks up the
enso family (enso-ultra/enso/enso-flash, hanzo-measured) and the provider-reported
relabel from priors/leaderboard.json.
Leaderboard gains a Source filter (All / Hanzo-measured / Vendor-reported) over a
pure sourceClass() classifier in the one reader, badges every row by class
(Enso / Hanzo-measured / reported), and shows the three Enso tiers side by side —
monotonic Ultra 92.9 > Pro 87.9 > Flash 75.8 GPQA, priced from the same corpus.
Honest by construction: enso ranks on merit (never floated to #1), tiers render
only when the corpus carries them, unscored rows stay omitted.
Re-run scripts/sync-benchmarks.mjs so the checked-in corpus fixture picks up the
enso family (enso-ultra/enso/enso-flash, hanzo-measured) and the provider-reported
relabel from priors/leaderboard.json.
Leaderboard gains a Source filter (All / Hanzo-measured / Vendor-reported) over a
pure sourceClass() classifier in the one reader, badges every row by class
(Enso / Hanzo-measured / reported), and shows the three Enso tiers side by side —
monotonic Ultra 92.9 > Pro 87.9 > Flash 75.8 GPQA, priced from the same corpus.
Honest by construction: enso ranks on merit (never floated to #1), tiers render
only when the corpus carries them, unscored rows stay omitted.
Re-run scripts/sync-benchmarks.mjs so the checked-in corpus fixture picks up the
enso family (enso-ultra/enso/enso-flash, hanzo-measured) and the provider-reported
relabel from priors/leaderboard.json.
Leaderboard gains a Source filter (All / Hanzo-measured / Vendor-reported) over a
pure sourceClass() classifier in the one reader, badges every row by class
(Enso / Hanzo-measured / reported), and shows the three Enso tiers side by side —
monotonic Ultra 92.9 > Pro 87.9 > Flash 75.8 GPQA, priced from the same corpus.
Honest by construction: enso ranks on merit (never floated to #1), tiers render
only when the corpus carries them, unscored rows stay omitted.
Extend the Router > Policy editor (RouterPolicyEditor) with the two org-router
controls the auto-router (Enso) needs, round-tripped through the existing
GET/POST /v1/{get,update}-router-policy:
- Enabled models: a checklist populated from the policy's servable `available`
set (shows name, submits id); Select all / Clear; empty selection = ALL models
allowed (labelled clearly).
- Savings<->quality dial: a labeled 0..1 slider (step 0.05) via FieldSlider;
0 = savings, 1 = quality, 0.5 = balanced; null/unset renders balanced.
Preserves prefer + costCeiling on save. RouterPolicy gains enabledModels /
qualityBias / available (RouterModel). The auto-routing ON/OFF toggle stays a
separate concern on the Smart-routing (ai-accounts) surface — not duplicated.
Playwright-verified (e2e/router-config.spec.ts, 3/3): panel renders, Select-all/
Clear re-count live, Save POSTs enabledModels + qualityBias (contract proof),
mobile no horizontal scroll. tsc clean; vitest 2751 pass; next build + build:embed green.
Extend the Router > Policy editor (RouterPolicyEditor) with the two org-router
controls the auto-router (Enso) needs, round-tripped through the existing
GET/POST /v1/{get,update}-router-policy:
- Enabled models: a checklist populated from the policy's servable `available`
set (shows name, submits id); Select all / Clear; empty selection = ALL models
allowed (labelled clearly).
- Savings<->quality dial: a labeled 0..1 slider (step 0.05) via FieldSlider;
0 = savings, 1 = quality, 0.5 = balanced; null/unset renders balanced.
Preserves prefer + costCeiling on save. RouterPolicy gains enabledModels /
qualityBias / available (RouterModel). The auto-routing ON/OFF toggle stays a
separate concern on the Smart-routing (ai-accounts) surface — not duplicated.
Playwright-verified (e2e/router-config.spec.ts, 3/3): panel renders, Select-all/
Clear re-count live, Save POSTs enabledModels + qualityBias (contract proof),
mobile no horizontal scroll. tsc clean; vitest 2751 pass; next build + build:embed green.
brands.ts stops duplicating the fleet brand data (lux/zoo/pars identity +
marks were re-typed here) — it now adapts @hanzo/brand/registry's
BrandIdentity onto the console Brand shape. Host resolution stays in ~/config
(SSR default + IAM app wiring untouched → zero auth-path change). Marks are
byte-identical (the registry carries the same console v1 currentColor marks),
so zero visual regression; getBrand() signature unchanged, all 8 consumers
unaffected. Drift-fix: Hanzo orgName 'Hanzo Industries Inc.' -> 'Hanzo AI Inc.'
(matches brand.json/legalEntity; not rendered in console).
typecheck (tsc --noEmit) green. Needs @hanzo/brand@^1.4.0 published + npm
install to update the lock (deploy-gate).
brands.ts stops duplicating the fleet brand data (lux/zoo/pars identity +
marks were re-typed here) — it now adapts @hanzo/brand/registry's
BrandIdentity onto the console Brand shape. Host resolution stays in ~/config
(SSR default + IAM app wiring untouched → zero auth-path change). Marks are
byte-identical (the registry carries the same console v1 currentColor marks),
so zero visual regression; getBrand() signature unchanged, all 8 consumers
unaffected. Drift-fix: Hanzo orgName 'Hanzo Industries Inc.' -> 'Hanzo AI Inc.'
(matches brand.json/legalEntity; not rendered in console).
typecheck (tsc --noEmit) green. Needs @hanzo/brand@^1.4.0 published + npm
install to update the lock (deploy-gate).
The catalog was driven entirely by the live gateway, so a full backend outage or an
unrouted pricing endpoint left the Models surface empty behind an error card rather
than a browsable list. This adds a versioned fixture, catalog.data.json, synced from
hanzoai/enso-bench priors/openrouter_models.json by scripts/sync-models.mjs and imported
at build time, as the guaranteed base of the one fetchCatalog. The reason it is a fixture
rather than an endpoint is the same reason the benchmark corpus is: it is a versioned
artefact that changes when a catalog sync lands, not per request, so an endpoint would
buy nothing and cost a loading state, a failure mode, and a fabrication risk on every
page view.
Each of the roughly three hundred forty rows carries the model id, vendor, context
window, both sides of the per-Mtok price, and the capability flags read from the prior's
own fields, so the Vision badge and the detail feature chips are derived, never guessed.
No description is emitted because the prior carries none, and an em-dash is more honest
than a fabricated blurb. Benchmark scores continue to come from the enso-bench leaderboard
corpus, which already excludes the degraded blank-heavy runs the summary marks, so a
model without a published score renders an em-dash and never a zero.
fetchCatalog now merges the fixture base with the live rich pricing catalog and the live
routing set in increasing order of authority, so live pricing always wins where it exists
and the fixture only fills what the live catalog omits. It no longer throws when the
gateway is unreachable; it degrades to the fixture with every model honestly marked
Catalog rather than Live. Vendor logos and blend semantics are unchanged.
The catalog was driven entirely by the live gateway, so a full backend outage or an
unrouted pricing endpoint left the Models surface empty behind an error card rather
than a browsable list. This adds a versioned fixture, catalog.data.json, synced from
hanzoai/enso-bench priors/openrouter_models.json by scripts/sync-models.mjs and imported
at build time, as the guaranteed base of the one fetchCatalog. The reason it is a fixture
rather than an endpoint is the same reason the benchmark corpus is: it is a versioned
artefact that changes when a catalog sync lands, not per request, so an endpoint would
buy nothing and cost a loading state, a failure mode, and a fabrication risk on every
page view.
Each of the roughly three hundred forty rows carries the model id, vendor, context
window, both sides of the per-Mtok price, and the capability flags read from the prior's
own fields, so the Vision badge and the detail feature chips are derived, never guessed.
No description is emitted because the prior carries none, and an em-dash is more honest
than a fabricated blurb. Benchmark scores continue to come from the enso-bench leaderboard
corpus, which already excludes the degraded blank-heavy runs the summary marks, so a
model without a published score renders an em-dash and never a zero.
fetchCatalog now merges the fixture base with the live rich pricing catalog and the live
routing set in increasing order of authority, so live pricing always wins where it exists
and the fixture only fills what the live catalog omits. It no longer throws when the
gateway is unreachable; it degrades to the fixture with every model honestly marked
Catalog rather than Live. Vendor logos and blend semantics are unchanged.
Replace @hanzo/iam-js-sdk with @hanzo/iam and route the entire client
sign-in through one redirect + PKCE flow where IAM owns every credential
step. Mount <IamProvider> at the root; the sign-in screen is one
"Log in with Hanzo" button (useIam().login()) and /auth/callback completes
the PKCE token exchange (useIam().handleCallback()).
The session provider, account resolution, and API client now read the IAM
identity: the API client carries the IAM access token as a Bearer on every
/v1 call (cloud SanitizeIdentity validates the JWT), the account is
projected from the IAM userinfo claims, and refreshSession delegates to the
SDK's rotating refresh grant. No session cookie, no confidential-client
BFF code->cookie exchange, no ROPC.
Strip the non-IAM login mechanisms:
- inline email/password + social-button form (SignInForm) and its wrapper
- ROPC /v1/iam/login (iam-login) + hand-rolled PKCE (pkce)
- server-driven provider list (providers) and signup BFF (signup)
- the /auth/refresh, /auth/signin, /auth/signup BFF endpoint routes
- the old @hanzo/iam-js-sdk Sdk wrapper
tsc --noEmit clean; next build and build:embed both green.
Replace @hanzo/iam-js-sdk with @hanzo/iam and route the entire client
sign-in through one redirect + PKCE flow where IAM owns every credential
step. Mount <IamProvider> at the root; the sign-in screen is one
"Log in with Hanzo" button (useIam().login()) and /auth/callback completes
the PKCE token exchange (useIam().handleCallback()).
The session provider, account resolution, and API client now read the IAM
identity: the API client carries the IAM access token as a Bearer on every
/v1 call (cloud SanitizeIdentity validates the JWT), the account is
projected from the IAM userinfo claims, and refreshSession delegates to the
SDK's rotating refresh grant. No session cookie, no confidential-client
BFF code->cookie exchange, no ROPC.
Strip the non-IAM login mechanisms:
- inline email/password + social-button form (SignInForm) and its wrapper
- ROPC /v1/iam/login (iam-login) + hand-rolled PKCE (pkce)
- server-driven provider list (providers) and signup BFF (signup)
- the /auth/refresh, /auth/signin, /auth/signup BFF endpoint routes
- the old @hanzo/iam-js-sdk Sdk wrapper
tsc --noEmit clean; next build and build:embed both green.
- OrgSwitcher is now the hoisted @hanzo/ui/product switcher (ui#36 closed):
a thin adapter wires ~/lib/org-scope (the same contract), the lazy
IamAdminApi.organizations pager (super-admin only), the /v1/iam/onboard
create hook, and the All-organizations picker row. One switcher, one home.
- Brand mark: HANZO logoContent + ui/HanzoMark now render @hanzo/logo
MARK_PATHS (the canonical 7-path shaded H, currentColor) — the flat 5-path
copies are gone; lux/zoo/pars white-label marks untouched.
- AppLauncher: Surfaces row (hanzo brand only, white-label safe) with the
shared shell's hanzo.team tile + billing.hanzo.ai.
- deps: @hanzo/logo ^1.0.13, @hanzo/ui ^8.0.5 (transpiled — ships raw TS).
Upstream unblocks published for the install: @hanzo/ui 8.0.5 (canvas peer
floor >=0.1.0) + @hanzo/ui-shadcn 5.9.1 (framer-motion ^11 || ^12).
- main-green drive-bys: proxy-allow duplicate 'dns' head removed;
billing-accounts test repointed to the shipped /v1/billing form;
shell test follows the Social→Publish display rename.
tsc 0 errors; vitest 2757/2757; next build + build:embed green.
- OrgSwitcher is now the hoisted @hanzo/ui/product switcher (ui#36 closed):
a thin adapter wires ~/lib/org-scope (the same contract), the lazy
IamAdminApi.organizations pager (super-admin only), the /v1/iam/onboard
create hook, and the All-organizations picker row. One switcher, one home.
- Brand mark: HANZO logoContent + ui/HanzoMark now render @hanzo/logo
MARK_PATHS (the canonical 7-path shaded H, currentColor) — the flat 5-path
copies are gone; lux/zoo/pars white-label marks untouched.
- AppLauncher: Surfaces row (hanzo brand only, white-label safe) with the
shared shell's hanzo.team tile + billing.hanzo.ai.
- deps: @hanzo/logo ^1.0.13, @hanzo/ui ^8.0.5 (transpiled — ships raw TS).
Upstream unblocks published for the install: @hanzo/ui 8.0.5 (canvas peer
floor >=0.1.0) + @hanzo/ui-shadcn 5.9.1 (framer-motion ^11 || ^12).
- main-green drive-bys: proxy-allow duplicate 'dns' head removed;
billing-accounts test repointed to the shipped /v1/billing form;
shell test follows the Social→Publish display rename.
tsc 0 errors; vitest 2757/2757; next build + build:embed green.
Extends the existing models product with two tabs rather than adding a second
catalog. The Catalog tab gains a vision capability badge derived from the
catalog's own features, both sides of the per-Mtok price, and the published
benchmark headline. Leaderboard ranks the enso-bench prior corpus by any
benchmark it covers. Blend lets an org choose the models its router runs over
and shows the Enso flash, blend and ultra tiers re-forming as that set changes.
Benchmark scores are a checked-in fixture regenerated from hanzoai/enso-bench by
scripts/sync-benchmarks.mjs and imported at build time, because the corpus is a
versioned artefact rather than live state: it changes when a bench run lands, not
per request, so an endpoint would buy nothing and cost a loading state, a failure
mode and a fabrication risk on every page view. Every score keeps its source, our
own harness is badged, a model with no published score renders an em-dash rather
than a zero, and a model unscored on the selected benchmark is omitted from the
ranking rather than ranked last at zero.
The blend rules are a port of the reference semantics in enso-bench arms.py
resolve_blend, so the console means exactly what the router means by enabled.
Alongside the hand-written semantics tests there is a parity suite that executes
arms.py and diffs its real output; it caught a genuine divergence, since Python's
stable sort preserves catalog order for equally priced models and an id tie-break
in the port silently reordered them. That suite skips cleanly when the enso-bench
checkout is absent so CI never fails on a missing sibling repo.
Blend persistence rides the org's existing OrgSettings row rather than inventing
an endpoint. The gateway does not yet carry the three model columns, named in a
TODO on the client, so the write is attempted for real and then re-read to
confirm it survived; when it did not the board says so plainly instead of
confirming a write the backend discarded.
Vendor logos reuse the existing self-contained ProviderLogo marks with a monogram
fallback, with no external requests. The blend row's vendor label now resolves
identity-first through the same resolver the avatar uses, so a gateway-served
model reads as its true vendor rather than showing Zhipu or Moonshot artwork
beside the word Zen.
Verified with typecheck, the unit suite, both builds including the go:embed gate,
and a Playwright spec that drives all three surfaces in a browser.
Extends the existing models product with two tabs rather than adding a second
catalog. The Catalog tab gains a vision capability badge derived from the
catalog's own features, both sides of the per-Mtok price, and the published
benchmark headline. Leaderboard ranks the enso-bench prior corpus by any
benchmark it covers. Blend lets an org choose the models its router runs over
and shows the Enso flash, blend and ultra tiers re-forming as that set changes.
Benchmark scores are a checked-in fixture regenerated from hanzoai/enso-bench by
scripts/sync-benchmarks.mjs and imported at build time, because the corpus is a
versioned artefact rather than live state: it changes when a bench run lands, not
per request, so an endpoint would buy nothing and cost a loading state, a failure
mode and a fabrication risk on every page view. Every score keeps its source, our
own harness is badged, a model with no published score renders an em-dash rather
than a zero, and a model unscored on the selected benchmark is omitted from the
ranking rather than ranked last at zero.
The blend rules are a port of the reference semantics in enso-bench arms.py
resolve_blend, so the console means exactly what the router means by enabled.
Alongside the hand-written semantics tests there is a parity suite that executes
arms.py and diffs its real output; it caught a genuine divergence, since Python's
stable sort preserves catalog order for equally priced models and an id tie-break
in the port silently reordered them. That suite skips cleanly when the enso-bench
checkout is absent so CI never fails on a missing sibling repo.
Blend persistence rides the org's existing OrgSettings row rather than inventing
an endpoint. The gateway does not yet carry the three model columns, named in a
TODO on the client, so the write is attempted for real and then re-read to
confirm it survived; when it did not the board says so plainly instead of
confirming a write the backend discarded.
Vendor logos reuse the existing self-contained ProviderLogo marks with a monogram
fallback, with no external requests. The blend row's vendor label now resolves
identity-first through the same resolver the avatar uses, so a gateway-served
model reads as its true vendor rather than showing Zhipu or Moonshot artwork
beside the word Zen.
Verified with typecheck, the unit suite, both builds including the go:embed gate,
and a Playwright spec that drives all three surfaces in a browser.
The GitOps module called /v1/gitops, which cloud never binds — the CD surface
was dead in the console. Repoint to the served /v1/deploy projection, remap the
DTO fields, admit deploy through the BFF proxy, and render the fleet on the
@hanzo/canvas Railway board with a node drawer.
The GitOps module called /v1/gitops, which cloud never binds — the CD surface
was dead in the console. Repoint to the served /v1/deploy projection, remap the
DTO fields, admit deploy through the BFF proxy, and render the fleet on the
@hanzo/canvas Railway board with a node drawer.
Turn the console CD product into a mobile-first deployment map wired to the
native cloud CD projection (cd.hanzo.ai's surface).
- FIX the #1 blocker: repoint the client from the never-bound /v1/gitops to
cloud's /v1/deploy, and REMAP the real clients/deploy DTOs into the console
view-models (repository/version->image, runningVersion->liveTag,
healthMessage->message, parentRefs[].ref->ownerRefs, object manifests->JSON,
logs blob->lines). Add the deploy head to the proxy allow-list.
- RENDER the fleet as a @hanzo/canvas ProjectCanvas map: foldFleet folds each
App CR into a service node (CD health status, git/image source, capability,
deploy time), a deterministic grid layout (no invented edges), env switcher,
search, and click-to-filter KPI tiles.
- ENRICH nodes best-effort in parallel: git repo+branch (GitApi.repos) and CI
build time (BuildsApi); missing enrichment never drops a node.
- DRILL-IN drawer (ServiceDetailChar tabs): Resources = the owned-resource
topology via treeToGraph, Deploys = the CI build timeline, Logs = live pod
logs, Source = git repo/branch/commit + image; confirm-gated Sync + Rollback
(rollback offers only real clean-semver git releases).
- MOBILE-first: full-screen drawer, touch pan/zoom, no horizontal body scroll,
nav collapses to the hamburger.
- Mount the shared @hanzo/canvas primitive (the base @hanzo/gitops wraps);
delete the dead parts.tsx + ui-contract.ts mount-seam.
- Tests: 52 (client DTO mapping + fold/grid/release-targets) + a responsive
Playwright e2e (desktop 1440 + mobile 390, screenshots, no-overflow +
nav-collapse asserts).
Turn the console CD product into a mobile-first deployment map wired to the
native cloud CD projection (cd.hanzo.ai's surface).
- FIX the #1 blocker: repoint the client from the never-bound /v1/gitops to
cloud's /v1/deploy, and REMAP the real clients/deploy DTOs into the console
view-models (repository/version->image, runningVersion->liveTag,
healthMessage->message, parentRefs[].ref->ownerRefs, object manifests->JSON,
logs blob->lines). Add the deploy head to the proxy allow-list.
- RENDER the fleet as a @hanzo/canvas ProjectCanvas map: foldFleet folds each
App CR into a service node (CD health status, git/image source, capability,
deploy time), a deterministic grid layout (no invented edges), env switcher,
search, and click-to-filter KPI tiles.
- ENRICH nodes best-effort in parallel: git repo+branch (GitApi.repos) and CI
build time (BuildsApi); missing enrichment never drops a node.
- DRILL-IN drawer (ServiceDetailChar tabs): Resources = the owned-resource
topology via treeToGraph, Deploys = the CI build timeline, Logs = live pod
logs, Source = git repo/branch/commit + image; confirm-gated Sync + Rollback
(rollback offers only real clean-semver git releases).
- MOBILE-first: full-screen drawer, touch pan/zoom, no horizontal body scroll,
nav collapses to the hamburger.
- Mount the shared @hanzo/canvas primitive (the base @hanzo/gitops wraps);
delete the dead parts.tsx + ui-contract.ts mount-seam.
- Tests: 52 (client DTO mapping + fold/grid/release-targets) + a responsive
Playwright e2e (desktop 1440 + mobile 390, screenshots, no-overflow +
nav-collapse asserts).
Every model-selection surface now uses ONE selector fed from the live gateway
catalog — the hanzo.chat family-grouped picker (Enso, Zen, Anthropic, OpenAI
first, then alphabetical; family headers; premium chip; search; monochrome).
Console runs @hanzo/gui (Tamagui), NOT @hanzo/ui-shadcn, so per the one-way-per-
repo rule this is a faithful Tamagui twin of @hanzo/ui/models ModelSelector with
the SAME contract ({models,value,onChange,size,chatOnly}) and SAME family taxonomy
(~/lib/api/families groupModelsByFamily, mirroring @hanzo/ui/models). Drop-in swap
when the console migrates to the shadcn design system.
- ModelSelector.tsx: the ONE selector (family sections, premium PRO chip, search
over the catalog, keyboard nav, monochrome marks, honest free-text fallback).
- useModelCatalog.ts: the ONE shared catalog-entries hook (fetchCatalog via the
authed /ai proxy). Playground useModels now derives its ModelOption view from it
(one fetch, exposes raw entries) — DRY.
- families.ts: add Enso as a first-party house family (own family, Hanzo mark);
reorder to the contract (Enso, Zen, Anthropic, OpenAI, then alphabetical) as the
ONE ordering shared by the selector AND the Models browser; add the contract-named
groupModelsByFamily(catalog,{chatOnly}); groupByFamily stays its chat-only default.
- brand.ts / ProviderLogo.tsx: Enso resolves to the house brand; ProviderLogo gains
a `mono` monochrome mode for the selector.
- Rewire: Composer + Evals (model under test + judge) onto ModelSelector; delete the
two old pickers (products/ModelPicker, playground/ModelPicker) and the superseded
provider-cascade grouping (playground/providers).
- Kill sunset zen4 literals in RouterPolicyEditor placeholders (catalog is truth).
Not unified (noted for later convergence): the modality playgrounds (image/video/
audio/embeddings) keep ModelSelect (a different domain — picking a non-chat model),
and agent-builder keeps its injected-loader ComboBox (a portable, decoupled builder).
Verify: tsc --noEmit clean for every touched file (54 pre-existing env-noise errors
from uninstalled @hanzo/canvas|capture|usage, down from 59 baseline — @hanzo/ui not
installed as expected); vitest families+brand+default-model+catalog 65/65 pass.
Ships to console.hanzo.ai only via the next hanzoai/cloud release embedding
console@main (CONSOLE_REF=main) — landing on console main does NOT deploy by itself.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Every model-selection surface now uses ONE selector fed from the live gateway
catalog — the hanzo.chat family-grouped picker (Enso, Zen, Anthropic, OpenAI
first, then alphabetical; family headers; premium chip; search; monochrome).
Console runs @hanzo/gui (Tamagui), NOT @hanzo/ui-shadcn, so per the one-way-per-
repo rule this is a faithful Tamagui twin of @hanzo/ui/models ModelSelector with
the SAME contract ({models,value,onChange,size,chatOnly}) and SAME family taxonomy
(~/lib/api/families groupModelsByFamily, mirroring @hanzo/ui/models). Drop-in swap
when the console migrates to the shadcn design system.
- ModelSelector.tsx: the ONE selector (family sections, premium PRO chip, search
over the catalog, keyboard nav, monochrome marks, honest free-text fallback).
- useModelCatalog.ts: the ONE shared catalog-entries hook (fetchCatalog via the
authed /ai proxy). Playground useModels now derives its ModelOption view from it
(one fetch, exposes raw entries) — DRY.
- families.ts: add Enso as a first-party house family (own family, Hanzo mark);
reorder to the contract (Enso, Zen, Anthropic, OpenAI, then alphabetical) as the
ONE ordering shared by the selector AND the Models browser; add the contract-named
groupModelsByFamily(catalog,{chatOnly}); groupByFamily stays its chat-only default.
- brand.ts / ProviderLogo.tsx: Enso resolves to the house brand; ProviderLogo gains
a `mono` monochrome mode for the selector.
- Rewire: Composer + Evals (model under test + judge) onto ModelSelector; delete the
two old pickers (products/ModelPicker, playground/ModelPicker) and the superseded
provider-cascade grouping (playground/providers).
- Kill sunset zen4 literals in RouterPolicyEditor placeholders (catalog is truth).
Not unified (noted for later convergence): the modality playgrounds (image/video/
audio/embeddings) keep ModelSelect (a different domain — picking a non-chat model),
and agent-builder keeps its injected-loader ComboBox (a portable, decoupled builder).
Verify: tsc --noEmit clean for every touched file (54 pre-existing env-noise errors
from uninstalled @hanzo/canvas|capture|usage, down from 59 baseline — @hanzo/ui not
installed as expected); vitest families+brand+default-model+catalog 65/65 pass.
Ships to console.hanzo.ai only via the next hanzoai/cloud release embedding
console@main (CONSOLE_REF=main) — landing on console main does NOT deploy by itself.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Pages and Workers are wired; R2/KV/D1 render as labelled Phase-2 tabs that
explain themselves instead of exposing controls that would 501.
- src/lib/api/cloudflare.ts: typed client over the asset plane. Relays
Cloudflare API v4 `result` verbatim, so the normalizers map the real CF
shapes (created_on, latest_stage, script id = script name) and tolerate the
`{success:true}` object the backend returns for an empty result. Name and
id validators mirror the backend's nameRE/idRE so a bad field is an inline
error, not a 400.
- CloudflareModule: Pages (projects, deployments, custom domains) and Workers
(scripts, workers.dev subdomain, zone routes). 503 -> connect-account
affordance linking the existing integrations flow rather than a second
connect surface; 403 explains the org-admin write gate; 501 -> Phase 2.
- BackendState: classify 501 as not-implemented, distinct from 404. The route
exists and answers honestly; say that rather than "not available here".
- ConfirmDelete: lifted out of DnsModule so both modules share one destructive
confirm.
Registered under Network beside DNS and Domains.
Pages and Workers are wired; R2/KV/D1 render as labelled Phase-2 tabs that
explain themselves instead of exposing controls that would 501.
- src/lib/api/cloudflare.ts: typed client over the asset plane. Relays
Cloudflare API v4 `result` verbatim, so the normalizers map the real CF
shapes (created_on, latest_stage, script id = script name) and tolerate the
`{success:true}` object the backend returns for an empty result. Name and
id validators mirror the backend's nameRE/idRE so a bad field is an inline
error, not a 400.
- CloudflareModule: Pages (projects, deployments, custom domains) and Workers
(scripts, workers.dev subdomain, zone routes). 503 -> connect-account
affordance linking the existing integrations flow rather than a second
connect surface; 403 explains the org-admin write gate; 501 -> Phase 2.
- BackendState: classify 501 as not-implemented, distinct from 404. The route
exists and answers honestly; say that rather than "not available here".
- ConfirmDelete: lifted out of DnsModule so both modules share one destructive
confirm.
Registered under Network beside DNS and Domains.
The Promo tab's Current-promo + Edit-promo panels (and the Caps tab's
Target-organization panel) are stacked in a vertical YStack but used Panel's
default grow=true (flex:1). Per Panel's own contract, flex-grown panels in a
column with no fixed height collapse onto each other — the Current-promo facts
overlapped the Edit-promo slider, making the flagship admin surface read as
broken. Pass grow={false} on the three column-stacked panels so each sizes to
its content and stacks cleanly (the documented fix).
Also folds in the surface's save/validation Note improvement: a success
confirmation renders a green check, reserving the red warning triangle for
errors. Verified locally (mocked global-admin render, before/after) — both tabs
stack cleanly desktop + mobile; tsc clean; admin/promo/budgets vitest 50/50.
The Promo tab's Current-promo + Edit-promo panels (and the Caps tab's
Target-organization panel) are stacked in a vertical YStack but used Panel's
default grow=true (flex:1). Per Panel's own contract, flex-grown panels in a
column with no fixed height collapse onto each other — the Current-promo facts
overlapped the Edit-promo slider, making the flagship admin surface read as
broken. Pass grow={false} on the three column-stacked panels so each sizes to
its content and stacks cleanly (the documented fix).
Also folds in the surface's save/validation Note improvement: a success
confirmation renders a green check, reserving the red warning triangle for
errors. Verified locally (mocked global-admin render, before/after) — both tabs
stack cleanly desktop + mobile; tsc clean; admin/promo/budgets vitest 50/50.
The social product face is renamed to Publish everywhere it's user-visible — the
registry label + description, the SocialModule PageHeader title, and the single-
product shell wordmark (social.hanzo.ai header). The description now leads with the
user's framing: 'Queue and publish your content everywhere.'
Kept UNCHANGED (one seam, one name for the value — only the label moved): the
internal id 'social', the /v1/social + /v1/marketing cloud seam, config.socialOnly,
shell==='social', and the social.hanzo.ai host mapping. Renaming those would break
the folded cloud binding + the host→mode resolution.
tsc --noEmit clean (0 errors).
The social product face is renamed to Publish everywhere it's user-visible — the
registry label + description, the SocialModule PageHeader title, and the single-
product shell wordmark (social.hanzo.ai header). The description now leads with the
user's framing: 'Queue and publish your content everywhere.'
Kept UNCHANGED (one seam, one name for the value — only the label moved): the
internal id 'social', the /v1/social + /v1/marketing cloud seam, config.socialOnly,
shell==='social', and the social.hanzo.ai host mapping. Renaming those would break
the folded cloud binding + the host→mode resolution.
tsc --noEmit clean (0 errors).
Promote DnsModule to the full zones/records CRUD dashboard (typed /v1/dns
client in lib/api/dns.ts, Cloudflare Proxied toggle, DNSSEC/TTL/priority),
admit the org-scoped 'dns' cloud head through the console BFF, and add the
'dns' product shell so dns.hanzo.ai boots straight into the dashboard. Add the
Domains module (register/renew names via cloud clients/domain → name.com).
Integrates console feat/dns-crud-dashboard (c6f7bb54a) + feat/dns-proxy-head
onto main; the 'dns' proxy head is added exactly once. Domains work committed
from the working tree.
tsc --noEmit clean; vitest green (dns 24, proxy-allow 26, shell 11, config 41).
Assisted-by: neo:claude-opus-4-8
Promote DnsModule to the full zones/records CRUD dashboard (typed /v1/dns
client in lib/api/dns.ts, Cloudflare Proxied toggle, DNSSEC/TTL/priority),
admit the org-scoped 'dns' cloud head through the console BFF, and add the
'dns' product shell so dns.hanzo.ai boots straight into the dashboard. Add the
Domains module (register/renew names via cloud clients/domain → name.com).
Integrates console feat/dns-crud-dashboard (da488eb2a) + feat/dns-proxy-head
onto main; the 'dns' proxy head is added exactly once. Domains work committed
from the working tree.
tsc --noEmit clean; vitest green (dns 24, proxy-allow 26, shell 11, config 41).
Two-tab admin module (admin: true, hidden from customers, gated by
useIsSuperAdmin + the server getAdminGate):
- Promo: view + upsert the single platform plan promo (percentOff, UTC
start/end window, applicable paid plans, active) over GET/PUT /v1/admin/promos.
- Caps: pick a target org, list its usage caps (threshold, hard-cap vs alert,
softPct, rate limit, derived periodSpentCents/over/warn/resets), and
create/edit/delete over GET/POST/PATCH/DELETE /v1/admin/spend-caps?org=<slug>.
Wiring: promos + spend-caps added to ADMIN_AGGREGATE_HEADS (admin-aggregate.ts)
and ADMIN_V1_HEADS (next.config.mjs); PATCH + DELETE handlers added to the
global-admin-gated /admin/aggregate proxy (PUT already present). client.ts gains
origin{Put,Patch,Delete} (request extended to PUT/PATCH/DELETE). Caps reuse the
tenant SpendAlert primitive + budgets-logic verbatim — one caps model, no fork.
tsc clean; +45 unit tests (promo-logic, admin-promos, admin-spend-caps,
admin-aggregate heads); next build green.
Two-tab admin module (admin: true, hidden from customers, gated by
useIsSuperAdmin + the server getAdminGate):
- Promo: view + upsert the single platform plan promo (percentOff, UTC
start/end window, applicable paid plans, active) over GET/PUT /v1/admin/promos.
- Caps: pick a target org, list its usage caps (threshold, hard-cap vs alert,
softPct, rate limit, derived periodSpentCents/over/warn/resets), and
create/edit/delete over GET/POST/PATCH/DELETE /v1/admin/spend-caps?org=<slug>.
Wiring: promos + spend-caps added to ADMIN_AGGREGATE_HEADS (admin-aggregate.ts)
and ADMIN_V1_HEADS (next.config.mjs); PATCH + DELETE handlers added to the
global-admin-gated /admin/aggregate proxy (PUT already present). client.ts gains
origin{Put,Patch,Delete} (request extended to PUT/PATCH/DELETE). Caps reuse the
tenant SpendAlert primitive + budgets-logic verbatim — one caps model, no fork.
tsc clean; +45 unit tests (promo-logic, admin-promos, admin-spend-caps,
admin-aggregate heads); next build green.
Add the 'dns' head so the DNS control plane (hanzoai/dns at dns.hanzo.ai) is
reachable through the same-origin /v1 user-bearer proxy: the DnsModule can list/
manage authoritative + Cloudflare zones over /v1/dns/*, org-scoped by the JWT
owner claim server-side.
Add the 'dns' head so the DNS control plane (hanzoai/dns at dns.hanzo.ai) is
reachable through the same-origin /v1 user-bearer proxy: the DnsModule can list/
manage authoritative + Cloudflare zones over /v1/dns/*, org-scoped by the JWT
owner claim server-side.
Detail rail now shows the project's REAL resources — Live URL, a Resources band
(Compute honest '—' edge-served, Storage from the live deployment bytes/files,
Domains count + bound-host list, Deployments count+status) — from /v1/projects/:slug
deployments + domains. Honest zeros; no faked project-scoped compute. Ships to
console.hanzo.ai on the next cloud rebuild (go:embed).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Detail rail now shows the project's REAL resources — Live URL, a Resources band
(Compute honest '—' edge-served, Storage from the live deployment bytes/files,
Domains count + bound-host list, Deployments count+status) — from /v1/projects/:slug
deployments + domains. Honest zeros; no faked project-scoped compute. Ships to
console.hanzo.ai on the next cloud rebuild (go:embed).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
On the go:embed console.hanzo.ai (served by the hanzoai/cloud binary, no Next BFF),
the casibase COOKIE-session endpoints are served UNPREFIXED — /v1/get-account,
/v1/signin, /v1/signout, /v1/update-preferences. account.ts called them under
/v1/iam/* (the OIDC/bearer gate → 401), so a valid cloud_session_id resolved to
null and AuthGate rendered SignIn despite being logged in. Drop the 'iam/' prefix
on the four session calls; iam/keys + iam/onboard stay (cloud serves those at /v1/iam/*).
Ships to console.hanzo.ai via a hanzoai/cloud rebuild embedding console@main.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
On the go:embed console.hanzo.ai (served by the hanzoai/cloud binary, no Next BFF),
the casibase COOKIE-session endpoints are served UNPREFIXED — /v1/get-account,
/v1/signin, /v1/signout, /v1/update-preferences. account.ts called them under
/v1/iam/* (the OIDC/bearer gate → 401), so a valid cloud_session_id resolved to
null and AuthGate rendered SignIn despite being logged in. Drop the 'iam/' prefix
on the four session calls; iam/keys + iam/onboard stay (cloud serves those at /v1/iam/*).
Ships to console.hanzo.ai via a hanzoai/cloud rebuild embedding console@main.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Langfuse retired (observability on SigNoz/o11y span plane). Removes the two
user-facing 'Langfuse' strings from the AI Metrics card. Applies the net
change from feat/ai-overview-page + chore/fork-hygiene-notice (identical
2-line debrand) directly, without dragging their stale 69-commit history.
Langfuse retired (observability on SigNoz/o11y span plane). Removes the two
user-facing 'Langfuse' strings from the AI Metrics card. Applies the net
change from feat/ai-overview-page + chore/fork-hygiene-notice (identical
2-line debrand) directly, without dragging their stale 69-commit history.
feat/analytics-instrumentation: page/event instrumentation across sign-in,
onboarding, api-keys, plans, projects, create-app; dep rename
@hanzo/analytics -> @hanzo/capture. SignInForm conflict resolved keeping
main's live IAM provider list + Apple/GitLab/Wallet social specs (dropped
the branch's stale unused QrCode import). typecheck clean.
feat/analytics-instrumentation: page/event instrumentation across sign-in,
onboarding, api-keys, plans, projects, create-app; dep rename
@hanzo/analytics -> @hanzo/capture. SignInForm conflict resolved keeping
main's live IAM provider list + Apple/GitLab/Wallet social specs (dropped
the branch's stale unused QrCode import). typecheck clean.
The release workflow tagged the image :v<package.json version> on every push to
main, so a push that did not bump package.json re-published different bytes under
the same :v tag — anything pinned to it silently drifted (a deploy got an image
other than the one the tag was cut for).
Each build now pushes an immutable, content-addressable sha-<short-git-sha> tag
(the tag deploys should pin), then retags that proven image to the next free
v<X.Y.Z> = max(highest git tag, highest pushed container tag) + 1 and pushes the
git tag as a receipt. Order is build -> push image -> tag, so a failed build
leaves no tag and no version number is ever reused or overwritten. The workflow
owns the v* tags (the v* push trigger and the package.json tag-compute are gone);
the lane is serialized and never cancels mid-flight.
The release workflow tagged the image :v<package.json version> on every push to
main, so a push that did not bump package.json re-published different bytes under
the same :v tag — anything pinned to it silently drifted (a deploy got an image
other than the one the tag was cut for).
Each build now pushes an immutable, content-addressable sha-<short-git-sha> tag
(the tag deploys should pin), then retags that proven image to the next free
v<X.Y.Z> = max(highest git tag, highest pushed container tag) + 1 and pushes the
git tag as a receipt. Order is build -> push image -> tag, so a failed build
leaves no tag and no version number is ever reused or overwritten. The workflow
owns the v* tags (the v* push trigger and the package.json tag-compute are gone);
the lane is serialized and never cancels mid-flight.
Ships two customer-facing features on the home + shell:
- Observability front-and-center on the overview (reuses ProductObservability).
- Native, CSP-safe first-run guided tour (Appcues alternative; zero external scripts).
Plus the comprehensive billing/usage/o11y E2E smoke (e2e/billing-usage-o11y.spec.ts).
tsc clean; tour vitest 10/10; the go:embed build:embed gate runs in CI.
Ships two customer-facing features on the home + shell:
- Observability front-and-center on the overview (reuses ProductObservability).
- Native, CSP-safe first-run guided tour (Appcues alternative; zero external scripts).
Plus the comprehensive billing/usage/o11y E2E smoke (e2e/billing-usage-o11y.spec.ts).
tsc clean; tour vitest 10/10; the go:embed build:embed gate runs in CI.
A fully NATIVE product tour (Appcues-style) with ZERO external scripts and zero new
deps, so it works inside the go:embed static console and under any CSP. GuidedTour
spotlights data-tour anchors with a box-shadow cutout + a floating tooltip (centers
gracefully when an anchor is absent/hidden); FirstRunTour shows it ONCE per account
on the home, after onboarding (defers via the onboarding local guard so they never
overlap). Pure, versioned, owner-keyed seen-guard mirrors lib/onboarding/guard.
Files: src/lib/tour/{steps.ts,steps.test.ts}, src/components/tour/{GuidedTour,FirstRunTour}.tsx,
mounted in (dashboard)/layout.tsx, data-tour="nav" anchor on the sidebar.
tsc clean; vitest 10/10 (tour logic).
A fully NATIVE product tour (Appcues-style) with ZERO external scripts and zero new
deps, so it works inside the go:embed static console and under any CSP. GuidedTour
spotlights data-tour anchors with a box-shadow cutout + a floating tooltip (centers
gracefully when an anchor is absent/hidden); FirstRunTour shows it ONCE per account
on the home, after onboarding (defers via the onboarding local guard so they never
overlap). Pure, versioned, owner-keyed seen-guard mirrors lib/onboarding/guard.
Files: src/lib/tour/{steps.ts,steps.test.ts}, src/components/tour/{GuidedTour,FirstRunTour}.tsx,
mounted in (dashboard)/layout.tsx, data-tour="nav" anchor on the sidebar.
tsc clean; vitest 10/10 (tour logic).
The home now surfaces the platform's live LLM signals — RED metrics, recent
logs, recent traces — directly on the overview, the way Langfuse put its metrics
dashboard up top. Reuses the ONE shared ProductObservability panel over the 'ai'
inference service (honest-empty until o11y emits; deep-links to /o11y). Adds
data-tour anchors (api-key, metrics) for the first-run tour. Additive, no new
deps, tsc clean.
The home now surfaces the platform's live LLM signals — RED metrics, recent
logs, recent traces — directly on the overview, the way Langfuse put its metrics
dashboard up top. Reuses the ONE shared ProductObservability panel over the 'ai'
inference service (honest-empty until o11y emits; deep-links to /o11y). Adds
data-tour anchors (api-key, metrics) for the first-run tour. Additive, no new
deps, tsc clean.
build-image.yml publishes v<package.json version> on a main push, so the merge
that fixed the proxy republished v8.4.138 — the tag the fleet already ran. The
image changed underneath a name that did not, which is not a release.
8.4.139 gives the fix a name to be rolled to. crs/console.yaml moves to it once
CI publishes.
The fix: /paas/<x> forwarded to /v1/<x>, so every call 404'd (/paas/apps ->
/v1/apps). It aimed there because that is where the standalone Node platform
served apps; the plane moved into cloud under /v1/paas and the path never
followed.
build-image.yml publishes v<package.json version> on a main push, so the merge
that fixed the proxy republished v8.4.138 — the tag the fleet already ran. The
image changed underneath a name that did not, which is not a release.
8.4.139 gives the fix a name to be rolled to. crs/console.yaml moves to it once
CI publishes.
The fix: /paas/<x> forwarded to /v1/<x>, so every call 404'd (/paas/apps ->
/v1/apps). It aimed there because that is where the standalone Node platform
served apps; the plane moved into cloud under /v1/paas and the path never
followed.
- Land the comprehensive billing/invoices/usage/o11y render smoke
(billing-usage-o11y.spec.ts: every billing sub-page, invoice view/download/
statement/reload, settings, usage/metrics/AI-metrics, the full o11y set, and a
dead-card audit) — the E2E agent authored it but never committed before the
session limit.
- console.spec + live-billing-admin: assert the TRUE "no data tunnel" invariant
(an unauthenticated request never gets a 2xx carrying backend JSON; a SPA-HTML
fallback and a >=401 gate both pass) instead of brittle exact status codes on
renamed/pruned paths (superbase->base, the go:embed-pruned /admin/aggregate).
theme-color #0a0a0a -> #000000 (live value).
- Shared fixture-server gate (_fixture.ts): the localhost:4000 render specs
(ai-economics/budgets/gpus/provider-billing(A)/entitlement-sidebar/
interactive-training/blank-audit) skip cleanly when that server is unreachable
instead of ECONNREFUSED-failing against prod.
- probe-o11y skips without HANZO_PASSWORD instead of hard-throwing.
- playwright retries:2 in CI to absorb Tamagui/RNW SPA-hydration render flakiness
(a real regression fails every attempt, so nothing is masked).
Full live run vs console.hanzo.ai: 15 passed / 299 skipped-cleanly / 0 failed.
Prod posture verified live: /v1/admin/* -> 403 JSON (fail-closed), no data tunnels
(superbase/keys/aggregate all SPA-HTML, never backend JSON).
- Land the comprehensive billing/invoices/usage/o11y render smoke
(billing-usage-o11y.spec.ts: every billing sub-page, invoice view/download/
statement/reload, settings, usage/metrics/AI-metrics, the full o11y set, and a
dead-card audit) — the E2E agent authored it but never committed before the
session limit.
- console.spec + live-billing-admin: assert the TRUE "no data tunnel" invariant
(an unauthenticated request never gets a 2xx carrying backend JSON; a SPA-HTML
fallback and a >=401 gate both pass) instead of brittle exact status codes on
renamed/pruned paths (superbase->base, the go:embed-pruned /admin/aggregate).
theme-color #0a0a0a -> #000000 (live value).
- Shared fixture-server gate (_fixture.ts): the localhost:4000 render specs
(ai-economics/budgets/gpus/provider-billing(A)/entitlement-sidebar/
interactive-training/blank-audit) skip cleanly when that server is unreachable
instead of ECONNREFUSED-failing against prod.
- probe-o11y skips without HANZO_PASSWORD instead of hard-throwing.
- playwright retries:2 in CI to absorb Tamagui/RNW SPA-hydration render flakiness
(a real regression fails every attempt, so nothing is masked).
Full live run vs console.hanzo.ai: 15 passed / 299 skipped-cleanly / 0 failed.
Prod posture verified live: /v1/admin/* -> 403 JSON (fail-closed), no data tunnels
(superbase/keys/aggregate all SPA-HTML, never backend JSON).
/paas/<x> built /v1/<x>, so every call 404'd: /paas/apps -> /v1/apps. It aimed
there because that is where the standalone Node platform served apps; the control
plane moved into cloud under /v1/paas and the path never followed.
Now /paas/<x> -> /v1/paas/<x>, name-preserving on both sides. apps is the proxy's
only consumer, so nothing else moves.
/paas/<x> built /v1/<x>, so every call 404'd: /paas/apps -> /v1/apps. It aimed
there because that is where the standalone Node platform served apps; the control
plane moved into cloud under /v1/paas and the path never followed.
Now /paas/<x> -> /v1/paas/<x>, name-preserving on both sides. apps is the proxy's
only consumer, so nothing else moves.
/paas/<x> built ${PLATFORM_URL}/v1/<x>, so every call landed on a path that does
not exist: /paas/apps -> /v1/apps -> 404. The board rendered nothing and the token
was never the problem (PAAS_SERVICE_TOKEN is set, 64 bytes).
It aimed at /v1/<x> because that IS where the standalone Node platform served
apps. The control plane moved into cloud under /v1/paas and this path did not
follow — the console kept asking the old shape of a service that no longer has it.
Now /paas/<x> -> /v1/paas/<x>: the route is the PaaS plane, so it forwards to the
PaaS plane, name-preserving on both sides. `apps` is the proxy's only consumer
(platform.ts url()), so nothing else moves.
NOT verified end-to-end: /v1/paas/* is SuperAdmin-gated, so the rendered board
needs a superadmin session to confirm. What is verified: the upstream path exists
(/v1/paas/apps answers, 500 "SuperAdmin required" — reached and refused, not 404),
cloud's RBAC to read App CRs is fixed, and /v1/paas/health is 200.
/paas/<x> built ${PLATFORM_URL}/v1/<x>, so every call landed on a path that does
not exist: /paas/apps -> /v1/apps -> 404. The board rendered nothing and the token
was never the problem (PAAS_SERVICE_TOKEN is set, 64 bytes).
It aimed at /v1/<x> because that IS where the standalone Node platform served
apps. The control plane moved into cloud under /v1/paas and this path did not
follow — the console kept asking the old shape of a service that no longer has it.
Now /paas/<x> -> /v1/paas/<x>: the route is the PaaS plane, so it forwards to the
PaaS plane, name-preserving on both sides. `apps` is the proxy's only consumer
(platform.ts url()), so nothing else moves.
NOT verified end-to-end: /v1/paas/* is SuperAdmin-gated, so the rendered board
needs a superadmin session to confirm. What is verified: the upstream path exists
(/v1/paas/apps answers, 500 "SuperAdmin required" — reached and refused, not 404),
cloud's RBAC to read App CRs is fixed, and /v1/paas/health is 200.
Sidebar + product-nav overhaul for console.hanzo.ai (embedded in the cloud release):
- nav-accordion: SINGLE-OPEN → EXPAND-ALL-BY-DEFAULT. Every category renders expanded;
an optional per-section chevron collapses one INDEPENDENTLY, persisted per-user
(navCategoriesOpen), respected on every render; filtering force-opens. Tests rewritten.
- Category headers un-indented — flush-left with Overview/Docs (count + collapse chevron
moved to the right), so the hierarchy reads clean.
- Whole-sidebar collapse to an icon RAIL (topbar toggle, persisted) with a HOVER flyout
overlay that doesn't push content (classic rail+flyout); mobile keeps the left drawer.
- Drill-in / drill-back: clicking a product with sub-pages DRILLS the sidebar into its
sub-nav (Overview · specifics · Settings/Status/Logs/Metrics) with a Back affordance;
a single-page product navigates directly (replaces the inline sub-nav).
- Add-product panel: the broken "Enable" gate → pin/unpin (+ / −) to the sidebar; "In
use" discovery from the real usage ledger; keeps "only pay for what you use".
- Bottom-left dedupe: ONE OrgSwitcher (org avatar + name; "All organizations" folded into
its dropdown) — removed the redundant app-grid button. SidebarWallet = real live balance.
- Chat widget dockable as a PERMANENT right column (floating <-> docked, persisted); on
phones it stays the floating bubble/sheet.
- Graceful 402 add-credits/top-up across the shared error primitives (States/BackendState).
- Mobile: overlay drawer + tap-scrim, >=44px targets, docked chat lg-only, no horizontal scroll.
Drive-by: align the stale projects.test.ts with the shipped /v1/iam routing (commit
1e17f0383 moved the code but not its test) — restores main to green.
Gate: tsc --noEmit 0 errors; vitest 2565/2565.
Sidebar + product-nav overhaul for console.hanzo.ai (embedded in the cloud release):
- nav-accordion: SINGLE-OPEN → EXPAND-ALL-BY-DEFAULT. Every category renders expanded;
an optional per-section chevron collapses one INDEPENDENTLY, persisted per-user
(navCategoriesOpen), respected on every render; filtering force-opens. Tests rewritten.
- Category headers un-indented — flush-left with Overview/Docs (count + collapse chevron
moved to the right), so the hierarchy reads clean.
- Whole-sidebar collapse to an icon RAIL (topbar toggle, persisted) with a HOVER flyout
overlay that doesn't push content (classic rail+flyout); mobile keeps the left drawer.
- Drill-in / drill-back: clicking a product with sub-pages DRILLS the sidebar into its
sub-nav (Overview · specifics · Settings/Status/Logs/Metrics) with a Back affordance;
a single-page product navigates directly (replaces the inline sub-nav).
- Add-product panel: the broken "Enable" gate → pin/unpin (+ / −) to the sidebar; "In
use" discovery from the real usage ledger; keeps "only pay for what you use".
- Bottom-left dedupe: ONE OrgSwitcher (org avatar + name; "All organizations" folded into
its dropdown) — removed the redundant app-grid button. SidebarWallet = real live balance.
- Chat widget dockable as a PERMANENT right column (floating <-> docked, persisted); on
phones it stays the floating bubble/sheet.
- Graceful 402 add-credits/top-up across the shared error primitives (States/BackendState).
- Mobile: overlay drawer + tap-scrim, >=44px targets, docked chat lg-only, no horizontal scroll.
Drive-by: align the stale projects.test.ts with the shipped /v1/iam routing (commit
487a06a33 moved the code but not its test) — restores main to green.
Gate: tsc --noEmit 0 errors; vitest 2565/2565.
Decomplect hanzoai/cloud's build: the console SPA static export (npm run
build:embed -> out/) is now a versioned immutable image (console-embed, /dist)
built by console's OWN CI, not re-run inside every cloud release. cloud will
FROM registry.hanzo.ai/hanzoai/console-embed:<ver> AS console + COPY --from,
turning the ~15-min cache-busted npm+Next long pole into a registry pull.
- Dockerfile.embed: node build -> FROM scratch with /dist (fail-hard on a
missing/placeholder bundle, same invariant cloud's console stage enforced;
bakes the same public console.hanzo.ai analytics id).
- hanzo.yml: images: console-embed (hanzoai/ci builds + auto-mirrors to
registry.hanzo.ai). Next.js server image stays in build-image.yml.
- cicd.yml: canonical hanzoai/ci caller.
Claude-Session: https://claude.ai/code/session_015Z1iLf7QBrq1LhignJrzDw
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Decomplect hanzoai/cloud's build: the console SPA static export (npm run
build:embed -> out/) is now a versioned immutable image (console-embed, /dist)
built by console's OWN CI, not re-run inside every cloud release. cloud will
FROM registry.hanzo.ai/hanzoai/console-embed:<ver> AS console + COPY --from,
turning the ~15-min cache-busted npm+Next long pole into a registry pull.
- Dockerfile.embed: node build -> FROM scratch with /dist (fail-hard on a
missing/placeholder bundle, same invariant cloud's console stage enforced;
bakes the same public console.hanzo.ai analytics id).
- hanzo.yml: images: console-embed (hanzoai/ci builds + auto-mirrors to
registry.hanzo.ai). Next.js server image stays in build-image.yml.
- cicd.yml: canonical hanzoai/ci caller.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Projects + the member roster called the /org/iam BFF proxy, which the one-binary
(static-export) console cannot run — so on console.hanzo.ai they returned the SPA
shell and the Platform page showed "Request failed (HTTP 200)". Route them through
the main client at /v1/iam (the cloud IAM edge) instead, so ONE path serves both
the one-binary and split topologies, with CSRF + X-Org-Id + retry + envelope
unwrap for free. IAM's {status,msg,data,data2} IS our ApiResponse — no second
client (iamList/iamOne/iamMutate on client.ts).
tsc --noEmit clean.
Claude-Session: https://claude.ai/code/session_01SpMZ69ur3tjAXCiwaa7Wv2
Projects + the member roster called the /org/iam BFF proxy, which the one-binary
(static-export) console cannot run — so on console.hanzo.ai they returned the SPA
shell and the Platform page showed "Request failed (HTTP 200)". Route them through
the main client at /v1/iam (the cloud IAM edge) instead, so ONE path serves both
the one-binary and split topologies, with CSRF + X-Org-Id + retry + envelope
unwrap for free. IAM's {status,msg,data,data2} IS our ApiResponse — no second
client (iamList/iamOne/iamMutate on client.ts).
tsc --noEmit clean.
A responsive card grid (like the reference) so a user finds the right door without
leaving the console: Product Support (support@hanzo.ai), Contact Sales
(sales@hanzo.ai), X (@hanzoai), Discord (discord.gg/hanzo), LinkedIn (company/hanzoai),
GitHub (hanzoai), Hugging Face (hanzoai), More to Come. hanzo.ai is the hub; the AI
chat widget answers first, this is the human/channel fallback. Registered as the
`contact` product (Settings category). Pure presentational, mobile-stacked.
A responsive card grid (like the reference) so a user finds the right door without
leaving the console: Product Support (support@hanzo.ai), Contact Sales
(sales@hanzo.ai), X (@hanzoai), Discord (discord.gg/hanzo), LinkedIn (company/hanzoai),
GitHub (hanzoai), Hugging Face (hanzoai), More to Come. hanzo.ai is the hub; the AI
chat widget answers first, this is the human/channel fallback. Registered as the
`contact` product (Settings category). Pure presentational, mobile-stacked.
Per the privilege-separation: z@ via console resolves to hanzo/z (non-admin), so
the credit gate refuses it. The funding spec now signs in through the admin.hanzo.ai
surface (admin-guard → owner==admin) and POSTs the credit + balance read there — the
only identity the gate admits. Robust login selectors for the hanzo.id portal form.
Per the privilege-separation: z@ via console resolves to hanzo/z (non-admin), so
the credit gate refuses it. The funding spec now signs in through the admin.hanzo.ai
surface (admin-guard → owner==admin) and POSTs the credit + balance read there — the
only identity the gate admits. Robust login selectors for the hanzo.id portal form.
Live Playwright E2E: z@ signs in, credits the maxpower org via
/v1/admin/customers/:org/credit, and asserts the balance moves by exactly the
grant; a second spec verifies the funded member (davelorenzini) reaches /platform
with no dead "Could not load". Secrets come from env (HANZO_PASSWORD/DAVE_PASSWORD)
— never hardcoded; the credentialed specs skip without them, so CI stays green.
Surfaced a defect: unauthenticated credit returns 500, not 403 (core.Guard's
*zip.HTTPError 403 is re-wrapped as a generic api-error 500) — which is why the
console renders "Could not load" instead of an auth state. The fail-closed test
asserts rejection (no money moves) and flags the code for a follow-up fix.
Live Playwright E2E: z@ signs in, credits the maxpower org via
/v1/admin/customers/:org/credit, and asserts the balance moves by exactly the
grant; a second spec verifies the funded member (davelorenzini) reaches /platform
with no dead "Could not load". Secrets come from env (HANZO_PASSWORD/DAVE_PASSWORD)
— never hardcoded; the credentialed specs skip without them, so CI stays green.
Surfaced a defect: unauthenticated credit returns 500, not 403 (core.Guard's
*zip.HTTPError 403 is re-wrapped as a generic api-error 500) — which is why the
console renders "Could not load" instead of an auth state. The fail-closed test
asserts rejection (no money moves) and flags the code for a follow-up fix.
The settings-as-Base admin pattern: a super-admin "Routing" editor on
admin.hanzo.ai that edits the platform + per-org auto-routing policy as DATA
(Base/SQLite OrgSettings rows), never env or a session-gated code toggle. This
is where auto-routing (enso) becomes a real admin toggle.
- OrgSettingsApi over /v1/{get-org-settings-list,get-org-settings,
update-org-settings,delete-org-settings} (super-admin gated upstream), on the
SAME originGet/originPost /ai bearer transport the router policy uses (no new
transport). Every write is read-modify-write, so sibling routing-policy fields
(routerPrefer, costCeiling, defaultSessionRouting, trainingContribution) are
never clobbered by the backend's full-row replace; revert to inherit deletes
the row only when it holds nothing else, else it clears just the field.
- RoutingModule (admin): three-state control (inherit / enabled / disabled) for
the global "*" default + per-org overrides, inline-editable, add-override for
an org not yet listed, honest empty + 403 states (OperatorAccessRequired). The
Hanzo brand seeds the org-first activation row — set org hanzo -> Enabled.
- Route the four heads through next.config AI_V1_HEADS + the /ai proxy ALLOWED set.
- 13 unit tests: state mapping, planSave field preservation, revert = delete.
The settings-as-Base admin pattern: a super-admin "Routing" editor on
admin.hanzo.ai that edits the platform + per-org auto-routing policy as DATA
(Base/SQLite OrgSettings rows), never env or a session-gated code toggle. This
is where auto-routing (enso) becomes a real admin toggle.
- OrgSettingsApi over /v1/{get-org-settings-list,get-org-settings,
update-org-settings,delete-org-settings} (super-admin gated upstream), on the
SAME originGet/originPost /ai bearer transport the router policy uses (no new
transport). Every write is read-modify-write, so sibling routing-policy fields
(routerPrefer, costCeiling, defaultSessionRouting, trainingContribution) are
never clobbered by the backend's full-row replace; revert to inherit deletes
the row only when it holds nothing else, else it clears just the field.
- RoutingModule (admin): three-state control (inherit / enabled / disabled) for
the global "*" default + per-org overrides, inline-editable, add-override for
an org not yet listed, honest empty + 403 states (OperatorAccessRequired). The
Hanzo brand seeds the org-first activation row — set org hanzo -> Enabled.
- Route the four heads through next.config AI_V1_HEADS + the /ai proxy ALLOWED set.
- 13 unit tests: state mapping, planSave field preservation, revert = delete.
GPUs — SEE your connected machines. The BYO connect fleet (`hanzo gpu connect`
boxes: home lab dbc/evo/spark) registers with a per-box heartbeat that ONLY
`GET /v1/fleet/workers` carries (`/v1/machines` folds them in without it,
`/v1/gpus` expands per-accelerator without it). New `FleetApi` (lib/api/fleet.ts)
reads it over the same-origin `/v1` bearer BFF (`fleet` allow-listed in
proxy-allow.ts; direct on the go:embed console), and a reused `ConnectedMachines`
section on the customer GPUs Overview + GPUs tab lists each box: name, accelerator
(arch), memory, online/offline (server-derived at a 90s heartbeat TTL), last
heartbeat, and a "Serving" badge when it runs hanzo-engine. Cloud GPU VMs
(`/v1/machines`, non-BYO) stay a separate list so a box is shown ONCE (DRY).
Honest states throughout; nothing fabricated.
Wallet — the sidebar chip shows the org balance (`/v1/billing/balance`, unchanged)
and "Top up" now LINKS to the brand's hosted payment page in a new tab. New
`config.payUrl` derives `pay.<brand>` from the brand billing host (white-label-safe:
a Lux console links to pay.lux.cloud, never pay.hanzo.ai). Display + link only — the
console hosts no card form and mints no credit.
Mobile — the section reuses the shared DataTable (scrolls inside its own overflow-x
box, never the page body) + flexWrap stat cards, the codebase's one responsive
mechanism. Verified live at 390x844 and 768x1024 (no horizontal body scroll).
Tests: +8 fleet (normalizer/helpers/route), +1 config payUrl (white-label), +3
responsive e2e (desktop render + phone/tablet no-overflow). Full suite 2544 green;
tsc clean; next build + build:embed (go:embed gate) green.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
GPUs — SEE your connected machines. The BYO connect fleet (`hanzo gpu connect`
boxes: home lab dbc/evo/spark) registers with a per-box heartbeat that ONLY
`GET /v1/fleet/workers` carries (`/v1/machines` folds them in without it,
`/v1/gpus` expands per-accelerator without it). New `FleetApi` (lib/api/fleet.ts)
reads it over the same-origin `/v1` bearer BFF (`fleet` allow-listed in
proxy-allow.ts; direct on the go:embed console), and a reused `ConnectedMachines`
section on the customer GPUs Overview + GPUs tab lists each box: name, accelerator
(arch), memory, online/offline (server-derived at a 90s heartbeat TTL), last
heartbeat, and a "Serving" badge when it runs hanzo-engine. Cloud GPU VMs
(`/v1/machines`, non-BYO) stay a separate list so a box is shown ONCE (DRY).
Honest states throughout; nothing fabricated.
Wallet — the sidebar chip shows the org balance (`/v1/billing/balance`, unchanged)
and "Top up" now LINKS to the brand's hosted payment page in a new tab. New
`config.payUrl` derives `pay.<brand>` from the brand billing host (white-label-safe:
a Lux console links to pay.lux.cloud, never pay.hanzo.ai). Display + link only — the
console hosts no card form and mints no credit.
Mobile — the section reuses the shared DataTable (scrolls inside its own overflow-x
box, never the page body) + flexWrap stat cards, the codebase's one responsive
mechanism. Verified live at 390x844 and 768x1024 (no horizontal body scroll).
Tests: +8 fleet (normalizer/helpers/route), +1 config payUrl (white-label), +3
responsive e2e (desktop render + phone/tablet no-overflow). Full suite 2544 green;
tsc clean; next build + build:embed (go:embed gate) green.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Extend the existing `router` product (PR #160's org-user surface) so it covers ALL
org AI usage in addition to training + routing — without duplicating anything:
- New "Usage" tab in RouterModule (Overview · Usage · Policy) that renders the org's
AI usage by REUSING the existing plumbing: native Hanzo usage (CloudUsageApi.overview
→ GET /v1/get-cloud-usages) beside imported connected-provider usage, via the same
@hanzo/usage <UsagePanel>/<ConnectedUsage> the AI Metrics module already uses.
- Factor the shared usage-board body (fetch + honest async state for both planes) out
of AiUsageModule into ONE component, src/components/products/usage/AiUsagePanels.tsx;
AiUsageModule is now a thin adapter over it. One implementation, never a second copy.
- Relabel the `router` registry entry (id + route unchanged, still non-admin, category
AI): label "AI Usage & Training", description mentions usage + training + routing; add
a "Usage" subpage beside "Policy" in the level-2 sub-nav.
- Training status stays sourced from GET /v1/router/stats (Overview: retrain-gate line +
quality proxy) and the opt-in training-contribution toggle stays in EXACTLY ONE place
(RouterOverview) — not added to AiUsageModule or the shared body.
No admin/platform-operator surfaces touched. tsc clean; vitest 2535/2535; next build ✓;
build:embed ✓ (static export ready, 31 handlers restored).
Claude-Session: https://claude.ai/code/session_015Z1iLf7QBrq1LhignJrzDw
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Extend the existing `router` product (PR #160's org-user surface) so it covers ALL
org AI usage in addition to training + routing — without duplicating anything:
- New "Usage" tab in RouterModule (Overview · Usage · Policy) that renders the org's
AI usage by REUSING the existing plumbing: native Hanzo usage (CloudUsageApi.overview
→ GET /v1/get-cloud-usages) beside imported connected-provider usage, via the same
@hanzo/usage <UsagePanel>/<ConnectedUsage> the AI Metrics module already uses.
- Factor the shared usage-board body (fetch + honest async state for both planes) out
of AiUsageModule into ONE component, src/components/products/usage/AiUsagePanels.tsx;
AiUsageModule is now a thin adapter over it. One implementation, never a second copy.
- Relabel the `router` registry entry (id + route unchanged, still non-admin, category
AI): label "AI Usage & Training", description mentions usage + training + routing; add
a "Usage" subpage beside "Policy" in the level-2 sub-nav.
- Training status stays sourced from GET /v1/router/stats (Overview: retrain-gate line +
quality proxy) and the opt-in training-contribution toggle stays in EXACTLY ONE place
(RouterOverview) — not added to AiUsageModule or the shared body.
No admin/platform-operator surfaces touched. tsc clean; vitest 2535/2535; next build ✓;
build:embed ✓ (static export ready, 31 handlers restored).
Co-authored-by: hanzo-dev <dev@hanzo.ai>
/v1/plans now carries promoPercent/promoUntil (commerce v1.48.6). The plan card
shows the effective (post-promo) price big, the list price struck through, and a
'50% off · limited time' badge — the discount is derived from the ONE plan source
via the pure, reusable lib/billing/promo (promoActive/effectiveMonthly/promoLabel),
no second discount source. Degrades cleanly to the list price when no promo is live.
/v1/plans now carries promoPercent/promoUntil (commerce v1.48.6). The plan card
shows the effective (post-promo) price big, the list price struck through, and a
'50% off · limited time' badge — the discount is derived from the ONE plan source
via the pure, reusable lib/billing/promo (promoActive/effectiveMonthly/promoLabel),
no second discount source. Degrades cleanly to the list price when no promo is live.
iam2 serves ONE token endpoint — the RFC/discovery /oauth/token. No backwards-compat
access_token spelling; fix the client to the standard, not the backend to the client.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
iam2 serves ONE token endpoint — the RFC/discovery /oauth/token. No backwards-compat
access_token spelling; fix the client to the standard, not the backend to the client.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
`useSearchParams()` is typed ReadonlyURLSearchParams | null, so the five raw
searchParams.get()/.toString() reads were `tsc --noEmit` errors (TS18047). CI only
runs `next build` (which tolerated them), so the standalone typecheck had drifted
red unnoticed. Fall back to empty params in one place; `npm run typecheck` is clean.
`useSearchParams()` is typed ReadonlyURLSearchParams | null, so the five raw
searchParams.get()/.toString() reads were `tsc --noEmit` errors (TS18047). CI only
runs `next build` (which tolerated them), so the standalone typecheck had drifted
red unnoticed. Fall back to empty params in one place; `npm run typecheck` is clean.
22ea663bf3 ("signup mints NO credit") deleted lib/server/billing-grant.ts and its
test but left app/auth/signup/route.ts still importing and awaiting grantWelcomeCredit,
so `next build` could not resolve '~/lib/server/billing-grant' and the v8.4.136 image
never shipped — the last two pushes to main (signup-no-credit and the #160 merge)
both failed to compile.
This finishes that commit's stated intent: the route no longer imports or calls the
grant, so a new account starts at $0 (credit comes only from an admin grant or the
user adding funds), and the header doc drops the now-false "$5 welcome grant" line.
31ae930438 ("signup mints NO credit") deleted lib/server/billing-grant.ts and its
test but left app/auth/signup/route.ts still importing and awaiting grantWelcomeCredit,
so `next build` could not resolve '~/lib/server/billing-grant' and the v8.4.136 image
never shipped — the last two pushes to main (signup-no-credit and the #160 merge)
both failed to compile.
This finishes that commit's stated intent: the route no longer imports or calls the
grant, so a new account starts at $0 (credit comes only from an admin grant or the
user adding funds), and the header doc drops the now-false "$5 welcome grant" line.
Removed the server-side signup auto-grant: app/auth/signup/route.ts no longer
calls grantWelcomeCredit (→ commerce /v1/billing/grant-starter). Deleted the now-
dead lib/server/billing-grant.ts helper + its test (no residual). Together with
the session-bootstrap claimWelcomeGrantOnce removal (bd6e583cb), the console no
longer auto-grants any credit on signup or load. A new account starts at $0;
credit comes only from an admin grant (admin.hanzo.ai) or the user adding funds.
Removed the server-side signup auto-grant: app/auth/signup/route.ts no longer
calls grantWelcomeCredit (→ commerce /v1/billing/grant-starter). Deleted the now-
dead lib/server/billing-grant.ts helper + its test (no residual). Together with
the session-bootstrap claimWelcomeGrantOnce removal (2fe3e197a), the console no
longer auto-grants any credit on signup or load. A new account starts at $0;
credit comes only from an admin grant (admin.hanzo.ai) or the user adding funds.
Upgrade the `router` product from the single policy-editor route into a two-tab
Router dashboard: Overview (routing observability) + Policy (the reused λ/µ
editor). One editor, one place — no duplication.
Overview reads GET /v1/router/stats (org-scoped, RequirePrincipal) and renders:
(a) cost saved as a blended $/MTok PROXY — saved_pct + routed vs counterfactual
index + cumulative saved, honest "—" when priced_events==0; (b) quality proxy —
reward_rate + coverage, engine_share, avg_confidence, shadow_agreement only when
non-null; (c) per-task routed-model distribution (Donut) + by-model Donut +
throughput LineChart; (e) an opt-in training-contribution toggle wired to
GET/POST /v1/{get,update}-training-contribution (feature vectors only, optimistic
+ honest revert); (f) the last-retrain gate verdict line.
- New pure, node-tested logic (components/products/router/logic.ts, +15 tests):
normalizeStats (partial/garbage → honest empty, cost stays null not $0),
formatters (em-dash on absent), distributions by share, throughput UTC labels,
retrainLine, range→hours. Reuses ui/Charts + ui/Metric + EmptyState/
BackendStateCard — no chart dep, honest states throughout.
- Transport mirrors get-router-policy exactly: three heads added to
next.config.mjs AI_V1_HEADS + app/ai/[...path] ALLOWED (v1/router/stats,
v1/{get,update}-training-contribution) — the /ai user-bearer proxy; no new
route handlers. go:embed hits cloud natively (honest BackendStateCard until the
ai router-stats wave ships).
- Also completes the half-applied v8.4.137 rename that left origin/main
non-building: RouterModule.tsx (the editor) → RouterPolicyEditor.tsx with its
broken ~/lib/api/router-policy import + InferenceRouterModule export fixed; the
registry entry repointed (id inference-router → router). No package.json bump.
tsc clean; vitest 2540/2540 (213 files, +15); next build ✓; build:embed ✓.
Claude-Session: https://claude.ai/code/session_015Z1iLf7QBrq1LhignJrzDw
Upgrade the `router` product from the single policy-editor route into a two-tab
Router dashboard: Overview (routing observability) + Policy (the reused λ/µ
editor). One editor, one place — no duplication.
Overview reads GET /v1/router/stats (org-scoped, RequirePrincipal) and renders:
(a) cost saved as a blended $/MTok PROXY — saved_pct + routed vs counterfactual
index + cumulative saved, honest "—" when priced_events==0; (b) quality proxy —
reward_rate + coverage, engine_share, avg_confidence, shadow_agreement only when
non-null; (c) per-task routed-model distribution (Donut) + by-model Donut +
throughput LineChart; (e) an opt-in training-contribution toggle wired to
GET/POST /v1/{get,update}-training-contribution (feature vectors only, optimistic
+ honest revert); (f) the last-retrain gate verdict line.
- New pure, node-tested logic (components/products/router/logic.ts, +15 tests):
normalizeStats (partial/garbage → honest empty, cost stays null not $0),
formatters (em-dash on absent), distributions by share, throughput UTC labels,
retrainLine, range→hours. Reuses ui/Charts + ui/Metric + EmptyState/
BackendStateCard — no chart dep, honest states throughout.
- Transport mirrors get-router-policy exactly: three heads added to
next.config.mjs AI_V1_HEADS + app/ai/[...path] ALLOWED (v1/router/stats,
v1/{get,update}-training-contribution) — the /ai user-bearer proxy; no new
route handlers. go:embed hits cloud natively (honest BackendStateCard until the
ai router-stats wave ships).
- Also completes the half-applied v8.4.137 rename that left origin/main
non-building: RouterModule.tsx (the editor) → RouterPolicyEditor.tsx with its
broken ~/lib/api/router-policy import + InferenceRouterModule export fixed; the
registry entry repointed (id inference-router → router). No package.json bump.
tsc clean; vitest 2540/2540 (213 files, +15); next build ✓; build:embed ✓.
New AI-category product 'inference-router': org admins edit their own task →
model-pool prefer table + per-1k cost ceiling over the new hanzoai/ai
/v1/get-router-policy + /v1/update-router-policy (org-admin gated, self-scoped,
org > '*' > conf fold). v1-first transport: originGet/originPost + the two heads
added to AI_V1_HEADS dispatch and the /ai proxy ALLOWED set — no new route
handlers. tsc clean, vitest 2525/2525, next build + build:embed green.
Claude-Session: https://claude.ai/code/session_018PmFAHZvbBSTsuWyebwMra
New AI-category product 'inference-router': org admins edit their own task →
model-pool prefer table + per-1k cost ceiling over the new hanzoai/ai
/v1/get-router-policy + /v1/update-router-policy (org-admin gated, self-scoped,
org > '*' > conf fold). v1-first transport: originGet/originPost + the two heads
added to AI_V1_HEADS dispatch and the /ai proxy ALLOWED set — no new route
handlers. tsc clean, vitest 2525/2525, next build + build:embed green.
Two fixes:
1) BOOT HANG (console.hanzo.ai splash): the session bootstrap awaited
AccountApi.session() (→ /v1/iam/get-account) with NO timeout, so a degraded
backend — the beego IAM proxy hop, a dead pruned route blocking 12s — left the
splash pending forever (diagnosed live: get-account PENDING >25s, body empty).
New reusable withTimeout() primitive caps the boot resolve at 8s → on timeout
the visitor is anonymous and the sign-in card renders; a later reload/refresh
resolves the real session. An app must never hand the browser to one request.
(Root cause is the beego get-account proxy — fixed for real by the iam2 flip.)
2) AUTO-CREDIT: removed claimWelcomeGrantOnce() from the session bootstrap — the
console auto-claimed the $5 welcome trial credit on every authenticated load.
No more automatic credit; admin grants at admin.hanzo.ai only.
The 19 local tsc errors are a node_modules gap (@hanzo/capture ^0.1.0 not npm-installed
locally); CI resolves it. session.tsx + with-timeout.ts are clean.
Two fixes:
1) BOOT HANG (console.hanzo.ai splash): the session bootstrap awaited
AccountApi.session() (→ /v1/iam/get-account) with NO timeout, so a degraded
backend — the beego IAM proxy hop, a dead pruned route blocking 12s — left the
splash pending forever (diagnosed live: get-account PENDING >25s, body empty).
New reusable withTimeout() primitive caps the boot resolve at 8s → on timeout
the visitor is anonymous and the sign-in card renders; a later reload/refresh
resolves the real session. An app must never hand the browser to one request.
(Root cause is the beego get-account proxy — fixed for real by the iam2 flip.)
2) AUTO-CREDIT: removed claimWelcomeGrantOnce() from the session bootstrap — the
console auto-claimed the $5 welcome trial credit on every authenticated load.
No more automatic credit; admin grants at admin.hanzo.ai only.
The 19 local tsc errors are a node_modules gap (@hanzo/capture ^0.1.0 not npm-installed
locally); CI resolves it. session.tsx + with-timeout.ts are clean.
New admin.hanzo.ai module (`admin: true`, category AI) answering the KEY
question "how many requests hit each model" plus unit economics and the
eval→training flywheel. Composes the existing admin reads — never forks them:
- Model mix: requests / share% / tokens / cost per (provider, model), folded
from /v1/admin/usage/funding over a 24h/7d/30d window (share donut + table +
totals row).
- Profitability: upstream cost vs revenue vs gross margin + runway
(/v1/admin/finance) and per-provider credit (/v1/admin/providers/credit).
- Training data: the HONEST collection card — the metering ledger (datastore)
holds no prompt/completion content and nothing harvests traffic; the only
training data is the user-curated eval dataset registry (live counts).
- Evals: recent LLM-as-judge runs (dataset, evaluator, score, when).
- Router loop: how eval scores fold into the enso router (offline ridge +
online LinUCB), with the honest "per-request reward not yet persisted".
Pure rollups in src/lib/api/ai-economics.ts (foldModelMix / topModelShares /
datasetStats / marginTone …) with 19 vitest cases; one route-mocked Playwright
spec (fable-5 75% mix, 62% margin, honest training card, fail-closed gate).
v8.4.135
New admin.hanzo.ai module (`admin: true`, category AI) answering the KEY
question "how many requests hit each model" plus unit economics and the
eval→training flywheel. Composes the existing admin reads — never forks them:
- Model mix: requests / share% / tokens / cost per (provider, model), folded
from /v1/admin/usage/funding over a 24h/7d/30d window (share donut + table +
totals row).
- Profitability: upstream cost vs revenue vs gross margin + runway
(/v1/admin/finance) and per-provider credit (/v1/admin/providers/credit).
- Training data: the HONEST collection card — the metering ledger (datastore)
holds no prompt/completion content and nothing harvests traffic; the only
training data is the user-curated eval dataset registry (live counts).
- Evals: recent LLM-as-judge runs (dataset, evaluator, score, when).
- Router loop: how eval scores fold into the enso router (offline ridge +
online LinUCB), with the honest "per-request reward not yet persisted".
Pure rollups in src/lib/api/ai-economics.ts (foldModelMix / topModelShares /
datasetStats / marginTone …) with 19 vitest cases; one route-mocked Playwright
spec (fable-5 75% mix, 62% margin, honest training card, fail-closed gate).
v8.4.135
The console ships into hanzoai/cloud as a Next.js STATIC EXPORT: generateMetadata
runs at build time with the default host, so the exported <title> is baked to
"Hanzo Cloud Console" for every host. The cloud serving layer rewrites it per
Host on first paint, but Next re-applies the baked metadata title on hydration,
reverting a Lux/Zoo tab to "Hanzo Cloud Console" — a white-label violation
(the visible shell was already client-branded; only the tab title leaked).
BrandTitle is a client net (mirrors ChunkGuard) that sets document.title from
window.location via the existing `branding.name` and re-affirms it through a head
MutationObserver, defeating the baked-metadata re-application. On the dynamic
standalone app the SSR title is already host-correct, so it is a no-op there.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The console ships into hanzoai/cloud as a Next.js STATIC EXPORT: generateMetadata
runs at build time with the default host, so the exported <title> is baked to
"Hanzo Cloud Console" for every host. The cloud serving layer rewrites it per
Host on first paint, but Next re-applies the baked metadata title on hydration,
reverting a Lux/Zoo tab to "Hanzo Cloud Console" — a white-label violation
(the visible shell was already client-branded; only the tab title leaked).
BrandTitle is a client net (mirrors ChunkGuard) that sets document.title from
window.location via the existing `branding.name` and re-affirms it through a head
MutationObserver, defeating the baked-metadata re-application. On the dynamic
standalone app the SSR title is already host-correct, so it is a no-op there.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Add the Interactive tab to Fine-tuning: a live LoRA client you create on a
base model, drive with forward_backward + optim_step (plotting the real loss
curve), sample from, and export a PEFT adapter.
TrainingApi hits the clean /v1-first `/v1/training/*` (next.config dispatches
the `training` head to the keyless /ai bearer proxy; the per-client
id/forward_backward/optim_step/sample/save_weights sub-paths are allow-listed,
with a DELETE handler). Engine 400/404/409 plain-text bodies surface verbatim.
Tolerant normalizers, vitest + a mocked Playwright e2e. v8.4.134.
Add the Interactive tab to Fine-tuning: a live LoRA client you create on a
base model, drive with forward_backward + optim_step (plotting the real loss
curve), sample from, and export a PEFT adapter.
TrainingApi hits the clean /v1-first `/v1/training/*` (next.config dispatches
the `training` head to the keyless /ai bearer proxy; the per-client
id/forward_backward/optim_step/sample/save_weights sub-paths are allow-listed,
with a DELETE handler). Engine 400/404/409 plain-text bodies surface verbatim.
Tolerant normalizers, vitest + a mocked Playwright e2e. v8.4.134.
Every client-facing same-origin API path is now /v1/<head>/… — one version,
no /<svc>/vN/ prefix, no nested /v1/<x>/vN/, no /api/. Supersedes the v8.4.16
/billing/v1 namespacing; completes the v8.4.120 /v1-rooted contract.
- Move 11 proxy handlers app/<svc>/… -> app/v1/<svc>/[...path] (a filesystem
route beats the /v1/[...path] cloud BFF; handlers re-root the upstream at v1/):
billing, commerce, ai-accounts (+settings/usage/routing-defaults), economy,
nodes, trading, superbase, vm. Auth/scoping/CSRF/allow-lists UNCHANGED —
only the path moved. UI tabs (/billing/*, /ai-accounts/*) still render.
- Remove the /v1/billing->/billing/v1 and /v1/commerce->/commerce/v1 rewrites.
- AI heads: playground images/videos + ai-connections build clean /v1/*;
next.config dispatches to /ai WITHOUT a nested version; app/ai re-roots at v1/.
New `ai` head so /v1/ai/connections dispatches. Fixes image/video/connections
on the go:embed console.
- Drop nested /v1/websearch/v1/scrape -> /v1/websearch/scrape; repoint apm
stale /api/v1 doc comments to the /v1/o11y the client actually calls.
- Left external (untouched): Gatus /api/v1, Cloudflare Turnstile /turnstile/v0,
Slack OAuth /oauth/v2.
tsc clean; vitest 2445/2445 (206 files); next build (route table shows every
/v1/<svc>/[...path] distinct) + build:embed green.
git grep -oE '/[a-z-]+/v[0-9]/' = external hosts only.
Every client-facing same-origin API path is now /v1/<head>/… — one version,
no /<svc>/vN/ prefix, no nested /v1/<x>/vN/, no /api/. Supersedes the v8.4.16
/billing/v1 namespacing; completes the v8.4.120 /v1-rooted contract.
- Move 11 proxy handlers app/<svc>/… -> app/v1/<svc>/[...path] (a filesystem
route beats the /v1/[...path] cloud BFF; handlers re-root the upstream at v1/):
billing, commerce, ai-accounts (+settings/usage/routing-defaults), economy,
nodes, trading, superbase, vm. Auth/scoping/CSRF/allow-lists UNCHANGED —
only the path moved. UI tabs (/billing/*, /ai-accounts/*) still render.
- Remove the /v1/billing->/billing/v1 and /v1/commerce->/commerce/v1 rewrites.
- AI heads: playground images/videos + ai-connections build clean /v1/*;
next.config dispatches to /ai WITHOUT a nested version; app/ai re-roots at v1/.
New `ai` head so /v1/ai/connections dispatches. Fixes image/video/connections
on the go:embed console.
- Drop nested /v1/websearch/v1/scrape -> /v1/websearch/scrape; repoint apm
stale /api/v1 doc comments to the /v1/o11y the client actually calls.
- Left external (untouched): Gatus /api/v1, Cloudflare Turnstile /turnstile/v0,
Slack OAuth /oauth/v2.
tsc clean; vitest 2445/2445 (206 files); next build (route table shows every
/v1/<svc>/[...path] distinct) + build:embed green.
git grep -oE '/[a-z-]+/v[0-9]/' = external hosts only.
Billing Center gains an Accounts tab: which account pays, and in what order.
Attach a billing account to the ORGANIZATION or to ONE PROJECT, see the ordered
chain, reorder it, detach it.
The chain is READ from commerce's own resolver, never recomputed here. Commerce
resolves the payer at charge time and is the one source of truth for who pays, so
the page writes a PRIORITY and re-reads the chain — it never predicts the order.
A local re-sort would be a second, divergent answer to the one question that must
have exactly one, and would start lying the moment commerce's ordering rule moves.
Attach and reorder are the SAME call: a binding's row id is deterministic in
(holderKind, holderId, accountId), so re-asserting a pair at a new priority
updates that one row. Reordering is not a second verb.
Priorities are anchored on the anchor's fixed 0, so a link promoted above the
derived subject gets a negative priority — how an explicit binding preempts the
anchor. An attach always lands at the END, never silently taking over today's
payer.
The holder is derived, never asserted. Whose chain an account attaches to is a
payer decision, so the browser names a holder KIND and the /billing proxy derives
holderId from the session — the same pin scopedBillingSearch already applies to
the billing subject, extended to the one write body that names a holder. A body
with no holderKind is untouched, so a spend-alert (whose scope IS a project name)
passes through unchanged.
The project switcher additionally sends X-Act-As-Project: an intent and an
assertion must not share a name. The intent is a request a validating boundary
checks against the caller's scope set before minting the authoritative
X-Project-Id; the existing X-Project-Id stamp is unchanged and stays advisory
(the gateway strips it, the /v1 /vm /commerce proxies drop it per the RED MED-1
eval-isolation invariant). The intent is consumed by a boundary and never
forwarded to a backend.
Reuses @hanzo/gui + the shared BackendState/PageHeader/EmptyState primitives; no
component forked, no brand literal (white-label safe). Routes are /v1 only.
Tests: 2499 green (208 files), tsc clean, next build compiles. Each guard proven
non-vacuous by neutering it and watching it fail — including one order test that
passed under neuter until its fixture was fixed to be priority-unsorted.
Billing Center gains an Accounts tab: which account pays, and in what order.
Attach a billing account to the ORGANIZATION or to ONE PROJECT, see the ordered
chain, reorder it, detach it.
The chain is READ from commerce's own resolver, never recomputed here. Commerce
resolves the payer at charge time and is the one source of truth for who pays, so
the page writes a PRIORITY and re-reads the chain — it never predicts the order.
A local re-sort would be a second, divergent answer to the one question that must
have exactly one, and would start lying the moment commerce's ordering rule moves.
Attach and reorder are the SAME call: a binding's row id is deterministic in
(holderKind, holderId, accountId), so re-asserting a pair at a new priority
updates that one row. Reordering is not a second verb.
Priorities are anchored on the anchor's fixed 0, so a link promoted above the
derived subject gets a negative priority — how an explicit binding preempts the
anchor. An attach always lands at the END, never silently taking over today's
payer.
The holder is derived, never asserted. Whose chain an account attaches to is a
payer decision, so the browser names a holder KIND and the /billing proxy derives
holderId from the session — the same pin scopedBillingSearch already applies to
the billing subject, extended to the one write body that names a holder. A body
with no holderKind is untouched, so a spend-alert (whose scope IS a project name)
passes through unchanged.
The project switcher additionally sends X-Act-As-Project: an intent and an
assertion must not share a name. The intent is a request a validating boundary
checks against the caller's scope set before minting the authoritative
X-Project-Id; the existing X-Project-Id stamp is unchanged and stays advisory
(the gateway strips it, the /v1 /vm /commerce proxies drop it per the RED MED-1
eval-isolation invariant). The intent is consumed by a boundary and never
forwarded to a backend.
Reuses @hanzo/gui + the shared BackendState/PageHeader/EmptyState primitives; no
component forked, no brand literal (white-label safe). Routes are /v1 only.
Tests: 2499 green (208 files), tsc clean, next build compiles. Each guard proven
non-vacuous by neutering it and watching it fail — including one order test that
passed under neuter until its fixture was fixed to be priority-unsorted.
The admin.hanzo.ai launch dashboard: govern access to every hosted service and
approve users, wired to the cloud featuregate control plane + IAM iam#104.
- FeatureGateModule: a Services board (per-service waitlist-mode toggle — remove
the waitlist one service at a time) + a Pending-Users approval queue.
- src/lib/api/admin-featuregate.ts: client over /v1/admin/services* (list, toggle,
onboard) through the global-admin-gated /admin/aggregate proxy (+ normalizer test).
- IamAdminApi.pendingUsers/approveUser/rejectUser: REUSE the IAM approval API
(iam#104) via the existing global-admin /admin/iam proxy — no second approval store.
- Wiring: 'services' added to ADMIN_AGGREGATE_HEADS + next.config ADMIN_V1_HEADS;
get-pending-users / approve-user / reject-user added to the /admin/iam allow-list.
- Registered as 'launch-control' (admin-only, Security category).
- tsc --noEmit clean; vitest green (client normalizers + allow-list).
The admin.hanzo.ai launch dashboard: govern access to every hosted service and
approve users, wired to the cloud featuregate control plane + IAM iam#104.
- FeatureGateModule: a Services board (per-service waitlist-mode toggle — remove
the waitlist one service at a time) + a Pending-Users approval queue.
- src/lib/api/admin-featuregate.ts: client over /v1/admin/services* (list, toggle,
onboard) through the global-admin-gated /admin/aggregate proxy (+ normalizer test).
- IamAdminApi.pendingUsers/approveUser/rejectUser: REUSE the IAM approval API
(iam#104) via the existing global-admin /admin/iam proxy — no second approval store.
- Wiring: 'services' added to ADMIN_AGGREGATE_HEADS + next.config ADMIN_V1_HEADS;
get-pending-users / approve-user / reject-user added to the /admin/iam allow-list.
- Registered as 'launch-control' (admin-only, Security category).
- tsc --noEmit clean; vitest green (client normalizers + allow-list).
The customer GPUs page now makes both paths to add a GPU explicit and equal:
- "Connect GPU" opens a drawer with the ready-to-copy `hanzo login && hanzo gpu
connect` (+ `--serve-engine` to also serve models) and the Desktop toggle note.
- "Deploy GPU" is the existing Visor/DOKS launch flow (relabeled from "Launch GPU").
Machine rows gain a monochrome Source badge distinguishing BYO (provider=byo) from
Cloud accelerators; the empty state offers both actions.
- gpus/ConnectGpuDrawer.tsx: the BYO connect drawer (copy-to-run commands).
- gpus/CustomerGpus.tsx: Connect+Deploy header actions, ProviderBadge, Source column.
- e2e/gpus-connect.spec.ts: mocked-network screenshot proof (BYO GB10 + cloud H100).
The customer GPUs page now makes both paths to add a GPU explicit and equal:
- "Connect GPU" opens a drawer with the ready-to-copy `hanzo login && hanzo gpu
connect` (+ `--serve-engine` to also serve models) and the Desktop toggle note.
- "Deploy GPU" is the existing Visor/DOKS launch flow (relabeled from "Launch GPU").
Machine rows gain a monochrome Source badge distinguishing BYO (provider=byo) from
Cloud accelerators; the empty state offers both actions.
- gpus/ConnectGpuDrawer.tsx: the BYO connect drawer (copy-to-run commands).
- gpus/CustomerGpus.tsx: Connect+Deploy header actions, ProviderBadge, Source column.
- e2e/gpus-connect.spec.ts: mocked-network screenshot proof (BYO GB10 + cloud H100).
- ConnectionsModule: a real, prominent Connections page (AI category) over the
EXISTING AiConnectionsApi — connect OpenAI/Anthropic/Google by API key or OAuth,
disconnect, honest states. Keys sealed to KMS server-side, never in the browser.
- ai-connections.ts: host-aware base (embed -> cloud native /v1; standalone -> the
narrow /ai bearer proxy, mirroring billing/commerce IS_EMBED) so it works on the
go:embed console.hanzo.ai; + usage()/listWithUsage() import methods.
- AiUsageModule: render <UsagePanel> (native) AND <ConnectedUsage> (imported) together
— the cross-provider plane; per-provider isolation, honest empty until connected.
- /ai proxy allow-lists the /v1/ai/connections/:provider/usage sub-path (standalone).
- @hanzo/usage ^0.1.5. typecheck + build:embed green; 2440 tests pass (+5 new).
- ConnectionsModule: a real, prominent Connections page (AI category) over the
EXISTING AiConnectionsApi — connect OpenAI/Anthropic/Google by API key or OAuth,
disconnect, honest states. Keys sealed to KMS server-side, never in the browser.
- ai-connections.ts: host-aware base (embed -> cloud native /v1; standalone -> the
narrow /ai bearer proxy, mirroring billing/commerce IS_EMBED) so it works on the
go:embed console.hanzo.ai; + usage()/listWithUsage() import methods.
- AiUsageModule: render <UsagePanel> (native) AND <ConnectedUsage> (imported) together
— the cross-provider plane; per-provider isolation, honest empty until connected.
- /ai proxy allow-lists the /v1/ai/connections/:provider/usage sub-path (standalone).
- @hanzo/usage ^0.1.5. typecheck + build:embed green; 2440 tests pass (+5 new).
ONE source of truth: render the social row purely from IAM get-app-login (the
app real provider list). Drop FALLBACK_PROVIDERS — a hardcoded set drifts from
IAM and can show a button IAM cannot honor. Empty list (loading or IAM
unreachable) => no social buttons; email/password stays. signInProvidersOf now
returns a plain array (one type, no null branch).
ONE source of truth: render the social row purely from IAM get-app-login (the
app real provider list). Drop FALLBACK_PROVIDERS — a hardcoded set drifts from
IAM and can show a button IAM cannot honor. Empty list (loading or IAM
unreachable) => no social buttons; email/password stays. signInProvidersOf now
returns a plain array (one type, no null branch).
The landing `overview` living board's PRIMARY source is the super-admin
`/v1/admin/overview` god-view (gated to the reserved `admin` org), which 403s a
non-super-admin — even an org's OWN admin (e.g. `hanzo/z`, Admin). It is meant to
fall back to the tenant usage ledger so it is never blank, but the fallback read
`UsageApi.overview` -> the `/billing/usage` Next BFF proxy, whose route handler is
PRUNED from the go:embed console that serves console.hanzo.ai. In the embed that
fallback failed and surfaced the honest-but-wrong "Access required" card instead of
the org's real spend.
Repoint the fallback at cloud's NATIVE `GET /v1/get-cloud-usages` (via the existing
`CloudUsageApi`) -- the SAME source the AI Metrics board (`AiUsageModule`) already
reads. It is org-scoped server-side and cookie-authed, so a non-super-admin gets a
200 for THEIR org and the board renders real usage; being cloud-native it also works
in the embed. A 403 on the admin aggregate still falls through here silently (the
isSuperAdmin gate already skips the aggregate for tenants).
DRY: the ONE `fromCloudUsage` adapter now accepts the canonical `@hanzo/usage`
`CloudUsageOverview` (what get-cloud-usages returns), reading the console-only
`byStatus` slice as an optional extension -- so BOTH usage sources (the cloud
aggregate and the `/billing` ledger rollup) flow through it unchanged.
tsc clean; vitest 2435/2435; build:embed green.
The landing `overview` living board's PRIMARY source is the super-admin
`/v1/admin/overview` god-view (gated to the reserved `admin` org), which 403s a
non-super-admin — even an org's OWN admin (e.g. `hanzo/z`, Admin). It is meant to
fall back to the tenant usage ledger so it is never blank, but the fallback read
`UsageApi.overview` -> the `/billing/usage` Next BFF proxy, whose route handler is
PRUNED from the go:embed console that serves console.hanzo.ai. In the embed that
fallback failed and surfaced the honest-but-wrong "Access required" card instead of
the org's real spend.
Repoint the fallback at cloud's NATIVE `GET /v1/get-cloud-usages` (via the existing
`CloudUsageApi`) -- the SAME source the AI Metrics board (`AiUsageModule`) already
reads. It is org-scoped server-side and cookie-authed, so a non-super-admin gets a
200 for THEIR org and the board renders real usage; being cloud-native it also works
in the embed. A 403 on the admin aggregate still falls through here silently (the
isSuperAdmin gate already skips the aggregate for tenants).
DRY: the ONE `fromCloudUsage` adapter now accepts the canonical `@hanzo/usage`
`CloudUsageOverview` (what get-cloud-usages returns), reading the console-only
`byStatus` slice as an optional extension -- so BOTH usage sources (the cloud
aggregate and the `/billing` ledger rollup) flow through it unchanged.
tsc clean; vitest 2435/2435; build:embed green.
Shared @hanzo/capture analytics client wired through AnalyticsProvider + AnalyticsBridge; sign-in/signup funnel, api-keys, plans, projects, paas create events. Rebased onto main (post QR-drop, post link-manager); version bumped to v8.4.133 so the main-push image build publishes a fresh semver tag. tsc --noEmit clean; all touched components are client components.
Shared @hanzo/capture analytics client wired through AnalyticsProvider + AnalyticsBridge; sign-in/signup funnel, api-keys, plans, projects, paas create events. Rebased onto main (post QR-drop, post link-manager); version bumped to v8.4.133 so the main-push image build publishes a fresh semver tag. tsc --noEmit clean; all touched components are client components.
A new Machines tab on the AI Accounts product: every provider account signed into
Claude Code / Codex / the CLI across your machines, grouped by device, with each
account's live usage (session/weekly rate limits, tokens, spend), how it BILLS (a
subscription bills your plan; an api key bills credits), the device's active
sessions, and a per-account / per-device LOG OUT that revokes the account and stops
its running sessions — plus the redundancy route plan (subscriptions first, then the
metered API backstop) across your accounts.
- lib/api/links.ts — the /v1/links client (cloudProxyV1Url; defensive normalizers);
'links' added to CLOUD_HEADS.
- ai-accounts/links-logic.ts — pure labels/tones/formatting + the KPI roll-up.
- ai-accounts/MachinesTab.tsx — the dashboard (honest loading/error/empty states,
@hanzo/gui v5 shorthands, mobile-responsive flexWrap rows).
- AIAccountsModule + registry: the Machines tab + subpage.
Every number is real from /v1/links or an honest '—'; nothing fabricated. tsc clean;
vitest 2435/2435 (+13); build:embed green. Reachability is the post-deploy gate
(same /v1 BFF / go:embed contract as agents).
A new Machines tab on the AI Accounts product: every provider account signed into
agent / Codex / the CLI across your machines, grouped by device, with each
account's live usage (session/weekly rate limits, tokens, spend), how it BILLS (a
subscription bills your plan; an api key bills credits), the device's active
sessions, and a per-account / per-device LOG OUT that revokes the account and stops
its running sessions — plus the redundancy route plan (subscriptions first, then the
metered API backstop) across your accounts.
- lib/api/links.ts — the /v1/links client (cloudProxyV1Url; defensive normalizers);
'links' added to CLOUD_HEADS.
- ai-accounts/links-logic.ts — pure labels/tones/formatting + the KPI roll-up.
- ai-accounts/MachinesTab.tsx — the dashboard (honest loading/error/empty states,
@hanzo/gui v5 shorthands, mobile-responsive flexWrap rows).
- AIAccountsModule + registry: the Machines tab + subpage.
Every number is real from /v1/links or an honest '—'; nothing fabricated. tsc clean;
vitest 2435/2435 (+13); build:embed green. Reachability is the post-deploy gate
(same /v1 BFF / go:embed contract as agents).
Connect the Hanzo GitHub App (existing connect flow) -> a connected GitHub card
opens a repositories view listing the org's granted repos with per-repo import +
live sync status (Not imported / Importing / Synced / Conflict) and import-all.
GitHubApi over the same-origin /v1/integrations head.
Connect the Hanzo GitHub App (existing connect flow) -> a connected GitHub card
opens a repositories view listing the org's granted repos with per-repo import +
live sync status (Not imported / Importing / Synced / Conflict) and import-all.
GitHubApi over the same-origin /v1/integrations head.
A new AI product (Mission Control) over the live agent-session plane
(/v1/agents/sessions): swipe one live terminal per agent session, drive it
(pause/resume/stop/message), and roster the run-targets (#48) with which
sessions run where. Server-side org isolation; pure logic unit-tested; the
catch-all renders it. Ships to console.hanzo.ai via the cloud embed of console@main.
A new AI product (Mission Control) over the live agent-session plane
(/v1/agents/sessions): swipe one live terminal per agent session, drive it
(pause/resume/stop/message), and roster the run-targets (#48) with which
sessions run where. Server-side org isolation; pure logic unit-tested; the
catch-all renders it. Ships to console.hanzo.ai via the cloud embed of console@main.
A new AI-category product over the live agent-session plane
(/v1/agents/sessions): one swipe card per session — a live terminal (the
event stream tailed over SSE, poll backstop), a status pill, the machine/
repo/agent it runs on, and the plane's control ops (pause/resume/stop/
message). A Devices view rosters the run-targets (#48) unioned with the
hosts live sessions report, showing which sessions run where, with a
link-a-computer form. Org isolation is server-side (bearer owner).
MissionControlApi over the same-origin /v1 (agents head already allow-listed);
pure logic unit-tested (deviceRoster union/no-double-count, eventLine,
mergeEvents, normalizers).
A new AI-category product over the live agent-session plane
(/v1/agents/sessions): one swipe card per session — a live terminal (the
event stream tailed over SSE, poll backstop), a status pill, the machine/
repo/agent it runs on, and the plane's control ops (pause/resume/stop/
message). A Devices view rosters the run-targets (#48) unioned with the
hosts live sessions report, showing which sessions run where, with a
link-a-computer form. Org isolation is server-side (bearer owner).
MissionControlApi over the same-origin /v1 (agents head already allow-listed);
pure logic unit-tested (deviceRoster union/no-double-count, eventLine,
mergeEvents, normalizers).
OrgIntegrationsModule: a connected GitHub card opens a repositories view
(GitHubReposView) listing the org's granted repos with per-repo import + live
sync status (Not imported / Importing / Synced / Conflict) and an import-all
action. GitHubApi (listRepos/importRepos) over the same-origin /v1/integrations
head; pure logic + normalizers unit-tested; StatusTag learns synced/conflict/importing.
OrgIntegrationsModule: a connected GitHub card opens a repositories view
(GitHubReposView) listing the org's granted repos with per-repo import + live
sync status (Not imported / Importing / Synced / Conflict) and an import-all
action. GitHubApi (listRepos/importRepos) over the same-origin /v1/integrations
head; pure logic + normalizers unit-tested; StatusTag learns synced/conflict/importing.
The QR sign-in card set an hz_session cookie sealed with the console secret that
cloud's /v1 can't read, while console.hanzo.ai authenticates via the casibase
session — so a QR login left the user effectively signed out for data calls, and
the /auth/device BFF 405s on the static embed anyway. Remove the button, the qr
view, and the dead QrSignIn component + iam-device wire + /auth/device route. One
way in: password + social + email signup. v8.4.131.
The QR sign-in card set an hz_session cookie sealed with the console secret that
cloud's /v1 can't read, while console.hanzo.ai authenticates via the casibase
session — so a QR login left the user effectively signed out for data calls, and
the /auth/device BFF 405s on the static embed anyway. Remove the button, the qr
view, and the dead QrSignIn component + iam-device wire + /auth/device route. One
way in: password + social + email signup. v8.4.131.
The embedded login hardcoded its social buttons, which drifted from IAM:
'Continue with GitLab' hinted provider-gitlab, a provider the hanzo-cloud app
does not have — IAM could not auto-advance and stranded the user on the
hanzo.id login page with no GitLab option (the reported 'redirects to hanzo.id
and doesn't have social options' dead-end). GitHub/Google were verified live to
auto-advance clean; GitLab reproduced the strand headless.
ONE source of truth: SignInForm now renders its social row from
get-app-login's real provider list (CORS-open to the console origin, verified),
mapped per provider TYPE (GitHub/Google/GitLab/Apple/Web3) — an unknown type
renders nothing, and a provider IAM can't honor never gets a button. Fallback
while loading / on a failed read = the set proven live (GitHub+Google+Wallet),
never GitLab. Apple (live on the app) now shows. +4 tests pin the normalizer
and the no-GitLab fallback.
Claude-Session: https://claude.ai/code/session_01XptqW83ZLpqyGBENc1wAQz
The embedded login hardcoded its social buttons, which drifted from IAM:
'Continue with GitLab' hinted provider-gitlab, a provider the hanzo-cloud app
does not have — IAM could not auto-advance and stranded the user on the
hanzo.id login page with no GitLab option (the reported 'redirects to hanzo.id
and doesn't have social options' dead-end). GitHub/Google were verified live to
auto-advance clean; GitLab reproduced the strand headless.
ONE source of truth: SignInForm now renders its social row from
get-app-login's real provider list (CORS-open to the console origin, verified),
mapped per provider TYPE (GitHub/Google/GitLab/Apple/Web3) — an unknown type
renders nothing, and a provider IAM can't honor never gets a button. Fallback
while loading / on a failed read = the set proven live (GitHub+Google+Wallet),
never GitLab. Apple (live on the app) now shows. +4 tests pin the normalizer
and the no-GitLab fallback.
Extend the affiliate dashboard onto cloud's new /v1/affiliates surface: per-period
share LineChart + per-referral aggregate, referral-link manager with click/signup/
conversion stats, privacy-preserving leaderboard (opt-in handle + your own rank,
never an org identity), and a SuperAdmin set-rate action. tsc clean, 2394 vitest
pass, next build green.
Extend the affiliate dashboard onto cloud's new /v1/affiliates surface: per-period
share LineChart + per-referral aggregate, referral-link manager with click/signup/
conversion stats, privacy-preserving leaderboard (opt-in handle + your own rank,
never an org identity), and a SuperAdmin set-rate action. tsc clean, 2394 vitest
pass, next build green.
Extend the affiliate dashboard onto the new cloud /v1/affiliates surface:
- Rewards panel: per-period share LineChart + per-direct-referral aggregate
contribution + the profit-share basis (your rate of Hanzo's margin).
- Referral links panel: list links with click/signup/conversion stats, copy,
and create (label + auto-minted code), respecting the per-affiliate cap.
- Leaderboard panel: opt-in handle + your own rank (always visible) + aggregate
only; never another org's identity.
- Admin: a Set-rate action (percent -> bps, capped at 93%) beside approve/payout.
- Wire a best-effort click ping into the ?aff capture (once per code/session).
API: AffiliatesApi.{earnings,links,createLink,setHandle,leaderboard,click} +
marginBps/handle on the overview; AdminAffiliatesApi.setRate. logic.{monthLabel,
percentToBps}. Defensive normalizers throughout.
Tests: normalizer + exact-path transport tests for every new call; monthLabel +
percentToBps units. tsc clean, 2394 vitest pass, next build green.
Extend the affiliate dashboard onto the new cloud /v1/affiliates surface:
- Rewards panel: per-period share LineChart + per-direct-referral aggregate
contribution + the profit-share basis (your rate of Hanzo's margin).
- Referral links panel: list links with click/signup/conversion stats, copy,
and create (label + auto-minted code), respecting the per-affiliate cap.
- Leaderboard panel: opt-in handle + your own rank (always visible) + aggregate
only; never another org's identity.
- Admin: a Set-rate action (percent -> bps, capped at 93%) beside approve/payout.
- Wire a best-effort click ping into the ?aff capture (once per code/session).
API: AffiliatesApi.{earnings,links,createLink,setHandle,leaderboard,click} +
marginBps/handle on the overview; AdminAffiliatesApi.setRate. logic.{monthLabel,
percentToBps}. Defensive normalizers throughout.
Tests: normalizer + exact-path transport tests for every new call; monthLabel +
percentToBps units. tsc clean, 2394 vitest pass, next build green.
Adds Continue-with-GitLab and Connect-Wallet buttons alongside GitHub/Google,
handing off to the hanzo.id hosted login via provider_hint. tsc clean; 2382
vitest tests pass.
Adds Continue-with-GitLab and Connect-Wallet buttons alongside GitHub/Google,
handing off to the hanzo.id hosted login via provider_hint. tsc clean; 2382
vitest tests pass.
Add "Continue with GitLab" (signInWith provider-gitlab) and "Connect Wallet"
(signInWith provider-web3) buttons alongside GitHub/Google. Both hand off to the
hanzo.id hosted login via provider_hint like the existing social buttons; the
wallet button lands on the login page where the native multi-chain SIWx flow
runs and returns an authorization code to /auth/callback.
Add "Continue with GitLab" (signInWith provider-gitlab) and "Connect Wallet"
(signInWith provider-web3) buttons alongside GitHub/Google. Both hand off to the
hanzo.id hosted login via provider_hint like the existing social buttons; the
wallet button lands on the login page where the native multi-chain SIWx flow
runs and returns an authorization code to /auth/callback.
Thin console surface for the native ArgoCD replacement: a GitOps product
(admin: true, Platform category) that reads the services.hanzo.ai operator CRs
through cloud's /v1/gitops/* — the console holds no cluster creds, cloud enforces
SuperAdmin. Applications board (name/version/health/sync + rollback/sync), an
application detail (header, actions, owned-resource inventory, rollout history,
logs), health/sync pills. The heavy topology/diff/log UI is deferred to the
parallel @hanzo/ui/gitops export via a documented MOUNT SEAM (ui-contract.ts) —
the pure treeToGraph adapter already maps into its @hanzo/canvas model. Adds the
gitops head to proxy-allow CLOUD_HEADS. tsc clean, 2353 tests green.
Thin console surface for the native ArgoCD replacement: a GitOps product
(admin: true, Platform category) that reads the services.hanzo.ai operator CRs
through cloud's /v1/gitops/* — the console holds no cluster creds, cloud enforces
SuperAdmin. Applications board (name/version/health/sync + rollback/sync), an
application detail (header, actions, owned-resource inventory, rollout history,
logs), health/sync pills. The heavy topology/diff/log UI is deferred to the
parallel @hanzo/ui/gitops export via a documented MOUNT SEAM (ui-contract.ts) —
the pure treeToGraph adapter already maps into its @hanzo/canvas model. Adds the
gitops head to proxy-allow CLOUD_HEADS. tsc clean, 2353 tests green.
Rename the deploy-plane client to the GitOps namespace the cloud agent owns:
GET /v1/gitops/applications, /{name}/tree, /{name}/resource/{ref}, /{name}/logs,
POST /{name}/rollback, POST /{name}/sync (sync replaces restart). Domain nouns
follow ArgoCD: Application/HealthStatus/SyncStatus. Pure folds + tree adapter
unchanged (feed the interim board and @hanzo/ui/gitops when it lands). 33 tests.
Rename the deploy-plane client to the GitOps namespace the cloud agent owns:
GET /v1/gitops/applications, /{name}/tree, /{name}/resource/{ref}, /{name}/logs,
POST /{name}/rollback, POST /{name}/sync (sync replaces restart). Domain nouns
follow ArgoCD: Application/HealthStatus/SyncStatus. Pure folds + tree adapter
unchanged (feed the interim board and @hanzo/ui/gitops when it lands). 33 tests.
Consumes the cloud-owned /v1/deploys contract (list/tree/resource/logs/rollback)
that reads the services.hanzo.ai operator CRs — the native ArgoCD-free deploy
plane. Pure logic folds CR .status (phase + ready replicas) into ArgoCD-style
health, desired-vs-live image tag into sync, and a CR's owned-resource tree into
the @hanzo/canvas node/edge model. 31 unit tests green.
Consumes the cloud-owned /v1/deploys contract (list/tree/resource/logs/rollback)
that reads the services.hanzo.ai operator CRs — the native ArgoCD-free deploy
plane. Pure logic folds CR .status (phase + ready replicas) into ArgoCD-style
health, desired-vs-live image tag into sync, and a CR's owned-resource tree into
the @hanzo/canvas node/edge model. 31 unit tests green.
The go:embed'd console serves the SPA shell (the / route's index.html) for every
path — verified live: GET / and GET /signin return byte-identical HTML. So a direct
/signin load mounts the dashboard tree (AuthGate), not the /signin route. AuthGate saw
no account and called router.replace('/signin'), a no-op at /signin, and spun on the
loader forever (inputs=0, buttons=0). Reaching /signin as a redirect target (from /,
/projects, ...) worked because the URL changed.
Extract the sign-in experience into one <SignIn/> component (tenant form / admin silent
SSO / redirect-to-/ when authed) rendered by BOTH the /signin route and AuthGate: at
/signin AuthGate defers to <SignIn/> instead of a no-op redirect, so /signin resolves to
the form without depending on a navigation. Add an e2e regression that hard-loads /signin
and asserts the form renders.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The go:embed'd console serves the SPA shell (the / route's index.html) for every
path — verified live: GET / and GET /signin return byte-identical HTML. So a direct
/signin load mounts the dashboard tree (AuthGate), not the /signin route. AuthGate saw
no account and called router.replace('/signin'), a no-op at /signin, and spun on the
loader forever (inputs=0, buttons=0). Reaching /signin as a redirect target (from /,
/projects, ...) worked because the URL changed.
Extract the sign-in experience into one <SignIn/> component (tenant form / admin silent
SSO / redirect-to-/ when authed) rendered by BOTH the /signin route and AuthGate: at
/signin AuthGate defers to <SignIn/> instead of a no-op redirect, so /signin resolves to
the form without depending on a navigation. Add an e2e regression that hard-loads /signin
and asserts the form renders.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Org-level Guide module over the real cloud clients/guide surface: an
interactive launch checklist the Business AI can complete for you.
- GuideModule.tsx — launch-progress bar (Complete/Total/Next tiles), a
focused current-step card (why · how-on-Hanzo · done-when + Mark done /
Skip / a primary Do-it-for-me), and the full step list with a state chip,
a blocked/lock hint, and inline per-row actions on non-terminal steps.
- Do-it-for-me streams the agent's plan → draft → action → result → state
events live (SSE via streamDo), aborts on unmount/close, and falls back
to the non-streaming JSON do when the backend can't stream. An error
event stays an error — success is never fabricated; states are loading /
BackendStateCard / empty throughout.
- Consumes the pre-written guide API client (GuideApi + streamDo, defensive
normalizers) + pure view logic (stateLabel/currentStep/clampPercent/…),
both unit-tested (17 tests). Fix: putCurriculum now takes a parsed object
(the transport JSON-encodes once) instead of a pre-serialized string,
which the restPut body would double-encode.
- Wiring: `guide` added to proxy-allow CLOUD_HEADS (the /v1 bearer BFF
forwards /v1/guide/*), one catalog entry + import in registry.tsx
(Apps, routes '' and ':tab'), and `guide` added to ALWAYS_ON_PRODUCTS so
every org sees the foundational onboarding surface (like 'platform').
Ships to console.hanzo.ai via the next hanzoai/cloud release embedding
console@main; build:embed stays green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Org-level Guide module over the real cloud clients/guide surface: an
interactive launch checklist the Business AI can complete for you.
- GuideModule.tsx — launch-progress bar (Complete/Total/Next tiles), a
focused current-step card (why · how-on-Hanzo · done-when + Mark done /
Skip / a primary Do-it-for-me), and the full step list with a state chip,
a blocked/lock hint, and inline per-row actions on non-terminal steps.
- Do-it-for-me streams the agent's plan → draft → action → result → state
events live (SSE via streamDo), aborts on unmount/close, and falls back
to the non-streaming JSON do when the backend can't stream. An error
event stays an error — success is never fabricated; states are loading /
BackendStateCard / empty throughout.
- Consumes the pre-written guide API client (GuideApi + streamDo, defensive
normalizers) + pure view logic (stateLabel/currentStep/clampPercent/…),
both unit-tested (17 tests). Fix: putCurriculum now takes a parsed object
(the transport JSON-encodes once) instead of a pre-serialized string,
which the restPut body would double-encode.
- Wiring: `guide` added to proxy-allow CLOUD_HEADS (the /v1 bearer BFF
forwards /v1/guide/*), one catalog entry + import in registry.tsx
(Apps, routes '' and ':tab'), and `guide` added to ALWAYS_ON_PRODUCTS so
every org sees the foundational onboarding surface (like 'platform').
Ships to console.hanzo.ai via the next hanzoai/cloud release embedding
console@main; build:embed stays green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Reads GET /v1/kb/graph (kb-page/kb-memory/kb-source nodes; parent,
wikilink, provenance edges) and renders a deterministic Fruchterman-
Reingold force graph on a CSP-safe canvas, click-to-inspect. Import
panel POSTs an Obsidian/Notion/Roam/Evernote export to /v1/kb/import.
Both ride the same-origin /v1 user-bearer BFF; 'kb'/'knowledge' heads
allow-listed in proxy-allow. Registered in the product registry under
AI as 'Knowledge'. Pure graph-logic (normalize/layout/hitTest) is unit
tested (8 vitest cases); proxy-allow head list stays green (25 cases).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Reads GET /v1/kb/graph (kb-page/kb-memory/kb-source nodes; parent,
wikilink, provenance edges) and renders a deterministic Fruchterman-
Reingold force graph on a CSP-safe canvas, click-to-inspect. Import
panel POSTs an Obsidian/Notion/Roam/Evernote export to /v1/kb/import.
Both ride the same-origin /v1 user-bearer BFF; 'kb'/'knowledge' heads
allow-listed in proxy-allow. Registered in the product registry under
AI as 'Knowledge'. Pure graph-logic (normalize/layout/hitTest) is unit
tested (8 vitest cases); proxy-allow head list stays green (25 cases).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Mount AnalyticsProvider (product: console, cookie/same-origin — the tenant is
stamped server-side, no getToken) inside the session so identify can bind the
signed-in actor. AnalyticsBridge fires route-change pageviews via
usePageview(usePathname()) and identifies the person by the stable owner/name
actor id (never email; anonymous sessions skipped).
Capture EVENTS at the real surfaces:
- signup funnel (SignInForm): SIGNUP_VIEWED on the create-account view,
SIGNUP_SUBMITTED on submit, SIGNUP_COMPLETED on account creation (self-serve
signup has no separate verify step).
- first action (onboarding LaunchStep): FIRST_ACTION on the first product tile.
- upgrade intent (PlansModule): PRICING_VIEWED on view, PLAN_CLICKED +
CHECKOUT_STARTED on a plan CTA.
- feature usage: API_KEY_CREATED (ApiKeysModule), PROJECT_CREATED / APP_CREATED
/ DEPLOY_STARTED (PaaS CreateAppForm), PROJECT_CREATED (ProjectsModule).
No secrets/PII captured — only user/org ids and non-sensitive props.
Mount AnalyticsProvider (product: console, cookie/same-origin — the tenant is
stamped server-side, no getToken) inside the session so identify can bind the
signed-in actor. AnalyticsBridge fires route-change pageviews via
usePageview(usePathname()) and identifies the person by the stable owner/name
actor id (never email; anonymous sessions skipped).
Capture EVENTS at the real surfaces:
- signup funnel (SignInForm): SIGNUP_VIEWED on the create-account view,
SIGNUP_SUBMITTED on submit, SIGNUP_COMPLETED on account creation (self-serve
signup has no separate verify step).
- first action (onboarding LaunchStep): FIRST_ACTION on the first product tile.
- upgrade intent (PlansModule): PRICING_VIEWED on view, PLAN_CLICKED +
CHECKOUT_STARTED on a plan CTA.
- feature usage: API_KEY_CREATED (ApiKeysModule), PROJECT_CREATED / APP_CREATED
/ DEPLOY_STARTED (PaaS CreateAppForm), PROJECT_CREATED (ProjectsModule).
No secrets/PII captured — only user/org ids and non-sensitive props.
@hanzo/usage 0.1.4 ships the gui/Tamagui <UsagePanel> at its own ./panel
source subpath (./react is the DOM <UsageDashboard>). Point AiUsageModule at
./panel and bump the dep. typecheck green.
@hanzo/usage 0.1.4 ships the gui/Tamagui <UsagePanel> at its own ./panel
source subpath (./react is the DOM <UsageDashboard>). Point AiUsageModule at
./panel and bump the dep. typecheck green.
Replace the ai-metrics LivingOverview client-side re-derivation with the ONE
<UsagePanel> (@hanzo/usage/react) reading GET /v1/get-cloud-usages via a new
CloudUsageApi (same-origin /v1 proxy, cookie auth). Transpile @hanzo/usage so
its source panel compiles in the client bundle, and drop its now-unnecessary
serverExternalPackages entry (its headless entry carries no node built-ins).
Replace the ai-metrics LivingOverview client-side re-derivation with the ONE
<UsagePanel> (@hanzo/usage/react) reading GET /v1/get-cloud-usages via a new
CloudUsageApi (same-origin /v1 proxy, cookie auth). Transpile @hanzo/usage so
its source panel compiles in the client bundle, and drop its now-unnecessary
serverExternalPackages entry (its headless entry carries no node built-ins).
These 6 commits (QR device login, Code dashboard, Treasury, OSS Authors) were
never on origin main; publish them forward. QR device login is the console side
of the device-flow login loop — /auth/device BFF starts+polls IAM with client
hanzo-cloud, which now carries the device_code grant (universe ed55bdaa). Bump
128→129 so a clean image builds (origin already tagged 128 without QR).
These 6 commits (QR device login, Code dashboard, Treasury, OSS Authors) were
never on origin main; publish them forward. QR device login is the console side
of the device-flow login loop — /auth/device BFF starts+polls IAM with client
hanzo-cloud, which now carries the device_code grant (universe ed55bdaa). Bump
128→129 so a clean image builds (origin already tagged 128 without QR).
The Treasury admin dashboard (reserve fund + revenue-share + backed payouts +
Hanzo L1 anchor, v8.4.112) and the OSS Authors royalty product (v8.4.111) that
this branch introduced are already present in main, merged via PR #122 and #120.
The core files (TreasuryAdminModule, admin-treasury{,.test}, AuthorsAdminModule,
admin-authors) are byte-identical; main additionally carries the /cloud->/v1
bearer-proxy migration on the two authors files, so main is strictly newer.
Record the branch as integrated with -s ours (keep main's tree unchanged) so the
stale duplicate is not re-applied and the branch can be retired cleanly.
The Treasury admin dashboard (reserve fund + revenue-share + backed payouts +
Hanzo L1 anchor, v8.4.112) and the OSS Authors royalty product (v8.4.111) that
this branch introduced are already present in main, merged via PR #122 and #120.
The core files (TreasuryAdminModule, admin-treasury{,.test}, AuthorsAdminModule,
admin-authors) are byte-identical; main additionally carries the /cloud->/v1
bearer-proxy migration on the two authors files, so main is strictly newer.
Record the branch as integrated with -s ours (keep main's tree unchanged) so the
stale duplicate is not re-applied and the branch can be retired cleanly.
Open console.<brand> on ANY machine, scan the QR with your phone, sign in +
approve at the brand IAM, and this tab's session starts — no password typed
on the machine at hand.
- session.ts: deviceCodeGrant(deviceCode, clientId) — public-client device
poll; maps authorization_pending/slow_down → pending, expired_token →
expired, success seals the session (reuses sealSession). SessionError now
carries the OAuth error code so the poll tells the states apart.
- app/auth/device/route.ts BFF: action=start proxies IAM's device endpoint at
the public issuer (so verification_uri is scannable), action=poll redeems and
sets the exact sealed cookies /auth/session uses.
- iam-device.ts: thin same-origin client wire over that route.
- QrSignIn.tsx: renders the QR of verification_uri_complete + the user code,
polls at the IAM cadence, and on approval reloads the session → '/'. Reached
via a "Sign in with QR code" affordance on SignInForm, so console.<brand> on
any device offers it.
- dep: qrcode.react 4.2.0 (pinned).
Tested: deviceCodeGrant states (session.test.ts, fetch-mocked); typecheck +
build green.
Open console.<brand> on ANY machine, scan the QR with your phone, sign in +
approve at the brand IAM, and this tab's session starts — no password typed
on the machine at hand.
- session.ts: deviceCodeGrant(deviceCode, clientId) — public-client device
poll; maps authorization_pending/slow_down → pending, expired_token →
expired, success seals the session (reuses sealSession). SessionError now
carries the OAuth error code so the poll tells the states apart.
- app/auth/device/route.ts BFF: action=start proxies IAM's device endpoint at
the public issuer (so verification_uri is scannable), action=poll redeems and
sets the exact sealed cookies /auth/session uses.
- iam-device.ts: thin same-origin client wire over that route.
- QrSignIn.tsx: renders the QR of verification_uri_complete + the user code,
polls at the IAM cadence, and on approval reloads the session → '/'. Reached
via a "Sign in with QR code" affordance on SignInForm, so console.<brand> on
any device offers it.
- dep: qrcode.react 4.2.0 (pinned).
Tested: deviceCodeGrant states (session.test.ts, fetch-mocked); typecheck +
build green.
The console predicate was already owner=='admin' (isSuperAdminOwner / gateAllows /
accountOf); accessClaims still projected a JWT isSuperAdmin boolean claim that
accountOf overrode. The gateway now drops the isSuperAdmin/isGlobalAdmin boolean
entirely, so this makes accessClaims owner-canonical too: SuperAdmin has ONE signal
(owner==admin org), no boolean claim read anywhere. Org-scoped isAdmin untouched.
The console predicate was already owner=='admin' (isSuperAdminOwner / gateAllows /
accountOf); accessClaims still projected a JWT isSuperAdmin boolean claim that
accountOf overrode. The gateway now drops the isSuperAdmin/isGlobalAdmin boolean
entirely, so this makes accessClaims owner-canonical too: SuperAdmin has ONE signal
(owner==admin org), no boolean claim read anywhere. Org-scoped isAdmin untouched.
SuperAdmin ⟺ the principal's IAM org (owner) IS the reserved 'admin' org — the same
equality IAM's User.IsSuperAdmin() uses (user.Owner == conf.AdminOrg). IAM DERIVES its
isSuperAdmin claim from that equality, so reading the claim as well was two signals for
one fact.
- config: export isSuperAdminOwner(owner) — THE predicate, one place.
- session.accountOf + auth/admin.isSuperAdminAccount: use it; drop the redundant
read entirely. No claim, no fallback, no compat.
- test: strengthened — a claim on a NON-admin-org account can NEVER confer SuperAdmin
(a second signal would be forgeable); admin-org membership alone decides.
tsc 0 errors; auth/session/identity/admin-policy suites 55/55 green.
SuperAdmin ⟺ the principal's IAM org (owner) IS the reserved 'admin' org — the same
equality IAM's User.IsSuperAdmin() uses (user.Owner == conf.AdminOrg). IAM DERIVES its
isSuperAdmin claim from that equality, so reading the claim as well was two signals for
one fact.
- config: export isSuperAdminOwner(owner) — THE predicate, one place.
- session.accountOf + auth/admin.isSuperAdminAccount: use it; drop the redundant
read entirely. No claim, no fallback, no compat.
- test: strengthened — a claim on a NON-admin-org account can NEVER confer SuperAdmin
(a second signal would be forgeable); admin-org membership alone decides.
tsc 0 errors; auth/session/identity/admin-policy suites 55/55 green.
Merges feat/sentry-dashboard into main. Sentry lands as a host-branded product FACE
(sentry.hanzo.ai = the hanzo brand wearing a Sentry error/log/trace shell over /v1/sentry).
RECONCILIATION — the social-mode lane (marketing/ads/social) had added more per-mode booleans
(config.{marketingOnly,adsOnly,socialOnly} + is{Marketing,Ads,Social}Host + {MARKETING,ADS,
SOCIAL}_ID + N per-mode branches in visibleCatalog/page). This branch generalized the billing
special-case into ONE `shell`/`ShellId` model. Resolved by DECOMPLECTING all FIVE faces into
that ONE model (a name is a value in one namespace, not N parallel booleans):
- config: ShellId = console|billing|marketing|ads|social|sentry; ONE `shellFromHost` resolver
(host prefix / NEXT_PUBLIC_*_ONLY / NEXT_PUBLIC_PRODUCT_SHELL) drives everything. The four
{billing,marketing,ads,social}Only booleans are now DERIVED aliases (shell === '<x>'), kept
for existing call sites + tests. Orthogonal to brand — a face never crosses a brand.
- shell.ts: ONE descriptor (rootId/wordmark/home/indexLabel) per face — the single source of
each face's scope. Replaces the {BILLING,MARKETING,ADS,SOCIAL}_ID consts (removed).
- registry: visibleCatalog + visibleCatalogByCategory collapse the 4 per-mode branches into
ONE isProductShell(config.shell) path (shellFor().rootId); e.shell hides only face-scoped
entries (sentry) from the console — marketing/ads/social stay normal Apps products.
- page: ONE shellHome redirect for every face. DashboardShell: ONE isProductShell face-nav
branch (billing/sentry = root sub-pages; single-screen marketing/ads/social = a lone
Overview; product wordmark beside the Hanzo mark — billing keeps its legacy mark-only look).
ZERO regression — all FIVE faces resolve, filter the catalog, and route home (unit-asserted).
package.json 8.4.128. tsc clean; vitest 2295/2295 (194 files); next build ✓; all 5 face roots
+ sentry sub-routes serve 200 at runtime.
Merges feat/sentry-dashboard into main. Sentry lands as a host-branded product FACE
(sentry.hanzo.ai = the hanzo brand wearing a Sentry error/log/trace shell over /v1/sentry).
RECONCILIATION — the social-mode lane (marketing/ads/social) had added more per-mode booleans
(config.{marketingOnly,adsOnly,socialOnly} + is{Marketing,Ads,Social}Host + {MARKETING,ADS,
SOCIAL}_ID + N per-mode branches in visibleCatalog/page). This branch generalized the billing
special-case into ONE `shell`/`ShellId` model. Resolved by DECOMPLECTING all FIVE faces into
that ONE model (a name is a value in one namespace, not N parallel booleans):
- config: ShellId = console|billing|marketing|ads|social|sentry; ONE `shellFromHost` resolver
(host prefix / NEXT_PUBLIC_*_ONLY / NEXT_PUBLIC_PRODUCT_SHELL) drives everything. The four
{billing,marketing,ads,social}Only booleans are now DERIVED aliases (shell === '<x>'), kept
for existing call sites + tests. Orthogonal to brand — a face never crosses a brand.
- shell.ts: ONE descriptor (rootId/wordmark/home/indexLabel) per face — the single source of
each face's scope. Replaces the {BILLING,MARKETING,ADS,SOCIAL}_ID consts (removed).
- registry: visibleCatalog + visibleCatalogByCategory collapse the 4 per-mode branches into
ONE isProductShell(config.shell) path (shellFor().rootId); e.shell hides only face-scoped
entries (sentry) from the console — marketing/ads/social stay normal Apps products.
- page: ONE shellHome redirect for every face. DashboardShell: ONE isProductShell face-nav
branch (billing/sentry = root sub-pages; single-screen marketing/ads/social = a lone
Overview; product wordmark beside the Hanzo mark — billing keeps its legacy mark-only look).
ZERO regression — all FIVE faces resolve, filter the catalog, and route home (unit-asserted).
package.json 8.4.128. tsc clean; vitest 2295/2295 (194 files); next build ✓; all 5 face roots
+ sentry sub-routes serve 200 at runtime.
sentry.hanzo.ai is the SAME console app, host-branded into a Sentry PRODUCT shell —
Hanzo IAM + @hanzo/gui identity, product-labelled "Sentry" (no upstream Sentry look).
Extends the brand-by-host machinery with an orthogonal product-SHELL concept and adds
the full /v1/sentry dashboard. Reuses the existing primitives; composition, not greenfield.
- config: ShellId + shellFromHost (console/billing/sentry faces), orthogonal to brand —
a shell never crosses a brand; billingOnly is now the derived `shell === 'billing'`.
- lib/products/shell.ts: the pure per-face descriptor (root module, wordmark, home) — the
ONE source the nav + home redirect + catalog gate share. + shell.test.ts.
- lib/api/sentry.ts: the /v1/sentry client — projects (+ DSN/key rotate), issues (list/get/
update/events), discover, events, logs, traces (+ detail), stats. Version-less same-origin
BFF (originV1Url, session cookie only), org server-enforced. Defensive normalizers + tests.
- components/products/sentry/*: Issues (search/status/sort/period/project + KPIs + sparklines),
IssueDetail (stack trace + source context, breadcrumbs, tags, linked trace, resolve/ignore/
reopen, occurrence timeline), Discover (filter/agg/group-by builder + table + chart), Logs
(level filter + detail rail), Traces (list + span waterfall), Monitor (event/error timeseries),
Projects (DSN + SDK snippet — CLEAN path, NO /api/), Members (composes Hanzo IAM TeamApi).
- SentryModule: ONE module routed by :tab (+ :tab/:id detail); the shell nav branch is
generalized (billing + sentry) from the descriptor, the home redirect too. Sub-pages derive
from SENTRY_TABS (one source). `logs` base-slug precedence proven in sentry-routing.test.ts.
- registry: sentry entry (shell-scoped → hidden from the full console); proxy-allow `sentry` head.
Verify: tsc clean; vitest 2267/2267 (193 files, +52 new); next build ✓; all 10 /sentry routes
serve 200 at runtime. Panels are contract-wired — the live /v1/sentry backend + the
authenticated Playwright proof against sentry.hanzo.ai are the post-deploy gate.
sentry.hanzo.ai is the SAME console app, host-branded into a Sentry PRODUCT shell —
Hanzo IAM + @hanzo/gui identity, product-labelled "Sentry" (no upstream Sentry look).
Extends the brand-by-host machinery with an orthogonal product-SHELL concept and adds
the full /v1/sentry dashboard. Reuses the existing primitives; composition, not greenfield.
- config: ShellId + shellFromHost (console/billing/sentry faces), orthogonal to brand —
a shell never crosses a brand; billingOnly is now the derived `shell === 'billing'`.
- lib/products/shell.ts: the pure per-face descriptor (root module, wordmark, home) — the
ONE source the nav + home redirect + catalog gate share. + shell.test.ts.
- lib/api/sentry.ts: the /v1/sentry client — projects (+ DSN/key rotate), issues (list/get/
update/events), discover, events, logs, traces (+ detail), stats. Version-less same-origin
BFF (originV1Url, session cookie only), org server-enforced. Defensive normalizers + tests.
- components/products/sentry/*: Issues (search/status/sort/period/project + KPIs + sparklines),
IssueDetail (stack trace + source context, breadcrumbs, tags, linked trace, resolve/ignore/
reopen, occurrence timeline), Discover (filter/agg/group-by builder + table + chart), Logs
(level filter + detail rail), Traces (list + span waterfall), Monitor (event/error timeseries),
Projects (DSN + SDK snippet — CLEAN path, NO /api/), Members (composes Hanzo IAM TeamApi).
- SentryModule: ONE module routed by :tab (+ :tab/:id detail); the shell nav branch is
generalized (billing + sentry) from the descriptor, the home redirect too. Sub-pages derive
from SENTRY_TABS (one source). `logs` base-slug precedence proven in sentry-routing.test.ts.
- registry: sentry entry (shell-scoped → hidden from the full console); proxy-allow `sentry` head.
Verify: tsc clean; vitest 2267/2267 (193 files, +52 new); next build ✓; all 10 /sentry routes
serve 200 at runtime. Panels are contract-wired — the live /v1/sentry backend + the
authenticated Playwright proof against sentry.hanzo.ai are the post-deploy gate.
Flesh the SocialModule to real parity with the live social-frontend over the extended
native /v1/social surface:
- Publish action: a post detail drawer with a real Publish now button
(POST /v1/social/posts/:id/publish) that surfaces the honest outcome — external id on
success, or the exact missing-credentials 503 on the fail-closed provider seam.
- Compose: draft / schedule / publish-now modes; when the target network isn't
configured to publish, an inline honest warning naming the missing OAuth-app creds
(from GET /v1/social/providers) — never a fabricated success.
- Calendar/list: a view toggle — the existing list table plus a calendar (agenda)
view grouping timed posts by day.
- Connect flow: the connect panel shows LIVE per-network publish-readiness
(configured / needs X_API_KEY, ...) beside the account add.
lib/api/social.ts gains providers() + posts.publish() + the server-managed post result
fields (accountId/externalId/error), all defensively normalized. social.test.ts (8 tests)
pins the same-origin /v1/social paths (providers, publish) + the normalizers. tsc --noEmit
clean; vitest green.
Flesh the SocialModule to real parity with the live social-frontend over the extended
native /v1/social surface:
- Publish action: a post detail drawer with a real Publish now button
(POST /v1/social/posts/:id/publish) that surfaces the honest outcome — external id on
success, or the exact missing-credentials 503 on the fail-closed provider seam.
- Compose: draft / schedule / publish-now modes; when the target network isn't
configured to publish, an inline honest warning naming the missing OAuth-app creds
(from GET /v1/social/providers) — never a fabricated success.
- Calendar/list: a view toggle — the existing list table plus a calendar (agenda)
view grouping timed posts by day.
- Connect flow: the connect panel shows LIVE per-network publish-readiness
(configured / needs X_API_KEY, ...) beside the account add.
lib/api/social.ts gains providers() + posts.publish() + the server-managed post result
fields (accountId/externalId/error), all defensively normalized. social.test.ts (8 tests)
pins the same-origin /v1/social paths (providers, publish) + the normalizers. tsc --noEmit
clean; vitest green.
Console half of the new /v1/ads domain seam (one console, host-resolved modes,
orthogonal /v1 domains). Mirrors the billing-only shell EXACTLY:
- config: adsOnly field + isAdsHost/isAds (ads.<brand> prefix, NEXT_PUBLIC_ADS_ONLY
override) — the host->mode twin of billingOnly.
- registry: a real Ads CatalogEntry (id 'ads', Apps) rendering AdsModule;
visibleCatalog/visibleCatalogByCategory filter to it when adsOnly, same shape as billing.
- page: home route redirects to /ads in ads-only mode.
- AdsApi + AdsModule: thin, honest per-org view over the REAL cloud /v1/ads surface
(summary + campaign CRUD), same client path as CRM; 'ads' head allow-listed in
proxy-allow CLOUD_HEADS.
tsc --noEmit green; config test +5 ads cases (26 pass).
Console half of the new /v1/ads domain seam (one console, host-resolved modes,
orthogonal /v1 domains). Mirrors the billing-only shell EXACTLY:
- config: adsOnly field + isAdsHost/isAds (ads.<brand> prefix, NEXT_PUBLIC_ADS_ONLY
override) — the host->mode twin of billingOnly.
- registry: a real Ads CatalogEntry (id 'ads', Apps) rendering AdsModule;
visibleCatalog/visibleCatalogByCategory filter to it when adsOnly, same shape as billing.
- page: home route redirects to /ads in ads-only mode.
- AdsApi + AdsModule: thin, honest per-org view over the REAL cloud /v1/ads surface
(summary + campaign CRUD), same client path as CRM; 'ads' head allow-listed in
proxy-allow CLOUD_HEADS.
tsc --noEmit green; config test +5 ads cases (26 pass).
The console half of the new /v1/social domain seam — the host→mode twin of
Billing/Marketing. social.<brand> (config.socialOnly, isSocialHost, or
NEXT_PUBLIC_SOCIAL_ONLY=1) boots the SAME console image into the ONE Social
product; the catalog is filtered to it and home redirects to /social.
- config: socialOnly on ConsoleConfig + isSocialHost/isSocial, resolved in
resolveConfig (mirrors billingOnly 1:1). 5 new host tests (26/26 pass).
- SocialModule: per-org Posts + Accounts CRUD + real summary over cloud
/v1/social, through the /v1 user-bearer BFF. Honest loading/error/empty
states, never fabricated rows.
- lib/api/social.ts: thin REST client (accounts + posts + summary),
defensive normalizers — twin of crm.ts/marketing.ts.
- registry: Social CatalogEntry + SOCIAL_ID + visibleCatalog(ByCategory)
social-only branch. proxy-allow: 'social' CLOUD_HEAD.
Typecheck: tsc --noEmit GREEN (0 errors).
The console half of the new /v1/social domain seam — the host→mode twin of
Billing/Marketing. social.<brand> (config.socialOnly, isSocialHost, or
NEXT_PUBLIC_SOCIAL_ONLY=1) boots the SAME console image into the ONE Social
product; the catalog is filtered to it and home redirects to /social.
- config: socialOnly on ConsoleConfig + isSocialHost/isSocial, resolved in
resolveConfig (mirrors billingOnly 1:1). 5 new host tests (26/26 pass).
- SocialModule: per-org Posts + Accounts CRUD + real summary over cloud
/v1/social, through the /v1 user-bearer BFF. Honest loading/error/empty
states, never fabricated rows.
- lib/api/social.ts: thin REST client (accounts + posts + summary),
defensive normalizers — twin of crm.ts/marketing.ts.
- registry: Social CatalogEntry + SOCIAL_ID + visibleCatalog(ByCategory)
social-only branch. proxy-allow: 'social' CLOUD_HEAD.
Typecheck: tsc --noEmit GREEN (0 errors).
Console half of the new /v1/marketing domain seam (one console, host-resolved
modes, orthogonal /v1 domains). Mirrors the billing-only shell EXACTLY:
- config: marketingOnly field + isMarketingHost/isMarketing (marketing.<brand>
prefix, NEXT_PUBLIC_MARKETING_ONLY override) — the host->mode twin of billingOnly.
- registry: a real Marketing CatalogEntry (id 'marketing', Apps) rendering
MarketingModule; visibleCatalog/visibleCatalogByCategory filter to it when
marketingOnly, same shape as billing.
- page: home route redirects to /marketing in marketing-only mode.
- MarketingApi + MarketingModule: thin, honest per-org view over the REAL cloud
/v1/marketing surface (summary + campaign CRUD), same client path as CRM;
'marketing' head allow-listed in proxy-allow CLOUD_HEADS.
tsc --noEmit green; config test +5 marketing cases (26 pass).
Console half of the new /v1/marketing domain seam (one console, host-resolved
modes, orthogonal /v1 domains). Mirrors the billing-only shell EXACTLY:
- config: marketingOnly field + isMarketingHost/isMarketing (marketing.<brand>
prefix, NEXT_PUBLIC_MARKETING_ONLY override) — the host->mode twin of billingOnly.
- registry: a real Marketing CatalogEntry (id 'marketing', Apps) rendering
MarketingModule; visibleCatalog/visibleCatalogByCategory filter to it when
marketingOnly, same shape as billing.
- page: home route redirects to /marketing in marketing-only mode.
- MarketingApi + MarketingModule: thin, honest per-org view over the REAL cloud
/v1/marketing surface (summary + campaign CRUD), same client path as CRM;
'marketing' head allow-listed in proxy-allow CLOUD_HEADS.
tsc --noEmit green; config test +5 marketing cases (26 pass).
New customer surface at /bot/run (BotsConsole) over cloud POST /v1/bots/run
(BotsApi.run): boot a desktop/terminal computer, run a computer-using bot on it
against a task, and attach live over the returned VNC session — org-scoped +
metered a flat per-run 'bot' fee (402 → add-funds nudge). Registered as the
'run' route on the customer-facing 'bot' product (distinct from BotModule's
gateway status and the admin BotsModule fleet-spend analytics).
Launch + watch today; a persistent runs list + stop need the cloud endpoints the
launch-only bots surface deliberately lacks (GET /v1/bots + stop, proxying the
bot-gateway's live nodes) — session history is client-side until then. VNC embed
needs the bot gateway to allow this console origin as a frame-ancestor; the
open-in-new-tab fallback works regardless.
New customer surface at /bot/run (BotsConsole) over cloud POST /v1/bots/run
(BotsApi.run): boot a desktop/terminal computer, run a computer-using bot on it
against a task, and attach live over the returned VNC session — org-scoped +
metered a flat per-run 'bot' fee (402 → add-funds nudge). Registered as the
'run' route on the customer-facing 'bot' product (distinct from BotModule's
gateway status and the admin BotsModule fleet-spend analytics).
Launch + watch today; a persistent runs list + stop need the cloud endpoints the
launch-only bots surface deliberately lacks (GET /v1/bots + stop, proxying the
bot-gateway's live nodes) — session history is client-side until then. VNC embed
needs the bot gateway to allow this console origin as a frame-ancestor; the
open-in-new-tab fallback works regardless.
Flip the Observe read plane (O11yApi.traces/observations/sessions + their trace/
session detail) from the /v1/evals cloud_usage projection to the NATIVE o11y span
plane (/v1/o11y), the declared observation-of-record. Step 3 of the unified AI-
observability collapse; the CTO call flagged open since v8.4.124.
- traces/observations/sessions read /v1/o11y/{traces,observations,sessions} via the
/v1 user-bearer BFF; unwrap o11y's { status, data } over { items, offset, limit };
map the native camelCase view-models (view.go) with honest guards (non-finite
cost/latency/tokens -> null em dash, never fabricated).
- trace(id)/session(id) DETAIL composed from the list views filtered by traceId/
sessionId (o11y exposes no detail endpoint). trace(id) header roll-ups come from the
SERVER-aggregated trace row (grouped over ALL spans) so a >200-span trace never
undercounts; the waterfall list is bounded to 200. Inline scores stay EVAL scores for
that trace (EvalsApi.listScoresTyped by traceId) — nothing lost.
- SCORES + score-configs + datasets/evaluators/runs STAY on /v1/evals. One way per
domain. o11y llmobs span views are org-scoped fail-closed on gen_ai.hanzo.org_id
(C1), server-set from the validated X-Org-Id — tenant-safe.
Red review (SHIP): LOW-1 trace-header undercount fixed via the server-aggregated row;
INFO-1 the 5 eval-domain trace/observation/session readers kept as a documented
RETAINED SDK surface (not re-wired into O11yApi) — evals.ts scope doc corrected.
Tests: o11y.test.ts (23) pure adapters + honesty guards + the flip contract
(traces/observations/sessions -> /v1/o11y, scores/score-configs -> /v1/evals, LOW-1
server-aggregated header + fallback). vitest 40/40 (o11y+evals) green; tsc clean for
changed files.
Flip the Observe read plane (O11yApi.traces/observations/sessions + their trace/
session detail) from the /v1/evals cloud_usage projection to the NATIVE o11y span
plane (/v1/o11y), the declared observation-of-record. Step 3 of the unified AI-
observability collapse; the CTO call flagged open since v8.4.124.
- traces/observations/sessions read /v1/o11y/{traces,observations,sessions} via the
/v1 user-bearer BFF; unwrap o11y's { status, data } over { items, offset, limit };
map the native camelCase view-models (view.go) with honest guards (non-finite
cost/latency/tokens -> null em dash, never fabricated).
- trace(id)/session(id) DETAIL composed from the list views filtered by traceId/
sessionId (o11y exposes no detail endpoint). trace(id) header roll-ups come from the
SERVER-aggregated trace row (grouped over ALL spans) so a >200-span trace never
undercounts; the waterfall list is bounded to 200. Inline scores stay EVAL scores for
that trace (EvalsApi.listScoresTyped by traceId) — nothing lost.
- SCORES + score-configs + datasets/evaluators/runs STAY on /v1/evals. One way per
domain. o11y llmobs span views are org-scoped fail-closed on gen_ai.hanzo.org_id
(C1), server-set from the validated X-Org-Id — tenant-safe.
Red review (SHIP): LOW-1 trace-header undercount fixed via the server-aggregated row;
INFO-1 the 5 eval-domain trace/observation/session readers kept as a documented
RETAINED SDK surface (not re-wired into O11yApi) — evals.ts scope doc corrected.
Tests: o11y.test.ts (23) pure adapters + honesty guards + the flip contract
(traces/observations/sessions -> /v1/o11y, scores/score-configs -> /v1/evals, LOW-1
server-aggregated header + fallback). vitest 40/40 (o11y+evals) green; tsc clean for
changed files.
Match the unified Hanzo app-shell (hanzo.app + hanzo.chat): the top-left
is now the white-label brand logomark ALONE (host-derived BrandMark — Hanzo H /
Lux / Zoo / Pars per host, never hardcoded, no wordmark/product-name/letter-H
text) with a right-click brand context menu (Settings · Brand · Docs · About),
and the org switcher + user/account menu + wallet consolidate into ONE bottom-left
cluster (was split user-on-top / wallet-below). Applied across the expanded rail,
the collapsed icon rail, the billing-only shell, and the mobile drawer (all mount
SidebarNav). Reuses the existing BrandMark/getBrand white-label resolver, OrgSwitcher,
SidebarWallet, and Popover menu primitive — no new systems, @hanzo/gui engine unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Match the unified Hanzo app-shell (hanzo.app + hanzo.chat): the top-left
is now the white-label brand logomark ALONE (host-derived BrandMark — Hanzo H /
Lux / Zoo / Pars per host, never hardcoded, no wordmark/product-name/letter-H
text) with a right-click brand context menu (Settings · Brand · Docs · About),
and the org switcher + user/account menu + wallet consolidate into ONE bottom-left
cluster (was split user-on-top / wallet-below). Applied across the expanded rail,
the collapsed icon rail, the billing-only shell, and the mobile drawer (all mount
SidebarNav). Reuses the existing BrandMark/getBrand white-label resolver, OrgSwitcher,
SidebarWallet, and Popover menu primitive — no new systems, @hanzo/gui engine unchanged.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The o11y public contract is FLAT and version-less (one /v1/, no nested
/api/vN). The upstream SigNoz engine version is an internal impl detail
resolved SERVER-SIDE in cloud (clients/o11y), never leaked into a route.
- telemetry.ts: SuperAdmin VM proxy o11y/vm/api/v1/{query,query_range}
-> o11y/vm/{query,query_range} (cloud vmproxy.go calls VM api/v1/* inside).
- apm.ts: composite builder query COMPOSITE_QUERY_RANGE 'api/v3/query_range'
-> 'query_range' (cloud query.go resolves the flat path to the v3 engine).
- proxy-allow.ts: the single `o11y` head already admits every o11y sub-path;
drop the dead `allowTelemetrySurface`/`TELEMETRY_READ` allowlist and the
now-dead `/telemetry` Next route (stripped by static export; replaced by
the SuperAdmin VM proxy — one and one way).
SuperAdmin gate + {up,sum(up),count(up)} allowlist preserved (cloud-side).
No `api/v1/query` / `api/v3/query_range` strings remain in console source.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The o11y public contract is FLAT and version-less (one /v1/, no nested
/api/vN). The upstream SigNoz engine version is an internal impl detail
resolved SERVER-SIDE in cloud (clients/o11y), never leaked into a route.
- telemetry.ts: SuperAdmin VM proxy o11y/vm/api/v1/{query,query_range}
-> o11y/vm/{query,query_range} (cloud vmproxy.go calls VM api/v1/* inside).
- apm.ts: composite builder query COMPOSITE_QUERY_RANGE 'api/v3/query_range'
-> 'query_range' (cloud query.go resolves the flat path to the v3 engine).
- proxy-allow.ts: the single `o11y` head already admits every o11y sub-path;
drop the dead `allowTelemetrySurface`/`TELEMETRY_READ` allowlist and the
now-dead `/telemetry` Next route (stripped by static export; replaced by
the SuperAdmin VM proxy — one and one way).
SuperAdmin gate + {up,sum(up),count(up)} allowlist preserved (cloud-side).
No `api/v1/query` / `api/v3/query_range` strings remain in console source.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
StatusModule reads the whole platform's VictoriaMetrics up{} inventory through
the new SuperAdmin-gated cloud VM proxy (/v1/o11y/vm/*), which 403s a non-super
caller. Without gating the ROUTE, a customer landing on /status hits that proxy
and gets a 403 console error + an error card.
Mark the `status` registry entry `admin: true` so ProductRoute renders the
graceful AdminManagedNotice for non-super callers (no proxy call, no console
error) and only a SuperAdmin renders StatusModule + the live board — matching
MetricsModule's PlatformInfraHealth gating. Customers never hit it (role-gated).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
StatusModule reads the whole platform's VictoriaMetrics up{} inventory through
the new SuperAdmin-gated cloud VM proxy (/v1/o11y/vm/*), which 403s a non-super
caller. Without gating the ROUTE, a customer landing on /status hits that proxy
and gets a 403 console error + an error card.
Mark the `status` registry entry `admin: true` so ProductRoute renders the
graceful AdminManagedNotice for non-super callers (no proxy call, no console
error) and only a SuperAdmin renders StatusModule + the live board — matching
MetricsModule's PlatformInfraHealth gating. Customers never hit it (role-gated).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
- Variables tab: real add/edit/delete env + secret editor (write-only secrets:
Keep/Replace, never revealed) writing through setEnv (PUT .../env). Kept sealed
secrets submit an empty value (preserve-on-empty) so an edit never wipes KMS.
- Logs tab: live-tail the latest deployment's logs while a build/deploy is in
progress (poll — endpoint is a snapshot, no SSE — reuse railway phase, auto-scroll,
stop at terminal).
- One create/connect-repo flow: extract shared CreateAppForm; the canvas 'New
service' now uses it (was a CLI-text stub), same path as the Applications board.
- Domains tab on the canvas drawer reuses DomainsPanel (add/remove/verify), not
verify-only.
- Pure env-editor helpers + unit tests (toEnvDrafts/draftsToEnv/validateEnvDrafts).
- Variables tab: real add/edit/delete env + secret editor (write-only secrets:
Keep/Replace, never revealed) writing through setEnv (PUT .../env). Kept sealed
secrets submit an empty value (preserve-on-empty) so an edit never wipes KMS.
- Logs tab: live-tail the latest deployment's logs while a build/deploy is in
progress (poll — endpoint is a snapshot, no SSE — reuse railway phase, auto-scroll,
stop at terminal).
- One create/connect-repo flow: extract shared CreateAppForm; the canvas 'New
service' now uses it (was a CLI-text stub), same path as the Applications board.
- Domains tab on the canvas drawer reuses DomainsPanel (add/remove/verify), not
verify-only.
- Pure env-editor helpers + unit tests (toEnvDrafts/draftsToEnv/validateEnvDrafts).
The /metrics and /status SuperAdmin infra-health board called the console's
Next.js `/telemetry/[...path]` server route, which the static-export embed
(cloud go:embeds console as output:'export') STRIPS — so a browser call to
`/telemetry/api/v1/query` 404s (the last console error).
Repoint TelemetryApi's transport from `/telemetry/*` to the same-origin,
versionless cloud proxy `/v1/o11y/vm/api/v1/{query,query_range}`
(cloudProxyV1Url → clients/o11y/vmproxy.go). Cloud gates it to platform
SuperAdmins, allowlists the query to exactly {up, sum(up), count(up)}, and
returns VM's native Prometheus envelope verbatim — so parseInstant/parseRange
are unchanged. One shared line fixes both MetricsModule and StatusModule.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The /metrics and /status SuperAdmin infra-health board called the console's
Next.js `/telemetry/[...path]` server route, which the static-export embed
(cloud go:embeds console as output:'export') STRIPS — so a browser call to
`/telemetry/api/v1/query` 404s (the last console error).
Repoint TelemetryApi's transport from `/telemetry/*` to the same-origin,
versionless cloud proxy `/v1/o11y/vm/api/v1/{query,query_range}`
(cloudProxyV1Url → clients/o11y/vmproxy.go). Cloud gates it to platform
SuperAdmins, allowlists the query to exactly {up, sum(up), count(up)}, and
returns VM's native Prometheus envelope verbatim — so parseInstant/parseRange
are unchanged. One shared line fixes both MetricsModule and StatusModule.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The AiAccessStep "Connect a provider login" card was a disabled "coming soon"
stub. The backend OAuth is now live (ai#85: GET /v1/ai/connections/:provider/
authorize + callback, KMS-sealed), so flip it to a real connect button.
- `AiConnectionsApi.authorizeUrl(provider)` — fetch-then-redirect: GETs
`…/connections/<provider>/authorize?format=json` → `{ authorizeUrl }` (tolerates
authorize_url / url), then the step redirects the browser to the provider consent
screen; the backend seals the token on its callback. Records the `connect` choice.
- `/ai` proxy allow-list: add the `v1/ai/connections/<provider>/authorize` sub-path
(a narrow regex, not a general tunnel). The callback is backend↔provider, never
through this proxy.
- Honest states: a provider whose OAuth app creds aren't provisioned returns 503 →
"not available on this deployment yet" for that provider (provisioning is a
separate ops step); other errors show a retry message. Providers are probed
lazily on click (no eager authorize calls that would mint dangling OAuth state).
Tests: +6 (ai-connections.test.ts) — authorize path/format, camel+snake+bare URL
normalization, throw-on-missing, 503 propagation, provider list. tsc + next build
clean; full vitest green except a pre-existing unrelated apm-service-scope failure
on main.
Claude-Session: https://claude.ai/code/session_016yg7GPhYdWCh9vpp4HEwLZ
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The AiAccessStep "Connect a provider login" card was a disabled "coming soon"
stub. The backend OAuth is now live (ai#85: GET /v1/ai/connections/:provider/
authorize + callback, KMS-sealed), so flip it to a real connect button.
- `AiConnectionsApi.authorizeUrl(provider)` — fetch-then-redirect: GETs
`…/connections/<provider>/authorize?format=json` → `{ authorizeUrl }` (tolerates
authorize_url / url), then the step redirects the browser to the provider consent
screen; the backend seals the token on its callback. Records the `connect` choice.
- `/ai` proxy allow-list: add the `v1/ai/connections/<provider>/authorize` sub-path
(a narrow regex, not a general tunnel). The callback is backend↔provider, never
through this proxy.
- Honest states: a provider whose OAuth app creds aren't provisioned returns 503 →
"not available on this deployment yet" for that provider (provisioning is a
separate ops step); other errors show a retry message. Providers are probed
lazily on click (no eager authorize calls that would mint dangling OAuth state).
Tests: +6 (ai-connections.test.ts) — authorize path/format, camel+snake+bare URL
normalization, throw-on-missing, 503 propagation, provider list. tsc + next build
clean; full vitest green except a pre-existing unrelated apm-service-scope failure
on main.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The v3 traces list builder HARD-fails with 'select columns cannot be empty for
panelType list' (500) when a noop list query carries no selectColumns — the recent-
traces widget on 6 product pages 500'd. Add the display columns normalizeTraceSpan
reads (name, duration_nano, response_status_code) as materialized static trace
columns. Logs list stays empty (its noop path returns a default row set — verified
200). Validated live: traces+selectColumns -> 200 with real span data.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The v3 traces list builder HARD-fails with 'select columns cannot be empty for
panelType list' (500) when a noop list query carries no selectColumns — the recent-
traces widget on 6 product pages 500'd. Add the display columns normalizeTraceSpan
reads (name, duration_nano, response_status_code) as materialized static trace
columns. Logs list stays empty (its noop path returns a default row set — verified
200). Validated live: traces+selectColumns -> 200 with real span data.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Adds an Errors (Issues) product under Observe, reading the o11y errortracking
module over the SAME version-less, IAM-scoped /v1/o11y/* BFF as Service Map/Logs:
- lib/api/apm.ts: Issue/Occurrence/IssueDetail types + defensive normalizers
(unwrap the {status,data} envelope, tolerate garbage) + ErrorTrackingApi
(listIssues/getIssue/updateIssue). Org scope is server-enforced.
- components/products/ErrorsModule.tsx: status tabs, KPI band (issues/unresolved/
regressed/events), by-level Donut, issues table, and a detail SlideOver with the
latest occurrence, stack trace, and resolve/ignore/reopen actions. Dependency-free
inline-SVG charts (CSP-safe); honest RuntimeNotice/empty states, never fabricated.
- registry.tsx: one Observe catalog entry ('errors', routes ''|':id').
- errortracking.test.ts: 8 normalizer tests (envelope unwrap, defaults, garbage).
tsc clean (my files); vitest 8/8. Lights up when cloud bumps its embedded o11y
dep to the errortracking build (same gating as the llmobs org-scope fix).
Adds an Errors (Issues) product under Observe, reading the o11y errortracking
module over the SAME version-less, IAM-scoped /v1/o11y/* BFF as Service Map/Logs:
- lib/api/apm.ts: Issue/Occurrence/IssueDetail types + defensive normalizers
(unwrap the {status,data} envelope, tolerate garbage) + ErrorTrackingApi
(listIssues/getIssue/updateIssue). Org scope is server-enforced.
- components/products/ErrorsModule.tsx: status tabs, KPI band (issues/unresolved/
regressed/events), by-level Donut, issues table, and a detail SlideOver with the
latest occurrence, stack trace, and resolve/ignore/reopen actions. Dependency-free
inline-SVG charts (CSP-safe); honest RuntimeNotice/empty states, never fabricated.
- registry.tsx: one Observe catalog entry ('errors', routes ''|':id').
- errortracking.test.ts: 8 normalizer tests (envelope unwrap, defaults, garbage).
tsc clean (my files); vitest 8/8. Lights up when cloud bumps its embedded o11y
dep to the errortracking build (same gating as the llmobs org-scope fix).
Native Code module surfacing the LIVE per-org /v1/code code-intelligence
engine, mirroring the Agents module's structure/idiom exactly.
- lib/api/code.ts — CodeApi (search/ask/context) over the same-origin /v1
user-bearer proxy, org-scoped SERVER-SIDE (never a client-side org param);
defensive normalizers + pure derivers/formatters. +21 unit tests.
- components/products/CodeModule.tsx + code/parts.tsx — a hybrid SEARCH box
(query + hybrid|text|symbol|semantic mode) → clickable file:line results
table (row → span detail pane), and an ASK panel rendering answer +
citations[] as file:line refs (click reveals the cited span via search).
Honest states throughout (inert-until-queried, "not connected" on a 404
route, BackendStateCard on 403/5xx, degraded banner) — never fabricated
data, exactly like Agents.
- Registered `code` in the products registry (Dev, Code2 icon) and
allow-listed the `code` head in proxy-allow.ts (+ test).
tsc clean; vitest +48 new pass (the lone suite failure is a pre-existing
origin/main apm-service-scope test, untouched here); next build green.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Native Code module surfacing the LIVE per-org /v1/code code-intelligence
engine, mirroring the Agents module's structure/idiom exactly.
- lib/api/code.ts — CodeApi (search/ask/context) over the same-origin /v1
user-bearer proxy, org-scoped SERVER-SIDE (never a client-side org param);
defensive normalizers + pure derivers/formatters. +21 unit tests.
- components/products/CodeModule.tsx + code/parts.tsx — a hybrid SEARCH box
(query + hybrid|text|symbol|semantic mode) → clickable file:line results
table (row → span detail pane), and an ASK panel rendering answer +
citations[] as file:line refs (click reveals the cited span via search).
Honest states throughout (inert-until-queried, "not connected" on a 404
route, BackendStateCard on 403/5xx, degraded banner) — never fabricated
data, exactly like Agents.
- Registered `code` in the products registry (Dev, Code2 icon) and
allow-listed the `code` head in proxy-allow.ts (+ test).
tsc clean; vitest +48 new pass (the lone suite failure is a pre-existing
origin/main apm-service-scope test, untouched here); next build green.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Native Code module surfacing the LIVE per-org /v1/code code-intelligence
engine, mirroring the Agents module's structure/idiom exactly.
- lib/api/code.ts — CodeApi (search/ask/context) over the same-origin /v1
user-bearer proxy, org-scoped SERVER-SIDE (never a client-side org param);
defensive normalizers + pure derivers/formatters. +21 unit tests.
- components/products/CodeModule.tsx + code/parts.tsx — a hybrid SEARCH box
(query + hybrid|text|symbol|semantic mode) → clickable file:line results
table (row → span detail pane), and an ASK panel rendering answer +
citations[] as file:line refs (click reveals the cited span via search).
Honest states throughout (inert-until-queried, "not connected" on a 404
route, BackendStateCard on 403/5xx, degraded banner) — never fabricated
data, exactly like Agents.
- Registered `code` in the products registry (Dev, Code2 icon) and
allow-listed the `code` head in proxy-allow.ts (+ test).
tsc clean; vitest +48 new pass (the lone suite failure is a pre-existing
origin/main apm-service-scope test, untouched here); next build green.
Native Code module surfacing the LIVE per-org /v1/code code-intelligence
engine, mirroring the Agents module's structure/idiom exactly.
- lib/api/code.ts — CodeApi (search/ask/context) over the same-origin /v1
user-bearer proxy, org-scoped SERVER-SIDE (never a client-side org param);
defensive normalizers + pure derivers/formatters. +21 unit tests.
- components/products/CodeModule.tsx + code/parts.tsx — a hybrid SEARCH box
(query + hybrid|text|symbol|semantic mode) → clickable file:line results
table (row → span detail pane), and an ASK panel rendering answer +
citations[] as file:line refs (click reveals the cited span via search).
Honest states throughout (inert-until-queried, "not connected" on a 404
route, BackendStateCard on 403/5xx, degraded banner) — never fabricated
data, exactly like Agents.
- Registered `code` in the products registry (Dev, Code2 icon) and
allow-listed the `code` head in proxy-allow.ts (+ test).
tsc clean; vitest +48 new pass (the lone suite failure is a pre-existing
origin/main apm-service-scope test, untouched here); next build green.
Fills the two stubbed seams in the App Platform canvas (@hanzo/canvas):
1. Per-service metrics — the card sparkline + drawer Metrics tab now show REAL
per-service RED metrics from cloud's o11y surface (GET /v1/o11y/metrics?product=
<slug>, clients/o11y): requests, error rate, and p95 latency time-series, org-
scoped server-side. New `lib/api/o11y-metrics.ts` client (honest states: 200
honest-empty for a service with no telemetry; connected:false on 503/404/401/403;
400 = bad slug → honest-empty for that one app — never throws, never a fabricated
chart). `platform-apps/metrics.ts` folds the requests series into the card's
ServiceMetric (undefined = no sparkline, the exact prior honest state) and fetches
the visible apps' metrics concurrency-capped. The drawer Metrics tab renders the
full requests/errors/latency set with a 1h/6h/24h window toggle. Per-service
CPU/memory are NOT exposed by this RED (trace-derived) read, so they are labeled
honestly as not-exposed rather than estimated.
2. Dependency edges — the platform store declares no service bindings (verified in
cloud clients/platform: no dependency/link/binding model), so instead of an
always-empty declared-deps endpoint we overlay the REAL OBSERVED runtime
dependency graph from o11y (ApmApi.dependencies → /v1/o11y/dependency_graph). A
solid `dependency` edge is drawn ONLY where both endpoints resolve to apps in the
canvas (matched by OTel service.name), and an observed dependency supersedes the
env-var-derived `reference` guess for the same pair. Env-var references remain the
declared-intent hint when no telemetry links two apps.
`buildProjectCanvas` gains an optional `extras` arg (metricByApp + serviceDeps) so
the fold stays pure; the module fetches the live o11y signals separately. No
@hanzo/canvas change needed — MetricSparkline/ServiceMetric already accept the data.
Tests: +24 (canvas metric injection + dependency-edge supersession/scoping,
o11y-metrics normalizer + honest transport states, metrics folds). Full suite
184 files / 2149 pass; tsc clean; next build ✓ (23/23).
Claude-Session: https://claude.ai/code/session_016yg7GPhYdWCh9vpp4HEwLZ
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Fills the two stubbed seams in the App Platform canvas (@hanzo/canvas):
1. Per-service metrics — the card sparkline + drawer Metrics tab now show REAL
per-service RED metrics from cloud's o11y surface (GET /v1/o11y/metrics?product=
<slug>, clients/o11y): requests, error rate, and p95 latency time-series, org-
scoped server-side. New `lib/api/o11y-metrics.ts` client (honest states: 200
honest-empty for a service with no telemetry; connected:false on 503/404/401/403;
400 = bad slug → honest-empty for that one app — never throws, never a fabricated
chart). `platform-apps/metrics.ts` folds the requests series into the card's
ServiceMetric (undefined = no sparkline, the exact prior honest state) and fetches
the visible apps' metrics concurrency-capped. The drawer Metrics tab renders the
full requests/errors/latency set with a 1h/6h/24h window toggle. Per-service
CPU/memory are NOT exposed by this RED (trace-derived) read, so they are labeled
honestly as not-exposed rather than estimated.
2. Dependency edges — the platform store declares no service bindings (verified in
cloud clients/platform: no dependency/link/binding model), so instead of an
always-empty declared-deps endpoint we overlay the REAL OBSERVED runtime
dependency graph from o11y (ApmApi.dependencies → /v1/o11y/dependency_graph). A
solid `dependency` edge is drawn ONLY where both endpoints resolve to apps in the
canvas (matched by OTel service.name), and an observed dependency supersedes the
env-var-derived `reference` guess for the same pair. Env-var references remain the
declared-intent hint when no telemetry links two apps.
`buildProjectCanvas` gains an optional `extras` arg (metricByApp + serviceDeps) so
the fold stays pure; the module fetches the live o11y signals separately. No
@hanzo/canvas change needed — MetricSparkline/ServiceMetric already accept the data.
Tests: +24 (canvas metric injection + dependency-edge supersession/scoping,
o11y-metrics normalizer + honest transport states, metrics folds). Full suite
184 files / 2149 pass; tsc clean; next build ✓ (23/23).
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The console's logs/traces list widget builds the v3 composite payload
(compositeQuery.{queryType,builderQueries}) with a matching v3 response parser
(parseListRows over data.result[].list). It posted to the version-less
/v1/o11y/query_range alias, which the embedded o11y resolves to the HIGHEST
version (v5) — whose composite query accepts only {queries:[…]} and 400s the v3
shape (unknown field "queryType"). This broke the overview-metrics widget on 6
product pages (studio/gateway/cli/registry/desktop/console).
Pin both composite calls to the explicit /v1/o11y/api/v3/query_range (verified
200 against live embed with the exact payload). Request+response stay a matched
v3 pair; the v3 handler is registered and live. No backend change.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The console's logs/traces list widget builds the v3 composite payload
(compositeQuery.{queryType,builderQueries}) with a matching v3 response parser
(parseListRows over data.result[].list). It posted to the version-less
/v1/o11y/query_range alias, which the embedded o11y resolves to the HIGHEST
version (v5) — whose composite query accepts only {queries:[…]} and 400s the v3
shape (unknown field "queryType"). This broke the overview-metrics widget on 6
product pages (studio/gateway/cli/registry/desktop/console).
Pin both composite calls to the explicit /v1/o11y/api/v3/query_range (verified
200 against live embed with the exact payload). Request+response stay a matched
v3 pair; the v3 handler is registered and live. No backend change.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Follows hanzoai/cloud removing the /v1/console/* API namespace — "console" is just
our FE name, so every route moves to its REAL domain. Forwards-only, no dual-path
fallback:
keys.ts originV1Url('console/keys') → originV1Url('iam/keys')
wallet.ts v1Url('console/topup/wallet') → v1Url('commerce/topup/wallet')
OrgOnboarding + OrgSwitcher v1Url('console/onboard') → v1Url('iam/onboard')
csrf.ts GET /v1/console/csrf → GET /v1/csrf
CSRF_WRITE_PREFIXES becomes SPECIFIC — ['/v1/iam/keys','/v1/iam/onboard','/v1/billing/',
'/v1/commerce/'] — NOT a broad '/v1/iam/', so the SPA's IAM login/signin writes still do
NOT trigger a spurious pre-auth CSRF mint (csrf.test.ts asserts /v1/iam/login|signin stay
false while the four gated surfaces stay true). Each call keeps its exact mechanism
(same-origin originV1Url for keys, cross-origin v1Url for onboard/topup) — only the path
segment changes.
Verified: npm run typecheck (0 errors), npm test (2125/2125, incl. csrf), npm run build
(Compiled successfully). Zero '/v1/console' / 'clients/console' references remain.
Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Follows hanzoai/cloud removing the /v1/console/* API namespace — "console" is just
our FE name, so every route moves to its REAL domain. Forwards-only, no dual-path
fallback:
keys.ts originV1Url('console/keys') → originV1Url('iam/keys')
wallet.ts v1Url('console/topup/wallet') → v1Url('commerce/topup/wallet')
OrgOnboarding + OrgSwitcher v1Url('console/onboard') → v1Url('iam/onboard')
csrf.ts GET /v1/console/csrf → GET /v1/csrf
CSRF_WRITE_PREFIXES becomes SPECIFIC — ['/v1/iam/keys','/v1/iam/onboard','/v1/billing/',
'/v1/commerce/'] — NOT a broad '/v1/iam/', so the SPA's IAM login/signin writes still do
NOT trigger a spurious pre-auth CSRF mint (csrf.test.ts asserts /v1/iam/login|signin stay
false while the four gated surfaces stay true). Each call keeps its exact mechanism
(same-origin originV1Url for keys, cross-origin v1Url for onboard/topup) — only the path
segment changes.
Verified: npm run typecheck (0 errors), npm test (2125/2125, incl. csrf), npm run build
(Compiled successfully). Zero '/v1/console' / 'clients/console' references remain.
Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
App Platform (and the org-wide Map) render as a Railway-style project canvas
over the live /v1/platform + /v1/<kind> data, using the reusable @hanzo/canvas
components (one canvas implementation, reused across both surfaces).
- PlatformAppsModule: upgraded from a table into the project canvas — env +
project switchers, ProjectCanvas of the org's apps + their domains + the
managed data they reference (honest env-derived edges), rich ServiceDetailDrawer
(Overview/Deployments/Variables/Metrics/Logs/Domains/SBOM — reuses the existing
SBOM/logs/domains rendering as tab content, not duplicated), "+ New service"
affordance (honest CLI/API paths), StatCards, and honest loading/empty/error.
- MapModule: migrated onto @hanzo/canvas (ProjectCanvas + ServiceDetailDrawer),
keeping the pure buildGraph fold; the bespoke MapCanvas/nodes/presentation are
removed (one node card, one canvas — DRY).
- platform-apps/canvas.ts: pure fold PlatformApp[] + resources -> the generic
node/edge model, honest edges only (unit-tested, 7 tests). subsystems.ts: the
curated /v1/<svc> capability catalog so a node shows its Hanzo capability.
- Metrics per app are an HONEST empty state (no fabricated chart) — documented
seam to wire o11y/usage. Dependency edges are env-derived — documented seam to
wire real dependency data.
tsc clean; vitest 2132/2132; next build green.
Claude-Session: https://claude.ai/code/session_016yg7GPhYdWCh9vpp4HEwLZ
Co-authored-by: hanzo-dev <dev@hanzo.ai>
App Platform (and the org-wide Map) render as a Railway-style project canvas
over the live /v1/platform + /v1/<kind> data, using the reusable @hanzo/canvas
components (one canvas implementation, reused across both surfaces).
- PlatformAppsModule: upgraded from a table into the project canvas — env +
project switchers, ProjectCanvas of the org's apps + their domains + the
managed data they reference (honest env-derived edges), rich ServiceDetailDrawer
(Overview/Deployments/Variables/Metrics/Logs/Domains/SBOM — reuses the existing
SBOM/logs/domains rendering as tab content, not duplicated), "+ New service"
affordance (honest CLI/API paths), StatCards, and honest loading/empty/error.
- MapModule: migrated onto @hanzo/canvas (ProjectCanvas + ServiceDetailDrawer),
keeping the pure buildGraph fold; the bespoke MapCanvas/nodes/presentation are
removed (one node card, one canvas — DRY).
- platform-apps/canvas.ts: pure fold PlatformApp[] + resources -> the generic
node/edge model, honest edges only (unit-tested, 7 tests). subsystems.ts: the
curated /v1/<svc> capability catalog so a node shows its Hanzo capability.
- Metrics per app are an HONEST empty state (no fabricated chart) — documented
seam to wire o11y/usage. Dependency edges are env-derived — documented seam to
wire real dependency data.
tsc clean; vitest 2132/2132; next build green.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The native @hanzo/gui Tracker (task #58, replaced Huly/hanzo.team) is a first-class
Hanzo Cloud work surface, peer of the project HUB. Add it to ALWAYS_ON_PRODUCTS so it
shows in the sidebar + ⌘K palette + launcher for every org (it was entitlement-gated,
so it rendered only via a direct /tracker URL and never appeared in nav).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The native @hanzo/gui Tracker (task #58, replaced Huly/hanzo.team) is a first-class
Hanzo Cloud work surface, peer of the project HUB. Add it to ALWAYS_ON_PRODUCTS so it
shows in the sidebar + ⌘K palette + launcher for every org (it was entitlement-gated,
so it rendered only via a direct /tracker URL and never appeared in nav).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The vector kind's createdAt is a numeric epoch; `?? ''` only guards null/undefined,
so `(number).localeCompare` threw 'localeCompare is not a function' and crashed the
whole /vector module render (surfaced once deep-link module rendering was fixed).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The vector kind's createdAt is a numeric epoch; `?? ''` only guards null/undefined,
so `(number).localeCompare` threw 'localeCompare is not a function' and crashed the
whole /vector module render (surfaced once deep-link module rendering was fixed).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The one-binary cloud embed is a Next output:'export' static build; cloud serves
the ROOT (dashboard)/page.tsx index.html for EVERY deep link (a static export
can't pre-generate arbitrary product slugs). So /models, /chat, /tracker … —
direct load AND client nav that hard-falls-back — rendered the home Overview,
never the module. No product module surfaced in the embed.
Fix: the home page resolves the LIVE path via usePathname() and hands any real
product route to the shared ProductRoute renderer (extracted from the [...slug]
catch-all — one definition, both entry points). mounted-gated so the first
client render matches the exported home ('/') — no hydration mismatch. On a real
Next server the home only renders for '/', so behavior there is unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The one-binary cloud embed is a Next output:'export' static build; cloud serves
the ROOT (dashboard)/page.tsx index.html for EVERY deep link (a static export
can't pre-generate arbitrary product slugs). So /models, /chat, /tracker … —
direct load AND client nav that hard-falls-back — rendered the home Overview,
never the module. No product module surfaced in the embed.
Fix: the home page resolves the LIVE path via usePathname() and hands any real
product route to the shared ProductRoute renderer (extracted from the [...slug]
catch-all — one definition, both entry points). mounted-gated so the first
client render matches the exported home ('/') — no hydration mismatch. On a real
Next server the home only renders for '/', so behavior there is unchanged.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
admin.hanzo.ai served the console SPA correctly (gated by admin-guard, on the
new console — NOT legacy console2) and /v1/admin/* returned real data, but the
(dashboard) shell wraps EVERY authenticated surface in <WaitlistGate>, which has
no admin bypass. So the operator superuser (z@hanzo.ai, owner=admin) saw the
consumer product waitlist panel instead of the operator cockpit on admin.hanzo.ai.
The operator cockpit is a distinct concern from consumer product rollout, so an
operator is never held behind the line:
- server (the access authority): waitlistAccess() short-circuits hasAccess=true on
an admin host (isAdminHost) before consulting the waitlist plugin.
- client (WaitlistGate): mirrors it — an admin host OR a super (platform) admin
disables the gate, so the cockpit never even flashes the waitlist panel.
Real authorization to admin.<brand> + /v1/admin/* is unchanged: admin-guard
ForwardAuth (PKCE via hanzo.id, org=admin) + the cloud global-admin gate still
enforce access. This only lifts the consumer waitlist UX off the operator surface.
Tests: +3 server waitlistAccess admin-host-bypass cases; tsc clean; full vitest
2082+ green; next build ✓.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
admin.hanzo.ai served the console SPA correctly (gated by admin-guard, on the
new console — NOT legacy console2) and /v1/admin/* returned real data, but the
(dashboard) shell wraps EVERY authenticated surface in <WaitlistGate>, which has
no admin bypass. So the operator superuser (z@hanzo.ai, owner=admin) saw the
consumer product waitlist panel instead of the operator cockpit on admin.hanzo.ai.
The operator cockpit is a distinct concern from consumer product rollout, so an
operator is never held behind the line:
- server (the access authority): waitlistAccess() short-circuits hasAccess=true on
an admin host (isAdminHost) before consulting the waitlist plugin.
- client (WaitlistGate): mirrors it — an admin host OR a super (platform) admin
disables the gate, so the cockpit never even flashes the waitlist panel.
Real authorization to admin.<brand> + /v1/admin/* is unchanged: admin-guard
ForwardAuth (PKCE via hanzo.id, org=admin) + the cloud global-admin gate still
enforce access. This only lifts the consumer waitlist UX off the operator surface.
Tests: +3 server waitlistAccess admin-host-bypass cases; tsc clean; full vitest
2082+ green; next build ✓.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Live verify of v8.4.125 (Dave/maxpower org admin) found platform absent from the
entitlement-gated customer sidebar/Apps map. The project HUB is a first-class core
capability, so add 'platform' to ALWAYS_ON_PRODUCTS — visible for every org.
tsc clean; vitest green.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Live verify of v8.4.125 (Dave/maxpower org admin) found platform absent from the
entitlement-gated customer sidebar/Apps map. The project HUB is a first-class core
capability, so add 'platform' to ALWAYS_ON_PRODUCTS — visible for every org.
tsc clean; vitest green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
New first-class `Platform` product (registry id `platform`, Platform category,
routes '' | ':name') → sidebar + Apps map + launcher + shared subpages. It's the
project HUB: create an IAM-native project (ProjectApi, name slugified so
name === deploy slug === the ?project= key), drag-drop a .zip/.tar.gz (or a
client-packed folder) to deploy over the embedded PaaS static engine
(/v1/platform/sites/*), view deployments with status/logs, bind custom domains,
and edit config. Cross-surface deep links on the ONE shared IAM project id —
Edit → hanzo.app/dev?project=<id>, Chat → hanzo.chat/?project=<id> — plus an
inbound ?project= handler that scopes + opens the hub.
- lib/api/platform-sites.ts (+ contract test): the /v1/platform/sites client.
- bearer-proxy: forward a NON-JSON body VERBATIM (bytes + Content-Type), never
text-decode/re-stamp application/json — unblocks binary artifact upload for the
ONE shared proxy; client.restPostRaw posts the artifact (keeps 401-refresh).
- lib/deploy/{archive,drop}.ts: pure ustar tar builder + native gzip + folder walk.
- lib/products/cross-surface.ts: ?project= links + slug helper (config.chatUrl added).
- ProjectApi.create gains optional displayName (additive). `projects` stays the
scope picker (no duplicate); models/billing-band/single-level-nav untouched.
tsc clean; vitest 2122/2122 (+48); next build ✓.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
New first-class `Platform` product (registry id `platform`, Platform category,
routes '' | ':name') → sidebar + Apps map + launcher + shared subpages. It's the
project HUB: create an IAM-native project (ProjectApi, name slugified so
name === deploy slug === the ?project= key), drag-drop a .zip/.tar.gz (or a
client-packed folder) to deploy over the embedded PaaS static engine
(/v1/platform/sites/*), view deployments with status/logs, bind custom domains,
and edit config. Cross-surface deep links on the ONE shared IAM project id —
Edit → hanzo.app/dev?project=<id>, Chat → hanzo.chat/?project=<id> — plus an
inbound ?project= handler that scopes + opens the hub.
- lib/api/platform-sites.ts (+ contract test): the /v1/platform/sites client.
- bearer-proxy: forward a NON-JSON body VERBATIM (bytes + Content-Type), never
text-decode/re-stamp application/json — unblocks binary artifact upload for the
ONE shared proxy; client.restPostRaw posts the artifact (keeps 401-refresh).
- lib/deploy/{archive,drop}.ts: pure ustar tar builder + native gzip + folder walk.
- lib/products/cross-surface.ts: ?project= links + slug helper (config.chatUrl added).
- ProjectApi.create gains optional displayName (additive). `projects` stays the
scope picker (no duplicate); models/billing-band/single-level-nav untouched.
tsc clean; vitest 2122/2122 (+48); next build ✓.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Guided post-signup wizard shown once (resumable, skippable) via a new
OnboardingGate in the dashboard layout. Reuses existing real surfaces:
- 2FA: MfaApi -> /console/mfa -> IAM mfa/setup
- consent: account preference (data-sharing default OFF) + local guard
- team: TeamApi confirm/rename org
- trial credits: Square hosted element + BillingApi.createPaymentMethod + welcome + balance
- AI access: BYO keys -> real KMS-sealed /v1/ai/connections (new AiConnectionsApi,
allow-listed in the /ai proxy); Hanzo router via AiAccountsApi.saveSettings;
provider-login OAuth is an honest coming-soon (backend gap)
- first action: deep-link CTAs
tsc clean; vitest 2074/2074 (+11); next build green.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Guided post-signup wizard shown once (resumable, skippable) via a new
OnboardingGate in the dashboard layout. Reuses existing real surfaces:
- 2FA: MfaApi -> /console/mfa -> IAM mfa/setup
- consent: account preference (data-sharing default OFF) + local guard
- team: TeamApi confirm/rename org
- trial credits: Square hosted element + BillingApi.createPaymentMethod + welcome + balance
- AI access: BYO keys -> real KMS-sealed /v1/ai/connections (new AiConnectionsApi,
allow-listed in the /ai proxy); Hanzo router via AiAccountsApi.saveSettings;
provider-login OAuth is an honest coming-soon (backend gap)
- first action: deep-link CTAs
tsc clean; vitest 2074/2074 (+11); next build green.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Upgrade the topbar OrgSwitcher from a load-everything dropdown into a
Vercel-style, truly lazy switcher that scales to thousands of orgs.
- Lazy-load / paginated search: new useOrgList hook fetches ONE page of
get-organizations at a time (orgQuery/ORG_PAGE_SIZE), appends via
mergeOrgs, and loads more on demand (infinite-scroll + Load more).
Search is debounced (250ms) and pushed to the server (field/value name
LIKE) so it narrows at the source; orgRows ALSO client-filters loaded
rows over name+displayName so what renders is correct even if the
backend ignores the server filter. hasMore derives from pageIsFull (no
reliance on a backend total).
- Vercel UI: Find organization search, avatar + name rows, honest
present-only plan/tier badge (tierOf — Hobby/Pro/Enterprise, omitted
when absent, never fabricated), checkmark on the current org, empty
state, and a Create organization footer wired to the existing /onboard
flow. Keyboard nav (up/down/enter/esc) mirrors CommandPalette.
- Masquerade preserved: super admin sees all orgs (lazy, paged); a
regular user sees only their own org (synthesized, unchanged, never
another tenant's). Switching still switchOrg (persist X-Org-Id +
reload). Projects stay lazy via useScope (untouched).
- Pure decisions in src/lib/org-list.ts (+16 vitest); reuses org-picker
logic (orgTitle/initialsOf) and org-scope filterOrgs — DRY.
tsc clean; vitest 2079 pass; next build ok.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Upgrade the topbar OrgSwitcher from a load-everything dropdown into a
Vercel-style, truly lazy switcher that scales to thousands of orgs.
- Lazy-load / paginated search: new useOrgList hook fetches ONE page of
get-organizations at a time (orgQuery/ORG_PAGE_SIZE), appends via
mergeOrgs, and loads more on demand (infinite-scroll + Load more).
Search is debounced (250ms) and pushed to the server (field/value name
LIKE) so it narrows at the source; orgRows ALSO client-filters loaded
rows over name+displayName so what renders is correct even if the
backend ignores the server filter. hasMore derives from pageIsFull (no
reliance on a backend total).
- Vercel UI: Find organization search, avatar + name rows, honest
present-only plan/tier badge (tierOf — Hobby/Pro/Enterprise, omitted
when absent, never fabricated), checkmark on the current org, empty
state, and a Create organization footer wired to the existing /onboard
flow. Keyboard nav (up/down/enter/esc) mirrors CommandPalette.
- Masquerade preserved: super admin sees all orgs (lazy, paged); a
regular user sees only their own org (synthesized, unchanged, never
another tenant's). Switching still switchOrg (persist X-Org-Id +
reload). Projects stay lazy via useScope (untouched).
- Pure decisions in src/lib/org-list.ts (+16 vitest); reuses org-picker
logic (orgTitle/initialsOf) and org-scope filterOrgs — DRY.
tsc clean; vitest 2079 pass; next build ok.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The rebooted o11y backend (cloud embedded o11y v1.5.4) serves the canonical
VERSION-LESS surface /v1/o11y/<resource> (no nested v1/v3, no /api). Proven live:
GET /v1/o11y/health -> 200 {"service":"o11y","status":"ok"}; the reads
(/services, /query_range, /rules) -> 403 "no validated principal" (IAM-gated).
The Insights modules were still calling the nested-version SigNoz forms
(/v1/o11y/v1/*, /v1/o11y/v3/query_range) over a bare /v1/o11y/* (originV1Url),
which on the live ingress reaches the gateway with no minted bearer -> 403.
- apm.ts (ApmApi): version-less paths (services, dependency_graph,
service/top_operations, hosts/pods/nodes/list, listErrors, dashboards,
query_range), addressed via cloudProxyV1Url (the /cloud user-bearer proxy).
- AlertsModule -> o11y/rules; o11y.ts annotation-queues/users -> /cloud;
added O11yApi.health() (o11y/health).
- proxy-allow/ServiceMap/Logs/ProductLogs docstrings updated to the version-less
+ bearer-proxy contract.
- Tests: canonical-paths pins ApmApi.dashboards -> /cloud/v1/o11y/dashboards;
apm-service-scope pins /cloud/v1/o11y/query_range. tsc clean, vitest 1900/1900.
- e2e/insights-o11y.spec.ts: (A) unauthenticated gate proof (PASSES LIVE), (B)
authenticated render proof on admin.hanzo.ai (staged: needs the admin-org
SuperAdmin password + a browser env that renders the RNW SPA).
- Traces/Observations left on /v1/evals (LLM-trace domain w/ cost/tokens/scores);
repointing to /v1/o11y/traces is a data-domain change flagged for the CTO.
The rebooted o11y backend (cloud embedded o11y v1.5.4) serves the canonical
VERSION-LESS surface /v1/o11y/<resource> (no nested v1/v3, no /api). Proven live:
GET /v1/o11y/health -> 200 {"service":"o11y","status":"ok"}; the reads
(/services, /query_range, /rules) -> 403 "no validated principal" (IAM-gated).
The Insights modules were still calling the nested-version SigNoz forms
(/v1/o11y/v1/*, /v1/o11y/v3/query_range) over a bare /v1/o11y/* (originV1Url),
which on the live ingress reaches the gateway with no minted bearer -> 403.
- apm.ts (ApmApi): version-less paths (services, dependency_graph,
service/top_operations, hosts/pods/nodes/list, listErrors, dashboards,
query_range), addressed via cloudProxyV1Url (the /cloud user-bearer proxy).
- AlertsModule -> o11y/rules; o11y.ts annotation-queues/users -> /cloud;
added O11yApi.health() (o11y/health).
- proxy-allow/ServiceMap/Logs/ProductLogs docstrings updated to the version-less
+ bearer-proxy contract.
- Tests: canonical-paths pins ApmApi.dashboards -> /cloud/v1/o11y/dashboards;
apm-service-scope pins /cloud/v1/o11y/query_range. tsc clean, vitest 1900/1900.
- e2e/insights-o11y.spec.ts: (A) unauthenticated gate proof (PASSES LIVE), (B)
authenticated render proof on admin.hanzo.ai (staged: needs the admin-org
SuperAdmin password + a browser env that renders the RNW SPA).
- Traces/Observations left on /v1/evals (LLM-trace domain w/ cost/tokens/scores);
repointing to /v1/o11y/traces is a data-domain change flagged for the CTO.
A compact health indicator in the lg+ topbar reflecting the OVERALL health of
the Hanzo cloud, pulled from the brand's Gatus status page (status.hanzo.ai).
How it pulls status: the badge fetches a same-origin /system-status BFF route
(app/system-status/route.ts) which server-side fetches
status.<brand>/api/v1/endpoints/statuses and returns a small JSON summary. This
sidesteps the status API's missing CORS header (a browser fetch cross-origin is
blocked) and matches the console's established BFF pattern — the badge renders
NATIVELY from the JSON summary (no iframe, no third-party script).
- src/lib/status/summary.ts — PURE summarizeStatuses(): collapses the Gatus feed
to { overall, total, up, down[] }; defensive (garbage → 'unknown', never throws).
- src/lib/status/summary.test.ts — vitest: operational/degraded/down/unknown +
last-result-wins + garbage input (7 tests).
- app/system-status/route.ts — GET BFF; bounded fetchWithTimeout(4s); fail-soft
→ overall:'unknown' at HTTP 200 (never 500); Cache-Control max-age=30.
- src/config/index.ts — per-brand statusUrl (status.<brand-domain>) +
NEXT_PUBLIC_STATUS_URL override, mirroring docsUrl.
- src/components/ui/SystemStatusBadge.tsx — compact dot+label pill (theme-aware
$green10/$yellow10/$red10 tokens), a Popover status panel listing any down
components + a "View full status" link; polls 60s, pauses when tab hidden,
non-blocking ("Checking…" until first response).
- src/components/DashboardShell.tsx — mounts <SystemStatusBadge/> as the first
topbar control.
Verification: vitest src/lib/status 7/7 green; tsc --noEmit clean for all changed
files (the only tsc errors in the tree are pre-existing @hanzo/usage module
resolution in unrelated ai-accounts/* files — a dep present in package.json but
not in this worktree's reused node_modules; my files import none of it). Not
deployed; no package.json version bump (release agent owns that).
A compact health indicator in the lg+ topbar reflecting the OVERALL health of
the Hanzo cloud, pulled from the brand's Gatus status page (status.hanzo.ai).
How it pulls status: the badge fetches a same-origin /system-status BFF route
(app/system-status/route.ts) which server-side fetches
status.<brand>/api/v1/endpoints/statuses and returns a small JSON summary. This
sidesteps the status API's missing CORS header (a browser fetch cross-origin is
blocked) and matches the console's established BFF pattern — the badge renders
NATIVELY from the JSON summary (no iframe, no third-party script).
- src/lib/status/summary.ts — PURE summarizeStatuses(): collapses the Gatus feed
to { overall, total, up, down[] }; defensive (garbage → 'unknown', never throws).
- src/lib/status/summary.test.ts — vitest: operational/degraded/down/unknown +
last-result-wins + garbage input (7 tests).
- app/system-status/route.ts — GET BFF; bounded fetchWithTimeout(4s); fail-soft
→ overall:'unknown' at HTTP 200 (never 500); Cache-Control max-age=30.
- src/config/index.ts — per-brand statusUrl (status.<brand-domain>) +
NEXT_PUBLIC_STATUS_URL override, mirroring docsUrl.
- src/components/ui/SystemStatusBadge.tsx — compact dot+label pill (theme-aware
$green10/$yellow10/$red10 tokens), a Popover status panel listing any down
components + a "View full status" link; polls 60s, pauses when tab hidden,
non-blocking ("Checking…" until first response).
- src/components/DashboardShell.tsx — mounts <SystemStatusBadge/> as the first
topbar control.
Verification: vitest src/lib/status 7/7 green; tsc --noEmit clean for all changed
files (the only tsc errors in the tree are pre-existing @hanzo/usage module
resolution in unrelated ai-accounts/* files — a dep present in package.json but
not in this worktree's reused node_modules; my files import none of it). Not
deployed; no package.json version bump (release agent owns that).
Rebrand all SigNoz/signoz branding in comments, docstrings, tests, SDK
identifiers, and LLM.md to the o11y product name (case-correct):
signoz->o11y, SigNoz->O11y, Signoz->O11y.
- rename type SignozDataSource -> O11yDataSource (apm.ts + index.ts re-export)
- fix stale comment ref O11ySignozApi.logs -> ApmApi.logs
Kept (NOT branding):
- proxy-allow.ts attribution reworded to explicit 'forked from SigNoz'
- admin-o11y.ts ClickHouse table names signoz_traces/signoz_logs left intact
(real upstream SigNoz schema owned by hanzoai/datastore, not this repo)
This repo does not import the collector; no dependency added.
Rebrand all SigNoz/signoz branding in comments, docstrings, tests, SDK
identifiers, and LLM.md to the o11y product name (case-correct):
signoz->o11y, SigNoz->O11y, Signoz->O11y.
- rename type SignozDataSource -> O11yDataSource (apm.ts + index.ts re-export)
- fix stale comment ref O11ySignozApi.logs -> ApmApi.logs
Kept (NOT branding):
- proxy-allow.ts attribution reworded to explicit 'forked from SigNoz'
- admin-o11y.ts ClickHouse table names signoz_traces/signoz_logs left intact
(real upstream SigNoz schema owned by hanzoai/datastore, not this repo)
This repo does not import the collector; no dependency added.
Add a read-only "Bill of Materials (SBOM)" section to the App Platform
deployment detail (the app-detail SlideOver), wired strictly to the backend
wire contract GET /v1/sbom/{ref}.
- data layer (lib/api/platform-apps.ts): new exported types SbomComponent +
Sbom (SbomView), and PlatformAppsApi.sbom(imageRef) — same-origin /v1
user-bearer proxy via cloudProxyV1Url, matching the file's restGet idiom;
returns null on 404 (no SBOM recorded — expected, not an error), throws on
any other non-200.
- UI (PlatformAppsModule.tsx): fetches sbom(appImageRef(app)) on SlideOver
open; reuses the shared Spinner (loading), DataTable (overflow-x scrollable
Name/Version/Type/License table, componentCount in the header) and the
existing muted-Text patterns for the "No SBOM recorded" empty state and the
"SBOM datastore unavailable" (503) note. Read-only, no mutations.
- appImageRef (platform-apps/logic.ts): one source for the image ref, shared
by the Image fact and the SBOM lookup (+ unit tests).
- proxy-allow.ts: allow-list the `sbom` cloud head so the /v1 BFF forwards it.
tsc --noEmit clean; vitest 2056/2056 (incl. +2 appImageRef, proxy-allow head).
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Add a read-only "Bill of Materials (SBOM)" section to the App Platform
deployment detail (the app-detail SlideOver), wired strictly to the backend
wire contract GET /v1/sbom/{ref}.
- data layer (lib/api/platform-apps.ts): new exported types SbomComponent +
Sbom (SbomView), and PlatformAppsApi.sbom(imageRef) — same-origin /v1
user-bearer proxy via cloudProxyV1Url, matching the file's restGet idiom;
returns null on 404 (no SBOM recorded — expected, not an error), throws on
any other non-200.
- UI (PlatformAppsModule.tsx): fetches sbom(appImageRef(app)) on SlideOver
open; reuses the shared Spinner (loading), DataTable (overflow-x scrollable
Name/Version/Type/License table, componentCount in the header) and the
existing muted-Text patterns for the "No SBOM recorded" empty state and the
"SBOM datastore unavailable" (503) note. Read-only, no mutations.
- appImageRef (platform-apps/logic.ts): one source for the image ref, shared
by the Image fact and the SBOM lookup (+ unit tests).
- proxy-allow.ts: allow-list the `sbom` cloud head so the /v1 BFF forwards it.
tsc --noEmit clean; vitest 2056/2056 (incl. +2 appImageRef, proxy-allow head).
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Systematic responsive/cross-platform pass. The v8.4.112 work already handles the big
items (no horizontal overflow on /, /models, /chat, /gpus, /billing at 390/768px;
tables scroll inside their own container; tab rows wrap; chat composer docks; coarse-
pointer tap targets are 44px; light-theme parity is intact). Concrete fixes:
- Sidebar footer no longer repeats the account identity — the new top switcher owns
it. SidebarWallet is now purely the wallet (balance → Cost, Top up, Sign out), so
the user's name/avatar isn't shown twice.
- Safe-area insets for notched devices: viewport-fit=cover exposes the insets; the
chat composer dock pads the home indicator (bottom); the SlideOver drawers inset
top (notch) + bottom (home indicator). Zero effect on devices without a cutout.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Systematic responsive/cross-platform pass. The v8.4.112 work already handles the big
items (no horizontal overflow on /, /models, /chat, /gpus, /billing at 390/768px;
tables scroll inside their own container; tab rows wrap; chat composer docks; coarse-
pointer tap targets are 44px; light-theme parity is intact). Concrete fixes:
- Sidebar footer no longer repeats the account identity — the new top switcher owns
it. SidebarWallet is now purely the wallet (balance → Cost, Top up, Sign out), so
the user's name/avatar isn't shown twice.
- Safe-area insets for notched devices: viewport-fit=cover exposes the insets; the
chat composer dock pads the home indicator (bottom); the SlideOver drawers inset
top (notch) + bottom (home indicator). Zero effect on devices without a cutout.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
authedFetch fetched GET /v1/console/csrf for EVERY mutating request in the embed, so a
mutating request that fires BEFORE a session cookie exists (the pre-login session POST)
minted a token with no principal → 403 — the SPA's ONE remaining browser console error
(self-healing, but a logged error). Cloud only gates POST/DELETE /v1/console/{keys,
onboard,topup/wallet}, POST /v1/billing/*, and mutating /v1/commerce/* (clients/console/
console.go). Scope csrfRequired(method,url) to exactly those prefixes: money-writes still
get the token; login/session/control-plane writes no longer trigger the spurious mint.
Tests: +scoping case; 8 csrf + 12 client-retry pass; typecheck clean.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
authedFetch fetched GET /v1/console/csrf for EVERY mutating request in the embed, so a
mutating request that fires BEFORE a session cookie exists (the pre-login session POST)
minted a token with no principal → 403 — the SPA's ONE remaining browser console error
(self-healing, but a logged error). Cloud only gates POST/DELETE /v1/console/{keys,
onboard,topup/wallet}, POST /v1/billing/*, and mutating /v1/commerce/* (clients/console/
console.go). Scope csrfRequired(method,url) to exactly those prefixes: money-writes still
get the token; login/session/control-plane writes no longer trigger the spurious mint.
Tests: +scoping case; 8 csrf + 12 client-retry pass; typecheck clean.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The embed session-bridge money path (v8.4.122: billing/commerce/keys at bare
/v1 same-origin, caller resolved from the first-party IAM cookie) is guarded by
the cloud binary's requireCSRF (clients/console/csrf.go) — POST/DELETE
/v1/console/{keys,onboard,topup/wallet}, POST /v1/billing/*, POST|PUT|PATCH|DELETE
/v1/commerce/*. An ambient-cookie write with no X-CSRF-Token is refused (403).
Wire the SPA to satisfy it, DRY, one module (src/lib/api/csrf.ts):
- csrfToken() mints from GET /v1/console/csrf (SOP hides its body from a
cross-site page), caches until ~1min pre-expiry, shares one in-flight fetch.
- applyCsrfToInit() stamps X-CSRF-Token on mutating requests in authedFetch (the
ONE fetch — covers billing/commerce/wallet via restRequest); keys.ts (raw
fetch) echoes it too. Both re-mint once on a 403 (server key resets on restart
when CONSOLE_CSRF_KEY is unset) — blue's re-fetch-on-403 contract.
- Gated on IS_EMBED + a mutating verb: a non-embed host writes through the
user-bearer BFF (Authorization ⇒ CSRF-immune), so this is a strict no-op there.
tsc clean; vitest 2048/2048 (+8 csrf: verb gate, cache, in-flight share, 403
re-mint, fail-secure null, header-shape stamping, non-embed no-op); next build ok.
The embed session-bridge money path (v8.4.122: billing/commerce/keys at bare
/v1 same-origin, caller resolved from the first-party IAM cookie) is guarded by
the cloud binary's requireCSRF (clients/console/csrf.go) — POST/DELETE
/v1/console/{keys,onboard,topup/wallet}, POST /v1/billing/*, POST|PUT|PATCH|DELETE
/v1/commerce/*. An ambient-cookie write with no X-CSRF-Token is refused (403).
Wire the SPA to satisfy it, DRY, one module (src/lib/api/csrf.ts):
- csrfToken() mints from GET /v1/console/csrf (SOP hides its body from a
cross-site page), caches until ~1min pre-expiry, shares one in-flight fetch.
- applyCsrfToInit() stamps X-CSRF-Token on mutating requests in authedFetch (the
ONE fetch — covers billing/commerce/wallet via restRequest); keys.ts (raw
fetch) echoes it too. Both re-mint once on a 403 (server key resets on restart
when CONSOLE_CSRF_KEY is unset) — blue's re-fetch-on-403 contract.
- Gated on IS_EMBED + a mutating verb: a non-embed host writes through the
user-bearer BFF (Authorization ⇒ CSRF-immune), so this is a strict no-op there.
tsc clean; vitest 2048/2048 (+8 csrf: verb gate, cache, in-flight share, 403
re-mint, fail-secure null, header-shape stamping, non-embed no-op); next build ok.
Out-of-box each customer org assembles its own backend: the sidebar/launcher/
palette show ONLY the products the org has enabled (always-on essentials + its
entitled set), with an "Add product" flow to enable more. Super admins bypass
gating (see everything) and get a per-org Entitlements editor to manage any org's
enabled products after masquerading in.
- src/lib/entitlements.ts: the ONE /v1/orgs/{org}/entitlements client + pure
helpers (ALWAYS_ON_PRODUCTS, entitledSet, filterEntitled, nextEnabled). Swapping
the mock for the real backend is this file alone; until it lands the GET 404s and
the set is treated as null=UNGATED (show everything) → zero pre-launch regression.
- src/lib/entitlements-context.tsx: EntitlementsProvider/useEntitlements — ONE
shared fetch of the active org's set, wired inside SessionProvider.
- registry: visibleCatalog(showAdmin, enabled?) + visibleCatalogByCategory +
addableCatalogByCategory gate through the one filterEntitled predicate; threaded
into DashboardShell, AppLauncher, CommandPalette, CategoryOverview + search.
- AddProductPanel: the customer enable flow; EntitlementsAdminModule + registry
entry 'entitlements' (admin:true): the super-admin per-org editor.
- proxy-allow: 'orgs' head admits the org-scoped entitlements surface through /v1.
- Rename isGlobalAdmin→isSuperAdmin across the client (useIsSuperAdmin,
isSuperAdminAccount, PickerContext/LoadContext field, 'Super admin' label).
TRANSITIONAL: isSuperAdminAccount reads account.isSuperAdmin ?? account.isGlobalAdmin
so it works before/after the IAM field rename. Server projected-claim untouched.
Tests: vitest 2040 pass (incl. entitlements 16, entitlements/logic 6, admin
back-compat 6, org-picker rename 25); tsc clean; next build ✓; playwright
entitlement-sidebar spec ✓ (gated nav shows Agents, hides GPUs, Add product lists
Enable GPUs).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Out-of-box each customer org assembles its own backend: the sidebar/launcher/
palette show ONLY the products the org has enabled (always-on essentials + its
entitled set), with an "Add product" flow to enable more. Super admins bypass
gating (see everything) and get a per-org Entitlements editor to manage any org's
enabled products after masquerading in.
- src/lib/entitlements.ts: the ONE /v1/orgs/{org}/entitlements client + pure
helpers (ALWAYS_ON_PRODUCTS, entitledSet, filterEntitled, nextEnabled). Swapping
the mock for the real backend is this file alone; until it lands the GET 404s and
the set is treated as null=UNGATED (show everything) → zero pre-launch regression.
- src/lib/entitlements-context.tsx: EntitlementsProvider/useEntitlements — ONE
shared fetch of the active org's set, wired inside SessionProvider.
- registry: visibleCatalog(showAdmin, enabled?) + visibleCatalogByCategory +
addableCatalogByCategory gate through the one filterEntitled predicate; threaded
into DashboardShell, AppLauncher, CommandPalette, CategoryOverview + search.
- AddProductPanel: the customer enable flow; EntitlementsAdminModule + registry
entry 'entitlements' (admin:true): the super-admin per-org editor.
- proxy-allow: 'orgs' head admits the org-scoped entitlements surface through /v1.
- Rename isGlobalAdmin→isSuperAdmin across the client (useIsSuperAdmin,
isSuperAdminAccount, PickerContext/LoadContext field, 'Super admin' label).
TRANSITIONAL: isSuperAdminAccount reads account.isSuperAdmin ?? account.isGlobalAdmin
so it works before/after the IAM field rename. Server projected-claim untouched.
Tests: vitest 2040 pass (incl. entitlements 16, entitlements/logic 6, admin
back-compat 6, org-picker rename 25); tsc clean; next build ✓; playwright
entitlement-sidebar spec ✓ (gated nav shows Agents, hides GPUs, Add product lists
Enable GPUs).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
In IS_EMBED (the static bundle the cloud binary go:embeds) there is NO Next server,
so the service-token BFF route handlers the money clients rely on — app/billing/v1,
app/commerce/[...path], app/keys/route.ts — are stripped by the static export; a
request to them falls through to the SPA shell (HTML, not JSON), so billing showed
'not available', the API-key CTA dead-ended, and the commerce store read as empty.
The embed is same-origin with the cloud binary, which serves the SAME heads at the
CANONICAL bare /v1/* (caller resolved from the first-party IAM session cookie →
validated principal, cloud middleware_identity.go), so in embed mode:
billingProxyV1Url → <origin>/v1/billing/<path> (was /billing/v1/<path>)
commerceProxyV1Url → <origin>/v1/commerce/<path> (was /commerce/v1/<path>)
keysUrl (keys.ts) → <origin>/v1/console/keys (was /keys)
Guarded by IS_EMBED, so every non-embed console (console2/admin/brand hosts, whose
gateway-fronted ingress 403s a cookie-only bare /v1) is UNCHANGED — only the cloud
embed build sets NEXT_PUBLIC_CONSOLE_EMBED=1. cloudProxyV1Url already equals
originV1Url on main (bare /v1), so cloud heads (framework/s3/gpus/functions/…) already
resolve correctly in the embed; billing/commerce/keys were the remaining BFF paths.
+embed-paths.test.ts pins the embed contract; canonical-paths.test.ts unchanged/green.
In IS_EMBED (the static bundle the cloud binary go:embeds) there is NO Next server,
so the service-token BFF route handlers the money clients rely on — app/billing/v1,
app/commerce/[...path], app/keys/route.ts — are stripped by the static export; a
request to them falls through to the SPA shell (HTML, not JSON), so billing showed
'not available', the API-key CTA dead-ended, and the commerce store read as empty.
The embed is same-origin with the cloud binary, which serves the SAME heads at the
CANONICAL bare /v1/* (caller resolved from the first-party IAM session cookie →
validated principal, cloud middleware_identity.go), so in embed mode:
billingProxyV1Url → <origin>/v1/billing/<path> (was /billing/v1/<path>)
commerceProxyV1Url → <origin>/v1/commerce/<path> (was /commerce/v1/<path>)
keysUrl (keys.ts) → <origin>/v1/console/keys (was /keys)
Guarded by IS_EMBED, so every non-embed console (console2/admin/brand hosts, whose
gateway-fronted ingress 403s a cookie-only bare /v1) is UNCHANGED — only the cloud
embed build sets NEXT_PUBLIC_CONSOLE_EMBED=1. cloudProxyV1Url already equals
originV1Url on main (bare /v1), so cloud heads (framework/s3/gpus/functions/…) already
resolve correctly in the embed; billing/commerce/keys were the remaining BFF paths.
+embed-paths.test.ts pins the embed contract; canonical-paths.test.ts unchanged/green.
* test(console): guard proxy allow-lists against internal-infra + privileged heads
Pin the same-origin /v1 proxy boundary to the canonical capability manifest
(hanzoai/openapi CAPABILITIES.md): assert CLOUD_HEADS + COMMERCE_HEADS never
admit an internal-infra name (principal/goja/mpc/controlplane) nor a privileged
head (iam/admin/kms), and that every head is a clean, unique, lowercase segment.
Enforces the mandate rule that internal infra never appears as a public
capability, at the console boundary — non-breaking, no allow-list widening.
* feat(signup): public open signup + waitlisted product access (referral + run-hanzod move-up)
Signup is now PUBLIC (open, no invite required) and PROTECTED; product access is
WAITLISTED with two server-attested move-up paths. One coherent system over the
waitlist Base plugin (/v1/waitlist/*), shared by console/chat/app.
Public + protected signup (/auth/signup):
- Turnstile bot wall (verifyTurnstile; config-gated on TURNSTILE_SECRET_KEY)
- per-IP sliding-window rate limit (signupLimiter, default 5/IP/hr)
- disposable-email block (isDisposableEmail)
- same-origin CSRF gate (unchanged); new signups are self-service customer orgs
(owner=personal slug, never the reserved admin org) — unchanged
- on success, best-effort join to the brand waitlist honoring a ?ref= referrer
Waitlisted product access:
- /auth/waitlist BFF resolves the signed-in email -> plugin status -> hasAccess
- WaitlistGate wraps the shell (AuthGate > WaitlistGate > OrgGate): renders the
product only at the front of the line, else the waitlist panel (position +
run-a-node + invite move-up). FAIL-OPEN: a waitlist blip never locks a user out.
- re-gatable via plugin knobs (WAITLIST_OPEN / WAITLIST_ACCESS_CAPACITY); the
console-side switch is WAITLIST_URL (unset => gate off).
SignInForm: Turnstile widget (signup mode) + ?ref= capture. Tests: rate limiter,
disposable guard, waitlist client fail-open (14 tests). typecheck + next build green.
---------
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
* test(console): guard proxy allow-lists against internal-infra + privileged heads
Pin the same-origin /v1 proxy boundary to the canonical capability manifest
(hanzoai/openapi CAPABILITIES.md): assert CLOUD_HEADS + COMMERCE_HEADS never
admit an internal-infra name (principal/goja/mpc/controlplane) nor a privileged
head (iam/admin/kms), and that every head is a clean, unique, lowercase segment.
Enforces the mandate rule that internal infra never appears as a public
capability, at the console boundary — non-breaking, no allow-list widening.
* feat(signup): public open signup + waitlisted product access (referral + run-hanzod move-up)
Signup is now PUBLIC (open, no invite required) and PROTECTED; product access is
WAITLISTED with two server-attested move-up paths. One coherent system over the
waitlist Base plugin (/v1/waitlist/*), shared by console/chat/app.
Public + protected signup (/auth/signup):
- Turnstile bot wall (verifyTurnstile; config-gated on TURNSTILE_SECRET_KEY)
- per-IP sliding-window rate limit (signupLimiter, default 5/IP/hr)
- disposable-email block (isDisposableEmail)
- same-origin CSRF gate (unchanged); new signups are self-service customer orgs
(owner=personal slug, never the reserved admin org) — unchanged
- on success, best-effort join to the brand waitlist honoring a ?ref= referrer
Waitlisted product access:
- /auth/waitlist BFF resolves the signed-in email -> plugin status -> hasAccess
- WaitlistGate wraps the shell (AuthGate > WaitlistGate > OrgGate): renders the
product only at the front of the line, else the waitlist panel (position +
run-a-node + invite move-up). FAIL-OPEN: a waitlist blip never locks a user out.
- re-gatable via plugin knobs (WAITLIST_OPEN / WAITLIST_ACCESS_CAPACITY); the
console-side switch is WAITLIST_URL (unset => gate off).
SignInForm: Turnstile widget (signup mode) + ?ref= capture. Tests: rate limiter,
disposable guard, waitlist client fail-open (14 tests). typecheck + next build green.
---------
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The mainnet default was the placeholder 36900; genesis
(lux/genesis/configs/hanzo-mainnet), the CLI, and the hanzo-evm comment
all say 36963. Align it so the console network model matches the CLI
exactly (same networkID/chainID/rpc per network):
mainnet 36900 -> 36963 (rpc.hanzo.network)
testnet 36962 (rpc.testnet.hanzo.network) [unchanged]
devnet 36964 (rpc.devnet.hanzo.network) [unchanged]
local 1337 (localhost:9630) [unchanged]
Sovereign L1: networkID == evmChainID. All values stay env-overridable.
Fixes the hanzo-evm hex example (0x9024 -> 0x9063) + doc comments.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The mainnet default was the placeholder 36900; genesis
(lux/genesis/configs/hanzo-mainnet), the CLI, and the hanzo-evm comment
all say 36963. Align it so the console network model matches the CLI
exactly (same networkID/chainID/rpc per network):
mainnet 36900 -> 36963 (rpc.hanzo.network)
testnet 36962 (rpc.testnet.hanzo.network) [unchanged]
devnet 36964 (rpc.devnet.hanzo.network) [unchanged]
local 1337 (localhost:9630) [unchanged]
Sovereign L1: networkID == evmChainID. All values stay env-overridable.
Fixes the hanzo-evm hex example (0x9024 -> 0x9063) + doc comments.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Pin the same-origin /v1 proxy boundary to the canonical capability manifest
(hanzoai/openapi CAPABILITIES.md): assert CLOUD_HEADS + COMMERCE_HEADS never
admit an internal-infra name (principal/goja/mpc/controlplane) nor a privileged
head (iam/admin/kms), and that every head is a clean, unique, lowercase segment.
Enforces the mandate rule that internal infra never appears as a public
capability, at the console boundary — non-breaking, no allow-list widening.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Pin the same-origin /v1 proxy boundary to the canonical capability manifest
(hanzoai/openapi CAPABILITIES.md): assert CLOUD_HEADS + COMMERCE_HEADS never
admit an internal-infra name (principal/goja/mpc/controlplane) nor a privileged
head (iam/admin/kms), and that every head is a clean, unique, lowercase segment.
Enforces the mandate rule that internal infra never appears as a public
capability, at the console boundary — non-breaking, no allow-list widening.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The network switcher now expresses ONE model — (label, networkID, evmChainID,
rpcEndpoint, apiEndpoint) — for every selectable network, in a new `lib/network.ts`.
- Stock networks wired to REAL Hanzo endpoints (env-overridable), honoring
networkID == evmChainID for the Hanzo sovereign L1:
mainnet 36900 rpc.hanzo.network (matches the deployed wallet RPC)
testnet 36962 rpc.testnet.hanzo.network (canonical genesis id)
devnet 36964 rpc.devnet.hanzo.network (canonical genesis id)
API stays same-origin for the stock tiers (they differ by X-Environment, not host,
keeping the session cookie first-party).
- Local: networkID/chainID 1337 (localnet), RPC localhost, API same-origin — a home
user running the cloud binary sees "Local" and the console talks to their binary.
- Custom: user enters networkID + EVM chainID (defaults to networkID) + RPC + optional
API endpoint; validated, persisted in localStorage, removable.
Selecting a network is ONE move: the active network's id IS the X-Environment string,
so it re-scopes every cloud call AND retargets chain/RPC/API — no parallel state, no
special-casing. `activeApiBase()` points the direct cloud client at the selected
deployment (`apiEndpoint` override, else same-origin). Existing mainnet/testnet/devnet
scoping is unchanged; the wallet's HANZO_MAINNET is now derived from the network model
(one source of truth).
Tests: 20 new (registry, resolution, validation, persistence). Full suite 1991 green,
typecheck + build green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The network switcher now expresses ONE model — (label, networkID, evmChainID,
rpcEndpoint, apiEndpoint) — for every selectable network, in a new `lib/network.ts`.
- Stock networks wired to REAL Hanzo endpoints (env-overridable), honoring
networkID == evmChainID for the Hanzo sovereign L1:
mainnet 36900 rpc.hanzo.network (matches the deployed wallet RPC)
testnet 36962 rpc.testnet.hanzo.network (canonical genesis id)
devnet 36964 rpc.devnet.hanzo.network (canonical genesis id)
API stays same-origin for the stock tiers (they differ by X-Environment, not host,
keeping the session cookie first-party).
- Local: networkID/chainID 1337 (localnet), RPC localhost, API same-origin — a home
user running the cloud binary sees "Local" and the console talks to their binary.
- Custom: user enters networkID + EVM chainID (defaults to networkID) + RPC + optional
API endpoint; validated, persisted in localStorage, removable.
Selecting a network is ONE move: the active network's id IS the X-Environment string,
so it re-scopes every cloud call AND retargets chain/RPC/API — no parallel state, no
special-casing. `activeApiBase()` points the direct cloud client at the selected
deployment (`apiEndpoint` override, else same-origin). Existing mainnet/testnet/devnet
scoping is unchanged; the wallet's HANZO_MAINNET is now derived from the network model
(one source of truth).
Tests: 20 new (registry, resolution, validation, persistence). Full suite 1991 green,
typecheck + build green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
CTO contract: ZERO prefix before /v1/ on any cloud API call. The console
rewrote /v1/<cloudhead> -> /cloud/v1/<cloudhead> (next.config.mjs) and
cloudProxyV1Url built /cloud/v1/... directly, so the /cloud/ prefix leaked to
clients and 404'd Automations (/v1/automations/* -> /cloud/v1/automations/*).
The user-bearer BFF (mints a short-lived IAM token from the session cookie;
cookie never reaches cloud-api; org server-authoritative from the Bearer owner;
same-origin CSRF guard on mutations; least-privilege allowCloudSurface allow-list)
moves from app/cloud/[...path] to app/v1/[...path]. It re-prepends the v1/ root,
so the allow-list and upstream URL still see v1/<head>. Every guard in
forwardWithUserBearer is preserved — a PATH change, not a security change.
- Removed the CLOUD_V1_HEADS / CLOUD_INFRA_V1_HEADS / CLOUD_PRODUCT_V1_HEADS
-> /cloud/v1 rewrites in next.config.mjs; cloud heads now fall through to the
/v1 catch-all (no rewrite). cloudProxyBase deleted; cloudProxyV1Url === originV1Url.
- Kept beforeFiles dispatch (wins over the catch-all): AI heads -> /ai, admin
aggregate /v1/admin/* -> /admin/aggregate, visor catalog -> /vm, /v1/billing/*
-> /billing/v1, /v1/commerce/* -> /commerce/v1 (server-internal; client only
ever builds /v1/...).
- Scrubbed every /cloud/v1 and /cloud proxy reference across routes, rewrites,
client calls, tests, comments, and LLM.md; dead CLOUD_V1_HEADS comment refs fixed.
Acceptance (built server): GET /v1/automations/connectors -> 401 JSON (reaches
the cloud BFF, not 404, not the SPA shell); /v1/agents, /v1/platform/projects ->
401 JSON (regression OK); /v1/billing/balance -> 401 "Sign in to view billing"
(billing dispatch still wins); /v1/bogushead -> 404 JSON (allow-list intact).
git grep /cloud/v1 = ZERO. tsc + next build green; 1965/1965 unit tests pass.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
CTO contract: ZERO prefix before /v1/ on any cloud API call. The console
rewrote /v1/<cloudhead> -> /cloud/v1/<cloudhead> (next.config.mjs) and
cloudProxyV1Url built /cloud/v1/... directly, so the /cloud/ prefix leaked to
clients and 404'd Automations (/v1/automations/* -> /cloud/v1/automations/*).
The user-bearer BFF (mints a short-lived IAM token from the session cookie;
cookie never reaches cloud-api; org server-authoritative from the Bearer owner;
same-origin CSRF guard on mutations; least-privilege allowCloudSurface allow-list)
moves from app/cloud/[...path] to app/v1/[...path]. It re-prepends the v1/ root,
so the allow-list and upstream URL still see v1/<head>. Every guard in
forwardWithUserBearer is preserved — a PATH change, not a security change.
- Removed the CLOUD_V1_HEADS / CLOUD_INFRA_V1_HEADS / CLOUD_PRODUCT_V1_HEADS
-> /cloud/v1 rewrites in next.config.mjs; cloud heads now fall through to the
/v1 catch-all (no rewrite). cloudProxyBase deleted; cloudProxyV1Url === originV1Url.
- Kept beforeFiles dispatch (wins over the catch-all): AI heads -> /ai, admin
aggregate /v1/admin/* -> /admin/aggregate, visor catalog -> /vm, /v1/billing/*
-> /billing/v1, /v1/commerce/* -> /commerce/v1 (server-internal; client only
ever builds /v1/...).
- Scrubbed every /cloud/v1 and /cloud proxy reference across routes, rewrites,
client calls, tests, comments, and LLM.md; dead CLOUD_V1_HEADS comment refs fixed.
Acceptance (built server): GET /v1/automations/connectors -> 401 JSON (reaches
the cloud BFF, not 404, not the SPA shell); /v1/agents, /v1/platform/projects ->
401 JSON (regression OK); /v1/billing/balance -> 401 "Sign in to view billing"
(billing dispatch still wins); /v1/bogushead -> 404 JSON (allow-list intact).
git grep /cloud/v1 = ZERO. tsc + next build green; 1965/1965 unit tests pass.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
console#132 (unified Usage view + audit/logs/billing query depth) and #133 merged
at version 8.4.118 without a bump, so CI re-pushed the mutable v8.4.118 tag over the
prior build. Bump to v8.4.119 so the next build publishes a clean, distinct tag and
the git version again identifies a unique image (tag truth). The live deploy is
digest-pinned (universe#445); this fixes forward drift.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
console#132 (unified Usage view + audit/logs/billing query depth) and #133 merged
at version 8.4.118 without a bump, so CI re-pushed the mutable v8.4.118 tag over the
prior build. Bump to v8.4.119 so the next build publishes a clean, distinct tag and
the git version again identifies a unique image (tag truth). The live deploy is
digest-pinned (universe#445); this fixes forward drift.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The go:embed static console has NO Next BFF, so billingProxyBase()'s /billing/v1/*
route-handler is absent → SPA fallback (200 HTML) → the overview 'Real-time usage'
tile (UsageApi.overview→fetchUsageRecords) + wallet throw 'Invalid response (HTTP
200)'. In the embed, /v1/* is served same-origin by cloud (validates the session,
resolves org from the owner claim) — proven by the working bare-/v1 heads (agents/
tracker/analytics). So IS_EMBED addresses cloud's /v1/billing/* directly. The
Next-server console (console2.hanzo.ai) keeps the /billing BFF (IS_EMBED=false) —
no regression there; embed billing was already broken so this can only improve.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The go:embed static console has NO Next BFF, so billingProxyBase()'s /billing/v1/*
route-handler is absent → SPA fallback (200 HTML) → the overview 'Real-time usage'
tile (UsageApi.overview→fetchUsageRecords) + wallet throw 'Invalid response (HTTP
200)'. In the embed, /v1/* is served same-origin by cloud (validates the session,
resolves org from the owner claim) — proven by the working bare-/v1 heads (agents/
tracker/analytics). So IS_EMBED addresses cloud's /v1/billing/* directly. The
Next-server console (console2.hanzo.ai) keeps the /billing BFF (IS_EMBED=false) —
no regression there; embed billing was already broken so this can only improve.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Decomplect the TWO automation surfaces into ONE native one. The console had
two external tiles both pointing at the standalone auto.hanzo.ai engine
(`auto` → auto.hanzo.ai, `automations` → auto.hanzo.ai/automations). Collapse
them into ONE native module backed by the go-forward `/v1/automations` engine
(706-piece catalogue, flows/runs durable on the shared Tasks engine) — like the
App Platform module is native on /v1/platform. No link-out, one nav tile.
- registry: remove the `auto` external entry; convert `automations` from
kind:external → a native module (routes + :tab; subpages Connectors/Runs).
- AutomationsModule: Flows (create/enable/disable/run/delete) · Connectors (the
706-piece catalogue, search + category filter) · Runs — over the /cloud
user-bearer proxy (org from the Bearer owner; honest loading/empty/error).
- lib/api/automations.ts: AutomationsApi + defensive normalizers (mirrors
paas.ts transport: cloudProxyV1Url → /cloud/v1/automations).
- match-core: `/auto` + `/automation` alias → `automations` (was → external
`auto`); ONE product, ONE surface, aliases preserved. The external kind stays
for the Lux/Zoo chain-app tiles (test fixture repointed to a chain app).
- proxy-allow CLOUD_HEADS + next.config CLOUD_V1_HEADS: add `automations`.
tsc --noEmit clean (0 errors), vitest 1970/1970 (+25 automations, match-core
updated), next build ✓.
Decomplect the TWO automation surfaces into ONE native one. The console had
two external tiles both pointing at the standalone auto.hanzo.ai engine
(`auto` → auto.hanzo.ai, `automations` → auto.hanzo.ai/automations). Collapse
them into ONE native module backed by the go-forward `/v1/automations` engine
(706-piece catalogue, flows/runs durable on the shared Tasks engine) — like the
App Platform module is native on /v1/platform. No link-out, one nav tile.
- registry: remove the `auto` external entry; convert `automations` from
kind:external → a native module (routes + :tab; subpages Connectors/Runs).
- AutomationsModule: Flows (create/enable/disable/run/delete) · Connectors (the
706-piece catalogue, search + category filter) · Runs — over the /cloud
user-bearer proxy (org from the Bearer owner; honest loading/empty/error).
- lib/api/automations.ts: AutomationsApi + defensive normalizers (mirrors
paas.ts transport: cloudProxyV1Url → /cloud/v1/automations).
- match-core: `/auto` + `/automation` alias → `automations` (was → external
`auto`); ONE product, ONE surface, aliases preserved. The external kind stays
for the Lux/Zoo chain-app tiles (test fixture repointed to a chain app).
- proxy-allow CLOUD_HEADS + next.config CLOUD_V1_HEADS: add `automations`.
tsc --noEmit clean (0 errors), vitest 1970/1970 (+25 automations, match-core
updated), next build ✓.
New Startups module rendering the cloud /v1/crm/applications pipeline as a
@hanzo/data board (lanes by stage: applied→screened→qualified→credits-offered→
onboarded→rejected). Cards show company, AI score, tier-1 flag, suggested credits;
card opens a SlideOver drawer with all submitted data, the AI screen (score/tier1/
credits/summary + copy-able draft reply), stage timeline, stage-advance buttons
(PATCH via the server stage machine; drag also advances), and a grant-credits deep
link into billing. StartupsApi mirrors CrmApi (originV1Url → /cloud bearer proxy).
Registry: one import + one Apps entry.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
New Startups module rendering the cloud /v1/crm/applications pipeline as a
@hanzo/data board (lanes by stage: applied→screened→qualified→credits-offered→
onboarded→rejected). Cards show company, AI score, tier-1 flag, suggested credits;
card opens a SlideOver drawer with all submitted data, the AI screen (score/tier1/
credits/summary + copy-able draft reply), stage timeline, stage-advance buttons
(PATCH via the server stage machine; drag also advances), and a grant-credits deep
link into billing. StartupsApi mirrors CrmApi (originV1Url → /cloud bearer proxy).
Registry: one import + one Apps entry.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
- Usage (new product, Observe): the org's unified footprint on one screen —
KPI band (spend/MTD/balance/LLM tokens+spend/machines/GPUs), spend-over-time +
spend-by-category charts, a CSV-exportable cost breakdown, and per-source
connected/not-connected badges. Backed by GET /v1/usage/summary (+ visor
inventory), org-scoped via the /cloud bearer proxy.
- Audit (upgraded to enterprise grade): filters (time/actor/action/resource+id/
result), real server pagination, a per-event detail drawer with the hash-chain
linkage (immutability evidence), and CSV export. Now backed by the org-scoped
cloud audit trail (GET /v1/audit) instead of the IAM record list.
- Logs: a query builder on the application-logs lens (severity/service/
contains-text over the o11y time-range query) + localStorage saved views +
CSV export of visible rows; contains-text + CSV added to the request lens too.
- Billing Reports: CSV export of the full filtered usage breakdown.
- Shared: src/lib/csv.ts (RFC-4180 serializer + browser download, one place);
api clients usage-summary.ts + audit.ts; register usage/audit as /cloud proxy
heads (next.config CLOUD_V1_HEADS + proxy-allow CLOUD_HEADS).
tsc 0, vitest 1679 green, next build ok.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
- Usage (new product, Observe): the org's unified footprint on one screen —
KPI band (spend/MTD/balance/LLM tokens+spend/machines/GPUs), spend-over-time +
spend-by-category charts, a CSV-exportable cost breakdown, and per-source
connected/not-connected badges. Backed by GET /v1/usage/summary (+ visor
inventory), org-scoped via the /cloud bearer proxy.
- Audit (upgraded to enterprise grade): filters (time/actor/action/resource+id/
result), real server pagination, a per-event detail drawer with the hash-chain
linkage (immutability evidence), and CSV export. Now backed by the org-scoped
cloud audit trail (GET /v1/audit) instead of the IAM record list.
- Logs: a query builder on the application-logs lens (severity/service/
contains-text over the o11y time-range query) + localStorage saved views +
CSV export of visible rows; contains-text + CSV added to the request lens too.
- Billing Reports: CSV export of the full filtered usage breakdown.
- Shared: src/lib/csv.ts (RFC-4180 serializer + browser download, one place);
api clients usage-summary.ts + audit.ts; register usage/audit as /cloud proxy
heads (next.config CLOUD_V1_HEADS + proxy-allow CLOUD_HEADS).
tsc 0, vitest 1679 green, next build ok.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The hanzoai/cloud go:embed serves console2 as a static SPA with NO Node BFF
runtime, so the server-side session routes (/auth/refresh, /auth/session) and the
/billing/v1/me/welcome proxy don't exist — their client POSTs fall through to the
GET-only SPA fallback and 405 on every load (3 console errors/load, observed via
live playwright E2E as z@hanzo.ai). The console already runs on the casibase
session there (login→org→modules→real data all work while these 405'd), so the
probes are pure noise + a doomed session-rotation attempt.
Gate them behind IS_EMBED (NEXT_PUBLIC_CONSOLE_EMBED=1, set by build-embed.mjs):
in the embed, refreshSession()/consoleGet()/establishSession()/signout-DELETE and
the welcome-grant self-heal skip the fetch and fall back to the casibase session —
identical behavior, zero 405s. The Next-server console (console2.hanzo.ai,
admin.hanzo.ai) leaves IS_EMBED false and keeps the full durable-session BFF.
Tests: refresh.test.ts adds an embed case (skips fetch, resolves false); all 5
refresh + 22 canonical-path tests pass.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The hanzoai/cloud go:embed serves console2 as a static SPA with NO Node BFF
runtime, so the server-side session routes (/auth/refresh, /auth/session) and the
/billing/v1/me/welcome proxy don't exist — their client POSTs fall through to the
GET-only SPA fallback and 405 on every load (3 console errors/load, observed via
live playwright E2E as z@hanzo.ai). The console already runs on the casibase
session there (login→org→modules→real data all work while these 405'd), so the
probes are pure noise + a doomed session-rotation attempt.
Gate them behind IS_EMBED (NEXT_PUBLIC_CONSOLE_EMBED=1, set by build-embed.mjs):
in the embed, refreshSession()/consoleGet()/establishSession()/signout-DELETE and
the welcome-grant self-heal skip the fetch and fall back to the casibase session —
identical behavior, zero 405s. The Next-server console (console2.hanzo.ai,
admin.hanzo.ai) leaves IS_EMBED false and keeps the full durable-session BFF.
Tests: refresh.test.ts adds an embed case (skips fetch, resolves false); all 5
refresh + 22 canonical-path tests pass.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The Smart Routing toggle was a purely-local sealed-cookie preference. Ops can now
set a per-org default (auto_routing_active + default_session_routing) from
admin.hanzo.ai, exposed by cloud-api `GET /v1/get-routing-defaults`.
- New READ-ONLY proxy `app/ai-accounts/v1/routing-defaults` forwards the caller's
minted user bearer to cloud-api (org = token owner), same auth pattern as `/cloud`.
Does NOT touch the org-settings write path (confused-deputy escalation — reads only).
- The cookie preference becomes a tri-state user OVERRIDE (true/false/null); absent
cookie = null = follow the org default.
- One pure `resolveRouting(pref, org)` (src/lib/products/ai-accounts.ts): explicit
override wins, else org default, else off; an org that disabled routing disables the
toggle with honest copy.
- Fail-soft everywhere: `routingDefaults()` returns null on 404 (older cloud-api) /
error, so the tab works unchanged with the preference alone.
- RoutingTab shows "Organization default: On/Off — set by your admin".
Tests: +4 resolveRouting, normalizeSettings updated for tri-state. 1929 green.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The Smart Routing toggle was a purely-local sealed-cookie preference. Ops can now
set a per-org default (auto_routing_active + default_session_routing) from
admin.hanzo.ai, exposed by cloud-api `GET /v1/get-routing-defaults`.
- New READ-ONLY proxy `app/ai-accounts/v1/routing-defaults` forwards the caller's
minted user bearer to cloud-api (org = token owner), same auth pattern as `/cloud`.
Does NOT touch the org-settings write path (confused-deputy escalation — reads only).
- The cookie preference becomes a tri-state user OVERRIDE (true/false/null); absent
cookie = null = follow the org default.
- One pure `resolveRouting(pref, org)` (src/lib/products/ai-accounts.ts): explicit
override wins, else org default, else off; an org that disabled routing disables the
toggle with honest copy.
- Fail-soft everywhere: `routingDefaults()` returns null on 404 (older cloud-api) /
error, so the tab works unchanged with the preference alone.
- RoutingTab shows "Organization default: On/Off — set by your admin".
Tests: +4 resolveRouting, normalizeSettings updated for tri-state. 1929 green.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Wire the AccountsTab provider badge off trackedProviderIds (derived export new
in @hanzo/usage 0.1.2), bump the dep, so each provider row shows whether it has
a live in-app usage pipeline or is connect-only. typecheck + 1925 vitest green.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Wire the AccountsTab provider badge off trackedProviderIds (derived export new
in @hanzo/usage 0.1.2), bump the dep, so each provider row shows whether it has
a live in-app usage pipeline or is connect-only. typecheck + 1925 vitest green.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
cloud-api now enforces per-org auto-routing via OrgSettings.AutoRouting
(hanzoai/ai), toggled through the global-admin-gated, non-gateway-exposed
POST /v1/update-org-settings. The Routing tab is a customer surface whose
minted hanzo-console bearer is not global-admin, and the only admin proxy
(/admin/aggregate) fail-closed-403s a non-global-admin — so there is no clean
authenticated path to write cloud-side OrgSettings, and forging one would be a
confused-deputy escalation. Keep the sealed-cookie org preference and document
the exact unlock condition; no auth bodge, no behavior change.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
cloud-api now enforces per-org auto-routing via OrgSettings.AutoRouting
(hanzoai/ai), toggled through the global-admin-gated, non-gateway-exposed
POST /v1/update-org-settings. The Routing tab is a customer surface whose
minted hanzo-console bearer is not global-admin, and the only admin proxy
(/admin/aggregate) fail-closed-403s a non-global-admin — so there is no clean
authenticated path to write cloud-side OrgSettings, and forging one would be a
confused-deputy escalation. Keep the sealed-cookie org preference and document
the exact unlock condition; no auth bodge, no behavior change.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Add a Routing tab to the AI Accounts module explaining model:"auto" (local
zen -> cheap tier -> frontier, billed as the X-Routed-Model that served it, up
to 90% lower spend), with docs + blog links and a copyable curl for API users.
Persist the org/user routingEnabled preference server-side via the SAME sealed-
cookie store the credential store uses (extended with a non-secret settings
blob) behind a new static /ai-accounts/v1/settings route (GET/PUT, session-gated,
CSRF-guarded). The toggle is honest about scope: a preference Hanzo surfaces read;
API callers opt in per request with model:"auto".
- lib/server/ai-accounts.ts: AI_SETTINGS_COOKIE + normalizeSettings/readSettings/
settingsCookie (fail-closed to routing OFF)
- app/ai-accounts/v1/settings/route.ts: GET/PUT preference route
- lib/api/ai-accounts.ts: AiAccountsSettings + settings()/saveSettings()
- components/products/ai-accounts/RoutingTab.tsx: value-prop card + toggle + curl
- AIAccountsModule.tsx: third Routing tab; registry.tsx: routing subpage
Validate: tsc --noEmit clean; vitest 1925/1925 (+2 normalizeSettings).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Add a Routing tab to the AI Accounts module explaining model:"auto" (local
zen -> cheap tier -> frontier, billed as the X-Routed-Model that served it, up
to 90% lower spend), with docs + blog links and a copyable curl for API users.
Persist the org/user routingEnabled preference server-side via the SAME sealed-
cookie store the credential store uses (extended with a non-secret settings
blob) behind a new static /ai-accounts/v1/settings route (GET/PUT, session-gated,
CSRF-guarded). The toggle is honest about scope: a preference Hanzo surfaces read;
API callers opt in per request with model:"auto".
- lib/server/ai-accounts.ts: AI_SETTINGS_COOKIE + normalizeSettings/readSettings/
settingsCookie (fail-closed to routing OFF)
- app/ai-accounts/v1/settings/route.ts: GET/PUT preference route
- lib/api/ai-accounts.ts: AiAccountsSettings + settings()/saveSettings()
- components/products/ai-accounts/RoutingTab.tsx: value-prop card + toggle + curl
- AIAccountsModule.tsx: third Routing tab; registry.tsx: routing subpage
Validate: tsc --noEmit clean; vitest 1925/1925 (+2 normalizeSettings).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
build:embed (the hanzoai/cloud go:embed source) failed in any isolated clone:
@hanzo/usage was pinned to file:../usage/packages/core — a sibling repo absent
from the Docker console-stage clone — so it resolved to a dangling symlink and
`next build` died with "Cannot find module '@hanzo/usage'". This is why the
cloud image silently shipped the placeholder shell.
Pin @hanzo/usage to the published 0.1.0 (registry.npmjs.org; exports the
UsageSnapshot type the console imports). Also drop the accidentally-committed
`node_modules` symlink (-> /Users/z/work/hanzo/console2/node_modules, a dead
macOS dev path to the old repo name) and tighten .gitignore to a bare
`node_modules` so it can't recur.
Verified: npm install + npm run build:embed from this branch emit a real static
export (7.7M out/, ~360KB index.html + 4.4M _next/) that hanzoai/cloud embeds.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
build:embed (the hanzoai/cloud go:embed source) failed in any isolated clone:
@hanzo/usage was pinned to file:../usage/packages/core — a sibling repo absent
from the Docker console-stage clone — so it resolved to a dangling symlink and
`next build` died with "Cannot find module '@hanzo/usage'". This is why the
cloud image silently shipped the placeholder shell.
Pin @hanzo/usage to the published 0.1.0 (registry.npmjs.org; exports the
UsageSnapshot type the console imports). Also drop the accidentally-committed
`node_modules` symlink (-> /Users/z/work/hanzo/console2/node_modules, a dead
macOS dev path to the old repo name) and tighten .gitignore to a bare
`node_modules` so it can't recur.
Verified: npm install + npm run build:embed from this branch emit a real static
export (7.7M out/, ~360KB index.html + 4.4M _next/) that hanzoai/cloud embeds.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
New Observe module 'ai-accounts' (label AI Accounts) with Overview + Accounts
tabs, over the headless @hanzo/usage engine plus the org's Hanzo commerce lane.
- Registry: one CatalogEntry (kind module, routes ''+:tab, subpage 'accounts')
so /ai-accounts and /ai-accounts/accounts route with no new page files.
- Accounts tab: connect Hanzo (native), OpenAI/Codex, Anthropic/Claude by
pasting an API key / OAuth token / cookie header; non-AI groups are honest
catalog-driven 'coming soon' rows. Secret POSTed to the new server route.
- Overview tab: server route runs runPipeline (nodeHost) per connected provider
and merges the real commerce CloudUsageOverview for the Hanzo lane; empty
state has a 'Connect your AI accounts' CTA (1% routed-usage fee copy).
- Credentials: sealed (AES-256-GCM, reusing session.ts) in an httpOnly cookie
scoped to /ai-accounts, per user; never localStorage, never logged, masked on
read-back. TODO(KMS) to move at-rest storage to kms.hanzo.ai.
- Dep: @hanzo/usage file:../usage/packages/core; serverExternalPackages entry.
typecheck clean; vitest 1923/1923.
New Observe module 'ai-accounts' (label AI Accounts) with Overview + Accounts
tabs, over the headless @hanzo/usage engine plus the org's Hanzo commerce lane.
- Registry: one CatalogEntry (kind module, routes ''+:tab, subpage 'accounts')
so /ai-accounts and /ai-accounts/accounts route with no new page files.
- Accounts tab: connect Hanzo (native), OpenAI/Codex, Anthropic/Claude by
pasting an API key / OAuth token / cookie header; non-AI groups are honest
catalog-driven 'coming soon' rows. Secret POSTed to the new server route.
- Overview tab: server route runs runPipeline (nodeHost) per connected provider
and merges the real commerce CloudUsageOverview for the Hanzo lane; empty
state has a 'Connect your AI accounts' CTA (1% routed-usage fee copy).
- Credentials: sealed (AES-256-GCM, reusing session.ts) in an httpOnly cookie
scoped to /ai-accounts, per user; never localStorage, never logged, masked on
read-back. TODO(KMS) to move at-rest storage to kms.hanzo.ai.
- Dep: @hanzo/usage file:../usage/packages/core; serverExternalPackages entry.
typecheck clean; vitest 1923/1923.
Every login now lands org-LESS on a full-page org picker (the "Home" org
list) instead of auto-scoping into the brand org. Clicking an org card scopes
the whole console to it (X-Org-Id); a sidebar Home affordance de-scopes back
to the picker. A one-org user still sees a one-card list and clicks in; a
global admin (z@hanzo.ai) sees every live org (masquerade).
- org-scope: add the SELECTION concern orthogonal to the org VALUE —
hasSelectedOrg()/enterOrg()/leaveOrg(). currentOrg()/setCurrentOrg()/
isScopedAway()/switchOrg()/filterOrgs() unchanged; switchOrg keeps the
selection set. Pure + tested (+4 tests).
- OrgPicker: the full-page landing — responsive card grid (logo or monogram,
role, honest quick facts), filter (reuses filterOrgs), client "Show more"
pagination (PAGE_SIZE 24), a Create-organization CTA (→ OrgOnboarding), and
honest loading/empty/no-match/error states (own-org fallback, never
fabricated). Global admin lists all orgs via /admin/iam; a tenant sees its
own org synthesized from the session.
- org-picker/logic: the pure decision core (sort/filter/paginate + the card
view-model, role, facts). 25 vitest cases, incl. a literal-substring
(no-regex) guard.
- OrgGate: routes 0 orgs → OrgOnboarding · has-orgs+none-selected → OrgPicker
· selected → the scoped shell. Drops the auto-scope-seed/reload effect
(explicit enter replaces it). Selection read on mount to avoid a flash.
- DashboardShell: the sidebar top-left keeps the OrgSwitcher (active org +
quick-switch) and gains a Home affordance (leaveOrg → picker) in the
expanded rail, the collapsed rail, and the mobile drawer.
- Drive-by (unblocks `next build` — pre-existing on this base): null-guard
useSearchParams()/usePathname() in app/accept + SearchModule (Next 15
stricter types).
typecheck clean (0), vitest 1923/1923 (+36 across the two new/updated files),
next build green (18/18). @hanzo/gui v5 shorthands only.
Every login now lands org-LESS on a full-page org picker (the "Home" org
list) instead of auto-scoping into the brand org. Clicking an org card scopes
the whole console to it (X-Org-Id); a sidebar Home affordance de-scopes back
to the picker. A one-org user still sees a one-card list and clicks in; a
global admin (z@hanzo.ai) sees every live org (masquerade).
- org-scope: add the SELECTION concern orthogonal to the org VALUE —
hasSelectedOrg()/enterOrg()/leaveOrg(). currentOrg()/setCurrentOrg()/
isScopedAway()/switchOrg()/filterOrgs() unchanged; switchOrg keeps the
selection set. Pure + tested (+4 tests).
- OrgPicker: the full-page landing — responsive card grid (logo or monogram,
role, honest quick facts), filter (reuses filterOrgs), client "Show more"
pagination (PAGE_SIZE 24), a Create-organization CTA (→ OrgOnboarding), and
honest loading/empty/no-match/error states (own-org fallback, never
fabricated). Global admin lists all orgs via /admin/iam; a tenant sees its
own org synthesized from the session.
- org-picker/logic: the pure decision core (sort/filter/paginate + the card
view-model, role, facts). 25 vitest cases, incl. a literal-substring
(no-regex) guard.
- OrgGate: routes 0 orgs → OrgOnboarding · has-orgs+none-selected → OrgPicker
· selected → the scoped shell. Drops the auto-scope-seed/reload effect
(explicit enter replaces it). Selection read on mount to avoid a flash.
- DashboardShell: the sidebar top-left keeps the OrgSwitcher (active org +
quick-switch) and gains a Home affordance (leaveOrg → picker) in the
expanded rail, the collapsed rail, and the mobile drawer.
- Drive-by (unblocks `next build` — pre-existing on this base): null-guard
useSearchParams()/usePathname() in app/accept + SearchModule (Next 15
stricter types).
typecheck clean (0), vitest 1923/1923 (+36 across the two new/updated files),
next build green (18/18). @hanzo/gui v5 shorthands only.
The level-1 product nav let multiple category sections stay expanded at once
(toggleCategory flipped each category independently), cluttering the sidebar.
Make it a true single-open accordion: opening a category collapses whatever was
open, and with no explicit choice the active route's category is the one open
section. Keeps the filtering=all-open and active-route-visible behaviors.
- nav-accordion.ts: openChoice() enforces the single-open invariant on read;
categoryIsOpen honors exactly one choice (else the active category);
toggleCategory opens only the clicked category (or clears on re-click).
Exported signatures unchanged — DashboardShell binding untouched.
- test: assert the single-open invariant (opening one collapses others; never
two expanded). 11/11 green.
The level-1 product nav let multiple category sections stay expanded at once
(toggleCategory flipped each category independently), cluttering the sidebar.
Make it a true single-open accordion: opening a category collapses whatever was
open, and with no explicit choice the active route's category is the one open
section. Keeps the filtering=all-open and active-route-visible behaviors.
- nav-accordion.ts: openChoice() enforces the single-open invariant on read;
categoryIsOpen honors exactly one choice (else the active category);
toggleCategory opens only the clicked category (or clears on re-click).
Exported signatures unchanged — DashboardShell binding untouched.
- test: assert the single-open invariant (opening one collapses others; never
two expanded). 11/11 green.
/models regression — groupByFamily dropped every do-ai model (OpenAI, Claude,
DeepSeek, Llama, …) because their provider "do-ai" matched no curated family, so
only Zen showed. Families are now derived from the ONE brand resolver
(brandForModel, by model id), so every gateway vendor surfaces (Zen first, then
OpenAI/Anthropic/Google/Meta/DeepSeek/Qwen/…); an unknown vendor falls to an honest
"Other models" catch-all — a chat model is never silently dropped again. Adds
OpenAI o-series id resolution + curated GLM/MiniMax marks; embedding/video ids are
typed correctly so they stay out of the chat browser.
/auth/refresh 502 — tokenRequest retries once on a TRANSIENT upstream failure
(network error or a non-JSON/HTML body, e.g. IAM mid-roll on its Recreate strategy),
self-healing a momentary blip; a definitive OAuth error envelope is still not retried
(invalid_grant → 401, else 502). The /models page also renders independently of the
session (pricing/plans failures are already caught).
Overview cleanup — removed the redundant Billing/Usage/Metrics summary band from
every product overview (the dedicated Billing/Usage/Metrics pages own those figures);
deleted the now-dead ProductQuickLinks component + quick-links helpers.
Sidebar redesign (Google-Cloud-Console style) — the top switcher is the USER
(account menu: profile · theme · sign out) with the ORG switcher directly below it;
removed the org-accent green left strip; the two-level slide is replaced by a single
always-visible grouped nav where the active product's sub-pages expand INLINE, so any
product or sub-page routes directly with no "back". The org switcher moved out of the
topbar (project scope stays). Category overview gains prev/next paging through the
fixed category order.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
/models regression — groupByFamily dropped every do-ai model (OpenAI, Claude,
DeepSeek, Llama, …) because their provider "do-ai" matched no curated family, so
only Zen showed. Families are now derived from the ONE brand resolver
(brandForModel, by model id), so every gateway vendor surfaces (Zen first, then
OpenAI/Anthropic/Google/Meta/DeepSeek/Qwen/…); an unknown vendor falls to an honest
"Other models" catch-all — a chat model is never silently dropped again. Adds
OpenAI o-series id resolution + curated GLM/MiniMax marks; embedding/video ids are
typed correctly so they stay out of the chat browser.
/auth/refresh 502 — tokenRequest retries once on a TRANSIENT upstream failure
(network error or a non-JSON/HTML body, e.g. IAM mid-roll on its Recreate strategy),
self-healing a momentary blip; a definitive OAuth error envelope is still not retried
(invalid_grant → 401, else 502). The /models page also renders independently of the
session (pricing/plans failures are already caught).
Overview cleanup — removed the redundant Billing/Usage/Metrics summary band from
every product overview (the dedicated Billing/Usage/Metrics pages own those figures);
deleted the now-dead ProductQuickLinks component + quick-links helpers.
Sidebar redesign (Google-Cloud-Console style) — the top switcher is the USER
(account menu: profile · theme · sign out) with the ORG switcher directly below it;
removed the org-accent green left strip; the two-level slide is replaced by a single
always-visible grouped nav where the active product's sub-pages expand INLINE, so any
product or sub-page routes directly with no "back". The org switcher moved out of the
topbar (project scope stays). Category overview gains prev/next paging through the
fixed category order.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
v8.4.114 rendered the upstream attribution only on NativeOverview products
(gateway) — resource cards and bespoke admin modules bypassed it. Add ONE
shared surface instead: `ProductUpstreamNote` mounted once in DashboardShell
under the product content column, resolving the active entry's `upstream` from
the catalog (the single source of truth). Now every fork module — native,
resource, or bespoke — shows "Built on open source — forked from <name>
(<license>)" linking upstream. Original Hanzo products render nothing.
Drop the now-redundant per-overview "Forked from" button in NativeOverview
(the shared note supersedes it — one link, one way); the informational
"Upstream" key-fact stays.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
v8.4.114 rendered the upstream attribution only on NativeOverview products
(gateway) — resource cards and bespoke admin modules bypassed it. Add ONE
shared surface instead: `ProductUpstreamNote` mounted once in DashboardShell
under the product content column, resolving the active entry's `upstream` from
the catalog (the single source of truth). Now every fork module — native,
resource, or bespoke — shows "Built on open source — forked from <name>
(<license>)" linking upstream. Original Hanzo products render nothing.
Drop the now-redundant per-overview "Forked from" button in NativeOverview
(the shared note supersedes it — one link, one way); the informational
"Upstream" key-fact stays.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Add an optional `upstream {name,url,license}` field to CatalogBase and set it
on the 12 verified fork modules (upstream verified against each repo's git
upstream remote / LICENSE / tree fingerprint):
base, records → PocketBase (MIT) iam → Casdoor (Apache-2.0)
chat → LibreChat (MIT) kv → Valkey (BSD-3-Clause)
docdb → FerretDB (Apache-2.0) s3 → SeaweedFS (Apache-2.0)
search → Meilisearch (MIT) vector → Qdrant (Apache-2.0)
studio → ComfyUI (GPL-3.0) auto → Activepieces (MIT)
gateway → KrakenD (Apache-2.0)
Render it in the module about surfaces (reusing existing plumbing, no new
components): NativeOverview gains a "Forked from <name>" link button beside
Source, resolveSpec appends an "Upstream" key-fact (name + SPDX license), and
the ProductInterstitial open-source card notes the fork. Original Hanzo
products (no upstream) are unchanged. Distinct from the Zen model brand policy —
this credits product forks, never model provenance.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Add an optional `upstream {name,url,license}` field to CatalogBase and set it
on the 12 verified fork modules (upstream verified against each repo's git
upstream remote / LICENSE / tree fingerprint):
base, records → PocketBase (MIT) iam → Casdoor (Apache-2.0)
chat → LibreChat (MIT) kv → Valkey (BSD-3-Clause)
docdb → FerretDB (Apache-2.0) s3 → SeaweedFS (Apache-2.0)
search → Meilisearch (MIT) vector → Qdrant (Apache-2.0)
studio → ComfyUI (GPL-3.0) auto → Activepieces (MIT)
gateway → KrakenD (Apache-2.0)
Render it in the module about surfaces (reusing existing plumbing, no new
components): NativeOverview gains a "Forked from <name>" link button beside
Source, resolveSpec appends an "Upstream" key-fact (name + SPDX license), and
the ProductInterstitial open-source card notes the fork. Original Hanzo
products (no upstream) are unchanged. Distinct from the Zen model brand policy —
this credits product forks, never model provenance.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Adds a customer-facing Finance surface (id finance-center, label Finance, Observe)
rendering the SHARED @hanzo/finance-ui FinanceDashboard — the SAME board
finance.hanzo.ai renders — over the unified finance ledger (/v1/finance/*), so a
spend/usage/credits card is identical across both surfaces (the shared-reuse point).
- finance-ledger.ts: console transport (the /cloud user-bearer proxy resolves the
org from the token owner; cookie-only bare /v1/finance/* 403s on the live ingress),
envelope-unwrap, wired to httpFinanceClient. +4 tests.
- FinanceModule.tsx: console chrome (PageHeader) + honest states (BackendStateCard)
around the shared board. Nothing reimplemented, nothing fabricated.
- next.config.mjs: 'finance' -> CLOUD_V1_HEADS (rewrite /v1/finance/* -> /cloud);
@hanzo/finance-ui -> transpilePackages.
- proxy-allow.ts: 'finance' -> CLOUD_HEADS (defense-in-depth allow-list).
- registry.tsx: catalog entry (distinct id from the admin 'finance' FinOps board and
from 'billing'/commerce).
Distinct from the shared package (@hanzo/finance-ui, published) which both this
module and finance.hanzo.ai consume. tsc clean; vitest 1891/1891; next build green.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Adds a customer-facing Finance surface (id finance-center, label Finance, Observe)
rendering the SHARED @hanzo/finance-ui FinanceDashboard — the SAME board
finance.hanzo.ai renders — over the unified finance ledger (/v1/finance/*), so a
spend/usage/credits card is identical across both surfaces (the shared-reuse point).
- finance-ledger.ts: console transport (the /cloud user-bearer proxy resolves the
org from the token owner; cookie-only bare /v1/finance/* 403s on the live ingress),
envelope-unwrap, wired to httpFinanceClient. +4 tests.
- FinanceModule.tsx: console chrome (PageHeader) + honest states (BackendStateCard)
around the shared board. Nothing reimplemented, nothing fabricated.
- next.config.mjs: 'finance' -> CLOUD_V1_HEADS (rewrite /v1/finance/* -> /cloud);
@hanzo/finance-ui -> transpilePackages.
- proxy-allow.ts: 'finance' -> CLOUD_HEADS (defense-in-depth allow-list).
- registry.tsx: catalog entry (distinct id from the admin 'finance' FinOps board and
from 'billing'/commerce).
Distinct from the shared package (@hanzo/finance-ui, published) which both this
module and finance.hanzo.ai consume. tsc clean; vitest 1891/1891; next build green.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
State-of-the-art visual/interaction QA pass (as Dave/maxpower, live) found the
console already excellent across mobile/tablet/laptop/desktop — distinct per-family
model icons, honest GPU prepay-card vs Machines credit gate, working ⌘K palette,
org switcher, quick-links band navigation, light+dark contrast, and NO horizontal
body overflow at any viewport. Four small CSS/markup polish defects were fixed:
- **Touch tap targets < 44px.** The top-bar controls (hamburger/Apps/account at
size="$3" = 36px; ThemeToggle/Help/Notifications at size="$2" = ~28px) were under
the 44×44 minimum on a coarse pointer. Added a `hz-topbar` class on the top-bar
XStack (DashboardShell) + a `@media (pointer: coarse){ .hz-topbar button {min-height/
min-width:44px} }` rule — touch devices meet WCAG 2.5.5; desktop mouse density is
deliberately unchanged (the rule is coarse-pointer-scoped).
- **No global keyboard focus ring.** Added a `:focus-visible` outline floor
(theme-token colour, adapts light/dark) + `:focus:not(:focus-visible){outline:none}`
so every control is focus-visible on tab-through without touching pointer presses.
- **Horizontal-scroll guard.** `html, body { overflow-x: clip }` — a stray fixed/
off-screen drawer can never scroll the whole document sideways (`clip` keeps sticky/
fixed descendants working). No overflow was observed live; this is the permanent floor.
- **Floating chat FAB overlapped bottom-right content** (Live/Catalog pills, table
badges). Reserved an 80px bottom gutter on the content column (split the content
`py` into responsive `pt` + fixed `pb={80}`) so the last row always clears the FAB.
e2e: e2e/polish-qa.spec.ts locks all of it — a PUBLIC block (runs in CI, no creds)
for the overflow-x guard + :focus-visible ring + no-sideways-scroll at 390/768/1440,
and an authenticated block (gates on HANZO_PASSWORD, repo convention) for overview
real-data, quick-links navigation, the GPU prepay-card gate, distinct model icons,
mobile sidebar→drawer collapse, and the ≥44px touch tap-targets.
Verification: tsc --noEmit clean; next build ✓ (BUILD_EXIT:0). Rebased on origin/main
(v8.4.111) → v8.4.112. Live re-verify + the authenticated e2e block are the post-deploy
gate (the (dashboard) group is behind AuthGate).
Co-authored-by: Claude <noreply@anthropic.com>
State-of-the-art visual/interaction QA pass (as Dave/maxpower, live) found the
console already excellent across mobile/tablet/laptop/desktop — distinct per-family
model icons, honest GPU prepay-card vs Machines credit gate, working ⌘K palette,
org switcher, quick-links band navigation, light+dark contrast, and NO horizontal
body overflow at any viewport. Four small CSS/markup polish defects were fixed:
- **Touch tap targets < 44px.** The top-bar controls (hamburger/Apps/account at
size="$3" = 36px; ThemeToggle/Help/Notifications at size="$2" = ~28px) were under
the 44×44 minimum on a coarse pointer. Added a `hz-topbar` class on the top-bar
XStack (DashboardShell) + a `@media (pointer: coarse){ .hz-topbar button {min-height/
min-width:44px} }` rule — touch devices meet WCAG 2.5.5; desktop mouse density is
deliberately unchanged (the rule is coarse-pointer-scoped).
- **No global keyboard focus ring.** Added a `:focus-visible` outline floor
(theme-token colour, adapts light/dark) + `:focus:not(:focus-visible){outline:none}`
so every control is focus-visible on tab-through without touching pointer presses.
- **Horizontal-scroll guard.** `html, body { overflow-x: clip }` — a stray fixed/
off-screen drawer can never scroll the whole document sideways (`clip` keeps sticky/
fixed descendants working). No overflow was observed live; this is the permanent floor.
- **Floating chat FAB overlapped bottom-right content** (Live/Catalog pills, table
badges). Reserved an 80px bottom gutter on the content column (split the content
`py` into responsive `pt` + fixed `pb={80}`) so the last row always clears the FAB.
e2e: e2e/polish-qa.spec.ts locks all of it — a PUBLIC block (runs in CI, no creds)
for the overflow-x guard + :focus-visible ring + no-sideways-scroll at 390/768/1440,
and an authenticated block (gates on HANZO_PASSWORD, repo convention) for overview
real-data, quick-links navigation, the GPU prepay-card gate, distinct model icons,
mobile sidebar→drawer collapse, and the ≥44px touch tap-targets.
Verification: tsc --noEmit clean; next build ✓ (BUILD_EXIT:0). Rebased on origin/main
(v8.4.111) → v8.4.112. Live re-verify + the authenticated e2e block are the post-deploy
gate (the (dashboard) group is behind AuthGate).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Mirrors the Affiliates + Referrals pattern for the new OSS Author program over the
real cloud /v1/authors surface (native-Go clients/authors). An author connects GitHub,
proves they own a repo (GitHub OAuth admin-check OR a hanzo.json verify-code file), and
earns a royalty when any org deploys their open-source project on Hanzo.
- AuthorsModule (customer, id:authors, Web3): not-enrolled Connect-GitHub card + 3-step
explainer; enrolled dashboard — status/verified/share, 4 MetricCards, a repositories
panel (verify + per-repo Copy-badge markdown), a verify-by-file recipe (hanzo.json
snippet), deploys-of-your-work, and payout history. Honest empty states throughout.
- AuthorsAdminModule (id:authors-admin, admin:true, Observe): Run-sweep + summary tiles +
author directory with status-gated Approve(+share override)/Reactivate/Payout/Suspend;
server-gated via /admin/aggregate; honest access/empty/error states.
- Clients: lib/api/authors.ts (BARE JSON via cloudProxyV1Url) + lib/api/admin-authors.ts
({status,msg,data} envelope via originGet/originPost); pure products/authors/logic.ts.
- Registration: 2 registry.tsx catalog entries (BookOpen icon); 'authors' added to
next.config.mjs CLOUD_V1_HEADS + ADMIN_V1_HEADS, proxy-allow.ts CLOUD_HEADS, and
admin-aggregate.ts ADMIN_AGGREGATE_HEADS. No claim.ts/session wiring (connect/verify
based — no ?xxx= link) and no app/ route (the catch-all resolves it).
Gates green: tsc --noEmit 0 errors; vitest 1864 → 1887 (+23: 7 authors + 8 admin + 8 logic);
next build ✓ (Compiled successfully, 18/18 pages).
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Mirrors the Affiliates + Referrals pattern for the new OSS Author program over the
real cloud /v1/authors surface (native-Go clients/authors). An author connects GitHub,
proves they own a repo (GitHub OAuth admin-check OR a hanzo.json verify-code file), and
earns a royalty when any org deploys their open-source project on Hanzo.
- AuthorsModule (customer, id:authors, Web3): not-enrolled Connect-GitHub card + 3-step
explainer; enrolled dashboard — status/verified/share, 4 MetricCards, a repositories
panel (verify + per-repo Copy-badge markdown), a verify-by-file recipe (hanzo.json
snippet), deploys-of-your-work, and payout history. Honest empty states throughout.
- AuthorsAdminModule (id:authors-admin, admin:true, Observe): Run-sweep + summary tiles +
author directory with status-gated Approve(+share override)/Reactivate/Payout/Suspend;
server-gated via /admin/aggregate; honest access/empty/error states.
- Clients: lib/api/authors.ts (BARE JSON via cloudProxyV1Url) + lib/api/admin-authors.ts
({status,msg,data} envelope via originGet/originPost); pure products/authors/logic.ts.
- Registration: 2 registry.tsx catalog entries (BookOpen icon); 'authors' added to
next.config.mjs CLOUD_V1_HEADS + ADMIN_V1_HEADS, proxy-allow.ts CLOUD_HEADS, and
admin-aggregate.ts ADMIN_AGGREGATE_HEADS. No claim.ts/session wiring (connect/verify
based — no ?xxx= link) and no app/ route (the catch-all resolves it).
Gates green: tsc --noEmit 0 errors; vitest 1864 → 1887 (+23: 7 authors + 8 admin + 8 logic);
next build ✓ (Compiled successfully, 18/18 pages).
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Mirrors the Affiliates + Referrals pattern for the new OSS Author program over the
real cloud /v1/authors surface (native-Go clients/authors). An author connects GitHub,
proves they own a repo (GitHub OAuth admin-check OR a hanzo.json verify-code file), and
earns a royalty when any org deploys their open-source project on Hanzo.
- AuthorsModule (customer, id:authors, Web3): not-enrolled Connect-GitHub card + 3-step
explainer; enrolled dashboard — status/verified/share, 4 MetricCards, a repositories
panel (verify + per-repo Copy-badge markdown), a verify-by-file recipe (hanzo.json
snippet), deploys-of-your-work, and payout history. Honest empty states throughout.
- AuthorsAdminModule (id:authors-admin, admin:true, Observe): Run-sweep + summary tiles +
author directory with status-gated Approve(+share override)/Reactivate/Payout/Suspend;
server-gated via /admin/aggregate; honest access/empty/error states.
- Clients: lib/api/authors.ts (BARE JSON via cloudProxyV1Url) + lib/api/admin-authors.ts
({status,msg,data} envelope via originGet/originPost); pure products/authors/logic.ts.
- Registration: 2 registry.tsx catalog entries (BookOpen icon); 'authors' added to
next.config.mjs CLOUD_V1_HEADS + ADMIN_V1_HEADS, proxy-allow.ts CLOUD_HEADS, and
admin-aggregate.ts ADMIN_AGGREGATE_HEADS. No claim.ts/session wiring (connect/verify
based — no ?xxx= link) and no app/ route (the catch-all resolves it).
Gates green: tsc --noEmit 0 errors; vitest 1864 → 1887 (+23: 7 authors + 8 admin + 8 logic);
next build ✓ (Compiled successfully, 18/18 pages).
Mirrors the Affiliates + Referrals pattern for the new OSS Author program over the
real cloud /v1/authors surface (native-Go clients/authors). An author connects GitHub,
proves they own a repo (GitHub OAuth admin-check OR a hanzo.json verify-code file), and
earns a royalty when any org deploys their open-source project on Hanzo.
- AuthorsModule (customer, id:authors, Web3): not-enrolled Connect-GitHub card + 3-step
explainer; enrolled dashboard — status/verified/share, 4 MetricCards, a repositories
panel (verify + per-repo Copy-badge markdown), a verify-by-file recipe (hanzo.json
snippet), deploys-of-your-work, and payout history. Honest empty states throughout.
- AuthorsAdminModule (id:authors-admin, admin:true, Observe): Run-sweep + summary tiles +
author directory with status-gated Approve(+share override)/Reactivate/Payout/Suspend;
server-gated via /admin/aggregate; honest access/empty/error states.
- Clients: lib/api/authors.ts (BARE JSON via cloudProxyV1Url) + lib/api/admin-authors.ts
({status,msg,data} envelope via originGet/originPost); pure products/authors/logic.ts.
- Registration: 2 registry.tsx catalog entries (BookOpen icon); 'authors' added to
next.config.mjs CLOUD_V1_HEADS + ADMIN_V1_HEADS, proxy-allow.ts CLOUD_HEADS, and
admin-aggregate.ts ADMIN_AGGREGATE_HEADS. No claim.ts/session wiring (connect/verify
based — no ?xxx= link) and no app/ route (the catch-all resolves it).
Gates green: tsc --noEmit 0 errors; vitest 1864 → 1887 (+23: 7 authors + 8 admin + 8 logic);
next build ✓ (Compiled successfully, 18/18 pages).
Pixel QA at 360/390 phone widths surfaced three mobile defects, all now fixed
in the shared primitives (verified in a real browser at 390 + 834):
- PageHeader: a header with many actions (Tracker's Projects/Refresh/List/Board/
New issue/Delete) ran off-screen and CLIPPED the last buttons — "New issue" and
"Delete project" were unreachable on a phone. Actions now take a full line below
the title and WRAP (< $md); inline right-aligned at $md+. TrackerModule's action
row is full-width on phones so it wraps rather than overflows.
- Field (SlideOver create/edit form): the fixed 180px label + 240px control forced
the row wider than a phone, clipping every label. FieldRow now STACKS (label above
a full-width control) below $md and keeps the two-column layout at $md+.
- DataTable empty state: the "Nothing here yet." message sat inside the min-width
(horizontally scrolling) table area and was clipped off the right on a phone. It
now renders outside the scroll area and centers/wraps within the visible width.
No change at tablet/laptop/desktop (>= $md) — the two-column form and inline actions
are preserved. typecheck clean.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Pixel QA at 360/390 phone widths surfaced three mobile defects, all now fixed
in the shared primitives (verified in a real browser at 390 + 834):
- PageHeader: a header with many actions (Tracker's Projects/Refresh/List/Board/
New issue/Delete) ran off-screen and CLIPPED the last buttons — "New issue" and
"Delete project" were unreachable on a phone. Actions now take a full line below
the title and WRAP (< $md); inline right-aligned at $md+. TrackerModule's action
row is full-width on phones so it wraps rather than overflows.
- Field (SlideOver create/edit form): the fixed 180px label + 240px control forced
the row wider than a phone, clipping every label. FieldRow now STACKS (label above
a full-width control) below $md and keeps the two-column layout at $md+.
- DataTable empty state: the "Nothing here yet." message sat inside the min-width
(horizontally scrolling) table area and was clipped off the right on a phone. It
now renders outside the scroll area and centers/wraps within the visible width.
No change at tablet/laptop/desktop (>= $md) — the two-column form and inline actions
are preserved. typecheck clean.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Turns the placeholder referrals entry (a ConsoleFeatureModule shim that 404'd —
no backend existed) into a real product over the new cloud /v1/referrals surface.
- src/lib/api/referrals.ts — customer client over the /cloud user-bearer proxy
(cloudProxyV1Url, live-ingress-safe for a new head): overview + claim, defensive
normalizers.
- ReferralsModule — one clean screen: link + Copy, 'give $5 get $10' explainer,
three real stat tiles (invites/credited/credit earned), referrals list with live
status; loading/BackendStateCard/empty states, no fabricated rows.
- Admin board (admin: true, hidden from customers): src/lib/api/admin-referrals.ts
via originGet/originPost -> the global-admin-gated app/admin/aggregate proxy;
ReferralsAdminModule = summary tiles + directory + a 'Run sweep' action.
- Signup capture: src/lib/referrals/claim.ts (stashReferralCode reads ?ref into
localStorage; claimReferralOnce POSTs /v1/referrals/claim once per session per
org after first login), wired into session.tsx beside the welcome grant.
- Wiring: 'referrals' added to CLOUD_V1_HEADS + CLOUD_HEADS (customer proxy) and
ADMIN_V1_HEADS + ADMIN_AGGREGATE_HEADS (admin proxy). Registry repointed to the
real module + an admin entry; dropped the dead docs deep link.
Gates: tsc --noEmit clean; vitest 1838/1838 (+15 referrals api/logic/claim); next
build ok. Version 8.4.107 -> 8.4.108.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Turns the placeholder referrals entry (a ConsoleFeatureModule shim that 404'd —
no backend existed) into a real product over the new cloud /v1/referrals surface.
- src/lib/api/referrals.ts — customer client over the /cloud user-bearer proxy
(cloudProxyV1Url, live-ingress-safe for a new head): overview + claim, defensive
normalizers.
- ReferralsModule — one clean screen: link + Copy, 'give $5 get $10' explainer,
three real stat tiles (invites/credited/credit earned), referrals list with live
status; loading/BackendStateCard/empty states, no fabricated rows.
- Admin board (admin: true, hidden from customers): src/lib/api/admin-referrals.ts
via originGet/originPost -> the global-admin-gated app/admin/aggregate proxy;
ReferralsAdminModule = summary tiles + directory + a 'Run sweep' action.
- Signup capture: src/lib/referrals/claim.ts (stashReferralCode reads ?ref into
localStorage; claimReferralOnce POSTs /v1/referrals/claim once per session per
org after first login), wired into session.tsx beside the welcome grant.
- Wiring: 'referrals' added to CLOUD_V1_HEADS + CLOUD_HEADS (customer proxy) and
ADMIN_V1_HEADS + ADMIN_AGGREGATE_HEADS (admin proxy). Registry repointed to the
real module + an admin entry; dropped the dead docs deep link.
Gates: tsc --noEmit clean; vitest 1838/1838 (+15 referrals api/logic/claim); next
build ok. Version 8.4.107 -> 8.4.108.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The /plans "Upgrade to Pro" page showed a bare "Not authorized": PlansApi.pricing() hit GET /v1/pricing, but on the live console ingress /v1/* is routed straight to the gateway-fronted cloud binary (cookie-only, no bearer) and 401s, so no tiers rendered and nobody could subscribe to Pro.
Fix: read the money-truth catalog through the per-tenant billing proxy (GET /billing/v1/plans -> commerce api/billing.ListPlans), the SAME credentialed BFF path every working billing call uses (balance/usage/subscriptions). Map the commerce staticPlan wire shape (bare array, CENTS, slug) to a display Plan (whole dollars), filter to the cloud account tiers (personal/team/enterprise), order the grid, and mark Pro popular. Each card CTA opens the brand billing portal checkout (config.billingUrl#pricing, Square) — a live, non-dead subscribe path matching the portal own CTA.
plans.ts rewritten (endpoint + shape + Plan/PlanLimits types); PlansModule.tsx consumes the new shape with honest loading/empty/error (BackendStateCard); index.ts exports Plan/PlanLimits; plans.test.ts (6) pins endpoint + cents->dollars + Pro popular + filter + order; canonical-paths.test.ts pins PlansApi.plans -> /billing/v1/plans.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The /plans "Upgrade to Pro" page showed a bare "Not authorized": PlansApi.pricing() hit GET /v1/pricing, but on the live console ingress /v1/* is routed straight to the gateway-fronted cloud binary (cookie-only, no bearer) and 401s, so no tiers rendered and nobody could subscribe to Pro.
Fix: read the money-truth catalog through the per-tenant billing proxy (GET /billing/v1/plans -> commerce api/billing.ListPlans), the SAME credentialed BFF path every working billing call uses (balance/usage/subscriptions). Map the commerce staticPlan wire shape (bare array, CENTS, slug) to a display Plan (whole dollars), filter to the cloud account tiers (personal/team/enterprise), order the grid, and mark Pro popular. Each card CTA opens the brand billing portal checkout (config.billingUrl#pricing, Square) — a live, non-dead subscribe path matching the portal own CTA.
plans.ts rewritten (endpoint + shape + Plan/PlanLimits types); PlansModule.tsx consumes the new shape with honest loading/empty/error (BackendStateCard); index.ts exports Plan/PlanLimits; plans.test.ts (6) pins endpoint + cents->dollars + Pro popular + filter + order; canonical-paths.test.ts pins PlansApi.plans -> /billing/v1/plans.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The Models page marked zen5-mini as the "Default" model, but zen5-mini is
PREMIUM — it 402s for a trial / $5-welcome balance, so a new user's first
call to the "default" model fails. The user-facing default must be a model
that always works on the trial tier.
zen5-flash is the non-premium Zen flagship (per the live catalog `premium`
flag; the Playground's default-model.test.ts documents the ground truth:
"zen5 / zen5-mini / zen5-max premium; zen5-flash / zen5-coder not").
- families.ts: DEFAULT_MODEL 'zen5-mini' -> 'zen5-flash' (the ONE constant
the Models page "Default" pill and the Zen-family sort read).
- ChatConversation.tsx: preselect DEFAULT_MODEL (case-insensitive) before
falling back to first-Zen, so Chat agrees with the Models page and never
seeds a premium default for a trial user.
- families.test.ts: retitle + pin DEFAULT_MODEL === 'zen5-flash'.
Playground already picked the non-premium Zen flagship at runtime
(defaultModelId), so Chat, Playground, and the Models page now all agree on
the same trial-safe default. tsc clean; vitest 1808/1808.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The Models page marked zen5-mini as the "Default" model, but zen5-mini is
PREMIUM — it 402s for a trial / $5-welcome balance, so a new user's first
call to the "default" model fails. The user-facing default must be a model
that always works on the trial tier.
zen5-flash is the non-premium Zen flagship (per the live catalog `premium`
flag; the Playground's default-model.test.ts documents the ground truth:
"zen5 / zen5-mini / zen5-max premium; zen5-flash / zen5-coder not").
- families.ts: DEFAULT_MODEL 'zen5-mini' -> 'zen5-flash' (the ONE constant
the Models page "Default" pill and the Zen-family sort read).
- ChatConversation.tsx: preselect DEFAULT_MODEL (case-insensitive) before
falling back to first-Zen, so Chat agrees with the Models page and never
seeds a premium default for a trial user.
- families.test.ts: retitle + pin DEFAULT_MODEL === 'zen5-flash'.
Playground already picked the non-premium Zen flagship at runtime
(defaultModelId), so Chat, Playground, and the Models page now all agree on
the same trial-safe default. tsc clean; vitest 1808/1808.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Pre-launch QA sweep found two honest-state defects on the LIVE console.
1) Chat "(empty response)" — the gateway can answer a 200 whose BODY is a plain
casibase error envelope (NOT SSE): `{status:"error", msg:"the token count:
[4198] exceeds the model: [minimax-m2.5]'s maximum token count: [4096]"}`.
That body carries no `data:` events, so `readChatStream` yielded no content and
resolved to '' -> the chat rendered a silent "(empty response)" bubble that hid
the real reason. New pure `streamErrorMessage` (stream.ts) detects a non-SSE
JSON error envelope (casibase `{status,msg}` AND OpenAI `{error:{message}}`),
and `readChatStream` throws it when the stream produced no content -> honest
error card. A real completion object (`choices`) is never treated as an error,
and a genuinely-empty successful stream still resolves to '' (no false error).
(The premium-model 402 path was already handled by the non-ok branch.)
2) Grants "$0.00" banner — the `POST /v1/admin/grants` create response does not
echo the requested amount/source, so the success banner read "Granted $0.00"
even though the ledger recorded the real amount. `AdminGrantsApi.create` now
backfills the REQUESTED amount/source/org when the response omits them, so the
returned row (which the banner renders) is self-consistent whatever the shape.
Tests: +stream.test.ts (6), +admin-grants.test.ts (3), +4 ai.test.ts regression
cases (200-envelope casibase + OpenAI, blank-stream no-false-error).
Gates: tsc --noEmit clean; vitest 1808/1808; next build OK.
NOTE (separate backend release): the ROOT cause of the chat failure is a GATEWAY
model-config bug — every routed model reports max_tokens=4096 (zen-agent->
minimax-m2.5, zen5->deepseek-v4-pro), far below their real context windows, so the
console's grounded system prompt (~4190 tok) exceeds it. This console fix makes the
error HONEST; the gateway 4096 cap must be raised on api.hanzo.ai.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Pre-launch QA sweep found two honest-state defects on the LIVE console.
1) Chat "(empty response)" — the gateway can answer a 200 whose BODY is a plain
casibase error envelope (NOT SSE): `{status:"error", msg:"the token count:
[4198] exceeds the model: [minimax-m2.5]'s maximum token count: [4096]"}`.
That body carries no `data:` events, so `readChatStream` yielded no content and
resolved to '' -> the chat rendered a silent "(empty response)" bubble that hid
the real reason. New pure `streamErrorMessage` (stream.ts) detects a non-SSE
JSON error envelope (casibase `{status,msg}` AND OpenAI `{error:{message}}`),
and `readChatStream` throws it when the stream produced no content -> honest
error card. A real completion object (`choices`) is never treated as an error,
and a genuinely-empty successful stream still resolves to '' (no false error).
(The premium-model 402 path was already handled by the non-ok branch.)
2) Grants "$0.00" banner — the `POST /v1/admin/grants` create response does not
echo the requested amount/source, so the success banner read "Granted $0.00"
even though the ledger recorded the real amount. `AdminGrantsApi.create` now
backfills the REQUESTED amount/source/org when the response omits them, so the
returned row (which the banner renders) is self-consistent whatever the shape.
Tests: +stream.test.ts (6), +admin-grants.test.ts (3), +4 ai.test.ts regression
cases (200-envelope casibase + OpenAI, blank-stream no-false-error).
Gates: tsc --noEmit clean; vitest 1808/1808; next build OK.
NOTE (separate backend release): the ROOT cause of the chat failure is a GATEWAY
model-config bug — every routed model reports max_tokens=4096 (zen-agent->
minimax-m2.5, zen5->deepseek-v4-pro), far below their real context windows, so the
console's grounded system prompt (~4190 tok) exceeds it. This console fix makes the
error HONEST; the gateway 4096 cap must be raised on api.hanzo.ai.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The bearer authenticated but Casbin denied /mfa/setup/* — IAM's authz filter
derives the request object by JSON-parsing the POST body, so a form-encoded body
yields an empty object and the self-access grant (objOwner==subOwner) never
matched. Fix: send the MFA params as the QUERY STRING with an empty body and
always include the pinned owner/name, so the filter reads them (its len(body)==0
branch) and grants self-access — the same rule that lets get-users?owner=<me>
through. No IAM change.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The bearer authenticated but Casbin denied /mfa/setup/* — IAM's authz filter
derives the request object by JSON-parsing the POST body, so a form-encoded body
yields an empty object and the self-access grant (objOwner==subOwner) never
matched. Fix: send the MFA params as the QUERY STRING with an empty body and
always include the pinned owner/name, so the filter reads them (its len(body)==0
branch) and grants self-access — the same rule that lets get-users?owner=<me>
through. No IAM change.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
MFA self-enrollment was unreachable: the console delegated 2FA to hanzo.id's
account page, but the custom hanzo.id login worker never establishes a Casdoor
account session, so a worker-authenticated user hits 'Unauthorized operation' on
the MFA setup endpoints (verified live). Fix: enroll 2FA IN the console.
- app/console/mfa/[action] BFF forwards initiate/verify/enable/disable to IAM as
the caller's OWN user bearer (adminBearer(resolveUser)), owner/name PINNED
server-side — a user can only manage their own 2FA. IAM's authz filter accepts
the bearer and Casbin authorizes self-service MFA.
- lib/api/mfa.ts client + ProfileModule Security tab: real 'Set up authenticator
app' flow (initiate → show TOTP secret/otpauth URI → enter 6-digit code →
verify → enable), an On/Off state, and Turn-off. Password change still deep-links
to IAM. MFA is enforced at login already (checkMfaEnable→NextMfa; SignInForm
hands off to the hosted challenge).
tsc + 1785 vitest green; next build ✓ (/console/mfa/[action] registered).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
MFA self-enrollment was unreachable: the console delegated 2FA to hanzo.id's
account page, but the custom hanzo.id login worker never establishes a Casdoor
account session, so a worker-authenticated user hits 'Unauthorized operation' on
the MFA setup endpoints (verified live). Fix: enroll 2FA IN the console.
- app/console/mfa/[action] BFF forwards initiate/verify/enable/disable to IAM as
the caller's OWN user bearer (adminBearer(resolveUser)), owner/name PINNED
server-side — a user can only manage their own 2FA. IAM's authz filter accepts
the bearer and Casbin authorizes self-service MFA.
- lib/api/mfa.ts client + ProfileModule Security tab: real 'Set up authenticator
app' flow (initiate → show TOTP secret/otpauth URI → enter 6-digit code →
verify → enable), an On/Off state, and Turn-off. Password change still deep-links
to IAM. MFA is enforced at login already (checkMfaEnable→NextMfa; SignInForm
hands off to the hosted challenge).
tsc + 1785 vitest green; next build ✓ (/console/mfa/[action] registered).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Live verification caught it: /console/accept ran update-user and it updated
displayName + signupApplication, but the password stayed EMPTY. Root cause:
casibase update-user with no `columns` param uses a default column set that
EXCLUDES password, and it only auto-appends the password columns when `columns`
is non-empty — so UpdateUserPassword hashed the value in memory but never wrote
the column (credential silently stayed unset). Fix: activateMember pins explicit
`columns=password,password_salt,password_type[,display_name,signup_application]`
so the hashed password + salt + type are persisted. Also mask the accept-page
password field (secureTextEntry+type=password, the @hanzo/gui workaround).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Live verification caught it: /console/accept ran update-user and it updated
displayName + signupApplication, but the password stayed EMPTY. Root cause:
casibase update-user with no `columns` param uses a default column set that
EXCLUDES password, and it only auto-appends the password columns when `columns`
is non-empty — so UpdateUserPassword hashed the value in memory but never wrote
the column (credential silently stayed unset). Fix: activateMember pins explicit
`columns=password,password_salt,password_type[,display_name,signup_application]`
so the hashed password + salt + type are persisted. Also mask the accept-page
password field (secureTextEntry+type=password, the @hanzo/gui workaround).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The Team invite created a passwordless zombie member with NO way to sign in
(email/OTP delivery is unwired; IAM send-invitation is a stub). This closes the
loop with a console-native, no-email, no-new-IAM-capability accept flow:
- POST /console/invite-link mints a sealed (AES-256-GCM, HKDF of the confidential
client secret), 14-day, org-admin-gated accept token for a pending member.
- Public /accept page + GET/POST /console/accept lets the invitee set their OWN
password (IAM hashes via update-user's passwordChanged path — never plaintext),
then sign in and land in their org with the assigned role. Single-use for
activation (refused once the member has a credential).
- InviteDialog surfaces the shareable link (honest 'email delivery isn't wired'
copy); roster shows Pending vs Active + a 2FA badge, and a 'Copy invite link'
row action for pending members (activates the pre-existing zombies too).
- identity.ts gains getMember/memberHasPassword/activateMember (same confidential
client as createUser/moveUserToOrg). +8 invite-token tests. tsc + 1785 vitest
green; next build ✓ (/accept, /console/accept, /console/invite-link registered).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Team invite created a passwordless zombie member with NO way to sign in
(email/OTP delivery is unwired; IAM send-invitation is a stub). This closes the
loop with a console-native, no-email, no-new-IAM-capability accept flow:
- POST /console/invite-link mints a sealed (AES-256-GCM, HKDF of the confidential
client secret), 14-day, org-admin-gated accept token for a pending member.
- Public /accept page + GET/POST /console/accept lets the invitee set their OWN
password (IAM hashes via update-user's passwordChanged path — never plaintext),
then sign in and land in their org with the assigned role. Single-use for
activation (refused once the member has a credential).
- InviteDialog surfaces the shareable link (honest 'email delivery isn't wired'
copy); roster shows Pending vs Active + a 2FA badge, and a 'Copy invite link'
row action for pending members (activates the pre-existing zombies too).
- identity.ts gains getMember/memberHasPassword/activateMember (same confidential
client as createUser/moveUserToOrg). +8 invite-token tests. tsc + 1785 vitest
green; next build ✓ (/accept, /console/accept, /console/invite-link registered).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
* feat(onboarding): grant $5 welcome credit on signup + self-heal on load
FIX 1 (onboarding paywall): a new signup lands at a $0 balance and 402s on
first chat because the idempotent commerce welcome-grant is never invoked.
- identity.ts: new server-only grantWelcomeCredit(org,user) — mints a user-bound
bearer and POSTs the idempotent `/v1/billing/me/welcome` behind the gateway
(X-Org-Id scoped). Best-effort, never throws, never blocks signup.
- signup route: award the grant after createUser (idempotent; failure is harmless).
- BillingApi.welcome() + claimWelcomeGrantOnce(owner): self-heal on first
authenticated load (social-login + pre-existing $0 users), once per browser
session via the per-tenant /billing/v1/me/welcome proxy.
- wired into SessionProvider.applyAccount; unit tests for the guard.
* fix(playground): default to a NON-PREMIUM chat model so a $5 trial user gets 200
FIX 3: the auto-default preferred the bare Zen flagship (zen5), which is PREMIUM —
a cold, trial-funded user 402d ('premium model requiring a paid balance') on the
very first Run.
- thread `premium` through the catalog: RichModel.premium → CatalogEntry (spread)
→ ModelOption.premium (useModels normalizer, from the /v1/models `premium` bool).
- default-model: choose from the NON-PREMIUM pool first (fallback to full only when
every model is premium), and prefer the general-purpose tier (zen5-flash) over a
specialized one (zen5-coder) via a generalist tiebreak.
- tests prove the default is provably non-premium (skips zen5/zen5-max/featured-premium).
* fix(onboarding): signup grant via commerce service-token grant-starter (not user token)
A fresh personal-org user cannot be resolved by the confidential hanzo-console
client (it lives in org 'hanzo'), so issue-user-token/password-grant fails. Use the
DESIGNED trusted-service path instead: commerce POST /v1/billing/grant-starter with
the COMMERCE SERVICE TOKEN the console already holds (billing-proxy).
- billing-proxy: export commerceBaseUrl() + commerceServiceToken() (DRY, one address).
- billing-grant.ts: grantWelcomeCredit(orgSlug) POSTs grant-starter (subject == the
personal-org slug, X-Org-Id + user body, trigger tag for idempotent dedupe).
Best-effort, swallows failures. identity.ts reverted (no cross-org token mint).
- signup route calls it after createUser; unit tests cover posting + swallow.
* feat(admin): per-row Grant quick action + Trial/Prepaid source selector
FIX 2: staff grant-credit gets a per-ROW quick action and a source bucket.
- admin-cockpit grantCredit accepts source?: 'trial'|'prepaid' (GrantSource type).
- CustomersModule: extract ONE reusable GrantCreditPanel (amount + source toggle,
default Trial since comps are non-cash + reason) used by BOTH the detail view and
a new per-row 'Grant' action (stopPropagation so it doesn't open the detail).
Notice banner shows the granted bucket.
* feat(admin): Grants ledger + Projects boards (global-admin, admin.hanzo.ai)
DELIVERABLE 4 — two new admin-only catalog entries under Observe (admin:true,
hidden from customers), honest loading/empty/403 states, no fabricated rows.
- Grants (id fleet-grants): fleet credit-grant ledger + issuance. admin-grants.ts
routes GET/POST /v1/admin/grants through the /admin/aggregate BFF (grants head added
to ADMIN_AGGREGATE_HEADS + next.config ADMIN_V1_HEADS, following the compute pattern).
Table (org, amount, Trial/Prepaid source badge, reason, staff actor, date) + a New
grant form (org + amount + source toggle + reason → POST), refresh after issue.
- Projects (id fleet-projects): READ-ONLY cross-org deploy board. admin-projects.ts is a
pure lens over the EXISTING global PlatformApi.apps() inventory (per neo — NO
/v1/admin/projects endpoint): org, app, health, cluster, live URL, drift; drill by org
via a filter. groupByOrg + toProjectRow unit-tested.
- registry: both entries (aliased FleetGrantsModule/FleetProjectsModule to avoid the
customer 'projects' collision).
* feat(billing): show trial + prepaid balance buckets distinctly
DELIVERABLE 5 — surface the new commerce bucket split ($5 non-cash trial vs real
prepaid money) everywhere the org balance shows, reusing the ONE live-balance source.
- wallet.ts CloudBalance: add optional trialGranted/trialBalance/creditsGranted/
creditsRemaining/prepaidBalance/prepaidAvailable (legacy build omits them → degrade
to the combined total, never fabricated).
- live-balance.ts: trialCents/prepaidCents + balanceSplitLabel ('$5.00 trial + $X.XX
credits'), null when neither bucket is reported. Unit-tested.
- SidebarWallet / WalletModule / BillingCredits render the split under the total.
* release(console): v8.4.102 — onboarding welcome-grant + admin Grants/Projects + trial/prepaid balance
---------
Co-authored-by: hanzo-dev <dev@hanzo.ai>
* feat(onboarding): grant $5 welcome credit on signup + self-heal on load
FIX 1 (onboarding paywall): a new signup lands at a $0 balance and 402s on
first chat because the idempotent commerce welcome-grant is never invoked.
- identity.ts: new server-only grantWelcomeCredit(org,user) — mints a user-bound
bearer and POSTs the idempotent `/v1/billing/me/welcome` behind the gateway
(X-Org-Id scoped). Best-effort, never throws, never blocks signup.
- signup route: award the grant after createUser (idempotent; failure is harmless).
- BillingApi.welcome() + claimWelcomeGrantOnce(owner): self-heal on first
authenticated load (social-login + pre-existing $0 users), once per browser
session via the per-tenant /billing/v1/me/welcome proxy.
- wired into SessionProvider.applyAccount; unit tests for the guard.
* fix(playground): default to a NON-PREMIUM chat model so a $5 trial user gets 200
FIX 3: the auto-default preferred the bare Zen flagship (zen5), which is PREMIUM —
a cold, trial-funded user 402d ('premium model requiring a paid balance') on the
very first Run.
- thread `premium` through the catalog: RichModel.premium → CatalogEntry (spread)
→ ModelOption.premium (useModels normalizer, from the /v1/models `premium` bool).
- default-model: choose from the NON-PREMIUM pool first (fallback to full only when
every model is premium), and prefer the general-purpose tier (zen5-flash) over a
specialized one (zen5-coder) via a generalist tiebreak.
- tests prove the default is provably non-premium (skips zen5/zen5-max/featured-premium).
* fix(onboarding): signup grant via commerce service-token grant-starter (not user token)
A fresh personal-org user cannot be resolved by the confidential hanzo-console
client (it lives in org 'hanzo'), so issue-user-token/password-grant fails. Use the
DESIGNED trusted-service path instead: commerce POST /v1/billing/grant-starter with
the COMMERCE SERVICE TOKEN the console already holds (billing-proxy).
- billing-proxy: export commerceBaseUrl() + commerceServiceToken() (DRY, one address).
- billing-grant.ts: grantWelcomeCredit(orgSlug) POSTs grant-starter (subject == the
personal-org slug, X-Org-Id + user body, trigger tag for idempotent dedupe).
Best-effort, swallows failures. identity.ts reverted (no cross-org token mint).
- signup route calls it after createUser; unit tests cover posting + swallow.
* feat(admin): per-row Grant quick action + Trial/Prepaid source selector
FIX 2: staff grant-credit gets a per-ROW quick action and a source bucket.
- admin-cockpit grantCredit accepts source?: 'trial'|'prepaid' (GrantSource type).
- CustomersModule: extract ONE reusable GrantCreditPanel (amount + source toggle,
default Trial since comps are non-cash + reason) used by BOTH the detail view and
a new per-row 'Grant' action (stopPropagation so it doesn't open the detail).
Notice banner shows the granted bucket.
* feat(admin): Grants ledger + Projects boards (global-admin, admin.hanzo.ai)
DELIVERABLE 4 — two new admin-only catalog entries under Observe (admin:true,
hidden from customers), honest loading/empty/403 states, no fabricated rows.
- Grants (id fleet-grants): fleet credit-grant ledger + issuance. admin-grants.ts
routes GET/POST /v1/admin/grants through the /admin/aggregate BFF (grants head added
to ADMIN_AGGREGATE_HEADS + next.config ADMIN_V1_HEADS, following the compute pattern).
Table (org, amount, Trial/Prepaid source badge, reason, staff actor, date) + a New
grant form (org + amount + source toggle + reason → POST), refresh after issue.
- Projects (id fleet-projects): READ-ONLY cross-org deploy board. admin-projects.ts is a
pure lens over the EXISTING global PlatformApi.apps() inventory (per neo — NO
/v1/admin/projects endpoint): org, app, health, cluster, live URL, drift; drill by org
via a filter. groupByOrg + toProjectRow unit-tested.
- registry: both entries (aliased FleetGrantsModule/FleetProjectsModule to avoid the
customer 'projects' collision).
* feat(billing): show trial + prepaid balance buckets distinctly
DELIVERABLE 5 — surface the new commerce bucket split ($5 non-cash trial vs real
prepaid money) everywhere the org balance shows, reusing the ONE live-balance source.
- wallet.ts CloudBalance: add optional trialGranted/trialBalance/creditsGranted/
creditsRemaining/prepaidBalance/prepaidAvailable (legacy build omits them → degrade
to the combined total, never fabricated).
- live-balance.ts: trialCents/prepaidCents + balanceSplitLabel ('$5.00 trial + $X.XX
credits'), null when neither bucket is reported. Unit-tested.
- SidebarWallet / WalletModule / BillingCredits render the split under the total.
* release(console): v8.4.102 — onboarding welcome-grant + admin Grants/Projects + trial/prepaid balance
---------
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Make the org's compute fleet easy to SEE and USE in one place, and open cluster
self-service to paying customers (drop the admin gate). Per-org customer console;
admin.hanzo.ai's cross-org compute boards stay separate.
- Kubernetes module is now the UNIFIED FLEET cockpit: managed + attached BYO
clusters (GET /v1/clusters, MERGED, with kind + nvidia/amd GPU inventory + node
count + status) and dialed-in BYO machines (GET /v1/machines, provider="byo"),
in one honest view — loading / empty "no compute yet" / error BackendStateCard,
never a fabricated row. Supersedes the old capacity-card design.
- Enable BYO cluster attach (replaces the dropped "import cluster" stub): a Register-
cluster form (name + kubeconfig paste/upload + default toggle) -> POST /v1/clusters,
with honest error paths (503 KMS-not-configured, 422 unreachable-kubeconfig,
402 billing, 400 invalid). PlatformApi.attachCluster/detachCluster added; the
Cluster type gains nvidiaGpu/amdGpu (matching the cloud clusterView).
- Show the three connect options so it is easy to DO: BYO cluster (the attach form),
BYO box (copy-paste `hanzo gpu connect` + desktop auto-link note), and BYOC cloud
account (honest "connect your AWS/GCP/Azure/DO account - coming").
- Un-hide the `clusters` + `kubernetes` catalog entries (drop admin:true) so a paying
customer reaches cluster self-service from the unified console.
- visor.ts VisorMachine gains os (provider already present) so BYO boxes are labeled.
- Pure kubernetes/logic.ts (summarizeFleet / byoBoxes / clusterNodeTotal /
describeAttachError / CONNECT_SNIPPET) + 16 vitest tests.
Verify: npm run typecheck (0 errors), npm test (1752 pass), next build (green, 15/15).
Make the org's compute fleet easy to SEE and USE in one place, and open cluster
self-service to paying customers (drop the admin gate). Per-org customer console;
admin.hanzo.ai's cross-org compute boards stay separate.
- Kubernetes module is now the UNIFIED FLEET cockpit: managed + attached BYO
clusters (GET /v1/clusters, MERGED, with kind + nvidia/amd GPU inventory + node
count + status) and dialed-in BYO machines (GET /v1/machines, provider="byo"),
in one honest view — loading / empty "no compute yet" / error BackendStateCard,
never a fabricated row. Supersedes the old capacity-card design.
- Enable BYO cluster attach (replaces the dropped "import cluster" stub): a Register-
cluster form (name + kubeconfig paste/upload + default toggle) -> POST /v1/clusters,
with honest error paths (503 KMS-not-configured, 422 unreachable-kubeconfig,
402 billing, 400 invalid). PlatformApi.attachCluster/detachCluster added; the
Cluster type gains nvidiaGpu/amdGpu (matching the cloud clusterView).
- Show the three connect options so it is easy to DO: BYO cluster (the attach form),
BYO box (copy-paste `hanzo gpu connect` + desktop auto-link note), and BYOC cloud
account (honest "connect your AWS/GCP/Azure/DO account - coming").
- Un-hide the `clusters` + `kubernetes` catalog entries (drop admin:true) so a paying
customer reaches cluster self-service from the unified console.
- visor.ts VisorMachine gains os (provider already present) so BYO boxes are labeled.
- Pure kubernetes/logic.ts (summarizeFleet / byoBoxes / clusterNodeTotal /
describeAttachError / CONNECT_SNIPPET) + 16 vitest tests.
Verify: npm run typecheck (0 errors), npm test (1752 pass), next build (green, 15/15).
Add a first-class "Git" catalog entry linking to the self-hosted Gitea
code host at git.hanzo.ai, following the SAME external-launch pattern as
Automation (auto.hanzo.ai): kind:'external' + href, brands:['hanzo'] so
the URL never leaks onto a Lux/Zoo console. One CatalogEntry surfaces it
in the Dev nav, the catalog overview, the app launcher, ⌘K, favorites,
and the discover interstitial — no shell/route edits (the registry is the
single source of nav + routing truth). GitBranch icon (already imported);
no docs/repo field (git.hanzo.ai IS the code host, no docs.hanzo.ai page).
tsc --noEmit clean; vitest 1692/1692; next build ✓.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add a first-class "Git" catalog entry linking to the self-hosted Gitea
code host at git.hanzo.ai, following the SAME external-launch pattern as
Automation (auto.hanzo.ai): kind:'external' + href, brands:['hanzo'] so
the URL never leaks onto a Lux/Zoo console. One CatalogEntry surfaces it
in the Dev nav, the catalog overview, the app launcher, ⌘K, favorites,
and the discover interstitial — no shell/route edits (the registry is the
single source of nav + routing truth). GitBranch icon (already imported);
no docs/repo field (git.hanzo.ai IS the code host, no docs.hanzo.ai page).
tsc --noEmit clean; vitest 1692/1692; next build ✓.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Org-brand sidebar header + Hanzo-H fallback, Material elevation/paper tokens,
alphabetical + selected-first product order (order.ts, DRY + tested), mobile nav
drawer opens LEFT and auto-closes on product tap, opacity-only hz-menu-in for
floating-ui anchored menus (SelectMenu/ComboBox) so they stay anchored.
@hanzo/gui shorthands only; no Svelte/Radix.
Org-brand sidebar header + Hanzo-H fallback, Material elevation/paper tokens,
alphabetical + selected-first product order (order.ts, DRY + tested), mobile nav
drawer opens LEFT and auto-closes on product tap, opacity-only hz-menu-in for
floating-ui anchored menus (SelectMenu/ComboBox) so they stay anchored.
@hanzo/gui shorthands only; no Svelte/Radix.
Live mobile audit of console.hanzo.ai (v8.4.98) at 375/768/1440. Stacking is
solid (zero horizontal overflow anywhere) and all core mobile interactions work
(hamburger nav drawer, ⌘K palette, search, org/scope switchers, app launcher,
chat composer). Two clear defects fixed:
1. Topbar search truncated to "S…" on phones. Two flex:1 siblings — the search
box and the right-side spacer — halved the box's width below lg, and the ⌘K
chip (meaningless without a keyboard) ate the rest, so the placeholder was
unreadable. The spacer now only flexes at lg+ (below lg the box fills the row)
and the ⌘K hint is hidden below lg. Desktop layout is unchanged.
2. FloatingChat bubble overlapped the composer's send control on /chat and
/playground (it's fixed bottom-right on every page). It is now suppressed on
those two surfaces — which already have their own full composer — while
staying one tap away everywhere else and still openable programmatically.
Gates: tsc --noEmit clean · vitest 1664/1664 · next build ✓.
Live mobile audit of console.hanzo.ai (v8.4.98) at 375/768/1440. Stacking is
solid (zero horizontal overflow anywhere) and all core mobile interactions work
(hamburger nav drawer, ⌘K palette, search, org/scope switchers, app launcher,
chat composer). Two clear defects fixed:
1. Topbar search truncated to "S…" on phones. Two flex:1 siblings — the search
box and the right-side spacer — halved the box's width below lg, and the ⌘K
chip (meaningless without a keyboard) ate the rest, so the placeholder was
unreadable. The spacer now only flexes at lg+ (below lg the box fills the row)
and the ⌘K hint is hidden below lg. Desktop layout is unchanged.
2. FloatingChat bubble overlapped the composer's send control on /chat and
/playground (it's fixed bottom-right on every page). It is now suppressed on
those two surfaces — which already have their own full composer — while
staying one tap away everywhere else and still openable programmatically.
Gates: tsc --noEmit clean · vitest 1664/1664 · next build ✓.
The console home now shows the org's full resource picture in one place: top-line
stat tiles (apps running, GPUs online split cloud vs BYO, nodes) plus three
at-a-glance sections (Apps, GPUs, Nodes) that deep-link to the product owning each.
Read-only aggregation over three REAL per-org sources — apps (/v1/platform), GPUs
(/v1/gpus), machines (/v1/machines) — loaded independently, so a slow/denied/unrouted
source degrades to its own "not reporting" line and never blanks the board.
- normalizeMachine (visor) + normalizeGpu (compute) now pass `provider` through so a
bring-your-own node/GPU (a DGX Spark GB10) badges BYO distinctly from Hanzo Cloud;
normalizeGpu also tolerates a BYO GPU's string `memory` ("128GB"/"80 GiB"/"131072MB")
→ numeric VRAM. Additive, defensive; DOKS rows unchanged.
- ResourceOverview + pure resource-logic (provider kind, online cloud/BYO split), both
unit-tested; PlatformAppsApi.listAllApps() de-dups the org-wide app read (DRY).
Full BYO render lands with the cloud redeploy that unions Visor DOKS inventory with
BYO fleet workers into /v1/machines + /v1/gpus.
The console home now shows the org's full resource picture in one place: top-line
stat tiles (apps running, GPUs online split cloud vs BYO, nodes) plus three
at-a-glance sections (Apps, GPUs, Nodes) that deep-link to the product owning each.
Read-only aggregation over three REAL per-org sources — apps (/v1/platform), GPUs
(/v1/gpus), machines (/v1/machines) — loaded independently, so a slow/denied/unrouted
source degrades to its own "not reporting" line and never blanks the board.
- normalizeMachine (visor) + normalizeGpu (compute) now pass `provider` through so a
bring-your-own node/GPU (a DGX Spark GB10) badges BYO distinctly from Hanzo Cloud;
normalizeGpu also tolerates a BYO GPU's string `memory` ("128GB"/"80 GiB"/"131072MB")
→ numeric VRAM. Additive, defensive; DOKS rows unchanged.
- ResourceOverview + pure resource-logic (provider kind, online cloud/BYO split), both
unit-tested; PlatformAppsApi.listAllApps() de-dups the org-wide app read (DRY).
Full BYO render lands with the cloud redeploy that unions Visor DOKS inventory with
BYO fleet workers into /v1/machines + /v1/gpus.
floating-ui positions SelectMenu/ComboBox Popover.Content with an inline
transform; a transform-based entrance (hz-pop-in) overrides that inline value
for the animation duration and detaches the menu from its trigger. New
opacity-only hz-menu-in keeps the anchor exact; hz-pop-in stays for centered
Dialog surfaces. Reduced-motion snaps.
floating-ui positions SelectMenu/ComboBox Popover.Content with an inline
transform; a transform-based entrance (hz-pop-in) overrides that inline value
for the animation duration and detaches the menu from its trigger. New
opacity-only hz-menu-in keeps the anchor exact; hz-pop-in stays for centered
Dialog surfaces. Reduced-motion snaps.
Left-side drawer matches the top-left hamburger (account drawer stays right);
SidebarNav.openProduct calls onNavigate() so the off-canvas nav dismisses on a
product tap (desktop passes a no-op — stays open).
Left-side drawer matches the top-left hamburger (account drawer stays right);
SidebarNav.openProduct calls onNavigate() so the off-canvas nav dismisses on a
product tap (desktop passes a no-op — stays open).
Monochrome node cards (@hanzo/gui tokens) with kind icon + live status dot
(running pulses; reduced-motion disables it), pan/zoom + fitView, minimap, controls.
One org-scoped read (PaasApi apps + ProvisioningApi data); polls via usePoll; honest
loading/empty/error states. Click a node -> side panel with details + deep links to
the product page and its /metrics observability. Canvas is client-only (dynamic
ssr:false); colorMode + edge hues track the real app theme.
Monochrome node cards (@hanzo/gui tokens) with kind icon + live status dot
(running pulses; reduced-motion disables it), pan/zoom + fitView, minimap, controls.
One org-scoped read (PaasApi apps + ProvisioningApi data); polls via usePoll; honest
loading/empty/error states. Click a node -> side panel with details + deep links to
the product page and its /metrics observability. Canvas is client-only (dynamic
ssr:false); colorMode + edge hues track the real app theme.
Honest edges only: domain->app from app.domains; app->resource only where an
unmasked env value names the resource host/name (secrets are masked, so a drawn
edge is a real link, never invented). Deterministic 3-tier layered layout. 18 unit
tests cover status normalization, node/edge derivation, layout determinism, summary.
Honest edges only: domain->app from app.domains; app->resource only where an
unmasked env value names the resource host/name (secrets are masked, so a drawn
edge is a real link, never invented). Deterministic 3-tier layered layout. 18 unit
tests cover status normalization, node/edge derivation, layout determinism, summary.
Close out the "port remaining old-console views" task. The old console
(hanzoai/console) and console2 have fully converged: /home/z/work/hanzo/console
is byte-identical to origin/main (v8.4.97), so nothing in "old" is missing from
"new". The only components not reachable from the product registry were an early
wave of views, since superseded and never re-wired:
- iam/{UserEditView,AppEditView,OrgView,logic} (from wip savepoint f28d796)
-> superseded by AdminModule's IamModule (Orgs/Users/Roles, full CRUD) +
AuditModule, and per-org IAM apps managed live in tenants/TenantDetail.
- applications/{ApplicationListView,ApplicationEditView,logic} (from cf5d309)
-> superseded by ApplicationsModule -> PaasApplications (the real deployed-apps
surface over /v1/platform).
- lib/api/applications.ts (ApplicationApi) + the `Application` type
-> the legacy casibase-era /v1/*-application(s) client, its only consumers were
the deleted views; the modern paas.ts client is the one and only way now.
One way, no dead code. Gates: tsc 0 errors, vitest 130 files / 1664 tests green,
next build compiled.
Close out the "port remaining old-console views" task. The old console
(hanzoai/console) and console2 have fully converged: /home/z/work/hanzo/console
is byte-identical to origin/main (v8.4.97), so nothing in "old" is missing from
"new". The only components not reachable from the product registry were an early
wave of views, since superseded and never re-wired:
- iam/{UserEditView,AppEditView,OrgView,logic} (from wip savepoint 5a2573d)
-> superseded by AdminModule's IamModule (Orgs/Users/Roles, full CRUD) +
AuditModule, and per-org IAM apps managed live in tenants/TenantDetail.
- applications/{ApplicationListView,ApplicationEditView,logic} (from cf5d309)
-> superseded by ApplicationsModule -> PaasApplications (the real deployed-apps
surface over /v1/platform).
- lib/api/applications.ts (ApplicationApi) + the `Application` type
-> the legacy casibase-era /v1/*-application(s) client, its only consumers were
the deleted views; the modern paas.ts client is the one and only way now.
One way, no dead code. Gates: tsc 0 errors, vitest 130 files / 1664 tests green,
next build compiled.
RED reviewed the v8.4-billing-surface proxy (src/lib/server/billing-proxy.ts).
All five findings fixed by REUSING the already-hardened bearer-proxy.ts pattern
(pathIsClean + normalized-URL re-validation + streaming), not a new guard.
RED-1 [SHIP-BLOCKER] encoded path-traversal out of /v1/billing/. isSafeSegment
rejected literal `..`/`/` but not `%2e%2e`/`.%2e`/`%2E%2E`/double-encoded
`%252e%252e` (Next single-decodes -> `%2e%2e`), which undici normalizes to a
real `..` and pops out of /v1/billing/ to the whole commerce API with the
service Bearer. FIX: replace isSafeSegment with the shared pathIsClean
(rejects empty, `.`/`..`, ANY `%XX`, matrix-param `;`) on the raw path, AND
re-validate the NORMALIZED URL.pathname still begins with /v1/billing/ AFTER
undici resolves it. Either check fails -> 400 with NO upstream fetch. Applies
to GET/POST/DELETE (the check is before the body read + fetch).
RED-2 [MED] content-type confusion / missing nosniff. Upstream CT/Content-
Disposition were forwarded verbatim, no nosniff. FIX: set
X-Content-Type-Options: nosniff on EVERY billing response; the binary branch
FORCES Content-Disposition: attachment with a SANITIZED filename (CR/LF/`;`/
quote/path chars stripped, never the upstream's verbatim); an active textual
type (text/html/xhtml/svg/js from a compromised/MITM'd plaintext hop) is
served inert as text/plain so window.open can never execute it at our origin.
RED-3 [MED] unbounded buffering -> memory DoS. res.arrayBuffer()/res.text()
buffered the whole body. FIX: STREAM res.body through on BOTH branches (matches
bearer-proxy); a null-body status (204 detach) still carries null.
RED-4 [LOW] 502 leaked the raw upstream exception (internal host). FIX: generic
"Billing upstream is unavailable." to the client; console.error the detail
server-side (mirrors bearer-proxy).
RED-5 [LOW] regression-net gap. New tests: encoded-traversal `['%2e%2e',...]`,
`['.%2e',...]`, `['%2E%2E',...]`, double-encoded, `%2f`, `..;`, and any
`%`-containing segment -> 400 with NO fetch (all verbs); binary-branch PDF
carries nosniff + attachment; nosniff on JSON; text/html+svg served inert;
generic 502 with no leak; pure helpers.
CONFIRMED-SAFE properties untouched: CSRF-first ordering, resolveUser/401,
COMMERCE_TOKEN/501, scopedBillingSearch/Body subject pinning, X-Org-Id from the
validated session.
tsc --noEmit: 0 errors. vitest: billing-proxy 28/28 (was 11), billing suites
114/114, full 1698/1698.
RED reviewed the v8.4-billing-surface proxy (src/lib/server/billing-proxy.ts).
All five findings fixed by REUSING the already-hardened bearer-proxy.ts pattern
(pathIsClean + normalized-URL re-validation + streaming), not a new guard.
RED-1 [SHIP-BLOCKER] encoded path-traversal out of /v1/billing/. isSafeSegment
rejected literal `..`/`/` but not `%2e%2e`/`.%2e`/`%2E%2E`/double-encoded
`%252e%252e` (Next single-decodes -> `%2e%2e`), which undici normalizes to a
real `..` and pops out of /v1/billing/ to the whole commerce API with the
service Bearer. FIX: replace isSafeSegment with the shared pathIsClean
(rejects empty, `.`/`..`, ANY `%XX`, matrix-param `;`) on the raw path, AND
re-validate the NORMALIZED URL.pathname still begins with /v1/billing/ AFTER
undici resolves it. Either check fails -> 400 with NO upstream fetch. Applies
to GET/POST/DELETE (the check is before the body read + fetch).
RED-2 [MED] content-type confusion / missing nosniff. Upstream CT/Content-
Disposition were forwarded verbatim, no nosniff. FIX: set
X-Content-Type-Options: nosniff on EVERY billing response; the binary branch
FORCES Content-Disposition: attachment with a SANITIZED filename (CR/LF/`;`/
quote/path chars stripped, never the upstream's verbatim); an active textual
type (text/html/xhtml/svg/js from a compromised/MITM'd plaintext hop) is
served inert as text/plain so window.open can never execute it at our origin.
RED-3 [MED] unbounded buffering -> memory DoS. res.arrayBuffer()/res.text()
buffered the whole body. FIX: STREAM res.body through on BOTH branches (matches
bearer-proxy); a null-body status (204 detach) still carries null.
RED-4 [LOW] 502 leaked the raw upstream exception (internal host). FIX: generic
"Billing upstream is unavailable." to the client; console.error the detail
server-side (mirrors bearer-proxy).
RED-5 [LOW] regression-net gap. New tests: encoded-traversal `['%2e%2e',...]`,
`['.%2e',...]`, `['%2E%2E',...]`, double-encoded, `%2f`, `..;`, and any
`%`-containing segment -> 400 with NO fetch (all verbs); binary-branch PDF
carries nosniff + attachment; nosniff on JSON; text/html+svg served inert;
generic 502 with no leak; pure helpers.
CONFIRMED-SAFE properties untouched: CSRF-first ordering, resolveUser/401,
COMMERCE_TOKEN/501, scopedBillingSearch/Body subject pinning, X-Org-Id from the
validated session.
tsc --noEmit: 0 errors. vitest: billing-proxy 28/28 (was 11), billing suites
114/114, full 1698/1698.
Complete the Billing Center's three external-portal punts over the ONE per-tenant
/billing/v1/* commerce proxy — PCI posture unchanged, tenant scoping server-side.
- Payment Methods: in-console Add (Square iframe -> nonce -> POST payment-methods;
RAW PAN never leaves the browser) + per-row Remove (confirm -> DELETE
payment-methods/:id). Set-default fail-secure-skipped (customer-id-in-path not
proxy-scopable).
- Subscriptions: in-console Cancel (at-period-end vs now -> POST :id/cancel) +
Reactivate (POST :id/reactivate); row reflects cancelAtPeriodEnd/canceledAt.
- Invoices: Download builds the PDF URL from the invoice id via the same-origin
proxy. Proxy extracted to tested lib/server/billing-proxy.ts: adds DELETE +
binary passthrough (application/pdf streamed as raw bytes with Content-Type/
Content-Disposition, no text() mangling), all auth/CSRF/scoping intact.
- DRY: useSquareCard hook shared by BillingCredits + PaymentMethodsModule.
- New BillingApi: createPaymentMethod/removePaymentMethod/cancelSubscription/
reactivateSubscription. tsc clean; vitest 1689/1689 (+22 billing/proxy tests).
Complete the Billing Center's three external-portal punts over the ONE per-tenant
/billing/v1/* commerce proxy — PCI posture unchanged, tenant scoping server-side.
- Payment Methods: in-console Add (Square iframe -> nonce -> POST payment-methods;
RAW PAN never leaves the browser) + per-row Remove (confirm -> DELETE
payment-methods/:id). Set-default fail-secure-skipped (customer-id-in-path not
proxy-scopable).
- Subscriptions: in-console Cancel (at-period-end vs now -> POST :id/cancel) +
Reactivate (POST :id/reactivate); row reflects cancelAtPeriodEnd/canceledAt.
- Invoices: Download builds the PDF URL from the invoice id via the same-origin
proxy. Proxy extracted to tested lib/server/billing-proxy.ts: adds DELETE +
binary passthrough (application/pdf streamed as raw bytes with Content-Type/
Content-Disposition, no text() mangling), all auth/CSRF/scoping intact.
- DRY: useSquareCard hook shared by BillingCredits + PaymentMethodsModule.
- New BillingApi: createPaymentMethod/removePaymentMethod/cancelSubscription/
reactivateSubscription. tsc clean; vitest 1689/1689 (+22 billing/proxy tests).
Two live capstone defects when billing/balance|usage 502s during a deploy roll:
1) Billing tiles hung on Loading forever (Projected had no error branch; no load timeout). 2) balance was refetched hundreds of times (636 in one session) with no backoff.
live-balance poll: fixed 30s setInterval -> self-scheduling timer with exponential backoff (base 2s, doubling, cap 60s) + equal-jitter, gated so automatic mount/focus/poll wait out the window; resets to 30s on first success; a user Refresh / balance-affecting action bypasses the breaker. Bounded call count during an outage instead of a storm. Public API + snapshot shape preserved.
Billing tiles: pure tileView() + useTimedOut() bound the spinner — on fetch error OR after a ~10s timeout the Cloud credit / Spend / Projected / Daily-spend tiles render the honest -/Unavailable fallback (the Dashboard/Machines pattern), never an infinite spinner. Happy path unchanged.
Author: Hanzo Dev <dev@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Two live capstone defects when billing/balance|usage 502s during a deploy roll:
1) Billing tiles hung on Loading forever (Projected had no error branch; no load timeout). 2) balance was refetched hundreds of times (636 in one session) with no backoff.
live-balance poll: fixed 30s setInterval -> self-scheduling timer with exponential backoff (base 2s, doubling, cap 60s) + equal-jitter, gated so automatic mount/focus/poll wait out the window; resets to 30s on first success; a user Refresh / balance-affecting action bypasses the breaker. Bounded call count during an outage instead of a storm. Public API + snapshot shape preserved.
Billing tiles: pure tileView() + useTimedOut() bound the spinner — on fetch error OR after a ~10s timeout the Cloud credit / Spend / Projected / Daily-spend tiles render the honest -/Unavailable fallback (the Dashboard/Machines pattern), never an infinite spinner. Happy path unchanged.
Author: Hanzo Dev <dev@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Defense-in-depth on the Status-board endpoint redaction: also drop hosts
on internal TLDs (.internal/.intranet/.corp/.lan/.home/.cluster, and any
*.cluster.* path) in addition to .svc/loopback/RFC1918/IPv6. The audit's
real leak (*.svc:port, localhost, 127.0.0.1) was already covered; this
closes the theoretical case of a scrape label on a private DNS zone. One
extra alternation + test cases. Version → 8.4.96.
Defense-in-depth on the Status-board endpoint redaction: also drop hosts
on internal TLDs (.internal/.intranet/.corp/.lan/.home/.cluster, and any
*.cluster.* path) in addition to .svc/loopback/RFC1918/IPv6. The audit's
real leak (*.svc:port, localhost, 127.0.0.1) was already covered; this
closes the theoretical case of a scrape label on a private DNS zone. One
extra alternation + test cases. Version → 8.4.96.
Harden the casibase store-admin allow-list added in v8.4.94: admit ONLY
the heads the console actually calls — get-stores/get-store (read),
add-store/update-store/delete-store/refresh-store-vectors (mutate).
Drop get-global-stores (a cross-tenant read the console never invokes —
StoreApi.listGlobal has zero callers) and get-store-names (unused) from
CLOUD_HEADS, so the /cloud proxy is not a wider tunnel than needed. Org
is always the Bearer owner server-side, but not exposing an unused
cross-tenant-read head is defense in depth. Pinned with a proxy-allow
test (positive + the two least-privilege negatives). Version → 8.4.95.
Harden the casibase store-admin allow-list added in v8.4.94: admit ONLY
the heads the console actually calls — get-stores/get-store (read),
add-store/update-store/delete-store/refresh-store-vectors (mutate).
Drop get-global-stores (a cross-tenant read the console never invokes —
StoreApi.listGlobal has zero callers) and get-store-names (unused) from
CLOUD_HEADS, so the /cloud proxy is not a wider tunnel than needed. Org
is always the Bearer owner server-side, but not exposing an unused
cross-tenant-read head is defense in depth. Pinned with a proxy-allow
test (positive + the two least-privilege negatives). Version → 8.4.95.
Make every console page real: no "coming soon", no dead/disabled stub
buttons, no false "not enabled"/"session expired". Ship live.
Zero coming-soon guarantee (structural):
- Remove ProductStatus 'soon' entirely (0/148 catalog entries used it) →
type now forbids a coming-soon product. Drops the SOON badge, Preview
label, and waitlist path from DashboardShell / AppLauncher /
CategoryOverview; delete the orphaned WaitlistForm (zero importers).
- Providers: remove the BYO-Weights tab (redundant with Custom Models,
only carrier of a future promise) + drop the soon badge from HonestTab.
- Wallet: HUSD "coming soon" → honest present-state + a real "Add credit
on Billing" (Square) action.
- GPUs: remove every dead `disabled hint=` stub (Add GPUs / Import
cluster / Connect DO/AWS / per-row kebab / Run diagnostics); the real
path is "Connect a provider" → /secrets (KMS credentials). KEEP the
real Prev/Next pagination (a boundary-disabled control, not a stub).
- Reword to present-state: gpus ledger caption, ProductSubpageStub,
platform/state 'unavailable', tasks/detail Logs/Signals/Queries,
OrgIntegrations (dead branch removed), hanzo-evm HUSD error strings.
- Finetuning: KEEP the registry entry (its module is already wired to the
LIVE /v1/train/* via TrainApi), DELETE the orphaned dead finetuning/
subdir + api/finetune.ts (hit the 404 /v1/finetune/*, zero importers).
Audit routing fixes (same class as the Vector /cloud fix — the live
ingress does NOT run next.config /v1/* rewrites, so bare-/v1/ clients
that rely on them fail; address the proxy EXPLICITLY):
- Commerce store clients → /commerce proxy (commerceProxyV1Url) instead
of rewrite-dependent /v1/commerce/* → fixes the 6 store pages'
FALSE "Not enabled for your account".
- Embeddings stores + ingest + cloud-usage ledger → /cloud bearer proxy
(new cloudGet/cloudPost) + allow-list the casibase heads (get-stores,
get-store, …, docs, get-files, get-cloud-usages) in proxy-allow →
fixes the FALSE "session expired" 401 on Collections.
- Status board: redact internal scrape instance (host:port) at the
source (redactInstance) so visor.hanzo.svc:19000 / localhost:8428 /
127.0.0.1:8429 never render to a customer.
Tests: tsc clean; vitest 1636 green (new redactInstance suite + a
match-core anti-drift guard that a declared subpage must be routed or it
stubs; canonical-paths pins commerce→/commerce, stores→/cloud); next
build green. package.json 8.4.89 → 8.4.90.
Make every console page real: no "coming soon", no dead/disabled stub
buttons, no false "not enabled"/"session expired". Ship live.
Zero coming-soon guarantee (structural):
- Remove ProductStatus 'soon' entirely (0/148 catalog entries used it) →
type now forbids a coming-soon product. Drops the SOON badge, Preview
label, and waitlist path from DashboardShell / AppLauncher /
CategoryOverview; delete the orphaned WaitlistForm (zero importers).
- Providers: remove the BYO-Weights tab (redundant with Custom Models,
only carrier of a future promise) + drop the soon badge from HonestTab.
- Wallet: HUSD "coming soon" → honest present-state + a real "Add credit
on Billing" (Square) action.
- GPUs: remove every dead `disabled hint=` stub (Add GPUs / Import
cluster / Connect DO/AWS / per-row kebab / Run diagnostics); the real
path is "Connect a provider" → /secrets (KMS credentials). KEEP the
real Prev/Next pagination (a boundary-disabled control, not a stub).
- Reword to present-state: gpus ledger caption, ProductSubpageStub,
platform/state 'unavailable', tasks/detail Logs/Signals/Queries,
OrgIntegrations (dead branch removed), hanzo-evm HUSD error strings.
- Finetuning: KEEP the registry entry (its module is already wired to the
LIVE /v1/train/* via TrainApi), DELETE the orphaned dead finetuning/
subdir + api/finetune.ts (hit the 404 /v1/finetune/*, zero importers).
Audit routing fixes (same class as the Vector /cloud fix — the live
ingress does NOT run next.config /v1/* rewrites, so bare-/v1/ clients
that rely on them fail; address the proxy EXPLICITLY):
- Commerce store clients → /commerce proxy (commerceProxyV1Url) instead
of rewrite-dependent /v1/commerce/* → fixes the 6 store pages'
FALSE "Not enabled for your account".
- Embeddings stores + ingest + cloud-usage ledger → /cloud bearer proxy
(new cloudGet/cloudPost) + allow-list the casibase heads (get-stores,
get-store, …, docs, get-files, get-cloud-usages) in proxy-allow →
fixes the FALSE "session expired" 401 on Collections.
- Status board: redact internal scrape instance (host:port) at the
source (redactInstance) so visor.hanzo.svc:19000 / localhost:8428 /
127.0.0.1:8429 never render to a customer.
Tests: tsc clean; vitest 1636 green (new redactInstance suite + a
match-core anti-drift guard that a declared subpage must be routed or it
stubs; canonical-paths pins commerce→/commerce, stores→/cloud); next
build green. package.json 8.4.89 → 8.4.90.
Two changes on this branch, both green (tsc clean, 1645 vitest pass, next build success):
1. feat: native Automations product tile — adds the `automations` catalog entry
pointing at the native /v1/automations engine (HIP-0106, repo hanzoai/cloud,
700+ connectors), brand-scoped to hanzo. Backend (cloud#113) already merged;
surface live at auto.hanzo.ai/automations (verified 200). Distinct from the
existing standalone `auto` tile (repo hanzoai/auto). Follow-up: consider
relabeling to disambiguate the two automation tiles in the grid.
2. fix(auth): admin-host silent SSO for the admin-console client — on admin.<brand>
the signin page now auto-initiates admin-console PKCE OAuth against the live
guard SSO session (no second manual login resolving the wrong identity).
Loop-guarded; tenant hosts (e.g. console.hanzo.ai) UNCHANGED — still SignInForm.
Two changes on this branch, both green (tsc clean, 1645 vitest pass, next build success):
1. feat: native Automations product tile — adds the `automations` catalog entry
pointing at the native /v1/automations engine (HIP-0106, repo hanzoai/cloud,
700+ connectors), brand-scoped to hanzo. Backend (cloud#113) already merged;
surface live at auto.hanzo.ai/automations (verified 200). Distinct from the
existing standalone `auto` tile (repo hanzoai/auto). Follow-up: consider
relabeling to disambiguate the two automation tiles in the grid.
2. fix(auth): admin-host silent SSO for the admin-console client — on admin.<brand>
the signin page now auto-initiates admin-console PKCE OAuth against the live
guard SSO session (no second manual login resolving the wrong identity).
Loop-guarded; tenant hosts (e.g. console.hanzo.ai) UNCHANGED — still SignInForm.
Header-scoped cloud heads (gpus, clusters, functions, platform/paas, vpcs,
load-balancers, builds, releases, pipelines, environments, indexers, oracles,
authz, embeddings search) 403 on the live ingress via bare /v1 (gateway strips
X-Org-Id, no minted bearer) — verified live. Route them through the /cloud
user-bearer proxy (cloudProxyV1Url), same class-fix as framework/s3/machines
(v8.4.70). Turns ~15 silently-broken modules into real per-org data.
Also: inline docs links -> canonical /docs/<slug> (edge/storage/machines/gpus/
agents/inference->gateway/crawl/functions/kms; embeddings landing kit); ChatView
carries the real chat owner (2-seg /chat/:owner/:name) instead of hardcoded
'admin' (non-admin orgs could not open saved chats); SearchModule derives its
base path so Crawl tabs/CTA stay under /crawl.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Header-scoped cloud heads (gpus, clusters, functions, platform/paas, vpcs,
load-balancers, builds, releases, pipelines, environments, indexers, oracles,
authz, embeddings search) 403 on the live ingress via bare /v1 (gateway strips
X-Org-Id, no minted bearer) — verified live. Route them through the /cloud
user-bearer proxy (cloudProxyV1Url), same class-fix as framework/s3/machines
(v8.4.70). Turns ~15 silently-broken modules into real per-org data.
Also: inline docs links -> canonical /docs/<slug> (edge/storage/machines/gpus/
agents/inference->gateway/crawl/functions/kms; embeddings landing kit); ChatView
carries the real chat owner (2-seg /chat/:owner/:name) instead of hardcoded
'admin' (non-admin orgs could not open saved chats); SearchModule derives its
base path so Crawl tabs/CTA stay under /crawl.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Resolve a model's brand from its IDENTITY (id/name) first, then provider, so a
gateway-served model tagged provider "hanzo" (qwen3.5-397b, glm-5.2, kimi-k2.6,
minimax-m2.5) shows its true vendor instead of the house block-H. New pure
brandForModel() + model-aware ProviderLogo, wired at every per-model call site
(Marketplace card, Model Catalog detail, Playground picker). Hanzo stays ONLY the
fallback for genuinely-Hanzo/unknown models; Zen (id zen*) keeps the Hanzo mark.
Add canonical self-contained inline SVG vendor marks (no CDN, CSP-safe, theme-aware
white-on-brand-tile): Anthropic sunburst (new), OpenAI blossom knot (replaces the
invented asterisk), Google Gemini spark star (replaces the Gemma gem). Marketplace
card derives logo + vendor label (brandLabel) + house Verified badge from the one
brandForModel result, so a card is never Qwen-logo + Zen-label.
tsc clean; vitest 1667/1667 (+15 brand); marks render-validated headless.
Resolve a model's brand from its IDENTITY (id/name) first, then provider, so a
gateway-served model tagged provider "hanzo" (qwen3.5-397b, glm-5.2, kimi-k2.6,
minimax-m2.5) shows its true vendor instead of the house block-H. New pure
brandForModel() + model-aware ProviderLogo, wired at every per-model call site
(Marketplace card, Model Catalog detail, Playground picker). Hanzo stays ONLY the
fallback for genuinely-Hanzo/unknown models; Zen (id zen*) keeps the Hanzo mark.
Add canonical self-contained inline SVG vendor marks (no CDN, CSP-safe, theme-aware
white-on-brand-tile): Anthropic sunburst (new), OpenAI blossom knot (replaces the
invented asterisk), Google Gemini spark star (replaces the Gemma gem). Marketplace
card derives logo + vendor label (brandLabel) + house Verified badge from the one
brandForModel result, so a card is never Qwen-logo + Zen-label.
tsc clean; vitest 1667/1667 (+15 brand); marks render-validated headless.
Mobile/tablet responsive polish across the console shell + chat + overview. All
five are console2-local app compositions; the shared @hanzo/gui primitives were
already correct (bumping them globally would wreck desktop density).
- Chat composer sticky to the viewport bottom on phones/tablets (.hz-chat-dock),
so it never first-paints below the fold; static in the capped column at lg+.
- Touch targets >=44px (WCAG 2.5.5): nav-drawer rows/controls via .hz-touch-target
(the desktop sidebar is a separate mount and stays dense), the hamburger, and
the chat send button.
- Nav drawer: explicit close X inside the drawer header (right-aligned), always
reachable on a 390px phone (backdrop/Escape still close too).
- Overview KPI grid: responsive columns (1 / md:2 / xl:4) so a 4-card row balances
instead of wrapping 3+1 at tablet widths.
- Chat conversation column capped at ~820px, centered, so it no longer runs
edge-to-edge on ultra-wide displays.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Mobile/tablet responsive polish across the console shell + chat + overview. All
five are console2-local app compositions; the shared @hanzo/gui primitives were
already correct (bumping them globally would wreck desktop density).
- Chat composer sticky to the viewport bottom on phones/tablets (.hz-chat-dock),
so it never first-paints below the fold; static in the capped column at lg+.
- Touch targets >=44px (WCAG 2.5.5): nav-drawer rows/controls via .hz-touch-target
(the desktop sidebar is a separate mount and stays dense), the hamburger, and
the chat send button.
- Nav drawer: explicit close X inside the drawer header (right-aligned), always
reachable on a 390px phone (backdrop/Escape still close too).
- Overview KPI grid: responsive columns (1 / md:2 / xl:4) so a 4-card row balances
instead of wrapping 3+1 at tablet widths.
- Chat conversation column capped at ~820px, centered, so it no longer runs
edge-to-edge on ultra-wide displays.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
P0: hard-navigating/refreshing any sub-route (e.g. /machines) threw
"Application error: a client-side exception has occurred" and stayed dead
until a full reload. Root cause: on a rolling deploy the just-served HTML
references a content-hashed chunk that the replica/CDN the browser hits
does not have; the Next origin serves that missing chunk URL as HTTP 200
app-shell HTML (Content-Type text/html), so the browser parses HTML as JS
into "Unexpected token <" -> ChunkLoadError. The failure lands ABOVE every
segment boundary during first hydration, and there was NO app/global-error,
so Next fell to its built-in dead-ended fallback (no router -> a later nav
back to / stays dead).
Fix:
- app/global-error.tsx (NEW): the missing OUTERMOST boundary. Replaces Next's
dead default; on a chunk skew self-heals with ONE reload per window, else a
self-contained recovery card (owns its own html/body).
- ChunkGuard: add CAPTURE-phase resource-error detection so a raw chunk 404
on initial deep-load is caught before webpack's loader rejects; route it
through the shared once-per-window guard (no fast reload loop).
- boundary-logic: export CHUNK_RELOAD_AT_KEY — ONE loop-breaker shared by
global-error, the dashboard segment, ProductErrorBoundary and ChunkGuard
(DRY; removes two duplicated magic strings).
- generateBuildId pinned to the commit (src/config/build-id.mjs): SOURCE_COMMIT
build-arg -> git HEAD -> package version, so every replica of a release shares
ONE build id (default minted a random id per build). Dockerfile + CI pass the
SHA as a build arg (alpine has no git binary).
Gates: tsc --noEmit clean, 1659 unit tests pass (7 new for resolveBuildId),
next build green. Curl-proof: deep-load /machines and /training serve 200, and
all 24 referenced chunks (incl global-error and the slug page) resolve 200 JS;
.next/BUILD_ID now equals git HEAD sha.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
P0: hard-navigating/refreshing any sub-route (e.g. /machines) threw
"Application error: a client-side exception has occurred" and stayed dead
until a full reload. Root cause: on a rolling deploy the just-served HTML
references a content-hashed chunk that the replica/CDN the browser hits
does not have; the Next origin serves that missing chunk URL as HTTP 200
app-shell HTML (Content-Type text/html), so the browser parses HTML as JS
into "Unexpected token <" -> ChunkLoadError. The failure lands ABOVE every
segment boundary during first hydration, and there was NO app/global-error,
so Next fell to its built-in dead-ended fallback (no router -> a later nav
back to / stays dead).
Fix:
- app/global-error.tsx (NEW): the missing OUTERMOST boundary. Replaces Next's
dead default; on a chunk skew self-heals with ONE reload per window, else a
self-contained recovery card (owns its own html/body).
- ChunkGuard: add CAPTURE-phase resource-error detection so a raw chunk 404
on initial deep-load is caught before webpack's loader rejects; route it
through the shared once-per-window guard (no fast reload loop).
- boundary-logic: export CHUNK_RELOAD_AT_KEY — ONE loop-breaker shared by
global-error, the dashboard segment, ProductErrorBoundary and ChunkGuard
(DRY; removes two duplicated magic strings).
- generateBuildId pinned to the commit (src/config/build-id.mjs): SOURCE_COMMIT
build-arg -> git HEAD -> package version, so every replica of a release shares
ONE build id (default minted a random id per build). Dockerfile + CI pass the
SHA as a build arg (alpine has no git binary).
Gates: tsc --noEmit clean, 1659 unit tests pass (7 new for resolveBuildId),
next build green. Curl-proof: deep-load /machines and /training serve 200, and
all 24 referenced chunks (incl global-error and the slug page) resolve 200 JS;
.next/BUILD_ID now equals git HEAD sha.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
* feat(o11y): reusable per-product ProductObservability panel on every product overview
One DRY <ProductObservability service=/> panel (RED metrics + recent logs +
recent traces) over the existing ApmApi (/cloud/v1/o11y query_range, the ZAP-fed
datastore), filtered to each product's OTel service.name via o11yServiceFor.
Rendered at the bottom of the shared NativeOverview so every product surfaces its
own live signals. Honest states: loading, o11y RuntimeNotice, connected-empty,
and a managed note when a product has no backing service.
* feat(o11y): admin.hanzo.ai global Fleet Observability board (global-admin only)
Cross-org fleet o11y god view reading /v1/admin/o11y (the server-gated aggregate
I built in cloud): fleet KPIs (requests/tokens/cost/errors/p95-p99/log volume/
active orgs/services/traces), usage + log-volume timeseries, and top orgs/models/
services leaderboards — all tenants aggregated from the ONE datastore.
- AdminO11yApi.global(range) via originGet('admin/o11y') → the console-origin
admin-aggregate proxy (getAdminGate, fail-closed 403 for non-global-admin).
- 'o11y' added to ADMIN_AGGREGATE_HEADS + ADMIN_V1_HEADS (same gated path as
compute/finance — no new proxy/trust boundary).
- Defensive normalizer (snake+camel tolerant, garbage → honest zeros/empty).
- Registry entry 'fleet-o11y' (Observe, admin:true — hidden from customers);
client OperatorAccessRequired gate mirrors the server gate.
- Tests: normalizer (real payload/snake-case/garbage/NaN) + allowAdminSurface
admits o11y. Version 8.4.88 -> 8.4.89.
---------
Co-authored-by: hanzo-dev <dev@hanzo.ai>
* feat(o11y): reusable per-product ProductObservability panel on every product overview
One DRY <ProductObservability service=/> panel (RED metrics + recent logs +
recent traces) over the existing ApmApi (/cloud/v1/o11y query_range, the ZAP-fed
datastore), filtered to each product's OTel service.name via o11yServiceFor.
Rendered at the bottom of the shared NativeOverview so every product surfaces its
own live signals. Honest states: loading, o11y RuntimeNotice, connected-empty,
and a managed note when a product has no backing service.
* feat(o11y): admin.hanzo.ai global Fleet Observability board (global-admin only)
Cross-org fleet o11y god view reading /v1/admin/o11y (the server-gated aggregate
I built in cloud): fleet KPIs (requests/tokens/cost/errors/p95-p99/log volume/
active orgs/services/traces), usage + log-volume timeseries, and top orgs/models/
services leaderboards — all tenants aggregated from the ONE datastore.
- AdminO11yApi.global(range) via originGet('admin/o11y') → the console-origin
admin-aggregate proxy (getAdminGate, fail-closed 403 for non-global-admin).
- 'o11y' added to ADMIN_AGGREGATE_HEADS + ADMIN_V1_HEADS (same gated path as
compute/finance — no new proxy/trust boundary).
- Defensive normalizer (snake+camel tolerant, garbage → honest zeros/empty).
- Registry entry 'fleet-o11y' (Observe, admin:true — hidden from customers);
client OperatorAccessRequired gate mirrors the server gate.
- Tests: normalizer (real payload/snake-case/garbage/NaN) + allowAdminSurface
admits o11y. Version 8.4.88 -> 8.4.89.
---------
Co-authored-by: hanzo-dev <dev@hanzo.ai>
The Finetuning + ML Pipelines pages showed 'Not enabled for your account' for a
signed-in customer, and Organization-Settings API keys couldn't be listed/minted.
Both are real money-path cracks — verified live as Dave (org maxpower).
ROOT CAUSE (proven live, NOT the iss theory):
- /training proxy forwarded the raw session COOKIE to cloud-api /v1/train/*, which
authorizes on a validated JWT principal => 403 'no validated principal'. With a
Bearer it is 200. (The token iss is already https://hanzo.id — IAM folds the
in-cluster host to originFrontend[0]; cloud-api accepts it. functions/app-platform
already work via the /cloud bearer proxy, so they were not the break.)
- keys.ts called cloud.hanzo.ai/v1/console/keys — a DIFFERENT origin than
console.hanzo.ai => browser CORS 'Failed to fetch' (and cloud-api 501s that
handler anyway).
FIX (surgical, isolation-safe, DRY):
- /training now mints a short-lived user-bound Bearer via adminBearer (the ONE
per-user cache the /cloud proxy uses) and forwards Bearer + X-Org-Id (orgFor pin);
the cookie is dropped upstream. Fails closed (502) if the token can't be minted.
Org stays server-authoritative (token owner claim) — no tenant-isolation change.
- New same-origin app/keys/route.ts uses identity.ts mintUserKey/getUserKey/
revokeUserKey (IAM confidential-client, the WORKING key path); keys.ts addresses
<origin>/keys. CSRF-guarded, honest 501 when unconfigured, secret shown once.
- Bundle the edge-503 hygiene: interpretPlatformError maps 503 -> 'unavailable'
(clean card), so a fail-closed zt backend never leaks ZT_CLIENT_* env to a customer.
tsc clean; vitest green; next build ok (/keys + /training routes registered).
The Finetuning + ML Pipelines pages showed 'Not enabled for your account' for a
signed-in customer, and Organization-Settings API keys couldn't be listed/minted.
Both are real money-path cracks — verified live as Dave (org maxpower).
ROOT CAUSE (proven live, NOT the iss theory):
- /training proxy forwarded the raw session COOKIE to cloud-api /v1/train/*, which
authorizes on a validated JWT principal => 403 'no validated principal'. With a
Bearer it is 200. (The token iss is already https://hanzo.id — IAM folds the
in-cluster host to originFrontend[0]; cloud-api accepts it. functions/app-platform
already work via the /cloud bearer proxy, so they were not the break.)
- keys.ts called cloud.hanzo.ai/v1/console/keys — a DIFFERENT origin than
console.hanzo.ai => browser CORS 'Failed to fetch' (and cloud-api 501s that
handler anyway).
FIX (surgical, isolation-safe, DRY):
- /training now mints a short-lived user-bound Bearer via adminBearer (the ONE
per-user cache the /cloud proxy uses) and forwards Bearer + X-Org-Id (orgFor pin);
the cookie is dropped upstream. Fails closed (502) if the token can't be minted.
Org stays server-authoritative (token owner claim) — no tenant-isolation change.
- New same-origin app/keys/route.ts uses identity.ts mintUserKey/getUserKey/
revokeUserKey (IAM confidential-client, the WORKING key path); keys.ts addresses
<origin>/keys. CSRF-guarded, honest 501 when unconfigured, secret shown once.
- Bundle the edge-503 hygiene: interpretPlatformError maps 503 -> 'unavailable'
(clean card), so a fail-closed zt backend never leaks ZT_CLIENT_* env to a customer.
tsc clean; vitest green; next build ok (/keys + /training routes registered).
Deterministic release from main HEAD (includes the :tab route fix v8.4.86, the
6 dead-Docs-button removals v8.4.87, and #94 route un-blank). Tagged so the build
is immune to the main-push concurrency-cancel war on the contended v8.4.87.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Deterministic release from main HEAD (includes the :tab route fix v8.4.86, the
6 dead-Docs-button removals v8.4.87, and #94 route un-blank). Tagged so the build
is immune to the main-push concurrency-cancel war on the contended v8.4.87.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
* test(console): mocked-network blank audit for every product route + product-content hook
* fix(nav): alias human product slugs (traces/deploy/plans-pricing/wallets/model-catalog/fine-tuning/web-search) → canonical ids
The single biggest source of 'half the pages are blank': a directly-navigated
URL whose slug != the registry id resolved to notfound -> a Next 404 the operator
read as a blank page. The nav/launcher/palette always open the canonical id, so
these 7 aliases exist only to keep a human slug (docs, bookmarks, the CTO e2e
list, a hand-typed URL) from 404ing. One map (SLUG_ALIASES), already applied by
resolveProductView via canonicalSlug. Proven end-to-end by the blank audit
(every alias slug now renders content, 0 notfound).
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
* test(console): mocked-network blank audit for every product route + product-content hook
* fix(nav): alias human product slugs (traces/deploy/plans-pricing/wallets/model-catalog/fine-tuning/web-search) → canonical ids
The single biggest source of 'half the pages are blank': a directly-navigated
URL whose slug != the registry id resolved to notfound -> a Next 404 the operator
read as a blank page. The nav/launcher/palette always open the canonical id, so
these 7 aliases exist only to keep a human slug (docs, bookmarks, the CTO e2e
list, a hand-typed URL) from 404ing. One map (SLUG_ALIASES), already applied by
resolveProductView via canonicalSlug. Proven end-to-end by the blank audit
(every alias slug now renders content, 0 notfound).
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
accessibility, crm, erp, templates, markets, trading set docs: ${DOCS}/<slug>
but those docs.hanzo.ai/docs/<slug> pages don't exist (verified HTTP 404 live) and
have no honest target — a redirect would mislead. Remove the docs: field on those
6 entries; consumers fall back to config.docsUrl (docs root), so no dead deep link.
The docs lane handles the other previously-missing slugs via docs-side redirects.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
accessibility, crm, erp, templates, markets, trading set docs: ${DOCS}/<slug>
but those docs.hanzo.ai/docs/<slug> pages don't exist (verified HTTP 404 live) and
have no honest target — a redirect would mislead. Remove the docs: field on those
6 entries; consumers fall back to config.docsUrl (docs root), so no dead deep link.
The docs lane handles the other previously-missing slugs via docs-side redirects.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
On admin.<brand> the admin guard has already authenticated the operator at the brand
IAM (a live SSO session), yet /signin rendered <SignInForm/> on EVERY host — forcing a
SECOND manual login that resolves the tenant identity (hanzo/z), not the operator
identity (admin/z), which breaks the operator panel.
Now the signin page auto-initiates admin-console OAuth on an admin host (isAdminHost):
startAdminSignin() mints a PKCE verifier, stashes it for the callback, and redirects to
IAM /v1/iam/oauth/authorize for client_id=admin-console in organization=admin — reusing
the guard SSO session and returning to /auth/callback with a code, no extra step. The
callback hands the stashed verifier to completeSignIn, which redeems it via the console
own BFF (PKCE, no secret). Tenant hosts are UNCHANGED — still <SignInForm/>, no verifier,
cloud-backend exchange.
Loop-guarded: fires once, never with a live session, never mid-callback.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
On admin.<brand> the admin guard has already authenticated the operator at the brand
IAM (a live SSO session), yet /signin rendered <SignInForm/> on EVERY host — forcing a
SECOND manual login that resolves the tenant identity (hanzo/z), not the operator
identity (admin/z), which breaks the operator panel.
Now the signin page auto-initiates admin-console OAuth on an admin host (isAdminHost):
startAdminSignin() mints a PKCE verifier, stashes it for the callback, and redirects to
IAM /v1/iam/oauth/authorize for client_id=admin-console in organization=admin — reusing
the guard SSO session and returning to /auth/callback with a code, no extra step. The
callback hands the stashed verifier to completeSignIn, which redeems it via the console
own BFF (PKCE, no secret). Tenant hosts are UNCHANGED — still <SignInForm/>, no verifier,
cloud-backend exchange.
Loop-guarded: fires once, never with a live session, never mid-callback.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The Containers (Pods/Containers/Images/Namespaces/Events), Fine-tuning
(Datasets/Checkpoints/Models), and Tasks (Schedules/Queues/Workers) modules
render their tab bar as REAL sub-routes (go(t.id) -> /<id>/<tab>, reading
params.tab) but their registry entries declared only { path: '' } -- so every
tab 404'd (Tasks/Queues degraded to a stub). Declare the ':tab' route on each so
the tab bar resolves. Tasks keeps its 2-segment ':ns/:wid' detail route
(unambiguous by segment count).
Also fix the API Keys docs button: 'https://docs.hanzo.ai/api' -> the docs site
serves under /docs (a bare docs.hanzo.ai/<slug> 404s), so use
${config.docsUrl}/docs/api (white-labeled).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Containers (Pods/Containers/Images/Namespaces/Events), Fine-tuning
(Datasets/Checkpoints/Models), and Tasks (Schedules/Queues/Workers) modules
render their tab bar as REAL sub-routes (go(t.id) -> /<id>/<tab>, reading
params.tab) but their registry entries declared only { path: '' } -- so every
tab 404'd (Tasks/Queues degraded to a stub). Declare the ':tab' route on each so
the tab bar resolves. Tasks keeps its 2-segment ':ns/:wid' detail route
(unambiguous by segment count).
Also fix the API Keys docs button: 'https://docs.hanzo.ai/api' -> the docs site
serves under /docs (a bare docs.hanzo.ai/<slug> 404s), so use
${config.docsUrl}/docs/api (white-labeled).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The shared per-product sub-page system (Status/Logs/Metrics/Settings — already
routed for all 136 products) is now backed by live o11y, scoped per product by
its OTel service.name via ONE parameterized mechanism (no bespoke per-product
wiring). Reuses the existing ApmApi o11y client + RuntimeNotice + LivingOverview.
- sources.ts: o11yServiceFor(entry) — product -> OTel service.name (repoBase
convention + tiny override), new o11yService field on subpageSourcesFor.
- apm.ts: per-service o11y filtering — listQueryPayload gains optional filters
(back-compat), serviceFilterItem, ApmApi.logs/traceSearch(service?), and
ApmApi.serviceHealth (pickService + serviceHealthOf RED verdict).
- Status: LIVE o11y RED-metrics health band (org-scoped, works for customers) +
deployment state; managed card only when neither reports; never a fake green.
- Logs: live o11y logs filtered to the product's service (replaces the dead
/paas/logs path); RuntimeNotice + honest empty states.
- Metrics: real ledger + live o11y p99 merged into the latency KPI (was stuck
at '—'); latencyP95 -> latencyP99 (honest to the RED metric we have).
Rebased onto origin/main (v8.4.84). tsc clean; vitest 1643/1643 (129 files);
next build 14/14 pages. o11y is LIVE (o11y.hanzo.ai/api/v2/readyz=200).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The shared per-product sub-page system (Status/Logs/Metrics/Settings — already
routed for all 136 products) is now backed by live o11y, scoped per product by
its OTel service.name via ONE parameterized mechanism (no bespoke per-product
wiring). Reuses the existing ApmApi o11y client + RuntimeNotice + LivingOverview.
- sources.ts: o11yServiceFor(entry) — product -> OTel service.name (repoBase
convention + tiny override), new o11yService field on subpageSourcesFor.
- apm.ts: per-service o11y filtering — listQueryPayload gains optional filters
(back-compat), serviceFilterItem, ApmApi.logs/traceSearch(service?), and
ApmApi.serviceHealth (pickService + serviceHealthOf RED verdict).
- Status: LIVE o11y RED-metrics health band (org-scoped, works for customers) +
deployment state; managed card only when neither reports; never a fake green.
- Logs: live o11y logs filtered to the product's service (replaces the dead
/paas/logs path); RuntimeNotice + honest empty states.
- Metrics: real ledger + live o11y p99 merged into the latency KPI (was stuck
at '—'); latencyP95 -> latencyP99 (honest to the RED metric we have).
Rebased onto origin/main (v8.4.84). tsc clean; vitest 1643/1643 (129 files);
next build 14/14 pages. o11y is LIVE (o11y.hanzo.ai/api/v2/readyz=200).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The managed data products (Vector, SQL, KV, Datastore, DocDB, Search) all
drive ProvisioningApi, which addressed a bare /v1/<kind>. On the live console
ingress a bare /v1/* is routed straight to hanzoai/gateway (bypassing Next),
where the provisioning backends authorize on the Bearer owner claim and 403 a
cookie-only call ('X-Org-Id required'). classifyBackend maps that 403 to
'access' -> the FALSE title 'Not enabled for your account' on pages whose data
is actually live and per-org.
Class-fix (same as storage.ts /v1/s3 + framework, v8.4.70): ProvisioningApi now
builds cloudProxyV1Url(kind) -> <origin>/cloud/v1/<kind>. app/cloud/[...path]
mints a short-lived user-bound IAM token from the session and forwards it, so
the org is resolved server-side and the real resources load. All seven data
kinds are already allow-listed in proxy-allow.ts CLOUD_HEADS; the /cloud route
already serves GET/POST/PUT/PATCH/DELETE. One-line-of-intent transport swap.
Genuinely-empty orgs now show the honest 'Create your first ...' empty state,
never 'not enabled'. 'Not enabled' remains only for a true 403 enablement gate.
Tests: pin every ProvisioningApi call to <origin>/cloud/v1/<kind> (never a bare
/v1) in provisioning.test.ts, and move provisioning into the canonical-paths
'proxy exceptions' block (it was wrongly asserted prefix-free, encoding the bug).
tsc + vitest (1620) + next build green.
v8.4.84
The managed data products (Vector, SQL, KV, Datastore, DocDB, Search) all
drive ProvisioningApi, which addressed a bare /v1/<kind>. On the live console
ingress a bare /v1/* is routed straight to hanzoai/gateway (bypassing Next),
where the provisioning backends authorize on the Bearer owner claim and 403 a
cookie-only call ('X-Org-Id required'). classifyBackend maps that 403 to
'access' -> the FALSE title 'Not enabled for your account' on pages whose data
is actually live and per-org.
Class-fix (same as storage.ts /v1/s3 + framework, v8.4.70): ProvisioningApi now
builds cloudProxyV1Url(kind) -> <origin>/cloud/v1/<kind>. app/cloud/[...path]
mints a short-lived user-bound IAM token from the session and forwards it, so
the org is resolved server-side and the real resources load. All seven data
kinds are already allow-listed in proxy-allow.ts CLOUD_HEADS; the /cloud route
already serves GET/POST/PUT/PATCH/DELETE. One-line-of-intent transport swap.
Genuinely-empty orgs now show the honest 'Create your first ...' empty state,
never 'not enabled'. 'Not enabled' remains only for a true 403 enablement gate.
Tests: pin every ProvisioningApi call to <origin>/cloud/v1/<kind> (never a bare
/v1) in provisioning.test.ts, and move provisioning into the canonical-paths
'proxy exceptions' block (it was wrongly asserted prefix-free, encoding the bug).
tsc + vitest (1620) + next build green.
v8.4.84
Video generation is now async (Sora-style): create returns a job id immediately,
the client polls GET /v1/videos/{id} and downloads GET /v1/videos/{id}/content.
The /ai proxy's allow-list was exact-match and only permitted the CREATE path
(v1/videos/generations), so the Playground could reach create but neither poll
nor download — the two dynamic sub-paths 404'd at the proxy.
Add a narrow, anchored pattern (v1/videos/{id} and /{id}/content, conservative
id charset) alongside the exact set. It stays a tight allow-list — anchored to
v1/videos/, create still only the exact path — never a general tunnel; method is
enforced by the backend (GET-only there). Complements hanzoai/ai#68.
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Video generation is now async (Sora-style): create returns a job id immediately,
the client polls GET /v1/videos/{id} and downloads GET /v1/videos/{id}/content.
The /ai proxy's allow-list was exact-match and only permitted the CREATE path
(v1/videos/generations), so the Playground could reach create but neither poll
nor download — the two dynamic sub-paths 404'd at the proxy.
Add a narrow, anchored pattern (v1/videos/{id} and /{id}/content, conservative
id charset) alongside the exact set. It stays a tight allow-list — anchored to
v1/videos/, create still only the exact path — never a general tunnel; method is
enforced by the backend (GET-only there). Complements hanzoai/ai#68.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
* feat(tracker): native @hanzo/gui Tracker module — issues grouped by status
Add a native console Tracker over the real cloud /v1/tracker surface,
proving a native FE renders issue ROWS GROUPED BY STATUS (the thing the
old Huly/Svelte hanzo.team tracker could not do).
- src/lib/api/tracker.ts: TrackerApi client modeled on crm.ts — same
keyless originV1Url + plain-REST helpers; bare-array lists; defensive
pure normalizers; projects + issues CRUD (PATCH updates).
- src/lib/api/client.ts: add restPatch (backend uses PATCH; restRequest
gains 'PATCH') — one-way, minimal.
- src/components/products/TrackerModule.tsx: project list (create +
drill-in) → per-project grouped List (one DataTable section per
status, the proof view) + Board toggle (5 columns, same data);
create/edit issue in a SlideOver with a quick one-click status control;
Linear-grade `c` keyboard shortcut opens create (⌘K stays owned by the
global CommandPalette). Reuses only the local ui/ kit.
- registry.tsx: one Platform catalog entry (id 'tracker', ClipboardList).
- next.config.mjs + proxy-allow.ts: allow-list the `tracker` head in both
(BFF→cloud user-bearer proxy), exactly like `crm`.
typecheck (tsc --noEmit) clean; 1611 unit tests pass.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* chore(release): v8.4.83 — ship native Tracker module
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
* feat(tracker): native @hanzo/gui Tracker module — issues grouped by status
Add a native console Tracker over the real cloud /v1/tracker surface,
proving a native FE renders issue ROWS GROUPED BY STATUS (the thing the
old Huly/Svelte hanzo.team tracker could not do).
- src/lib/api/tracker.ts: TrackerApi client modeled on crm.ts — same
keyless originV1Url + plain-REST helpers; bare-array lists; defensive
pure normalizers; projects + issues CRUD (PATCH updates).
- src/lib/api/client.ts: add restPatch (backend uses PATCH; restRequest
gains 'PATCH') — one-way, minimal.
- src/components/products/TrackerModule.tsx: project list (create +
drill-in) → per-project grouped List (one DataTable section per
status, the proof view) + Board toggle (5 columns, same data);
create/edit issue in a SlideOver with a quick one-click status control;
Linear-grade `c` keyboard shortcut opens create (⌘K stays owned by the
global CommandPalette). Reuses only the local ui/ kit.
- registry.tsx: one Platform catalog entry (id 'tracker', ClipboardList).
- next.config.mjs + proxy-allow.ts: allow-list the `tracker` head in both
(BFF→cloud user-bearer proxy), exactly like `crm`.
typecheck (tsc --noEmit) clean; 1611 unit tests pass.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
* chore(release): v8.4.83 — ship native Tracker module
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
---------
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Fix 1 — per-family model icons (DRY, one map, every catalog surface):
Every model family rendered the same faint mark (the Zen ensō ring on every Zen
row — the biggest family — plus flat letter monograms Q/Me/DS/Mi/G/AI for the
third-party families), so nothing read as a recognizable brand. Added ONE curated
family→mark map (`src/components/ui/brand-marks.ts`, `BRAND_MARK` keyed by the
canonical BrandKey) of our own tasteful, monochrome inline-SVG marks, consumed
ONLY by `ProviderLogo` — so the Models catalog family headers + rows, the
playground ModelPicker rail + rows, Marketplace, Provider admin and Providers
explore all light up for free:
- Zen (house brand) → the bold Hanzo block-H, knocked out of a filled tile —
NEVER an upstream family glyph (brand policy); replaces the faint ensō circle.
- Qwen → origami hexagon · DeepSeek → whale · Meta → infinity · Mistral → block-M
· Google Gemma → cut gem · OpenAI GPT-OSS → six-point knot. (+ xAI/Moonshot/
NVIDIA marks for the broader provider picker.) Each on its brand hue, each
visually distinct; unknown providers keep the honest neutral-initials fallback.
No external logo hotlinks, no trademark files — avatars, `currentColor`,
theme-adaptive. brand.test locks every curated family to its OWN unique mark.
Fix 2 — CPU=credit vs GPU=prepay-card, made obvious:
The behavior was already enforced server-side; this makes the funding source clear
to the customer. New pure `fundingModel(kind,{creditCents,hasCard})` (machines/
logic.ts, unit-tested) is the one source of truth, rendered by a shared, visually
distinct `FundingNote`:
- CPU / non-GPU → GREEN "Launches on your Hanzo credit · $X available · charged
to credits · no card required" (real balance from /v1/billing/balance; empty →
"Add credits"). Shown in the launch drawer AND the Machines overview.
- GPU → YELLOW "Prepay only · charged to your card · 24-hour minimum" (never
credits; no card on file → "Add a payment card & prepay"). Shown in the launch
drawer AND the GPUs overview. Replaces the drawer's redundant no-card block.
Nothing fabricated — the credit figure is the real balance; copy matches what the
server charges.
typecheck clean · vitest 1611 pass (+ funding + brand-mark coverage) · next build ✓
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Fix 1 — per-family model icons (DRY, one map, every catalog surface):
Every model family rendered the same faint mark (the Zen ensō ring on every Zen
row — the biggest family — plus flat letter monograms Q/Me/DS/Mi/G/AI for the
third-party families), so nothing read as a recognizable brand. Added ONE curated
family→mark map (`src/components/ui/brand-marks.ts`, `BRAND_MARK` keyed by the
canonical BrandKey) of our own tasteful, monochrome inline-SVG marks, consumed
ONLY by `ProviderLogo` — so the Models catalog family headers + rows, the
playground ModelPicker rail + rows, Marketplace, Provider admin and Providers
explore all light up for free:
- Zen (house brand) → the bold Hanzo block-H, knocked out of a filled tile —
NEVER an upstream family glyph (brand policy); replaces the faint ensō circle.
- Qwen → origami hexagon · DeepSeek → whale · Meta → infinity · Mistral → block-M
· Google Gemma → cut gem · OpenAI GPT-OSS → six-point knot. (+ xAI/Moonshot/
NVIDIA marks for the broader provider picker.) Each on its brand hue, each
visually distinct; unknown providers keep the honest neutral-initials fallback.
No external logo hotlinks, no trademark files — avatars, `currentColor`,
theme-adaptive. brand.test locks every curated family to its OWN unique mark.
Fix 2 — CPU=credit vs GPU=prepay-card, made obvious:
The behavior was already enforced server-side; this makes the funding source clear
to the customer. New pure `fundingModel(kind,{creditCents,hasCard})` (machines/
logic.ts, unit-tested) is the one source of truth, rendered by a shared, visually
distinct `FundingNote`:
- CPU / non-GPU → GREEN "Launches on your Hanzo credit · $X available · charged
to credits · no card required" (real balance from /v1/billing/balance; empty →
"Add credits"). Shown in the launch drawer AND the Machines overview.
- GPU → YELLOW "Prepay only · charged to your card · 24-hour minimum" (never
credits; no card on file → "Add a payment card & prepay"). Shown in the launch
drawer AND the GPUs overview. Replaces the drawer's redundant no-card block.
Nothing fabricated — the credit figure is the real balance; copy matches what the
server charges.
typecheck clean · vitest 1611 pass (+ funding + brand-mark coverage) · next build ✓
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The admin-aggregate forwards a user bearer minted by issue-user-token for the
reserved-admin operator (admin/z). Its owner=admin + isAdmin=true are correct, but
its aud defaults to the target user's own app (admin-console), which is NOT in
cloud's audience allowlist — so SanitizeIdentity rejects the token, the request
resolves anonymous, and every /v1/admin/* 403s 'global admin required'.
Fix: scope the minted bearer to the brand cloud audience (<brand>-cloud, always in
cloud's BrandAudiences), host-aware, admin path only.
- config.cloudAudience(host) = BRANDS[brand].iamApp (correct even on admin hosts).
- issueUserToken(user, aud?) / adminBearer(user, aud?) cached per (user, audience).
- BearerProxyOpts.audience; admin-aggregate passes cloudAudience(host).
Tenant proxies omit audience → default (target-app) aud, unchanged; confidential
mint client (hanzo-console) and owner semantics untouched. No cloud change.
tsc clean; vitest 1603/1603; next build green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The admin-aggregate forwards a user bearer minted by issue-user-token for the
reserved-admin operator (admin/z). Its owner=admin + isAdmin=true are correct, but
its aud defaults to the target user's own app (admin-console), which is NOT in
cloud's audience allowlist — so SanitizeIdentity rejects the token, the request
resolves anonymous, and every /v1/admin/* 403s 'global admin required'.
Fix: scope the minted bearer to the brand cloud audience (<brand>-cloud, always in
cloud's BrandAudiences), host-aware, admin path only.
- config.cloudAudience(host) = BRANDS[brand].iamApp (correct even on admin hosts).
- issueUserToken(user, aud?) / adminBearer(user, aud?) cached per (user, audience).
- BearerProxyOpts.audience; admin-aggregate passes cloudAudience(host).
Tenant proxies omit audience → default (target-app) aud, unchanged; confidential
mint client (hanzo-console) and owner semantics untouched. No cloud change.
tsc clean; vitest 1603/1603; next build green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The default Overview (and every product overview + o11y usage panel) showed the
"Access required" wall because GET /v1/billing/usage returned 403. Root cause
(proven live as davelorenzini/maxpower): on the console ingress /v1/* is routed to
the gateway-fronted cloud binary, which requires a JWT bearer (AUTH_PUBLIC_PATHS
excludes billing) — a cookie-only browser request has none, so cloud-api's
clients/console/billing.go resolveCaller finds no validated principal and 403s
("sign in to view billing"). Same class proven by /v1/functions -> 403
"X-Org-Id required". The bare /v1/billing/* NEVER reaches the console Next server
(so the next.config /v1/billing -> /billing/v1 rewrite never fires).
The console's OWN per-tenant proxy app/billing/v1/[...path]/route.ts (service token
+ server-pinned org subject) works perfectly: proven live /billing/v1/balance ->
{available:2046235,user:"maxpower"} and /billing/v1/usage -> 287 real ledger rows.
wallet.ts already addresses it directly; billing.ts + aimetrics.ts + SettlementModule
regressed to the bare /v1/billing/* form.
Fix (same class as v8.4.70 framework/s3 -> /cloud/v1): add ONE billingProxyV1Url
helper (client.ts, the billing twin of cloudProxyV1Url) and point every billing
client at /billing/v1/* directly. Kill wallet.ts's duplicate local appUrl (DRY).
canonical-paths.test pins billing into the proxy-exceptions block; aimetrics.test
asserts /billing/v1/usage. Tenant isolation unchanged (proxy still pins the subject
server-side). No cloud/backend change needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The default Overview (and every product overview + o11y usage panel) showed the
"Access required" wall because GET /v1/billing/usage returned 403. Root cause
(proven live as davelorenzini/maxpower): on the console ingress /v1/* is routed to
the gateway-fronted cloud binary, which requires a JWT bearer (AUTH_PUBLIC_PATHS
excludes billing) — a cookie-only browser request has none, so cloud-api's
clients/console/billing.go resolveCaller finds no validated principal and 403s
("sign in to view billing"). Same class proven by /v1/functions -> 403
"X-Org-Id required". The bare /v1/billing/* NEVER reaches the console Next server
(so the next.config /v1/billing -> /billing/v1 rewrite never fires).
The console's OWN per-tenant proxy app/billing/v1/[...path]/route.ts (service token
+ server-pinned org subject) works perfectly: proven live /billing/v1/balance ->
{available:2046235,user:"maxpower"} and /billing/v1/usage -> 287 real ledger rows.
wallet.ts already addresses it directly; billing.ts + aimetrics.ts + SettlementModule
regressed to the bare /v1/billing/* form.
Fix (same class as v8.4.70 framework/s3 -> /cloud/v1): add ONE billingProxyV1Url
helper (client.ts, the billing twin of cloudProxyV1Url) and point every billing
client at /billing/v1/* directly. Kill wallet.ts's duplicate local appUrl (DRY).
canonical-paths.test pins billing into the proxy-exceptions block; aimetrics.test
asserts /billing/v1/usage. Tenant isolation unchanged (proxy still pins the subject
server-side). No cloud/backend change needed.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
One reusable ProductQuickLinks band, wired once in the product catch-all for
every product's Overview (native, living, or bespoke) — never hand-copied per
module. Each card is scoped to THAT product and links to a real destination:
- Billing → Cost Reports pre-filtered to the product's meter
(/billing/reports?product=<tag>; unfiltered for the whole-ledger inference
surfaces). BillingReports reads the ?product deep-link and filters the ledger.
- Usage → the product's own Metrics sub-page (/<id>/metrics), the REAL
/v1/billing/usage ledger scoped by metadata.product.
- Metrics → the same per-product Metrics dashboard.
Figures are REAL (one product-scoped UsageApi.overview read) or honest-empty —
never fabricated, never an Access-required wall; the links always work. The
product→meter decision reuses the ONE metricsScopeFor source (DRY), so Usage for
Models shows model usage, Usage for GPUs shows GPU usage. Suppressed for the
money/account/admin/rollup surfaces. Pure quick-links.ts is unit-tested (11).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
One reusable ProductQuickLinks band, wired once in the product catch-all for
every product's Overview (native, living, or bespoke) — never hand-copied per
module. Each card is scoped to THAT product and links to a real destination:
- Billing → Cost Reports pre-filtered to the product's meter
(/billing/reports?product=<tag>; unfiltered for the whole-ledger inference
surfaces). BillingReports reads the ?product deep-link and filters the ledger.
- Usage → the product's own Metrics sub-page (/<id>/metrics), the REAL
/v1/billing/usage ledger scoped by metadata.product.
- Metrics → the same per-product Metrics dashboard.
Figures are REAL (one product-scoped UsageApi.overview read) or honest-empty —
never fabricated, never an Access-required wall; the links always work. The
product→meter decision reuses the ONE metricsScopeFor source (DRY), so Usage for
Models shows model usage, Usage for GPUs shows GPU usage. Suppressed for the
money/account/admin/rollup surfaces. Pure quick-links.ts is unit-tested (11).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Leg 2 of the admin.hanzo.ai login. The credential login mints the code for the
PUBLIC admin-console app, but the redeem POSTed the console origin /v1/iam/signin,
which the ingress routes to the cloud backend (casibase) — and casibase redeems
with its confidential hanzo-cloud client, so IAM rejected it ("the token is for
wrong application (client_id)") and bounced the operator back to /signin.
The console now redeems the code ITSELF, host-aware: on an admin host iam-login
authorizes with PKCE (S256 codeChallenge in the login body) and completeSignIn
posts {code, codeVerifier} to the new BFF app/auth/signin, which runs
pkceCodeGrant(client_id=admin-console, code_verifier) with NO client secret —
RFC 7636 public-client path (verified in IAM GetAuthorizationCodeToken: empty
secret + matching S256 verifier is admitted; admin-console has the
authorization_code + refresh_token grants). Tenant hosts are unchanged (no
challenge; the cloud backend keeps redeeming with hanzo-cloud).
durableSessionClientId(host) is the ONE host->client decision (admin-console on
admin hosts, else the confidential hanzo-console); /auth/refresh uses it so an
admin session refreshes secretlessly with admin-console. accountOf + applyCookies
extracted to session.ts (one writer for /auth/session|refresh|signin); createPkce
is the one PKCE source. No new secret to provision.
tsc clean; npm test 1578/1578 (+durableSessionClientId/pkceCodeGrant/refresh
host-aware + PKCE S256 correctness); next build green (/auth/signin registered).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Leg 2 of the admin.hanzo.ai login. The credential login mints the code for the
PUBLIC admin-console app, but the redeem POSTed the console origin /v1/iam/signin,
which the ingress routes to the cloud backend (casibase) — and casibase redeems
with its confidential hanzo-cloud client, so IAM rejected it ("the token is for
wrong application (client_id)") and bounced the operator back to /signin.
The console now redeems the code ITSELF, host-aware: on an admin host iam-login
authorizes with PKCE (S256 codeChallenge in the login body) and completeSignIn
posts {code, codeVerifier} to the new BFF app/auth/signin, which runs
pkceCodeGrant(client_id=admin-console, code_verifier) with NO client secret —
RFC 7636 public-client path (verified in IAM GetAuthorizationCodeToken: empty
secret + matching S256 verifier is admitted; admin-console has the
authorization_code + refresh_token grants). Tenant hosts are unchanged (no
challenge; the cloud backend keeps redeeming with hanzo-cloud).
durableSessionClientId(host) is the ONE host->client decision (admin-console on
admin hosts, else the confidential hanzo-console); /auth/refresh uses it so an
admin session refreshes secretlessly with admin-console. accountOf + applyCookies
extracted to session.ts (one writer for /auth/session|refresh|signin); createPkce
is the one PKCE source. No new secret to provision.
tsc clean; npm test 1578/1578 (+durableSessionClientId/pkceCodeGrant/refresh
host-aware + PKCE S256 correctness); next build green (/auth/signin registered).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Problem 1 — GPU catalog unreachable ("Accelerators 0 available to launch").
ROOT CAUSE: the console host ingress routes /v1/* straight to the gateway
(-> cloud-api), BYPASSING Next -- so the next.config /v1/gpu-sizes -> /vm/v1/gpus
rewrite never runs and cloud-api serves NO visor catalog route -> empty catalog.
Same class as the framework/s3 fix (v8.4.70). Proven in-cluster: visor
/v1/{gpus,regions,sizes} = 200 real DO catalog; cloud-api /v1/gpu-sizes 404s.
FIX: new vmProxyBase/vmProxyV1Url (client.ts); VisorApi reads the catalog
(regions/sizes/gpus) through the /vm visor proxy EXPLICITLY and machines/
launch/quote/terminate through the /cloud user-bearer proxy -- never a bare
/v1/*. Regression-pinned in visor.test.ts (fetch-capture) + canonical-paths.test.ts.
Problem 2 — GPU launches bill a REAL card (prepay), never credits.
GPU billing policy surfaced in LaunchDrawer + enforced server-side (cloud-api +
commerce, tracked separately): PREPAY ONLY (card-funded prepaid balance, never
granted credits), CARD REQUIRED (no card on file -> launch BLOCKED with an add-card
CTA -> /billing/credits), 24-HOUR MINIMUM (hourly x 24 charged upfront, shown as the
Quote headline + "charged now" on Launch). Copy changed from "metered to your Hanzo
balance" -> prepay/card/24h-minimum. Card-on-file gate fails CLOSED (a failed
payment-methods read blocks the launch, never a silent credit fallback). CPU
machines unchanged (still metered to the credit balance).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Problem 1 — GPU catalog unreachable ("Accelerators 0 available to launch").
ROOT CAUSE: the console host ingress routes /v1/* straight to the gateway
(-> cloud-api), BYPASSING Next -- so the next.config /v1/gpu-sizes -> /vm/v1/gpus
rewrite never runs and cloud-api serves NO visor catalog route -> empty catalog.
Same class as the framework/s3 fix (v8.4.70). Proven in-cluster: visor
/v1/{gpus,regions,sizes} = 200 real DO catalog; cloud-api /v1/gpu-sizes 404s.
FIX: new vmProxyBase/vmProxyV1Url (client.ts); VisorApi reads the catalog
(regions/sizes/gpus) through the /vm visor proxy EXPLICITLY and machines/
launch/quote/terminate through the /cloud user-bearer proxy -- never a bare
/v1/*. Regression-pinned in visor.test.ts (fetch-capture) + canonical-paths.test.ts.
Problem 2 — GPU launches bill a REAL card (prepay), never credits.
GPU billing policy surfaced in LaunchDrawer + enforced server-side (cloud-api +
commerce, tracked separately): PREPAY ONLY (card-funded prepaid balance, never
granted credits), CARD REQUIRED (no card on file -> launch BLOCKED with an add-card
CTA -> /billing/credits), 24-HOUR MINIMUM (hourly x 24 charged upfront, shown as the
Quote headline + "charged now" on Launch). Copy changed from "metered to your Hanzo
balance" -> prepay/card/24h-minimum. Card-on-file gate fails CLOSED (a failed
payment-methods read blocks the launch, never a silent credit fallback). CPU
machines unchanged (still metered to the credit balance).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The shared list primitive every module renders:
- Loading paints SKELETON ROWS in the real column layout (honest 'loading',
not a centered spinner void).
- Header: quiet Medium ($color10), hairline underline instead of a heavy fill.
- Columns gain `align` + `mono`: numeric/amount/ID columns right-align and
typeset in Geist Mono tabular figures (dashboard-grade, column-aligned data).
- Cells vertically center their content (justify=center); empty state calmer.
- Rows ease their hover fill (.hz-row, 140ms).
StorageModule: timestamps + byte sizes -> mono tabular; actions column ->
align:right + centered (drops the self=stretch flex=1 that floated the trash
icon below the row baseline). No other module used that pattern.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The shared list primitive every module renders:
- Loading paints SKELETON ROWS in the real column layout (honest 'loading',
not a centered spinner void).
- Header: quiet Medium ($color10), hairline underline instead of a heavy fill.
- Columns gain `align` + `mono`: numeric/amount/ID columns right-align and
typeset in Geist Mono tabular figures (dashboard-grade, column-aligned data).
- Cells vertically center their content (justify=center); empty state calmer.
- Rows ease their hover fill (.hz-row, 140ms).
StorageModule: timestamps + byte sizes -> mono tabular; actions column ->
align:right + centered (drops the self=stretch flex=1 that floated the trash
icon below the row baseline). No other module used that pattern.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Basel ships only Book (400) + Medium (500). Every heading/label requested
600-900 was browser-SYNTHESIZED into a smeared faux-bold. One global invariant
(`* { font-synthesis: none }`, wins over Tamagui's runtime reset) makes every
requested heavy weight fall to the real Medium face — crisp, never synthetic.
- globals.css: font-synthesis:none (universal !important + body); add .hz-mono
(Geist Mono + tabular) for dense data/code, keep .hz-tnum for display numerals.
- shared primitives normalized to the Book/Medium system: PageHeader, EmptyState,
Metric (MetricCard/Panel/LegendDot) titles -> 500 with tight tracking.
- LivingOverview tiles: hero KPI / donut / distribution / series numbers -> Basel
Medium + tabular figures (display numerals stay elegant; mono is reserved for
tables/IDs).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Basel ships only Book (400) + Medium (500). Every heading/label requested
600-900 was browser-SYNTHESIZED into a smeared faux-bold. One global invariant
(`* { font-synthesis: none }`, wins over Tamagui's runtime reset) makes every
requested heavy weight fall to the real Medium face — crisp, never synthetic.
- globals.css: font-synthesis:none (universal !important + body); add .hz-mono
(Geist Mono + tabular) for dense data/code, keep .hz-tnum for display numerals.
- shared primitives normalized to the Book/Medium system: PageHeader, EmptyState,
Metric (MetricCard/Panel/LegendDot) titles -> 500 with tight tracking.
- LivingOverview tiles: hero KPI / donut / distribution / series numbers -> Basel
Medium + tabular figures (display numerals stay elegant; mono is reserved for
tables/IDs).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The global-admin surface for launching, branding, domain-binding, and managing
white-label tenants + resold sub-orgs. The MANAGEMENT UI over the platform's
provisioning — tenant/package/domain/brand RECORDS are the single source of truth,
nothing hardcoded as the canonical path; honest-state everywhere (real where a
backend answers, honest not-connected where a platform endpoint isn't bound yet).
- TenantsModule (admin: true, category Platform) + tenants/: tenants list COMPOSED
from IAM orgs (brand) + admin cockpit (plan/wallet/status) + platform clusters;
reseller TREE derived from metadata.parentOrg or (honestly flagged) owner email;
package catalog read from the platform (DATA, seeded from platform-seed/packages.json,
never a hardcoded const); New-tenant create (real IAM org); per-tenant manage
(brand write REAL via IAM org fields, cluster provision REAL, domain list+bind,
IAM apps, package grant, suspend/reactivate REAL).
- BFF: no new proxy — all platform calls ride the existing /paas catch-all (light up
when the platform serves them; honest 404 today). Only server change:
add/update/delete-organization added to the /admin/iam allow-list (global-admin
gated, org-name pinned) so tenant-create + brand-write are REAL.
- Data-driven brand resolver: TenantsApi.brandConfig(host) + TenantBrandConfig
replace the hardcoded BRANDS/HOST_BRANDS map in config.ts (marked deprecated with
the precise migration; not swapped this pass — it's a build-time OAuth boundary).
- Missing platform endpoints flagged for the foundation phase: GET /v1/packages +
package table, POST/DELETE /v1/org/{org}/package/{id} (composite provisionPackage),
GET|POST /v1/org/{org}/domain (auto ingress+DNS+cert), GET /v1/brand?host=,
parentOrgId column.
- Tests: +41 (packages normalizer+seed, model compose/tree/infer, tenants-API
path/normalizer) all green; tsc clean for all new files; /tenants + /tenants/packages
render 200 with zero page errors through the admin-gated catch-all.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The global-admin surface for launching, branding, domain-binding, and managing
white-label tenants + resold sub-orgs. The MANAGEMENT UI over the platform's
provisioning — tenant/package/domain/brand RECORDS are the single source of truth,
nothing hardcoded as the canonical path; honest-state everywhere (real where a
backend answers, honest not-connected where a platform endpoint isn't bound yet).
- TenantsModule (admin: true, category Platform) + tenants/: tenants list COMPOSED
from IAM orgs (brand) + admin cockpit (plan/wallet/status) + platform clusters;
reseller TREE derived from metadata.parentOrg or (honestly flagged) owner email;
package catalog read from the platform (DATA, seeded from platform-seed/packages.json,
never a hardcoded const); New-tenant create (real IAM org); per-tenant manage
(brand write REAL via IAM org fields, cluster provision REAL, domain list+bind,
IAM apps, package grant, suspend/reactivate REAL).
- BFF: no new proxy — all platform calls ride the existing /paas catch-all (light up
when the platform serves them; honest 404 today). Only server change:
add/update/delete-organization added to the /admin/iam allow-list (global-admin
gated, org-name pinned) so tenant-create + brand-write are REAL.
- Data-driven brand resolver: TenantsApi.brandConfig(host) + TenantBrandConfig
replace the hardcoded BRANDS/HOST_BRANDS map in config.ts (marked deprecated with
the precise migration; not swapped this pass — it's a build-time OAuth boundary).
- Missing platform endpoints flagged for the foundation phase: GET /v1/packages +
package table, POST/DELETE /v1/org/{org}/package/{id} (composite provisionPackage),
GET|POST /v1/org/{org}/domain (auto ingress+DNS+cert), GET /v1/brand?host=,
parentOrgId column.
- Tests: +41 (packages normalizer+seed, model compose/tree/infer, tenants-API
path/normalizer) all green; tsc clean for all new files; /tenants + /tenants/packages
render 200 with zero page errors through the admin-gated catch-all.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Full-console walkthrough flagged /automation, /automations, /ml-pipelines,
/mlpipelines as raw 404s. Root cause: the nav opens each entry by its canonical
id (auto → auto.hanzo.ai external launch; kubeflow → in-console module), so a
directly-navigated/bookmarked conventional slug matched no entry and hit
notFound(). DNS + Zero-Trust already render honest BackendStateCard degraded
states (verified — no change).
- ML Pipelines: rename entry id kubeflow → ml-pipelines so the id IS the
intuitive slug (label was already 'ML Pipelines'; Kubeflow is the engine, in
the description). /ml-pipelines is now the canonical route.
- Slug aliases: ONE SLUG_ALIASES table in match-core (the single resolver) maps
automation/automations → auto, mlpipelines/kubeflow → ml-pipelines. canonicalSlug
rewrites the head segment up front in resolveProductView, so every branch reasons
over the canonical id. A module alias resolves to the real route; an external
target resolves to a new 'external' view kind.
- Catch-all: an 'external' view renders ProductInterstitial (the in-console
discover page with an Open button that launches the product's own domain) —
never a 404 for a hand-typed external-product URL.
DRY: aliasing in one place, no duplicate modules, no fake soon states, honest
by construction. tsc clean; vitest 1534/1534 (+10 match-core alias/external);
next build ✓ 14/14.
Full-console walkthrough flagged /automation, /automations, /ml-pipelines,
/mlpipelines as raw 404s. Root cause: the nav opens each entry by its canonical
id (auto → auto.hanzo.ai external launch; kubeflow → in-console module), so a
directly-navigated/bookmarked conventional slug matched no entry and hit
notFound(). DNS + Zero-Trust already render honest BackendStateCard degraded
states (verified — no change).
- ML Pipelines: rename entry id kubeflow → ml-pipelines so the id IS the
intuitive slug (label was already 'ML Pipelines'; Kubeflow is the engine, in
the description). /ml-pipelines is now the canonical route.
- Slug aliases: ONE SLUG_ALIASES table in match-core (the single resolver) maps
automation/automations → auto, mlpipelines/kubeflow → ml-pipelines. canonicalSlug
rewrites the head segment up front in resolveProductView, so every branch reasons
over the canonical id. A module alias resolves to the real route; an external
target resolves to a new 'external' view kind.
- Catch-all: an 'external' view renders ProductInterstitial (the in-console
discover page with an Open button that launches the product's own domain) —
never a 404 for a hand-typed external-product URL.
DRY: aliasing in one place, no duplicate modules, no fake soon states, honest
by construction. tsc clean; vitest 1534/1534 (+10 match-core alias/external);
next build ✓ 14/14.
On an admin console host the operator could not sign into the cockpit: after the
admin-guard passed, console2s own app-login failed with
oauth2 invalid_grant: the token is for wrong application,
application.Name:[hanzo-cloud], token.Application:[admin-console]
Root cause: admin.<brand> switched the OAuth APP to admin-console but never
switched the ORG, so login resolved into the brand tenant org (hanzo) instead of
the reserved global-admin org (admin) where admin-console is registered — the
code was minted in the wrong org and the token audience mismatched.
BUG #1 (src/config/index.ts resolveConfig): iamOrgName never switched on an admin
host. The app and the org now travel together — a sibling of the existing
app-switch: const admin = isAdminHost(host); app = admin ? adminApp : iamApp;
org = admin ? ADMIN_ORG : b.iamOrgName. NEXT_PUBLIC_* override precedence
unchanged. ADMIN_ORG (=admin) is ONE global org across every brand.
BUG #2 (src/lib/auth/iam-login.ts): the direct credential login hardcoded
organization: (a TENANT multi-org behaviour) on every host, so the admin host
never pinned org=admin. Now organization = isAdminHost(window.location.hostname)
? config.iamOrgName : — admin.<brand> authenticates INTO admin, tenants keep the
resolve-across-orgs-by-email behaviour (unchanged). The login wire already
derives its host + redirectUri client-side from window.location, so the SSR
build-time default host never enters the login flow.
Tenant (console.hanzo.ai) auth and the admin-guard org-membership gate are
untouched.
Tests: resolveConfig(admin.hanzo.ai) -> {admin-console, admin-console, admin};
resolveConfig(console.hanzo.ai) unchanged; new iam-login.test.ts proves the
credential POST carries client_id/application=admin-console + organization=admin
on admin.hanzo.ai and brand-app + empty org on a tenant host.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
On an admin console host the operator could not sign into the cockpit: after the
admin-guard passed, console2s own app-login failed with
oauth2 invalid_grant: the token is for wrong application,
application.Name:[hanzo-cloud], token.Application:[admin-console]
Root cause: admin.<brand> switched the OAuth APP to admin-console but never
switched the ORG, so login resolved into the brand tenant org (hanzo) instead of
the reserved global-admin org (admin) where admin-console is registered — the
code was minted in the wrong org and the token audience mismatched.
BUG #1 (src/config/index.ts resolveConfig): iamOrgName never switched on an admin
host. The app and the org now travel together — a sibling of the existing
app-switch: const admin = isAdminHost(host); app = admin ? adminApp : iamApp;
org = admin ? ADMIN_ORG : b.iamOrgName. NEXT_PUBLIC_* override precedence
unchanged. ADMIN_ORG (=admin) is ONE global org across every brand.
BUG #2 (src/lib/auth/iam-login.ts): the direct credential login hardcoded
organization: (a TENANT multi-org behaviour) on every host, so the admin host
never pinned org=admin. Now organization = isAdminHost(window.location.hostname)
? config.iamOrgName : — admin.<brand> authenticates INTO admin, tenants keep the
resolve-across-orgs-by-email behaviour (unchanged). The login wire already
derives its host + redirectUri client-side from window.location, so the SSR
build-time default host never enters the login flow.
Tenant (console.hanzo.ai) auth and the admin-guard org-membership gate are
untouched.
Tests: resolveConfig(admin.hanzo.ai) -> {admin-console, admin-console, admin};
resolveConfig(console.hanzo.ai) unchanged; new iam-login.test.ts proves the
credential POST carries client_id/application=admin-console + organization=admin
on admin.hanzo.ai and brand-app + empty org on a tenant host.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The org > project selector ships already (ScopeSwitcher in the shell,
ScopeProvider in app/(dashboard)/layout.tsx, selection persisted via
lib/scope + localStorage). scope.test.ts proves the STORE; nothing proved
the WIRE — that a selected project actually reaches X-Project-Id on every
cloud call (the header visor attributes org>app>project usage by, spoof-
proofed at cloud.SanitizeIdentity).
Black-box test through a real get() over a stubbed global fetch:
- org-level (no project): org-scoped call, NO X-Project-Id
- project selected: X-Project-Id stamped, still under X-Org-Id
- project cleared: X-Project-Id drops back to org-level
- active environment rides along as X-Environment
No production change; locks the contract a customer scoping by project relies on.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The org > project selector ships already (ScopeSwitcher in the shell,
ScopeProvider in app/(dashboard)/layout.tsx, selection persisted via
lib/scope + localStorage). scope.test.ts proves the STORE; nothing proved
the WIRE — that a selected project actually reaches X-Project-Id on every
cloud call (the header visor attributes org>app>project usage by, spoof-
proofed at cloud.SanitizeIdentity).
Black-box test through a real get() over a stubbed global fetch:
- org-level (no project): org-scoped call, NO X-Project-Id
- project selected: X-Project-Id stamped, still under X-Org-Id
- project cleared: X-Project-Id drops back to org-level
- active environment rides along as X-Environment
No production change; locks the contract a customer scoping by project relies on.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Live: console.hanzo.ai/playground → "Could not reach the backend — HTTP 502",
model selector empty ("Choose a model"), Run blocked. ROOT CAUSE: the
ChatPlayground catalog fetch (aicatalog.fetchCatalog via useModels) hard-depended
on /v1/pricing/models — that endpoint 502s on the live ingress and its restGet had
NO .catch, so the whole Promise.all rejected even though /v1/models (200, the full
~59-model DO-first catalog incl the zen5 family) succeeded right beside it. The
working /v1/models result was discarded → 502 card → no model preselected.
- Fix 1 (catalog reachability, DRY): fetchCatalog now makes /v1/models the PRIMARY,
always-routed source and /v1/pricing/models a best-effort overlay (the EXACT
resilience CloudModelApi.list already uses). When pricing 502s it falls through to
the live set; live-only entries are normalized name<-id, provider<-owned_by so the
picker row never renders blank (also fixes a pre-existing latent blank-name).
Throws only if the live /v1/models set itself is unreachable. Marketplace +
ModelCatalog (the other fetchCatalog consumers) get the same resilience.
- Fix 2 (auto-select promoted Zen): new pure default-model.ts (defaultModelId,
extracted from useModels so it's node-testable without the hook's UI imports;
re-exported, callers unchanged). Default = latest PROMOTED Zen flagship: honor an
explicit catalog `featured` flag first (auto-tracks zen6 with no code change), else
the bare Zen flagship by name (zen5) over a mini/flash/coder tier, else any servable
text model. ModelOption carries `featured`. ChatPlayground seed effect is retry-safe.
tsc --noEmit=0; vitest 1502 pass (+9 default-model, +2 aicatalog 502-resilience;
the pre-existing canonical-paths.test.ts s3 case is RED on origin/main HEAD — the
v8.4.70 storage.ts->cloudProxyV1Url move left that expectation stale — UNRELATED:
storage.ts/canonical-paths.test.ts/client.ts untouched); next build 14/14.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Live: console.hanzo.ai/playground → "Could not reach the backend — HTTP 502",
model selector empty ("Choose a model"), Run blocked. ROOT CAUSE: the
ChatPlayground catalog fetch (aicatalog.fetchCatalog via useModels) hard-depended
on /v1/pricing/models — that endpoint 502s on the live ingress and its restGet had
NO .catch, so the whole Promise.all rejected even though /v1/models (200, the full
~59-model DO-first catalog incl the zen5 family) succeeded right beside it. The
working /v1/models result was discarded → 502 card → no model preselected.
- Fix 1 (catalog reachability, DRY): fetchCatalog now makes /v1/models the PRIMARY,
always-routed source and /v1/pricing/models a best-effort overlay (the EXACT
resilience CloudModelApi.list already uses). When pricing 502s it falls through to
the live set; live-only entries are normalized name<-id, provider<-owned_by so the
picker row never renders blank (also fixes a pre-existing latent blank-name).
Throws only if the live /v1/models set itself is unreachable. Marketplace +
ModelCatalog (the other fetchCatalog consumers) get the same resilience.
- Fix 2 (auto-select promoted Zen): new pure default-model.ts (defaultModelId,
extracted from useModels so it's node-testable without the hook's UI imports;
re-exported, callers unchanged). Default = latest PROMOTED Zen flagship: honor an
explicit catalog `featured` flag first (auto-tracks zen6 with no code change), else
the bare Zen flagship by name (zen5) over a mini/flash/coder tier, else any servable
text model. ModelOption carries `featured`. ChatPlayground seed effect is retry-safe.
tsc --noEmit=0; vitest 1502 pass (+9 default-model, +2 aicatalog 502-resilience;
the pre-existing canonical-paths.test.ts s3 case is RED on origin/main HEAD — the
v8.4.70 storage.ts->cloudProxyV1Url move left that expectation stale — UNRELATED:
storage.ts/canonical-paths.test.ts/client.ts untouched); next build 14/14.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The v8.4.70 build break (framework/client.ts + storage.ts imported the
cloudProxyV1Url that #81 DELETED → tsc TS2305; next build type-checks, so CI
shipped no new image) blocked BOTH live CTO reports from deploying: the authed
overview (sound code — UsageApi.overview → /v1/billing/usage, LivingOverview
degrades to an honest ErrorState) and the Qwen/Llama/DeepSeek model brand
icons (already fixed in 6dfa9c059: Qwen #615CED, Meta #0866FF, DeepSeek #4D6BFE).
The build fix landed concurrently in c458efa8f (re-add cloudProxyV1Url — the
prod-correct variant: the live ingress does NOT rewrite bare /v1/s3, /v1/framework
to the console app, so those heads address /cloud EXPLICITLY). But it left vitest
RED: canonical-paths.test.ts still asserted the old prefix-free
StorageApi.buckets → /v1/s3/buckets. This restores green + pins both invariants:
- canonical-paths.test.ts: drop the stale prefix-free s3 assertion; add a
documented cloud-proxy-exceptions block pinning s3 + framework to /cloud/v1/*
(so a future canonicalization can't repoint them to a bare /v1/ that 403s live).
- families.test.ts: a families↔brand contract test — every curated family logo
resolves through the ONE normalizeBrand→BRANDS resolver to a real colour + icon,
keyed off the exact live pricing.json providers (Qwen/Meta/DeepSeek). Permanent
guard for the 'icons blank' report.
Test-only (runtime fixes already on main). tsc 0; vitest 1507/1507 (121 files);
next build ✓ 14/14.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The v8.4.70 build break (framework/client.ts + storage.ts imported the
cloudProxyV1Url that #81 DELETED → tsc TS2305; next build type-checks, so CI
shipped no new image) blocked BOTH live CTO reports from deploying: the authed
overview (sound code — UsageApi.overview → /v1/billing/usage, LivingOverview
degrades to an honest ErrorState) and the Qwen/Llama/DeepSeek model brand
icons (already fixed in f6bcb5b94: Qwen #615CED, Meta #0866FF, DeepSeek #4D6BFE).
The build fix landed concurrently in d3f4081a2 (re-add cloudProxyV1Url — the
prod-correct variant: the live ingress does NOT rewrite bare /v1/s3, /v1/framework
to the console app, so those heads address /cloud EXPLICITLY). But it left vitest
RED: canonical-paths.test.ts still asserted the old prefix-free
StorageApi.buckets → /v1/s3/buckets. This restores green + pins both invariants:
- canonical-paths.test.ts: drop the stale prefix-free s3 assertion; add a
documented cloud-proxy-exceptions block pinning s3 + framework to /cloud/v1/*
(so a future canonicalization can't repoint them to a bare /v1/ that 403s live).
- families.test.ts: a families↔brand contract test — every curated family logo
resolves through the ONE normalizeBrand→BRANDS resolver to a real colour + icon,
keyed off the exact live pricing.json providers (Qwen/Meta/DeepSeek). Permanent
guard for the 'icons blank' report.
Test-only (runtime fixes already on main). tsc 0; vitest 1507/1507 (121 files);
next build ✓ 14/14.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
v8.4.70's framework + storage clients import cloudProxyV1Url to address the /cloud
bearer proxy explicitly (a bare /v1/framework or /v1/s3 hits hanzoai/gateway with no
principal → 403). But that helper had been deleted from client.ts by the earlier
/v1-canonicalization, so the build failed: "'cloudProxyV1Url' is not exported from
'./client'". Re-add cloudProxyBase + cloudProxyV1Url (the <origin>/cloud/v1/<path>
builder) so the CMS/ERP/Help framework calls and the media DAM S3 calls resolve and
reach the working proxy. next build green (14/14).
v8.4.70's framework + storage clients import cloudProxyV1Url to address the /cloud
bearer proxy explicitly (a bare /v1/framework or /v1/s3 hits hanzoai/gateway with no
principal → 403). But that helper had been deleted from client.ts by the earlier
/v1-canonicalization, so the build failed: "'cloudProxyV1Url' is not exported from
'./client'". Re-add cloudProxyBase + cloudProxyV1Url (the <origin>/cloud/v1/<path>
builder) so the CMS/ERP/Help framework calls and the media DAM S3 calls resolve and
reach the working proxy. next build green (14/14).
Same ingress-bypass class as the framework fix: StorageApi built its URLs with
originV1Url → `/v1/s3/*`, which console.hanzo.ai's ingress routes DIRECTLY to
hanzoai/gateway (bypassing Next), so the request lands with no principal → 403
"valid principal required". This broke BOTH the S3 file-manager product AND the CMS
media DAM (media-upload.ts presigns uploads via StorageApi).
Fix: cloudProxyV1Url → `/cloud/v1/s3/*` (the `/cloud` route reaches app/cloud's
bearer proxy; `s3` is allow-listed in proxy-allow.ts CLOUD_HEADS). Presigned PUT/GET
URLs are absolute S3 and unaffected — only the minting calls (buckets/objects/
presign) move to the proxy. Tests updated to the corrected /cloud/v1/s3 path (15
pass). Ships in v8.4.70 alongside the framework fix.
Same ingress-bypass class as the framework fix: StorageApi built its URLs with
originV1Url → `/v1/s3/*`, which console.hanzo.ai's ingress routes DIRECTLY to
hanzoai/gateway (bypassing Next), so the request lands with no principal → 403
"valid principal required". This broke BOTH the S3 file-manager product AND the CMS
media DAM (media-upload.ts presigns uploads via StorageApi).
Fix: cloudProxyV1Url → `/cloud/v1/s3/*` (the `/cloud` route reaches app/cloud's
bearer proxy; `s3` is allow-listed in proxy-allow.ts CLOUD_HEADS). Presigned PUT/GET
URLs are absolute S3 and unaffected — only the minting calls (buckets/objects/
presign) move to the proxy. Tests updated to the corrected /cloud/v1/s3 path (15
pass). Ships in v8.4.70 alongside the framework fix.
The CMS "Content" page showed "Not enabled for your account" for a real user whose
org HAS the cms module installed. Root cause: the framework client built its URLs
with originV1Url → `/v1/framework/*`, but on console.hanzo.ai the INGRESS routes
`/v1/*` DIRECTLY to hanzoai/gateway (bypassing the Next.js app), so the next.config
`/v1/framework → /cloud/v1/framework` rewrite never runs. The gateway has no
principal for that path and returns 403 "valid principal required" → the module
renders its honest access-denied card.
Fix: build framework URLs with cloudProxyV1Url → `/cloud/v1/framework/*` (the same
per-tenant bearer-proxy path CRM/Prompts/Agents use, allow-listed as the `framework`
head in proxy-allow.ts). The `/cloud` route DOES reach Next's app/cloud proxy, which
mints a short-lived user-bound token and forwards to cloud-api with the org resolved
from the token owner. Verified live: `/cloud/v1/framework/doctypes` = 200 with the
real doctypes for maxpower; `/v1/framework/doctypes` = 403 (gateway). One-line import
swap to an already-exported, already-used helper; tsc clean, framework client tests
pass.
The CMS "Content" page showed "Not enabled for your account" for a real user whose
org HAS the cms module installed. Root cause: the framework client built its URLs
with originV1Url → `/v1/framework/*`, but on console.hanzo.ai the INGRESS routes
`/v1/*` DIRECTLY to hanzoai/gateway (bypassing the Next.js app), so the next.config
`/v1/framework → /cloud/v1/framework` rewrite never runs. The gateway has no
principal for that path and returns 403 "valid principal required" → the module
renders its honest access-denied card.
Fix: build framework URLs with cloudProxyV1Url → `/cloud/v1/framework/*` (the same
per-tenant bearer-proxy path CRM/Prompts/Agents use, allow-listed as the `framework`
head in proxy-allow.ts). The `/cloud` route DOES reach Next's app/cloud proxy, which
mints a short-lived user-bound token and forwards to cloud-api with the org resolved
from the token owner. Verified live: `/cloud/v1/framework/doctypes` = 200 with the
real doctypes for maxpower; `/v1/framework/doctypes` = 403 (gateway). One-line import
swap to an already-exported, already-used helper; tsc clean, framework client tests
pass.
The Inference · Logs view already streamed the org's REAL recorded inference
calls (one commerce-usage-ledger row per billed call), but the rows were not
clickable and the LogLine projection discarded the rich per-call fields. Close
that gap — each row now opens the shared DetailPane showing what actually
happened for that call: model, provider, outcome, cost, prompt/completion/total
tokens, streamed, tier, product/agent attribution (only when the ledger tagged
it), request + transaction id, and time — every value REAL from the ledger
record, honest em-dash for absent. The full prompt/response TEXT is not on the
ledger row, so it is honestly stated as streaming from observability once its
trace runtime is connected — never fabricated.
DRY, no new surface: enrich LogLine with its source UsageRecord + one pure
logDetailFacts projection (logic.ts), one openLogDetail slide-over over the
existing DetailPane (panes.tsx, identical descriptor form to openEndpointDetail),
and wire onRowPress + a chevron affordance (LogsView.tsx). Reuses the shared Fact
row, StatusDot, and PrimaryButton — same look and feel as every other detail
surface.
Verification: tsc --noEmit clean; vitest 1136/1136 (+4 logDetailFacts /
LogLine.record); next build compiled successfully. Live authenticated render is
gated behind the console's server-cookie AuthGate (no backend session locally),
so verified via the component prop-level tests + a clean /[...slug] compile that
serves /inference/logs 200 in the dev server.
The Inference · Logs view already streamed the org's REAL recorded inference
calls (one commerce-usage-ledger row per billed call), but the rows were not
clickable and the LogLine projection discarded the rich per-call fields. Close
that gap — each row now opens the shared DetailPane showing what actually
happened for that call: model, provider, outcome, cost, prompt/completion/total
tokens, streamed, tier, product/agent attribution (only when the ledger tagged
it), request + transaction id, and time — every value REAL from the ledger
record, honest em-dash for absent. The full prompt/response TEXT is not on the
ledger row, so it is honestly stated as streaming from observability once its
trace runtime is connected — never fabricated.
DRY, no new surface: enrich LogLine with its source UsageRecord + one pure
logDetailFacts projection (logic.ts), one openLogDetail slide-over over the
existing DetailPane (panes.tsx, identical descriptor form to openEndpointDetail),
and wire onRowPress + a chevron affordance (LogsView.tsx). Reuses the shared Fact
row, StatusDot, and PrimaryButton — same look and feel as every other detail
surface.
Verification: tsc --noEmit clean; vitest 1136/1136 (+4 logDetailFacts /
LogLine.record); next build compiled successfully. Live authenticated render is
gated behind the console's server-cookie AuthGate (no backend session locally),
so verified via the component prop-level tests + a clean /[...slug] compile that
serves /inference/logs 200 in the dev server.
The Nodes surface (Network category, enabled on lux/zoo/pars + hanzo) showed
validators + peers per luxd primary network, but not the network's chains. This
adds the live primary-network chain set — the letter chains X C D Q A B T Z G K
plus the P-Chain — read from `platform.getBlockchains` through the same
same-origin, session-gated, method-allowlisted `/nodes` proxy.
- `/nodes` proxy: `platform.getBlockchains` added as the 5th (and only new)
allowlisted luxd read method. A network counts as reporting if validators,
peers, OR chains answered; chains are best-effort (a network can report
validators yet not answer getBlockchains → honest empty chain list, never
fabricated chains).
- `nodes.ts`: `RawBlockchain`/`ChainInfo` types + PURE `normalizeChains`
(prepends the P-Chain, which getBlockchains omits; preserves reported order;
drops id-less chains). `NetworkInventory.chains` added.
- `NodesModule`: renamed to "Networks & Nodes"; per-network card gains a Chains
count + live chain chips; a Chains table (Network · Chain · Blockchain ID · VM)
renders above the validators/peers table, honoring the network filter.
- Tests: +3 normalizeChains cases over the real devnet wire shape (33/33 pass).
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
The Nodes surface (Network category, enabled on lux/zoo/pars + hanzo) showed
validators + peers per luxd primary network, but not the network's chains. This
adds the live primary-network chain set — the letter chains X C D Q A B T Z G K
plus the P-Chain — read from `platform.getBlockchains` through the same
same-origin, session-gated, method-allowlisted `/nodes` proxy.
- `/nodes` proxy: `platform.getBlockchains` added as the 5th (and only new)
allowlisted luxd read method. A network counts as reporting if validators,
peers, OR chains answered; chains are best-effort (a network can report
validators yet not answer getBlockchains → honest empty chain list, never
fabricated chains).
- `nodes.ts`: `RawBlockchain`/`ChainInfo` types + PURE `normalizeChains`
(prepends the P-Chain, which getBlockchains omits; preserves reported order;
drops id-less chains). `NetworkInventory.chains` added.
- `NodesModule`: renamed to "Networks & Nodes"; per-network card gains a Chains
count + live chain chips; a Chains table (Network · Chain · Blockchain ID · VM)
renders above the validators/peers table, honoring the network filter.
- Tests: +3 normalizeChains cases over the real devnet wire shape (33/33 pass).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The still-valid residual of #77 (which #81's canonicalization couldn't carry — #77
imported the now-deleted cloudProxyV1Url). Two real bugs, redone canonically on main:
1. o11y annotation-queues + users reads hit the DIRECT-cloud origin (`v1Url` ->
config.cloudUrl). The o11y runtime scopes tenancy by the minted bearer's owner and
403s a cookie-only call in prod, so those 4 reads (annotationQueues/annotationQueue/
annotationQueueItems/users) were dead on the deployed console. Switched to the ONE
canonical `originV1Url('o11y/…')` -> `/v1/o11y/…`; next.config rewrites the o11y head
to the `/cloud` bearer proxy (server) and the static embed reaches it directly — the
exact transport every other o11y read (ServiceMap/Alerts) already uses. The #41 sweep
only missed these because they were `v1Url`, not the deleted prefixed helper.
2. The `observations` + `users` catalog entries were TRAPPED inside registry.tsx's
opening JSDoc block (the `/**` never closed before them), so they never registered in
nav/routing despite ObservationsModule/UsersModule existing, being imported, and
fetching real data. Closed the comment and moved both entries into the active catalog
under Observe (beside Annotation Queues), so they render in the sidebar and route via
the catch-all like their siblings.
Supersedes #77 (unmergeable — it referenced the deleted helper). Verify: tsc --noEmit
= 0; vitest 1475/1475 (120 files); next build ✓ (14/14, the /[...slug] catch-all that
renders the catalog compiles). Authenticated visual e2e (the 4 o11y reads returning
real data; Observations/Users in the sidebar) is post-deploy.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The still-valid residual of #77 (which #81's canonicalization couldn't carry — #77
imported the now-deleted cloudProxyV1Url). Two real bugs, redone canonically on main:
1. o11y annotation-queues + users reads hit the DIRECT-cloud origin (`v1Url` ->
config.cloudUrl). The o11y runtime scopes tenancy by the minted bearer's owner and
403s a cookie-only call in prod, so those 4 reads (annotationQueues/annotationQueue/
annotationQueueItems/users) were dead on the deployed console. Switched to the ONE
canonical `originV1Url('o11y/…')` -> `/v1/o11y/…`; next.config rewrites the o11y head
to the `/cloud` bearer proxy (server) and the static embed reaches it directly — the
exact transport every other o11y read (ServiceMap/Alerts) already uses. The #41 sweep
only missed these because they were `v1Url`, not the deleted prefixed helper.
2. The `observations` + `users` catalog entries were TRAPPED inside registry.tsx's
opening JSDoc block (the `/**` never closed before them), so they never registered in
nav/routing despite ObservationsModule/UsersModule existing, being imported, and
fetching real data. Closed the comment and moved both entries into the active catalog
under Observe (beside Annotation Queues), so they render in the sidebar and route via
the catch-all like their siblings.
Supersedes #77 (unmergeable — it referenced the deleted helper). Verify: tsc --noEmit
= 0; vitest 1475/1475 (120 files); next build ✓ (14/14, the /[...slug] catch-all that
renders the catalog compiles). Authenticated visual e2e (the 4 o11y reads returning
real data; Observations/Users in the sidebar) is post-deploy.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Two new white-label brands recognized by the unified console so their hosts
render branded, mirroring lux/zoo/pars:
- config: BrandId gains '7stars' | 'yotoda'; BRANDS + HOST_BRANDS entries.
Both are general Hanzo-cloud customers seeded AS ORGS in the hanzo IAM
(hanzo.id) — they have NO own .id issuer, so iamUrl = https://hanzo.id with
the per-brand iamOrgName (7stars/yotoda) + iamApp (7stars-cloud/yotoda-cloud).
Login resolves against hanzo.id, org-scoped by the JWT owner (aud=<brand>-cloud),
matching how the orgs/apps were provisioned. Own billing.<domain>/docs.<domain>.
HOST_BRANDS suffixes 7stars.dev / yotoda.tech cover every subdomain
(cloud.*, console.*, admin.*) via the endsWith('.'+suffix) match.
- brand-scope: BRAND_CATEGORIES null (FULL AI-cloud catalog, like hanzo — they
are general cloud customers, not web3-only like the sovereign-chain brands).
BRAND_NODE_NETWORKS [] — they own no chain, so the Nodes surface reports on no
networks (never another brand's chain).
- branding/brands: BRANDS registry gains 7Stars/Yotoda with their own
brandName/orgName/websiteUrl/adminDomain (adminDomain is the admin-gate email
boundary — @7stars.dev / @yotoda.tech match the seeded owners z@7stars.dev /
z@yotoda.tech). Logo falls back to the generic Hanzo blocky-H mark (no bespoke
asset yet); swap logoContent when a real mark ships.
Tests: index.test.ts (host resolution, hanzo.id issuer, per-brand billing/docs,
admin app) + registry-brand.test.ts (full-catalog scope, zero node networks).
npm test 975/975 green. tsc/next build add zero new type errors (diff-proven
identical to origin/main; the pre-existing next/navigation nullable errors are a
local Node 26 vs CI Node 24 toolchain drift, not from these files).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Two new white-label brands recognized by the unified console so their hosts
render branded, mirroring lux/zoo/pars:
- config: BrandId gains '7stars' | 'yotoda'; BRANDS + HOST_BRANDS entries.
Both are general Hanzo-cloud customers seeded AS ORGS in the hanzo IAM
(hanzo.id) — they have NO own .id issuer, so iamUrl = https://hanzo.id with
the per-brand iamOrgName (7stars/yotoda) + iamApp (7stars-cloud/yotoda-cloud).
Login resolves against hanzo.id, org-scoped by the JWT owner (aud=<brand>-cloud),
matching how the orgs/apps were provisioned. Own billing.<domain>/docs.<domain>.
HOST_BRANDS suffixes 7stars.dev / yotoda.tech cover every subdomain
(cloud.*, console.*, admin.*) via the endsWith('.'+suffix) match.
- brand-scope: BRAND_CATEGORIES null (FULL AI-cloud catalog, like hanzo — they
are general cloud customers, not web3-only like the sovereign-chain brands).
BRAND_NODE_NETWORKS [] — they own no chain, so the Nodes surface reports on no
networks (never another brand's chain).
- branding/brands: BRANDS registry gains 7Stars/Yotoda with their own
brandName/orgName/websiteUrl/adminDomain (adminDomain is the admin-gate email
boundary — @7stars.dev / @yotoda.tech match the seeded owners z@7stars.dev /
z@yotoda.tech). Logo falls back to the generic Hanzo blocky-H mark (no bespoke
asset yet); swap logoContent when a real mark ships.
Tests: index.test.ts (host resolution, hanzo.id issuer, per-brand billing/docs,
admin app) + registry-brand.test.ts (full-catalog scope, zero node networks).
npm test 975/975 green. tsc/next build add zero new type errors (diff-proven
identical to origin/main; the pre-existing next/navigation nullable errors are a
local Node 26 vs CI Node 24 toolchain drift, not from these files).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Adds a "Markets" product (Web3) — the analytics/management plane for the Lux DEX
economy, the twin of the Trading (deploy/manage) module.
- lib/api/economy.ts — client + pure normalizers for the `dex` subgraph
(markets/fills/day-data). Honest to the CLOB reality: 24h volume, trades, book
depth, best-bid/ask, last price are real fields; USD TVL is NOT fabricated (a
CLOB has depth, not pooled TVL); the day-history series is empty until the
subgraph's MarketDayData producer emits.
- overview/living: fromLuxIndexer adapter + a `lux-economy` LivingOverview config
(KPIs, volume/trades/depth donuts, recent-trade feed, maker-health row) — the
reusable board machinery, one config + one adapter, no new overview UI.
- app/economy/[...path]/route.ts — session-gated, brand-scoped GraphQL proxy to
graphd's `dex` subgraph (ONE fixed query, no client GraphQL); honest not-reporting
when unreachable.
- MarketsModule — the living board + the DeFiLlama-style per-market table, both over
the /economy proxy. Registered under Web3 (lux.cloud shows it).
Data source: luxfi/graph `dex` subgraph (markets/fills) + the maker :2112 metrics.
Tests: 23 new (economy normalizers + fromLuxIndexer); full suite 1468 green.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds a "Markets" product (Web3) — the analytics/management plane for the Lux DEX
economy, the twin of the Trading (deploy/manage) module.
- lib/api/economy.ts — client + pure normalizers for the `dex` subgraph
(markets/fills/day-data). Honest to the CLOB reality: 24h volume, trades, book
depth, best-bid/ask, last price are real fields; USD TVL is NOT fabricated (a
CLOB has depth, not pooled TVL); the day-history series is empty until the
subgraph's MarketDayData producer emits.
- overview/living: fromLuxIndexer adapter + a `lux-economy` LivingOverview config
(KPIs, volume/trades/depth donuts, recent-trade feed, maker-health row) — the
reusable board machinery, one config + one adapter, no new overview UI.
- app/economy/[...path]/route.ts — session-gated, brand-scoped GraphQL proxy to
graphd's `dex` subgraph (ONE fixed query, no client GraphQL); honest not-reporting
when unreachable.
- MarketsModule — the living board + the DeFiLlama-style per-market table, both over
the /economy proxy. Registered under Web3 (lux.cloud shows it).
Data source: luxfi/graph `dex` subgraph (markets/fills) + the maker :2112 metrics.
Tests: 23 new (economy normalizers + fromLuxIndexer); full suite 1468 green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Adds a first-class "Trading" product under Web3: deploy the market-maker and
trader bots to the Hanzo PaaS from a config form, list the org's deployed bots,
watch each one's live quote quality (the maker's :2112 metrics) and DEX order
book, and control them (start/stop/redeploy/logs).
- lib/products/trading/templates.ts — the two deployable-app definitions
(maker + trader) with a typed config schema; toCreateAppInput maps a filled
config → a PaaS git app (BuildKit builds luxfi/{maker,trader} → GHCR).
Signer keys are secretRef fields (KMS-synced), never typed in the browser.
- lib/api/trading.ts — pure Prometheus-metrics + order-book normalizers.
- app/trading/[...path]/route.ts — session-gated, brand-scoped, method-allowlisted
proxy (mirrors /nodes): scrapes the maker :2112 metrics + reads the DEX book,
honest not-reporting when unreachable.
- components/products/TradingModule.tsx (+ trading/{logic,DeployForm}) — the
list/status/orderbook views + deploy/start/stop/redeploy/logs, over the existing
PaasApi control plane (one deploy path; the bots are ordinary PaaS git apps).
- registry: Trading entry (Web3, brand-agnostic; data brand-scoped in the proxy
so lux.cloud sees only Lux networks).
Tests: 34 new (templates/normalizers/logic), full suite 1311 green.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds a first-class "Trading" product under Web3: deploy the market-maker and
trader bots to the Hanzo PaaS from a config form, list the org's deployed bots,
watch each one's live quote quality (the maker's :2112 metrics) and DEX order
book, and control them (start/stop/redeploy/logs).
- lib/products/trading/templates.ts — the two deployable-app definitions
(maker + trader) with a typed config schema; toCreateAppInput maps a filled
config → a PaaS git app (BuildKit builds luxfi/{maker,trader} → GHCR).
Signer keys are secretRef fields (KMS-synced), never typed in the browser.
- lib/api/trading.ts — pure Prometheus-metrics + order-book normalizers.
- app/trading/[...path]/route.ts — session-gated, brand-scoped, method-allowlisted
proxy (mirrors /nodes): scrapes the maker :2112 metrics + reads the DEX book,
honest not-reporting when unreachable.
- components/products/TradingModule.tsx (+ trading/{logic,DeployForm}) — the
list/status/orderbook views + deploy/start/stop/redeploy/logs, over the existing
PaasApi control plane (one deploy path; the bots are ordinary PaaS git apps).
- registry: Trading entry (Web3, brand-agnostic; data brand-scoped in the proxy
so lux.cloud sees only Lux networks).
Tests: 34 new (templates/normalizers/logic), full suite 1311 green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Every /cms/* URL now renders the native DocType renderer over /v1/framework/* — no
iframe, no raw JSON, no 404. Fixes the live console.hanzo.ai/cms/collections/Article
-> {"error":"Not found"} bug (the deployed image lacked the wired CMS sub-routes, so
the catch-all resolved them to notFound() and a Next RSC navigation served a JSON
404). The routes were declared correctly; this ships them complete.
- Rich text = native Lexical (the same engine Payload's MIT richtext-lexical uses),
built fresh + thin on core lexical@0.46.0 and registered over @hanzo/data's
`richText` type in Provider.tsx (registerField override, no fork). Toolbar:
bold/italic/underline, H1-3 + paragraph + quote, bullet/number lists, links,
undo/redo. Stores the Lexical EditorState JSON; read view -> sanitized HTML via
$generateHtmlFromNodes. Pure serialization round-trips + migrates legacy plain
Text bodies (never throws). A DocType field typed RichText renders it.
- Content-type builder: "New collection" defines a DocType's name + typed fields
on-page (add/remove/reorder/require/list, every framework fieldtype with the extra
inputs each needs). Pure builder-logic.ts.
- Media = real DAM: drag/drop or pick -> uploads to the org's own S3 (cms-media
bucket, the same /v1/s3 SeaweedFS presigned-PUT as Storage) -> Media doc with the
stable object key -> thumbnails presigned on-view; delete removes doc + object.
- Publish/Unpublish (+ Submit/Cancel) in the record editor.
- Project scope: the org->project ScopeSwitcher filters the records list and stamps
new records, only on collections that declare a `project` field. One engine,
project is a filter — no per-project/per-org CMS instances.
tsc clean; vitest 1418 pass (+richtext/builder/media/project/richText round-trip);
next build 14/14. Needs cloud v1.786.52+ (RichText fieldtype) deployed to accept a
RichText field live.
Every /cms/* URL now renders the native DocType renderer over /v1/framework/* — no
iframe, no raw JSON, no 404. Fixes the live console.hanzo.ai/cms/collections/Article
-> {"error":"Not found"} bug (the deployed image lacked the wired CMS sub-routes, so
the catch-all resolved them to notFound() and a Next RSC navigation served a JSON
404). The routes were declared correctly; this ships them complete.
- Rich text = native Lexical (the same engine Payload's MIT richtext-lexical uses),
built fresh + thin on core lexical@0.46.0 and registered over @hanzo/data's
`richText` type in Provider.tsx (registerField override, no fork). Toolbar:
bold/italic/underline, H1-3 + paragraph + quote, bullet/number lists, links,
undo/redo. Stores the Lexical EditorState JSON; read view -> sanitized HTML via
$generateHtmlFromNodes. Pure serialization round-trips + migrates legacy plain
Text bodies (never throws). A DocType field typed RichText renders it.
- Content-type builder: "New collection" defines a DocType's name + typed fields
on-page (add/remove/reorder/require/list, every framework fieldtype with the extra
inputs each needs). Pure builder-logic.ts.
- Media = real DAM: drag/drop or pick -> uploads to the org's own S3 (cms-media
bucket, the same /v1/s3 SeaweedFS presigned-PUT as Storage) -> Media doc with the
stable object key -> thumbnails presigned on-view; delete removes doc + object.
- Publish/Unpublish (+ Submit/Cancel) in the record editor.
- Project scope: the org->project ScopeSwitcher filters the records list and stamps
new records, only on collections that declare a `project` field. One engine,
project is a filter — no per-project/per-org CMS instances.
tsc clean; vitest 1418 pass (+richtext/builder/media/project/richText round-trip);
next build 14/14. Needs cloud v1.786.52+ (RichText fieldtype) deployed to accept a
RichText field live.
hanzoai/auto (auto.hanzo.ai) — visual AI workflow automation over 400+ MCP tools
and agents (the n8n/Zapier surface) — was not in the console. Add it to the AI
category as an external launch tile: it's a standalone app with its own full UI
on shared Hanzo IAM, so the tile opens it already-signed-in (like the Lux/Zoo
chain apps). Scoped brands:['hanzo'] so the auto.hanzo.ai URL never leaks onto a
Lux/Zoo white-label console.
Tests: 90 registry/brand tests pass; tsc clean.
hanzoai/auto (auto.hanzo.ai) — visual AI workflow automation over 400+ MCP tools
and agents (the n8n/Zapier surface) — was not in the console. Add it to the AI
category as an external launch tile: it's a standalone app with its own full UI
on shared Hanzo IAM, so the tile opens it already-signed-in (like the Lux/Zoo
chain apps). Scoped brands:['hanzo'] so the auto.hanzo.ai URL never leaks onto a
Lux/Zoo white-label console.
Tests: 90 registry/brand tests pass; tsc clean.
The CTO contract is "nothing before /v1/". PR #79 (482251e) canonicalized 7 clients
but 3 helpers still hand-rolled a service-prefixed `<origin>/<svc>/v1/` URL —
aiV1Url (/ai), cloudProxyV1Url (/cloud), commerceProxyV1Url (/commerce) — fanning
out to 6 data-product clients AND ~13 product modules. DELETING them (not just
redefining) makes a non-canonical path COMPILER-IMPOSSIBLE: there is now ONE url
builder for the whole /v1 surface (originV1Url), exactly like billing/visor/
provisioning post-#79. Every remaining caller builds the bare, prefix-free
`/v1/<resource>`; next.config rewrites each head to its UNCHANGED same-origin BFF
proxy (app/ai, app/cloud, app/commerce — service-token / user-bearer injection intact).
- delete aiV1Url/cloudProxyV1Url/commerceProxyV1Url + aiBase/cloudProxyBase/
commerceProxyBase; repoint all callers to originV1Url (compiler-enforced, no caller left).
- aicatalog/embeddings: /ai/v1/{pricing,plans,models,embeddings} -> /v1/… ; add
`pricing`+`plans` to AI_V1_HEADS (already in the /ai proxy ALLOWED set).
- functions/paas/framework + Builds/Environments/Pipelines/Releases modules:
/cloud/v1/<h> -> /v1/<h>; new CLOUD_PRODUCT_V1_HEADS (functions/framework/
environments/pipelines/builds/releases) rewrites -> /cloud (already in proxy-allow
CLOUD_HEADS). apm(o11y) + paas(platform) heads were already rewritten.
- commerce: /commerce/v1/<x> -> the canonical namespace /v1/commerce/<x>, ONE rewrite
-> /commerce/v1/ (the billing twin) — collision-proof vs the generic store heads
(product/order/user/store). Local cUrl() namespaces once, in one place.
- extend canonical-paths.test.ts: aicatalog/apm/commerce/embeddings/functions/paas each
assert /v1/<resource> + never /<svc>/v1/. Realign functions.test + client-retry
illustrative URLs to the canonical form.
grep -rE '/(cloud|vm|ai|billing|org|commerce)/v1' src/lib/api/*.ts is clean.
tsc --noEmit ok; vitest 1439 pass; next build ok. Every console API call is now /v1/<resource>.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The CTO contract is "nothing before /v1/". PR #79 (4507cf5) canonicalized 7 clients
but 3 helpers still hand-rolled a service-prefixed `<origin>/<svc>/v1/` URL —
aiV1Url (/ai), cloudProxyV1Url (/cloud), commerceProxyV1Url (/commerce) — fanning
out to 6 data-product clients AND ~13 product modules. DELETING them (not just
redefining) makes a non-canonical path COMPILER-IMPOSSIBLE: there is now ONE url
builder for the whole /v1 surface (originV1Url), exactly like billing/visor/
provisioning post-#79. Every remaining caller builds the bare, prefix-free
`/v1/<resource>`; next.config rewrites each head to its UNCHANGED same-origin BFF
proxy (app/ai, app/cloud, app/commerce — service-token / user-bearer injection intact).
- delete aiV1Url/cloudProxyV1Url/commerceProxyV1Url + aiBase/cloudProxyBase/
commerceProxyBase; repoint all callers to originV1Url (compiler-enforced, no caller left).
- aicatalog/embeddings: /ai/v1/{pricing,plans,models,embeddings} -> /v1/… ; add
`pricing`+`plans` to AI_V1_HEADS (already in the /ai proxy ALLOWED set).
- functions/paas/framework + Builds/Environments/Pipelines/Releases modules:
/cloud/v1/<h> -> /v1/<h>; new CLOUD_PRODUCT_V1_HEADS (functions/framework/
environments/pipelines/builds/releases) rewrites -> /cloud (already in proxy-allow
CLOUD_HEADS). apm(o11y) + paas(platform) heads were already rewritten.
- commerce: /commerce/v1/<x> -> the canonical namespace /v1/commerce/<x>, ONE rewrite
-> /commerce/v1/ (the billing twin) — collision-proof vs the generic store heads
(product/order/user/store). Local cUrl() namespaces once, in one place.
- extend canonical-paths.test.ts: aicatalog/apm/commerce/embeddings/functions/paas each
assert /v1/<resource> + never /<svc>/v1/. Realign functions.test + client-retry
illustrative URLs to the canonical form.
grep -rE '/(cloud|vm|ai|billing|org|commerce)/v1' src/lib/api/*.ts is clean.
tsc --noEmit ok; vitest 1439 pass; next build ok. Every console API call is now /v1/<resource>.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
On console.hanzo.ai the ingress routes /v1/* straight to cloud-api, bypassing the
keyless /ai bearer proxy — so a /v1 image call reaches cloud with NO user Bearer
and 401s (premium image gen requires auth). Call /ai/v1/images|videos/generations
directly (this app → forwardWithUserBearer mints the user-bound bearer) so the
Playground Image/Video tabs generate real, per-user-metered media.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
On console.hanzo.ai the ingress routes /v1/* straight to cloud-api, bypassing the
keyless /ai bearer proxy — so a /v1 image call reaches cloud with NO user Bearer
and 401s (premium image gen requires auth). Call /ai/v1/images|videos/generations
directly (this app → forwardWithUserBearer mints the user-bound bearer) so the
Playground Image/Video tabs generate real, per-user-metered media.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
feat/erp-help-native (e2baba7): ERP + Help Center now render through the SAME
generic DocType renderer (src/components/doctype/*) that draws CMS, over the ONE
framework surface /v1/framework/*. Deletes the EmbeddedApp iframe subtree
entirely: EmbeddedApp.tsx, ProvisionPanel.tsx, embed-hosts, embed-probe,
api/embed, api/cms, api/erp, and the app/{cms,erp}/[...path] proxy routes
(-1872 lines). ERP + Help + CMS are ALL native now — zero iframe in the console.
Resolved package.json version to 8.4.66 (above live v8.4.65).
feat/erp-help-native (72ac722): ERP + Help Center now render through the SAME
generic DocType renderer (src/components/doctype/*) that draws CMS, over the ONE
framework surface /v1/framework/*. Deletes the EmbeddedApp iframe subtree
entirely: EmbeddedApp.tsx, ProvisionPanel.tsx, embed-hosts, embed-probe,
api/embed, api/cms, api/erp, and the app/{cms,erp}/[...path] proxy routes
(-1872 lines). ERP + Help + CMS are ALL native now — zero iframe in the console.
Resolved package.json version to 8.4.66 (above live v8.4.65).
Decomplect: make a non-canonical API path architecturally impossible for the
data-product surface. The 7 clients that hand-rolled a service-prefixed
/<svc>/v1/… path (billing, aimetrics, compute, visor, platform, provisioning,
storage) plus the Settlement component now build a bare /v1/<resource> via the
one originV1Url helper; next.config rewrites each head to its hardened
same-origin BFF proxy (service-token / user-bearer injection unchanged). Also
stamp X-Actor-Id (the signed-in user) in baseHeaders alongside
X-Org-Id/X-Project-Id, so org+project+user pass on EVERY call.
- billing/aimetrics: /billing/v1/<x> -> /v1/billing/<x> (rewrite -> app/billing/v1)
- compute: /cloud/v1/gpus[/alerts|/pools] -> /v1/gpus… (rewrite -> /cloud)
- visor: /cloud/v1/machines… -> /v1/machines…; /vm/v1/{regions,sizes} ->
/v1/{regions,sizes}; /vm/v1/gpus (catalog) -> /v1/gpu-sizes
(DISTINCT head: /v1/gpus is the cloud-api INVENTORY, not the catalog)
- platform: /cloud/v1/{clusters…,org/…/cluster} -> /v1/… (rewrite -> /cloud)
- provisioning/storage: /cloud/v1/{sql,vector,…,s3/…} -> /v1/… (rewrite -> /cloud)
- delete the per-client base-path builders (billingUrl / vm / clustersUrl-via-cloud);
grep -rE '/(cloud|vm|ai|billing|org)/v1' src/lib/api/*.ts is clean (only the
client.ts BFF-helper docs for the out-of-scope clients remain).
- X-Actor-Id sourced from a new lib/actor-scope (SessionProvider keeps it in
lockstep with the resolved account: the auth twin of org-scope).
tsc --noEmit ok; vitest 1432 pass; next build ok.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Decomplect: make a non-canonical API path architecturally impossible for the
data-product surface. The 7 clients that hand-rolled a service-prefixed
/<svc>/v1/… path (billing, aimetrics, compute, visor, platform, provisioning,
storage) plus the Settlement component now build a bare /v1/<resource> via the
one originV1Url helper; next.config rewrites each head to its hardened
same-origin BFF proxy (service-token / user-bearer injection unchanged). Also
stamp X-Actor-Id (the signed-in user) in baseHeaders alongside
X-Org-Id/X-Project-Id, so org+project+user pass on EVERY call.
- billing/aimetrics: /billing/v1/<x> -> /v1/billing/<x> (rewrite -> app/billing/v1)
- compute: /cloud/v1/gpus[/alerts|/pools] -> /v1/gpus… (rewrite -> /cloud)
- visor: /cloud/v1/machines… -> /v1/machines…; /vm/v1/{regions,sizes} ->
/v1/{regions,sizes}; /vm/v1/gpus (catalog) -> /v1/gpu-sizes
(DISTINCT head: /v1/gpus is the cloud-api INVENTORY, not the catalog)
- platform: /cloud/v1/{clusters…,org/…/cluster} -> /v1/… (rewrite -> /cloud)
- provisioning/storage: /cloud/v1/{sql,vector,…,s3/…} -> /v1/… (rewrite -> /cloud)
- delete the per-client base-path builders (billingUrl / vm / clustersUrl-via-cloud);
grep -rE '/(cloud|vm|ai|billing|org)/v1' src/lib/api/*.ts is clean (only the
client.ts BFF-helper docs for the out-of-scope clients remain).
- X-Actor-Id sourced from a new lib/actor-scope (SessionProvider keeps it in
lockstep with the resolved account: the auth twin of org-scope).
tsc --noEmit ok; vitest 1432 pass; next build ok.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Frontend CX defects found in a live deep-test of console.hanzo.ai:
- Compute/Machines: a non-200 from /cloud/v1/machines (esp. 403/5xx) rendered
the empty "Launch your first machine" state — a permission/load error
masquerading as "you have none", the opposite of the page's "nothing is
fabricated" promise. interpretVisorError now maps 401 -> sign-in, 403 ->
honest permission state, and any other non-200 -> a retryable load error;
CustomerMachines shows the empty/launch state ONLY on a real 200-with-zero.
- Chat: Enter did nothing but insert a newline. @hanzogui/input swallows the
onKeyPress prop (never wired to the DOM) and forwards onKeyDown; the newline
default fires on keydown, so the send handler must live there. Enter sends,
Shift+Enter is a newline, IME composition never sends.
- Chat: model chain-of-thought leaked into the answer bubble. New pure
splitThinking() separates a final answer from <think> reasoning (streaming-
safe); the bubble renders only the answer with reasoning behind an optional,
collapsed disclosure.
- Observe/Logs: landed on the empty "Application logs" tab while "Request
activity" (always real for the org) had data. Request activity now leads and
is the default tab.
Team members (#4) already routes through the single canonical /org/iam
get-users path at HEAD — no dead-endpoint waterfall remains to remove.
Build gate: tsc --noEmit, vitest (1418 tests), next build — all green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Frontend CX defects found in a live deep-test of console.hanzo.ai:
- Compute/Machines: a non-200 from /cloud/v1/machines (esp. 403/5xx) rendered
the empty "Launch your first machine" state — a permission/load error
masquerading as "you have none", the opposite of the page's "nothing is
fabricated" promise. interpretVisorError now maps 401 -> sign-in, 403 ->
honest permission state, and any other non-200 -> a retryable load error;
CustomerMachines shows the empty/launch state ONLY on a real 200-with-zero.
- Chat: Enter did nothing but insert a newline. @hanzogui/input swallows the
onKeyPress prop (never wired to the DOM) and forwards onKeyDown; the newline
default fires on keydown, so the send handler must live there. Enter sends,
Shift+Enter is a newline, IME composition never sends.
- Chat: model chain-of-thought leaked into the answer bubble. New pure
splitThinking() separates a final answer from <think> reasoning (streaming-
safe); the bubble renders only the answer with reasoning behind an optional,
collapsed disclosure.
- Observe/Logs: landed on the empty "Application logs" tab while "Request
activity" (always real for the org) had data. Request activity now leads and
is the default tab.
Team members (#4) already routes through the single canonical /org/iam
get-users path at HEAD — no dead-endpoint waterfall remains to remove.
Build gate: tsc --noEmit, vitest (1418 tests), next build — all green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
ERP and Help Center join CMS as NATIVE lanes on the Hanzo Framework — thin
hosts scoping the SAME generic renderer (components/doctype/*) to module=erp /
module=help, with ZERO per-doctype UI code (the DRY proof). This finishes the
Great Unification: CMS + CRM + ERP + Help all native DocTypes, all iframes dead.
- ErpModule/HelpModule rewritten as thin hosts (like CmsModule): collections
browser + records list + record detail, routed under /erp/collections and
/helpdesk/collections. Install CTA installs the lane's DocTypes/hooks;
submit/cancel + status flow come from the schema (no ERP/Help-specific UI).
- registry: erp + helpdesk -> native module routes (collections/:doctype +
:name), repo hanzoai/cloud, native descriptions.
- CollectionsBrowser: additive optional setupDescription/setupBullets so the
pre-install empty state reads correctly per lane. CMS default byte-identical
-- no behavior/permission/proxy change (the RED-passed path is unchanged).
- Kill the iframe/embed subtree ENTIRELY (finishes the unification): the
Frappe/Payload proxy route handlers app/erp + app/cms are Next catch-alls that
SHADOWED the native /*/collections SPA routes (a route handler wins over the
[...slug] page) -> deleting them unshadows native ERP AND native CMS (CMS was
latently shadow-broken since 8.4.63). Removed the now-dead EmbeddedApp /
ProvisionPanel / EmbedApi / CmsApi / ErpApi + embed-hosts + embed-probe + their
tests. No iframe/embed path remains anywhere in the console.
typecheck clean; vitest 1360/1360 (109 files); next build green (the /cms +
/erp proxy routes are gone from the manifest, so /*/collections reach the SPA).
ERP and Help Center join CMS as NATIVE lanes on the Hanzo Framework — thin
hosts scoping the SAME generic renderer (components/doctype/*) to module=erp /
module=help, with ZERO per-doctype UI code (the DRY proof). This finishes the
Great Unification: CMS + CRM + ERP + Help all native DocTypes, all iframes dead.
- ErpModule/HelpModule rewritten as thin hosts (like CmsModule): collections
browser + records list + record detail, routed under /erp/collections and
/helpdesk/collections. Install CTA installs the lane's DocTypes/hooks;
submit/cancel + status flow come from the schema (no ERP/Help-specific UI).
- registry: erp + helpdesk -> native module routes (collections/:doctype +
:name), repo hanzoai/cloud, native descriptions.
- CollectionsBrowser: additive optional setupDescription/setupBullets so the
pre-install empty state reads correctly per lane. CMS default byte-identical
-- no behavior/permission/proxy change (the RED-passed path is unchanged).
- Kill the iframe/embed subtree ENTIRELY (finishes the unification): the
Frappe/Payload proxy route handlers app/erp + app/cms are Next catch-alls that
SHADOWED the native /*/collections SPA routes (a route handler wins over the
[...slug] page) -> deleting them unshadows native ERP AND native CMS (CMS was
latently shadow-broken since 8.4.63). Removed the now-dead EmbeddedApp /
ProvisionPanel / EmbedApi / CmsApi / ErpApi + embed-hosts + embed-probe + their
tests. No iframe/embed path remains anywhere in the console.
typecheck clean; vitest 1360/1360 (109 files); next build green (the /cms +
/erp proxy routes are gone from the manifest, so /*/collections reach the SPA).
Adds Image and Video tabs to the Playground, symmetric to Audio/Chat:
- ImagePlayground: Zen image model + prompt + size → POST /v1/images/generations
→ renders the real image (hosted url or inline b64).
- VideoPlayground: Zen video model + prompt → POST /v1/videos/generations
→ renders the real clip (base64 MP4 blob or url).
- PlaygroundApi.images/videos (src/lib/api/playground.ts) ride the SAME keyless
/ai bearer proxy chat/audio use; invalidateBalance() after each (metered).
- Open images/videos in the /ai proxy allow-list (route.ts) and the
next.config.mjs AI_V1_HEADS rewrite. No new auth, no billing bypass.
Zen-brand model ids only; pickers filter to the image/video families.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Adds Image and Video tabs to the Playground, symmetric to Audio/Chat:
- ImagePlayground: Zen image model + prompt + size → POST /v1/images/generations
→ renders the real image (hosted url or inline b64).
- VideoPlayground: Zen video model + prompt → POST /v1/videos/generations
→ renders the real clip (base64 MP4 blob or url).
- PlaygroundApi.images/videos (src/lib/api/playground.ts) ride the SAME keyless
/ai bearer proxy chat/audio use; invalidateBalance() after each (metered).
- Open images/videos in the /ai proxy allow-list (route.ts) and the
next.config.mjs AI_V1_HEADS rewrite. No new auth, no billing bypass.
Zen-brand model ids only; pickers filter to the image/video families.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The model catalog rendered logos from each model's raw provider string, so the
Zen family flip-flopped (models tagged 'hanzo' → block-H, others → ensō) and
every third-party family fell through to a gray initials chip ('QW'). Fixes:
- Rows + detail now render the model's FAMILY brand (not raw provider), so a
family is internally consistent: Zen is ALWAYS the ensō; Qwen/OpenAI/etc. each
show one mark. (Directive: Zen provider always uses Zen.)
- Extract pure brand resolution into ui/brand.ts (normalizeBrand + BRANDS
registry) — unit tested, no GUI deps. Every curated family key resolves to a
real brand-colored tile (Qwen/OpenAI/DeepSeek/Meta/Mistral/Google + Anthropic/
GLM/Kimi/MiniMax/Nvidia/xAI); only genuinely-unknown providers get neutral
initials (honest, no fabricated trademark logos).
- Mobile: row hides the context column on phones + narrows numeric columns so
rows never overflow (mobile-first, $md restores the desktop layout).
Tests: 27 pass (brand 6 + families 21). tsc --noEmit clean.
The model catalog rendered logos from each model's raw provider string, so the
Zen family flip-flopped (models tagged 'hanzo' → block-H, others → ensō) and
every third-party family fell through to a gray initials chip ('QW'). Fixes:
- Rows + detail now render the model's FAMILY brand (not raw provider), so a
family is internally consistent: Zen is ALWAYS the ensō; Qwen/OpenAI/etc. each
show one mark. (Directive: Zen provider always uses Zen.)
- Extract pure brand resolution into ui/brand.ts (normalizeBrand + BRANDS
registry) — unit tested, no GUI deps. Every curated family key resolves to a
real brand-colored tile (Qwen/OpenAI/DeepSeek/Meta/Mistral/Google + Anthropic/
GLM/Kimi/MiniMax/Nvidia/xAI); only genuinely-unknown providers get neutral
initials (honest, no fabricated trademark logos).
- Mobile: row hides the context column on phones + narrows numeric columns so
rows never overflow (mobile-first, $md restores the desktop layout).
Tests: 27 pass (brand 6 + families 21). tsc --noEmit clean.
Replaces the 'Jobs' tab/JobsView (a bespoke async-tracker) with an Ingest surface over
the ONE /v1/docs/ingest endpoint: three real sources (pasted text · GitHub repo · website)
+ a target collection. Text indexes inline; a repo or crawl returns a durable hanzoai/tasks
workflow id and the UI links to the ONE Tasks product to track it ('Track in Tasks →',
/tasks/<org>/<wid>) — there is no second async system. Lower panel = the store's REAL
indexed files (get-files), reframed honestly as 'Indexed files' not a job log. Tab + subpage
renamed jobs→ingest. EmbeddingsApi gains ingestGitHub/ingestCrawl; IngestStats gains
async/workflowId. tsc clean.
Replaces the 'Jobs' tab/JobsView (a bespoke async-tracker) with an Ingest surface over
the ONE /v1/docs/ingest endpoint: three real sources (pasted text · GitHub repo · website)
+ a target collection. Text indexes inline; a repo or crawl returns a durable hanzoai/tasks
workflow id and the UI links to the ONE Tasks product to track it ('Track in Tasks →',
/tasks/<org>/<wid>) — there is no second async system. Lower panel = the store's REAL
indexed files (get-files), reframed honestly as 'Indexed files' not a job log. Tab + subpage
renamed jobs→ingest. EmbeddingsApi gains ingestGitHub/ingestCrawl; IngestStats gains
async/workflowId. tsc clean.
Replaces the cms.<brand> Payload iframe/Studio embed with a NATIVE, metadata-
driven surface over the LIVE /v1/framework/* DocType engine. Ships the DRY
foundation the ERP/CRM/Helpdesk lanes reuse: ONE generic framework client + ONE
generic DocType renderer (the 'one engine + one renderer renders every app' model).
- src/lib/framework/{types,client,fields}.ts — the ONE FrameworkApi client
(doctypes/records/modules/roles over the /cloud bearer proxy, allow-listed as
the new 'framework' head) + the pure mapper DocType metadata <-> @hanzo/data
FieldDefinition/record for EVERY fieldtype (relation/select/currency/attach/
check/datetime/…), relation label enrichment, slugify (URL-safe names),
publish/media/collection helpers. 32 pure unit tests.
- src/components/doctype/* — the generic renderer over @hanzo/data's RecordsView/
RecordDetail/RecordForm: CollectionsBrowser (module doctypes + first-run install
+ new-collection), DocTypeRecords (table, or the MediaGrid gallery for a media
doctype; inline edit sends the FULL validated body), DocTypeDetail (view/edit/
create/delete + publish/unpublish + submit/cancel). Zero per-doctype code.
- CmsModule.tsx is now a thin host scoping the generic renderer to module=cms.
- proxy-allow: the 'framework' head; registry: cms native routes, repo hanzoai/cloud.
Names are slug/hex only (slugify + isValidDoctypeName) so they are space-/%-free —
correct on the live engine AND through the console's own pathIsClean bearer proxy.
Per-org + honest-empty by construction: the engine enforces tenancy (principal.
Tenant) + per-DocType permissions server-side.
Cloud side (hanzoai/cloud): the CMS content model (Page/Post/Article/Media/
Navigation/Author, module 'cms') + the generic app-lane install
(POST /v1/framework/modules/cms/install).
Verify: tsc clean; vitest (framework 32); next build ✓ (14/14 pages).
Replaces the cms.<brand> Payload iframe/Studio embed with a NATIVE, metadata-
driven surface over the LIVE /v1/framework/* DocType engine. Ships the DRY
foundation the ERP/CRM/Helpdesk lanes reuse: ONE generic framework client + ONE
generic DocType renderer (the 'one engine + one renderer renders every app' model).
- src/lib/framework/{types,client,fields}.ts — the ONE FrameworkApi client
(doctypes/records/modules/roles over the /cloud bearer proxy, allow-listed as
the new 'framework' head) + the pure mapper DocType metadata <-> @hanzo/data
FieldDefinition/record for EVERY fieldtype (relation/select/currency/attach/
check/datetime/…), relation label enrichment, slugify (URL-safe names),
publish/media/collection helpers. 32 pure unit tests.
- src/components/doctype/* — the generic renderer over @hanzo/data's RecordsView/
RecordDetail/RecordForm: CollectionsBrowser (module doctypes + first-run install
+ new-collection), DocTypeRecords (table, or the MediaGrid gallery for a media
doctype; inline edit sends the FULL validated body), DocTypeDetail (view/edit/
create/delete + publish/unpublish + submit/cancel). Zero per-doctype code.
- CmsModule.tsx is now a thin host scoping the generic renderer to module=cms.
- proxy-allow: the 'framework' head; registry: cms native routes, repo hanzoai/cloud.
Names are slug/hex only (slugify + isValidDoctypeName) so they are space-/%-free —
correct on the live engine AND through the console's own pathIsClean bearer proxy.
Per-org + honest-empty by construction: the engine enforces tenancy (principal.
Tenant) + per-DocType permissions server-side.
Cloud side (hanzoai/cloud): the CMS content model (Page/Post/Article/Media/
Navigation/Author, module 'cms') + the generic app-lane install
(POST /v1/framework/modules/cms/install).
Verify: tsc clean; vitest (framework 32); next build ✓ (14/14 pages).
o11y's last two query signals — application LOGS and trace search — are the
composite POST /api/v3/query_range (GET /api/v1/logs is a stub). Added to the
existing ApmApi (DRY, one o11y client, same /cloud/v1/o11y/* convention as
ServiceMap + Alerts): logs()/traceSearch() + pure builders/parsers
(listQueryPayload, parseListRows, toIso, normalizeLogRow/Logs, normalizeTraceSpan/
Spans). LogsModule is now two real lenses — Application logs (live o11y logs,
range + severity/service filters, honest RuntimeNotice/empty states) and the
prior Request activity ledger lens (kept, always-real fallback). Traces/
Observations stay on /v1/evals (LLM domain), Metrics on VictoriaMetrics — no
regression. tsc 0 errors; vitest 1373/1373 (+13 apm); next build ✓.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
o11y's last two query signals — application LOGS and trace search — are the
composite POST /api/v3/query_range (GET /api/v1/logs is a stub). Added to the
existing ApmApi (DRY, one o11y client, same /cloud/v1/o11y/* convention as
ServiceMap + Alerts): logs()/traceSearch() + pure builders/parsers
(listQueryPayload, parseListRows, toIso, normalizeLogRow/Logs, normalizeTraceSpan/
Spans). LogsModule is now two real lenses — Application logs (live o11y logs,
range + severity/service filters, honest RuntimeNotice/empty states) and the
prior Request activity ledger lens (kept, always-real fallback). Traces/
Observations stay on /v1/evals (LLM domain), Metrics on VictoriaMetrics — no
regression. tsc 0 errors; vitest 1373/1373 (+13 apm); next build ✓.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The LaunchDrawer pre-fills a fun `adjective-animal` name (dark-llama, cosmic-axolotl,
turbo-wombat) so launch is click-and-go; a 🎲 button re-rolls it, it re-rolls after each
launch, and it stays fully editable. Pure curated word lists (src/lib/naming.ts), no deps.
tsc clean; vitest 1355/1355; next build ✓. Completes #43.
The LaunchDrawer pre-fills a fun `adjective-animal` name (dark-llama, cosmic-axolotl,
turbo-wombat) so launch is click-and-go; a 🎲 button re-rolls it, it re-rolls after each
launch, and it stays fully editable. Pure curated word lists (src/lib/naming.ts), no deps.
tsc clean; vitest 1355/1355; next build ✓. Completes #43.
Pre-fill the machine/GPU launch drawer's Name field with a Docker/Heroku-style
adjective-animal name (dark-llama, cosmic-axolotl, turbo-wombat) so a user can
click-and-go and rapid-launch. A 🎲 button re-rolls on demand, and the name
re-rolls after each successful launch so repeat-clicking Launch keeps getting a
fresh fun name. Still fully editable.
- src/lib/naming.ts — pure adjective-animal generator (curated lists, no deps);
randomName({ suffix }) adds a short base36 token only when uniqueness is needed.
- LaunchDrawer: lazy useState(randomName) auto-fills on mount; post-launch
re-roll (the drawer instance persists across the DetailPane close/reopen);
the 🎲 re-roll button sits beside the field.
The launch POST already carries this name (VisorApi.launch → /v1/machines/launch);
end-to-end launch is gated on the in-flight /v1/machines gateway route.
tsc clean; vitest 1279/1279 (+3 naming); next build ✓.
Pre-fill the machine/GPU launch drawer's Name field with a Docker/Heroku-style
adjective-animal name (dark-llama, cosmic-axolotl, turbo-wombat) so a user can
click-and-go and rapid-launch. A 🎲 button re-rolls on demand, and the name
re-rolls after each successful launch so repeat-clicking Launch keeps getting a
fresh fun name. Still fully editable.
- src/lib/naming.ts — pure adjective-animal generator (curated lists, no deps);
randomName({ suffix }) adds a short base36 token only when uniqueness is needed.
- LaunchDrawer: lazy useState(randomName) auto-fills on mount; post-launch
re-roll (the drawer instance persists across the DetailPane close/reopen);
the 🎲 re-roll button sits beside the field.
The launch POST already carries this name (VisorApi.launch → /v1/machines/launch);
end-to-end launch is gated on the in-flight /v1/machines gateway route.
tsc clean; vitest 1279/1279 (+3 naming); next build ✓.
A minimal, honest console for the per-org Hanzo PaaS — cloud's native
/v1/platform control plane (hanzoai/cloud clients/platform). A signed-in org
member manages their OWN container apps: list + live status, deploy/stop/start,
source-tagged deployment logs (cloud#75), KMS-sealed env (secret values ALWAYS
masked), and verified custom domains (DNS challenge records + Verify).
DISTINCT from the admin `applications` fleet board (/v1/apps) and from
internal-admin platform.hanzo.ai. Org-scoped by the Bearer owner via the /cloud
bearer proxy (the raw session cookie never reaches cloud-api).
- lib/api/platform-apps.ts — typed plain-REST client for /v1/platform/* over
originV1Url → /cloud proxy (`platform` already allow-listed in proxy-allow.ts;
added to next.config CLOUD_V1_HEADS so /v1/platform/* rewrites to /cloud).
- components/products/PlatformAppsModule.tsx — list + SlideOver detail
(overview/deploy, env masked, domains + verify, source-tagged logs). Honest
states throughout: Loader, EmptyState (create-via-CLI), BackendStateCard for a
/v1 failure — never fabricated rows.
- components/products/platform-apps/logic.ts (+ .test.ts, 9 tests) — pure view
logic; maskedEnvRows ASSERTS a secret's plaintext never renders.
- registry: one new 'app-platform' Compute entry.
Verify: tsc --noEmit clean, vitest 1343/1343, next build ✓ compiled. Authed
visual e2e is post-deploy (console convention).
A minimal, honest console for the per-org Hanzo PaaS — cloud's native
/v1/platform control plane (hanzoai/cloud clients/platform). A signed-in org
member manages their OWN container apps: list + live status, deploy/stop/start,
source-tagged deployment logs (cloud#75), KMS-sealed env (secret values ALWAYS
masked), and verified custom domains (DNS challenge records + Verify).
DISTINCT from the admin `applications` fleet board (/v1/apps) and from
internal-admin platform.hanzo.ai. Org-scoped by the Bearer owner via the /cloud
bearer proxy (the raw session cookie never reaches cloud-api).
- lib/api/platform-apps.ts — typed plain-REST client for /v1/platform/* over
originV1Url → /cloud proxy (`platform` already allow-listed in proxy-allow.ts;
added to next.config CLOUD_V1_HEADS so /v1/platform/* rewrites to /cloud).
- components/products/PlatformAppsModule.tsx — list + SlideOver detail
(overview/deploy, env masked, domains + verify, source-tagged logs). Honest
states throughout: Loader, EmptyState (create-via-CLI), BackendStateCard for a
/v1 failure — never fabricated rows.
- components/products/platform-apps/logic.ts (+ .test.ts, 9 tests) — pure view
logic; maskedEnvRows ASSERTS a secret's plaintext never renders.
- registry: one new 'app-platform' Compute entry.
Verify: tsc --noEmit clean, vitest 1343/1343, next build ✓ compiled. Authed
visual e2e is post-deploy (console convention).
The same-origin CSRF guard (`sameOriginOK`) was enforced ONLY inside the shared
`forwardWithUserBearer` (the user-bearer proxies: /cloud, /ai, /vm, /commerce,
/cms, /superbase, /tasksd, /admin/aggregate). Every HAND-ROLLED cookie-auth
mutating route lacked it — so a cross-site page carrying the victim's auto-sent
cookie could drive a state change: KMS secret create/rotate/delete (/admin/kms),
PaaS control-plane deploy/scale/delete (/paas), IAM user/org/project mutations
(/admin/iam, /org/iam), billing writes + wallet credit, key mint/revoke, org
onboard, waitlist join, login/logout. `hz_session` is SameSite=Lax, but the
fallback casibase cookie's SameSite is not controlled by the console — so this
defense-in-depth guard is required, not optional.
Decomplected into ONE guard, `csrfRefusal(req, shape)` (co-located with the pure
`sameOriginOK` in bearer-proxy.ts): null on a same-origin request or a safe
method, else a fail-closed 403 in the caller's error envelope. Reads only headers
(never the body), so it composes before any req.text()/json(). `forwardWithUserBearer`
now calls it too — one policy, one place, applied to the WHOLE BFF.
Applied at the top of: forwardIam (→ /admin/iam + /org/iam), /admin/kms, /paas,
/billing/v1, /billing/v1/topup/wallet, /training, /keys, /onboard, /waitlist,
/auth/{session,refresh,signup}.
Also hardened, same "never trust the client" principle:
- /training now server-resolves X-Org-Id via `orgFor` (pins a non-global admin to
their own org) instead of forwarding the raw browser header — matches /paas +
/admin/kms, so a brand admin can't drive another tenant's training jobs even if
the backend trusted the forwarded header.
- /billing/v1/topup/wallet now requires a session (`resolveUser`) and credits the
SERVER-RESOLVED billing subject, never the client-supplied `userId` (which let a
caller credit an arbitrary account); stamps X-Org-Id for correct ledger
namespacing. (Commerce must still dedupe on (network, txHash) — RED handoff.)
Tests: +6 csrfRefusal cases; full suite 1340 passing, tsc --noEmit clean.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The same-origin CSRF guard (`sameOriginOK`) was enforced ONLY inside the shared
`forwardWithUserBearer` (the user-bearer proxies: /cloud, /ai, /vm, /commerce,
/cms, /superbase, /tasksd, /admin/aggregate). Every HAND-ROLLED cookie-auth
mutating route lacked it — so a cross-site page carrying the victim's auto-sent
cookie could drive a state change: KMS secret create/rotate/delete (/admin/kms),
PaaS control-plane deploy/scale/delete (/paas), IAM user/org/project mutations
(/admin/iam, /org/iam), billing writes + wallet credit, key mint/revoke, org
onboard, waitlist join, login/logout. `hz_session` is SameSite=Lax, but the
fallback casibase cookie's SameSite is not controlled by the console — so this
defense-in-depth guard is required, not optional.
Decomplected into ONE guard, `csrfRefusal(req, shape)` (co-located with the pure
`sameOriginOK` in bearer-proxy.ts): null on a same-origin request or a safe
method, else a fail-closed 403 in the caller's error envelope. Reads only headers
(never the body), so it composes before any req.text()/json(). `forwardWithUserBearer`
now calls it too — one policy, one place, applied to the WHOLE BFF.
Applied at the top of: forwardIam (→ /admin/iam + /org/iam), /admin/kms, /paas,
/billing/v1, /billing/v1/topup/wallet, /training, /keys, /onboard, /waitlist,
/auth/{session,refresh,signup}.
Also hardened, same "never trust the client" principle:
- /training now server-resolves X-Org-Id via `orgFor` (pins a non-global admin to
their own org) instead of forwarding the raw browser header — matches /paas +
/admin/kms, so a brand admin can't drive another tenant's training jobs even if
the backend trusted the forwarded header.
- /billing/v1/topup/wallet now requires a session (`resolveUser`) and credits the
SERVER-RESOLVED billing subject, never the client-supplied `userId` (which let a
caller credit an arbitrary account); stamps X-Org-Id for correct ledger
namespacing. (Commerce must still dedupe on (network, txHash) — RED handoff.)
Tests: +6 csrfRefusal cases; full suite 1340 passing, tsc --noEmit clean.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Retire the remaining standalone Next server routes so the console is a pure
static SPA calling same-origin /v1/console/* (served by the go:embed one-binary,
routed through the gateway in the split deploy — one way, both topologies):
- waitlist, embed-status, billing/v1/topup/wallet -> ported to cloud
/v1/console/{waitlist,embed-status,topup/wallet} (real server work: Go
handlers land in hanzoai/cloud).
- keys, onboard -> repointed to the already-merged cloud /v1/console/{keys,
onboard} (completes cloud#74's console side; they were still calling the old
/keys,/onboard handlers, which broke under the static export).
- docs -> a client redirect page (app/docs/page.tsx): a host->docsUrl map the
browser already has (config.docsUrl); no server work, so no handler. Resolves
the brand in an effect (no SSR/CSR hydration mismatch). Replaces the 308
route the static export cannot run.
All calls go through the central client's v1Url() (config.cloudUrl, same-origin),
so the error envelope, cookie creds, and retry/refresh are unchanged. The ported
route.ts handlers are deleted (build:embed already stashed every route.ts; these
simply no longer exist).
Verified: tsc --noEmit clean; vitest 1334/1334 green; `npm run build:embed`
emits the full static out/ (real @hanzo/gui bundle, /docs prerendered).
NOTE: deploy the cloud image carrying the /v1/console/* handlers BEFORE this
console build (the SPA now depends on them). The remaining BFF proxies
(/cloud,/ai,/commerce,/billing catch-alls) are a separate, larger repoint for
full embed functionality and are out of this change's scope.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Retire the remaining standalone Next server routes so the console is a pure
static SPA calling same-origin /v1/console/* (served by the go:embed one-binary,
routed through the gateway in the split deploy — one way, both topologies):
- waitlist, embed-status, billing/v1/topup/wallet -> ported to cloud
/v1/console/{waitlist,embed-status,topup/wallet} (real server work: Go
handlers land in hanzoai/cloud).
- keys, onboard -> repointed to the already-merged cloud /v1/console/{keys,
onboard} (completes cloud#74's console side; they were still calling the old
/keys,/onboard handlers, which broke under the static export).
- docs -> a client redirect page (app/docs/page.tsx): a host->docsUrl map the
browser already has (config.docsUrl); no server work, so no handler. Resolves
the brand in an effect (no SSR/CSR hydration mismatch). Replaces the 308
route the static export cannot run.
All calls go through the central client's v1Url() (config.cloudUrl, same-origin),
so the error envelope, cookie creds, and retry/refresh are unchanged. The ported
route.ts handlers are deleted (build:embed already stashed every route.ts; these
simply no longer exist).
Verified: tsc --noEmit clean; vitest 1334/1334 green; `npm run build:embed`
emits the full static out/ (real @hanzo/gui bundle, /docs prerendered).
NOTE: deploy the cloud image carrying the /v1/console/* handlers BEFORE this
console build (the SPA now depends on them). The remaining BFF proxies
(/cloud,/ai,/commerce,/billing catch-alls) are a separate, larger repoint for
full embed functionality and are out of this change's scope.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Replace the external-portal / HUSD-only dead-end with a real card top-up IN the
console. 'Add credits' (BillingOverview, HomeSummary), 'Top up' (SidebarWallet),
and the Billing → Credits tab now open /billing/credits: a Square Web Payments
card form that credits the org's canonical cloud-credit balance — the SAME ledger
the gateway debits for AI usage.
- BillingCredits.tsx: amount picker + Square card iframe (PCI SAQ-A — the PAN is
entered into Square's iframe and tokenized in-browser; we only ever hold the
single-use nonce). Pay → POST /billing/v1/topup/token via the same-origin proxy
(service token + server-pinned subject) → commerce charges + credits the org.
Button locks in-flight (no double-submit); nonce is single-use (no double-charge);
honest states (config-unavailable, decline, success). Sandbox badge + test-card
hint when the deployment is Square sandbox.
- lib/billing/square.ts: typed Web Payments SDK surface, fail-safe env→CDN map
(non-'production' → sandbox tokenizer), pure amount validators, idempotent loader.
- BillingApi.paymentConfig() + topupWithCard() over the existing /billing/v1 proxy.
- HUSD crypto stays a secondary option (link to /wallet); no external billing.hanzo.ai.
Tests: square.test.ts (11) green; tsc strict + next build clean; full suite 1324 green.
Replace the external-portal / HUSD-only dead-end with a real card top-up IN the
console. 'Add credits' (BillingOverview, HomeSummary), 'Top up' (SidebarWallet),
and the Billing → Credits tab now open /billing/credits: a Square Web Payments
card form that credits the org's canonical cloud-credit balance — the SAME ledger
the gateway debits for AI usage.
- BillingCredits.tsx: amount picker + Square card iframe (PCI SAQ-A — the PAN is
entered into Square's iframe and tokenized in-browser; we only ever hold the
single-use nonce). Pay → POST /billing/v1/topup/token via the same-origin proxy
(service token + server-pinned subject) → commerce charges + credits the org.
Button locks in-flight (no double-submit); nonce is single-use (no double-charge);
honest states (config-unavailable, decline, success). Sandbox badge + test-card
hint when the deployment is Square sandbox.
- lib/billing/square.ts: typed Web Payments SDK surface, fail-safe env→CDN map
(non-'production' → sandbox tokenizer), pure amount validators, idempotent loader.
- BillingApi.paymentConfig() + topupWithCard() over the existing /billing/v1 proxy.
- HUSD crypto stays a secondary option (link to /wallet); no external billing.hanzo.ai.
Tests: square.test.ts (11) green; tsc strict + next build clean; full suite 1324 green.
next build's strict type-check (onlyShorthandStyleProps) rejects the maxWidth
longhand on a Stack; tsc --noEmit did not surface it. Also relabel the route
honestly (it is a reachable design-reference, not 'not shipped').
(cherry picked from commit 9ce0625ce413e8c3e52eaadddd327c0d2f30a759)
next build's strict type-check (onlyShorthandStyleProps) rejects the maxWidth
longhand on a Stack; tsc --noEmit did not surface it. Also relabel the route
honestly (it is a reachable design-reference, not 'not shipped').
(cherry picked from commit 9ce0625ce413e8c3e52eaadddd327c0d2f30a759)
Five "advertised-but-broken" surfaces the live E2E suite flagged, fixed honestly
in the client (no fabrication):
- Vector module rendered nothing: normalizeResourceList validates + unwraps the
provisioning list at the transport boundary (bare array, or a
data/items/results/resources/collections/list/rows wrapper incl. one level of
nesting e.g. Qdrant result.collections), honest [] fallback. A wrapped 200 body
was reaching the list view's for..of and throwing behind the error boundary while
SQL/KV (bare arrays) rendered. ONE place, every kind.
- /chat reply now STREAMS token-by-token via AiApi.ragChatStream (grounded RAG
headers ride PlaygroundApi.streamChat). SSE parser canonical home moved to
lib/api/stream.ts (one definition, re-exported from playground/stream.ts). The
error card's Retry now re-runs the last user turn (was a no-op).
- Functions list self-freshens: useReloadOnFocus refetches on window focus /
tab-visible so an API/CLI-deployed function appears without a reload; + Refresh.
- Sign-out redirects deterministically to /signin after DELETE /auth/session
(AuthGate's reactive redirect could be pre-empted by an in-flight session
re-hydrate, stranding the user on /).
- CRM summary rollup lag is BACKEND (materialized rollup eventual consistency);
the console already refetches /v1/crm/summary after every create/delete —
flagged, NOT faked.
tsc --noEmit clean · vitest 1290/1290 (3 new suites) · next build ok.
Five "advertised-but-broken" surfaces the live E2E suite flagged, fixed honestly
in the client (no fabrication):
- Vector module rendered nothing: normalizeResourceList validates + unwraps the
provisioning list at the transport boundary (bare array, or a
data/items/results/resources/collections/list/rows wrapper incl. one level of
nesting e.g. Qdrant result.collections), honest [] fallback. A wrapped 200 body
was reaching the list view's for..of and throwing behind the error boundary while
SQL/KV (bare arrays) rendered. ONE place, every kind.
- /chat reply now STREAMS token-by-token via AiApi.ragChatStream (grounded RAG
headers ride PlaygroundApi.streamChat). SSE parser canonical home moved to
lib/api/stream.ts (one definition, re-exported from playground/stream.ts). The
error card's Retry now re-runs the last user turn (was a no-op).
- Functions list self-freshens: useReloadOnFocus refetches on window focus /
tab-visible so an API/CLI-deployed function appears without a reload; + Refresh.
- Sign-out redirects deterministically to /signin after DELETE /auth/session
(AuthGate's reactive redirect could be pre-empted by an in-flight session
re-hydrate, stranding the user on /).
- CRM summary rollup lag is BACKEND (materialized rollup eventual consistency);
the console already refetches /v1/crm/summary after every create/delete —
flagged, NOT faked.
tsc --noEmit clean · vitest 1290/1290 (3 new suites) · next build ok.
Integrates the Basel Grotesk (UI) + Geist Mono (code) typography pass with the
family model-browser blank-row fix. Strict superset of v8.4.52.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Integrates the Basel Grotesk (UI) + Geist Mono (code) typography pass with the
family model-browser blank-row fix. Strict superset of v8.4.52.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The Zen family showed two nameless rows: the gateway's meta-routers (router:general,
…) bucket into Zen by provider but carry no display name, and modelDisplayName
returns '' when a record has no name. Fix both: isChatModel now excludes router:*
(a routing policy, not a pickable model — it lives in the Routing tab), and the row
label falls back to the raw id when there's no display name (displayLabel). 21 unit
tests (router exclusion + never-blank label).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Zen family showed two nameless rows: the gateway's meta-routers (router:general,
…) bucket into Zen by provider but carry no display name, and modelDisplayName
returns '' when a record has no name. Fix both: isChatModel now excludes router:*
(a routing policy, not a pickable model — it lives in the Routing tab), and the row
label falls back to the raw id when there's no display name (displayLabel). 21 unit
tests (router exclusion + never-blank label).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Converge the console onto the canonical Hanzo typography without ripping the
Tamagui mechanism:
- Self-host Basel Grotesk (Book 400 + Medium 500) via @font-face in
app/globals.css and override the @hanzo/gui (Tamagui) v5 body + heading font
family to 'Basel' in gui.config.ts, so every Text/Paragraph/H* renders Basel
(one place, whole product). Replaces the default system-font stack.
- Geist Mono for code/data via CDN import + a code/pre/kbd/samp rule.
Sidebar toggle (lucide PanelLeft) + true-black tokens already shipped.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Converge the console onto the canonical Hanzo typography without ripping the
Tamagui mechanism:
- Self-host Basel Grotesk (Book 400 + Medium 500) via @font-face in
app/globals.css and override the @hanzo/gui (Tamagui) v5 body + heading font
family to 'Basel' in gui.config.ts, so every Text/Paragraph/H* renders Basel
(one place, whole product). Replaces the default system-font stack.
- Geist Mono for code/data via CDN import + a code/pre/kbd/samp rule.
Sidebar toggle (lucide PanelLeft) + true-black tokens already shipped.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Release: the Models module is now the unified, family-grouped model browser at
chat parity (Zen first + Qwen/Meta Llama/DeepSeek/Mistral/Google Gemma/OpenAI
GPT-OSS), true-black surface-depth ladder, skeleton loading, tabular numerals
across all metric cards + the model browser.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Release: the Models module is now the unified, family-grouped model browser at
chat parity (Zen first + Qwen/Meta Llama/DeepSeek/Mistral/Google Gemma/OpenAI
GPT-OSS), true-black surface-depth ladder, skeleton loading, tabular numerals
across all metric cards + the model browser.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
CTO design bar (Linear/Vercel/Stripe): elevate the flagship model surface and the
whole shell's depth.
- Surface depth ladder over true-black: $color1 #050505 (resting panels), $color2
#0a0a0a, $color3/$color4 #171717/#1f1f1f (interactive/elevated). Cards now read
with real depth over the #000 canvas instead of flat black — applied globally, so
every panel (agents, metrics, cards) gains the same layering. Text-contrast scale
($color10–12) untouched.
- Model browser: designed skeleton loading (shimmer family cards, no spinner),
staggered fade-in entrance (40ms), tabular numerals on every numeric column
(context / $-per-Mtok / counts / stats) so figures align, hairline stat dividers,
tighter type scale (family $5/800, stat $7/800 -0.5 tracking, uppercase labels),
crisp hover rows, and a proper icon empty state.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
CTO design bar (Linear/Vercel/Stripe): elevate the flagship model surface and the
whole shell's depth.
- Surface depth ladder over true-black: $color1 #050505 (resting panels), $color2
#0a0a0a, $color3/$color4 #171717/#1f1f1f (interactive/elevated). Cards now read
with real depth over the #000 canvas instead of flat black — applied globally, so
every panel (agents, metrics, cards) gains the same layering. Text-contrast scale
($color10–12) untouched.
- Model browser: designed skeleton loading (shimmer family cards, no spinner),
staggered fade-in entrance (40ms), tabular numerals on every numeric column
(context / $-per-Mtok / counts / stats) so figures align, hairline stat dividers,
tighter type scale (family $5/800, stat $7/800 -0.5 tracking, uppercase labels),
crisp hover rows, and a proper icon empty state.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The <html> inline background and viewport themeColor were still #0a0a0a — a hair
off the true-black the .t_dark CSS override paints. Match them to #000000 so the
very first paint (before CSS) and the mobile browser chrome are pure black too,
consistent with hanzo.ai + hanzo.chat.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The <html> inline background and viewport themeColor were still #0a0a0a — a hair
off the true-black the .t_dark CSS override paints. Match them to #000000 so the
very first paint (before CSS) and the mobile browser chrome are pure black too,
consistent with hanzo.ai + hanzo.chat.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Replace the flat 444-row catalog table with a family-grouped browser matching
hanzo.chat's picker exactly: collapsible sections per family — Zen first (with
zen5-mini flagged Default), then Qwen · Meta Llama · DeepSeek · Mistral · Google
Gemma · OpenAI GPT-OSS — each nesting its current-gen chat models with real
context, $/Mtok price, and live-vs-catalog availability. Click a model for the
full specs/pricing/features detail panel (unchanged). Search filters across every
family; a stats strip shows families / models / available-now. Reuses ProviderLogo
+ formatters; grouping is the pure, unit-tested groupByFamily. One console home for
model selection, the same families the user sees in chat.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Replace the flat 444-row catalog table with a family-grouped browser matching
hanzo.chat's picker exactly: collapsible sections per family — Zen first (with
zen5-mini flagged Default), then Qwen · Meta Llama · DeepSeek · Mistral · Google
Gemma · OpenAI GPT-OSS — each nesting its current-gen chat models with real
context, $/Mtok price, and live-vs-catalog availability. Click a model for the
full specs/pricing/features detail panel (unchanged). Search filters across every
family; a stats strip shows families / models / available-now. Reuses ProviderLogo
+ formatters; grouping is the pure, unit-tested groupByFamily. One console home for
model selection, the same families the user sees in chat.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The unified model browser groups the live catalog into hanzo.chat's exact 7
families — Zen (house brand) first, then Qwen · Meta Llama · DeepSeek · Mistral ·
Google Gemma · OpenAI GPT-OSS. Data-driven from /v1/pricing/models joined with
/v1/models: provider-defined families match the provider string; the named slices
(Gemma ⊂ Google, GPT-OSS ⊂ OpenAI) match an id slice, so provider-grouping's
Gemini/GPT-5 noise and the HuggingFace hub mirror stay out. Current-gen chat only
(drops zen4/qwen2 sunset gens + embedding/rerank/tts/asr/image/guard modalities +
:free dup aliases). Empty families are dropped — honest to what the gateway serves.
fetchCatalog now merges live-only models the older pricing bundle omits (the
current Zen set: zen5-flash/coder/nano-*), deduped by id and name, marked Available.
Pure + unit-tested (19 cases): chat-exact curation, distill disambiguation, slice
matching, sunset filtering, Zen-first ordering, zen5-mini default.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The unified model browser groups the live catalog into hanzo.chat's exact 7
families — Zen (house brand) first, then Qwen · Meta Llama · DeepSeek · Mistral ·
Google Gemma · OpenAI GPT-OSS. Data-driven from /v1/pricing/models joined with
/v1/models: provider-defined families match the provider string; the named slices
(Gemma ⊂ Google, GPT-OSS ⊂ OpenAI) match an id slice, so provider-grouping's
Gemini/GPT-5 noise and the HuggingFace hub mirror stay out. Current-gen chat only
(drops zen4/qwen2 sunset gens + embedding/rerank/tts/asr/image/guard modalities +
:free dup aliases). Empty families are dropped — honest to what the gateway serves.
fetchCatalog now merges live-only models the older pricing bundle omits (the
current Zen set: zen5-flash/coder/nano-*), deduped by id and name, marked Available.
Pure + unit-tested (19 cases): chat-exact curation, distill disambiguation, slice
matching, sunset filtering, Zen-first ordering, zen5-mini default.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
`output: 'export'` prerenders every page THROUGH app/layout.tsx, whose
generateMetadata reads the Host header (next/headers `headers()`) to brand the
SSR <title> per host. A static export has no request, so that request-time read
throws in the Server Components render for ALL pages — the export aborted on
/_not-found (and /signin), so `npm run build:embed` emitted no out/ and the
hanzoai/cloud one-binary silently shipped the fallback shell instead of the real
console.
build-embed.mjs now, for the export ONLY, drops the layout's next/headers import
and resolves the host to undefined (→ the build-time default brand; the embed is
same-origin and re-resolves the real brand client-side from window.location),
then restores the pristine layout in the finally. The normal `npm run build`
(server build, per-host SSR <title>) is untouched.
Verified: build:embed now emits out/ (index.html ~369 KB, /_next/static
assets); app/layout.tsx is restored to pristine after the run.
`output: 'export'` prerenders every page THROUGH app/layout.tsx, whose
generateMetadata reads the Host header (next/headers `headers()`) to brand the
SSR <title> per host. A static export has no request, so that request-time read
throws in the Server Components render for ALL pages — the export aborted on
/_not-found (and /signin), so `npm run build:embed` emitted no out/ and the
hanzoai/cloud one-binary silently shipped the fallback shell instead of the real
console.
build-embed.mjs now, for the export ONLY, drops the layout's next/headers import
and resolves the host to undefined (→ the build-time default brand; the embed is
same-origin and re-resolves the real brand client-side from window.location),
then restores the pristine layout in the finally. The normal `npm run build`
(server build, per-host SSR <title>) is untouched.
Verified: build:embed now emits out/ (index.html ~369 KB, /_next/static
assets); app/layout.tsx is restored to pristine after the run.
* feat(console): admin AI-provider control board — enable/disable + set-primary over gated /v1/admin/providers
Adds the platform-wide provider MANAGEMENT dashboard (admin.hanzo.ai) for the
shared-gateway upstream providers (do-ai, openrouter, fireworks, openai-direct,
zen): one row per provider with a working Enabled toggle, a Primary badge +
Make-primary action, model count, a key present/missing pill (NEVER the key),
and an honest DERIVED health verdict (enabled+keyPresent=Ready, enabled+no-key=
No key, disabled=Off — labeled derived, not a live probe). DISTINCT from the
customer 'providers' catalog entry (model catalog + BYOK per-org CRUD).
Server: 'providers' added to the global-admin-gated admin-aggregate heads
(ADMIN_AGGREGATE_HEADS + next.config ADMIN_V1_HEADS); the aggregate route now
exports POST (same getAdminGate fail-closed 403 + same-origin CSRF the shared
forwardWithUserBearer already enforces on any mutating method — no new trust
boundary). New originPost in client.ts pins the mutation to the console's OWN
origin so a split-origin NEXT_PUBLIC_CLOUD_URL can't route around the gate.
Client: typed ProviderAdminApi (list/toggle/setPrimary) + optional-safe
normalizers + a pure deriveHealth. keyPresent is strict-true (fail-closed — a
provider key is never modeled or surfaced).
Integration flag: disabling OpenRouter here also gates it out of the pricing
catalog (the DO-first ENABLE_OPENROUTER sync reads provider-enabled state).
Tests: provider-admin.test.ts (deriveHealth matrix, normalizer key-leak
safety, same-origin /v1/admin/providers URL shape for GET+POST, never the
cloud host) + admin-aggregate providers head. tsc --noEmit clean; vitest
1179/1179 (97 files); next build clean (17/17, /admin/aggregate + /[...slug]
registered). Authenticated visual e2e is post-deploy.
* fix(console): admin-aggregate proxy targets cloud /v1/admin/* (integration-path fix)
The console admin-aggregate proxy (app/admin/aggregate/[...path]/route.ts) rebuilt
the upstream path as `admin/<head>` and forwarded it verbatim to CLOUD_API_URL (an
origin, no /v1), so a browser call to /v1/admin/providers hit
cloud-api.hanzo.svc:8000/admin/providers. But cloud serves EVERY admin route under
/v1/admin/* (hanzoai/ai's `/v1/*` beego glob for /v1/admin/providers{,/toggle,/primary};
cloud's own clients/admin `app.Get("/v1/admin/{overview,finance,compute,...}")`). There
is no bare /admin/* route → the provider dashboard's list/toggle/primary all 404'd.
(The overview/finance/compute boards masked the same mis-path behind LivingOverview's
honest usage-ledger fallback; provider-admin has no fallback, so it was visibly broken.)
Fix (server-side upstream path only; the browser-facing clean /v1/admin/* is unchanged):
- route.ts: build `v1/admin/<head>` (was `admin/<head>`) so the verbatim forward lands
on cloud's real /v1/admin/* route. The rewrite destination (/admin/aggregate/<head>)
is the internal Next route and correctly carries no /v1/ — this handler adds it.
- admin-aggregate.ts allowAdminSurface: validate the exact forwarded shape
`v1/admin/<allowed-head>` (segs[0]==='v1' && segs[1]==='admin' && ALLOWED.has(segs[2])),
refusing v1/admin/iam, v1/admin/kms, bare v1/admin, the pre-fix bare admin/<head>, and
every traversal. The two-layer pathIsClean + allow-list defense (raw AND WHATWG-normalized
path) is intact on the new shape: v1/admin/providers/../iam is refused at layer 1 (literal
..) and its normalized form v1/admin/iam at layer 2 (iam not allowed).
Beneficial side-effect: overview/finance/compute/orgs/audit/products/usage now also target
/v1/admin/* correctly (all shared this one proxy). next.config.mjs is untouched — its rewrite
already fires for every ADMIN_V1_HEAD incl providers, GET and POST.
Also (RED LOW-1): ProviderAdminModule toggle no longer flips the row optimistically before
the server confirms — a slow 403 never briefly renders an unauthorized 'on'; the enabled
state changes ONLY on a 2xx (the switch is disabled via `busy` in flight).
Tests: admin-aggregate.test.ts rewritten to the v1/admin/<head> shape (+ refuses the
pre-fix bare admin/<head>); bearer-proxy.test.ts +7 end-to-end forward tests proving the
upstream URL is cloud/v1/admin/providers (not /admin/providers), GET+POST forward, and
traversal / iam / kms 404 without ever fetching. tsc --noEmit clean; vitest 1187/1187
(97 files); next build ✓ (/admin/aggregate/[...path] registered).
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
* feat(console): admin AI-provider control board — enable/disable + set-primary over gated /v1/admin/providers
Adds the platform-wide provider MANAGEMENT dashboard (admin.hanzo.ai) for the
shared-gateway upstream providers (do-ai, openrouter, fireworks, openai-direct,
zen): one row per provider with a working Enabled toggle, a Primary badge +
Make-primary action, model count, a key present/missing pill (NEVER the key),
and an honest DERIVED health verdict (enabled+keyPresent=Ready, enabled+no-key=
No key, disabled=Off — labeled derived, not a live probe). DISTINCT from the
customer 'providers' catalog entry (model catalog + BYOK per-org CRUD).
Server: 'providers' added to the global-admin-gated admin-aggregate heads
(ADMIN_AGGREGATE_HEADS + next.config ADMIN_V1_HEADS); the aggregate route now
exports POST (same getAdminGate fail-closed 403 + same-origin CSRF the shared
forwardWithUserBearer already enforces on any mutating method — no new trust
boundary). New originPost in client.ts pins the mutation to the console's OWN
origin so a split-origin NEXT_PUBLIC_CLOUD_URL can't route around the gate.
Client: typed ProviderAdminApi (list/toggle/setPrimary) + optional-safe
normalizers + a pure deriveHealth. keyPresent is strict-true (fail-closed — a
provider key is never modeled or surfaced).
Integration flag: disabling OpenRouter here also gates it out of the pricing
catalog (the DO-first ENABLE_OPENROUTER sync reads provider-enabled state).
Tests: provider-admin.test.ts (deriveHealth matrix, normalizer key-leak
safety, same-origin /v1/admin/providers URL shape for GET+POST, never the
cloud host) + admin-aggregate providers head. tsc --noEmit clean; vitest
1179/1179 (97 files); next build clean (17/17, /admin/aggregate + /[...slug]
registered). Authenticated visual e2e is post-deploy.
* fix(console): admin-aggregate proxy targets cloud /v1/admin/* (integration-path fix)
The console admin-aggregate proxy (app/admin/aggregate/[...path]/route.ts) rebuilt
the upstream path as `admin/<head>` and forwarded it verbatim to CLOUD_API_URL (an
origin, no /v1), so a browser call to /v1/admin/providers hit
cloud-api.hanzo.svc:8000/admin/providers. But cloud serves EVERY admin route under
/v1/admin/* (hanzoai/ai's `/v1/*` beego glob for /v1/admin/providers{,/toggle,/primary};
cloud's own clients/admin `app.Get("/v1/admin/{overview,finance,compute,...}")`). There
is no bare /admin/* route → the provider dashboard's list/toggle/primary all 404'd.
(The overview/finance/compute boards masked the same mis-path behind LivingOverview's
honest usage-ledger fallback; provider-admin has no fallback, so it was visibly broken.)
Fix (server-side upstream path only; the browser-facing clean /v1/admin/* is unchanged):
- route.ts: build `v1/admin/<head>` (was `admin/<head>`) so the verbatim forward lands
on cloud's real /v1/admin/* route. The rewrite destination (/admin/aggregate/<head>)
is the internal Next route and correctly carries no /v1/ — this handler adds it.
- admin-aggregate.ts allowAdminSurface: validate the exact forwarded shape
`v1/admin/<allowed-head>` (segs[0]==='v1' && segs[1]==='admin' && ALLOWED.has(segs[2])),
refusing v1/admin/iam, v1/admin/kms, bare v1/admin, the pre-fix bare admin/<head>, and
every traversal. The two-layer pathIsClean + allow-list defense (raw AND WHATWG-normalized
path) is intact on the new shape: v1/admin/providers/../iam is refused at layer 1 (literal
..) and its normalized form v1/admin/iam at layer 2 (iam not allowed).
Beneficial side-effect: overview/finance/compute/orgs/audit/products/usage now also target
/v1/admin/* correctly (all shared this one proxy). next.config.mjs is untouched — its rewrite
already fires for every ADMIN_V1_HEAD incl providers, GET and POST.
Also (RED LOW-1): ProviderAdminModule toggle no longer flips the row optimistically before
the server confirms — a slow 403 never briefly renders an unauthorized 'on'; the enabled
state changes ONLY on a 2xx (the switch is disabled via `busy` in flight).
Tests: admin-aggregate.test.ts rewritten to the v1/admin/<head> shape (+ refuses the
pre-fix bare admin/<head>); bearer-proxy.test.ts +7 end-to-end forward tests proving the
upstream URL is cloud/v1/admin/providers (not /admin/providers), GET+POST forward, and
traversal / iam / kms 404 without ever fetching. tsc --noEmit clean; vitest 1187/1187
(97 files); next build ✓ (/admin/aggregate/[...path] registered).
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Bump past the live v8.4.50 so the true-black change ships as a clean immutable
semver tag (SEMVER-only build; a branch build without a bump collides with an
existing tag).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Bump past the live v8.4.50 so the true-black change ships as a clean immutable
semver tag (SEMVER-only build; a branch build without a bump collides with an
existing tag).
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
New 'Service Map' product (Observe) over the real o11y/SigNoz APM controllers
via the same-origin /cloud user-bearer proxy: /v1/o11y/v1/services (RED per
service), /dependency_graph (call edges), /service/top_operations. Every KPI/
row/edge folds over what the runtime returned — honest empty/RuntimeNotice on
503/404/403/401, never fabricated APM data. Tap a service row → detail rail
(RED overview, top operations, up/downstream deps).
- lib/api/apm.ts: ApmApi client + normalizers (services/deps/ops/hosts/pods/
nodes/exceptions/dashboards) with a stable ApmWindow.
- observability/apm-format.ts: pure RED/number/duration formatters.
- ServiceMapModule.tsx: the mounted module; wired into registry as 'service-map'.
- index.ts: barrel exports (apm NodeRow aliased ApmNodeRow — distinct from the
blockchain nodes.ts NodeRow).
Verified: 35/35 tests pass, tsc --noEmit clean (0 errors).
New 'Service Map' product (Observe) over the real o11y/SigNoz APM controllers
via the same-origin /cloud user-bearer proxy: /v1/o11y/v1/services (RED per
service), /dependency_graph (call edges), /service/top_operations. Every KPI/
row/edge folds over what the runtime returned — honest empty/RuntimeNotice on
503/404/403/401, never fabricated APM data. Tap a service row → detail rail
(RED overview, top operations, up/downstream deps).
- lib/api/apm.ts: ApmApi client + normalizers (services/deps/ops/hosts/pods/
nodes/exceptions/dashboards) with a stable ApmWindow.
- observability/apm-format.ts: pure RED/number/duration formatters.
- ServiceMapModule.tsx: the mounted module; wired into registry as 'service-map'.
- index.ts: barrel exports (apm NodeRow aliased ApmNodeRow — distinct from the
blockchain nodes.ts NodeRow).
Verified: 35/35 tests pass, tsc --noEmit clean (0 errors).
Override the @hanzo/gui (Tamagui) .t_dark base --background to pure #000 so the
console reads as ONE black brand with the marketing site (--background:#000)
and hanzo.chat's OLED .dark theme. Panels sit a hair above pure black (#050505
press / #171717 hover-elevated) for depth. defaultTheme was already dark.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Override the @hanzo/gui (Tamagui) .t_dark base --background to pure #000 so the
console reads as ONE black brand with the marketing site (--background:#000)
and hanzo.chat's OLED .dark theme. Panels sit a hair above pure black (#050505
press / #171717 hover-elevated) for depth. defaultTheme was already dark.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Refine the console toward a quiet, spacious, low-glare feel that's healthy to
work in for a full day (Linear-esque FEEL, our own @hanzo/gui tokens).
Calm tokens (app/globals.css, scoped html:root.t_dark/.t_light so they win over
the generated @hanzo/gui theme on specificity — DRY, whole app calms at once):
- softer cool-charcoal surfaces with gentle elevation STEPS so cards read as
calm panels, not flat voids on pure black
- off-white primary text (no pure-#fff glare) + muted secondary steps
- low-contrast hairline borders; comfortable body line-height + antialiasing
Sidebar (DashboardShell):
- calm neutral section headers (Linear-style) instead of a saturated rainbow;
per-product COLOR now lives only on the icons (restrained accent)
- softer active state ($color4, not the loud $color5 block)
- more breathing room: taller category headers, larger row + section gaps,
responsive rail padding (collapsed vs expanded)
Big desktop: content is a centered, capped column (max 1680) with padding that
scales up at xl — wide screens read comfortably, not stretched full-bleed.
Responsive:
- PageHeader wraps (flex + minW) so long subtitles wrap on mobile instead of
running off-screen; actions drop below the title when narrow (DRY, every page)
- Inference "Usage Overview" overlap fixed: MetricStat no longer flex-collapses
(flex-basis:0 in an auto-height column made the label overlap the value)
typecheck 0 errors · 1167 tests · next build green.
Refine the console toward a quiet, spacious, low-glare feel that's healthy to
work in for a full day (Linear-esque FEEL, our own @hanzo/gui tokens).
Calm tokens (app/globals.css, scoped html:root.t_dark/.t_light so they win over
the generated @hanzo/gui theme on specificity — DRY, whole app calms at once):
- softer cool-charcoal surfaces with gentle elevation STEPS so cards read as
calm panels, not flat voids on pure black
- off-white primary text (no pure-#fff glare) + muted secondary steps
- low-contrast hairline borders; comfortable body line-height + antialiasing
Sidebar (DashboardShell):
- calm neutral section headers (Linear-style) instead of a saturated rainbow;
per-product COLOR now lives only on the icons (restrained accent)
- softer active state ($color4, not the loud $color5 block)
- more breathing room: taller category headers, larger row + section gaps,
responsive rail padding (collapsed vs expanded)
Big desktop: content is a centered, capped column (max 1680) with padding that
scales up at xl — wide screens read comfortably, not stretched full-bleed.
Responsive:
- PageHeader wraps (flex + minW) so long subtitles wrap on mobile instead of
running off-screen; actions drop below the title when narrow (DRY, every page)
- Inference "Usage Overview" overlap fixed: MetricStat no longer flex-collapses
(flex-basis:0 in an auto-height column made the label overlap the value)
typecheck 0 errors · 1167 tests · next build green.
The Model Catalog rows already open a rich detail pane, but the detail's primary
action pushed a bare /playground and DROPPED the model the user was looking at — it
looked wired but lost the selection. Now it deep-links /playground?p=<share> carrying
that model, so the Playground opens PRESELECTED on it (the composer restores the model
from the ?p= share state it already reads on mount). Same fix applied to the
Marketplace 'Try' CTA — both reuse ONE pure helper.
- New pure playgroundPathForModel(modelId) in playground/share.ts — the ONE way to
deep-link the Playground onto a model (URI-safe; empty prompt, default settings).
- ModelCatalogModule detail: 'Open in Playground' → prominent 'Try in Playground'
(theme=light) via the helper; routing/copy reuse the derived modelId.
- MarketplaceModule.open(): available model → playgroundPathForModel(id) (was bare
/playground); catalog-only → /models. DRY, one deep-link path.
tsc clean; +2 share tests (round-trip + slash/space id), marketplace 16/16.
The Model Catalog rows already open a rich detail pane, but the detail's primary
action pushed a bare /playground and DROPPED the model the user was looking at — it
looked wired but lost the selection. Now it deep-links /playground?p=<share> carrying
that model, so the Playground opens PRESELECTED on it (the composer restores the model
from the ?p= share state it already reads on mount). Same fix applied to the
Marketplace 'Try' CTA — both reuse ONE pure helper.
- New pure playgroundPathForModel(modelId) in playground/share.ts — the ONE way to
deep-link the Playground onto a model (URI-safe; empty prompt, default settings).
- ModelCatalogModule detail: 'Open in Playground' → prominent 'Try in Playground'
(theme=light) via the helper; routing/copy reuse the derived modelId.
- MarketplaceModule.open(): available model → playgroundPathForModel(id) (was bare
/playground); catalog-only → /models. DRY, one deep-link path.
tsc clean; +2 share tests (round-trip + slash/space id), marketplace 16/16.
Base records (RecordsModule) now render the @hanzo/data RecordsView — table <-> board,
filter/sort/group, inline cell edit, kanban drag — over REAL per-org Base data via the
/superbase proxy (new base-data/CollectionView; inline edits + board moves persist through
BaseDataApi.updateRecord, honest error banner). CollectionTable superseded (one way).
RecordDetailView gains a titled detail panel; DnsModule onRowPress -> onOpen (new DataTable API).
CRM = Base views: CrmModule renders companies / contacts / opportunities through the SAME
RecordsView — CRM entities expressed as @hanzo/data FieldDefinition schemas + pure record
mappers (crm/collections: money->currency, epoch-s->ms, companyId->named relation chip);
opportunities get a stage PIPELINE board; company relation options injected for filter.
Live create stays; delete preserved + upgraded to bulk-delete via row selection. Read-only
views over live data (no /v1/crm update endpoint yet) — honest by construction.
@hanzo/data 1.1.0 -> ^1.2.0. Rebased on latest main (8.4.49 -> 8.4.50).
tsc clean; vitest 1198 green (+ crm/collections); next build green.
Base records (RecordsModule) now render the @hanzo/data RecordsView — table <-> board,
filter/sort/group, inline cell edit, kanban drag — over REAL per-org Base data via the
/superbase proxy (new base-data/CollectionView; inline edits + board moves persist through
BaseDataApi.updateRecord, honest error banner). CollectionTable superseded (one way).
RecordDetailView gains a titled detail panel; DnsModule onRowPress -> onOpen (new DataTable API).
CRM = Base views: CrmModule renders companies / contacts / opportunities through the SAME
RecordsView — CRM entities expressed as @hanzo/data FieldDefinition schemas + pure record
mappers (crm/collections: money->currency, epoch-s->ms, companyId->named relation chip);
opportunities get a stage PIPELINE board; company relation options injected for filter.
Live create stays; delete preserved + upgraded to bulk-delete via row selection. Read-only
views over live data (no /v1/crm update endpoint yet) — honest by construction.
@hanzo/data 1.1.0 -> ^1.2.0. Rebased on latest main (8.4.49 -> 8.4.50).
tsc clean; vitest 1198 green (+ crm/collections); next build green.
The customer GPU catalog rendered as non-clickable rate rows (Overview 'Popular
accelerators', the GPUs-tab 'GPU catalog', and the Pricing tab) — real live visor
data, but it read like a static brochure. Now every accelerator row is TAP-TO-ACT:
tapping one opens the shared LaunchDrawer (kind=gpu) preselected on that accelerator's
size slug (the drawer already supports initialSize), so the price you see is the price
you launch. Same pattern as machines PR#57's MachineCatalog → onLaunch.
- launch() now takes an optional initialSize (memoized); launchGpu(row) = launch(row.slug).
- onRowPress wired on all three catalog DataTables + the Pricing tab (new optional onLaunch prop).
- Header / empty-state / settings 'Launch' buttons fixed to () => launch() (no event-as-size).
- Honest copy: 'tap to launch' hints; no fabricated data (empty catalog still honest).
tsc clean; gpus vitest 10/10.
The customer GPU catalog rendered as non-clickable rate rows (Overview 'Popular
accelerators', the GPUs-tab 'GPU catalog', and the Pricing tab) — real live visor
data, but it read like a static brochure. Now every accelerator row is TAP-TO-ACT:
tapping one opens the shared LaunchDrawer (kind=gpu) preselected on that accelerator's
size slug (the drawer already supports initialSize), so the price you see is the price
you launch. Same pattern as machines PR#57's MachineCatalog → onLaunch.
- launch() now takes an optional initialSize (memoized); launchGpu(row) = launch(row.slug).
- onRowPress wired on all three catalog DataTables + the Pricing tab (new optional onLaunch prop).
- Header / empty-state / settings 'Launch' buttons fixed to () => launch() (no event-as-size).
- Honest copy: 'tap to launch' hints; no fabricated data (empty catalog still honest).
tsc clean; gpus vitest 10/10.
Two surfaces, both over the ONE /v1 surface with real data + honest states,
reusing the existing LivingOverview + design system (DRY, no new UI systems).
Surface 1 — admin.hanzo.ai "Overlord" overview (god-view of EVERYTHING):
- New living-overview config `overlord` + pure adapter `fromOverlord` composing
THREE real sources: the operator inventory (PlatformApi.apps → the platform-wide
PRODUCT HEALTH board + product/healthy/needs-attention counts + distinct-org
count — the centerpiece), the all-orgs `/v1/admin/overview` aggregate
(usage/spend/top-models/activity/alerts) when routed, and the real commerce
usage ledger (all-orgs) as the honest fallback so the board is never blank.
- New `overlord` catalog entry (Observe, admin:true) rendered by the ONE
LivingOverview. GLOBAL-ADMIN ONLY: hidden from every customer's nav/launcher/
palette (visibleCatalog filters admin entries), the catch-all shows the managed
notice for a non-admin, and `/v1/admin/overview` is server-gated by getAdminGate.
- Pure health-tally helpers (`healthTally`, `orgsFromApps`) — every product-count
KPI is derived from the real inventory, never fabricated (empty → honest em-dash).
Surface 2 — Web Search + Crawl product panel (SearXNG + Crawl4AI, LIVE):
- New `WebSearchApi` (lib/api/websearch.ts) over cloud `/v1/websearch/*`; search
wired same-origin prefix-free `/v1/websearch/search` → the hardened `/cloud`
user-bearer proxy (added `websearch` to CLOUD_HEADS + CLOUD_V1_HEADS — minimal,
additive; distinct arrays from the concurrent providers lane).
- New tabbed `SearchModule` (Overview · Try Search · API · Engines · Config) —
a REAL live search box, honest live-probe health (no health endpoint exists),
the two endpoints + copy-paste curl, the deployed engine set (read-only), and
the honest deployed config. HONEST GAPS surfaced, not hidden: usage is not
metered yet (no cloud_usage rows for websearch), and scrape is documented but
NOT a live try-it (it needs the shared WEBSEARCH_API_KEY, not a user session —
so the console can never drive a scrape; no secret is ever exposed).
- The `websearch` + `crawl` catalog entries render the one module (crawl upgraded
from a native-overview stub — one product, cross-linked, no duplicate surface).
Tab slugs are non-base (search/api/engines/config) so they never collide with
the shared Settings/Status/Logs/Metrics per-product sub-pages.
Verification: tsc --noEmit clean; vitest 1191/1191 (98 files; +28: 7 Overlord
adapter, 8 websearch normalizers, 9 search logic, 1 websearch allow-list, +3
registry-consistency now covering the new configs); next build ✓ (all routes;
/overlord + /websearch/* + /crawl all resolve 200 on the dev server, catch-all
compiles clean). Live authenticated visual e2e (admin session) is post-deploy.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Two surfaces, both over the ONE /v1 surface with real data + honest states,
reusing the existing LivingOverview + design system (DRY, no new UI systems).
Surface 1 — admin.hanzo.ai "Overlord" overview (god-view of EVERYTHING):
- New living-overview config `overlord` + pure adapter `fromOverlord` composing
THREE real sources: the operator inventory (PlatformApi.apps → the platform-wide
PRODUCT HEALTH board + product/healthy/needs-attention counts + distinct-org
count — the centerpiece), the all-orgs `/v1/admin/overview` aggregate
(usage/spend/top-models/activity/alerts) when routed, and the real commerce
usage ledger (all-orgs) as the honest fallback so the board is never blank.
- New `overlord` catalog entry (Observe, admin:true) rendered by the ONE
LivingOverview. GLOBAL-ADMIN ONLY: hidden from every customer's nav/launcher/
palette (visibleCatalog filters admin entries), the catch-all shows the managed
notice for a non-admin, and `/v1/admin/overview` is server-gated by getAdminGate.
- Pure health-tally helpers (`healthTally`, `orgsFromApps`) — every product-count
KPI is derived from the real inventory, never fabricated (empty → honest em-dash).
Surface 2 — Web Search + Crawl product panel (SearXNG + Crawl4AI, LIVE):
- New `WebSearchApi` (lib/api/websearch.ts) over cloud `/v1/websearch/*`; search
wired same-origin prefix-free `/v1/websearch/search` → the hardened `/cloud`
user-bearer proxy (added `websearch` to CLOUD_HEADS + CLOUD_V1_HEADS — minimal,
additive; distinct arrays from the concurrent providers lane).
- New tabbed `SearchModule` (Overview · Try Search · API · Engines · Config) —
a REAL live search box, honest live-probe health (no health endpoint exists),
the two endpoints + copy-paste curl, the deployed engine set (read-only), and
the honest deployed config. HONEST GAPS surfaced, not hidden: usage is not
metered yet (no cloud_usage rows for websearch), and scrape is documented but
NOT a live try-it (it needs the shared WEBSEARCH_API_KEY, not a user session —
so the console can never drive a scrape; no secret is ever exposed).
- The `websearch` + `crawl` catalog entries render the one module (crawl upgraded
from a native-overview stub — one product, cross-linked, no duplicate surface).
Tab slugs are non-base (search/api/engines/config) so they never collide with
the shared Settings/Status/Logs/Metrics per-product sub-pages.
Verification: tsc --noEmit clean; vitest 1191/1191 (98 files; +28: 7 Overlord
adapter, 8 websearch normalizers, 9 search logic, 1 websearch allow-list, +3
registry-consistency now covering the new configs); next build ✓ (all routes;
/overlord + /websearch/* + /crawl all resolve 200 on the dev server, catch-all
compiles clean). Live authenticated visual e2e (admin session) is post-deploy.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
- SidebarWallet balance row: router.push('/cost') → '/billing' (no 'cost'
module in the registry; billing is the canonical balance/spend surface).
- HomeSummary 'View cost' button: same /cost → /billing fix.
- Embeddings SettingsView docs button: docsUrl/embeddings → docsUrl/docs/embeddings
(Fumadocs serves only under /docs/*; matches the docsUrl() /docs convention).
Also updated the stale SidebarWallet docstring that referenced the removed /cost.
- SidebarWallet balance row: router.push('/cost') → '/billing' (no 'cost'
module in the registry; billing is the canonical balance/spend surface).
- HomeSummary 'View cost' button: same /cost → /billing fix.
- Embeddings SettingsView docs button: docsUrl/embeddings → docsUrl/docs/embeddings
(Fumadocs serves only under /docs/*; matches the docsUrl() /docs convention).
Also updated the stale SidebarWallet docstring that referenced the removed /cost.
The document <title> is SSR metadata resolved from the build-time default host,
so console.lux.cloud / console.zoo.cloud tabs read 'Hanzo Cloud Console' — a
white-label violation (Hanzo name on a Lux/Zoo surface). Read the request Host
header in generateMetadata and resolve the brand per host, so the tab title is
'Lux Cloud Console' / 'Zoo Cloud Console'. The visible shell was already correct
(client resolves brand from window.location); only the SSR title leaked.
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
The document <title> is SSR metadata resolved from the build-time default host,
so console.lux.cloud / console.zoo.cloud tabs read 'Hanzo Cloud Console' — a
white-label violation (Hanzo name on a Lux/Zoo surface). Read the request Host
header in generateMetadata and resolve the brand per host, so the tab title is
'Lux Cloud Console' / 'Zoo Cloud Console'. The visible shell was already correct
(client resolves brand from window.location); only the SSR title leaked.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Gap 1 (console self-serve domains UI) over the live /v1/platform/.../domains
surface (via the /cloud bearer proxy, org from the Bearer owner):
- lib/api/paas.ts: PaasDomain + listDomains/addDomain/verifyDomain/removeDomain.
- DomainsPanel.tsx: a Domains section on the app detail — lists the default host,
org-subtree hosts, and BYO custom domains with an HONEST per-domain status from
the operator CR (live / provisioning / awaiting deploy / unverified, never
fabricated); an Add-domain form; per-domain Remove; and — for a pending custom
domain — the exact DNS records to publish (TXT + CNAME, with copy) plus a Verify
action that flips it live with TLS. Default host is non-removable.
- paas/logic.ts (+tests): pure isPendingCustom / canRemoveDomain / domainStatusLabel
/ orderDomains. Wired into PaasApplications AppDetail.
Drive-by: fix a pre-existing origin/main tsc error in overview/living/
open-edition.test.ts (vi.fn<[Args],Return> → single-function-type form the
installed vitest requires) so `tsc --noEmit` is green. Not caused by / related to
this feature; next build (which excludes tests) never surfaced it.
Verify: tsc --noEmit clean; vitest 1167/1167 (+12 domain logic); next build ✓.
Gap 1 (console self-serve domains UI) over the live /v1/platform/.../domains
surface (via the /cloud bearer proxy, org from the Bearer owner):
- lib/api/paas.ts: PaasDomain + listDomains/addDomain/verifyDomain/removeDomain.
- DomainsPanel.tsx: a Domains section on the app detail — lists the default host,
org-subtree hosts, and BYO custom domains with an HONEST per-domain status from
the operator CR (live / provisioning / awaiting deploy / unverified, never
fabricated); an Add-domain form; per-domain Remove; and — for a pending custom
domain — the exact DNS records to publish (TXT + CNAME, with copy) plus a Verify
action that flips it live with TLS. Default host is non-removable.
- paas/logic.ts (+tests): pure isPendingCustom / canRemoveDomain / domainStatusLabel
/ orderDomains. Wired into PaasApplications AppDetail.
Drive-by: fix a pre-existing origin/main tsc error in overview/living/
open-edition.test.ts (vi.fn<[Args],Return> → single-function-type form the
installed vitest requires) so `tsc --noEmit` is green. Not caused by / related to
this feature; next build (which excludes tests) never surfaced it.
Verify: tsc --noEmit clean; vitest 1167/1167 (+12 domain logic); next build ✓.
The hanzoai/cloud Go binary go:embeds the console SPA and serves it at its own
web root; the Dockerfile already looks for `npm run build:embed` to produce the
static bundle. This adds that target — the last piece of 'True 1-binary FE'.
- next.config.mjs: CONSOLE_EMBED=1 → output:'export' + images.unoptimized and
DROPS the aiSurfaceRewrites (a static export cannot run rewrites, and does not
need them: the clean /v1/<head> the SPA already builds terminates directly at
the embedded cloud's mounted /v1 subsystems, which is what the rewrites used to
forward to via the Next BFF). The normal `npm run build` (server build) is
UNCHANGED, so the standalone console deployment never regresses.
- scripts/build-embed.mjs: prepares the app for output:'export' for ONE build and
ALWAYS restores it (finally block; main stays byte-identical):
(1) stashes every app/**route.ts — a static export has no runtime for a
server route handler; the BFF proxies collapse to cloud /v1/* and the two
standalone routes (keys/onboard) are ported to cloud /v1/console/*.
(2) overlays the two dynamic client pages ([...slug], discover/[id]) with a
force-static server wrapper (generateStaticParams + dynamicParams=false)
so they satisfy output:'export'; the real client body still ships in the
JS bundle (client nav hydrates it) and deep links hit the host's SPA
fallback (cloud/webui.go serveIndex → index.html) which re-resolves them.
- build:embed npm script.
Proven: `npm run build:embed` → out/ (47 files, 6 html incl. discover/ + the
SPA-shell index.html at 376 KB); working tree restored clean after.
The hanzoai/cloud Go binary go:embeds the console SPA and serves it at its own
web root; the Dockerfile already looks for `npm run build:embed` to produce the
static bundle. This adds that target — the last piece of 'True 1-binary FE'.
- next.config.mjs: CONSOLE_EMBED=1 → output:'export' + images.unoptimized and
DROPS the aiSurfaceRewrites (a static export cannot run rewrites, and does not
need them: the clean /v1/<head> the SPA already builds terminates directly at
the embedded cloud's mounted /v1 subsystems, which is what the rewrites used to
forward to via the Next BFF). The normal `npm run build` (server build) is
UNCHANGED, so the standalone console deployment never regresses.
- scripts/build-embed.mjs: prepares the app for output:'export' for ONE build and
ALWAYS restores it (finally block; main stays byte-identical):
(1) stashes every app/**route.ts — a static export has no runtime for a
server route handler; the BFF proxies collapse to cloud /v1/* and the two
standalone routes (keys/onboard) are ported to cloud /v1/console/*.
(2) overlays the two dynamic client pages ([...slug], discover/[id]) with a
force-static server wrapper (generateStaticParams + dynamicParams=false)
so they satisfy output:'export'; the real client body still ships in the
JS bundle (client nav hydrates it) and deep links hit the host's SPA
fallback (cloud/webui.go serveIndex → index.html) which re-resolves them.
- build:embed npm script.
Proven: `npm run build:embed` → out/ (47 files, 6 html incl. discover/ + the
SPA-shell index.html at 376 KB); working tree restored clean after.
The whole-repo sweep after v8.4.42 caught the one remaining user-facing Base
competitor reference: the built-in assistant's system prompt described Base as a
'Firebase-style backend' (from the v8.4.43 grounded-assistant lane). Rewrote it in
Hanzo's own voice — 'a realtime backend — spin up per-org Bases with content types,
records, and auth'. The console is now free of Supabase/Firebase user-facing copy.
Drive-by: open-edition.test.ts (#60) used the old vitest vi.fn<[Args],Return>() form
that vitest v3.2.4 rejects — main's tsc was RED. Migrated to the v3 single-fn-type
form. tsc clean, vitest 1163/1163, next build green.
The whole-repo sweep after v8.4.42 caught the one remaining user-facing Base
competitor reference: the built-in assistant's system prompt described Base as a
'Firebase-style backend' (from the v8.4.43 grounded-assistant lane). Rewrote it in
Hanzo's own voice — 'a realtime backend — spin up per-org Bases with content types,
records, and auth'. The console is now free of Supabase/Firebase user-facing copy.
Drive-by: open-edition.test.ts (#60) used the old vitest vi.fn<[Args],Return>() form
that vitest v3.2.4 rejects — main's tsc was RED. Migrated to the v3 single-fn-type
form. tsc clean, vitest 1163/1163, next build green.
Add the Open Edition / run-for-pay overview as a living-overview config
(add-a-product = 1 config) that renders from the REAL commerce usage
ledger scoped to the `open-edition` product tag. Spend billed = the
served-revenue figure R (cost + 25% resell margin) per the pricing spec.
- living/registry.ts: `openEditionOverview` config + `open-edition` map
key. Reuses UsageApi.overview({ product: 'open-edition' }) + the
existing fromCloudUsage adapter (DRY) — honest-empty when no run-for-pay
usage, never a mock.
- products/registry.tsx: `livingOverviewModule('open-edition')` + a
catalog entry (Observe category) → the board lives at /open-edition.
- living/open-edition.test.ts: behavioral proof the loader forwards the
`open-edition` product scope, maps real data through fromCloudUsage,
and rolls up honest-empty (4 tests).
- e2e/open-edition.spec.ts: dedicated Playwright visual gate asserting the
run-for-pay header, the cost+25% Spend KPI caption, and the spend/tokens
KPIs render; captures a full-page screenshot.
- e2e/pages.spec.ts: add `open-edition` to the all-pages screenshot sweep.
Canonical model: universe docs/architecture/run-for-pay-pricing.md (price)
+ run-for-pay-and-contributor-revenue.md (settlement).
Additive only (no deletions); does not touch the concurrent session's
staged adapters.ts / registry.test.ts.
Add the Open Edition / run-for-pay overview as a living-overview config
(add-a-product = 1 config) that renders from the REAL commerce usage
ledger scoped to the `open-edition` product tag. Spend billed = the
served-revenue figure R (cost + 25% resell margin) per the pricing spec.
- living/registry.ts: `openEditionOverview` config + `open-edition` map
key. Reuses UsageApi.overview({ product: 'open-edition' }) + the
existing fromCloudUsage adapter (DRY) — honest-empty when no run-for-pay
usage, never a mock.
- products/registry.tsx: `livingOverviewModule('open-edition')` + a
catalog entry (Observe category) → the board lives at /open-edition.
- living/open-edition.test.ts: behavioral proof the loader forwards the
`open-edition` product scope, maps real data through fromCloudUsage,
and rolls up honest-empty (4 tests).
- e2e/open-edition.spec.ts: dedicated Playwright visual gate asserting the
run-for-pay header, the cost+25% Spend KPI caption, and the spend/tokens
KPIs render; captures a full-page screenshot.
- e2e/pages.spec.ts: add `open-edition` to the all-pages screenshot sweep.
Canonical model: universe docs/architecture/run-for-pay-pricing.md (price)
+ run-for-pay-and-contributor-revenue.md (settlement).
Additive only (no deletions); does not touch the concurrent session's
staged adapters.ts / registry.test.ts.
Make every product's shared base sub-pages real, correct, and per-product via ONE
metadata source, no fabrication.
- Metrics: consolidate the ledger-scope decision to sources.ts metricsScopeFor (kill
the dead MetricsFeed/O11Y_METRICS_PRODUCTS dup); every product filters by
metadata.product===id (honest-empty, never the org total); the inference surface
(inference/models/api/gateway) reads the whole ledger with an explicit honest
'org-wide inference' banner + scope-aware subtitle.
- Status/Logs: verified SERVICE_OVERRIDE (models, bot->bot-gateway, helpdesk->help)
grounded in the live /v1/apps inventory; fix console spec service console2->console;
neutral+honest 'no operator row' copy; Logs-specific honest managed card.
- Settings: settingsConfigFor surfaces real product-specific config (reuse the overview
spec facts+actions, else category default) — a real Configuration card, not a dead form.
- Overview: console spec health repointed; defaultSpec stays honest.
Only subpage/*, overview/*, overview/living/* + per-product metadata. Did NOT touch
AgentsModule/agents/* or assistant/*. tsc clean; vitest 1140/1140; next build green.
Make every product's shared base sub-pages real, correct, and per-product via ONE
metadata source, no fabrication.
- Metrics: consolidate the ledger-scope decision to sources.ts metricsScopeFor (kill
the dead MetricsFeed/O11Y_METRICS_PRODUCTS dup); every product filters by
metadata.product===id (honest-empty, never the org total); the inference surface
(inference/models/api/gateway) reads the whole ledger with an explicit honest
'org-wide inference' banner + scope-aware subtitle.
- Status/Logs: verified SERVICE_OVERRIDE (models, bot->bot-gateway, helpdesk->help)
grounded in the live /v1/apps inventory; fix console spec service console2->console;
neutral+honest 'no operator row' copy; Logs-specific honest managed card.
- Settings: settingsConfigFor surfaces real product-specific config (reuse the overview
spec facts+actions, else category default) — a real Configuration card, not a dead form.
- Overview: console spec health repointed; defaultSpec stays honest.
Only subpage/*, overview/*, overview/living/* + per-product metadata. Did NOT touch
AgentsModule/agents/* or assistant/*. tsc clean; vitest 1140/1140; next build green.
Make the console's built-in chat assistant a genuine expert on the whole Hanzo
suite, GROUNDED in real sources (the product registry + docs RAG), never
hallucinated — ONE shared system prompt across all three chat surfaces.
- src/lib/assistant/: decomplected into a PURE builder (prompt-content.ts,
unit-tested) + a thin registry-bound wrapper (system-prompt.ts). Catalog
section generated FROM the live registry (visibleCatalogByCategory) — all
products, per-category, name+description+GCP-analog+deep-link; complete,
current, brand-white-labeled, admin-gated for customers. Plus a curated
accurate 'what Hanzo is' overview + an honest behavior contract (never invent;
say so when Hanzo lacks a thing).
- Wired DRY into ChatConversation (=> FloatingChat bubble + full /chat page) via
AiApi.ragChat, and CommandPalette >/? via commandBarSystemPrompt (base + NAV
contract) — replaces the old nav-only prompt.
- AiApi.ragChat gains optional history (backward-compatible) for grounded
multi-turn; X-Retrieval store 'docs' shared, degrades gracefully.
tsc clean; npm test 1142/1142 (+10); next build green. Rebased on v8.4.42.
Make the console's built-in chat assistant a genuine expert on the whole Hanzo
suite, GROUNDED in real sources (the product registry + docs RAG), never
hallucinated — ONE shared system prompt across all three chat surfaces.
- src/lib/assistant/: decomplected into a PURE builder (prompt-content.ts,
unit-tested) + a thin registry-bound wrapper (system-prompt.ts). Catalog
section generated FROM the live registry (visibleCatalogByCategory) — all
products, per-category, name+description+GCP-analog+deep-link; complete,
current, brand-white-labeled, admin-gated for customers. Plus a curated
accurate 'what Hanzo is' overview + an honest behavior contract (never invent;
say so when Hanzo lacks a thing).
- Wired DRY into ChatConversation (=> FloatingChat bubble + full /chat page) via
AiApi.ragChat, and CommandPalette >/? via commandBarSystemPrompt (base + NAV
contract) — replaces the old nav-only prompt.
- AiApi.ragChat gains optional history (backward-compatible) for grounded
multi-turn; X-Retrieval store 'docs' shared, degrades gracefully.
tsc clean; npm test 1142/1142 (+10); next build green. Rebased on v8.4.42.
Base was a content-type dashboard over the SuperBase orchestrator's own
collections (contacts/tenants/users), so the org saw one shared Base and had no
way to make another — 'stuck with a single base'. Rework it into the Base
INSTANCES manager over the real tenants API (each row = a Base on its own
<slug>.base.hanzo.ai), so the user can SEE all their Bases, CREATE a new one, and
CONFIGURE one (name/size/status/delete). One Base binding — the /superbase proxy
(user bearer + X-Org-Id from the JWT owner, derive-once). Clean split from
Records (which browses a Base's collections + records).
- NEW lib/base-data/tenants.ts (BaseTenantsApi over the tenants collection)
- NEW base/bases-logic.ts (+test): slug/validate/size presets/status
- NEW base/BasesManager.tsx: list + New Base + configure
- BaseModule -> BasesManager; registry routes ''|new|:base
- Drop the Supabase/Firebase copy + gcp:'Firebase' from the Base entry
- Remove the superseded content-type dashboard (BaseDashboard/CollectionBuilder/logic)
Copy: no competitor names in the Base UI or docstrings.
Base was a content-type dashboard over the SuperBase orchestrator's own
collections (contacts/tenants/users), so the org saw one shared Base and had no
way to make another — 'stuck with a single base'. Rework it into the Base
INSTANCES manager over the real tenants API (each row = a Base on its own
<slug>.base.hanzo.ai), so the user can SEE all their Bases, CREATE a new one, and
CONFIGURE one (name/size/status/delete). One Base binding — the /superbase proxy
(user bearer + X-Org-Id from the JWT owner, derive-once). Clean split from
Records (which browses a Base's collections + records).
- NEW lib/base-data/tenants.ts (BaseTenantsApi over the tenants collection)
- NEW base/bases-logic.ts (+test): slug/validate/size presets/status
- NEW base/BasesManager.tsx: list + New Base + configure
- BaseModule -> BasesManager; registry routes ''|new|:base
- Drop the Supabase/Firebase copy + gcp:'Firebase' from the Base entry
- Remove the superseded content-type dashboard (BaseDashboard/CollectionBuilder/logic)
Copy: no competitor names in the Base UI or docstrings.
Extend the admin compute-analytics boards from bot/machine to the full
kind spectrum so DOKS clusters, node pools and Functions surface in
admin.hanzo.ai like Bots/Machines.
- admin-compute.ts: widen ComputeKind to bot|machine|cluster|nodepool|
function; asKind now canonicalizes over the whole spectrum (fallback
machine, mirror of visor CanonicalKind) so a cluster/nodepool/function
row never pollutes a sibling board via keepKind.
- ComputeModule.tsx: KIND_UI entries for cluster/nodepool/function;
ClustersModule (kind=cluster) + FunctionsModule (kind=function) thin
wrappers over the ONE ComputeBoard, mirroring Bots/Machines.
- registry.tsx: register cluster-fleet + function-fleet (admin:true,
category Observe), distinct from the customer clusters/functions
products (same split as vms vs machines).
- admin-compute.test.ts: cover the widened spectrum (cluster/nodepool/
function fold + kind-filtering, unknown-kind fallback).
Honest-empty until the emitters + cloud read land. DRY: one ComputeBoard,
one datastore aggregate, one kind canonicalizer.
Extend the admin compute-analytics boards from bot/machine to the full
kind spectrum so DOKS clusters, node pools and Functions surface in
admin.hanzo.ai like Bots/Machines.
- admin-compute.ts: widen ComputeKind to bot|machine|cluster|nodepool|
function; asKind now canonicalizes over the whole spectrum (fallback
machine, mirror of visor CanonicalKind) so a cluster/nodepool/function
row never pollutes a sibling board via keepKind.
- ComputeModule.tsx: KIND_UI entries for cluster/nodepool/function;
ClustersModule (kind=cluster) + FunctionsModule (kind=function) thin
wrappers over the ONE ComputeBoard, mirroring Bots/Machines.
- registry.tsx: register cluster-fleet + function-fleet (admin:true,
category Observe), distinct from the customer clusters/functions
products (same split as vms vs machines).
- admin-compute.test.ts: cover the widened spectrum (cluster/nodepool/
function fold + kind-filtering, unknown-kind fallback).
Honest-empty until the emitters + cloud read land. DRY: one ComputeBoard,
one datastore aggregate, one kind canonicalizer.
- AuthzModule: off dead /paas onto /cloud user-bearer proxy → cloud authz
subsystem (hanzoai/authz) GET /v1/authz/policies; per-org enforcer picked
from the Bearer-derived X-Org-Id. Match FE type to the Casbin [sub,obj,act]
tuple (effect always allow); honest-empty + PlatformStateCard on failure.
- SettlementModule: off dead /paas onto the existing /billing/v1 commerce
proxy → GET /v1/billing/payouts (ListPayouts), org-scoped server-side.
Match FE type to commerce payoutResponse (amount cents/currency, status,
destinationType/Id, created). 501 when COMMERCE_TOKEN unset → honest card.
- authz head already admitted in proxy-allow CLOUD_HEADS + next.config
CLOUD_V1_HEADS.
- AuthzModule: off dead /paas onto /cloud user-bearer proxy → cloud authz
subsystem (hanzoai/authz) GET /v1/authz/policies; per-org enforcer picked
from the Bearer-derived X-Org-Id. Match FE type to the Casbin [sub,obj,act]
tuple (effect always allow); honest-empty + PlatformStateCard on failure.
- SettlementModule: off dead /paas onto the existing /billing/v1 commerce
proxy → GET /v1/billing/payouts (ListPayouts), org-scoped server-side.
Match FE type to commerce payoutResponse (amount cents/currency, status,
destinationType/Id, created). 501 when COMMERCE_TOKEN unset → honest card.
- authz head already admitted in proxy-allow CLOUD_HEADS + next.config
CLOUD_V1_HEADS.
Repoint the last two "not connected" chain-data pages off the admin
/paas proxy onto the native cloud user-bearer proxy, backed by the new
cloud clients/graph subsystem:
- IndexerModule: restGet(paas('indexers')) -> cloudProxyV1Url('indexers')
- OraclesModule: restGet(paas('oracles')) -> cloudProxyV1Url('oracles')
Admit both heads on the /cloud proxy: add indexers,oracles to
next.config.mjs CLOUD_V1_HEADS and proxy-allow.ts CLOUD_HEADS. Bump
8.4.39 -> 8.4.40 so a fresh image builds.
Repoint the last two "not connected" chain-data pages off the admin
/paas proxy onto the native cloud user-bearer proxy, backed by the new
cloud clients/graph subsystem:
- IndexerModule: restGet(paas('indexers')) -> cloudProxyV1Url('indexers')
- OraclesModule: restGet(paas('oracles')) -> cloudProxyV1Url('oracles')
Admit both heads on the /cloud proxy: add indexers,oracles to
next.config.mjs CLOUD_V1_HEADS and proxy-allow.ts CLOUD_HEADS. Bump
8.4.39 -> 8.4.40 so a fresh image builds.
Alerts: restGet('/paas/alerts') -> cloudProxyV1Url('o11y/v1/rules'), the real
hanzoai/o11y alert-rule-states route (cloud mounts /v1/o11y/*, reverse-proxies to
the o11y Deployment which rewrites /v1/o11y/* -> /api/v1/rules; listRules ->
ListRuleStates). Normalize the flattened GettableRule envelope
{status,data:{rules:[…]}} to the flat Alert row: name<-alert, severity<-labels.
severity, status<-state (or 'disabled'), condition<-description. lastFired left
empty honestly (rule-list carries no last-fired timestamp).
Logs: kept honest. o11y's GET /v1/o11y/v1/logs is a hardcoded empty stub and the
only real log read is a composite POST query_range — no clean logs-list route to
repoint to. Copy now names the true gap (needs a real logs-list route) instead of
the stale "VictoriaLogs not deployed"; nothing fabricated.
Status: unchanged — already on native VictoriaMetrics up{} via /telemetry (real
data). Repointing to platform apps would regress to a different, empty concern.
Heads: add 'o11y' to next.config CLOUD_V1_HEADS + server/proxy-allow CLOUD_HEADS
so /cloud admits the o11y sub-surface.
Alerts: restGet('/paas/alerts') -> cloudProxyV1Url('o11y/v1/rules'), the real
hanzoai/o11y alert-rule-states route (cloud mounts /v1/o11y/*, reverse-proxies to
the o11y Deployment which rewrites /v1/o11y/* -> /api/v1/rules; listRules ->
ListRuleStates). Normalize the flattened GettableRule envelope
{status,data:{rules:[…]}} to the flat Alert row: name<-alert, severity<-labels.
severity, status<-state (or 'disabled'), condition<-description. lastFired left
empty honestly (rule-list carries no last-fired timestamp).
Logs: kept honest. o11y's GET /v1/o11y/v1/logs is a hardcoded empty stub and the
only real log read is a composite POST query_range — no clean logs-list route to
repoint to. Copy now names the true gap (needs a real logs-list route) instead of
the stale "VictoriaLogs not deployed"; nothing fabricated.
Status: unchanged — already on native VictoriaMetrics up{} via /telemetry (real
data). Repointing to platform apps would regress to a different, empty concern.
Heads: add 'o11y' to next.config CLOUD_V1_HEADS + server/proxy-allow CLOUD_HEADS
so /cloud admits the o11y sub-surface.
Theme (the real apply): v8.4.36's accent used a CSS class (hz-accent-fill) on the
accent surfaces, but Tamagui does NOT forward className to a Button's DOM node
(only to Stacks), so the org's saved brand color never recolored anything. Rebuilt
the mechanism to be Tamagui-native and verified LIVE: src/lib/theme/accent.ts now
holds the resolved accent in a tiny external store (setOrgAccent, called on load by
OrgAccentProvider AND on save by SettingsModule) exposed via useAccent(); the genuine
accent surfaces (PrimaryButton, the active GPU/Settings tabs, the active sidebar nav
item) recolor with real @hanzo/gui props — inline bg + readable contrast text (light
accent -> black text, dark -> white), the nav via an accent left-bar — reverting to
the default monochrome when the org disables its theme or the hex is invalid.
Verified in a browser: enable green -> primary button green + white text; yellow ->
black text; disable -> reverts (no inline style). Dead globals.css accent block +
classNames removed.
GPUs Pools tab: now honest-empty 'No GPU node pools yet' whenever the org has no
reachable GPU clusters (none provisioned, or the native /cloud/v1/clusters endpoint
isn't live) — a pools-specific state distinct from the Clusters tab, never a
fabricated pool. (Pools are derived from the org's real clusters.)
Rebased on v8.4.37 (Inference dashboard) — strict superset. tsc clean; vitest
1132/1132 (+2 accentFor); next build green.
Theme (the real apply): v8.4.36's accent used a CSS class (hz-accent-fill) on the
accent surfaces, but Tamagui does NOT forward className to a Button's DOM node
(only to Stacks), so the org's saved brand color never recolored anything. Rebuilt
the mechanism to be Tamagui-native and verified LIVE: src/lib/theme/accent.ts now
holds the resolved accent in a tiny external store (setOrgAccent, called on load by
OrgAccentProvider AND on save by SettingsModule) exposed via useAccent(); the genuine
accent surfaces (PrimaryButton, the active GPU/Settings tabs, the active sidebar nav
item) recolor with real @hanzo/gui props — inline bg + readable contrast text (light
accent -> black text, dark -> white), the nav via an accent left-bar — reverting to
the default monochrome when the org disables its theme or the hex is invalid.
Verified in a browser: enable green -> primary button green + white text; yellow ->
black text; disable -> reverts (no inline style). Dead globals.css accent block +
classNames removed.
GPUs Pools tab: now honest-empty 'No GPU node pools yet' whenever the org has no
reachable GPU clusters (none provisioned, or the native /cloud/v1/clusters endpoint
isn't live) — a pools-specific state distinct from the Clusters tab, never a
fabricated pool. (Pools are derived from the org's real clusters.)
Rebased on v8.4.37 (Inference dashboard) — strict superset. tsc clean; vitest
1132/1132 (+2 accentFor); next build green.
Redesign the Inference page to the endpoints-dashboard mockup, wired to REAL sources
(honest '—'/empty where unexposed — never the mockup's placeholder numbers). Sidebar +
topbar untouched; only the Inference module content + the shared Metrics sub-page changed.
- Endpoints = managed model catalog (/v1/models) merged with the org's deployed KServe
InferenceServices (cloud /v1/ml/models; new 'ml' /cloud head in proxy-allow + rewrite).
Per-endpoint Requests(24h) + trend sparkline = REAL usage ledger by model id; KServe phase
from live status.conditions; P95/uptime honest '—'.
- Hero 'Connected to Hanzo Cloud' (honest managed copy + purple SVG accent), purple Deploy
Endpoint CTA (real POST /v1/ml/models), right rail Usage Overview (real ledger window +
prior-period deltas) + Quick Actions + Need help (real routes/links).
- Inference OWNS Status + Logs as :tab views (health board + real recorded inference
activity), declared as specific subpages so the router renders them.
- Shared per-product Metrics -> product-parameterized LivingOverview over the real usage
ledger scoped by metadata.product; new byStatus + tokens breakdowns. P95 honest '—'.
tsc clean; vitest 1130/1130; next build green. Rebased on origin/main (v8.4.36) -> v8.4.37.
Redesign the Inference page to the endpoints-dashboard mockup, wired to REAL sources
(honest '—'/empty where unexposed — never the mockup's placeholder numbers). Sidebar +
topbar untouched; only the Inference module content + the shared Metrics sub-page changed.
- Endpoints = managed model catalog (/v1/models) merged with the org's deployed KServe
InferenceServices (cloud /v1/ml/models; new 'ml' /cloud head in proxy-allow + rewrite).
Per-endpoint Requests(24h) + trend sparkline = REAL usage ledger by model id; KServe phase
from live status.conditions; P95/uptime honest '—'.
- Hero 'Connected to Hanzo Cloud' (honest managed copy + purple SVG accent), purple Deploy
Endpoint CTA (real POST /v1/ml/models), right rail Usage Overview (real ledger window +
prior-period deltas) + Quick Actions + Need help (real routes/links).
- Inference OWNS Status + Logs as :tab views (health board + real recorded inference
activity), declared as specific subpages so the router renders them.
- Shared per-product Metrics -> product-parameterized LivingOverview over the real usage
ledger scoped by metadata.product; new byStatus + tokens breakdowns. P95 honest '—'.
tsc clean; vitest 1130/1130; next build green. Rebased on origin/main (v8.4.36) -> v8.4.37.
GPU tabs (the customer bug): a non-admin's GPU page rendered the same static
catalog for every sub-tab (Clusters/Pools/Pricing/Alerts all showed the GPU
catalog) because CustomerGpus was one static component with no tab bar. It is now
TABBED like AdminGpus — the shared GpuTabBar + GPU_TABS (one source of truth,
router.push navigation), active tab from params.tab — with DISTINCT, customer-
scoped, per-org content per tab:
- Overview/GPUs: visor catalog (/vm /v1/gpus) + the org's own GPU machines.
- Clusters: the org's own clusters (PlatformApi.listClusters -> user-bearer
/cloud/v1/clusters), honest-empty; reuses ClustersTab (DRY).
- Pools: GPU node pools derived from the org's real clusters (honest-empty).
- Pricing: the REAL per-accelerator price list from the live visor catalog.
- Alerts: real alerts derived from the org's own GPU machines' health; reuses
AlertsTab (DRY), honest-empty when healthy.
- Settings: honest per-org GPU settings + real counts.
AdminGpus behavior is unchanged (now shares GpuTabBar/GPU_TABS). Pure derivations
(gpuPoolsFromClusters/gpuAlertsFromMachines/catalog stats) are unit-tested — real
per-org data or honest-empty, never fabricated.
Theme accent (folded in): the org's saved brand color (themeData.colorPrimary +
isEnabled) was persisted but never applied. Added src/lib/theme/accent.ts
(applyOrgAccent -> one root --hz-accent CSS var + data-hz-accent) applied on load
(OrgAccentProvider) AND immediately on save (SettingsModule). Genuine accent
surfaces read the one var via hz-accent-fill/hz-accent-bar (PrimaryButton, active
sidebar nav, active tabs) — DRY, reverts to default when disabled/invalid.
tsc clean; vitest 1092/1092 (+16 new); next build green.
GPU tabs (the customer bug): a non-admin's GPU page rendered the same static
catalog for every sub-tab (Clusters/Pools/Pricing/Alerts all showed the GPU
catalog) because CustomerGpus was one static component with no tab bar. It is now
TABBED like AdminGpus — the shared GpuTabBar + GPU_TABS (one source of truth,
router.push navigation), active tab from params.tab — with DISTINCT, customer-
scoped, per-org content per tab:
- Overview/GPUs: visor catalog (/vm /v1/gpus) + the org's own GPU machines.
- Clusters: the org's own clusters (PlatformApi.listClusters -> user-bearer
/cloud/v1/clusters), honest-empty; reuses ClustersTab (DRY).
- Pools: GPU node pools derived from the org's real clusters (honest-empty).
- Pricing: the REAL per-accelerator price list from the live visor catalog.
- Alerts: real alerts derived from the org's own GPU machines' health; reuses
AlertsTab (DRY), honest-empty when healthy.
- Settings: honest per-org GPU settings + real counts.
AdminGpus behavior is unchanged (now shares GpuTabBar/GPU_TABS). Pure derivations
(gpuPoolsFromClusters/gpuAlertsFromMachines/catalog stats) are unit-tested — real
per-org data or honest-empty, never fabricated.
Theme accent (folded in): the org's saved brand color (themeData.colorPrimary +
isEnabled) was persisted but never applied. Added src/lib/theme/accent.ts
(applyOrgAccent -> one root --hz-accent CSS var + data-hz-accent) applied on load
(OrgAccentProvider) AND immediately on save (SettingsModule). Genuine accent
surfaces read the one var via hz-accent-fill/hz-accent-bar (PrimaryButton, active
sidebar nav, active tabs) — DRY, reverts to default when disabled/invalid.
tsc clean; vitest 1092/1092 (+16 new); next build green.
Each level-1 CATEGORY is now a collapsible section: the header is a clickable
button with an obvious rotating chevron (▸ collapsed, ▾ expanded), keyboard-
toggleable + aria-expanded, over its product rows revealed in order when open.
The ~120-item flat list condenses to 13 tidy topic headers so the nav stops
overwhelming the user.
- Pure model: src/lib/products/nav-accordion.ts (categoryIsOpen/toggleCategory,
10 unit tests). Default COLLAPSED for most; the active route's category is
always open (navigating reveals it, even if collapsed); filtering opens every
matching group so search is never hidden; clearing search restores collapse.
- Persisted per-user via usePreferences (account-backed + localStorage cache,
the existing sidebarCollapsed idiom) under navCategoriesOpen — survives reloads
+ navigations, never clobbers other choices.
- CategorySection in DashboardShell; body animates height (grid-rows 0fr<->1fr) +
opacity via .hz-acc, chevron rotates via .hz-chevron, both reduced-motion-
guarded; collapsed body is inert (out of tab order). Shared by the desktop
sidebar AND the mobile drawer (one SidebarNav). Items/icons/colors/routes/
active-state unchanged; only the grouping is now collapsible.
tsc 0 errors, vitest 1086/1086 (+10 nav-accordion), next build green.
Each level-1 CATEGORY is now a collapsible section: the header is a clickable
button with an obvious rotating chevron (▸ collapsed, ▾ expanded), keyboard-
toggleable + aria-expanded, over its product rows revealed in order when open.
The ~120-item flat list condenses to 13 tidy topic headers so the nav stops
overwhelming the user.
- Pure model: src/lib/products/nav-accordion.ts (categoryIsOpen/toggleCategory,
10 unit tests). Default COLLAPSED for most; the active route's category is
always open (navigating reveals it, even if collapsed); filtering opens every
matching group so search is never hidden; clearing search restores collapse.
- Persisted per-user via usePreferences (account-backed + localStorage cache,
the existing sidebarCollapsed idiom) under navCategoriesOpen — survives reloads
+ navigations, never clobbers other choices.
- CategorySection in DashboardShell; body animates height (grid-rows 0fr<->1fr) +
opacity via .hz-acc, chevron rotates via .hz-chevron, both reduced-motion-
guarded; collapsed body is inert (out of tab order). Shared by the desktop
sidebar AND the mobile drawer (one SidebarNav). Items/icons/colors/routes/
active-state unchanged; only the grouping is now collapsible.
tsc 0 errors, vitest 1086/1086 (+10 nav-accordion), next build green.
P0 [CRITICAL]: v8.4.33 resilientFetch called the global fetch as a METHOD
(deps.doFetch(url,init) → this=deps) → the browser threw 'Failed to execute fetch
on Window: Illegal invocation' on EVERY cloud/BFF call — the whole API layer broke
(Analytics/Models/CRM/CMS/... all 'Could not reach the backend'). The client-retry
unit tests passed because they injected a MOCK doFetch (no this requirement) — the
exact class a mock hides. Fixed: destructure const doFetch = deps.doFetch and call it
BARE (this=undefined) — works for a raw global fetch AND a wrapped one. New regression
test simulates a global-only fetch (throws unless this is the global) and asserts the
bare invocation. Live console was rolled back to v8.4.31 on detection; this is the fix.
LESSON: verify a shared-fetch refactor by RENDERING a live data page, not just unit tests.
live-shape (caught by the same live pass):
- CMS: Payload SQLite INTEGER ids ({id:3}) were read as strings → id='' (rowKey
collisions); number-aware idStr. Media bytes url carries ?prefix=<tenant> that the
filename-reconstruction dropped → cmsMediaSrc proxies the doc's real url through /cms.
- Commerce: /v1/store/current wraps the record as {store:{}} → currentStore unwraps .store.
RED LOW-1: /erp allow-list pinned to EXACTLY {Account, Item, Sales Order} (was any
DocType) so an entitled brand member can't over-read User/Salary Slip/etc. through the
shared ERP_API_TOKEN. RED verdict on v8.4.33: 0 crit/high/med, cross-tenant isolation
SOUND across CMS/ERP/Help/Analytics — SHIP.
Playground (coordinator, real user bugs):
- Multi-image upload: composer attachment (single) → attachments[] (append; multi-select
dialog OR successive uploads/drag-drop accumulate); file input 'multiple'; thumbnail
strip with count + per-image remove; buildRunMessages pushes one image_url part per image.
- 'Run does nothing' (image-only): validateRun now counts an attached image as user
content — an image-only vision prompt is valid and Run proceeds; blocks ONLY a
genuinely-empty message, and the reason renders PROMINENTLY right above the Run button.
tsc clean; vitest 1076/1076 (89 files); next build green.
P0 [CRITICAL]: v8.4.33 resilientFetch called the global fetch as a METHOD
(deps.doFetch(url,init) → this=deps) → the browser threw 'Failed to execute fetch
on Window: Illegal invocation' on EVERY cloud/BFF call — the whole API layer broke
(Analytics/Models/CRM/CMS/... all 'Could not reach the backend'). The client-retry
unit tests passed because they injected a MOCK doFetch (no this requirement) — the
exact class a mock hides. Fixed: destructure const doFetch = deps.doFetch and call it
BARE (this=undefined) — works for a raw global fetch AND a wrapped one. New regression
test simulates a global-only fetch (throws unless this is the global) and asserts the
bare invocation. Live console was rolled back to v8.4.31 on detection; this is the fix.
LESSON: verify a shared-fetch refactor by RENDERING a live data page, not just unit tests.
live-shape (caught by the same live pass):
- CMS: Payload SQLite INTEGER ids ({id:3}) were read as strings → id='' (rowKey
collisions); number-aware idStr. Media bytes url carries ?prefix=<tenant> that the
filename-reconstruction dropped → cmsMediaSrc proxies the doc's real url through /cms.
- Commerce: /v1/store/current wraps the record as {store:{}} → currentStore unwraps .store.
RED LOW-1: /erp allow-list pinned to EXACTLY {Account, Item, Sales Order} (was any
DocType) so an entitled brand member can't over-read User/Salary Slip/etc. through the
shared ERP_API_TOKEN. RED verdict on v8.4.33: 0 crit/high/med, cross-tenant isolation
SOUND across CMS/ERP/Help/Analytics — SHIP.
Playground (coordinator, real user bugs):
- Multi-image upload: composer attachment (single) → attachments[] (append; multi-select
dialog OR successive uploads/drag-drop accumulate); file input 'multiple'; thumbnail
strip with count + per-image remove; buildRunMessages pushes one image_url part per image.
- 'Run does nothing' (image-only): validateRun now counts an attached image as user
content — an image-only vision prompt is valid and Run proceeds; blocks ONLY a
genuinely-empty message, and the reason renders PROMINENTLY right above the Run button.
tsc clean; vitest 1076/1076 (89 files); next build green.
Customer Machines showed a real but NON-interactive catalog (region chips + every size row were static text) under the "launch your first machine" state, so a data-rich priced catalog you couldn't click read as "not clickable / fake." Make it a real launch surface; finish the last /paas->/cloud data wiring in the cluster path.
- MachineCatalog: every size row is now clickable -> opens the real LaunchDrawer preselected on that size (and region); region chips are selectable filters (filter the size list via pure filterSizes + preset the launch region). Rows reflow to a mobile-friendly 2-column layout (no fixed 4-column table). No fabricated data: with no onLaunch the rows stay informational and an empty catalog still renders nothing.
- LaunchDrawer: accepts initialSize/initialRegion to open preselected.
- CustomerMachines: one openLaunch(preset) opener feeds the header button, empty-state CTA, and the catalog.
- visor: capture the per-size regions[] visor already returns (was dropped in normalizeSize) + pure filterSizes(sizes, query, region), unit-tested.
- platform: repoint provisionCluster from the /paas service-token proxy to native cloud /v1 (/cloud/v1/org/{org}/cluster, user IAM session) - the last /paas call in the cluster path; cluster reads already use /cloud/v1/clusters.
tsc --noEmit clean; visor.test.ts 16/16 (added regions + filterSizes cases). Verified locally headless: tap a size -> drawer opens with the correct $24/mo quote; mobile 0px overflow. Live data lights up once the console redeploys (this branch's /cloud allow-list already admits machines/clusters/gpus) against cloud v1.786.26 which now serves GET /v1/machines.
Customer Machines showed a real but NON-interactive catalog (region chips + every size row were static text) under the "launch your first machine" state, so a data-rich priced catalog you couldn't click read as "not clickable / fake." Make it a real launch surface; finish the last /paas->/cloud data wiring in the cluster path.
- MachineCatalog: every size row is now clickable -> opens the real LaunchDrawer preselected on that size (and region); region chips are selectable filters (filter the size list via pure filterSizes + preset the launch region). Rows reflow to a mobile-friendly 2-column layout (no fixed 4-column table). No fabricated data: with no onLaunch the rows stay informational and an empty catalog still renders nothing.
- LaunchDrawer: accepts initialSize/initialRegion to open preselected.
- CustomerMachines: one openLaunch(preset) opener feeds the header button, empty-state CTA, and the catalog.
- visor: capture the per-size regions[] visor already returns (was dropped in normalizeSize) + pure filterSizes(sizes, query, region), unit-tested.
- platform: repoint provisionCluster from the /paas service-token proxy to native cloud /v1 (/cloud/v1/org/{org}/cluster, user IAM session) - the last /paas call in the cluster path; cluster reads already use /cloud/v1/clusters.
tsc --noEmit clean; visor.test.ts 16/16 (added regions + filterSizes cases). Verified locally headless: tap a size -> drawer opens with the correct $24/mo quote; mobile 0px overflow. Live data lights up once the console redeploys (this branch's /cloud allow-list already admits machines/clusters/gpus) against cloud v1.786.26 which now serves GET /v1/machines.
Backend rolls invisible to customers. Root cause of a real 'Could not load — Upstream
service is unavailable' (Dave/maxpower, Models catalog): cloud is single-replica
Recreate, so a deploy-roll has a brief downtime window; a read landing in it got a
502/503/504 and the console showed a scary manual-Retry card.
Fixed in the ONE shared fetch (client.ts authedFetch → the pure, injectable
resilientFetch) that BOTH the casibase-envelope (request) and plain-REST (restRequest)
paths flow through — covers EVERY client fetch (Models, Overview, Billing, CRM, CMS,
ERP, commerce, analytics, agents, prompts, …), DRY.
- Transient upstream (502/503/504 or a network connection error) on an IDEMPOTENT read
(GET/HEAD) → auto-retry with exponential backoff (300→900→2000ms, up to 3) BEFORE the
honest 'Could not load' card, so a momentary roll self-heals; the card shows ONLY on a
persistent outage (after retries exhaust).
- Genuine 4xx (401/403/404/402) → NOT retried (honest state immediately).
- Mutation (POST/PUT/PATCH/DELETE) → NOT auto-retried (a 5xx'd write may have applied —
re-sending could double-create; the user retries manually).
- Caller-aborted request → honored, never retried.
- The 401 silent-refresh (v8.4.29) is preserved as the second orthogonal resilience,
guarded against a refresh loop.
+13 tests (client-retry.test.ts): the exact Models-catalog 503→200 self-heal, budget
exhaust → honest error, network retry, 4xx/mutation no-retry, abort honored, 401 refresh
no-loop, + classification helpers.
v8.4.33 = the deployed superset (v8.4.32 native-apps set + this). tsc clean; vitest
1061/1061; next build green.
Backend rolls invisible to customers. Root cause of a real 'Could not load — Upstream
service is unavailable' (Dave/maxpower, Models catalog): cloud is single-replica
Recreate, so a deploy-roll has a brief downtime window; a read landing in it got a
502/503/504 and the console showed a scary manual-Retry card.
Fixed in the ONE shared fetch (client.ts authedFetch → the pure, injectable
resilientFetch) that BOTH the casibase-envelope (request) and plain-REST (restRequest)
paths flow through — covers EVERY client fetch (Models, Overview, Billing, CRM, CMS,
ERP, commerce, analytics, agents, prompts, …), DRY.
- Transient upstream (502/503/504 or a network connection error) on an IDEMPOTENT read
(GET/HEAD) → auto-retry with exponential backoff (300→900→2000ms, up to 3) BEFORE the
honest 'Could not load' card, so a momentary roll self-heals; the card shows ONLY on a
persistent outage (after retries exhaust).
- Genuine 4xx (401/403/404/402) → NOT retried (honest state immediately).
- Mutation (POST/PUT/PATCH/DELETE) → NOT auto-retried (a 5xx'd write may have applied —
re-sending could double-create; the user retries manually).
- Caller-aborted request → honored, never retried.
- The 401 silent-refresh (v8.4.29) is preserved as the second orthogonal resilience,
guarded against a refresh loop.
+13 tests (client-retry.test.ts): the exact Models-catalog 503→200 self-heal, budget
exhaust → honest error, network retry, 4xx/mutation no-retry, abort honored, 401 refresh
no-loop, + classification helpers.
v8.4.33 = the deployed superset (v8.4.32 native-apps set + this). tsc clean; vitest
1061/1061; next build green.
Maximize native app coverage in the console — bind ERP, Content (CMS), Analytics,
and Commerce to their canonical backends per-org / entitlement-gated, one canonical
way, no fabricated data. Contracts verified against source repos + live probes.
Analytics — rebound to the FOUR real cloud clients/analytics routes (overview/
timeseries/top/health; the module had called 5 non-existent endpoints with wrong
shapes). LLM lens is REAL live per-org data (hanzo.cloud_usage, prod ClickHouse);
web/commerce lenses honest-empty via the backend 'available' flag. Dropped the
fabricated Real-Time tab (no backend). Tabs: Overview + LLM (top models).
Content (CMS) — tabbed: NATIVE Collections + Media/DAM read live over Payload REST
through a new /cms user-bearer proxy. Payload's multi-tenant plugin isolates rows by
the IAM owner claim → each org reads ONLY its own (per-org, backend-enforced);
allow-list admits only the two tenant-scoped collections + media bytes, never the
users/tenants registry. Studio tab keeps the entitlement-gated admin embed.
ERP — tabbed + entitlement-gated (Frappe is single-tenant → brand-org/global-admin
only). Overview drives a REAL /v1/platform deploy of the ERPNext app (idempotent
create-project+app+deploy, live status). Accounting/Items/Sales are NATIVE Frappe
REST summary views (real erpnext-v15 DocType fields) over a new /erp proxy (Frappe
token auth, SSRF-clamped, read-only resource lists) — honest 'deploy ERP' until an
instance is live. Desk embeds the real desk once reachable.
Commerce — Products full CRUD (create+delete over /v1/product; validator needs
name+sku+slug); Store settings reads the org's real storefront (/v1/store/current).
Orders/Customers/Inventory/Promotions stay real per-org reads. Via the /commerce
bearer proxy (org from token owner). hanzoai/commerce is the ONE authority — NOT Medusa.
GPUs (drive-by) — KPI reconciled: was distinct-model count (6) vs the catalog table +
Launch drawer configs (9); now shows launchable configs with model count in the sub.
tsc clean; vitest 1050/1050 (+22); next build green (/cms + /erp routes registered).
Maximize native app coverage in the console — bind ERP, Content (CMS), Analytics,
and Commerce to their canonical backends per-org / entitlement-gated, one canonical
way, no fabricated data. Contracts verified against source repos + live probes.
Analytics — rebound to the FOUR real cloud clients/analytics routes (overview/
timeseries/top/health; the module had called 5 non-existent endpoints with wrong
shapes). LLM lens is REAL live per-org data (hanzo.cloud_usage, prod ClickHouse);
web/commerce lenses honest-empty via the backend 'available' flag. Dropped the
fabricated Real-Time tab (no backend). Tabs: Overview + LLM (top models).
Content (CMS) — tabbed: NATIVE Collections + Media/DAM read live over Payload REST
through a new /cms user-bearer proxy. Payload's multi-tenant plugin isolates rows by
the IAM owner claim → each org reads ONLY its own (per-org, backend-enforced);
allow-list admits only the two tenant-scoped collections + media bytes, never the
users/tenants registry. Studio tab keeps the entitlement-gated admin embed.
ERP — tabbed + entitlement-gated (Frappe is single-tenant → brand-org/global-admin
only). Overview drives a REAL /v1/platform deploy of the ERPNext app (idempotent
create-project+app+deploy, live status). Accounting/Items/Sales are NATIVE Frappe
REST summary views (real erpnext-v15 DocType fields) over a new /erp proxy (Frappe
token auth, SSRF-clamped, read-only resource lists) — honest 'deploy ERP' until an
instance is live. Desk embeds the real desk once reachable.
Commerce — Products full CRUD (create+delete over /v1/product; validator needs
name+sku+slug); Store settings reads the org's real storefront (/v1/store/current).
Orders/Customers/Inventory/Promotions stay real per-org reads. Via the /commerce
bearer proxy (org from token owner). hanzoai/commerce is the ONE authority — NOT Medusa.
GPUs (drive-by) — KPI reconciled: was distinct-model count (6) vs the catalog table +
Launch drawer configs (9); now shows launchable configs with model count in the sub.
tsc clean; vitest 1050/1050 (+22); next build green (/cms + /erp routes registered).
The zt cloud client bound /v1/mesh/services + /v1/edge/nodes and the heads +
proxy-allow landed, but the two module fetches were left on the /paas proxy.
Switch both to cloudProxyV1Url (the user-bearer /cloud proxy) like the other
repointed modules. Networks already used /v1/networks. Now all 12 infra pages
(compute/DO/platform/zt) read the native cloud /v1 gateway.
The zt cloud client bound /v1/mesh/services + /v1/edge/nodes and the heads +
proxy-allow landed, but the two module fetches were left on the /paas proxy.
Switch both to cloudProxyV1Url (the user-bearer /cloud proxy) like the other
repointed modules. Networks already used /v1/networks. Now all 12 infra pages
(compute/DO/platform/zt) read the native cloud /v1 gateway.
Surface the standalone, already-deployed Lux/Zoo web3 apps (Explorer,
Exchange, Bridge, Faucet, Safe, DEX, Wallet) as launch tiles in the Web3
category — not rebuilt in-console, opened at their own domains.
Modeled as a restored `kind: 'external'; href` CatalogEntry member (the
honest sum type for a standalone app that owns no in-console route) — it
slots into the `kind !== 'module'` fail-closed guards the module-only
collapse deliberately preserved, so productSubpages/resolveProductView/
destinationsFor/productModules never manufacture a dead route for it.
`openProduct` becomes the ONE opener: a module navigates to `/<id>`, an
external opens `href` in a new tab. Every card seam (nav, launcher, ⌘K,
category page, level-2 siblings) routes through it, so no external tile
can 404.
Per-entry brand scope (`brands?: BrandId[]` + pure `entryInBrandScope`,
mirroring `nodeNetworksForBrand`) keeps the two suites from cross-leaking
inside the shared Web3 category: Lux tiles show only on lux, Zoo only on
zoo. Every href is a real, verified deployment — no fabricated URLs.
Tests: per-entry brand-scope predicate (no cross-leak); tsc clean; full
suite 1019 passing.
Surface the standalone, already-deployed Lux/Zoo web3 apps (Explorer,
Exchange, Bridge, Faucet, Safe, DEX, Wallet) as launch tiles in the Web3
category — not rebuilt in-console, opened at their own domains.
Modeled as a restored `kind: 'external'; href` CatalogEntry member (the
honest sum type for a standalone app that owns no in-console route) — it
slots into the `kind !== 'module'` fail-closed guards the module-only
collapse deliberately preserved, so productSubpages/resolveProductView/
destinationsFor/productModules never manufacture a dead route for it.
`openProduct` becomes the ONE opener: a module navigates to `/<id>`, an
external opens `href` in a new tab. Every card seam (nav, launcher, ⌘K,
category page, level-2 siblings) routes through it, so no external tile
can 404.
Per-entry brand scope (`brands?: BrandId[]` + pure `entryInBrandScope`,
mirroring `nodeNetworksForBrand`) keeps the two suites from cross-leaking
inside the shared Web3 category: Lux tiles show only on lux, Zoo only on
zoo. Every href is a real, verified deployment — no fabricated URLs.
Tests: per-entry brand-scope predicate (no cross-leak); tsc clean; full
suite 1019 passing.
Two GLOBAL-ADMIN operator boards on admin.hanzo.ai (Observe, beside Business +
Finance), two lenses over ONE datastore table split on `kind`: Bots (kind=bot —
@hanzo/bot agents booted, gateway-connected) and Machines (kind=machine — raw VMs
visor opens). Each surfaces per-org/app/project count, active, and spend, grouped
org -> app -> project, sourced from the unified datastore (ClickHouse) via a new
`compute` admin-aggregate head. `/v1/admin/compute?kind=` is server-gated by
getAdminGate (the RED-H1 gate) and rewritten to app/admin/aggregate — no new proxy
or trust boundary.
- lib/api/admin-compute.ts: kind-parameterized, optional-safe client + pure
foldEvents/buildTree over both pre-aggregated {leaves} and raw {events} (9-col
datastore schema: org, app, project, kind, event, machine_id, size, price_cents,
ts). Rollup {count,active,spendCents}; normalizeCompute(raw, kind) filters to kind.
- components/products/ComputeModule.tsx: ONE ComputeBoard({kind}); BotsModule /
MachinesModule are thin wrappers (collapsible org->app->project tree + KPIs,
honest loading/403/404/empty states — honest-empty until the emitter lands).
- registry: `bots` + `vms` (Machines) entries, admin:true; the admin machines module
is aliased to avoid the clash with the per-org customer Machines (visor).
- admin-aggregate.ts + next.config.mjs: `compute` added to the admin read heads.
- Pairs with cloud GET /v1/admin/compute (hanzoai/cloud#62).
tsc clean; npm test 1012/1012; next build green.
Two GLOBAL-ADMIN operator boards on admin.hanzo.ai (Observe, beside Business +
Finance), two lenses over ONE datastore table split on `kind`: Bots (kind=bot —
@hanzo/bot agents booted, gateway-connected) and Machines (kind=machine — raw VMs
visor opens). Each surfaces per-org/app/project count, active, and spend, grouped
org -> app -> project, sourced from the unified datastore (ClickHouse) via a new
`compute` admin-aggregate head. `/v1/admin/compute?kind=` is server-gated by
getAdminGate (the RED-H1 gate) and rewritten to app/admin/aggregate — no new proxy
or trust boundary.
- lib/api/admin-compute.ts: kind-parameterized, optional-safe client + pure
foldEvents/buildTree over both pre-aggregated {leaves} and raw {events} (9-col
datastore schema: org, app, project, kind, event, machine_id, size, price_cents,
ts). Rollup {count,active,spendCents}; normalizeCompute(raw, kind) filters to kind.
- components/products/ComputeModule.tsx: ONE ComputeBoard({kind}); BotsModule /
MachinesModule are thin wrappers (collapsible org->app->project tree + KPIs,
honest loading/403/404/empty states — honest-empty until the emitter lands).
- registry: `bots` + `vms` (Machines) entries, admin:true; the admin machines module
is aliased to avoid the clash with the per-org customer Machines (visor).
- admin-aggregate.ts + next.config.mjs: `compute` added to the admin read heads.
- Pairs with cloud GET /v1/admin/compute (hanzoai/cloud#62).
tsc clean; npm test 1012/1012; next build green.
Casdoor refresh tokens are ALSO ~3.6KB full-user JWTs, so v8.4.30 sealed cookie
was still 5560 bytes (> browser 4KB cap → a real browser would reject it). Split:
- hz_session (Path=/, sealed {access-exp, projected claims}, ~1KB): resolveUser/BFF.
- hz_rt (Path=/auth, sealed refresh token, chunked hz_rt0/hz_rt1): sent ONLY to
/auth — never to /v1 or the BFF, so no header bloat / gateway-431 risk.
Both sealed (integrity). Live-verified: establish/GET/refresh-rotate all 200.
Casdoor refresh tokens are ALSO ~3.6KB full-user JWTs, so v8.4.30 sealed cookie
was still 5560 bytes (> browser 4KB cap → a real browser would reject it). Split:
- hz_session (Path=/, sealed {access-exp, projected claims}, ~1KB): resolveUser/BFF.
- hz_rt (Path=/auth, sealed refresh token, chunked hz_rt0/hz_rt1): sent ONLY to
/auth — never to /v1 or the BFF, so no header bloat / gateway-431 risk.
Both sealed (integrity). Live-verified: establish/GET/refresh-rotate all 200.
The v8.4.29 sealed cookie held the raw Casdoor access token (whole user object,
~9.8 KB) which exceeds the browser 4 KB per-cookie limit → a real browser would
reject it (curl does not). sealSession now projects to the small display/authz
claim set + refresh token + exp → a bounded ~1 KB cookie. Live-verified.
The v8.4.29 sealed cookie held the raw Casdoor access token (whole user object,
~9.8 KB) which exceeds the browser 4 KB per-cookie limit → a real browser would
reject it (curl does not). sealSession now projects to the small display/authz
claim set + refresh token + exp → a bounded ~1 KB cookie. Live-verified.
The last ComingSoon stub is now a real module. The cloud mlsvc
(hanzoai/cloud clients/ml) fronts the Kubeflow-family CRDs as REST, so
KubeflowModule is the read-only orchestration + control-plane lens over
that live surface (distinct from Fine-tuning's train-my-model wizard):
- Control-plane health strip from a REAL probe (GET /v1/train/health) —
which Kubeflow operators/CRDs (Trainer/trainjobs, Katib/experiments)
are actually served; honest connected/degraded/not-reporting states.
- Pipelines = Katib Experiments (GET /v1/train/experiments).
- Runs = trainer TrainJobs (GET /v1/train/jobs).
Pipelines/runs REUSE TrainApi (one client, no duplication); the new
KubeflowApi adds only the control-plane probe the console lacked (a
tolerant fetch that reads the 503 body restGet would discard). The
/training proxy allowlist gains train/health (additive, read-only).
Registry: kubeflow flips soon -> enabled, routes -> KubeflowModule.
Honest states only, no fabricated data. tsc clean; 84 registry tests pass.
The last ComingSoon stub is now a real module. The cloud mlsvc
(hanzoai/cloud clients/ml) fronts the Kubeflow-family CRDs as REST, so
KubeflowModule is the read-only orchestration + control-plane lens over
that live surface (distinct from Fine-tuning's train-my-model wizard):
- Control-plane health strip from a REAL probe (GET /v1/train/health) —
which Kubeflow operators/CRDs (Trainer/trainjobs, Katib/experiments)
are actually served; honest connected/degraded/not-reporting states.
- Pipelines = Katib Experiments (GET /v1/train/experiments).
- Runs = trainer TrainJobs (GET /v1/train/jobs).
Pipelines/runs REUSE TrainApi (one client, no duplication); the new
KubeflowApi adds only the control-plane probe the console lacked (a
tolerant fetch that reads the 503 body restGet would discard). The
/training proxy allowlist gains train/health (additive, read-only).
Registry: kubeflow flips soon -> enabled, routes -> KubeflowModule.
Honest states only, no fabricated data. tsc clean; 84 registry tests pass.
The 94-page screenshot sweep signed in per test (beforeEach), so ~94 logins as
z@hanzo.ai tripped IAM's 'too many login attempts' rate-limit around page 35 —
that's the security feature working, not a page failure. Switch to a shared
serial context: one signIn in beforeAll, every page reuses the cookie. Faster
(~1 login vs 94) and no rate-limit, so the full sweep completes.
The 94-page screenshot sweep signed in per test (beforeEach), so ~94 logins as
z@hanzo.ai tripped IAM's 'too many login attempts' rate-limit around page 35 —
that's the security feature working, not a page failure. Switch to a shared
serial context: one signIn in beforeAll, every page reuses the cookie. Faster
(~1 login vs 94) and no rate-limit, so the full sweep completes.
- off-list secrets path: accept 401 OR 404 (both block the tunnel; prod hits the
auth gate → 401 before the 404 allow-list check). A 2xx would be the real bug.
- API key extraction: match only a FULL hk- token (16+ chars, no ellipsis) so it
never grabs the masked 'hk-2f18…' account-card display as a credential.
- /v1/messages: pick a model that is ACTUALLY in /v1/models right now instead of
hardcoding claude-sonnet-4-6 (not provisioned on DO → correct 'not available').
All verified against live prod; the surfaces themselves (proxy gating, key mint,
Anthropic-compat inference) already work — these were test-data/expectation drift.
- off-list secrets path: accept 401 OR 404 (both block the tunnel; prod hits the
auth gate → 401 before the 404 allow-list check). A 2xx would be the real bug.
- API key extraction: match only a FULL hk- token (16+ chars, no ellipsis) so it
never grabs the masked 'hk-2f18…' account-card display as a credential.
- /v1/messages: pick a model that is ACTUALLY in /v1/models right now instead of
hardcoding claude-sonnet-4-6 (not provisioned on DO → correct 'not available').
All verified against live prod; the surfaces themselves (proxy gating, key mint,
Anthropic-compat inference) already work — these were test-data/expectation drift.
Extends the EXISTING finance living-overview to read the now-multi-vendor
/v1/admin/finance (cloud enriches its cost side from commerce /v1/costs):
- FinanceCost gains {configured, totalCents, vendors[], period}; margin/spend now
reflect the whole-platform COGS (DO compute + LLM providers), not DO MTD alone.
- fromFinance projects cost.vendors onto a 'vendorCogs' distribution (donut) and
makes the headline spend + margin the commerce COGS — decoupled from DO, so a
missing DO_API_TOKEN no longer blanks COGS/margin (DO stays the credit/runway
treasury view + burn-down series only).
- registry: 'COGS (all vendors)' headline + a 'COGS by vendor' donut beside the
burn-down; profitability verdict now gates on commerce COGS, not DO.
- reads ONLY /v1/admin/finance — no console-side /costs proxy (the admin-cogs
duplicate is superseded and dropped).
- tests: vendor donut, zero-line pruning, DO-off-COGS-still-flows, COGS-off honest
empty. 380 unit tests + tsc + next build green.
Extends the EXISTING finance living-overview to read the now-multi-vendor
/v1/admin/finance (cloud enriches its cost side from commerce /v1/costs):
- FinanceCost gains {configured, totalCents, vendors[], period}; margin/spend now
reflect the whole-platform COGS (DO compute + LLM providers), not DO MTD alone.
- fromFinance projects cost.vendors onto a 'vendorCogs' distribution (donut) and
makes the headline spend + margin the commerce COGS — decoupled from DO, so a
missing DO_API_TOKEN no longer blanks COGS/margin (DO stays the credit/runway
treasury view + burn-down series only).
- registry: 'COGS (all vendors)' headline + a 'COGS by vendor' donut beside the
burn-down; profitability verdict now gates on commerce COGS, not DO.
- reads ONLY /v1/admin/finance — no console-side /costs proxy (the admin-cogs
duplicate is superseded and dropped).
- tests: vendor donut, zero-line pruning, DO-off-COGS-still-flows, COGS-off honest
empty. 380 unit tests + tsc + next build green.
Issue 1 — Status/Logs/Metrics not wired (o11y):
- /v1/o11y is NOT 503 (stale) — it's a 403 (auth) reverse-proxy to SigNoz, whose
runtime is un-set-up (setupCompleted:false, no data). Status read /paas/apps which
reports ZERO apps; Logs read /paas/logs which 401s (no such endpoint). Neither ever
showed data. The live signal is VictoriaMetrics (up{job=*-health}, ~29 targets).
- New read-only same-origin proxy app/telemetry/[...path] -> VictoriaMetrics query API
(authenticated, GET-only, allow-listed to /api/v1/query|query_range|series|labels|
label/*/values, traversal-hardened, honest 501 when VM_URL unset).
- lib/api/telemetry.ts (pure parse + service-health helpers, unit-tested).
- StatusModule: real up{} service-health board (down-first, healthy/down counts).
- MetricsModule: real VM infra dashboard (KPIs, healthy/targets-over-time, health
donut, down-now) — replaces the unwired 'metrics' NativeOverview; distinct from
AI Metrics. LogsModule: honest 'no log store deployed' state (no fabricated grid).
Issue 2 — launch-machine form: FieldSelect used @hanzo/gui <Select native>, which in
gui 7.3.0 emits bare <option> with NO <select> wrapper — every dropdown app-wide (27
usages) rendered as a non-interactive flat list. In the launch drawer this buried the
Quote + Launch button. FieldSelect now renders a real native <select> (theme-var
styled, native mobile picker), fixing the region picker and all other dropdowns.
Issue 3 — mobile: the FieldSelect fix repairs every form's pickers; DataTable now
scrolls horizontally on overflow instead of clipping wide tables (cut-off columns).
Verified live (VictoriaMetrics + real z@hanzo.ai session): Status 29 services/22
healthy/7 down, Metrics dashboard, Logs honest state, launch drawer native region
select with Launch visible, mobile table scroll. tsc clean; 964 vitest pass.
Also: dev-only next.config rewrite (DEV_CLOUD_ORIGIN, inert in prod) to run the
console locally against a real backend; removed orphaned observability/metrics.ts.
Issue 1 — Status/Logs/Metrics not wired (o11y):
- /v1/o11y is NOT 503 (stale) — it's a 403 (auth) reverse-proxy to SigNoz, whose
runtime is un-set-up (setupCompleted:false, no data). Status read /paas/apps which
reports ZERO apps; Logs read /paas/logs which 401s (no such endpoint). Neither ever
showed data. The live signal is VictoriaMetrics (up{job=*-health}, ~29 targets).
- New read-only same-origin proxy app/telemetry/[...path] -> VictoriaMetrics query API
(authenticated, GET-only, allow-listed to /api/v1/query|query_range|series|labels|
label/*/values, traversal-hardened, honest 501 when VM_URL unset).
- lib/api/telemetry.ts (pure parse + service-health helpers, unit-tested).
- StatusModule: real up{} service-health board (down-first, healthy/down counts).
- MetricsModule: real VM infra dashboard (KPIs, healthy/targets-over-time, health
donut, down-now) — replaces the unwired 'metrics' NativeOverview; distinct from
AI Metrics. LogsModule: honest 'no log store deployed' state (no fabricated grid).
Issue 2 — launch-machine form: FieldSelect used @hanzo/gui <Select native>, which in
gui 7.3.0 emits bare <option> with NO <select> wrapper — every dropdown app-wide (27
usages) rendered as a non-interactive flat list. In the launch drawer this buried the
Quote + Launch button. FieldSelect now renders a real native <select> (theme-var
styled, native mobile picker), fixing the region picker and all other dropdowns.
Issue 3 — mobile: the FieldSelect fix repairs every form's pickers; DataTable now
scrolls horizontally on overflow instead of clipping wide tables (cut-off columns).
Verified live (VictoriaMetrics + real z@hanzo.ai session): Status 29 services/22
healthy/7 down, Metrics dashboard, Logs honest state, launch drawer native region
select with Launch visible, mobile table scroll. tsc clean; 964 vitest pass.
Also: dev-only next.config rewrite (DEV_CLOUD_ORIGIN, inert in prod) to run the
console locally against a real backend; removed orphaned observability/metrics.ts.
The Templates gallery cards were text-only and dead-ended after fork
("Draft — deploy it to go live" with no action). Two fixes:
1. Preview banner: render the gallery screenshot (t.preview) with a branded
gradient fallback (stable per category + framework glyph) when it's absent
or 404s — cards are visual immediately and auto-upgrade to the real shot
once gallery.hanzo.ai serves it. No broken images, no fabricated screenshots.
2. Deploy flow: fork→draft now shows a clear "Deploy" button that ships the
project live via projectsvc git deploy (POST /v1/projects/:slug/deploy
{source:git}); building → "Check status" → "Open site" (liveUrl). Each
phase shows exactly one next step, so "how to deploy" is never ambiguous.
TemplatesApi gains deploy()/status()/isLive()/normalizeDeployResult over the
existing same-origin /v1 surface. 18 vitest tests, next build green (14/14).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The Templates gallery cards were text-only and dead-ended after fork
("Draft — deploy it to go live" with no action). Two fixes:
1. Preview banner: render the gallery screenshot (t.preview) with a branded
gradient fallback (stable per category + framework glyph) when it's absent
or 404s — cards are visual immediately and auto-upgrade to the real shot
once gallery.hanzo.ai serves it. No broken images, no fabricated screenshots.
2. Deploy flow: fork→draft now shows a clear "Deploy" button that ships the
project live via projectsvc git deploy (POST /v1/projects/:slug/deploy
{source:git}); building → "Check status" → "Open site" (liveUrl). Each
phase shows exactly one next step, so "how to deploy" is never ambiguous.
TemplatesApi gains deploy()/status()/isLive()/normalizeDeployResult over the
existing same-origin /v1 surface. 18 vitest tests, next build green (14/14).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Add an 'Open in builder' primary CTA to each starter card that deep-links to
the hanzo.app builder pre-seeded to customize this template by prompt:
<app>/dev?template=<source>&prompt=<seed>&action=edit. A small inline input
takes an optional free-text customization; the seed prompt carries the template
context (title/framework/description) so the builder auto-starts the first
generation.
- buildBuilderUrl(template, userText, appBase) + customizePrompt(): pure,
injection-safe (single URL-encoded query params), unit-tested (+7 tests).
- config.appUrl (NEXT_PUBLIC_APP_URL, default https://hanzo.app).
- 'Fork / deploy' kept as the secondary action + honest 404 gallery fallback.
tsc --noEmit clean; vitest 881/881.
Add an 'Open in builder' primary CTA to each starter card that deep-links to
the hanzo.app builder pre-seeded to customize this template by prompt:
<app>/dev?template=<source>&prompt=<seed>&action=edit. A small inline input
takes an optional free-text customization; the seed prompt carries the template
context (title/framework/description) so the builder auto-starts the first
generation.
- buildBuilderUrl(template, userText, appBase) + customizePrompt(): pure,
injection-safe (single URL-encoded query params), unit-tested (+7 tests).
- config.appUrl (NEXT_PUBLIC_APP_URL, default https://hanzo.app).
- 'Fork / deploy' kept as the secondary action + honest 404 gallery fallback.
tsc --noEmit clean; vitest 881/881.
RED reviewed v8.4.22's embeds (0 critical; SSRF clamp, iframe SOP, no-credential-
injection, honest normalizers all REFUTED). Fixes the console residuals RED flagged:
- Server-side entitlement gate: /embed-status resolves the caller's org (token owner)
and returns `entitled` per app. cms/erp/help are all brand-owned single instances,
so a non-owning (customer) org gets entitled:false + NO embed URL + no probe -> the
module shows the provision panel. Only a brand-org member / global admin embeds.
This is now the AUTHORITATIVE gate (the client check was cosmetic). Client normalizer
fails closed (entitled strict-true; stale server -> provision panel, never a frame).
- Help is brand-owned too (was embed-for-all) -> a customer never frames the shared
Frappe Helpdesk (removes unverified cross-org ticket-visibility risk).
- Dropped the false 'org==tenant enforced server-side' claims in EmbeddedApp/
embed-hosts/module docstrings (the console gates WHO it frames; the shared app still
owes its own per-org isolation -> separate CMS-side fix).
- Trimmed the iframe sandbox (dropped allow-top-navigation-by-user-activation,
allow-popups-to-escape-sandbox, clipboard-read).
- /waitlist: bind recorded email to the session account; stop forwarding forgeable XFF.
tsc clean; vitest 952/952 (+13 entitlement/brand-org/fail-closed); next build green.
RED reviewed v8.4.22's embeds (0 critical; SSRF clamp, iframe SOP, no-credential-
injection, honest normalizers all REFUTED). Fixes the console residuals RED flagged:
- Server-side entitlement gate: /embed-status resolves the caller's org (token owner)
and returns `entitled` per app. cms/erp/help are all brand-owned single instances,
so a non-owning (customer) org gets entitled:false + NO embed URL + no probe -> the
module shows the provision panel. Only a brand-org member / global admin embeds.
This is now the AUTHORITATIVE gate (the client check was cosmetic). Client normalizer
fails closed (entitled strict-true; stale server -> provision panel, never a frame).
- Help is brand-owned too (was embed-for-all) -> a customer never frames the shared
Frappe Helpdesk (removes unverified cross-org ticket-visibility risk).
- Dropped the false 'org==tenant enforced server-side' claims in EmbeddedApp/
embed-hosts/module docstrings (the console gates WHO it frames; the shared app still
owes its own per-org isolation -> separate CMS-side fix).
- Trimmed the iframe sandbox (dropped allow-top-navigation-by-user-activation,
allow-popups-to-escape-sandbox, clipboard-read).
- /waitlist: bind recorded email to the session account; stop forwarding forgeable XFF.
tsc clean; vitest 952/952 (+13 entitlement/brand-org/fail-closed); next build green.
CMS was a window.open link-out; ERP/Help were 'soon' placeholders. Port all three
into the console as EMBEDDED (SSO iframe) or HONEST-provision surfaces, binding to
the canonical Payload/Frappe backends (not reimplemented). CRM stays the native
/v1/crm reference; these are the embed half of the Business-OS.
- EmbeddedApp: the one way to frame a canonical app IN the console shell (full-height
iframe, scoped sandbox, real loading + honest 'Open full screen' fallback — never a
fabricated load verdict). ProvisionPanel: DRY honest pre-provision surface over the
real /waitlist intake.
- embed-hosts.ts (PURE): white-label cms|erp|help.<brand> host derivation.
- /embed-status BFF + pure embed-probe.ts: session-gated reachability probe, NO
god-mode, SSRF-clamped to known brand domains, AbortSignal-bounded.
- CmsModule: embed the Studio for a brand-org member/global admin ONLY (customer org
gets an honest provision panel — no cross-tenant framing of the shared instance).
- ErpModule: erp.<brand> is 502 -> honest 'Deploy ERP' panel; SAME gate embeds the
real desk once live. HelpModule: embeds the live shared brand support desk (Frappe
scopes tickets per-user via SSO).
- registry: erp + helpdesk soon -> enabled native modules.
Verified against live cluster + repos (single shared HANZO_ORG=hanzo instances; no
per-customer-org isolation yet) so nothing claims tenancy it doesn't have.
typecheck 0 errors; vitest 914/914 (+21); next build green (/embed-status registered).
CMS was a window.open link-out; ERP/Help were 'soon' placeholders. Port all three
into the console as EMBEDDED (SSO iframe) or HONEST-provision surfaces, binding to
the canonical Payload/Frappe backends (not reimplemented). CRM stays the native
/v1/crm reference; these are the embed half of the Business-OS.
- EmbeddedApp: the one way to frame a canonical app IN the console shell (full-height
iframe, scoped sandbox, real loading + honest 'Open full screen' fallback — never a
fabricated load verdict). ProvisionPanel: DRY honest pre-provision surface over the
real /waitlist intake.
- embed-hosts.ts (PURE): white-label cms|erp|help.<brand> host derivation.
- /embed-status BFF + pure embed-probe.ts: session-gated reachability probe, NO
god-mode, SSRF-clamped to known brand domains, AbortSignal-bounded.
- CmsModule: embed the Studio for a brand-org member/global admin ONLY (customer org
gets an honest provision panel — no cross-tenant framing of the shared instance).
- ErpModule: erp.<brand> is 502 -> honest 'Deploy ERP' panel; SAME gate embeds the
real desk once live. HelpModule: embeds the live shared brand support desk (Frappe
scopes tickets per-user via SSO).
- registry: erp + helpdesk soon -> enabled native modules.
Verified against live cluster + repos (single shared HANZO_ORG=hanzo instances; no
per-customer-org isolation yet) so nothing claims tenancy it doesn't have.
typecheck 0 errors; vitest 914/914 (+21); next build green (/embed-status registered).
Investigated the "brand host (cloud.lux.network) hangs during render, while
console.hanzo.ai is fast" report. It does NOT reproduce in the app and cannot by
design: the page-render path (app/layout.tsx + (dashboard)/layout.tsx, the only
server components) does ZERO per-brand network fetch — no next/headers, cookies(),
generateMetadata, or server-only render fetch. Brand resolves from window.location
in the browser; SSR uses the build-time NEXT_PUBLIC_DEFAULT_HOST, so the server
HTML is byte-identical for every brand host (verified: cloud.lux.network and
console.hanzo.ai return the SAME md5, <title>Hanzo Cloud Console</title>, HTTP 200
in ~4-18ms for lux/zoo/pars/hanzo). The prod origin difference is an ingress/
routing artifact, not app SSR (out of scope; app code only).
The real in-code "no timeout → the route wedges" hazard (the described failure
class) IS fixed: every request-time server fetch — the /v1/* BFF proxies plus IAM/
cloud identity resolution — had NO upstream timeout, so a reachable-but-silent
backend blocked the route until the client gave up.
Fix, DRY: one src/lib/server/fetch-timeout.ts (fetchWithTimeout) — a bounded
AbortSignal COMPOSED with any caller signal (init.signal / req.signal), so a
request aborts on EITHER a client disconnect OR the timeout. Default 10_000ms, env
HANZO_UPSTREAM_TIMEOUT_MS. On timeout it rejects like an aborted fetch, so every
existing catch keeps its honest fallback (resolveUser → null → 401; proxies → 502).
Threaded through identity.ts (all 5 IAM/cloud calls), bearer-proxy.ts (the shared
proxy engine → cloud/ai/vm/tasksd/commerce/superbase), iam-proxy.ts, and the
custom proxies (/paas, /training, /admin/kms, /billing, /billing/topup/wallet,
/waitlist). The /nodes per-brand luxd RPC probe was already bounded — left as-is.
Verification: npm run typecheck 0 errors; npm test 823/823 (69 files, +6 new
fetch-timeout tests); next build green (all routes); Host-header curl test returns
200 fast for BOTH cloud.lux.network and console.hanzo.ai.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Investigated the "brand host (cloud.lux.network) hangs during render, while
console.hanzo.ai is fast" report. It does NOT reproduce in the app and cannot by
design: the page-render path (app/layout.tsx + (dashboard)/layout.tsx, the only
server components) does ZERO per-brand network fetch — no next/headers, cookies(),
generateMetadata, or server-only render fetch. Brand resolves from window.location
in the browser; SSR uses the build-time NEXT_PUBLIC_DEFAULT_HOST, so the server
HTML is byte-identical for every brand host (verified: cloud.lux.network and
console.hanzo.ai return the SAME md5, <title>Hanzo Cloud Console</title>, HTTP 200
in ~4-18ms for lux/zoo/pars/hanzo). The prod origin difference is an ingress/
routing artifact, not app SSR (out of scope; app code only).
The real in-code "no timeout → the route wedges" hazard (the described failure
class) IS fixed: every request-time server fetch — the /v1/* BFF proxies plus IAM/
cloud identity resolution — had NO upstream timeout, so a reachable-but-silent
backend blocked the route until the client gave up.
Fix, DRY: one src/lib/server/fetch-timeout.ts (fetchWithTimeout) — a bounded
AbortSignal COMPOSED with any caller signal (init.signal / req.signal), so a
request aborts on EITHER a client disconnect OR the timeout. Default 10_000ms, env
HANZO_UPSTREAM_TIMEOUT_MS. On timeout it rejects like an aborted fetch, so every
existing catch keeps its honest fallback (resolveUser → null → 401; proxies → 502).
Threaded through identity.ts (all 5 IAM/cloud calls), bearer-proxy.ts (the shared
proxy engine → cloud/ai/vm/tasksd/commerce/superbase), iam-proxy.ts, and the
custom proxies (/paas, /training, /admin/kms, /billing, /billing/topup/wallet,
/waitlist). The /nodes per-brand luxd RPC probe was already bounded — left as-is.
Verification: npm run typecheck 0 errors; npm test 823/823 (69 files, +6 new
fetch-timeout tests); next build green (all routes); Host-header curl test returns
200 fast for BOTH cloud.lux.network and console.hanzo.ai.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
A tenant (non-global) admin like `hanzo/z` can only ever act in their OWN org —
the server pins them there and every cross-tenant call 403s. But `OrgGate`
restored a persisted "last org" (`hz_last_org` / `hanzo.console.org`) on sign-in
WITHOUT checking the user can access it. So a leftover `adnexus` scope (from a
prior global-admin switch) made every org-scoped call — e.g.
`/org/iam/get-organization-projects?organization=adnexus` — 403 for z.
Fix: in the OrgGate seed effect, a non-global admin is ALWAYS hard-pinned to
`owner`. If a stale cross-tenant scope is active it's reset and the page reloads
once (guarded on `currentOrg() !== owner`, so it can't loop) — self-healing
existing stale state and preventing recurrence. Global admins keep the
switch-and-restore behavior. Complements the v8.4.18/19 gates on the admin
aggregates; this closes the org-SCOPED 403s.
Co-authored-by: dev <dev@hanzo.ai>
A tenant (non-global) admin like `hanzo/z` can only ever act in their OWN org —
the server pins them there and every cross-tenant call 403s. But `OrgGate`
restored a persisted "last org" (`hz_last_org` / `hanzo.console.org`) on sign-in
WITHOUT checking the user can access it. So a leftover `adnexus` scope (from a
prior global-admin switch) made every org-scoped call — e.g.
`/org/iam/get-organization-projects?organization=adnexus` — 403 for z.
Fix: in the OrgGate seed effect, a non-global admin is ALWAYS hard-pinned to
`owner`. If a stale cross-tenant scope is active it's reset and the page reloads
once (guarded on `currentOrg() !== owner`, so it can't loop) — self-healing
existing stale state and preventing recurrence. Global admins keep the
switch-and-restore behavior. Complements the v8.4.18/19 gates on the admin
aggregates; this closes the org-SCOPED 403s.
Co-authored-by: dev <dev@hanzo.ai>
Follows v8.4.18 (#44), which gated only the overview aggregate + /paas probe.
This release also gates the OrgSwitcher/CommandPalette org list and BrandLogo's
org-logo lookup, so a per-org (non-global) admin's dashboard load fires ZERO
cross-tenant /admin/iam calls — no more 403 noise in the browser console.
Follows v8.4.18 (#44), which gated only the overview aggregate + /paas probe.
This release also gates the OrgSwitcher/CommandPalette org list and BrandLogo's
org-logo lookup, so a per-org (non-global) admin's dashboard load fires ZERO
cross-tenant /admin/iam calls — no more 403 noise in the browser console.
v8.4.18 (#44) gated the platform-overview loader (`/v1/admin/overview` + the
`/paas/apps` health probe) on `isGlobalAdmin`, but the dashboard chrome still
fired two more CROSS-TENANT admin calls for every user on every load:
- `/admin/iam/get-organizations?owner=admin` — the OrgSwitcher + CommandPalette
org list, server-gated to global (admin-org) admins.
- `/admin/iam/get-organization?id=admin/<tenant>` — BrandLogo's org-logo lookup.
For a per-ORG admin who is NOT a global admin (e.g. `hanzo/z`) both 403, so a
tenant still saw a wall of red 403s in the browser console on every dashboard
load even after v8.4.18.
Gate them with the SAME `useIsGlobalAdmin` signal the overview loader + nav use:
- OrgSwitcher / CommandPalette: skip `get-organizations` for a non-global-admin
(they still see their current org + "Create organization"; just no cross-tenant
switch list).
- BrandLogo: a tenant reads its OWN org logo via the org-scoped `/org/iam` proxy
(`TeamApi.organization`, which authorizes any member and pins to the caller's
own org) instead of the admin-gated `/admin/iam` proxy — the logo still works,
minus the 403.
Global admins are unchanged. No permission or server change; server gates still
enforce. typecheck + 887 tests + next build all green.
v8.4.18 (#44) gated the platform-overview loader (`/v1/admin/overview` + the
`/paas/apps` health probe) on `isGlobalAdmin`, but the dashboard chrome still
fired two more CROSS-TENANT admin calls for every user on every load:
- `/admin/iam/get-organizations?owner=admin` — the OrgSwitcher + CommandPalette
org list, server-gated to global (admin-org) admins.
- `/admin/iam/get-organization?id=admin/<tenant>` — BrandLogo's org-logo lookup.
For a per-ORG admin who is NOT a global admin (e.g. `hanzo/z`) both 403, so a
tenant still saw a wall of red 403s in the browser console on every dashboard
load even after v8.4.18.
Gate them with the SAME `useIsGlobalAdmin` signal the overview loader + nav use:
- OrgSwitcher / CommandPalette: skip `get-organizations` for a non-global-admin
(they still see their current org + "Create organization"; just no cross-tenant
switch list).
- BrandLogo: a tenant reads its OWN org logo via the org-scoped `/org/iam` proxy
(`TeamApi.organization`, which authorizes any member and pins to the caller's
own org) instead of the admin-gated `/admin/iam` proxy — the logo still works,
minus the 403.
Global admins are unchanged. No permission or server change; server gates still
enforce. typecheck + 887 tests + next build all green.
The platform overview home (`livingOverviewModule('overview')`) is the default
landing for every signed-in user, but its loader fired the CROSS-TENANT
`/v1/admin/overview` aggregate (and the `/paas/apps` health probe) for everyone.
Those are server-gated to global (admin-org) admins, so a tenant user — even an
org's OWN admin, e.g. `hanzo/z` — got a wall of repeated `403 (Forbidden)` in the
browser console on every dashboard load.
It "worked" only because the loader caught the 403 and fell back to the org-scoped
usage ledger; the board rendered, but spammed the console with doomed requests.
Fix: thread `isGlobalAdmin` (already resolved by `useIsGlobalAdmin`, the same
signal the nav/launcher use to hide admin surfaces) through the ONE loader call
site into `OverviewContext`, and in the platform-overview loader skip the admin
aggregate + apps probe for non-global-admins — going straight to the org-scoped
usage ledger (the exact source the catch-fallback already used). Global admins are
unchanged. `withHealth` gains an optional `probeApps` (default true) so the four
other, already admin-gated overviews are untouched.
Net: a tenant admin's overview renders identically, minus the 403 console noise;
no permission or server change.
Co-authored-by: dev <dev@hanzo.ai>
The platform overview home (`livingOverviewModule('overview')`) is the default
landing for every signed-in user, but its loader fired the CROSS-TENANT
`/v1/admin/overview` aggregate (and the `/paas/apps` health probe) for everyone.
Those are server-gated to global (admin-org) admins, so a tenant user — even an
org's OWN admin, e.g. `hanzo/z` — got a wall of repeated `403 (Forbidden)` in the
browser console on every dashboard load.
It "worked" only because the loader caught the 403 and fell back to the org-scoped
usage ledger; the board rendered, but spammed the console with doomed requests.
Fix: thread `isGlobalAdmin` (already resolved by `useIsGlobalAdmin`, the same
signal the nav/launcher use to hide admin surfaces) through the ONE loader call
site into `OverviewContext`, and in the platform-overview loader skip the admin
aggregate + apps probe for non-global-admins — going straight to the org-scoped
usage ledger (the exact source the catch-fallback already used). Global admins are
unchanged. `withHealth` gains an optional `probeApps` (default true) so the four
other, already admin-gated overviews are untouched.
Net: a tenant admin's overview renders identically, minus the 403 console noise;
no permission or server change.
Co-authored-by: dev <dev@hanzo.ai>
* feat(console): consolidate CRM + Accessibility Business-OS modules over native /v1
CRM — the first Business-OS brick — as ONE canonical module over the native-Go
cloud /v1/crm surface (cloud clients/crm on Base/SQLite: companies, contacts,
opportunities; a port of Twenty's core model), per-org via the user-bearer /cloud
proxy. Consolidates the two competing CRM PRs (#38 feat/console2-crm and #39
crm-work): keeps #39's richer routed-tab views + defensive normalizers + tests,
re-paths its API from the explicit /cloud/v1 form to the canonical same-origin
originV1Url('crm') (matching Agents/Evals/Prompts — the one way), and grafts #38's
next.config `crm` head rewrite + per-row delete. crm.ts is the single typed mirror
of the /v1/crm contract (one method per route); every row is org-scoped SERVER-SIDE
from the token owner claim, with honest loading/empty/error states in @hanzo/gui.
Accessibility — a Wix-style WCAG scanner for the site being built. Runs Deque's
axe-core against the current page 100% client-side (engine lazy-loaded into its own
chunk, never the main bundle); pure sort/summarize/WCAG-label logic in
~/lib/a11y/scan is unit-tested without a browser or engine.
- next.config.mjs / proxy-allow.ts: allow-list the `crm` head on both the rewrite
and the bearer proxy (same least-privilege path as the 5 existing surfaces).
- registry: CRM + Accessibility in the Apps catalog.
- version 8.4.16 -> 8.4.17; axe-core 4.12.1 (lazy import, own chunk).
typecheck clean; 887 unit tests pass (13 new: 9 crm + 4 a11y); next build green.
* feat(console): fold Content Studio + ERP/Help Center into the Business-OS suite (v8.4.17)
Consolidates the three overlapping Business-OS PRs into ONE canonical superset.
Onto the #39 base (canonical CRM over originV1Url → /v1/crm direct + per-row
delete, and the client-side axe-core Accessibility scanner), fold in #42's:
- CmsModule (Content Studio: honest in-console home for the live Payload CMS)
- registry entries cms (Content), erp + helpdesk (honest soon → ComingSoon)
Reconciliation: kept #39's originV1Url CRM (hits /v1/crm directly, the majority
agents/prompts/evals pattern) over #42's /cloud-prefixed cloudProxyV1Url; kept
#39's CrmModule (superset — adds delete); dropped #42's stray gcp:'Content';
regenerated package-lock.json for axe-core 4.12.1 (was package.json-only).
Supersedes #38, #39, #42.
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
* feat(console): consolidate CRM + Accessibility Business-OS modules over native /v1
CRM — the first Business-OS brick — as ONE canonical module over the native-Go
cloud /v1/crm surface (cloud clients/crm on Base/SQLite: companies, contacts,
opportunities; a port of Twenty's core model), per-org via the user-bearer /cloud
proxy. Consolidates the two competing CRM PRs (#38 feat/console2-crm and #39
crm-work): keeps #39's richer routed-tab views + defensive normalizers + tests,
re-paths its API from the explicit /cloud/v1 form to the canonical same-origin
originV1Url('crm') (matching Agents/Evals/Prompts — the one way), and grafts #38's
next.config `crm` head rewrite + per-row delete. crm.ts is the single typed mirror
of the /v1/crm contract (one method per route); every row is org-scoped SERVER-SIDE
from the token owner claim, with honest loading/empty/error states in @hanzo/gui.
Accessibility — a Wix-style WCAG scanner for the site being built. Runs Deque's
axe-core against the current page 100% client-side (engine lazy-loaded into its own
chunk, never the main bundle); pure sort/summarize/WCAG-label logic in
~/lib/a11y/scan is unit-tested without a browser or engine.
- next.config.mjs / proxy-allow.ts: allow-list the `crm` head on both the rewrite
and the bearer proxy (same least-privilege path as the 5 existing surfaces).
- registry: CRM + Accessibility in the Apps catalog.
- version 8.4.16 -> 8.4.17; axe-core 4.12.1 (lazy import, own chunk).
typecheck clean; 887 unit tests pass (13 new: 9 crm + 4 a11y); next build green.
* feat(console): fold Content Studio + ERP/Help Center into the Business-OS suite (v8.4.17)
Consolidates the three overlapping Business-OS PRs into ONE canonical superset.
Onto the #39 base (canonical CRM over originV1Url → /v1/crm direct + per-row
delete, and the client-side axe-core Accessibility scanner), fold in #42's:
- CmsModule (Content Studio: honest in-console home for the live Payload CMS)
- registry entries cms (Content), erp + helpdesk (honest soon → ComingSoon)
Reconciliation: kept #39's originV1Url CRM (hits /v1/crm directly, the majority
agents/prompts/evals pattern) over #42's /cloud-prefixed cloudProxyV1Url; kept
#39's CrmModule (superset — adds delete); dropped #42's stray gcp:'Content';
regenerated package-lock.json for axe-core 4.12.1 (was package.json-only).
Supersedes #38, #39, #42.
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Deep-links /billing/reports (now unshadowed) and asserts the god-view gate matches
the account grant (z is a hanzo org-admin → honest 403 + managed fallback; an
admin-org member → 200 KPI board). No app change.
Deep-links /billing/reports (now unshadowed) and asserts the god-view gate matches
the account grant (z is a hanzo org-admin → honest 403 + managed fallback; an
admin-org member → 200 KPI board). No app change.
The per-tenant commerce DATA proxy (app/billing/[...path]/route.ts) claimed the
whole /billing/* URL space; a Next route handler wins over the catch-all page for a
matching segment, so every billing tab except Overview (/billing/reports, budgets,
invoices, subscriptions, payment-methods, credits) resolved to the proxy and
returned commerce {"error":"not found"} / raw JSON instead of the UI. This
blocked the v8.4.15 Reports cost-dimension (product/agent) surface in production.
Namespace the data proxy under /billing/v1/* (the 'always /v1/' convention) so it
can never collide with a UI tab slug; tab URLs fall through to app/(dashboard)/[...slug].
- move app/billing/[...path] -> app/billing/v1/[...path]; topup/wallet likewise
(forward target commerce/v1/billing/<path> unchanged — v1 is now a static segment)
- billingUrl() (billing.ts + aimetrics.ts) and wallet.ts appUrl() prepend v1/
- tests: aimetrics.test.ts asserts /billing/v1/usage; billing-isolation e2e fetches /billing/v1/<p>
tsc clean; 874/874 tests; next build green (routes /billing/v1/[...path],
/billing/v1/topup/wallet, /[...slug] catch-all serves the tabs).
The per-tenant commerce DATA proxy (app/billing/[...path]/route.ts) claimed the
whole /billing/* URL space; a Next route handler wins over the catch-all page for a
matching segment, so every billing tab except Overview (/billing/reports, budgets,
invoices, subscriptions, payment-methods, credits) resolved to the proxy and
returned commerce {"error":"not found"} / raw JSON instead of the UI. This
blocked the v8.4.15 Reports cost-dimension (product/agent) surface in production.
Namespace the data proxy under /billing/v1/* (the 'always /v1/' convention) so it
can never collide with a UI tab slug; tab URLs fall through to app/(dashboard)/[...slug].
- move app/billing/[...path] -> app/billing/v1/[...path]; topup/wallet likewise
(forward target commerce/v1/billing/<path> unchanged — v1 is now a static segment)
- billingUrl() (billing.ts + aimetrics.ts) and wallet.ts appUrl() prepend v1/
- tests: aimetrics.test.ts asserts /billing/v1/usage; billing-isolation e2e fetches /billing/v1/<p>
tsc clean; 874/874 tests; next build green (routes /billing/v1/[...path],
/billing/v1/topup/wallet, /[...slug] catch-all serves the tabs).
Add a global-admin-only Finance board to admin.hanzo.ai over the ONE
LivingOverview system — DigitalOcean credit burn-down (our primary ~$40k
venue), month-to-date spend, MRR, total revenue, gross margin %, runway,
and a profitability health verdict. TRUE by construction: every tile reads
the real `/v1/admin/finance` aggregate; no fallback fabricates numbers.
- lib/api/finance.ts: FinanceApi.finance() + normalizeFinance — optional-safe
map of `/v1/admin/finance` onto Finance. Reads via originGet (same-origin
`<origin>/v1/admin/finance`), so the request rides the global-admin-gated
aggregate proxy. runwayDays preserves NULL (never coerced to 0 = fake alarm).
- overview/living/adapters.ts: fromFinance (payload → OverviewData, honest-empty
on unconfigured DO / commerce) + pure financeHealth verdict (green profitable /
yellow thin-margin <20% / red burning-faster / '' unknown when DO off).
- overview/living/registry.ts: `finance` living config — 6 KPI tiles + credit
burn-down bar series + health/alerts. No try/catch fallback (finance is
true-by-construction; a denied/not-routed backend renders the honest error).
- products/registry.tsx: `finance` catalog entry, `admin: true` (Observe) —
hidden from every customer's nav/launcher/palette; the catch-all renders a
managed notice for a non-admin. Reuses livingOverviewModule; no new UI.
- SECURITY: financial data is Hanzo-internal. Routed through the `/admin/
aggregate` bearer proxy (getAdminGate: verified @hanzo.ai + IAM global-admin,
fail-closed 403) — NOT the generic /cloud product proxy. `finance` added to
ADMIN_AGGREGATE_HEADS (admin-aggregate.ts) + ADMIN_V1_HEADS (next.config.mjs);
the allow-list still REFUSES admin/iam + admin/kms. A non-admin can never see
or reach the board or the data.
tsc --noEmit: 0 errors. vitest: 874/874 (incl. +8 finance: normalizeFinance,
fromFinance, financeHealth, allowAdminSurface finance head). next build: ✓
compiled, 14/14 pages.
Add a global-admin-only Finance board to admin.hanzo.ai over the ONE
LivingOverview system — DigitalOcean credit burn-down (our primary ~$40k
venue), month-to-date spend, MRR, total revenue, gross margin %, runway,
and a profitability health verdict. TRUE by construction: every tile reads
the real `/v1/admin/finance` aggregate; no fallback fabricates numbers.
- lib/api/finance.ts: FinanceApi.finance() + normalizeFinance — optional-safe
map of `/v1/admin/finance` onto Finance. Reads via originGet (same-origin
`<origin>/v1/admin/finance`), so the request rides the global-admin-gated
aggregate proxy. runwayDays preserves NULL (never coerced to 0 = fake alarm).
- overview/living/adapters.ts: fromFinance (payload → OverviewData, honest-empty
on unconfigured DO / commerce) + pure financeHealth verdict (green profitable /
yellow thin-margin <20% / red burning-faster / '' unknown when DO off).
- overview/living/registry.ts: `finance` living config — 6 KPI tiles + credit
burn-down bar series + health/alerts. No try/catch fallback (finance is
true-by-construction; a denied/not-routed backend renders the honest error).
- products/registry.tsx: `finance` catalog entry, `admin: true` (Observe) —
hidden from every customer's nav/launcher/palette; the catch-all renders a
managed notice for a non-admin. Reuses livingOverviewModule; no new UI.
- SECURITY: financial data is Hanzo-internal. Routed through the `/admin/
aggregate` bearer proxy (getAdminGate: verified @hanzo.ai + IAM global-admin,
fail-closed 403) — NOT the generic /cloud product proxy. `finance` added to
ADMIN_AGGREGATE_HEADS (admin-aggregate.ts) + ADMIN_V1_HEADS (next.config.mjs);
the allow-list still REFUSES admin/iam + admin/kms. A non-admin can never see
or reach the board or the data.
tsc --noEmit: 0 errors. vitest: 874/874 (incl. +8 finance: normalizeFinance,
fromFinance, financeHealth, allowAdminSurface finance head). next build: ✓
compiled, 14/14 pages.
H1 (HIGH): the admin business god-view had NO console-side server gate — /v1/admin/*
was not rewritten and rested solely on an unverified cloud-side gate. Add
app/admin/aggregate/[...path] behind getAdminGate (global-admin only, fail-closed
403) → forwardWithUserBearer; rewrite /v1/admin/{overview,usage,orgs,audit,products}
to it (iam/kms untouched). New originGet pins AdminApi to the console origin so a
split-origin NEXT_PUBLIC_CLOUD_URL can't bypass the gate. Least-privilege surface is
the pure, tested lib/server/admin-aggregate.ts (refuses admin/iam, admin/kms).
L1 (LOW, proven): agentUsageFor id-OR-name Set union conflated two agents within an
org. Prefer exact id, fall back to name only when id matched nothing. +collision tests.
L2 (LOW, proven): unbounded cost table under high agent/product cardinality. New pure
capRows (COST_ROW_CAP=100) bounds the DOM to top-by-spend with an honest Show-all
affordance (never hides real data). +tests.
RED-refuted vectors verified safe (fallback scope, metadata forgery, DoS, honest
state, client gating). typecheck clean; 853/853 tests; next build green (new route
registered).
H1 (HIGH): the admin business god-view had NO console-side server gate — /v1/admin/*
was not rewritten and rested solely on an unverified cloud-side gate. Add
app/admin/aggregate/[...path] behind getAdminGate (global-admin only, fail-closed
403) → forwardWithUserBearer; rewrite /v1/admin/{overview,usage,orgs,audit,products}
to it (iam/kms untouched). New originGet pins AdminApi to the console origin so a
split-origin NEXT_PUBLIC_CLOUD_URL can't bypass the gate. Least-privilege surface is
the pure, tested lib/server/admin-aggregate.ts (refuses admin/iam, admin/kms).
L1 (LOW, proven): agentUsageFor id-OR-name Set union conflated two agents within an
org. Prefer exact id, fall back to name only when id matched nothing. +collision tests.
L2 (LOW, proven): unbounded cost table under high agent/product cardinality. New pure
capRows (COST_ROW_CAP=100) bounds the DOM to top-by-spend with an honest Show-all
affordance (never hides real data). +tests.
RED-refuted vectors verified safe (fallback scope, metadata forgery, DoS, honest
state, client gating). typecheck clean; 853/853 tests; next build green (new route
registered).
Usage/billing visibility:
- aimetrics UsageRecord extracts metadata.{product,agent} (canonical contract);
perAgent + agentUsageFor rollups over the SAME charged commerce ledger.
- Cost Reports add product + agent breakdowns (presentDimensions gates each on
real data — honest until spend is tagged); BillingReports renders them.
- Agents detail pane shows per-agent cost from the ledger (agentUsageFor), not a
hardcoded/registry metric; honest '—' until attributed.
admin.hanzo.ai business dashboard (global-admin only):
- New admin-business living overview (MRR/revenue/usage-cost/orgs/customers,
revenue-by-product + plan-mix + top-agents-by-cost donuts, alerts, activity,
fleet health) over /v1/admin/overview allOrgs, honest usage-ledger+operator
fallback; reuses the ONE LivingOverview system.
- admin-overview gains an optional named-distributions map (revenue/plans/
topAgents), present only when the backend sends it; fromAdminOverview projects
each into distribution[key].
- Registry catalog entry 'business' (Observe, admin:true) — gated by getAdminGate
+ useIsGlobalAdmin; the aggregate is server-gated.
Mobile-responsive by construction (gui v5 shorthands + flexWrap rows, no fixed
grids). typecheck clean; 841/841 tests; next build green. /v1 only.
Usage/billing visibility:
- aimetrics UsageRecord extracts metadata.{product,agent} (canonical contract);
perAgent + agentUsageFor rollups over the SAME charged commerce ledger.
- Cost Reports add product + agent breakdowns (presentDimensions gates each on
real data — honest until spend is tagged); BillingReports renders them.
- Agents detail pane shows per-agent cost from the ledger (agentUsageFor), not a
hardcoded/registry metric; honest '—' until attributed.
admin.hanzo.ai business dashboard (global-admin only):
- New admin-business living overview (MRR/revenue/usage-cost/orgs/customers,
revenue-by-product + plan-mix + top-agents-by-cost donuts, alerts, activity,
fleet health) over /v1/admin/overview allOrgs, honest usage-ledger+operator
fallback; reuses the ONE LivingOverview system.
- admin-overview gains an optional named-distributions map (revenue/plans/
topAgents), present only when the backend sends it; fromAdminOverview projects
each into distribution[key].
- Registry catalog entry 'business' (Observe, admin:true) — gated by getAdminGate
+ useIsGlobalAdmin; the aggregate is server-gated.
Mobile-responsive by construction (gui v5 shorthands + flexWrap rows, no fixed
grids). typecheck clean; 841/841 tests; next build green. /v1 only.
The gallery "Fork / deploy" button now creates a REAL project in-console via
POST /v1/projects/fork (cloud projectsvc) instead of only opening the gallery
source URL — the ONE way to start a project from a template.
- lib/api/templates.ts: TemplatesApi.fork(slug, {name?}) POSTs to the
same-origin /v1/projects/fork (originV1Url, no prefix) and normalizes the
returned projectsvc Project (normalizeForkedProject, pure/tested).
- TemplatesModule: per-card idle -> forking -> created state; on success shows
the new project (Open site when a liveUrl exists, else honest draft). On a 404
(older backend without the fork route) it falls back to opening the gallery
source, so the button is never dead.
- next.config.mjs + proxy-allow.ts: add the `projects` head so /v1/projects*
(incl. /fork) routes through the hardened /cloud bearer proxy, org-scoped from
the Bearer owner.
Tests: normalizeForkedProject + TemplatesApi.fork (exact same-origin URL, body
with/without name override, 404 ApiError for the fallback); proxy-allow admits
the projects fork subtree. tsc clean; vitest 834/834.
The gallery "Fork / deploy" button now creates a REAL project in-console via
POST /v1/projects/fork (cloud projectsvc) instead of only opening the gallery
source URL — the ONE way to start a project from a template.
- lib/api/templates.ts: TemplatesApi.fork(slug, {name?}) POSTs to the
same-origin /v1/projects/fork (originV1Url, no prefix) and normalizes the
returned projectsvc Project (normalizeForkedProject, pure/tested).
- TemplatesModule: per-card idle -> forking -> created state; on success shows
the new project (Open site when a liveUrl exists, else honest draft). On a 404
(older backend without the fork route) it falls back to opening the gallery
source, so the button is never dead.
- next.config.mjs + proxy-allow.ts: add the `projects` head so /v1/projects*
(incl. /fork) routes through the hardened /cloud bearer proxy, org-scoped from
the Bearer owner.
Tests: normalizeForkedProject + TemplatesApi.fork (exact same-origin URL, body
with/without name override, 404 ApiError for the fallback); proxy-allow admits
the projects fork subtree. tsc clean; vitest 834/834.
console2's canonical, decoupled agent builder becomes the true superset: its
host-injected loader seam (unchanged) + hanzo.chat (@hanzo/ai)'s advanced
generation config. One component over the ONE /v1/agents backend — hanzo.chat
and console v8 render the identical builder.
Contract (types.ts):
- AgentConfig: temperature/topP/topK/stream/thinking/useTools/webSearch +
reasoningEffort, all with defaults; folded onto AgentSpec as OPTIONAL config +
knowledge, so a simple agent is unchanged.
- ReasoningEffort = the full Hanzo/Claude ladder low·medium·high·xhigh·max·
ultracode (ultracode = xhigh+workflows, top tier, use sparingly) — supersedes
@hanzo/ai's old 3-level enum.
- AgentCreateBody: the pruned wire value the builder emits; createAgent now
takes the body (no more 'as AgentSpec' cast at the call site).
Pure logic (logic.ts): defaultConfig/clampConfig/pruneConfig +
normalizeList(→tools,knowledge, DRY). toCreateBody prunes every default knob, so
opening Advanced never changes what a simple agent posts. clampNum fixed: NaN→min
but ±∞ clamp to the nearest bound (slider-to-top lands on max, not min).
UI (AgentBuilder.tsx): hidden-by-default Advanced section (sliders/switches/select
over the existing Field primitives). loaders.ts + NewAgentBody pass config+knowledge
through to POST /v1/agents.
Verified: all pure transforms proven via a standalone node harness (22/22 incl.
backward-compat, clamp edge cases, prune, ultracode). tsc/vitest run in CI.
console2's canonical, decoupled agent builder becomes the true superset: its
host-injected loader seam (unchanged) + hanzo.chat (@hanzo/ai)'s advanced
generation config. One component over the ONE /v1/agents backend — hanzo.chat
and console v8 render the identical builder.
Contract (types.ts):
- AgentConfig: temperature/topP/topK/stream/thinking/useTools/webSearch +
reasoningEffort, all with defaults; folded onto AgentSpec as OPTIONAL config +
knowledge, so a simple agent is unchanged.
- ReasoningEffort = the full Hanzo/Claude ladder low·medium·high·xhigh·max·
ultracode (ultracode = xhigh+workflows, top tier, use sparingly) — supersedes
@hanzo/ai's old 3-level enum.
- AgentCreateBody: the pruned wire value the builder emits; createAgent now
takes the body (no more 'as AgentSpec' cast at the call site).
Pure logic (logic.ts): defaultConfig/clampConfig/pruneConfig +
normalizeList(→tools,knowledge, DRY). toCreateBody prunes every default knob, so
opening Advanced never changes what a simple agent posts. clampNum fixed: NaN→min
but ±∞ clamp to the nearest bound (slider-to-top lands on max, not min).
UI (AgentBuilder.tsx): hidden-by-default Advanced section (sliders/switches/select
over the existing Field primitives). loaders.ts + NewAgentBody pass config+knowledge
through to POST /v1/agents.
Verified: all pure transforms proven via a standalone node harness (22/22 incl.
backward-compat, clamp edge cases, prune, ultracode). tsc/vitest run in CI.
CI workflow now builds+pushes ghcr.io/hanzoai/console:v<version> directly
(no more console2→console retag hack). registry product source-links and the
build/deploy doc updated to the renamed repo. Image name == repo name, one way.
CI workflow now builds+pushes ghcr.io/hanzoai/console:v<version> directly
(no more console2→console retag hack). registry product source-links and the
build/deploy doc updated to the renamed repo. Image name == repo name, one way.
One product, two build lineages: console ships app-semver 8.4.x, cloud
ships its own Go-module v1.786.x (never above v1 — Go module semantics +
the standing rule). Unify only the STORY under a "Hanzo Cloud <MAJOR.MINOR>"
umbrella, single-sourced from the console app version (no second place holds
it): next.config injects NEXT_PUBLIC_APP_VERSION from package.json;
config derives branding.release ("8.4") + branding.productLine
("Hanzo Cloud 8.4"), shown on the sign-in screen. Convention documented in
LLM.md. Nothing in Go changes. typecheck clean, vitest 793/793.
One product, two build lineages: console ships app-semver 8.4.x, cloud
ships its own Go-module v1.786.x (never above v1 — Go module semantics +
the standing rule). Unify only the STORY under a "Hanzo Cloud <MAJOR.MINOR>"
umbrella, single-sourced from the console app version (no second place holds
it): next.config injects NEXT_PUBLIC_APP_VERSION from package.json;
config derives branding.release ("8.4") + branding.productLine
("Hanzo Cloud 8.4"), shown on the sign-in screen. Convention documented in
LLM.md. Nothing in Go changes. typecheck clean, vitest 793/793.
Cut a fresh semver from a verified-clean main HEAD so CI publishes
ghcr.io/hanzoai/console2:v8.4.11. Tree already type-checks + builds
clean (concurrent lanes resolved the earlier RecordsModule maxW /
metrics.test null-type breakages); this bump is the publish trigger.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Cut a fresh semver from a verified-clean main HEAD so CI publishes
ghcr.io/hanzoai/console2:v8.4.11. Tree already type-checks + builds
clean (concurrent lanes resolved the earlier RecordsModule maxW /
metrics.test null-type breakages); this bump is the publish trigger.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The user asked to call it just 'S3'. Rename the user-visible product
name everywhere it surfaces — the catalog entry (registry.tsx label +
description), the StorageModule page header title, and the Zero Trust
data-plane posture row — plus the two resource-console doc comments that
list the kinds. The provisioning kind id stays 's3' and the file-manager
backend (/v1/s3) is unchanged; this is a label rename only.
typecheck clean, vitest 778/778 green.
The user asked to call it just 'S3'. Rename the user-visible product
name everywhere it surfaces — the catalog entry (registry.tsx label +
description), the StorageModule page header title, and the Zero Trust
data-plane posture row — plus the two resource-console doc comments that
list the kinds. The provisioning kind id stays 's3' and the file-manager
backend (/v1/s3) is unchanged; this is a label rename only.
typecheck clean, vitest 778/778 green.
Makes Base usable BY CLICKING, not just via the API — the gap the live Playwright
check found (the base admin UI is read-only). A 'Records' product (Data category):
browse a collection, open a record, edit it, create new ones — all rendered from
the collection's OWN field schema through @hanzo/data (DataTable for the list,
RecordDetail/RecordForm for detail; every field type is now editable per
hanzoai/ui#232). Data flows through console2's per-user /superbase proxy (IAM
bearer minted server-side; the proxy allow-list gains the collections + records
paths). Routes: /records (index) · /records/:collection · /records/:collection/:id
(:id=new → create).
base-data/{api,fields} map Base schema → @hanzo/data FieldDefinition[] and do the
list/get/create/update/delete; CollectionTable + RecordDetailView are the views.
Registered next to Base (the backend) — Base is the store, Records is the app on
top. 19 base-data tests pass; RecordsModule + registry typecheck clean (the 4
remaining tsc errors are pre-existing: @hanzo/dash local-only + metrics.test).
Co-authored-by: zeekay <z@zeekay.io>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Makes Base usable BY CLICKING, not just via the API — the gap the live Playwright
check found (the base admin UI is read-only). A 'Records' product (Data category):
browse a collection, open a record, edit it, create new ones — all rendered from
the collection's OWN field schema through @hanzo/data (DataTable for the list,
RecordDetail/RecordForm for detail; every field type is now editable per
hanzoai/ui#232). Data flows through console2's per-user /superbase proxy (IAM
bearer minted server-side; the proxy allow-list gains the collections + records
paths). Routes: /records (index) · /records/:collection · /records/:collection/:id
(:id=new → create).
base-data/{api,fields} map Base schema → @hanzo/data FieldDefinition[] and do the
list/get/create/update/delete; CollectionTable + RecordDetailView are the views.
Registered next to Base (the backend) — Base is the store, Records is the app on
top. 19 base-data tests pass; RecordsModule + registry typecheck clean (the 4
remaining tsc errors are pre-existing: @hanzo/dash local-only + metrics.test).
Co-authored-by: zeekay <z@zeekay.io>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The CI token can push the existing console2 ghcr package but lacks
write_package to CREATE a new ghcr.io/hanzoai/console package, so the atomic
buildx --push of both tags failed and v8.4.9 published NEITHER image. Back to
single console2 tag so releases build again. The console2 → console image
rename needs the ghcr package created + repo-linked first (an
org/settings step), then the tag can be added.
The CI token can push the existing console2 ghcr package but lacks
write_package to CREATE a new ghcr.io/hanzoai/console package, so the atomic
buildx --push of both tags failed and v8.4.9 published NEITHER image. Back to
single console2 tag so releases build again. The console2 → console image
rename needs the ghcr package created + repo-linked first (an
org/settings step), then the tag can be added.
Per-org Analytics product over cloud clients/analytics: Overview (hanzo.events +
events_daily), Real-Time (live sessions/feed), LLM (cloud_usage + observations).
Same-origin /v1/analytics/* via the /cloud bearer proxy; analytics head added to
proxy-allow CLOUD_HEADS + next.config CLOUD_V1_HEADS. Registered under Observe.
Every metric a real warehouse query; honest-empty otherwise.
Per-org Analytics product over cloud clients/analytics: Overview (hanzo.events +
events_daily), Real-Time (live sessions/feed), LLM (cloud_usage + observations).
Same-origin /v1/analytics/* via the /cloud bearer proxy; analytics head added to
proxy-allow CLOUD_HEADS + next.config CLOUD_V1_HEADS. Registered under Observe.
Every metric a real warehouse query; honest-empty otherwise.
Dual-tag release so the console image exists at this version before the operator
CR + gateway cut over from console2 → console in one coordinated deploy.
Dual-tag release so the console image exists at this version before the operator
CR + gateway cut over from console2 → console in one coordinated deploy.
'console2' was only ever a working name — the package is already @hanzo/console
and it's v8. Start the rename by publishing ghcr.io/hanzoai/console:<ver>
ALONGSIDE console2:<ver>. Purely additive — nothing consumes the console image
yet, so no rollout can break. The cutover (operator CR + gateway k8s Service
console2→console, in ONE deploy) and dropping the console2 tag follow once the
new image has published on a release.
'console2' was only ever a working name — the package is already @hanzo/console
and it's v8. Start the rename by publishing ghcr.io/hanzoai/console:<ver>
ALONGSIDE console2:<ver>. Purely additive — nothing consumes the console image
yet, so no rollout can break. The cutover (operator CR + gateway k8s Service
console2→console, in ONE deploy) and dropping the console2 tag follow once the
new image has published on a release.
Rebased onto main v8.4.7 (Prompts/Agents/Evals live via next.config /v1 rewrites,
dynamic model+prompt agent builder, ComboBox). Was fe3ee26 (v8.4.5).
Cross-tenant eval fix ships in cloud v1.786.10.
Rebased onto main v8.4.7 (Prompts/Agents/Evals live via next.config /v1 rewrites,
dynamic model+prompt agent builder, ComboBox). Was fe3ee26 (v8.4.5).
Cross-tenant eval fix ships in cloud v1.786.10.
Products inherit a per-category color family by default (one color per category:
AI/Compute/Data/Security/…), user override still wins, no-category callers keep
their legacy curated pick. colorOf/keyOf thread the entry's category so the sidebar
icons, collapsed rail, and L2 header recolor per category in one place. Category
landing (/category/<slug>, CategoryOverview — already built) tiles + header glyph +
the L1/L2 category labels are tinted the category color. colors.ts pure + tested.
tsc clean, vitest 711/711, next build green.
Products inherit a per-category color family by default (one color per category:
AI/Compute/Data/Security/…), user override still wins, no-category callers keep
their legacy curated pick. colorOf/keyOf thread the entry's category so the sidebar
icons, collapsed rail, and L2 header recolor per category in one place. Category
landing (/category/<slug>, CategoryOverview — already built) tiles + header glyph +
the L1/L2 category labels are tinted the category color. colors.ts pure + tested.
tsc clean, vitest 711/711, next build green.
The sidebar product filter is hoisted out of the level-1 slide panel into a
persistent header above the two-level slide, so a user deep in a product's
sub-pages can filter + jump straight to another product without going Back.
showLevel2 yields to the product list while filtering; selecting a result
clears the filter and slides to that product's level-2 sub-nav. One input,
one predicate (entryMatches), one list. Mobile drawer inherits it.
tsc clean, vitest 706/706, next build green.
The sidebar product filter is hoisted out of the level-1 slide panel into a
persistent header above the two-level slide, so a user deep in a product's
sub-pages can filter + jump straight to another product without going Back.
showLevel2 yields to the product list while filtering; selecting a result
clears the filter and slides to that product's level-2 sub-nav. One input,
one predicate (entryMatches), one list. Mobile drawer inherits it.
tsc clean, vitest 706/706, next build green.
PRIORITY 1 — S3 file manager. Upgrades the 'Object Storage' catalog entry from
the generic provisioning resource card to a REAL S3 file manager over the
org-scoped /v1/s3 control plane in the unified cloud binary (hanzoai/cloud
clients/s3). One console, one backend — no external s3.hanzo.ai UI.
- src/lib/api/storage.ts (StorageApi): buckets list/create/delete, object list
(folder-style via prefix), delete, and presigned upload/download. Metadata ops
go through the same-origin /cloud user-bearer proxy (cloudProxyV1Url — s3 is
already allow-listed in proxy-allow.ts). Upload/download use PRESIGNED URLs:
the backend mints a time-boxed URL scoped to the exact bucket+key and the
browser transfers bytes DIRECTLY to S3 — bypassing the proxy (which buffers the
body as text + forces JSON content-type, corrupting binary) and never exposing
the admin credential. Defensive normalizers (billing.ts style); org is
server-authoritative (never a browser claim).
- src/components/products/StorageModule.tsx: bucket list (create/delete) plus an
object browser with breadcrumb folder navigation, upload (file picker to
presigned direct-to-S3), download, delete. Honest loading/empty(first-run)/
BackendState (503/404/403) states — never a fabricated bucket/object. hanzo/gui
v5 shorthands; mirrors FunctionsModule.
- registry.tsx: s3 entry now routes to StorageModule (repo hanzoai/s3).
PRIORITY 2 — KMS repoint. src/lib/server/identity.ts KMS_URL default
http://kms.hanzo.svc (legacy Infisical fork) to http://cloud.hanzo.svc:8000
(embedded cloud KMS serving /v1/kms/orgs/{org}/secrets natively, HIP-0106). The
/admin/kms proxy forwards to kmsBaseUrl + /v1/kms/orgs/{org}/secrets — matches.
CAVEAT (documented, not a blocker): the embedded KMS is health-only (secret ops
503) until CLOUD_KMS_MASTER_KEY_REF is provisioned + secrets migrated; the KMS
module shows its honest 'not initialized' state until then.
Tests: vitest storage.test.ts 15/15 (normalizers, folder detection, presign,
traversal-safe key encoding, /cloud-proxy URL construction, direct-to-S3 upload).
tsc --noEmit clean. next build green (14/14 pages). Version 8.4.1 to 8.4.2.
PRIORITY 1 — S3 file manager. Upgrades the 'Object Storage' catalog entry from
the generic provisioning resource card to a REAL S3 file manager over the
org-scoped /v1/s3 control plane in the unified cloud binary (hanzoai/cloud
clients/s3). One console, one backend — no external s3.hanzo.ai UI.
- src/lib/api/storage.ts (StorageApi): buckets list/create/delete, object list
(folder-style via prefix), delete, and presigned upload/download. Metadata ops
go through the same-origin /cloud user-bearer proxy (cloudProxyV1Url — s3 is
already allow-listed in proxy-allow.ts). Upload/download use PRESIGNED URLs:
the backend mints a time-boxed URL scoped to the exact bucket+key and the
browser transfers bytes DIRECTLY to S3 — bypassing the proxy (which buffers the
body as text + forces JSON content-type, corrupting binary) and never exposing
the admin credential. Defensive normalizers (billing.ts style); org is
server-authoritative (never a browser claim).
- src/components/products/StorageModule.tsx: bucket list (create/delete) plus an
object browser with breadcrumb folder navigation, upload (file picker to
presigned direct-to-S3), download, delete. Honest loading/empty(first-run)/
BackendState (503/404/403) states — never a fabricated bucket/object. hanzo/gui
v5 shorthands; mirrors FunctionsModule.
- registry.tsx: s3 entry now routes to StorageModule (repo hanzoai/s3).
PRIORITY 2 — KMS repoint. src/lib/server/identity.ts KMS_URL default
http://kms.hanzo.svc (legacy Infisical fork) to http://cloud.hanzo.svc:8000
(embedded cloud KMS serving /v1/kms/orgs/{org}/secrets natively, HIP-0106). The
/admin/kms proxy forwards to kmsBaseUrl + /v1/kms/orgs/{org}/secrets — matches.
CAVEAT (documented, not a blocker): the embedded KMS is health-only (secret ops
503) until CLOUD_KMS_MASTER_KEY_REF is provisioned + secrets migrated; the KMS
module shows its honest 'not initialized' state until then.
Tests: vitest storage.test.ts 15/15 (normalizers, folder detection, presign,
traversal-safe key encoding, /cloud-proxy URL construction, direct-to-S3 upload).
tsc --noEmit clean. next build green (14/14 pages). Version 8.4.1 to 8.4.2.
A new Commerce category surfaces the hanzoai/commerce merchant store natively
inside the console (no admin.commerce.hanzo.ai subdomain). Six pages —
Products, Orders, Customers, Inventory, Promotions, Store settings — each a
native module over the real commerce backend, scoped to the signed-in org.
- BFF: app/commerce/[...path]/route.ts forwards to commerce.hanzo.svc:8001 via
forwardWithUserBearer (mints a short-lived user IAM token; commerce EdgeAuth
resolves the org from the owner claim). Least-privilege allow-list
(allowCommerceSurface / COMMERCE_HEADS): only the merchant REST heads
(product/order/user/variant/discount/collection/store/…) — /billing, /checkout,
/_/commerce/tenants are NOT reachable (money stays on the /billing proxy).
- Client: src/lib/api/commerce.ts (CommerceApi) — defensive normalizers over the
real {count,models,facets} envelope; empty store → honest empty, never faked.
- UI: one CommerceResource list (fetch → loading/empty/error via BackendStateCard)
+ six thin pages; Store settings notes Square/Billing. @hanzo/gui v5 shorthands.
- Category: 'Commerce' added to brand-scope (hanzo shows it; web3 brands don't).
- No Stripe, no new DB, no billing-engine change. Payments remain Square via
hanzoai/commerce /v1/billing.
Verification: tsc --noEmit clean; vitest 52 green (commerce/logic/proxy-allow/
brand-scope); next build ✓ (/commerce/[...path] compiled). The one failing test
(billing/logic.ts groupSpend ordering) is pre-existing on origin/main, unrelated.
A new Commerce category surfaces the hanzoai/commerce merchant store natively
inside the console (no admin.commerce.hanzo.ai subdomain). Six pages —
Products, Orders, Customers, Inventory, Promotions, Store settings — each a
native module over the real commerce backend, scoped to the signed-in org.
- BFF: app/commerce/[...path]/route.ts forwards to commerce.hanzo.svc:8001 via
forwardWithUserBearer (mints a short-lived user IAM token; commerce EdgeAuth
resolves the org from the owner claim). Least-privilege allow-list
(allowCommerceSurface / COMMERCE_HEADS): only the merchant REST heads
(product/order/user/variant/discount/collection/store/…) — /billing, /checkout,
/_/commerce/tenants are NOT reachable (money stays on the /billing proxy).
- Client: src/lib/api/commerce.ts (CommerceApi) — defensive normalizers over the
real {count,models,facets} envelope; empty store → honest empty, never faked.
- UI: one CommerceResource list (fetch → loading/empty/error via BackendStateCard)
+ six thin pages; Store settings notes Square/Billing. @hanzo/gui v5 shorthands.
- Category: 'Commerce' added to brand-scope (hanzo shows it; web3 brands don't).
- No Stripe, no new DB, no billing-engine change. Payments remain Square via
hanzoai/commerce /v1/billing.
Verification: tsc --noEmit clean; vitest 52 green (commerce/logic/proxy-allow/
brand-scope); next build ✓ (/commerce/[...path] compiled). The one failing test
(billing/logic.ts groupSpend ordering) is pre-existing on origin/main, unrelated.
Live browser pass as Dave (maxpower) found pages that were connected-but-read-as-broken:
- Machines: /vm/v1/machines 403s for a signed-in customer (visor authorizes the
public catalog but denies the per-org list) → the page said 'Sign in to view your
machines' next to the real region/size catalog. interpretVisorError now maps 403→
connected-managed (only 401 = sign-in); CustomerMachines shows 'Launch your first
machine' + the live catalog, never a sign-in wall.
- platform/state forbidden: reframed to 'Connected · managed by Hanzo' (green check, no
warning triangle, no Retry) so Containers/Edge/Applications read connected, not error.
- Applications: repointed from casibase IAM OAuth apps (get-applications) to the DEPLOYED
app services (/v1/apps) — connected/managed/empty states + deploy-via-Functions/Agents.
- Agents: 'Connected · no agents yet' banner on the live 200-empty state.
- Proxy defaults hardened (vm/cloud/tasksd): '|| default' (not '??') so an env
reconciled to an EMPTY string still resolves the in-cluster service.
tsc clean; vitest green (visor test updated for 403→connected).
Live browser pass as Dave (maxpower) found pages that were connected-but-read-as-broken:
- Machines: /vm/v1/machines 403s for a signed-in customer (visor authorizes the
public catalog but denies the per-org list) → the page said 'Sign in to view your
machines' next to the real region/size catalog. interpretVisorError now maps 403→
connected-managed (only 401 = sign-in); CustomerMachines shows 'Launch your first
machine' + the live catalog, never a sign-in wall.
- platform/state forbidden: reframed to 'Connected · managed by Hanzo' (green check, no
warning triangle, no Retry) so Containers/Edge/Applications read connected, not error.
- Applications: repointed from casibase IAM OAuth apps (get-applications) to the DEPLOYED
app services (/v1/apps) — connected/managed/empty states + deploy-via-Functions/Agents.
- Agents: 'Connected · no agents yet' banner on the live 200-empty state.
- Proxy defaults hardened (vm/cloud/tasksd): '|| default' (not '??') so an env
reconciled to an EMPTY string still resolves the in-cluster service.
tsc clean; vitest green (visor test updated for 403→connected).
Agents: rebuilt AgentsModule into a rich dashboard over /cloud/v1/agents (was
/paas): 5 stat cards, invocations area chart, health donut, agents table with
status tabs + pagination + version badges, recent-activity feed, top-agents bar
list, 30d resource-usage panel. Every number real/derived; polished
create-first empty state + real New-Agent flow. New lib/api/agents.ts (+22 tests)
+ agents/{parts,forms}.tsx.
Machines: customer branch shows the real visor region/size catalog + pricing
(MachineCatalog) under the launch state — never blank.
GPUs: role-routed like Machines — customer sees the real visor GPU catalog +
their GPU machines (CustomerGpus); admin keeps the /paas fleet. Overview route
is role-aware (GpusOverview). +4 visor catalog normalizer tests.
Containers: surface the apps 403 as a graceful 'Managed control plane' card
(was a masked bare-empty table). Edge: honest coming-soon/managed state.
platform/state.tsx: split 401/403 (forbidden → 'Managed control plane') from
501 (not-configured → admin token hint) so customers never see the false
PAAS_SERVICE_TOKEN message across every /paas module.
visor.ts: add regions()/sizes()/gpus() catalog + normalizers.
tsc clean; vitest 639+ green; next build 14/14.
Agents: rebuilt AgentsModule into a rich dashboard over /cloud/v1/agents (was
/paas): 5 stat cards, invocations area chart, health donut, agents table with
status tabs + pagination + version badges, recent-activity feed, top-agents bar
list, 30d resource-usage panel. Every number real/derived; polished
create-first empty state + real New-Agent flow. New lib/api/agents.ts (+22 tests)
+ agents/{parts,forms}.tsx.
Machines: customer branch shows the real visor region/size catalog + pricing
(MachineCatalog) under the launch state — never blank.
GPUs: role-routed like Machines — customer sees the real visor GPU catalog +
their GPU machines (CustomerGpus); admin keeps the /paas fleet. Overview route
is role-aware (GpusOverview). +4 visor catalog normalizer tests.
Containers: surface the apps 403 as a graceful 'Managed control plane' card
(was a masked bare-empty table). Edge: honest coming-soon/managed state.
platform/state.tsx: split 401/403 (forbidden → 'Managed control plane') from
501 (not-configured → admin token hint) so customers never see the false
PAAS_SERVICE_TOKEN message across every /paas module.
visor.ts: add regions()/sizes()/gpus() catalog + normalizers.
tsc clean; vitest 639+ green; next build 14/14.
Part A — Billing Center (one `billing` catalog entry, tabbed):
- Consolidate the scattered Cost/Subscriptions/Payment-methods entries into ONE
`BillingModule` (registry ''+:tab) under Observe. Delete superseded CostModule.
- Overview: balance/credits + month-to-date spend + clearly-labelled linear
projection + daily-spend trend (real /v1/billing/usage ledger, pure logic.ts).
- Reports: cost breakdown by real ledger dimension (model/provider — no invented
project/SKU), filterable table + BarChart + spend-share Donut over a range.
- Budgets: REAL create+list over commerce spend-alerts (GET/POST /v1/billing/
spend-alerts). Edit/delete withheld pending commerce per-alert ownership check.
- Invoices: GET /v1/billing/invoices + download; honest empty.
- Subscriptions/Payment methods/Credits: reuse existing modules verbatim as tabs.
- Add `scopedBillingBody` (billing-scope) so a write body's subject is pinned
server-side — create-budget works without the browser knowing its subject and a
forged body subject can't widen scope. Wired into the /billing proxy write path.
Part B — billing-only shell (billing.<brand> = same image, filtered):
- config.billingOnly (host billing.<brand> OR NEXT_PUBLIC_BILLING_ONLY=1).
- visibleCatalog / DashboardShell nav filter to the Billing Center sub-pages,
full chrome kept; default route redirects / -> /billing.
- cmd+K + AppLauncher source from visibleCatalog so scoping is consistent.
Honest states everywhere; no fabricated data. New unit tests: billing/logic,
scopedBillingBody, config billing-only host. e2e/pages.spec updated for the
consolidation. Docs in LLM.md.
Part A — Billing Center (one `billing` catalog entry, tabbed):
- Consolidate the scattered Cost/Subscriptions/Payment-methods entries into ONE
`BillingModule` (registry ''+:tab) under Observe. Delete superseded CostModule.
- Overview: balance/credits + month-to-date spend + clearly-labelled linear
projection + daily-spend trend (real /v1/billing/usage ledger, pure logic.ts).
- Reports: cost breakdown by real ledger dimension (model/provider — no invented
project/SKU), filterable table + BarChart + spend-share Donut over a range.
- Budgets: REAL create+list over commerce spend-alerts (GET/POST /v1/billing/
spend-alerts). Edit/delete withheld pending commerce per-alert ownership check.
- Invoices: GET /v1/billing/invoices + download; honest empty.
- Subscriptions/Payment methods/Credits: reuse existing modules verbatim as tabs.
- Add `scopedBillingBody` (billing-scope) so a write body's subject is pinned
server-side — create-budget works without the browser knowing its subject and a
forged body subject can't widen scope. Wired into the /billing proxy write path.
Part B — billing-only shell (billing.<brand> = same image, filtered):
- config.billingOnly (host billing.<brand> OR NEXT_PUBLIC_BILLING_ONLY=1).
- visibleCatalog / DashboardShell nav filter to the Billing Center sub-pages,
full chrome kept; default route redirects / -> /billing.
- cmd+K + AppLauncher source from visibleCatalog so scoping is consistent.
Honest states everywhere; no fabricated data. New unit tests: billing/logic,
scopedBillingBody, config billing-only host. e2e/pages.spec updated for the
consolidation. Docs in LLM.md.
One authoritative build ending the deploy-war. Two genuinely-unmerged Network
modules land (nodes: per-node luxd validators/peers; dns: per-org managed DNS);
all other session branches were already on main (git cherry-verified) and are
pruned, not re-merged. The api.hanzo.ai-gateway default change was rejected (CR
documents in-cluster CF-403 on public hosts; safe default is cloud.hanzo.svc).
Fixed pre-existing observability/metrics.test.ts null-override types so
tsc --noEmit is fully green.
tsc --noEmit clean; next build is the authoritative Node-24 gate (on-cluster
Kaniko, no GitHub builders).
One authoritative build ending the deploy-war. Two genuinely-unmerged Network
modules land (nodes: per-node luxd validators/peers; dns: per-org managed DNS);
all other session branches were already on main (git cherry-verified) and are
pruned, not re-merged. The api.hanzo.ai-gateway default change was rejected (CR
documents in-cluster CF-403 on public hosts; safe default is cloud.hanzo.svc).
Fixed pre-existing observability/metrics.test.ts null-override types so
tsc --noEmit is fully green.
tsc --noEmit clean; next build is the authoritative Node-24 gate (on-cluster
Kaniko, no GitHub builders).
The DNS module cherry-pick (bee05edc) added a second id:'dns' catalog entry while
main already carried a DNS overview stub in the Network cluster. Upgrade that
well-placed stub to render the real DnsModule (zones/records over /v1/dns) and
remove the duplicate — one id, one entry, one way.
The DNS module cherry-pick (bee05edc) added a second id:'dns' catalog entry while
main already carried a DNS overview stub in the Network cluster. Upgrade that
well-placed stub to render the real DnsModule (zones/records over /v1/dns) and
remove the duplicate — one id, one entry, one way.
Add a real `nodes` catalog entry (Network category) surfacing individual luxd
node infrastructure — validators (P-chain platform.getCurrentValidators) + peers
(info.peers) — across networks, wired to LIVE luxd RPC. Complements the Bootnode
`networks` module (network-level counts) with per-NODE inventory. REAL data only;
honest "not reporting" per unreachable network, honest empty otherwise.
- app/nodes/[...path]/route.ts: same-origin proxy mirroring the /bootnode security
pattern — session-gated, brand/org-aware (brandFromHost), least-privilege. Only
path is v1/inventory; only the four read methods getCurrentValidators/peers/
getNodeVersion/getHeight are called server-side. Per-network RPC hosts in a small
env-overridable map; unreachable host -> honest not-reporting, never fake rows.
- lib/api/nodes.ts (extended; cluster-capacity logic untouched): pure
normalizeValidators/normalizePeers/combineInventory -> uniform NodeRow, dedupe by
nodeID (validator wins, version enriched from peer), parseUptimePct/parseHeight/
fmtWeight; NodesApi browser client over the proxy.
- lib/products/brand-scope.ts: nodeNetworksForBrand DATA scope — hanzo=all networks
(super-admin/infra view), lux/zoo/pars scoped to their own chain. Nodes lives in
Network so category scope admits it on every brand.
- components/products/NodesModule.tsx: per-network summary cards + network filter +
DataTable (Network/Role/Node ID/Version/Status/Uptime/Height); BackendStateCard/
EmptyState honest states.
- Confirmed live (2026-07-01): lux mainnet/testnet/devnet, pars-mainnet. zoo has no
confirmed public host yet -> honest not-reporting.
Tests: nodes normalizers (real captured wire shapes) + brand->network scoping.
typecheck clean, vitest 404/404 (37 files), next build green. package 8.2.1->8.2.2.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a real `nodes` catalog entry (Network category) surfacing individual luxd
node infrastructure — validators (P-chain platform.getCurrentValidators) + peers
(info.peers) — across networks, wired to LIVE luxd RPC. Complements the Bootnode
`networks` module (network-level counts) with per-NODE inventory. REAL data only;
honest "not reporting" per unreachable network, honest empty otherwise.
- app/nodes/[...path]/route.ts: same-origin proxy mirroring the /bootnode security
pattern — session-gated, brand/org-aware (brandFromHost), least-privilege. Only
path is v1/inventory; only the four read methods getCurrentValidators/peers/
getNodeVersion/getHeight are called server-side. Per-network RPC hosts in a small
env-overridable map; unreachable host -> honest not-reporting, never fake rows.
- lib/api/nodes.ts (extended; cluster-capacity logic untouched): pure
normalizeValidators/normalizePeers/combineInventory -> uniform NodeRow, dedupe by
nodeID (validator wins, version enriched from peer), parseUptimePct/parseHeight/
fmtWeight; NodesApi browser client over the proxy.
- lib/products/brand-scope.ts: nodeNetworksForBrand DATA scope — hanzo=all networks
(super-admin/infra view), lux/zoo/pars scoped to their own chain. Nodes lives in
Network so category scope admits it on every brand.
- components/products/NodesModule.tsx: per-network summary cards + network filter +
DataTable (Network/Role/Node ID/Version/Status/Uptime/Height); BackendStateCard/
EmptyState honest states.
- Confirmed live (2026-07-01): lux mainnet/testnet/devnet, pars-mainnet. zoo has no
confirmed public host yet -> honest not-reporting.
Tests: nodes normalizers (real captured wire shapes) + brand->network scoping.
typecheck clean, vitest 404/404 (37 files), next build green. package 8.2.1->8.2.2.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
A Network-category console module: lists org-scoped DNS zones and their records
on the unified /v1/dns surface (api.hanzo.ai gateway → hanzodns → CoreDNS +
Cloudflare sync). Honest BackendStateCard states (401/404/503) until the route
is bound — never fabricates a zone/record. Mirrors the Networks module; uses
@hanzo/data DataTable + the X-Org-Id the cloud client stamps.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
A Network-category console module: lists org-scoped DNS zones and their records
on the unified /v1/dns surface (api.hanzo.ai gateway → hanzodns → CoreDNS +
Cloudflare sync). Honest BackendStateCard states (401/404/503) until the route
is bound — never fabricates a zone/record. Mirrors the Networks module; uses
@hanzo/data DataTable + the X-Org-Id the cloud client stamps.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Consolidates 5 reviewed branches (PRs #24#25#28#29#35):
- Model catalog: real Zen ensō + Hanzo H marks; Providers link
- cmd+K: scrolls (mouse + keyboard-follow); docs deep links resolve (/docs)
- Settings: editable org branding (name/logo/colors/theme) with real save
- Linear-style ProductIcon tiles across cmd+K, sidebar, overview headers
- Per-category overview pages (12) + the AI hub
- Observability org-wide on login (Langfuse metrics, no per-project gate)
Consolidates 5 reviewed branches (PRs #24#25#28#29#35):
- Model catalog: real Zen ensō + Hanzo H marks; Providers link
- cmd+K: scrolls (mouse + keyboard-follow); docs deep links resolve (/docs)
- Settings: editable org branding (name/logo/colors/theme) with real save
- Linear-style ProductIcon tiles across cmd+K, sidebar, overview headers
- Per-category overview pages (12) + the AI hub
- Observability org-wide on login (Langfuse metrics, no per-project gate)
The Langfuse-derived views (metrics/logs/traces/sessions/scores/observations)
share the o11y REST client. Document + lock the tenancy contract: every call
stamps X-Org-Id (currentOrg(), always set on login) and adds X-Project-Id ONLY
when a project is selected — so these views are ORG-WIDE by default and narrow to
a project only when one is picked. No project required to 'just log in and see
metrics'. Adds a real MetricsModule (org rollups over /v1/o11y + /v1/metrics),
pure metrics logic, and its test. Honest states preserved (loading / not-
initialized 503 / empty) — no fabricated data.
The Langfuse-derived views (metrics/logs/traces/sessions/scores/observations)
share the o11y REST client. Document + lock the tenancy contract: every call
stamps X-Org-Id (currentOrg(), always set on login) and adds X-Project-Id ONLY
when a project is selected — so these views are ORG-WIDE by default and narrow to
a project only when one is picked. No project required to 'just log in and see
metrics'. Adds a real MetricsModule (org rollups over /v1/o11y + /v1/metrics),
pure metrics logic, and its test. Honest states preserved (loading / not-
initialized 503 / empty) — no fabricated data.
next.config transpilePackages still listed the OLD package name, so Next parsed
@hanzo/dash's shipped TSX source as plain JS → 'Unexpected token' on export type.
Rename the transpile entry, regenerate the lockfile onto @hanzo/dash@0.3.0.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
next.config transpilePackages still listed the OLD package name, so Next parsed
@hanzo/dash's shipped TSX source as plain JS → 'Unexpected token' on export type.
Rename the transpile entry, regenerate the lockfile onto @hanzo/dash@0.3.0.
Co-authored-by: hanzo-dev <dev@hanzo.ai>
* feat(base): render Bases under Org → Project (drop the 'tenant' noun)
A superbase tenant IS a full Hanzo Base instance → label the page 'Bases' + show
the Org → Project scope (top-bar ScopeSwitcher) as a breadcrumb, consistent with
every resource module. Passes labels + context to the shared @hanzo/dashboard
screens (props added in superbase feat/base-labels-context). Needs that package
republished + a version bump here to build.
* chore: @hanzo/dashboard → @hanzo/dash@0.3.0 (coherent SDK name) + Base labels/context
Renames the dashboard SDK dep + imports to the canonical @hanzo/dash (was the
incoherent @hanzo/dashboard). 0.3.0 carries the labels/context props so the Base
page renders 'Bases — <org> / <project>' (Org → Project scope) instead of the
'Tenants' noun.
* chore: v8.2.12 — Bases-under-Org via @hanzo/dash@0.3.0 (merge main)
---------
Co-authored-by: hanzo-dev <dev@hanzo.ai>
* feat(base): render Bases under Org → Project (drop the 'tenant' noun)
A superbase tenant IS a full Hanzo Base instance → label the page 'Bases' + show
the Org → Project scope (top-bar ScopeSwitcher) as a breadcrumb, consistent with
every resource module. Passes labels + context to the shared @hanzo/dashboard
screens (props added in superbase feat/base-labels-context). Needs that package
republished + a version bump here to build.
* chore: @hanzo/dashboard → @hanzo/dash@0.3.0 (coherent SDK name) + Base labels/context
Renames the dashboard SDK dep + imports to the canonical @hanzo/dash (was the
incoherent @hanzo/dashboard). 0.3.0 carries the labels/context props so the Base
page renders 'Bases — <org> / <project>' (Org → Project scope) instead of the
'Tenants' noun.
* chore: v8.2.12 — Bases-under-Org via @hanzo/dash@0.3.0 (merge main)
---------
Co-authored-by: hanzo-dev <dev@hanzo.ai>
Dave (maxpower) saw his real $99.74 on mount but it never CHANGED without a
reload — "not seeing increase in the wallet view". The balance READ path was
correct (every surface hits /billing/balance, server-scoped to the caller's
commerce subject = maxpower, the exact subject the gateway debits), but liveness
was missing: SidebarWallet only polled 30s; WalletModule, CostModule fetched on
mount only; nothing refetched on window focus or after a balance-affecting
action. So a completion (debit) or an external billing.hanzo.ai top-up (credit)
was invisible until a manual refresh/reload.
Fix — ONE shared reactive balance store (src/lib/billing/live-balance.ts):
- owns the single /billing/balance fetch (in-flight de-dupe + freshness window
so N mounted consumers cause ONE call);
- refetches on mount, on window focus + tab-visibility (returning from the Square
top-up portal now shows the new balance with no reload), and on ONE ref-counted
30s poll (paused when hidden);
- invalidateBalance() forces an immediate refetch after any balance-affecting action.
useCloudBalance() (useSyncExternalStore) is consumed by SidebarWallet, the Wallet
page cloud-credit card, and the Cost page balance card — every money surface now
shows the SAME live number.
Wire the completion seam: PlaygroundApi.chat (Chat/Playground/cmd-K) and the
streaming runner both invalidateBalance() on a finished completion, and the wallet
top-up success does too — so spend/credit reflects immediately.
Also: /billing proxy responses now send Cache-Control: no-store (a per-tenant
money response must never be cached). And drop the broken self-referential
node_modules 120000 symlink that origin/main re-tracked (it breaks
npm install / vitest / next build locally).
Tests: new live-balance.test.ts (10 — dedupe, freshness, phase mapping,
invalidate, no-flicker). tsc clean, vitest 573/573, next build green (14 pages).
Dave (maxpower) saw his real $99.74 on mount but it never CHANGED without a
reload — "not seeing increase in the wallet view". The balance READ path was
correct (every surface hits /billing/balance, server-scoped to the caller's
commerce subject = maxpower, the exact subject the gateway debits), but liveness
was missing: SidebarWallet only polled 30s; WalletModule, CostModule fetched on
mount only; nothing refetched on window focus or after a balance-affecting
action. So a completion (debit) or an external billing.hanzo.ai top-up (credit)
was invisible until a manual refresh/reload.
Fix — ONE shared reactive balance store (src/lib/billing/live-balance.ts):
- owns the single /billing/balance fetch (in-flight de-dupe + freshness window
so N mounted consumers cause ONE call);
- refetches on mount, on window focus + tab-visibility (returning from the Square
top-up portal now shows the new balance with no reload), and on ONE ref-counted
30s poll (paused when hidden);
- invalidateBalance() forces an immediate refetch after any balance-affecting action.
useCloudBalance() (useSyncExternalStore) is consumed by SidebarWallet, the Wallet
page cloud-credit card, and the Cost page balance card — every money surface now
shows the SAME live number.
Wire the completion seam: PlaygroundApi.chat (Chat/Playground/cmd-K) and the
streaming runner both invalidateBalance() on a finished completion, and the wallet
top-up success does too — so spend/credit reflects immediately.
Also: /billing proxy responses now send Cache-Control: no-store (a per-tenant
money response must never be cached). And drop the broken self-referential
node_modules 120000 symlink that origin/main re-tracked (it breaks
npm install / vitest / next build locally).
Tests: new live-balance.test.ts (10 — dedupe, freshness, phase mapping,
invalidate, no-flicker). tsc clean, vitest 573/573, next build green (14 pages).
RED's final re-review: double-encoded traversal CLOSED, recommends ship. Two LOW
residuals remained — both inert against the Go backend fleet, but Blue closes them
so the boundary is robust INDEPENDENT of any downstream decode behavior (don't rely
on 'the upstream is Go, single-decodes'):
- R1: N>=3 encoding (%25252e) / overlong UTF-8 (%c0%ae) — pathIsClean now rejects
ANY surviving percent-escape /%[0-9a-f]{2}/i (a legit segment carries none after
Next's single decode; a residual %XX is a multi-encoding/overlong tell). Does NOT
over-reject literal-% names (50%off -> %of, 'o' not hex -> allowed).
- R2: '..;' matrix-param traversal — reject any ';' segment (matrix params unused by
these REST APIs).
The authoritative post-normalization new URL() gate (v8.2.10) is unchanged; this is
the fast defense-in-depth first gate. Non-blocking per RED. RED INFO (/paas + /billing
bypass bearer-proxy) is by-design — they have their own gates (admin+service-token /
billing-scope.ts).
NOTE: local tsc/vitest are down (env upgraded to Node v26 mid-session + shared
node_modules symlink loop); change is a monotonic regex broadening over the
563-test-passing v8.2.10 guard. Validated via CI next build (Node 24) + live (%252e->404,
clean->401 no over-reject).
RED's final re-review: double-encoded traversal CLOSED, recommends ship. Two LOW
residuals remained — both inert against the Go backend fleet, but Blue closes them
so the boundary is robust INDEPENDENT of any downstream decode behavior (don't rely
on 'the upstream is Go, single-decodes'):
- R1: N>=3 encoding (%25252e) / overlong UTF-8 (%c0%ae) — pathIsClean now rejects
ANY surviving percent-escape /%[0-9a-f]{2}/i (a legit segment carries none after
Next's single decode; a residual %XX is a multi-encoding/overlong tell). Does NOT
over-reject literal-% names (50%off -> %of, 'o' not hex -> allowed).
- R2: '..;' matrix-param traversal — reject any ';' segment (matrix params unused by
these REST APIs).
The authoritative post-normalization new URL() gate (v8.2.10) is unchanged; this is
the fast defense-in-depth first gate. Non-blocking per RED. RED INFO (/paas + /billing
bypass bearer-proxy) is by-design — they have their own gates (admin+service-token /
billing-scope.ts).
NOTE: local tsc/vitest are down (env upgraded to Node v26 mid-session + shared
node_modules symlink loop); change is a monotonic regex broadening over the
563-test-passing v8.2.10 guard. Validated via CI next build (Node 24) + live (%252e->404,
clean->401 no over-reject).
Each product CATEGORY now has its own landing page at a stable
`/category/<slug>` route (AI, Compute, Data, Network, Security, …) — the
category-level twin of the native product overview. It shows the category name,
an honest one-line description of what the category is, and a grid of every
product in it (each card opening the product's native route). `soon` products
are shown with the existing SOON affordance — never hidden, never faked.
The "AI" overview is the hub for all things AI: it groups Models, Providers,
Inference, Agents, Embeddings, Playground, and Prompts, and leads with prominent
shortcuts to the Model Catalog and Providers.
- Routing follows the SAME pattern as products: one `ProductModule` with a
`:slug` `ProductRoute` (`categoryRouteModule`) in `productModules`, resolved by
the same `resolveRoute` and rendered by the same catch-all. It is deliberately
NOT a `catalog` entry — a category is a grouping of products, not a product, so
it never appears as a card in the nav / home / launcher. Unknown or
out-of-brand slugs `notFound()` (propagated cleanly by ProductErrorBoundary).
- All content is derived from the registry (`visibleCatalogByCategory`, brand-
and admin-scoped) — zero fabricated data. A new product appears on its
category page for free.
- Nav wiring: the sidebar level-1 category headers, the sidebar level-2
"More in <category>", and the catalog-home category headers all link to the
category overview. Breadcrumbs render `Home / Category / <Name>`.
- Pure taxonomy helpers `categorySlug` / `categoryFromSlug` / `CATEGORY_SUMMARY`
in brand-scope.ts (dependency-free), re-exported from the registry; unit-tested
in registry-brand.test.ts (round-trip, unique slugs, complete summaries).
No version bump.
Each product CATEGORY now has its own landing page at a stable
`/category/<slug>` route (AI, Compute, Data, Network, Security, …) — the
category-level twin of the native product overview. It shows the category name,
an honest one-line description of what the category is, and a grid of every
product in it (each card opening the product's native route). `soon` products
are shown with the existing SOON affordance — never hidden, never faked.
The "AI" overview is the hub for all things AI: it groups Models, Providers,
Inference, Agents, Embeddings, Playground, and Prompts, and leads with prominent
shortcuts to the Model Catalog and Providers.
- Routing follows the SAME pattern as products: one `ProductModule` with a
`:slug` `ProductRoute` (`categoryRouteModule`) in `productModules`, resolved by
the same `resolveRoute` and rendered by the same catch-all. It is deliberately
NOT a `catalog` entry — a category is a grouping of products, not a product, so
it never appears as a card in the nav / home / launcher. Unknown or
out-of-brand slugs `notFound()` (propagated cleanly by ProductErrorBoundary).
- All content is derived from the registry (`visibleCatalogByCategory`, brand-
and admin-scoped) — zero fabricated data. A new product appears on its
category page for free.
- Nav wiring: the sidebar level-1 category headers, the sidebar level-2
"More in <category>", and the catalog-home category headers all link to the
category overview. Breadcrumbs render `Home / Category / <Name>`.
- Pure taxonomy helpers `categorySlug` / `categoryFromSlug` / `CATEGORY_SUMMARY`
in brand-scope.ts (dependency-free), re-exported from the registry; unit-tested
in registry-brand.test.ts (round-trip, unique slugs, complete summaries).
No version bump.
Branding (Settings → Branding was read-only host config):
- BrandingTab is now an editable org-branding form (display name, website,
logo URL, favicon URL, primary color + "apply custom theme") with a real
Save that round-trips the FULL org record to Hanzo IAM via
TeamApi.updateOrganization → the /org/iam self-service proxy. Honest states:
saving / saved / error; a non-admin sees the fields read-only with a gated
notice (the server proxy 403 surfaced as the same honest access message).
No fake success. The prior host-runtime values stay as a read-only
"Runtime (resolved per host)" section.
- Server: /org/iam proxy now allows update-organization (org-admin-only via
requireAdminForWrite), pinned to the caller's OWN org by BOTH the ?id name
and the record's body name (forwardIam), so a brand admin can't retarget
another tenant. admin.ts adds a ThemeData type + Organization.themeData.
Icons (Linear-style):
- New src/components/ui/ProductIcon.tsx — a rounded-square tile filled with the
product's accent color and the glyph knocked out in near-white (the same
raw-hex fill + #fff glyph technique as SwatchButton / ProviderLogo); neutral
$color12/$color1 chip when no color.
- Swapped into CatalogRow (CommandPalette), the sidebar NavRow collapsed +
expanded and its L2 detail header (DashboardShell), and the NativeOverview
product header — each preserving the product's colorOf() accent.
Tests: iam-proxy.test adds org-name body extraction (the parsing the new
update-organization write guard depends on).
Branding (Settings → Branding was read-only host config):
- BrandingTab is now an editable org-branding form (display name, website,
logo URL, favicon URL, primary color + "apply custom theme") with a real
Save that round-trips the FULL org record to Hanzo IAM via
TeamApi.updateOrganization → the /org/iam self-service proxy. Honest states:
saving / saved / error; a non-admin sees the fields read-only with a gated
notice (the server proxy 403 surfaced as the same honest access message).
No fake success. The prior host-runtime values stay as a read-only
"Runtime (resolved per host)" section.
- Server: /org/iam proxy now allows update-organization (org-admin-only via
requireAdminForWrite), pinned to the caller's OWN org by BOTH the ?id name
and the record's body name (forwardIam), so a brand admin can't retarget
another tenant. admin.ts adds a ThemeData type + Organization.themeData.
Icons (Linear-style):
- New src/components/ui/ProductIcon.tsx — a rounded-square tile filled with the
product's accent color and the glyph knocked out in near-white (the same
raw-hex fill + #fff glyph technique as SwatchButton / ProviderLogo); neutral
$color12/$color1 chip when no color.
- Swapped into CatalogRow (CommandPalette), the sidebar NavRow collapsed +
expanded and its L2 detail header (DashboardShell), and the NativeOverview
product header — each preserving the product's colorOf() accent.
Tests: iam-proxy.test adds org-name body extraction (the parsing the new
update-organization write guard depends on).
RED's re-review confirmed 4/5 fixes closed but found a residual HIGH: pathIsClean
validated the PRE-normalization string, so a double-encoded %252e%252e (Next decodes
once -> %2e%2e, survives the guard) then normalized to real ../ inside undici's URL
parser at fetch time -> reached /v1/get-account, Base _superusers, escaped CLOUD_HEADS
on /cloud /vm /superbase. Live-proven (401 = passed the guard).
Robust fix (validate what fetch ACTUALLY sends):
- forwardWithUserBearer now re-parses the built target URL with new URL() and runs the
AUTHORITATIVE pathIsClean + allow() gate on the NORMALIZED pathname (relative to the
target base), then fetches that normalized dest — so %2e, double-encoding, and any
future encoding are all gated on the exact path undici will request. One-way, DRY:
fixes every helper proxy (/cloud, /vm, /superbase, /tasksd) at once.
- pathIsClean also now rejects %2e (not just %2f) as a fast defense-in-depth first gate
(catches the Next-single-decoded %2e%2e before URL construction).
New tests: 4 double-encoded pathIsClean cases (red today, green now). typecheck clean,
vitest 563/563, next build green. RED re-review of bearer-proxy path validation requested.
RED's re-review confirmed 4/5 fixes closed but found a residual HIGH: pathIsClean
validated the PRE-normalization string, so a double-encoded %252e%252e (Next decodes
once -> %2e%2e, survives the guard) then normalized to real ../ inside undici's URL
parser at fetch time -> reached /v1/get-account, Base _superusers, escaped CLOUD_HEADS
on /cloud /vm /superbase. Live-proven (401 = passed the guard).
Robust fix (validate what fetch ACTUALLY sends):
- forwardWithUserBearer now re-parses the built target URL with new URL() and runs the
AUTHORITATIVE pathIsClean + allow() gate on the NORMALIZED pathname (relative to the
target base), then fetches that normalized dest — so %2e, double-encoding, and any
future encoding are all gated on the exact path undici will request. One-way, DRY:
fixes every helper proxy (/cloud, /vm, /superbase, /tasksd) at once.
- pathIsClean also now rejects %2e (not just %2f) as a fast defense-in-depth first gate
(catches the Next-single-decoded %2e%2e before URL construction).
New tests: 4 double-encoded pathIsClean cases (red today, green now). typecheck clean,
vitest 563/563, next build green. RED re-review of bearer-proxy path validation requested.
- ProviderLogo rendered first-party (Zen/Hanzo) models with a generic Sparkles
glyph. Now render the REAL marks knocked out of a filled rounded tile: the Zen
ensō (identical geometry to @zenlm/logo) and the Hanzo block-H (@hanzo/logo) —
so zen models show the proper logo and read on-brand (Linear-style cut-out).
- Add a 'Providers' button to the Model Catalog header → /providers. Models and
providers are one AI surface; this makes it easy to get back to providers.
- ProviderLogo rendered first-party (Zen/Hanzo) models with a generic Sparkles
glyph. Now render the REAL marks knocked out of a filled rounded tile: the Zen
ensō (identical geometry to @zenlm/logo) and the Hanzo block-H (@hanzo/logo) —
so zen models show the proper logo and read on-brand (Linear-style cut-out).
- Add a 'Providers' button to the Model Catalog header → /providers. Models and
providers are one AI surface; this makes it easy to get back to providers.
Product modules mount CLIENT-ONLY under the catch-all route (the authed shell
renders a loader during SSR, so the /playground server HTML carries no module
markup — verified). With NO error boundary anywhere in the app, a throw in one
module's first client render bubbled to Next's root fallback and white-screened
the whole console with "Application error: a client-side exception has occurred"
— but only on a DIRECT load / REFRESH; in-app nav re-renders fresh and hid it.
That matches the reported /playground, /prompts, /gpus crashes exactly.
Fix (one place, closes the class for every product route — DRY):
- ProductErrorBoundary wraps the resolved module in the catch-all page. A module
throw now keeps the shell + nav and shows an honest, retryable card instead of
a white screen. Re-throws Next control flow (notFound/redirect/CSR bailout) so
routing still works; auto-recovers a ChunkLoadError (rolling-deploy skew) with
ONE guarded reload (no loop).
- app/(dashboard)/error.tsx: Next-native backstop for throws above the module
(the resolver), rendered inside the shell.
- boundary-logic.ts: pure decisions (chunk detect / control-flow detect / reload
gate), 11 unit tests. Proven end-to-end against a production build: a real
throw renders the card with zero uncaught pageerror (screenshots).
e2e/deeplink-refresh.spec.ts locks the reported scenario: /playground, /prompts,
/gpus (+ controls) must render on direct load AND refresh with no white-screen.
tsc clean · vitest 562/562 · next build green.
Product modules mount CLIENT-ONLY under the catch-all route (the authed shell
renders a loader during SSR, so the /playground server HTML carries no module
markup — verified). With NO error boundary anywhere in the app, a throw in one
module's first client render bubbled to Next's root fallback and white-screened
the whole console with "Application error: a client-side exception has occurred"
— but only on a DIRECT load / REFRESH; in-app nav re-renders fresh and hid it.
That matches the reported /playground, /prompts, /gpus crashes exactly.
Fix (one place, closes the class for every product route — DRY):
- ProductErrorBoundary wraps the resolved module in the catch-all page. A module
throw now keeps the shell + nav and shows an honest, retryable card instead of
a white screen. Re-throws Next control flow (notFound/redirect/CSR bailout) so
routing still works; auto-recovers a ChunkLoadError (rolling-deploy skew) with
ONE guarded reload (no loop).
- app/(dashboard)/error.tsx: Next-native backstop for throws above the module
(the resolver), rendered inside the shell.
- boundary-logic.ts: pure decisions (chunk detect / control-flow detect / reload
gate), 11 unit tests. Proven end-to-end against a production build: a real
throw renders the card with zero uncaught pageerror (screenshots).
e2e/deeplink-refresh.spec.ts locks the reported scenario: /playground, /prompts,
/gpus (+ controls) must render on direct load AND refresh with no white-screen.
tsc clean · vitest 562/562 · next build green.
- ProviderLogo rendered first-party (Zen/Hanzo) models with a generic Sparkles
glyph. Now render the REAL marks knocked out of a filled rounded tile: the Zen
ensō (identical geometry to @zenlm/logo) and the Hanzo block-H (@hanzo/logo) —
so zen models show the proper logo and read on-brand (Linear-style cut-out).
- Add a 'Providers' button to the Model Catalog header → /providers. Models and
providers are one AI surface; this makes it easy to get back to providers.
- ProviderLogo rendered first-party (Zen/Hanzo) models with a generic Sparkles
glyph. Now render the REAL marks knocked out of a filled rounded tile: the Zen
ensō (identical geometry to @zenlm/logo) and the Hanzo block-H (@hanzo/logo) —
so zen models show the proper logo and read on-brand (Linear-style cut-out).
- Add a 'Providers' button to the Model Catalog header → /providers. Models and
providers are one AI surface; this makes it easy to get back to providers.
* refactor(auth): call the account surface under /v1/iam/*
Pairs with hanzoai/ai serving signin/signout/get-account/update-preferences
under the organized /v1/iam/ namespace. The client account calls (account.ts)
and the server-side session resolve (identity.ts resolveUser) now target
/v1/iam/*; all remaining references (doc comments) updated for accuracy.
Deploy order: cloud-api (with V1IamRewriteFilter) MUST ship before this, so
/v1/iam/* resolves. No top-level fallback is kept — forward-perfect.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* refactor(cloud): default to cloud.hanzo.svc, drop the cloud-api alias name
The API binary Service is canonically `cloud` (universe renamed cloud-api →
cloud; the cloud-api ClusterIP is a transitional alias). The console2 CR already
sets CLOUD_API_URL=cloud.hanzo.svc, but the server-route code DEFAULTS still
named the dead alias — so any deployment without the explicit env (local dev)
would dial a name slated for removal. Point both defaults (identity.ts,
training proxy) at cloud.hanzo.svc — one name.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: zeekay <z@zeekay.io>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* refactor(auth): call the account surface under /v1/iam/*
Pairs with hanzoai/ai serving signin/signout/get-account/update-preferences
under the organized /v1/iam/ namespace. The client account calls (account.ts)
and the server-side session resolve (identity.ts resolveUser) now target
/v1/iam/*; all remaining references (doc comments) updated for accuracy.
Deploy order: cloud-api (with V1IamRewriteFilter) MUST ship before this, so
/v1/iam/* resolves. No top-level fallback is kept — forward-perfect.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
* refactor(cloud): default to cloud.hanzo.svc, drop the cloud-api alias name
The API binary Service is canonically `cloud` (universe renamed cloud-api →
cloud; the cloud-api ClusterIP is a transitional alias). The console2 CR already
sets CLOUD_API_URL=cloud.hanzo.svc, but the server-route code DEFAULTS still
named the dead alias — so any deployment without the explicit env (local dev)
would dial a name slated for removal. Point both defaults (identity.ts,
training proxy) at cloud.hanzo.svc — one name.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
---------
Co-authored-by: zeekay <z@zeekay.io>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Command palette (cmd+K):
- The results list clipped instead of scrolling: the body had maxH:420 but the
inner ScrollView had no flex bound. Add overflow:hidden on the body + flex:1
on the ScrollView so the list scrolls (mouse/trackpad) past the fold, and show
the scroll indicator.
- Keyboard ↑/↓ moved selection off-screen with no follow. Tag the active row
(id=cmdk-active) and scrollIntoView({block:'nearest'}) on selection change, so
arrowing always keeps the highlighted item visible. All 50 results are now
reachable and discoverable.
Docs deep links:
- docs.hanzo.ai serves the Fumadocs site under the /docs base path
(docs.hanzo.ai/docs/<slug>), but the console linked bare docs.hanzo.ai/<slug>
→ every 'Full docs' / resource docs link 404'd. Point DOCS (registry) and
docsUrl(kind) (resource/logic) at .../docs. Matches the created product pages.
Command palette (cmd+K):
- The results list clipped instead of scrolling: the body had maxH:420 but the
inner ScrollView had no flex bound. Add overflow:hidden on the body + flex:1
on the ScrollView so the list scrolls (mouse/trackpad) past the fold, and show
the scroll indicator.
- Keyboard ↑/↓ moved selection off-screen with no follow. Tag the active row
(id=cmdk-active) and scrollIntoView({block:'nearest'}) on selection change, so
arrowing always keeps the highlighted item visible. All 50 results are now
reachable and discoverable.
Docs deep links:
- docs.hanzo.ai serves the Fumadocs site under the /docs base path
(docs.hanzo.ai/docs/<slug>), but the console linked bare docs.hanzo.ai/<slug>
→ every 'Full docs' / resource docs link 404'd. Point DOCS (registry) and
docsUrl(kind) (resource/logic) at .../docs. Matches the created product pages.
* fix(vm proxy): default VISOR_URL to visor.hanzo.svc:19000 (was :80)
Cosmetic source fix — the live CR + universe already set VISOR_URL to :19000, which
governs runtime. This corrects the fallback constant so an env-less run also targets
the port visor actually serves (its Service exposes :19000 only; :80 → 502 upstream
unreachable). No version bump; rides the next build (the compute session owns /vm).
* fix(security): RED findings — cross-tenant projects, %2f allow-list bypass, scope headers, error DNS (v8.2.7)
Adversarial review (RED, PR#18/#19) found live holes in the BFF auth path. Fixes:
- [CRITICAL] Cross-tenant project enumeration. /org/iam/get-organization-projects
with an OMITTED/empty ?organization passed the 'validate-if-present' check
(ownerOk(null)=true), and IAM drops its WHERE on empty -> returned EVERY org's
projects (IAM bypasses Casbin for project routes, so the proxy is the only gate).
CONFIRMED LIVE (Dave/maxpower saw dhd, 7stars-dev projects). Fix: forwardIam now
PINS ?organization to the caller's orgScope for a non-global admin on org-keyed
segments (pinnedSearch, server-authoritative like X-Org-Id); global admins
unrestricted. Org-keyed WRITES must carry owner+organization == own org (no
owner='' junk rows). New orgParamSegments={get-organization-projects,add/delete-project}.
- [HIGH] %2f + .. allow-list bypass on /cloud, /superbase, /tasksd. Next decodes
%2f into segments without re-normalizing dot-segments, and fetch() collapses '..'
AFTER the allow-list -> 'functions%2f..%2f..%2fiam' slipped a foreign head past
allowCloudSurface. Fix: forwardWithUserBearer now rejects any '', '.', '..' or
surviving %2f segment (pathIsClean) BEFORE the allow-list, and trims trailing
slashes. One guard fixes every helper-based proxy; /ai was already immune (exact-match Set).
- [MEDIUM] Dropped forwardScope on /cloud + /vm — no longer forward browser-controlled
X-Project-Id/X-Environment (org is authoritative via the Bearer owner; the resources
are org-keyed). A project-scoped feature must validate membership first.
- [LOW] Redacted 502 bodies (were leaking internal svc host/port) -> generic message +
server-side console.error. Both bearer-proxy and iam-proxy.
- [bundled] /vm default VISOR_URL -> visor.hanzo.svc:19000 (was :80; visor serves :19000).
New pure tests: pinnedSearch (4), pathIsClean (3). typecheck clean, vitest 551/551,
next build green. Re-review by RED requested.
* fix(vm proxy): default VISOR_URL to visor.hanzo.svc:19000 (was :80)
Cosmetic source fix — the live CR + universe already set VISOR_URL to :19000, which
governs runtime. This corrects the fallback constant so an env-less run also targets
the port visor actually serves (its Service exposes :19000 only; :80 → 502 upstream
unreachable). No version bump; rides the next build (the compute session owns /vm).
* fix(security): RED findings — cross-tenant projects, %2f allow-list bypass, scope headers, error DNS (v8.2.7)
Adversarial review (RED, PR#18/#19) found live holes in the BFF auth path. Fixes:
- [CRITICAL] Cross-tenant project enumeration. /org/iam/get-organization-projects
with an OMITTED/empty ?organization passed the 'validate-if-present' check
(ownerOk(null)=true), and IAM drops its WHERE on empty -> returned EVERY org's
projects (IAM bypasses Casbin for project routes, so the proxy is the only gate).
CONFIRMED LIVE (Dave/maxpower saw dhd, 7stars-dev projects). Fix: forwardIam now
PINS ?organization to the caller's orgScope for a non-global admin on org-keyed
segments (pinnedSearch, server-authoritative like X-Org-Id); global admins
unrestricted. Org-keyed WRITES must carry owner+organization == own org (no
owner='' junk rows). New orgParamSegments={get-organization-projects,add/delete-project}.
- [HIGH] %2f + .. allow-list bypass on /cloud, /superbase, /tasksd. Next decodes
%2f into segments without re-normalizing dot-segments, and fetch() collapses '..'
AFTER the allow-list -> 'functions%2f..%2f..%2fiam' slipped a foreign head past
allowCloudSurface. Fix: forwardWithUserBearer now rejects any '', '.', '..' or
surviving %2f segment (pathIsClean) BEFORE the allow-list, and trims trailing
slashes. One guard fixes every helper-based proxy; /ai was already immune (exact-match Set).
- [MEDIUM] Dropped forwardScope on /cloud + /vm — no longer forward browser-controlled
X-Project-Id/X-Environment (org is authoritative via the Bearer owner; the resources
are org-keyed). A project-scoped feature must validate membership first.
- [LOW] Redacted 502 bodies (were leaking internal svc host/port) -> generic message +
server-side console.error. Both bearer-proxy and iam-proxy.
- [bundled] /vm default VISOR_URL -> visor.hanzo.svc:19000 (was :80; visor serves :19000).
New pure tests: pinnedSearch (4), pathIsClean (3). typecheck clean, vitest 551/551,
next build green. Re-review by RED requested.
Advance prod (operator-pinned v8.1.1) to current main: KMS secret CRUD, IAM
Users CRUD, IAM Roles CRUD, 89-page e2e harness. Build publishes
ghcr.io/hanzoai/console2:v8.2.7; operator CR bump follows once the image lands.
Advance prod (operator-pinned v8.1.1) to current main: KMS secret CRUD, IAM
Users CRUD, IAM Roles CRUD, 89-page e2e harness. Build publishes
ghcr.io/hanzoai/console2:v8.2.7; operator CR bump follows once the image lands.
Cuts a release so prod (operator-pinned) can advance from v8.1.1 to include:
- KMS secret management (create/reveal/delete)
- IAM Users CRUD (create/promote/delete)
- IAM Roles CRUD (create/delete)
- 89-page screenshot e2e harness
All auth via /v1/iam/* + cookie-session /v1/*. Build publishes
ghcr.io/hanzoai/console2:v8.2.7.
Cuts a release so prod (operator-pinned) can advance from v8.1.1 to include:
- KMS secret management (create/reveal/delete)
- IAM Users CRUD (create/promote/delete)
- IAM Roles CRUD (create/delete)
- 89-page screenshot e2e harness
All auth via /v1/iam/* + cookie-session /v1/*. Build publishes
ghcr.io/hanzoai/console2:v8.2.7.
IAM already serves /v1/iam/{add,update,delete}-role (iam controllers/role.go) —
I was wrong that it needed a backend. Wire it: allowlist the 3 role mutations in
the /admin/iam proxy, add addRole/updateRole/deleteRole to IamAdminApi, and give
the Roles tab a create/delete view (RolesAdminView, mirrors UsersAdminView).
All auth flows through /v1/iam/* per the one-path rule. Typecheck clean.
IAM is now fully CRUD in-console: Orgs (list), Users (create/promote/delete),
Roles (create/delete), Applications + Providers (add/edit/delete) — no link-out
for the common lifecycle.
IAM already serves /v1/iam/{add,update,delete}-role (iam controllers/role.go) —
I was wrong that it needed a backend. Wire it: allowlist the 3 role mutations in
the /admin/iam proxy, add addRole/updateRole/deleteRole to IamAdminApi, and give
the Roles tab a create/delete view (RolesAdminView, mirrors UsersAdminView).
All auth flows through /v1/iam/* per the one-path rule. Typecheck clean.
IAM is now fully CRUD in-console: Orgs (list), Users (create/promote/delete),
Roles (create/delete), Applications + Providers (add/edit/delete) — no link-out
for the common lifecycle.
Projects rendered 'not routed' because ProjectApi hit the cloud /v1 cookie path
for IAM endpoints: console.hanzo.ai/v1/iam/get-organization-projects → the gateway
sends /v1/* to the CLOUD binary, which does NOT serve IAM → 404. Proven live:
that exact URL returns 404, while IAM serves the endpoint.
Fix (same BFF-Bearer pattern, existing infra — no new mega-router):
- projects.ts now calls the same-origin /org/iam proxy via makeIamClient, which
mints a user-bound Bearer server-side and forwards to iam.hanzo.svc. Org resolves
from the token owner claim (per-tenant), the member-roster pattern.
- /org/iam allow-list gains get-organization-projects (GET) + add-project,
delete-project (POST, org-admin only via requireAdminForWrite).
- SECURITY: forwardIam now also pins the ?organization param AND the body
organization field to the caller's org (ownerOk), closing the cross-tenant gap
for the projects lister/CRUD (ownerOk(null) is a no-op for segments without it,
so no regression to get-users/get-roles). bodyOwner generalized to bodyField.
typecheck clean, vitest 505/505 (+4 new: projects.test.ts, iam-proxy.test.ts),
next build green. Auth-mint/proxy path touched → hand to RED.
Projects rendered 'not routed' because ProjectApi hit the cloud /v1 cookie path
for IAM endpoints: console.hanzo.ai/v1/iam/get-organization-projects → the gateway
sends /v1/* to the CLOUD binary, which does NOT serve IAM → 404. Proven live:
that exact URL returns 404, while IAM serves the endpoint.
Fix (same BFF-Bearer pattern, existing infra — no new mega-router):
- projects.ts now calls the same-origin /org/iam proxy via makeIamClient, which
mints a user-bound Bearer server-side and forwards to iam.hanzo.svc. Org resolves
from the token owner claim (per-tenant), the member-roster pattern.
- /org/iam allow-list gains get-organization-projects (GET) + add-project,
delete-project (POST, org-admin only via requireAdminForWrite).
- SECURITY: forwardIam now also pins the ?organization param AND the body
organization field to the caller's org (ownerOk), closing the cross-tenant gap
for the projects lister/CRUD (ownerOk(null) is a no-op for segments without it,
so no regression to get-users/get-roles). bodyOwner generalized to bodyField.
typecheck clean, vitest 505/505 (+4 new: projects.test.ts, iam-proxy.test.ts),
next build green. Auth-mint/proxy path touched → hand to RED.
The ai data-scoping filters (GetEffectiveOrg, controllers/org_resolver.go)
and the provisioning sub-service both read `X-Org-Id` — NOT `X-IAM-Org-Id`.
cloud mints X-IAM-Org-Id OUTBOUND toward commerce from the validated
principal, so the browser stamp was inert dead weight (and the old comment
claiming GetEffectiveOrg reads X-IAM-Org-Id was drift). Keep the required
X-Org-Id stamp; drop X-IAM-Org-Id; note X-Project-Id is the canonical
project sub-scope evalsvc now reads.
The ai data-scoping filters (GetEffectiveOrg, controllers/org_resolver.go)
and the provisioning sub-service both read `X-Org-Id` — NOT `X-IAM-Org-Id`.
cloud mints X-IAM-Org-Id OUTBOUND toward commerce from the validated
principal, so the browser stamp was inert dead weight (and the old comment
claiming GetEffectiveOrg reads X-IAM-Org-Id was drift). Keep the required
X-Org-Id stamp; drop X-IAM-Org-Id; note X-Project-Id is the canonical
project sub-scope evalsvc now reads.
The data + serverless surfaces (vector/sql/kv/s3/docdb/datastore/search,
functions/prompts/agents) and visor compute now resolve org from the Bearer
JWT owner claim; a cookie-only browser call 403s ('X-Org-Id required'). The
console BFF now mints a short-lived user-bound IAM token server-side (the
proven /ai + /keys pattern) and forwards it, so the browser path works
end-to-end, per-org — no token in the browser, org never browser-supplied.
- src/lib/server/bearer-proxy.ts — ONE shared forwardWithUserBearer(req, opts):
resolveUser (session cookie) -> adminBearer (shared per-user token cache in
identity.ts) -> forward with Authorization: Bearer + X-Org-Id=owner, cookie
NEVER forwarded (dodges the public-gateway 431), response STREAMED (SSE/JSON/
204). Pure errorBody/upstreamHeaders + proxy-allow.ts allow-lists, unit-tested.
- app/cloud/[...path] — user-bearer proxy to cloud-api for the data + serverless
heads (allowCloudSurface); provisioning.ts + functions.ts repointed to
<origin>/cloud/v1/* (was the cookie-only direct path that 403s).
- app/vm/[...path] — user-bearer proxy to visor (allowVisorSurface) for the
compute surface (regions/gpus/machines); ready for the compute UI.
- DRY: /ai, /tasksd, /superbase refactored onto the shared helper — 3 duplicate
issue-user-token caches deleted, one adminBearer cache for every proxy.
typecheck clean, vitest 464/464 (+14 new), next build green (/cloud + /vm compiled).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The data + serverless surfaces (vector/sql/kv/s3/docdb/datastore/search,
functions/prompts/agents) and visor compute now resolve org from the Bearer
JWT owner claim; a cookie-only browser call 403s ('X-Org-Id required'). The
console BFF now mints a short-lived user-bound IAM token server-side (the
proven /ai + /keys pattern) and forwards it, so the browser path works
end-to-end, per-org — no token in the browser, org never browser-supplied.
- src/lib/server/bearer-proxy.ts — ONE shared forwardWithUserBearer(req, opts):
resolveUser (session cookie) -> adminBearer (shared per-user token cache in
identity.ts) -> forward with Authorization: Bearer + X-Org-Id=owner, cookie
NEVER forwarded (dodges the public-gateway 431), response STREAMED (SSE/JSON/
204). Pure errorBody/upstreamHeaders + proxy-allow.ts allow-lists, unit-tested.
- app/cloud/[...path] — user-bearer proxy to cloud-api for the data + serverless
heads (allowCloudSurface); provisioning.ts + functions.ts repointed to
<origin>/cloud/v1/* (was the cookie-only direct path that 403s).
- app/vm/[...path] — user-bearer proxy to visor (allowVisorSurface) for the
compute surface (regions/gpus/machines); ready for the compute UI.
- DRY: /ai, /tasksd, /superbase refactored onto the shared helper — 3 duplicate
issue-user-token caches deleted, one adminBearer cache for every proxy.
typecheck clean, vitest 464/464 (+14 new), next build green (/cloud + /vm compiled).
Co-authored-by: Hanzo AI <ai@hanzo.ai>
* feat(console2): make all 14 external products native in-console overviews
The registry declared 14 products with kind:'external' (gateway, dns, cdn,
mpc, cli, sdks, api, ide, desktop, registry, metrics, crawl, studio, console),
but open.ts / match-core / NativeOverview / overviewFor were already collapsed
to a no-external world. Result: those 14 pushed /${id} which resolveProductView
returned notfound → HARD 404 dead links from the overview grid + app launcher.
Convert each external entry to kind:'module' routes:overviewRoutes(id), rendering
the existing NativeOverview (bespoke OVERVIEW_SPECS already merged — real header,
live platform-app health, key facts, native actions, INLINE docs, zero link-out).
Collapse CatalogEntry union to module-only and ProductStatus to enabled|soon;
remove the dead external branches in DashboardShell + OverviewModule and the stale
ext/href config. One way to open anything: a native route.
resolve.test.ts already pins all 14 specs + native-route actions; match-core.test
updated to assert the kind-guard fails closed for a non-module entry.
typecheck 0 errors, 381 vitest pass.
* feat(console2): Subscriptions + Payment Methods + Marketplace pages (real feeds)
Three new production-complete control-plane pages, all backed by REAL /v1 data,
matching the console taxonomy — no new backend needed (they ride existing feeds).
Billing sub-pages (category Observe, alongside cost/plans):
- SubscriptionsModule → GET /v1/billing/subscriptions (commerce, via the /billing
per-tenant proxy: server-injected COMMERCE_TOKEN, org-scoped, client can't widen).
Plan / status / seats / price / renewal. Read-only; manage links to the portal.
- PaymentMethodsModule → GET /v1/billing/payment-methods. Card-data MASKED by
construction: normalizer extracts only brand+last4+expMonth/Year+isDefault — a
PAN/CVV/token in the payload is dropped and never reaches the display object
(dedicated leak test asserts it). Renders '•••• last4'. Read-only; add links to portal.
- billing.ts: Subscription+PaymentMethod types + normalizeSubscriptions/
normalizePaymentMethods (handle Stripe snake_case AND camelCase, nested card obj,
Unix seconds/ms dates). billing.test.ts: +9 tests incl the PAN/CVV/token leak guard.
Marketplace (category Apps, alongside chat/bot/search):
- MarketplaceModule → the storefront over the REAL model catalog (aicatalog.
fetchCatalog → GET /v1/pricing/models via the authed /ai proxy). Category tiles,
featured shelf (real catalog flag), filterable listings w/ real per-Mtok pricing,
Try-it→Playground CTA. Reuses the existing aicatalog client + ProviderLogo — a
distinct storefront view over the SAME catalog, not a duplicate of Model Catalog.
- marketplace/logic.ts (categorize/featured/applyFilters/marketStats) + 16 tests
incl a regex-injection safety test (search is a literal substring filter).
Hardening across all three: read-only, org-scoped (IDOR-proof), no secrets in the
bundle, XSS-safe (plain <Text>, no dangerouslySetInnerHTML), honest loading/empty/
error states (BackendStateCard/ErrorState), every number a real field or '—' —
nothing fabricated. Tamagui shorthand only, dark design language.
typecheck 0 errors · 406 vitest pass (+25 from the new suites).
* docs(console2): document the all-pages build in LLM.md (external→native + billing/marketplace + honest scope)
* fix(console2): billing-proxy tenant isolation — X-Org-Id + full subject-key pinning (RED HIGH)
RED found the /billing proxy's tenant scoping was INERT — a cross-tenant IDOR:
1. It stamped X-Hanzo-Org, but commerce reads X-Org-Id on the service-token path
(commerce/middleware/accesstoken.go) — the header silently fell back to the
service org, so every tenant shared one commerce namespace.
2. It pinned only ?user=, but subscriptions filter ?userId=
(commerce/api/billing/subscriptions.go) — with no userId the query returned
EVERY subject's subscriptions in the namespace (cross-tenant read).
Fix, mirroring commerce's own edge-auth exactly:
- Send X-Org-Id (like the exemplary /ai proxy) so the namespace resolves per-tenant.
- Pin the FULL subject-key set {user,userId,customerId} to the server-resolved
subject (= commerce/middleware/edgeauth.go billingSubjectKeys) so NO billing
endpoint is left unfiltered whichever param it reads; ?org= is still dropped.
- Extract the scoping to a pure src/lib/server/billing-scope.ts (scopedBillingSearch
+ billingSubject) — testable without the Next runtime, same pattern as ai-proxy.ts.
- Defense-in-depth: normalizePaymentMethods clamps last4 to the last 4 digits even
if commerce puts a full PAN there.
Tests: billing-scope.test.ts (11) — client-forged-subject overwrite, two-tenant
disjointness, non-subject passthrough; billing.test.ts +1 (last4 PAN clamp);
e2e/billing-isolation.spec.ts — live two-tenant disjoint subscription/payment sets;
the 3 new pages added to the 89-route render pass. typecheck 0, 487 vitest, next build ✓.
Rebased on latest main (living-overview #17).
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
* feat(console2): make all 14 external products native in-console overviews
The registry declared 14 products with kind:'external' (gateway, dns, cdn,
mpc, cli, sdks, api, ide, desktop, registry, metrics, crawl, studio, console),
but open.ts / match-core / NativeOverview / overviewFor were already collapsed
to a no-external world. Result: those 14 pushed /${id} which resolveProductView
returned notfound → HARD 404 dead links from the overview grid + app launcher.
Convert each external entry to kind:'module' routes:overviewRoutes(id), rendering
the existing NativeOverview (bespoke OVERVIEW_SPECS already merged — real header,
live platform-app health, key facts, native actions, INLINE docs, zero link-out).
Collapse CatalogEntry union to module-only and ProductStatus to enabled|soon;
remove the dead external branches in DashboardShell + OverviewModule and the stale
ext/href config. One way to open anything: a native route.
resolve.test.ts already pins all 14 specs + native-route actions; match-core.test
updated to assert the kind-guard fails closed for a non-module entry.
typecheck 0 errors, 381 vitest pass.
* feat(console2): Subscriptions + Payment Methods + Marketplace pages (real feeds)
Three new production-complete control-plane pages, all backed by REAL /v1 data,
matching the console taxonomy — no new backend needed (they ride existing feeds).
Billing sub-pages (category Observe, alongside cost/plans):
- SubscriptionsModule → GET /v1/billing/subscriptions (commerce, via the /billing
per-tenant proxy: server-injected COMMERCE_TOKEN, org-scoped, client can't widen).
Plan / status / seats / price / renewal. Read-only; manage links to the portal.
- PaymentMethodsModule → GET /v1/billing/payment-methods. Card-data MASKED by
construction: normalizer extracts only brand+last4+expMonth/Year+isDefault — a
PAN/CVV/token in the payload is dropped and never reaches the display object
(dedicated leak test asserts it). Renders '•••• last4'. Read-only; add links to portal.
- billing.ts: Subscription+PaymentMethod types + normalizeSubscriptions/
normalizePaymentMethods (handle Stripe snake_case AND camelCase, nested card obj,
Unix seconds/ms dates). billing.test.ts: +9 tests incl the PAN/CVV/token leak guard.
Marketplace (category Apps, alongside chat/bot/search):
- MarketplaceModule → the storefront over the REAL model catalog (aicatalog.
fetchCatalog → GET /v1/pricing/models via the authed /ai proxy). Category tiles,
featured shelf (real catalog flag), filterable listings w/ real per-Mtok pricing,
Try-it→Playground CTA. Reuses the existing aicatalog client + ProviderLogo — a
distinct storefront view over the SAME catalog, not a duplicate of Model Catalog.
- marketplace/logic.ts (categorize/featured/applyFilters/marketStats) + 16 tests
incl a regex-injection safety test (search is a literal substring filter).
Hardening across all three: read-only, org-scoped (IDOR-proof), no secrets in the
bundle, XSS-safe (plain <Text>, no dangerouslySetInnerHTML), honest loading/empty/
error states (BackendStateCard/ErrorState), every number a real field or '—' —
nothing fabricated. Tamagui shorthand only, dark design language.
typecheck 0 errors · 406 vitest pass (+25 from the new suites).
* docs(console2): document the all-pages build in LLM.md (external→native + billing/marketplace + honest scope)
* fix(console2): billing-proxy tenant isolation — X-Org-Id + full subject-key pinning (RED HIGH)
RED found the /billing proxy's tenant scoping was INERT — a cross-tenant IDOR:
1. It stamped X-Hanzo-Org, but commerce reads X-Org-Id on the service-token path
(commerce/middleware/accesstoken.go) — the header silently fell back to the
service org, so every tenant shared one commerce namespace.
2. It pinned only ?user=, but subscriptions filter ?userId=
(commerce/api/billing/subscriptions.go) — with no userId the query returned
EVERY subject's subscriptions in the namespace (cross-tenant read).
Fix, mirroring commerce's own edge-auth exactly:
- Send X-Org-Id (like the exemplary /ai proxy) so the namespace resolves per-tenant.
- Pin the FULL subject-key set {user,userId,customerId} to the server-resolved
subject (= commerce/middleware/edgeauth.go billingSubjectKeys) so NO billing
endpoint is left unfiltered whichever param it reads; ?org= is still dropped.
- Extract the scoping to a pure src/lib/server/billing-scope.ts (scopedBillingSearch
+ billingSubject) — testable without the Next runtime, same pattern as ai-proxy.ts.
- Defense-in-depth: normalizePaymentMethods clamps last4 to the last 4 digits even
if commerce puts a full PAN there.
Tests: billing-scope.test.ts (11) — client-forged-subject overwrite, two-tenant
disjointness, non-subject passthrough; billing.test.ts +1 (last4 PAN clamp);
e2e/billing-isolation.spec.ts — live two-tenant disjoint subscription/payment sets;
the 3 new pages added to the 89-route render pass. typecheck 0, 487 vitest, next build ✓.
Rebased on latest main (living-overview #17).
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Per the 'one /v1, no extraneous prefix' rule: the Networks module now calls
same-origin /v1/networks (gateway-routed to the bootnode control plane), not a
per-backend /bootnode/* proxy. Deletes app/bootnode. Honest states unchanged.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Per the 'one /v1, no extraneous prefix' rule: the Networks module now calls
same-origin /v1/networks (gateway-routed to the bootnode control plane), not a
per-backend /bootnode/* proxy. Deletes app/bootnode. Honest states unchanged.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The admin Platform Overview is now a REUSABLE `LivingOverview` component system
(one component, many configs), not a one-off. Videogame-like: count-up KPIs, live
sparklines, a streaming/virtualized activity feed, throttled polling — tasteful,
60fps, reduced-motion-guarded. Backed by REAL /v1 data, no mocks; every missing
feed renders its honest empty/skeleton/em-dash, never fabricated numbers.
System (src/components/products/overview/living/):
- config.ts declarative LivingOverviewConfig: tiles in rows + one real-data
load() => OverviewData + a live block (pollMs/countUp).
- motion.ts pure count-up/sparkline-ring/poll-clock math (unit-tested).
- hooks.ts thin rAF/interval drivers (useCountUp animates from the current
on-screen value on retarget; usePoll/useReducedMotion/usePageHidden),
all self-cleaning — no leaked frames/timers.
- logic.ts pure tile decisions: unit-aware formatMetric, deltaOf ("—" w/o basis),
hasTrend, status/health colors, mergeActivity (stream dedupe),
windowRows (virtualization), worst/tally (unit-tested).
- tiles.tsx the 6 animated tiles (reuse ui/Charts verbatim; skeleton/empty/error).
- LivingOverview.tsx the driver: one throttled poll loop (5s floor, paused when
hidden/errored), reqRef race guard, background refetch never blanks a
board with real data. globals.css: hz-skeleton/hz-pulse/hz-row-in.
Real data (adapters.ts, pure + tested): fromCloudUsage (commerce usage ledger),
fromAdminOverview (new lib/api/admin-overview.ts — /v1/admin/overview, optional-safe,
degrades to honest empty on 404), fromFunctions, healthFromApps (operator inventory).
Wired (overview/living/registry.ts — declarative catalog): overview (platform
centerpiece at / and /overview; admin aggregate w/ honest fallback to usage+health),
ai-metrics, functions, gpus. Product route '' renders livingOverviewModule(id); tabbed
products keep :tab, reachable via the sidebar sub-nav (declared subpages) — no dead-end.
Adding a product overview = one config, no UI.
Deletes the superseded OverviewModule + AiMetricsModule (+ aimetrics/{StatTile,
UsageChart,format}) — one overview system, DRY.
typecheck clean (0 errors), 449/449 tests (42 files), next build green (14/14).
Visual proof via headless Playwright: full board renders w/ count-up + live sparklines
+ streaming + donut + health tally, values change across a 5s poll, reduced-motion
snaps to real values, functions/gpus render honest empty/error states w/o crashing.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The admin Platform Overview is now a REUSABLE `LivingOverview` component system
(one component, many configs), not a one-off. Videogame-like: count-up KPIs, live
sparklines, a streaming/virtualized activity feed, throttled polling — tasteful,
60fps, reduced-motion-guarded. Backed by REAL /v1 data, no mocks; every missing
feed renders its honest empty/skeleton/em-dash, never fabricated numbers.
System (src/components/products/overview/living/):
- config.ts declarative LivingOverviewConfig: tiles in rows + one real-data
load() => OverviewData + a live block (pollMs/countUp).
- motion.ts pure count-up/sparkline-ring/poll-clock math (unit-tested).
- hooks.ts thin rAF/interval drivers (useCountUp animates from the current
on-screen value on retarget; usePoll/useReducedMotion/usePageHidden),
all self-cleaning — no leaked frames/timers.
- logic.ts pure tile decisions: unit-aware formatMetric, deltaOf ("—" w/o basis),
hasTrend, status/health colors, mergeActivity (stream dedupe),
windowRows (virtualization), worst/tally (unit-tested).
- tiles.tsx the 6 animated tiles (reuse ui/Charts verbatim; skeleton/empty/error).
- LivingOverview.tsx the driver: one throttled poll loop (5s floor, paused when
hidden/errored), reqRef race guard, background refetch never blanks a
board with real data. globals.css: hz-skeleton/hz-pulse/hz-row-in.
Real data (adapters.ts, pure + tested): fromCloudUsage (commerce usage ledger),
fromAdminOverview (new lib/api/admin-overview.ts — /v1/admin/overview, optional-safe,
degrades to honest empty on 404), fromFunctions, healthFromApps (operator inventory).
Wired (overview/living/registry.ts — declarative catalog): overview (platform
centerpiece at / and /overview; admin aggregate w/ honest fallback to usage+health),
ai-metrics, functions, gpus. Product route '' renders livingOverviewModule(id); tabbed
products keep :tab, reachable via the sidebar sub-nav (declared subpages) — no dead-end.
Adding a product overview = one config, no UI.
Deletes the superseded OverviewModule + AiMetricsModule (+ aimetrics/{StatTile,
UsageChart,format}) — one overview system, DRY.
typecheck clean (0 errors), 449/449 tests (42 files), next build green (14/14).
Visual proof via headless Playwright: full board renders w/ count-up + live sparklines
+ streaming + donut + health tally, values change across a 5s poll, reduced-motion
snaps to real values, functions/gpus render honest empty/error states w/o crashing.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Drives a signed-in session over every registered product route, asserts each
mounts without a hard crash (no Next error overlay, non-blank body, <500), and
captures a full-page screenshot to e2e/screenshots/<id>.png. The 'screenshot it
all, verify every page is wired FE↔BE' pass. Gitignores screenshots/test-results.
Running it against live console.hanzo.ai surfaced a P0: the cloud /v1 backend is
returning 502/503, so sign-in (/v1/signin) fails for all users.
Drives a signed-in session over every registered product route, asserts each
mounts without a hard crash (no Next error overlay, non-blank body, <500), and
captures a full-page screenshot to e2e/screenshots/<id>.png. The 'screenshot it
all, verify every page is wired FE↔BE' pass. Gitignores screenshots/test-results.
Running it against live console.hanzo.ai surfaced a P0: the cloud /v1 backend is
returning 502/503, so sign-in (/v1/signin) fails for all users.
IamModule's Users tab was read-only + linked out to the external casdoor console,
but IamAdminApi already has add/update/delete-user (and the /admin/iam proxy
allowlists those mutations). Surface them: create user (name/email/password,
argon2id-hashed by IAM), promote/demote global-admin (shield toggle), and delete
— all scoped to the active org through the server-gated proxy. Honest states
(loading / operator-required 403 / error / empty). Typecheck clean.
IamModule's Users tab was read-only + linked out to the external casdoor console,
but IamAdminApi already has add/update/delete-user (and the /admin/iam proxy
allowlists those mutations). Surface them: create user (name/email/password,
argon2id-hashed by IAM), promote/demote global-admin (shield toggle), and delete
— all scoped to the active org through the server-gated proxy. Honest states
(loading / operator-required 403 / error / empty). Typecheck clean.
The KmsModule listed metadata and linked OUT to the standalone kms.hanzo.ai
console for everything else. But the /admin/kms proxy + KmsAdminApi already
support full CRUD (list/reveal/create/rotate/remove) over /v1/kms/orgs/{org}/
secrets. Surface it: create/upsert form (path/name/env/value, secure), per-row
reveal (one value, shown once, audited, never cached/listed), and delete — all
through the server-gated admin proxy, scoped to the active org. Keeps the
zero-knowledge stance (no bulk value listing). Removes the external link-out, so
console2 is the single KMS management surface. Typecheck clean.
The KmsModule listed metadata and linked OUT to the standalone kms.hanzo.ai
console for everything else. But the /admin/kms proxy + KmsAdminApi already
support full CRUD (list/reveal/create/rotate/remove) over /v1/kms/orgs/{org}/
secrets. Surface it: create/upsert form (path/name/env/value, secure), per-row
reveal (one value, shown once, audited, never cached/listed), and delete — all
through the server-gated admin proxy, scoped to the active org. Keeps the
zero-knowledge stance (no bulk value listing). Removes the external link-out, so
console2 is the single KMS management surface. Typecheck clean.
Adds 4 credential-free live tests proving production posture: root serves
(200/dark #0a0a0a) + /base resolves; server proxies (superbase/bootnode/keys)
reject unauth with 401; proxy allow-lists reject off-list paths with 404 (no
tunnel); unknown route never 5xxs. 5/5 green vs console.hanzo.ai — real CI signal
without the prod superuser password.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Adds 4 credential-free live tests proving production posture: root serves
(200/dark #0a0a0a) + /base resolves; server proxies (superbase/bootnode/keys)
reject unauth with 401; proxy allow-lists reject off-list paths with 404 (no
tunnel); unknown route never 5xxs. 5/5 green vs console.hanzo.ai — real CI signal
without the prod superuser password.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Extract the taxonomy + per-brand scope into dependency-free src/lib/products/
brand-scope.ts (pure, brand-passed-in) so it's unit-testable without hostname
mocking or loading the React-heavy registry. registry re-exports it (no API
change). New registry-brand.test.ts PROVES: hanzo=all 12 categories; lux/zoo/
pars=ONLY Web3/Network/Security/Dev/Settings (web3/bootnode), hiding every
AI-cloud category; Networks(Web3) surfaces on lux/zoo. 12 tests green, 381 total,
typecheck + next build clean.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Extract the taxonomy + per-brand scope into dependency-free src/lib/products/
brand-scope.ts (pure, brand-passed-in) so it's unit-testable without hostname
mocking or loading the React-heavy registry. registry re-exports it (no API
change). New registry-brand.test.ts PROVES: hanzo=all 12 categories; lux/zoo/
pars=ONLY Web3/Network/Security/Dev/Settings (web3/bootnode), hiding every
AI-cloud category; Networks(Web3) surfaces on lux/zoo. 12 tests green, 381 total,
typecheck + next build clean.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
The core bootnode ('Web3 Backend in a Box') primitive, ported into console2 so
the lux/zoo web3 consoles manage real blockchain networks (chain/nodes/status/
RPC). Reads the live bootnode control plane via a new per-user /bootnode proxy
(mints the user's IAM bearer; least-privilege to the networks surface + launch/
rpc/scale), rendered with @hanzo/data's DataTable. Honest states on 401/404/503.
Retires the old bootnode-admin app — one console (hanzoai/console), brand-scoped.
typecheck + build + 352 tests green.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The core bootnode ('Web3 Backend in a Box') primitive, ported into console2 so
the lux/zoo web3 consoles manage real blockchain networks (chain/nodes/status/
RPC). Reads the live bootnode control plane via a new per-user /bootnode proxy
(mints the user's IAM bearer; least-privilege to the networks surface + launch/
rpc/scale), rendered with @hanzo/data's DataTable. Honest states on 401/404/503.
Retires the old bootnode-admin app — one console (hanzoai/console), brand-scoped.
typecheck + build + 352 tests green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Two customer-facing bugs found in a live real-tenant e2e audit of
console.hanzo.ai, both making the "backend-aware FE" partially broken.
BUG 1 — Overview usage/spend widget showed no spend.
The Overview called cloud `/v1/get-cloud-usages`, which returns 200 with
{"status":"error","msg":"usage ledger unavailable: datastore peer not
connected"} — the cloud usage-ledger's o11y datastore peer is down. Repoint
`UsageApi.overview()` at the REAL commerce ledger `/v1/billing/usage` (via the
existing per-tenant `/billing/*` proxy — the SAME source the Cost page and the
gateway debit against, X-Hanzo-Org scoped). New pure `usage-adapter.ts` rolls
the raw records up into the rich `CloudUsageOverview` the dashboard already
renders (totals, prior-period deltas, dense time series, top-N + Other
spend-by-model, paginated inference activity) — reusing the ONE canonical
aimetrics parse, so Overview and Cost agree to the cent. Overview UI unchanged.
Verified live: commerce returns 158 real records for hanzo/z; cloud ledger is
dead. `UsageRecord` gains additive premium/stream/status/requestId (from the
commerce metadata) for faithful activity rows.
BUG 2 — API Keys never listed a minted key (uncopyable/unrevocable, re-minted).
`POST /keys` mints a real working hk- key (User.AccessKey in IAM), but
`GET /keys` derived hasKey from the cloud `get-account` session claim, which
returns accessKey='' for a freshly-minted key → the page reverted to the empty
"Create" state on reload. Read the key AUTHORITATIVELY from IAM
`get-user?id=<owner>/<name>` (new `getUserKey` server helper) instead. Verified
live: IAM holds z's accessKey=hk-eeedb378-... while get-account returns ''. The
key now lists (prefix + last created/rotated date) and revoke works.
- No mocks/fixtures; honest states preserved. Coordinated admin/per-host/ingress
files untouched. tsc clean, 369 vitest pass (22 new adapter tests), next build green.
Two customer-facing bugs found in a live real-tenant e2e audit of
console.hanzo.ai, both making the "backend-aware FE" partially broken.
BUG 1 — Overview usage/spend widget showed no spend.
The Overview called cloud `/v1/get-cloud-usages`, which returns 200 with
{"status":"error","msg":"usage ledger unavailable: datastore peer not
connected"} — the cloud usage-ledger's o11y datastore peer is down. Repoint
`UsageApi.overview()` at the REAL commerce ledger `/v1/billing/usage` (via the
existing per-tenant `/billing/*` proxy — the SAME source the Cost page and the
gateway debit against, X-Hanzo-Org scoped). New pure `usage-adapter.ts` rolls
the raw records up into the rich `CloudUsageOverview` the dashboard already
renders (totals, prior-period deltas, dense time series, top-N + Other
spend-by-model, paginated inference activity) — reusing the ONE canonical
aimetrics parse, so Overview and Cost agree to the cent. Overview UI unchanged.
Verified live: commerce returns 158 real records for hanzo/z; cloud ledger is
dead. `UsageRecord` gains additive premium/stream/status/requestId (from the
commerce metadata) for faithful activity rows.
BUG 2 — API Keys never listed a minted key (uncopyable/unrevocable, re-minted).
`POST /keys` mints a real working hk- key (User.AccessKey in IAM), but
`GET /keys` derived hasKey from the cloud `get-account` session claim, which
returns accessKey='' for a freshly-minted key → the page reverted to the empty
"Create" state on reload. Read the key AUTHORITATIVELY from IAM
`get-user?id=<owner>/<name>` (new `getUserKey` server helper) instead. Verified
live: IAM holds z's accessKey=hk-eeedb378-... while get-account returns ''. The
key now lists (prefix + last created/rotated date) and revoke works.
- No mocks/fixtures; honest states preserved. Coordinated admin/per-host/ingress
files untouched. tsc clean, 369 vitest pass (22 new adapter tests), next build green.
console.hanzo.ai = full AI cloud; console.lux.cloud / console.zoo.cloud /
console.pars.* = web3/bootnode admin only (Web3 + Network + Security + Dev +
Settings — on-chain, networks/nodes/peering, keys/HSM/authz, dev keys, org).
ONE knob: BRAND_CATEGORIES in registry, filtered at the single catalog-consumption
point (visibleCatalog/catalogByCategory/visibleCatalogByCategory) via inBrand +
brandCategoryOrder. Settings already shows brand-resolved info (brand/name/IAM/
billing per host). Hanzo unchanged. typecheck + 345 tests green.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
console.hanzo.ai = full AI cloud; console.lux.cloud / console.zoo.cloud /
console.pars.* = web3/bootnode admin only (Web3 + Network + Security + Dev +
Settings — on-chain, networks/nodes/peering, keys/HSM/authz, dev keys, org).
ONE knob: BRAND_CATEGORIES in registry, filtered at the single catalog-consumption
point (visibleCatalog/catalogByCategory/visibleCatalogByCategory) via inBrand +
brandCategoryOrder. Settings already shows brand-resolved info (brand/name/IAM/
billing per host). Hanzo unchanged. typecheck + 345 tests green.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
On an admin console host (admin.hanzo.ai) resolve the OAuth client to the
admin-org app `admin-console` so IAM login resolves the global-admin identity
(owner=admin); every normal host keeps the brand cloud client (hanzo-cloud).
Isolated to src/config: `adminApp` per brand (ONE global admin-console app for
the reserved admin org), `isAdminHost()`, and a HOST-keyed cache (admin.hanzo.ai
and cloud.hanzo.ai are the same brand but must resolve to different clients — a
brand-keyed cache would collide). iamAppName + iamClientId travel together;
NEXT_PUBLIC_* overrides still win. Composes with the admin-mode UI (untouched).
+7 vitest (admin/normal host resolution, cache isolation, strict admin. prefix);
tsc --noEmit clean.
On an admin console host (admin.hanzo.ai) resolve the OAuth client to the
admin-org app `admin-console` so IAM login resolves the global-admin identity
(owner=admin); every normal host keeps the brand cloud client (hanzo-cloud).
Isolated to src/config: `adminApp` per brand (ONE global admin-console app for
the reserved admin org), `isAdminHost()`, and a HOST-keyed cache (admin.hanzo.ai
and cloud.hanzo.ai are the same brand but must resolve to different clients — a
brand-keyed cache would collide). iamAppName + iamClientId travel together;
NEXT_PUBLIC_* overrides still win. Composes with the admin-mode UI (untouched).
+7 vitest (admin/normal host resolution, cache isolation, strict admin. prefix);
tsc --noEmit clean.
The whole suite gated on HANZO_PASSWORD, so CI got zero signal without the prod
superuser secret. Split the credential-free sign-in render check into its own
describe so it always runs — asserts email/password + GitHub/Google + passkey.
Verified green against live console.hanzo.ai. Authenticated flows still gate on
HANZO_PASSWORD.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The whole suite gated on HANZO_PASSWORD, so CI got zero signal without the prod
superuser secret. Split the credential-free sign-in render check into its own
describe so it always runs — asserts email/password + GitHub/Google + passkey.
Verified green against live console.hanzo.ai. Authenticated flows still gate on
HANZO_PASSWORD.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Shell + information architecture (owns DashboardShell, nav, header, registry
category/sub-page contract, ⌘K, Team/Settings/Profile). No product content
modules touched (referenced by id).
1. Two-level sidebar nav (Linear-style). Level 1 = categorized product list;
clicking a product slides into its sub-nav (level 2) with a Back affordance;
the open product follows the route. CSS-transform slide (.hz-slide,
reduced-motion aware).
2. Uniform sub-page contract. Every product gets Overview · Settings · Status ·
Logs · Metrics plus its declared specifics (productSubpages, match-core).
A sub-page with no backend renders an honest ProductSubpageStub — never a
404, never fabricated.
3. ⌘K jumps to ANY level. searchDestinations indexes products + declared
specifics ("queues" → Compute › Tasks › Queues).
4. Category restructure. Deploy→Platform; new Training (Fine-tuning + ML
Pipelines) and Settings (Team/Settings/Profile); Compute gains
Kubernetes/Clusters/Tasks; Async category + Jobs entry KILLED (Tasks
replaces Jobs). Dev/Web3 retained (real products).
5. Sidebar chrome. H mark only (no wordmark), no in-sidebar collapse toggle
(moved to header), animated collapse (.hz-collapse, 264↔64).
6. Header cleanup. Removed user name + Sign out from the header; Sign out now in
the footer wallet under Top up; footer user row → Profile; kept org/project/
network(env) switchers + theme + help + notifications(bell→/alerts).
7. Team (org member mgmt: list/invite/role/remove + read-only Roles), org
Settings (General/Branding), Profile (Account/Security/API Keys). Member
mgmt runs over a NEW org-scoped /org/iam proxy so an ORG admin (not only a
global admin) manages their own org — tenant-isolated server-side, with the
body-owner cross-tenant write gap closed in a shared forwardIam (also
hardens /admin/iam). DRY IAM envelope client (iam-envelope).
Admin↔customer surface gating (systemic): admin-only products (Providers, IAM,
KMS, Secrets, Audit, Clusters, Kubernetes) + admin sub-pages (Models › Routing)
are hidden from a customer's nav/launcher/⌘K and render a graceful "Managed by
Hanzo" notice on direct access instead of a hostile 403. Signal = global-admin
(isGlobalAdminAccount, DRY with OrgGate). Customer surfaces (Models browse,
Playground, Chat, API keys, Cost, Team, Compute/data) fully work per-org.
Network×org×project scope was already first-class (client.ts stamps X-Org-Id +
X-IAM-Org-Id + X-Project-Id + X-Environment; ScopeSwitcher env picker) — kept
as-is.
Verify: tsc clean · vitest 308 (incl. new sub-page/routing/destinations/org-
policy tests) · next build green (/org/iam route compiled) · Playwright desktop
+ 390px mobile, both personas.
Shell + information architecture (owns DashboardShell, nav, header, registry
category/sub-page contract, ⌘K, Team/Settings/Profile). No product content
modules touched (referenced by id).
1. Two-level sidebar nav (Linear-style). Level 1 = categorized product list;
clicking a product slides into its sub-nav (level 2) with a Back affordance;
the open product follows the route. CSS-transform slide (.hz-slide,
reduced-motion aware).
2. Uniform sub-page contract. Every product gets Overview · Settings · Status ·
Logs · Metrics plus its declared specifics (productSubpages, match-core).
A sub-page with no backend renders an honest ProductSubpageStub — never a
404, never fabricated.
3. ⌘K jumps to ANY level. searchDestinations indexes products + declared
specifics ("queues" → Compute › Tasks › Queues).
4. Category restructure. Deploy→Platform; new Training (Fine-tuning + ML
Pipelines) and Settings (Team/Settings/Profile); Compute gains
Kubernetes/Clusters/Tasks; Async category + Jobs entry KILLED (Tasks
replaces Jobs). Dev/Web3 retained (real products).
5. Sidebar chrome. H mark only (no wordmark), no in-sidebar collapse toggle
(moved to header), animated collapse (.hz-collapse, 264↔64).
6. Header cleanup. Removed user name + Sign out from the header; Sign out now in
the footer wallet under Top up; footer user row → Profile; kept org/project/
network(env) switchers + theme + help + notifications(bell→/alerts).
7. Team (org member mgmt: list/invite/role/remove + read-only Roles), org
Settings (General/Branding), Profile (Account/Security/API Keys). Member
mgmt runs over a NEW org-scoped /org/iam proxy so an ORG admin (not only a
global admin) manages their own org — tenant-isolated server-side, with the
body-owner cross-tenant write gap closed in a shared forwardIam (also
hardens /admin/iam). DRY IAM envelope client (iam-envelope).
Admin↔customer surface gating (systemic): admin-only products (Providers, IAM,
KMS, Secrets, Audit, Clusters, Kubernetes) + admin sub-pages (Models › Routing)
are hidden from a customer's nav/launcher/⌘K and render a graceful "Managed by
Hanzo" notice on direct access instead of a hostile 403. Signal = global-admin
(isGlobalAdminAccount, DRY with OrgGate). Customer surfaces (Models browse,
Playground, Chat, API keys, Cost, Team, Compute/data) fully work per-org.
Network×org×project scope was already first-class (client.ts stamps X-Org-Id +
X-IAM-Org-Id + X-Project-Id + X-Environment; ScopeSwitcher env picker) — kept
as-is.
Verify: tsc clean · vitest 308 (incl. new sub-page/routing/destinations/org-
policy tests) · next build green (/org/iam route compiled) · Playwright desktop
+ 390px mobile, both personas.
Four resource consoles wired to REAL backends with honest states (never fabricated).
- Kubernetes (Compute): real DOKS clusters via PlatformApi (/paas → platform);
stat cards + cluster table with provisioned CPU/RAM DERIVED from node-pool slugs
(honest "—" for GPU/unknown); Import (honest) + Create → real provisionCluster.
- Containers (Compute): apps-inventory Workloads + Pods/Images/Namespaces/Events as
:tab sub-routes over /paas (tolerant shapes, honest states); cluster-detail sidebar.
- Training (AI/Fine-tuning): live mlsvc /v1/train/{jobs,experiments} + /v1/ml/models
via generalized /training proxy; stat cards, jobs table, training-loss chart,
checkpoints, models, configs; New-job panel (base model from real aicatalog) →
POST /v1/train/jobs (402 ResourceMeter surfaced honestly); Save-as-config.
- Tasks (Compute): Temporal console over hanzoai/tasks tasksd via NEW /tasksd
minted-Bearer proxy; Workflows/Schedules/Queues/Workers/Activities :tab sub-routes;
stat cards; workflow detail panel + step graph + 8 sub-tabs; engine-health /
throughput / queue-util / recent rail. Public tasks TLS not live yet → honest
states until the in-cluster engine is reachable.
Registry: removed the Async category + the Jobs entry; Tasks & Kubernetes → Compute.
Shared: promoted console primitives to ui/Metric.tsx (DRY; gpus/charts re-exports);
nodes.ts capacity derivation (+12 unit tests). tsc 0 / vitest 304 / next build green.
Four resource consoles wired to REAL backends with honest states (never fabricated).
- Kubernetes (Compute): real DOKS clusters via PlatformApi (/paas → platform);
stat cards + cluster table with provisioned CPU/RAM DERIVED from node-pool slugs
(honest "—" for GPU/unknown); Import (honest) + Create → real provisionCluster.
- Containers (Compute): apps-inventory Workloads + Pods/Images/Namespaces/Events as
:tab sub-routes over /paas (tolerant shapes, honest states); cluster-detail sidebar.
- Training (AI/Fine-tuning): live mlsvc /v1/train/{jobs,experiments} + /v1/ml/models
via generalized /training proxy; stat cards, jobs table, training-loss chart,
checkpoints, models, configs; New-job panel (base model from real aicatalog) →
POST /v1/train/jobs (402 ResourceMeter surfaced honestly); Save-as-config.
- Tasks (Compute): Temporal console over hanzoai/tasks tasksd via NEW /tasksd
minted-Bearer proxy; Workflows/Schedules/Queues/Workers/Activities :tab sub-routes;
stat cards; workflow detail panel + step graph + 8 sub-tabs; engine-health /
throughput / queue-util / recent rail. Public tasks TLS not live yet → honest
states until the in-cluster engine is reachable.
Registry: removed the Async category + the Jobs entry; Tasks & Kubernetes → Compute.
Shared: promoted console primitives to ui/Metric.tsx (DRY; gpus/charts re-exports);
nodes.ts capacity derivation (+12 unit tests). tsc 0 / vitest 304 / next build green.
Fixes Dave's live-Playground complaints on console.hanzo.ai/playground.
- ModelPicker: rebuilt as a keyboard-navigable provider→model CASCADE (Zen-first
provider rail + model pane with real context badge + $/Mtok + live dot;
searchable; free-text fallback). New pure providers.ts (Zen-first grouping) +tests.
- ResponsePanel: render the completion as real markdown (new pure markdown.ts
tokenizer + MarkdownView: fenced code blocks w/ copy, inline code, bold/italic,
lists, headings, links) instead of plaintext; add a clear Stop control in the
panel header during streaming (AbortController was already wired end-to-end).
- history.ts: namespace per user (owner/name), auto-persist every completed run
so History auto-populates; one account never sees another's runs (+tests).
- ModelSettings: consolidated into a collapsible side-pane ATTACHED to the prompt
builder (desktop) and a bottom sheet on mobile (new SettingsSheet, reusing the
shell Dialog drawer pattern); shrink the oversized slider thumb + thin the track.
- ChatPlayground/Composer: responsive 3-zone layout stacks cleanly at ~390px with
no horizontal scroll; a settings toggle opens the desktop pane / mobile sheet.
Verified: tsc --noEmit clean, vitest 311/311, next build green; Playwright desktop
+ 390px (cascade, keyboard nav, stop, markdown, mobile stack, settings sheet).
Wallet "Top up" deliberately NOT rerouted to pay.hanzo.ai: it is ALSO broken
(GET /v1/commerce/tenant -> 404 "unknown tenant", so the Square Web Payments SDK
never initializes). Breakage not moved; root cause reported for a backend fix.
Fixes Dave's live-Playground complaints on console.hanzo.ai/playground.
- ModelPicker: rebuilt as a keyboard-navigable provider→model CASCADE (Zen-first
provider rail + model pane with real context badge + $/Mtok + live dot;
searchable; free-text fallback). New pure providers.ts (Zen-first grouping) +tests.
- ResponsePanel: render the completion as real markdown (new pure markdown.ts
tokenizer + MarkdownView: fenced code blocks w/ copy, inline code, bold/italic,
lists, headings, links) instead of plaintext; add a clear Stop control in the
panel header during streaming (AbortController was already wired end-to-end).
- history.ts: namespace per user (owner/name), auto-persist every completed run
so History auto-populates; one account never sees another's runs (+tests).
- ModelSettings: consolidated into a collapsible side-pane ATTACHED to the prompt
builder (desktop) and a bottom sheet on mobile (new SettingsSheet, reusing the
shell Dialog drawer pattern); shrink the oversized slider thumb + thin the track.
- ChatPlayground/Composer: responsive 3-zone layout stacks cleanly at ~390px with
no horizontal scroll; a settings toggle opens the desktop pane / mobile sheet.
Verified: tsc --noEmit clean, vitest 311/311, next build green; Playwright desktop
+ 390px (cascade, keyboard nav, stop, markdown, mobile stack, settings sheet).
Wallet "Top up" deliberately NOT rerouted to pay.hanzo.ai: it is ALSO broken
(GET /v1/commerce/tenant -> 404 "unknown tenant", so the Square Web Payments SDK
never initializes). Breakage not moved; root cause reported for a backend fix.
* feat(console2): native control planes (zero external link-outs) + Hanzo Functions dashboard
Three deliverables, one PR, all over the one /v1 surface.
1) No external link-outs (priority). The catalog's `external` kind is removed:
CatalogEntry is module-only, ProductStatus is 'enabled' | 'soon'. The 14
products that used to open another domain (Gateway, DNS, CDN, MPC, CLI, SDKs,
API, IDE, Desktop, Registry, Metrics, Crawl, Studio, Console) are now native
in-console routes rendering ONE shared NativeOverview (overviewFor(id) +
overviewRoutes(id), the DRY twin of soonRoutes): header + summary, a REAL
health band (probes PlatformApi.apps() with honest not-deployed/not-reporting
states), key-fact cards, native-route actions, and INLINE docs. Content is a
pure OverviewSpec per product (overview/spec.ts + resolve.ts, with a
catalog-derived defaultSpec fallback). The external branches in open.ts,
DashboardShell, AppLauncher, CommandPalette, ProductInterstitial, and
OverviewModule are removed.
2) Hanzo Functions dashboard. FunctionsModule rebuilt into a tabbed product
(Overview · Functions · Deployments · Triggers · Secrets · Settings) over the
rich lib/api/functions.ts (GET /v1/functions*). Branded "Hanzo Functions" with
the honest Fission engine badge. Overview: 6 KPI cards derived from real rows
(deriveOverview, honest "—"), real-series sparklines + trendPct deltas, an
"Invocations over time" LineChart with 1H/6H/24H/7D/30D toggles, an "Invocation
status" Donut, and the shared FunctionsBrowser (table + DetailRail). Secrets is
names-only. Reuses functions/{FunctionsTable,DetailRail,parts}.tsx unchanged.
3) Overview "Explore products" drops the enablement gate: no more
Enabled/External/Soon badge; every product is open-for-all with Open (native) +
a "Learn more" affordance to the native /discover/:id interstitial.
Idiom: strictly @hanzo/gui v5 shorthands. New tests: overview/resolve.test.ts.
npm run typecheck clean (0 errors); npm test 298/298 (31 files); every route
compiles + 200s on the dev server.
Drive-by: remove the bogus tracked node_modules self-symlink blob that broke
npm install/vitest (.gitignore already ignores node_modules/).
* docs(console2): fix overviewFor comment reference
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
* feat(console2): native control planes (zero external link-outs) + Hanzo Functions dashboard
Three deliverables, one PR, all over the one /v1 surface.
1) No external link-outs (priority). The catalog's `external` kind is removed:
CatalogEntry is module-only, ProductStatus is 'enabled' | 'soon'. The 14
products that used to open another domain (Gateway, DNS, CDN, MPC, CLI, SDKs,
API, IDE, Desktop, Registry, Metrics, Crawl, Studio, Console) are now native
in-console routes rendering ONE shared NativeOverview (overviewFor(id) +
overviewRoutes(id), the DRY twin of soonRoutes): header + summary, a REAL
health band (probes PlatformApi.apps() with honest not-deployed/not-reporting
states), key-fact cards, native-route actions, and INLINE docs. Content is a
pure OverviewSpec per product (overview/spec.ts + resolve.ts, with a
catalog-derived defaultSpec fallback). The external branches in open.ts,
DashboardShell, AppLauncher, CommandPalette, ProductInterstitial, and
OverviewModule are removed.
2) Hanzo Functions dashboard. FunctionsModule rebuilt into a tabbed product
(Overview · Functions · Deployments · Triggers · Secrets · Settings) over the
rich lib/api/functions.ts (GET /v1/functions*). Branded "Hanzo Functions" with
the honest Fission engine badge. Overview: 6 KPI cards derived from real rows
(deriveOverview, honest "—"), real-series sparklines + trendPct deltas, an
"Invocations over time" LineChart with 1H/6H/24H/7D/30D toggles, an "Invocation
status" Donut, and the shared FunctionsBrowser (table + DetailRail). Secrets is
names-only. Reuses functions/{FunctionsTable,DetailRail,parts}.tsx unchanged.
3) Overview "Explore products" drops the enablement gate: no more
Enabled/External/Soon badge; every product is open-for-all with Open (native) +
a "Learn more" affordance to the native /discover/:id interstitial.
Idiom: strictly @hanzo/gui v5 shorthands. New tests: overview/resolve.test.ts.
npm run typecheck clean (0 errors); npm test 298/298 (31 files); every route
compiles + 200s on the dev server.
Drive-by: remove the bogus tracked node_modules self-symlink blob that broke
npm install/vitest (.gitignore already ignores node_modules/).
* docs(console2): fix overviewFor comment reference
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
The arcd runner can't pull ghcr.io/hanzoai/nodejs:24-alpine (403) — broke every
build since v0.7.32. Use the public ECR Docker-library mirror (no auth, no rate
limit), the v0.7.9 pattern; align the workflow pre-pull to 24-alpine.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The arcd runner can't pull ghcr.io/hanzoai/nodejs:24-alpine (403) — broke every
build since v0.7.32. Use the public ECR Docker-library mirror (no auth, no rate
limit), the v0.7.9 pattern; align the workflow pre-pull to 24-alpine.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Wire published @hanzo/data@1.1.0 (peer @hanzo/gui 7.3.0) into the Base UI
as a composable, honest collection viewer.
- next.config.mjs: transpile @hanzo/data (ships TSX source, like @hanzo/gui)
- src/lib/base-data/fields.ts: pure baseCollectionToFields() mapping a Base
collection schema -> @hanzo/data FieldDefinition[]. Covers text/number/bool/
email/url/editor/date/autodate/select+multiSelect/json/relation/file/geoPoint;
skips hidden+system fields (keeps id); handles modern `fields` and legacy
`schema`/nested `options`.
- src/lib/base-data/api.ts: tiny BaseDataApi over a Base /v1 (listCollections,
listRecords) -- raw REST + optional bearer, shares the app's typed ApiError.
- src/components/base-data/CollectionTable.tsx: client component; schema ->
fields -> records -> @hanzo/data DataTable with honest
loading/empty/error/not-found states (no fabricated rows).
- src/lib/base-data/fields.test.ts: 10 vitest cases for the mapping.
Verify: `npm run typecheck` clean; `npm test` 58/58.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Wire published @hanzo/data@1.1.0 (peer @hanzo/gui 7.3.0) into the Base UI
as a composable, honest collection viewer.
- next.config.mjs: transpile @hanzo/data (ships TSX source, like @hanzo/gui)
- src/lib/base-data/fields.ts: pure baseCollectionToFields() mapping a Base
collection schema -> @hanzo/data FieldDefinition[]. Covers text/number/bool/
email/url/editor/date/autodate/select+multiSelect/json/relation/file/geoPoint;
skips hidden+system fields (keeps id); handles modern `fields` and legacy
`schema`/nested `options`.
- src/lib/base-data/api.ts: tiny BaseDataApi over a Base /v1 (listCollections,
listRecords) -- raw REST + optional bearer, shares the app's typed ApiError.
- src/components/base-data/CollectionTable.tsx: client component; schema ->
fields -> records -> @hanzo/data DataTable with honest
loading/empty/error/not-found states (no fabricated rows).
- src/lib/base-data/fields.test.ts: 10 vitest cases for the mapping.
Verify: `npm run typecheck` clean; `npm test` 58/58.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Base product module rendering the shared @hanzo/dashboard screens (published
on npm) via a per-user /superbase proxy (mints the user's IAM bearer); catalog
entry + page /base · /base/new. Plus the Base look: black #0a0a0a surface
aligning to the zinc-on-black identity. Consumes @hanzo/dashboard@0.2.0.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Base product module rendering the shared @hanzo/dashboard screens (published
on npm) via a per-user /superbase proxy (mints the user's IAM bearer); catalog
entry + page /base · /base/new. Plus the Base look: black #0a0a0a surface
aligning to the zinc-on-black identity. Consumes @hanzo/dashboard@0.2.0.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Polish the Chat UI without touching any data wiring — Chat still calls the
real /v1/chat/completions through the keyless /ai proxy, and every state/API
call, prop, and honest empty/down state is preserved.
- Bubbles: assistant turns read as open text with a sparkle medallion +
name + timestamp and comfortable line-height (dropped the heavy bordered
card); the user turn is a refined right-aligned accent bubble. Both render
light markdown — fenced code blocks (monospace, tinted card, optional lang),
inline code chips, and bold.
- Markdown: new dependency-free renderer (chat/markdown.tsx) reusing the
existing `fontFamily: 'monospace'` idiom — no heavy remark/rehype tree added
(console2 ships no markdown lib).
- Welcome/empty state: sparkle avatar + "How can I help?" + 3–4 clickable
suggested-prompt chips that fill the composer on click.
- Composer: one rounded, elevated input with a code-insert ({}) and a circular
send affordance (hover/press states) over a subtle muted hint row.
- ChatView: read-only history thread matches the new bubble look + markdown.
- ChatListView: name cell reads as a link (weight + hover); table unchanged.
All Tamagui shorthands (bg/maxW/rounded/items/justify/self/p/px/py/gap) per
onlyShorthandStyleProps. tsc --noEmit clean; 245 vitest tests pass.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Polish the Chat UI without touching any data wiring — Chat still calls the
real /v1/chat/completions through the keyless /ai proxy, and every state/API
call, prop, and honest empty/down state is preserved.
- Bubbles: assistant turns read as open text with a sparkle medallion +
name + timestamp and comfortable line-height (dropped the heavy bordered
card); the user turn is a refined right-aligned accent bubble. Both render
light markdown — fenced code blocks (monospace, tinted card, optional lang),
inline code chips, and bold.
- Markdown: new dependency-free renderer (chat/markdown.tsx) reusing the
existing `fontFamily: 'monospace'` idiom — no heavy remark/rehype tree added
(console2 ships no markdown lib).
- Welcome/empty state: sparkle avatar + "How can I help?" + 3–4 clickable
suggested-prompt chips that fill the composer on click.
- Composer: one rounded, elevated input with a code-insert ({}) and a circular
send affordance (hover/press states) over a subtle muted hint row.
- ChatView: read-only history thread matches the new bubble look + markdown.
- ChatListView: name cell reads as a link (weight + hover); table unchanged.
All Tamagui shorthands (bg/maxW/rounded/items/justify/self/p/px/py/gap) per
onlyShorthandStyleProps. tsc --noEmit clean; 245 vitest tests pass.
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Redesign the Playground from the multi-model compare board into the polished
3-zone surface in the mockup, reusing the existing AI binding (runner/stream/
PlaygroundApi) — nothing about model output, tokens or cost is fabricated.
Layout (per mockup):
- Header "Playground" + subtitle + Save prompt / </> code / Share actions.
- Tabs: Chat · Completions · Embeddings · Audio · Vision.
- Composer (left): model chip with a REAL "context" badge + searchable picker
over the live catalog (aicatalog.fetchCatalog, 375 models), System prompt +
user/assistant turns with char counts, and a footer of Add message / Upload
(image→vision) / {} Variables / Run (⌘↵ + caret). Completions collapses to a
single Prompt card.
- Examples (labelled starters w/ model chips) + History (real local prior runs,
honest-empty) beneath the composer.
- Right rail: Response/Logs panel (real completion, USAGE tokens + COST from the
model's real $/Mtok, "—" when absent) and Model settings (Temperature 0.7,
Top P 0.9, Max tokens, Stop, Advanced: freq/presence penalty + seed).
Real behaviors, no backend: Save prompt (local library → Examples), Code (real
cURL/JSON request preview), Share (encode composer into ?p= link, restore on
load), {{variables}} substitution, ⌘↵ to run.
Wiring: Temperature/top-p/max-tokens/stop + advanced penalties/seed flow through
paramsOf into the request (sent only when set). Removes the compare-only files
(ComparePlayground/CompareColumn/AddModel/useCompare/SettingsControls).
Tests: +37 unit tests (params/variables/share/prompts/request-preview/compose/
relative); 282 total green. tsc clean, next build green.
Redesign the Playground from the multi-model compare board into the polished
3-zone surface in the mockup, reusing the existing AI binding (runner/stream/
PlaygroundApi) — nothing about model output, tokens or cost is fabricated.
Layout (per mockup):
- Header "Playground" + subtitle + Save prompt / </> code / Share actions.
- Tabs: Chat · Completions · Embeddings · Audio · Vision.
- Composer (left): model chip with a REAL "context" badge + searchable picker
over the live catalog (aicatalog.fetchCatalog, 375 models), System prompt +
user/assistant turns with char counts, and a footer of Add message / Upload
(image→vision) / {} Variables / Run (⌘↵ + caret). Completions collapses to a
single Prompt card.
- Examples (labelled starters w/ model chips) + History (real local prior runs,
honest-empty) beneath the composer.
- Right rail: Response/Logs panel (real completion, USAGE tokens + COST from the
model's real $/Mtok, "—" when absent) and Model settings (Temperature 0.7,
Top P 0.9, Max tokens, Stop, Advanced: freq/presence penalty + seed).
Real behaviors, no backend: Save prompt (local library → Examples), Code (real
cURL/JSON request preview), Share (encode composer into ?p= link, restore on
load), {{variables}} substitution, ⌘↵ to run.
Wiring: Temperature/top-p/max-tokens/stop + advanced penalties/seed flow through
paramsOf into the request (sent only when set). Removes the compare-only files
(ComparePlayground/CompareColumn/AddModel/useCompare/SettingsControls).
Tests: +37 unit tests (params/variables/share/prompts/request-preview/compose/
relative); 282 total green. tsc clean, next build green.
The OrgSwitcher collapsed to a STATIC non-clickable label whenever the admin-gated
org list returned empty (every tenant: /admin/iam is global-admin-only → 403), and
there was NO create-org affordance. Now: the trigger is ALWAYS an interactive
Popover (current org always shown + filter + switch), with a 'Create organization'
flow that posts to /onboard and scope-switches into the new org. /onboard relaxed:
an existing-org user can create an ADDITIONAL org (created WITHOUT moving them — a
move would strip a global admin's status + orphan their current org); zero-org
first-run still creates+joins. v0.7.31
The OrgSwitcher collapsed to a STATIC non-clickable label whenever the admin-gated
org list returned empty (every tenant: /admin/iam is global-admin-only → 403), and
there was NO create-org affordance. Now: the trigger is ALWAYS an interactive
Popover (current org always shown + filter + switch), with a 'Create organization'
flow that posts to /onboard and scope-switches into the new org. /onboard relaxed:
an existing-org user can create an ADDITIONAL org (created WITHOUT moving them — a
move would strip a global admin's status + orphan their current org); zero-org
first-run still creates+joins. v0.7.31
Decomplect the shared resourceModule factory (backs all managed-data kinds)
into ONE spec-driven console, upgrading every data page at once:
- resource/logic.ts pure per-kind ResourceSpec + fleet/status/endpoint/
snippet helpers (RESOURCE_SPECS, 16 unit tests). The list API carries
lifecycle facts only, so usage metrics are honest "absent" (null -> "—"),
never fabricated.
- resource/parts.tsx ResourceStat (honest "—" + "Awaiting metering"),
StatusDonutCard, TabBar, SnippetBlock, CopyField, SectionCard.
- resource/ResourceListView.tsx the polished home console: REAL fleet stat
row + tabs (Overview / <instances> / Access / Metrics / [tool] / Settings)
+ right rail (status donut, quick actions, quick start) + the real create
flow (POST /v1/<kind>, password shown once).
- resource/ResourceInstanceView.tsx tabbed single-instance console
(Overview / Access / Settings) with a real confirmed delete.
- ResourceModule.tsx thin router; same resourceModule/resourceRoutes
exports -> zero registry churn, all 5 graded kinds (+docdb/search) tuned.
Honest by construction: status breakdown from real lifecycle, create/delete
real, the data-plane tool tab (Query/Browser/Explore) is an explicit
"coming soon" with the real connect snippet — never a fake success.
Gates: tsc --noEmit clean, vitest 245 pass, next build 14/14. Bump 0.7.30.
Decomplect the shared resourceModule factory (backs all managed-data kinds)
into ONE spec-driven console, upgrading every data page at once:
- resource/logic.ts pure per-kind ResourceSpec + fleet/status/endpoint/
snippet helpers (RESOURCE_SPECS, 16 unit tests). The list API carries
lifecycle facts only, so usage metrics are honest "absent" (null -> "—"),
never fabricated.
- resource/parts.tsx ResourceStat (honest "—" + "Awaiting metering"),
StatusDonutCard, TabBar, SnippetBlock, CopyField, SectionCard.
- resource/ResourceListView.tsx the polished home console: REAL fleet stat
row + tabs (Overview / <instances> / Access / Metrics / [tool] / Settings)
+ right rail (status donut, quick actions, quick start) + the real create
flow (POST /v1/<kind>, password shown once).
- resource/ResourceInstanceView.tsx tabbed single-instance console
(Overview / Access / Settings) with a real confirmed delete.
- ResourceModule.tsx thin router; same resourceModule/resourceRoutes
exports -> zero registry churn, all 5 graded kinds (+docdb/search) tuned.
Honest by construction: status breakdown from real lifecycle, create/delete
real, the data-plane tool tab (Query/Browser/Explore) is an explicit
"coming soon" with the real connect snippet — never a fake success.
Gates: tsc --noEmit clean, vitest 245 pass, next build 14/14. Bump 0.7.30.
One spine for the Models, Providers, and (later) hanzo.ai / @hanzo/dev / desktop
surfaces, all read through the authenticated /ai proxy. Real data, honest states.
aicatalog (the spine):
- Joins the TWO real catalog record shapes — first-party Zen (`context`+`name`)
and third-party (`contextWindow`+`id` like openai/gpt-5). Fixes context showing
"—" on 339/375 models and cross-references availability by the stable id.
- Adds priceBucket/matchesQuery/modelTypes/CONTEXT_BUCKETS filters, the provider
`verified` flag, modelDisplayName (strips "OpenAI: " row prefixes), and
fetchPlans() reading the real /v1/plans subscription tiers (rpm/tpm/quota),
honest-empty on 401/404.
Components (self-contained, prop-driven, liftable to @hanzo/ui):
- ProviderLogo — monochrome avatar resolved by provider name: first-party Sparkles
mark, curated known-provider glyphs, initials chip otherwise. No external URLs.
- SelectMenu — reusable Popover dropdown for the Providers filter row.
Models page: ProviderLogo in rows + provider column, search box, collapsible
type/provider/pricing filters, stacked in/out pricing, real context via the join,
and subscription-plan badges in the detail (model tier -> /v1/plans limits).
Providers page: Explore / My Providers / Custom Models / BYO Weights tabs (the
latter three honest, pointing at the real add/deploy flow), search + type/context/
pricing/verified/sort row, ProviderLogo + Verified badge on cards and detail.
/ai proxy: allow v1/plans through the authenticated proxy (least-privilege add).
Overview: already at parity on the real usage ledger — verified, not rebuilt.
Gates: tsc --noEmit clean, 230/230 vitest (incl. 12 new aicatalog tests),
next build green (14/14). Bump 0.7.28 -> 0.7.29.
One spine for the Models, Providers, and (later) hanzo.ai / @hanzo/dev / desktop
surfaces, all read through the authenticated /ai proxy. Real data, honest states.
aicatalog (the spine):
- Joins the TWO real catalog record shapes — first-party Zen (`context`+`name`)
and third-party (`contextWindow`+`id` like openai/gpt-5). Fixes context showing
"—" on 339/375 models and cross-references availability by the stable id.
- Adds priceBucket/matchesQuery/modelTypes/CONTEXT_BUCKETS filters, the provider
`verified` flag, modelDisplayName (strips "OpenAI: " row prefixes), and
fetchPlans() reading the real /v1/plans subscription tiers (rpm/tpm/quota),
honest-empty on 401/404.
Components (self-contained, prop-driven, liftable to @hanzo/ui):
- ProviderLogo — monochrome avatar resolved by provider name: first-party Sparkles
mark, curated known-provider glyphs, initials chip otherwise. No external URLs.
- SelectMenu — reusable Popover dropdown for the Providers filter row.
Models page: ProviderLogo in rows + provider column, search box, collapsible
type/provider/pricing filters, stacked in/out pricing, real context via the join,
and subscription-plan badges in the detail (model tier -> /v1/plans limits).
Providers page: Explore / My Providers / Custom Models / BYO Weights tabs (the
latter three honest, pointing at the real add/deploy flow), search + type/context/
pricing/verified/sort row, ProviderLogo + Verified badge on cards and detail.
/ai proxy: allow v1/plans through the authenticated proxy (least-privilege add).
Overview: already at parity on the real usage ledger — verified, not rebuilt.
Gates: tsc --noEmit clean, 230/230 vitest (incl. 12 new aicatalog tests),
next build green (14/14). Bump 0.7.28 -> 0.7.29.
Re-pin off public.ecr.aws (rate-limited builds + violates ghcr-only). nodejs is the
Node.js runtime mirror (hanzoai/node is the blockchain node). COPY-before-install
(the real Kaniko --single-snapshot fix) is preserved.
Re-pin off public.ecr.aws (rate-limited builds + violates ghcr-only). nodejs is the
Node.js runtime mirror (hanzoai/node is the blockchain node). COPY-before-install
(the real Kaniko --single-snapshot fix) is preserved.
- default SSR/build host -> cloud.hanzo.ai (was console.hanzo.ai); brand still
resolves by hostname suffix, so console.hanzo.ai/console2.hanzo.ai (which now
301 to cloud.hanzo.ai at the gateway) still map to brand hanzo.
- cloudUrl() stays SAME-ORIGIN: the SPA calls cloud.hanzo.ai/v1, and the gateway
routes that /v1 to the cloud package (global IAM-JWT + rate-limit) — so
"everything goes through the gateway" holds with the cookie first-party (no CORS).
- console product + experiments external links -> cloud.hanzo.ai.
- default SSR/build host -> cloud.hanzo.ai (was console.hanzo.ai); brand still
resolves by hostname suffix, so console.hanzo.ai/console2.hanzo.ai (which now
301 to cloud.hanzo.ai at the gateway) still map to brand hanzo.
- cloudUrl() stays SAME-ORIGIN: the SPA calls cloud.hanzo.ai/v1, and the gateway
routes that /v1 to the cloud package (global IAM-JWT + rate-limit) — so
"everything goes through the gateway" holds with the cookie first-party (no CORS).
- console product + experiments external links -> cloud.hanzo.ai.
The v0.7.26/27/28 image builds 403'd: today's base-image thrashing pointed the
Dockerfile at ghcr.io/hanzoai/nodejs:24-alpine, which is PRIVATE — the host
builder's ghcr login is scoped to console2's own package and can't read the
separate nodejs package (403 Forbidden on the base pull).
build-image.yml still pre-pulls + caches public.ecr.aws/docker/library/node:
22-alpine (its comment even says the Dockerfile uses it). Re-align the Dockerfile
to that public base: no auth, no 403, and the warm ARC runner serves it straight
from the cache the pre-pull step populates. node 22 is the version v0.7.25
shipped on. The Kaniko COPY-before-install + retry-hardened npm install fixes are
untouched.
The v0.7.26/27/28 image builds 403'd: today's base-image thrashing pointed the
Dockerfile at ghcr.io/hanzoai/nodejs:24-alpine, which is PRIVATE — the host
builder's ghcr login is scoped to console2's own package and can't read the
separate nodejs package (403 Forbidden on the base pull).
build-image.yml still pre-pulls + caches public.ecr.aws/docker/library/node:
22-alpine (its comment even says the Dockerfile uses it). Re-align the Dockerfile
to that public base: no auth, no 403, and the warm ARC runner serves it straight
from the cache the pre-pull step populates. node 22 is the version v0.7.25
shipped on. The Kaniko COPY-before-install + retry-hardened npm install fixes are
untouched.
Upgrades the Zero Trust surface from five plain tabbed tables into a cloud-console
landing page (the Image #11 operational style), wired to the REAL /v1/zt/* mesh:
- Overview: KPI cards (routers/services/identities/sessions/policies — real
counts or honest em-dash), a router→service→identity topology strip (only
nodes that came back; status-coloured), and a post-quantum POSTURE card tying
the data plane together: Object Storage (S3) ⇄ Zero Trust over Hanzo zap
(ML-KEM-768 key exchange · ML-DSA-65 signatures). PQ-session % shows only when
the backend reports a real cipher — never guessed.
- Honest by construction: each of the 5 sections loads independently; when the
zt backend isn't mounted on this host every section degrades to ONE
BackendStateCard while the (true) PQ posture still shows. No fabricated rows,
trends, or telemetry.
- DRY: the five detail tabs reuse the SAME zeroTrustSurfaces + ForwardSurface
(now exported from ConsoleFeatureModule) — one zero-trust surface, not two.
ZeroTrustModule moved out of the generic table shell into its own rich module
(mirrors Embeddings/Overview); registry repointed.
- Pure logic in zt/logic.ts (counts, topology, posture) with vitest coverage.
tsc --noEmit (strict) clean. v0.7.26.
Upgrades the Zero Trust surface from five plain tabbed tables into a cloud-console
landing page (the Image #11 operational style), wired to the REAL /v1/zt/* mesh:
- Overview: KPI cards (routers/services/identities/sessions/policies — real
counts or honest em-dash), a router→service→identity topology strip (only
nodes that came back; status-coloured), and a post-quantum POSTURE card tying
the data plane together: Object Storage (S3) ⇄ Zero Trust over Hanzo zap
(ML-KEM-768 key exchange · ML-DSA-65 signatures). PQ-session % shows only when
the backend reports a real cipher — never guessed.
- Honest by construction: each of the 5 sections loads independently; when the
zt backend isn't mounted on this host every section degrades to ONE
BackendStateCard while the (true) PQ posture still shows. No fabricated rows,
trends, or telemetry.
- DRY: the five detail tabs reuse the SAME zeroTrustSurfaces + ForwardSurface
(now exported from ConsoleFeatureModule) — one zero-trust surface, not two.
ZeroTrustModule moved out of the generic table shell into its own rich module
(mirrors Embeddings/Overview); registry repointed.
- Pure logic in zt/logic.ts (counts, topology, posture) with vitest coverage.
tsc --noEmit (strict) clean. v0.7.26.
ROOT CAUSE (proven in the build log): the install's own 'test -f next/dist/bin/next'
PASSED, then 'COPY . .' ran, then the build RUN couldn't find next. Under Kaniko
--single-snapshot, a COPY that follows RUN npm install in the same stage drops the
RUN's freshly-created node_modules. The old multi-stage Dockerfile avoided this (no
COPY after install); my single-stage reorder reintroduced it. Fix: COPY all source
FIRST, then install, then build — node_modules is created by the last RUNs so nothing
clobbers it. This (not the base registry or the .bin symlink) was the real blocker.
ROOT CAUSE (proven in the build log): the install's own 'test -f next/dist/bin/next'
PASSED, then 'COPY . .' ran, then the build RUN couldn't find next. Under Kaniko
--single-snapshot, a COPY that follows RUN npm install in the same stage drops the
RUN's freshly-created node_modules. The old multi-stage Dockerfile avoided this (no
COPY after install); my single-stage reorder reintroduced it. Fix: COPY all source
FIRST, then install, then build — node_modules is created by the last RUNs so nothing
clobbers it. This (not the base registry or the .bin symlink) was the real blocker.
The full @hanzo/gui dep tree intermittently installs ~80 packages short (incl next)
— npm reports success but skips them, surfacing later as 'next not found'. Now:
retry-hardened fetch, an explicit 'npm install next' repair if its bin is missing,
and a hard 'test -f' assert so a partial install fails loudly at the install step
(with a clear cause) rather than at build.
The full @hanzo/gui dep tree intermittently installs ~80 packages short (incl next)
— npm reports success but skips them, surfacing later as 'next not found'. Now:
retry-hardened fetch, an explicit 'npm install next' repair if its bin is missing,
and a hard 'test -f' assert so a partial install fails loudly at the install step
(with a clear cause) rather than at build.
Two fixes for the broken builds:
1. Base image: use ghcr.io/hanzoai/nodejs:24-alpine (our mirror of node:24-alpine)
per the ghcr-only policy. (public.ecr.aws rate-limited; mirror.gcr.io was a
stopgap. hanzoai/node is the blockchain node — nodejs is the Node.js runtime.)
Bumped 22→24.
2. Invoke next via node_modules/next/dist/bin/next, not the .bin/next symlink: the
@hanzo/gui RN dep tree intermittently drops the symlink under the build npm
('sh: next: not found') even though the next package installs. Direct invocation
is symlink-independent. Build + runner CMD both updated.
Two fixes for the broken builds:
1. Base image: use ghcr.io/hanzoai/nodejs:24-alpine (our mirror of node:24-alpine)
per the ghcr-only policy. (public.ecr.aws rate-limited; mirror.gcr.io was a
stopgap. hanzoai/node is the blockchain node — nodejs is the Node.js runtime.)
Bumped 22→24.
2. Invoke next via node_modules/next/dist/bin/next, not the .bin/next symlink: the
@hanzo/gui RN dep tree intermittently drops the symlink under the build npm
('sh: next: not found') even though the next package installs. Direct invocation
is symlink-independent. Build + runner CMD both updated.
public.ecr.aws/docker/library/node:22-alpine started returning TOOMANYREQUESTS on
the base-image pull (the real cause of the build failures — a partial pull also
surfaced as the misleading 'next: not found'). mirror.gcr.io/library/node:22-alpine
is Google's Docker Hub mirror — reliable, not rate-limited. Combined with the
single-stage install+build, the v0.7.27 admin-fix build is unblocked.
public.ecr.aws/docker/library/node:22-alpine started returning TOOMANYREQUESTS on
the base-image pull (the real cause of the build failures — a partial pull also
surfaced as the misleading 'next: not found'). mirror.gcr.io/library/node:22-alpine
is Google's Docker Hub mirror — reliable, not rate-limited. Combined with the
single-stage install+build, the v0.7.27 admin-fix build is unblocked.
The deps→build cross-stage COPY of node_modules intermittently dropped
node_modules/.bin/next under Kaniko (sh: next: not found at 'npm run build',
despite a clean install adding ~850 packages). Reproduced: local install is fine,
so it's the cross-stage symlink handoff. Install + next build now run in ONE stage
on the same filesystem — the seam is gone. Runner stage unchanged (runtime next
start worked through its COPY all along). Unblocks the v0.7.27 admin-fix build.
The deps→build cross-stage COPY of node_modules intermittently dropped
node_modules/.bin/next under Kaniko (sh: next: not found at 'npm run build',
despite a clean install adding ~850 packages). Reproduced: local install is fine,
so it's the cross-stage symlink handoff. Install + next build now run in ONE stage
on the same filesystem — the seam is gone. Runner stage unchanged (runtime next
start worked through its COPY all along). Unblocks the v0.7.27 admin-fix build.
IAM never populates isGlobalAdmin AND admin-org members carry isAdmin=false, so the
gate's '&& isAdmin' made NO ONE a global admin → every legitimate admin was bounced
from admin.hanzo.ai to the console (redirect loop). Fix: membership in the reserved
'admin' org alone = global admin. Client OrgGate + server identity.ts. Tenants
(owner!=='admin') stay non-global → admin remains locked to them. v0.7.26
IAM never populates isGlobalAdmin AND admin-org members carry isAdmin=false, so the
gate's '&& isAdmin' made NO ONE a global admin → every legitimate admin was bounced
from admin.hanzo.ai to the console (redirect loop). Fix: membership in the reserved
'admin' org alone = global admin. Client OrgGate + server identity.ts. Tenants
(owner!=='admin') stay non-global → admin remains locked to them. v0.7.26
Resolve the home-lead fork to the full OverviewModule (Image-#3 vision: metric
cards + sparklines + tokens/spend/by-model charts + activity + quick actions +
wallet + system status) over the narrower AiMetricsModule lead. AiMetrics stays
its own route. One home dashboard, one way.
Resolve the home-lead fork to the full OverviewModule (Image-#3 vision: metric
cards + sparklines + tokens/spend/by-model charts + activity + quick actions +
wallet + system status) over the narrower AiMetricsModule lead. AiMetrics stays
its own route. One home dashboard, one way.
Functions' add/add ui/Charts.tsx was dead code (no consumer imported CHART_COLORS/
STATUS_COLORS). Take the canonical superset (Sparkline/LineChart/BarChart/Donut/
BarRows). One chart module, one palette name, no backwards-compat alias. Fixed the
legend swatch to the file's own styled-div idiom (was a themed bg with a hex).
Functions' add/add ui/Charts.tsx was dead code (no consumer imported CHART_COLORS/
STATUS_COLORS). Take the canonical superset (Sparkline/LineChart/BarChart/Donut/
BarRows). One chart module, one palette name, no backwards-compat alias. Fixed the
legend swatch to the file's own styled-div idiom (was a themed bg with a hex).
The Overview was a product grid; now it leads with the same tested AI Metrics
dashboard (requests/tokens/spend over time + per-model breakdown, real per-org
data) — the Langfuse-style project home — with the product catalog below for
navigation. DRY: reuses AiMetricsModule exactly. v0.7.25
The Overview was a product grid; now it leads with the same tested AI Metrics
dashboard (requests/tokens/spend over time + per-model breakdown, real per-org
data) — the Langfuse-style project home — with the product catalog below for
navigation. DRY: reuses AiMetricsModule exactly. v0.7.25
Merge Overview + Embeddings; collapse the two duplicate chart implementations
(components/charts/Charts.tsx + components/ui/Charts.tsx) into ONE canonical
ui/Charts.tsx superset built on pure @hanzo/gui primitives (promotable to the
shared @hanzo/gui package as a charts category). Repoint OverviewModule +
embeddings/OverviewView. tsc clean.
Merge Overview + Embeddings; collapse the two duplicate chart implementations
(components/charts/Charts.tsx + components/ui/Charts.tsx) into ONE canonical
ui/Charts.tsx superset built on pure @hanzo/gui primitives (promotable to the
shared @hanzo/gui package as a charts category). Repoint OverviewModule +
embeddings/OverviewView. tsc clean.
Compute → Machines as one node of a real DOKS cluster pool (GET /v1/org/{org}/
cluster → machinesFromClusters: sum(pool.count) rows, vCPU/RAM from the DO slug,
monthly cost from the platform bill-from table labeled 'est.'). 8 tabs, 7 metric
cards, status donut, machine table, selected-machine right rail. Per-node CPU%/
MEM%/GPU/uptime/IP the control plane doesn't expose → '—' (never fabricated).
Reboot/Terminate honest-disabled (no real endpoint at that altitude). currentOrg-
scoped; not-configured (501, PaaS token disabled) is the honest first state.
Additive platform.ts only. tsc clean · 20 machines tests green.
Compute → Machines as one node of a real DOKS cluster pool (GET /v1/org/{org}/
cluster → machinesFromClusters: sum(pool.count) rows, vCPU/RAM from the DO slug,
monthly cost from the platform bill-from table labeled 'est.'). 8 tabs, 7 metric
cards, status donut, machine table, selected-machine right rail. Per-node CPU%/
MEM%/GPU/uptime/IP the control plane doesn't expose → '—' (never fabricated).
Reboot/Terminate honest-disabled (no real endpoint at that altitude). currentOrg-
scoped; not-configured (501, PaaS token disabled) is the honest first state.
Additive platform.ts only. tsc clean · 20 machines tests green.
The /v1/billing/usage ledger carries per-request rows (metadata.model, totalTokens,
amount in CENTS). The Cost page flattened it with a generic reader → every row
'Usage', no tokens, and cost ×100 ($1.06 shown as $106). Now: looksLikeLedger()
+ perModel() roll up by real model name with correct cents — shared (DRY) with the
new AI Metrics module (StatTiles: requests/tokens/spend/balance, usage-over-time,
per-model breakdown, recent activity) reading the same real per-org data. o11y
RuntimeNotice points at AI Metrics (which has data) when traces are uninitialized.
32 unit tests (billing/aimetrics/format), tsc+build green.
The /v1/billing/usage ledger carries per-request rows (metadata.model, totalTokens,
amount in CENTS). The Cost page flattened it with a generic reader → every row
'Usage', no tokens, and cost ×100 ($1.06 shown as $106). Now: looksLikeLedger()
+ perModel() roll up by real model name with correct cents — shared (DRY) with the
new AI Metrics module (StatTiles: requests/tokens/spend/balance, usage-over-time,
per-model breakdown, recent activity) reading the same real per-org data. o11y
RuntimeNotice points at AI Metrics (which has data) when traces are uninitialized.
32 unit tests (billing/aimetrics/format), tsc+build green.
Ships the merged work (multi-model compare Playground with abort-safe billing,
the unified EmptyState/Cost sweep) as a public semver. Overview/Embeddings/
Machines/GPUs/Functions land in v0.7.24 as the conflict integration completes.
Ships the merged work (multi-model compare Playground with abort-safe billing,
the unified EmptyState/Cost sweep) as a public semver. Overview/Embeddings/
Machines/GPUs/Functions land in v0.7.24 as the conflict integration completes.
Comprehensive responsive pass so the console works at phone/tablet/laptop/
desktop, plus a floating assistant reachable from every page and a wallet that
doubles as the signed-in identity + a click-through to in-console billing.
P1 — Mobile/responsive shell (DashboardShell.tsx)
- Layout responsiveness is CSS-driven (Tamagui v5 media style props:
`display="none"` + `$lg={{ display:'flex' }}`), NOT a JS `useMedia()` branch —
the server and the client's first paint emit identical markup, so there is no
hydration mismatch and no flash of the compact layout on a wide screen.
- < lg (1024px): the persistent sidebar is HIDDEN behind a hamburger in the
topbar that opens the SAME nav as a left drawer (closes on select/backdrop);
the topbar condenses — org/scope/user/sign-out fold into one right-side menu
so nothing overflows at 375px; the Apps button collapses to icon-only.
- ≥ lg: the persistent sidebar is always on (collapsible) with the full inline
topbar controls.
- Fixed the collapsed-rail icons (20px, 44px hit targets — were too small).
- The nav body (SidebarNav) is shared by the desktop sidebar and the drawer (DRY).
- Responsive content padding ($md), wallet always reachable.
P2 — Floating AI chat (FloatingChat.tsx, mounted once in the dashboard layout)
- A chat bubble fixed bottom-right on every page. Click → opens the assistant:
a full-screen sheet < lg, a ~380×560 popover ≥ lg (sizing is CSS-driven too).
- REUSES the one working chat surface (ChatConversation → AiApi.chat → the
keyless /ai proxy). No AI rebuilt. A new `compact` mode on ChatConversation
drops the page header + fixed min-height so it fills the sheet; "History"
deep-links to the full /chat page.
P3 — Wallet as identity + billing click-through (SidebarWallet.tsx)
- The wallet now shows the signed-in user's avatar (IAM photo, else initials)
+ display name from useSession, alongside the live balance.
- Clicking the wallet/identity routes into the in-console Cost module (/cost:
balance, usage, invoices). "Top up" still deep-links to the brand billing
portal (billing.hanzo.ai) — payment is never rebuilt.
Verification
- `tsc --noEmit` clean; `next build` succeeds (14/14 pages).
- Playwright (headless) verified live at 375/768/1024/1440 with the backend
mocked: persistent-sidebar↔hamburger swap, drawer open/close, full-screen chat
sheet, account menu, wallet identity — all PASS, and NO React hydration
mismatch. Apps-label collapse confirmed (icon-only 375 / labeled 1440).
Comprehensive responsive pass so the console works at phone/tablet/laptop/
desktop, plus a floating assistant reachable from every page and a wallet that
doubles as the signed-in identity + a click-through to in-console billing.
P1 — Mobile/responsive shell (DashboardShell.tsx)
- Layout responsiveness is CSS-driven (Tamagui v5 media style props:
`display="none"` + `$lg={{ display:'flex' }}`), NOT a JS `useMedia()` branch —
the server and the client's first paint emit identical markup, so there is no
hydration mismatch and no flash of the compact layout on a wide screen.
- < lg (1024px): the persistent sidebar is HIDDEN behind a hamburger in the
topbar that opens the SAME nav as a left drawer (closes on select/backdrop);
the topbar condenses — org/scope/user/sign-out fold into one right-side menu
so nothing overflows at 375px; the Apps button collapses to icon-only.
- ≥ lg: the persistent sidebar is always on (collapsible) with the full inline
topbar controls.
- Fixed the collapsed-rail icons (20px, 44px hit targets — were too small).
- The nav body (SidebarNav) is shared by the desktop sidebar and the drawer (DRY).
- Responsive content padding ($md), wallet always reachable.
P2 — Floating AI chat (FloatingChat.tsx, mounted once in the dashboard layout)
- A chat bubble fixed bottom-right on every page. Click → opens the assistant:
a full-screen sheet < lg, a ~380×560 popover ≥ lg (sizing is CSS-driven too).
- REUSES the one working chat surface (ChatConversation → AiApi.chat → the
keyless /ai proxy). No AI rebuilt. A new `compact` mode on ChatConversation
drops the page header + fixed min-height so it fills the sheet; "History"
deep-links to the full /chat page.
P3 — Wallet as identity + billing click-through (SidebarWallet.tsx)
- The wallet now shows the signed-in user's avatar (IAM photo, else initials)
+ display name from useSession, alongside the live balance.
- Clicking the wallet/identity routes into the in-console Cost module (/cost:
balance, usage, invoices). "Top up" still deep-links to the brand billing
portal (billing.hanzo.ai) — payment is never rebuilt.
Verification
- `tsc --noEmit` clean; `next build` succeeds (14/14 pages).
- Playwright (headless) verified live at 375/768/1024/1440 with the backend
mocked: persistent-sidebar↔hamburger swap, drawer open/close, full-screen chat
sheet, account menu, wallet identity — all PASS, and NO React hydration
mismatch. Apps-label collapse confirmed (icon-only 375 / labeled 1440).
Upgrades the thin StoresModule in place into the Embeddings product (Overview·
Explore·Collections·Jobs·Models·Settings): collections=per-org vector stores
(get-stores), Explore=POST /v1/search on {owner}-{store}-docs (server-resolved
owner — store is only a query param), Models+generate=/v1/models + /v1/embeddings
via the keyless /ai proxy. currentOrg-scoped throughout; no secret reaches the
browser; /ai allow-list NOT widened. Honest-empty everywhere a field/endpoint is
absent (get-cloud-usages not merged yet → metric cards degrade to —; RRF drops
score → —; no vector point-lookup → empty) — never fabricated. Deletes the dead
StoresModule/StoreListView (registry was the only consumer); reuses StoreEditView.
Drive-by: corrects the stale 'built-in' admin-policy assertion to false (gate code
untouched). tsc clean · vitest 67/67 · next build 14/14.
Upgrades the thin StoresModule in place into the Embeddings product (Overview·
Explore·Collections·Jobs·Models·Settings): collections=per-org vector stores
(get-stores), Explore=POST /v1/search on {owner}-{store}-docs (server-resolved
owner — store is only a query param), Models+generate=/v1/models + /v1/embeddings
via the keyless /ai proxy. currentOrg-scoped throughout; no secret reaches the
browser; /ai allow-list NOT widened. Honest-empty everywhere a field/endpoint is
absent (get-cloud-usages not merged yet → metric cards degrade to —; RRF drops
score → —; no vector point-lookup → empty) — never fabricated. Deletes the dead
StoresModule/StoreListView (registry was the only consumer); reuses StoreEditView.
Drive-by: corrects the stale 'built-in' admin-policy assertion to false (gate code
untouched). tsc clean · vitest 67/67 · next build 14/14.
* feat(console): side-by-side multi-model compare Playground
Tabbed Playground (Chat/Completions/Embeddings/Audio/Vision) whose marquee is a
side-by-side compare board: ONE shared System+User (or Prompt) broadcasts to N
model columns that run in PARALLEL through the keyless /ai proxy, each streaming
its own output while reporting REAL tokens, cost (catalog $/Mtok) and latency
(time-to-first-token + total). Per-column model + optional settings override with
a sync-across-all toggle; one column erroring/stopping never disturbs the others.
Single-model mode is one column. Examples seed the prompt; History records a run.
- app/ai/[...path]: stream the upstream body through (real TTFT) instead of
buffering; allow-list v1/audio/speech for the Audio (TTS) tab. Both additive +
backward-compatible for existing non-streaming callers.
- lib/api/playground.ts: add streamChat (SSE, stream_options.include_usage),
embeddings, speech — additive to PlaygroundApi.
- Models selectable from the LIVE catalog (CloudModelApi → /ai/v1/models +
/v1/pricing/models), the same source the Models page uses. No mocks.
- Pure, unit-tested core (cost/SSE-parse/runner/history): 28 vitest tests.
* fix(console): cancel upstream on abort + release reader + honest stopped state
Red review follow-ups on the compare Playground (no scope creep):
1. [MED] Client abort now cancels upstream generation (stops over-billing the
user's own org + leaking N sockets after Stop/tab-switch/unmount):
- app/ai/[...path]/route.ts: pass `signal: req.signal` to the gateway fetch so
a browser->proxy abort propagates proxy->gateway.
- ComparePlayground: useEffect cleanup calls compare.cancel() on unmount;
cancel() aborts every column's AbortController.
2. [MED] runner.ts: wrap the SSE read loop in try/finally with
`reader.cancel().catch(()=>{})` so the ReadableStream + connection are
released on every exit — normal [DONE], a thrown mid-stream error chunk, or an
abort. New test asserts the reader is cancelled on a mid-stream error chunk.
3. [LOW] An aborted run no longer renders/records as success: new 'stopped'
RunPhase, CompareColumn shows a Stopped state, History uses
ok = !error && !aborted and shows a 'stopped' badge.
tsc --noEmit clean; vitest 29 playground tests green (28 + new MED-2 test).
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
* feat(console): side-by-side multi-model compare Playground
Tabbed Playground (Chat/Completions/Embeddings/Audio/Vision) whose marquee is a
side-by-side compare board: ONE shared System+User (or Prompt) broadcasts to N
model columns that run in PARALLEL through the keyless /ai proxy, each streaming
its own output while reporting REAL tokens, cost (catalog $/Mtok) and latency
(time-to-first-token + total). Per-column model + optional settings override with
a sync-across-all toggle; one column erroring/stopping never disturbs the others.
Single-model mode is one column. Examples seed the prompt; History records a run.
- app/ai/[...path]: stream the upstream body through (real TTFT) instead of
buffering; allow-list v1/audio/speech for the Audio (TTS) tab. Both additive +
backward-compatible for existing non-streaming callers.
- lib/api/playground.ts: add streamChat (SSE, stream_options.include_usage),
embeddings, speech — additive to PlaygroundApi.
- Models selectable from the LIVE catalog (CloudModelApi → /ai/v1/models +
/v1/pricing/models), the same source the Models page uses. No mocks.
- Pure, unit-tested core (cost/SSE-parse/runner/history): 28 vitest tests.
* fix(console): cancel upstream on abort + release reader + honest stopped state
Red review follow-ups on the compare Playground (no scope creep):
1. [MED] Client abort now cancels upstream generation (stops over-billing the
user's own org + leaking N sockets after Stop/tab-switch/unmount):
- app/ai/[...path]/route.ts: pass `signal: req.signal` to the gateway fetch so
a browser->proxy abort propagates proxy->gateway.
- ComparePlayground: useEffect cleanup calls compare.cancel() on unmount;
cancel() aborts every column's AbortController.
2. [MED] runner.ts: wrap the SSE read loop in try/finally with
`reader.cancel().catch(()=>{})` so the ReadableStream + connection are
released on every exit — normal [DONE], a thrown mid-stream error chunk, or an
abort. New test asserts the reader is cancelled on a mid-stream error chunk.
3. [LOW] An aborted run no longer renders/records as success: new 'stopped'
RunPhase, CompareColumn shows a Stopped state, History uses
ok = !error && !aborted and shows a 'stopped' badge.
tsc --noEmit clean; vitest 29 playground tests green (28 + new MED-2 test).
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Red review follow-ups on the compare Playground (no scope creep):
1. [MED] Client abort now cancels upstream generation (stops over-billing the
user's own org + leaking N sockets after Stop/tab-switch/unmount):
- app/ai/[...path]/route.ts: pass `signal: req.signal` to the gateway fetch so
a browser->proxy abort propagates proxy->gateway.
- ComparePlayground: useEffect cleanup calls compare.cancel() on unmount;
cancel() aborts every column's AbortController.
2. [MED] runner.ts: wrap the SSE read loop in try/finally with
`reader.cancel().catch(()=>{})` so the ReadableStream + connection are
released on every exit — normal [DONE], a thrown mid-stream error chunk, or an
abort. New test asserts the reader is cancelled on a mid-stream error chunk.
3. [LOW] An aborted run no longer renders/records as success: new 'stopped'
RunPhase, CompareColumn shows a Stopped state, History uses
ok = !error && !aborted and shows a 'stopped' badge.
tsc --noEmit clean; vitest 29 playground tests green (28 + new MED-2 test).
Red review follow-ups on the compare Playground (no scope creep):
1. [MED] Client abort now cancels upstream generation (stops over-billing the
user's own org + leaking N sockets after Stop/tab-switch/unmount):
- app/ai/[...path]/route.ts: pass `signal: req.signal` to the gateway fetch so
a browser->proxy abort propagates proxy->gateway.
- ComparePlayground: useEffect cleanup calls compare.cancel() on unmount;
cancel() aborts every column's AbortController.
2. [MED] runner.ts: wrap the SSE read loop in try/finally with
`reader.cancel().catch(()=>{})` so the ReadableStream + connection are
released on every exit — normal [DONE], a thrown mid-stream error chunk, or an
abort. New test asserts the reader is cancelled on a mid-stream error chunk.
3. [LOW] An aborted run no longer renders/records as success: new 'stopped'
RunPhase, CompareColumn shows a Stopped state, History uses
ok = !error && !aborted and shows a 'stopped' badge.
tsc --noEmit clean; vitest 29 playground tests green (28 + new MED-2 test).
Comprehensive responsive pass so the console works at phone/tablet/laptop/
desktop, plus a floating assistant reachable from every page and a wallet that
doubles as the signed-in identity + a click-through to in-console billing.
P1 — Mobile/responsive shell (DashboardShell.tsx)
- Layout responsiveness is CSS-driven (Tamagui v5 media style props:
`display="none"` + `$lg={{ display:'flex' }}`), NOT a JS `useMedia()` branch —
the server and the client's first paint emit identical markup, so there is no
hydration mismatch and no flash of the compact layout on a wide screen.
- < lg (1024px): the persistent sidebar is HIDDEN behind a hamburger in the
topbar that opens the SAME nav as a left drawer (closes on select/backdrop);
the topbar condenses — org/scope/user/sign-out fold into one right-side menu
so nothing overflows at 375px; the Apps button collapses to icon-only.
- ≥ lg: the persistent sidebar is always on (collapsible) with the full inline
topbar controls.
- Fixed the collapsed-rail icons (20px, 44px hit targets — were too small).
- The nav body (SidebarNav) is shared by the desktop sidebar and the drawer (DRY).
- Responsive content padding ($md), wallet always reachable.
P2 — Floating AI chat (FloatingChat.tsx, mounted once in the dashboard layout)
- A chat bubble fixed bottom-right on every page. Click → opens the assistant:
a full-screen sheet < lg, a ~380×560 popover ≥ lg (sizing is CSS-driven too).
- REUSES the one working chat surface (ChatConversation → AiApi.chat → the
keyless /ai proxy). No AI rebuilt. A new `compact` mode on ChatConversation
drops the page header + fixed min-height so it fills the sheet; "History"
deep-links to the full /chat page.
P3 — Wallet as identity + billing click-through (SidebarWallet.tsx)
- The wallet now shows the signed-in user's avatar (IAM photo, else initials)
+ display name from useSession, alongside the live balance.
- Clicking the wallet/identity routes into the in-console Cost module (/cost:
balance, usage, invoices). "Top up" still deep-links to the brand billing
portal (billing.hanzo.ai) — payment is never rebuilt.
Verification
- `tsc --noEmit` clean; `next build` succeeds (14/14 pages).
- Playwright (headless) verified live at 375/768/1024/1440 with the backend
mocked: persistent-sidebar↔hamburger swap, drawer open/close, full-screen chat
sheet, account menu, wallet identity — all PASS, and NO React hydration
mismatch. Apps-label collapse confirmed (icon-only 375 / labeled 1440).
Comprehensive responsive pass so the console works at phone/tablet/laptop/
desktop, plus a floating assistant reachable from every page and a wallet that
doubles as the signed-in identity + a click-through to in-console billing.
P1 — Mobile/responsive shell (DashboardShell.tsx)
- Layout responsiveness is CSS-driven (Tamagui v5 media style props:
`display="none"` + `$lg={{ display:'flex' }}`), NOT a JS `useMedia()` branch —
the server and the client's first paint emit identical markup, so there is no
hydration mismatch and no flash of the compact layout on a wide screen.
- < lg (1024px): the persistent sidebar is HIDDEN behind a hamburger in the
topbar that opens the SAME nav as a left drawer (closes on select/backdrop);
the topbar condenses — org/scope/user/sign-out fold into one right-side menu
so nothing overflows at 375px; the Apps button collapses to icon-only.
- ≥ lg: the persistent sidebar is always on (collapsible) with the full inline
topbar controls.
- Fixed the collapsed-rail icons (20px, 44px hit targets — were too small).
- The nav body (SidebarNav) is shared by the desktop sidebar and the drawer (DRY).
- Responsive content padding ($md), wallet always reachable.
P2 — Floating AI chat (FloatingChat.tsx, mounted once in the dashboard layout)
- A chat bubble fixed bottom-right on every page. Click → opens the assistant:
a full-screen sheet < lg, a ~380×560 popover ≥ lg (sizing is CSS-driven too).
- REUSES the one working chat surface (ChatConversation → AiApi.chat → the
keyless /ai proxy). No AI rebuilt. A new `compact` mode on ChatConversation
drops the page header + fixed min-height so it fills the sheet; "History"
deep-links to the full /chat page.
P3 — Wallet as identity + billing click-through (SidebarWallet.tsx)
- The wallet now shows the signed-in user's avatar (IAM photo, else initials)
+ display name from useSession, alongside the live balance.
- Clicking the wallet/identity routes into the in-console Cost module (/cost:
balance, usage, invoices). "Top up" still deep-links to the brand billing
portal (billing.hanzo.ai) — payment is never rebuilt.
Verification
- `tsc --noEmit` clean; `next build` succeeds (14/14 pages).
- Playwright (headless) verified live at 375/768/1024/1440 with the backend
mocked: persistent-sidebar↔hamburger swap, drawer open/close, full-screen chat
sheet, account menu, wallet identity — all PASS, and NO React hydration
mismatch. Apps-label collapse confirmed (icon-only 375 / labeled 1440).
Upgrades the Fine-tuning module from a read-only job list into a full training
surface wired to the cloud broker (hanzoai/ai /v1/finetune/*) via a same-origin,
user-scoped proxy.
- app/training/[...path]/route.ts same-origin proxy → /v1/finetune/* (cookie
forward, the get-account pattern; allow-listed
sub-paths; org re-resolved server-side). No key
or HF token ever reaches the browser.
- src/lib/api/finetune.ts typed client (unwraps the {status,msg,data}
envelope incl. the HTTP-200 error shape)
- finetuning/HfPicker.tsx browse/search HuggingFace models + datasets;
private/gated flagged; pick → start a job
- finetuning/NewJobPanel.tsx base-model + dataset pickers, LoRA/QLoRA/full,
Recommended preset that just works, GPU with a
live time/cost estimate, Start + Save-as-config
- finetuning/JobsView.tsx jobs list (honest empty/error states)
- finetuning/JobDetail.tsx live status polling, checkpoints, GPU-hours,
Deploy-to-inference, Cancel
- finetuning/logic.ts(+test) pure formatters + cost mirror + config store (17
vitest cases)
- FinetuningModule.tsx tabbed shell (Jobs/New/Models/Datasets/Configs);
internal nav, no new registry routes
tsc --noEmit clean · 17 finetuning vitest pass · next build clean.
Upgrades the Fine-tuning module from a read-only job list into a full training
surface wired to the cloud broker (hanzoai/ai /v1/finetune/*) via a same-origin,
user-scoped proxy.
- app/training/[...path]/route.ts same-origin proxy → /v1/finetune/* (cookie
forward, the get-account pattern; allow-listed
sub-paths; org re-resolved server-side). No key
or HF token ever reaches the browser.
- src/lib/api/finetune.ts typed client (unwraps the {status,msg,data}
envelope incl. the HTTP-200 error shape)
- finetuning/HfPicker.tsx browse/search HuggingFace models + datasets;
private/gated flagged; pick → start a job
- finetuning/NewJobPanel.tsx base-model + dataset pickers, LoRA/QLoRA/full,
Recommended preset that just works, GPU with a
live time/cost estimate, Start + Save-as-config
- finetuning/JobsView.tsx jobs list (honest empty/error states)
- finetuning/JobDetail.tsx live status polling, checkpoints, GPU-hours,
Deploy-to-inference, Cancel
- finetuning/logic.ts(+test) pure formatters + cost mirror + config store (17
vitest cases)
- FinetuningModule.tsx tabbed shell (Jobs/New/Models/Datasets/Configs);
internal nav, no new registry routes
tsc --noEmit clean · 17 finetuning vitest pass · next build clean.
Build the Overview page wired end-to-end to live data (no mock data):
- metrics / charts / spend-by-model / recent activity ← /v1/get-cloud-usages
(the hanzo.cloud_usage ledger), org-scoped by the X-Org-Id header;
- wallet balance ← commerce /v1/billing/balance (WalletApi.cloudBalance);
- quick actions ← the real product registry (no dead links).
- src/lib/api/usage.ts: typed UsageApi.overview client (+ allOrgs god-view).
- src/components/charts/Charts.tsx: dependency-free SVG charts (sparkline, line,
bar, donut) — console2 ships no chart lib; these theme to the dark shell and
render in the Next web DOM alongside @hanzo/gui.
- src/components/products/OverviewModule.tsx: the dashboard — time range
(24H/7D/30D/Custom), 4 metric cards w/ sparkline + "vs prior" delta, tokens
line, spend bar, spend-by-model donut + ranked list, recent activity (filter
tabs + pagination), quick actions, honest system-status footer, wallet.
Uniform loading/empty/error states; honest "—" for data with no live source
(GPU/latency → linked to the Status page rather than faked).
- app/(dashboard)/page.tsx: the home renders the Overview (the Explore-products
catalog is kept below).
- src/lib/products/registry.tsx: 'overview' module at /overview — also the
all-orgs admin surface via <OverviewDashboard allOrgs/>.
Build the Overview page wired end-to-end to live data (no mock data):
- metrics / charts / spend-by-model / recent activity ← /v1/get-cloud-usages
(the hanzo.cloud_usage ledger), org-scoped by the X-Org-Id header;
- wallet balance ← commerce /v1/billing/balance (WalletApi.cloudBalance);
- quick actions ← the real product registry (no dead links).
- src/lib/api/usage.ts: typed UsageApi.overview client (+ allOrgs god-view).
- src/components/charts/Charts.tsx: dependency-free SVG charts (sparkline, line,
bar, donut) — console2 ships no chart lib; these theme to the dark shell and
render in the Next web DOM alongside @hanzo/gui.
- src/components/products/OverviewModule.tsx: the dashboard — time range
(24H/7D/30D/Custom), 4 metric cards w/ sparkline + "vs prior" delta, tokens
line, spend bar, spend-by-model donut + ranked list, recent activity (filter
tabs + pagination), quick actions, honest system-status footer, wallet.
Uniform loading/empty/error states; honest "—" for data with no live source
(GPU/latency → linked to the Status page rather than faked).
- app/(dashboard)/page.tsx: the home renders the Overview (the Explore-products
catalog is kept below).
- src/lib/products/registry.tsx: 'overview' module at /overview — also the
all-orgs admin surface via <OverviewDashboard allOrgs/>.
Tabbed Playground (Chat/Completions/Embeddings/Audio/Vision) whose marquee is a
side-by-side compare board: ONE shared System+User (or Prompt) broadcasts to N
model columns that run in PARALLEL through the keyless /ai proxy, each streaming
its own output while reporting REAL tokens, cost (catalog $/Mtok) and latency
(time-to-first-token + total). Per-column model + optional settings override with
a sync-across-all toggle; one column erroring/stopping never disturbs the others.
Single-model mode is one column. Examples seed the prompt; History records a run.
- app/ai/[...path]: stream the upstream body through (real TTFT) instead of
buffering; allow-list v1/audio/speech for the Audio (TTS) tab. Both additive +
backward-compatible for existing non-streaming callers.
- lib/api/playground.ts: add streamChat (SSE, stream_options.include_usage),
embeddings, speech — additive to PlaygroundApi.
- Models selectable from the LIVE catalog (CloudModelApi → /ai/v1/models +
/v1/pricing/models), the same source the Models page uses. No mocks.
- Pure, unit-tested core (cost/SSE-parse/runner/history): 28 vitest tests.
Tabbed Playground (Chat/Completions/Embeddings/Audio/Vision) whose marquee is a
side-by-side compare board: ONE shared System+User (or Prompt) broadcasts to N
model columns that run in PARALLEL through the keyless /ai proxy, each streaming
its own output while reporting REAL tokens, cost (catalog $/Mtok) and latency
(time-to-first-token + total). Per-column model + optional settings override with
a sync-across-all toggle; one column erroring/stopping never disturbs the others.
Single-model mode is one column. Examples seed the prompt; History records a run.
- app/ai/[...path]: stream the upstream body through (real TTFT) instead of
buffering; allow-list v1/audio/speech for the Audio (TTS) tab. Both additive +
backward-compatible for existing non-streaming callers.
- lib/api/playground.ts: add streamChat (SSE, stream_options.include_usage),
embeddings, speech — additive to PlaygroundApi.
- Models selectable from the LIVE catalog (CloudModelApi → /ai/v1/models +
/v1/pricing/models), the same source the Models page uses. No mocks.
- Pure, unit-tested core (cost/SSE-parse/runner/history): 28 vitest tests.
Click a provider card → ProviderDetailPanel: provider name + stats (models, max
context, from-price, available) + the provider's full model list (name, type,
context, in/out price, status). Pairs with the model click-through. v0.7.21
Click a provider card → ProviderDetailPanel: provider name + stats (models, max
context, from-price, available) + the provider's full model list (name, type,
context, in/out price, status). Pairs with the model click-through. v0.7.21
* fix(ai): tenant-scope Providers/Stores/Models/Apps to the org + restore RAG retrieval
The AI/data admin views (ProviderListView, StoreListView/EditView,
ModelRouteList/EditView, ApplicationListView) used account.name (the USERNAME)
or a hardcoded 'admin' as the casibase owner. casibase entities are org-owned:
get-* scopes to the session org (GetScopedOwner) and honors the owner param only
for global admins, and AddStore trusts the body owner. So a username owner broke
global-admin org switching and orphaned newly-created stores. Switch all six
call sites to currentOrg() — the one active org-scope value (also stamped as
X-Org-Id), matching the v0.7.0 org-as-a-value model.
Also stamp X-IAM-Org-Id alongside X-Org-Id in the cloud client: the casibase
header-scoped filters (GetEffectiveOrg: usage/vectors/activities) read
X-IAM-Org-Id, so org switching now re-scopes those too (honored only for the
principal's own org or a global admin — safe).
RAG: the keyless /ai proxy rebuilt upstream headers from scratch and dropped
X-Retrieval/X-Retrieval-Store, so AiApi.ragChat silently degraded to a plain
answer. Forward the allow-listed retrieval headers (extracted to the pure,
tested lib/server/ai-proxy). 4 new tests; typecheck clean, 52 tests pass.
* console2: unified empty-state + cost/billing + wired AI pages (one way, forward-only)
The DRY pass toward 'every page real + useful': ONE EmptyState (the honest
first-run onboarding surface every module reuses instead of a dead screen), ONE
CostModule + billing client (real wallet/spend from commerce), and the AI pages
(Providers/Agents/Inference/Fine-tuning) wired to real data with that shared
empty state. Aligned the stray longhand maxWidth→maxW (onlyShorthandStyleProps:
one way, the redundant alias is off) and narrowed EmptyAction.icon to ReactElement.
tsc --noEmit clean (0 errors). Salvaged + verified from the throttled agent's tree.
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Co-authored-by: Hanzo <z@hanzo.ai>
* fix(ai): tenant-scope Providers/Stores/Models/Apps to the org + restore RAG retrieval
The AI/data admin views (ProviderListView, StoreListView/EditView,
ModelRouteList/EditView, ApplicationListView) used account.name (the USERNAME)
or a hardcoded 'admin' as the casibase owner. casibase entities are org-owned:
get-* scopes to the session org (GetScopedOwner) and honors the owner param only
for global admins, and AddStore trusts the body owner. So a username owner broke
global-admin org switching and orphaned newly-created stores. Switch all six
call sites to currentOrg() — the one active org-scope value (also stamped as
X-Org-Id), matching the v0.7.0 org-as-a-value model.
Also stamp X-IAM-Org-Id alongside X-Org-Id in the cloud client: the casibase
header-scoped filters (GetEffectiveOrg: usage/vectors/activities) read
X-IAM-Org-Id, so org switching now re-scopes those too (honored only for the
principal's own org or a global admin — safe).
RAG: the keyless /ai proxy rebuilt upstream headers from scratch and dropped
X-Retrieval/X-Retrieval-Store, so AiApi.ragChat silently degraded to a plain
answer. Forward the allow-listed retrieval headers (extracted to the pure,
tested lib/server/ai-proxy). 4 new tests; typecheck clean, 52 tests pass.
* console2: unified empty-state + cost/billing + wired AI pages (one way, forward-only)
The DRY pass toward 'every page real + useful': ONE EmptyState (the honest
first-run onboarding surface every module reuses instead of a dead screen), ONE
CostModule + billing client (real wallet/spend from commerce), and the AI pages
(Providers/Agents/Inference/Fine-tuning) wired to real data with that shared
empty state. Aligned the stray longhand maxWidth→maxW (onlyShorthandStyleProps:
one way, the redundant alias is off) and narrowed EmptyAction.icon to ReactElement.
tsc --noEmit clean (0 errors). Salvaged + verified from the throttled agent's tree.
---------
Co-authored-by: Hanzo AI <ai@hanzo.ai>
Co-authored-by: Hanzo <z@hanzo.ai>
The DRY pass toward 'every page real + useful': ONE EmptyState (the honest
first-run onboarding surface every module reuses instead of a dead screen), ONE
CostModule + billing client (real wallet/spend from commerce), and the AI pages
(Providers/Agents/Inference/Fine-tuning) wired to real data with that shared
empty state. Aligned the stray longhand maxWidth→maxW (onlyShorthandStyleProps:
one way, the redundant alias is off) and narrowed EmptyAction.icon to ReactElement.
tsc --noEmit clean (0 errors). Salvaged + verified from the throttled agent's tree.
The DRY pass toward 'every page real + useful': ONE EmptyState (the honest
first-run onboarding surface every module reuses instead of a dead screen), ONE
CostModule + billing client (real wallet/spend from commerce), and the AI pages
(Providers/Agents/Inference/Fine-tuning) wired to real data with that shared
empty state. Aligned the stray longhand maxWidth→maxW (onlyShorthandStyleProps:
one way, the redundant alias is off) and narrowed EmptyAction.icon to ReactElement.
tsc --noEmit clean (0 errors). Salvaged + verified from the throttled agent's tree.
Open tabs reference the prior build's hashed chunks after a deploy; those URLs
fall through to the app shell (HTML), so the browser throws ChunkLoadError /
'Unexpected token <' and blanks. ChunkGuard catches that exact failure and does
ONE guarded full reload to pull fresh HTML + current chunks. v0.7.19
Open tabs reference the prior build's hashed chunks after a deploy; those URLs
fall through to the app shell (HTML), so the browser throws ChunkLoadError /
'Unexpected token <' and blanks. ChunkGuard catches that exact failure and does
ONE guarded full reload to pull fresh HTML + current chunks. v0.7.19
- aicatalog: ONE source (/v1/pricing/models via /ai proxy) — 444 real models,
15 real providers, with context/pricing/specs/tier/provider. No fabrication.
- Model Catalog: polished table (model+params, type, context, in/out $/Mtok,
TRUE provider, live Available status) + stats bar. Fixes the qwen/glm 'Hanzo
(Zen)' mislabel — real provider per model.
- Providers: Explore grid (action cards + real provider cards + stats), was
'0 built-in'. /providers/manage keeps the custom-provider CRUD.
- Brand: our models show as 'Zen', never 'Hanzo (Zen)'. v0.7.18
- aicatalog: ONE source (/v1/pricing/models via /ai proxy) — 444 real models,
15 real providers, with context/pricing/specs/tier/provider. No fabrication.
- Model Catalog: polished table (model+params, type, context, in/out $/Mtok,
TRUE provider, live Available status) + stats bar. Fixes the qwen/glm 'Hanzo
(Zen)' mislabel — real provider per model.
- Providers: Explore grid (action cards + real provider cards + stats), was
'0 built-in'. /providers/manage keeps the custom-provider CRUD.
- Brand: our models show as 'Zen', never 'Hanzo (Zen)'. v0.7.18
Pinned wallet widget on every page — per-tenant balance via the /billing proxy +
Top-up deep-links to billing.hanzo.ai/topup (pay.hanzo.ai Square/crypto checkout),
never rebuilds payment. Collapsed mode = wallet icon. v0.7.17.
TODO: promote to @hanzo/ui as a reusable cross-app component (one way, composable).
Pinned wallet widget on every page — per-tenant balance via the /billing proxy +
Top-up deep-links to billing.hanzo.ai/topup (pay.hanzo.ai Square/crypto checkout),
never rebuilds payment. Collapsed mode = wallet icon. v0.7.17.
TODO: promote to @hanzo/ui as a reusable cross-app component (one way, composable).
The AI/data admin views (ProviderListView, StoreListView/EditView,
ModelRouteList/EditView, ApplicationListView) used account.name (the USERNAME)
or a hardcoded 'admin' as the casibase owner. casibase entities are org-owned:
get-* scopes to the session org (GetScopedOwner) and honors the owner param only
for global admins, and AddStore trusts the body owner. So a username owner broke
global-admin org switching and orphaned newly-created stores. Switch all six
call sites to currentOrg() — the one active org-scope value (also stamped as
X-Org-Id), matching the v0.7.0 org-as-a-value model.
Also stamp X-IAM-Org-Id alongside X-Org-Id in the cloud client: the casibase
header-scoped filters (GetEffectiveOrg: usage/vectors/activities) read
X-IAM-Org-Id, so org switching now re-scopes those too (honored only for the
principal's own org or a global admin — safe).
RAG: the keyless /ai proxy rebuilt upstream headers from scratch and dropped
X-Retrieval/X-Retrieval-Store, so AiApi.ragChat silently degraded to a plain
answer. Forward the allow-listed retrieval headers (extracted to the pure,
tested lib/server/ai-proxy). 4 new tests; typecheck clean, 52 tests pass.
The AI/data admin views (ProviderListView, StoreListView/EditView,
ModelRouteList/EditView, ApplicationListView) used account.name (the USERNAME)
or a hardcoded 'admin' as the casibase owner. casibase entities are org-owned:
get-* scopes to the session org (GetScopedOwner) and honors the owner param only
for global admins, and AddStore trusts the body owner. So a username owner broke
global-admin org switching and orphaned newly-created stores. Switch all six
call sites to currentOrg() — the one active org-scope value (also stamped as
X-Org-Id), matching the v0.7.0 org-as-a-value model.
Also stamp X-IAM-Org-Id alongside X-Org-Id in the cloud client: the casibase
header-scoped filters (GetEffectiveOrg: usage/vectors/activities) read
X-IAM-Org-Id, so org switching now re-scopes those too (honored only for the
principal's own org or a global admin — safe).
RAG: the keyless /ai proxy rebuilt upstream headers from scratch and dropped
X-Retrieval/X-Retrieval-Store, so AiApi.ragChat silently degraded to a plain
answer. Forward the allow-listed retrieval headers (extracted to the pure,
tested lib/server/ai-proxy). 4 new tests; typecheck clean, 52 tests pass.
SECURITY: an org owner (Dave/maxpower, org-level isAdmin) could reach the admin UI.
- gateAllows (server authority for /admin/* proxies): require isGlobalAdmin, NOT
isAdminGranted (which accepted org-level isAdmin). Verified brand-email stays as
2nd factor. Org admins now 403 on admin ops even with @adminDomain email.
- OrgGate: redirect non-global-admins OFF admin.hanzo.ai to the console host +
render-guard so the admin console never flashes. Banner already isGlobalAdmin.
- isGlobalAdmin now recognizes BOTH metadata orgs (admin + built-in), matching
admin-policy ORG_METADATA_OWNERS.
Bundles v0.7.13 (models owner/name token fix + banner gate). v0.7.14.
SECURITY: an org owner (Dave/maxpower, org-level isAdmin) could reach the admin UI.
- gateAllows (server authority for /admin/* proxies): require isGlobalAdmin, NOT
isAdminGranted (which accepted org-level isAdmin). Verified brand-email stays as
2nd factor. Org admins now 403 on admin ops even with @adminDomain email.
- OrgGate: redirect non-global-admins OFF admin.hanzo.ai to the console host +
render-guard so the admin console never flashes. Banner already isGlobalAdmin.
- isGlobalAdmin now recognizes BOTH metadata orgs (admin + built-in), matching
admin-policy ORG_METADATA_OWNERS.
Bundles v0.7.13 (models owner/name token fix + banner gate). v0.7.14.
1. identity.ts: user.id must be <owner>/<name> (IAM GetOwnerAndNameFromId), not the
bare casdoor UUID — fixes Model Catalog 'Could not authorize: wrong token count
for ID <uuid>' for org-member accounts (Dave/maxpower) that carry an id field.
2. OrgGate.tsx: the admin.hanzo.ai ops banner gated on isAdmin (org-level) so an
ORG owner (Dave/maxpower) saw it. Gate on isGlobalAdmin (admin/built-in org) —
org admins are not cross-tenant admins. v0.7.13.
1. identity.ts: user.id must be <owner>/<name> (IAM GetOwnerAndNameFromId), not the
bare casdoor UUID — fixes Model Catalog 'Could not authorize: wrong token count
for ID <uuid>' for org-member accounts (Dave/maxpower) that carry an id field.
2. OrgGate.tsx: the admin.hanzo.ai ops banner gated on isAdmin (org-level) so an
ORG owner (Dave/maxpower) saw it. Gate on isGlobalAdmin (admin/built-in org) —
org admins are not cross-tenant admins. v0.7.13.
The one remaining cross-service gap (v0.7.x already proxies AI/IAM/KMS). wallet
still hit cookie-only /v1/billing/balance -> 404. New app/billing/[...path] proxy
forwards /billing/* -> commerce with the service token + server-resolved own-org
scope (X-Hanzo-Org + BillingSubject; client cannot widen). Matches the /admin/*
proxy pattern + resolveUser. Wallet.cloudBalance repointed same-origin. v0.7.12.
The one remaining cross-service gap (v0.7.x already proxies AI/IAM/KMS). wallet
still hit cookie-only /v1/billing/balance -> 404. New app/billing/[...path] proxy
forwards /billing/* -> commerce with the service token + server-resolved own-org
scope (X-Hanzo-Org + BillingSubject; client cannot widen). Matches the /admin/*
proxy pattern + resolveUser. Wallet.cloudBalance repointed same-origin. v0.7.12.
gui.d.ts was augmenting @hanzogui/web which is not a direct dep (resolves only
via pnpm .pnpm path). Add @hanzogui/core augmentation (which is a direct dep) so
GuiCustomConfig → Conf flows through and shorthand props (bg/px/py/items/justify
etc.) are typed correctly. Also fix Button `color=` → `theme=` in OrgGate banner.
Before: 371 type errors. After: 0.
gui.d.ts was augmenting @hanzogui/web which is not a direct dep (resolves only
via pnpm .pnpm path). Add @hanzogui/core augmentation (which is a direct dep) so
GuiCustomConfig → Conf flows through and shorthand props (bg/px/py/items/justify
etc.) are typed correctly. Also fix Button `color=` → `theme=` in OrgGate banner.
Before: 371 type errors. After: 0.
List both get-global-providers (Hanzo platform-keyed, read-only, Built-in badge)
and per-org custom providers in one view. Users see all providers enabled out of
the box via Hanzo's DO-AI keys; adding a custom provider overrides/extends per org.
List both get-global-providers (Hanzo platform-keyed, read-only, Built-in badge)
and per-org custom providers in one view. Users see all providers enabled out of
the box via Hanzo's DO-AI keys; adding a custom provider overrides/extends per org.
- OrgGate: replace hard hard-block for hanzo-org users with a dismissible
amber banner pointing at admin.hanzo.ai; staff can use console.hanzo.ai
normally for cloud work (models, API keys, AI inference etc.)
- OrgGate: restore last selected org from localStorage on sign-in so the
scope remembers where the user left off
- Add e2e/ Playwright tests: sign-in, admin banner, API key create/confirm,
/v1/models verification, OpenAI + Anthropic inference tests
- Add playwright.config.ts targeting https://console.hanzo.ai by default
- package.json: add e2e + e2e:headed scripts
- OrgGate: replace hard hard-block for hanzo-org users with a dismissible
amber banner pointing at admin.hanzo.ai; staff can use console.hanzo.ai
normally for cloud work (models, API keys, AI inference etc.)
- OrgGate: restore last selected org from localStorage on sign-in so the
scope remembers where the user left off
- Add e2e/ Playwright tests: sign-in, admin banner, API key create/confirm,
/v1/models verification, OpenAI + Anthropic inference tests
- Add playwright.config.ts targeting https://console.hanzo.ai by default
- package.json: add e2e + e2e:headed scripts
Port the remaining old-console surfaces into console2 as forward-compatible
modules: Zero Trust, Integrations, Referrals, Experiments, Dashboards,
Score Analytics, plus prompt-create/metrics and dataset items/runs sub-modules.
Each surface points at its real/planned /v1 endpoint and renders real rows when
present; a 404/405/503 collapses to the shared honest BackendState card (no demo
rows). console2 now carries the old console's full information architecture while
backend routes light up independently.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Port the remaining old-console surfaces into console2 as forward-compatible
modules: Zero Trust, Integrations, Referrals, Experiments, Dashboards,
Score Analytics, plus prompt-create/metrics and dataset items/runs sub-modules.
Each surface points at its real/planned /v1 endpoint and renders real rows when
present; a 404/405/503 collapses to the shared honest BackendState card (no demo
rows). console2 now carries the old console's full information architecture while
backend routes light up independently.
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
Builds were red: docker/setup-buildx-action + docker/build-push-action
spin up an ephemeral buildkit container that can't see the host image
cache, so it re-pulled node:22-alpine from Docker Hub every run and hit
the unauthenticated 429 pull-rate limit; the action's build-summary
artifact upload also hit the Actions storage quota.
Switch to the canonical hanzoai/ci pattern: raw `docker buildx build
--push` on the host builder, which reuses the cached base layer (no
re-pull, no artifact upload). Adds a cache-aware base-image guard that
retries a cold pull with linear backoff. SEMVER tag + GHCR push unchanged.
Builds were red: docker/setup-buildx-action + docker/build-push-action
spin up an ephemeral buildkit container that can't see the host image
cache, so it re-pulled node:22-alpine from Docker Hub every run and hit
the unauthenticated 429 pull-rate limit; the action's build-summary
artifact upload also hit the Actions storage quota.
Switch to the canonical hanzoai/ci pattern: raw `docker buildx build
--push` on the host builder, which reuses the cached base layer (no
re-pull, no artifact upload). Adds a cache-aware base-image guard that
retries a cold pull with linear backoff. SEMVER tag + GHCR push unchanged.
The /paas proxy forwarded only the god-mode service token, so PaaS
resources couldn't scope per tenant. Now it forwards the full tenant
path the browser stamps:
- X-Org-Id is RE-RESOLVED server-side via the admin policy (orgFor): a
global admin's switched org (the X-Org-Id it already sends) is honored,
a brand admin is pinned to their own — authoritative, never the raw
spoofable claim. Same trust boundary as the IAM/KMS admin proxies.
- X-Project-Id + X-Environment pass through verbatim as sub-scopes within
that org.
Forward-correct: the control plane scopes by tenant once it reads these,
harmless until then. Adds scope.test.ts (9 tests: store round-trip, merge
semantics, persistence, projectEnvironments intrinsic-3 + custom). 38 green.
The /paas proxy forwarded only the god-mode service token, so PaaS
resources couldn't scope per tenant. Now it forwards the full tenant
path the browser stamps:
- X-Org-Id is RE-RESOLVED server-side via the admin policy (orgFor): a
global admin's switched org (the X-Org-Id it already sends) is honored,
a brand admin is pinned to their own — authoritative, never the raw
spoofable claim. Same trust boundary as the IAM/KMS admin proxies.
- X-Project-Id + X-Environment pass through verbatim as sub-scopes within
that org.
Forward-correct: the control plane scopes by tenant once it reads these,
harmless until then. Adds scope.test.ts (9 tests: store round-trip, merge
semantics, persistence, projectEnvironments intrinsic-3 + custom). 38 green.
The staff redirect button passed two children ("Go to admin." + the
{adminDomain} expression); Tamagui Button lays children out with its
icon-gap, so the two text nodes rendered with a stray space
("Go to admin. hanzo.ai"). Collapse to a single template-literal child.
Header retitled "<Brand> staff" → "<Brand> Admin" (white-label via brand).
The staff redirect button passed two children ("Go to admin." + the
{adminDomain} expression); Tamagui Button lays children out with its
icon-gap, so the two text nodes rendered with a stray space
("Go to admin. hanzo.ai"). Collapse to a single template-literal child.
Header retitled "<Brand> staff" → "<Brand> Admin" (white-label via brand).
Projects under the org, each with intrinsic mainnet/testnet/devnet
environments (+ custom), scoping every module at once.
- lib/scope.ts: module-level active { org, project?, environment } the
non-React API client reads synchronously to stamp headers. Org pinned
to the brand org; STOCK_ENVIRONMENTS = mainnet/testnet/devnet.
- lib/api/client.ts: baseHeaders stamps X-Project-Id (when a project is
selected) + X-Environment on every cloud call — one change scopes all
existing modules (o11y, api-keys, deploys, …) with no per-module edits.
- lib/api/projects.ts: ProjectApi over the REAL Hanzo IAM contract
(/v1/iam/get-organization-projects | add-project | delete-project),
keyed (owner, name) with indexed organization = the brand org.
- lib/scope-context.tsx: ScopeProvider — loads the org's projects once,
holds the active selection, mirrors it into the module scope +
localStorage, derives per-project environments. Honest: an unrouted
projects endpoint resolves to org-level only, never a fabricated row.
- components/ScopeSwitcher.tsx: project + environment pickers in the top
bar (next to OrgSwitcher); env dots keyed to network tier.
- components/products/ProjectsModule.tsx: projects CRUD + "Use" to set
active scope; honest not-routed/empty states, no fakes.
- registry: Projects flips external → in-console module (Deploy).
Environments are a console-side scoping dimension (IAM Project has no
environments column); X-Environment is sent canonically for backend
adoption. tsc --noEmit clean.
Projects under the org, each with intrinsic mainnet/testnet/devnet
environments (+ custom), scoping every module at once.
- lib/scope.ts: module-level active { org, project?, environment } the
non-React API client reads synchronously to stamp headers. Org pinned
to the brand org; STOCK_ENVIRONMENTS = mainnet/testnet/devnet.
- lib/api/client.ts: baseHeaders stamps X-Project-Id (when a project is
selected) + X-Environment on every cloud call — one change scopes all
existing modules (o11y, api-keys, deploys, …) with no per-module edits.
- lib/api/projects.ts: ProjectApi over the REAL Hanzo IAM contract
(/v1/iam/get-organization-projects | add-project | delete-project),
keyed (owner, name) with indexed organization = the brand org.
- lib/scope-context.tsx: ScopeProvider — loads the org's projects once,
holds the active selection, mirrors it into the module scope +
localStorage, derives per-project environments. Honest: an unrouted
projects endpoint resolves to org-level only, never a fabricated row.
- components/ScopeSwitcher.tsx: project + environment pickers in the top
bar (next to OrgSwitcher); env dots keyed to network tier.
- components/products/ProjectsModule.tsx: projects CRUD + "Use" to set
active scope; honest not-routed/empty states, no fakes.
- registry: Projects flips external → in-console module (Deploy).
Environments are a console-side scoping dimension (IAM Project has no
environments column); X-Environment is sent canonically for backend
adoption. tsc --noEmit clean.
The 'I don't see any models' wave + sidebar/command UX.
- Models is catalog-first: the default tab is the LIVE model list (~49 Zen
models via the /ai proxy); routing policy moves to a secondary 'Routing' tab
(/models/routing). Retires the duplicate empty-by-default 'Model Catalog' nav
entry — one product, real models on the obvious click.
- Docs are EXTERNAL (brand docsUrl, new tab): a top sidebar 'Docs' entry, the
header '?' icon, and a server /docs -> docs.<brand> redirect (no in-app 404).
ComingSoon's API-docs link repointed off the 404-ing ${cloudUrl}/docs.
- Sidebar collapses/expands from the brand 'H' mark (icon-only <-> full),
persisted to the account; the grid launcher stays. A filter box narrows the
whole sidebar to find any product fast; Overview/Docs are fixed top links.
- cmd+K runs ACTIONS too (toggle theme, browse all apps, open settings, switch
org, ask AI / search docs, sign out, per-org switch), ranked alongside catalog
nav — no dead entries. Removed unused openMode.
- DRY: switchOrg() shared by the switcher + palette; pure match-core (resolveRoute
+ entryMatches) is unit-tested without the GUI tree. Default pins fixed
(dead 'billing' -> 'models','chat'). tsc + 29 vitest + next build clean.
The 'I don't see any models' wave + sidebar/command UX.
- Models is catalog-first: the default tab is the LIVE model list (~49 Zen
models via the /ai proxy); routing policy moves to a secondary 'Routing' tab
(/models/routing). Retires the duplicate empty-by-default 'Model Catalog' nav
entry — one product, real models on the obvious click.
- Docs are EXTERNAL (brand docsUrl, new tab): a top sidebar 'Docs' entry, the
header '?' icon, and a server /docs -> docs.<brand> redirect (no in-app 404).
ComingSoon's API-docs link repointed off the 404-ing ${cloudUrl}/docs.
- Sidebar collapses/expands from the brand 'H' mark (icon-only <-> full),
persisted to the account; the grid launcher stays. A filter box narrows the
whole sidebar to find any product fast; Overview/Docs are fixed top links.
- cmd+K runs ACTIONS too (toggle theme, browse all apps, open settings, switch
org, ask AI / search docs, sign out, per-org switch), ranked alongside catalog
nav — no dead entries. Removed unused openMode.
- DRY: switchOrg() shared by the switcher + palette; pure match-core (resolveRoute
+ entryMatches) is unit-tested without the GUI tree. Default pins fixed
(dead 'billing' -> 'models','chat'). tsc + 29 vitest + next build clean.
The org-scope module defaults the active org to the brand org (for the cross-org
admin). On a customer host, seed the signed-in user's OWN org as the active scope
the first time (only when no explicit switch is in effect), so the OrgSwitcher
chip and X-Org-Id reflect the real tenant (e.g. maxpower) instead of the brand
org. Never clobbers an admin's deliberate switch.
The org-scope module defaults the active org to the brand org (for the cross-org
admin). On a customer host, seed the signed-in user's OWN org as the active scope
the first time (only when no explicit switch is in effect), so the OrgSwitcher
chip and X-Org-Id reflect the real tenant (e.g. maxpower) instead of the brand
org. Never clobbers an admin's deliberate switch.
The @hanzo/gui Input ignores the RN secureTextEntry/keyboardType props on web,
so the password rendered as type=text (visible while typing). Set the web input
type explicitly (type="password") so it masks; also corrects autoComplete to
current-password.
The @hanzo/gui Input ignores the RN secureTextEntry/keyboardType props on web,
so the password rendered as type=text (visible while typing). Set the web input
type explicitly (type="password") so it masks; also corrects autoComplete to
current-password.
The build step used `node -p require('./package.json').version`; node is not on
the ARC runner PATH, so the substitution silently yielded the tag `:v` and the
operator deploy 404'd. Resolve the version with grep/sed and fail-loud if empty.
The build step used `node -p require('./package.json').version`; node is not on
the ARC runner PATH, so the substitution silently yielded the tag `:v` and the
operator deploy 404'd. Resolve the version with grep/sed and fail-loud if empty.
Login resolves the user's ORG from their email instead of pinning the brand's
own org: a customer in any org signs into the brand console with email+password.
- iam-login.ts: POST /v1/iam/login with organization: (cross-org email
resolution) → OAuth code → existing completeSignIn → /v1/signin exchange.
Replaces the SDK org-pinned redirect that made non-brand-org users
un-signinable. MFA (NextMfa/RequiredMfa) hands off to IAM's same-site hosted
flow — IAM sets iam_session_id SameSite=Lax, so cross-site fetch MFA can't
complete here; no faked inline step.
- SignInForm: email+password state machine; social (getProviderSigninUrl) kept.
- OrgGate: the console runs in the user's CUSTOMER org — blocks the internal
brand org (owner===config.iamOrgName → admin.<domain>) and the zero-org case.
- SECURITY /paas/[...path]: gate with getAdminGate (403 if not a brand admin) +
runtime nodejs. The forwarded PAAS_SERVICE_TOKEN is control-plane god-mode and
was previously reachable by any authenticated browser.
- getAdminGate: orgScope=user.owner (was brand.id) so the IAM/KMS proxies pin a
non-global admin to their OWN org; require a VERIFIED email (authoritative IAM
recheck for thin claims). admin-policy + tests updated (14 pass).
Login resolves the user's ORG from their email instead of pinning the brand's
own org: a customer in any org signs into the brand console with email+password.
- iam-login.ts: POST /v1/iam/login with organization: (cross-org email
resolution) → OAuth code → existing completeSignIn → /v1/signin exchange.
Replaces the SDK org-pinned redirect that made non-brand-org users
un-signinable. MFA (NextMfa/RequiredMfa) hands off to IAM's same-site hosted
flow — IAM sets iam_session_id SameSite=Lax, so cross-site fetch MFA can't
complete here; no faked inline step.
- SignInForm: email+password state machine; social (getProviderSigninUrl) kept.
- OrgGate: the console runs in the user's CUSTOMER org — blocks the internal
brand org (owner===config.iamOrgName → admin.<domain>) and the zero-org case.
- SECURITY /paas/[...path]: gate with getAdminGate (403 if not a brand admin) +
runtime nodejs. The forwarded PAAS_SERVICE_TOKEN is control-plane god-mode and
was previously reachable by any authenticated browser.
- getAdminGate: orgScope=user.owner (was brand.id) so the IAM/KMS proxies pin a
non-global admin to their OWN org; require a VERIFIED email (authoritative IAM
recheck for thin claims). admin-policy + tests updated (14 pass).
Root cause of empty models + broken org switcher: /v1/{iam,kms,models} 404/401
(cookie-only) on the console host. Route every privileged call through console2's
own server proxies (user bearer + admin gate), and make org scope a switchable value.
- models-catalog: repoint /v1/models -> /ai proxy (shared aiV1Url in client.ts);
catalog now populates with live Zen models. playground reuses the shared aiBase.
- org-scope.ts: currentOrg/setCurrentOrg/isScopedAway/filterOrgs. client.ts stamps
X-Org-Id: currentOrg() so data modules re-scope on switch.
- OrgSwitcher: lists ALL visible orgs, filter box, in-place re-scope (set+reload).
- IamModule/AuditModule read currentOrg(); KmsModule now a names-only inventory
over KmsAdminApi.list (the /admin/kms proxy), values never fetched.
- admin-policy.ts: pure gateAllows/ownerAllowed/orgFor extracted from the gate +
routes (decomplect) so the shipped predicate is the tested one.
- vitest: 22 tests RED->GREEN (gate allow/deny+scoping, scope+filter, catalog /ai).
tsc --noEmit + next build clean.
Root cause of empty models + broken org switcher: /v1/{iam,kms,models} 404/401
(cookie-only) on the console host. Route every privileged call through console2's
own server proxies (user bearer + admin gate), and make org scope a switchable value.
- models-catalog: repoint /v1/models -> /ai proxy (shared aiV1Url in client.ts);
catalog now populates with live Zen models. playground reuses the shared aiBase.
- org-scope.ts: currentOrg/setCurrentOrg/isScopedAway/filterOrgs. client.ts stamps
X-Org-Id: currentOrg() so data modules re-scope on switch.
- OrgSwitcher: lists ALL visible orgs, filter box, in-place re-scope (set+reload).
- IamModule/AuditModule read currentOrg(); KmsModule now a names-only inventory
over KmsAdminApi.list (the /admin/kms proxy), values never fetched.
- admin-policy.ts: pure gateAllows/ownerAllowed/orgFor extracted from the gate +
routes (decomplect) so the shipped predicate is the tested one.
- vitest: 22 tests RED->GREEN (gate allow/deny+scoping, scope+filter, catalog /ai).
tsc --noEmit + next build clean.
Two more old-console pages as real o11y modules: Observations (the flat
cross-trace span/generation view, GET /v1/o11y/observations) and Users (per-user
analytics rollup, GET /v1/o11y/users). O11yApi extended with both endpoints +
the O11yUser type. Same paged DataTable + honest RuntimeNotice pattern as the
other o11y modules; registered under Observe. tsc clean.
Two more old-console pages as real o11y modules: Observations (the flat
cross-trace span/generation view, GET /v1/o11y/observations) and Users (per-user
analytics rollup, GET /v1/o11y/users). O11yApi extended with both endpoints +
the O11yUser type. Same paged DataTable + honest RuntimeNotice pattern as the
other o11y modules; registered under Observe. tsc clean.
Flip every 'soon' product (ComingSoon stub) to a real, enabled in-console module
— attestations/oracles/indexer/tokens/settlement, alerts/logs, pipelines/
releases/builds/environments, hsm/authz/service-mesh/load-balancer/vpc, jobs/
edge/functions/containers/machines/gpus, agents/inference/finetuning. Each
follows the established module pattern: typed restGet over the same-origin /paas
proxy, DataTable, honest interpretPlatformError→PlatformStateCard not-configured
state, Refresh. Registry: status soon→enabled + routes wired. Full tsc clean.
Catalog is now 61 enabled modules + 16 external; no 'soon' stubs remain.
Flip every 'soon' product (ComingSoon stub) to a real, enabled in-console module
— attestations/oracles/indexer/tokens/settlement, alerts/logs, pipelines/
releases/builds/environments, hsm/authz/service-mesh/load-balancer/vpc, jobs/
edge/functions/containers/machines/gpus, agents/inference/finetuning. Each
follows the established module pattern: typed restGet over the same-origin /paas
proxy, DataTable, honest interpretPlatformError→PlatformStateCard not-configured
state, Refresh. Registry: status soon→enabled + routes wired. Full tsc clean.
Catalog is now 61 enabled modules + 16 external; no 'soon' stubs remain.
The mark now follows config.brand — each brand's OWN published, interactive
animated SVG (@hanzo/logo, @luxfi/logo, @zooai/logo: getAnimatedSVG, load→hover→
press). Static block-H during SSR/first paint (no hydration mismatch). The logo
is now the brand's playable 'AI' on every loading + sign-in surface.
The mark now follows config.brand — each brand's OWN published, interactive
animated SVG (@hanzo/logo, @luxfi/logo, @zooai/logo: getAnimatedSVG, load→hover→
press). Static block-H during SSR/first paint (no hydration mismatch). The logo
is now the brand's playable 'AI' on every loading + sign-in surface.
The mint/revoke success path called useSession().reload(), which flips the
session loading flag -> AuthGate renders its Loader -> the dashboard (and
ApiKeysView) unmounts -> the freshly-minted key (local newKey state) is lost on
remount, so 'Your new API key' never showed. The session masks accessKey anyway,
so the reload provided no benefit. Show the new key from local state only.
Verified live (v0.6.0): /keys POST 200 + /ai chat proxy 200 (real 'PONG'/Hanzo
answer); only the keys UI render was affected.
The mint/revoke success path called useSession().reload(), which flips the
session loading flag -> AuthGate renders its Loader -> the dashboard (and
ApiKeysView) unmounts -> the freshly-minted key (local newKey state) is lost on
remount, so 'Your new API key' never showed. The session masks accessKey anyway,
so the reload provided no benefit. Show the new key from local state only.
Verified live (v0.6.0): /keys POST 200 + /ai chat proxy 200 (real 'PONG'/Hanzo
answer); only the keys UI render was affected.
P0 — make it work for Dave:
- Root cause of 'chats/playground don't work': /v1/chat/completions requires
Authorization: Bearer; the browser sent cookie-only -> rejected. Fixed with a
keyless server-side AI proxy (app/ai/[...path]) that mints a short-lived
user-bound IAM token (issue-user-token, hanzo-console app-on-behalf) and
forwards to the gateway. No key in the browser, no rotation per turn.
- API keys: app/keys route mints/rotates/revokes the per-user hk- key via IAM
(mint-user-keys/revoke-user-keys); ApiKeysModule is now create/copy/rotate/
revoke with show-once secret handling.
- Chat is interactive (ChatConversation) over AiApi.chat; honest 402 billing state.
- src/lib/server/identity.ts: server-only trust boundary (resolveUser + IAM ops).
P1 — chrome polish:
- Header/sidebar show the Hanzo H mark + 'Console' (HanzoMark, BrandLogo with
org-logo fallback).
- Fullscreen Launchpad-style app launcher (AppLauncher) with filter, from the
header 'Apps' button, sidebar grid icon, and the command palette.
- cmd+K palette gains a 'Browse all apps' affordance.
Verified end-to-end (curl, real creds): minted hk- key + issued user JWT both
200 on api.hanzo.ai/v1/chat/completions. typecheck + next build clean.
P0 — make it work for Dave:
- Root cause of 'chats/playground don't work': /v1/chat/completions requires
Authorization: Bearer; the browser sent cookie-only -> rejected. Fixed with a
keyless server-side AI proxy (app/ai/[...path]) that mints a short-lived
user-bound IAM token (issue-user-token, hanzo-console app-on-behalf) and
forwards to the gateway. No key in the browser, no rotation per turn.
- API keys: app/keys route mints/rotates/revokes the per-user hk- key via IAM
(mint-user-keys/revoke-user-keys); ApiKeysModule is now create/copy/rotate/
revoke with show-once secret handling.
- Chat is interactive (ChatConversation) over AiApi.chat; honest 402 billing state.
- src/lib/server/identity.ts: server-only trust boundary (resolveUser + IAM ops).
P1 — chrome polish:
- Header/sidebar show the Hanzo H mark + 'Console' (HanzoMark, BrandLogo with
org-logo fallback).
- Fullscreen Launchpad-style app launcher (AppLauncher) with filter, from the
header 'Apps' button, sidebar grid icon, and the command palette.
- cmd+K palette gains a 'Browse all apps' affordance.
Verified end-to-end (curl, real creds): minted hk- key + issued user JWT both
200 on api.hanzo.ai/v1/chat/completions. typecheck + next build clean.
Async is the canonical home for Tasks per the org taxonomy. Appended as an 11th
category so the ten GCP-equivalent groups keep their exact labels and order
(no reorder); catalogByCategory is data-driven, so it renders generically.
Async is the canonical home for Tasks per the org taxonomy. Appended as an 11th
category so the ten GCP-equivalent groups keep their exact labels and order
(no reorder); catalogByCategory is data-driven, so it renders generically.
Memory (Data): list + search (kind filter + text) + detail/edit + add/delete,
honest 'initializing' card until /v1/memory deploys. Tasks (Compute, GCP Cloud
Tasks): namespace selector + Workflows/Schedules tabs + cluster strip, workflow
detail + durable history, on the LIVE /v1/tasks engine. Both render honest
states on a gated/absent route; mutations report through the shared toast.
Entries appended (no reorder); grouped by category.
Memory (Data): list + search (kind filter + text) + detail/edit + add/delete,
honest 'initializing' card until /v1/memory deploys. Tasks (Compute, GCP Cloud
Tasks): namespace selector + Workflows/Schedules tabs + cluster strip, workflow
detail + durable history, on the LIVE /v1/tasks engine. Both render honest
states on a gated/absent route; mutations report through the shared toast.
Entries appended (no reorder); grouped by category.
Dashboard layout wraps the shell in ToastProvider + CommandPaletteProvider. The
shell top bar gains the command search box (opens the palette), theme toggle, a
help launcher (opens the palette in docs mode), and the org switcher; a breadcrumb
bar sits below it. ResourceModule create/delete now report through the toast, so
the one feedback primitive is actually used.
Dashboard layout wraps the shell in ToastProvider + CommandPaletteProvider. The
shell top bar gains the command search box (opens the palette), theme toggle, a
help launcher (opens the palette in docs mode), and the org switcher; a breadcrumb
bar sits below it. ResourceModule create/delete now report through the toast, so
the one feedback primitive is actually used.
CommandPalette is ONE command surface (Cmd/Ctrl+K) with modes selected by the
query: default fuzzy-filters the catalog and jumps to any product; > asks the AI
to find a product (NAV <id>) or answer; ? asks the docs knowledge store (RAG).
searchCatalog is the dependency-free fuzzy ranker. OrgSwitcher shows the account's
org and, only for a real multi-brand membership, switches to that brand's console
host. Honest throughout — AI/RAG/IAM failures degrade to truthful states.
CommandPalette is ONE command surface (Cmd/Ctrl+K) with modes selected by the
query: default fuzzy-filters the catalog and jumps to any product; > asks the AI
to find a product (NAV <id>) or answer; ? asks the docs knowledge store (RAG).
searchCatalog is the dependency-free fuzzy ranker. OrgSwitcher shows the account's
org and, only for a real multi-brand membership, switches to that brand's console
host. Honest throughout — AI/RAG/IAM failures degrade to truthful states.
Toast is the one feedback primitive — ToastProvider + useToast() with a portalled
top-right viewport, theme-aware accents, auto-dismiss. ThemeToggle flips dark/light
via next-theme. Breadcrumbs derive Home/Category/Product/detail from the route +
catalog, so a new product gets correct crumbs for free. GUI primitives only.
Toast is the one feedback primitive — ToastProvider + useToast() with a portalled
top-right viewport, theme-aware accents, auto-dismiss. ThemeToggle flips dark/light
via next-theme. Breadcrumbs derive Home/Category/Product/detail from the route +
catalog, so a new product gets correct crumbs for free. GUI primitives only.
AiApi composes the single OpenAI-compatible gateway binding (PlaygroundApi):
plain chat, listModels, and ragChat grounded in a knowledge store (docs by
default) via the built-in retrieval path — the X-Retrieval-Store header turns
on RAG and names the store; the org owner is resolved server-side. restPost and
PlaygroundApi.chat gain an optional headers arg so RAG and plain chat share ONE
binding. No parallel AI client; failures throw ApiError for honest states.
AiApi composes the single OpenAI-compatible gateway binding (PlaygroundApi):
plain chat, listModels, and ragChat grounded in a knowledge store (docs by
default) via the built-in retrieval path — the X-Retrieval-Store header turns
on RAG and names the store; the org owner is resolved server-side. restPost and
PlaygroundApi.chat gain an optional headers arg so RAG and plain chat share ONE
binding. No parallel AI client; failures throw ApiError for honest states.
billingUrl moves from SHARED to the per-brand BRANDS table, resolved like
iamUrl. Each brand's console (Cost product, PlansModule manage-billing) links
to ITS billing host, scoped to ITS org by the brand JWT. Cloud backend stays
shared/multi-tenant.
billingUrl moves from SHARED to the per-brand BRANDS table, resolved like
iamUrl. Each brand's console (Cost product, PlansModule manage-billing) links
to ITS billing host, scoped to ITS org by the brand JWT. Cloud backend stays
shared/multi-tenant.
Native @hanzo/gui modules over the REAL /v1/o11y REST surface; honest
RuntimeNotice on 503/404 — no fabricated data.
- Traces detail: flat observations table -> nested span TREE waterfall
(SpanTree) built from parentObservationId, with a Tree|Table toggle.
Orphans/cycles surface as roots so every observation appears once.
- Score Configs: new Observe module on /v1/o11y/score-configs (read-only).
- Annotation Queues: new Observe module on /v1/o11y/annotation-queues
(real public REST list — contradicts the earlier 'no backend' finding).
Skipped (honest, no usable Hanzo backend or would duplicate/fake):
dashboards/widgets + score-analytics (no saved-dashboard REST, charts
would be fabricated), llm-connections/mcp (covered by Providers/ModelCatalog),
agents (backend not routed at gateway — real paths 404), org/projects deep
settings (already covered by Settings + IAM, no write endpoints), and the
Langfuse integration surfaces (feature-flags/entitlements/automations/
batch-exports/developer-tools/slack/mixpanel/blobstorage).
catalog 73 -> 75 entries; appended only (no reorder).
Native @hanzo/gui modules over the REAL /v1/o11y REST surface; honest
RuntimeNotice on 503/404 — no fabricated data.
- Traces detail: flat observations table -> nested span TREE waterfall
(SpanTree) built from parentObservationId, with a Tree|Table toggle.
Orphans/cycles surface as roots so every observation appears once.
- Score Configs: new Observe module on /v1/o11y/score-configs (read-only).
- Annotation Queues: new Observe module on /v1/o11y/annotation-queues
(real public REST list — contradicts the earlier 'no backend' finding).
Skipped (honest, no usable Hanzo backend or would duplicate/fake):
dashboards/widgets + score-analytics (no saved-dashboard REST, charts
would be fabricated), llm-connections/mcp (covered by Providers/ModelCatalog),
agents (backend not routed at gateway — real paths 404), org/projects deep
settings (already covered by Settings + IAM, no write endpoints), and the
Langfuse integration surfaces (feature-flags/entitlements/automations/
batch-exports/developer-tools/slack/mixpanel/blobstorage).
catalog 73 -> 75 entries; appended only (no reorder).
Merges port-{settings-models,prompts-evals,o11y-core}. 73 catalog entries across the 10 categories; new modules wired to real /v1 backends with honest states (o11y 503 until runtime init). tsc + next build green.
Merges port-{settings-models,prompts-evals,o11y-core}. 73 catalog entries across the 10 categories; new modules wired to real /v1 backends with honest states (o11y 503 until runtime init). tsc + next build green.
ProviderListView/ProviderEditView imported ~/lib/zap, but the cloud /zap
WebSocket face is not served (edge returns SPA HTML, not a WS upgrade — per
lib/zap/client.ts LIVE STATUS), so Providers rendered 'Failed to load
providers'. Switch both to ~/lib/api (identical surface). Part of v0.1.8.
ProviderListView/ProviderEditView imported ~/lib/zap, but the cloud /zap
WebSocket face is not served (edge returns SPA HTML, not a WS upgrade — per
lib/zap/client.ts LIVE STATUS), so Providers rendered 'Failed to load
providers'. Switch both to ~/lib/api (identical surface). Part of v0.1.8.
Port the old console (Langfuse-fork) eval surfaces into console2 as native
modules on @hanzo/gui + @hanzogui/lucide-icons-2 — no antd/shadcn/tremor.
Wired to the REAL cloud /v1 backend; honest loading/empty/unavailable states
on 404/503 (NEVER fabricated prompts/datasets/scores).
- Playground (AI): GET /v1/models + POST /v1/chat/completions — fully working
model run (system prompt, message thread, sampling params, token usage).
- Evals (Observe): POST /v1/evals/runs (real per-item run summary) +
GET /v1/evals/scores (real scores list), Run/Scores tabs.
- Datasets (Observe): POST /v1/evals/datasets + /v1/evals/dataset-items (real
create); forward-compatible GET list with honest unavailable card.
- Prompts (AI): forward-compatible GET /v1/prompts probe; honest deep-link card
(no /v1 prompts route mounted yet).
Shared: ModelPicker (one way to pick a gateway model), BackendState (honest
/v1 error → card). API: lib/api/{playground,evals}.ts via the REST client.
Registry: playground+evals stubs upgraded in place (no reorder); prompts+
datasets appended. tsc --noEmit + next build both green.
Port the old console (Langfuse-fork) eval surfaces into console2 as native
modules on @hanzo/gui + @hanzogui/lucide-icons-2 — no antd/shadcn/tremor.
Wired to the REAL cloud /v1 backend; honest loading/empty/unavailable states
on 404/503 (NEVER fabricated prompts/datasets/scores).
- Playground (AI): GET /v1/models + POST /v1/chat/completions — fully working
model run (system prompt, message thread, sampling params, token usage).
- Evals (Observe): POST /v1/evals/runs (real per-item run summary) +
GET /v1/evals/scores (real scores list), Run/Scores tabs.
- Datasets (Observe): POST /v1/evals/datasets + /v1/evals/dataset-items (real
create); forward-compatible GET list with honest unavailable card.
- Prompts (AI): forward-compatible GET /v1/prompts probe; honest deep-link card
(no /v1 prompts route mounted yet).
Shared: ModelPicker (one way to pick a gateway model), BackendState (honest
/v1 error → card). API: lib/api/{playground,evals}.ts via the REST client.
Registry: playground+evals stubs upgraded in place (no reorder); prompts+
datasets appended. tsc --noEmit + next build both green.
Port the old console's observability core (Langfuse-shaped) to native
@hanzo/gui modules:
- Traces: list + detail (overview, I/O, observations, scores) at /o11y
- Sessions: list + detail (overview + traces) at /sessions
- Scores: list at /scores
All read the REAL /v1/o11y endpoints and render honest states (loading /
runtime-initializing / empty) on 503/404 — never fabricated traces or
charts. Replaces the Traces deep-link placeholder (ObservabilityModule
removed); appends Sessions + Scores entries (no reorder of existing).
tsc --noEmit and next build both pass.
Port the old console's observability core (Langfuse-shaped) to native
@hanzo/gui modules:
- Traces: list + detail (overview, I/O, observations, scores) at /o11y
- Sessions: list + detail (overview + traces) at /sessions
- Scores: list at /scores
All read the REAL /v1/o11y endpoints and render honest states (loading /
runtime-initializing / empty) on 503/404 — never fabricated traces or
charts. Replaces the Traces deep-link placeholder (ObservabilityModule
removed); appends Sessions + Scores entries (no reorder of existing).
tsc --noEmit and next build both pass.
DRY pieces for the o11y surfaces: pure formatters (date/latency/cost/
score value/JSON), shared detail parts (DetailRow/Badge/Tags/JsonCard),
the honest RuntimeNotice (503 not-initialized / 404 unrouted / access /
error), and the list Pager. No fabricated data.
DRY pieces for the o11y surfaces: pure formatters (date/latency/cost/
score value/JSON), shared detail parts (DetailRow/Badge/Tags/JsonCard),
the honest RuntimeNotice (503 not-initialized / 404 unrouted / access /
error), and the list Pager. No fabricated data.
Typed client for the /v1/o11y surface over the plain-REST transport
(restGet/v1Url): list endpoints return { data, meta }, detail endpoints
one object. 503/404 surface as typed ApiError so callers render honest
states. Tenancy is server-side (cookie credentials only).
Typed client for the /v1/o11y surface over the plain-REST transport
(restGet/v1Url): list endpoints return { data, meta }, detail endpoints
one object. 503/404 surface as typed ApiError so callers render honest
states. Tenancy is server-side (cookie credentials only).
Port hanzoai/console's deep settings + models pages into console2 as native
modules wired to the REAL /v1 + /v1/iam endpoints. Honest loading/404/401/503
states everywhere — never fabricates keys, models, or settings.
New modules (registry, appended — no reorder):
- Model Catalog (AI): real GET /v1/models + best-effort /v1/pricing/models
overlay; provider filter, premium tier, $/Mtok columns. Read-only catalog
(routing lives in Models, credentials in Providers).
- API Keys (Dev): the account's real cloud credential (accessKey/accessSecret
from get-account), masked by default with explicit reveal + copy; honest
"managed by gateway" state when no key material is exposed to the browser.
- Settings (Security): tabbed General / API Keys / Members / Branding. General
reads real account (get-account) + org (/v1/iam/get-organization); Members
reads /v1/iam/get-users; API Keys embeds the shared ApiKeysView (DRY);
Branding shows the real per-host runtime config. Identity mutations deep-link
to IAM rather than being re-implemented.
Shared + API:
- ui/States.tsx: one honest async-state renderer (honestError + ErrorState +
asApiError) with per-surface copy overrides. AdminModule refactored onto it
(removes its duplicate honestError/ErrorCard).
- api/models-catalog.ts: CloudModelApi over the REST (non-envelope) /v1/models.
- api/admin.ts: IamAdminApi.organization(name) single-org getter.
Shell: top-bar account name now links to /settings (canonical account menu).
Gates: tsc --noEmit exit 0; next build exit 0.
Skipped (no real console2 backend — porting as shells would be slop): Langfuse
feature-flags (2 internal flags), developer-tools (Langfuse-branded copy),
automations/batch-exports/integrations (tRPC+Prisma only). Members/Audit/
Secrets/LLM-connections/Billing already exist as IAM/Audit/KMS/Providers/Cost.
Port hanzoai/console's deep settings + models pages into console2 as native
modules wired to the REAL /v1 + /v1/iam endpoints. Honest loading/404/401/503
states everywhere — never fabricates keys, models, or settings.
New modules (registry, appended — no reorder):
- Model Catalog (AI): real GET /v1/models + best-effort /v1/pricing/models
overlay; provider filter, premium tier, $/Mtok columns. Read-only catalog
(routing lives in Models, credentials in Providers).
- API Keys (Dev): the account's real cloud credential (accessKey/accessSecret
from get-account), masked by default with explicit reveal + copy; honest
"managed by gateway" state when no key material is exposed to the browser.
- Settings (Security): tabbed General / API Keys / Members / Branding. General
reads real account (get-account) + org (/v1/iam/get-organization); Members
reads /v1/iam/get-users; API Keys embeds the shared ApiKeysView (DRY);
Branding shows the real per-host runtime config. Identity mutations deep-link
to IAM rather than being re-implemented.
Shared + API:
- ui/States.tsx: one honest async-state renderer (honestError + ErrorState +
asApiError) with per-surface copy overrides. AdminModule refactored onto it
(removes its duplicate honestError/ErrorCard).
- api/models-catalog.ts: CloudModelApi over the REST (non-envelope) /v1/models.
- api/admin.ts: IamAdminApi.organization(name) single-org getter.
Shell: top-bar account name now links to /settings (canonical account menu).
Gates: tsc --noEmit exit 0; next build exit 0.
Skipped (no real console2 backend — porting as shells would be slop): Langfuse
feature-flags (2 internal flags), developer-tools (Langfuse-branded copy),
automations/batch-exports/integrations (tRPC+Prisma only). Members/Audit/
Secrets/LLM-connections/Billing already exist as IAM/Audit/KMS/Providers/Cost.
main already supersedes it: same real platform contract (/v1/apps +
/v1/org/{org}/cluster) PLUS X-Org-Id (resource modules), Bot/Wallet honest
states, Clusters real-contract rewrite, and the PaaS token fix. Recording the
integration so the line is single; cutting v0.1.8 as the cumulative release.
main already supersedes it: same real platform contract (/v1/apps +
/v1/org/{org}/cluster) PLUS X-Org-Id (resource modules), Bot/Wallet honest
states, Clusters real-contract rewrite, and the PaaS token fix. Recording the
integration so the line is single; cutting v0.1.8 as the cumulative release.
Live Playwright verification surfaced real wiring bugs; fixed all in console2
(honest states everywhere, no fakes):
- client.ts: stamp X-Org-Id (brand org) on every cloud call — the provisioning
service 403'd 'X-Org-Id required' on the direct cloud-api path. Fixes the 7
data modules (vector/sql/kv/s3/datastore/docdb/search) → real data / empty.
- platform.ts: rework to the REAL platform contract — GET /v1/apps (apps
inventory) + GET|POST /v1/org/{org}/cluster; drop dead /v1/clusters + k8s
passthrough. Status = real health board; Kubernetes = real workloads per
cluster; Clusters = real dedicated-DOKS list (honest empty).
- platform/state.tsx: upstream 401/403 → honest 'not configured'.
- BotModule: /v1/bot/health 404 → honest 'not routed on this host'.
- WalletModule: /v1/billing/balance 404 → honest 'not available'.
- StatusTag: understand platform health verdicts (green/yellow/red).
typecheck + build clean. Operator CR token repointed (universe) to the correct
paas-console-token (the old hanzo-paas/MASTERTOKEN is rejected by platform).
Live Playwright verification surfaced real wiring bugs; fixed all in console2
(honest states everywhere, no fakes):
- client.ts: stamp X-Org-Id (brand org) on every cloud call — the provisioning
service 403'd 'X-Org-Id required' on the direct cloud-api path. Fixes the 7
data modules (vector/sql/kv/s3/datastore/docdb/search) → real data / empty.
- platform.ts: rework to the REAL platform contract — GET /v1/apps (apps
inventory) + GET|POST /v1/org/{org}/cluster; drop dead /v1/clusters + k8s
passthrough. Status = real health board; Kubernetes = real workloads per
cluster; Clusters = real dedicated-DOKS list (honest empty).
- platform/state.tsx: upstream 401/403 → honest 'not configured'.
- BotModule: /v1/bot/health 404 → honest 'not routed on this host'.
- WalletModule: /v1/billing/balance 404 → honest 'not available'.
- StatusTag: understand platform health verdicts (green/yellow/red).
typecheck + build clean. Operator CR token repointed (universe) to the correct
paas-console-token (the old hanzo-paas/MASTERTOKEN is rejected by platform).
The PaaS modules targeted an assumed platform surface (/v1/clusters,
/v1/org/{org}/cluster/{id}/k8s/{kind}) that does not exist — the live
platform.hanzo.ai/v1 REST API serves /v1/org/{org}/cluster (org-scoped
dedicated clusters) and /v1/apps (the workload/drift board). Re-point the
single data layer (src/lib/api/platform.ts) at the real endpoints:
- listClusters → /v1/org/{org}/cluster (unwrap {clusters}); org from config.
- add AppsApi.listApps → /v1/apps (unwrap {apps}) — the live deploy data.
- drop the dead k8s-browse client (no backend) + CLUSTER_ROUTES guess.
Status + Kubernetes now render the real /v1/apps workloads (cluster,
namespace, image, health) instead of gating on a non-existent k8s-browse
behind a (for hanzo) empty dedicated-cluster list. StatusTag tones the
drift-board health (healthy/warning/down). Auth is unchanged: the /paas
proxy already sends Authorization: Bearer; the fix is the token VALUE
(operator CR → paas-console-token) + these paths.
The PaaS modules targeted an assumed platform surface (/v1/clusters,
/v1/org/{org}/cluster/{id}/k8s/{kind}) that does not exist — the live
platform.hanzo.ai/v1 REST API serves /v1/org/{org}/cluster (org-scoped
dedicated clusters) and /v1/apps (the workload/drift board). Re-point the
single data layer (src/lib/api/platform.ts) at the real endpoints:
- listClusters → /v1/org/{org}/cluster (unwrap {clusters}); org from config.
- add AppsApi.listApps → /v1/apps (unwrap {apps}) — the live deploy data.
- drop the dead k8s-browse client (no backend) + CLUSTER_ROUTES guess.
Status + Kubernetes now render the real /v1/apps workloads (cluster,
namespace, image, health) instead of gating on a non-existent k8s-browse
behind a (for hanzo) empty dedicated-cluster list. StatusTag tones the
drift-board health (healthy/warning/down). Auth is unchanged: the /paas
proxy already sends Authorization: Bearer; the fix is the token VALUE
(operator CR → paas-console-token) + these paths.
Rebuild the product catalog to the canonical ten categories, in order:
AI · Compute · Data · Network · Security · Dev · Deploy · Observe · Web3 · Apps.
66 entries; each names its Google Cloud equivalent. Honest 3-state enablement:
enabled (23, in-console modules) / external (16, live Hanzo surfaces) / soon (27).
Every real working module is preserved (recategorized, not broken).
Add Status (Observe): live health of every Hanzo service across clusters, from
REAL data only — composes PlatformApi.listClusters + KubernetesApi deployments
over the /paas control plane, with honest not-configured/unavailable/empty
states and no fabricated dots.
Decomplect: one coming-soon surface for all soon leaves; delete the dead
duplicate PaaS client (PlatformModule + lib/paas) and the unused coming-soon
factory. Release v0.1.6.
Rebuild the product catalog to the canonical ten categories, in order:
AI · Compute · Data · Network · Security · Dev · Deploy · Observe · Web3 · Apps.
66 entries; each names its Google Cloud equivalent. Honest 3-state enablement:
enabled (23, in-console modules) / external (16, live Hanzo surfaces) / soon (27).
Every real working module is preserved (recategorized, not broken).
Add Status (Observe): live health of every Hanzo service across clusters, from
REAL data only — composes PlatformApi.listClusters + KubernetesApi deployments
over the /paas control plane, with honest not-configured/unavailable/empty
states and no fabricated dots.
Decomplect: one coming-soon surface for all soon leaves; delete the dead
duplicate PaaS client (PlatformModule + lib/paas) and the unused coming-soon
factory. Release v0.1.6.
Phase 5 — add the Observability category with truthful entries, no fake charts:
- Observability (/o11y): console-native module that probes the REAL /v1/o11y
runtime and reports status (online / not-initialized 503 / not-routed 404 /
access / error), deep-links to the full observability surface for traces,
evals, and prompts, and marks the native in-console browser as coming
(HIP-0106). Never renders placeholder telemetry.
- Insights (external) + Analytics (relocated here) round out the category.
This is the staged first step for the largest old-console surface; the deeper
native port is honestly deferred, not faked.
Phase 5 — add the Observability category with truthful entries, no fake charts:
- Observability (/o11y): console-native module that probes the REAL /v1/o11y
runtime and reports status (online / not-initialized 503 / not-routed 404 /
access / error), deep-links to the full observability surface for traces,
evals, and prompts, and marks the native in-console browser as coming
(HIP-0106). Never renders placeholder telemetry.
- Insights (external) + Analytics (relocated here) round out the category.
This is the staged first step for the largest old-console surface; the deeper
native port is honestly deferred, not faked.
Phase 4 — one platform transport: route ALL control-plane calls through the
same-origin /paas proxy (server-side token injection, no CORS, honest 501
when unset) instead of direct cross-origin platform.hanzo.ai.
- platform.ts: clusters now go via /paas; add KubernetesApi over
/v1/org/{org}/cluster/{id}/k8s/{deployments,pods,services,ingresses,events,crs}.
- KubernetesModule: cluster picker + resource tabs, defensive per-kind columns,
honest loading/not-configured/backend-unavailable/error/empty states.
- ClustersModule: flip 'soon' -> real; render the shared honest state card for
not-configured (501) / backend-unavailable (404).
- New shared platform/state.tsx interprets /paas errors one way.
Phase 4 — one platform transport: route ALL control-plane calls through the
same-origin /paas proxy (server-side token injection, no CORS, honest 501
when unset) instead of direct cross-origin platform.hanzo.ai.
- platform.ts: clusters now go via /paas; add KubernetesApi over
/v1/org/{org}/cluster/{id}/k8s/{deployments,pods,services,ingresses,events,crs}.
- KubernetesModule: cluster picker + resource tabs, defensive per-kind columns,
honest loading/not-configured/backend-unavailable/error/empty states.
- ClustersModule: flip 'soon' -> real; render the shared honest state card for
not-configured (501) / backend-unavailable (404).
- New shared platform/state.tsx interprets /paas errors one way.
Phase 3 — wire the console to the existing identity/secrets subsystems over
the canonical /v1 surface (HIP-0111), each an honest module:
- Identity (/iam): tabbed Organizations / Users / Roles (RBAC) over Hanzo
IAM /v1/iam/get-{organizations,users,roles} (casdoor envelope). One generic
AdminListView drives all three; 404/401/empty are explicit honest states.
- Audit (/audit): identity & access event log over /v1/iam/get-records.
- Secrets (/kms): KMS is zero-knowledge (encrypted names+values, token/ZAP
auth, no list-values endpoint) — the module states the model, probes the
real /v1/kms surface to report reachability, and deep-links to the KMS
console. It never fabricates a secret table.
iam/kms flip from external links to modules; ext.iam/ext.kms removed.
Phase 3 — wire the console to the existing identity/secrets subsystems over
the canonical /v1 surface (HIP-0111), each an honest module:
- Identity (/iam): tabbed Organizations / Users / Roles (RBAC) over Hanzo
IAM /v1/iam/get-{organizations,users,roles} (casdoor envelope). One generic
AdminListView drives all three; 404/401/empty are explicit honest states.
- Audit (/audit): identity & access event log over /v1/iam/get-records.
- Secrets (/kms): KMS is zero-knowledge (encrypted names+values, token/ZAP
auth, no list-values endpoint) — the module states the model, probes the
real /v1/kms surface to report reachability, and deep-links to the KMS
console. It never fabricates a secret table.
iam/kms flip from external links to modules; ext.iam/ext.kms removed.
Replace the ad-hoc AI/Data/Apps/Identity/Infrastructure/Commerce grouping
with the exact nine categories + order from the marketing site product
dropdown (navigation-data.ts productsNav): AI & Agents, Developer, Apps,
Compute, Data, Async, Platform, Observability, Web3. One taxonomy across
every Hanzo surface. Empty groups don't render (catalogByCategory skips them).
Replace the ad-hoc AI/Data/Apps/Identity/Infrastructure/Commerce grouping
with the exact nine categories + order from the marketing site product
dropdown (navigation-data.ts productsNav): AI & Agents, Developer, Apps,
Compute, Data, Async, Platform, Observability, Web3. One taxonomy across
every Hanzo surface. Empty groups don't render (catalogByCategory skips them).
- WalletModule (Commerce): connect a non-custodial wallet on Hanzo Mainnet
(36900) via ethers/EIP-1193, show wallet HUSD + cloud credit balances, and
top up credit with HUSD. Honest states throughout (no wallet, HUSD greenfield,
chain unreachable, endpoint unconfigured) — never a fabricated balance.
- src/lib/wallet/hanzo-evm.ts: one canonical Hanzo Mainnet + HUSD definition
(ethers v6), env-overridable RPC; HUSD address is public (NEXT_PUBLIC), never
a secret.
- src/lib/api/wallet.ts: cloud balance via the real GET /v1/billing/balance, and
recordWalletTopup → the console's own POST /billing/topup/wallet.
- app/billing/topup/wallet/route.ts: server route (mirrors /paas) — verifies the
HUSD transfer on-chain, then records to commerce as a husd crypto payment and
credits the balance. Hosted here because billing.hanzo.ai is a static export
and commerce is owned elsewhere. Server-only config (KMS, never NEXT_PUBLIC).
- registry: wallet entry; api/index: WalletApi export. Adds ethers 6.17.0.
- WalletModule (Commerce): connect a non-custodial wallet on Hanzo Mainnet
(36900) via ethers/EIP-1193, show wallet HUSD + cloud credit balances, and
top up credit with HUSD. Honest states throughout (no wallet, HUSD greenfield,
chain unreachable, endpoint unconfigured) — never a fabricated balance.
- src/lib/wallet/hanzo-evm.ts: one canonical Hanzo Mainnet + HUSD definition
(ethers v6), env-overridable RPC; HUSD address is public (NEXT_PUBLIC), never
a secret.
- src/lib/api/wallet.ts: cloud balance via the real GET /v1/billing/balance, and
recordWalletTopup → the console's own POST /billing/topup/wallet.
- app/billing/topup/wallet/route.ts: server route (mirrors /paas) — verifies the
HUSD transfer on-chain, then records to commerce as a husd crypto payment and
credits the balance. Hosted here because billing.hanzo.ai is a static export
and commerce is owned elsewhere. Server-only config (KMS, never NEXT_PUBLIC).
- registry: wallet entry; api/index: WalletApi export. Adds ethers 6.17.0.
'Interstitial screens to discover guides/docs/how-tos + link to GitHub OSS for
each product' + the OSS-gets-paid hook:
- /discover/<id> route + ProductInterstitial: identity + open/get-started CTA,
Docs & guides + Open-source (GitHub) link cards, and an 'Open source gets paid'
card stating the model (25% of cloud revenue -> OSS contributors, computed from
each deployment's SBOM, settled on-chain in HUSD) with Contribute + OSS-dividends
links. Catalog cards gain a Learn-more (info) affordance; non-enabled Get-started
routes to the interstitial.
- OSS_PROGRAM constant (one source of truth: 25% / HUSD / SBOM / dividends dashboard),
aligned with hanzo.ai sbomRevenueConfig + the commerce contributor/payout system.
tsc clean; next build green (/discover/[id] live).
'Interstitial screens to discover guides/docs/how-tos + link to GitHub OSS for
each product' + the OSS-gets-paid hook:
- /discover/<id> route + ProductInterstitial: identity + open/get-started CTA,
Docs & guides + Open-source (GitHub) link cards, and an 'Open source gets paid'
card stating the model (25% of cloud revenue -> OSS contributors, computed from
each deployment's SBOM, settled on-chain in HUSD) with Contribute + OSS-dividends
links. Catalog cards gain a Learn-more (info) affordance; non-enabled Get-started
routes to the interstitial.
- OSS_PROGRAM constant (one source of truth: 25% / HUSD / SBOM / dividends dashboard),
aligned with hanzo.ai sbomRevenueConfig + the commerce contributor/payout system.
tsc clean; next build green (/discover/[id] live).
Per directive 'use proper semver for all, no sha': build-image.yml now tags
ghcr.io/hanzoai/console2 with the semver version only — a v* git tag publishes
that exact version, a main push publishes v<package.json version> (bump to
release). Drops the sha-<sha7> and floating :latest tags. Bump 0.1.1 -> 0.1.2
(GCP-grade resource detail + Plans & Pricing + Team launcher).
Per directive 'use proper semver for all, no sha': build-image.yml now tags
ghcr.io/hanzoai/console2 with the semver version only — a v* git tag publishes
that exact version, a main push publishes v<package.json version> (bump to
release). Drops the sha-<sha7> and floating :latest tags. Bump 0.1.1 -> 0.1.2
(GCP-grade resource detail + Plans & Pricing + Team launcher).
The 'manage/create databases ala GCP' + 'discover, enable, pay' surface,
all on REAL backend contracts (no invented controls):
- ResourceModule gains an instance DETAIL view (list+detail in one component,
mirroring ProvidersModule's params.name): click a resource -> GET /v1/<kind>/<name>
overview (status/kind/endpoint/user/db/created) + connection guidance + danger-zone
delete. New resourceRoutes() helper binds index + :name to one instance (DRY);
the 7 data products (sql/vector/datastore/kv/search/s3/docdb) use it. Resources
are serverless/create-by-name (POST /v1/<kind> takes only {name}) — no fake
tier/size/region knobs.
- PlansModule: GCP-style Plans & Pricing on the live rate card (GET /v1/pricing):
per-tier cards (vCPU/RAM/SSD/transfer, monthly+hourly, feature bullets, free/popular
badges) + block-storage metering. Paying delegates to config.billingUrl (the one
money surface, never reimplemented). New typed PlansApi (plans.ts).
- Team launcher: hanzo.team catalog entry (Apps, external team.hanzo.ai).
tsc --noEmit clean; next build green (9/9).
The 'manage/create databases ala GCP' + 'discover, enable, pay' surface,
all on REAL backend contracts (no invented controls):
- ResourceModule gains an instance DETAIL view (list+detail in one component,
mirroring ProvidersModule's params.name): click a resource -> GET /v1/<kind>/<name>
overview (status/kind/endpoint/user/db/created) + connection guidance + danger-zone
delete. New resourceRoutes() helper binds index + :name to one instance (DRY);
the 7 data products (sql/vector/datastore/kv/search/s3/docdb) use it. Resources
are serverless/create-by-name (POST /v1/<kind> takes only {name}) — no fake
tier/size/region knobs.
- PlansModule: GCP-style Plans & Pricing on the live rate card (GET /v1/pricing):
per-tier cards (vCPU/RAM/SSD/transfer, monthly+hourly, feature bullets, free/popular
badges) + block-storage metering. Paying delegates to config.billingUrl (the one
money surface, never reimplemented). New typed PlansApi (plans.ts).
- Team launcher: hanzo.team catalog entry (Apps, external team.hanzo.ai).
tsc --noEmit clean; next build green (9/9).
Flip the existing 'bot' catalog entry from an external link to an in-console
module. New BotModule reports live gateway status from /v1/bot/health (via a
small BotApi on the REST layer, since the bot speaks plain JSON, not the
casibase envelope) and deep-links the operator surfaces (bot home, control UI,
docs, source). Backend (hanzoai/bot -> bot-gateway) is already routed at
/v1/bot/* by the unified gateway.
Flip the existing 'bot' catalog entry from an external link to an in-console
module. New BotModule reports live gateway status from /v1/bot/health (via a
small BotApi on the REST layer, since the bot speaks plain JSON, not the
casibase envelope) and deep-links the operator surfaces (bot home, control UI,
docs, source). Backend (hanzoai/bot -> bot-gateway) is already routed at
/v1/bot/* by the unified gateway.
Found via testing: cloud.hanzo.ai serves the SPA catch-all (200 text/html for any /v1 path), NOT the backend; the real /v1 is behind the unified gateway api.hanzo.ai (hanzoai/ingress→hanzoai/gateway v2.13.0 → cloud / separate services / per-org k8s, rate-limited+gated+priced). Browser uses same-origin /v1 (each console host's ingress proxies to the gateway); this SSR fallback now points at the gateway.
Found via testing: cloud.hanzo.ai serves the SPA catch-all (200 text/html for any /v1 path), NOT the backend; the real /v1 is behind the unified gateway api.hanzo.ai (hanzoai/ingress→hanzoai/gateway v2.13.0 → cloud / separate services / per-org k8s, rate-limited+gated+priced). Browser uses same-origin /v1 (each console host's ingress proxies to the gateway); this SSR fallback now points at the gateway.
Resolves the brand at RUNTIME from the request hostname (console.hanzo.ai→hanzo, console.lux.cloud→lux, console.zoo.cloud→zoo). Tenancy: ONE cloud /v1 backend serves all orgs (same-origin per host → first-party cookie, no CORS), each brand authenticates against its OWN live IAM (hanzo.id / lux.id / zoolabs.id / pars.id; client_id <org>-cloud per HIP-0111). config is a brand-aware Proxy so the /v1 client + IAM SDK go per-host with no consumer changes; cloudUrl is same-origin (window.origin); NEXT_PUBLIC_* still override. Dockerfile + CI no longer bake NEXT_PUBLIC_* (that pinned one brand) → one brand-agnostic image (sha-<sha7>+latest). Fixed a 'Hanzo' subtitle brand-leak. Verified: tsc clean + next build green. NOTE: cloud backend must accept all brand issuers/auds; each console host's ingress must proxy /v1 to the backend + register the redirect URI in that brand's IAM app.
Resolves the brand at RUNTIME from the request hostname (console.hanzo.ai→hanzo, console.lux.cloud→lux, console.zoo.cloud→zoo). Tenancy: ONE cloud /v1 backend serves all orgs (same-origin per host → first-party cookie, no CORS), each brand authenticates against its OWN live IAM (hanzo.id / lux.id / zoolabs.id / pars.id; client_id <org>-cloud per HIP-0111). config is a brand-aware Proxy so the /v1 client + IAM SDK go per-host with no consumer changes; cloudUrl is same-origin (window.origin); NEXT_PUBLIC_* still override. Dockerfile + CI no longer bake NEXT_PUBLIC_* (that pinned one brand) → one brand-agnostic image (sha-<sha7>+latest). Fixed a 'Hanzo' subtitle brand-leak. Verified: tsc clean + next build green. NOTE: cloud backend must accept all brand issuers/auds; each console host's ingress must proxy /v1 to the backend + register the redirect URI in that brand's IAM app.
The mainnet branch wrote a two-line tags value with $'\n', which GitHub
Actions rejects for key=value outputs ("Invalid format ...:latest") —
so every Build Docker Image run failed at 'Compute per-env config' and
no image was ever produced by CI. Use the multi-line heredoc output form
so build-push-action receives both newline-separated tags.
The mainnet branch wrote a two-line tags value with $'\n', which GitHub
Actions rejects for key=value outputs ("Invalid format ...:latest") —
so every Build Docker Image run failed at 'Compute per-env config' and
no image was ever produced by CI. Use the multi-line heredoc output form
so build-push-action receives both newline-separated tags.
NEXT_PUBLIC_IAM_URL is inlined at build time, so the deployed image sent
the browser authorize redirect to https://iam.hanzo.ai — which mints
iss=https://iam.hanzo.ai, a different issuer than the canonical
https://hanzo.id that the cloud /v1 backend validates. Sign-in dropped
on iam.hanzo.ai and never round-tripped back to console2.
- src/config, .env.example, Dockerfile ARG, mainnet CI build-arg: point
the browser at https://hanzo.id (the value baked into the image).
- Align iamAppName/iamClientId source defaults to hanzo-cloud (was the
stale hanzo-console / empty), matching the cloud-api backend binding
(iamApplication / IAM_AUDIENCE = hanzo-cloud). A default build now
targets the correct app instead of a non-existent one with no client.
App/client stay hanzo-cloud on purpose: console2 is a front-end of the
shared cloud /v1 backend, which exchanges the code and validates aud as
hanzo-cloud — it is not its own IAM principal.
NEXT_PUBLIC_IAM_URL is inlined at build time, so the deployed image sent
the browser authorize redirect to https://iam.hanzo.ai — which mints
iss=https://iam.hanzo.ai, a different issuer than the canonical
https://hanzo.id that the cloud /v1 backend validates. Sign-in dropped
on iam.hanzo.ai and never round-tripped back to console2.
- src/config, .env.example, Dockerfile ARG, mainnet CI build-arg: point
the browser at https://hanzo.id (the value baked into the image).
- Align iamAppName/iamClientId source defaults to hanzo-cloud (was the
stale hanzo-console / empty), matching the cloud-api backend binding
(iamApplication / IAM_AUDIENCE = hanzo-cloud). A default build now
targets the correct app instead of a non-existent one with no client.
App/client stay hanzo-cloud on purpose: console2 is a front-end of the
shared cloud /v1 backend, which exchanges the code and validates aud as
hanzo-cloud — it is not its own IAM principal.
Job 2: reorganize the catalog into the canonical 10-category CLOUD AXIS
(AI/Compute/Data/Network/Security/Dev/Deploy/Observe/Chain/Apps) so console2
reads like a cloud console. Three entry kinds (module/external/soon) => zero
dead links, zero fakes; 'soon' primitives render an honest ComingSoon overview.
Job 3: PaaS embedded natively under Deploy (PlatformModule) wired to the real
platform.hanzo.ai control plane via a same-origin /paas proxy (service token
server-side from KMS). Real apps + declared/running/drift + redeploy; honest
loading/not-configured/empty states.
Job 4: catalog honest by construction; PaaS shows only real data. No placeholder
cards, demo projects, or lorem stats.
Job 2: reorganize the catalog into the canonical 10-category CLOUD AXIS
(AI/Compute/Data/Network/Security/Dev/Deploy/Observe/Chain/Apps) so console2
reads like a cloud console. Three entry kinds (module/external/soon) => zero
dead links, zero fakes; 'soon' primitives render an honest ComingSoon overview.
Job 3: PaaS embedded natively under Deploy (PlatformModule) wired to the real
platform.hanzo.ai control plane via a same-origin /paas proxy (service token
server-side from KMS). Real apps + declared/running/drift + redeploy; honest
loading/not-configured/empty states.
Job 4: catalog honest by construction; PaaS shows only real data. No placeholder
cards, demo projects, or lorem stats.
Union merge — feature's categorized catalog architecture is canonical, with
main's data/storage products + status badges folded in (lose nothing):
- registry.tsx: feature's CatalogEntry discriminated union (category + kind +
admin + derived productModules) as the base; FOLD IN main's data/storage cloud
products (vector, sql, datastore, kv, search, s3, docdb, base, clusters) as
categorized 'module' entries via resourceModule/comingSoon — these are the
console frontend for cloud's /v1 provisioning control plane. Extend
ProductStatus to 'enabled'|'available'|'soon'|'waitlist' and add repo? so the
folded products keep their status badges. Resolve the id 'search' collision:
managed Search data product keeps id 'search' (owns the route, maps to the
provisioning kind); feature's external search.hanzo.ai becomes 'ai-search'.
- DashboardShell.tsx: feature's Pinned + categorized NavRow shell; FOLD main's
SOON/WAITLIST status badge into NavRow (feature had dropped it).
- page.tsx: feature's grouped ProductCard grid; extend StatusBadge to render
Soon/Waitlist (blue/yellow) alongside Enabled/Available (folds main's badge).
Verify: tsc --noEmit strict CLEAN; next build green (6/6 pages). The repo's
untracked PaaS WIP (ComingSoon/PlatformModule/paas — another agent's, in neither
branch) is left untouched and excluded from this commit.
Union merge — feature's categorized catalog architecture is canonical, with
main's data/storage products + status badges folded in (lose nothing):
- registry.tsx: feature's CatalogEntry discriminated union (category + kind +
admin + derived productModules) as the base; FOLD IN main's data/storage cloud
products (vector, sql, datastore, kv, search, s3, docdb, base, clusters) as
categorized 'module' entries via resourceModule/comingSoon — these are the
console frontend for cloud's /v1 provisioning control plane. Extend
ProductStatus to 'enabled'|'available'|'soon'|'waitlist' and add repo? so the
folded products keep their status badges. Resolve the id 'search' collision:
managed Search data product keeps id 'search' (owns the route, maps to the
provisioning kind); feature's external search.hanzo.ai becomes 'ai-search'.
- DashboardShell.tsx: feature's Pinned + categorized NavRow shell; FOLD main's
SOON/WAITLIST status badge into NavRow (feature had dropped it).
- page.tsx: feature's grouped ProductCard grid; extend StatusBadge to render
Soon/Waitlist (blue/yellow) alongside Enabled/Available (folds main's badge).
Verify: tsc --noEmit strict CLEAN; next build green (6/6 pages). The repo's
untracked PaaS WIP (ComingSoon/PlatformModule/paas — another agent's, in neither
branch) is left untouched and excluded from this commit.
* feat(products): register full data/storage catalog + enablement status
Adds `status` ('enabled'|'soon'|'waitlist') + `repo` to every ProductModule so
the console tracks enablement of all Hanzo cloud products in ONE place. Registers
the OSS-Google-Cloud data/storage suite as modules — Vector, SQL, Datastore, KV,
Search, S3, Base (soon) and DocDB (waitlist) — each a ZAP-native Hanzo fork mapped
to its repo, with a ComingSoon placeholder (repo link + status) until its admin
module lands. Nav + dashboard cards render the status badge.
Products → repos: Vector=hanzoai/vector (Qdrant-compat), SQL=hanzoai/sql,
Datastore=hanzoai/datastore (ClickHouse-compat), KV=hanzoai/kv (Redis-compat),
Search=hanzoai/search, S3=hanzoai/s3, Base=hanzoai/base, DocDB=hanzoai/docdb.
* feat(products): add Clusters module (shared Hanzo Cloud vs BYO DOKS)
The data/storage products (Vector/SQL/Datastore/KV/Search/S3/Base/DocDB) are
all live on hanzo-k8s via the operator. Adds the one new control-plane surface
the platform needs: Clusters — choose where workloads run (shared multi-tenant
Hanzo Cloud, or your own/Hanzo-provisioned DOKS cluster, reconciled by the same
operator). Deploy-any-repo stays under Applications.
* feat(products): working data/storage + clusters admin modules
Replace the comingSoon() placeholders for sql/vector/datastore/kv/search/s3/
docdb with a DRY resourceModule() factory over the provisioning REST contract
(POST/GET/DELETE /v1/<kind>): list, create-with-once-shown connectionString +
password reveal ("store this now"), and per-row delete. Tenancy is server-side
(gateway injects X-Org-Id), so the browser sends cookie creds only.
- lib/api/client.ts: plain-REST helpers (restGet/restPost/restDelete + v1Url)
beside the casibase envelope path — provisioning + platform speak raw JSON /
201 / 204 / DELETE, reusing the same cookie creds + ApiError. One transport.
- lib/api/provisioning.ts: ProvisioningApi keyed by ResourceKind.
- lib/api/platform.ts: PlatformApi (DOKS clusters) with centralized
CLUSTER_ROUTES + DOKS region/size options; base = NEXT_PUBLIC_PLATFORM_URL.
- components/products/ResourceModule.tsx: the factory (list/create/delete,
copyable masked secret reveal, slug validation, loading/empty/error).
- components/products/ClustersModule.tsx: list + provision DOKS + attach (name
+ kubeconfig) against the platform control plane.
- components/ui/StatusTag.tsx, lib/slug.ts: shared/DRY across both modules.
- registry: swap routes to the working modules and clear 'soon'/'waitlist'
status so nav badges clear. Base stays a placeholder (no single-resource).
- fix two pre-existing type errors in ComingSoonModule (maxWidth->maxW,
theme active->blue) so the branch typechecks clean.
kind map: sql->databases, vector->vector, datastore->datastore, kv->kv,
search->search, s3->storage, docdb->docdb.
Verified: npm ci + tsc --noEmit => 0 errors (CI-equivalent flat install).
* console: native product naming + gate Clusters to coming-soon
Native naming (Hanzo brand rule — product name only, no upstream OSS
name in any surface):
- ResourceKind wire kinds align to the cloud /v1 contract exactly:
databases→sql, storage→s3 (vector/datastore/kv/search/docdb unchanged).
- Strip every upstream name from product descriptions + connectionHints
(Postgres/Qdrant/ClickHouse/Redis/Meilisearch/Mongo/-compatible → the
Hanzo product name). Zero forbidden names remain in registry.tsx.
Clusters: register as status:'soon' rendering the coming-soon placeholder
(repo hanzoai/operator). The platform attach/provision endpoints in
platform.ts are unconfirmed (PR not merged), so we don't ship a button to
a non-existent endpoint. ClustersModule.tsx + platform.ts stay in the tree
(unreferenced from the live route) to flip back to enabled in one line once
the platform surface lands. Data products (sql/vector/datastore/kv/search/
s3/docdb) stay ENABLED — their /v1 kinds are real and shipping now.
tsc --noEmit: clean.
---------
Co-authored-by: zeekay <z@zeekay.io>
* feat(products): register full data/storage catalog + enablement status
Adds `status` ('enabled'|'soon'|'waitlist') + `repo` to every ProductModule so
the console tracks enablement of all Hanzo cloud products in ONE place. Registers
the OSS-Google-Cloud data/storage suite as modules — Vector, SQL, Datastore, KV,
Search, S3, Base (soon) and DocDB (waitlist) — each a ZAP-native Hanzo fork mapped
to its repo, with a ComingSoon placeholder (repo link + status) until its admin
module lands. Nav + dashboard cards render the status badge.
Products → repos: Vector=hanzoai/vector (Qdrant-compat), SQL=hanzoai/sql,
Datastore=hanzoai/datastore (ClickHouse-compat), KV=hanzoai/kv (Redis-compat),
Search=hanzoai/search, S3=hanzoai/s3, Base=hanzoai/base, DocDB=hanzoai/docdb.
* feat(products): add Clusters module (shared Hanzo Cloud vs BYO DOKS)
The data/storage products (Vector/SQL/Datastore/KV/Search/S3/Base/DocDB) are
all live on hanzo-k8s via the operator. Adds the one new control-plane surface
the platform needs: Clusters — choose where workloads run (shared multi-tenant
Hanzo Cloud, or your own/Hanzo-provisioned DOKS cluster, reconciled by the same
operator). Deploy-any-repo stays under Applications.
* feat(products): working data/storage + clusters admin modules
Replace the comingSoon() placeholders for sql/vector/datastore/kv/search/s3/
docdb with a DRY resourceModule() factory over the provisioning REST contract
(POST/GET/DELETE /v1/<kind>): list, create-with-once-shown connectionString +
password reveal ("store this now"), and per-row delete. Tenancy is server-side
(gateway injects X-Org-Id), so the browser sends cookie creds only.
- lib/api/client.ts: plain-REST helpers (restGet/restPost/restDelete + v1Url)
beside the casibase envelope path — provisioning + platform speak raw JSON /
201 / 204 / DELETE, reusing the same cookie creds + ApiError. One transport.
- lib/api/provisioning.ts: ProvisioningApi keyed by ResourceKind.
- lib/api/platform.ts: PlatformApi (DOKS clusters) with centralized
CLUSTER_ROUTES + DOKS region/size options; base = NEXT_PUBLIC_PLATFORM_URL.
- components/products/ResourceModule.tsx: the factory (list/create/delete,
copyable masked secret reveal, slug validation, loading/empty/error).
- components/products/ClustersModule.tsx: list + provision DOKS + attach (name
+ kubeconfig) against the platform control plane.
- components/ui/StatusTag.tsx, lib/slug.ts: shared/DRY across both modules.
- registry: swap routes to the working modules and clear 'soon'/'waitlist'
status so nav badges clear. Base stays a placeholder (no single-resource).
- fix two pre-existing type errors in ComingSoonModule (maxWidth->maxW,
theme active->blue) so the branch typechecks clean.
kind map: sql->databases, vector->vector, datastore->datastore, kv->kv,
search->search, s3->storage, docdb->docdb.
Verified: npm ci + tsc --noEmit => 0 errors (CI-equivalent flat install).
* console: native product naming + gate Clusters to coming-soon
Native naming (Hanzo brand rule — product name only, no upstream OSS
name in any surface):
- ResourceKind wire kinds align to the cloud /v1 contract exactly:
databases→sql, storage→s3 (vector/datastore/kv/search/docdb unchanged).
- Strip every upstream name from product descriptions + connectionHints
(Postgres/Qdrant/ClickHouse/Redis/Meilisearch/Mongo/-compatible → the
Hanzo product name). Zero forbidden names remain in registry.tsx.
Clusters: register as status:'soon' rendering the coming-soon placeholder
(repo hanzoai/operator). The platform attach/provision endpoints in
platform.ts are unconfirmed (PR not merged), so we don't ship a button to
a non-existent endpoint. ClustersModule.tsx + platform.ts stay in the tree
(unreferenced from the live route) to flip back to enabled in one line once
the platform surface lands. Data products (sql/vector/datastore/kv/search/
s3/docdb) stay ENABLED — their /v1 kinds are real and shipping now.
tsc --noEmit: clean.
---------
Co-authored-by: zeekay <z@zeekay.io>
Turn console2 into the one place to see, enable, and manage every Hanzo
product, with billing → billing.hanzo.ai for all.
- registry: ONE product catalog (categories + module-vs-external + enablement
status), the single source of truth for nav, overview, and router. Adding a
product = one CatalogEntry.
- favorites: pin products to the sidebar. Built on a new account-backed
preferences layer (usePreferences) — customizations persist to the IAM user
account, so they follow the user across every device/login and product.
localStorage is only a fast-paint cache.
- shell: Pinned section + categorized catalog; exact-match active (no
double-highlight); each row opens (in-console route or external tab) + pin toggle.
- overview: product catalog grouped by category with status, pin, and
Open/Get-started.
- api: AccountApi.updatePreferences → POST /v1/update-preferences (self-scoped).
Typecheck + next build clean.
npm ci failed in CI (node:22-alpine npm 10.9) with EUSAGE 'Missing:
react-native-worklets@0.8.3 from lock file' — @hanzo/gui's react-native
optional/platform deps resolve differently across npm versions, so a
lockfile built by one npm is rejected by another's strict ci. npm install
reconciles deterministically for the build platform.
The ZAP-native data layer (src/lib/zap/{client,transport,providers}.ts)
imports @zap-proto/web/client, @zap-proto/zap, and superjson; declare them
so a clean `npm ci` in CI resolves them (the prior build failed: 'Module
not found: @zap-proto/web/client' because the lockfile lacked them).
Swap the Providers views from the REST `~/lib/api` to the ZAP-native
`~/lib/zap` (one import line each) — proving the @hanzo/gui + @zap-proto/web
go-forward: same call surface, binary ZAP over WebSocket instead of
JSON-over-HTTP, zero view-component changes.
- src/lib/zap/index.ts: barrel re-exporting ProviderApi (= ProviderApiZap),
ApiError, Provider — the drop-in twin of ~/lib/api.
- ProviderListView/ProviderEditView: import from ~/lib/zap.
- providers.ts list(): return { rows, total } to match the REST getList
contract exactly (true drop-in; fixes the list-view shape).
tsc --noEmit (strict) clean. Backs onto cloud's new /zap WS face which
dispatches each call into the same /v1 casibase handlers.
Billing is owned by hanzoai/commerce (backend) + hanzoai/billing (portal at
billing.hanzo.ai) — the console must not reimplement payments/balance. Add an
externalLinks registry (orthogonal to product modules) and render it in the
shell; Billing opens config.billingUrl (NEXT_PUBLIC_BILLING_URL, default
https://billing.hanzo.ai) in a new tab.
The backend auto-creates an anonymous-user session for the chat product, so
get-account returns status:ok even with no real sign-in. As an ADMIN console
that made AuthGate show the dashboard for an unauthenticated visitor, while
admin endpoints (get-providers, etc.) rejected the anon session with 'Please
sign in first'. Treat type==='anonymous-user' as null so the console requires
a real IAM sign-in.
Mirror the Providers pattern: product-module + list/edit views on @hanzo/gui +
typed /v1 API modules, registered in the nav. tsc 0 errors, next build green.
Next.js 15 multi-stage build; NEXT_PUBLIC_* baked at build (same-origin /v1,
IAM client_id=hanzo-cloud to match cloud-api's /v1/signin). Self-hosted ARC
runner, push to ghcr.io/hanzoai/console2.
description:Create a bug report to help us improve
title:"bug: "
labels:["🐞❔ unconfirmed bug"]
body:
- type:textarea
attributes:
label:Describe the bug
description:A clear and concise description of the bug, as well as what you expected to happen when encountering it.
validations:
required:true
- type:textarea
attributes:
label:To reproduce
description:Describe how to reproduce your bug. Please provide detailed steps, code snippets, reproduction repos etc.
validations:
required:true
- type:textarea
attributes:
label:SDK and container versions
description:If you're experiencing an issue with an integration or SDK, please ensure you're using the latest version. If you're self-hosting Langfuse, check that you're running the most recent version. If updating isn't an option, please provide the specific versions you're currently using.
- type:textarea
attributes:
label:Additional information
description:Add any other information related to the bug here, screenshots if applicable.
- type:dropdown
id:contribute
attributes:
label:Are you interested to contribute a fix for this bug?
description:If this is a confirmed bug, the maintainers are happy to support with guidance and review.
<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. -->
Fixes # (issue)
<!-- Please provide a loom video for visual changes to speed up reviews
Loom Video: https://www.loom.com/
-->
## Type of change
<!-- Please delete bullets that are not relevant. -->
- [ ] Bug fix (non-breaking change which fixes an issue)
# required to fetch internal or private CodeQL packs
packages:read
# only required for workflows in private repositories
actions:read
contents:read
strategy:
fail-fast:false
matrix:
include:
- language:javascript-typescript
build-mode:none
# CodeQL supports the following values keywords for 'language': 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
# Use `c-cpp` to analyze code written in C, C++ or both
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
steps:
- name:Checkout repository
uses:actions/checkout@v4
# Initializes the CodeQL tools for scanning.
- name:Initialize CodeQL
uses:github/codeql-action/init@v3
with:
languages:${{ matrix.language }}
build-mode:${{ matrix.build-mode }}
# If you wish to specify custom queries, you can do so here or in a config file.
# By default, queries listed here will override any specified in a config file.
# Prefix the list here with "+" to use these queries and those in the config file.
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
# queries: security-extended,security-and-quality
# If the analyze step fails for one of the languages you are analyzing with
# "We were unable to automatically build your code", modify the matrix above
# to set the build mode to "manual" for that language. Then modify this step
# to build your code.
# ℹ️ Command-line programs to run using the OS shell.
# 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
- if:matrix.build-mode == 'manual'
shell:bash
run:|
echo 'If you are using a "manual" build mode for one or more of the' \
'languages you are analyzing, replace this with the commands to build' \
First off, thanks for taking the time to contribute! ❤️
The best ways to contribute to Langfuse:
- Submit and vote on [Ideas](https://github.com/orgs/langfuse/discussions/categories/ideas)
- Create and comment on [Issues](https://github.com/langfuse/langfuse/issues)
- Open a PR.
We welcome contributions through GitHub pull requests. This document outlines our conventions regarding development workflow, commit message formatting, contact points, and other resources. Our goal is to simplify the process and ensure that your contributions are easily accepted.
We gratefully welcome improvements to documentation ([docs repo](https://github.com/langfuse/langfuse-docs)), the core application (this repo) and the SDKs ([Python](https://github.com/langfuse/langfuse-python), [JS](https://github.com/langfuse/langfuse-js)).
The maintainers are available on [Discord](https://langfuse.com/discord) in case you have any questions.
> And if you like the project, but just don't have time to contribute code, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
>
> - Star the project;
> - Tweet about it;
> - Refer to this project in your project's readme;
> - Submit and vote on [Ideas](https://github.com/orgs/langfuse/discussions/categories/ideas);
> - Create and comment on [Issues](https://github.com/langfuse/langfuse/issues);
> - Mention the project at local meetups and tell your friends/colleagues.
## Making a change
_Before making any significant changes, please [open an issue](https://github.com/langfuse/langfuse/issues)._ Discussing your proposed changes ahead of time will make the contribution process smooth for everyone. Large changes that were not discussed in an issue may be rejected.
Once we've discussed your changes and you've got your code ready, make sure that tests are passing and open your pull request.
A good first step is to search for open [issues](https://github.com/langfuse/langfuse/issues). Issues are labeled, and some good issues to start with are labeled: [good first issue](https://github.com/langfuse/langfuse/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22).
## Project Overview
### Technologies we use
- Application (this repository)
- NextJS 14, pages router
- NextAuth.js / Auth.js
- tRPC: Frontend APIs
- Prisma ORM
- Zod
- Tailwind CSS
- shadcn/ui tailwind components (using Radix and tanstack)
> This will change in Langfuse version 3.0. More in the [GitHub Discussions](https://github.com/orgs/langfuse/discussions/1902).
```mermaid
flowchart LR
Browser ---|Web UI & TRPC API| App
Integrations/SDKs ---|Public HTTP API| App
subgraph i1["Application Network"]
App["Langfuse Application"]
end
subgraph i2["Database Network"]
DB["Postgres Database"]
end
App --- DB
```
### Database Overview
The diagram below may not show all relationships if the foreign key is not defined in the database schema. For instance, `trace_id` in the `observation` table is not defined as a foreign key to the `trace` table to allow unordered ingestion of these objects, but it is still a foreign key in the application code.
Full database schema: [packages/shared/prisma/schema.prisma](packages/shared/prisma/schema.prisma)
<img src="./packages/shared/prisma/database.svg">
## Repository Structure
We built a monorepo using [pnpm](https://pnpm.io/motivation) and [turbo](https://turbo.build/repo/docs) to manage the dependencies and build process. The monorepo contains the following packages:
-`web`: is the main application package providing Frontend and Backend APIs for Langfuse.
-`worker` (no production yet): contains an application for asynchronous processing of tasks. This package is not yet used in production.
-`packages`:
-`shared`: contains shared code between the above packages.
-`config-eslint`: contains eslint configurations which are shared between the above packages.
-`config-typescript`: contains typescript configurations which are shared between the above packages.
-`ee`: contains all enterprise features. See [EE README](ee/README.md) for more details.
## Development Setup
Requirements
- Node.js 20 as specified in the [.nvmrc](.nvmrc)
- Pnpm v.9.5.0
- Docker to run the database locally
**Note:** You can also simply run Langfuse in a **GitHub Codespace** via the provided devcontainer. To do this, click on the green "Code" button in the top right corner of the repository and select "Open with Codespaces".
**Steps**
1. Fork the repository and clone it locally
2. Run the development database
```bash
pnpm run infra:dev:up
```
3. Create an env file
```bash
cp .env.dev.example .env
```
4. Install dependencies
```bash
pnpm install
```
5. Run the migrations
All database migrations and configs are in the `shared` package.
```bash
pnpm --filter=shared run db:migrate
# Optional: seed the database
# pnpm run db:seed
# pnpm run db:seed:examples
# pnpm --filter=shared run db:seed:load
```
6. Start the development server
```bash
pnpm run dev
```
7. Open the web app in the browser:
http://localhost:3000
8. Log in as a test user (after you ran `db:seed` command):
Username: demo@langfuse.com
Password: password
## Monorepo quickstart
- Available packages and their dependencies
Packages are included in the monorepo according to the `pnpm-workspace.yaml` file. Each package maintains its own dependencies defined in the `package.json`. Internal dependencies can be added as well by adding them to the package dependencies: `"@langfuse/shared": "workspace:*"`.
- Executing commands
You can run commands in all packages at once. For example, to install all dependencies in all packages, you can execute:
```bash
pnpm install
pnpm run dev
pnpm --filter=web run dev # execute command only in one package
```
In the root `package.json`, you can find scripts which are executed with turbo e.g. `turbo run dev`. These scripts are executed with the help of Turbo. Turbo executes the commands in all packages taking care of the correct order of execution. Task definitions can be found in the `turbo.config.js` file.
- Run migrations
To run migrations, you can execute the following command.
```bash
pnpm run db:migrate -- --name <name of the migration>
```
> [!NOTE]
> If you frequently switch branches, use `pnpm run dx` instead of `pnpm run dev`. This command will install dependencies, reset the database (wipe and apply all migrations), and run the database seeder with example data before starting the development server.
> [!NOTE]
> If you find yourself stuck and want to clean the repo, execute `pnpm run nuke`. It will remove all node_modules and build files.
## System behavior
### Ingestion API `(/public/api/ingestion)`
- the ingestion API takes different event types (creation and updates of traces, generations, spans, events)
- The API loops through each event and:
- validates the event
- stores the event raw in the events table
- calculates tokens for `generations`
- matches models from the `models` table to model for `generations` events
- upserts the event in the `traces` or `observations` table
- returns a `207` HTTP status code with a list of errors if any event failed to be ingested
## Commit messages
On the main branch, we adhere to the best practices of [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). All pull requests and branches are squash-merged to maintain a clean and readable history. This approach ensures the addition of a conventional commit message when merging contributions.
## Test the public API
The API is tested using Jest. With the development server running, you can run the tests with:
Run all
```bash
npm run test
```
Run interactively in watch mode
```bash
npm run test:watch
```
These tests are also run in CI.
## CI/CD
We use GitHub Actions for CI/CD, the configuration is in [`.github/workflows/pipeline.yml`](.github/workflows/pipeline.yml)
CI on `main` and `pull_request`
- Check Linting
- E2E test of API using Jest
- E2E tests of UI using Playwright
CD on `main`
- Publish Docker image to GitHub Packages if CI passes. Done on every push to `main` branch. Only released versions are tagged with `latest`.
## Staging environment
We run a staging environment at [https://staging.langfuse.com](https://staging.langfuse.com) that is automatically deployed on every push to `main` branch.
The same environment is also used for preview deployments of pull requests. Limitations:
- SSO is not available as dynamic domains are not supported by most SSO providers.
- When making changes to the database, migrations to the staging database need to be applied manually by a maintainer. If you want to interactively test database changes in the staging environment, please reach out.
You can use the staging environment end-to-end with the Langfuse integrations or SDKs (host: `https://staging.langfuse.com`). However, please note that the staging environment is not intended for production use and may be reset at any time.
## Production environment
When a new release is tagged on the `main` branch (excluding prereleases), it triggers a production deployment. The deployment process consists of two steps:
1. The Docker image is published to GitHub Packages with the version number and `latest` tag.
2. The deployment is carried out on Langfuse Cloud. This is done by force pushing the `main` branch to the `production` branch during every release, using the [`release.yml`](.github/workflows/release.yml) GitHub Action.
## Theming
At Langfuse, we utilize CSS variables to manage our theme settings across the platform.
Our approach leverages separate CSS variables for backgrounds (--background) and foregrounds (--foreground), fully adhering to the [shadcn/ui](https://ui.shadcn.com/docs/theming) color conventions. The background suffix can be omitted if the variable is used for the background color of the component. We recommend using HSL values for these colors to enhance consistency and customization. There is no need to manually handle dark mode styling with "dark:" prefixes, as next-themes automatically manages the theme switching.
Given the following CSS variables:
```
--primary: 222.2 47.4% 11.2%; // e.g. background-color
--primary-foreground: 210 40% 98%; // e.g. text-color
```
The background color of the following component will be `hsl(var(--primary))` and the foreground color will be `hsl(var(--primary-foreground))`.
| --dark-yellow | Dark yellow for warning text | LevelColor |
| --light-green | Light green for success status badge background | StatusBadge |
| --dark-green | Dark green for success status badge text and dot | StatusBadge |
| --light-blue | Light blue for background of Staging label | LangfuseLogo |
| --dark-blue | Dark blue for text and border of Staging label | LangfuseLogo |
| --accent-light-blue | Light blue accent for table link hover effect | TableLink |
| --accent-dark-blue | Dark blue accent for table link text | TableLink |
### Adding New Colors
1. Global Definitions: Add new CSS variable definitions in the global.css file.
2. Tailwind Configuration: Reflect these new colors in the tailwind.config.js to maintain alignment with Tailwind's utility classes.
By following these guidelines, you can ensure that any contributions to our theme are consistent, maintainable, and aligned with our design system.
## Maintainers
### Using secrets stored in 1Password
When applying changes to non-local environments, you may need to use secrets stored in 1Password. We use the 1Password CLI for this purpose.
Example:
```bash
op run --env-file="./.env" -- pnpm --filter=shared run db:deploy
```
### Editing default models and prices
You can update the default AI models and prices by adding or updating an entry in `worker/src/constants/default-model-prices.json`.
Please note that
- prices are in USD
- the list is ordered by ID, so make sure to keep this order and insert new models at the end of the list
- the `updated_at` field must be updated with the current date in ISO 8601 format. Otherwise, the change will be ignored.
### Transition period until V3 release
Until the V3 release, both the JSON record must be updated **and** a migration must be created to continue supporting self-hosted users. Note that the migration must updated both the `models` as well as the `prices` table accordingly.
## License
Langfuse is MIT licensed, except for `ee/` folder. See [LICENSE](LICENSE) and [docs](https://langfuse.com/docs/open-source) for more details.
When contributing to the Langfuse codebase, you need to agree to the [Contributor License Agreement](https://cla-assistant.io/langfuse/langfuse). You only need to do this once and the CLA bot will remind you if you haven't signed it yet.
Portions of this software are licensed as follows:
* Apache License, Version 2.0 (LICENSE-APACHE or
https://www.apache.org/licenses/LICENSE-2.0)
* MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)
- All content that resides under the "ee/", "web/src/ee/", and/or "worker/src/ee/" directories of this repository, if these directories exist, is licensed under the license defined in "ee/LICENSE".
- All third party components incorporated into the Langfuse Software are licensed under the original license provided by the owner of the applicable component.
- Content outside of the above mentioned directories or restrictions above is available under the "MIT Expat" license as defined below.
at your option.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
Unless you explicitly state otherwise, any contribution intentionally
submitted for inclusion in the work by you, as defined in the Apache-2.0
license, shall be dual licensed as above, without any additional terms or
conditions.
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
See HIP-0137 (hanzoai/hips) for the standard this follows.
<span>Langfuse uses <a href="https://github.com/orgs/langfuse/discussions"><strong>Github Discussions</strong></a> for Support and Feature Requests.</span>
<br/>
<span>We're hiring. <a href="https://langfuse.com/careers"><strong>Join us</strong></a> in Product Engineering and Developer Relations.</span>
- **LLM Observability:** Instrument your app and start ingesting traces to Langfuse ([Quickstart](https://langfuse.com/docs/get-started), [Integrations](https://langfuse.com/docs/integrations) [Tracing](https://langfuse.com/docs/tracing))
- **Langfuse UI:** Inspect and debug complex logs ([Demo](https://langfuse.com/docs/demo), [Tracing](https://langfuse.com/docs/tracing))
- **Prompt Management:** Manage, version and deploy prompts from within Langfuse ([Prompt Management](https://langfuse.com/docs/prompts/get-started))
- **Prompt Engineering:** Test and iterate on your prompts with the [LLM Playground](https://langfuse.com/docs/playground)
### Monitor
- **LLM Analytics:** Track metrics (cost, latency, quality) and gain insights from dashboards & data exports ([Analytics](https://langfuse.com/docs/analytics))
- **LLM Evaluations:** Collect and calculate scores for your LLM completions ([Scores & Evaluations](https://langfuse.com/docs/scores))
- Run ([Model-based evaluations](https://langfuse.com/docs/scores/model-based-evals)) and LLM-as-a-Judge within Langfuse
- Collect user feedback ([User Feedback](https://langfuse.com/docs/scores/user-feedback))
- Manually score LLM outputs in Langfuse ([Manual Scores](https://langfuse.com/docs/scores/manually))
### Test
- **Experiments:** Track and test app behaviour before deploying a new version
- Datasets let you test expected in and output pairs and benchmark performance before deploying ([Datasets](https://langfuse.com/docs/datasets))
- Track versions and releases in your application ([Experimentation](https://langfuse.com/docs/experimentation), [Prompt Management](https://langfuse.com/docs/prompts))
## Get started
### Langfuse Cloud
Managed deployment by the Langfuse team, generous free-tier (hobby plan), no credit card required.
Templated deployments: [Railway, GCP, AWS, Azure, Kubernetes and others](https://langfuse.com/docs/deployment/self-host#platform-specific-information)
All config is `NEXT_PUBLIC_*` (browser app, cookie auth). See `.env.example`.
## Get Started
| Var | Default | Meaning |
| --- | --- | --- |
| `NEXT_PUBLIC_CLOUD_URL` | same origin, else `https://api.hanzo.ai` | The ONE Hanzo API endpoint (unified `/v1` backend). Never a per-service API host. |
| `NEXT_PUBLIC_IAM_URL` | `https://iam.hanzo.ai` | Hanzo IAM OIDC authority |
| `NEXT_PUBLIC_IAM_APP_NAME` | `hanzo-console` | IAM application (`<org>-<app>`) |
| `NEXT_PUBLIC_IAM_ORG_NAME` | `hanzo` | IAM organization |
| `NEXT_PUBLIC_IAM_CLIENT_ID` | — | OAuth client id |
### API Keys
## Architecture
You need a Langfuse public and secret key to get started. Sign up [here](https://cloud.langfuse.com) and find them in your project settings.
### Ingesting Data · Instrumenting Your Application · LLM Observability with Langfuse
Note: We recommend using our fully async, typed [SDKs](https://langfuse.com/docs/sdk) that allow you to instrument any LLM application with any underlying model. They are available in [Python (Decorators)](https://langfuse.com/docs/sdk/python) & [JS/TS](https://langfuse.com/docs/sdk/typescript). The SDKs will always be the most fully featured and stable way to ingest data into Langfuse.
See the [→ Quickstart](https://langfuse.com/docs/get-started) to integrate Langfuse.
| [LiteLLM](https://langfuse.com/docs/integrations/litellm) | Python, JS/TS (proxy only) | Use any LLM as a drop in replacement for GPT. Use Azure, OpenAI, Cohere, Anthropic, Ollama, VLLM, Sagemaker, HuggingFace, Replicate (100+ LLMs). |
| [Vercel AI SDK](https://langfuse.com/docs/integrations/vercel-ai-sdk) | JS/TS | TypeScript toolkit designed to help developers build AI-powered applications with React, Next.js, Vue, Svelte, Node.js. |
| [API](https://langfuse.com/docs/api) | | Directly call the public API. OpenAPI spec available. |
| [Langflow](https://langfuse.com/docs/integrations/langflow) | Python-based UI for LangChain, designed with react-flow to provide an effortless way to experiment and prototype flows. |
- [Discord](https://langfuse.com/discord): community support
- Privately: contact at langfuse dot com
## Contributing to Langfuse
- Vote on [Ideas](https://github.com/orgs/langfuse/discussions/categories/ideas)
- Raise and comment on [Issues](https://github.com/langfuse/langfuse/issues)
- Open a PR - see [CONTRIBUTING.md](CONTRIBUTING.md) for details on how to setup a development environment.
See [LLM.md](./LLM.md) for the full design (base choice, /v1 client, auth flow,
the product-module registry, and the Providers surface). Endpoint reference in
[docs/endpoints.md](./docs/endpoints.md).
## License
This repository is MIT licensed, except for the `ee` folders. See [LICENSE](LICENSE) and [docs](https://langfuse.com/docs/open-source) for more details.
## Misc
### GET API to export your data
[**GET routes**](https://langfuse.com/docs/integrations/api) to use data in downstream applications (e.g. embedded analytics). You can also access them conveniently via the SDKs ([docs](https://langfuse.com/docs/query-traces)).
### Security & Privacy
We take data security and privacy seriously. Please refer to our [Security and Privacy](https://langfuse.com/security) page for more information.
### Telemetry
By default, Langfuse automatically reports basic usage statistics of self-hosted instances to a centralized server (PostHog).
This helps us to:
1. Understand how Langfuse is used and improve the most relevant features.
2. Track overall usage for internal and external (e.g. fundraising) reporting.
None of the data is shared with third parties and does not include any sensitive information. We want to be super transparent about this and you can find the exact data we collect [here](/web/src/features/telemetry/index.ts).
You can opt-out by setting `TELEMETRY_ENABLED=false`.
<img alt="Star History Chart" src="https://api.star-history.com/svg?repos=langfuse/langfuse&type=Date" />
</picture>
</a>
### Open Source Projects Using Langfuse
Top open-source Python projects that use Langfuse, ranked by stars ([Source](https://github.com/langfuse/langfuse-docs/blob/main/components-mdx/dependents)):
We strongly recommend using the latest version of Langfuse to receive all security updates.
For more information, please refer to the [Data Security & Privacy](https://langfuse.com/docs/data-security-privacy) page in the documentation or contact security@langfuse.com.
Join us in building out Langfuse in Berlin, Germany. Langfuse is the open source LLM engineering platform: we build tooling to help developers [build & improve LLM applications](https://langfuse.com/docs).
We are an open source company, we hire in person (4+ days a week), we only hire excellent technical talent. Find more information on our [careers page](https://langfuse.com/careers)
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
zooqueen
hanzo-devandzooqueen
zandhanzo-dev
a
