Compare commits

...
1551 Commits
Author SHA1 Message Date
hanzo-dev 8c3ccb55ac refactor(api): follow the ai surface to /v1/ai/<resource>
The namespaces I invented (rag, chat, content, compute, work, ops, auth) are
replaced by the ONE service namespace the canonical spec in hanzoai/openapi
mandates: /v1/<service>/<resource>, and the service is `ai`.

/v1/chat was not just stuttering — the gateway routes GET|POST /v1/chat/{path}
to chat.hanzo.svc, so those calls would have reached a DIFFERENT SERVICE.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-27 08:03:14 -07:00
hanzo-dev 6422afdcf7 refactor(cloud): move the ai callers and the two gates that key on their paths
The callers are the easy half — cli/{gpu,link} POST /v1/ai/providers, cmd/smoke
reads /v1/auth/account and /v1/chat/chats. The two GATES are the half that fails
silently, and both would have shipped broken.

paywall.go + clients/entitlements/require.go hold allow-lists of the routes a user
needs in order to sign in and pay. They match by STRING, so they do not move when a
route moves: leaving /v1/signin and /v1/get-account on them after the surface was
namespaced would have put a 402 in front of SIGN-IN. That is the same outage this
file already documents twice — once from a trailing slash, once from casing — and it
would have been a third. TestAuthRoutesAreNeverPaywalled now pins the live paths,
their case/slash variants, AND asserts the dead spellings are no longer exempt, so a
future move fails a test instead of production.

account_principal.go was not on any audit list; I found it sweeping. It fronts the
account read with the validated principal, and its own docstring explains why it
exists: without it the SPA's SuperAdmin gate bounced operators to login while the
same session got 200 from every /v1/admin route. It intercepts by PATH MATCH, so a
stale literal does not error — the middleware just stops firing, falls through to
the casibase surface, and hands the SPA the anonymous owner again. The exact bug it
was written to fix, restored silently. The path is now a named constant with that
reasoning attached.

Deliberately NOT touched: clients/visor/* still calls /v1/get-machines,
/v1/get-machine, /v1/delete-machine, /v1/get-node-pools, /v1/delete-node-pool.
Those target VISOR — a separate Casibase fork with its own route table that happens
to share the old naming. Editing them would have broken working code, and no build
would have caught it.

routers + the migrated packages build and test green. clients/entitlements'
TestSwitchesDefaultOff fails identically on a clean baseline (pre-existing).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 22:55:04 -07:00
hanzo-dev e92cf60378 fix(zapface): carry the HTTP verb, stop inferring it from the method name
The ZAP dispatcher chose its HTTP method by looking at the method NAME: a "get-"
prefix meant GET, everything else meant POST. That was sound only because the /v1
surface encoded its verb in every route name — /v1/get-store and /v1/update-store
are different names, so a name WAS a complete request description.

The RESTful surface removes that signal entirely. /v1/ai/providers/{owner}/{name}
answers GET, PATCH and DELETE at one path, and no prefix distinguishes them. Under
the old rule every one of those would have been sent as a POST: a read as a write,
and a DELETE landing on the create route instead of destroying anything. Silently,
with a 2xx.

So the method is now an HTTP request line — "<VERB> <path>":

    GET    ai/providers/acme/openai
    PATCH  ai/providers/acme/openai
    DELETE ai/providers/acme/openai
    POST   ai/providers

A method with no verb is REFUSED, not defaulted. Defaulting would convert a
caller's omission into a wrong-but-plausible request, and on a surface where the
verb decides between reading a resource and destroying it, a plausible wrong guess
is the worst available outcome. The integration test asserts the refusal names the
missing verb.

The fixture in the integration test now switches on METHOD AND PATH, which is what
made the old design's problem concrete: it is the same pair the dispatcher has to
carry, and the reason a name alone can no longer produce it.

Worth recording: this face has no first-party consumer left — console's src/lib/zap
is gone and nothing imports it — but /zap is still mounted in serve.go, so it is
fixed rather than left silently guessing. Whether to retire the mount is a separate
call. The cloud.event checkout carrying the same code is a WORKTREE of this repo on
another branch; it inherits this fix on merge and was deliberately not touched.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 22:43:41 -07:00
hanzo-dev 8316db1f9b feat(admin): DigitalOcean fleet board — inventory, safety analysis, controls
admin.hanzo.ai could show what we BILL but not what we RUN. The 13 TiB of block
storage, the 64 nodes, the 295 volumes were only visible in the DO console, with
no cross-reference to what Kubernetes actually mounts — so "is this orphaned?"
had no answer a human could act on.

/v1/admin/infra is that answer: the DO account inventory joined against EVERY
cluster's PersistentVolumes, folded into one classification per volume.

The safety rule is the whole point, and it is the mistake this was written after
nearly making. A volume is deletable ONLY when no PersistentVolume in ANY cluster
names it in spec.csi.volumeHandle. Specifically:

  - Reference beats absence. One PV anywhere protects the volume, no matter what
    the tags, the attachment state, or the other seven clusters say.
  - DOKS `k8s:<uuid>` tags are ADVISORY. They survive cluster deletion and they
    lie in both directions, so they are displayed and never trusted.
  - An incomplete scan freezes everything. If a single cluster is unreachable,
    the cross-reference is unsound, so NOTHING is deletable — not degraded, not
    best-effort. TestIncompleteScanBlocksEveryDeletion and
    TestUnreachableClusterFreezesEverything hold that line.
  - Idle is not orphaned. A Bound PVC no pod mounts is flagged for review and is
    never counted as reclaimable.

The server never trusts the client's verdict: DELETE re-runs a full fresh
cross-cluster scan and refuses anything that verdict does not clear, so a volume
that went live between page-load and button-press is protected. Deletes snapshot
first by default; the snapshot is the undo. Every mutation is audited, including
the denials.

Verified against the live account: 8 clusters, 64 nodes, 295 volumes, $8610.30/mo.
Of 13.19 TiB, exactly 3 volumes / 500 GiB / $50/mo are unreferenced — matching a
hand audit. The naive "no k8s tag" test would have proposed deleting 4.39 TiB of
live cluster data.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 20:03:53 -07:00
hanzo-dev f5aad4dd36 perf(admin): fan out the overview's per-org reads
The Platform Overview folded every org serially, two independent reads each
(users, money). At 122 orgs that is ~244 blocking round-trips before a single tile
renders, and it gets worse with every tenant that signs up — the reason the admin
dashboard loads slowly.

The reads do not depend on each other, so they now run concurrently under a fixed
ceiling of 12: bounded so a large fleet cannot stampede the finance ledger or the
IAM store. Accumulation is mutex-guarded; go test -race passes on the overview path.

Behaviour is unchanged, including the partial-read semantics: if ANY org's money
fails to read the totals are an undercount, so commerce still reports degraded
rather than healthy.

The 3 failures in this package (GrantCredit x2, SuspendReactivate) are pre-existing
and identical on clean main.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 18:22:18 -07:00
2c24ea104a feat(agents): seed the built-in crew @dev @des @vi on org first-touch (re-land) (#342)
Re-land of the crew seed (a parallel force-push to cloud main dropped it).
personalities.go: dev/des/vi personas + idempotent SeedPersonalities(ctx,org)
(one registry, UNIQUE(org,name); no-op without a model). account.go OAuth
callback seeds per-org after EnsureWorkspace (best-effort, never blocks login).
Native TestSeedPersonalities green. TEAM_AGENTS_ENABLED=1 already live +
AIDefaultModel=deepseek-v4-flash → the crew materializes and answers @-mentions.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-26 18:22:18 -07:00
99a00f69f0 rebuild(cloud): embed console-embed@sha-bd8a816 (casibase auth /v1/* fix + console per-project resources) + activate MCP builtin tool-plane (#292)
No Go change — this rebuild re-resolves the freshly-republished console-embed:latest
(console main bd8a81651) into the go:embed console served at console.hanzo.ai, and
ships builtin.go's auto '/v1 route → MCP tool' plane at /v1/tools/mcp (already in main,
newer than the deployed v1.801.69).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-26 18:22:18 -07:00
zeekayandhanzo-dev 1f62bf4aa8 chore: trigger release build for iam2 v0.15.4 (federation fix)
d411200 (iam2 v0.15.1→v0.15.4 bump) did not trigger a release run; nudge
the push-triggered release so the federation-security-fixed image ships.
2026-07-26 18:22:18 -07:00
hanzo-dev ff86446070 feat(account): take USDC on any chain — rails replace the HUSD hardcode
Crypto top-up was architecturally complete and could not take a cent. The gate was
a single hardcoded (HANZO_HUSD_ADDRESS, HANZO_HUSD_TREASURY) pair, HUSD is not
deployed on Hanzo Mainnet, so POST /v1/commerce/topup/wallet answered 501 forever
and the console mirrored it with a build-time NEXT_PUBLIC_ gate that reported "not
available yet" no matter what the server could accept.

A rail is one accepted (chain, token, treasury) triple, configured as data in
TOPUP_RAILS. Customers already hold USDC on Base/Ethereum/Polygon, so accepting
the assets they actually have is what makes this path earn. A new chain is now a
config entry, not a code change — the receipt check is one well-known JSON-RPC
call and one well-known event, which is chain-agnostic already.

Per-token decimals are the load-bearing detail. USDC has 6, HUSD has 18, and the
old code divided by a fixed 1e16. Reusing that on USDC would round a $5.00 top-up
to zero cents; reusing USDC's divisor on an 18-decimal token would credit 10^12
times too much. Cents now come from the rail's own decimals, and a test pins it.

Adds GET /v1/commerce/topup/rails so the browser learns the accepted set at
RUNTIME. That removes the build-time coupling that made this dead: enabling a rail
no longer means rebuilding and redeploying a frontend. The listing is a separate
view type from the config struct, so an operational field (the RPC endpoint, and
anything added later) cannot leak by merely existing — a field is published only
if put there deliberately.

Everything that made the original correct is kept: the credit is the ON-CHAIN
value and never a client number, it lands on the gateway-validated caller (no
IDOR), and it is recorded S2S with the service token. The ledger row now names the
rail actually verified rather than asserting "hanzo"/"husd" for every payment.

Behaviour is unchanged where nothing is configured: no rail ⇒ honest 501, never a
fabricated credit. With TOPUP_RAILS unset this deploy is a no-op.

15 tests pass, 5 new: 6-decimal pricing, multi-rail requires naming one, unknown
rail 400, transfer to another rail's treasury 400, listing omits the RPC URL.
2026-07-26 18:19:23 -07:00
antje 82e48a3b30 test(identity): the anonymous floor under the org switch, and BillingOrg's truth table
The org-switch tests proved the SELECTION behaves. Nothing proved the machinery is
invisible to a request carrying no credential at all — and SanitizeIdentity runs in
front of everything, so a mistake there is not scoped to org-switching: it takes out
unauthenticated routes too, and /health is what the kubelet probes.

  - TestAnonymousRoutesAreUntouched: bare / forged X-Org-Id / unparseable bearer all
    still 200 on a public route. The switch arm lives inside `claims != nil`, so an
    anonymous request must never reach it; this pins that structurally rather than by
    reading the code.
  - TestAnonymousGrantsNoPrincipal: letting anonymous THROUGH must not make it
    someone. A forged X-Org-Id survives for the Phase-1 data path but mints no user
    and no admin, so principal.Org refuses it.
  - TestMembershipMatchIsByteExact: isMember must not fold. "ACME"/"Acme"/"ac me"/a
    zero-width variant are DISTINCT orgs and each pins to home. A trailing-space
    variant is deliberately absent: fasthttp OWS-trims it on the wire, so the
    boundary receives the exact member org and correctly honors it; the whitespace
    fold risk is claim-side and covered by trailWSOwner in middleware_identity_test.
  - TestHomeOrgHeaderSurvivesSwitch: home and effective must stay DISTINCT facts.
    BillingOrg decides who pays from both, so collapsing them silently removes the
    masquerade carve-out.
  - clients/principal/billingorg_test.go: the package had no unit test for the ONE
    "who pays" resolver. Seven cases pin both policies as two branches — member pays
    the org acted in, SuperAdmin masquerade pays the admin ledger, org admin gets no
    carve-out, unvalidated bills nothing — plus Ledger tracking BillingOrg, since the
    ~35 resource-meter call sites reach the ledger through it.

Tests only; no behavior change. Added to the existing orgswitch file rather than a
second one, and isMember/BillingOrg are left exactly as they are: read against an
independent implementation of the same fix, they are equal-or-better on every
property that matters (exact bytes, no fold, empty set admits nothing, silent
refusal, and refusing outright when the org is unresolvable).
2026-07-26 18:17:44 -07:00
hanzo-devandantje 75788dd07b affiliates: margin is set in admin.hanzo.ai, live, not in env
The share base — Hanzo's gross margin, which every affiliate commission is a rate
OF — could not be changed. It came from AFFILIATE_MARGIN_BPS and was snapshotted
into state at Mount, so editing the env did nothing until the pod restarted, and
there was no admin control at all. Margin tracks real cost of revenue and moves;
a boot-time constant read from the environment is the wrong shape for it.

Now a registered platform switch, affiliate_margin_bps, editable in
admin.hanzo.ai and read LIVE at each accrual. Def.Env is deliberately empty: this
must not be settable by environment variable. Same mechanism clients/rollingcap
already uses for its admin-editable per-tier caps — flags.Int over a registered
Def — so no new machinery, one way to do this.

The clamp is now a pure clampMarginBps, testable without the engine: out of
[0,10000] falls back to the policy default so a bad edit cannot over-inflate or
negate the base, while 0 and 10000 stay LEGAL (accrue nothing / share gross
revenue). Unset resolves to Def.Default (4000), not 0 — that direction matters,
because 0 is a legitimate margin, so zero-on-missing would silently switch off
every commission instead of failing loudly.

NOT made per-affiliate, deliberately. The margin base is computed ONCE per
source-spend event and then paid up to three affiliates (L1/L2/L3). The
invariant this file is built around — maxL1RateBps = 10000 - l2 - l3 — guarantees
the SUM of every level's share on one event stays within that event's margin. Give
each affiliate its own base and three affiliates on one event compute three
different bases, so the sum can exceed the margin actually earned and the platform
pays out more than it made. The per-affiliate knob that is safe already exists and
admin already sets it: Affiliate.RateBps, bounded by that same cap.

Four tests: the switch is registered (unregistered ⇒ flags.Int returns 0 ⇒ no
commission accrues at all, so this is worth pinning), carries no Env, is not
ReadOnly; unset is the default not zero; the clamp honours 0/100% and rejects
impossible values; the base is re-read rather than snapshotted.

25 tests fail in this package before and after this change — all
"CLOUD_KMS_MASTER_KEY_REF is required on an encryption-capable build", verified
identical on pristine origin/main by stashing. None are mine.
2026-07-26 18:13:36 -07:00
hanzo-dev 57c2ee9e92 event: accept anonymous marketing telemetry on the one canonical door
POST /v1/event refused every caller that could not resolve to an org, so a
logged-out marketing page had nowhere to send a pageview: a rendered-DOM audit
found the 403 on 16 of 22 page loads across every public surface, i.e. no
pageviews and no errors from logged-out traffic at all.

A caller that presents NOTHING now takes an anonymous lane and is attributed to
a reserved public tenant. A caller that presents an ingest credential which does
not resolve is still refused, so a misconfigured key surfaces as a 403 instead of
filing its events where its owner cannot read them.

One path, not a fork. Admission is the only thing the lanes do differently: both
share decodeIngest, and both end at ingestDecoded — extracted here as the single
tail (fold, write core, receipt) so what happens to an admitted event is written
once. The vouched-for lane passes dropped=0, so its behavior is unchanged.

Attribution is structural rather than checked. admitPublic takes no request, so
no header, query, or body field can reach it and the tenant it returns is always
the constant: an anonymous write cannot land in a real org's partition, and the
'$' in the sentinel is outside the IAM org alphabet so it cannot collide with one.
Kinds are an allowlist of two (pageview, error) — identify and group name a person
and a group, and a custom event is the whole product/billing surface. The stored
name comes from the kind, closing the anonymous name space to two values. Fields
are a projection, so personId, groupId, commerce fields and the entire client
property bag cannot reach the row; an anonymous row's properties hold only the
server-folded $exception and $source. Bytes and batch length are bounded and
refused rather than truncated, ingest is capped per client IP and per socket peer
(the header key is caller-settable, the peer is not), DNT/Sec-GPC store nothing,
and the public tenant never fans out to a destination.

CLOUD_ANALYTICS_PUBLIC_CAPTURE, the existing anonymous-capture switch, still turns
the whole lane off.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 18:00:34 -07:00
65d0dbcbeb feat(agents): seed the built-in crew @dev @des @vi on org first-touch (re-land) (#342)
Re-land of the crew seed (a parallel force-push to cloud main dropped it).
personalities.go: dev/des/vi personas + idempotent SeedPersonalities(ctx,org)
(one registry, UNIQUE(org,name); no-op without a model). account.go OAuth
callback seeds per-org after EnsureWorkspace (best-effort, never blocks login).
Native TestSeedPersonalities green. TEAM_AGENTS_ENABLED=1 already live +
AIDefaultModel=deepseek-v4-flash → the crew materializes and answers @-mentions.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-26 18:00:20 -07:00
5f518ae493 rebuild(cloud): embed console-embed@sha-bd8a816 (casibase auth /v1/* fix + console per-project resources) + activate MCP builtin tool-plane (#292)
No Go change — this rebuild re-resolves the freshly-republished console-embed:latest
(console main bd8a81651) into the go:embed console served at console.hanzo.ai, and
ships builtin.go's auto '/v1 route → MCP tool' plane at /v1/tools/mcp (already in main,
newer than the deployed v1.801.69).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-26 18:00:07 -07:00
zeekayandhanzo-dev 2dfce35465 chore: trigger release build for iam2 v0.15.4 (federation fix)
d411200 (iam2 v0.15.1→v0.15.4 bump) did not trigger a release run; nudge
the push-triggered release so the federation-security-fixed image ships.
2026-07-26 18:00:07 -07:00
hanzo-dev be8651ae31 Merge remote-tracking branch 'origin/main' into fix/agent-default-enso
# Conflicts:
#	go.mod
2026-07-26 17:54:12 -07:00
hanzo-dev 6058aa3532 deps: repin hanzoai/o11y to v1.5.31 — the tag, not a GC'd pseudo-version
main was unbuildable. go.mod pinned
o11y v1.5.31-0.20260726155004-2b66f3201d03 and that revision no longer
exists upstream, so every container build died at `go mod download` with
"invalid version: unknown revision 2b66f3201d03".

v1.5.31 is cut from o11y 6c1f0135b, which is the commit the pseudo-version
was reaching for: it carries the kv-go cache refactor that drops upstream
go-redis, and it still pins hanzoai/sqlite v0.3.2. Tagging HEAD instead
would have dragged in sqlite v0.4.0 and forced a data-plane driver bump
through MVS; falling back to v1.5.30 would have re-added the go-redis
dependency the refactor just removed. This is the one commit that fixes
the build without doing either.
2026-07-26 17:53:24 -07:00
zeekayandhanzo-dev 8eff71c937 deps: hanzoai/iam v1.33.8 -> v1.33.15 (CORS preflight)
cloud imports the IAM server at a published semver and serves it in-process, so
the embedded identity surface was seven patches behind the standalone one. That
mattered: v1.33.15 is the release where the Guard stops authenticating CORS
preflights. Standalone deploy/iam is already on it, so leaving cloud on v1.33.8
meant flipping hanzo.id to the embedded IAM would have silently REGRESSED the
fix — the browser would go back to a 401 preflight and an empty org switcher.

v1.33.15 renames the entrypoint (its "Route, not Mount" change), so the call and
the comments around it move with it.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 17:43:28 -07:00
antje e6a1af1a53 build: pin hanzoai/o11y to the released v1.5.30, not a revision that never shipped
main was unbuildable. go.mod pinned o11y at the pseudo-version
v1.5.31-0.20260726155004-2b66f3201d03, and that revision exists in exactly one
place: somebody's module cache. It is not on origin and not reachable from any
tag, so `go mod download` in the on-cluster build resolved "unknown revision"
and every image build of cloud failed before it compiled a line.

v1.5.30 is the last released patch and its tree is byte-identical to the cached
pseudo-version (diff -rq over both module directories is empty), so this is the
same code under a name the builder can actually fetch — not a version bump, and
not a jump forward past anything.
2026-07-26 17:37:02 -07:00
antje 9bafa850cd money: the SELECTED org is the payer of record
The @hanzo/iam switcher moved data and nothing else. A person picks an org,
every surface stamps X-Org-Id from that choice, and the money still came out
of their HOME org: the boundary re-minted X-Org-Id from the `owner` claim
unconditionally, and principal.BillingOrg keyed the debit on home anyway. Both
halves are fixed here, and they are one fix — one org, for data and money alike.

  - SanitizeIdentity honors a selection the token's signed `orgs` claim says the
    caller belongs to (isMember). IAM already mints that set, home first;
    nothing else can widen it. A selection OUTSIDE the set is discarded, not
    refused — a stale localStorage choice after a revoked membership reads and
    bills the caller's OWN org, never someone else's. A legacy token, an opaque
    key and a machine principal carry no set, so they cannot switch at all.
  - principal.BillingOrg returns that effective org. Platform sudo is the one
    exception and is not a selection: a masquerading SuperAdmin still spends
    from the admin ledger, keyed on the header the boundary already mints.
  - HomeOrg -> Ledger. A name that states the wrong fact is how a gate ends up
    keying one wallet while the debit spends another.

And an unresolvable org now REFUSES instead of charging someone else:

  - WalletOf propagates ok=false. It used to discard BillingOrg's ok-bit and
    return an EMPTY ledger, which is not "no ledger" but "whatever the next
    layer substitutes".
  - metering.AuthorizeVerdict and Record refuse an empty org. orgFor fell back
    to the deployment's BRAND org, so an org-less principal was gated against
    Hanzo's balance and its debit posted under Hanzo's header. orgFor stays for
    CONFIG reads (spend rules, caps, plan tier), where the platform's own org IS
    the right default, and is no longer reachable from the money path.

Tests fail without the change: TestSelectedOrgIsThePayer bills "hanzo" instead
of the selected "acme"; TestUnresolvableOrgRefuses resolves a wallet with no
payer; TestUnresolvableOrgRefuses_NoBrandSubstitute posts a real debit to the
brand's ledger.
2026-07-26 17:37:02 -07:00
hanzo-dev c1a36548e1 test(guide): prove the eight Guide growth seams end to end
Mounts the real wire — framework + content + automations + guide + company on one
zip.App — and walks a fresh org through the agentic-company journey, asserting each
seam against the in-process subsystems instead of a stub. The only fakes are the AI
completion (a deterministic draft) and the growth-observe seams, which are bound to
org-scoped reads exactly as apps/wire_seams.go binds them in prod.

What it proves:

  1. formation begins at structure and is idempotent, and the founder-KYC gate holds:
     an unattributed founder cannot cross founders to payment (422), a non-SuperAdmin
     decision is refused (403), and only an attributed SuperAdmin reviewer
     confirmation opens it.
  2. the marketing module and its Campaign DocType resolve for an org that never ran
     an install, while an unknown module still resolves false.
  3. the observe layer is org-scoped: seams true only for alpha leave beta at formed
     with zeroed metrics and no signal set.
  4. suggest ranks the journey root first, reports it automatable, and fails closed
     without a principal.
  5. the tactics corpus filters by observed stage; an explicit stage query lifts the
     stage floor but can never unlock a has:<capability> tactic whose signal is
     absent; a category query is a strict subset of the unfiltered read.
  6. a content_generate step runs the real invoke to content to framework path: a
     Campaign lands, the step auto-marks done, and the acted detector independently
     re-marks it done after a reset.
  7. the blueprint admin plane is SuperAdmin-gated, and a disable takes effect on the
     next org resolve.
  8. the loop advances autonomously over four iterations: the observed stage climbs
     formed to launched to activated to scaling as each milestone's real effect comes
     online, the next-step pointer walks the chain, and three real work-product docs
     land.

Seam 5 asserts the category filter server-side against a category that actually
surfaces at the observed stage, so a non-empty result is required before any
no-leak claim is made — an empty read would prove nothing.

LLM.md records why these tests looked slow: they are fsync-bound, and t.TempDir()
under /tmp puts every SQLite commit behind the ext4 journal.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 17:35:16 -07:00
zeekay 25c1a1d3f3 deps: hanzoai/orm v0.6.10 — one version across the fleet
v0.6.10 is the current published tag and main matches it exactly. Every Go
backend that depends on orm now pins the same one, so "the orm" means a single
thing everywhere rather than a spread of v0.6.8 / v0.6.9 / pseudo-versions.

v0.6.10 carries db.Registry as a generic Registry[T io.Closer]. That generic is
the point: the registry calls exactly one method on a handle — Close — because
releasing it is the whole of its job, and what a handle IS stays the caller
business. Pinning T to orm own DB interface would have forced every owner of
per-tenant files to adopt orm entity API just to get lifecycle management, which
is exactly the toll that made commerce write its own unbounded userDBs/orgDBs
maps instead of reusing this. commerce now runs RegistryConfig[DB] with its own
DB type.

Verified per repo rather than assumed: commerce ./db builds and its tests pass,
git ./models/db builds, base orm consumer builds.
2026-07-26 17:34:28 -07:00
hanzo-dev 84a7f7b9a1 fix(agents): default to enso, and stop upstream names reaching a customer
An agent created without a model was stored with the deployment default,
whose literal was an UPSTREAM name — so GET /v1/agents answered
"deepseek-v4-flash" for des, dev, vi and verify-run. That publishes which
base sits behind a Hanzo model, which is exactly what the enso name exists
to abstract. It is also a margin leak: the branded SKUs carry retail
pricing while the raw upstream ids are served near cost.

ONE place decides the default. cloud.DefaultModel is the only literal;
CLOUD_AI_DEFAULT_MODEL defaults to it and every subsystem reads that. The
duplicate hardcode in clients/code/ask.go is gone.

ONE function decides the brand boundary. cloud.ZenModel maps an upstream
family name to the Hanzo name; cloud.UpstreamModel is the predicate behind
it, matching a family as a word so "qwen3.5-397b" matches and "zen5-coder"
does not. Applied at every write (config at Mount, caller at create and
update) and guarded at every read (toView, toRunView, the activity feed),
so an upstream name can neither enter the registry nor be served from it.

Store.migrateModel rewrites the rows that predate this. Idempotent: it
selects by the same predicate that decides where rows land, so a second
pass moves nothing. Reversible: the pre-migration value goes to
model_snapshot first (INSERT OR IGNORE, so the first value seen is kept),
and one UPDATE restores it. agent_runs is deliberately NOT rewritten — a
run records what actually happened; toRunView guards the presentation.

Two further leaks found by sweeping the customer-visible surfaces:

  - GET /v1/benchmark/presets shipped the enso-ultra arm list as "shipped
    enso-ultra blend" — a direct enso-to-upstream disclosure. The reference
    preset is now a worked example in models we name.
  - hanzo code --help advertised upstream ids, and the Zen5 Pro picker
    description named the base it maps to.

The guard is clients/agents/brand_test.go: it drives every read of the
registry against a deployment configured with an upstream default and
scans the raw response bytes for any upstream family. Reverting any one of
the write or read guards makes it fail.

That package could not run at all — since hanzoai/sqlite v0.3 the pure-Go
build is encryption-capable, so every store open wanted a master key and
all 104 tests errored out. It now has the same TestMain every other
store-backed package already uses.

BLAST RADIUS: an agent with no explicit model moves from a near-cost
upstream SKU to the branded family, and enso is priced $4/$20 per Mtok
against deepseek-v4-flash at $0.14/$0.28. The four live rows carry 21 runs
total, so absolute exposure today is small, but the rate change is real
and the knob is one constant plus CLOUD_AI_DEFAULT_MODEL.
2026-07-26 17:30:34 -07:00
zeekay 6f6e03ff81 deps: repin hanzoai/ai to v1.831.6 — the tag, not a pseudo-version
Was v1.831.5-0.20260726065328-5420f6ba9987 while tag v1.831.6 exists and is
newer. A pseudo-version shadowing a real, later tag is the drift that had this
fleet disagreeing about what a dependency means — the same defect fixed in cloud
and commerce for hanzoai/orm today.

Checked the rest rather than bulk-repinning: cloud sendgrid-go and o11y, and
commerce sendgrid-go, are pseudo-versions AHEAD of their latest tag. Those are
the honest case for an unreleased commit, and "fixing" them would be a
downgrade. Only the two genuinely shadowing pins moved.
2026-07-26 17:00:33 -07:00
antje 716217670f fix(auth): a publishable key must not authenticate — then one pk-
pk- is the published key and sk- is the secret one. Cloud did not hold that line:
IdentityFromRequest resolved ANY isAPIKey token into "the same principal a JWT
yields", and pk- is in APIKeyPrefixes. So a key IAM documents as "stored
verbatim, safe to show" — the one you put in a browser bundle — authenticated
like a secret and could READ everything its owning org could.

The codebase had three different answers on this and could not all be right:
auth_identity.go called pk- write-only, build.go called it read-only, and
analytics/publishable.go said the IAM family "mint a FULL principal that can
READ" and therefore built a SECOND publishable-key family to avoid it — pk_
(underscore), HMAC'd under CLOUD_INGEST_KEY_SECRET, with its own mint endpoint.
The underscore was load-bearing: it kept that key out of isAPIKey.

Fixed at the boundary rather than routed around it. IdentityFromRequest refuses a
publishable key outright, so publishable means publishable at every door, not
just the one that remembered to dodge. pk- deliberately STAYS in APIKeyPrefixes:
OrgForKey must still resolve it to learn which tenant a browser beacon belongs
to. Resolvable, not authenticating.

That makes the collapse safe, so it happens in the same commit: the pk_ family,
its HMAC, its secret and POST /v1/ingest/keys are gone, and /v1/event resolves a
pk- through the SAME IAM seam as every other key. One publishable key, issued by
the service that owns identity.

Order matters and is the whole point — collapsing first would have shipped a
public read credential.

Verified: full build; the analytics suite green with the auth tests rewritten
against the IAM seam (a stubbed resolveKeyOrg) so they still assert what they
always did — admitted, key's org beats a forged one, unresolvable fails closed.
TestIAMEmbedBehindMiddlewareChain and TestConfigValidate_ShardSafety fail
identically with this change stashed; they are pre-existing.
2026-07-26 16:58:53 -07:00
zeekayandhanzo-dev 514c4f8e2f ci: resolve the reusable from .hanzo/workflows
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.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 16:57:09 -07:00
hanzo-dev 5116fbf6fc git(webhook): read X-Git-* headers, accept the pre-rename pair
Our webhook header says X-Git, not X-Gitea. Cloud is the RECEIVER, so it moves
first: it now prefers X-Git-Event / X-Git-Signature and still reads the
X-Gitea-* pair the git image sends today.

Order is the whole point. The two images roll independently, and if the fork
started sending X-Git-* while cloud only understood X-Gitea-*, every push
webhook would fall through the event check and 204 — no signature error, no log,
deploys just silently stop firing. Receiver-accepts-both makes either order
safe. The fallback is a rename in flight, not a compatibility layer: it comes
out in the same change that makes the fork send the new names.

Also drops the upstream name from this file
type giteaPush -> pushEvent, and the doc comments now describe the ingest
without it. The two remaining mentions are the pre-rename header literals,
which are wire values, not our branding.

TestWebhookAcceptsBothHeaderSpellings covers it with one app and one capture,
asserting the build count climbs 1 then 2 so neither spelling can pass on the
others build. Proven non-vacuous: with the fallback reads removed it fails
X-Gitea-Event/X-Gitea-Signature not honored: builds = 1, want 2. Polls for the
count rather than sleeping, because fireBranchBuild is detached from the request
(context.WithoutCancel) - a fixed sleep is what made the first version flake on
TempDir cleanup.

go test ./clients/git/ -run Webhook passes; go build ./clients/git/ clean;
both files gofmt-clean. (A fresh worktree cannot link ./cmd/account - clients/flags
wants native/flags/target/release/libhanzo_flags.a, a Rust artifact only the main
checkout has built. Pre-existing, unrelated to this change.)
2026-07-26 16:52:32 -07:00
zeekayandhanzo-dev 1558023ec6 rip beego out of cloud
The last real use was sessionAccessToken, which mapped a first-party session
cookie to a server-stored JWT by reading web.GlobalSessions — the process-global
the retired Casdoor iam-v1 embed populated.

That embed is gone. IAM v2 (github.com/hanzoai/iam) is zip-native on
hanzoai/orm + hanzoai/sqlite and mounts directly on cloud app, so NOTHING in
this binary ever set that global. The function could only return "". It was dead
code keeping an entire web framework, and its process-global config, in the
dependency graph.

Removed rather than kept as a fallback: a bridge to a session manager that is
never initialised is not a fallback, it is a lie about where sessions come from.
If a first-party session needs to resolve to a token again it resolves through
IAM v2.

The guarantee it existed to provide is unchanged and now stronger. The test no
longer skips when a session manager happens to be present and no longer reaches
into a framework global — a session cookie without a bearer resolves ANONYMOUS,
unconditionally. Green.

beego is out of go.mod. One HTTP framework (zip), one data layer (orm).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 16:41:23 -07:00
hanzo-dev efaeedb82c fix(kms): serve the operator's list contract so the standalone KMS can retire
The embedded /v1/kms plane and the standalone KMS answered the same request
differently, which is what blocked pointing the KMS operator at cloud:
  operator sends ?environment=&secretPath=   cloud read ?env=&path=
  operator reads  {"names":[...]}            cloud returned {"secrets":[],"total":0}
Repointing KMS_API_BASE would therefore have parsed as 'no secrets' for all 108
KMSSecret syncs — every service silently starved rather than erroring.

listSecrets now accepts either spelling and returns a superset carrying BOTH
`secrets`/`total` (this plane's clients) and `names` (the operator). One endpoint
serves both, so the standalone can be retired without a flag day or a lockstep
operator release.

firstNonEmpty is split out as a plain function so the precedence rule (primary
before alias, empty treated as absent) is tested without a request context: 5/5.
The remaining clients/kms failures are pre-existing and environmental — the suite
wants CLOUD_KMS_MASTER_KEY_REF (105 failures on untouched main); my test passes
standalone and go vet is clean.

Parity must still be proven against a POPULATED path before the operator is
repointed and the standalone retired.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 16:29:36 -07:00
8913ece0a6 feat(agents): seed the built-in crew @dev @des @vi on org first-touch (re-land) (#342)
Re-land of the crew seed (a parallel force-push to cloud main dropped it).
personalities.go: dev/des/vi personas + idempotent SeedPersonalities(ctx,org)
(one registry, UNIQUE(org,name); no-op without a model). account.go OAuth
callback seeds per-org after EnsureWorkspace (best-effort, never blocks login).
Native TestSeedPersonalities green. TEAM_AGENTS_ENABLED=1 already live +
AIDefaultModel=deepseek-v4-flash → the crew materializes and answers @-mentions.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 16:28:59 -07:00
zeekayandhanzo-dev 94130dca61 rebuild(cloud): embed console-embed@sha-bd8a816 (casibase auth /v1/* fix + console per-project resources) + activate MCP builtin tool-plane (#292)
No Go change — this rebuild re-resolves the freshly-republished console-embed:latest
(console main bd8a81651) into the go:embed console served at console.hanzo.ai, and
ships builtin.go's auto '/v1 route → MCP tool' plane at /v1/tools/mcp (already in main,
newer than the deployed v1.801.69).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 16:28:59 -07:00
zeekayandhanzo-dev d9a99e6a54 chore: trigger release build for iam2 v0.15.4 (federation fix)
8e61a92 (iam2 v0.15.1→v0.15.4 bump) did not trigger a release run; nudge
the push-triggered release so the federation-security-fixed image ships.
2026-07-26 16:28:59 -07:00
hanzo-dev 4ea8b06f79 fix(code): normalize embedder base to /v1 — deployed CLOUD_AI_BASE_URL lacks /v1, so /v1/code semantic tier posted to /embeddings (405) → vectors:0. Append /v1 when absent; ask/RAG now works. (#238) 2026-07-26 16:28:59 -07:00
hanzo-dev 829cdf72cc refactor(auto): decomplect — remove the /v1/auto reverse-proxy + clients/auto (#176)
Kill the second automation surface. /v1/auto was a per-org reverse proxy
(clients/auto + clients/auto/proxy) to the standalone hanzoai/auto engine
(auto.hanzo.svc) — a duplicate of the native, in-process /v1/automations
Connectors+Automations engine (clients/automations, cloud.EmbeddedTasks,
706-piece catalogue). One engine, one surface: /v1/automations is the ONE
native automation engine. The external engine + its console link-out are
retired (console + universe in paired PRs).

- Remove the order-140 blank import of clients/auto from subsystems.
- Delete clients/auto/ (auto.go + proxy/).

No functional loss: /v1/automations already serves flows/versions/runs/
pieces/MCP natively. clients/kb keeps its own AUTO_UPSTREAM piece-runner
coupling (a separate, pre-existing bridge to a never-implemented engine
endpoint) — reported for a follow-up, not touched here.

go build ./... green, go vet green, go test ./clients/automations + root ok.
2026-07-26 16:28:59 -07:00
hanzo-dev 802bb6ad29 cloud: follow the Kafka adaptor to its canonical name
hanzoai/stream is retired as a product -- it is the Kafka interface to Hanzo
PubSub, not a thing of its own -- so the module is now github.com/hanzoai/kafka.
The repo had in fact been redirecting hanzoai/kafka -> hanzoai/stream, so the
import path and the canonical URL disagreed.

Pinned v1.2.1, not the newer tag on the adaptor's main. main had already dropped
Broker.Serve() for Startup() + caller-driven HandleConnection(), and this
package calls Serve(): taking main would have broken the build for a reason
unrelated to the rename. v1.2.1 is v1.2.0 plus the rename, same API. Migrating
onto Startup/HandleConnection is a separate deliberate step.

clients/kafka tests pass.
2026-07-26 16:23:03 -07:00
zeekay 8a38817b5e deps: hanzoai/orm v0.6.8 — the published tag, not a pseudo-version
cloud was pinned to v0.6.8-0.20260726065619-7b3c62da906d: a commit, not a
release. A pseudo-version pins a moment rather than a contract, so MVS can
resolve a tree nobody reviewed and nothing in the fleet agrees on what "the orm"
is.

Now the same published v0.6.8 as hanzoai/git and hanzoai/visor. That tag carries
db.Registry — per-tenant resolve/bound/evict/materialise, the primitive behind
one SQLite per object with S3 as the source of truth.
2026-07-26 16:12:38 -07:00
zeekayandhanzo-dev c4047ee492 docs: the CD plane is /v1/deploy/*, not /v1/deploy/api/*
/v1/ only, never /api/. Two package comments claimed an /api/ segment
this code has never served:

  dashboard.go:1   "projection API at /v1/deploy/api/*"
  projection.go:14 "ArgoCD-UI-compatible /v1/deploy/api/v1/* surface"

The registered prefix is one constant — dashboard.go:45
`const dashPrefix = "/v1/deploy"` — and every route is dashPrefix+"/...".
The same file's own line 6 already says "no /api/, no inner /v1", and
e2e/tests/100-cd-deploy.spec.ts:68 asserts /v1/deploy/api/v1/applications
404s. So the comments contradicted the code, the sibling comment, and the
test. Comment-only: a reader copying the documented path would have built
a client against a URL that 404s.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 16:01:22 -07:00
zeekay e72addafca fix: point forge API calls at /v1 — /api/v1 is gone
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.
2026-07-26 15:51:34 -07:00
zeekay 08f2554969 fix(provisioning): hand customers a kv:// DSN, not redis://
The DBaaS provisioner returned connection strings as redis://…, and that string
goes to the customer over the JSON API as connectionString. Our own client
parses kv://, kvs:// and unix:// only, so a provisioned KV addon shipped a DSN
that hanzokv/go rejects.

The Datastore spec.type stays "valkey". That one is the operator's contract —
Engine::Valkey in operator/src/crd.rs — not our vocabulary to rename. Same for
the requirepass config directive the server reads.

Pre-existing test failures in this package are unchanged: the failing set is
identical before and after (verified by diff), and includes cases like
TestStore_InstanceColumnRoundTrips that never touch a DSN.
2026-07-26 13:20:19 -07:00
zeekay 5876cecb7a refactor(kb): one prefix — /v1/kb
The knowledge surface mounted every handler twice, at /v1/knowledge and /v1/kb.
Two paths to one handler is two answers to "where is this", and the smoke test
had already picked the other one from the package doc.

/v1/kb is the prefix. The package doc and the smoke check follow it.
2026-07-26 13:16:37 -07:00
zeekayandhanzo-dev 6e82c09897 chore: commit outstanding working-tree changes
10 files changed, 102 insertions(+), 102 deletions(-)

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 13:16:37 -07:00
3baf677016 feat(sync/tracker/git): GitHub App → native tracker mirror + index-on-import + .hanzo/workflows orchestrator (#357)
The native side of the org-wide GitHub App sync. The push→reconcile path already
existed (githubWebhook → cloud.Sync); this adds the two missing halves the owner
asked for and layers /v1/code over every mirrored repo.

TRACKER MIRROR (issues → native tracker, the one way, no second store):
- tracker_seam.go: cloud.UpsertIssue inversion seam (twin of cloud.Sync) — feeders
  never import clients/tracker.
- clients/tracker/github_sink.go: registers the sink; idempotent-by-ExtRef upsert
  into one "GH" team (Source=git, Repo discriminator), open/closed→todo/done.
- clients/tracker/store.go: GetIssueByExtRef + (org,project,ext_ref) index.
- clients/integrations/github_webhook.go: `issues`/`issue_comment` → mirror the
  parent issue (same signed-installation→org resolution as push).
- clients/integrations/github_issues.go: mirror mapping + POST
  /v1/integrations/github/issues/backfill (bounded, idempotent, returns counts).

INDEX-ON-IMPORT (/v1/code covers EVERY mirrored repo, not just pushed-since-import):
- clients/git/index_on_import.go + ImportRepo/mirror: emit the SAME
  cloud.LifecyclePushLanded the push/inbound paths emit, so index_on_push indexes
  the default-branch tip on import too. Origin = source host → mirror_out suppresses
  the echo. Detached + best-effort (never blocks/fails the writer).

.hanzo/workflows NATIVE CI/CD (design + dormant MVP):
- clients/git/build_on_push.go: a lifecycle reactor that reads .hanzo/workflows/*.yml
  (or root hanzo.yml, same images: schema) at the pushed tip and enqueues each image
  to platform /v1/arcd/enqueue (BuildKit→operator), NO GitHub Actions. Ships DORMANT
  (no-op unless CLOUD_NATIVE_CICD_ENABLED + the enqueue token) so linking is inert.

Tests: tracker sink (idempotent upsert + status map + isolation), integrations
compile+run, git import emits push.landed, orchestrator parse/body/tag/owner map.
All green (CGO_ENABLED=0, pure-Go as prod ships).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-26 12:30:54 -07:00
antje bb50b2aeef docs: name our engine Hanzo Datastore in comments; fix stale driver claims
Comment/prose only (plus one test's own t.Fatal diagnostic string).
go build + go vet green on every touched package.

clients/o11y/LLM.md also carried two claims the code disproves: it said the
query plane READS "via clickhouse-go v2.44.0 (upstream)" and pins "upstream
ch-go v0.71.0". Neither module is in the tree —

  grep -cE 'ClickHouse/ch-go|ClickHouse/clickhouse-go' go.sum go.mod -> 0 0
  clients/o11y/event_ingest.go:59:  datastore "github.com/hanzo-ds/go"
  go.mod: github.com/hanzo-ds/go v1.0.1 · github.com/hanzo-ds/native v0.72.0
  gh api /repos/hanzo-ds/native -> "de-branded fork of ch-go"

Deliberately NOT renamed, each verified third-party:
  - clients/blueprint/estimate.go dbHints — sniffs a USER's project deps
  - clients/guide/base.yaml — factual prose about ClickHouse Inc's public
    benchmarks; rebranding it would make a true statement false
  - clients/samples/live_test.go — `docker run clickhouse/clickhouse-server`
  - o11y/LLM.md `clickhousetraces`/`clickhouselogsexporter` — OTel exporter
    factory type strings, must match the compiled collector
  - o11y/LLM.md `ch-go` where it describes the external dd-sketch exporter
2026-07-26 11:54:31 -07:00
zeekayandhanzo-dev 517b8a0650 ci(containment): prove containment from the import graph, not from a link
The containment job led with `go build ./...`, which links every cmd/ main —
and linking needs native/flags/target/release/libhanzo_flags.a, the Rust
staticlib clients/flags pulls in under cgo. Nothing in this job builds it:
`make native` runs in the gate job, in that job's own workspace. On GitHub it
passed only because the arc runners reuse a workspace and target/ is
gitignored, so an earlier gate job's leftover .a was still on disk. On a
container runner with a fresh volume there is no leftover, and every cmd/ main
died at `ld: cannot find .../libhanzo_flags.a` — a guard job failing on an
artifact it does not own, telling us nothing about containment.

Containment is an import-graph property and `go list -deps` — already the
check doing the real work here — reads the same untagged file set without
linking. The compile added no proof, only a second place that has to build.
The gate job stays the ONE place that builds.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 11:22:30 -07:00
zeekayandhanzo-dev 526172f200 test(apps): add the prefs frozen row — wire golden was latent-red on main
Wire() mounts prefs (dd20b05f) between settings and notify; the frozen
sequence never got the row, so TestWireOrderMatchesFrozen has failed on main
ever since with "Wire() has 107 specs, frozen sequence has 106". Same shape as
fe63e9bb (destinations).

The row records what Wire actually does — OwnsHealth false, Shutdown non-nil
(prefs.Shutdown closes the store) — so the golden still fails the moment the
mount ORDER or those flags change, which is the only thing it is for.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 11:22:22 -07:00
hanzo-dev 71bead9cea paywall: flip it from admin.hanzo.ai — no redeploy
The switch was already in the cockpit and already registered; it just governed
nothing. clients/flags imports the root package, and the root package imports
routers to mount the edge middleware, so root could never import flags and no
filter mounted from serve.go could read a switch. `paywall_enforced` therefore
drove clients/entitlements.RequireProduct — a leaf, free to import flags — while
the paywall serve.go actually mounts stayed env-gated. And RequireProduct is
mounted nowhere, so flipping that switch changed nothing at all.

Inverted at the direction the dependency already runs, rather than fighting it:
the root package holds the seam (switch.go — SetSwitchReader in, Switch out),
flags fills it on Mount, serve.go reads it. No new import in either direction, and
the key is a constant in the root package so the registry entry, the evaluator and
the edge cannot drift onto different strings.

Enforcement is now `cfg.PaywallEnforced || Switch(...)`, so PAYWALL_ENFORCED stays
the floor: a deployment that already sets it keeps enforcing exactly as before,
and Switch reports false until an engine mounts — an unmounted switch never
enforces a paywall nobody turned on.

Tests cover dark-before-mount, that a flip reaches the edge, that flipping back
OFF restores access (the kill switch is the point), and detach.
2026-07-26 10:32:14 -07:00
zeekay 70aae48c86 fix(api): /api/ returns a real 404 instead of the console shell
We version at /v1/ and never carry an /api/ prefix. But nothing enforced it:
an /api/ request matched no route, fell through to the SPA mount, and came
back 200 text/html. So api.hanzo.ai/api/v1/user rendered the console page,
and api.hanzo.ai/api/totally-made-up-nonsense answered 200 as well.

A caller on the wrong prefix got a page that looked like it worked instead of
an error telling them the prefix does not exist. Adding /api/ to apiPrefixes
puts it in the same class as /v1/, /zap and /healthz: an unmatched path there
is a real 404 in JSON, never the shell.

Pinned with a regression test, since the failure mode is a 200 that looks fine
rather than a crash.
2026-07-26 10:24:38 -07:00
zeekay 2c887dba3b chore(deps): luxfi/kms v1.11.8 -> v1.12.9
KMS is the embedded luxfi/kms SecretStore in this binary serving /v1/kms/*,
and it was eight minor versions behind. The standalone image in-cluster is
already v1.12.10, so the library the API runs on was older than the daemon it
replaced. clients/kms builds on it.
2026-07-26 10:16:53 -07:00
hanzo-dev 704011d389 paywall: read enforcement per request, and name why the cockpit cannot reach it
You asked to flip the paywall from admin.hanzo.ai. Two things stood in the way,
and only one of them is code I can move.

Fixed: enforcement was evaluated ONCE at mount — Paywall(bool) chose a
passthrough closure at startup — so the value could not change without
restarting the binary. It is now a func read per request, so the moment a
reader is wired the switch hot-applies. A nil reader is the dark default.
serve.go passes cfg.PaywallEnforced for now, byte-identical behaviour.

Also gave the cockpit switch the env fallback it was missing: the
`paywall_enforced` Def registered no Env, so it resolved store -> "false" and
ignored PAYWALL_ENFORCED entirely. Anyone reading that switch got a different
answer than the running gate. It now falls back to the same env var, and
entitlements exports Enforced() as the ONE reader of the key.

NOT fixed, because it is structural and worth stating rather than hacking
around: clients/flags imports the ROOT package (cloud.Deps/Handle/OrgStore),
and the root package imports routers to mount this middleware. So root can
never import flags, and NO edge filter mounted from serve.go can read a
switch. That is why `paywall_enforced` governs
clients/entitlements.RequireProduct — a leaf, free to import flags — while the
middleware serve.go actually mounts is env-gated. Worse, RequireProduct is
mounted NOWHERE (every call site is a commented-out example), so flipping that
switch in admin.hanzo.ai today changes nothing at all. Closing it means either
inverting flags off the root package, or moving enforcement onto RequireProduct
at the gated route groups. Both are real changes; neither is a config nudge.

Tests: enforcement flips on an already-mounted app (on, off, and back — the
kill switch must restore access), and a nil reader never gates.
2026-07-26 09:11:11 -07:00
hanzo-dev 21cd20589e deps: pin commerce to a real tag — main did not build
go.mod pinned github.com/hanzoai/commerce v1.49.20-0.20260726065453-1f6a1e10775c.
A vX.Y.Z-0.<ts>-<hash> pseudo-version means "a commit after vX.Y.(Z-1)", so Go
validates it against v1.49.19 — and that tag is NOT on the remote. commerce jumps
v1.49.12 -> v1.49.20 there, while v1.49.19 exists only in a local clone, so it was
either never pushed or later removed. Every consumer of the module graph therefore
failed resolution, not just one package:

  invalid pseudo-version: preceding tag (v1.49.19) not found

Reproduced on pristine origin/main, so this is not from any local edit. It is the
same shape as the iam v1.33.6 re-tag: a moved or missing tag breaking everyone
downstream, and it blocks building a cloud image at all.

Fixed by pinning the real immutable tag v1.49.21, which CONTAINS the commit the
pseudo-version was reaching for (verified: git merge-base --is-ancestor
1f6a1e10775c v1.49.21). That also satisfies the standing rule that pins are
immutable semver, never floating or derived.

Verified: ./clients/commerceclient builds, and the root package, ./routers and
./clients/entitlements all vet clean. The remaining local link errors are a
missing prebuilt native/flags/target/release/libhanzo_flags.a, which CI builds —
unrelated to this and present before.
2026-07-26 09:10:55 -07:00
zeekay 6c720908f4 chore(deps): hanzokv/go v9.22.0, via hanzoai/o11y
v9.22.0 renames the package identifier from redis to kv, and its companion
modules moved path with it: extra/redisotel -> extra/kvotel and extra/rediscmd
-> extra/kvcmd, which stop at v9.21.1 under the old names.

Nothing in cloud imports any of them, but hanzoai/o11y's rediscache does, so
cloud cannot bump the client alone: extra/rediscmd v9.21.1 still says redis.X
and does not compile against a package now called kv. Taking o11y at
2b66f3201, which moved to the kv-named companions, resolves all three
consistently.
2026-07-26 08:59:57 -07:00
hanzo-dev 2b3f5f6f58 paywall: decide on a canonical path, so casing and a slash cannot flip the gate
Two bugs, one cause: gated() and allowlisted() compared the raw request path
against lists written in lower case with no trailing slash. The same route in
another form missed both, and which list it missed decided which way it broke.

  /V1/chat/completions   missed the "/v1/" prefix    -> skipped the paywall
  /v1/IAM/callback       missed the "/v1/iam/" allow -> 402 on an OAuth callback
  /v1/signin/            matched no exact case       -> 402 in front of sign-in

So a shift key was a bypass, and a trailing slash was a lockout. Both are now
one canonical() applied once at the top of gated(), with allowlisted() reading
the folded value — the gate decides on a single form and cannot disagree with
itself. /v1/ itself is untouched: nothing is trimmed below the prefix.

Tests assert both directions, including that folding does not open a hole
(/V1/chat/completions/ still gates) and that the non-/v1 surface is unaffected.
Verified they catch the bug rather than restate the code: with canonical()
stubbed to fold nothing, all four fail and name each path above; with the fix,
the package is green.

Enforcement is still off (PAYWALL_ENFORCED=false), so this changes nothing in
production today — it removes two of the reasons the flag could not be flipped.
2026-07-26 08:39:21 -07:00
zeekay 26d5e0f433 fix(docker): run tini as PID 1 so orphaned git children get reaped
/cloud is PID 1 in its container (ENTRYPOINT ["/cloud"], no init wrapper,
shareProcessNamespace unset), and PID 1 inherits every orphaned descendant.

git is not one process. fetch/clone fan out to git-upload-pack,
git-index-pack, git-rev-list and git-pack-objects. When cloud kills a wedged
direct child — gitPackStream.Close does exactly that, and correctly, to avoid
hanging on a disconnected client — those grandchildren orphan and reparent to
PID 1. A Go program never reaps adopted orphans and there is no SIGCHLD
handler anywhere in this codebase, so each one becomes a permanent zombie
holding a PID slot.

Measured on worker-xl-37bw71 via a hostPID probe:

  == total procs: 18741
    18553 git
  == zombie count: 18553
  == zombie git PPIDs: 18553 -> ppid 4141630
  --- ppid 4141630: /cloud

18,553 of 18,741 processes on that node were zombie git, every one parented
to /cloud. The node crossed kubelet's pid.available<10% threshold and evicted
pods — including cloud itself, which is replicas:1/Recreate, so it was a full
/v1 outage until reschedule. insights-web went with it. A zombie consumes no
CPU and no memory, so nothing but the eviction ever surfaced it.

Every gitCmd() call site was audited first: all 17 reap correctly via Run,
Output, withPackSlot(ctx, cmd.Run) or Start+Wait. The leak was never a missing
Wait in this code — it is the grandchildren, which only an init can collect.

`--` keeps cloud's own args untouched, and tini forwards signals unchanged so
SIGTERM still drains normally. `test -x /sbin/tini` makes a wrong path fail
the BUILD rather than producing an image that cannot start, matching the
existing `test -n "$SC"` guard beside it.
2026-07-26 06:53:17 -07:00
zandhanzo-dev 06e399491b feat(build): stamp VERSION from the image tag
Pass the image tag through to buildkit as build-arg:VERSION, so a binary reports
the version it was actually published under (cloud links it into cloud.Version →
the X-Api-Version header) instead of the "dev" default.

The tag is already the authority for what is being built, so deriving VERSION
from it means the reported version can never drift from the ref that was pushed.
Skips "latest" (not a version) and is a no-op for any Dockerfile without an
ARG VERSION.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-26 01:06:53 -07:00
zeekay f0ab9e7fb9 chore(deps): drop upstream go-redis — one KV client, at github.com/hanzokv/go
cloud imported NEITHER redis client in its own source; both were `// indirect`,
reached through four dependencies. Each has now moved, so tidy drops upstream:

  o11y/pkg/cache/rediscache   (also carried extra/redisotel + the redismock test)
  hanzoai/ai/object
  hanzoai/commerce/infra
  hanzoai/orm

github.com/redis/* count in this go.mod is now 0. Editing cloud directly at any
point would have been a fix at the wrong layer — the duplication lived upstream
of it.
2026-07-25 23:56:56 -07:00
antje dd20b05f41 feat(prefs): one per-user preference plane, so a person is the same person in every product
Today each surface keeps its own copy of "who you are and how you like things" in
its own localStorage, so the same person reads as two different users depending
on which tab they are in — the console remembers a theme insights has never heard
of, and neither survives a new device.

`GET/PATCH /v1/prefs` is the one place that answers it. Two decisions carry the
design:

PATCH, not PUT. A surface saves the keys it owns and nothing else. Under a PUT
every client would be responsible for preserving every other client's keys, and
the first one to forget would silently delete them — so the merge lives on the
server, inside the store transaction. Read-modify-write across two calls is a
lost update, and multi-tab saving is the case a preferences surface actually
sees, not an edge case.

The key is the canonical `<owner>/<name>`, never the bare X-User-Id. A bare name
is not unique across orgs: `hanzo/z` and `admin/z` are two different people, and
keying on `z` would hand one of them the other's document.

Isolation is server-side on every statement, and there is deliberately no path to
read someone else's preferences — not for an org admin, not for a platform
SuperAdmin. Nothing here is a credential, so unlike settings there is no KMS split
to maintain; if a preference ever needs custody it does not belong in this table.

Tests: 8 merge/decode cases (a partial save preserves a foreign surface's keys; a
null value deletes; a nested object is REPLACED, not deep-merged, so a value can
actually be cleared; a corrupt row starts the user fresh instead of failing every
future write; the bound holds on the merged result, not just the patch) plus 3
real-SQLite cases (missing reads as empty, two writers' distinct keys both
survive, two subjects never share a document).

The store tests inject a throwaway cek master key rather than skipping without
one — they skipped on an encryption-capable build at first, which meant the
isolation invariant was untested on exactly the configuration production ships.
2026-07-25 23:09:06 -07:00
antje 98e05b6aa4 git: delete the unwired import trio — one import path, not two
importrepo.go added POST /v1/git/repos/:name/import but the route was never
registered, so its three tests 404'd and go test ./clients/git was red. It
re-composed the exact primitives github_import.go already wires (importFetch,
ensureMirrorTarget, RecordConflict/ClearConflict) — a duplicate import path,
not a second concern. ci.go committed .hanzo/workflows via that dead path only.

Delete all three (719 lines). github_import.go remains the one import path;
the git suite is green.
2026-07-25 22:13:18 -07:00
a1bf850c96 feat(deploy): GET /v1/deploy/gitops — the CD plane read, distinct from the workload board
Every other read in clients/deploy projects operator App CRs: one row per
workload, declared vs running tag. A CD Application (apps.hanzo.ai/v1alpha1) is
the layer ABOVE that — the git source CD polls, the commit it last applied, the
deploys it performed.

They disagree in exactly the case an operator most needs to see: main carries a
new image pin, CD has not applied that commit yet, so every App CR still declares
the old tag and the drift board reads "Synced" while the deploy is stuck. Reading
the CD plane makes that visible instead of invisible.

k8s.CDApplications is the shared coordinate (clients/k8s), not a private copy.
Build + clients/deploy tests green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 17:37:14 -07:00
f0931cab5f chore(sync): delete the per-repo sync.yml — superseded by the org webhook
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>
2026-07-25 17:37:14 -07:00
antje fbe41ec92b feat(entitlements): standing, git import, principal wallet
Lands the in-flight work alongside the two auth/royalty commits already on
main: an entitlements standing check with its tests, the git CI + repo-import
clients, and the principal wallet. Builds clean (go build ./... exit 0).
2026-07-25 15:35:07 -07:00
antje f50f29a8bb cloud auth: exclude ALL machine principals from SuperAdmin (red M1 fix)
Follow-up to the audience decomplection (f429d7228). Red found that once the aud is
no longer a gate, owner==adminOrg becomes the sole key to cloud SuperAdmin, reachable
by ANY admin-org client_credentials app — and the existing exclusion
(isKMSMachinePrincipal) only caught the one -platform-kms audience. A generic admin-org
machine app (or IAM's blank-Organization→adminOrg default) would inherit platform-admin.

Fix: idClaims now parses IAM's `type` claim; isMachinePrincipal(claims) =
type=="application" OR the owner-bound KMS-sync audience. The SuperAdmin grant and the
X-User-IsOrgAdmin mint both gate on !isMachinePrincipal. type=="application" catches
EVERY machine app (object/token_oauth.go stamps it); the KMS-aud union is the
defensive fallback for a token missing `type`. Fail-closed: unknown/empty type is
treated as NON-machine so a real human admin (owner==adminOrg) is never locked out —
human admin behavior is UNCHANGED (a human admin token, any audience, still SuperAdmin).

Proven: new TestSanitizeIdentity case 'admin-org application-type token is denied
SuperAdmin (M1)' passes; the human 'arbitrary audience still gets SuperAdmin' case and
both machine-denial cases pass; the full clients/kms red machine-token suite
(AdminSlip, ForeignMachineAud, MultiValueAud, AdminOrgMachineToken, PaaSSyncEndToEnd)
green. Also scrubs the dead jwtAudiencesFromEnv reference in clients/deploy/login.go
(L2). HELD (unpushed) pending the IAM cutover settling + red re-review.
2026-07-25 15:22:36 -07:00
zeekayandhanzo-dev cd5cbd9345 ci(cloud): CI gates, it does not deploy — drop the builder that could not build
The `deploy` job I carried over from .hanzo/workflows/deploy.yml claimed to
build the cloud image and roll it out, and could do neither. Measured, not
assumed:

- `buildctl-daemonless.sh` is not in 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).
- Its `secrets.GIT_CLONE_TOKEN` exists on neither the repo nor the org; the
  forge org carries GH_PAT, GHCR_USER, GHCR_TOKEN and nothing else.
- `kubectl patch app` is undone on the next poll by cd.hanzo.ai's selfHeal,
  which restores the CR from the universe pin.

Fixing it would have been worse than deleting it: the cloud image and its v*
tags already have exactly ONE owner, clients/platform/release.go (POST
/v1/runner {release:true}). A second builder on the same commit is the
double-build hanzo.yml's images: block already refuses by name. Rollout is,
and stays, a reviewed tag pin in hanzoai/universe.

So the native pipeline is what CI is for: gate + containment.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 15:21:51 -07:00
zeekayandantje 796ba9df68 auth: two key families and OAuth2, not six shapes
The API recognised six credential shapes — pk-, sk-, hk-, pk_, fw_, hz_.
Two of them, fw_ and hz_, were listed as API-key prefixes and minted by
nothing at all: dead entries that widened what counts as a credential
for no reason. Removed from both the authority and admission's mirror,
and from the redaction regex that enumerated the same set.

Note fw_ is still the framework module's TABLE prefix (fw_doctypes,
fw_documents, fw_roles) — unrelated to keys, untouched.

isAPIKey now reads the one list instead of repeating it as a chain of
prefix tests, so the authority is a value rather than a shape spread
across two functions.

hk- stays accepted for now, deliberately: IAM mints it (mintKey delegates
to iam.mintUserKey — cloud only validates), so dropping it here before
IAM renames the family would reject every key IAM hands out. The order is
IAM mints sk-, holders re-key, then the entry goes.
2026-07-25 15:19:04 -07:00
zeekayandantje 0b46a4ff8d feat(authors): /v1/authors/basis — an author can audit their own royalty
An author saw the AMOUNT and never the BASIS. GET /v1/authors/basis serves the
arithmetic behind the number: the share as applied, the CURRENT cost model (rate
card + class sizing, read from clients/blueprint), the immutable author_ledger
rows verbatim, the deploy edges that made each deploying org count, and a
reconciliation of ledger to balance.

The value is captured at accrual and already stored — LatchAccrual writes
share_bps/spend_cents/earning_cents in the SAME transaction as the balance
increment — so a row explains itself forever and is served verbatim, never
recomputed. The rate card is deliberately NOT stamped per row: spend_cents is
commerce's all-provider rollup, priced hour-by-hour across the month, so a single
per-row card would be a fabrication by construction. It is served separately and
labelled current via asOf. Zero schema change, zero migration.

- compute_proof is served exactly as stored: null when absent, never a hash, a
  txn id, or a word standing in for an attestation that does not exist
- PURE READ: never sweeps, accrues or pays, unlike GET /v1/authors which accrues
  lazily — an audit must not move the money it is auditing
- org-scoped from the principal; no id/org accepted from URL, query or body; an
  org with no author record gets {isAuthor:false}, never a 404 that leaks
- a row keeps the share AS APPLIED while the top level shows the current one, and
  shareSource distinguishes a negotiated override from the platform default
- reconciliation is account-wide (LedgerTotals), never the returned window, and
  window.truncated says so when rows were cut
- /v1/admin/authors/:id/basis mirrors the same builder for support
- blueprint gains Rates()/Sizing() so authors never re-declares a price or a
  footprint; the cost model keeps one owner
- authors tests gain the repo's standard TestMain dev-key shim (as in the root
  package) so the suite runs on an encryption-capable build
2026-07-25 15:19:04 -07:00
zeekayandhanzo-dev b5192af1e1 deps: ai v1.831.3 — hk- key resolution over client_secret_basic
Unblocks customer API keys. IAM gates get-user?accessKey= on a confidential-APP
principal (p.App != "" holding CapKeyResolve), and it derives p.App ONLY from
`Authorization: Basic <clientId>:<clientSecret>`. ai v1.831.2 sent a
client_credentials bearer, whose principal is org-scoped with an EMPTY App, so
every hk- key got 401 "API key validation failed: IAM error: auth:Unauthorized
operation". v1.831.3 sends Basic — probed live against prod IAM v1.33.8 with
the real hanzo-cloud credential: Basic → 200 ok, bearer → auth:Unauthorized
operation, query-params → 401.

Also collapses the balance gate's duplicate resolver onto the same one, so the
prepaid gate stops silently fail-opening on hk- keys.

The application row needed no change: it is already admin/hanzo-cloud, and
admin IS a reserved signing owner, so the owner-pin was never the blocker.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 15:16:59 -07:00
antje e12a781599 fix(build): pin the prebuilt inputs — a cloud image was not reproducible
`ARG CONSOLE_IMAGE/SKILLS_IMAGE/FLAGS_IMAGE` all defaulted to `:latest`, and those
defaults are LOAD-BEARING: the builder that actually ships our releases is the native
one (POST /v1/runner -> launchDirectBuild -> BuildKit) and it passes no --build-arg.
`release.yml`, which the old comment said would "resolve CONSOLE_IMAGE to a fresh
digest", is a stub and resolves nothing. So the console baked into a cloud image was
decided by WHEN the build ran, not by what we shipped — build the same cloud sha twice,
get two different products.

It bit today: cloud v1.801.215 was built ~12 minutes before console CI finished
publishing the console-embed carrying v8.5.26, so a release whose entire purpose was
that console change silently baked the previous console and went green. On the live
site `document.fonts.size` stayed 0 and every customer kept reading the product in a
fallback face. Nothing failed; the version number just stopped meaning anything.

Pinned to the immutable per-commit tags each input's own CI publishes. A console,
skills or flags change now reaches production through a reviewable cloud commit that
names it — which is the same "floating tags never reach a cluster" rule we already
apply to cluster pins, applied one layer down where it was quietly missing.
2026-07-25 15:02:21 -07:00
zeekayandhanzo-dev b6042582b8 ci: one native pipeline — the gates now gate the deploy
.github/workflows holds exactly one file: the sync nudge, which runs zero CI.
The three pipelines that used to run beside each other are one graph in
.hanzo/workflows/cicd.yml:

  .github/workflows/cicd.yml       -> job `gate`         (unchanged caller;
      every real detail still lives in hanzo.yml, which platform.hanzo.ai
      reads too, so no build logic moved)
  .github/workflows/containment.yml-> job `containment`  (verbatim; only its
      own self-exclusion path follows the file)
  .hanzo/workflows/deploy.yml      -> job `deploy`, needs: [gate, containment]

That needs: edge is the whole point. deploy.yml fired on `push: main`
independently of both gates, so a red suite or a containment breach still cut
an image and patched three operator apps — the gates could only report a fact
the deploy had already ignored. One graph is the only way one job blocks
another.

Two defects fixed on the way:

- deploy.yml declared no `workflow_dispatch`, but sync-from-github.yml
  dispatches the pipeline by name after every fast-forward (a push made with
  the workflow token triggers nothing). That curl could only 404, so synced
  commits built nothing. cicd.yml declares the trigger; the sync now names it.
- hanzo.yml still credited a release.yml that was deleted. The v* tags and the
  main image are owned by clients/platform/release.go (POST /v1/runner
  {release:true}) — the in-cloud port of that workflow.

Not yet live: hanzoai/cloud on git.hanzo.ai is still a Gitea PULL MIRROR with
Actions off (measured: mirror=true, has_actions=false), so nothing under
.hanzo/workflows runs there until it is converted to canonical
(hanzoai/.github: scripts/forge-migrate.sh convert).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 14:57:57 -07:00
zeekayandhanzo-dev 249efbee86 o11y(vmproxy): admit the absolute fleet signals and live alert state
The Lux board's allowlist described the fleet only in relative terms — who is up,
who is at what height, who has peers. A fleet that has stopped agrees with itself
perfectly on all of it: same height, same hash, five up, four peers each. The board
paints a full row of green over a frozen chain, which is how two days of freeze
looked like a healthy network.

Four series that cannot be satisfied by agreement:

  lux_network_c_tip_age_seconds     wall clock minus the freshest tip's own
                                    timestamp — climbs while the chain sits still
  lux_network_block_height_spread   a lagging or wedged validator
  lux_network_tip_hash_variants     distinct hashes at one height; >1 is a fork
  lux_network_ready_but_rpc_dead    pods reporting Ready while their RPC is dead

And the firing alert set itself, aggregated by name/network/severity. vmalert
already remote-writes its state into the same VictoriaMetrics this proxy reads, so
the board can show what is ACTUALLY firing over the path that already exists — no
second data path, no second ingress, no second access boundary to get wrong, and
no UI re-derivation of the rules that could quietly disagree with them.

The aggregation is deliberate: alertname/network/severity and nothing finer, so the
series stays small and no instance-level detail crosses the boundary.

Contract unchanged otherwise — exact-string allowlist, SuperAdmin-only, fail-closed.
All five allowlist and gate tests pass.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 14:48:15 -07:00
antje 69c5fca283 fix(release): a partial tag list has no maximum — ask the registry, and fail if it can't answer
The release computed a version BELOW one already published, aimed at overwriting it.
Measured today: `POST /v1/runner {release:true}` on a tree whose live image was
v1.801.213 answered `image: ghcr.io/hanzoai/cloud:v1.801.210`.

Three defects, each fixed in one place:

1. The published-tag read asked GitHub's package-metadata API, which needs a
   `read:packages` scope our PAT does not carry. It answered 403.

2. That failure was logged as a warning and swallowed, so the version was computed
   from git tags alone. Git tags had stalled at v1.801.209 while the registry had
   reached v1.801.213 — hence 210. Folding in the published tags IS the phantom-tag
   prevention the doc comment promises; with it silently disabled, the promise was
   not kept. A partial view has no maximum, so the compute now FAILS rather than
   guesses. Fail-closed, no silent cap.

3. githubJSON decoded the body regardless of status. GitHub answers a non-2xx with
   an error object, never the success shape, so decoding it produced a bogus
   unmarshal error that MASKED the 403 — which is why this read as a decode bug and
   survived four releases. It now decodes only a 2xx and returns the status, so every
   caller's existing `if code != …` policy is reachable for the first time. The
   422-collision and 204 policies are untouched (those callers pass out=nil).

The registry, not GitHub's metadata API, is now the authority on which tags exist:
it is what `docker pull` resolves against and what an overwrite would clobber, and
its pull scope is anonymous — one less credential in the path. Pagination is
mandatory, not incidental: GHCR caps a page at 1000 tags in insertion order, so the
newest versions are on the LAST page; reading page one alone reports a stale max, the
same unsound answer by another route. Exceeding the page bound is an error, never a
truncated list.

Tests: the regression test fails on the old behaviour with the exact signature
("compute returned 1.786.43 — a version below a pushed image") and passes on the fix;
pagination proves the last page's max wins; githubJSON proves 403 surfaces as 403.
2026-07-25 13:59:35 -07:00
zeekayandhanzo-dev 0c805b9367 fix(sync): the nudge runs on OUR pool — GitHub-hosted is billing-blocked
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>
2026-07-25 13:46:51 -07:00
zandhanzo-dev 6158f6b111 refactor(k8s): one declaration per cluster coordinate, six copies deleted
The App CR coordinate was declared three times under two names (paas appsGVR,
deploy appsCRGVR, platform appsGVR); Deployments twice; Namespaces three times
(platform namespacesGVR, provisioning nsGVR, ml nsGVR). Same value, six extra
places to disagree.

That is not hypothetical here. The whole point of the App/Service kind migration
is that this coordinate CHANGES, and a subsystem holding a private copy silently
reads the wrong resource and reports an honest-looking empty board — which paas
already shipped once (it scanned services while the fleet had moved to apps).

clients/k8s now holds Apps, Deployments and Namespaces; 18 files reference them.
There is deliberately no Services coordinate: the fleet holds zero of that kind,
so offering it would invite the same bug back.

Build + vet clean across paas/deploy/platform/provisioning/ml/k8s; paas and apps
tests green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 13:46:31 -07:00
zeekayandhanzo-dev f0a1d510bf ci: wire cloud's sync, and say plainly why GitHub still runs two gates
Adds the two halves of the sync this repo never had, and deletes the tombstone:

  .github/workflows/sync.yml            nudge git.hanzo.ai on a GitHub push
  .hanzo/workflows/sync-from-github.yml 10-min fast-forward, fail-loud
  .github/workflows/release.yml         DELETED — since a877eda2 it existed
                                        only to echo "the native pipeline is
                                        deploy.yml". A workflow whose whole job
                                        is to announce that it is not the
                                        pipeline is the tombstone the law
                                        abolishes; sync.yml's header carries
                                        that sentence now.

cicd.yml and containment.yml STAY, and the reason is measured, not deferred:
against the live forge, hanzoai/cloud reports `mirror: true` and
`has_actions: false` — it is a Gitea pull mirror with Actions disabled, and
`/api/v1/repos/hanzoai/cloud/actions/tasks` returns ZERO runs, so
.hanzo/workflows/deploy.yml has never executed. Moving the GitHub gates now
would not relocate CI, it would end it: cicd.yml is the only running test gate
plus the cloud-flags image, and containment.yml is a SECURITY control (no
release binary may link clients/controlplane or spoof testing.Testing()).
Compare hanzoai/app, which reports `mirror: false, has_actions: true` and whose
native ff-main run succeeds every 10 minutes — that is what this repo needs.

The unblock is one act on the forge, not a code change: convert hanzoai/cloud
from pull mirror to canonical, which is also what enables Actions
(hanzoai/.github scripts/forge-migrate.sh convert --repo hanzoai/cloud). The
files are staged so the flip is the only remaining step.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 13:40:30 -07:00
antje a4e4d551af ci(native): runs-on hanzo-build-linux-amd64 — the label runners declare
Runners declare [ubuntu-latest ubuntu-22.04 ubuntu-24.04
hanzo-build-linux-amd64]. 'hanzo-linux-amd64' is not among them, so this
workflow's jobs queue forever unclaimed — which is why this repo has never
produced a native build (actions/runs total_count was 0).
2026-07-25 13:27:48 -07:00
z e6d7c23237 fix(auth): ai v1.831.2 — hk- API keys resolve via bearer (GA blocker)
Picks up the fix for: every customer hk- key 401'd at inference because
getUserByAccessKey authenticated to IAM with query-param clientId/clientSecret,
which yields no principal and so can never satisfy authz.CapKeyResolve.

Pairs with IAM_KEY_RESOLVE_APPS=hanzo-cloud on the cloud CR — the allowlist is
fail-secure, so both halves are required.
2026-07-25 13:06:33 -07:00
zandhanzo-dev de5782e48b feat(paas): discover the scan set so tenant-<org> workloads are visible
The scan set was a literal list, so a tenant namespace was invisible however
correctly it classified. discoverNamespaces asks the cluster instead — listing
NAMESPACES (the honest question: 'which namespaces are ours?') rather than
deriving the set from a cluster-wide CR list, which would answer a different
question and pull every tenant's objects through this process to do it. No new
RBAC: the cloud SA already holds namespaces get,list.

Safety properties, both pinned by tests:
  * discovery only ADDS to the first-party set, so an empty or failed listing
    degrades to previous behavior instead of blanking the board. (Caught by
    TestDeploy_SuperAdmin_EnvSelectsNamespace: an early version returned only
    what it discovered, and a fake with no Namespace objects produced an empty
    scan set -> 404.)
  * nsClass still filters, so a namespace that is not ours can never enter the
    set however discovery goes.

Tenancy is unchanged and still computed BEFORE any List: scopedNamespaces
confines a non-super OrgAdmin to namespaces whose tenant equals their validated
org; a tenant-<org> namespace authorizes to that org.

The cache sits behind a POINTER because cloud.Service stores State by value — a
mutex in  is copied and guards nothing (go vet: 'assignment copies lock
value'). vet is clean.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 12:50:33 -07:00
zandhanzo-dev c0b285183a refactor(paas): one total namespace classifier; unhide hanzo-mainnet
Three places encoded one fact and had drifted apart: the nsEnv map (3 namespaces),
nsOrg's suffix-strip (knew only -devnet/-testnet), and scanOrder's literal list
(the same 3). A tenant-<org> namespace matched none of them, so it classified as
its OWN org and was never scanned — tenant workloads were invisible by
construction, and hanzo-mainnet's CR was invisible too.

nsClass(ns) -> (tenant, env, ok) is now the single source of that truth, and it is
TOTAL: every input is decided, an unrecognised namespace is classified OUT rather
than guessed at, so the reader still cannot reach beyond the platform tier. nsOrg,
envOf and nsForEnv are projections of it; the nsEnv map is deleted. There is no
second place left to disagree.

Tenancy is unchanged and still computed BEFORE any List: scopedNamespaces confines
a non-super OrgAdmin to namespaces whose tenant equals their validated org, so a
tenant-<org> namespace now authorizes to that org instead of to hanzo.

scanOrder gains hanzo-mainnet (first-party, was missing). Discovering tenant-*
needs the dynamic client threaded into the scan set — the follow-up; the
authorization axis it needs already exists.

Tests: scanOrder now asserts the invariant that matters (every scanned namespace
classifies to a real tenant, else it would render rows no OrgAdmin could be
confined to), plus a totality/confinement table incl. tenant-maxpower -> maxpower,
tenant- -> out, kube-system -> out, hanzo-evil -> out.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 12:28:07 -07:00
06029d645f fix(apps): wire the orphaned platform + projects Shutdown (SIGTERM resource leak)
Both subsystems define Shutdown and neither was wired, so the serve layer never
called them: platform.Shutdown (clients/platform/platform.go:892) cancels the
build-reconciler goroutine and the compute meter and closes the store;
projects.Shutdown closes its store. On SIGTERM both were orphaned.

wire_test encoded the leak as expected behavior (hasShutdown: false) — it now
asserts the fix. platform.Shutdown/projects.Shutdown are func() error, so they
take the same ctxShutdown wrapper as wallets/x402/framework/content.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 11:53:35 -07:00
hanzo-dev 75e5615b0b destinations(insights): the project token is ours (hi_), not an upstream phc_
The adapter documented its credential as 'e.g. phc_…' — an upstream brand that
does not exist in our fork. Hanzo Insights already issues Hanzo-branded tokens
(insights/models/utils.py: hi_ project, hix_ personal, his_ secret, hia_ oauth),
and capture's validate_token takes any ASCII<=64 string — it only REJECTS the
personal prefixes. So the insights sink needs a hi_ project token from our OWN
instance: one auth system, no upstream credential, nothing to invent.
2026-07-25 11:34:25 -07:00
antje ffaa319c6e refactor(o11y): rip the CLOUD_OTLP_INGEST_ENABLED gate — capability, not a flag
The embedded OTLP ingest was gated behind a boolean env on top of its real
precondition (a datastore DSN). That extra switch is what let the fleet's ONLY
ingest path be silently turned off: the standalone collector it was meant to
fall back to is retired, all 24 otel-agents target cloud:4318, and every one of
them sat in connection-refused / queue-full / 'Rejecting data' — logs from every
service discarded, with nothing surfacing the loss.

Ingest now runs exactly when a DSN is configured, because the DSN is what it
writes to. One condition, derived from actual capability. Fail-soft on
construction error is unchanged, so a bad telemetry config still cannot take
cloud down. Dropped TestIngestEnabled with the function it covered.
2026-07-25 11:09:43 -07:00
hanzo-dev d3a640bae8 destinations: our first-party sinks are Hanzo-branded; upstream names live only in NOTICE
The two FIRST-PARTY sinks leaked their upstream fork names into the public API:
Name() returned 'Hanzo Analytics (Umami)' / 'Hanzo Insights (PostHog)' and the
platform IDs — which are the API path (/v1/destinations/<id>), the DB platform
column, and the KMS secretsPath — were literally 'umami' / 'posthog'. These are
OUR products, so they are now named for Hanzo, one way:

  id 'umami'   -> 'analytics'   Name 'Hanzo Analytics'   (analytics.hanzo.ai)
  id 'posthog' -> 'insights'    Name 'Hanzo Insights'    (insights.hanzo.ai)

Error strings follow ('analytics: websiteId is required', 'insights: api_key is
required'). Upstream attribution moves to a NOTICE file — the ONE place it
belongs — covering Umami, PostHog, Casibase, and Casdoor.

Left alone deliberately: integrations/analytics.go's 'posthog' provider is a
GENUINE third-party connector (PostHog Cloud, the user's own Personal API Key),
like ga4/meta — naming a real external service is correct, not a brand leak.
Source comments that explain which upstream a fork derives from are engineering
attribution, not user-visible branding.

Build green. The 2 store/fanout test failures are the pre-existing KMS
fail-closed guard (CLOUD_KMS_MASTER_KEY_REF required) — identical on clean main,
verified by stashing this change.
2026-07-25 10:59:45 -07:00
antje 4ffb8852b9 ask: route research synthesis to an available capable model + fallback
/v1/ask web synthesis routed to deps.AIDefaultModel (bare deepseek-v4-flash),
a paid third-party flash model. When it is throttled, out of balance on the
M2M identity, or its provider is down, synthesize() emitted the degraded
"model is unavailable" note even though sources were grounded — a weak answer
for research/deep, the mode that most needs a strong writer.

Route synthesis per mode with a fallback chain (synthModels): research/deep
lead with zen5 (a capable Hanzo model that streams FREE on the binary's M2M
identity — strong + always reachable), search/news with zen5-flash (fast
tier). Caller in.Model still wins; CLOUD_ASK_MODEL_<MODE>/CLOUD_ASK_MODEL
override; deps.AIDefaultModel is appended as a final backstop. synthesize()
now tries the chain in order and only degrades honestly when EVERY model is
down — a single model outage advances to the next capable model instead of
emitting an empty/weak answer. Additive: books-advisor (empty mode) and the
per-answer metering are untouched.

Proven on the live M2M path: model=zen5 -> strong, clean, 12-source Clojure
research report (deepseek-v4-flash intermittently 402s; zen5 200s free).
2026-07-25 10:23:26 -07:00
zeekayandhanzo-dev 4efffd4944 feat(team): Inbox activity-notification feed (mentions, DMs, comments, assignments)
The workbench Inbox activity feed was always empty: the write path materialized
DocNotifyContext (seed.go projectNotifyContexts) but never generated the
InboxNotification docs the Inbox reads. The classic Inbox
(notification-resources/InboxNotificationsClientImpl) reads notifications via
findAll — findAll(notification.class.ActivityInboxNotification, {user,
archived:false}) and CommonInboxNotification — the SAME query path as
DocNotifyContext, NOT domainRequest (that stub serves the separate, newer
@hcengineering/communication operation-domain, a different wire shape the classic
Inbox never queries).

notify.go adds projectNotifications, the trigger the write path (txCreate/txUpdate)
runs after applying a content Tx. It generates ActivityInboxNotification docs
(idempotent, read-flag-preserving) that findAll returns:
  - @-mention in a channel message      -> notify each mentioned member
  - direct message                      -> notify every other participant
  - comment (ChatMessage on a doc)      -> notify the doc's subscribers + mentioned
  - assignee set on a doc (Issue, ...)   -> notify the assignee (auto-subscribed),
                                           attached to a synthesized DocUpdateMessage

Recipients are auto-subscribed (ensureNotifyContext) so the Inbox can group the
notification under a context; dncID/personSpaceOf are shared with
projectNotifyContexts so contexts never diverge or duplicate. Read/unread + the
badge count need no extra machinery — the client writes isViewed:true through the
ordinary tx path and findAll returns the updated flag.

domainRequest's communication stub is left well-formed empty and its comment
corrected to reflect that it is a separate subsystem, not the Inbox path.

Tests: mention/DM/assignment/comment each produce exactly one unread
ActivityInboxNotification returned by the Inbox findAll query; author never
self-notified; idempotent replay preserves read state; unread count shrinks on read.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 08:40:40 -07:00
antje a664c138b5 cloud: pin iam v1.33.8 — fresh forward tag, resolve v1.33.6 force-retag go.sum landmine
Supersedes the interim v1.33.7@3af15c79 pin (missing F1a/F1b/login.go — the
login code that FAILED the real-browser gate) with v1.33.8@71f7ee47 (the
real-browser-gate-GREEN cutover HEAD: /access_token alias + F1a + F1b +
login.go PKCE fix). Forward-only; go.sum reconciled to the fresh v1.33.8
hash (stale mismatched v1.33.6 + interim v1.33.7 lines swept). The /v1/ask
grounding code already on main rides along.
2026-07-25 07:04:36 -07:00
zeekayandhanzo-dev 891f0c6dfa feat(integrations): Chrome connector — local browser-extension pairing
Add Chrome as an org-plane apikey connector on /v1/integrations (the
/connectors surface both hanzo.app and the console render). It represents
pairing the Hanzo browser extension — a LOCAL install that drives Chrome
over an MCP bridge for agent tasks.

Honest model: no third-party OAuth (there is no external IdP for a local
extension). It is the framework's apikey shape with a LOCAL PAIRING token
as the credential, sealed to KMS under api_key. Verification is STRUCTURAL
(offline: non-empty + length + base64url/JWT charset, fail-closed) because
the extension bridge is localhost-bound and unreachable from cloud — no
faked remote call. AdminOnly, seal-before-row, token-free errors, parity
with the cloudflare/warpcast/whatsapp org apikey connectors.

Tests: registers + lists on /v1/integrations, verify-before-store, KMS
custody round-trip, tenant isolation, org-admin gate, no token leak.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-25 06:54:58 -07:00
hanzo-dev ed1e789634 deps: bump hanzoai/iam v1.33.6 → v1.33.7 (unjam cloud CI)
v1.33.6 was force-re-tagged on GitHub after this go.sum recorded it → the Go
proxy holds the immutable original (h1:79DN2h1R) while GitHub serves the moved
tag → 'go mod verify' checksum mismatch fails EVERY cloud build (the containment
gate), blocking all cloud deploys (exception-scrub, paywall dark-ship, console
platform-shell fix). v1.33.7 is an IMMUTABLE re-cut of the intended content
(commit 3af15c79 'serve the deployed fleet's legacy token/userinfo path aliases'
= the current v1.33.6 tip the fleet runs). Bumping to it (x.x.x+1) pins a stable,
integrity-verifiable hash. Builds green. Stop force-moving published tags.
2026-07-25 06:44:06 -07:00
antje a1d4235fc8 release: embed console@02e5478417 — platform.hanzo.ai platform-mode + OSS App Store
console-embed:latest (07:31Z) carries the native platform/deploy home + the
1030-app OSS marketplace. Cut a cloud release to embed it so platform.hanzo.ai
serves the deploy platform, not the generic console home.
2026-07-25 00:33:47 -07:00
antjeandhanzo-dev f074b4ad29 paywall: 402 gate requiring an active paid plan before product access (dark-shipped)
A request filter (routers.Paywall) that, when PAYWALL_ENFORCED=true, refuses a gated
/v1 product route from a validated org with NO active paid plan — 402
{error:"subscription_required", plan:"pro", price:"$20/mo",
url:"https://cloud.hanzo.ai/plans"} — then PAYG. Default FALSE: a DARK SHIP, zero
behavior change until an owner flips the flag. Not deployed.

- routers.Paywall (serve.go: app.Use AFTER IdentityMiddleware/BillingGate, BEFORE
  MountAll) keys on the VALIDATED principal.Org / owner claim, NEVER a client X-Org-Id.
  Decision order: dark-ship passthrough -> non-/v1 & allow-listed sell/service routes ->
  anonymous (the route's own auth answers) -> super-admin bypass -> fail-OPEN (org
  unresolved / commerce nil / read error) -> live paid plan admits -> else 402. A
  paywall in front of the pay button is catastrophic, so the allow-list exempts
  /v1/signin,/v1/signout,/v1/get-account, the WHOLE /v1/billing/* money surface (the
  console PlansModule.tsx -> PlansApi subscribe flow reads GET /v1/billing/plans; +
  subscribe/balance/payment-methods/usage/subscriptions), /v1/plans*, the /v1/iam/*
  auth/OAuth/OIDC callbacks, /v1/models*, /v1/entitlements, and every /v1/*/health.

- "active paid plan" = commerceclient.ActivePaidPlan, a NEW optional capability on the
  co-resident commerce client resolved by type-assertion (mirrors types.ModelLister) so
  the narrow CommerceClient interface, disabled.go and rpc.go are untouched; a
  split-deploy/disabled client can't answer -> nil PlanChecker -> fail open. It reads the
  org's ACTIVE or TRIALING (never canceled/past_due/unpaid, per
  commerce/models/subscription.Status), unexpired subscriptions and classifies the tier
  via clients/plan.Paid. Distinct from CheckEntitlement (per-product, Status=Active only
  -> would mis-read a trial as unentitled).

- clients/plan.Paid is catalog-driven off the embedded @hanzo/plans subscription.json
  (the money-truth): a PAID cloud tier = an account category (personal/team/enterprise)
  that costs money (priceMonthly>0 or contactSales). Realizes the owner's HARD CUT at
  "Pro ($20/mo, the EXISTING Pro plan) and above" -> {pro,plus,max,team,team-max,
  enterprise,custom} with NO hardcoded slug list; the world-*/social-* product lines and
  the free developer tier are excluded.

Tests -- go build ./... compiles clean (whole-module go vet exit 0; the only go build
./... errors are pre-existing CGO final-links of cmd/* binaries against the absent local
luxcpp lib, CI-built); go test ./routers/... GREEN 9/9: active-plan passes, no-plan 402
(exact body), allow-listed paths pass with no plan AND never consult commerce, admin
bypass, PAYWALL_ENFORCED=false everything passes, + fail-open/nil-checker/anonymous/
non-v1. clients/plan paid_test.go pins the cut to the real catalog.

Drive-by: clients/plan TestPlans_Vocab was pre-existing RED on origin/main (brittle
`!= 10` vs the v1.4.4 catalog's 12 namespaces) -> converted to a `>=10` lower bound
matching the sibling `Keys < 40` assertion, so the package is green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 23:44:01 -07:00
antje 6a0d254028 ask: native agentic web-search/deep-research grounding domain
Fold the answer-engine capability into the existing /v1/ask advisor as a new
WEB grounding domain, selected by mode (search|news|research|deep) — ONE
endpoint, not a second /v1/answer. Additive: an empty mode runs the figure
advisor (books) exactly as before.

Server-side bounded agentic loop (clean-room, not AGPL-derived): plan →
in-process native meta-search (reuses websearch.metaSearch via a new in-process
Search seam, no HTTP loopback) → server-side relevance rank/dedup → synthesize a
cited answer via the in-process AI path → follow-ups. Streams the @hanzo/ai
SearchEvent envelope (sources → status → text → follow_ups → done) over SSE, or
returns one JSON object.

Money: the web path GATES the caller's balance and METERS the resolved payer via
the advisor's own per-org ResourceMeter (Base.Bill) — the single revenue debit
(the in-process M2M AI calls are gateway-exempt). Bounded to <=3 LLM calls + a
capped set of search passes; a model outage degrades honestly and is not billed.

- clients/websearch/compose.go: exported in-process Search(ctx,query,lang) seam
- clients/ask/{web,relevance,stream}.go: the web domain, mode registry, ranking, envelope
- clients/ask/ask.go: AskRequest gains mode/q + web params; mode dispatch
2026-07-24 23:25:07 -07:00
antje e4f663aff8 chore(cloud): bump hanzoai/commerce v1.49.18 → v1.49.19 (money-path fixes)
Ships the two adversarially-found commerce money bugs live (commerce is embedded
in the cloud binary — the tag is the ship artifact):
- coupon redeem double-mint (HIGH): the once-per-user guard filtered Tags= on an
  exact string that never matched the compound written tag, so the same user
  re-minted a credit grant on every submit. Fixed with a deterministic-id
  couponredemption record (fail-closed, per-(code,user) locked). Proven + negative-controlled.
- inventory AdjustStock oversell (MEDIUM): raw deltas drove AvailableQuantity
  negative and still 200'd. Now 409 'insufficient available stock', level untouched.
commerce v1.49.19: gofmt clean, go test ./api/coupon ./api/inventory green, go build ./... 0.
2026-07-24 23:20:44 -07:00
hanzo-dev fad100a90d analytics: scrub secrets+PII from exception stacks/messages before store + fan-out
RED (o11y dogfood review) found error $exception (a *Exception struct) bypassed
scrubValue (only string/map/slice cases) — raw err.stack/message stored in
hanzo.events AND forwarded RAW to 3rd-party destinations (forward.go), leaking
tokens/API-URLs-with-query-secrets/PII, esp. now that @hanzo/event captureErrors
routes control-plane stacks (platform/console/hanzo.app all on 0.3.1).

Fix, one place: scrubException() redacts Message+Stack at the foldException fold
point (protects both the stored row and the pre-scrub fan-out copy) + a
*Exception case in scrubValue (defense in depth) + secretRe extends the string
scrubber beyond email to bearer/hk-/sk-/pk-/pk_/fw_/hz_ keys and
?token=/access_token=/api_key= query secrets. Copy semantics — never mutates the
caller. Test: email+bearer+sk-+access_token in a stack all redacted, original
unmutated. go build + package tests green.
2026-07-24 22:53:19 -07:00
zeekayandhanzo-dev 1e344c0bf4 test(admin): spend-caps write-path brand negative (red I7)
Closes the highest-value cross-tenant vector the read-path negatives don't cover: a
Lux admin POST /v1/admin/spend-caps?org=zoo must forward X-Org-Id=lux downstream
(targetOrg ignores ?org= for a non-super caller), never zoo. -race green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 18:42:38 -07:00
zeekayandhanzo-dev 64911105ff feat(o11y): Lux Network dashboard VM-proxy allowlist
Add 12 fixed, parameter-free, cluster="lux-k8s"-pinned queries to the
SuperAdmin-gated VM proxy (node/pod memory, deployment+statefulset health,
lux_validator_* + lux_network_*). Raw-query rejection + range-arg validation
intact. 5/5 TestVMProxy* green. Feeds the console 'Lux Network' board.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 17:53:03 -07:00
zeekayandhanzo-dev cd78c5b36a test(admin): brand-named tenant-scope negatives — Lux admin cannot reach Zoo/Hanzo/DO
Makes the generic escalation-line invariant concrete for the real brands the ONE
shared cockpit binary serves. An admitted Lux white-label tenant admin (z@lux.network,
org=lux) is hard-pinned to the Lux subtree:
  - cannot read Zoo org data (?org=zoo ignored → sees only lux)
  - cannot list Hanzo users (IAM read hard-pinned to owner=lux)
  - cannot reach the DigitalOcean god-views (compute/finance are SuperAdmin-only → 403)

All -race green alongside a7583e75's white-label admission suite.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 17:43:17 -07:00
hanzo-devandzeekay 743fc40b5d feat(admin): fail-closed white-label tenant admission for the operator cockpit
admin.hanzo.ai (apps/operator) is served DIRECTLY off cloud-api /v1 (the
hanzo_iam_token/cloud_session_id path SanitizeIdentity validates), so the
/v1/admin/* gate is the only boundary. GuardScoped previously admitted ANY
org-admin (principal.IsOrgAdmin) — so any customer's own-org admin could open
the cockpit. Tighten it to the WL admission tier:

  super (owner==AdminOrg, cross-tenant)  OR
  org-admin of an org in State.WLTenants (subtree-scoped via ResolveScope)

- core.State.WLTenants: fail-closed allowlist (nil/empty => SuperAdmin-only),
  seeded ONCE from ADMIN_WL_TENANT_ORGS at Mount. IsWhiteLabelTenant is the one
  read (verbatim, trimmed, no fold).
- core.GuardScoped now requires super OR (IsOrgAdmin && Org in WLTenants);
  a non-enabled org-admin gets the same 403 as a member/forge. Fleet god-views
  stay core.Guard (super-only) — a WL tenant never reaches a fleet number.
- /v1/admin/me returns isWhiteLabel + scopeOrgs so the SPA renders the subtree
  cockpit server-authoritatively (super=fleet, WL=own subtree).

Tests: WL tenant admitted+own-subtree; non-WL org-admin refused on every scoped
panel; WL tenant 403 on every god-view; fleet-only default (empty set) fail-closed;
IsWhiteLabelTenant unit-pinned. Harness enables 'maxpower' as the WL test tenant.
2026-07-24 17:43:17 -07:00
antje dfaa359511 feat(authors): accept a GitHub/GitLab ORG url in Verify a repo — owner-wide claim
Live bug: pasting github.com/luxfi (an ORG, no repo name) was rejected as malformed.
Now an org url is a first-class target — ownership proven EXACTLY like a repo claim
(the same proveOwnership: OAuth admin/push OR hanzo.json verify-code), against the
owner's canonical <owner>/.github control repo. Controlling that repo == controlling
the owner; an un-owned org fails both proofs → 422, identical to an un-owned repo.
Zero new forge methods. Deploy attribution tries the per-repo claim first, then an
owner-wide org claim — both coexist. New author_orgs table (IF NOT EXISTS, backward-
compatible), first-verify-wins. Softened the defaultShareBps comment (public rate is
presented by the FE, not promised here); the 2000 bps value + all math are byte-identical.

gofmt clean; go build/vet green; go test ./clients/authors ✓ 17/17 (14 pre-existing + 3 new:
org-url accepted+covers-owner, hanzo.json org proof, un-owned org refused).
2026-07-24 17:13:34 -07:00
antje 1ed8f3b37d platform: meter running-deployment compute → org spend (closes OSS royalty loop)
The author-royalty sweep (clients/authors) accrues 20% of a deploying org's
METERED spend, but a running template deployment added nothing to that spend —
only build minutes were metered, once (buildmeter.go). EstimateTemplate priced
the SBOM compute rate yet had no consumer. This wires the last stitch.

A periodic single-writer meter (computemeter.go), started next to the build
reconciler and stopped on Shutdown, charges every `live` app's own org for the
compute it consumed since the last tick, at its SBOM rate
(blueprint.EstimateService → the SAME rate card the console shows), through the
shared ResourceMeter → commerce ledger. The org's metered spend now carries real
running compute, so the shipped 20% sweep automatically takes its cut —
creator/treasury paid, end to end: deploy → SBOM-rate compute meter → org spend
→ 20% → creator.

Money-path correctness:
- Idempotent / at-most-once per (app, span): a per-app watermark
  (platform_apps.compute_metered_at) is compare-and-set advanced in the same
  store before the debit, so a double-tick or restart never double-charges.
- Watermark reset to now on every transition INTO live (FinalizeLive + start),
  so a stopped/redeployed app is never billed for time it was not running.
- First sight (watermark 0) starts the clock with no back-charge.
- Metered in microdollars (µ$/hr rate card) — no sub-cent rounding loss.
- Self-deploys are metered like any other app (their compute is theirs); the
  self-royalty exclusion stays entirely in the authors sweep.

blueprint.EstimateService is the single-container analogue of EstimateTemplate,
sharing one cost formula (priceFootprint) so a bare deployment and a one-service
template of the same image price identically.

Tests (CGO_ENABLED=0, -race): compute arithmetic; a live app meters its org at
the SBOM rate per hour; double-tick = single charge; first-sight/stopped never
charge; and the metered spend yields the expected 20% creator cut at monthly
scale.
2026-07-24 16:42:45 -07:00
zeekayandhanzo-dev 9fa690ad18 entitlements: server-side unified paywall (RequireProduct + /v1/entitlements)
Extend clients/entitlements with the enforcement authority behind the
@hanzogui/shell client gate — no new subsystem (frozen wire spec intact).

- RequireProduct(commerce, product): group middleware. Defers to the ONE
  authority commerce.CheckEntitlement (plan tier -> @hanzo/plans license
  features). Unvalidated -> 403; nil/error/nil-result -> ALLOW (fail open, an
  outage never locks out a paying user); definitive Active==false -> 402.
  Mirrors clients/team/entitle.go, not the fail-closed enable gate.
- GET /v1/entitlements: authoritative {tier, apps:{studio,bot,world,platform,
  team,admin}} projection the shell reads. Fails SAFE-TO-LOCKED (200, never 500)
  on commerce error; admin = c.IsAdmin().

CATALOG FLAG: @hanzo/plans v1.4.4 licensing.product_ids licenses only team/
engine/engine-rocm. studio, bot, world, platform are ABSENT, so enforcing them
now would 402 every org. Enforcement is therefore wired LIVE nowhere: world/bots/
platform carry commented RequireProduct markers (flip on once the catalog adds
the product); team keeps its deliberate observe-only gate; admin stays super-
admin gated. Projection reports the real per-org bool (studio/bot/world/platform
= false until the catalog is updated).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 16:32:04 -07:00
antje 5309dd09d3 docs(iam): supervised Casdoor→embedded-IAM cutover runbook
The code blocker is shipped (iam v1.33.6 aliases + cloud pin). IAM_CUTOVER.md is
the one-session supervised flip: migrate-v1 --dry-run drift gate → real migrate
into /var/lib/cloud/iam/iam.db (before seed) → CLOUD_ENABLE_STAGED=iam → repoint
routes.yaml iam-hanzo-ai iam.hanzo.svc:80→cloud.hanzo.svc:8000 (hot, no ingress
restart) → Playwright parity → retire the Casdoor iam CR. Each step: verify +
rollback. Money/auth-critical; explicitly NOT fired here.
2026-07-24 16:19:22 -07:00
antje 1286c41f16 chore(iam): bump embedded IAM pin v1.33.0 → v1.33.6
Picks up the legacy token/userinfo path aliases (hanzoai/iam v1.33.6) the
deployed fleet hard-codes — /v1/iam/oauth/access_token, /oauth/refresh_token,
/v1/iam/userinfo — so the Casdoor→embedded-IAM cutover serves every hard-coded
caller (hanzo CLI, KMS bridge, gateway admin/waitlist guards, commerce) instead
of 404ing them. Embedded-IAM surface (root pkg + clients/iam) compiles clean and
iamserver still exposes Mount/OpenSQLite/Seed unchanged.
2026-07-24 16:13:54 -07:00
antje bc04b675fa authors: automatic creator-payout loop — 20% everywhere, scheduler-driven, Hanzo forks → treasury
Close the OSS creator-payout loop so accrual AND payout run with no human.

20% EVERYWHERE: the treasury revenue-share policy now defaults to 20% (2000 bps)
when unset (ledger.DefaultRevenueShareBps — one place; SetPolicy still accepts any
0–10000). The 25%-era payout test is rewritten share-derived so it never drifts.
(defaultShareBps=2000 already landed @ea5ae54b4.)

AUTOMATE: clients/authors/scheduler.go mirrors clients/social/scheduler.go — a
single-writer ticker (CLOUD_AUTHORS_SCHEDULER_INTERVAL, default 1h) drives
sweepAndPayout: accrue every approved author's period royalty, then AUTO-PAY the
full pending balance. issuePayout is the ONE payout path shared by the scheduler
and the /v1/admin/authors/:id/payout operator override. Idempotent: RecordPayout's
atomic pending guard makes auto-payout at-most-once — never a double-pay, never
exceeds accrued−paid.

HANZO FORKS → TREASURY ("pay ourselves"): a repo owned by a brand org (owner ∈
{hanzoai, hanzo-*}) is auto-attributed on first deploy to the treasury SYSTEM
author (org = brand slug), so Hanzo earns 20% on its own templates when other orgs
deploy them. That royalty is realized into the treasury reserve via the shared
treasury client (new treasury.Credit → ledger Seed, idempotent by ref) — no
external wallet, no new ledger. White-label by brand (lux→luxfi, zoo→zooai).

TDD (clients/authors + clients/treasury green): 20% accrual, auto-payout
idempotency, Hanzo-fork→treasury routing (royalty never hits an external wallet),
maintainer detection.
2026-07-24 16:06:36 -07:00
antje 4ef2510254 blueprint: OSS-template SBOM → compute-cost model (/v1/blueprint)
Parse a blueprint's docker-compose into its SBOM (bill of container
images) and price the stack's CPU/memory footprint through a documented
rate card (microdollars per vCPU-/GB-hour, DigitalOcean-droplet-derived +
platform margin; tunable via CLOUD_BLUEPRINT_UCPU_HR/_UGB_HR). Sizing is
the declared deploy.resources reservations/limits (or legacy cpus/mem_*)
else a default footprint per inferred class (db/cache/web/worker/other);
deploy.replicas scales it.

EstimateTemplate(id) -> {sbom, vcpuHr, gbHr, microUsdPerHour,
estCentsPerMonth} is the in-process seam the deploy path meters an org on
and the "~$X/mo to run" the console shows — the compute cost the 20%
author royalty (clients/authors, defaultShareBps=2000) is taken from.
Distinct from clients/sbom (CycloneDX packages inside one image, keyed by
digest); this is the bill of IMAGES a stack runs, keyed by template.

Surface: GET /v1/blueprint (index), /v1/blueprint/sbom?template=<id> (one),
/v1/blueprint/sbom (batch), /v1/blueprint/health. 5 embedded OSS
blueprints; pure I/O-free core; 11 tests green; frozen wire-order refrozen.
2026-07-24 15:58:38 -07:00
antje 6865c4c5a6 ask: unified grounded /v1/ask advisor (books contributor + pluggable registry) 2026-07-24 15:35:55 -07:00
antje ea5ae54b46 authors: OSS creator royalty = 20% (was contradictory 25% const / 5% comment)
defaultShareBps 2500→2000. 20% is the ONE canonical creator share across the OSS
marketplace (oss.hanzo.ai, platform templates, 'Earn 20%' CTA). Reconciled the
25%-vs-5% contradiction in the code+comments; test expectations track the const.
2026-07-24 15:28:24 -07:00
hanzo-dev a877eda205 ci(release): neutralize → sync-notice; native build/deploy is .hanzo/workflows/deploy.yml (GitHub is a mirror) 2026-07-24 15:13:32 -07:00
hanzo-dev 01ee372a67 ci(deploy): native Hanzo pipeline — BuildKit ./Dockerfile → ghcr.io/hanzoai/cloud:<sha> → patch app {cloud,cloud-iam2-canary,cloud-reader} 2026-07-24 15:13:25 -07:00
antje b8658dc543 trace-pipeline bump (ai v1.831.1 + o11y v1.5.30) + admin infra visibility + commerce revenue-read fix
- go.mod/go.sum: ai v1.831.0->v1.831.1 (gen_ai spans nest under the request span;
  always stamp org_id + X-Session-Id + deployment.environment), o11y v1.5.28->v1.5.30
  (querier resolves $N trace_id before the trace-summary short-circuit)
- clients/admin: infra visibility — products fleet view, revenue read (fanin), types
- clients/paas: fleet observer published to admin (products/health rollup)

Money/trace commerce co-resident source fix already live via 9feef2acf (v1.801.203);
this ships the trace-pipeline module bump + admin/paas visibility.
2026-07-24 12:43:32 -07:00
antje bc3e9e52de books: address scanner red findings 2026-07-24 12:37:55 -07:00
antje 93f20d40d9 books: scanner + inbox + vendors/rules + transactions 2026-07-24 12:37:55 -07:00
z 8b961f3273 docs: modernize + LLM.md + cross-links (one-way SDK model) 2026-07-24 12:29:49 -07:00
z 96833fde9a docs: modernize + LLM.md + cross-links (one-way SDK model) 2026-07-24 12:29:42 -07:00
zeekayandhanzo-dev cfd1c5bf00 feat(webhooks): delivery log + test-send + secret rotation — the console product surface
Extend the global /v1/webhooks subsystem with the surface a console Webhooks
product needs — persisted delivery logs, inline test-send, secret rotation, and
cheap usage counters — all riding the ONE existing delivery path.

- store: `delivery` table (per-org, endpoint_id/delivery_id/subject/attempt/
  status/http_status/error/duration_ms/created) with opportunistic retention
  (newest 500/endpoint, pruned on insert); recordDelivery/deliveries/usage/
  setSecret methods.
- dispatch: attempt() now returns a rich attemptResult (ok/retryable/httpStatus/
  err/duration); deliver() records ONE best-effort row per attempt from the
  worker goroutine (off the ack path) — "retrying" mid-ladder, terminal "ok"/
  "failed". Same attempt() is the single sign+POST the test-send reuses.
- api: GET /:id/deliveries (org-scoped, newest-first, ?limit default 50/max 200,
  ?status=), POST /:id/test (synchronous single-attempt send + row + inline
  result, works while disabled), POST /:id/rotate-secret (reveal-once, old
  secret invalid immediately). list/get carry deliveries7d + failures7d from one
  grouped aggregate.

Tests (+6): per-attempt logging incl. retries, retention prune, deliveries list
org-isolation/filter/limit, test-send signature+row+disabled, rotate-secret
old-invalid/new-verifies, usage counters. 21/21 green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 12:28:12 -07:00
zeekayandhanzo-dev 4aa2ea79cf build(deps): bump hanzoai/commerce v1.49.17 → v1.49.18 (local webhook engine removed; delivery = the global /v1/webhooks dispatcher)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 12:03:41 -07:00
zeekayandhanzo-dev 2d77642de2 feat(webhooks): global /v1/webhooks — one registry + bus-driven dispatcher for all platform events
Owner directives: webhooks are a first-class top-level resource (/v1/webhooks,
never nested under billing) and EVERY global event on the platform bus must be
webhook-deliverable.

- clients/webhooks: org-scoped registry CRUD at /v1/webhooks (validated principal,
  org from the gateway-minted identity; per-org SQLite store; server-generated
  secret returned only on create) + ONE durable JetStream consumer
  (webhooks-dispatch on stream COMMERCE today; streams are a config list) that
  fans events to subscribed endpoints with NATS-wildcard filters (*, >).
- Delivery = the canonical semantics: X-Webhook-Signature (t=,v1= HMAC-SHA256),
  X-Webhook-Event, X-Webhook-Delivery (stable per attempt-group), fresh sig per
  attempt, 3 attempts 1s/5s/25s+jitter, 10s timeout, retry only network/5xx/429.
  Org-isolated: an event only ever reaches its own org's endpoints; org-less
  events deliver to nobody. Ack-on-queue — a slow subscriber never stalls the bus.
- Fail-soft Mount (registry serves with the bus down; consumer retries) +
  Shutdown drains stores and the worker pool.
- apps: wired after catalogsync; frozen golden updated — including the share and
  books rows the parallel stream added to Wire() without updating the golden
  (the golden was already red on HEAD; reconciled to reality).

15 tests green (fresh run): CRUD auth + org isolation, subject matcher, header/
signature recompute, retry ladder, delivery org isolation, disabled-endpoint
skip, in-process NATS end-to-end.

Supersedes commerce's local delivery engine (v1.49.15) — rip tracked separately.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 11:50:21 -07:00
antje 0fd3d62f71 deps(cloud): commerce v1.49.16 → v1.49.17 — activate self-serve create-store + onboarding + paywall
commerce runs co-resident in cloud (commerceinproc). Bumping the dep brings the
Shopify-parity backend live: org-admins can create a store in their OWN org (home==
effective bound), onboarding's trial starts at store creation, and the subscription
paywall (billing/paywall) enforces the $20/mo gate — SuperAdmins exempt, trial/sub/
invite pass. Cloud builds clean with v1.49.17 (verified).
2026-07-24 09:47:04 -07:00
antje 62c58040a6 books: land the AI bookkeeper on /v1/books (native double-entry, per-org SQLite)
A native 'books' domain in the cloud one-binary — the ERPNext Accounts SEMANTICS
ported to Go, NO Postgres/Formance/ERPNext-Python. Reads commerce
/v1/billing/transactions (sole posting source, read-only) and books the
double-entry twin; GAAP rev-rec (Customer Wallet = deferred-revenue liability,
recognized at usage); accrual P&L + Balance Sheet + export; AI Ask brain (SaaS
metrics: MRR/ARR/burn/runway) + clarifying questions; bank engine with PDF
(rsc.io/pdf + foot-check reconciliation), OFX/CSV, Plaid, Teller + reconciliation.
Exact int64 cents, per-org Base/SQLite, ~35 tests green (built blue/red/cto).
Registered in apps.go beside treasury; adds rsc.io/pdf direct dep.
2026-07-24 02:04:15 -07:00
antje 84ecd7b6f2 merge: analytics destination adapters (Umami + PostHog + GA4/Meta ecommerce)
Fan POST /v1/analytics out to analytics.hanzo.ai (Umami /api/send) and
insights.hanzo.ai (PostHog /v1/e); ecommerce -> GA4/Meta conversion mapping.
Fail-soft fanout; adapters inert until per-site KMS keys are set (additive).
2026-07-24 01:51:26 -07:00
antje 2a1d76ae4d fix(destinations): PostHog → /v1/e, Umami visitor id → id (red must-fix)
Two silent-drop contract bugs from adversarial (red) review of the Umami +
PostHog analytics sinks — both fail soft, so a paid product ingested zero.

- posthog [critical]: Send POSTed to <host>/batch, but Hanzo Insights
  capture-rs registers ONLY /v1/e|/v1/s|/v1/ai (rust/capture/src/router.rs;
  legacy /batch REMOVED, Django APPEND_SLASH=False) → every event 404'd and
  was dropped (postJSON logs, never wedges). Repoint to /v1/e; the
  {api_key,batch:[…]} body is unchanged — capture-rs's untagged
  RawRequest::Batch variant accepts it verbatim.

- umami [medium]: umamiPayload.DistinctID serialized as `distinctId`, a field
  absent from the fork's /api/send zod schema (src/app/api/send/route.ts) →
  silently stripped, so the forwarded visitor id never keyed the session
  (stitching fell back to IP+UA). Rename the JSON tag to `id`, the schema's
  real session key: sessionId = id ? uuid(website,id) : uuid(website,ip,ua,salt).

Tests now assert the real WIRE contract (a struct-field assert cannot catch a
JSON-tag bug — the source of the false confidence red flagged):
TestPostHogSendEndToEnd → /v1/e; TestUmamiBuild + TestUmamiSendEndToEnd → the
visitor id marshals under `id`, never `distinctId`.

go build + go vet + go test ./clients/destinations/... green.
2026-07-24 01:44:56 -07:00
antje 734c52b93f refactor(share): login-first provisioning, fresh deterministic email, env base
Three hardening fixes from live testing against the zrok controller:
- LOGIN-FIRST: token(org, create) tries login before create — an existing
  account (the common path) costs ONE login and never touches admin; create
  only on a real miss. Slims the controller interface to token()+overview()
  (org-centric — the controller owns all credential derivation, the handler
  just passes org; DRY).
- FRESH EMAIL: zrok SOFT-deletes accounts (a deleted email stays in the unique
  index, un-recreatable forever), so a plain share-<org>@ that was ever touched
  is burned. accountEmail now carries an HMAC freshness suffix
  (share-<org>-<hash8>@hanzo.ai) — deterministic, unguessable, and distinct
  from any prior scheme, so no burn can strand an org.
- ENV BASE: ZROK_API_BASE (default /api/v2) makes the /api/v2 -> /v1 cutover a
  CR edit, not a rebuild — flip it the moment the /v1 zrok image deploys.
Builds + unit tests green.
2026-07-24 01:24:27 -07:00
antje 1e8ec3e11a chore(commerce): ship store access billing 2026-07-24 01:10:51 -07:00
antje 7f9ba10b16 fix(share): per-org account email uses a hyphen, not plus
share-<org>@hanzo.ai. A plus local part trips some validators, and zrok
soft-deletes accounts (its unique email index then blocks a recreate of
the same address) — a hyphenated, stable identity sidesteps both. Verified
live against the controller: create 201 + login 200 for share-hanzo.
2026-07-24 00:57:25 -07:00
antje 5824068aa1 feat(destinations): add Umami + PostHog sinks and native ecommerce mapping
Fan the /v1 analytics event stream out to two first-party analytics sinks
alongside the existing ad platforms, and map schema.org/GA4 ecommerce actions
onto GA4 and Meta's native conversion schemas.

- umami.go: POST /api/send (Hanzo Analytics fork). Credential-less public
  beacon keyed by the non-secret website id; forwards the end-user UA+IP so
  Umami attributes session/geo. Pageviews sent without a name (Umami's rule).
- posthog.go: POST /batch (Hanzo Insights fork). Project api_key is the KMS
  secret, carried in the body (never URL/log); distinct_id keyed, empty dropped.
- fanout.go: resolveSecret treats a Secret-less, Fallback-less destination as
  credential-less (public ingest) instead of failing closed.
- translate.go: map product_viewed/product_added/begin_checkout/purchase (+
  schema.org aliases) onto the commerce standard events; lift ecommerce line
  items (items/products array, or a first-class product id) into Conversion.Items.
- ga4.go: render GA4 items[] + purchase transaction_id.
- meta.go: render Meta content_ids/contents/content_type/num_items + order_id.
- destination.go: normalized Item type + Conversion.Items/Referrer.
- send.go: shared non-PII first-party analytics data helper.

Secrets stay in KMS; no credential in any endpoint, error, or log line.
Tests: adapter payload + ecommerce mapping (mock HTTP), translate vocabulary +
item lift, credential-less resolution. go test ./clients/destinations/... green.
2026-07-24 00:52:49 -07:00
antje f429d7228d cloud auth: IAM-native trust — drop the per-app audience allowlist
Trust becomes exactly what IAM asserts: a valid SIGNATURE from a trusted ISSUER
(the brand set) plus EXPIRY. The audience (a minting app's client_id) is now
INFORMATIONAL, not an access gate — cloud no longer keeps a hand-maintained mirror
of IAM's app registry. That mirror was the lone non-IAM-native gate and it drifted:
every new first-party app (most recently hanzo-commerce, breaking the commerce-admin
AI assistant) silently 401'd until someone edited GATEWAY_ALLOWED_AUDIENCES. A new
first-party app now 'just works' with zero cloud change.

Removed: identityValidator.audiences, Config.JWTAudiences, jwtAudiencesFromEnv,
defaultJWTAudiences, BrandAudiences, unionStrings. validate() enforces issuer + expiry
via jwt.Expected{} (empty AnyAudience skips ONLY the audience match; go-jose still
checks exp/nbf against time.Now). Fail-secure on an empty ISSUER set is preserved.

PRESERVED (unchanged): owner-claim org scoping on every guard; SuperAdmin =
owner==adminOrg AND !isKMSMachinePrincipal; the KMS-machine SuperAdmin-denial
(isKMSMachinePrincipal reads claims.Audience directly, not the removed allowlist);
OrgHasUnsafeRune. Tests reframed to the new invariant and all green, incl. the KMS
red adversarial suite (multi-value aud, admin-slip, owner-bound machine-aud, trim/
unsafe owner). One new test proves any aud from a trusted issuer validates while a
wrong issuer / expired token still rejects.

The user-facing behavior change: a real admin (owner==adminOrg, isAdmin) is now
SuperAdmin from ANY first-party app, not only allowlisted ones — owner is the
authority, which is correct for an internal IAM where every app is first-party.
2026-07-24 00:32:47 -07:00
antje c549074bb8 fix(share): zrok API is /api/v2 + application/zrok.v1+json media type
The controller's go-swagger API mounts at basePath /api/v2 and consumes/
produces ONLY application/zrok.v1+json (application/json → 415/500, and a
v1 path → the SPA's 202 HTML). ensureAccount/login/overview now hit the
right base with the right content type. Verified: /api/v2/login returns
the account token 200.
2026-07-24 00:29:37 -07:00
zeekayandhanzo-dev 3ecbcfe1c8 build(deps): bump hanzoai/commerce v1.49.14 → v1.49.15 (billing webhooks live: X-Webhook-* delivery, lifecycle emission, bounded retry)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-24 00:18:45 -07:00
antje 803267b226 feat(share): /v1/share/* — ngrok-native public sharing in the one cloud binary
Provisions a per-org zrok account from the caller's validated IAM identity
so the Rust CLI's `hanzo share <port>` publishes a local service to a public
https://<token>.share.hanzo.ai URL with zero manual setup.

- POST /v1/share/enable: stateless, deterministic per-org account (email
  share+<org>@hanzo.ai, password HMAC(secret,org)) — ensure-account + login
  reconstruct the same credential every time; the zrok controller IS the
  store, no local persistence. Returns {accountToken, controller, namespace,
  urlTemplate} for the tunnel client. Idempotent.
- GET /v1/share: the org's active shares (CLI + console Shares view), honest-
  empty when the controller is unreachable.
- Fail-closed 503 until ZROK_ADMIN_TOKEN; org from principal (never a client
  field) so a caller can only ever provision/read its OWN org. .Group routes,
  mockable controller client, unit-tested.
2026-07-24 00:10:33 -07:00
zeekayandhanzo-dev 031388bd1a git: public explore/landing — OSS-first, no sign-in to browse
git.hanzo.ai (served by cloud's embedded git forge, clients/git) returned a raw
403 'sign in to view Hanzo Git' for signed-out visitors. Most Hanzo projects are
OSS, so the default face is now open, GitHub-style:

- uiExplore + /explore: lists every PUBLIC repo across ALL orgs, searchable (?q=),
  no auth. Cross-org via {DataDir}/orgs enumeration (per-org stores have no global
  index), capped at maxExploreScan.
- uiHome: signed out -> public explore/landing; signed in -> your org's repos.
- uiRepoAccess: repo/tree/blob/commits views serve PUBLIC repos anonymously;
  private repos stay org-authed and answer the SAME 404 (no existence leak),
  mirroring smart-HTTP's resolvePackRepo(allowPublic).
- Store.ListPublic: per-org public-repo query.
- state.dataDir threaded through Mount for the org enumeration.

Anonymous clone of public repos already worked (smart_http); this opens the
browser surface to match. Updated TestRootUI_HostGuard to the new public-landing
contract (/ -> 200 explore, missing repo -> native 404).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-23 15:17:57 -07:00
hanzo-dev d7f7077484 guide: fold the full Zen of Hanzo genome into a version-aware seed
Seed the DB-backed blueprint with the complete corpus — the 64-principle
spine plus 888 modern + 114 heritage strategies (1002 total), each filed
under a spine principle and tagged by era. base.yaml is the assembled
genome, kept byte-synced with the GitOps origin.

Schema: Blueprint.Principles (the 64 archetypes); Strategy gains
principle/source/era/blog. Validate enforces referential integrity — every
strategy's principle resolves to a spine slug, no duplicate id across the
1002 — plus unique principle slugs.

Version-aware seed (SeedOrUpgrade): a monotonic seedVersion is stamped on
the seed row (source="seed"); an admin write flips it to source="admin".
On Mount a brand with no row is seeded, an UNEDITED seed at an older
generation is upgraded in place, and a brand ever admin-edited is never
touched again. A self-healing backfill marks legacy version>=2 rows as
admin.

Fix two review LOWs:
- authoringBlueprint returns a clone of the embedded fixture in its
  pre-seed fallbacks, so an in-place PATCH can't corrupt the shared value.
- putBlueprint / listBlueprintVersions fetch the write key via
  LatestResolved without parsing, so a corrupt stored row is still
  replaceable by a valid PUT.

Tests: assembled seed parses+validates; /v1/guide/strategies surfaces the
888; a v2 seed upgrades an unedited v1 row and never clobbers an admin
edit; legacy backfill; the two LOW PoCs. Frozen wire green.
2026-07-23 13:28:33 -07:00
hanzo-dev c5b69e2139 guide: DB-backed blueprint — seeded fixture, 3-tier resolution, SuperAdmin authoring, strategies corpus
Make the whole Guide™ playbook DB-backed and SuperAdmin-editable — nothing static.

Schema: extend the engine into a full Blueprint (Section/Strategy/Template + an
Enabled lever on every item, default-on). The engine stays pure — Blueprint.Curriculum()
projects the ENABLED journey (disabled section drops its steps; disabled step drops and
its dependents lose the edge), so reconcile/Next/Available/Counts are unchanged. Parse is
fail-closed; Validate enforces DAG-acyclic + no-dangling over the authored graph AND the
enabled projection.

Seed: embed base.yaml (12 sections · 67 steps · 114 strategies · 6 templates, a
byte-identical synced copy of the universe fixture) as the blueprint; supersede
default.yaml. On Mount, seed-if-absent into a shared versioned store (guide_blueprint,
brand-keyed) — a redeploy never clobbers admin edits.

Resolve (three tiers): org override (per-org) → brand blueprint (shared DB, seeded,
SuperAdmin-authored) → embedded fixture (fail-safe). A disabled/unparseable tier is
skipped.

Author: /v1/guide/blueprint/* gated on IsSuperAdmin (owner==admin) — a normal org member
or per-org admin gets 403. GET/PUT the whole blueprint, GET versions (PITR), PATCH an
item (edit + the enable/disable lever). Every write is validated fail-closed and appended
as a new version; edits take effect on the next resolve.

Filter: GET /v1/guide/strategies?category=&stage=&workload= — the ENABLED corpus,
org-scoped, joined to the observe layer (stage:* is a monotone readiness floor,
research==formed; has:* maps to module:*/connected:*/analytics/revenue/deployed/
funnel:signups; extend standardConnectors so the join is real).

Green: go build ./clients/guide/... ./apps/...; go vet; go test ./clients/guide/... (50
tests incl SuperAdmin-gate 403, idempotent-seed no-clobber, org>brand>fixture resolution,
disabled section/step drop, corpus filter). apps TestWireOrderMatchesFrozen green (routes
added to the existing guide subsystem).
2026-07-23 12:21:56 -07:00
hanzo-dev a0dbfc75a0 guide: real-time growth-observe layer — signals, stage classifier, /v1/guide/profile
Add the Guide's OBSERVE layer so the Business AI grounds on an org's REAL
platform truth, org-scoped and honest-degrading.

Growth signals extend the Detector vocabulary (detect.go stays THE coupling
point): module:<name>, connected:<provider>, funnel:<stage>, deployed, revenue,
customers:>=<N>. Each reads a sibling subsystem through an injected Signals seam
bound at the composition root (apps/wire_seams.go) — guide imports none of them,
the coding-dispatcher injected-function pattern. A nil seam field honest-degrades
its signal to not-present; the vocabulary is the contract, a read fills in when a
provably org-scoped seam lands. lookupDetector resolves parameterized <kind>:<param>
signals so a curriculum step can auto-detect on any of them.

classifyStage folds a SignalSet into a first-principles growth stage
(formed->launched->activated->scaling) — pure, total, exhaustively tested; the
ladder is data, driven by OUTCOMES (presence, engagement, money), not setup.

GET /v1/guide/profile exposes {stage, signals, keyMetrics}, org-scoped on the
validated principal, READ-ONLY, recomputed each request (real-time by pull) via the
existing reconcile path + the growth probes.

Bound reads (provably org-scoped, nil-safe): framework.ModuleInstalled (new,
module-granularity sibling of Installed), integrations.Connected (new, boolean,
never the token), the in-package analytics funnel. deployed/revenue/customers stay
unbound seams (deploy is cluster-scoped; commerce/crm have no clean per-org
in-process read) — honest-degrading until a provably org-scoped read exists.

Tenant isolation: every signal read keys on the caller's own org; TestHTTPProfile
CrossTenantIsolation proves org A's profile never reflects org B's signals and each
request's probes read only the caller's org. framework/integrations seam reads have
their own org-scoping tests.
2026-07-23 10:13:15 -07:00
hanzo-dev dba4666173 research: gate HA object-store durability behind CLOUD_RESEARCH_DURABLE opt-in
The unified store's durability plane auto-activated whenever S3_ADMIN_* was
configured (prod sets it), so deploying it would begin fencing real tenant
data on the object store's conditional-PUT (If-Match) atomicity before that
atomicity is validated against the deployed SeaweedFS version (Red's takeover-
fence staging gate H2). Gate it behind CLOUD_RESEARCH_DURABLE (off by default):
the store runs local-only until the flag is set, and the shard router already
pins each org to one writer (ha.Owner) — so this is NOT the rolling-deploy
outage, and the DDL-drift-proof + evidence-preserving record layer is fully
active. The object-store snapshot/fence turns on deliberately after the gate.
2026-07-23 09:41:46 -07:00
hanzo-dev df1de096ff test(framework): guard stampFixture clone — fail if DocField/DocPerm gain a non-scalar field (red LOW-1: shallow-clone would corrupt the always-on registry cross-org) 2026-07-23 07:40:15 -07:00
hanzo-dev 84281e3ddc guide: always-on standard modules + AI suggest + per-brand journeys
Complete the stranded Guide feature so a fresh org's journey works with no
per-org module install.

framework: MarkAlwaysOn/AlwaysOnModules mark a registered module always-on —
its DocType fixtures resolve for every org via GetDocType/ListDocTypes and the
Installed predicate, with no per-org install row. This defaults only the SCHEMA
on; every document row stays physically org-scoped. A per-org stored DocType
still overrides the fixture. always_on_isolation_test.go proves org A's records
are unreadable by org B even though the DocType resolves for both.

content: marketing is always-on (doctypes.go init), so content_generate
completes for a fresh org — the fix for "content: marketing module not installed
for org". Drop the now-unreachable not-installed guard in EnsureCatalogAsset (a
fresh org without a studio still quietly skips at Generate).

guide: builtin-2 journey rooted at "Form your company", then positioning →
launch steps and the daily agentic growth loop; positioning gates on company.
Add /v1/guide/suggest + /v1/guide/chat — read-only AI "what to do next", grounded
in the org's real progress + funnel, never running an action. Resolve the
white-label brand journey (brands/<brand>.yaml; zoo ships zoo-1) at Mount.

cek: TestMain seeds an ephemeral master key so the encrypted-at-rest stores open
on an encryption-capable test build (framework, content, guide) — mirrors
compliance/integrations/flags/venue.
2026-07-23 07:37:19 -07:00
antje e2cf2e978b agents: CLI-facing control drain for locally-started sessions
The dashboard already POSTs pause/resume/stop/message, recorded as durable
KindControl events. A cloud-dispatched routed run gets them forwarded to the
tasks engine, but a LOCALLY-started `hanzo code` session is not task-backed —
so the running surface must pull them itself.

Add GET /v1/agents/sessions/:id/control?after=<seq>: an owner-scoped, cursor-
driven drain of a session's control commands (ListControlAfter filters to
control, oldest first). Read-only, org is the only tenant key, foreign id 404s.
Test covers filter/order/cursor/tenant-isolation.
2026-07-23 07:01:31 -07:00
hanzo-dev d5c1a5b676 Merge branch 'blue/research-orm' into blue/research-unified
Unify the research record layer (hanzoai/orm typed records, DDL-drift-proof
+ migrateLegacy evidence carry-forward) onto the HA file-durability layer
(ha-elected single-writer + fenced ship-before-ack). Reconcile the three
files both branches touch:
- store.go: ORM's typed-orm rewrite — supersedes the raw-SQL ALTER-migrate
  path (schema migration is structurally impossible under orm).
- migrate_test.go: ORM's legacy-DATA migration test (ALTER-convergence is
  obsolete under orm).
- research.go: both — HA's durability wiring (WithDurable + shipDurable
  ship-before-ack in every write handler) plus ORM's postGrant scope comment.

deps: orm v0.6.1 -> v0.6.7 (CreateIfAbsent typed-record ingest the orm store
needs) and commerce v1.49.13 -> v1.49.14 (DatastoreAdapter satisfies orm
v0.6.7's orm.DB CreateIfAbsent, keeping ./apps/ building).
2026-07-23 04:38:14 -07:00
hanzo-dev eed81e6c8e Merge branch 'blue/cloud-ha-sqlite' into blue/research-unified 2026-07-23 04:13:09 -07:00
hanzo-dev 51eb4f281c test(durable): gate the encrypted takeover proof on a real cek round-trip (R1)
TestRecordShipsSoTakeoverKeepsIt reopens the shipped store through cek. On a CGO
build whose SQLite lacks SQLCipher, PRAGMA key is silently ignored so cek writes a
plaintext file it then cannot migrate on reopen (sqlcipher_export absent) — and the
suite TestMain still injects a dev key because sqlitedrv.EncryptionAvailable() reports
a false-positive yes, so the test hard-failed under the default CGO build.

cekCanReopen probes the actual round-trip: it holds under pure-Go (plaintext) and
real libsqlcipher (encrypted, exercising the .dek sidecar cross-pod restore), and
skips only on the broken-capability build. go test ./... stays green everywhere;
ship-before-return is proven under CGO_ENABLED=0 and by TestRecordOnNonOwnerFailsClosed.
2026-07-23 04:01:16 -07:00
hanzo-dev 945b2d5aba durable: loud gate when HA is disabled on multi-replica (L2) + document M3/M4/M5
Red L2: durability disabled now routes through disabledDurability(), which logs at
ERROR on a MULTI-REPLICA deployment (>1 CLOUD_PEERS) — per-org stores then survive
only via shard routing + per-pod RWO PVC, so a lost PVC loses data — and at INFO for
single-replica/dev where local-only is expected. The encryption-capable-build-without-
cipher case is treated as a misconfig (fail closed + loud), never a silent plaintext
ship or a silent drop back to the non-HA outage.

Red M3: documented degraded-open recovery — a degraded pod stays read-only for the
cached store's life (in-place re-acquire would CarryForward-restore under the live
handle = stale reads); recovery is a fresh open (pod restart / shard reroute), with
quiesce-close-reopen as the future enhancement.

Red M4/M5: documented the SeaweedFS operational requirements the fence rests on —
object versioning + no-expiry lifecycle on the org-db prefix (lease round is the
system of record; a dropped/rolled-back lease can un-fence a zombie), and RWO
per-writer PVCs for DataDir, never RWX.
2026-07-23 03:40:32 -07:00
hanzo-dev 5b5c95fea9 perf(research): one-time marker so a restart skips the legacy re-scan
The legacy migration was idempotent but re-read the raw-SQL tables on every open. A
completion marker (a kindMeta record under a distinct id from the seq clock, written
in the SAME tx as the migration so it commits iff the migration commits) short-circuits
every later open. Greenfield stores mark done immediately. Test asserts the marker is
set post-migration and that a re-open stays correct (no duplication).
2026-07-23 03:39:04 -07:00
hanzo-dev 41c2b3edb2 test(durable): H2 staging gate — SeaweedFS If-Match/If-None-Match atomicity
The single-writer fence rests on the gateway evaluating If-None-Match:* (create-only)
and If-Match (version-conditioned) preconditions ATOMICALLY server-side — the one
property the in-process fakes cannot prove. This env-gated integration test races 12
concurrent writers against the REAL S3ConditionalStore and asserts EXACTLY ONE wins
each precondition; two winners = split-brain possible, do not ship durability against
that gateway. Skipped in unit runs; run in staging with CLOUD_DURABLE_IT=1 + S3_ADMIN_*
before durability fences real tenant data (or on a SeaweedFS version bump).
2026-07-23 03:38:20 -07:00
hanzo-dev 8938a22cde durable: never hold the store lock across object-store I/O + timeouts + overflow guard
Red M1: forPath held the store-wide c.mu through openDurable→Hydrate (Acquire +
CarryForward round-trips, untimed) — a hung SeaweedFS froze the whole subsystem, a
cache-hit For() included. Now the durable open runs with c.mu RELEASED, deduped by
an in-flight record so concurrent For() for one org opens exactly once (cek cannot
open a file twice); every object-store round-trip (hydrate, Sync, close) is bounded
by durableOpTimeout (30s) so a slow store degrades to bounded latency, never a
deadlock. The local-only path is unchanged (disk I/O under c.mu as before).

Red L3: CloseAll ships each final state with c.mu released and time-bounded (was a
background-ctx ship under the lock) — Durable.Close takes a ctx now.

Red L1: unframe checked m+sl > len(b), which a max-uint64 length wraps past, then
panics the slice. Now checked as sl > len(b)-m (subtraction, no wrap) → fails closed.

Tests: TestDurableForDedupsConcurrentOpens (8 concurrent For → one store), the L1
oversized-length frame fails closed, all durable + research + root OrgStore green.
2026-07-23 03:35:24 -07:00
hanzo-dev 1bd58f0fc0 fix(research): carry pre-orm raw-SQL evidence forward on open (was orphaning it)
CRITICAL (red): the orm store read only _entities, so an existing per-org file whose
evidence lived in the old raw-SQL experiment/attempt/artifact tables read as EMPTY —
every logged run silently vanished the instant orm shipped (data intact in-file, but
all reads returned 0). migrateLegacy now runs in openStore: gated on old-table
existence (greenfield skips), idempotent via CreateIfAbsent, fail-secure (a migration
error fails the open rather than serving empty over real data).

- Each version keeps its OLD seq value → canonical/supersession preserved exactly (a
  corrected run stays canonical); the append clock is advanced past every migrated seq
  so a later ingest still supersedes (proven with a ts=0 correction across the boundary).
- Rows read by COLUMN NAME (SELECT *) → a table left by any older schema (even the
  outage-era one missing provenance columns) migrates without a 'no such column'.
- content_hash/revision/status/visibility/consent/provenance + artifact blobs verbatim.
- Regression TestLegacyDataMigration: seed old tables incl a correction pair → open →
  assert pre-migration truth (corrected canonical, retained intact, artifact bytes),
  a later ingest supersedes, an unrelated ingest doesn't flip it, re-open is a no-op.

Also (red): setArtifactVisibility now does its read-modify-write in a transaction like
setGrant (LOW); a scale note at the loaders documents the in-memory-fold tradeoff +
indexed-Filter escalation (MEDIUM, org-bounded); postGrant's client-supplied project
is confirmed intentional (org is the tenant boundary, project an org-internal target
label) with a clarifying comment (LOW).
2026-07-23 03:33:45 -07:00
hanzo-dev 7140168680 durable: fix live-path lost-write — Record ships (H1), restore dir-order, checkpoint result (M2)
Red H1: research.Record (in-process A/B evidence, experiments.go:425) committed
locally but NEVER shipped — an acked write lost on takeover, and unfenced on a
non-owner. Record now Syncs before returning and propagates a not-acked ship as an
error (mirrors the HTTP shipDurable), so a takeover keeps it and a non-owner fails
closed instead of persisting a stale divergent local copy.

Writing the H1 takeover regression surfaced a real restore bug: restore() wrote the
.dek key sidecar BEFORE RestoreFile created the parent dir, so a fresh successor
(orgs/<slug>/ absent) failed the sidecar write → hydrate degraded → EMPTY store =
the lost write. RestoreFile (which MkdirAll's) now runs first, then the sidecar.
The flat-tempdir unit test masked it; added TestDurableRestoreIntoFreshNestedDir.

Red M2: wal_checkpoint(TRUNCATE) result was discarded — busy!=0 ships a partial
snapshot (committed frames still in WAL) as acked = silent lost write. Now
QueryRow'd; fail closed on busy!=0.

Tests: TestRecordShipsSoTakeoverKeepsIt (takeover keeps the evidence, real cek
key-sidecar cross-pod restore), TestRecordOnNonOwnerFailsClosed, and the nested-dir
restore regression — all green.
2026-07-23 03:30:20 -07:00
hanzo-dev dc48ee02c5 compliance,legal: close the 2 red LOWs — role-gate decideAccreditation; catch {{index . "k"}}/{{$.k}} undeclared-field refs 2026-07-23 03:10:46 -07:00
hanzo-dev 5ee3853c2d Merge remote-tracking branch 'origin/main' into blue/cloud-adopt-provision 2026-07-23 03:04:14 -07:00
hanzo-dev fe63e9bb4e test(apps): add destinations frozen row — wire golden was latent-red on main (Wire mounted it, frozen omitted it) 2026-07-23 03:02:04 -07:00
hanzo-dev 5770ae8720 test(research): concurrent-ingest seq monotonicity under -race
24 concurrent ingests of distinct content must all land (no lost write, no dup) and
the server-assigned append clock (seq) must be unique + gapless in [1,N] — the
concurrency proof for the per-store seq that replaced SQL AUTOINCREMENT, backed by
OrgDB single-writer + orm writeMu + the ingest tx.
2026-07-23 02:59:34 -07:00
hanzo-dev b5f1e2dcad company/compliance/idv/legal: decomplect the KYC/verification decision from the callback
A KYC/verification terminal status is now reached by three orthogonal paths, never a
client-asserted status:

- provider reconcile (pull): company kyc/refresh + compliance verifications/:id/refresh
  consult the wired provider for the settled status; Manual stays pending.
- provider webhook (push): compliance verifications/webhook authenticates by HMAC
  signature (idv.Webhook, KMS-sealed secret, disabled by default) and reconciles the
  referenced check from the provider API, so the request body cannot dictate a status.
- reviewer decision: company kyc/decision (a platform reviewer) and compliance
  verifications/:id/decision (an org admin or platform reviewer) are role-gated and
  attributed (DecidedBy = the acting user), and produce a DISTINCT reviewer_confirmed,
  never a provider_verified.

guardKYCVerified and the compliance decision accept only an attributed provider pass or
reviewer_confirmed. A founder/check records who decided; an unattributed "verified"
fails closed. startKYC clamps a provider's inquiry-time status to pending.

legal: the counsel-review notice is coupled to the category — formation and equity
templates always carry it, forced on override and emitted at render — and an override
body may reference only declared fields.

compliance createAccreditation records only an asserted state; a provider_verified
state routes through the attributed decision endpoint.

Remove the committed cek key sidecars and gitignore the pattern; tests seal their
stores under t.TempDir().
2026-07-23 02:57:21 -07:00
hanzo-dev 874c328ca5 feat(compliance,legal): corporate back-office — KYC/KYB orchestration + legal template engine
Hanzo Compliance (/v1/compliance): org-scoped KYC/KYB verification through a
provider-agnostic seam, accreditation-state tracking, and a compliance-scoped read
of the shared tamper-evident audit plane (SOC 2 posture). Subject PII is sealed at
rest (cek) and referenced by opaque id everywhere else — never in logs, audit, or
URLs. No path yields a verified status on create; a terminal decision comes only
from the provider (refresh) or an authenticated, audited callback.

Hanzo Legal (/v1/legal): a versioned, org-overridable standardized template library
plus a pure, deterministic merge-field generation engine, a sealed document store,
and e-sign + filing seams. The counsel-review notice is a non-droppable invariant on
formation and securities documents.

clients/idv: the ONE identity/business verification seam — honest Manual default,
config-driven Persona/Onfido/Stripe adapter with a KMS-sealed key and a strict,
fail-closed status classifier. Consumed by BOTH compliance onboarding KYB and company
formation KYC; company now resolves a real provider from config (fail-closed),
replacing the manual-only default.

Boundary invariant, enforced in the data model and on the wire: platform tooling with
licensed providers and professionals in the loop — provider-reported or tracked states
only, never a platform assertion of "compliant" or "legally valid".
2026-07-23 02:57:21 -07:00
hanzo-dev a832e1f3ba test(research): give App.Test the repo-standard 30s timeout, not the 1s default
The research HTTP tests used the bare app.Fiber().Test(req) whose default client
timeout (1s) is too tight for a cold cek-encrypted per-org SQLite open, so they
flaked as i/o timeouts. Match the rest of the repo (base/exec/world tests):
fiber.TestConfig{Timeout: 30 * time.Second}. Assertions unchanged.
2026-07-23 02:56:49 -07:00
hanzo-dev 44d237a66a cloud: wire the per-org store through the HA-durable path (research)
OrgStore gains an opt-in Durability (WithDurable): when set, forPath hydrates each
org's SQLite from the object store BEFORE opening (elected owner CarryForward-seals
to its lease round; non-owner refreshes read-only), binds the handle, and Sync ships
it fenced after a write. A degraded hydrate never blocks the open — the store always
opens (reads local, writes fail closed) so a second replica can never break it. With
no option it is byte-identical to the local-only cache the other 12 subsystems use.

BuildDeps constructs the deployment Durability (buildDurability): the SeaweedFS S3
If-Match ConditionalStore (same s3admin identity as deps.VFS), membership over
CLOUD_PEERS (the SAME set the shard router elects on), and the per-org envelope
Cipher rooted at the KMS master. No object store ⇒ nil ⇒ local-only. An
encryption-capable build with no cipher is refused (never ship plaintext snapshots).

research wires WithDurable(b.Durable) and calls Sync after each write commits
(ship-before-ack): a not-acked ship (deposed/degraded) returns 503 so the client
retries on the org's current owner — no acknowledged write is lost on failover. On a
local deployment the ship is a successful no-op. Scoped to research as the proof; the
seam (WithDurable) is the one other subsystems adopt next.

durable_test.go adds the cek-encrypting-build coverage: the .dek key sidecar ships
with the database bytes and is restored on hydrate, plus the (sidecar,db) frame
round-trip.
2026-07-23 02:56:25 -07:00
hanzo-dev 0c9cc4d46b deps: bump hanzoai/vfs v0.6.4 → v0.6.6 (modernc out of the graph)
v0.6.4's replica/sqlite.go blank-imports modernc.org/sqlite directly, which
registers the "sqlite" database/sql driver a SECOND time alongside cek's
hanzoai/sqlite — a double-register panic at init the moment a binary links both
(which wiring internal/org's durable path into cloud is the first to do). v0.6.6
(469995c + ffd32ca) routes replica through the ONE hanzoai/sqlite driver, so a
single registration stands. Patch bump, FencedStore API unchanged.
2026-07-23 02:56:07 -07:00
hanzo-dev df447d3470 refactor(research): migrate store from raw SQL to hanzoai/orm
Kills the 'no such column' DDL-drift bug class permanently: records are typed Go
values stored as JSON in orm's fixed _entities table, so adding a field is a struct
change with ZERO DDL. orm layers over the per-org *sql.DB cloud.OrgDB already opens
(cek-encrypted, single-writer, WAL) via orm.AdaptSQLite — orm manages the records,
the caller owns the file — so encryption at rest and the HA durability plane are
preserved and the openStore(*sql.DB) seam is unchanged.

Behaviors preserved over the orm model:
- dedup/idempotency: CreateIfAbsent keyed by <project>:<id>:<content_hash>
- versioned/canonical: a per-store monotone seq stamped inside the ingest tx
  (never client ts); canonical = latest-appended non-retracted per stable id
- queries (counts, list, totals, projects, artifacts) reimplemented as in-memory
  folds over orm Query (per-org stores are small)
- evidence model intact: ingest forces private/non-trainable/non-publishable,
  faulted runs retained, artifact sha256 server-derived, provenance first-class

Artifact bytes split into a distinct blob keyspace so the diary feed never loads
blobs, and because orm's _entities id is a global PRIMARY KEY (kind-prefixed ids
keep each kind in its own keyspace). Regression test proves a new provenance field
needs no migration; the 11 evidence-semantics tests pass against the orm store.
2026-07-23 02:53:29 -07:00
hanzo-dev 046beb5ae8 org: Durable — the reusable single-writer + hydrate + fenced-ship gate
Packages the handoff_test.go discipline into one value a per-org SQLite store
wires at open/write/close. Composes the three lanes: ha election (CASFencer
lease = WHO writes), replica.FencedStore (CarryForward-on-takeover + round-fenced
ship = HOW it ships, no acknowledged write lost, deposed writer rejected as
ErrStaleRound), and the org envelope Cipher (durable object at rest).

Snapshot is a raw file copy — checkpoint the WAL on the store's sole connection,
read the actual local file bytes, and ship them framed with the cek .dek key
sidecar. Backend-agnostic: identical whether the local file is cek-encrypted
(production) or plaintext (dev), so an existing on-disk store needs no migration
and cek stays the local at-rest gate.

Hydrate never makes a store unopenable (degrades read-only, writes fail closed) —
the outage was a second replica breaking the store.

durable_test.go proves it over one object store: two replicas contend → one
writes, the other defers, both open, no split-brain; a rolling takeover hydrates
the shipped snapshot with no lost write; a deposed writer is fenced; an
unreachable store degrades read-only, never 'unavailable'.
2026-07-23 02:36:15 -07:00
hanzo-dev a8b52baf9f scrub(s3): rename minio→s3/SeaweedFS across object-store code
The object store is the SeaweedFS S3 gateway reached via github.com/hanzoai/s3-go
(package name minio, aliased s3). Rename the import alias minio→s3 and every
minio.X reference to s3.X; MinioConditionalStore→S3ConditionalStore,
NewMinioConditionalStore→NewS3ConditionalStore; fix comments/docs that named the
old MinIO fork. Upstream transitive module names (github.com/minio/*) in
go.mod/go.sum are external deps of hanzoai/s3-go and are left as-is.

No behavior change: pure rename + comments.
2026-07-23 02:19:31 -07:00
hanzo-dev 8f0d633d24 test(metering): fix pre-existing TestRecord_DebitsFinanceInProcess (2 causes)
Pre-existing failure on clean main, unrelated to the pre-pay work — two causes,
both surfaced now that the metering suite runs:

1) Encryption gate: on an encryption-capable (cgo) build, cek refuses to open
   the finance store without CLOUD_KMS_MASTER_KEY_REF. The root package's
   TestMain supplies a throwaway dev key; the clients/metering test package had
   no TestMain, so the finance-in-process test couldn't open a store. Add the
   same dev-key TestMain (mirrors the root; only when the build can encrypt and
   no key is provided — CI's real key still wins).

2) Stale ceil-based assertions vs the exact 18-decimal ledger. Since the
   Money Int->Atto migration, finance debits the EXACT sub-cent amount: a 1.5c
   micros debit lands as 1.5c, leaving 98.5c (/usr/bin/zsh.985) — not a ceiled 98c. The
   RecordResult still reports the ceiled 2c (Cents() rounds up for whole-cent
   contexts), which is unchanged. Assert the exact ledger balance (money.Cmp
   against ParseUSD) instead of bal.Cents(), which ceils 98.5->99. The anti-leak
   invariant holds: the sub-cent debit is recorded exactly, never dropped to 0.

Full metering suite green.
2026-07-23 02:09:39 -07:00
hanzo-dev 41c73dd177 test(metering): pre-pay lifecycle — zero balance refused, funded served+debited
The CTO pre-pay acceptance scenario end to end: a freshly provisioned org
starts at a ZERO balance, so a metered request is REFUSED (402, no free floor,
nothing recorded); after a pre-pay deposit lands, the same request is SERVED
and DEBITS the balance; when the balance is exhausted, it is refused again. The
gate (Client.Authorize: funded := available > 0) already enforced this; this is
the explicit acceptance test for the pre-pay model. Stub balance made
thread-safe (setAvailable). Green under -race.
2026-07-23 01:59:22 -07:00
hanzo-dev c3d28bd278 merge main into CDP merge (concurrent advance) 2026-07-23 01:42:14 -07:00
hanzo-dev 76a7b184b3 research: idempotent migrate — converge old-schema stores, fix outage
The store returned 500 'research store unavailable' because migrate() ran
CREATE TABLE IF NOT EXISTS (a no-op on an existing table) then CREATE INDEX
ix_exp_git ON experiment(git_sha) — which failed 'no such column: git_sha'
on any org store created before the provenance columns landed. CREATE TABLE
IF NOT EXISTS never adds a column to an existing table.

Fix: after creating the tables, ALTER TABLE ADD COLUMN every current non-key
column (tolerating 'duplicate column name' when already present), THEN the
indexes. migrate() now converges any older schema to the current column set
and is idempotent across re-opens. Adding a column = add it to the CREATE
plus the ensure list. Regression tests reproduce the outage (old table
without git_sha) + idempotent re-open + fresh-db all-duplicates.
2026-07-23 01:41:43 -07:00
hanzo-dev 411865bcea research: idempotent migrate — converge old-schema stores, fix outage
The store returned 500 'research store unavailable' because migrate() ran
CREATE TABLE IF NOT EXISTS (a no-op on an existing table) then CREATE INDEX
ix_exp_git ON experiment(git_sha) — which failed 'no such column: git_sha'
on any org store created before the provenance columns landed. CREATE TABLE
IF NOT EXISTS never adds a column to an existing table.

Fix: after creating the tables, ALTER TABLE ADD COLUMN every current non-key
column (tolerating 'duplicate column name' when already present), THEN the
indexes. migrate() now converges any older schema to the current column set
and is idempotent across re-opens. Adding a column = add it to the CREATE
plus the ensure list. Regression tests reproduce the outage (old table
without git_sha) + idempotent re-open + fresh-db all-duplicates.
2026-07-23 01:41:03 -07:00
hanzo-dev f87bb69f57 merge(cloud): CDP destinations (GA4/Meta/TikTok/Reddit/LinkedIn/X) + AI GTM
Server-side fan-out behind /v1/event: clients/destinations (6 adapters, per-org
KMS-custodied secrets, org-isolated store, bounded fail-soft fan-out), the RAW
pre-scrub forward sink in clients/analytics, and the AI-GTM analytics lens +
destinations_connect tool in clients/guide. Additive; no go.mod change.
2026-07-23 01:40:29 -07:00
hanzo-dev 7b2da28c5b fix(help): ingress-owned edge limit, gated categories, opaque ticket ref, capped intake
Red-review fixes on the /v1/help public plane:

- Drop the app per-IP rate limiter. Behind hanzoai/ingress the socket peer IS the
  ingress, so a per-IP limiter keys every customer to ONE shared bucket (a global
  throttle + trivial DoS) and X-Forwarded-For is client-settable (a fresh value per
  request evades the limit and grows the bucket map without bound). The ingress owns
  the per-client edge limit; the plane bounds each request instead.

- GET /v1/help/categories now returns only sections that front a Published + public
  article, so an internal (agent-only) category name or description never leaks.

- Intake returns an opaque random public_ref in place of the monotonic ticket name,
  so an anonymous submitter cannot read the org's ticket volume. The sequential name
  stays internal to the agent plane.

- Cap the whole intake body at 64 KiB before parsing.

Tests: clients/help green (adds no-shared-bucket-throttle, category-gating, oversized-
body, opaque-ref assertions).
2026-07-23 01:38:36 -07:00
blueandhanzo-dev 3a8391235e feat(help): native /v1/help support product on the framework engine
Complete the Hanzo Support model as DocType fixtures and add the thin
/v1/help public plane — the native-Go replacement for the Frappe Helpdesk
(Vue + Python Frappe on Werkzeug), on Base in the one cloud binary.

Model (clients/help/help.go): add hd-article + hd-article-category (the KB)
and hd-communication (the ticket conversation thread); add a source field to
hd-ticket for inbound-connector provenance. Agents author and triage all of
it on the generic role-gated /v1/framework/hd-* surface — no new agent code.

Public plane (clients/help/subsystem.go): the anonymous face the secure-by-
default engine cannot serve — GET /v1/help/articles + /articles/:slug (only
status=Published AND is_public=1, re-checked on direct fetch), /categories,
and POST /v1/help/tickets (rate-limited customer intake creating the ticket
plus its opening conversation message). The served org is fixed server-side
(CLOUD_HELP_PUBLIC_ORG, else the deployment brand), never client-chosen, and
fails closed when unset. Storage delegates entirely to the framework
in-process API — one engine, no duplicated CRUD.

Wire help as a mount subsystem (apps.go + frozen wire order), alongside
knowledge, the other framework lane with a companion subsystem.
2026-07-23 01:38:36 -07:00
hanzo-dev 87aa341e20 feat(fleet): GB10-class unified SoC inventory — machine RAM, sm arch, CUDA/driver
nvidia-smi reports memory.total as [N/A] on a Grace-Blackwell SoC (no
dedicated VRAM counter) so the board showed nothing for spark. A unified
NVIDIA SoC now reports the machine RAM snapped to hardware capacity
(snap bound widened to 8 GiB — GB10 firmware reserves ~6.3 GiB), its sm
arch from compute_cap (12.1 -> sm_121), and the host CUDA toolkit +
driver versions ride the registration, mirroring the AMD rocm/hip pair.
2026-07-23 01:27:09 -07:00
hanzo-dev c18e20d625 fix(fleet): unified APU reports the machine RAM, snapped to hardware capacity
An APU board figure now matches the Apple convention: the unified pool is
the MACHINE memory (128 GiB Strix Halo says 128 GiB), not the GTT tunable.
Kernel-visible MemTotal snaps up to the next 16 GiB DIMM capacity only when
the gap is a plausible firmware reservation (<= 6 GiB); a real carve-out
stays honest. evo: 118 GiB GTT / 124.4 GiB visible -> 131072 MiB.
2026-07-23 01:19:23 -07:00
antje 43871c446a refactor(admin): rename /v1/admin/storage → /v1/admin/block-storage
Free /v1/admin/storage for the operator's S3 object-buckets view (a distinct
storage concern); the DO block-volume + datastore-fill fleet is /block-storage.
No consumers yet, so the rename is clean. Handler storage→blockStorage, file
storage.go→block_storage.go (history preserved). Pairs with the operator SPA
Block Storage page + console repoint.
2026-07-22 23:44:21 -07:00
hanzo-dev 93dc54977c feat(functions): target=fleet — run a function on the org GPU fleet
A python function created with target=fleet invokes as an fn.run job on
the org gpu-jobs queue through the ONE embedded tasks engine (new
View.StartActivity/DescribeActivity seam, tasks v1.51.4): same queue,
same claim loop, same result a direct tasks-API submit gets. invoke
blocks bounded by TimeoutSec (900s ceiling, matching the sandbox);
longer jobs belong on the tasks API. Job outcome maps onto the sandbox
execResult contract so billing gate + metering + invocation recording
are identical across executors; fail-closed when the engine is not
ready. Also: functions suite gains the sibling TestMain encryption
harness (suite now runs on an encryption-capable build without CI env).
2026-07-22 23:37:53 -07:00
hanzo-dev 3010dccef2 feat(destinations): fan the /v1/event stream out to ad + analytics platforms
Translate the canonical /v1/event stream to each connected platform's
conversion schema and forward it server-side. GA4 (Measurement Protocol)
and Meta (Pixel + Conversions API) work end-to-end; X, LinkedIn, TikTok,
and Reddit are scaffolded against the same Destination interface.

- clients/destinations: the Destination interface + per-platform adapters
  + translator (canonical EVENTS -> normalized conversion) + per-org
  registry (Base/SQLite, API secrets KMS-sealed) + the analytics fan-out
  consumer. A destination may reuse an integrations OAuth token
  (Meta CAPI <- meta_ads) or seal its own; PII match keys are SHA-256
  hashed before send.
- clients/analytics: a one-way fan-out sink after the write core, handed
  the RAW (pre-scrub) batch so a Conversions-API forwarder can hash the
  match keys the warehouse drops; detached + fail-soft, no-op when unset.
- clients/guide: read the analytics funnel (GET /v1/guide/analytics + an
  overview fold) and expose destinations_connect as an MCP tool.

Tests: translator mapping, GA4 + Meta send end-to-end (mock + PII
hashing), store tenant isolation, fan-out, and the connect seam.
2026-07-22 23:11:51 -07:00
hanzo-dev e7ab2ee968 benchmark: keep fugu as arena DATA (a benchmarked/routable model), not marketing
Restore the fugu-ultra published_claim rows + the test fixture — fugu is just
another model we verify in the arena and can route to, like grok/gpt/opus. The
comments stay neutral (no 'disprove the rival' narration). The rule is only: no
fugu on the Enso MARKETING pages (hanzo.ai/enso — already clean). Reverses the
over-broad purge in a80f92c.
2026-07-22 23:07:28 -07:00
hanzo-dev a80f92cca5 benchmark: purge competitor from the public /v1/benchmark arena
Remove the 4 sakana/fugu-ultra published_claim rows + scrub the two comments that
named the competitor (house rule: no competitor names in source). The public
leaderboard (unauth GET /v1/benchmark/leaderboard) no longer exposes it. Legit
arena models (grok/gpt/opus/fable etc., provider-reported) are unchanged. Removed
the fugu-ultra test fixture (594 attempts remain, test still >=500 green).
2026-07-22 23:03:12 -07:00
antje 1198254ffd feat(admin): GET /v1/admin/storage — DO block-storage fleet + datastore fill
The data source for admin.hanzo.ai's realtime Block Storage board, so we can
watch the analytics datastore fill and scale DO storage before it runs out.
SuperAdmin only (the s.guard wrap). Two REAL sources, each degrading independently:

- Fleet inventory (count · total capacity · monthly cost · per-volume region +
  attachment) from the DigitalOcean API — a new Volumes() on the existing
  DO_API_TOKEN client (paginated). DO gives capacity + attachment but NOT fill %,
  so a volume's used/pct stay ABSENT (the console renders "—", never a fabricated
  number).
- The analytics datastore's own fill from ClickHouse system.disks (the 200Gi PVC)
  over the SAME shared aiobject.DatastoreQuery the analytics + compute lenses use —
  no second connection. This is THE number the operator scales on. Near-full
  volumes raise an alert (warn ≥ 80%, critical ≥ 90%).

Honest by construction: DO unconfigured → empty fleet; datastore not connected →
no datastore card. admin creates no table and holds no storage state — it only reads.

Pure buildStorageSnapshot / alertLevel / datastoreFillFromRow are unit-tested
(fleet totals, cost, absent per-volume fill, the datastore card + alert, the
system.disks bytes→GiB→pct math, zero-capacity → nil). Pairs with console 8.4.151.
2026-07-22 22:36:12 -07:00
hanzo-dev ea65ba9e48 merge(main): integrate main (experiments+catalog) into campaign-gtm 2026-07-22 22:20:48 -07:00
hanzo-dev 73d51910a8 merge(main): integrate latest main into connectors-catalog-100 2026-07-22 22:18:54 -07:00
hanzo-dev bcc84015a8 fix(connectors): pin salesforce instance_url to SF hosts (reject IP/IMDS/port), invert recaptcha to allowlist, twitter confidential-client guard (red) 2026-07-22 22:18:29 -07:00
hanzo-dev 8baac66b43 feat(fleet): fn.run — the functions-runner lane on a linked node
A linked node with uv claims fn.run jobs from the org gpu-jobs queue: an
inline Python script executed in an ephemeral uv run env on the node own
GPU stack, result = output tail + exit code + duration; nonzero exit
fails the activity with the traceback. Poison-loop guard becomes
per-lane, so a render-less node (evo) still claims its own lanes and
declines renders back to the queue. E2E-proven: submit via tasks API ->
evo claim -> uv run (rocm-smi visible) -> result GET.
2026-07-22 22:14:04 -07:00
hanzo-dev 4164cd33b0 feat(campaign): compose the merged experiments primitive for creative A/B
Rebased onto origin/main (experiments primitive landed @52decbb). Campaign A/B now
composes clients/experiments instead of a nil-seam placeholder:

- experiment.go: AssignFunc composes experiments.Assign (bucketing); AnalyzeFunc
  composes experiments.Analyze (pull-model — it reads the metric from analytics
  itself, no duplicate measurement). Both nil-safe: single-creative honest default.
- metrics.go: GET /v1/campaign/:id/metrics embeds the A/B analysis (abTest) when a
  campaign runs >1 creative and an experiment is wired.
- apps/wire_seams.go: SetExperiment wires Assign+Analyze at the composition root
  (campaign-linked experiments live in the org's default project).

Tests: assigned variant flows to the executor plan (utm_content); single-creative
never assigns; assign-error fails soft to the default creative.
2026-07-22 22:00:10 -07:00
hanzo-dev 2f482b1ce4 feat(campaign): /v1/campaign GTM orchestration + paid channel consumes connectors
Top-level go-to-market plane: a Campaign is a VALUE that spans channels; a
Channel is an orthogonal EXECUTOR it fans out to. Each channel consumes the
connector plane via integrations.TokenFor — the campaign object never touches a
credential.

- clients/campaign: Campaign model + store (per-org SQLite, cek at rest), the
  Channel interface + injected-func registry, /v1/campaign surface (CRUD +
  launch/pause fan-out + channels add/remove + metrics), experiment seam for
  creative A/B (nil-safe).
- clients/ads/provider.go: the ad-network execution edge (LaunchPaid/PaidSpend/
  PausePaid) — resolves the org's ad token via TokenFor, Meta executed for real,
  fail-closed on a disabled connector. Standalone POST /v1/ads/campaigns/:id/launch.
- clients/analytics/campaign.go: CampaignMetrics — the ONE campaign-metrics query
  over hanzo.events, org + utm_campaign bound positionally (tenancy invariant).
- apps/wire_seams.go: paid channel wired at the composition root (campaign never
  imports ads, ads never imports campaign).

Tests: fan-out, connector-consumes-token (httptest Meta), tenant isolation,
connector-disabled-blocks-send, spend fan-in, analytics tenancy predicate.
2026-07-22 21:54:30 -07:00
blueandhanzo-dev c7376993b9 connectors: complete third-party catalog to 100% of the historical list
Add 20 connectors on the established declarative planes (no plane changes):

Key connectors (userScope, keyVerify) — CRM/support, analytics, commerce, content:
  zendesk, pipedrive, intercom, reamaze, optimizely, amplitude, mixpanel,
  posthog, coinbase_commerce, shipstation, shipwire, contentful, netlify.
Bespoke body-inspecting Verify (200-with-error-in-body) over a shared, redirect-
refusing transport (verifypost.go): authorizenet, recaptcha.
Org OAuth (AdminOnly, reuse the callback/state plane): salesforce (instance_url
  custody + SSRF guard), adroll, twitter (S256 PKCE derived from the client secret
  so no shared Authorize/Exchange contract changes), google_bigquery, google_cloud
  (reuse google.go plumbing, read-only scopes).

One shared subdomain-origin normalizer (zendesk/reamaze); shopify keeps its own.
Least-privilege scopes throughout; fail-closed + token-free verified per connector.
Real httptest tests: wiring/placement, KMS seal, fail-closed, tenant isolation,
token-free, least-privilege scope, PKCE challenge!=verifier, instance_url SSRF.
2026-07-22 21:53:26 -07:00
hanzo-dev 52decbbc04 merge(main): integrate latest main into feat/experiments 2026-07-22 21:40:22 -07:00
hanzo-dev bb147ac06d fix(experiments): gate winner-promotion on org admin (red finding — a prod flag write) 2026-07-22 21:39:39 -07:00
hanzo-dev d965a68885 feat(fleet): render an AMD APU as the processor it is
A unified-memory APU now reports the cpuinfo marketing name, normalized
from BIOS shouting: AMD RYZEN AI MAX+ 395 w/ Radeon 8060S ->
"AMD Ryzen AI Max+ 395 w/ Radeon 8060S (gfx1151)". Model numbers keep
their casing; discrete cards and non-Ryzen hosts keep their names.
2026-07-22 20:54:20 -07:00
hanzo-dev aca6db042a feat(account): remove trial funding — usage is pre-paid, org starts at zero
Business model: no trial credits. Onboarding no longer grants any starter
credit — onboardFirstRun drops the commerce GrantCredit call, the account
state drops the commerce client, and provision's result drops trialGranted.
The first-run path still drives the ONE atomic IAM provision (org + admin
move + hashed org-scoped credential); the org just starts at a zero balance.

Removed payout.Client.GrantCredit (its only caller was this funding path —
no dead code); the additive Deposit + the referral/affiliate/author programs
are untouched.

Test: first-run drives provision ONCE (owner/name from get-user, resolved
slug), no funding call; a retry converges.
2026-07-22 20:48:37 -07:00
hanzo-dev 9c56954ce6 feat(experiments): unified A/B EXPERIMENT primitive composing flags+analytics+research
/v1/experiments is the VALUE that composes three existing planes, never a fourth
engine. ASSIGNMENT = flags (deterministic subject->variant via engineEvaluate; no
second bucketing, no assignment store). MEASUREMENT = analytics (one org-scoped
hanzo.events query; the eventsWhere isolation invariant). EVIDENCE = research
(per-variant samples as kind=ab rows; two-proportion z significance is a pure
function over them). Lifecycle: create writes the multivariate flag def; assign is
a flags evaluation; analyze folds analytics outcomes per variant by joining each
subject to its flags assignment; decide promotes a winner by rewriting the flag
rollout to 100%.

Seams added (additive, one-way): flags.Assign/PutDef/GetDef, analytics.Outcomes,
research.Record/List. clients/campaign composes experiments.Assign/Analyze to run a
creative A/B without reinventing assignment or evidence.

Variant KIND is orthogonal: variant.payload can be a feature config, ad-creative
id, email subject, or model id.
2026-07-22 20:42:07 -07:00
hanzo-dev 27adcc80ea feat(fleet): honest AMD APU inventory — unified memory, family name, arch + ROCm/HIP
- An APU whose VRAM is a token carve-out now reports its GTT unified pool
  (Strix Halo: 1 GiB VRAM carve-out vs ~118 GiB usable) with unified=true;
  discrete cards keep dedicated VRAM. Fixes evo showing 1 GB.
- gfx family naming: gfx1151 -> AMD Strix Halo (also Strix Point, Phoenix),
  so the board says what the silicon is, not just the iGPU series.
- Inventory records the native gfx arch per GPU and the host ROCm + HIP
  versions (/opt/rocm/.info/version, hipconfig), surfaced on /v1/fleet/workers.
- docs: bring-your-gpu.md converged on hanzo link (gpu connect is gone).
2026-07-22 20:40:35 -07:00
hanzo-dev 787664527c feat(account): onboard drives ONE atomic IAM provision + funds the trial
The production signup path (POST /v1/iam/onboard) did create-organization THEN
move-user as two non-atomic S2S calls — a fault between them orphaned the org
(the exact bug IAM's provision() fixed), and it minted no credential and
granted no trial. First-run onboarding now calls the ONE atomic
POST /v1/iam/admin/provision (service-token) instead: org + admin move +
hashed credential + trial claim converge, and a mid-flight retry resumes on
the founder's own org rather than orphaning it.

On the one-time trial grant (the once-per-verified-identity claim IAM
returns), it funds the identity's CANONICAL org via commerce
POST /v1/billing/credit with a per-identity idempotency key
(starter:<verified-email>) — so the per-org dedup is a per-identity dedup, the
anti-farm gate (one trial per identity, not per org). Funding is best-effort +
idempotent: a hiccup never fails an onboarding that already provisioned.

The additional-org flow (caller already has a home org) is unchanged
(create-without-move). A legacy fallback keeps the old pair when the service
token is unset, so a partial deploy still onboards.

Test: first-run drives provision ONCE (owner/name from get-user, resolved
slug), funds with the per-identity key + bounded 500c to the canonical org,
and a retry grants no second trial → never double-funds.
2026-07-22 20:33:20 -07:00
hanzo-dev fe04a60187 Merge remote-tracking branch 'origin/main' into blue/research
# Conflicts:
#	apps/apps.go
#	apps/wire_test.go
#	clients/research/datastore.go
#	clients/research/research.go
#	clients/research/research_test.go
#	clients/research/ssrf.go
#	clients/research/store.go
2026-07-22 20:32:44 -07:00
hanzo-dev 61019879f4 feat(payout): idempotent GrantCredit (POST /v1/billing/credit) for on-signup funding
Deposit (POST /v1/billing/deposit) is additive — a retried onboard would
double-fund. GrantCredit posts the idempotent /v1/billing/credit: commerce
dedups on idempotencyKey, so the same key credits at most once. The starter
grant uses a per-identity key against the identity's canonical org, so the
per-org dedup is a per-identity dedup — the trial-abuse gate (one trial per
verified identity, not per org).

A *Client method only (not the shared Commerce interface), so the authors/
affiliates seams are unaffected.

Tests: posts /v1/billing/credit with the per-identity idempotencyKey +
bounded 500c + starter-credit tag + org namespace; unconfigured is an honest
error.
2026-07-22 20:26:04 -07:00
hanzo-dev d9f2735cf8 research: N2 — supersession is seq-authoritative, not client ts
Canonical ordering used client ts first. But the backfill importer stamps a wall-clock ts
(~1.7e9) while the SDK live path sends none (ts=0), so an SDK correction/retraction (ts=0)
of a backfilled experiment (ts=big) sorted BEFORE it and NEVER superseded — the stale
value stayed canonical while the producer saw added=1 (the exact 91.4→69.7 stale-correction
case in the intended backfill+live-SDK workflow). canonicalExpWhere/AttWhere now order by
the server's monotonic append clock seq (latest-APPEND-wins, un-forgeable by a client); ts
is display-only (measured-at). datastore.go notes the deferred canonical OLAP read must be
seq-authoritative too (never argMax(ts)).

Cross-tool PoC (TestSupersessionIsSeqNotClientTS): ts=big backfill → ts=0 SDK correction
wins (69.7) AND ts=0 SDK retraction withdraws (canonical=0); attempt correction likewise;
all 17 tests green.
2026-07-22 20:23:18 -07:00
hanzo-dev 68b0e1a0dc feat(integrations): Guide marketing/ad connectors — meta/google-ads/analytics/microsoft/tiktok/reddit/linkedin/warpcast/whatsapp (red GO, least-privilege) 2026-07-22 19:59:43 -07:00
hanzo-dev aef466ee2a fix(integrations): drop write-capable business_management from meta_ads scopes
Red MEDIUM: meta_ads is documented read-only, but metaScopes carried
business_management — read+WRITE to Business Manager assets (users, ad
accounts, system users). Ad-account enumeration uses /me/adaccounts under
ads_read, so no read path needs it; the custodied ~60-day token no longer
carries business-asset write authority.

Harden the forbidden-scope guard to reject business_management and any
*_management / rw_* grant (not just ads_management), so a write scope cannot
regress. Add two tests: the short-token fallback (fb_exchange_token leg fails →
seal the short token with its real ~now+3600 expiry, no refresh) and a
cross-provider state-confusion negative (a meta_ads state replayed at
google_ads/callback is rejected as invalid state).
2026-07-22 19:49:58 -07:00
hanzo-dev b93e7320b1 research: M1/M2 content-address artifacts server-side; M3 close SSRF denylist gaps
M1: the artifact sha256 was client-asserted + never verified (poisonable, hash-addressed
unearned). Now the caller submits the BYTES (base64 content); the SERVER hashes them and
that sha256 is the identity + ref (sha256:<hash>). A client-asserted sha256 must MATCH
(else 422); content is required; poisoning needs a preimage. Bytes are stored + retrievable
by hash (GET /v1/research/artifacts/:sha256, org-scoped). First-writer-wins resolved.

M2: Artifact.ref was an ungated file:// twin of the SSRF-gated endpoint. The server now
DERIVES ref = sha256:<hash> and ignores any client ref — no file:///etc/passwd can be
stored or served back.

M3: ssrfSafe comment corrected to best-effort INGEST HYGIENE (not the dial-time control);
added the ranges the stdlib predicates miss — CGNAT 100.64/10 (Alibaba IMDS
100.100.100.200), IANA protocol 192.0.0/24 (Oracle IMDS 192.0.0.192), 0/8, TEST-NETs,
198.18/15, 240/4, NAT64, v6 doc; named dialTimeGuardTODO as the greppable pin required
before any endpoint dialer ships.

17 tests pass incl content-address poisoning-rejected + blob round-trip + new SSRF ranges.
2026-07-22 19:48:50 -07:00
hanzo-dev 299dde6848 research: H1 — honor retraction (was a silent no-op)
revision is now part of content identity (hashExp/hashAtt) so a retraction of an
otherwise-identical run is a DISTINCT retained version, not an INSERT-OR-IGNORE no-op.
Canonical redefined: THE single latest version by (ts,seq); if that latest is retracted
the id has NO canonical (withdrawn) — the NOT EXISTS no longer filters revision, so a
newest-retraction wins and no earlier version resurfaces. Also canonicalize hashed JSON
(sorted-key, whitespace-free) so a re-serialization never mints a spurious version (L3).

Red PoC: retract → withdrawn from canonical (0), retained keeps both (2); a later
correction restores canonical. 16 tests pass.
2026-07-22 19:41:24 -07:00
hanzo-dev ae7330a539 feat(integrations): Guide marketing/ad/analytics OAuth connectors
Add nine org-scoped connectors for the Business AI Guide's Account-Linking
step, on the same registry + KMS-sealed custody as google/github/cloudflare:

  meta_ads          OAuth  Advertising  Facebook/Instagram Ads + Pages (long-lived token)
  google_ads        OAuth  Advertising  reuses google.go plumbing, adwords scope
  google_analytics  OAuth  Analytics    reuses google.go plumbing, analytics.readonly
  microsoft_ads     OAuth  Advertising  Microsoft Advertising (Bing), refresh token
  tiktok_ads        OAuth  Advertising  TikTok for Business, durable token
  reddit_ads        OAuth  Advertising  Basic-auth client, refresh token
  linkedin_ads      OAuth  Advertising  read + reporting, optional refresh
  warpcast          apikey Social       Farcaster via Neynar key (keyVerify)
  whatsapp          apikey Messaging    WhatsApp Cloud API token + phone id (keyVerify)

Each is one declarative provider file over the existing Provider contract;
oauth_http.go is the shared bounded, token-free transport the form/JSON
exchanges reuse. Scopes are least-privilege (read/reporting; write scopes
added when a write path is wired). All AdminOnly — linking a client's
marketing account is an org-admin action. Tokens are read by the ads /
analytics / marketing readers via integrations.TokenFor(org, provider, name).

Tests: authorize/exchange against httptest stand-ins, KMS seal-before-row,
verify-before-store fail-closed, tenant isolation, org-admin gate, and
token-free errors/responses per provider.
2026-07-22 19:31:20 -07:00
hanzo-dev 7ad8940061 feat(venue): /v1/cloud DO/AWS/GCP/Azure account connectors → fleet fold (red GO all 4; SafeRESTConfig gate) 2026-07-22 19:28:45 -07:00
hanzo-dev aa119d6108 research: wire /v1/research + R&D Ops Board into the cloud binary
The evidence plane (HIP-0512) was built + committed but orphaned — absent from
apps.Wire(), so it 404'd in prod and the board showed only its seed snapshot.
Wire it as a non-staged subsystem (mounts under the production mount-all default),
the arena's sibling right after benchmark, and mount its embedded R&D Ops Board at
/research (same-origin with the plane it reads).

- apps.go: import + {Name:"research", Mount, Shutdown} after benchmark
- wire_test.go: frozen sequence updated (research, non-staged, has Shutdown)
- research.go: mount the embedded board UI at /research (like tasks/ui)
- clients/research/ui: the board embed + serving test

go build ./cmd/cloud links (617MB); apps wire/staged guards + full research
suite green. Goes live at api.hanzo.ai/v1/research + /research on image deploy.
2026-07-22 19:25:34 -07:00
hanzo-dev e1158dc6eb fix(venue,fleet): close Red's 3 HIGH + 1 MED in the discovery/fold + keyless-verify path
HIGH-2 (exec-kubeconfig RCE) + HIGH-3 (SSRF guarded the wrong field): one hardened
fold entrypoint. fleet.SafeRESTConfig — which dynFromKubeconfig/Register now funnel
through (so it also closes the shared visor.attachCluster BYO path) — REJECTS a
kubeconfig that carries an exec or auth-provider credential plugin (client-go would
run a local binary with the pod's full env) and SSRF-guards restCfg.Host, the ACTUAL
dial target the node-list hits (https-only; no loopback/private/link-local/IMDS/
unspecified/multicast). The guard now covers the kubeconfig SERVER, not the
discovery-reported endpoint (which diverges for DO/Azure). Bypass env
FLEET_ALLOW_PRIVATE_HOSTS for loopback test apiservers only.

HIGH-1 (GCP credentialJson SSRF/LFI/exfil): validateGoogleCredential fail-closes the
customer credentials JSON BEFORE google.CredentialsFromJSON — only a service_account
key is accepted (token_uri pinned to a google host); an external_account (WIF) config,
whose credential_source.url/file and token_url are attacker-chosen (pod SSRF /
arbitrary file read / token exfiltration, firing during verify), is rejected. Keyless
WIF becomes a Hanzo-owned config (follow-on), never customer-authored.

MED-4 (AWS region SSRF): a region is validated against ^[a-z]{2}-[a-z]+-\d+$ before
it is interpolated into the STS/EKS host, so "evil.com/" can never redirect the
assumed-role token off-account.

Venue's wrong-field endpoint pre-guard is removed (fleet is the one gate). Tests:
fleet SafeRESTConfig (exec/auth-provider/non-routable/non-https reject, public allow,
bypass); venue exec-kubeconfig-not-folded, server-diverges-from-endpoint-guarded,
hostile-external_account-rejected, validateGoogleCredential, validRegion. Fold-consumer
suites (visor/ml/fleet) green; cmd/cloud links. (Harness: fiber v3 Test timeout raised
off its 1s default so CI-box load can't flake the fold's TLS dial.)
2026-07-22 19:19:57 -07:00
hanzo-dev 30f4f4cd40 docs(LLM): add /v1/cloud venue plane to the Open Cloud planes map 2026-07-22 19:19:57 -07:00
hanzo-dev 68d0399fbb feat(venue): add Azure (AKS) as the 4th provider — AAD + ARM REST, keyless WIF
Same discovery interface as DO/AWS/GCP, folding into the ONE fleet. An org
registers an Azure AD app (tenant + client): a client_secret drives the
service-principal flow; its absence selects KEYLESS Workload Identity Federation
(Hanzo presents its own federated OIDC token as a client assertion — no customer
secret stored). Discovery is plain ARM REST (net/http, no azure-sdk-for-go): GET
managedClusters per subscription, POST listClusterUserCredential for each
kubeconfig, fold. Tests cover both the SP and keyless-WIF paths (httptest AAD +
ARM stubs) plus token-free errors and keyless-seal.
2026-07-22 19:19:57 -07:00
hanzo-dev 910e18609c feat(base): forward /v1/collections/* to the managed Base orchestrator
The go:embed console (served BY the cloud binary) drives the Base product's
data plane at /v1/collections/* but has no Next BFF (pruned by build:embed), so
the calls hit cloud's native /v1 router — which had no such route → 404, and the
whole Base product (Bases manager + Records) went dark on console.hanzo.ai.

Add a principal-gated reverse proxy (clients/base/collections.go, the clients/o11y
pattern) that forwards /v1/collections[/*] 1:1 to the managed Base (base.hanzo.ai,
in-cluster Service; overridable via CLOUD_BASE_ORCHESTRATOR_URL/HOST) — the
in-binary replacement for the retired console BFF. cloud can't mint a hanzo.id JWT
(JWKS-only), so it forwards the caller's OWN Bearer; the managed Base validates it
and scopes tenants by the token subject. allowCollections reproduces the BFF's
least-privilege allowBaseSurface (collections data plane only; no Base admin tunnel).
Always on, before the embed gate. Tests: allow-list, director (Host+path+bearer),
principal gate (403 fail-closed).
2026-07-22 19:16:20 -07:00
hanzo-dev 9d71c41059 research: COALESCE empty-store totals (SUM over zero rows is NULL) + regression test 2026-07-22 18:24:29 -07:00
hanzo-dev a6dbbdf9f3 feat(venue): /v1/cloud connect-a-cloud-account plane — discover org clusters, fold into the ONE fleet
An org links labeled DigitalOcean / AWS / GCP accounts (verified live, KMS-sealed,
keyless where possible); venue discovers each account's native Kubernetes clusters
and folds them into clients/fleet.Register — the same registry visor surfaces at
/v1/clusters and ml federates onto. No second cluster registry.

- DigitalOcean: PAT -> GET /v2/account, list DOKS clusters, pull each kubeconfig (godo).
- AWS: cross-account STS AssumeRole pinned by external id (confused-deputy), eks
  List/DescribeCluster, k8s-aws-v1 presigned token. Hand-rolled REST + owned SigV4
  (pinned by the canonical get-vanilla vector); no aws-sdk-go-v2 service trees.
- GCP: Workload Identity Federation or SA key via oauth2/google, container REST
  clusters.list; no google container SDK / gRPC.

Multi-credential per org (labeled, /orgs/{org}/cloud/{provider}/{label}), org-scoped
and tenant-isolated, admin-gated mutations, SSRF guard on discovered endpoints,
per-new-cluster billing meter through the shared compute fee. One discovery
interface, thin providers behind it. Zero new module deps (godo + oauth2 present).
2026-07-22 18:24:22 -07:00
hanzo-dev b5e2237937 merge(main): integrate parallel main into the 3 drive-home plane merges 2026-07-22 18:24:06 -07:00
zeekayandhanzo-dev f50161a2b8 feat(analytics): behavior read lenses on /v1/analytics/top (pages/referrers/sources)
Extend the ONE breakdown endpoint with three org-scoped behavior lenses over
hanzo.events — answering WHERE people go, WHAT they look at, and WHERE they come
from — as ranked {key, pageviews, visitors, pct} lists alongside models/products:

- topPages       GROUP BY path (WHERE event='$pageview')
- topReferrers   GROUP BY referrer_domain, self/empty referrer bucketed "(direct)"
- topSources     GROUP BY utm_source, empty utm bucketed "(none)"

Read-side only: no ingest/write-core/schema change. Each lens rides eventsWhere
so the org is bound POSITIONALLY (never interpolated) — same tenant boundary as
every other query. pct is share of the TRUE in-window pageview total via
`sum(pageviews) OVER ()`, so a top-N list honestly shows the long tail. Every
lens degrades to honest-empty (available:false, empty items, Debug log) when the
events table is absent/errored — never a 500 (mirrors the overview web lens).

visitors=uniqExact(distinct_id), pageviews=count of $pageview — identical to the
web overview lens.

Tests: breakdownSQL binds org positionally + filters $pageview + buckets
direct/none + window-fn total; buildBreakdown pct is share of in-window total
(not returned-rows sum); honest-empty on datastore error. gofmt+vet clean, no
go.sum drift.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-22 18:23:27 -07:00
hanzo-dev 4e6950c77d feat(automations): /v1/automations IFTTT trigger plane on the one engine (red GO: rate-budget bounded) 2026-07-22 18:22:47 -07:00
hanzo-dev 5829869811 feat(cloudflare): /v1/cloudflare asset plane (Pages/Workers/Workers-AI/R2/KV/D1), Workers-AI on the unified spine (red GO)
# Conflicts:
#	apps/wire_test.go
2026-07-22 18:22:33 -07:00
hanzo-dev 0a08cc4c96 feat(integrations): GitHub Pages on the App token (red-SHIP: grant-cached, token-safe, 403-split) 2026-07-22 18:19:38 -07:00
hanzo-dev b9a9f856a4 research: diary artifacts — POST/GET /v1/research/artifacts (hash-addressed, private-by-default)
Adds the research-diary artifact record (raw-artifact retention class): a
dashboard-snapshot (PNG of the canonical board) or ai-report (generated page),
addressed by sha256 content hash — a re-POST of the same bytes is a no-op (the
hash-addressed idempotency). The bytes live at ref (blob store); this stores the
verifiable manifest with the same provenance (project, git_sha/branch/dirty,
lib_versions) as a run.

  POST /v1/research/artifacts        record one artifact (idempotent by sha256)
  GET  /v1/research/artifacts?run=&project=&since=   diary feed, newest-first

Private by default; public only via the separate visibility grant (POST
/v1/research/grants with sha256), the same rule as runs; no implicit training/commons
rights. Rolls up to hanzo.research_artifact (append-only, keyed by sha256). 14 tests
pass.
2026-07-22 18:12:12 -07:00
hanzo-dev 5c8338c0be research: versioned append-only model + first-class provenance + consent (CTO legal model)
Reshapes the AttemptStore per the updated ToS/DPA/Research-Supplemental terms:

- VERSIONED, not write-once. A correction APPENDS a new version under the same
  stable id; the prior is RETAINED (superseded), never mutated. Version identity is
  content_hash over the measurement AND its provenance, so an idempotent re-ingest is
  a no-op while a corrected number or a run on a new commit/lib version is a new
  retained version. revision ∈ {original,corrected,retracted}; canonical/superseded
  are derived (latest non-retracted per stable id).
- RETAINED vs CANONICAL exposed as distinct counts everywhere (ingest response,
  /totals, /projects). retained is the truth; canonical is the deduped view, so dedup
  never reads as loss. faulted/failed runs are retained (negative results are evidence).
- PROVENANCE first-class + queryable: project (column), git_sha/git_branch (indexed),
  git_dirty, lib_versions (structured JSON) — the longitudinal 'which lib version
  regressed X' record.
- PRIVATE by default; visibility (private/org/public) + trainable + publishable are
  each a SEPARATE authorized grant (POST /v1/research/grants), never implied by upload.
- Retention classes separable (nonpersonal metadata/provenance permanent; raw
  artifacts own retention; secrets never stored). Honest durability label: versioned ·
  append-only; cloud mirroring rolling out — NOT yet immutable/replicated/recovery-tested.

12 tests pass (pure-Go): idempotent-by-content, correction-appends-version,
provenance-distinct-versions, faulted-retained, private-by-default+grant,
projects/totals canonical+retained, SSRF, HTTP round-trip+provenance+tenant-isolation,
grant-separate-from-upload.
2026-07-22 18:01:14 -07:00
hanzo-dev 12f2afc69c chore(deps): bump hanzoai/ai v1.831.0 (12-model BYOK catalog) + refreeze wire order (benchmark) 2026-07-22 17:49:49 -07:00
hanzo-dev 819b6e1677 research: /v1/research evidence plane — per-org SQLite source of truth + hanzoai/datastore roll-up (HIP-0512)
Adds the Hanzo Research surface (HIP-0512 §"Hanzo Research"): every experiment
across every product accrues as immutable, queryable evidence under one
discriminator (kind ∈ benchmark|kernel-perf|training|ablation|policy-eval).

Two planes: each org's transactional SQLite (per HIP-0302, physical file
isolation) is the durable source of truth; it rolls up best-effort into
hanzoai/datastore (ClickHouse) via the account-usage warehouse pattern for the
cross-project OLAP surface. A datastore outage degrades to rolled_up:false, never
a failed ingest.

Ingest is idempotent by stable id — attempt by (project,benchmark,item,model),
experiment by (project,<kind>:<subject>:<task>) with a ts-guarded upsert for
latest-run-canonical — so a corpus imports exactly once however many times it is
replayed (the no-data-loss guarantee) and an out-of-order replay of an older run
cannot regress a newer number.

Surface:
  POST /v1/research/experiments   ingest a batch → SQLite → roll up
  GET  /v1/research/experiments   list, latest-run-canonical (?project= ?kind=)
  GET  /v1/research/projects      every project + real totals (ops board)
  GET  /v1/research/totals        headline aggregate + per-kind (?project=)

Org is the physical tenant boundary (validated principal, never a client field);
project is a first-class column so the org's ops board aggregates across its
projects in one query. BYO endpoint is SSRF-gated at ingest (loopback/private/
link-local/metadata denylist, https required). status is a stored run-state field
(default complete); the live leasing state machine is the durable-execution
increment.

Tests (9, pure-Go): idempotent double-ingest, latest-run-canonical + no-regress,
attempt immutability, project/totals aggregates, SSRF denylist, HTTP round-trip +
tenant isolation + fail-soft roll-up.
2026-07-22 17:49:49 -07:00
hanzo-dev 86a0607a51 fix(cloudflare): floor the per-call BYO inference fee (red F-1)
A non-text Workers AI modality (whisper audio, vision/classification image
bytes) yields no prompt text, so aiPromptText → "" → EstTokens → 0 → the
token-denominated BYO fee → 0. ResourceMeter.Gate short-circuits on a
0-cent cost BEFORE calling commerce Authorize, so a frozen / broke /
over-cap org got ungated, unbilled Hanzo-proxied inference — no balance
check, no debit row.

Root cause: a token-denominated fee cannot price a non-text modality. Fix:
floor the per-CALL fee. BYOInferenceFeeMicros now returns max(token fee,
BYOFloorMicros) with a non-zero default floor ($0.0001), so:
  - the gate reservation is ALWAYS >= 1 cent → the gate ALWAYS runs → a
    frozen/broke/over-cap org is REFUSED, never proxied;
  - every /ai/run leaves a debit row >= the floor → no silent proxied call.
This closes F-1 and the F-2 unbilled-call gap (same root cause) together.

Also reorder aiRun: the balance/freeze gate now runs BEFORE account
resolution, so a refused org makes ZERO Cloudflare contact (no discovery,
no run). The floor is one shared, generic knob in the inference-billing
spine (CLOUD_AI_BYO_FLOOR_UUSD) — not a Cloudflare-specific path.

Tests: a broke org + a non-text model is refused 402 with zero CF contact
and zero debits; a funded text run whose model reports no usage still bills
the floor. BYO fee/floor math unit-tested with the floor isolated.
2026-07-22 17:47:21 -07:00
blueandhanzo-dev 3d7ef2f0c1 fix(automations): bound the trigger run-start surface (RED HIGH-1/MED-1/MED-2/LOW-1)
Deliver was the only run-start path with no bound. Add three orthogonal per-org
bounds in the ONE shared startRun, plus the loop/redelivery hardening:

HIGH-1 amplification (self-trigger loop / fan-out / hook-hammer):
- concurrency: orgRunLimiter now guards EVERY run-start (moved into startRun; runFlow
  parity), full → 429.
- durable rate budget: CountRunsSince (persisted rows, survives restart) caps run-starts
  per rolling minute (CLOUD_AUTOMATIONS_RUNS_PER_MIN, default 300), enforced BEFORE the
  insert → a fan-out/loop hits the ceiling and stops.
- causation depth: TriggerEvent.Depth → FlowRunInput.Depth; Deliver refuses at
  maxCausationDepth so an in-platform cycle terminates. /hooks reads X-Causation-Depth;
  the seam carries depth.

MED-1: the github push webhook skips a bot/App-authored push (isBotActor "[bot]") — our
own outbound mirror pushes AS the App bot, so "on push → our push → push" cannot loop.
MED-2: engine readiness is checked BEFORE the run-row insert, and a transient start
failure DELETEs the row (not FAILED) — a not-ready/crash no longer burns the DedupeKey,
so redelivery retries instead of dropping the event.
LOW-1: /hooks with no X-Idempotency-Key content-hashes the body, so a hammer of identical
POSTs collapses to one run.

Tests (cgo + pure-Go, race-clean): TestDeliverLoopBounded (in-platform cycle terminates),
TestDeliverRateCapped (durable budget), TestDeliverEngineNotReadyRetryable (no key burn),
TestInboundHookContentHashDedupe, TestBotActorGuard.
2026-07-22 17:46:14 -07:00
blueandhanzo-dev f39205b729 refactor(automations): decomplect trigger-arrival + unify run-start (one way)
Polish toward one-way + compose, no behavior change:

- armTrigger: the ONE trigger-SOURCE arrival plane (cron schedule for POLLING,
  routing-index subscription for WEBHOOK/APP_WEBHOOK, nothing for MANUAL),
  extracted out of setEnabled so status-flip and trigger-arrival are separate
  concerns. The action chain is untouched here — any trigger source pairs with any
  actions (a product, not a switch).
- startRun: the ONE way a firing turns (rule, run id, event) into a durable run —
  persist-gate then dispatch, threading the event payload. Shared by the manual
  /run and event Deliver paths; a cron tick still starts through the engine
  schedule. Deliver collapses to pure match + dispatch; runFlow to a lean handler.

Tests green (cgo + pure-Go), race-clean.
2026-07-22 17:46:14 -07:00
blueandhanzo-dev 7fbe7999cd feat(automations): compose inbound webhooks into the trigger engine (github seam)
Wires the existing verified provider webhooks into the automations Deliver plane
via a composition-root seam, so a real external event fires subscribed flows —
without integrations importing automations (which imports it for credential
custody).

- integrations.SetAutomationTrigger: a primitive-typed seam (nil-safe no-op when
  automations is disabled), set once at the apps composition root to
  automations.Deliver.
- github push webhook now also fires github/push to subscribed flows for the
  signature-verified installation org (best-effort; ev.After is the dedupe key).
- stripe/channels reach the SAME Deliver with a one-line fireTrigger call.

Test: the seam passes the verified event verbatim, fail-closes on empty org, and
no-ops unwired.
2026-07-22 17:46:14 -07:00
blueandhanzo-dev 3b405ffa7a feat(automations): inbound event triggers — fire flows on webhooks/messages/cron
Adds the IFTTT inbound plane to the ONE automations engine: an external event
(provider webhook, inbound message, scheduler tick) starts every enabled flow
whose WEBHOOK/APP_WEBHOOK trigger matches (source, event), threading the event
payload into the run as {{trigger.*}}.

- trigger.go: Deliver(ctx, org, TriggerEvent) — org-scoped match over the routing
  index, per-org durable start via the shared engine (runStarter -> executeFlow),
  at-most-once by DedupeKey (CreateRunIfAbsent gate), fail-closed on a missing org.
- store: automations_triggers routing index (org, provider, event -> flow+version),
  maintained by setEnabled — the inbound analog of the POLLING cron schedule.
- engine: seed outputs["trigger"] so actions read the firing event.
- POST /v1/automations/hooks/:source/:event — authenticated inbound sink.
- each run emits ONE o11y event beside the exactly-once meter + audit.
- main_test.go: cek dev-key TestMain (mirrors clients/sync) so the suite runs under
  cgo and pure-Go alike.

Tests: trigger->action fire + payload threading (real embedded engine), tenant
isolation, idempotency, fail-closed, HTTP org gate, enable/disable lifecycle.
2026-07-22 17:46:14 -07:00
hanzo-dev bf3975de81 fix(integrations): address Red review on GitHub Pages (grant cache, 403 disambiguation, secret scrub)
LOW-1: cache the installation grant set per-installation-id (45s TTL) so a
status-polling console no longer re-enumerates up to 100 upstream repo pages
on every Pages request. Keyed strictly by installation id (never org name) and
TTL-bounded, so a reconnect gets a fresh key and a revoked grant cannot outlive
the TTL — the cache can never widen cross-tenant scope.

LOW-2: pagesErr now distinguishes a rate-limit 403/429 (x-ratelimit-remaining:0,
Retry-After, or a rate-limit body) — surfaced as 429 with the retry hint — from a
genuine permission 403 that keeps the actionable re-authorize message.

INFO-1: truncateBody redacts credential-shaped substrings (gh*_ / github_pat_ /
Bearer <value>) from any surfaced provider error body — defense in depth.

Adopts Red's github_pages_adversarial_test.go (two-installation cross-tenant +
injection/cname/token/confused-deputy matrices) and adds fast-follow tests for
the grant-cache keying/collapse, the 403/429 split, and the secret scrub. Full
integrations suite green under -race.
2026-07-22 17:42:03 -07:00
hanzo-dev 9911d9970c feat(integrations): GitHub Pages management on the App installation token
Five org-authed routes, siblings of the repo list/import, addressing one
repo as a resource on the same short-lived installation token:

  GET    /v1/integrations/github/repos/:repo/pages        status + live URL + custom domain
  POST   /v1/integrations/github/repos/:repo/pages        enable/configure (branch source or Actions)
  PUT    /v1/integrations/github/repos/:repo/pages        set/clear custom domain, HTTPS, source
  DELETE /v1/integrations/github/repos/:repo/pages        disable
  POST   /v1/integrations/github/repos/:repo/pages/builds request a build

Org comes from the validated principal; the repo name is intersected with
the installation's granted set and the owner is taken from GitHub's own
full_name, so a caller can neither address an ungranted repo nor inject an
owner into the GitHub API path. The token rides only the Authorization
header. Fail-closed: unconfigured 503, unconnected 409, ungranted 404.
2026-07-22 17:42:03 -07:00
hanzo-dev 42d533d616 test(apps): refreeze wire golden — add benchmark subsystem
The benchmark subsystem was added to Wire() (native /v1/benchmark arena)
without updating the frozen mount-order golden, so TestWireOrderMatchesFrozen
fails on main (93 Wire specs vs 92 frozen). Add the missing entry in its
Wire() position (after evals). Mechanical refreeze, independent of the
Cloudflare asset plane in the parent commit.
2026-07-22 17:41:07 -07:00
hanzo-dev d930c60dce feat(cloudflare): first-class /v1/cloudflare/* asset plane
Consolidate the per-org Cloudflare asset plane under the first-class
/v1/cloudflare/* prefix (sibling of /v1/dns, /v1/domain): connecting the
provider stays on the integrations plane, managing resources moves here.

Surface + core-manage each resource against the CF v4 API with the org's
own KMS-sealed token (fail-closed, tenant-isolated on the validated
principal):
- Zones + Analytics (read): list/get zones, zone traffic dashboard
- Pages, Workers (handlers unchanged, prefix relocated)
- Workers AI: POST /ai/run/{model} metered inference
- R2, KV (+ key value get/put/delete), D1 (+ query): wired for real
  (were Phase-2 501 stubs)

Thin hand-rolled REST over the CF v4 API on net/http, decomplected to one
seam: client.send is the ONE authed request/read primitive (Bearer-only,
bounded, token-free); envelope unwrap (exec/cfDo/cfUpload), verbatim relay
(pass), raw value (getRaw) and the AI run (runAI) all compose over it, so
the request/auth/error dance is written once. acctClient/acctWrite are the
ONE auth+account preamble every account-scoped handler shares — each
resource handler is a thin, orthogonal body over those two seams.

Workers AI meters through the ONE unified usage/billing spine
(cloud.AIMeterProvider "ai") and emits the ONE gen_ai o11y span
(clients.StartGenAISpan), at the thin BYO fee since the org's own token
already paid Cloudflare for the compute. New shared, generic (not
CF-specific) inference-billing surface in metered_ai.go: BYOFeeBps /
BYOInferenceFeeMicros / MicrosToGateCents + exported AIMeterProvider and
EstTokens. The gen_ai span constructor is extracted from aihttp.go so
chat, embed and workers-ai share one.

Least-privilege connector scopes grown to match the now-wired surfaces
(R2/KV/D1/Workers-AI/Analytics). Model, key and id path segments are
validated (anchored charset + no-traversal) so no caller value can
smuggle path structure or a host into an upstream URL.

Tests (httptest CF stub + fake commerce): tenant isolation, the model
SSRF guard, the org-admin mutation gate, raw KV value relay, D1 query,
and the Workers AI debit landing on the unified "ai" spine.
2026-07-22 17:41:07 -07:00
hanzo-dev 2b61d83ea8 research: mount /v1/research in the composition root + freeze wire order
Registers the research subsystem in apps.Wire() (after benchmark, before
treasury) with its Shutdown, and freezes its position — and benchmark's, which
closes a pre-existing Wire/frozen gap on main — in TestWireOrderMatchesFrozen.
2026-07-22 17:35:37 -07:00
zeekayandhanzo-dev 32091f488c refactor(analytics): unify event ingest onto ONE canonical door /v1/event
Make POST /v1/event the single canonical ingest door: one handler
implementation, one write core (ingestEvents), serving every wire shape
and every auth context. The other five routes become thin aliases/shims
delegating to it.

- decodeIngest: ONE wire-tolerant decoder accepting a bare Event object,
  a bare [Event] array, AND the {batch:[…]} | {events:[…]} envelope the
  Segment/beacon/publishable paths speak — all yielding the SAME
  []CaptureEvent the write core consumes.
- eventTenant: auth is the orthogonal pluggable concern on the one door —
  (1) IAM bearer, (2) write-only publishable key (pk_, folded in from the
  old /v1/ingest), (3) out-of-band IAM access key; fail-closed 403 with NO
  brand-host fallback on the canonical door.
- ingestBody: the ONE ingest core (tolerant decode → foldException → the
  ONE write core). eventIngest, the site-host carve (eventWithOrg), and the
  /v1/ingest alias all funnel through it; auth is the only per-door
  difference.
- Site-host carve repointed to /v1/event (eventWithOrg forces org from the
  resolved Site); isAnalyticsPath adds /v1/event so a published-site beacon
  POSTing <host>/v1/event lands host-forced. The org-forced-from-host
  adversarial invariant holds for /v1/event too.
- /v1/ingest is now a thin DEPRECATED alias of eventHandle (one-shot
  deprecation log, $source=ingest tag); /v1/ingest/keys minting unchanged.
- /v1/analytics{,/batch}, /v1/tracker, /v1/insights/e kept as thin
  foreign-protocol shims (external Segment/PostHog compat only) funnelling
  through the SAME write core; captureWithOrg now delegates to ingestBody.

Write core and hanzo.events schema unchanged. Tests prove the three wire
shapes land identically, pk_/bearer/host auth contexts resolve the same
tenant into a byte-identical warehouse row, and the exact app beacon
{batch:[ev]} body is accepted on /v1/event via the site-host carve.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-22 17:35:24 -07:00
hanzo-dev d6ca4ba692 research: /v1/research evidence plane — per-org SQLite source of truth + hanzoai/datastore roll-up (HIP-0512)
Adds the Hanzo Research surface (HIP-0512 §"Hanzo Research"): every experiment
across every product accrues as immutable, queryable evidence under one
discriminator (kind ∈ benchmark|kernel-perf|training|ablation|policy-eval).

Two planes: each org's transactional SQLite (per HIP-0302, physical file
isolation) is the durable source of truth; it rolls up best-effort into
hanzoai/datastore (ClickHouse) via the account-usage warehouse pattern for the
cross-project OLAP surface. A datastore outage degrades to rolled_up:false, never
a failed ingest.

Ingest is idempotent by stable id — attempt by (project,benchmark,item,model),
experiment by (project,<kind>:<subject>:<task>) with a ts-guarded upsert for
latest-run-canonical — so a corpus imports exactly once however many times it is
replayed (the no-data-loss guarantee) and an out-of-order replay of an older run
cannot regress a newer number.

Surface:
  POST /v1/research/experiments   ingest a batch → SQLite → roll up
  GET  /v1/research/experiments   list, latest-run-canonical (?project= ?kind=)
  GET  /v1/research/projects      every project + real totals (ops board)
  GET  /v1/research/totals        headline aggregate + per-kind (?project=)

Org is the physical tenant boundary (validated principal, never a client field);
project is a first-class column so the org's ops board aggregates across its
projects in one query. BYO endpoint is SSRF-gated at ingest (loopback/private/
link-local/metadata denylist, https required). status is a stored run-state field
(default complete); the live leasing state machine is the durable-execution
increment.

Tests (9, pure-Go): idempotent double-ingest, latest-run-canonical + no-regress,
attempt immutability, project/totals aggregates, SSRF denylist, HTTP round-trip +
tenant isolation + fail-soft roll-up.
2026-07-22 17:28:09 -07:00
antje 39e472a88c feat(commerce): re-expose plan authority CRUD at /v1/plans/* + commerce v1.49.13
Re-ship increment 3a (the subscription/DNS plan CHARGE authority). Restores the
mount reverted in 8c87a38fa after the v1.49.12 seed bug, now on the RED-approved
fix commerce v1.49.13 (fix/plans-seed-roundtrip):
  - models/plan Metadata_ datastore:",noindex" (envelope round-trips; team.minSeats
    no longer served null)
  - bundle expansion builds a LOCAL zero-price childSnapshotPlan — never writes a
    $0 partial row into the plan authority (fixes world-pro/world-team $0 under-charge)
  - corrective boot seed force-corrects unmanaged partial rows to the embed while
    leaving admin edits (Managed) authoritative

Mount mirrors the 2b catalog mount: planapi.AdminRoute(storeV1, commercebilling.
SeedRows) on the /v1 bundle + own /v1/plans in commercePrefixes so it reaches
commerce (requireSuperAdmin-gated), not the AI /v1/* 402 catch-all. PUBLIC read
stays GET /v1/billing/plans. Money-path suites green (TestProdPath_SeedReadbackAllFields,
TestProdPath_CorrectsPreexistingBadRows); cloud prefix tests green.
2026-07-22 17:16:03 -07:00
zeekayandhanzo-dev 11e08b17aa feat(analytics): route /v1/analytics beacon ingest on published site hosts
Published sites POST analytics beacons to <site-host>/v1/analytics (and
/v1/insights/e), but that hit the static site server and 405'd — while
/v1/base already routed via the sites base-carve. Mirror the base carve
exactly for analytics ingest, so a page on yadota.hanzo.app (or a bound
custom domain) can send its own beacons into hanzo.events.

sites: add analyticsHostHandler + SetAnalyticsHostHandler + isAnalyticsPath
(prefix /v1/analytics OR ==/v1/insights/e). In Middleware, for both the slug
host and the custom-domain branch, carve the ingest POST to the handler with
org = resolved Site.Org (server-supplied, host-derived — never the caller/
body), gated on method POST so the authenticated GET read lenses
(/v1/analytics/overview|timeseries|top on api.hanzo.ai) are never hijacked.
The base carve stays first and independent.

analytics: extract captureWithOrg / insightsWithOrg — the Segment/beacon and
PostHog decode+ingest cores with an EXPLICIT org — so the deprecated aliases
(org via captureTenant) and the site-host carve (org forced from the Site)
share the ONE write core (ingestEvents), no copy. build() installs the carve
via sites.SetAnalyticsHostHandler, gated by the same already-existing flag the
anonymous ingest path uses (CLOUD_ANALYTICS_PUBLIC_CAPTURE, default ON); off
⇒ a site host 405s a beacon POST, unchanged.

Tests: sites carve routing (slug + custom host force Site.Org, not body/header
claim; GET serves static; /v1/base still routes to base; self host Continues;
non-live 405; no-handler 405; isAnalyticsPath). analytics end-to-end through
Mount+sites.Middleware (forced site org, 503-not-403 discriminator; empty
batch 200; custom domain; GET not hijacked; non-site host uses the normal
gate; disabled when public capture off).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-22 17:02:10 -07:00
hanzo-dev 18f74ea7e6 feat(link): --mirror flag — explicit off-switch for the render mirror sweep
The render mirror sweeps every local studio output into the org library
with the WORKER token, so on a box whose login org differs from the
content org it misroutes files; until now the only disable was pointing
--studio-url at a dead port. --mirror=false is the honest switch; default
true keeps current behavior. Ported from feat/per-gpu-queue 9468354
(superseded branch — the gpu command family there became link on main).
2026-07-22 16:53:17 -07:00
antje 00a9fdc2b4 chore(deps): bump hanzoai/iam v1.32.2 → v1.33.0
Clean-room IAM cutover-parity release. v1.33.0 closes the gaps cloud's
consumers need for a casdoor→clean-room identity cutover:
- orgs membership claim on tokens (multi-org tenancy the validator reads)
- casdoor membership verb aliases (clients/team invite consumes)
- get-user?accessKey= key resolution (hk-/pk-/sk-, CapKeyResolve-gated)
- Docker Registry v2 token + JWKS endpoints
All exported surface cloud imports (pkg/model, pkg/store, server) unchanged
→ compile-safe. NO deploy, NO CLOUD_IAM_IMPL flip (retired); casdoor remains
the live authority until the staged shadow-parity cutover.
2026-07-22 16:14:28 -07:00
hanzo-dev 9ad57a957c sites: drop reserved labels from the first-party allowlist (RED F-2)
Belt-and-suspenders on the brand apex: New() now filters IsReserved labels out of the
first-party allowlist (logging the drop), so an operator setting CLOUD_SITES_FIRSTPARTY=
login (or api/wallet/console/…) can never turn an auth-sensitive host into a publishable
site. Default cd,flow,gallery are clean and unaffected. TestFirstPartyDropsReserved pins it
(cd/flow/gallery serve; api/login/wallet dropped). Closes RED's last actionable finding —
F-1 (org-pin) already fixed in 541c63f; host-parsing + Base-path RED-confirmed sound.
2026-07-22 15:28:36 -07:00
hanzo-dev 541c63fedb sites: org-PIN first-party hosts (RED #4 ship-blocker) — never shadow-able
RED review of the first-party allowlist found the real risk: siteSlug returns a bare
slug and serve() resolved it via ResolveUniqueLiveSlug (the unique-LIVE-slug-across-ALL-
orgs fallback). So cd.hanzo.ai → Resolve('cd') → a CUSTOMER's project named 'cd' could be
served on our internal brand host — and via the OAuth-redirect path in reserved.go that is
account takeover. The allowlist gates WHICH labels serve; it did NOT pin WHOSE project.

Fix: first-party resolution is PINNED to the owning org (hanzo). siteSlug now returns a
firstParty flag; serve()/resolveLivePinned route a first-party host through the new
Resolver.ResolveOrg → store.ResolveOrgLiveSlug (WHERE org=? AND slug=? AND status='live'),
which can NEVER return another org's project. Multi-tenant hanzo.app is unchanged (still
unique-across-orgs). Fail-closed: no owning org (CLOUD_SITES_FIRSTPARTY_ORG, default hanzo)
⇒ first-party disabled entirely.

TestFirstPartyOrgPinned proves it: a first-party host calls ResolveOrg(hanzo,slug) and NEVER
the unique-slug Resolve; a multi-tenant host does the opposite. tsc/build green.
2026-07-22 15:25:06 -07:00
hanzo-dev 4a916c7f0e build(cloud): build ONLY the cloud binary — retire the Go hanzo CLI target
The shipped hanzo is the Rust CLI (~/work/hanzo/cli, curl hanzo.sh); the Go
cmd/hanzo was only ever a local 'make hanzo' control-plane build (CI/release
already build only cloud). Remove the make target so cloud builds exactly the
one stateless unified-API binary. cmd/hanzo + cli/ stay as reference for the
still-to-port client-side tools (GPU fleet worker link, runner, engine,
security); the code wrapper + zen-tier 1M mechanism are now in the Rust CLI.
2026-07-22 15:24:39 -07:00
hanzo-dev ef53a03ba7 sites: first-party apex (hanzo.ai) — OPT-IN allowlist for OUR internal sites
Converge cd/flow/gallery.hanzo.ai off the legacy s3://cdn staticFiles plane onto the
Projects PaaS plane (clients/sites → hanzo-sites/hanzo/<slug>). The site router served
only <slug>.hanzo.app (user sites); hanzo.ai is a SelfDomain it never resolved.

hanzo.ai is INTERNAL-ONLY (users get <slug>.hanzo.app), so it uses the OPPOSITE security
model to the multi-tenant apex: sites are OPT-IN via an explicit allowlist
(CLOUD_SITES_FIRSTPARTY=cd,flow,gallery on CLOUD_SITES_FIRSTPARTY_APEX=hanzo.ai). ONLY an
allow-listed label serves; EVERY other hanzo.ai host (api/console/iam/kms/world/chat/…,
listed in reserved.go or not) falls through PROTECTED by default — so a first-come project
can never shadow a real internal host (the reserved.go OAuth account-takeover). No
denylist-completeness burden on the brand's own domain. hanzo.app (user sites) unchanged.

Tests: TestSiteSlugFirstParty pins the boundary (allow-listed serve; api/iam/kms/world/
unlisted all protected; dotted key can't match; hanzo.app unaffected). tsc/build green.
2026-07-22 15:14:21 -07:00
hanzo-dev 57740cfc50 benchmark: AttemptStore seam + runner + presets + proof tests on real data
Architecture per CTO directive: read/leaderboard/compare/worker go through the
AttemptStore interface — fileStore is LOCAL-DEV (DataDir JSONL); the cloud backend
(relational + object store, stateless API) swaps in behind the same interface, no
handler change. NEVER pod-local writes in prod.

- store.go: AttemptStore interface + fileStore (append-only, idempotent by item×model)
- runner.go: execution worker (OpenAI-compatible call → extract → score → Append,
  cache-before-spend via Has); items from the evaluator plane
- presets.go: POST/GET /v1/benchmark/presets — design-your-own router blend (enso-<name>)
- benchmark_test.go: PROVES on real attempts — fable-5 measured 81.3 vs published 94.6
  (gap +13.3), grok vs gpt-5.6-sol paired n=198 net+5 McNemar p=0.30, exact-McNemar unit

Fugu Ultra GPQA claim 95.5 vs our harness 94.4% (answered) is the flagship
replicate-or-disprove. Builds clean; unified binary links.
2026-07-22 14:36:10 -07:00
hanzo-dev 1decfcdfc2 benchmark: native /v1/benchmark arena — replicate-or-disprove any provider
Sibling to /v1/eval, mounted into the unified cloud binary (apps.go). The benchmark
ARENA: run the top-14 canonical public benchmarks against any model/endpoint under ONE
standardized harness, and replicate-or-disprove a published claim. Provenance-first,
never blended: published_claim (vendor-reported) vs hanzo-measured (our harness) are
separate planes — the gap is the signal (Fugu claims GPQA 95.5; our harness measures
~92-95 by fault accounting; fable-5 claims 94.6, we measure 81.3).

Routes: GET /catalog (top-14, native flags), GET /leaderboard?benchmark= (per-model
measured ∥ published, coverage-aware), GET /compare?a=&b= (paired common-set +
rescue/damage + exact McNemar — the only valid arm-vs-arm test), POST /runs (BYO model
or endpoint; cache-before-spend; execution worker follow-on). Builds clean; unified
binary links.
2026-07-22 14:36:10 -07:00
antje 8c87a38fa5 Revert "feat(commerce): expose plan authority CRUD at /v1/plans/* + commerce v1.49.12"
This reverts commit cb977a9633.
2026-07-22 14:27:28 -07:00
zeekayandhanzo-dev 0a6b51a721 feat(projects): wire analytics + Base data space ON by default for new projects
Every new project now gets analytics collection and a Base data space
(form/forum/data submissions) wired by default — no opt-in — through the ONE
create path.

- createProject applies setProjectDefaults(analytics ON unless the caller passes
  analytics:false; space_id = "<org>/<slug>") then best-effort provisions the
  Base space. /v1/sites (ensureProject) routes through the same helpers, so
  defaults live in exactly one place.
- Fail-soft: a Base provisioning error (incl. embed disabled) is logged and
  swallowed — it never fails project creation, mirroring the CF edge-purge policy.
- clients/base.EnsureSpace: idempotent, in-process (no HTTP) provisioner that
  opens the org's per-org Base app and ensures the public-create "submissions"
  collection exists.
- store: additive analytics/space_id columns (migration matches the existing
  cache_control/last_purge_at ALTER pattern); analytics defaults ON for existing
  rows too. Exposed on the project view as analytics/space.

Tests: analytics default-ON, analytics:false opt-out, space provisioned on
create, and provisioning failure is fail-soft (create still 201, persists).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-22 14:09:12 -07:00
antje e6fd762b25 fix(team): flatten model HTML in bot replies — a bot answering '<p>yes.</p>' now renders 'yes.', not the literal tag (double-escape bug on hanzo.team DMs/channels) 2026-07-22 14:06:26 -07:00
antje cb977a9633 feat(commerce): expose plan authority CRUD at /v1/plans/* + commerce v1.49.12
Increment 3a — the subscription/DNS plan CHARGE authority. Mirrors the 2b catalog
mount: register commerce's plan SuperAdmin CRUD (api/plan -> planApi.AdminRoute)
on cloud's /v1 bundle group, injecting the embed seed source
(commercebilling.SeedRows — the SAME @hanzo/plans embed the boot seed +
resolveSubscriptionPlan read), and own /v1/plans in commercePrefixes so it reaches
commerce, not the AI /v1/* 402 catch-all.

commerce v1.49.12 (feat/plans-sot cherry-picked onto v1.49.11): models/plan
authority + runPlansSeed (env COMMERCE_PLANS_SEED, idempotent/count-gated) +
resolveSubscriptionPlan reads the editable authority with embed fallback. The mint
gates score the IMMUTABLE embed (paidTier/IncludedMonthlyCents), NOT the DB price —
an admin edit never moves a charge gate. Seed == embed (TestSeededPricesEqualEmbed),
so first boot changes NO charge. Each handler requireSuperAdmin-gated (anon -> 403).
2026-07-22 13:55:06 -07:00
zeekayandhanzo-dev d9fbc6af96 feat(projects): dedicated POST /v1/projects/:slug/purge + emit Cache-Tag; DRY the edge purge
- Add POST /v1/projects/:slug/purge (mirrored at /v1/platform/sites/:slug/purge):
  resolve (org,slug), flush the edge cache-tag site-<org>-<slug>, stamp
  LastPurgeAt, persist, return 200 Project. Never touches the S3 origin. Org-scoped
  exactly like deploy (403 no org, 404 unknown slug). CF-unconfigured/failing purge
  is non-fatal (stamps + 200), matching deploy's behavior.
- DRY: extract purgeTag (the ONE cf.PurgeTags + cache-tag derivation + failure
  policy) and purgeEdge (purge + stamp). deploy(onPublish), setDomains, del, and the
  new purge handler all route through purgeTag — no copy-pasted CF call.
- Cache-Tag on served responses already emitted in sites.streamSite (unchanged);
  tightened its comment + CacheTag doc to state the emit/purge pairing invariant.
- Scrub stale svc suffix from prose (6→0): projectsvc→projects, tasksvc→tasks,
  cloud-mlsvc comment reworded; zapsvc test fixture → zap. msvc (third-party) left.
- Enforce one vocabulary in touched comments (project / deployment / S3 origin /
  edge cache-tag / purge); no behavior change.
- Tests: purge_test.go — stamps LastPurgeAt, CF-unconfigured→200, 403/404 scope,
  S3 origin untouched.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-22 13:48:20 -07:00
hanzo-dev ebb773fe94 feat(integrations): ecommerce + AI-startup key connectors
One key-verify mechanism (keyVerify) plus the payment, model, messaging, and
SaaS connectors an online store or AI startup needs, on the user-scoped
/v1/connectors plane. Each provider is declarative data — origin, path,
credential placement, offline checks — over a single fail-closed, token-free
verify; a new connector is a registration, not another hand-rolled HTTP dance.

Providers: stripe, paypal, square, shopify; gemini, groq, mistral, cohere,
together, replicate, huggingface, openrouter, xai, fireworks, deepseek,
pinecone; sendgrid, resend, postmark, mailchimp, klaviyo, twilio; hubspot,
notion, linear, airtable.

A customer key seals to KMS only on a 2xx from the provider's cheapest
authenticated read; non-2xx and transport errors store nothing and never echo
the credential. authClient no longer follows redirects, so a 3xx fails closed
and custom credential headers are not forwarded across a hop.
2026-07-22 13:26:14 -07:00
hanzo-dev ee1435d146 merge(main): final catch-up before connectors ship 2026-07-22 09:07:13 -07:00
hanzo-dev 230058ed9b merge(main): catch up before shipping connectors 2026-07-22 08:42:21 -07:00
01c6fc407b build(deps): bump hanzoai/ai v1.829.7 → v1.830.0 (free-tier flash cap #143) (#351)
Pulls the free-tier auto-routing flash cap (ai#111): a CONFIDENT free-tier org's
`auto` is confined to the flash pool (blended-price ceiling), so a non-paying
caller is never routed to a premium model. Enso stays the default; paid/trial,
explicit model, and X-Max-Cost still win. Single-commit jump; cloud builds clean
against v1.830.0 (CGO_ENABLED=0).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-22 08:39:46 -07:00
zandGitHub 0c49314de2 sync: freshness reconcile scheduler + gitToken graceful fallback (git.hanzo.ai native cutover)
Periodic reconcile scheduler (clients/sync) that keeps every poll sync current (env-gated CLOUD_SYNC_RECONCILE_INTERVAL, leader-safe on the Recreate singleton writer, bounded by the shared reconcileSem), plus OrgStore.Each cross-org sweep primitive and store.ListAll. gitToken now falls back App-token -> GIT_MIRROR_TOKEN -> anonymous instead of hard-failing, so github reconciles (public immediately, private once GIT_MIRROR_TOKEN is set) stop freezing. Tests: scheduler_test, orgdb_test TestOrgStoreEach, git_provider_test TestGitTokenFallback; go vet ./... clean.
2026-07-22 03:52:39 -07:00
antje 320ff539c5 feat(commerce): expose SuperAdmin catalog CMS at /v1/catalog/* in the embed
admin.hanzo.ai's editor (console v8.4.154) CRUDs /v1/catalog/entries, but
commerce's setupRoutes wires only /v1/commerce/* — the /v1/catalog CMS
(api.Route -> catalogApi.AdminRoute, standalone-only) 404'd in the co-resident
binary. mountCommerce is the adapter for exactly these setupRoutes-skipped
families: mount catalogApi.AdminRoute on the existing /v1 bundle group (storeV1:
AddHost+RequestContext+errorScope+IAMTokenRequired — the same chain the
standalone /v1 bundle uses), and own /v1/catalog in commercePrefixes so it
reaches commerce, not the AI /v1/* balance catch-all.

No commerce module change: catalogApi.AdminRoute already ships in v1.49.9. Each
handler is requireSuperAdmin-gated (anon -> 401/403, cross-tenant data — never
org-scoped). Editor unchanged; closes the admin-edit half of the loop.
2026-07-22 03:30:36 -07:00
hanzo-dev 470e12644b deploy: bump embedded commerce v1.49.10 → v1.49.11 (billing-reads 502 class fix)
Picks up the #146 sibling fix: the co-resident billing READS (ListInvoices,
ListBillingSubscriptions, ListPayouts, GetPaymentConfig, DownloadInvoicePDF) no longer
nil-deref-panic (→502) on the embed path when no org is in Locals — they resolve the org
via nil-safe GetOrganizationOK. Compile-verified clean:
go build ./apps/... ./clients/account/... ./clients/commerceclient/...
2026-07-22 03:29:52 -07:00
hanzo-dev 296fe6261a deploy: bump embedded commerce v1.49.9 → v1.49.10 (spend-alerts 502 fix)
Picks up the #146 fix: GET /v1/billing/spend-alerts (the console Budgets page) no
longer panics (→ 502) on the co-resident embed path when no org is in Locals.
commerce ListSpendAlerts + its CRUD siblings + billingSubject now resolve the org
via the nil-safe GetOrganizationOK. Compile-verified clean:
go build ./apps/... ./clients/account/... ./clients/commerceclient/...
2026-07-22 03:09:37 -07:00
hanzo-dev 21626ec7b8 Merge remote-tracking branch 'origin/main' into consolidate/held-work 2026-07-22 03:03:17 -07:00
hanzo-dev f0d7dc07be merge(connectors): OAuth/apikey connector plane (anthropic, openai, copilot, device, refresh)
# Conflicts:
#	clients/integrations/integrations.go
2026-07-22 02:56:27 -07:00
antje 00b6293a65 deploy: bump embedded commerce v1.49.8 → v1.49.9
Increment-1 catalog SoT: commerce Bootstrap now seeds the 17 infra-tier
catalogentry rows (11 cloud + 3 gpu + 3 datastore) via runInfraCatalogSeed
(count-gated, idempotent, non-fatal) and projects an infra brand scope +
Metadata at GET /v1/commerce/catalog?brand=infra. Purely additive; billing/
orders/Stripe untouched.
2026-07-22 02:52:44 -07:00
hanzo-dev 3766f6ba0c merge(deps): commerce v1.49.3 bump + flags/metering test follow-through
# Conflicts:
#	go.mod
#	go.sum
#	hanzo.yml
2026-07-22 02:46:33 -07:00
antje 67f6111918 fix(team): run the entitlement/guest-cap gate at sendInvite too
The team.guests cap ran only at selectWorkspace (the guest's later login),
never at sendInvite — the actual guest add. A workspace admin could invite
guests past the plan cap and the add itself was ungated. Call the SAME
entitle seam at the add point, OBSERVE-MODE consistent with the login gate:
it logs the over-cap denial and admits today, and the 402 arms the day
enforcement returns. Commerce/plans errors admit inside entitle, so a
licensing outage never bricks an invite. Tests prove the gate runs at the
add point (commerce + plan cap consulted, genuine over-cap rank) yet admits,
and that an infra error still records the invite.
2026-07-22 01:53:55 -07:00
antje 9187dcdd6e fix(team/collab): close seedYLog TOCTOU — route the seed through the hub
createContent seeded a brand-new doc's live update log with a bare
Get(miss)-then-Put. In the gap between the miss and the Put, a concurrent
first edit on the live WS lane could land and then be overwritten by the
seed (lost update), or the seed could overwrite a log that just went live.
Seed THROUGH the collab hub (seedIfAbsent): it reuses the room's flushMu/mu,
so the empty-check and the set are atomic under the room lock and the seed
and the field's live editor serialize on ONE room. The seed applies only
when the log is still empty — never clobbers a live edit. Deterministic +
concurrent (-race) tests prove the live edit always survives.
2026-07-22 01:48:48 -07:00
antje 701c1f794a fix(team): converge concurrent logins to one personal workspace
EnsureWorkspace was check-then-insert (WorkspacesOf -> INSERT) with no
uniqueness on the personal-workspace identity, so two concurrent logins for
the same (org, account) could each see 'none' and mint a duplicate personal
workspace (reproduced: 32 concurrent logins -> 6 rows). Add a partial-unique
index on (owner_org, owner) — EnsureWorkspace is the sole creator and always
writes owner=account — with a dedup that converges any pre-existing duplicates
to the earliest row, and make the create an idempotent upsert (ON CONFLICT DO
NOTHING then adopt the winner). Concurrent EnsureWorkspace now yields exactly
one row. Heal logic extracted to adoptExisting, reused on both paths.
2026-07-22 01:44:56 -07:00
antje 87cc4db15e fix(team): surface a real seat-read error instead of a false 0 members
Seats swallowed the row Scan error, so a genuine DB failure reported (0, 0)
— indistinguishable from an org with no members, under-counting billed
seats. Propagate the error (the aggregate COUNT always returns one row, so
any Scan error is a real failure); the wallet's /billing/plan read now
502s honestly and retries instead of rendering a truthful-looking 0.
2026-07-22 01:40:23 -07:00
antje b8253bf75e fix(auth): console identity from the ONE validated principal, not casibase
DECOMPLECTION. The operator SPA (admin.hanzo.ai) authenticates via /v1/signin (a
cloud PKCE session → the X-User-* principal the gateway/middleware mints) but read
its IDENTITY from /v1/get-account, which the embedded IAM (casibase) answers from ITS
OWN session cookie. A PKCE session is not a casibase session, so get-account returned
owner:"hanzo" (anonymous) or "Unauthorized operation" — and the SPA SuperAdmin gate
(owner==admin && isAdmin), reading that, bounced the operator UI to login even though
the SAME session got 200 from every /v1/admin/* route. Identity source and auth source
disagreed: two session models for one surface.

Now identity IS the principal. AccountFromPrincipal (registered after IdentityMiddleware,
before MountAll's casibase mount) answers /v1/get-account from X-User-Owner/Name/Email/
IsAdmin when a VALIDATED principal is present (owner = HOME org, so a SuperAdmin
org-switched into a tenant stays one); with no principal it falls through to casibase
unchanged (anonymous sign-in + legacy casibase-session callers untouched). One truth,
additive, fail-open. Fixes the operator console UI being unusable via browser login.
2026-07-22 01:36:35 -07:00
antje 0bbbf3c358 fix(finance): never show held funds as spendable in the balance projection
The commerce S2S fallback set available = balance whenever the reported
available was 0, so a fully-held wallet (balance == holds, available 0)
rendered its entire balance as spendable — money the prepaid gate would
refuse. Derive available as balance NET OF holds when commerce reports only
a balance, clamped at 0 (holds beyond balance never go negative). Extracted
as spendableCents with a table test; a fully-held org proves the handler.
2026-07-22 01:36:03 -07:00
antje 01cd52930e fix(team): cap workspace-invite org grant at member — no org-admin escalation
A workspace invite passed the body role straight into the org-level IAM
grant, so a single-workspace admin could make an invitee an org IAM admin/
owner (trusted elsewhere via IsAdmin). Cap the org grant at member; the rich
role stays workspace-scoped on the local roster row. Test proves the cap.
2026-07-22 01:01:50 -07:00
antje 478f50760b fix(team/collab): close room-resurrection race (panic) + stop lost updates on flush
Two defects in the single-replica collab hub (collabws.go):

1) BLOCKING race → 'panic: close of closed channel' + registry corruption. join
   registered its peer in rm.peers AFTER releasing h.mu, so in that gap a concurrent
   leave of the last old peer would GC the room (delete h.rooms[key] + close(rm.stop),
   ending the flusher). The resurrected room then panicked on its next leave
   (close of an already-closed channel) and could evict a live room (split-brain).
   This is the ordinary 'reconnect by the sole editor' shape. Fix: register the peer
   while STILL holding h.mu, before the slow VFS load — a concurrent leave can no
   longer see the room as empty. Lock order stays h->rm. A failed first-open now
   undoes the join via leave() so it leaks neither the peer nor the room+flusher.

2) Silent lost updates on flush. flush cleared rm.dirty BEFORE the Put and discarded
   the Put error, so a transient VFS failure dropped the buffered window (dirty already
   false => neither the ticker nor last-leave retried). Fix: clear dirty only on a
   SUCCESSFUL Put, re-arm it on failure, and serialize the persist (flushMu) so two
   overlapping flushes cannot reorder their Puts.

TDD: TestCollabHubConcurrentJoinLeaveNoPanicNoLeak hammers join+leave on one doc from
500 goroutines under -race (reproduces the panic + a room leak without the fix, clean
with it). TestCollabFlushRetriesAfterPutError proves a failed Put keeps the room dirty
and nothing is persisted, then a later Put persists and clears dirty.
2026-07-22 00:53:51 -07:00
antje 26b2f13f8a fix(finance): surface a real balance-read error instead of rendering it as $0
ledgerFinance.Balance discarded store.Balance's error (bal, _ := ...), so a real
read failure — a DB Scan error or a corrupt/garbled stored-balance ParseInt failure —
returned (zero, nil), indistinguishable from a genuine zero. That defeated the
documented 'a balance that cannot be read is unknown, and unknown is not broke'
invariant every caller relies on: /v1/billing/balance and /v1/finance/balance showed
a FUNDED customer $0.00, and the AI prepaid gate (metering.fetchAvailable) refused a
funded org's request. Propagate the error; the callers' guards already render 503 on
a non-nil read error. Direction was already safe (zero only under-reports), so this is
correctness + observability, not an over-charge.

TDD: TestBalanceReadErrorSurfaces closes the store's DB out from under the cached
handle and asserts Balance now returns an error, not (0,nil). Fails before, passes after.
2026-07-22 00:53:51 -07:00
hanzo-dev 6dda723198 merge(main): bring the integration up to current main before shipping 2026-07-22 00:10:59 -07:00
hanzo-dev 47764c02a8 fix(cli/code): size Codex context window to the served model, not a flat 262144
The codexLike provider hardcoded '-c model_context_window=262144' (+auto_compact
235929) for EVERY model, so enso / zen5 — which the gateway serves at 1M
(ai flagshipWindow pin, live) — were capped at 256K in the 'hanzo code' Codex
wrapper. That surfaced to the user as 'maximum context exceeded' at 262144 even
after switching to zen5-pro.

Make the window model-aware: codeContextWindow(model) → 1M for the enso/zen5
flagship tiers, 131072 for flash; auto-compact at 90%. Threads the served model
into provider(base, model). Only codexLike sets provider (codex has no carrier,
so its model IS the served zen id). Tests updated + a sizing test added.
2026-07-21 23:58:19 -07:00
antje 20d0e9465d fix(analytics): stop /v1/analytics 500 — replace panicking sync.Map with mutex+map
The deprecated-alias 'log once per path' used a package sync.Map (Go's HashTrieMap),
which entered a 'ran out of hash bits while inserting' panic state under the hot
ingest path — so the Recover middleware turned EVERY POST /v1/analytics (and /batch,
/tracker) into a 500. Events stopped landing in hanzo.events once the map degraded.
The alias set is tiny (3 paths); swap the sync.Map for a mutex-guarded map — no trie
state to corrupt, cannot panic. Behavior unchanged (still logs each alias once).
go build ./... green.
2026-07-21 23:29:10 -07:00
antje 347b96171e fix(agents): retry + model-failover on transient upstream overload so bot replies stop dropping
The agent-run path made ONE completion call; when the default agent model
(deepseek-v4-flash) returned a transient upstream 429 'Platform overloaded'
(~1 in 3 under load), the run recorded an error and the bot reply was dropped.

- types: add ErrUpstreamBusy sentinel — the shared vocabulary for a transient,
  safely-retryable upstream failure (429/5xx/empty-choices/'overloaded').
- aihttp: classify + tag transient chat-completion failures with ErrUpstreamBusy
  (errors.Is-detectable); permanent errors (400/auth/unserved model) stay
  untagged and fail fast. Message preserved; no control-flow change for
  non-agent callers (interactive chat untouched).
- agents/executeRun: bounded retry (3 attempts, equal-jittered backoff, ctx-aware)
  on ErrUpstreamBusy, then ONE failover to the reliable model (CLOUD_AI_FALLBACK_MODEL,
  default 'best') if the agent's own model stays throttled. Retrying a completion
  is side-effect-free, so metering still debits EXACTLY once on the eventual
  success (runAgent meters only r.Status==ok) and never on failed attempts.
- Bill the model ACTUALLY used (r.Model) — a failover run bills 'best', not the
  throttled model it started on.
- Scoped to the autonomous agent/bot run path ONLY; interactive user-facing
  chat/completions behavior is unchanged.

TDD: 429-twice-then-200 -> one ok run + one debit; persistent 429 + failover
exhausted -> clean error run + no debit; failover-success bills the used model;
transient-classifier unit test (429/503/500/empty-choices busy, 400 not).
2026-07-21 23:17:25 -07:00
hanzo-dev d486e3f108 fix(sites): complete the coalesce+ceiling WIP — add sync/strconv imports + fixed-window takeToken() 2026-07-21 22:39:55 -07:00
hanzo-dev 57b673bfe0 merge(site-releases): consolidate onto main 2026-07-21 22:38:35 -07:00
hanzo-dev 007cccfd03 merge(channels): consolidate onto main
# Conflicts:
#	apps/apps.go
#	apps/wire_test.go
#	clients/channels/routes.go
2026-07-21 22:38:22 -07:00
hanzo-dev 318047fc59 merge(cloudflare-connector): consolidate onto main
# Conflicts:
#	clients/integrations/cloudflare.go
#	clients/integrations/cloudflare_test.go
#	clients/integrations/integrations.go
2026-07-21 22:37:57 -07:00
hanzo-dev 0177b19bbd merge(account-usage): consolidate onto main
# Conflicts:
#	clients/link/http.go
#	clients/link/store.go
2026-07-21 22:30:47 -07:00
hanzo-dev e7cb198c06 merge(link-router): consolidate onto main
# Conflicts:
#	clients/link/http.go
2026-07-21 22:30:05 -07:00
hanzo-dev 5d1da72b38 merge(leaderboard): consolidate onto main
# Conflicts:
#	apps/apps.go
2026-07-21 22:16:01 -07:00
hanzo-dev 65f7106436 merge(cd-projection-clusters-projects-stream): consolidate onto main
# Conflicts:
#	clients/deploy/dashboard.go
#	clients/deploy/dashboard_endpoints_test.go
#	clients/deploy/deploy_test.go
#	clients/deploy/projection.go
#	clients/deploy/stream.go
2026-07-21 22:12:33 -07:00
hanzo-dev 88d987c61e merge(admin-billing-credit): consolidate onto main 2026-07-21 22:09:28 -07:00
hanzo-dev 8390b5cab9 merge(admin-credit-grant): consolidate onto main
# Conflicts:
#	clients/admin/commerce/commerce.go
2026-07-21 22:09:12 -07:00
hanzo-dev 2eaa0f3df4 merge(analytics-capture-v2): consolidate onto main
# Conflicts:
#	clients/analytics/analytics.go
#	clients/analytics/capture.go
2026-07-21 22:07:28 -07:00
hanzo-dev b26389ad15 merge(zen-upstream-key-env-fallback): consolidate onto main
# Conflicts:
#	apps/zen.go
#	apps/zen_key_test.go
2026-07-21 22:03:03 -07:00
hanzo-dev d75a341f9f merge(agents-typed-ops): consolidate onto main 2026-07-21 21:55:48 -07:00
hanzo-dev fab042bbc5 feat(gpu): HANZO_STUDIO_VRAM env overrides studio vram mode
Default stays --normalvram (safe for small BYO GPUs); big-memory boxes (GB10
128G unified) can set HANZO_STUDIO_VRAM=--highvram so the render backend keeps
models GPU-resident. Additive + opt-in; other workers unchanged.
2026-07-21 21:44:51 -07:00
5e60fb5ab9 refactor(iam): drop Casdoor iam-v1 entirely — cloud embeds the clean hanzoai/iam (#349)
cloud's last tie to the retired Casdoor/Beego fork (hanzoai/iam-v1) is gone:

- clients/iam: embeds the clean hanzoai/iam (zip-native + hanzoai/orm) via
  iamserver.Mount over its own SQLite store; fail-closed 503 on boot failure.
  Removes the dual-impl identitySpec (CLOUD_IAM_IMPL=iam2 branch) + clients/iam2.
- clients/platform + clients/deploy: read the IAM-owned Project resource via
  iam/pkg/store over the embedded DB() instead of iam-v1's object-store ormer.
- cmd/hanzo: retires the `hanzo iam` Casdoor daemon subcommand.
- go.mod: the last transitive iam-v1 edge was hanzoai/ai/object; bump ai
  v1.829.3 -> v1.829.4 (Casdoor-free cut). go mod tidy drops iam-v1 entirely.

Remaining iam-v1 references are accurate "retired/gone" doc comments only.
Tests green: clients/iam, clients/platform, clients/deploy. Wire frozen-order
golden consistent (iam2->iam collapse).

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-21 20:19:11 -07:00
antje c2a9e8e6c6 fix(webui): serve each route's OWN exported shell — ends the OAuth login loop
The embedded console served index.html for EVERY non-asset path, so a deep
load of /auth/callback hydrated '/' instead; AuthGate discarded the ?code and
bounced to /signin — sign-in could never complete on the embedded console.
Now an extensionless path tries the static-export route shell (<route>.html)
first, with the index treatment (no-cache + white-label title rewrite, one
shared brandTitle); direct .html requests are also no-cache.
2026-07-21 19:40:14 -07:00
edd5f16375 chore(deps): bump hanzoai/ai → v1.829.7 (admin.* signin redeems as admin-console; admin-login P0) (#350)
Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-21 18:50:56 -07:00
hanzo-dev c593b50252 chore(deps): bump hanzoai/ai v1.829.5 → v1.829.6
Router-config routes (/v1/router/{policy,defaults,ledger,rewards,artifact-meta}
and /v1/org/settings) now serve over api.hanzo.ai. The v1.829.5 refactor moved them
to ZAP-native handlers and deleted their beego routes, but :8000 is the beego
web.Router — the ZAP registry backs a separate transport — so they 404'd in prod
(console Router->Policy, chat/app routing defaults). v1.829.6 adds RouterConfigBridge
(one beego adapter dispatching in-process through the SAME gateway registry, so the
ZAP handler stays the sole impl) and restores their isBalanceExempt entries.
2026-07-21 18:18:26 -07:00
hanzo-dev 3e2e1d84be merge: detect AMD GPUs in node inventory (evo gfx1151 was invisible) 2026-07-21 18:11:28 -07:00
hanzo-dev ec777cc40e link: detect AMD GPUs in the node inventory (rocm-smi / kfd topology / vulkaninfo)
detectGPUs now reports AMD accelerators as first-class resources alongside NVIDIA
and Apple Metal — discrete Radeon cards and gfx APUs alike (evo's gfx1151 Radeon
8060S on the RYZEN AI MAX+ 395). Resolution order: rocm-smi --showproductname (name
+ gfx target), then the kfd topology under /sys (GPU nodes by simd_count, gfx from
gfx_target_version), then a vulkaninfo summary; VRAM filled from amdgpu sysfs
mem_info_vram_total. Pure parsers are unit-tested against evo's real rocm-smi CSV
and kfd properties; the gfx_target_version decode (110501 → gfx1151) is covered.
2026-07-21 18:06:33 -07:00
hanzo-dev 1faadab30e merge: hanzo link|unlink|status — bring a machine into the fleet as a node
The unified Go binary is hanzo dev — the unified Hanzo Go binary

Usage:
  hanzo <command> [flags]

Control commands (gcloud/doctl-style):
  agent        invoke a managed Hanzo agent to run a task (headless)
  apps         list/get the platform apps board (declared/running/drift)
  auth         manage authentication + stored identities (login, logout, whoami, list, switch, token)
  bot          launch a computer-using agent (booted desktop or terminal)
  build        enqueue a platform-native build (runner fabric)
  clusters     provision/list/select dedicated DOKS clusters
  code         launch a coding agent (claude, codex, dev) on a Hanzo cloud model
  config       view/edit ~/.hanzo/config preferences
  deploy       drive a platform redeploy (rolling restart, zero-downtime)
  engine       run a local hanzo-engine (OpenAI + Anthropic model server)
  k8s          deploy-target helpers (current target)
  link         bring this machine into the Hanzo cloud fleet as a node (fabric + compute worker)
  login        authenticate against Hanzo IAM (hanzo.id) and store a token
  logout       remove stored credentials
  run          launch a workload on Hanzo compute (container or function)
  runner       run this machine as a JIT CI runner for your org (GitHub Actions)
  security     scan files for hardcoded secrets (local guardrail; no server/auth)
  status       show the org's fleet — every node with each of its GPUs
  unlink       take this machine out of the fleet (deregister + stop hanzod)
  whoami       show the current identity from the stored token

Service subcommands (server mode):
  account      serve the account subsystem standalone
  account-bridge serve the account-bridge subsystem standalone
  admin        serve the admin subsystem standalone
  admission    serve the admission subsystem standalone
  ads          serve the ads subsystem standalone
  affiliates   serve the affiliates subsystem standalone
  agent        serve the agent subsystem standalone
  agents       serve the agents subsystem standalone
  agentskills  serve the agentskills subsystem standalone
  ai           serve the ai subsystem standalone
  analytics    serve the analytics subsystem standalone
  audit        serve the audit subsystem standalone
  authors      serve the authors subsystem standalone
  authz        serve the authz subsystem standalone
  automations  serve the automations subsystem standalone
  base         serve the base subsystem standalone
  billing      serve the billing subsystem standalone
  bots         serve the bots subsystem standalone
  captable     serve the captable subsystem standalone
  catalogsync  serve the catalogsync subsystem standalone
  channels     serve the channels subsystem standalone
  cloud        serve the full unified surface (all enabled subsystems, one listener)
  cloudflare   serve the cloudflare subsystem standalone
  code         serve the code subsystem standalone
  commerce     serve the commerce subsystem standalone
  company      serve the company subsystem standalone
  content      serve the content subsystem standalone
  crm          serve the crm subsystem standalone
  dataroom     serve the dataroom subsystem standalone
  datastore    datastore-fork analytics DB — not a Go serve target (see help text)
  deploy       serve the deploy subsystem standalone
  dns          serve the dns subsystem standalone
  do           serve the do subsystem standalone
  domain       serve the domain subsystem standalone
  entitlements serve the entitlements subsystem standalone
  evals        serve the evals subsystem standalone
  exec         serve the exec subsystem standalone
  flags        serve the flags subsystem standalone
  framework    serve the framework subsystem standalone
  functions    serve the functions subsystem standalone
  gateway      serve the gateway subsystem standalone
  git          serve the git subsystem standalone
  graph        serve the graph subsystem standalone
  guide        serve the guide subsystem standalone
  iam          serve standalone Hanzo IAM (full Beego server: login UI, OAuth2/OIDC, LDAP/RADIUS)
  ingress      serve the ingress subsystem standalone
  integrations serve the integrations subsystem standalone
  kafka        serve the kafka subsystem standalone
  kms          serve the kms subsystem standalone
  knowledge    serve the knowledge subsystem standalone
  licensing    serve the licensing subsystem standalone
  link         serve the link subsystem standalone
  marketing    serve the marketing subsystem standalone
  marketplace  serve the marketplace subsystem standalone
  metrics      serve the metrics subsystem standalone
  ml           serve the ml subsystem standalone
  notify       serve the notify subsystem standalone
  o11y         serve the o11y subsystem standalone
  paas         serve the paas subsystem standalone
  plan         serve the plan subsystem standalone
  platform     serve the platform subsystem standalone
  plugins      serve the plugins subsystem standalone
  pricing      serve the pricing subsystem standalone
  product      serve the product subsystem standalone
  projects     serve the projects subsystem standalone
  prompts      serve the prompts subsystem standalone
  provisioning serve the provisioning subsystem standalone
  pubsub       serve the pubsub subsystem standalone
  referrals    serve the referrals subsystem standalone
  rollingcap   serve the rollingcap subsystem standalone
  runtime      serve the runtime subsystem standalone
  sbom         serve the sbom subsystem standalone
  security     serve the security subsystem standalone
  settings     serve the settings subsystem standalone
  sign         serve the sign subsystem standalone
  social       serve the social subsystem standalone
  storage      serve the storage subsystem standalone
  sync         serve the sync subsystem standalone
  tasks        serve the tasks subsystem standalone
  team         serve the team subsystem standalone
  templates    serve the templates subsystem standalone
  tools        serve the tools subsystem standalone
  tracker      serve the tracker subsystem standalone
  treasury     serve the treasury subsystem standalone
  usage        serve the usage subsystem standalone
  validators   serve the validators subsystem standalone
  visor        serve the visor subsystem standalone
  wallets      serve the wallets subsystem standalone
  websearch    serve the websearch subsystem standalone
  world        serve the world subsystem standalone
  x402         serve the x402 subsystem standalone
  zen          serve the zen subsystem standalone
  zero-trust   serve the zero-trust subsystem standalone

Meta:
  help         show this message
  version      print version and exit

Flags are per-subcommand (e.g. `hanzo cloud --enable=iam,kms --brand=hanzo`,
`hanzo kms --listen=:8443`). Run a subcommand to see its config via env/flags. (HIP-0106): link composes fabric join (hanzo dev — the unified Hanzo Go binary

Usage:
  hanzo <command> [flags]

Control commands (gcloud/doctl-style):
  agent        invoke a managed Hanzo agent to run a task (headless)
  apps         list/get the platform apps board (declared/running/drift)
  auth         manage authentication + stored identities (login, logout, whoami, list, switch, token)
  bot          launch a computer-using agent (booted desktop or terminal)
  build        enqueue a platform-native build (runner fabric)
  clusters     provision/list/select dedicated DOKS clusters
  code         launch a coding agent (claude, codex, dev) on a Hanzo cloud model
  config       view/edit ~/.hanzo/config preferences
  deploy       drive a platform redeploy (rolling restart, zero-downtime)
  engine       run a local hanzo-engine (OpenAI + Anthropic model server)
  k8s          deploy-target helpers (current target)
  link         bring this machine into the Hanzo cloud fleet as a node (fabric + compute worker)
  login        authenticate against Hanzo IAM (hanzo.id) and store a token
  logout       remove stored credentials
  run          launch a workload on Hanzo compute (container or function)
  runner       run this machine as a JIT CI runner for your org (GitHub Actions)
  security     scan files for hardcoded secrets (local guardrail; no server/auth)
  status       show the org's fleet — every node with each of its GPUs
  unlink       take this machine out of the fleet (deregister + stop hanzod)
  whoami       show the current identity from the stored token

Service subcommands (server mode):
  account      serve the account subsystem standalone
  account-bridge serve the account-bridge subsystem standalone
  admin        serve the admin subsystem standalone
  admission    serve the admission subsystem standalone
  ads          serve the ads subsystem standalone
  affiliates   serve the affiliates subsystem standalone
  agent        serve the agent subsystem standalone
  agents       serve the agents subsystem standalone
  agentskills  serve the agentskills subsystem standalone
  ai           serve the ai subsystem standalone
  analytics    serve the analytics subsystem standalone
  audit        serve the audit subsystem standalone
  authors      serve the authors subsystem standalone
  authz        serve the authz subsystem standalone
  automations  serve the automations subsystem standalone
  base         serve the base subsystem standalone
  billing      serve the billing subsystem standalone
  bots         serve the bots subsystem standalone
  captable     serve the captable subsystem standalone
  catalogsync  serve the catalogsync subsystem standalone
  channels     serve the channels subsystem standalone
  cloud        serve the full unified surface (all enabled subsystems, one listener)
  cloudflare   serve the cloudflare subsystem standalone
  code         serve the code subsystem standalone
  commerce     serve the commerce subsystem standalone
  company      serve the company subsystem standalone
  content      serve the content subsystem standalone
  crm          serve the crm subsystem standalone
  dataroom     serve the dataroom subsystem standalone
  datastore    datastore-fork analytics DB — not a Go serve target (see help text)
  deploy       serve the deploy subsystem standalone
  dns          serve the dns subsystem standalone
  do           serve the do subsystem standalone
  domain       serve the domain subsystem standalone
  entitlements serve the entitlements subsystem standalone
  evals        serve the evals subsystem standalone
  exec         serve the exec subsystem standalone
  flags        serve the flags subsystem standalone
  framework    serve the framework subsystem standalone
  functions    serve the functions subsystem standalone
  gateway      serve the gateway subsystem standalone
  git          serve the git subsystem standalone
  graph        serve the graph subsystem standalone
  guide        serve the guide subsystem standalone
  iam          serve standalone Hanzo IAM (full Beego server: login UI, OAuth2/OIDC, LDAP/RADIUS)
  ingress      serve the ingress subsystem standalone
  integrations serve the integrations subsystem standalone
  kafka        serve the kafka subsystem standalone
  kms          serve the kms subsystem standalone
  knowledge    serve the knowledge subsystem standalone
  licensing    serve the licensing subsystem standalone
  link         serve the link subsystem standalone
  marketing    serve the marketing subsystem standalone
  marketplace  serve the marketplace subsystem standalone
  metrics      serve the metrics subsystem standalone
  ml           serve the ml subsystem standalone
  notify       serve the notify subsystem standalone
  o11y         serve the o11y subsystem standalone
  paas         serve the paas subsystem standalone
  plan         serve the plan subsystem standalone
  platform     serve the platform subsystem standalone
  plugins      serve the plugins subsystem standalone
  pricing      serve the pricing subsystem standalone
  product      serve the product subsystem standalone
  projects     serve the projects subsystem standalone
  prompts      serve the prompts subsystem standalone
  provisioning serve the provisioning subsystem standalone
  pubsub       serve the pubsub subsystem standalone
  referrals    serve the referrals subsystem standalone
  rollingcap   serve the rollingcap subsystem standalone
  runtime      serve the runtime subsystem standalone
  sbom         serve the sbom subsystem standalone
  security     serve the security subsystem standalone
  settings     serve the settings subsystem standalone
  sign         serve the sign subsystem standalone
  social       serve the social subsystem standalone
  storage      serve the storage subsystem standalone
  sync         serve the sync subsystem standalone
  tasks        serve the tasks subsystem standalone
  team         serve the team subsystem standalone
  templates    serve the templates subsystem standalone
  tools        serve the tools subsystem standalone
  tracker      serve the tracker subsystem standalone
  treasury     serve the treasury subsystem standalone
  usage        serve the usage subsystem standalone
  validators   serve the validators subsystem standalone
  visor        serve the visor subsystem standalone
  wallets      serve the wallets subsystem standalone
  websearch    serve the websearch subsystem standalone
  world        serve the world subsystem standalone
  x402         serve the x402 subsystem standalone
  zen          serve the zen subsystem standalone
  zero-trust   serve the zero-trust subsystem standalone

Meta:
  help         show this message
  version      print version and exit

Flags are per-subcommand (e.g. `hanzo cloud --enable=iam,kms --brand=hanzo`,
`hanzo kms --listen=:8443`). Run a subcommand to see its config via env/flags., delegated to the Rust CLI installed as hanzo code claude · /home/z/work/hanzo/cloud · start
  model routing: on → api.hanzo.ai (prompts + code go here; usage metered to your org)
  session stream: on → https://hanzo.bot/sessions/sess_4729b3a0a623c55d0d3b7b08fe8ebe35
resume: hanzo --resume 4729b3a0a623c55d0d3b7b08fe8ebe35) with compute-worker
registration (CPU cores+model, memory, each GPU), heartbeats, claims gpu-jobs.
unlink is idempotent; status renders the fleet with each GPU distinct. hanzo dev — the unified Hanzo Go binary

Usage:
  hanzo <command> [flags]

Control commands (gcloud/doctl-style):
  agent        invoke a managed Hanzo agent to run a task (headless)
  apps         list/get the platform apps board (declared/running/drift)
  auth         manage authentication + stored identities (login, logout, whoami, list, switch, token)
  bot          launch a computer-using agent (booted desktop or terminal)
  build        enqueue a platform-native build (runner fabric)
  clusters     provision/list/select dedicated DOKS clusters
  code         launch a coding agent (claude, codex, dev) on a Hanzo cloud model
  config       view/edit ~/.hanzo/config preferences
  deploy       drive a platform redeploy (rolling restart, zero-downtime)
  engine       run a local hanzo-engine (OpenAI + Anthropic model server)
  k8s          deploy-target helpers (current target)
  link         bring this machine into the Hanzo cloud fleet as a node (fabric + compute worker)
  login        authenticate against Hanzo IAM (hanzo.id) and store a token
  logout       remove stored credentials
  run          launch a workload on Hanzo compute (container or function)
  runner       run this machine as a JIT CI runner for your org (GitHub Actions)
  security     scan files for hardcoded secrets (local guardrail; no server/auth)
  status       show the org's fleet — every node with each of its GPUs
  unlink       take this machine out of the fleet (deregister + stop hanzod)
  whoami       show the current identity from the stored token

Service subcommands (server mode):
  account      serve the account subsystem standalone
  account-bridge serve the account-bridge subsystem standalone
  admin        serve the admin subsystem standalone
  admission    serve the admission subsystem standalone
  ads          serve the ads subsystem standalone
  affiliates   serve the affiliates subsystem standalone
  agent        serve the agent subsystem standalone
  agents       serve the agents subsystem standalone
  agentskills  serve the agentskills subsystem standalone
  ai           serve the ai subsystem standalone
  analytics    serve the analytics subsystem standalone
  audit        serve the audit subsystem standalone
  authors      serve the authors subsystem standalone
  authz        serve the authz subsystem standalone
  automations  serve the automations subsystem standalone
  base         serve the base subsystem standalone
  billing      serve the billing subsystem standalone
  bots         serve the bots subsystem standalone
  captable     serve the captable subsystem standalone
  catalogsync  serve the catalogsync subsystem standalone
  channels     serve the channels subsystem standalone
  cloud        serve the full unified surface (all enabled subsystems, one listener)
  cloudflare   serve the cloudflare subsystem standalone
  code         serve the code subsystem standalone
  commerce     serve the commerce subsystem standalone
  company      serve the company subsystem standalone
  content      serve the content subsystem standalone
  crm          serve the crm subsystem standalone
  dataroom     serve the dataroom subsystem standalone
  datastore    datastore-fork analytics DB — not a Go serve target (see help text)
  deploy       serve the deploy subsystem standalone
  dns          serve the dns subsystem standalone
  do           serve the do subsystem standalone
  domain       serve the domain subsystem standalone
  entitlements serve the entitlements subsystem standalone
  evals        serve the evals subsystem standalone
  exec         serve the exec subsystem standalone
  flags        serve the flags subsystem standalone
  framework    serve the framework subsystem standalone
  functions    serve the functions subsystem standalone
  gateway      serve the gateway subsystem standalone
  git          serve the git subsystem standalone
  graph        serve the graph subsystem standalone
  guide        serve the guide subsystem standalone
  iam          serve standalone Hanzo IAM (full Beego server: login UI, OAuth2/OIDC, LDAP/RADIUS)
  ingress      serve the ingress subsystem standalone
  integrations serve the integrations subsystem standalone
  kafka        serve the kafka subsystem standalone
  kms          serve the kms subsystem standalone
  knowledge    serve the knowledge subsystem standalone
  licensing    serve the licensing subsystem standalone
  link         serve the link subsystem standalone
  marketing    serve the marketing subsystem standalone
  marketplace  serve the marketplace subsystem standalone
  metrics      serve the metrics subsystem standalone
  ml           serve the ml subsystem standalone
  notify       serve the notify subsystem standalone
  o11y         serve the o11y subsystem standalone
  paas         serve the paas subsystem standalone
  plan         serve the plan subsystem standalone
  platform     serve the platform subsystem standalone
  plugins      serve the plugins subsystem standalone
  pricing      serve the pricing subsystem standalone
  product      serve the product subsystem standalone
  projects     serve the projects subsystem standalone
  prompts      serve the prompts subsystem standalone
  provisioning serve the provisioning subsystem standalone
  pubsub       serve the pubsub subsystem standalone
  referrals    serve the referrals subsystem standalone
  rollingcap   serve the rollingcap subsystem standalone
  runtime      serve the runtime subsystem standalone
  sbom         serve the sbom subsystem standalone
  security     serve the security subsystem standalone
  settings     serve the settings subsystem standalone
  sign         serve the sign subsystem standalone
  social       serve the social subsystem standalone
  storage      serve the storage subsystem standalone
  sync         serve the sync subsystem standalone
  tasks        serve the tasks subsystem standalone
  team         serve the team subsystem standalone
  templates    serve the templates subsystem standalone
  tools        serve the tools subsystem standalone
  tracker      serve the tracker subsystem standalone
  treasury     serve the treasury subsystem standalone
  usage        serve the usage subsystem standalone
  validators   serve the validators subsystem standalone
  visor        serve the visor subsystem standalone
  wallets      serve the wallets subsystem standalone
  websearch    serve the websearch subsystem standalone
  world        serve the world subsystem standalone
  x402         serve the x402 subsystem standalone
  zen          serve the zen subsystem standalone
  zero-trust   serve the zero-trust subsystem standalone

Meta:
  help         show this message
  version      print version and exit

Flags are per-subcommand (e.g. `hanzo cloud --enable=iam,kms --brand=hanzo`,
`hanzo kms --listen=:8443`). Run a subcommand to see its config via env/flags. is a
superset — non-Go verbs pass through to hanzo-node so nothing breaks.
2026-07-21 17:56:10 -07:00
hanzo-dev 0a24aa76e3 link: hanzo is a superset — delegate non-Go verbs to the Rust CLI (hanzo-node)
The Go unified binary takes the `hanzo` name (HIP-0106). fabricCLI now resolves the
Rust fabric/dev CLI as `hanzo-node` (then a self-guarded `hanzo`), and cmd/hanzo
delegates any verb that is neither a Go control verb nor a served subsystem —
node, dev, wallet, network, … — to it via cli.Passthrough. So one `hanzo` name
serves both: link/unlink/status + the whole Go surface native, and `hanzo node up`
(the fabric that link composes) plus the Rust dev verbs handed through unchanged.
2026-07-21 17:22:39 -07:00
hanzo-dev 6dfd242fba Merge remote-tracking branch 'origin/main' into feat/hanzo-link 2026-07-21 17:22:26 -07:00
hanzo-dev c696d1a4e5 Merge remote-tracking branch 'origin/main' into feat/hanzo-link
# Conflicts:
#	cli/gpu.go
2026-07-21 16:58:53 -07:00
hanzo-dev 42c98780a8 link: RED-review fixes — unlink idempotency + comment sweep
unlink is now idempotent: runDisconnect treats an already-terminal (409) or absent
(404) fleet row as the desired end state (no-op with a clear notice), and unlink
runs stopFabric unconditionally so a deregister error never leaves hanzod running —
the deregister error is reported, not short-circuited. Tests cover the 409/404
idempotent path and the 500 error-surfacing path.

Sweeps the remaining `gpu connect` prose in comments to `link` (engine, runner,
visor fleet/board/visor, and the gpu/fleet spec + engine test headers).
2026-07-21 16:56:58 -07:00
hanzo-dev c591636a8b chore(deps): bump hanzoai/ai v1.829.3 → v1.829.5 (RESTful ZAP-native router routes; beego split-brain killed) 2026-07-21 16:54:53 -07:00
antje e380d0737c fix(team): heal the authenticating caller's own member row (real Seats:0 fix)
The live wallet Seats:0 for maxpower was NOT the orgs claim (Dave's claim already
lists maxpower/admin). Dave OWNS a maxpower workspace, but a team-go migration left
his own member row is_bot=1/active=0, so Seats (which filters active=1 AND is_bot=0)
excluded him while getUserWorkspaces still listed the workspace (no flag filter).
EnsureWorkspace early-returned on the existing workspace without ever correcting
the row, so every re-login kept 0.

A user who just authenticated through IAM is by definition an active, non-bot member
of their own workspace: EnsureWorkspace now forces the caller's OWN row (never
anyone else's) to active=1/is_bot=0 on the existing-workspace path. Idempotent.
TestEnsureWorkspaceHealsMigratedMember reproduces Dave's exact shape red→green.
2026-07-21 16:26:18 -07:00
antje 47e39d78b7 fix(team): home org always ensured a seat; createContent seeds the ydoc log
Two live hanzo.team defects:

1) Wallet Seats:0 for the caller's own org. orgsClaim dropped the HOME org (the
   org the wallet, Seats, and every account-store surface scope to via extra.org)
   whenever the IAM orgs claim was non-empty but did not itself list home — the
   fallback only fired for an EMPTY claim. So establishSession never ensured a
   home-org workspace, and Seats(home) returned 0 for an org that has the caller
   as a member. Home is now unconditionally in the set, so its workspace (hence a
   seat) is ensured at every login. Reproduced in TestOrgsClaimAlwaysIncludesHome.

2) New-Issue dialog description dropped on create. createContent stored only the
   markup SNAPSHOT blob; the collaborative editor replays the Y.js update log the
   WS lane serves (ydoc-<id>-<field>), a different blob, so the description showed
   empty. createContent now also seeds that log from the front-supplied Y.js
   update (never clobbering an existing/live log; scoped to createContent).
   TestCollabCreateContentSeedsYLog covers it.
2026-07-21 16:05:22 -07:00
hanzo-dev d43479712b link: hanzo link|unlink|status — bring a machine into the fleet as a node
link composes the two node memberships under one verb: it starts hanzod via the
canonical `hanzo node up` (best-effort; --no-fabric skips it) and runs the
compute-worker loop that registers this host's CPU (cores + model), memory, and
each GPU as its own resource, then heartbeats and claims jobs from the org queue.
unlink deregisters the node and stops hanzod; status renders the fleet with each
GPU shown distinctly and this box highlighted. Works on a CPU-only node.

Replaces the gpu connect|status|disconnect surface (one way, no alias). Adds a
CPU model field to the advertised inventory — CLI registration and the visor
fleet record in lockstep. The worker machinery (register/heartbeat/claim, studio,
engine advertise) is unchanged; only the command layer and inventory grow.
2026-07-21 16:02:16 -07:00
antje 92910c173d fix(admin): commerce cost god-view uses the in-process transport (fixes commerce.inproc DNS fail)
The admin cockpit's commerce reader (/v1/admin/finance COGS, /v1/admin/usage,
costs) built a PLAIN http.Client but its base is commerceinproc.BaseURL() — which
returns the 'http://commerce.inproc' placeholder when commerce is co-resident. A
plain client DNS-resolves that host → 'lookup commerce.inproc: no such host', so
the admin finance/cost god-view silently errored ('commerce unreachable'). Swap to
commerceinproc.Client() — the self-routing transport metering already uses:
in-process dispatch for the placeholder host, plain HTTP for a split-deploy URL.
Only this admin client hit it (the others use real env URLs).
2026-07-21 15:52:30 -07:00
antje 65b45b1aa7 feat(billing): default rolling-cap fallback — protect pay-as-you-go too
The per-tier rolling cap only governed SEEDED subscription tiers (free/pro/…).
Pay-as-you-go / empty / unknown tiers fell through to uncapped — a burst-spend
hole for the entire non-subscription user base (every current org is
pay-as-you-go). Add ai_rolling_cap_cents_default: when a caller's tier has no
specific cap, the reader falls back to it, so EVERY caller gets a rolling ceiling
once set. Default 0 = opt-in (no behavior change until an admin sets it in the
cockpit); tier-specific caps still win. Fail-open on tier/sum error unchanged.
Test covers the fallback (pay-as-you-go over default → deny; tier-specific beats
default; empty+no-default still admits).
2026-07-21 15:23:02 -07:00
hanzo-dev fb8d30dc14 test(apps): refreeze wire golden — add validators (91st subsystem)
A parallel merge (feat(validators): NFT-gated node provisioning) added the
validators subsystem to Wire() at position 45 (after ads) without updating the
frozen golden, so TestWireOrderMatchesFrozen fails 91 vs 90 — the failing test
behind main's red CI once the go.sum compile error is fixed. Refroze to match
Wire() order + flags (ownsHealth=false, hasShutdown=true).
2026-07-21 15:17:23 -07:00
hanzo-dev 56d1036c52 fix(deps): go mod tidy — complete go.sum, unblock main CI
Main CI/CD has been red for 8+ commits: go.sum was missing transitive
entries (mongo-driver/bson via golang-set, btcd/chainhash/v2 via btcec,
hanzos3/go-sdk via zapdb, go-json-experiment/json + luxfi/filesystem via
luxfi/node) so go vet/test/build all fail before any test runs. A parallel
dep bump landed without tidy. Pure require-list + go.sum reconcile; versions
unchanged (luxfi/node stays v1.36.15).
2026-07-21 14:52:15 -07:00
zeekayandhanzo-dev 79ebb519e9 fix(validators): register /v1/validators collection root flat (avoid trailing-slash 404)
Group("/v1/validators").Post("") registers "/v1/validators/", which the
portal's bare POST /v1/validators would miss. Register the list+provision
collection root via app.Get/app.Post like clients/wallets et al.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-21 14:24:55 -07:00
43a8099d36 feat(fleet): per-GPU render queue — targeted lanes, visibility, cancel, usage (#346)
* test(apps): refreeze wire golden — add rollingcap subsystem

Wire() mounts 90 subsystems but the frozen sequence listed 89: the rollingcap
gate (mounted after billing) was added to Wire() without refreezing the golden,
so TestWireOrderMatchesFrozen has been red on main. Add the missing entry at its
Wire() position — the same maintenance the earlier dns+cloudflare refreeze did.
Pre-existing drift, unrelated to the per-GPU queue work; folded in so cloud CI's
go-unit gate (which runs ./apps/) is green again.

* feat(fleet): per-GPU render queue — targeted lanes, visibility, cancel, usage

Make all BYO-GPU render work flow through the org's gpu-jobs queue, visible and
manageable per GPU, and close the hidden direct-submit hole.

cli/gpu.go
- Two-lane claim: the worker claims its OWN lane ("gpu:<identity>") FIRST, then
  the shared "gpu-jobs" lane — targeting is the taskQueue VALUE within the one
  gpu-jobs namespace, so a job pinned to spark is never starved and no worker
  steals another GPU's targeted job.
- Render submit moves from the open POST /prompt to the gated
  POST /v1/worker/execute with X-Worker-Token (KMS STUDIO_WORKER_TOKEN).
- Worker reports live GPU utilization (nvidia-smi) each heartbeat via
  POST /v1/fleet/samples.

cli/studio.go
- Launch the local ComfyUI with --listen 127.0.0.1 --worker-mode (was 0.0.0.0,
  unauthenticated) — the worker dials loopback, so binding wider only exposed an
  open /prompt; worker-mode gates the submit seam.

clients/visor
- GET /v1/fleet/jobs?gpu=&status= — the org's queue, each row tagged with the
  GPU it targets (''=shared lane) + the claiming worker; ?gpu=X matches target OR
  claimant; status normalized to queued|running|completed|failed|canceled; the
  full ComfyUI graph is omitted (cheap SaveImage label instead).
- POST /v1/fleet/jobs/:id/cancel {run,reason} — org-scoped cancel via the tasks
  CancelActivityForOrg wrapper (tasks v1.51.2).
- POST /v1/fleet/samples — BYO util ingest into the existing samples warehouse
  the board already overlays; fleetUnit gains Queued/Running per-GPU depth.

Reuses ActivitiesForOrg (one engine, one tenant key), fail-soft by source.
TDD: claim precedence, gpuTarget, status normalize, filter, per-node counts,
sample build, route tenancy — ./cli/ + ./clients/visor/ added to the CI go-unit
gate so they run every push.

* fix(gpu): detach + bound the util sampler so a hung nvidia-smi can't wedge the worker

sampleGPUs shelled nvidia-smi with no timeout and reportSample ran SYNCHRONOUSLY in
the worker's select loop (heartbeat tick + render-progress tick). Under GPU/driver
pressure nvidia-smi can hang, blocking the whole loop → no heartbeats, no claims →
the machine flaps offline and stops rendering mid-run.

- sampleGPUs takes a ctx and runs the probe via exec.CommandContext under a 5s cap
  (self-cancels instead of hanging); the probe is an injectable package var.
- reportSample detaches probe+POST onto its own goroutine under a 20s budget and
  returns immediately, so the select loop is never blocked. At most one report in
  flight per ticker site (interval >> budget); self-cancels on worker shutdown.

Test: a hung sampler (blocks until its bounded ctx fires) — reportSample still
returns to the caller at once, proving claim/heartbeat can't wedge (-race clean).

* fix(fleet): adversarial batch — pagination, render preflight, filter/stall/token hardening

F1 (MAJOR): the queue + fleet reads no longer truncate at 100 rows. gpuJobs and
byoWorkers cursor-walk the org's namespace to completion via the new paginated
tasks read (ActivitiesPageForOrg, tasks v1.51.3); gpuJobs then recency-sorts and
bounds terminal history (all live jobs kept + last 50 terminal). Past ~100 lifetime
renders a busy org no longer hides live jobs or drops online workers.

F2 (MAJOR): worker render preflight. A node advertises studioCap + claims render
lanes ONLY when it can serve — STUDIO_WORKER_TOKEN present AND a studio reachable
(or launched via --studio-dir). Otherwise it heartbeats as present but claims
nothing (no poison loop of 403→FAILED→reclaim), with a loud one-time operator
warning. Re-evaluated each heartbeat so a studio dying/recovering flips claiming.

F3: ?gpu= filter is case-insensitive (node ids are lower-case).
F4: a running job past its lease surfaces as 'stalled' (worker died, not yet reaped)
    instead of 'running' forever.
F5: every loopback studio call (execute/history/view/upload/queue) sends
    X-Worker-Token, robust to the worker-mode gate widening scope.
F7: corrected the '/prompt' → '/v1/worker/execute' error string.

Tests: >100-row ordering/bound + stall + case-insensitive filter + cancel err→HTTP
(404/409) mapping; terminal complete/fail hit the exact ns+wf+run path (catches a
routing regression a 200-everything stub would miss); SharePolicy.reject fallback;
not-ready node claims nothing; studioCap gating. tasks v1.51.3 adds
ActivitiesPageForOrg with a >100 pagination test.

---------

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-21 14:13:55 -07:00
antje 22f261f02b security: reserve stg slug — close shared-client redirect takeover vector
The shared hanzo-app OAuth client trusts https://stg.hanzo.app/callback, but `stg` was not a reserved subdomain — an attacker could first-come-claim stg.hanzo.app, run authorize(client_id=hanzo-app, redirect=stg.hanzo.app/callback) (IAM exact-matches), and harvest a logged-in user code minted with aud=hanzo-app that api.hanzo.ai trusts → account takeover. stg.hanzo.app is 404/unbound today, so reserving closes it safely.

Adds `stg` to sites.baseReserved + reserved-superset test (reserved ⊇ {www,stg}) + storage-layer BindHost(stg)-rejected test. Cherry-picked ONLY the isolated clients/sites files from 5ac8f89; the larger per-app IAM client changes (appauth.go/projects.go/iam) stay OUT of main pending red re-review.

Verified: go build ./... ok; CGO=0 go test ./clients/sites/... ok; BindHost(stg)→errReservedHost, stg does not resolve.
2026-07-21 13:48:33 -07:00
zeekayandhanzo-dev a9258b54e9 feat(validators): POST /v1/validators — NFT-gated node provisioning + owner-gated registration
Phase-1 of GDA/SDM validator onboarding on lux.cloud. New /v1/validators/*
subsystem: a caller proves wallet control (EIP-191 personal_sign challenge,
address recovered server-side) AND on-chain ownership of a Validator-tier
GenesisNFT on Ethereum mainnet (ownerOf against 0x31e0F919C67ceDd2Bc3E294340Dc900735810311,
reusing the luxfi/geth read path), then the endpoint:
  - generates a luxd staking identity (TLS+BLS+ML-DSA-65 -> strict-PQ NodeID)
    via luxfi/node/staking — byte-identical to genesis/cmd/venuekeygen — and
    SEALS it into KMS (never plaintext; fail-closed);
  - persists the org -> tokenId -> slot entitlement (per-org SQLite);
  - writes a NEW-node LuxNetwork CR (group node.lux.cloud, ns lux-validators)
    + KMSSecret sync — three hard guards make it structurally incapable of
    touching the live hand-managed luxd StatefulSets;
  - ENQUEUES an owner-gated registration (pending_owner_approval, NEVER
    auto-submitted to any P-Chain).

Adds github.com/luxfi/node v1.36.15 (requires cloud's exact pinned
crypto/ids/geth — zero version skew). 13 tests pass incl. a live ETH-mainnet
ownerOf read; go vet clean.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-21 13:38:14 -07:00
hanzo-dev 8278466fc0 cap+router RED fixes: spend-cap writes require org-admin + bump ai v1.829.3 / commerce v1.49.8
- F2-1: gate the co-resident spend-alert CRUD WRITES (POST/PATCH/DELETE) to an ORG ADMIN
  / SuperAdmin / trusted S2S token (requireSpendCapAdmin) — commerce's user group admitted
  any authenticated member, so a compromised member key could DELETE the org's cap
  (unbounded spend) or POST a 1c enforce cap (org-wide 402 DoS). Reads (list/authorize)
  stay member/S2S-open. Exports accountclient.IsServiceToken for the gate.
- bump github.com/hanzoai/ai v1.829.0 → v1.829.3 (router allowlist HARD floor + no
  unowned-OrgSettings clobber across all writers: beego/ZAP/trainer/generic-setter).
- bump github.com/hanzoai/commerce v1.49.7 → v1.49.8 (spend-cap fails OPEN on unknown
  spend, not closed — no 402-storm on a finance-read blip).
2026-07-21 12:53:44 -07:00
b7f0e069b2 sync: repoint the git provider from Gitea to the native /v1/git plane (#347)
The universal sync engine's git provider drove an EXTERNAL Gitea store
(giteaFromEnv → gitea.mirrorIn / ensurePushMirror). Repoint it to the native git
object-plane seams already registered by clients/git at Mount, so the ONE git
store IS the in-binary /v1/git plane and no byte transits an external git host:

  - inbound (source push)  → cloud.InboundGitSync  (fast-forward-only advance;
                             a diverged native ref is a Conflict, native preserved)
  - reconcile pull/both    → cloud.ImportGitRepo   (ff mirror every branch in;
                             MirrorURL=source registers the native→source push-back)
  - reconcile push-only    → cloud.EnsureGitMirror (declare the outbound target;
                             the native mirror_out lifecycle does the pushing)

sync_api.reconcileOutboundMirror likewise moves onto cloud.EnsureGitMirror — the
ONE outbound-target registrar — so a sync's mirror target is never split across
two stores. gitea.go + gitea_test.go (the entire external-Gitea client) are now
dead and removed: forwards-only, no dead code, DRY.

This also FIXES the provider being inert in prod: giteaFromEnv fails closed
without GITEA_TOKEN/URL (unset on cloud), so no git sync could reconcile; the
native seams are in-process and need no external config. resolve() (the pure
decision core) is unchanged — TestGitResolve green; build + vet clean. The
KMS-gated store tests (TestSyncValidation) fail identically on origin/main
(CLOUD_KMS_MASTER_KEY_REF test-env requirement), orthogonal to this change.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-21 11:51:59 -07:00
5f5aa1b876 git: serve native git UI at git.hanzo.ai root (host-routed, GitHub-style URLs) (#345)
The native /v1/git UI (ui.go) was reachable only under /git/* on every host, so
git.hanzo.ai/ and git.hanzo.ai/<org>/<repo> fell through to the console SPA
catch-all (webui.go app.All("/*")) — the console shadowed the git host root.

Extend the existing onGitHost host-routing (already guarding the root smart-HTTP
/:org/:repo/* clone paths) to the UI: register the SAME handlers at the root
("/", "/:org/:repo", tree/blob/commits) gated to the git host. On api/console
they fall through (c.Next()) to the console catch-all, so a bare /:org/:repo
never shadows it there; on git.hanzo.ai they serve the native browser.

URLs are now canonical per host — one and only one way: base "" on the git host
(git.hanzo.ai/<org>/<repo>, matching the clone URL) and "/git" where the console
embeds the browser. Thread that base through render/templates/href-builders; the
UI clone box shows the clean git-host form (git.hanzo.ai/<org>/<repo>.git).

Non-destructive: additive routes behind a host guard; smart-HTTP clone routing
(distinct /info/refs|/git-*-pack tail) and console/api hosts are unchanged.
TestRootUI_HostGuard covers git-host serve + api-host fall-through.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-21 11:44:11 -07:00
hanzo-dev 68c40c86e7 chore(deps): bump github.com/hanzoai/ai v1.829.0 → v1.829.2 (per-org router config surface)
Picks up the per-org enabled-models allowlist + savings-vs-quality dial: OrgSettings
RouterEnabledModels/RouterQualityBias, the /v1/get-router-policy + /v1/update-router-policy
carry them (GET also returns the servable-model catalog), and resolveAutoModel enforces
the allowlist (both heuristic + engine paths) and the dial (cost-budget narrow + SLO
tighten). Opt-in: an org that sets neither routes exactly as before.
2026-07-21 11:40:42 -07:00
hanzo-dev 4bfc5ecec6 docs(projects/CONTRACT): converge the two site planes into one — static crs/ retires into Projects
Decision + per-site migration runbook: every first-party static site (cd/flow/
gallery/yadota) becomes a Project served by the ONE host-router (clients/sites),
bundle moved to the canonical <bucket>/<org>/<slug> layout (no external-prefix
special case — resolver keeps one code path). <slug>.hanzo.ai becomes a bound host
routed through cloud, mirroring the *.hanzo.app wildcard edge. Steps 1-2 additive
(no live-routing change); the cutover (route *.hanzo.ai via cloud, delete the
staticFiles Middleware+IngressRoute) is a reviewed per-host flip, cd.hanzo.ai LAST.
End state: static-sites.yaml holds zero first-party sites — one router, one S3
layout, one store; sites sourced from hanzo-apps.
2026-07-21 10:59:00 -07:00
6c95c5ec99 refactor(iam): drop cloud's DIRECT iam-v1 dep — use the clean v2 iam OrgRef (#344)
'iam-v1 is dead; use the new clean iam for all things.' cloud imported the dead
Casdoor fork github.com/hanzoai/iam-v1 in 6 files for exactly ONE type: OrgRef
{Org,Role} (a JWT-claim membership ref). The v2 clean-room iam (github.com/
hanzoai/iam) now EXPORTS it at pkg/model.OrgRef (= schema.OrgRef, byte-identical
JSON) as of v1.32.1. Repoint all 6 (auth_identity, token_validator,
clients/team/{invite,account}, + 2 tests) to model.OrgRef and bump iam→v1.32.1.

cloud's own code now has ZERO direct iam-v1 imports. iam-v1 remains ONLY as a
TRANSITIVE dep via hanzoai/ai/object, which still couples to the full Casdoor
IAM API (Claims/GetUser/GetOrganization/MFA…) — a major separate migration
(ai's domain), not an OrgRef swap. Builds clean; model.OrgRef resolves.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-21 10:55:54 -07:00
hanzo-dev 0863e74a4e cap: mount spend-alerts CRUD writes co-resident — customers could not set a cap
The GET list + GET /authorize are served co-resident, but POST/PATCH/DELETE
/v1/billing/spend-alerts were NOT — so a customer creating/editing/removing a usage
cap fell through the account bridge's /v1/billing/* wildcard (billingForwardable
includes POST spend-alerts), forwarded to COMMERCE_URL (= this binary), and
self-dispatched into the SAME 502 loop authorize hit. Net: self-service cap
management was impossible in the unified binary (every write 502'd).

Register CreateSpendAlert / UpdateSpendAlert / DeleteSpendAlert co-resident with the
exact chain commerce's own route table gates them (api/billing/handlers.go:322-325,
user group userRequired = TokenRequired) + the global RequestContext: an IAM JWT OR
the COMMERCE_SERVICE_TOKEN, org from the gateway-pinned X-Org-Id. Org-scoped by
namespace (a caller writes only their OWN org's caps; a foreign :id misses in their
namespace), so no PinBillingSubject — spend-alerts are org-level. Specific routes
shadow the bridge wildcard (order 100 < 122). Completes the self-service cap CRUD:
list + authorize (already co-resident) + create/edit/delete (this).
2026-07-21 10:00:45 -07:00
79f9ce256c feat(agents): seed the built-in crew @dev @des @vi on org first-touch (re-land) (#342)
Re-land of the crew seed (a parallel force-push to cloud main dropped it).
personalities.go: dev/des/vi personas + idempotent SeedPersonalities(ctx,org)
(one registry, UNIQUE(org,name); no-op without a model). account.go OAuth
callback seeds per-org after EnsureWorkspace (best-effort, never blocks login).
Native TestSeedPersonalities green. TEAM_AGENTS_ENABLED=1 already live +
AIDefaultModel=deepseek-v4-flash → the crew materializes and answers @-mentions.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-21 09:51:39 -07:00
zeekayandhanzo-dev e4ed9b1760 feat(agents): seed the built-in crew — @dev @des @vi — on org first-touch
The named personas from the old hanzo.ai site, brought into Hanzo Team as
ordinary rows in the ONE agents registry: nothing special-cased downstream —
they list, project into the Team roster as bot members (bots.go), and answer
@-mentions through the SAME agents.RunOnBehalf path every agent uses.

- clients/agents/personalities.go: the canonical crew (dev=builder, des=designer,
  vi=visionary) + SeedPersonalities(ctx, org) — idempotent via the registry's
  UNIQUE(org,name); no-ops without a default model (never a half-seeded org) or
  an unmounted subsystem (safe to call best-effort on the login path).
- clients/team/account.go: the OAuth callback seeds the crew per-org right after
  EnsureWorkspace — a new org gets its default office AND its default crew
  together. Best-effort: a seed hiccup NEVER blocks login.

Native test green: TestSeedPersonalities — creates the crew, ListForOrg returns
the @dev/@des/@vi handles with model+prompt, re-seed is a 0-create no-op (no
dup), no-model is a clean no-op. To make them TALK, the Chunter responder flips
on with TEAM_AGENTS_ENABLED=1 (the deploy env) — the pipeline is already built.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-21 09:46:22 -07:00
hanzo-dev f559c34a91 fix(commerce): serve spend-alerts/authorize co-resident, breaking the 502 self-dispatch loop
The request-edge metering gate (clients/metering scopeAuthorize) reads the per-scope
spend-cap verdict at GET /v1/billing/spend-alerts/authorize over commerceinproc. With no
co-resident handler it fell through to the account bridge's /v1/billing/* wildcard, which
re-forwarded it to COMMERCE_URL (the public api.hanzo.ai edge = this binary) BY PATH through
the same transport, re-entering the wildcard until the depth-8 guard refused -> 502. The live
pod logged ~135x/30m of this (org "maxpower"). The cap is a policy overlay so the gate FAILS
OPEN (outer status 200, no traffic blocked), but every authorize call burned 8 full-app
dispatches and the spend cap never actually evaluated (always fail-open) — a silent policy hole.

Register commerce's own AuthorizeSpendCap co-resident in mountCommerce (order 100, ahead of the
bridge at 122) so the specific route shadows the wildcard and the gate hits the real handler at
depth 1 — the same co-resident move already made for plans/spend-alerts/invoices/etc. Service-
token chain (RequestContext + TokenRequired), mirroring commerce's OWN gate on this route, not
the IAM/PinBillingSubject console chain (a service token is not an IAM JWT, so IAMTokenRequired
would leave GetOrganization unset and AuthorizeSpendCap would 500).

Regression test in clients/commerceinproc/selfdispatch_test.go pins both arrangements: without
the specific route the wildcard self-loops to the depth-8 refusal (the prod 502 signature); with
it the handler serves once at depth 1 and the wildcard never fires.
2026-07-21 09:41:12 -07:00
hanzo-dev 6c7bb25e46 feat(deploy): project static-plane SITES into the fleet list — CD dashboard shows ALL
GET /v1/deploy/applications listed only App CRs (the ~72 pod-backed services), so
every static-plane SITE — cd.hanzo.ai itself, flow, gallery, yadota, … — was
invisible on the CD dashboard. A site has no App CR / Deployment: it is a
`staticFiles` Middleware (S3 origin `s3://cdn/<slug>`) + an IngressRoute (its host),
served straight from S3 with zero pods.

clients/deploy/sites.go: listSiteApplications enumerates the staticFiles Middlewares
per namespace and joins each to its IngressRoute host, projecting one Application row
per site with Role:"site", Repository=the S3 origin, Endpoints=[https://<host>], and
— since a static site is served from exactly its declared prefix — always Synced
(Version==RunningVersion=="static"). Health = routed (Healthy) vs defined-but-unrouted
(Missing). Best-effort (mirrors runningVersions): a missing-CRD/RBAC list error logs
and yields nothing, so the services half of the board always renders.

deploy.go: middlewaresGVR + ingressRoutesGVR (hanzo.ai/v1alpha1). applications.go:
fold site rows into the per-namespace scan + the summary. deploy_test.go:
TestListSiteApplications (a staticFiles Middleware + IngressRoute → one role:"site"
row; an unrouted Middleware → Missing, no endpoints).

Aligns with "delivery is the cloud deploy engine": the CD dashboard now renders the
WHOLE delivery surface — every service AND every site.
2026-07-21 09:40:12 -07:00
zeekayandhanzo-dev 32902f69ec fix(deps): bump hanzoai/ai → v1.829.0 (iam-v1 repoint) so cloud graph drops old iam root
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-21 09:39:14 -07:00
zeekayandhanzo-dev 6ed1e45ae6 refactor(iam): unify on hanzoai/iam@v1.32.0 (former iam2) + retire fork as iam-v1
Clean-room rewrite is now github.com/hanzoai/iam@v1.32.0 (continues the version line
so MVS selects it over the fork's v1.31.x); cloud embeds it via server.Mount. The
fork's object/iamserver/root usages repoint to github.com/hanzoai/iam-v1@v1.31.37.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-21 09:30:35 -07:00
antje 1d0c2f274f fix(ai): split completions (M2M) from embeddings (pk-) credential — stop bot replies 403ing on the read-only publishable key
deps.AI (chat completions, a WRITE endpoint: agents/guide/crm/content/
sitegen/code-ask) and deps.Embed (embeddings, READ-ONLY: code-index + KB)
were ONE shared client authenticated by CLOUD_AI_API_KEY — a read-only
publishable (pk-) key from secret cloud-ai-embed-key. The gateway 403s a
pk- key on any write endpoint ('Publishable keys can only access read-only
endpoints ... use a secret key'), so bot replies intermittently failed.

Split the credential by concern:
- pickCompletionsClient (deps.AI) REFUSES any pk- key (publishableKey guard)
  and authenticates with the binary's IAM M2M identity (IAM_CLIENT_ID/SECRET,
  already deployed) — the durable no-static-key path. A secret sk-/hk- static
  key is still honored as an operator override.
- pickEmbedClient (deps.Embed) keeps the pk- key UNCHANGED (correct
  least-privilege for a read-only call); falls back to the M2M resolution when
  no static embed key is set.

Metering unchanged: both clients wrap the ONE meteredAIClient path. No CR/KMS
change needed — the M2M identity is already in the cloud CR.

Tests (pick_test.go): completions refuse pk- and present the M2M bearer;
completions honor an sk- key; pk--only + no M2M fails closed (never sends the
pk- key to the write endpoint); embeddings present the pk- key; embed falls
back to M2M with no key; BuildDeps splits both credentials end to end.
2026-07-21 09:06:13 -07:00
antje 62d83460ce team(wallet): seats count every verified org + honest Free plan display
- establishSession EnsureWorkspace's the FULL verified membership set, not just
  the home org, so a non-home org's wallet counts the caller as a seat instead
  of "0 Members in your org". The multi-org lane unioned getUserWorkspaces across
  every org but left the seat/member projection seeded only for the home org; one
  membership set now drives the token, the workspace union, AND the seat count.
- wallet page: an empty commerce plan renders "Free" + an Upgrade CTA (the login
  gate admits a no-subscription org on the effective Free tier) instead of a bare
  "—" that read as a data failure. Never fabricates a tier.
- wallet header reflows at narrow widths: the Top up button holds its intrinsic
  size (flexShrink 0) under a wrapping row, so it stays whole at 390px instead of
  clipping to "Top".
- test: Seats counts distinct active non-bot members (owner + guest; bot and
  inactive excluded; tenant-scoped).
2026-07-21 09:01:09 -07:00
antje e265ccc78e analytics: publishable-key direct ingest (pk_) — fastest capture path, no Kafka hop
Adds a write-only publishable key and a direct-to-ClickHouse ingest ALONGSIDE
the existing /v1/event + Kafka-tier pipeline (nothing removed).

- pk_<b64url(org)>.<b64url(hmac)> — org sealed under HMAC-SHA256(CLOUD_INGEST_KEY_SECRET,
  org). Ingest-only BY CONSTRUCTION: the pk_ underscore prefix is outside
  isAPIKey's set, so SanitizeIdentity/OrgForKey refuse it — it can never become a
  bearer principal, so it can never read. Verify is one HMAC compute (no IAM/DB
  hop) — the lowest-latency path. Fails closed when the secret is unset.
- POST /v1/ingest — {batch:[WireEvent]} authed by pk_, org stamped from the SIGNED
  key (never the body), funneled through the ONE write core (ingestEvents) into
  hanzo.events, tagged source=ingest.
- POST /v1/ingest/keys — an org owner (validated principal) mints a pk_ for its
  OWN org.
- GET /v1/errors — type:'error' read lens (validated principal; reads never accept
  the write-only key). error is now first-class in canonicalType/resolveEventName
  ('error'/$error); the WireEvent error object folds into properties.$exception.

Tests: mint↔verify round trip, fail-closed matrix (forged org, wrong secret,
malformed), exception folding, canonicalType.
2026-07-20 23:45:24 -07:00
antje c37d4ba5b6 build(deps): @hanzo/plans v1.4.3 → v1.4.4 (goja bundle NAMESPACES synced)
Picks up the sites.*/base.* namespace grouping in the embedded plans bundle so
/v1/plans/vocab matches the canonical entitlements vocabulary. Subscription caps
(ai.rolling_cap_usd/_window_hours, sites/base included) already flowed via the raw
__PLANS_DATA__ injection; this closes the last display-path drift.
2026-07-20 23:25:44 -07:00
hanzo-dev 9feef2acf5 fix(billing): serve the console's billing READS co-resident, breaking the 502 self-dispatch loop
commerce's api.Route() billing bundle is never compiled into the cloud binary, so
GET /v1/billing/{invoices,subscriptions,spend-alerts,payouts,payment-config} had no
handler here and fell through to the account bridge's /v1/billing/* wildcard. The
bridge forwards to COMMERCE_URL, which defaults to the public api.hanzo.ai edge —
i.e. THIS binary — re-entering the same bridge in an unbounded self-dispatch loop
that surfaces as a 502. In prod there is no separate commerce backend to point
COMMERCE_URL at (the in-cluster commerce Service selects the cloud pods), so
co-residence is the only way to break the loop.

Register commerce's own read handlers on the shared app (order 100, shadowing the
bridge wildcard at 122), behind RequestContext + IAMTokenRequired (org namespace from
the gateway-validated X-Org-Id) + a new PinBillingSubject middleware that carries the
SAME subject-pinning the bridge applies (reusing resolveCaller/scopedBillingSearch/
account.Payer) so a co-resident read can never widen past the caller and an
unvalidated caller is refused before the handler runs. This is the same co-resident
move already made for plans/usage/balance.

Bump the embedded hanzoai/commerce dep to v1.49.7 (catalog SOT + public/admin catalog API).
2026-07-20 18:35:25 -07:00
hanzo-dev cc09ef7c76 merge: serve GET /v1/billing/plans in-process (break the 502 self-dispatch loop) 2026-07-20 17:54:00 -07:00
hanzo-dev 1e5924fd20 fix(commerce): serve GET /v1/billing/plans in-process, breaking the 502 self-dispatch loop
commerce's legacy api.Route() billing bundle (ListPlans, invoices, subscriptions)
is NOT registered by the co-resident embed — setupRoutes wires only /v1/commerce/*
— so /v1/billing/plans had no handler in the cloud binary. The account bridge's
/v1/billing/* wildcard (order 122) then forwarded the read back to commerce at
COMMERCE_URL, which defaults to the public api.hanzo.ai edge, re-entering the same
bridge in an unbounded self-dispatch loop that surfaced as
'commerce unreachable: Get https://api.hanzo.ai/v1/billing/plans' -> 502.

Register commerce's static ListPlans on the shared app in mountCommerce (order 100,
ahead of the bridge) so the specific route shadows the wildcard and plans serve
in-process — the same co-resident move billing.go already makes for usage/balance.
2026-07-20 17:31:49 -07:00
antje 4be228e223 team: collab room flusher — burst-then-idle edits persist on the debounce clock
append() only flushed when the NEXT append found the debounce due, so a
typing burst followed by idle sat dirty in memory until the last peer
left. The per-room flusher ticks the same debounce; GC closes it.
2026-07-20 17:12:55 -07:00
hanzo-devandantje d204d99620 build(deps): commerce v1.49.6 — RED residual fixes (dunning, re-subscribe, books integrity) 2026-07-20 17:12:33 -07:00
antje 07c47cb585 team: collab WS keepalive — server pings keep throttled tabs off the 1006 path
Backgrounded tabs throttle the provider's awareness renewals; without
server pings the idle read deadline fires an abrupt close the provider
surfaces as 1006 — the 'cannot connect to collaboration service' banner.
The browser's network stack auto-pongs even when throttled; each pong
extends the read deadline.
2026-07-20 17:09:33 -07:00
antje 2aa440dba0 team: live collaborative editing — hocuspocus WS lane at /collaborator
The front's @hocuspocus/provider (2.15) speaks its protocol at the bare
/collaborator path with the doc id IN-BAND, which no ingress rewrite can
bridge to the collab relay's /v1/collab/<id> mux — so the live lane joins
the snapshot RPC lane in clients/team: collabws.go serves the hocuspocus
wire (Auth in-band with the SAME HS256 session token + workspace pin +
membership gate as collab.go, SyncStep1 -> replay + empty-diff Step2 +
server Step1, SyncStatus acks, awareness echo keepalive) over zip/wsx,
persisting the Y.js update log per doc on deps.VFS under the tenant-scoped
blob key. The server never parses update payloads: Y.js updates are
commutative + idempotent, so log replay converges; a lone peer's
full-state SyncStep2 (the reply to the server's empty-SV Step1) replaces
the log — compaction without a server-side CRDT. Rooms are in-process
(cloud pins replicas=1, single writer).
2026-07-20 17:07:35 -07:00
antje ea3b885bf0 team: Slack-model multi-org — orgs claim → workspace union + explicit select + invite
Bumps iam to v1.31.34 and carries the verified `orgs` membership-set claim end
to end, so a user's team workspaces union across every org they belong to.

- cloud.VerifiedIdentity gains Orgs []iam.OrgRef, copied from the verified
  claims (idClaims parses the signed `orgs`); empty on legacy tokens.
- establishSession folds the full membership set into the session token
  (extra.orgs), fallback [{owner, admin}] for a legacy token; extra.user carries
  the IAM id for a mid-session refresh. Still fails closed on empty owner. The
  short workspace token (rides the transactor URL) stays minimal (extra.org only).
- getUserWorkspaces unions WorkspacesOf across every session org, each
  WorkspaceInfo tagged with its owning org for the client switcher.
- selectWorkspace resolves an EXPLICIT (org∈session, slug) — clean BadRequest on
  absent, WorkspaceAmbiguous on a slug in two orgs, never a silent default.
  getWorkspaceInfo resolves the token's workspace claim, killing the wss[0]
  default the same way. Single-workspace fast path unchanged (front selects by
  URL). Cross-tenant isolation preserved (every lookup owner_org-scoped).
- Invite plane (clients/team/invite.go): sendInvite resolves the invitee in IAM
  (get-user), POSTs add-membership as the confidential hanzo-team app
  (client_secret_basic, CapMembershipAdmin), and writes the local member row;
  owner/admin only. getMemberships is the mid-session refresh (live get-memberships,
  session-set fallback). AddMember upserts the roster row idempotently.

Tests: table tests for the orgs round-trip (+legacy fallback), the workspace
union, cross-org select, no-default/ambiguous refusals, getWorkspaceInfo
no-default, guest-cap unaffected, invite writes membership+row (mock IAM) +
admin gate, refresh live/fallback, and VerifiedIdentity.Orgs claim flow.
2026-07-20 16:48:25 -07:00
antje 4ce57f4686 team: collaborator RPC plane + chat notify-context projection
The Team front was losing two core lanes against the native backend:

- Issue/doc rich-text creation dead-ended: the front's collaborator-client
  POSTs createContent/updateContent/getContent to /collaborator/rpc/:documentId,
  which only had the Y.js WS relay behind it — every RPC 404'd, so
  createMarkup threw and tracker issues/documents could not be created.
  collab.go now serves that contract on deps.VFS (same tenant-scoped blob
  keys as files.go): snapshots at makeCollabJsonId ids, membership-gated,
  no-oracle 404s. Ingress path-splits /collaborator/rpc → cloud (universe).

- Channels/DMs vanished from the chat navigator on reload: the nav lists
  notification:class:DocNotifyContext per {user} (upstream server triggers
  materialize them; we never did). seed.go's trigger now projects contexts
  from chunter Channel/DirectMessage membership — create on member add,
  remove on leave, lastUpdateTimestamp bump per message (heals pre-existing
  channels on first message) — and mirrors every write as a derived tx that
  tx() broadcasts so live sessions refresh.

Tests: collab RPC round-trip + tenancy red bars; channel→context projection
(create/touch/leave). chat_test's local clChannel const moved to seed.go.
2026-07-20 16:18:33 -07:00
antje 413b41f310 build(deps): plans v1.4.3 — team-max/enterprise license the team product 2026-07-20 16:04:57 -07:00
antje 9153932095 team: native login — IAM password RPC, provider_hint federation, platform severities
The hanzo.team login page goes native: the SPA form now authenticates
straight against Hanzo IAM (there are no local accounts) and the social
buttons land directly in the provider OAuth flow.

- account RPC "login": server-side IAM password grant — the SAME two-step
  the platform e2e auth helper locks (POST /v1/iam/login responseType=code,
  then the confidential code exchange) — followed by the EXACT session
  establishment the OAuth callback runs (now ONE shared establishSession:
  userinfo → verified owner claim → workspace ensure → HS256 token). The
  password rides only in the body of the one IAM login call, is never
  logged or persisted, and bad credentials answer a clean 401 with the
  platform status the form already translates.
- /auth/google and /auth/github: same authorize hop as /auth/openid (the
  one registered callback) carrying provider_hint=provider-google/github,
  so hanzo.id auto-federates straight into the provider (console-proven,
  id >= 0.2.6); explicit ?provider_hint= passes through verbatim.
- /providers now surfaces Google + GitHub + Hanzo so the SPA renders the
  three buttons with zero client wire changes.
- Status.Severity is the platform's STRING enum ("ERROR"), not an int the
  SPA compares against nothing — error styling and retry now behave.

Tests: password login mints a verifying session (mock IAM), bad creds 401
with no password in logs or response, provider_hint mapping, providers
surface. TestPersistenceCRUD remains the known pre-existing host red.
2026-07-20 16:04:12 -07:00
antje d98bcfc1dc build(deps): commerce v1.49.5 — card-on-file self-serve subscribe 2026-07-20 16:03:47 -07:00
antje afae891bee feat(billing): wire the rolling-window AI-spend cap (admin-configurable)
Installs the ai gate's per-tier rolling AI-spend cap — the Anthropic-style burst
limit that resets continuously (usage older than the window drops out of the
trailing sum; no reset job). Composes three co-resident globals and owns no state:

  aiobject.TierReader()  — the caller's commerce plan tier
  finance.Current()      — the ledger's windowed usage sum (SumUsageSince)
  flags.Int(key)         — the admin-editable per-tier caps

The two knobs (window hours + per-tier cap cents) are platform switches, so
admin.hanzo.ai renders and edits them LIVE via the existing /v1/admin/flags
cockpit — zero bespoke admin UI. Seed defaults mirror @hanzo/plans subscription.json
(developer $0.75 / pro $2.50 / plus $12 / max $25 per 3h window).

- clients/rollingcap: the new subsystem (own package — it imports clients/flags,
  which imports root cloud, so the wiring lives above that edge). Registers the
  switches (init) + installs the reader (Mount, no routes). FAILS OPEN on any
  tier/finance error — a commerce blip must never 429 a paying caller.
- types.FinanceClient: expose SumUsageSince (the trailing-window source) on the
  interface (was only on the concrete ledger); billing/marketing test mocks updated.
- apps.go: mount rollingcap after commerce/plan (its globals are wired by then).
- go.mod: hanzoai/ai v1.827.1 → v1.828.1 (the SetRollingCapReader hook).

Inert until deployed on the unified binary; the hook is nil elsewhere. Tests cover
the decision table (over/under-cap, window-off, unknown/uncapped tier, fail-open on
tier+sum errors) + Mount no-op when globals unwired + seed coverage.
2026-07-20 15:53:17 -07:00
antje f6c18f82a0 fix(team): entitle gate observes, never blocks — the 402 bricked all logins
No org has subscription rows yet and no self-serve checkout exists, so the
definitive-no 402 on selectWorkspace locked every user out (live 2026-07-20,
front rendered it as NoLoaderForStrings). Log the denial, admit, and bring
enforcement back with the card-on-file subscribe path.
2026-07-20 15:09:40 -07:00
zeekayandhanzo-dev 8a846ead55 build: force GOWORK=off so cloud builds standalone, not via the parent go.work
Root cause of the "broken module graph" (make test / go build ./... failing with
oxy invalid-version, ugorji/koanf ambiguous imports, k8s.io/kubernetes staging
referencing removed API groups): `~/work/hanzo/go.work` auto-shadows this tree but
does NOT list ./cloud. In that workspace mode Go drops cloud's own go.mod
directives — the oxy replace, the ugorji monolith exclude, and the k8s.io/*
staging pins — so the graph that those directives keep consistent falls apart.
cloud is a standalone deploy unit (own go.mod/Dockerfile/binary) and must not join
that workspace (merging its k8s/otel tree with o11y's reintroduces the koanf split
ambiguity; the parent workspace is independently red on koanf).

Fix: the Makefile forces GOWORK=off for all go targets — exactly how CI and the
Dockerfile build (fresh checkout, no parent go.work). No go.mod change was needed;
the existing directives are correct for module mode. A committed go.work was
rejected: it would flip the Dockerfile into workspace mode after its -mod=readonly
`go mod download` step.

Proof (GOWORK=off, == what make now runs): `go build ./...` exit 0, `go vet ./...`
exit 0, `go mod tidy` stable (no go.mod change). `make build` exit 0. `go test
./...` runs (was fully blocked before): 128 ok / 103 no-test / 10 fail, every
failure runtime not module-graph — encrypted-OrgDB tests that need CGO+libsqlcipher
(the Dockerfile's -tags libsqlite3 stage), a bundle-embed test needing make
deploy-ui, and pre-existing behavior tests (metering/zt/o11y). See LLM.md.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-20 14:59:19 -07:00
antje 3ad9b14fba build(deps): commerce v1.49.4 — per-seat billing release 2026-07-20 13:55:46 -07:00
antje dbe8227442 team: usage/wallet page — @hanzo/ui@8 static embed at /v1/team/billing/ui/ + org-scoped plan read
- clients/team/wallet: small Vite/React page on @hanzo/ui@8 (balance
  three-bucket split, current-period usage, plan + seats, top-up link to
  billing.hanzo.ai), mobile-first monochrome; committed dist go:embed'd
  (the console/tasks one-binary precedent).
- clients/team/billing.go: session-gated serve of the embed + GET
  /v1/team/billing/plan (seats/guests from the org's member rows, plan +
  team.guests cap through the same commerce/plans seams entitle uses);
  orgPrincipal is the ONE token→tenant resolution (files plane rebased on it).
- money reads stay on cloud's own /v1/billing/balance + /v1/usage/summary:
  the hanzo_iam_token cookie the team callback sets is now a validated
  principal (aud hanzo-team appended to defaultJWTAudiences, forwards-only),
  so the org is pinned server-side from the verified claim — no second
  auth mechanism.
- tests: billing 401 unauth (through real Mount), embedded shell + bundle
  served authed, plan org-scoped across two tenants, audience pin.
2026-07-20 13:48:15 -07:00
zeekayandhanzo-dev 10a143b9a0 refactor(routes): group clients/team under app.Group("/v1/team")
Finishes the one convertible subsystem the group sweep skipped: team's routes
were spread across 5 register funcs whose receiver was named `g` (colliding
with the group var). Resolved by passing the group as a zip.Router param
(register(r zip.Router, ...)) instead of *zip.App — one `tg := app.Group(
"/v1/team")` in Mount, threaded to acct/bridge/files.register + the two inline
transactor routes, all rewritten to relative paths. (Note *zip.App does NOT
satisfy zip.Router — App.Fiber() returns *fiber.App vs the interface's
fiber.Router — so the two test harnesses now pass app.Group("/v1/team") too.)

Route table preserved (13 team routes byte-identical); team test suite green
(exercises the real /v1/team/* paths end-to-end); combined build +
TestWireOrderMatchesFrozen pass. deploy stays flat by design — it already DRYs
via const dashPrefix and its loginPath/callbackPath vars are reused for
redirects (scope.go), so grouping would risk redirect paths for no real gain.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-20 13:12:48 -07:00
antje 6338b892e4 refactor(cloud): drop svc from stale comment prose (finish the suffix cleanup)
Follow-up to de05be1d: the doc comments still named packages by their old
svc-suffix (iamsvc.Mount, pricingsvc, provisioningsvc, mlsvc, evalsvc, plansvc,
productsvc, syncsvc, gatewaysvc) — stale references to symbols that are now bare.
Corrected to the real names across config/middleware_identity/eval/gateway/git/
ml/pricing/projects. Comment-only; no code change.

Deliberately kept: cloud-mlsvc at clients/ml/ml.go (a real ClusterRoleBinding
name in ml-rbac.yaml, correctly referenced) and the "zapsvc" test-fixture repo
strings (test data, not an identifier).

Also gofmt'd clients/pricing/admin_http_test.go (pre-existing import-order drift).
2026-07-20 13:01:31 -07:00
antje d6a65e1a97 harden(team): bounded tokens, verified tenant, WS origin gate, OAuth state, billing gate
- token: every session token carries exp (30d; workspace 12h); Decode enforces
  exp/nbf with 60s skew; pre-rollout no-exp tokens honored until a fixed
  legacy cutoff (constant, no env). The "secret" fallback literal is GONE —
  empty secret is a hard ErrNoSecret and the TEAM_DEV_INSECURE hatch is dead.
- account: OAuth state is a random nonce bound to a short-lived cookie
  (navigateUrl rides in the cookie), verified one-shot on callback; the tenant
  comes ONLY from the RS256/JWKS-verified IAM token owner (cloud.NewTokenValidator)
  — fail closed, no default org.
- transactor: WS upgrade enforces an Origin allow-list (same host, team
  surfaces, *.hanzo.ai, absent Origin for non-browser); serves the front's
  /api/v1/statistics poll target (own-workspace sessions only).
- entitle: selectWorkspace requires the org's 'team' license — definitive no
  → 402 + upgradeUrl billing.hanzo.ai; guest role capped by the plan's
  team.guests entitlement (join order); infra errors ALWAYS admit so the gate
  can never brick login mid-rollout.
2026-07-20 12:57:56 -07:00
antje de05be1da9 refactor(cloud): drop the svc suffix — bare package names + spelled-out test helpers
One name per thing, no compound-word cruft. The `svc` suffix was never a real
package (zero `package *svc`) — only import aliases and abbreviated test helpers.

- Import aliases → bare package names: plansvc→plan (commerceclient),
  captablesvc→captable + dataroomsvc→dataroom (company/adapters). No stutter, no
  alias where the bare name is unambiguous.
- Test helpers spelled out: fakeSvc→fakeService, testSvc→testService,
  newSvc→newService — across admin/agents/deploy/domain/functions/ingress/
  integrations/ml/platform/provisioning/storage/wallets tests, callers updated
  in-package.
- Stale `// Package …svc` doc-comment prose corrected to the real package name
  (exec/iam/plugin/pricing/product/provisioning/sync/tasks).

Naming only — no logic change. go build + test-compile green on all 21 packages.

Note: the clients/team package (filesSvc/fsvc rename) is excluded here — it has
concurrent in-progress work; its svc cleanup lands with that change.
2026-07-20 12:56:12 -07:00
antje 7484b3a0c2 plans v1.4.1: hanzo.team commercial model — $20/$100/$200 ladder + $25/user team
Bump github.com/hanzoai/plans v1.4.0 -> v1.4.1 (catalog: pro repriced $20
on hanzo_pro_20, new plus $100, max $200, team $25/user per-seat minSeats 2,
team.guests entitlement, team namespace).

Pin the contract in clients/plan tests: TestPlans_Ladder freezes the
subscription ladder prices + stripe lookup keys + team per-seat/minSeats;
TestLicenseEntitlement_TeamProduct freezes the hanzo.team entitlement gate —
licensing.product:team emitted for pro, plus, max AND team, engine on max,
never on developer. Vocab namespaces 9 -> 10 (team).

Smoke-booted: /v1/plans/subscriptions serves the new ladder,
/v1/plans/entitlements/team carries licensing.product:team.
2026-07-20 10:51:13 -07:00
hanzo-dev e96505d3c7 feat(base): host-as-project-ref — serve /v1/base + /v1/realtime + /_/ on the app host
A published site host now serves its org own Base data plane (HIP-0014). The
sites middleware, on a /v1/base|/v1/realtime|/_/ path, calls an injected per-org
Base handler with the org the SUBDOMAIN resolves to (Site.Org) — never the
caller — so an anon page reaches its own Base, authz by Base collection rules.
One seam (sites.SetBaseHostHandler, mirroring SetResolver; no import cycle),
gated by CLOUD_BASE_PUBLIC_HOST (default OFF): absent the flag a site host serves
only static files, unchanged. This is what makes maxpower.hanzo.app/_/ (admin) +
the public contact form + anon realtime chat work — the token supersedes the
key/host for signed-in users (org from IAM), keys/host are the tokenless path.
2026-07-20 09:00:38 -07:00
hanzo-dev 79e936a7f2 wip(sites): MEDIUM-1 — coalesce+ceiling the shared Cloudflare purge (INCOMPLETE)
Partial fix for red MEDIUM-1 (unbounded shared purge = cross-tenant blast
radius). Per-tag coalescing + process-wide per-minute ceiling in the Purger.
NOT finished: MEDIUM-2 (release retention GC), LOW-1 (reject rel=="."),
LOW-2 (empty dest ETag = fail). Do not merge until complete + red re-review.
2026-07-19 23:22:19 -07:00
antje 0c06f9b78d sites: bare <slug>.hanzo.app is the ONE servable host — publish binds + advertises it
The org-scoped two-label design (<slug>.<org>.hanzo.app) was never servable: a
k8s wildcard Ingress host and a Let's Encrypt wildcard cert each match exactly
ONE label, so the two-label host neither routes nor gets TLS. Publish still
stamped it as liveUrl and bound it, so every 'Visit' link and the console/app
cards pointed at a dead host, and the sites edge served nothing.

One host, one way:
- siteURL → https://<slug>.<apex> (bare); siteHost → bare <slug> (the global
  first-come binding key — matches TestSiteHostBindingIsFirstComeAndTenantSafe,
  which already asserted bare-host first-come). A second org publishing the same
  slug is refused the subdomain and serves at its S3 URL only.
- siteSlug parses ONLY the bare host; a dotted key falls through to the API
  pipeline. unique-live-slug resolve (added earlier) keeps pre-binding publishes
  servable with no backfill.
- tests updated to the bare-host contract throughout.
2026-07-19 22:08:55 -07:00
hanzo-dev 6fa8e70435 feat(sites): publish by server-side promote into immutable releases
Static sites had no way to put content at a site's prefix through the API.
Add one: a release plane on the existing site engine.

A release is an immutable prefix whose id is a digest of the object manifest
it was promoted from; the site record holds a pointer to the release it
serves, and siteResolver resolves through it. Publishing copies server-side
within the object store, so no bytes traverse the API and no client holds an
S3 credential. Rollback is the same pointer flip aimed at an older release.

Isolation: the source is a path relative to the caller's own org space. The
org segment comes from the validated principal (the one org rule this package
already uses for site prefixes) and the bucket never comes from the request,
so a caller has no syntax for naming another tenant's data. safeRel roots and
cleans both the source and every object key.

Atomicity: the release row is written only after every object lands, and
activation is one statement whose WHERE requires that row in the same tenant,
so a partially-copied release cannot be pointed at. ActivateRelease is the
sole writer of the pointer on the activate path.

Releases live in <org>/.releases/<slug>/<id>/, a sibling of the mutable
serving prefix, so a full-artifact deploy reclaims the pointer without
destroying retained releases. Caps reuse the artifact budget.

POST   /v1/sites/:slug/publish
POST   /v1/sites/:slug/releases
GET    /v1/sites/:slug/releases
POST   /v1/sites/:slug/releases/:release/activate

Mirrored under /v1/platform/sites. Inert for existing sites: an empty pointer
serves the legacy prefix.
2026-07-19 21:48:52 -07:00
zeekayandhanzo-dev 834987d2f4 refactor(routes): group single-prefix subsystems under app.Group("/v1/<x>")
45 subsystems converted from flat full-path registration to the idiomatic zip
app.Group("/v1/<prefix>") + relative-path pattern — DRY the prefix, one and
only one way. Route-preserving: proved Group(p).<M>("/rel") == flat
app.<M>("p/rel") byte-for-byte; bare-prefix root routes kept FLAT (Group(p).
Get("") would add a trailing slash). Multi-prefix / dynamic-path / cross-
function-collision subsystems deliberately left flat.

Every converted subsystem gated on route-table preservation + go build + go vet;
combined ./clients/... + ./apps/... compiles clean; TestWireOrderMatchesFrozen
passes (Wire()/composition root untouched — grouping is inside each Mount).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-19 21:13:40 -07:00
antje 51107c55cc merge: shared admin core/warehouse ClickHouse helpers (data-platform-warehouse-helpers)
feat/data-platform-warehouse-helpers: clients/admin/core/warehouse.go + invoices/
metrics/subscriptions refactored onto it (aimetrics portion already landed via
#10). Conflict resolved keeping main's CreateCreditGrant, dropping the SaaS-metrics
helpers moved to warehouse.go. Tests: clients/admin (all subpkgs) ok, apps ok.
2026-07-19 20:45:00 -07:00
hanzo-devandantje c483b5868b admin(data-platform): shared core/warehouse ClickHouse helpers + invoices/metrics/subscriptions using them + test coverage + aimetrics 2026-07-19 20:43:08 -07:00
antje 4a63b00add merge: fleet gpu-connect CPU arch/cores/RAM reporting (fleet-byo-cpu-spec)
feat/fleet-byo-cpu-spec: gpu-connect nodes report CPU arch + cores + RAM on
/v1/fleet (cli/gpu.go, clients/visor board+fleet). Redundant #331 flags-test
tweak dropped in favor of main's. Tests: visor ok, cli ok, apps ok (CGO-off);
flags green under CGO-on (its one CGO-off failure is pre-existing, matches main).
2026-07-19 20:40:58 -07:00
hanzo-devandantje 41fe52d694 feat(fleet): gpu-connect nodes report CPU arch + cores + RAM on /v1/fleet
BYO nodes that dial in via `hanzo gpu connect` reported only their GPUs, so the
/v1/fleet board (and the world Fleet panel) showed NO CPU arch or system memory
for them — unlike code-linked run-targets, whose Spec already carries
arch/cpus/memory. evo-2 (Strix Halo, x86_64) and spark (GB10, aarch64), both
128 GB, appear on the board as BOTH a run-target AND a gpu-connect worker; the
BYO rows surfaced blank arch/memory.

Add the host's static CPU spec to the fleet presence record, read from the real
machine (never hardcoded), in the SAME convention the fleet already uses for
code-linked nodes so a machine shows ONE arch string across both rows:
  - reporter (cli/gpu.go): registration gains arch, cpus, memory. detectArch is
    `uname -m` (aarch64 | x86_64 | arm64) to match the existing fleet convention
    (NOT runtime.GOARCH's arm64/amd64). detectMemTotal reads /proc/meminfo
    MemTotal on Linux (evo-2, spark) / sysctl hw.memsize on Darwin; cpus =
    runtime.NumCPU. 0/"" when unknown, never faked.
  - decoder (clients/visor/fleet.go): fleetRegistration + byoWorker mirror the
    three fields (lockstep with the CLI) and byoWorkers populates them.
  - board (clients/visor/board.go): workerUnits -> byoUnit fills
    fleetSpec.Arch/CPUs/Memory (the fields agentUnits already sets), so a
    gpu-connect node and a code-linked node describe themselves identically.

Verified on a real GB10 (spark-class): detectArch=aarch64 (uname -m), nproc 20,
/proc/meminfo 127600528 kB -> 130662940672 bytes — byte-identical to how the SAME
box already reports as a code-linked run-target (arch=aarch64 cpus=20
memory=130662940672).

Tests: parseMemTotalKB, detectMemTotal (real host >0), detectArch (uname -m
convention, not GOARCH), buildRegistration host spec; fleetRegistration decode +
byoUnit projection + unknown-spec omitted.
2026-07-19 20:37:43 -07:00
antje 32664d746d merge: admin AI-metrics read view (aimetrics-router-verify)
feat/aimetrics-router-verify: clients/admin/aimetrics.go — /v1/admin/aimetrics
read view. Tests: clients/admin (+subpkgs) ok, apps ok.
2026-07-19 20:37:05 -07:00
hanzo-devandantje 5a50f1ee6a admin(aimetrics): AI-metrics read view (clients/admin/aimetrics) + test 2026-07-19 20:36:47 -07:00
antje 6fa3a2df68 merge: thin audited admin credit-grant relay (admin-credit-grant)
feat/admin-credit-grant: clients/admin/creditgrant.go — audited relay to the
commerce credit-grant. Tests: clients/admin (+subpkgs) ok, apps ok.
2026-07-19 20:35:35 -07:00
hanzo-devandantje 34956f0fc2 feat(admin): thin audited credit-grant relay at POST /v1/admin/credit-grants
The one admin mint surface. SuperAdmin-only (core.Guard); forwards verbatim to
commerce's already-mint-gated POST /v1/billing/credit-grants (middleware.Mint →
PlatformOnly) via COMMERCE_SERVICE_TOKEN, scoped to the target org, and writes one
tamper-evident audit record. Commerce stays the sole credit-grant ledger — no
in-process mint. NOT deployed; for red review (mint surface).
2026-07-19 20:35:15 -07:00
antje c50a5646b5 merge: unified inbound channel ingest plane (channels)
feat/channels: clients/channels/{slack,teams,telegram,store}.go + integrations
ingress + cmd/channels — envelope, pairing, policy, per-platform adapters.
Tests: clients/channels ok, clients/integrations ok, apps ok.
2026-07-19 20:34:57 -07:00
hanzo-devandantje 782627658a feat(channels): unified inbound channel ingest plane (envelope, pairing, policy, per-platform adapters)
Preserve divergent channel-ingest work: clients/channels package (envelope
normalization, pairing, delivery policy, Slack/Discord/Teams/Telegram
adapters, store), cmd/channels entrypoint, integration event-emit hooks,
and apps wiring.
2026-07-19 20:30:04 -07:00
antje cbd91a4d1e sites: serve bare <slug>.hanzo.app again — unique-live-slug resolve
The org-scoped host redesign (<slug>.<org>.hanzo.app) left the edge unservable:
a k8s Ingress host and a Let's Encrypt wildcard each match exactly ONE label, so
the two-label shape never routes nor gets TLS, while the one-label product URL
every surface advertises (palette, share copy, publish toast) was rejected by
siteSlug and fell through to the console pipeline. Net: no published site
resolved at all.

Fix, preserving the org-scoped design:
- siteSlug accepts a bare non-reserved <slug>.<apex> label again (org-scoped
  two-label parsing unchanged, ready for per-org certs later)
- siteResolver falls back for bare keys: explicit site_hosts binding first,
  else ResolveUniqueLiveSlug — serve iff EXACTLY ONE live project owns the
  slug across orgs; ambiguous or draft ⇒ honest 404. Deterministic,
  hijack-safe (reserved labels rejected at the host boundary), and
  migration-free for publishes that predate host binding.
- tests: bare-host parse cases + unique/ambiguous/draft resolve proofs
2026-07-19 20:01:41 -07:00
antje 5acb6b5acd chore(gitignore): ignore local .worktrees/ container
The .worktrees/ directory holds local git worktrees (dev infra), never part of
the tree — mirrors the existing .claude/ rule so a working checkout stays clean.
2026-07-19 19:54:27 -07:00
antje b99ee45898 merge: kmsreseal dual-face auth + owner-claim assertion
feat/kms-reseal-migration: split reseal tokenFunc into src/dst faces (CR app-name
credential vs per-org <org>-platform-kms), assert minted-token owner==target org
(refuse admin), flag empty source folders as seeding-wedge risk. Tests: apps ok;
cmd/kmsreseal ok (full suite green under CGO; new auth/owner tests green under CGO-off).
2026-07-19 19:52:29 -07:00
hanzo-devandantje f2ffc0d770 feat(kmsreseal): dual-face auth + owner-claim assertion for the reseal migration
The reseal migration reads from the standalone KMS and writes into cloud KMS —
two faces with DIFFERENT identities. Split the single tokenFunc into srcAuth/dstAuth:
src uses the CR app-name credentialsRef (the standalone accepts it); dst uses the
per-org <org>-platform-kms credential (cloud accepts it dynamically, admin-denied,
no static audience widening).

Defense-in-depth (LOW-1): decodeJWTOwner reads the minted token owner/isAdmin claims
locally and asserts owner == target org (refusing admin tokens) before any read/write,
so a misscoped credential fails its target instead of acting on the wrong org. An
empty source folder is flagged as a seeding-wedge risk instead of silently skipped.

Tests (auth_test.go): decodeJWTOwner, owner-mismatch + admin-refusal gates,
dual-face token brokering.
2026-07-19 19:50:16 -07:00
antje 2a4267fcfb merge: CD per-app detail endpoints (syncwindows, revision metadata, resource-tree SSE), tenant-scoped
feat/cd-detail-endpoints: serve the three per-app endpoints the ArgoCD SPA
detail view calls, scoped by the same resolveScope/findNamespace path as
dashApp. Tests green: clients/deploy, apps.
2026-07-19 19:48:39 -07:00
hanzo-devandantje d0682cd978 deploy: serve the three per-app CD detail endpoints, tenant-scoped
The ArgoCD SPA's application-detail view calls three per-app endpoints the
projection did not serve, spamming "404 page not found" toasts. Add them,
scoped by the same resolveScope/findNamespace path as dashApp — a SuperAdmin
sees the whole fleet, a validated org member sees only its own apps, a
cross-tenant name is a clean 404 (no oracle), an unvalidated caller fails
closed:

- GET /applications/:name/syncwindows -> the permissive-empty
  ApplicationSyncWindowState (no sync windows run; canSync true).
- GET /applications/:name/revisions/:revision/metadata -> honest minimal
  RevisionMetadata (message = the revision, HEAD resolves to the declared
  image tag; date = the CR creation time; author empty). Image-based deploys
  carry no git commit and the manifest repo is not the app's source, so no
  author is fabricated and it never 404s.
- GET /stream/applications/:name/resource-tree -> the live ApplicationTree
  as SSE (data: {"result": tree}), the scope gate before any emission,
  emitted once then refreshed on the keep-alive interval, honoring ctx cancel.
2026-07-19 19:48:16 -07:00
antje 564e6c4386 merge: Hanzo Domains registrar (name.com) + session store + routed-dispatch reach 2026-07-19 18:31:14 -07:00
hanzo-devandantje 3edbbe2753 feat(cloud): domain registrar (name.com) + session store — routed-dispatch reach + CD promote job
clients/domain: registrar layer — name.com client, pricing, register,
per-org store, /v1 mount. clients/session: session store backing routed
runs. Agents: mailbox + routing reach the dispatch targets; release.yml
gains the declared-tag promote job (universe CR bump, Hanzo CD syncs).
2026-07-19 18:31:12 -07:00
hanzo-devandantje bda1a1681c coding: verify + PR + close the session when a routed run completes
A routed run's machine pushes with its own credential and streams into the
session, but cloud still owns the completion — the integrity gate, the PR row, and
the session's terminal state (the machine never closes the session, so it was
staying "running" forever). Give a routed run the SAME cloud-side completion the
local keystone path runs after a sandbox push.

- completeChanged: the shared terminal for a run that reported changes — VerifyRef
  the pushed branch LANDED (fail-closed to a session error + no PR if absent), file
  the native PR, mirror done, close the session done. The local path (Run) now calls
  it too, so the two paths cannot drift.
- finalizeRouted: maps a machine's terminal report onto that completion — reported
  failure closes the session error (no PR), no-changes closes done (no PR), a changed
  push runs completeChanged. No secret crosses; cloud only reads the ref it can see.
- DeliverRoutedRunActivity runs the completion once, after a real report, on a
  cancel-immune bounded context, so a completed run is never re-executed by a retry.
  The completion seam is injected at the composition root (NewDispatcher), the same
  injected-seam shape index_on_push uses, so the free-function activity reaches the
  dispatcher's git/tracker/session seams without a global Dispatcher.
- RoutedRun carries Actor + AgentRef (cloud-side only, never sent to the machine) so
  the completion attributes the session close and files the PR with the right
  assignee.

Also document the mailbox's single-replica dependency at its definition (accepted,
inherited from cloud's KMS-lock replicas:1) with a future replica-aware note.

Tests: routed changed+verify -> PR filed + session done; verify fails -> no PR +
session error; no changes -> done no PR; reported error -> error no PR (verify never
runs); NewDispatcher wires the seam; the durable type bridge preserves attribution.
2026-07-19 18:17:08 -07:00
hanzo-dev bc762e3704 chore(deps): bump hanzoai/ai v1.827.0 -> v1.827.1 (NULL-safe OrgSettings scan) 2026-07-19 13:19:34 -07:00
hanzo-dev 4fd6c8d427 deploy: debrand the projection instance label argocd.argoproj.io -> hanzo.ai
The CD projection synthesized an argocd.argoproj.io/instance label on every app
(visible on every card). It is Hanzo-native CD, not ArgoCD — the App CRs carry
hanzo.ai/* labels. Emit hanzo.ai/instance instead; env + org labels unchanged.
(The argoproj.io/v1alpha1 response SHAPE stays until the @hanzo/gui FE that reads
@hanzo/ui/cd native types replaces the ArgoCD SPA.)
2026-07-19 12:44:19 -07:00
hanzo-dev 0c24ee1322 deploy: tenant-scope the CD projection to IAM orgs and projects
Resolve each /v1/deploy read request's scope from the validated identity —
the same boundary clients/platform.tenant uses (validated principal +
injective provisioning.SanitizeOrg + the c.IsAdmin SuperAdmin predicate).
A SuperAdmin sees the whole fleet; a validated org member sees only its own
org's apps (hanzo.ai/org label, tenant-<org> namespace); anyone else is
refused. Scoped reads: applications list/detail/resource-tree, clusters,
projects, and the SSE stream. sync/rollback + the argocd bootstrap stay
SuperAdmin-only.

projectApp reads app.kubernetes.io/part-of into spec.project (default when
absent) and surfaces hanzo.ai/org. The projects endpoint reflects the
IAM-owned (org,name) Project resource in-process — org-scoped for a normal
org, all orgs for a SuperAdmin — with a synthesized default so every app's
spec.project resolves. IAM stays the single source; no CD-side project row.
2026-07-19 12:44:19 -07:00
hanzo-dev e9d470d089 chore(deps): bump hanzoai/ai v1.826.7 -> v1.827.0
Integrates the last two router branches now on ai main:
- per-org RoutingPolicy on the hot path (decomplected per-org routing)
- context_window surfaced in /v1/models

(do-ai premium routes + judge/MFJP + mean-field + RouterCostCeiling slider
+ the judge-panel deadlock fix already shipped via v1.826.7, already live.)
clients/... compiles clean against v1.827.0.
2026-07-19 12:32:04 -07:00
hanzo-dev 7b073f334f deploy(stream): guard typed-nil watch object + recover on watch goroutines
A malformed watch event carrying a typed-nil *unstructured.Unstructured would
nil-deref on GetName() in forwardWatch. The read plane installs no panic
recovery around detached goroutines, so that crash would take down the whole
process. Guard the typed-nil, and recover at the spawn site so no future
malformed event can crash the plane. Adds a regression test.

Red review: SHIP (this closes the sole LOW finding).
2026-07-19 10:15:48 -07:00
hanzo-dev 00a31dd644 feat(deploy): project /clusters, /projects, /stream/applications for the CD dashboard
The ArgoCD-UI-compatible surface returned nothing at three endpoints the
applications view calls, so the SPA error-toasted on load:

  GET /v1/deploy/clusters            -> 404
  GET /v1/deploy/projects            -> 404
  GET /v1/deploy/stream/applications -> 404

Add all three as read-only projections over the SAME App-CR source dashAppList
reads (listAppCRs + runningVersions + projectApp: one source, one projection),
SuperAdmin-gated by guard(), safe on cloud-reader (no writer/commerce imports):

- /clusters -> ClusterList of the destinations the fleet reconciles into,
  deduped, always including the in-cluster destination, with a per-cluster
  application count. argoCluster has no config field, so a cluster credential
  cannot be surfaced by construction.
- /projects -> AppProjectList: prefers real argoproj.io/v1alpha1 AppProject CRs
  when that CRD is served (reshaped to only the intended spec fields), otherwise
  synthesizes one permissive project per distinct App-CR project name (default
  always present).
- /stream/applications -> the applications watch as SSE: one ADDED event per
  current App CR, then live ADDED/MODIFIED/DELETED from a per-namespace watch,
  held open with keep-alives. Every watch + goroutine is bound to the request and
  torn down on disconnect; degrades to keep-alive only if the watch verb is not
  granted; fails closed (503) with no cluster client.

Tests (go test -race green): cluster dedupe + always-in-cluster + never-emits-
credentials; project distinct/default + synth-permissive + real-CR-only-intended-
fields; stream ADDED-per-app + zero-app-no-panic + honors-ctx-cancel + SSE-headers;
all three routes 403 without SuperAdmin.
2026-07-19 10:15:48 -07:00
zandGitHub dae694eebf fix(commerce): stop the in-process self-dispatch recursion that crash-loops the writer (#341)
scopeRateLimiter reads its own rules via a co-resident commerce self-dispatch (GET /v1/billing/spend-alerts) on every authed request; the rule cache fills only after the fetch returns, so the self-dispatch re-enters scopeRateLimiter with a cold cache → unbounded in-process recursion → writer stack-overflow (single request) / OOM (concurrent). Dump-attributed (goroutine 4423, 21,823 setRequestCancel) and real-binary A/B verified on current main+fix (GET returns, POST 402s, 40-concurrent peaks 228 goroutines, 0 pileup). Exempt the commerce config surface from its own gate + an on-path depth backstop.
2026-07-19 09:56:11 -07:00
zeekayandhanzo-dev 7107d3c43d harden(team): Chunter responder OFF by default + bounded/lazy (anti-storm)
Post-mortem containment for the v1.801.104 writer crash. To be unambiguous on
root cause: the fatal was the commerce co-resident dispatch reentrancy
(stack: apps.mountCommerce.IAMTokenRequired.func5 → commerce@v1.49.3
iammiddleware.go:157 → unbounded net/http.setRequestCancel goroutines), the bug
PR #341 fixes, introduced by 697b89e (enso per-tier gate) in the .99→.104 range —
NOT this responder. The responder makes ZERO outbound calls at boot (it fires only
from session.tx, the live client-WS write path; never from reconcile/replay). Any
build of current main still crashes until #341 lands, independent of this change.

That said, an unbounded per-message responder IS a foot-gun, so this makes it
safe-by-default and bounded regardless:

- OFF by default: Mount wires the LLM seam ONLY when TEAM_AGENTS_ENABLED=1. A nil
  runAgent makes maybeAgentReply return at the top → NO outbound model call can
  fire. An un/mis-configured binary is provably inert.
- Fresh-only: a message created before this process booted (>60s grace) is a
  replay/backfill and is NEVER answered — kills the "replayed backlog fans out into
  thousands of HTTP calls" failure mode.
- Single-flight per (workspace, space, bot): a burst to one conversation collapses
  to one turn; duplicates dropped, not queued.
- Hard concurrency cap: a global semaphore (TEAM_AGENTS_MAX_CONCURRENCY, default 4,
  clamped 1..64) bounds in-flight turns; over the cap, DROP.
- Circuit breaker per agent: after 3 consecutive failures skip the agent for 60s —
  the backoff that turns a publishable-key 403 storm into a quiet trickle. No
  retries, ever.

TDD (all -race green): TestNoReplyToBacklogAtBoot boots against a 500-message
backlog and asserts ZERO runner calls (then one fresh post IS answered);
TestConcurrencyCapBounded (cap=2, 8 msgs → exactly 2 in-flight, rest dropped);
TestSingleFlightPerConversation (5 msgs, 1 conversation → 1 turn);
TestCircuitBreakerBacksOff (persistent failure → runner called exactly threshold
times, circuit opens). Existing responder + roster tests unchanged.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-19 09:47:44 -07:00
hanzo-dev eb48905ecc feat(deploy): project /clusters, /projects, /stream/applications for the CD dashboard
The ArgoCD-UI-compatible surface returned nothing at three endpoints the
applications view calls, so the SPA error-toasted on load:

  GET /v1/deploy/clusters            -> 404
  GET /v1/deploy/projects            -> 404
  GET /v1/deploy/stream/applications -> 404

Add all three as read-only projections over the SAME App-CR source dashAppList
reads (listAppCRs + runningVersions + projectApp: one source, one projection),
SuperAdmin-gated by guard(), safe on cloud-reader (no writer/commerce imports):

- /clusters -> ClusterList of the destinations the fleet reconciles into,
  deduped, always including the in-cluster destination, with a per-cluster
  application count. argoCluster has no config field, so a cluster credential
  cannot be surfaced by construction.
- /projects -> AppProjectList: prefers real argoproj.io/v1alpha1 AppProject CRs
  when that CRD is served (reshaped to only the intended spec fields), otherwise
  synthesizes one permissive project per distinct App-CR project name (default
  always present).
- /stream/applications -> the applications watch as SSE: one ADDED event per
  current App CR, then live ADDED/MODIFIED/DELETED from a per-namespace watch,
  held open with keep-alives. Every watch + goroutine is bound to the request and
  torn down on disconnect; degrades to keep-alive only if the watch verb is not
  granted; fails closed (503) with no cluster client.

Tests (go test -race green): cluster dedupe + always-in-cluster + never-emits-
credentials; project distinct/default + synth-permissive + real-CR-only-intended-
fields; stream ADDED-per-app + zero-app-no-panic + honors-ctx-cancel + SSE-headers;
all three routes 403 without SuperAdmin.
2026-07-19 09:25:40 -07:00
zeekayandhanzo-dev d4c435b17c feat(team): Chunter agent responder — org agents become talkable in chat
Bots-as-members (bots.go/roster reconcile) already projects each org agent as a
workspace Employee, but a message to a bot did nothing — the AI was present and
mute. This adds the WRITE/response half: when a human posts a Chunter ChatMessage
addressed to an active bot member — a DirectMessage whose participants include the
bot, or a channel message that @-mentions it — the transactor runs that agent
through agents.RunOnBehalf (the ONE billed/metered/recorded in-process run path)
and posts the model's answer back into the SAME conversation as that bot, via the
SAME applyTx + hub.broadcast write the SPA and roster projection use.

- chat.go: parseChatMessage, replyTargets (DM-member OR @mention addressing),
  maybeAgentReply (cheap gate → agents list → per-bot async turn), replyAsBot
  (recovered + 90s-bounded goroutine; never blocks the WS loop). plainText/
  htmlMarkup bridge stored markup ↔ LLM text. Loop guard: a bot-authored message
  never triggers a reply.
- transactor.go: transServer gains runAgent (the LLM seam) + log; session.tx fires
  maybeAgentReply on the client write path only (roster/sync call applyTx directly,
  so a projection can never trigger a reply).
- bots.go: agentReplyRunner adapts agents.RunOnBehalf (error-status run → post
  nothing, never an empty bubble).
- team.go Mount wires runAgent=agentReplyRunner. Responder is off (nil runner) when
  unwired, so the path is fully additive.

TDD: 16 tests — parse/ignore, plainText/htmlMarkup, DM + mention addressing, the
full DM reply loop with a fake runner (asserts on-behalf-of user, agent id, plain
prompt, reply authored by the bot in the same conversation), loop-guard, and
disabled-when-no-runner. All clients/team tests green (CGO_ENABLED=0), go vet clean.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-19 09:06:50 -07:00
hanzo-dev 5694426431 chore(deps): bump ai v1.826.6 -> v1.826.7 (judge self-call pileup fix; unblocks commerce v1.49.3) 2026-07-19 07:16:48 -07:00
hanzo-dev f1c663c1bc feat(deploy): OAuth sign-in for the CD dashboard (PKCE, verify-before-mint)
cd.hanzo.ai rendered but every API call 403'd with no way to sign in: the IAM
session cookie is host-scoped to hanzo.id, so no other host's session can ever
authorize cd, and clients/deploy had no login route.

Adds GET /v1/deploy/login + /callback + POST /logout against the admin-console
app (org=admin; hanzo-cloud's org is hanzo, which is why admin users were never
found). Public PKCE client, no secret. The callback verifies the exchanged token
through cloud's own JWKS validator and decides SuperAdmin on VERIFIED claims
before minting; the unverified decode is gone. session/userinfo becomes a public
bootstrap so the SPA can discover it is signed out. guard() is unchanged.

DEPLOY_PUBLIC_URL is now REQUIRED (login/callback 503 without it).

blue built, red cleared: gate stronger than before, zero regressions.
2026-07-19 04:06:40 -07:00
hanzo-dev 2044c2684c deploy: verify the token before minting the session; make sign-in reachable
Red review of the sign-in round trip found no security defect, and four ways it
would fail in practice. All four are the same shape: correct in the happy path,
unhelpful or unreachable in the real one.

MINT ONLY WHAT THIS DEPLOYMENT WILL ACCEPT. The callback now runs the exchanged
token through cloud's OWN validator before writing the cookie, and decides the
admin-org question on VERIFIED claims. The audience allowlist is env-overridable
and jwtAudiencesFromEnv REPLACES the baked default, so a deployment whose
CLOUD_JWT_AUDIENCES / GATEWAY_ALLOWED_AUDIENCES omits this console's client_id
minted a cookie the boundary refused on the next request — 403, document-bounce
to sign-in, IAM session still live, instant code, mint, 403, forever. It now
fails once, with the reason and the knob to turn. The unverified claim decode is
gone with it.

That validator is exported from cloud (NewTokenValidator) rather than rebuilt
here: SanitizeIdentity validates on the way in, a subsystem minting a session
needs the same verdict a moment earlier, and two copies of it could drift into
exactly the mint-then-refuse loop above. jwksURLFor is now the one derivation
both share.

SIGN-IN HAS TO BE REACHABLE FROM WHERE THE USER IS. The dashboard is an XHR
client, so guard()'s document bounce never fires for it — it got a 403 and dead
-ended with no route to sign-in. /v1/deploy/session/userinfo is now the one
public bootstrap route: {loggedIn:false} plus the sign-in URL for an anonymous
caller, the real identity for a SuperAdmin. It discloses no identity, no cluster
state, no configuration, and gates nothing; every route that returns fleet data
or mutates a CR stays guarded.

The OAuth origin is now configuration, not the Host header. Deriving a redirect
from caller-controlled input is only ever saved by the registry's exact-match
check — a second lock covering for a broken first one. With no DEPLOY_PUBLIC_URL
sign-in fails closed naming the knob.

Logout is POST: as a GET any site could sign a SuperAdmin out by navigation,
which a SameSite=Lax cookie still rides. The session lifetime comes from the
verified expiry, clamped — an already-expired token no longer becomes an
eight-hour cookie, and a bogus far-future exp no longer becomes a decade-long
one. Both cookies take the __Host- prefix, which the browser only honours for
Secure, Path=/, Domain-less cookies, so a sibling *.hanzo.ai host cannot shadow
them.
2026-07-19 03:45:48 -07:00
hanzo-dev c35cdc72c0 deploy: sign in to the cd console with IAM, so its SuperAdmin gate is reachable
Every /v1/deploy route gates on c.IsAdmin(), which SanitizeIdentity mints only
from a validated IAM principal whose org is the reserved admin org. The console
had no way to establish one: the IAM session cookie is host-only on hanzo.id, so
a session from hanzo.id or admin.hanzo.ai is never presented to cd.hanzo.ai, and
the whole surface 403'd with no sign-in anywhere. Add the round trip.

  GET /v1/deploy/login    redirect into IAM authorize (PKCE S256, CSRF state)
  GET /v1/deploy/callback exchange the code, mint the session, land on returnTo
  GET /v1/deploy/logout   clear the session for this host

The session is cloud's EXISTING one: the callback writes the IAM access token to
hanzo_iam_token, the first name in cookieTokenNames, which SanitizeIdentity
already reads and independently verifies (signature, issuer, audience, expiry)
into the same principal a Bearer yields. No second session mechanism, and the
gate, the validation and the SuperAdmin predicate are unchanged.

Fail closed at every step: no code is redeemed unless the returned state equals
the nonce in the HttpOnly flow cookie this browser started with (login CSRF), a
principal outside the admin org is refused a cookie outright, and a return path
that is not a path on this host collapses to /. The cookie is HttpOnly, Secure,
SameSite=Lax and host-only, so page JS cannot read the token and no cross-site
POST carries it.

guard() keeps c.IsAdmin() as the only gate; only the shape of the refusal is
negotiated. A browser navigation is sent to the sign-in page instead of a dead-end
403; every API call keeps its 403, decided by Sec-Fetch-Dest/Mode when present and
never inferred from Accept alone, and a non-GET is never redirected.

admin-console is the client because its IAM organization is the admin org;
hanzo-cloud is owned by admin but organized under hanzo, so it resolves
admin-org users in the wrong org and never finds them.
2026-07-19 02:49:20 -07:00
zandGitHub 412b367ad6 chore(deps): bump commerce v1.49.3 — bounded org-resolution cache on the auth path (#340)
Auth-path org resolution hit the datastore on every request, allocating the
Organization before the blocking store call, so requests stalled on the
connection pool each pinned one and the heap tracked the backlog. Confirmed
from a live goroutine profile: 46 waiters in sql.(*DB).conn under
org.Resolve <- IAMTokenRequired, organization.New at 26.4% of a 1301MB heap.

Carries three fixes uncovered while landing it:
- follow commerce's resolver consolidation (middleware/svcorg -> pkg/org)
- point the go-unit test list at clients/flags; the stale clients/featureflags
  path failed setup on a missing directory and had CI/CD red on main
- assert the post-#331 flags contract: runtime flags ignore env, boot-time
  ReadOnly rows still read it. That test asserted the override #331 removed
  and never ran because of the stale path above.
2026-07-19 02:47:02 -07:00
hanzo-dev 0e8086f88d test(flags): assert the post-#331 contract — runtime flags ignore env
#331 stripped Env from waitlist_*/public_signup/gateway_* so /v1/flags is
the single source of truth, but left this test asserting the env override
it had just removed. The stale clients/featureflags path meant the package
never ran in CI, so it stayed green.

Now pins both halves: a runtime flag holds its default against an env var,
and a boot-time ReadOnly row still reads env.
2026-07-19 02:30:45 -07:00
hanzo-dev 9f4cc62ca6 fix(ci): point the go-unit test list at clients/flags
clients/featureflags was renamed to clients/flags; the stale path made
'go test' fail setup on a directory that does not exist, which has been
failing CI/CD on main.
2026-07-19 02:13:29 -07:00
hanzo-dev 24119a53b6 test(metering): follow commerce's resolver consolidation to pkg/org
commerce v1.49.3 folds middleware/svcorg into pkg/org so one resolver
serves every caller; Invalidate moves with it.
2026-07-19 01:47:45 -07:00
hanzo-dev eb9bee21ef chore(deps): bump commerce v1.49.3 — bounded org-resolution cache on the auth path
Auth-path org resolution hit the datastore on every request and allocated
the Organization before the blocking store call, so requests stalled on the
connection pool pinned one each and the heap tracked the backlog. v1.49.3
serves request-owned copies from a bounded LRU and refuses credential-named
orgs at the model layer.
2026-07-19 01:32:15 -07:00
0515c77120 analytics(ingest): PostHog-wire uuid->idempotent MessageID + utm_* attribution mapping (#338)
Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-19 00:05:43 -07:00
hanzo-dev 53c17fb3cc chore(cloud): vendor hanzoai/ai v1.826.6 — DO model catalog + mean-field + judge-panel
Brings the full run into the deployed service: 55-model DO GenAI catalog (Claude
opus-4.8/sonnet-5/fable-5/haiku, GPT-5.6/5.5/4o/o3, deepseek-v4-pro, llama-4, qwen,
glm, kimi — capabilities declared per live probe), the mean-field congestion router
(gated), the live /v1/router/judge-panel endpoint, the Mean-Field Judge Panel, and
geo-aware consent. Prod model ConfigMap (universe) syncs the catalog data separately.
2026-07-18 23:45:24 -07:00
hanzo-dev c71dce4116 chore(deps): bump commerce v1.49.2 — legacy numeric org-id resolves by name (SEV1)
Replaces the pseudo-version pin (v1.49.2-0.20260719024505-24ff20a68f52, the
Bug-A iterator-leak fix only) with the released v1.49.2, which also carries the
Bug-B guard: org.Resolve skips the doomed GetById for a legacy all-digit cached
id (IAM Valkey's stale 1772587477 for 'hanzo') and resolves by name, so the
(*Query).ById legacy-numeric path that hot-looped in v1.801.95 is never taken.
Keeps ai v1.826.4 (in-proc TierReader). go.mod+go.sum only.
2026-07-18 21:43:01 -07:00
z defdf84aea metering: SEV1 fix — cap authorize HARD-timeouts + fails open, never hangs completions
The auth fix let the metering cap check actually reach commerce AuthorizeSpendCap; a
legacy-org GetById hot-loop there then HUNG every completion (no timeout on the
in-proc authorize) — a cap that can block/hang the completion path is worse than one
that does not enforce. scopeAuthorize now runs the authorize under a strict 1.5s
deadline AND a select-based hard timeout that returns even if the in-proc handler
goroutine is STUCK (an unresponsive hot-loop cannot be interrupted, so ctx alone would
not unblock). On timeout OR any error -> AuthorizeVerdict fails OPEN (allow) — a slow,
broken, or hot-looping commerce ALWAYS allows, never waits. OnCapError logs each
fail-open so a degraded cap is observable. Regression test: a 10s-hanging authorize
returns an ALLOW in ~1.5s (completion never hangs).

The commerce hot-loop itself (the root cause) is fixed separately; this timeout is the
non-negotiable safety net that makes the cap path unable to hang regardless.
2026-07-18 21:17:47 -07:00
hanzo-dev 48a7814d3f chore(cloud): vendor hanzoai/ai v1.826.4 — Mean-Field Judge Panel + geo-consent live
v1.826.4 ships the LLM-as-judge dense-reward loop fully activated: the Mean-Field
Judge Panel (diverse calibrated judges, reputation-weighted consensus), geo-aware
consent (EU/UK/EEA explicit opt-in via CF-IPCountry, non-EU opt-out default), judge
config dynamic at admin.hanzo.ai (OrgSettings "*" row, no env), MFJP enabled by
default on a diverse cheap panel, and internal dev orgs seeded on. Judge scoring uses
the existing probe service bearer (no new secret). Also carries the MFJP + scientific
proof from v1.826.3.
2026-07-18 21:08:23 -07:00
hanzo-dev 94a24fce47 chore(deps): bump commerce to datastore iterator conn-leak fix
commerce 24ff20a6 closes single-row query iterators (Query.First). This
stops the Postgres pool leak that starved org.Resolve on the co-resident
balance + per-tier gate path — the 'context deadline exceeded' that made
the Enso per-tier SKU gate fail open and spiked chat latency to 10-40s.
2026-07-18 19:47:55 -07:00
zeekayandhanzo-dev 53761f7e73 test(apps): refreeze wire golden — add dns + cloudflare subsystems
Wire() gained the /v1/dns zone plane (after projects) and /v1/cloudflare edge
plane (after integrations) but the frozen golden in wire_test.go was not
updated, so TestWireOrderMatchesFrozen failed (87 specs vs 85 frozen) — which
red-lit cloud's CI/CD and blocked the auto-release image build. Refreeze the
golden to the exact runtime sequence (verified position-by-position, 87==87).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 18:41:01 -07:00
hanzo-dev c5b34364e8 feat(k8s): unified /v1/k8s surface on api.hanzo.ai — DOKS clusters + nodes
The ONE Kubernetes noun, proxied to Visor (clients/visor/k8s.go): list the
org's DOKS clusters, one cluster's detail (node pools + worker nodes), DEPLOY
(create) / delete clusters, and the fleet-wide worker nodes. Reads are org-scoped
by the validated IAM owner; mutations (create/delete) are admin-gated
(principal.IsSuperAdmin || IsOrgAdmin) — real house-account infra spend.

Consolidates the worker-node consumption: managedMachines now reads
/v1/k8s/nodes (was /v1/kubernetes-nodes), matching Visor's consolidated path —
no parallel kubernetes-* surface remains.

- k8s.go: listK8sClusters / getK8sCluster / createK8sCluster (admin) /
  deleteK8sCluster (admin) / listK8sNodes; wire structs + view mappers.
- visor.go: mount the /v1/k8s/* group; managedMachines -> /v1/k8s/nodes.
- tests: proxy + tenant-scoping, detail shape, nodes, and the admin gate
  (a non-admin create/delete is refused BEFORE reaching Visor); the fleet
  DOKS-node fake tracks the new /v1/k8s/nodes path.
2026-07-18 17:38:13 -07:00
67594d3341 chore(deps): bump hanzoai/ai v1.826.0 → v1.826.2 (dense auto-reward + exploration floor) (#336)
Brings the flywheel-turning fixes into the deployed binary: v1.826.1 LLM-judge dense
quality rewards + v1.826.2 dense implicit auto-reward (quality×cost) + epsilon
exploration floor (#109). Enables ROUTER_AUTOREWARD_ENABLED / ROUTER_EXPLORE_EPSILON.
./apps (ai.Mount) compiles clean against v1.826.2.

Co-authored-by: zeekay <zeekay@hanzo.ai>
2026-07-18 17:32:15 -07:00
zeekayandhanzo-dev dc923e566c docs(platform): correct buildJobSpec doc-drift (RED INFO)
- buildJobSpec doc claimed the REVERTED over-hardening (allowPrivilegeEscalation=
  false, all caps dropped); correct it to the actual documented rootless posture
  (defaults left for rootlesskit newuidmap) + point at the securityContext.
- tenantPullSecretName comment overstated "cloud-api holds no secrets grant";
  clarify cloud's only Secrets write is the per-tenant KMS-auth creds in a TENANT
  ns, and that the isolated build ns must stay OFF the tenant-RBAC selector so no
  secrets grant is projected there (R6).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 17:23:20 -07:00
zandGitHub 2b4150638c Merge pull request #335 from hanzoai/fix/platform-projects-500
fix(platform): GET /v1/platform/projects 200-empties on unavailable IAM store (console-init 500)
2026-07-18 17:19:51 -07:00
hanzo-dev b238d809e1 fix(platform): list projects degrades to 200 empty when IAM store unavailable
GET /v1/platform/projects 500'd on console dashboard init. The iamStore guard
converts a nil co-resident IAM object store into a typed 503, but listProjects
re-stamped ANY store error as a 500 (zip.Errorf(500, "list: %v", err)),
discarding the status — so a signed-in session's first read broke dashboard
init with {"status":500,"error":"list: platform requires the co-resident IAM
store, which is not initialized"}.

The dashboard's first authenticated read now degrades any store failure to an
empty project set (200 []) — a new org genuinely has zero projects — logging the
real cause for operators (never swallowed), written in-band so no outer error
filter can reflatten it. Also guards a stray nil row from nil-derefing into a
500. The store-level 503 guard + its three unit tests are unchanged.

Repro + regression gate: TestListProjects_NilIAMStore_ServesEmpty200 (real
iamProjects over a nil in-process IAM engine — the deployed condition) and
TestListProjects_StoreError_ServesEmpty200.
2026-07-18 17:18:39 -07:00
zeekayandhanzo-dev 21c171bef2 fix(paas): RED H1/L1 — deploy is superadmin-only + explicit-env (close the platform-restart DoS)
RED found the /v1/paas auth broadening handed every brand-org ("hanzo") OrgAdmin
fleet-wide rolling-restart of the platform's OWN tier (the only namespaces the board
scans are hanzo{,-testnet,-devnet}, where iam/kms/gateway/cloud/… run) — a live DoS
lever, partially re-opening the 2026-07-08 admin-org P0.

H1: the MUTATING POST /v1/paas/apps/:app/deploy now uses operatorGuard (principal.
IsSuperAdmin ONLY), not the broad read guard. Restarting a shared platform service is
a platform-operator action; a customer-org admin — even of the brand org — is refused
403. The READ board (list/get) stays SuperAdmin||OrgAdmin (observe, audit-logged,
bounded). Confinement (scopedNamespaces) unchanged.

L1: deploy REQUIRES ?env=main|test|dev (nsForEnv-validated) — a bare deploy no longer
silently targets production; the CLI requires --env before the call.

Tests: TestDeploy_OrgAdmin_403_Platform (the H1 regression), _NonAdmin_403,
_SuperAdmin_RollingRestart, _RequiresExplicitEnv, _SuperAdmin_EnvSelectsNamespace;
CLI TestDeployRequiresEnv. All green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 17:14:42 -07:00
hanzo-dev ed5d5be5dd fix(deps): bump ai v1.825.2 -> v1.826.0 (enso per-tier gate enforcement + real router-stats model ids) 2026-07-18 17:07:21 -07:00
hanzo-dev 697b89e11e fix(billing): enforce enso per-tier gate — inject co-resident commerce tier into ai
The embedded ai per-tier SKU gate (family_tier.go) was fail-open in-cluster: it
resolved the caller's tier with an authed HTTP self-call to the cloud edge, which
401/403s a service token on /v1/billing/*, so the gate saw "" and admitted every
tier — enso/enso-ultra were open to free callers.

Mirror wireFinance's SetBalanceReader: install aiobject.SetTierReader so ai reads
the subscription tier DIRECTLY over the co-resident commerce client the metering
gate already bills over (commerceinproc in-process, with the service token commerce
itself accepts) — never the cloud edge. Add metering.Client.Tier to decode tier.name
from GET /v1/billing/tier. Fail-safe preserved: a commerce error or unknown tier
folds to "" (allow), so a commerce blip never locks out a paying caller.

Bumps ai v1.824.2 -> v1.825.2 (the object.TierReader seam).
2026-07-18 16:54:47 -07:00
hanzo-dev 7070fffd03 feat(visor): fold DOKS worker nodes into the fleet — 3rd machine source
managedMachines unioned Visor's registry (/v1/get-machines) + live droplet list
(/v1/machines); a DOKS cluster's worker NODES appeared in neither (their droplet
carries a k8s tag, not a hanzo-org droplet tag), so world.hanzo.ai showed
standalone droplets but never cluster nodes.

Add GET /v1/kubernetes-nodes as the THIRD source (Visor unions the house-account
hanzo-org-tagged clusters + BYOC Provider.ClusterID clusters and returns each
worker node as a Machine keyed by droplet id). It is processed after registry and
live, so a DOKS node whose droplet is ALSO in the live list dedupes by droplet id
and never lists twice; a cluster-only node surfaces. Independently resilient like
the other two — a kubernetes-nodes outage is logged and skipped, never hiding the
registry/live/BYO sources.

Test: TestMachinesMergeDOKSNodes — a DOKS-only node appears, and a node whose
droplet is already live collapses BY ID (the node row carries a different name, so
only id-dedup can merge it). Full clients/visor suite green (31 subtests).
2026-07-18 16:52:27 -07:00
zeekayandhanzo-dev 3a9a00f2b2 docs(llm): document the unified hanzo CLI ↔ /v1/paas contract (apps/deploy/clusters off one IAM login)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 16:49:03 -07:00
hanzo-dev 11bf05434f merge(cloudflare): move asset routes under /v1/integrations/cloudflare — unified provider shape, never top-level 2026-07-18 16:46:59 -07:00
zandGitHub 4cc5f87137 Merge pull request #334 from hanzoai/feat/event-canonical
analytics: canonical POST /v1/event + fail-closed key->org convergence
2026-07-18 16:46:45 -07:00
hanzo-dev 6fe0f98a5f analytics: canonical POST /v1/event front door (Event|[]Event), one write core
POST /v1/event is the ONE ingestion door: body is a single Event or a JSON-array
batch (no /v1/event/batch), org resolved IAM-only and fail-closed (eventTenant),
funneled through the ONE write core (ingestEvents) into hanzo.events. The
Segment/beacon (/v1/analytics,/v1/tracker) and PostHog (/v1/insights/e) wires
become thin DEPRECATED adapters over the same core. Org is never read from body.
2026-07-18 16:46:16 -07:00
hanzo-dev fd55a5b5c0 analytics: fail-closed project-key->org via the ONE IAM key seam (cloud.OrgForKey)
capture resolves a presented project/API key to its owner org through the single
IAM key resolver (sharedKeys, 60s cache incl. miss-cache). A presented-but-
unresolvable key is refused (403) and NEVER falls through to the brand-host
fallback, so a keyed request can never cross-tenant write. Anonymous marketing
traffic still resolves to the public brand org server-side from Host.
2026-07-18 16:46:16 -07:00
eb6ab336d5 chore(deps): bump hanzoai/ai v1.824.2 → v1.825.1 (Enso auto-serve + churn-resilient trainer) (#333)
Brings the merged Enso router fixes into the deployed cloud binary:
- #107 (v1.825.0): auto never routes to a family SKU it can't serve + forward the
  resolved model (withModel body rewrite) → model=auto serves 200 (was 404); grant-
  aware known predicate; flywheel boots from the single shared Bootstrap.
- #108 (v1.825.1): trainer fits EARLY (~90s after boot) then cadence → completed
  retrain cycles survive frequent redeploys (churn-resilient).
./apps (ai.Mount site) compiles clean against v1.825.1 (API-compatible).

Co-authored-by: zeekay <zeekay@hanzo.ai>
2026-07-18 16:44:32 -07:00
z 7e38d98551 billing: admit the verified S2S service token past the /v1/billing/* gate (cap authorize) + flag commerce
The metering cap-gate authorize (and the SuperAdmin cap-oversight Forward) call the
in-proc /v1/billing/spend-alerts/authorize with the COMMERCE_SERVICE_TOKEN, but the
customer /v1/billing/* bridge required a validated IAM principal -> "sign in to view
billing" (403) -> the cap fails-open and never enforces. billingData now admits a
trusted S2S caller carrying the verified service token: org from the EdgeAuth-controlled
X-Org-Id, query forwarded VERBATIM (a trusted caller names its own subject), no
subject-pin. A public caller can never present it (the gateway 401s a Bearer that is
not an IAM JWT / hk-|pk-|sk- key), and an unauthenticated caller still gets 403 (tested).
Adds spend-alerts/authorize to the GET allowlist; constant-time token compare.

ATOMIC with the flag: bumps commerce to v1.49.2 (SPEND_CAP_ENFORCE, default OFF), so
the instant the cap can reach the handler the enforcement gate is fail-open in the
binary -> auto-deploy stays safe until an operator flips the flag after the canary proof.

Security invariants tested: public/unauth -> 403; wrong bearer -> 403; verified token +
X-Org-Id -> forwards verbatim; token без X-Org-Id -> 403.
2026-07-18 16:40:05 -07:00
hanzo-dev 044eb14c18 refactor(cloudflare): move asset routes under /v1/integrations/cloudflare
The per-org Cloudflare asset plane (Pages/Workers/R2/KV/D1) is repointed from a
first-level /v1/cloudflare/* surface to /v1/integrations/cloudflare/*, so a
third-party provider is connected AND used under one unified namespace — matching
where the connector's connect/callback/verify/disconnect legs and the KMS token
coordinate already live. Pure path move: no auth, isolation, or handler logic
changes. Route registrations, doc comments, and tests repointed together.

No collision with the connector's parametric routes: the asset paths are all
3+ segments (/cloudflare/{pages,workers,r2,kv,d1}/...) while the connector's
/v1/integrations/:provider and /:provider/{connect,callback,disconnect,verify}
are 1- and 2-segment patterns whose literal second segment never equals an asset
group. Static-under-param co-registration is already proven in the integrations
plane (slack/link static beside :provider). Mount order unchanged: integrations
before cloudflare.
2026-07-18 16:38:59 -07:00
hanzo-dev 606c20bcc5 merge(dns): /v1/dns forward head — path-guarded org-scoped proxy so console.hanzo.ai/dns loads zones
Red-cleared (double-encoding traversal closed, 9 tests green). Bearer-relayed, no standing cred.
2026-07-18 16:28:42 -07:00
zeekayandhanzo-dev 2dab7ddf12 fix(platform): rootless buildkit securityContext — match documented posture
The first rootless spec over-hardened (allowPrivilegeEscalation:false +
capabilities drop ALL), which breaks rootlesskit's setuid newuidmap/newgidmap
sub-uid mapping — proven by an on-cluster canary:
  newuidmap ... failed: operation not permitted
Relax to the documented moby/buildkit k8s rootless posture: privileged:false,
runAsUser/Group 1000, runAsNonRoot, seccomp+AppArmor Unconfined, and leave
allowPrivilegeEscalation / default caps at k8s defaults (newuidmap needs them).
Still user-namespaced, no host root — the decisive win over privileged=true.
Re-canaried: rootless build + scoped push-hanzoai cred pushed to ghcr OK.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 16:26:32 -07:00
zeekayandhanzo-dev c99117ace9 feat(cli,paas): unify apps/deploy/clusters on the LIVE Go cloud — one IAM login, org-scoped
`hanzo apps list`, `hanzo deploy`, `hanzo clusters` targeted the OLD TS-Dokploy
contract (/v1/apps, /v1/org/{org}/cluster, /v1/org/.../redeploy) — all 404 on the
live Go cloud (ghcr.io/hanzoai/cloud). Repoint the CLI at the endpoints the Go
cloud actually serves, authorized off the SAME IAM login `hanzo build` now uses
(no --platform-token). Drift confirmed live as z@hanzo.ai:
  /v1/apps            → 404      /v1/paas/apps         → 403 (was SuperAdmin-only)
  /v1/org/*/cluster   → 404      /v1/clusters          → 200 (already org-scoped)
                                 /v1/platform/projects → 500 (co-resident IAM off)

CLI (cli/platform.go, cli/commands.go):
  apps list/get   → GET /v1/paas/apps[/{app}]  (no client org filter — the board is
                    confined to the caller's org SERVER-side by the validated identity)
  deploy <app>    → POST /v1/paas/apps/{app}/deploy  (rolling restart; --env selects
                    the lifecycle namespace; org from identity, not the path)
  clusters list/get → GET /v1/clusters  (Visor-managed + BYO; org from identity)
Removed the TS-contract vestiges with NO Go backend: `apps sync` (the board is
live-computed), `clusters create/select/install-baseline/target` and `k8s target`
(DOKS provisioning + deploy-target selection are not implemented on the Go cloud).
Reshaped the Cluster DTO to the live visor clusterView (dropped dead Phase/Active/
operator/baseline fields). Platform client doc corrected: it CAN validate IAM tokens.

Backend (clients/paas): authorize the fleet board off ONE IAM identity, exactly like
/v1/runner (clients/platform/runner.go). guard now admits a validated principal who
is a SuperAdmin OR an OrgAdmin (principal.Validated + IsSuperAdmin || IsOrgAdmin —
the ONE verifier, unforgeable off-gateway), and each handler CONFINES a non-super
caller to the platform namespaces its own validated org owns (scopedNamespaces, keyed
on principal.Org — never a client header): a SuperAdmin sees the whole fleet, an
OrgAdmin only its own org (empty board / clean 404 otherwise), so a tenant admin can
never observe — or restart — another org's, or a platform, app. `?org=` cannot widen
the view (confinement is at the namespace scan, before the filter).

deploy is now a real zero-downtime ROLLING RESTART (the kubectl-rollout-restart
mechanism: stamp the pod-template hanzo.ai/restartedAt annotation) instead of the
409-refuse. It never changes the declared TAG (that stays a git commit, the one thing
Hanzo CD's selfHeal reconciles), so there is no drift to revert — the honest,
GitOps-compatible "redeploy this app". resolveTarget split so the machine release
path (release.go) keeps the full scan; the identity-scoped deploy/getApp use the
caller's authorized namespaces.

SECURITY: this broadens auth on a control-plane surface (new mutating restart path).
Mirrors blue's IAM-admin pattern; flag for red. TDD: 12 new paas cases (role gate,
tenant confinement on list/get/deploy, forged-org cannot widen, rolling-restart lands
the annotation, foreign-org 404 + no mutation) + the CLI path/DTO tests, all green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 16:23:03 -07:00
zeekayandhanzo-dev 20320d27a3 fix(platform): close RED H1/H2/M1 on the /v1/runner build path
RED re-review of the unify-infra PaaS-auth flip found 2 HIGH + 1 MED on the
privileged build endpoint. Fixes:

H1 (borders CRITICAL) — cross-org supply-chain push. imageAllowed() permitted
ghcr.io/{hanzoai,luxfi,zooai}/ regardless of the caller's validated org, so any
org-admin could overwrite another brand's prod image via the shared push cred.
Bind the image's registry-org to the caller's org (orgRegistryNamespaces map);
only a real SuperAdmin may cross. The machine (fabric) token keeps full
owned-registry latitude. Cross-org now 403; same-org 202.

H2 — privileged rootful buildkit in the main platform namespace with the shared
3-org push cred. buildJobSpec is now ROOTLESS (moby/buildkit:*-rootless, uid 1000,
no privileged, no privilege-escalation, caps dropped, --oci-worker-no-process-
sandbox), runs in a DEDICATED isolated namespace (CLOUD_PLATFORM_BUILD_NS default
→ hanzo-build, off the platform ns), and mounts ONLY the target org's push
credential (push-<namespace>), never the shared kaniko-ghcr. Node-pool taint +
automountServiceAccountToken:false retained.

M1 — `image` bypassed validateBuildInputs → buildkit --output attribute
injection (ghcr.io/hanzoai/x,registry.insecure=true). Added validateImageRef
(strict single OCI ref, rejects comma/space/quote/newline/'='), folded into
validateBuildInputs and enforced early at the handler.

I2 — the identity validator now fail-closes on an empty resolved issuer OR
audience set instead of silently disabling that axis; issuerAllowed denies on
an empty trusted set.

TDD: cross-org 403 + same-org 202 + SuperAdmin cross-org + orgless-403 +
image-injection-reject + rootless/scoped-cred spec + empty-trust-set-deny all
green (pure-Go, as prod ships).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 16:16:54 -07:00
hanzo-dev 23cce4635b fix(dns): close double-encoded traversal in the /v1/dns path guard
The prior prefix guard checked fasthttp's URI().Path(), which decodes only ONE
layer of percent-encoding. A DOUBLE-encoded traversal survives that one decode as
a literal %2e/%2f that still KEEPS the /v1/dns/ prefix -- so the prefix check
passes, cloud forwards base + /v1/dns/%2e%2e/admin, and the upstream decodes the
second layer to /v1/admin. Proven bypasses: /v1/dns/%252e%252e/admin,
/v1/dns/%252e%252e%252fadmin, /v1/dns/..%252fadmin.

After the prefix check, also refuse any once-decoded path that still carries a `%`
(a still-encoded byte => the client double-encoded) or `..` (residual traversal).
Neither appears in a legitimate DNS-API path -- zone labels are DNS names /
punycode xn--, and the query string (checked separately) is unaffected. Fail
closed 400 before a byte leaves cloud.

Also relay the upstream Location header so a 3xx -- never followed, per
CheckRedirect -- passes back verbatim (status + Location) as the comment claims,
rather than being silently dropped.

Regression: the escaped-path test gains the 3 double-encoded vectors (each refused
400 with 0 upstream bytes), plus a redirect test proving an upstream 302 is not
followed and its Location relays verbatim. 9 tests green.
2026-07-18 15:40:42 -07:00
hanzo-dev 9dfce8dc90 merge(cloud): per-org /v1/cloudflare asset plane
Adds the clients/cloudflare subsystem — Pages+Workers wired, R2/KV/D1 stubbed —
gated by the org-comingling guardrail and org-admin mutation check; wired into
apps/apps.go. Red-reviewed SHIP: comingling guardrail + org-admin mutation gate
verified PASS, 12/12 tests green, isolation core intact.
2026-07-18 15:29:47 -07:00
hanzo-dev fe34402e0b fix(dns): lock the /v1/dns forward head to its own prefix; don't follow upstream 3xx
The forward head built the upstream target from uri.Path(), which is NORMALIZED
and percent-decoded. Fiber matches the /v1/dns/* wildcard on the RAW path, so a
dot-segment or encoded-dot traversal (/v1/dns/../../admin/secrets,
/v1/dns/..%2f..%2fadmin, /v1/dns/../../../metrics) still routed to the handler
while the normalized path escaped the prefix -- letting the caller drive the
WHOLE path on the DNS host. Contained today only because the upstream 404s
unknown paths; a latent path-scope escape the moment :8443 serves anything else.

Guard the normalized path fail-closed BEFORE building the target: require it to
be exactly /v1/dns or under /v1/dns/, else 400 and forward nothing. Because the
path is already normalized, every traversal/encoded-dot escape fails this check.
Correct the comment that wrongly claimed the path was locked by the route match
(the host-pinning claim was, and stays, true).

Also stop the shared http.Client from following upstream 3xx (CheckRedirect =>
http.ErrUseLastResponse) so redirect responses pass through verbatim and a 3xx
can never silently re-target the request onto another host or path.

Regression test proves fail-closed: each escaped path is refused (400) and 0
bytes reach the upstream. Existing 7 tests stay green (8 total).
2026-07-18 15:29:39 -07:00
hanzo-dev e138fa60b5 fix(cloudflare): red fixes — comingling guardrail, org-admin mutation gate, stored-account resolution
Addresses Red's FIX-THEN-SHIP findings:
- HIGH: stamp X-Hanzo-Org (the served org) on every /v1/cloudflare response so a
  per-org caller can detect a pinned/comingled org. The platform Pages client asserts
  it equals the requested org and fails LOUD if a non-org-switch-capable service token
  made the identity boundary pin X-Org-Id to the token's own owner — no silent
  cross-tenant read/write.
- MEDIUM: gate mutations (POST/PUT/DELETE) on principal.IsOrgAdmin via a new authWrite
  front door (reads stay validated-org-only), parity with the AdminOnly connector. A
  non-admin is refused before any KMS token read and never reaches Cloudflare.
- LOW: resolveAccount now prefers the account captured at connect time
  (integrations.ConnectionFor ExternalID), falling back to live /accounts discovery
  only when none is stored — no per-call round-trip, deterministic for multi-account
  tokens.

Tests: +TestResponseStampsActingOrg, +TestMutationRequiresOrgAdmin,
+TestStoredAccountSkipsDiscovery; existing mutation tests drive as org admin. 12/12
pass, -race clean.
2026-07-18 15:28:34 -07:00
hanzo-dev f9b0b0ef64 feat(cloudflare): per-org /v1/cloudflare asset plane (Pages+Workers wired, R2/KV/D1 stubbed)
New cloud subsystem clients/cloudflare exposing /v1/cloudflare/{pages,workers,r2,kv,d1}/*,
sibling to hanzodns's /v1/dns. It reads each org's KMS-sealed Cloudflare token in-process
through the integrations custody seam (integrations.TokenFor) and proxies to the Cloudflare
API v4 with the cfDo shape reused verbatim from hanzodns — no global env token, no
bearer-relay hop (that is only hanzodns's separate-process need).

Tenant isolation: org is derived ONLY from the validated principal (principal.Org); the KMS
token path is keyed on that org, so cross-org token reach is structurally impossible and an
unvalidated request fails closed (403). Pages (project CRUD, deploy, custom-domain add/delete)
and Workers (script put/list/delete via multipart module upload, workers.dev subdomain, zone
route bind/list/delete) are wired; R2/KV/D1 ship typed provider methods + routes that answer
an honest 501 (never a fake success).

Appends the Workers connector scopes (Account:Workers Scripts:Edit, Zone:Workers Routes:Edit)
for the now-callable capabilities and wires the subsystem into apps.Wire after integrations.
2026-07-18 15:28:34 -07:00
hanzo-dev e6d93ee637 deploy: clean API paths — /v1/deploy/<resource>, no /api/ prefix, no inner /v1
House rule: no extraneous /api/, just /v1/. The projection API moves from
/v1/deploy/api/v1/* → /v1/deploy/<resource> (settings, session/userinfo, version,
account/can-i, applications, applications/{name}/resource-tree, .../{sync,rollback}).
This IS the deploy API now — the superseded native /v1/deploy/{applications,:name/*}
routes are removed (their readers stay, reused by the projection). health +
reconcile unchanged. Guard test updated.
2026-07-18 15:05:11 -07:00
hanzo-dev b84bfa1ca3 feat(dns): forward /v1/dns/* to the DNS control plane under the caller's own bearer
console.hanzo.ai serves the DnsModule but cloud held no /v1/dns head, so
console.hanzo.ai/v1/dns/* 404'd and the dashboard showed empty zones. Add a thin
forward head (clients/dns) that relays each /v1/dns/* request to the DNS control
plane (HANZO_DNS_URL, default the in-cluster coredns-hanzodns service), preserving
verb, path, query, body, status codes and error bodies.

Isolation is bearer-relay: the head forwards the caller's OWN validated bearer
(cloud.CallerBearer) plus the server-validated X-Org-Id, substituting NO service
credential, so the DNS plane's own per-org authorization still holds and a caller
in org A can reach only org A's zones. Fail-closed: no validated principal => 403,
before any byte leaves cloud. It builds a fresh upstream request, so no inbound
header is blindly relayed; the upstream host comes only from env (no SSRF).

Decomplect the token resolution the identity boundary and this relay both need
into one callerToken helper (validatedPrincipal now delegates to it) and expose
CallerBearer for the relay; an opaque API key is never relayed as a bearer.
2026-07-18 14:56:20 -07:00
hanzo-dev ec7b68441d merge(cloud): /v1/deploy is API-only — the FE moved to the hanzoai/spa cd-ui App
The monochrome dashboard now serves at cd.hanzo.ai/ (root, base-href /) from the
cd-ui App CR (hanzoai/spa); cloud keeps ONLY the IAM-gated projection API at
/v1/deploy/api/*. Drops the go:embed FE + the deploy-ui-embed Dockerfile stage.
The FE is no longer /v1/-prefixed and no longer baked into the money binary.
2026-07-18 14:26:49 -07:00
hanzo-dev 9102deae8d deploy: drop the FE from the money binary — /v1/deploy is API-only
The monochrome dashboard SPA now ships as the hanzoai/spa-based cd-ui App CR
served at cd.hanzo.ai/ (base-href /); cloud keeps ONLY the IAM-gated projection
API, moved from /v1/deploy/ui/api/* to /v1/deploy/api/* (same-origin with the
SPA). Removes the go:embed dashFS + static serve (dashStatic/serveDashIndex) +
webui/dist + the deploy-ui-embed Dockerfile COPY stage. Guard test updated to the
/v1/deploy/api/* routes (still 403 without SuperAdmin). RED invariant holds — the
API terminates in cloud behind IdentityMiddleware + the guard.
2026-07-18 14:15:07 -07:00
zeekayandhanzo-dev ff7c26c882 feat(cli): hanzo build owner/name shorthand → GitHub https URL
The platform build muscle (launchDirectBuild) clones an https git URL; the CLI
sent the bare `owner/name` positional verbatim, so `hanzo build luxfi/wallet`
failed server-side with "repo.url must use https". normalizeRepoURL expands a
bare owner/name to https://github.com/owner/name (the host for every
hanzoai/luxfi/zooai repo) and passes an explicit URL / scp-style remote through
untouched. Test: TestNormalizeRepoURL. Completes the IAM-login dogfood:
`hanzo build luxfi/wallet ... --sha <full> ...` now 202s + launches the build.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 13:51:21 -07:00
zeekayandhanzo-dev 6348531d7d sites: org-scope published host + CI guard against zen streaming regression
Publish routing is now org-scoped: a project publishes to
<slug>.<org>.<apex> (e.g. myapp.maxpower.hanzo.app) instead of the flat
global <slug>.<apex>. The slug namespace becomes per-org — two orgs can
own the same slug and their sites can never collide or shadow one another.

- deploy.go: siteHost(org,slug)=<slug>.<org> is the ONE bound/resolved key;
  onPublish binds it; siteURL renders https://<slug>.<org>.<apex>.
- sites.go siteSlug: accept the two-label host <slug>.<org>.<apex>, validate
  both labels (slug non-reserved), return <slug>.<org> as the resolve key so
  bind and resolve agree. Org isolation is now STRUCTURAL in the hostname.
- store unchanged: site_hosts already keys on arbitrary full host strings
  (custom-domain path proves exact full-host ResolveHost match).

containment.yml: add a required "zen streaming-fix floor" check that fails
any PR/push whose effective github.com/hanzoai/zen is below v1.4.1 (the
first release carrying the SSE body-close fix, commit 50328b8). A stale
branch that reverts go.mod's zen pin to v1.4.0 can no longer silently
re-break streaming (empty SSE completions) — the durable root-cause guard.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 13:49:05 -07:00
hanzo-dev f6ab219ba1 feat(admin): thin audited credit-grant relay at POST /v1/admin/credit-grants
The one admin mint surface. SuperAdmin-only (core.Guard); forwards verbatim to
commerce's already-mint-gated POST /v1/billing/credit-grants (middleware.Mint →
PlatformOnly) via COMMERCE_SERVICE_TOKEN, scoped to the target org, and writes one
tamper-evident audit record. Commerce stays the sole credit-grant ledger — no
in-process mint. NOT deployed; for red review (mint surface).
2026-07-18 13:43:34 -07:00
zeekayandhanzo-dev 0d79eeb1e0 feat(cli,platform): unify PaaS auth on IAM — one login authorizes build/deploy/apps
A plain `hanzo login` (IAM) now authorizes every PaaS control-plane op with no
separate --build-token / --platform-token. ONE identity, org+role scoped.

CLI (cli/cli.go): Env.buildToken() and Env.platformToken() fall back to the IAM
access token as the FINAL resort (precedence unchanged above it: flag > env >
credential-store service token > IAM login). So after `hanzo login` the CLI sends
the IAM JWT as the platform bearer. "No token" errors now point at `hanzo login`
and fire only when there is ALSO no IAM login. Tests: added
TestBuildTokenFallsBackToIAM / TestPlatformTokenFallsBackToIAM (precedence
preserved — a dedicated token still wins).

Platform (clients/platform/runner.go): /v1/runner (build-enqueue) — the one
control-plane endpoint that ignored identity — now accepts EITHER the shared
build-callback token (machine path: git-push, self-release, operator; constant-time,
unchanged) OR a validated IAM principal who is an admin (principal.IsSuperAdmin ||
principal.IsOrgAdmin over principal.Validated). Both bounded by the SAME
owned-registry allowlist, so identity never widens the image boundary. Release
self-publish stays machine-token-only. IAM builds are org-attributed to the caller's
VALIDATED org and refuse a foreign organizationId unless SuperAdmin. Reuses the ONE
identity verifier (SanitizeIdentity mints unforgeable X-User-* from the verified JWT)
— no parallel JWT crypto. deploy/apps were already IAM-authorized via the tenant()
boundary. Tests: 7 new IAM cases (admin launches, non-admin 403, forged-no-user 403,
disallowed-image 403, foreign-org 403, release 403) + corrected fail-closed 403.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 13:22:37 -07:00
zeekayandhanzo-dev 783e16ebd0 fix(cloud): re-pin zen v1.4.2 — restore the SSE stream body-close fix
The argo/gitops merge db0957b (v1.801.77) resolved the go.mod conflict to its
stale second parent (zen v1.4.0), silently reverting the v1.4.1 bump landed at
v1.801.76. v1.4.0 still carries the serve() `defer resp.Body.Close()` race that
empties every streamed completion (200 with a 0-byte body) — which broke every
hanzo.app builder stream. Re-pin to zen v1.4.2 (the body-close fix + reasoning_content
passthrough regression pin) and thinking v0.1.1 (reasoning default). Streaming
now forwards every chunk, including delta.reasoning_content.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 12:55:21 -07:00
hanzo-dev a404cb1f4a merge(cloud): embed the monochrome ArgoCD UI (ghcr.io/hanzoai/deploy-ui-embed) into /v1/deploy/ui
The deploy-ui-embed image is published; cloud's Dockerfile now COPYs its /dist
into clients/deploy/webui/dist (go:embed). release.yml builds a cloud image that
serves the REAL monochrome dashboard at /v1/deploy/ui instead of the fallback.
2026-07-18 12:46:52 -07:00
hanzo-dev 4c0be6271c cloud: embed the monochrome ArgoCD UI bundle (ghcr.io/hanzoai/deploy-ui-embed) into clients/deploy/webui/dist
Mirrors the console-embed stage: FROM the prebuilt deploy-ui-embed image, COPY
/dist -> clients/deploy/webui/dist (go:embed source for /v1/deploy/ui). GATE: do
NOT merge until ghcr.io/hanzoai/deploy-ui-embed:latest is published (else the
build cannot pull the base). Until merged, the money binary serves the fallback.
2026-07-18 12:43:17 -07:00
hanzo-dev 34d97820b3 merge(cloud): deploy dashboard RED fast-follows (guard test + health hardening) 2026-07-18 12:40:51 -07:00
hanzo-dev a8443e1f2a deploy: RED fast-follows — guard table-test (LOW-2) + drop raw error from public health (INFO-1)
LOW-2: TestDeployRoutesRequireAdmin asserts every /v1/deploy(/ui) route 403s
without X-User-IsAdmin and passes with it (health stays public) — guards against
a future unguarded-route refactor.
INFO-1: the unauthenticated /v1/deploy/health path reports booleans only; the raw
k8s error (apiserver/RBAC detail) is logged server-side, not returned.
LOW-1 (CSRF): verified no-op — the IAM session cookie is SameSite=Lax AND the
ambient cookie->JWT bridge is same-origin-gated (sessionBridgeSameOrigin), so a
cross-origin CSRF POST gets no identity and the deploy guard 403s.
2026-07-18 12:40:50 -07:00
hanzo-dev e1e7315457 merge(cloud): ArgoCD monochrome dashboard via App-CR projection at /v1/deploy/ui
Serves the full ArgoCD React UI fed a read-projection of operator App CRs shaped
as v1alpha1 Applications — no argocd api-server/repo-server/redis/stored CRD.
SuperAdmin-gated; IAM owns identity at the edge. Money binary builds green;
projection render tests pass. Real monochrome bundle is a CI artifact (make
deploy-ui / deploy-ui-embed image); fallback shell until that lands.
2026-07-18 12:21:56 -07:00
zandGitHub 32d7c32aea docs(llm): document /v1/deploy GitOps plane (quality pass) 2026-07-18 12:20:20 -07:00
hanzo-dev c196cb9c4a docs(llm): document the /v1/deploy GitOps plane + embedded gitops-engine 2026-07-18 12:20:06 -07:00
hanzo-dev d23f8342c9 deploy: make deploy-ui builds the monochrome bundle into webui/dist (gitignored)
CI story for the dashboard bundle, mirroring make webui: DEPLOY_DIR=<hanzoai/deploy
rebrand/hanzo-monochrome> yarn build -> clients/deploy/webui/dist (go:embed). Only
the fallback index.html + .gitignore are tracked; the real 43MB bundle is
build-time-only. Money binary builds green with the real bundle embedded.
2026-07-18 12:19:40 -07:00
hanzo-dev a58def8a15 deploy: ArgoCD monochrome dashboard via App-CR projection at /v1/deploy/ui
Serves the full ArgoCD React UI fed a READ-PROJECTION of operator App CRs shaped
as v1alpha1 Applications — NO argocd api-server, NO repo-server, NO redis, NO
stored Application/AppProject CRD. projection.go maps App CR -> Application +
resource-tree (reusing the native readers/engine health). dashboard.go
reimplements the UI's api-server subset (settings/userinfo/version/can-i +
applications list/get/resource-tree + sync/rollback->App-CR reconcile) + serves
the go:embed'd monochrome bundle with base-href rewrite. SuperAdmin-gated; argocd
auth disabled (IAM owns identity at the edge). Projection render tests green.
UI bundle is a CI artifact (committed fallback shell; make deploy-ui overwrites).
2026-07-18 12:19:40 -07:00
hanzo-dev b831d76649 chore(cloud): vendor hanzoai/ai v1.824.2 — real model names for super-admin platform view
v1.824.2 unmasks the router-stats model ids (arm-N → real names like zen5-coder /
opus-4.8) for the PLATFORM scope when the caller is a super-admin of the own brand;
every other caller keeps the arm-N privacy masking. So the world.hanzo.ai admin view
(Routing Throughput / Enso arms) shows actual models instead of "Enso arm 2".
2026-07-18 12:15:04 -07:00
hanzo-dev ffc01f28ea fix(cloud/visor): fleet surfaces DO droplets via registry+live-DO union
world's admin fleet (GET /v1/machines -> listMachines) sourced machines only
from Visor's registry (/v1/get-machines), so DigitalOcean droplets that were
provisioned but not (yet) in the registry never appeared -- DO nodes were
entirely missing from the fleet.

Source the managed-machine set as the deduped UNION of the registry AND
Visor's LIVE DO reseller list (GET /v1/machines -> ListComputeMachines ->
service.ListOrgMachines, the live Droplets.ListByTag(orgTag)). Dedup is by
provider id OR name; the registry entry wins a collision so its enrichment/
masking is preserved. One helper (managedMachines) now feeds listMachines,
listGPUs and the /v1/fleet board so all three agree on which machines exist,
not just how they normalize. BYO fold unchanged; only machines Visor actually
returns are surfaced (nothing fabricated).
2026-07-18 12:13:48 -07:00
z fac09ffaa6 billing: metering client honors METERING_TEST (safe test-mode canary/staging)
buildMeteringClient ignored the documented METERING_TEST env, so the metering client
was ALWAYS live (c.test=false) — a staging/canary could not route debits to the
sandbox books, and the usage-cap smoke would have moved real money. Now METERING_TEST=true
sets Config.Test, so fin.RecordUsage writes the TEST finance books and the cap read
(org.TestMode via SQUARE_ENVIRONMENT=sandbox) sees the SAME test books. Unset in prod
= live, unchanged.
2026-07-18 12:13:31 -07:00
z 3e61401ebf cap: enforce + alert on the FINANCE ledger (where the unified binary records usage)
The spend cap read commerce's transaction store, which the co-resident cloud binary
leaves EMPTY (usage is recorded via fin.RecordUsage on the finance ledger) — so in
prod the cap summed 0 and never enforced, and the alert never fired. This wires the
cap onto the ledger prod actually writes, ORG-WIDE (the finance Entry carries no
scope; per-scope is a follow-up):

- sqlstore.SumByKindSince: additive read-only aggregate (kind + created_at index,
  18-decimal TEXT folded in Go) — no Entry schema change.
- finance.SumUsageSince: the org's metered usage (cents) since a cutoff, deposits
  excluded, sandbox books for a test org.
- finance.SetUsageHook: dependency-inverted post-debit seam (finance never imports
  commerce) the cap alert fires through.
- apps/commerce.go: SetPeriodSpendReader(financePeriodSpend) so AuthorizeSpendCap
  reads finance spend since the UTC month start, and SetUsageHook(fireCapAlert) so a
  finance debit fires the org's spend-alerts on the same crossing.

Composes the commerce policy/CRUD/promo/admin/ancestor-fix (commerce
v1.49.1->v1.49.2 injection seam) — a targeted host re-wire, not a redo.
2026-07-18 12:07:10 -07:00
hanzo-dev 8d84734984 deps: commerce v1.49.0->v1.49.1 — real subscription tier derivation
Completes the Enso per-tier gate: ai v1.824.1 already enforces min_tier at the
family pipe + auto-router; this bumps the co-resident commerce so /v1/billing/tier
returns the caller's REAL plan (was stubbed always-Free). Fail-open on uncertainty.
2026-07-18 11:43:21 -07:00
zandGitHub db0957b2b9 merge(cloud): embed argo gitops-engine under /v1/deploy — reconcile + RED HIGH-1 prune fuse (inert: DEPLOY_ENGINE_ENABLED off) 2026-07-18 11:27:44 -07:00
hanzo-dev 8f11c84800 chore(deploy): go mod tidy after rebase onto main (union: main deps + gitops-engine v0.7.2 + k8s 0.35.3 staging) 2026-07-18 11:27:25 -07:00
hanzo-dev 8cb8f6625f chore(cloud): vendor hanzoai/ai v1.824.1 — Enso flywheel boots from Mount
v1.824.1 boots StartRouterTrainer + StartRouterProbe from ai.Mount, so the flywheel
runs in the deployed (embedded-in-cloud) service, not just the standalone aid binary.
Both still self-gate on their env flags; universe sets ROUTER_TRAIN_ENABLED=1 to turn
training on. Also carries the retrain-timeline fix (retrains now count).
2026-07-18 11:27:15 -07:00
hanzo-dev 51f0c1cbd4 deploy: prune-safety fuse (RED HIGH-1) on the engine reconcile
Five guards before any deletion: (i) refuse an empty desired set; (ii) dry-run
sizes the prune set + a count/ratio fuse (DEPLOY_ENGINE_PRUNE_MAX default 10,
_RATIO default 0.20) refuses a mass prune; (iii) WithPruneConfirmed gates prune
on the fuse passing; (iv) PVC + KMSSecret are excluded from prune entirely (data
anchors, irreversible); (v) parseManifestDir walks recursively so a nested
manifest is never silently dropped (which prune would read as a deletion).
prune stays off by default (DEPLOY_ENGINE_PRUNE).
2026-07-18 11:26:02 -07:00
hanzo-dev 0c5dbcaaac deploy: pin gitops-engine to hanzoai/deploy/gitops-engine v0.7.2 (no replace)
Drops the filesystem replace => ../deploy/gitops-engine. The fork's engine module
was renamed to its real repo path (github.com/hanzoai/deploy/gitops-engine, tag
gitops-engine/v0.7.2) so cloud requires it as a normal pinned version — CI builds
the money binary with NO sibling checkout, NO argoproj alias. tidy + scoped build
green over SSH.
2026-07-18 11:26:02 -07:00
hanzo-dev 1180fe77a1 deploy: embed argo gitops-engine in-process under /v1/deploy (reconcile half) 2026-07-18 11:26:02 -07:00
hanzo-dev 7c02008ade ci(release): auto-promote the proven tag into universe crs/cloud.yaml
Every merge to main builds + smoke-tests + tags a proven image, but nothing
recorded that tag as the desired state Hanzo CD deploys, so api.hanzo.ai sat on
a stale pin (v1.801.71) while proven images (…72-…75) never rolled. The old
image-update.yml deploy hub was deleted in the Hanzo CD cutover; a direct CR
patch is reverted by ArgoCD selfHeal.

Add a promote job that, after the tag receipt, bumps spec.image.tag in
hanzoai/universe crs/cloud.yaml and commits deploy(cloud): <tag> — the SAME
yq-bump the hanzoai/ci reusable does for every other service. The universe-crs
ArgoCD Application (automated sync + selfHeal) then reconciles it to the cluster.
No hand-dispatch, no hand-edit.
2026-07-18 11:02:47 -07:00
d9bfa032ea fix(cloud): zen v1.4.1 (SSE body-close race) + thinking v0.1.1 (reasoning default)
Fixes empty streaming completions for zen5* (hanzo.app builder P0):
- zen v1.4.1 stops serve() from closing the upstream body before fiber's lazy
  SendStreamWriter drains it (every SSE completion was truncated to a 200 + empty body).
- thinking v0.1.1 makes glm-5.2/deepseek Off send reasoning_effort:none, so zen5-coder
  streams the answer immediately instead of a long silent content:null reasoning preamble.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 10:49:51 -07:00
z e2acfd2a8f admin+metering: SuperAdmin usage-cap + promo control plane; fix net/http spend_cap→402
Adds the /v1/admin control plane admin.hanzo.ai drives, twinning /v1/admin/flags:
  - /v1/admin/promos (GET/PUT, core.Guard SuperAdmin) → commerce /v1/platform/promo:
    configure the admin-controlled plan promo (percentOff/start/end/plans/active).
  - /v1/admin/spend-caps (GET/POST/PATCH/DELETE, core.GuardScoped) → commerce
    /v1/billing/spend-alerts with X-Org-Id: oversee/override ANY org’s usage caps
    (SuperAdmin via ?org=; a scoped admin hard-pinned to their own — the escalation
    line). Reuses the customer’s OWN spend-alert rows, no parallel model.
commerce.Forward is the ONE service-token seam these ride, relaying commerce’s own
status so a 400/403/404 surfaces honestly instead of masking as success.

Fixes clients/metering/middleware.go defaultOnDenied: a FUNDED caller over a
per-scope spend cap now maps to a DISTINCT 402 spend_cap_exceeded (errors.Is), not
the 503 it fell through to — parity with the zip-native denyVerdict, so any product
on the net/http middleware surfaces the same honest verdict.
2026-07-18 09:56:58 -07:00
hanzo-dev 4bc9f99f3d build(deps): bump embedded luxfi/kms v1.11.8 -> v1.12.4
Brings the ACTIVE Hanzo KMS custody plane (api.hanzo.ai/v1/kms/*, served by the
cloud-embedded luxfi/kms per HIP-0106) to the latest v1.x. keys (v1.4.1) and
crypto (v1.20.2) already latest; luxfi/mpc stays out of the graph (threshold
signing is a wire-coupled external daemon, not a linked module). v1.12.4 verifies
against the public sumdb; clients/kms + cmd/cloud build green.
2026-07-18 09:52:56 -07:00
z 88f27d7305 fix(cloud/fleet): never surface a GPU slug's VRAM as system RAM
toMachineView's memGB fallback read the integer before "gb" out of any
size slug. On a DO GPU droplet the slug's gb is VRAM (gpu-h100x8-640gb ->
640 GB VRAM), not system RAM, so a GPU node missing its upstream memSize
would render 640 GB of "system memory" -- a misleading number.

Guard the fallback with the GPU check already needed for v.GPU: reuse the
single gpuSpecOf(slug) call (spec, isGpu) and apply the slug's gb figure
only when !isGpu. Real m.MemSize still takes precedence for every provider,
GPU nodes included, so a GPU machine that reports its true RAM is
unaffected -- only the VRAM-as-RAM fallback is suppressed.

Table tests: a gpu-h100x8-640gb slug with empty MemSize yields Mem=="" (not
"640 GB") while still resolving GPU=="H100", and the same slug with a real
MemSize=="1920gb" reports "1920 GB".
2026-07-18 09:43:47 -07:00
z 618eafc2bd fix(cloud/fleet): map system memory + parse DO size-slug vCPU/RAM
The fleet view (world.hanzo.ai cloud variant) renders machines from
cloud's /v1/machines -> listMachines -> toMachineView. Two honest-data
gaps left system RAM and DigitalOcean vCPU counts blank:

1. System memory was never surfaced: machineView had no memory field and
   toMachineView never read the upstream memSize, so every provider's RAM
   column rendered empty.
2. DO vCPU was dropped: toMachineView filled vcpu only when CpuSize parsed
   as a bare integer, but DigitalOcean reports size SLUGS (s-4vcpu-8gb),
   so strconv.Atoi failed and vCPU showed nothing.

Fix:
- Add MemSize to visorMachine (upstream already sends it; it was simply
  unmapped) and Mem to machineView.
- parseSizeSlug pulls the integer before "vcpu" and the integer before
  "gb" out of a size slug (s-4vcpu-8gb -> 4,8; g-8vcpu-32gb -> 8,32).
- normalizeMem renders "N GB" only for trustworthy inputs (explicit
  gb/gib, explicit mb converted with rounding, a bare integer as MB when
  >=1024 else GB) and returns "" for anything ambiguous -- never a
  fabricated number.
- toMachineView keeps the Atoi(CpuSize) path and falls back to the slug's
  vcpu; sets Mem from normalizeMem(MemSize) and falls back to the slug's
  gb figure. The GPU-spec logic is unchanged.

Table tests cover the slug parser, the mem rounding, and the mapper
precedence (explicit values win, honest omission when neither yields one).
2026-07-18 09:37:45 -07:00
zandGitHub cf216f193f Merge feat/code-normalized-continue into main 2026-07-18 09:30:51 -07:00
antje d8c258e94d gpu worker: collect SaveGLB outputs — 3D meshes travel back to the library
collectOutputs read only the 'images' key, but SaveGLB publishes under '3d', so a
generated .glb never mirrored to the org library. Gather every saver's outputs
(images + 3d), so the studio 3D lane's mesh lands like an image or video render.
2026-07-18 09:27:56 -07:00
hanzo-dev c6c28fd9c3 feat(code): normalize continue across harnesses 2026-07-18 09:26:22 -07:00
hanzo-dev be4ae6a921 integrations: Cloudflare OAuth connect path alongside apikey (same KMS coordinate)
The cloudflare provider now offers a browser OAuth path in addition to the
shipped apikey path. /connect dispatches by request: a "token" key in the body
seals via apikey (verify-before-store, unchanged); its absence starts the
Authorization Code flow (confidential client, client_secret, no PKCE — the
framework's OAuth pattern) and the exchanged access token is sealed to the SAME
KMS coordinate (/orgs/{org}/integrations/cloudflare/api_token), so the DNS
provider layer is auth-method-agnostic.

Framework: connect dispatch is now capability-based (Verify and/or Authorize)
rather than Kind-only; Mount validates RedirectPath for any OAuth-capable
provider; bodyHasCredential picks the path. The OAuth leg gates on its own app
creds (Creds().ClientID) so a missing Cloudflare OAuth app degrades to an honest
503 without breaking the always-available apikey path.

Requires a registered Cloudflare OAuth app: CLOUDFLARE_OAUTH_CLIENT_ID/SECRET in
env, redirect https://api.hanzo.ai/v1/integrations/cloudflare/callback.
2026-07-18 09:14:07 -07:00
zeekayandhanzo-dev 998685c4fb rebuild(cloud): embed console-embed@sha-bd8a816 (casibase auth /v1/* fix + console per-project resources) + activate MCP builtin tool-plane (#292)
No Go change — this rebuild re-resolves the freshly-republished console-embed:latest
(console main bd8a81651) into the go:embed console served at console.hanzo.ai, and
ships builtin.go's auto '/v1 route → MCP tool' plane at /v1/tools/mcp (already in main,
newer than the deployed v1.801.69).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-18 08:57:15 -07:00
hanzo-dev c3e02036ba feat(connectors): OAuth/apikey connector plane (Anthropic, OpenAI, Copilot, device flow, refresh)
Preserve divergent connector work: verify-before-store connector types
(Anthropic, OpenAI, Copilot), device-authorization flow, token refresh,
connector registry/store, and integration/store/link plumbing.
2026-07-18 01:26:55 -07:00
hanzo-dev 2b6dbddf0c feat(channels): unified inbound channel ingest plane (envelope, pairing, policy, per-platform adapters)
Preserve divergent channel-ingest work: clients/channels package (envelope
normalization, pairing, delivery policy, Slack/Discord/Teams/Telegram
adapters, store), cmd/channels entrypoint, integration event-emit hooks,
and apps wiring.
2026-07-18 01:26:09 -07:00
hanzo-dev 6d42382aed fix(kms): unshadow the bare secrets-list route (/secrets/+ not /secrets/*)
The value routes registered the optional-greedy wildcard `/secrets/*`, which
fiber also matches with an empty tail — so the bare `GET .../secrets` list path
was answered by getSecret (400 "secret name is required") and listSecrets was
unreachable. Switch the getSecret/deleteSecret value routes to the required-
greedy `+` (one-or-more), so `/secrets` falls through to the exact list route
while `/secrets/<path>/<name>` still reads/deletes. reqWildcard reads the `+`
param.

Regression test list_route_test.go asserts the bare list path returns 200 with
a secrets array (was 400) and that value reads still work.
2026-07-18 01:19:23 -07:00
hanzo-dev 57b6ac109b integrations: Cloudflare apikey connector (verify-before-seal, org-admin gated)
Register Cloudflare as an apikey-kind connector on the /v1/integrations plane.
A customer-supplied scoped API token is verified live against Cloudflare's
GET /user/tokens/verify (must be status:active) before it is sealed into the
org's KMS namespace (/orgs/{org}/integrations/cloudflare/api_token); the
connection row holds only non-secret account metadata. connect/verify/disconnect
are org-admin gated from the validated principal (principal.IsOrgAdmin).

Extends the connector framework with the apikey credential seam shared by future
customer-credential providers: Provider.Kind/AdminOnly/Verify, VerifyInput,
connectByCredential (verify-before-seal, fail-closed), and the verify route.

Serves POST /v1/integrations/cloudflare/{connect,verify,disconnect} and
GET /v1/integrations.
2026-07-18 00:07:53 -07:00
z 305e7dd8d3 Merge feat/route-work-to-target: route coding run to chosen target machine 2026-07-17 23:32:54 -07:00
hanzo-dev a1074d0691 coding: verify + PR + close the session when a routed run completes
A routed run's machine pushes with its own credential and streams into the
session, but cloud still owns the completion — the integrity gate, the PR row, and
the session's terminal state (the machine never closes the session, so it was
staying "running" forever). Give a routed run the SAME cloud-side completion the
local keystone path runs after a sandbox push.

- completeChanged: the shared terminal for a run that reported changes — VerifyRef
  the pushed branch LANDED (fail-closed to a session error + no PR if absent), file
  the native PR, mirror done, close the session done. The local path (Run) now calls
  it too, so the two paths cannot drift.
- finalizeRouted: maps a machine's terminal report onto that completion — reported
  failure closes the session error (no PR), no-changes closes done (no PR), a changed
  push runs completeChanged. No secret crosses; cloud only reads the ref it can see.
- DeliverRoutedRunActivity runs the completion once, after a real report, on a
  cancel-immune bounded context, so a completed run is never re-executed by a retry.
  The completion seam is injected at the composition root (NewDispatcher), the same
  injected-seam shape index_on_push uses, so the free-function activity reaches the
  dispatcher's git/tracker/session seams without a global Dispatcher.
- RoutedRun carries Actor + AgentRef (cloud-side only, never sent to the machine) so
  the completion attributes the session close and files the PR with the right
  assignee.

Also document the mailbox's single-replica dependency at its definition (accepted,
inherited from cloud's KMS-lock replicas:1) with a future replica-aware note.

Tests: routed changed+verify -> PR filed + session done; verify fails -> no PR +
session error; no changes -> done no PR; reported error -> error no PR (verify never
runs); NewDispatcher wires the seam; the durable type bridge preserves attribution.
2026-07-17 23:13:07 -07:00
z 9922104692 Merge feat/kms-reseal-migration: CR-driven KMS re-seal migration tool (#79) 2026-07-17 23:10:37 -07:00
a44aaffbed auth: accept admin-console audience in the cloud JWT allowlist (#332)
The cloud already trusts hanzo-admin-guard (the admin surface) but not admin-console
(the admin console's own OIDC client), so a SuperAdmin token minted via admin-console
was rejected on /v1/admin with 'invalid audience' — forcing an awkward hanzo-admin-guard
detour. Add admin-console so the admin console's tokens work directly, matching
GATEWAY_ALLOWED_AUDIENCES which already lists it.

Co-authored-by: zeekay <z@hanzo.ai>
2026-07-17 23:03:19 -07:00
hanzo-dev 2936317959 docs: open cloud planes blueprint (HIP-0129)
Plane map with honest tiers in LLM.md: /v1/connectors custody (in flight), /v1/channels transport (planned, branch reserved), shipped planes named by package. Spec home HIP-0129; roadmap P1-P15 lives there.
2026-07-17 22:49:44 -07:00
zeekayandz d1f7667486 gateway: nest clients/gatewaypolicy → clients/gateway/edge (kill the compound)
"gatewaypolicy" is a compound (gateway+policy) and read as a second gateway
package. It is the ONE Gateway concern with clients/gateway — the per-org edge
policy STORE (OrgRPM ceiling + CORS + cache) that the /v1/gateway/config plane and
the package-cloud edge middleware both read.

They are two packages only to break a Go import cycle: clients/gateway imports root
cloud (cloud.Deps), and middleware_edge.go IS package cloud — so the store must be a
LEAF both can import. A flat merge cycles. Fix per the no-compound law: nest the leaf
UNDER gateway as clients/gateway/edge (edge.Policy/Store/New). One gateway namespace;
/v1/gateway/config surface unchanged; edge-middleware logic unchanged.

NOT redundant with the external hanzoai/gateway (KrakenD): that does coarse per-route
edge rate-limit + auth at ingress; this is per-AUTHENTICATED-org RPM (needs the decoded
token org), an app-level ceiling the edge proxy cannot compute. Different layer.

Pure rename (49/49, no logic change); full cmd/cloud binary links; gateway + gateway/edge
tests pass; gofmt/vet clean.
2026-07-17 22:47:51 -07:00
ee2cf3a11b flags: runtime flags resolve from /v1/flags only — drop redundant env gates (#331)
waitlist_* / public_signup / gateway_* are runtime flags; strip their Env: fallbacks so
they resolve from the /v1/flags DB engine → Default (single source of truth, flipped live,
no redeploy). Boot-time ReadOnly rows (subsystem_*, network_id_*) keep Env — that IS their
boot mechanism. Nothing read these env vars outside the flags engine (verified).

Co-authored-by: zeekay <z@hanzo.ai>
2026-07-17 22:46:51 -07:00
hanzo-dev 55fcaea0b7 agents/integrations: reach routed dispatch from the Slack trigger
Wire the load-bearing trigger so a coding run can be dispatched to a chosen
linked machine end-to-end. Extend the Slack coding grammar with an optional
routing prefix — code: <repo> on <machine> <task> — resolve <machine> org-scoped
(id or friendly label) and set Req.TargetID. An unknown or foreign machine is an
honest error, never a silent local fallback; an untargeted request is byte-
unchanged (repo <task>).

- agents.ResolveTarget: the ONE org-scoped id-or-label resolver, fail-closed, so a
  trigger surface turns 'on evo' into a target id without leaking another tenant's
  inventory.
- slack_coding: parseCoding yields (repo, target, task); a routed run skips the KMS
  agent-credential fetch (the machine authenticates with its own credential); the
  ack + result card report a routed run as queued-on-<machine>, followed live in
  mission-control, not a premature branch-pushed verdict.

Tests: ResolveTarget id/label precedence + cross-org not-found + unmounted fail-
closed; parseCoding on-prefix grammar (routing only when 'on' is the token after
the repo; 'on-call'/'only' untouched); routed result card is queued not done.
2026-07-17 22:42:59 -07:00
z 2aac986043 Merge fix/consensus-bump: luxfi/consensus v1.36.9 (unbreak force-moved checksum) 2026-07-17 22:33:25 -07:00
zeekayandhanzo-dev 141e417742 build(deps): bump ai → v1.822.3 — drop the last WqyJh audio-fork edges
cloud transitively pulled github.com/WqyJh/{go-cosyvoice,go-openai-realtime}
through ai v1.822.2 (the go-openai-fork release, which predated ai's TTS
switch to the hanzo-owned forks). ai v1.822.3 wires ai/tts onto
github.com/hanzoai/go-cosyvoice + go-openai-realtime, so tidy drops both WqyJh
edges from cloud's graph. cloud now pulls ZERO third-party OpenAI-lineage:
WqyJh 0, sashabaranov 0, ClickHouse 0. Single datastore sql registrant
(hanzo-ds/go). Builds clean.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-17 22:29:42 -07:00
hanzo-blue 173ec3a0a8 docs(kmsreseal): runbook SCOPE = exact per-host dry-run counts (#79) 2026-07-17 22:26:48 -07:00
hanzo-blue 4d63dde788 docs(kmsreseal): operator LLM.md — subcommands, dry-run findings, gated cutover (#79)
4-host map, G1 delta (78-union), G5 boot-cycle verdict (safe: direct master key),
seeding wedge-risk prerequisite. Dry-run only; cutover CTO-gated.
2026-07-17 22:25:33 -07:00
z 1d2e93a45e feat(admin): fleet-aggregate billing endpoints (metrics + invoices + subscriptions)
admin.hanzo.ai's SaaS-metrics/Invoices/Subscriptions pages were placeholders
awaiting cross-org /v1/admin/* endpoints. Add them as super-admin (core.Guard)
fleet-aggregate readers over the existing commerce billing engine:

  GET /v1/admin/metrics        — SaaS god-view: MRR/ARR/net-new/churn/active-subs/
                                 paying-customers/plan-mix/top-customers/recent.
                                 Single S2S proxy — commerce /v1/metrics/saas is
                                 already a cross-org aggregate (same gate finance
                                 Costs uses: RequirePlatformAdmin→IsServiceToken).
  GET /v1/admin/invoices       — cross-org invoice list; fan core.ListOrgs out
  GET /v1/admin/subscriptions  — cross-org subscription list; per-tenant reads
                                 merged (identical to revenue.go's fan-out).

Honest degradation: a failed per-org read contributes no rows, never fabricated.
go build ./clients/admin/... green, gofmt clean. Pairs with admin operator UI
(feat/admin-billing-fleet-ui).
2026-07-17 22:23:47 -07:00
zeekayandhanzo-dev 2c6f900aa2 refactor(go-openai): import the hanzoai/go-openai fork directly, drop the replace
cloud/clients{,/agent} used sashabaranov/go-openai only via a 'replace =>
hanzoai/go-openai' — which does not propagate to cloud's own consumers, so
gateway/iam/etc. each had to copy it. Now the fork declares its own module
path (github.com/hanzoai/go-openai v1.41.0): require it directly. Bumps the
lockstep fork adopters — ai v1.822.2, agent v0.1.3 — so the hz.Mount Completer
boundary shares ONE openai type set (was a hanzoai-vs-sashabaranov type
mismatch). No replace anywhere; upstream sashabaranov remains only as an
indirect dep of the go-cosyvoice TTS chain (owned next). cmd/cloud keeps its
single datastore sql registrant (hanzo-ds/go). Builds clean.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-17 22:11:47 -07:00
zandGitHub e655b848de Merge: cloud S3 client minio-go → hanzoai/s3-go (the one house S3 client)
7 files repoint minio-go v7 → hanzoai/s3-go (a byte-identical fork, package
minio, zero call-site churn); minio-go demoted to indirect. Red-verified:
presign + conditional-CAS byte-identical to the prior v7.0.100 dep, drop-in.
Deploy-gate: live SeaweedFS CAS smoke (If-Match/If-None-Match/412).
2026-07-17 22:05:03 -07:00
hanzo-blue 7fc7dcf125 feat(kmsreseal): CR-driven KMS re-seal migration tool (#79)
Embeds the fleet KMS into cloud by re-sealing the ~125 KMSSecret-referenced
secrets from the legacy standalone (unsealed at rest) into cloud's embedded
/v1/kms (AES-256-GCM sealed per secret). Driven by the KMSSecret CRs — the
authoritative (org,path,env,key) manifest — not a raw store copy.

- inventory: pure CR parse/validate/dedup; handles explicit keys, folder-sync
  (empty keys[]), the env-default divergence (cloud refuses empty env), and
  malformed CRs (fail-loud, never silently dropped). Reuses cloud/clients/kms
  ValidSegment/ValidSubpath so a coordinate the store would reject is never built.
- reseal: per-CR org-bound auth (owner==projectSlug), GET standalone -> POST cloud
  (cloud seals). Idempotent upserts, re-runnable. Plaintext transits memory only,
  wiped after write; results carry coordinates + status, never values.
- verify: read-only SHA-256 hash-compare standalone-vs-cloud + org-isolation matrix
  (cross-org 403, no-principal 403) against the real cloud guard.
- preflight: cloud /v1/kms reachability + JWT-validation probes + offline G1 delta.
- runbook: the ordered, rollback-safe cutover (standalone stays read-only).

Tests: round-trip against cloud's REAL embedded /v1/kms in-process (real seal,
real guard) via a zip app.Fiber().Test transport adapter; seal-proof (no plaintext
on disk); wrong-org refusal; folder-sync via LIST; hash-mismatch detection;
isolation matrix. go test ./cmd/kmsreseal green.
2026-07-17 22:03:16 -07:00
zeekay 0a47ea327d policy: kill /v1/featuregate/mode alias + rename featuregate → admission
featuregate READ like a synonym for flags — the source of the "isn't this the
same thing?" confusion. It is not: flags is the Policy decide-ENGINE (/v1/flags);
this package is the request-ADMISSION gate that composes it one-way (host→service
registry + waitlist.<svc> mode read + Enforce middleware + IAM approval check).
Renamed to `admission` — the precise systems term for policy-gating requests
(k8s-style admission control) — which also dodges the gate/gateway/gatewaypolicy
name cluster. flags stays THE engine; admission is a thin one-way consumer.

Also kills the /v1/featuregate/mode compat alias entirely (route + Enforce exempt
entry + test): one route, /v1/flags/waitlist. No shim, no adaptor, no backwards
compat — per the one-and-only-one-way law.

flags engine surface unchanged. Build/vet green; admission tests + apps frozen-Wire
order test pass (admission holds featuregate's slot). Deeper Policy collapse
(authz/entitlements/gatewaypolicy → one engine) is a separate staged HIP-0127 pass.
2026-07-17 21:26:28 -07:00
hanzo-dev bc086c53cf agents/coding: route a coding run to a chosen target machine
When a coding run carries a targetId (a registered /v1/agents/targets
machine), enqueue it as a durable task addressed to that target on the ONE
embedded tasks engine instead of running it in the cloud sandbox. No target
keeps the local sandbox path byte-unchanged.

- mailbox: an in-process rendezvous between the durable RoutedRunWorkflow and
  the external machine that claims a run over HTTP; tenant + machine isolation
  is a property of the (org,target) key, not a check a caller can skip.
- routing: per-target claim key (a capability, stored only as a SHA-256 hash,
  constant-time verified) is the machine identity; a fail-closed liveness gate
  (online + a live runner) is the dispatch admission.
- claim/report HTTP surface (org bearer + X-Target-Key) lets a machine claim
  and complete only runs addressed to it.
- coding.Dispatcher gains a routed branch: open the session on the target,
  enqueue the durable RoutedRunWorkflow (no secret in the payload — the machine
  authenticates with its own credential), return queued; fail closed on an
  unavailable target or a failed enqueue, never fall back to local.

Tests: dispatch-to-target, no-target-local-unchanged, dead-target-fail-closed,
cross-machine/cross-org claim denied, mailbox isolation + claim race.
2026-07-17 21:26:04 -07:00
hanzo-dev 83ab5130db Route the S3 object plane through the hanzoai/s3-go client
Swap the S3 client in the 7 direct importers from github.com/minio/minio-go/v7
to github.com/hanzoai/s3-go (package minio; a minio-go v7.0.98 fork). Drop-in:
same package name and same New/Client/Options, {Get,Put,List,MakeBucket,
RemoveObject,RemoveObjects}Options, ObjectInfo/Object/ErrorResponse surface and
credentials.NewStaticV4; conditional-CAS (SetMatchETag/SetMatchETagExcept) and
presign paths unchanged.

minio-go leaves the direct requires and stays indirect (luxfi/zapdb via
clients/kms). Run go mod tidy after the s3-go v1.0.0 tag is published to
populate go.sum.
2026-07-17 21:24:02 -07:00
antje 1a5cc134a0 gpu worker: a claimed job survives the engine recycle window
The supervisor recycles at queue-idle, but a freshly CLAIMED job is invisible
to the engine queue until its graph is submitted — so recycles fired over the
claim-to-submit window and staging failed on a dead engine, consuming the job
(observed twice in prod, seconds apart). Two invariants close it: a staging
latch the supervisor honors before recycling, and waitEngine() so a job
claimed while a recycle is already mid-flight waits out the restart instead
of dying on connection-refused.
2026-07-17 20:28:12 -07:00
z a7e4d68acf feat(link): server-side failover router over linked accounts + per-account usage
Add the execution half of route.go's redundancy seam: a Router that routes a
signed-in caller's inference through one of their OWN linked provider accounts,
resolves that account's KMS-sealed credential, and cycles to the next in-org
account on a live 429 — never falling back to a platform key or crossing the
tenant boundary. Meters each served call per (org, provider, profile) and
exposes the per-account breakdown at /v1/billing/usage/accounts (+ the canonical
/v1/links/usage/accounts).

- resolver.go: the credential-fetch contract consumed (Resolver seam) + a
  KMS-backed impl keyed at orgs/<org>/providers/<provider>/<profile>; Credential
  redacts under every fmt verb, resolves only within one org's namespace, and
  never falls back to a platform key.
- select.go: the non-secret account selector (openclaw Model@provider:profile,
  X-Provider-Account header, session pin) — carries no org/subject.
- router.go: in-org candidate selection (Links.ListLinked only), cycle-on-429,
  fail-secure, per-account cooldown; PolicyPlan|MostRemaining|RoundRobin.
- routed.go + meter.go: a summing per-account usage counter beside the Links +
  the meter that bills api-key accounts via commerce and leaves subscriptions
  plan-paid (BillingMode), so a call is metered once per meaning.
- carrier.go + wire.go: a process-local credential carrier (never serialized) +
  the Deps composition root and the AIClient upstream adapter. Inert until called.

Tests prove routing through a linked account, in-org cycling on 429, the
cross-org isolation boundary (against the real store), fail-secure with no
platform-key fallback, and that a credential never reaches a log or error.
2026-07-17 19:19:33 -07:00
zeekay 559e54bd45 build(iam2): bump v0.15.4 → v0.16.0 (argon2id SOTA password hashing) 2026-07-17 17:35:27 -07:00
z 9c4f6df7a7 refactor(usage): unify account-usage onto the ONE /v1/usage surface
The account-usage plane (2024df4) wrongly opened a SECOND usage surface inside
clients/link (/v1/links/usage). Move it into clients/usage so usage owns ALL
usage and link owns links and nothing usage — one surface, orthogonal, one window.

Moves (package link -> usage): sample.go (the Sample value + Sanitize), datastore.go
(the hanzo.account_usage warehouse series + reads, now behind a `warehouse` type that
holds only the DDL latch over aiobject's shared datastore — no handle, so usage keeps
NO Shutdown), and the record/samples handlers (account.go). Reconciled with the usage
subsystem: cloudUsageTable -> the existing llmTable, dsTime -> the existing tsLiteral,
duplicate aString -> dsString.

Route table (was /v1/links/usage*):
  POST /v1/usage           record account-usage samples (the collector)
  GET  /v1/usage/samples   one provider account's own lane dash (time series)
  GET  /v1/usage/summary   THE one summary — merged (see below)
  GET  /v1/usage/analytics{,/access}  unchanged

Summary collision resolved by MERGE, not two endpoints: the account-usage global view
folds into the existing /v1/usage/summary as a labelled `accounts` block beside spend +
LLM, over ONE window (aiobject.ResolveCloudUsageWindow drives both). Nothing dropped —
the caller's own linked-account rows AND the org Hanzo-routed rows both ride the one
summary, each side reporting its own availability, never summed.

Decomplected the Link-refresh: reportUsage braided a warehouse write with a Link
upsert, and since POST /v1/links already sets an account's usage snapshot, the sample
-> snapshot path was a SECOND way to do that. record now records usage only; the link
registry stays link's own concern. Drops the 3 Link-registry tests (they exercised
/v1/links, unreachable in a usage-only mount) and the Link half of 2 more; the warehouse
+ value coverage moves intact. No back-compat alias (the route was hours old).

Wire guard unchanged: link keeps its Shutdown (SQLite store), usage keeps none.
2026-07-17 16:53:17 -07:00
hanzo-dev 69f3d23b53 fix(iam-edge): forward the public sign-in surface before the tenant gate
console.hanzo.ai is served one-binary off cloud, so its /v1/iam/* calls hit the
iam_edge — which required a validated org for EVERY route. That 401'd
'sign in to continue' on the sign-in routes themselves (get-app-login, login,
oauth token exchange), a chicken-and-egg that bricked console login (the
'unknown iam route' / 'sign in to continue' users saw). Forward the
unauthenticated-by-design sign-in surface (login-page config, credential submit,
signin/signup, captcha/verification aids, the OAuth token endpoint, OIDC
discovery) straight to IAM BEFORE the org gate. Tenant CRUD + org metadata stay
fully gated — no tenant-data route is opened. Test: TestIamEdgePublic.
2026-07-17 16:50:29 -07:00
hanzo-dev 04a7644f42 feat(integrations): Cloudflare apikey connector (verify-before-store, KMS custody, org-admin gate) 2026-07-17 16:14:21 -07:00
hanzo-dev 754becb1e0 wip(fleet-samples plane (clients/samples + /v1/fleet board)): rescued from agent that hit the session limit
Committed as-is to preserve the work (the building agent died mid-verify).
Not yet built/tested green; NOT merged to main. Resume from here.
2026-07-17 16:04:56 -07:00
zeekay 607deab802 chore: trigger release build for iam2 v0.15.4 (federation fix)
e5b28e4 (iam2 v0.15.1→v0.15.4 bump) did not trigger a release run; nudge
the push-triggered release so the federation-security-fixed image ships.
2026-07-17 15:21:10 -07:00
zeekay e5b28e4f6b build(iam2): bump v0.15.1 → v0.15.4 (federation SuperAdmin-mint CRITICAL fix)
v0.15.4 closes the red-team CRITICAL in the federation broker: authorize
Application.Organization on write + reserved-org guard in federation
link/provision (was: social login could mint a SuperAdmin / take over a
cross-tenant account) + SSRF IP filter. Required before the hanzo.id social
cutover. Build pipeline healthy (consensus v1.36.3).
2026-07-17 15:03:48 -07:00
hanzo-dev 67e9d54902 Merge: surface the iam2 canary in /v1/flags 2026-07-17 12:39:04 -07:00
z 563ad78dee flags: surface the iam2 canary in /v1/flags
A read-only subsystem_iam2_active switch on the platform panel, mirroring
subsystem_iam_active, makes the clean-room iam2 selection visible in the /v1/flags
cockpit. The selector stays ONE thing — CLOUD_IAM_IMPL=iam2 at boot, applied on
the next reconcile — this switch reflects it, it does not add a second control.
Its description names the gate: the IAM cutover parity suite
(universe e2e/50-iam-cutover-parity) must be green against the iam2 shadow before
the canary is flipped.
2026-07-17 12:38:47 -07:00
hanzo-dev 2024df413b feat(account-usage): clients/link usage plane — samples, datastore series, /v1/links/usage
The account-usage plane over clients/link: a Sample value (one metering lane of
one provider account at one instant), a ReplacingMergeTree warehouse projection
(hanzo.account_usage + a dedup-preserving daily rollup MV) read back with explicit
read-time argMax dedup, and the /v1/links/usage surface — report samples, a
per-provider dash, and a global summary that sets a user's own linked-account plan
usage beside the org's Hanzo-routed cost of record, every row labelled by
source/scope/confidence and never summed together.

A windowless sample (a valid window class with no meter-reported duration or
reset) keys its class's nominal bucket, never the zero instant: every ranged read
filters window_start into [from,to) and the TTL drops epoch rows on arrival, so a
zero-keyed row would be written-but-never-read and would silently drop out of the
summary. Re-polls of a windowless counter collapse onto that one nominal instance
(ReplacingMergeTree by ts), so it is one row per lane, never summed across polls —
reconciling the two window-instance tests the rescued WIP left in contradiction.
2026-07-17 12:31:12 -07:00
hanzo-dev b413370b19 fix(identity): mint X-Billing-Account-Id from the claim, never from the client
The header was captured from client input and re-injected verbatim for any
validated principal. That was defensible while it was a mere attribution hint
no debit ever read — the comment said as much. It is not one anymore:
ai/object.Payer now resolves the PAYING account from it, so forwarding the
client's copy would let a caller name its own payer, which is the whole thing
the claim exists to prevent. A signup-org member could have sent
`X-Billing-Account-Id: org:hanzo` and pointed their spend at the shared pool.

It is now minted from the validated `billing_account` claim
(idClaims.mintedBillingAccount), mirroring iamauth.Claims.MintedBillingAccount
byte-for-byte, so the in-binary path binds what the gateway would and both
resolve one payer. The raw client copy is deleted on ingress and not restored.

The console read and the top-up now hand Payer that same claim, so the balance a
member SEES, the account a top-up FUNDS, and the account the ai gate DEBITS are
one wallet. Feeding Payer a different credential per call site is the modern
shape of the old org-vs-"org/user" split: a funded balance the gate refuses.

Tests drive real signed tokens through the boundary: the claim reaches the
header for person/org/project, a forged copy never survives (even on a token
that carries no claim, where a restored copy would be the only value present),
and an anonymous caller carries no payer at all.
2026-07-17 12:27:34 -07:00
z beea858117 refactor(flags,featuregate): decomplect the waitlist host-gate out of the flag engine
flags is now the PURE (Principal,context)->verdict engine: Register/Bool/Int/
String/Board/SetPlatformSwitch/Defs + /v1/flags/* + native evaluator + the
platform-switch seed. ZERO host->service / ModeForHost / waitlist.<svc> /
mode-route knowledge.

The complete launch waitlist-gate feature moves to clients/featuregate, which
COMPOSES flags one-way (flags.Bool/Register/SetPlatformSwitch/Def/Defs; flags
never imports featuregate):
- flags/waitlist_store.go -> featuregate/registry.go (host->service map)
- flags/waitlist.go -> featuregate/waitlist.go (mode decide + admin funcs +
  seed + waitlist.<svc> Def registration + Mount/Shutdown + the mode route)
- flags/waitlist_store_test.go -> featuregate/registry_test.go
- the registry OrgStore handle (was flags.Client.registry) is now featuregate
  package state, opened in featuregate.Mount, closed in Shutdown
- Enforce default gate is now the LOCAL WaitlistModeForHost
- /v1/flags/waitlist AND /v1/featuregate/mode compat alias served by
  featuregate (route name unchanged)
- apps.Wire re-adds featuregate after admin (after flags); wire_test frozen row
- admin/services.go swaps the flags import to featuregate for the board funcs
2026-07-17 12:06:06 -07:00
zeekay 763daed531 fix(flags): keep /v1/featuregate/mode as a TEMPORARY compat alias for /v1/flags/waitlist
The namespace collapse (132d01a) renamed the live waitlist-mode read to
/v1/flags/waitlist and made /v1/featuregate/mode a 404 — correct per the one-namespace
Policy primitive, but a BREAKING change to a public route whose external callers cannot
be fully enumerated from the monorepo (a deployed frontend could still call the old
path). Per the hard "never goes down for any customer" constraint, ship the collapse
WITHOUT the break: /v1/flags/waitlist is canonical; /v1/featuregate/mode is a temporary
alias to the same handler; both exempt from the Enforce gate.

Delete the alias (this route + its exempt entry in featuregate/middleware.go) once every
caller is confirmed on /v1/flags/waitlist — a one-line follow-up, gated on the owner.

Verified: gofmt clean, go build/vet green, exempt-path test asserts BOTH routes ungated.
2026-07-17 11:24:57 -07:00
hanzo-dev 6a269a581c Merge rip/services-kind: read one workload kind (App), drop the Service shim
services.hanzo.ai is dead (0 Service CRs cluster-wide; the fleet is 100% App).
clients/paas, clients/deploy, and clients/platform drop the two-kind read shim
and read apps.hanzo.ai only. The paas deploy endpoint (and release seam) now
always refuse a git-declared App with 409, naming the universe git path to
commit the tag to.
2026-07-17 11:01:28 -07:00
hanzo-dev 638cbe34ef paas/deploy/platform: read one workload kind (App), drop the Service shim
The services.hanzo.ai kind is dead: zero Service CRs exist cluster-wide and
the whole fleet is apps.hanzo.ai (kind App). These three cluster-facing planes
carried a two-kind read shim (App first, Service fallback) that is no longer
reachable, so strip it and read one kind — App.

- clients/paas: drop servicesGVR + crGVRs(); listApps/getApp/observeFleet read
  appsGVR directly (no cross-kind dedup). The deploy endpoint now always refuses
  (409): every App CR in the platform namespaces is git-declared and reconciled
  by Hanzo CD with selfHeal, so a patch here is reverted — the response names the
  git path to commit the tag to. releaseService refuses on the same grounds.
- clients/deploy: drop servicesCRGVR + appCRGVRs() and the "hanzo.ai/Service"
  registry entry; health/getAppCR/listAppCRs read appsCRGVR directly. coreSvcGVR
  (the core/v1 Service child object) is unchanged.
- clients/platform: drop servicesGVR + crGVRs(); resolveCR/getCR/deleteService
  read and delete appsGVR only. Tenant apps are still written and patched as App
  CRs in tenant-<org>.

Tests updated to the one-kind reality. Builds/vets/gofmt clean; go.mod untouched.
2026-07-17 11:00:25 -07:00
zeekay 132d01a0ff flags: move the waitlist mode read /v1/featuregate/mode -> /v1/flags/waitlist (one namespace)
The guard's public waitlist-mode read now lives under /v1/flags (the flags engine
owns it) — there is NO /v1/featuregate HTTP endpoint. The route, the Enforce
exempt prefix, and the doc/prose comments move; the featuregate Go PACKAGE (native
Enforce middleware) is NOT renamed, and the /v1/admin/services board is unchanged.

- clients/flags/routes.go            GET /v1/featuregate/mode -> GET /v1/flags/waitlist
- clients/flags/waitlist.go          doc comments repointed
- clients/featuregate/middleware.go  defaultExemptPrefixes /v1/featuregate/ -> /v1/flags/waitlist
- clients/featuregate/middleware_test.go  exempt-path assertion updated
- apps/apps.go                       stale prose comment repointed

Verified green: go build ./clients/flags/... ./clients/featuregate/... ./apps/...,
go vet, and CGO_ENABLED=0 go test ./clients/featuregate/...
2026-07-17 10:57:25 -07:00
hanzo-dev 141a8505b2 Merge: real semver only — ai v1.821.1 / iam v1.31.28 / luxfi from sumdb (kill pseudo-versions + force-moved-tag poison) 2026-07-17 10:48:06 -07:00
zandhanzo-dev b0fc5838eb Real semver across the board: ai v1.821.1, iam v1.31.28, luxfi from sumdb
Three coordinate-hygiene fixes so the pipeline resolves deterministically:
  - ai v1.820.0 -> v1.821.1. v1.820.0 pinned iam at an orphaned pseudo-version
    (a commit rebased out of existence); v1.821.1 pins the real iam tag v1.31.28.
  - iam -> v1.31.28, the real published tag; the pseudo-version and its replace
    are gone.
  - luxfi go.sum re-recorded from the immutable sum.golang.org via go mod tidy,
    so consensus/vm can no longer carry the hashes a force-moved git tag served.

Nothing but coordinates changed; ai v1.821.1 is v1.820.0's tree with one dep line
repinned, so the compiled result is identical to the shipped v1.801.49. Real
public semver only: no pseudo-versions, no replaces, no force-moved tags.
2026-07-17 10:47:19 -07:00
zeekay e2c900e4e7 fix(release): fail-closed container-tag floor so an orphaned tag is never reused
The v1.801.50 tag collision: a run pushed :v1.801.50 then was cancelled after
imagetools-create but before its git tag (orphaned container tag). The Tag steps
container-tag floor (cont_max) was fail-OPEN — `gh api ... 2>/dev/null || true`
yields "" on any API error — so a later run did NOT see :v1.801.50, recomputed
the same number, and REASSIGNED :v1.801.50 to a different image: an ambiguous
mutable prod tag (silent flip on any fresh-node reschedule).

Fail-CLOSED: if the container-tag lookup ERRORS (vs legitimately empty), retry the
whole attempt instead of proceeding on a git-only floor that cannot see the orphan.
A version that already has a pushed image is now never reused.

NOT reordering git-tag before imagetools-create (the other candidate fix): that
reintroduces the phantom "tag exists, image does not" this workflow was built to
prevent. Pairs with the crane-mirror timeout (5d8ec40) that stops the hang→cancel
which orphans tags in the first place. Compute-step cont_max left as-is (hint only).

[skip ci]
2026-07-17 10:29:03 -07:00
antjeandGitHub 3c560765d0 supervisor: recycle only at queue-idle; busy is not dead (#329)
Recycling on each completed render killed long renders mid-sample when short
jobs shared the engine (observed: every direct render died within ~6 minutes
while probe jobs cycled). The recycle now defers until the queue is empty.
Health: an engine that answers /queue with work in it is alive however slowly
it answers /system_stats; restarts require three consecutive silent probes
with an idle or unreadable queue.
2026-07-17 02:48:12 -07:00
hanzo-dev e87835bab0 fix(release): mirror LOGIN is best-effort too — a registry blip must not fail the release
The 'Mirror credential' step fail-safed only on a missing KMS token, not on the
docker-login to registry.hanzo.ai itself. A transient 502 from the mirror registry
(ingress blip; the registry was healthy 6m before and after) killed the whole
serialized release — no image, no tag — even though ghcr (the PRIMARY) was fine.
Both login paths now skip the mirror (MIRROR_OK unset) on failure and continue.
Complements 5d8ec40 (the crane-copy timeout): the mirror is now best-effort end to end.
2026-07-17 02:26:28 -07:00
z 5d8ec408d3 fix(release): bound the registry.hanzo.ai crane mirror with a timeout
An unbounded `crane copy` to registry.hanzo.ai can HANG (not just fail) — the
best-effort mirror once livelocked the Tag step and held the entire serialized
release lane (concurrency: release-cloud, cancel-in-progress:false), so no queued
release could run. A best-effort mirror must never be able to block the git-tag
receipt that follows it. `timeout 120` makes it truly best-effort.

[skip ci]
2026-07-17 02:06:48 -07:00
zeekay 8ea9134423 build(iam2): bump v0.14.0 → v0.15.1 (federation + signing-key generation)
v0.15.0 adds the OIDC/OAuth2 social-federation broker (Google/GitHub);
v0.15.1 mints signing keys for keyless reserved-org certs so the embedded
iam2 publishes a JWKS and can sign tokens (shadow-canary finding). Carries
the full parity + RFC surface into the cloud image for the hanzo.id cutover.
2026-07-17 01:35:15 -07:00
hanzo-dev ffdd5e2242 build(deps): adopt luxfi/consensus v1.36.9 (unbreak force-moved v1.36.2 checksum)
luxfi/consensus v1.36.2 was force-repushed with different go.mod content, so
cloud's committed go.sum no longer matches and 'go mod download' aborts with a
SECURITY ERROR — breaking EVERY release. Same recurring luxfi force-move pattern
as ad7e414 (keys). Bump to latest stable v1.36.9; clients/controlplane (only
importer) compiles clean, go mod verify passes.
2026-07-17 01:27:58 -07:00
antjeandGitHub 8c34978d89 render: poll window matches the dispatch cap; engine recycles after each render (#326)
* render: poll window matches the dispatch cap; engine recycles after each render

The 10m local history poll undercut the 4h startToCloseTimeout the dispatcher
grants — live renders (observed 8-70m) were marked failed while still sampling;
only the mirror later delivered them. renderWindow now matches the cap.

The engine leaks ~58GB per render. The handler signals a recycle after each
COMPLETED render (never on timeout — the engine may still be sampling and the
mirror rescues late finishes); the supervisor restarts on the signal.

* mirror: skip hidden files — AppleDouble forks pass the extension check

._foo.png is a mac resource fork, not a render; 700+ of them poisoned a
library within an hour of the mirror going live.

* deps: luxfi/consensus v1.36.2 -> v1.36.3 — the v1.36.2 tag was re-pushed

Cold builds fail sumdb verification against the moved tag (downloaded
eKzasq4O... vs sealed IbeWQF1w...). v1.36.3 is the immutable successor;
never re-tag a published version.
2026-07-17 01:26:40 -07:00
hanzo-dev ad26470ae2 feat(ai): bump ai v1.818.0 → v1.820.0 — router live-by-default + record-all + self-export/delete
Ships to prod: router.enabled=true (model=auto routes for every org by default),
per-request RoutingEvent recording for auto AND explicit models (up/down feedback
works on all models), per-org + global fit-gate-deploy-publish training, and the
self-scoped routing-data export/delete (data ownership). Pairs with the universe
CR ROUTER_ENDPOINT removal (heuristic 300ns is the live path).
2026-07-17 01:25:40 -07:00
hanzo-dev 37aeab8060 dedup: extract clients/payout from the 3 byte-mirror commerce.go copies
referrals/affiliates/authors each carried a byte-identical commerce.go (their own
doc-comments said so): the same commerce interface, httpCommerce, newCommerceClient,
deposit(), spendCents(), errUnconfigured — the S2S COMMERCE_SERVICE_TOKEN money-in
path (POST /v1/billing/deposit) + usage-rollup, triplicated.

Extract ONE clients/payout (attributed-credit -> commerce via commerceinproc): the
exported Commerce/Client/NewClient/ErrUnconfigured. Each program keeps a THIN
adapter — its own lowercase commerce interface + a commerceSeam that delegates to
payout.Client — so the program store/handler code AND their fakeCommerce test doubles
are untouched, and each program still names its own grant tag (grant:referral /
grant:affiliate / grant:author). ~330 duplicated lines collapse to one binding.

Zero behaviour change: identical HTTP contract, headers (X-Org-Id, Bearer), body,
fail-soft (ErrUnconfigured on deposit / 0 on spend when unwired), and errors.Is
sentinel. Adds payout unit tests (httptest) that give the extracted HTTP path REAL
coverage the fakes never did — ok clients/payout 0.010s.
2026-07-17 01:19:36 -07:00
hanzo-dev a41c2ae9e6 dedup: fold clients/gojabase into clients/goja (the Base binding is an option)
gojabase was the read-WRITE-Base sibling of goja: it wrapped a goja.Host and
added per-tenant Base/SQLite persistence, but duplicated the Host/Config/Request/
Response/New surface. Fold it into the ONE goja package as the Base-binding
CONSTRUCTOR — the persistence layer is now opted into via NewBase (vs New for a
read-only catalog bundle):

  goja.New   / goja.Host   / goja.Config   / goja.Request    read-only engine (plans/pricing)
  goja.NewBase / goja.BaseHost / goja.BaseConfig / goja.BaseRequest   + per-tenant Base

Moves gojabase.go -> clients/goja/base.go (renamed types, no goja. self-import),
store.go -> basestore.go, and both test files, all into package goja (zero
identifier collisions, coverage preserved). Repoints every importer —
dataroom/captable/sign (RW) to goja.Base*; plan/pricing already used goja and are
unchanged; base uses goja.TenantSegment. clients/gojabase deleted.

Behaviour is byte-identical: the engine, the per-request transaction commit-on-
<400, the injective TenantSegment, and the __db/__blob/__newId/__now host globals
are unchanged; only the package + exported names moved. No routes (both are
libraries). The gojabase[...] error prefix is kept as the RW-layer diagnostic label.
2026-07-17 01:19:36 -07:00
hanzo-dev d22d107e85 dedup: fold connectorruntime into the one automations subsystem
clients/connectorruntime mounts exactly ONE route —
POST /v1/automations/connectors/:id/run — the in-process goja runner paired with
automations own GET /v1/automations/connectors catalogue. It was a separate Wire
entry solely for that route. Fold connectorruntime.Mount in as a terminal
sub-mount of automations.Mount and drop its Wire entry + import -> ONE
automations subsystem.

The route is DISTINCT from every automations route and automations mounts no
/v1/automations/* wildcard, so there is no shadow; the runner still resolves the
shared engine lazily. clients/connectorruntime stays a focused package
(composition); its internal bundlecmd tool is untouched. Frozen wire row
removed.
2026-07-17 01:19:36 -07:00
hanzo-dev 5b020fc441 dedup: fold platform cron into the one tasks subsystem
clients/cron mounts NO routes — its Mount only launches a background starter
that registers durable schedules on the SAME shared engine (cloud.EmbeddedTasks)
that clients/tasks fronts. It was a separate Wire entry purely to get its
goroutine launched. Fold it in as a terminal sub-mount of tasks.Mount and drop
the cron Wire entry + import -> ONE tasks subsystem.

clients/cron stays a focused package (composition, not code-dumping): tasks
imports and invokes it. No routes change (cron never had any); the scheduler
still waits for the post-MountAll engine, so timing is unchanged. Frozen wire
row removed.
2026-07-17 01:19:36 -07:00
hanzo-dev d44fae4cf5 dedup: normalize the plan subsystem enable id "plans" -> "plan"
clients/plan.Mount was wired under the name "plans" while its package, and now
its generated standalone cmd, are "plan" — one subsystem, two names. Normalize
the Wire enable id (and cmd/plans -> cmd/plan, ServeSingle arg) to "plan".

Product routes are unchanged: the subsystem still serves /v1/plans/* (plural),
including its OwnsHealth /v1/plans/health probe — only the enable id / binary
name changes. No route drop; mount-all default still enables it (empty Enable =
all on). Updated the frozen wire row and the two cmd/cloud enable-id references;
TestMountAllAndServeHealth now maps plan to its real /v1/plans/health path
(enable id no longer equals route prefix for plan, as is already true for
account/runtime/agent).
2026-07-17 01:19:36 -07:00
c842f3b1df fix(release): resolve prebuilt artifact digests + unbreak cloud-flags publish (#327)
cloud#321 landed the Go-only Dockerfile (FROM cloud-flags:latest) but the
release.yml integration wasn't in it, and the reusable could not publish
cloud-flags at all — so every release since has FAILED at
'FROM cloud-flags:latest: not found'. Two fixes:

1. native/flags/Dockerfile base ghcr.io/hanzoai/mirror/rust -> public.ecr.aws
   (digest-identical). The hanzoai/ci reusable builds cloud-flags with the repo
   GITHUB_TOKEN, which 403s pulling the cross-repo-linked private mirror package;
   a public base is GITHUB_TOKEN-pullable, so cloud-flags finally publishes.

2. release.yml resolves console-embed/agent-skills/cloud-flags :latest to
   IMMUTABLE digests at release time (crane) and passes them as CONSOLE_IMAGE/
   SKILLS_IMAGE/FLAGS_IMAGE build-args to BOTH the smoke build and the push build,
   replacing CONSOLE_CACHEBUST. Reproducible (pinned, not floating :latest) AND
   fresh (a console/skills/flags change is a new digest). A MISSING artifact FAILS
   the release BEFORE build/smoke/tag — the receipt invariant holds, never a
   phantom tag on an image that could not embed the real console.

Preserves #322's functional + migration smoke gates (different sections).


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-17 01:18:50 -07:00
55810833c5 bench(finance): BenchmarkListUsage — the co-resident usage-read path (BUG 2) (#325)
The finance domain had no benchmark; this measures the read that replaced the
commerceinproc self-dispatch — finance.ListUsage over a per-org SQLite ledger,
at 100/1000/5000 seeded debits. Backs the reproducibility claim in the
hanzo-unified-tenant-cloud paper (1.25/10.5/61 ms). Also surfaces a real N+1:
store.Entries fetches postings per row the usage view never uses — a
postings-free read would cut this ~10x (follow-up).


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-17 01:06:20 -07:00
zandhanzo-dev d7f24d8e61 Money names its unit: Int -> Atto
There were two words for one idea. money.Amount.Minor() returns an integer at the
CURRENCY's decimals — money.USD declares 2, so cents. cloudmoney.Amount.Int()
returns an integer at 18 decimals — atto. Both are "the backing integer", neither
name says which, and they differ by 10^16.

That is not a style complaint. It is how

    Amount: cloudmoney.FromInt(u.Charge.Minor()), // exact 18-dp USD, no floor

got written, reviewed, and shipped. It type-checked (both sides *big.Int), it read
as "make an Amount from the integer", and it billed a $17.376 zen call as
$0.0000000000000017 until v1.801.44. The package documented the trap in prose —
"Take the decimal, never Amount.Minor()" — because a comment was the only place
the unit existed. Prose is not a type.

So name the unit, not the Go type: FromInt -> FromAtto, Int() -> Atto(),
IntString() -> AttoString(). FromCents/Cents already did this and were never
confused with anything. Now the units are visible at the call site, and the
mistake reads as one: FromAtto(x.Cents()) is obviously wrong where
FromInt(x.Minor()) was obviously fine. It no longer type-checks either —
FromAtto takes *big.Int, Cents() returns int64 — so the pairing that cost us the
money is now two independent kinds of error instead of zero.

Values are untouched: Atto/AttoString return exactly what Int/IntString did, so
the treasury ledger hash and every stored 18-decimal string are byte-identical.
No migration, no data change — only the names, and the compiler found every one
of them (45 sites; a regex could not have, because .Int() also belongs to big.Int
and decimal).

Zero regressions: the failing set is identical to origin/main.
2026-07-17 00:52:06 -07:00
zeekayandhanzo-dev ad7e414672 build(deps): adopt stable luxfi/keys v1.4.1 (unbreak force-moved v1.4.0 checksum)
luxfi/keys v1.4.0 was force-moved on the remote (tree 5153d639→80a3745a),
producing a go.sum checksum mismatch that broke `go mod tidy`/`go build` and
the hanzoai/cloud image build in CI. Every keys tag v1.1.0..v1.4.0 was
force-moved with content changes; only v1.4.1 is byte-stable (local==remote
tree 17551acd). Adopt v1.4.1 as the single stable version. Its go.mod floors
the unified luxfi stack, so the transitive set moves forward (geth 1.17.12→
1.20.1, consensus 1.35.32→1.36.2, crypto/database/warp/zap/…), all within v1.

go.mod/go.sum only; diff vs origin/main is luxfi/* exclusively. Embedded
iam2 v0.14.0, apps.go, and concurrent commerce/agent work untouched.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-17 00:50:13 -07:00
92123af64e build: decomplect the cloud image — cloud compiles ONLY Go (#321)
The console SPA, agent-skills catalog, and native flags staticlib are each now
built by their OWN CI as a versioned immutable image and PULLED into the cloud
build, instead of rebuilding node+python+rust from scratch every release. The
console stage (cold npm install + full Next static export, cache-busted every
build) was the ~20-min long pole; it is now a registry pull.

- Dockerfile: console/skills/flagslib stages -> FROM ${CONSOLE_IMAGE}/
  ${SKILLS_IMAGE}/${FLAGS_IMAGE} prebuilt pulls; COPY sources updated
  (/dist, /catalog, /libhanzo_flags.a). Mirror golang+alpine bases, GOPRIVATE,
  and every RED gate (SQLCipher proof, modernc guard, cek frozen-format) are
  unchanged. Pins are ghcr.io so both buildx lanes pull directly; mirrored to
  registry.hanzo.ai (S3) for GET-flow consumers. release.yml still owns the
  cloud image + v* tags (it resolves CONSOLE_IMAGE to a fresh console-embed
  digest, as CONSOLE_CACHEBUST did).
- native/flags/Dockerfile: the cloud-flags artifact (rust -> scratch /libhanzo_flags.a).
- hanzo.yml: images: cloud-flags (distinct artifact, never a v* tag) + zccache
  RUSTC_WRAPPER on the native-flags gate (no-op unless the runner carries it).

Companion artifact publishers: hanzoai/console#(console-embed),
hanzoai/openapi#(agent-skills).


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-17 00:49:57 -07:00
hanzo-dev 47d099075f refactor(flags): extract the Policy primitive — fold featuregate's waitlist into the flags engine
featureflags -> flags (Hanzo's Unleash-analog / hanzoai/flags): ONE runtime
decision engine, (Principal, context) -> verdict, evaluated in-process, hot.

Fold the launch-control waitlist off its DUPLICATE SQLite mode store
(clients/featuregate) onto the one engine:

  - a service's waitlist mode IS the platform switch waitlist.<svc>,
    evaluated through the same native evaluator as every other flag
  - the host->service registry folds into clients/flags (waitlist_store.go,
    mode column dropped — the mode is the switch)
  - featuregate.Enforce stays but as a CONSUMER of flags.WaitlistModeForHost
    (the decide), via an injectable Gate seam
  - /v1/featuregate/mode -> served by flags (the decide), same wire shape
  - /v1/admin/services -> an admin lens like /v1/admin/flags
  - per-user approval still reuses IAM (featuregate/approval.go, unchanged)
  - featuregate dropped from apps Wire() — it exposes only Enforce now

The flags package doc names the aspirational end-state: authz (access policy)
and entitlements (product-access policy) are the SAME (Principal,context)->
verdict shape and could COMPOSE this one engine. NOT touched here — flagged only.

Tests (green): featuregate RULE acceptance matrix + approvals; folded-registry
store (Seed/ServiceForHost/List/Upsert); flags env/board/parsers;
apps TestWireOrderMatchesFrozen. Native-engine + cek store tests need
CGO+libsqlcipher+libhanzo_flags (CI), unchanged.
2026-07-17 00:48:30 -07:00
hanzo-dev 10f185f563 billing bridge: ask commerce what it gates, stop keeping a copy
The bridge's mint guard kept its own list of commerce's mint routes under the
comment 'kept in lockstep with api/billing/handlers.go'. A comment cannot hold
two lists together, and it hadn't: 10 paths here against the 16 commerce gates.
Six money-mint routes were outside this guard entirely.

Commerce now DECLARES its gated surface — middleware.Mint records what it gates,
MintRoutes() exports it (commerce v1.49.0) — so the guard reads that declaration
instead of copying it. A mint route added in commerce is covered here with nobody
remembering anything, which is the only version of this that survives contact
with a busy repo.

Registration is what populates the registry, so the guard registers commerce's
billing routes before reading it. The request-level assertion is unchanged and is
the part that matters: an ordinary org user's call must never REACH commerce,
because arriving at all means arriving with the admin service token that
satisfies MayMintMoney.

Proof it bites: allowlisting 'deposit' fails with the escalation itself —
'POST /v1/billing/deposit reached commerce carrying Bearer svc-tok'.

16/16 gated routes refused. All six bridge tests pass.
2026-07-17 00:41:23 -07:00
antjeandGitHub b8c17f06aa gpu: mirror local studio renders to the library (independent of claims) (#324)
Every 30s (its own ticker in the connect select loop), scan --studio-dir/output
recursively for image files new or changed since the last scan and POST each to
<studio-url>/v1/library/upload with the worker's bearer, tagged ?node=<identity>
and ?subpath=<subfolder>. So EVERY render lands in studio.hanzo.ai — including
ones produced OUTSIDE the job path: a graph hand-run on the node, or a render
that finished after its activity was reaped (the stranded-late-render class). The
mirror's independence from claims/activities is the point.

State is a tiny in-memory map[relpath]size that skips unchanged files; the studio
endpoint dedupes byte-identical uploads, so a re-scan after restart is cheap and
harmless. One log line per newly stored file; upload failures are summarized once
per scan and retried next tick (no 5xx spam). New --studio-url flag (default
https://studio.hanzo.ai, HANZO_STUDIO_UPLOAD_URL honored) so the mirror works
WITHOUT jobs. No new deps. Test: cli/gpu_mirror_test.go (new/changed uploaded,
unchanged skipped, node+subpath+bearer carried).
2026-07-17 00:20:24 -07:00
antje 21673ccde9 agent: v0.1.2 — pass a completion billing refusal (402) through, not a 502
Bump github.com/hanzoai/agent v0.1.1 -> v0.1.2 and have the in-process completer
return the agent typed hz.UpstreamError{Status,Body} on a non-2xx completion. The
round then passes a caller-facing 4xx (402 insufficient_balance, 429, 403) through
verbatim so a no-credit user sees "add credits", not an opaque "agent: completion"
502. Proven live: POST /v1/agent with a real hk- key ran the round end-to-end and
the completion returned 402. Dropped the now-unused clip() helper. Simplified
commerce_errorscope_test to the real invariant (typed 403 never flattened to 5xx)
now that commerce v1.48.10 honors status itself; the scope stays as the boundary.
2026-07-17 00:01:18 -07:00
antje f3f0181052 deps: commerce v1.48.5 -> v1.48.10 — free $0 tiers stay self-serve (paid-tier gate keys on price, not includedCreditUsd) 2026-07-16 22:38:59 -07:00
zandhanzo-dev cd2f5dece8 MountAll's doc outlived Typed
It still said the MountFunc takes the app as `any` and that in-repo subsystems
recover it via Typed. Neither is true: MountFunc names *zip.App and Typed is
deleted. The app is handed to each mount as itself.
2026-07-16 22:24:17 -07:00
antje 22d899d684 feat(sync,git): Gitea-native sync provider + webhook reject parity; fix LoadConfig flag panic
CHANGE 1 — the /v1/sync git provider drives GITEA (the one git store), not the
retired cloud embedded store:
- clients/sync/gitea.go: a Gitea REST + go-git client (GIT_ADMIN_TOKEN, GITEA_URL).
  Inbound = fast-forward-only go-git fetch(source) -> push(Gitea), so a diverged ref
  is a conflict, never overwritten (split-brain guard, now on Gitea). Outbound = a
  Gitea push-mirror (sync_on_commit) so Gitea itself propagates every commit. Fails
  closed when GIT_ADMIN_TOKEN is unset.
- git_provider.go Reconcile and sync_api.go patch/delete now compose those Gitea
  primitives; the cloud embedded seams (InboundGitSync/ImportGitRepo/EnsureGitMirror)
  are retired from the sync path. resolve() decision, loop guard, cursor idempotency,
  and hop limit are unchanged.

CHANGE 3 — webhook reject parity + a pre-existing root test panic:
- Wrap /v1/git/webhook and the slack(events,commands)/discord/teams/telegram inbound
  webhooks in cloud.Terminal so a bad-signature 401 / malformed 400 survives the
  commerce /v1 500-flatten (uniform reject codes, matching /v1/sync and
  /v1/connector/github/webhook).
- config.go LoadConfig: guard the process-global flag registration with a sync.Once,
  so a re-entrant LoadConfig (many test callers in one binary) no longer panics
  "flag redefined: enable".

CHANGE 2 (retire the embedded git server) is NOT done: it is still a live dependency.
cloneURL resolves to api.hanzo.ai/v1/git (cloud's OWN embedded server) and the
coding-agent orchestrator clones from uploadPack, pushes to receivePack, and reads the
store via VerifyRef. Deferred — migrate coding to Gitea first.

Tests (CGO_ENABLED=0): clients/sync + clients/integrations green; new
clients/sync/gitea_test.go proves reconcile acts on Gitea and the fast-forward guard.
2026-07-16 22:20:41 -07:00
hanzo-dev 820c79a0e1 Merge: Mount takes *zip.App — delete the Typed shim and its 85 wrappers 2026-07-16 21:57:01 -07:00
antje 5aa2a8fa5f edge: scope commerce error envelope to its own routes (unblock release smoke — 14 endpoints 500→4xx)
commercemid.ErrorHandlerJSON() was installed as a /v1 GROUP middleware, but fiber
matches group middleware by PREFIX, not by the handle a route registered on. So on
the shared /v1 it wrapped EVERY subsystem mounted after commerce (projects, agents,
wallets, functions, integrations, marketplace, team, s3, analytics, knowledge,
automations, deploy, billing) and flattened their typed zip.HTTPError (403 "X-Org-Id
required", 400, …) into a blanket 500 — the store envelope always renders 500. The
authenticated release smoke (#322) correctly fails on 5xx, so this blocked every
release since it landed.

Fix stays cloud-side (no commerce dep bump, no money-path churn): commerceErrorScope
guards the envelope by commercePrefixes, so it stays on commerce and every other
subsystem renders its own status via zip default. Pre-commerce subsystems (kms,
o11y) already did; this makes the post-commerce ones match. Verified with the REAL
commerce middleware: /v1/projects 403 (was 500), /v1/store/current keeps the 500
envelope. Regression test added.
2026-07-16 21:50:00 -07:00
zandhanzo-dev fa60ebed6a Mount takes *zip.App: delete Typed and the 85 wrappers
MountFunc took `app any` and cloud.Typed asserted it back to *zip.App on every
mount — a runtime check doing the type system's job, with a failure branch that
could not fire because the only value ever passed is a *zip.App. Every subsystem
paid for it: 85 call sites read cloud.Typed(x.Mount) instead of x.Mount.

The reason given was circular. cloud said `any` was load-bearing because an
external module (licensing) exposed func(any, Deps) error; licensing said it used
`any` to avoid an import cycle in pkg/cloud. Each pointed at the other, and the
cycle cannot exist: this package already imports zip (build.go), and zip does not
import cloud. The `any` was justified by nothing.

So name the type. MountFunc is func(*zip.App, Deps) error — what every subsystem
already exported and what licensing's own doc claimed all along. Typed is deleted,
the 85 wrappers are gone, and the three in-repo mounts that hand-rolled the same
assertion (mountZen, mountMetrics, MountO11y) just take the app.

The compiler immediately found what the `any` had been hiding: four mounts still
shaped func(any, ...), one of them across a module boundary. That is the point —
a signature drift is now a build failure instead of a runtime error nobody would
see until a subsystem mounted.

Also here, because the same rip surfaced them:

  - iam: v1.31.27-0.20260716191958-4400762928a2 -> v1.31.28, and the replace
    pinning a second pseudo-version is dropped. The required pseudo-version named
    a commit that no longer exists (it was rebased away), so `go mod tidy` could
    not resolve it; v1.31.28 is a real tag and a strict superset of what the
    replace pointed at. A version, not a coordinate, and no replace.
  - licensing -> v0.1.5, which is where the typed Mount ships.
  - cloud.OrgConfig is aliased next to LicenseEntitlement. Both are named by
    CommerceClient's methods, but only one was exported, so the exported
    interface could not be implemented from outside without reaching into
    cloud/types — an omission, not a boundary.
  - build_registration_test.go tested Typed and nothing else. "Recovers the
    *zip.App" proved an adapter passed through its argument; "fails closed on a
    wrong type" cannot be compiled now. What is left is the assertion that a
    subsystem signature IS a MountFunc — which the build checks.

No regressions: the failing set is byte-identical to origin/main (11 pre-existing
TestAudit_*).
2026-07-16 21:47:19 -07:00
zeekay 48cd0e41e1 build(iam2): bump embedded iam2 v0.1.1 → v0.14.0 (parity-complete surface)
The CLOUD_IAM_IMPL=iam2 identity fold (clients/iam2, identitySpec) was pinned
to iam2 v0.1.1 — an early cut missing the whole console-parity surface. Bump
to v0.14.0 so the embed actually serves what hanzo.id needs:

  - RFC/IETF surface (HIP-0111): OAuth2 code+PKCE/refresh/client_credentials/
    password, RFC 8693 token-exchange, 7662 introspection, 7009 revocation,
    8414 AS-metadata, OIDC UserInfo, SCIM 2.0 Users
  - Casdoor verb-alias compat (transitional cutover bridge) for every verb the
    live console/gateway hard-code: users/orgs/apps/providers/roles/projects
  - operator bootstrap upsert (IAM CR reconciliation), TOTP MFA enrollment,
    organization-scoped projects (ScopeSwitcher)

No wiring change — main's identitySpec + co-mingle iam2server.Mount(app, db)
compile unchanged against the v0.14.0 API. zip already at v1.8.3.
2026-07-16 21:43:03 -07:00
antje ec50b73366 feat(connector,sync): /v1/connector/github/webhook namespace + reject paths survive the commerce /v1 500-flatten
CHANGE A — first-party vs external route naming. Rename /v1/github-webhook ->
/v1/connector/github/webhook, opening the external-platform namespace
/v1/connector/<provider>/webhook (github now; gitlab/others are sibling literal
routes later, each with its own signature scheme). /v1/git/webhook (first-party
Hanzo Git) and /v1/sync (the bridge) are unchanged. No live consumer breaks:
the GitHub App isn't created yet.

CHANGE B — 500 -> real 4xx on the reject paths. mountCommerce registers
commerce's ErrorHandlerJSON on app.Group("/v1"); that filter rewrites ANY error
a downstream /v1 handler PROPAGATES into a hardcoded HTTP 500. Every /v1
subsystem mounted after commerce is wrapped the same way -- git, sync AND
integrations alike. git does NOT escape it: its isolated tests read 401 only
because they don't co-mount commerce (its bad-sig path is never exercised in
prod, so the flatten went unseen). Add cloud.Terminal, which writes a returned
*zip.HTTPError in-band and returns nil, so the filter's c.Next() sees nil and
has nothing to flatten. Wrap /v1/sync (all verbs) and the connector webhook.
sync no-principal is now 401 (was 403) -- an authentication failure, matching
the webhook's bad-sig 401. The commerce filter is left untouched.

Tests reproduce the /v1 flatten filter and assert: sync unauth -> 401, connector
bad-sig -> 401, malformed body -> 400; connector resolves at the new path and
the old /v1/github-webhook 404s.
2026-07-16 21:32:46 -07:00
antje 146d65d380 edge: /v1/agent self-meters (fix 503 balance_unavailable on the agent orchestrator)
The global BillingGate priced /v1/agent/* at a flat 1c via a dead legacy
bot-reverse-proxy rule in DefaultPrice, so every agent request was gated: the
unauthenticated preset/conversation reads hit the balance check, failed closed,
and 503d before the orchestrator handler ever ran. The route was mounted and
winning precedence the whole time — the gate short-circuited ahead of it.

/v1/agent is self-metered: the reads are free and POST /v1/agent bills through
the /v1/chat/completions it runs in-process (gated + metered downstream), so the
edge must price it 0 or double-bill. Drop the legacy branch (and its now-unused
cloudEdgePriceCents const); price /v1/agent and /v1/agent/* at 0. Tests updated.
2026-07-16 21:06:09 -07:00
hanzo-dev b44bb4da4b Merge feat/openapi-spec: /v1/openapi.json generated from the live router
The spec IS the router, not a description of it: apps.Wire() -> MountAll ->
app.Fiber().GetRoutes(). 983 operations / 692 paths / 109 products, served beside
/zap so ZAP and OpenAPI are two projections of one route table rather than two
sources that can disagree.

A drift test proves the bijection and was proved to fire; it already caught
/v1/pricing-policy and /v1/pricing/policy collapsing onto one operationId.

# Conflicts:
#	serve.go
2026-07-16 20:42:42 -07:00
5c148bd48e fix(billing,smoke): usage reads the co-resident ledger (not a self-dispatch) + a real authenticated release smoke (#322)
A live authenticated smoke surfaced two production bugs; this fixes both and
adds the durable smoke that now guards every release.

BUG — /v1/billing/usage 500 for a valid caller. usage() proxied
"/v1/billing/usage" through commerceinproc, which re-dispatches BY PATH.
Commerce's own billing routes are behind //go:build cloud and never compiled
here, so the ONLY registration of that path is usage() itself — the S2S hop
re-entered the handler, which self-answered "sign in to view billing". This is
the SAME defect balance() was already fixed for. usage() now reads the usage
ledger DIRECTLY from cloud's own finance ledger (finance.ListUsage → the
wallet→revenue debits RecordUsage wrote), off the self-dispatching hop;
split-deploy falls back to the commerce S2S read, unchanged.

BUG — the balance gate 402'd read-only GETs (fixed in hanzoai/ai, pinned via
the go.mod bump). A $0-balance org could not VIEW its own resources. Fixed in
the ai module's BalanceGateFilter — reads never spend, so GET/HEAD/OPTIONS are
exempt; only writes/metered POSTs gate on balance.

SMOKE — cmd/smoke: a durable, authenticated per-subsystem prober. One
side-effect-free read per core subsystem; a read that 402s (balance gate) or
5xx-es (crash) fails the release. Baked into the image (Dockerfile) and wired
into release.yml as the functional gate after the boot check, so a release can
never ship with chat/billing/projects/kms/... down. The smoke token is
KMS/secret-sourced (never hardcoded); absent → the anonymous matrix still gates
public/authed and catches every 402-on-read / 5xx.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-16 20:35:56 -07:00
hanzo-dev 833b2764f1 cli: multi-identity credential store with active-pointer switch
Store every logged-in identity in ~/.hanzo/identities.json keyed by a stable
<owner>/<name> key (admin/z, hanzo/z), with an Active pointer; mirror the active
identity into credentials.json so every legacy single-file reader is unchanged.
A second login as a different owner for the same email (privilege separation:
hanzo-admin-guard vs hanzo-console) is stored beside the first, not over it.

New: auth list (whoami --all), auth switch <owner|owner/name> (alias use),
logout [<owner>]. Token refresh writes through the store (SaveActive) so the
active identity stays fresh after rotation. All files stay mode 0600.

One credential store, active-pointer switch, backward compatible.
2026-07-16 20:20:53 -07:00
hanzo-dev 6644af0533 dedup: fold hanzoai/o11y module wildcard into the one o11y subsystem
apps.Wire() had TWO {Name:"o11y"} entries: the in-repo read plane
(o11y.MountO11y) and the external hanzoai/o11y module wildcard
(cloud.Typed(o11ymod.Mount)). Fold the module wildcard in as the TERMINAL
sub-mount inside o11y.MountO11y (registered after every specific /v1/o11y/*
route, so Fiber in-order match still gives them precedence), delete the 2nd
Wire entry and the now-unused o11ymod import -> ONE o11y spec.

/v1/o11y/health is preserved exactly: the merged entry keeps OwnsHealth=false,
so the generic always-ok route is registered before MountAll (ahead of the
wildcard) — byte-identical to when the module co-entry, also OwnsHealth=false,
triggered it. Frozen wire order updated (two co-owned rows -> one); the
no-duplicate test no longer needs an o11y exemption.
2026-07-16 20:17:18 -07:00
hanzo-dev ced7fdf490 dedup: delete dead clients/session
Zero importers, no cmd/session, absent from apps.Wire(); its /v1/code/sessions
surface was never mounted (dark). Removes session.go, store.go, session_test.go.
2026-07-16 20:10:06 -07:00
hanzo-dev 24e51b17d9 fix(cloud): serve /v1/iam/* — the org-scoped edge to Hanzo IAM
The one-binary console (console.hanzo.ai — cloud serves console's static export)
reads org members + projects at /v1/iam/*, but cloud 404'd those (IAM isn't
folded in-process yet) and the old /org/iam BFF proxy is pruned from the static
export. So the browser got the SPA shell (HTTP 200 HTML), which the client
surfaced as "Request failed (HTTP 200)" — the Platform page died on "Could not
load".

iam_edge.go adds an org-scoped reverse edge at /v1/iam/* → the standalone IAM,
mounted when IAM is NOT folded in-process (else that subsystem owns the path — no
double-mount). The org is PINNED to the caller's validated, server-minted
X-Org-Id (never a raw client header) — load-bearing, since IAM's own authz is
permissive on the org-keyed routes, so without the pin one tenant could read
another's projects. A super admin may cross; a tenant may not; writes require an
org admin and must carry the caller's own org. Shares the ONE IAM identity
(iamHost/iamCred) with the API-key resolver (DRY).

Verified: 7 gate tests (pin, cross-tenant refuse, super-cross, allow-list, 401,
write-gate, own predicate) + go build clean.
2026-07-16 20:07:12 -07:00
zandGitHub 4dda15d2d0 chore(deps): bump hanzoai/tasks → v1.51.1 (fix api.hanzo.ai concurrent-map-writes crash)
Fixes the live recurring tasksd concurrent-map-writes fatal (hanzoai/tasks#18, v1.51.1). Build green; the failing 'Test' check is the pre-existing repo-wide LoadConfig flag-redefine panic (fails on main + all branches), unrelated to this go.mod-only bump.
2026-07-16 20:02:07 -07:00
hanzo-dev dcc440e589 Merge: tenant apps are App CRs — the last writer of the Service kind
clients/platform was the only thing still minting Service CRs; every other
declarer is already App. A role-less App dispatches to the operator's service
profile, the same reconcile the Service kind ran, so a tenant workload carries
over verbatim.

Existing tenant CRs still resolve (App first, Service second). A redeploy patches
the kind it IS rather than minting a twin — two CRs on one name is the
commerce-admin ownerRef flap, not a migration. Teardown deletes BOTH kinds:
either alone rebuilds the app the tenant just deleted, still billing.

113 tests pass, 7 new.
2026-07-16 19:40:04 -07:00
hanzo-dev 071c698792 platform: tenant apps are App CRs — the last writer of the Service kind
clients/platform was the only thing still minting Service CRs. Every other
declarer is already App: universe git has zero hanzo.ai/v1 kind:Service, the
operator calls App "the sole workload reconciler for the collapsed fleet", and 69
of the 80 live CRs are Apps. A tenant app was the exception for no reason — a
role-less App dispatches to the operator's service profile (controllers/app.rs
`classify("") => Dispatch::Service`), which is the same reconcile the Service kind
ran, so an App carries a tenant workload verbatim.

Nothing mints a new Service CR after this. What already exists still resolves:
reads, patches, scales and deletes walk crGVRs() — App first, Service second — so
the 3 live tenant CRs written before this keep working untouched.

A redeploy of a pre-collapse app patches the kind it IS rather than declaring an
App twin. Two CRs claiming one name is not a migration, it is the commerce-admin
flap: both kinds materialize the same children through the same materializer under
one field manager, so the Deployment's ownerRef just flips between them.

Teardown deletes BOTH kinds. Either kind alone re-materializes the Deployment, so
removing only the one that resolves first would rebuild the app the tenant just
deleted — running, and still billing, minutes after a successful delete.

Sequencing (deploy order matters): operator v0.7.7 carries the Claim guard that
makes App the deterministic owner when both kinds claim a name. This is safe
before it — the no-twin rule means a colliding pair is never created here — but
the guard is what makes an existing collision safe to clean up.

REMOVABLE once no Service CR remains in any tenant namespace: drop servicesGVR
from crGVRs() and the delete-both, and this file is App-only.

Tests: 113 pass; 7 new (kind is App, no twin on legacy redeploy, delete removes
both kinds, idempotent delete, resolution order, absence honest). The 10 tests
that asserted a Service CR is written now assert the kind we write.
TestMigrateOverLegacyPlatformApps fails identically on pristine main (sqlcipher
codec, environmental).
2026-07-16 19:39:56 -07:00
antje 7075d8ba01 apps: frozen wire list — add sync entry (main added /v1/sync to Wire; frozen drifted, breaking TestWireOrderMatchesFrozen); fix agent route comment 2026-07-16 19:38:00 -07:00
hanzo-dev 5d185a4c8b Merge: paas reads the kind the fleet runs on, and does not fight the git declarer
The PaaS control plane serves platform.hanzo.ai and read services only: 69 App CRs
run in the scanned namespaces against 7 Service CRs, so the SUPERADMIN drift board
rendered 7 rows for a 69-app fleet — 1 in production — and /v1/paas/health probed
the Service CRD, found it served, and reported ok over a blind board.

Reads now walk App first, Service second, deduped by name. Writes refuse a
git-declared App (Hanzo CD syncs it with selfHeal, so a patch is reverted on the
next sync) and name the file to commit to; a Service CR still patches.

35 tests pass, 0 fail.
2026-07-16 19:30:16 -07:00
hanzo-devandz 43958eb36e feat(shard): in-binary org→owner shard router for horizontal writer scale
Lifts the unified binary off replicas:1 on DigitalOcean (RWO-only block
storage, no RWX) WITHOUT any shared volume. Each org is pinned by rendezvous
hashing (ha.Owner over the static CLOUD_PEERS ring) to exactly one owner pod;
a request whose org this pod does not own is transparently forwarded to the
owner, so every per-org SQLite store (KMS, finance, and every org-keyed store),
audit append, per-org rate ceiling, and prepaid billing debit runs on ONE pod.

THE INVARIANT — no two pods ever write one tenant's SQLite file — is upheld by
two independent guarantees that compose: per-pod RWO PVC (different physical
files per pod) + org→owner routing (all of an org's writes on one pod).

- shardrouter.go: the middleware. Runs immediately after SanitizeIdentity so it
  keys on the VALIDATED, server-minted X-Org-Id (never a client header), hashes
  the SAME injective SanitizeOrg slug the on-disk path uses (routing key ≡ file
  key), and forwards via a fasthttp streaming proxy (SSE/chat pass through — a
  streaming chat still carries a per-org billing debit, so it routes too) with
  dial-only retry across an owner's roll gap and a 421 loop-guard on divergence.
  Static identical membership rules out dual-owner and routing loops.
- config.go: CLOUD_PEERS (id@addr ring) + POD_NAME (self). Sharding auto-enables
  only when >1 peer; Validate fails closed if self is not in the ring or if
  embedded iam (non-shardable process-local sessions) is co-enabled.
- serve.go: wires the middleware after IdentityMiddleware; shard-aware boot log.
- audit_serve.go: per-shard audit is automatic on the per-pod PVC; stamp the
  shard id on the AU-9 checkpoint stream so the tail-truncation monitor tracks
  N heads. writerpin.SingleWriter is correct PER SHARD (each pod sole writer of
  its orgs); the writer lease is pod-local under per-pod PVC and stays off.

No-op (byte-identical to today) when CLOUD_PEERS names ≤1 pod. N pinned at 3;
rebalance-on-N-change (a tenant-file move) is the documented follow-up.

Tests prove: exactly one owner per org (deterministic, total, evenly
distributed); all pods agree (no dual-writer); owned served locally, unowned
forwarded to the owner (local chain never runs, hop header set, response
streamed); org-less served locally; loop-guard 421; boot-gate fail-closed.
2026-07-16 19:28:27 -07:00
hanzo-dev bfcc9893a0 Merge: bill zen in the credit unit — FromInt(Minor()) understated every debit by 10^16 2026-07-16 19:26:12 -07:00
hanzo-dev ba34cae921 Bill zen in the credit unit, not the currency's minor unit
zen prices every SKU as an exact 18-dp value tagged money.USD. money.USD
declares 2 decimals, so Amount.Minor() rescales that value to CENTS, while
cloudmoney.FromInt reads its argument as 18-dp. Composing the two divided
every zen debit by 10^16: a $17.376 charge debited $0.000000000000001738,
and any charge under half a cent folded to a zero that metering.Record drops
before it reaches the ledger — no debit row, call served free.

The spend gate read the same composition. FromInt(est.Minor()).Cents() is
always 0, and AuthorizeVerdict only compares balance against size when
AmountCents > 0, so the size check was dead code and any org with a positive
balance could draw a request of any size. The dust debits never accumulated,
so the cap could not trip either.

Route the seam through one conversion. credit() carries the exact decimal
across and changes only the minor-unit convention — no rescale, no rounding,
no factor — because the decimal is the value and a currency's Decimals is a
rendering convention. cloudmoney.FromDecimal is the typed counterpart of
ParseUSD that makes this expressible without a string round-trip. nano()
takes the typed Amount rather than a bare *big.Int, so a cents integer can no
longer reach the warehouse fold.

The tests asserted Amount.Int() against Charge.Minor() — the same integer on
both sides — so they proved a round-trip and were blind to the unit. They now
assert against known dollar values built through a different constructor: a
$17.376 charge debits $17.376. Reintroducing Minor()-into-FromInt fails all
of them, including a gate test that admits an over-cap request.
2026-07-16 19:24:29 -07:00
hanzo-dev 164a2f9b56 Forward only the billing paths the console reads
The /v1/billing/* bridge attaches the commerce service token, and that token
satisfies commerce's MayMintMoney. The subpath was checked for traversal but
not against a set, so POST /v1/billing/deposit forwarded a mint for any
signed-in user — pinned to their own subject, which aims the mint rather than
stopping it. Commerce closed this on its direct path the day after the bridge
reopened it, and wider: the bridge needs only a validated principal, never an
admin bit.

The forwardable set is now a per-method table, consulted before the token is
attached, 404 on anything else. Per-method because payouts is a GET read and a
POST mint on one path — a method-blind set hands the mint to every reader.

Nothing reachable today: commerce's mint is not compiled into this binary and
commerce.hanzo.svc resolves here. But devnet runs a real mint-capable commerce
and points cloud-api at it under a second name for the same thing; unifying
those names would arm it. The gate should exist before that cleanup does.
2026-07-16 18:54:20 -07:00
blue 0c92f38c9d Gate the billing bridge on an allowlist: the service token is authorization
/v1/billing/* forwarded any subpath to commerce carrying the admin
COMMERCE_SERVICE_TOKEN, validated only against path traversal. Forwarding IS
authorization there: commerce gates money-mint on
MayMintMoney = IsServiceToken || IsSuperAdmin, so every forwarded path ran with
platform authority. Commerce 403s an org admin who POSTs /v1/billing/deposit
directly; through this bridge the same person was handed the platform's own
credential, and the subject-pinning aimed the credit at their own account.
Pinning is an IDOR control, not an authority control.

Add billingForwardable: a per-method allowlist of the endpoints the console
actually calls, enforced before the token is attached. An unlisted path 404s.
Allowlist, not denylist — a mint route commerce adds tomorrow is unreachable
with no change here. GET and POST are separate sets because `payouts` is a read
AND a mint-gated write; one method-blind set would hand the mint to every reader.
The POST set holds nothing that creates balance from a client-named amount.

Not exploitable in the current topology: commerce is co-resident in cloud, whose
build never compiles mount.go (//go:build cloud), so no api.Route billing bundle
is reachable and the forward loops back to this bridge. It is one COMMERCE_URL
away from live — devnet already runs a standalone commerce.

Tests: an ordinary org user's deposit/credit/refund/credit-grants/husd/allotment
now never reach commerce; the console's 12 real calls still forward; the store
bridge still cannot tunnel into billing.
2026-07-16 18:36:07 -07:00
hanzo-dev 08fc4ff7fb Embed zen v1.4.0 so the prompt-cache fix reaches production
zen v1.4.0 bills the prompt cache: cache_read was priced in the catalog,
published in /v1/models, and never charged. cloud pinned v1.3.11, so the
fix could not reach api.hanzo.ai, where the traffic lands.

The module graph cannot move: zen's own go.mod is byte-identical between
v1.3.11 and v1.4.0 (same sha256), and cloud holds exactly one zen edge.

NOTE: this is necessary but NOT sufficient. hmoney.Minor() returns cents
while cloudmoney.FromInt expects atto, so apps/zen.go understates every
debit by 1e16 and the spend gate reads AmountCents 0. Correct pricing is
still zeroed downstream. Tracked separately; that fix is what makes cache
billing real.
2026-07-16 18:21:12 -07:00
hanzo-dev 4efbb5faea openapi: serve GET /v1/openapi.json generated from the live router
The route table gets a third projection. /zap replays the /v1 handlers, the
console renders them, and GET /v1/openapi.json now describes them — all read
from the ONE router after MountAll, so none can drift and none holds a second
copy. There is no checked-in spec file and no second registry.

openapi.Live(app) reads app.Fiber().GetRoutes(true) (fiber's own filter drops
Use() middleware); every other function is pure over that []Route. Each
operation is tagged with its product — the first path segment after /v1/ —
so a CLI can build `hanzo <product> <resource> <verb>` with no judgment.

Reading the LIVE router is the only total source: POST /v1/kms/auth/login is
registered as Group("/v1/kms/auth").Post("/login") and no grep can find it,
and the route set is a function of deployment config, so the document varies
per deployment — correctly. Unauthenticated: it grants no capability, every
route it names stays auth-gated, and `hanzo --help` must build its tree
before login.

The drift guard (cmd/cloud/openapi_test.go) is a bijection over the fully
mounted apps.Wire(): 983 operations / 692 paths / 109 products, every live
route present, no operation invented. Shown to fail on a broken translation
(353 routes reported missing) before being restored.

Honest boundaries, asserted rather than papered over:
  - No schemas. The router holds func(*zip.Ctx) error; the request type is a
    local inside the handler (var req secretPutRequest; json.Unmarshal(...)),
    unreachable by reflection. cloud.Handle[S] is generic over the SERVICE,
    not the payload. The path to schemas is zip's typed ops, which today
    number zero — which is why zip's own generator emits nothing here.
  - No responses block. OpenAPI 3.1 makes it optional; fabricating 200/ok on
    ~900 routes would assert what nothing knows.
  - HEAD/CONNECT excluded — forced, not taste. CONNECT has no OpenAPI field;
    fiber auto-generates HEAD in startupProcess(), so including it would make
    the document depend on lifecycle stage.
  - Catch-alls are opaque: POST /v1/billing/deposit is not a route here.

Corrects LLM.md, which the code contradicted: Wire() does exist (apps.go:188),
MountAll does not sort, and byte-identical patterns MERGE rather than panic.
A high handler count is not a collision — app.Post(path, mw1, mw2, mw3, h) is
one registration with four handlers (apps/commerce.go:151), and 34 live routes
are that shape, so the generator never reads the count.
2026-07-16 18:14:23 -07:00
antje f3c2d2b98c cloud: mount hanzoai/agent /v1/agent (no-shim); delete dead clients/chat
clients/agent adapter injects the ai completion (in-process, billed) + tools.Default()
into github.com/hanzoai/agent; POST /v1/agent live path. Dispatch resolves the caller
via the ONE canonical tools.PrincipalFrom — no reconstructed principal. Builds green
on the v1.801.35 base. DEPLOY-BLOCKED: go.mod uses a local replace for hanzoai/agent
(CI needs a fetchable release + the local module-cache shallow-clone bug resolved).
2026-07-16 18:00:50 -07:00
hanzo-dev 491141790f Bill the prompt cache in production: zen v1.3.11 -> v1.4.0
cache_read was priced in the catalog and published in /v1/models, but never
charged: on an openai upstream every cached input token billed at the full
`in` rate, and on an anthropic one it left the bill entirely. zen v1.4.0
normalizes both dialects into one tally over three disjoint classes
(fresh + cached + cacheWrite == the whole prompt) and derives once per
response. cloud embeds zen via apps/zen.go, so the fix is inert at
api.hanzo.ai until this pin moves.

zen v1.4.0's go.mod is byte-identical to v1.3.11's, so the require edit and
the two go.sum lines are the whole change: no transitive pin moves, and
nothing else in the graph names zen.
2026-07-16 17:49:16 -07:00
hanzo-dev 8e6e81d6da Merge: fix the zen margin test's decimal + money types (unblocks CI on main) 2026-07-16 17:48:36 -07:00
z 5a8218bb53 apps: price the zen test with the decimal money actually uses
The zen margin test never compiled, so CI has been red on main since it landed:
it parsed prices with shopspring/decimal and handed the result to hmoney.New,
which takes hanzoai/decimal. Two identically-named types, one of them wrong.

    vet: cannot use d (struct type "github.com/shopspring/decimal".Decimal)
         as "github.com/hanzoai/decimal".Decimal value in argument to hmoney.New

Money has exactly one decimal. A second one that merely LOOKS like it is how a
price silently becomes a different number, which is why the compiler is right to
refuse. Parse with hanzoai/decimal (decimal.Parse — the same call zen itself
prices with); this was the only file in cloud importing shopspring.

Read the debit through Amount.Int(), not Amount.Minor(). The test held two money
types at once: zen's hanzoai/money.Amount (Charge/Cost) has Minor(), but
meterUsage returns cloud's clients/money.Amount, whose accessor is Int() — it
wraps Minor() and returns the identical *big.Int, so the assertions are unchanged.

The tests themselves are worth keeping: they prove the debit is the retail Charge
and never the upstream COGS, that a 3x-margin tier collects 3x, and that a
sub-cent call does not floor to zero. They just could not run.

Not run locally: ./apps links a prebuilt Rust staticlib (libhanzo_flags.a) that
is built in CI, not here. vet — the step CI actually failed — passes, and the
package builds.
2026-07-16 17:48:26 -07:00
hanzo-dev 1ebcd3259d GOPRIVATE names the namespace that is actually private
GOPRIVATE named zap-proto/*, which is public -- all 55 repos, all 6 modules
cloud needs served anonymously from the public proxy. The namespace that is
private went unnamed: github.com/hanzoai/* (467 private repos incl. ai,
account, commerce, orm, xorm, beego, csqlite). It resolved only by falling
through GOPROXY's direct fallback, and passed checksums only because go.sum
already pins everything.

containment.yml then set GOSUMDB=off to compensate. GOSUMDB does not scope to
a namespace: that disabled checksum verification for every module in the
build, public ones included, in the image that handles payments -- breaking
the invariant the Dockerfile three files away states and honors.

Public modules keep proxy and sumdb immutability; private ones go direct and
authenticated. Verified under the CI and Dockerfile env with -mod=readonly and
sumdb on: build 0, go mod verify all verified.
2026-07-16 17:33:16 -07:00
hanzo-devandantje b9856a4408 feat(sync): universal /v1/sync engine — GitHub/GitLab ⇆ native Hanzo Git
One reconcile loop, one place a sync happens. clients/sync owns the Sync
record (source/target/direction/trigger/cursor), a per-org sqlite `sync`
table, /v1/sync CRUD + /v1/sync/:id/run, and a kind→Provider registry with a
single Reconcile(sync,event) contract. Git is the first provider, composing the
existing git object-plane seams (InboundGitSync inbound, ImportGitRepo reconcile,
EnsureGitMirror outbound) — no second copy of any git op.

Triggers resolve to Syncs and enqueue the engine (cloud.Sync), never sync
directly: the GitHub App webhook now serves the path it actually fires at
(/v1/github-webhook, was a prod 404 at /v1/integrations/github/webhook) and hands
the verified push to the engine; the Gitea push webhook gains a loop guard
(skip pusher == GIT_SYNC_ACTOR). Loops break on the engine cursor (identical
fingerprints are a no-op) + actor guard; chained propagation (a sync's target is
another's source) is bounded by a hop limit.

Seams (root cloud): SyncFunc + RegisterSync/Sync, GitMirrorController +
EnsureGitMirror. Fail-closed on unmounted engine / missing secret. Tests
(CGO_ENABLED=0): engine loop-guard/idempotency/chain/hop-limit, git resolve,
CRUD+patch+run, webhook signature/isolation/enqueue, gitea loop guard.
2026-07-16 17:26:06 -07:00
hanzo-dev 97072d0443 build: GOPRIVATE names the namespace that is actually private
GOPRIVATE listed github.com/zap-proto/*. Every zap-proto repo is public — all 55
of them — and every zap-proto module this build needs is served by the public
proxy anonymously. It was never the reason anything resolved direct.

The namespace that IS private went unnamed: github.com/hanzoai/* — ai, account,
commerce, orm, xorm, beego, csqlite and ~30 more. Those only ever built by
falling through GOPROXY's `direct` fallback after the proxy 404'd them, and only
kept passing the checksum step because go.sum already pins them, so no sumdb
lookup happens. It worked by accident, one added dependency away from failing.

containment.yml compensated for that unnamed namespace with GOSUMDB=off, which
does not scope to hanzoai — it disables checksum verification for EVERY module in
the build, the public majority included. The Dockerfile's comment reasoned the
same way inverted ("hanzoai/* and luxfi/* are PUBLIC ... only zap-proto/* is
exempt"); hanzoai/* is largely private and luxfi/* (all 37 deps here) is public.

Naming github.com/hanzoai/* is what the off switch was standing in for. GOPRIVATE
implies GONOPROXY+GONOSUMDB for exactly that namespace, so the private modules go
direct+authenticated and skip the sumdb that cannot see them, while zap-proto and
luxfi keep the public proxy + checksum db — the immutable hashes that make a
force-moved tag unable to break or poison the build. GONOSUMDB and GOSUMDB=off
are dropped: scoped by GOPRIVATE, they are redundant, and blanket-off is a
supply-chain regression in a money image.

hanzoiam/* is not listed: 12b6e1c reverted the scim/saml/ldap embed, so nothing
in go.mod requires it. It goes back when the modules resolve, named as private.

Verified under the exact CI/Dockerfile env (GOPRIVATE=github.com/hanzoai/* only,
GOSUMDB=sum.golang.org, GOFLAGS=-mod=readonly): build exit 0, vet exit 0,
`go mod verify` = all modules verified, and `go mod download` resolves both a
public module (zap-proto/zip) and a private one (hanzoai/ai).
2026-07-16 17:21:31 -07:00
antje 563856fc88 deps: ai v1.816.0 -> v1.817.0 — global auto-routing switch is the '*' settings row, not ROUTER_ENABLED env (config-as-Base)
Runtime routing policy now sources from the GlobalDefaultOwner OrgSettings
row (admin.hanzo.ai-editable SQLite), env demoted to deprecated fallback.
Per-org override unchanged.
2026-07-16 17:16:33 -07:00
hanzo-dev d5266685d0 paas: read the kind the fleet runs on, and don't fight the git declarer
The PaaS control plane serves platform.hanzo.ai and read `services` only. The
fleet collapsed onto `kind: App` and this reader never followed: 69 App CRs run
across the scanned namespaces against 7 Service CRs, so the SUPERADMIN drift
board rendered 7 rows for a 69-app fleet — 1 row in `hanzo`, production, and that
row is a duplicate CR. It was not an error anyone could see. The board looked
plausible and was blind to 68 of 69 services; every read of an App-declared
service 404'd; and /v1/paas/health probed the Service CRD, found it served, and
reported ok — status theater over a blind board. clients/deploy already solved
this with an App-first/Service-second read order; this gives the same order to
the reader that needed it.

Both kinds are listed and deduped by name: one workload is one row even when an
App CR and a Service CR both claim the name, because a Deployment has one
controller ownerRef and the operator's Claim guard gives it to the App.

The write path is the harder half. Hanzo CD syncs 68 of the 69 App CRs from
universe `infra/k8s/operator/crs/` with selfHeal on, so patching an App CR here
is reverted on the next sync — the deploy would report success and silently roll
back. That is worse than refusing, so deploy and release now resolve which kind
holds the workload and refuse a git-declared one, naming the file to commit to.
A Service CR has no git declarer (cloud and kubectl write them directly), so it
still patches exactly as before — the tenant plane and the untransitioned CRs are
untouched. release.go's "no ArgoCD" claim was true when written and is not now.

This does not restore an admin deploy button for the git-declared fleet. Under
GitOps that button belongs in git, and ImageUpdate already names that seam
(registry→git→cluster). Whether /v1/paas/deploy should commit to universe or be
retired is a CTO call, not one to make silently inside a read fix.

Tests: 35 pass, 0 fail, including the pre-existing release suite. The fleet-sees-
App-CRs case is seeded to the shape of the real `hanzo` namespace.
2026-07-16 17:12:40 -07:00
antje 12b6e1c118 revert(iam2): back out scim/saml/ldap embed — hanzoiam repos do not resolve
Reverts 3aaf9d23. go.mod pinned github.com/hanzoiam/{ldap,saml,scim}, but none
of the three repos exist: https, ssh, and API all return not found, and ldap
was never fetched by any proxy or cache. Cold machines — including release
runners — fail go mod download, so main could neither build nor release.
Local builds passed only on module caches warmed 21:36-21:48 UTC today.

iam2 restored to v0.1.1, the state prod v1.801.38 ships. Re-land the embed
unchanged once the hanzoiam repos exist and resolve from a cold GOMODCACHE.
2026-07-16 17:01:45 -07:00
hanzo-dev 25cecf25a2 Merge: one name for the account, one for the org — and the last copy of the payer rule deleted 2026-07-16 16:38:08 -07:00
z ecc9b2ab54 billing: one name for the account, one name for the org
Two functions were called Payer and returned different things: account.Payer
returns the ACCOUNT that pays, principal.Payer returned the ORG whose ledger
holds it. Those are different values on the same request — a person in the shared
signup org pays from account "hanzo/alice" held in ledger "hanzo" — and one name
for both is how the gate came to key the pool while the debit spent the person.
Rename it to what it returns: principal.HomeOrg. An org names a ledger; an
account names a wallet within it.

Fix the last copy of the rule with it. clients/metering is cloud's vendored
metering client, and its IdentityFromGatewayHeaders still hardcoded `user := org`
under the same false premise, while its doc claimed cloud "mirrors" the module
"exactly so every product keys the SAME ledger entry" — a promise two independent
copies cannot keep. Both now call hanzoai/account.Payer, so they agree by
construction and the comment is true for a reason.

Its test asserted the divergence in words — "want hanzo (per-org billing key, not
org/sub)" — which is how a premise outlives the code that disproved it. It now
asserts equality with the rule.
2026-07-16 16:37:43 -07:00
hanzo-devandz 70e4ab8887 build(cloud): mirror base images to ghcr.io/hanzoai/mirror/* (kill public.ecr.aws 429s)
public.ecr.aws (ECR Public) rate-limits anonymous pulls with HTTP 429 on shared
CI runners; a 429 on any base pull aborts the release (a release died pulling
python:3.12-alpine). Repoint all five FROMs to 1:1 linux/amd64 mirrors in our
own GHCR namespace, pinned by digest for immutability:

  node    ghcr.io/hanzoai/mirror/node:24-alpine@sha256:0cb0e7c3195bce740b6c8d8b27432c92360e3b7f1528087f2c50640b177950c6
  python  ghcr.io/hanzoai/mirror/python:3.12-alpine@sha256:aa679aa4eed6eb56c1dc6ad3f1b98b7d2d788fd961596779d188fdedad97fb38
  rust    ghcr.io/hanzoai/mirror/rust:1-alpine3.22@sha256:b348cb409ac0a73de15065997a360063cf87465574a15e3e4469862cb8996f02
  golang  ghcr.io/hanzoai/mirror/golang:1.26-alpine3.22@sha256:47d47cb5cc3c7dac409dcb6c3a98a6263571218046cd02d709527feef804a77c
  alpine  ghcr.io/hanzoai/mirror/alpine:3.22@sha256:7c8cb692ae09657cbc4a3f3cbd0e8d5a2690ba38386aaaf252dbb060bf5eb2e6

The four the task named plus alpine:3.22 (the final-stage base — same registry,
same 429 exposure) so no FROM still hits public.ecr.aws. release.yml already
logs the build into ghcr.io (GH_PAT, docker/login-action) before building, so
buildx resolves these private mirrors today with no new plumbing. Only the five
FROM lines + one rationale comment change; nothing else in the Dockerfile.
2026-07-16 15:48:48 -07:00
hanzo-dev f9b2060faa feat(ai): bump ai v1.814.0 → v1.816.0 — router self-probe, flywheel trainer, casibase metering
Ships the full router flywheel into the cloud binary: the self-probe
(continuous tagged auto traffic → reward ledger), the fit→gate→auto-deploy
→publish trainer, the routing-latency guard (~0.68us heuristic), and
casibase-chat usage/o11y metering. Also carries the zen warehouse+span
wiring already on main.

Migrates the billing-subject callers (balance.go, account/billing.go +
tests) from the ai/object.Payer that v1.816.0 REMOVED to the extracted
github.com/hanzoai/account.Payer — the same rule in its new home (the
concurrent decomplect). Same replace directive for the force-pushed iam
pseudo-version account v0.2.0 pins.
2026-07-16 15:32:35 -07:00
z 88453727c1 probe: pin what zip typed ops can bind, before migrating 792 routes onto them
zip.Get[In, Out] is advertised as ONE op projected into three surfaces (REST ·
OpenAPI · MCP), and cloud's raw routes were slated to migrate onto it starting
with clients/agents. Measured first, against the route shapes cloud actually
has.

The registry works: registering one typed op populates /.well-known/openapi.json
and the /mcp tool surface, both of which are absent today only because cloud
registers zero typed ops (installOpenAPIRoutes/installMCP early-return on
len(a.ops)==0).

The binding does not. registerTyped's fiber handler passes c.Body() — nil for a
GET — into op.invoke and nothing else, and fiber's DefaultCtx.Context() returns
context.Background(). So a typed handler sees no path param, no query param, and
no header. 16 of clients/agents' 25 routes carry a path param and would receive a
zero In; the ?live/?host/?status/?agent filters would vanish; and the org, which
every agents handler reads via principal.Org(c) -> tenant(c) -> 403, is
unreachable. Migrating as-is would answer the wrong session for every :id route
and drop the authz gate on all of them.

MCP is the sharp edge: tool arguments arrive as the body, so MCP is the ONE
projection that DOES fill In, and mcpCall runs op.invoke with no identity at all.
A migrated org-scoped op would answer an anonymous caller, and the only way to
give it an org would be an org field in the typed In — caller-supplied, i.e. a
cross-tenant read. Both horns are unacceptable, so clients/agents does not
migrate at this zip version.

The org half needs no framework change: fiber's SetContext (already used by
TracingMiddleware) is honored by the ctx registerTyped hands to op.invoke, so
middleware can carry the validated org to a typed handler off the wire, over REST
and MCP alike, without an In field. TestPrincipalBridgeCarriesOrg proves it on
stock zip. Only URL binding is missing.

These are characterization tests: they pin the gap as the current contract and
fail with "UNBLOCKED: invert this test" the moment zip binds a URL, so the
migration restarts on a failing build rather than on someone remembering.
2026-07-16 15:14:25 -07:00
hanzo-dev 94aa7b4791 ci(cloud): GOPRIVATE += github.com/hanzoiam/* (enterprise IAM modules)
The iam2 embed pulls github.com/hanzoiam/{scim,saml} (+ ldap under -tags iam2_ldap).
hanzoiam is a distinct org from hanzoai, so hanzoai/* did NOT cover it — the test
phase would route these private modules through the public proxy/sumdb and 404.
Git auth is already handled by the reusable CI's GH_PAT insteadOf (covers any
github.com private repo the PAT reads).
2026-07-16 15:04:30 -07:00
zeekay 3aaf9d2374 feat(iam2): wire SCIM + SAML into the cloud embed; LDAP GPL-isolated behind -tags iam2_ldap
Last code step of the iam2 migration. clients/iam2 blank-imports the Apache-2.0
enterprise features so their init() self-registers into iam2's feature registry;
iam2server.Mount -> feature.MountAll auto-mounts them under CLOUD_IAM_IMPL=iam2.
ONE mechanism (database/sql driver pattern) — no feature.Register call in cloud,
which (feature.Register appends with no dedup) would double-mount and collide routes.

  _ github.com/hanzoiam/scim   SCIM 2.0 provisioning  (/scim/*)
  _ github.com/hanzoiam/saml   SAML IdP + SP SSO      (/v1/iam/saml/*, /v1/iam/acs, /v1/iam/get-saml-login)

LDAP is GPL-isolated: hanzoiam/ldap links goldap (GPL-2.0), so it is opt-in only via
clients/iam2/ldap_enabled.go (//go:build iam2_ldap). The DEFAULT cloud binary stays
copyleft-free — proven: `go list -deps ./clients/iam2/` has no goldap; only under
-tags iam2_ldap does it pull github.com/lor00x/goldap + hanzoai/ldapserver.

deps: hanzoai/iam2 v0.1.1->v0.1.4; + hanzoiam/{scim,saml,ldap}; go mod tidy.
2026-07-16 14:59:47 -07:00
hanzo-devandz 2aeea28f7a feat(kms): one-time legacy ZapDB -> per-org SQLite migration (deploy-safe cutover)
Without this, deploying the per-org store over live data boots an EMPTY store and
orphans every secret — cloud KMS is the authoritative source the kms-operator syncs
out to every service, so that is a cluster-wide outage. New() now runs a one-time,
writer-only, keyed, FATAL-on-error migration BEFORE serving: it opens the legacy
{DataDir}/kms ZapDB (encrypted at rest with the master key), streams every SEALED
secret (kms/secrets/ prefix; the JSON value carries the full coordinate + AES-GCM
ciphertext + ML-KEM wrapped DEK) verbatim into its per-org SQLite file via store.put
— NEVER unsealing, so no plaintext is exposed and the AAD path-binding survives —
then archives the legacy dir to {DataDir}/kms.migrated so the OS lock is released for
good. Idempotent (prior .migrated marker or absent store = no-op; put upserts).

Tests: migrate roundtrip (opens to same plaintext), no-legacy-store no-op, and the
cross-org relocation defense still holds after migration. Full kms suite green (2
pre-existing admin-edge fails only).
2026-07-16 14:55:16 -07:00
hanzo-devandz 28ff703da0 feat(kms): per-org SQLite store — replaces OS-locked embedded ZapDB, lifts replicas=1
The embedded luxfi/kms ZapDB (a Badger fork) held an exclusive OS lock on ONE dir
for ALL orgs — the hard reason cloud ran replicas=1 behind a cross-process writer
lease. This replaces it with per-org encrypted SQLite ({DataDir}/orgs/{org}/kms.db
via cloud.OrgDB->cek, per-db DEK), which has no exclusive-opener lock, so distinct
tenants never contend and different pods can serve different tenants.

Crypto stays in the client (Seal/Open AES-256-GCM envelope, AAD-bound to the FULL
/orgs/{org} path): plaintext never reaches the file, and a record physically moved
into another org's file still fails to Open (cross-org swap defense preserved).
Adds cloud.PlatformDB for the reserved non-tenant (_platform) partition.

Verified: 54 PASS / 2 FAIL in clients/kms; the 2 fails (admin-edge dualmount/authz)
are PRE-EXISTING — proven failing identically on origin/main. concurrent_open_probe
proves per-org SQLite has no exclusive lock. Build + finance (pure-Go) green.

Branch only — NOT for main/deploy until red review passes.
2026-07-16 14:55:16 -07:00
zandhanzo-dev 6e417599c3 billing: the edge gate keys the account the debit spends
The gate keyed `user := home` — the org pool, always — on the premise that
prepaid billing is per-org. That premise is false. A person in the shared signup
org holds their OWN account: its members are strangers, not a team, and a shared
org is not a shared wallet. That is what IAM's signed billing_account claim states
and what ai's meter debits.

So the gate authorized against a balance nobody drained. Fund the pool and a
signup-org person still 402s, because their usage comes out of their own account;
fund the person and an empty pool blocks them anyway. Two layers, two answers, one
request.

Resolve through hanzoai/account.Payer — the same function ai debits with, on the
same credential — so the gate and the debit cannot name different accounts. The
premise is removed rather than restated.

The masquerade split is preserved by construction, not by care: the account is
resolved WITHIN the home org, so Account.Org IS the home org and a SuperAdmin
acting in another org still bills their own ledger. A claim naming a foreign
ledger is refused, so it cannot redirect a debit into the org being acted on.

Tests assert against the rule rather than a constant, so they cannot drift the way
the premise did: the signup-org person keys their own account, a real org pools,
the claim wins for a person and a project, and every case is checked equal to what
the debit computes.
2026-07-16 14:42:34 -07:00
hanzo-dev f00f549739 merge: iam2 embed subsystem — CLOUD_IAM_IMPL selects beego (default) or iam2
clients/iam2 mounts the clean-room zip+orm IAM at /v1/iam when CLOUD_IAM_IMPL=iam2,
else beego, byte-for-byte unchanged. Flag OFF by default → inert. iam2 v0.1.1 seam.
2026-07-16 14:38:03 -07:00
hanzo-dev 18537ce994 feat(iam2): select /v1/iam impl via CLOUD_IAM_IMPL (default beego, unchanged)
apps.Wire's identity slot now calls identitySpec(): CLOUD_IAM_IMPL=iam2 mounts the clean-room iam2 (zip+orm), anything else — including unset, the production default — keeps the legacy beego Casdoor embed byte-for-byte. The two impls own the SAME absolute prefixes (/v1/iam/*, /login/oauth/*) and cannot co-mount, so exactly one occupies the slot per boot and mount order is preserved. Off by default => completely inert until a canary flips the flag; selection (this) stays orthogonal to activation (cfg.Enabled).
2026-07-16 14:32:15 -07:00
hanzo-dev 509d0f8ff3 feat(iam2): clean-room IAM v2 embed subsystem (zip+orm, beego-free)
clients/iam2 folds the beego-free Hanzo IAM v2 into the unified cloud binary as an in-process identity plane — the either/or twin of clients/iam. Matches the cloud.Typed contract func(*zip.App, cloud.Deps) error: cloud hands subsystems a cloud.Deps (not an orm.DB), so Mount opens its OWN embedded SQLite ({DataDir}/iam2/iam.db, mirroring the beego embed's {DataDir}/iam layout), seeds config new-only+idempotent from the SAME init_data.json the beego iam uses (non-fatal, honest degrade), then iam2server.Mount registers the whole surface at the canonical absolute paths.

Fail-closed like clients/iam: a store-open or mount failure serves 503 on the identity prefixes while every co-resident subsystem stays up; iam2server.Mount's only panic path (a registered enterprise feature) is recovered in safeMount so it never crashes the shared binary. A TODO marks where the parallel-lane hanzoiam/{scim,saml,ldap} feature.Register lines land.

Pins github.com/hanzoai/iam2 v0.1.1 (seam held stable across the parallel internals refactor); transitive MVS bumps are all patch-level within v1.x (zip 1.8.3, orm promoted to direct, luxfi/crypto 1.20.1, argon2id 1.0.0, pgx 5.9.2). Inert until wired — see the apps.Wire gating follow-up.
2026-07-16 14:32:06 -07:00
hanzo-dev dc9cb10b43 fix(ci): bound the SECOND version scan too (compute step) — same unbounded --paginate
The compute-next-version step had the same full-registry --paginate as the tag
step (fixed in b72394f). It ran first, so it could hang before the build. Bound
it to one page too. Both version scans are now O(1 page), not O(registry).
2026-07-16 14:28:00 -07:00
hanzo-dev 10362142a1 feat(zen): warehouse + gen_ai span emission with exact margin — ai v1.814.0
zen's commerce Meter now also calls ai's TraceServedUsage (recordTrace
WITHOUT recordUsage — the commerce debit stays the ONE billing source,
never doubled), carrying zen's exact per-tier retail (Charge) and upstream
COGS (Cost) folded atto→nano, so zen* traffic in the unified binary lands
in hanzo.cloud_usage + the o11y span plane with TRUE margin instead of
being warehouse-blind. Rides the ai v1.813.1→v1.814.0 bump; balance.go
(+ its drift-guard test) migrated to the renamed Payer/PayerOf API —
same subjects, one rule.
2026-07-16 14:26:17 -07:00
zandGitHub 6961df4901 Merge pull request #315 from hanzoai/cloud-zen-family-events
feat(zen): embedded-zen meter writes the family RoutingEvent (last link) + ai v1.813.5/zen v1.3.11
2026-07-16 14:08:50 -07:00
hanzo-dev b64c2daa65 feat(zen): embedded-zen meter writes the family RoutingEvent (the last link)
The embedded zen mount serves the zen catalog in-process and never reaches ai's
pipeToFamily, so zen* calls produced ZERO routing events — starving stats, world,
spark retrain, and /v1/feedback joins. Wire cloud's zen Meter to ALSO write the
RoutingEvent through the ONE shared writer object.RecordFamilyRouting (source="family",
served arm = zen.Usage.Upstream, join key = zen.Usage.ResponseID — the client-visible
response id, new in zen v1.3.11 — tokens + retail cost), fire-and-forget beside the
existing debit. Bumps zen v1.3.7 → v1.3.11 (Usage.ResponseID); ai already v1.813.6
carries object.RecordFamilyRouting.
2026-07-16 14:08:28 -07:00
antje 2763842079 git: Gitea push-webhook ingest (POST /v1/git/webhook)
The external Hanzo Git server (Gitea fork, git.hanzo.ai) POSTs push events
here so a push landing on it drives the SAME push-to-deploy core the embedded
smart-HTTP receive-pack path drives: fireBranchBuild -> cloud.OnGitPush deploy
trigger + EmitLifecycle. One code path, no duplication.

HMAC auth: X-Gitea-Signature is hex HMAC-SHA256 of the raw body, verified
constant-time against GIT_WEBHOOK_SECRET (KMS-synced hanzo/prod:/git/webhook-secret).
Fail-closed 401 on unset secret or mismatch. Only X-Gitea-Event: push acts;
others 204. Zero-SHA / non-branch refs are no-ops.
2026-07-16 12:05:08 -07:00
zandGitHub 670153907d Merge decomplect/account-payer: migrate to ai.Payer — unbreaks main, ends the self-serve 402
main pinned ai v1.813.6 (which deletes billing_subject.go for the Payer/Account
refactor) without migrating the call sites, so main did not compile:
  clients/billing/balance.go:59: undefined: aiobject.BillingSubject

This migrates the call sites to the ONE rule: Payer(Credential)->Account
(owner = Person|Org|Project). Ends the live 402 where a self-serve signup's top-up
minted to the shared org pool 'hanzo' while the gate debited 'hanzo/alice' ($0) --
customer paid, locked out, money in a pool their org-mates could spend.

Green: go build -tags 'libsqlite3 sqlite_fts5' ./clients/... rc=0;
go test ./clients/billing ./clients/account rc=0. go.mod/go.sum identical to main.
2026-07-16 11:51:27 -07:00
hanzo-dev e081547ad3 fix(billing): migrate off deleted BillingSubject → ai.Payer/PayerOf — unbreaks main
main pins ai v1.813.6, which contains the Payer/Account refactor (billing_subject.go
and its PERSONAL_BILLING_ORGS/ORG_BILLING_ORGS lying default are deleted). But the
call sites were never migrated, so main does not compile:
  clients/billing/balance.go:59: undefined: aiobject.BillingSubject
  clients/billing/balance.go:61: undefined: aiobject.BillingSubjectFromUserKey

Migrates balance.go + finance.go + billing.go to the ONE rule —
Payer(Credential{Owner,Name}).Subject() / PayerOf(org,key).Subject() — and DRYs the
duplicate subject resolvers. This is the cloud half of the fix that ends the live
self-serve 402 (top-up minted to the shared org pool 'hanzo' while the gate debited
'hanzo/alice' = $0).

go.mod/go.sum untouched vs main. Green: go build -tags 'libsqlite3 sqlite_fts5'
./clients/... rc=0; go test ./clients/billing ./clients/account rc=0.
2026-07-16 11:50:51 -07:00
hanzo-dev adfca0b3fe refactor(billing): route top-up + console subject through ai.Payer, one rule
The console top-up (clients/account/billing.go) and the finance read
(clients/billing/finance.go) each re-implemented the billing subject as "always
the org" — the reverted lineage's rule. Against ai's gate, which bills a signup
person per-person, that is the split: money minted to subject "hanzo" (the pool)
while the gate debited "hanzo/alice" ($0) → the paid-up member 402'd.

Delete both twins; resolve the subject through the ONE rule, ai/object.Payer,
keyed on the IAM username (X-User-Name) the gate also keys on. Top-up credits and
console reads now land on the SAME account the gate debits — they cannot drift
because there is one function. The killed PERSONAL_BILLING_ORGS / ORG_BILLING_ORGS
env is inert here too (test proves hostile values change nothing).

Requires ai v1.809.5, which must be tagged FROM ai main after decomplect/account-payer
merges — NOT off a branch. The prior one-rule fix was tagged off an unmerged branch
(v1.806.8/.9), main never got it, and every later tag resurrected the allowlists;
that is why this bug is live. go.sum refreshes via `go mod tidy` once the tag exists.
Verified locally via a replace to the ai branch: clients build + twin tests green.
2026-07-16 11:47:10 -07:00
antje f4f506f9be ci(release): retire notify-universe — Hanzo CD owns git→cluster sync
The repository_dispatch deploy hub is gone (universe image-update.yml
removed in universe d07cf945; the dispatches were silently suppressed by
the flagged sender account regardless). Deploys are declared-tag bumps in
universe crs/, synced by Hanzo CD (ArgoCD, ns hanzo-cd) and reconciled by
the operator. [skip ci]
2026-07-16 11:36:10 -07:00
antjeandGitHub 7e9bc187f1 deps: hanzoai/ai v1.813.1 -> v1.813.6 (balance-exempt routing config + enso family helper) (#314)
ai#102: /v1/get-routing-defaults + org-settings CRUD + routing-ledger
export are configuration metadata, never wallet-gated — unblocks reading
org routing defaults for $0-balance orgs and the operator platform flip.
Edge auto-routing billing tests green.
2026-07-16 11:28:33 -07:00
antje 69e21ecff1 platform: allow the self-hosted fleet registry in the native build lane
registry.hanzo.ai/{hanzoai,luxfi,zooai}/ join the /v1/runner push allowlist —
Wave 0 of the native CI/CD migration. Until now only release.yml's crane
mirror could reach the fleet registry; the native BuildKit lane was
ghcr-only by policy.
2026-07-16 11:13:07 -07:00
hanzo-dev b72394f461 fix(ci): version-assignment scanned the WHOLE registry — livelocked releases
The "atomic free-version assignment" step paginated every container version
(`gh api --paginate .../versions`) to find the max release number. As the
registry accumulated tags this grew unbounded and hung the step for 30+ min,
livelocking every cloud release. Container versions are created newest-first and
version tags are monotonic, so the max is always on the newest page — query one
bounded page (?per_page=100) instead of the full history. Fast + correct.
2026-07-16 11:11:39 -07:00
hanzo-dev e07d454096 refactor(ledger): drop redundant "core" — the ledger adapter is apps.ledger
Values, not places: the finance-backed credit-ledger adapter is qualified by its
namespace (apps.ledger), not a braided ledgercoreCredit compound. Rename the type
ledgercoreCredit → ledger, the file commerce_ledger.go → ledger.go, and scrub
"ledgercore" from prose (the ledger IS the core — "core" adds nothing). No behavior
change; admin/core tests green, changed packages build.
2026-07-16 10:18:47 -07:00
antje a2812e1505 feat(chat): clients/chat — one /v1/chat tool-calling orchestrator
POST /v1/chat runs one LLM tool-calling round that lets a model manage a system
via tools. Composes existing cloud pieces, reinventing nothing:
- LLM routing + per-org reserve/settle billing: the ai subsystem's
  /v1/chat/completions, invoked in-process (Fiber Test) — the only path that
  both returns tool_calls AND carries the billing gate.
- tool plane (clients/tools): the org's registered MCP/registry tools are
  offered to the model and dispatched server-side (activation + price gated).
- capabilities: graph (advisory node-ops -> ops the client applies) and create
  (server-executed, tools = the org's registered MCP render services).
Returns {reply, actions, ops}. chat mounts before ai so /v1/chat resolves here
(the ai /v1/chat alias is shadowed); ai keeps /v1/chat/completions.
2026-07-16 10:02:29 -07:00
hanzo-devandantje 630722d168 feat(ai): bump ai subsystem v1.813.0 → v1.813.1
Carries the PAID-Enso revert + the family learning loop: per-family-call RoutingEvents
+ shadow A/B (records what the learned engine would have picked), /v1/feedback signal
contract (up/down/regenerate/switch/abandon/accept/revert/rating/dismiss) with the
online reward forward to the engine's /route/observe, ROUTER_ADMIN_TOKEN service-auth
on the training-data exports, and Zen/Enso provider branding. Lights up /v1/router/stats
+ world.hanzo.ai (shadow-vs-served agreement).
2026-07-16 09:53:56 -07:00
hanzo-dev 404486a479 feat(ai): bump ai subsystem v1.812.0 → v1.813.0 — router policy, rewards, margin, DO backfill
Ships the per-org router policy (get/update-router-policy + the org > '*' >
conf fold on every auto route), the routing-reward ledger, the nano margin
ledger (costNano/billedNano/marginNano + unpriced flagging), and the
gaps-only DigitalOcean usage backfill (POST /v1/admin/usage/backfill-do,
dry-run default). The release image also re-embeds console@main
(CONSOLE_REF=main), picking up the console Router page (v8.4.137+).
2026-07-16 09:28:20 -07:00
hanzo-dev 8fff1a33cc feat(credit): ONE ledger seam — commerce credit + admin grant mint into finance.Current()
The last mile of "one way to grant credit": cloud implements commerce's
creditledger.CreditLedger (v1.48.5) over the native finance ledger and injects it
at mountCommerce (EmbedConfig.Ledger). Now commerce's POST /v1/billing/credit AND
the admin.hanzo.ai grant (/v1/admin/customers/:org/credit) both mint into the SAME
per-org finance wallet the ai prepaid gate reads — a granted credit is immediately
spendable, no split ledger. The admin path drops its parallel finance.Deposit for
the one creditledger.Credit call (idempotency key rides through; commerce HTTP
deposit remains the split-deploy fallback).

- apps/commerce_ledger.go: ledgercoreCredit adapter (compile-time asserted against
  commerce's exported interface); org-pool wallet (Subject==Org); fails closed with
  no co-resident finance.
- apps/commerce.go: inject Ledger: ledgercoreCredit{} at mountCommerce.
- clients/admin/core/grant.go: grantDeposit prefers creditledger.Get() (the one
  ledger) over its own finance.Deposit.

Verified: changed pkgs build green on commerce v1.48.5 + ai v1.812.0; admin/core
grant tests pass. Ships with the ai free-tier removal (v1.811.0+) already on main.
2026-07-16 09:14:59 -07:00
antje 2db0bcf87f ci(release): pass GIT_AUTH_TOKEN build secret — Dockerfile renamed the id from gh_token (45387fb7) but the workflow still passed gh_token, so the private console clone ran credentialless and the release failed 2026-07-16 01:50:00 -07:00
antje 45387fb70f build: consume the standard GIT_AUTH_TOKEN build secret (was gh_token)
One secret id everywhere: BuildKit's gitsource convention (GIT_AUTH_TOKEN,
which the fabric's buildFrontendCmd already attaches) is also what the
Dockerfile's console-embed and go-mod fetch stages mount. gh_token was a
second name for the same credential.
2026-07-16 01:19:03 -07:00
antje efc1c5152d deps: hanzoai/ai v1.812.0 + commerce v1.48.5 — reward ledger, router policy, connections import reach prod
ai v1.809.4 → v1.812.0: RoutingEvent reward ledger (/v1/add-routing-reward,
/v1/export-routing-rewards), per-org router policy + observability, Enso
public arms + retrain-status, connected-provider usage import (OpenAI/
Anthropic), own-brand god-view gate (TokenIsOwnBrand), Bearer-aware
get-cloud-usages, billing nano margin ledger, unpriced-model flagging.

commerce v1.48.2 → v1.48.5: mint-gated org-keyed credit primitive +
injected-ledger seam; fixes the phantom luxfi/cevm test import that broke
go mod tidy for every consumer (this repo included).
2026-07-16 01:16:12 -07:00
antje 2cbbbb31ec feat(fabric): GIT_AUTH_TOKEN build secret — private-repo fetches for the build Jobs
The buildkit Job now surfaces the console-git-token Secret (optional) as the
GIT_AUTH_TOKEN env, and buildctl attaches it as the same-named build secret;
BuildKit's gitsource presents it as the HTTPS credential for the git context.
Fixes the fabric's inability to build PRIVATE repos (github.com/hanzoai/cloud
itself: 'could not read Username' — the rel_HvInGKU failure). Public repos and
Secret-less clusters fetch anonymously exactly as before.
2026-07-16 01:15:07 -07:00
antje f459e889d5 feat(git): public repos — anonymous read for the build fabric
A repo gains a visibility bit: PATCH /v1/git/repos/:name {"public":true}
(or create-time "public"). Public grants ANONYMOUS upload-pack/info-refs
only — receive-pack and the whole control plane stay org-authed, and a
private or missing repo answers the same uniform 404 so anonymous probing
cannot enumerate.

This is what lets the credential-less buildkit build Job (launchDirectBuild
git context) fetch from the embedded git server — the same reason public
GitHub repos build with no env. Private-repo builds remain a later
GIT_AUTH_TOKEN feature.

resolvePackRepo grows the allowPublic branch (fetch-side only): anonymous
callers address org-level repos by the orgRE-validated :org path segment;
the path-vs-identity guard for authenticated callers is unchanged.
2026-07-16 01:05:30 -07:00
antjeandGitHub d6b4361822 test(platform): end-to-end git push -> buildFromPush enqueue proof (#311)
Wire a REAL smart-HTTP git push through the actual production seam
(cloud.RegisterPushBuilder <-> cloud.OnGitPush) into the real platform
push builder, and assert the matching app's build is enqueued (a
building deployment for the pushed commit). The two halves were covered
in isolation (clients/git TestPushFiresBuildTrigger; platform
TestBuildFromPush_LaunchesMatchingApp) but nothing connected a live push
to the real builder end to end. Pure-Go dev build (CGO_ENABLED=0).
2026-07-16 00:45:07 -07:00
hanzo-dev b02257731f Merge land/slack-on-bridge: Slack chat path onto the generalized bridge — one chat code path 2026-07-16 00:15:57 -07:00
hanzo-dev 42e6bf84a1 refactor(integrations): Slack chat path onto the generalized bridge — one chat code path 2026-07-16 00:13:59 -07:00
zandGitHub f469043773 Merge feat/bots-control-plane: decomplect the bot plane, proxy instead of duplicate
Deletes clients/bot — a place-name that had collected three concerns (a mount, a
transport, and two unrelated domain wire protocols). One value per module:
  run       -> clients/bots      /v1/bots (no store)
  dispatch  -> clients/coding    /v1/coding-tasks
  transport -> clients/runtime   address, identity, framing, cleartext policy
  machine   -> clients/visor     /v1/compute/bots (moved off /v1/bots)
  session   -> clients/agents    the one registry (reverted to main)

Fixes a live route collision: visor's listBots silently won GET /v1/bots (the
router merges byte-identical patterns, first wins), so cloud served machine rows
as runs and orgs' real runs were invisible.

POST /v1/bots/run now returns 501 instead of charging $1.00 for a bot that never
booted -- the runtime has no launch endpoint. Stop fails closed: a bare 404 is
502, only a structured error body means already-stopped.

Net -613 lines. runtime never imports bots/coding; the reverse is a compile-error
cycle, so the one-way dependency is structurally enforced.
2026-07-15 23:27:48 -07:00
zandGitHub afbf789dc6 Merge fix/billing-balance-collision: read prepaid balance from the finance ledger, not a self-call
Cloud's /v1/billing/balance proxy was the only handler registered (commerce's
GetBalance is behind //go:build cloud, never compiled in) so it called itself,
depth 2. Reads the finance ledger via the existing finance.Current() seam and
single-sources the subject from aiobject.BillingSubject so console and gate
cannot drift.
2026-07-15 23:27:02 -07:00
zandGitHub 5d56b479ea Merge pull request #310 from hanzoai/bump/ai-v1.809.4
chore(ai): bump embedded ai v1.809.3 -> v1.809.4 (enso comp cold-cache fix)
2026-07-15 23:07:00 -07:00
hanzo-dev a0d75f185f chore(ai): bump embedded hanzoai/ai v1.809.3 -> v1.809.4 (enso comp cold-cache fix) 2026-07-15 23:06:41 -07:00
hanzo-dev c65427feaa bots: proxy the runtime instead of copying its state; name the transport
Red found the substrate was wrong: cloud kept its own registry of runs. It minted
an id the runtime had never heard of, so /v1/bots listed runs that did not exist,
stop closed records for runs that were never started, and run charged $1.00 for a
bot that never booted — the runtime has no launch operation at all, and nothing
in run ever contacted it. The registry that exists is the runtime's own tenant
store; it is the only thing that knows whether a sandbox is alive.

So cloud owns policy and the runtime owns the run:
  - GET /v1/bots and POST /v1/bots/:runId/stop proxy the runtime, gated by the
    validated principal and org. The org is cloud's, never the client's, and the
    runtime keys every run under tenants/{org}/ — so a foreign run resolves under
    the caller's org, where it does not exist, and 404s.
  - POST /v1/bots/run returns 501. There is no launch operation to call, so the
    honest answer is that it is not implemented. It no longer charges.
  - The agents session plane is reverted verbatim: no surface column, no Agent
    filter, no SessionOpen, no in-process stop. It never should have carried a
    second copy of the runtime's state.

Absence is only meaningful from a callee that could have said otherwise, so the
transport separates ErrNotFound (the operation ANSWERED absent) from ErrNotServed
(no such operation). A runtime without the stop route reports absent for every
run; treating that as "already stopped" made a stop that cannot fail. It is 502.

Decomplect the transport: clients/bot was named for the host it dials and braided
three concerns — an ops face plus two unrelated domain protocols. It is now
clients/runtime, a domain-free transport (address, identity, framing, cleartext
policy, /v1/bot/* ops face) that must not import bots/coding. Each domain owns its
own wire stub (bots/wire.go, coding/task.go), so the ZAP swap per HIP-0106/0120 is
a seam swap. Wire spec bot -> runtime; cmd/bot -> cmd/runtime.

The duplicate-route guard was a no-op: the router MERGES byte-identical patterns
into one route with chained handlers, so counting entries never saw the collision
it guarded. It now asserts one handler per route, and a test proves it fires on
the original bug. Fiber's Test() defaults to a 1s wall-clock deadline, which made
the isolation guards flake under load; they now pass an explicit timeout.

Route table unchanged: /v1/bots (runs), /v1/compute/bots (machines), /v1/bot/*
(runtime ops).
2026-07-15 22:52:24 -07:00
hanzo-dev aad2bd189c feat(git): JSON read/browse surface for the console repo-browser
The console repo-browser (hanzoai/console products/git) needs machine-readable
refs/tree/blob/commits/readme, but git only served those as HTML (ui.go) + the
repo-CRUD control plane. Add the JSON twin, reusing ONE set of go-git read
helpers so the HTML + JSON surfaces can never drift:

  GET /v1/git/repos/:name/refs                   → { branches, tags, default }
  GET /v1/git/repos/:name/tree?ref&path          → { entries:[{name,path,type,size,mode}] }
  GET /v1/git/repos/:name/blob?ref&path          → { path,size,encoding,content,binary,truncated }
  GET /v1/git/repos/:name/commits?ref&path&limit → { commits:[{sha,shortSha,message,author*,date}] }
  GET /v1/git/repos/:name/readme?ref             → { path, content, encoding }

- browse.go: the handlers + DTOs (mirror the console GitApi normalizers verbatim).
  ref+path ride as ?ref=&path= query params (the UI's own convention) so a slashed
  branch is unambiguous. Reuses org()/findRepo()/openGit()/resolveRef()/
  cleanTreePath(). Org-scoped (X-Org-Id); a repo outside the caller's org 404s.
  Distinct trailing segments — never shadow the :org/:repo smart-HTTP routes.
- ui.go: findReadme → readmeAt (returns filename+content); the ONE readme scan now
  backs both the HTML repo home and the JSON /readme (DRY, no duplication).
- browse_test.go: seeds a nested tree + README + binary file, asserts every endpoint
  + org isolation + honest 404/403 + empty-repo refs.

CGO_ENABLED=0 go test ./clients/git/ green (full package); go vet + build clean.
Stays v1.x.x (Go module). Ships with console@main on the next cloud release.
2026-07-15 22:23:09 -07:00
hanzo-dev 4b5c482051 fix(billing): read the prepaid balance from the finance ledger, not a self-call
GET /v1/billing/balance and /v1/finance/balance proxied to commerce at the SAME
path they are registered on. commerceinproc publishes the shared zip app and
re-dispatches by path, and commerce's own /v1/billing/* routes are never
registered in this binary (api.Route runs only from commerce's mount.go, which
is //go:build cloud; cloud ships -tags "libsqlite3 sqlite_fts5"). So the proxy
re-entered itself, hit its own sign-in gate with no principal, and reported
"billing upstream status 500".

Co-resident, the prepaid wallet is cloud's own finance ledger: wireFinance points
the ai gate's balance read at it, the edge meter debits it (metering.fetchAvailable
already resolves finance.Current() first), and an admin grant credits it
(core.grantDeposit already prefers it). Read it directly through that same seam.
The commerce S2S read stays as the split-deploy fallback.

The subject comes from ai/object.BillingSubject — the function the ai prepaid gate
itself resolves — instead of a re-implemented copy. cloud and ai each keeping their
own copy of that rule is what let them drift: the console scoped to the org while
the gate scoped to "org/user", so the view showed a funded org while the gate
refused the member.

Fail posture unchanged: a balance that cannot be read is UNKNOWN and surfaces as
502 — never rendered as a zero balance. The sign-in gate and org scoping are
untouched; the org still comes from the validated principal only.

Tests: self-dispatch pinned at depth 2 (the seam's real mechanics, which the
existing SetHandler-stub test cannot see); router semantics probed (byte-identical
patterns MERGE and silently shadow; equal-specificity param-name conflicts PANIC at
registration; most-specific wins over registration order); balance regression,
gate-subject parity, unreadable-is-not-zero, sign-in gate, and cross-org isolation.
2026-07-15 22:16:46 -07:00
antje 02ffc01b58 feat(insights): /v1/insights — the unified native surface on the ONE analytics engine
A wire adapter, not a second pipeline: POST /v1/insights/e accepts PostHog-
shaped payloads (single or {batch}) from @hanzo/insights and any compatible
SDK, maps $-properties onto the native CaptureEvent, and rides the SAME
capture path (tenant gate -> normalize -> scrub -> hanzo.events). GET
/v1/insights/events is the console's tenant-scoped recent-events read; GET
/v1/insights/health reports the surface. Flags deliberately stay at /v1/flags.

Scale path stays stateless: accept on any replica, pooled batch INSERT sink;
the queue-buffered (mq/pubsub -> Datastore consumer) upgrade swaps the exec
behind buildEventsInsert with no handler changes.
2026-07-15 21:35:30 -07:00
zandGitHub 20e7b148fc Merge pull request #309 from hanzoai/bump/ai-v1.809.3
chore(ai): bump embedded ai v1.809.2 -> v1.809.3 (comped preview balance fix)
2026-07-15 21:30:55 -07:00
hanzo-dev fb9fe44107 chore(ai): bump embedded hanzoai/ai v1.809.2 -> v1.809.3 (comped preview bypasses enforceBalanceGate) 2026-07-15 21:30:09 -07:00
hanzo-dev ec2105f75e Merge land/hybrid-connectors: injective tenant S3 key (close cross-tenant collision) + orgPathSafe guard 2026-07-15 21:21:56 -07:00
hanzo-dev 04bee3d212 fix(projects): injective tenant S3 key via verbatim principal.Org (close cross-tenant collision) + orgPathSafe traversal guard 2026-07-15 21:21:25 -07:00
hanzo-dev d251389f19 bots: state the list cap explicitly
The published contract has no pagination, so the list is capped either way; set
it at the store maximum here rather than inherit the store's 100-row default.
2026-07-15 20:52:36 -07:00
hanzo-dev ecae57354c bots: give the three "bot" values one namespace each; make the run control plane native
GET /v1/bots was registered twice: clients/visor (bot machines) and clients/bots
(bot runs). The router resolves byte-identical patterns by first-registration
without panicking, and visor mounts first, so visor's machine list answered the
console's run list and clients/bots.list was unreachable. The console normalized
machine rows into run rows, yielding one blank-runId row per kind=bot machine
with a dead sessionUrl, and hid the org's real runs.

Name the values apart, one home and one route namespace each:
  - bot run     -> clients/bots  /v1/bots            (unchanged; the console + CLI contract)
  - bot machine -> clients/visor /v1/compute/bots    (moved; a machine is compute)
  - bot runtime -> clients/bot   /v1/bot/*           (passthrough for runtime-owned ops)

Make the run control plane native. clients/bots holds no store: a run is recorded
on the agents session plane under agent label "bot", so the run id is the session
id and one registry serves every kind of agent work. list reads it org-scoped;
stop resolves (org, runId) against that record and drives the runtime only after
ownership is proven, so a run of another tenant is a 404 the runtime never hears
about. An unreachable runtime is a 502 with the record left live.

Two seams (Runs, Runtime) are injected in adapters.go, the only file in
clients/bots importing agents/bot, so handlers unit-test against fakes.

agents: sessions carry a surface (the modality a session runs on, matching the
runtime's own origin.surface) via the established additive-column migration;
SessionFilter gains Agent so a product face reads only its own sessions;
OpenSession takes SessionOpen; StopSession is the single-session twin of
StopSessions and shares its one write path (stopOne).

Contract change: a run id is now the session id, not bot_<hex>. No bot_ id was
durable anywhere -- the old run handler minted an id and stored it nowhere -- so
there is nothing to migrate. Ids stay opaque to clients.
2026-07-15 20:38:54 -07:00
antje 6079ee5f32 cli/gpu: heartbeat the claimed activity + fleet presence DURING a render (goroutine in claimAndRun) — a >120s render no longer drops the machine offline mid-render; fixes BYO-GPU fix/compose/render hitting the deadline + going offline 2026-07-15 20:21:31 -07:00
zandGitHub 74cea96986 Merge pull request #308 from hanzoai/bump/ai-v1.809.2
chore(ai): bump embedded hanzoai/ai v1.809.1 -> v1.809.2 (Enso limited-preview gating)
2026-07-15 19:19:07 -07:00
hanzo-dev 7204e96c27 chore(ai): bump embedded hanzoai/ai v1.809.1 -> v1.809.2 (Enso limited-preview gating)
Lands the Enso limited-preview gating into the live api.hanzo.ai binary
(cloud embeds ai in-process via ai.Mount). v1.809.2 adds ai's Enso family
routing (ENSO_URL -> enso pod) + waitlist gating: ModelAccess visibility in
/v1/models, 403 request-access for ungated SKUs, comped bypass of the balance
gate for granted callers, POST /v1/models/:model/access, org `hanzo` seed.

Independent of the concurrent zen v1.3.0 -> v1.3.7 bump (#307), which this
branch is based on top of.
2026-07-15 19:16:00 -07:00
hanzo-dev 840dacc659 Merge land/chat-connectors: generalized ChatBridge + Discord/Teams/Telegram adapters for hanzo.chat 2026-07-15 19:11:41 -07:00
hanzo-dev 81f495db18 land(chat): generalized ChatBridge + Discord/Teams/Telegram adapters for hanzo.chat 2026-07-15 19:09:52 -07:00
zandGitHub 42bbf2db9d Merge pull request #307 from hanzoai/fix/zen-bump-clean
fix(zen): bump embedded hanzoai/zen v1.3.0 → v1.3.7 (1M ladder fix)
2026-07-15 19:04:13 -07:00
hanzo-dev a37339c7e5 fix(zen): bump embedded hanzoai/zen v1.3.0 -> v1.3.7 (1M ladder need() fix)
The cloud binary serves the zen* family IN-PROCESS via zen.Mount, so the
embedded module version — not the zen pod image — is what serves zen5. v1.3.0
sized the ladder rung by the byte estimate alone: a ~230K-token prompt with a
32K max_tokens budget estimated ~258K (under glm-5.2's 262144 cap), stayed on
glm-5.2, which then saw prompt+output = 262145 and 400'd. v1.3.7 sizes the rung
by need() = messages + tool schema + max_tokens, overflowing a >262144 total to
the 1M deepseek-v4-pro rung. Brings the Enso family + gating in-binary too.
2026-07-15 19:03:37 -07:00
antje 478aeb2e33 fix(image): runtime needs libgcc — the flags staticlib references _Unwind_*
The hanzo-flags Rust staticlib compiles with unwinding (panic-guarded FFI);
its _Unwind_* references resolve from libgcc_s, which the alpine runtime did
not carry — /cloud failed relocation at exec ('Error relocating /cloud:
_Unwind_GetIP: symbol not found') and smoke red-gated the release. Add libgcc
to the runtime apk set.
2026-07-15 18:47:52 -07:00
hanzo-dev 090c7091bb Merge land/agent-deploy-sites: agent AI-brief site build+deploy to <slug>.hanzo.app, metered per deploy 2026-07-15 18:41:36 -07:00
hanzo-dev f3cb5f1d7b land(sites): agent AI-brief site build+deploy to <slug>.hanzo.app, metered per deploy 2026-07-15 18:40:05 -07:00
antje 8ad160e912 feat(flags): native flag engine — stateless Rust FFI + SQLite per project, /v1/flags
native/flags: hanzo-flags, a stateless Rust staticlib with PostHog-compatible
evaluation — the exact Insights rollout hash (sha1 first-15-hex / LONG_SCALE,
pinned by test vectors), the full vendored property-operator set (exact/regex/
semver/date/relative-date...), condition groups (variant-override groups first),
multivariate cumulative selection, payloads. Pure (defs JSON, ctx JSON) ->
response JSON behind a panic-guarded C ABI: hanzo_flags_evaluate/_free.
65 tests green.

clients/featureflags becomes the NATIVE engine (no external evaluator, no KV,
no network): definitions in per-(org, project) SQLite via cloud.OrgDB
(encrypted at rest via cek), hot in-memory platform snapshot (TTL 15s),
evaluation over cgo. The INSIGHTS_FLAGS_URL HTTP proxy is gone. Bool/Int/
String and the admin Board keep their shapes; sources are flags -> env ->
default (first cockpit write creates the definition — env fallback intact
until then, zero regression). engine_stub (!cgo) degrades loudly, fail-safe.

/v1/flags (org-scoped via principal, project via X-Project-Id): POST /v1/flags
(+/decide alias) evaluate; GET/PUT/DELETE /v1/flags/defs[/:key]; GET
/v1/flags/activity; GET /v1/flags/health. PUT /v1/admin/flags/:key (SuperAdmin)
is the cockpit write path through SetPlatformSwitch — flips apply immediately
in-pod, peers converge within one TTL.

Build: Dockerfile flagslib stage (rust:1-alpine musl staticlib, --locked) copied
to the exact ${SRCDIR}-relative cgo link path; make native; hanzo.yml
native-flags step + clients/featureflags in the hermetic unit gate.
go test ./clients/featureflags ./apps green (FFI live).
2026-07-15 18:38:01 -07:00
zeekayandhanzo-dev ccf9b61d09 fix(console): white-label the embedded console <title> by request Host
The console SPA shipped in the unified cloud binary is a STATIC export of
hanzoai/console whose <title> is baked to the default (Hanzo) brand at build
time. The embed cannot read the request Host, so every host — including
console.lux.cloud and console.zoo.cloud — served "Hanzo Cloud Console" in the
browser tab, a white-label violation. (The standalone Next.js app is host-aware
via generateMetadata, but it is retired from this serving path: cloud serves
the console in-process from the go:embed static export.)

Rewrite the SPA shell's <title> at the serving layer (serveIndex/indexFor) to
the request host's brand, reusing the existing brands registry (BrandForHost):
console.lux.cloud -> "Lux Cloud Console", console.hanzo.ai -> "Hanzo Cloud
Console" (unchanged), console.zoo.cloud -> "Zoo Cloud Console". Matches
hanzoai/console's own `${brandName} Console` output — one source of truth. The
Hanzo/default host returns the embedded bytes unchanged (no regression); a shell
with no <title> is never altered.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-15 18:25:22 -07:00
hanzo-dev ee0587f20c Merge land/featuregate: per-service waitlist-mode control plane 2026-07-15 18:10:27 -07:00
antje 294bfb6b24 deps: bump ai v1.808.1 -> v1.809.1
Brings live: get-cloud-usages Bearer + balance-exempt (usage panel works at
$0), the /v1/ai/connections usage-import endpoint. Console changes ride the
same release via CONSOLE_REF=main embed. Build green.
2026-07-15 17:38:07 -07:00
hanzo-dev c5e59e6e4f wip(account-usage plane (clients/link usage + datastore)): rescued from agent that hit the session limit
Committed as-is to preserve the work (the building agent died mid-verify).
Not yet built/tested green; NOT merged to main. Resume from here.
2026-07-15 14:46:43 -07:00
hanzo-dev 7ceecbbc7a land(featuregate): per-service waitlist-mode control plane
Global SQLite registry {service, hosts, waitlistMode} + admin board/toggle
(/v1/admin/services*, /v1/featuregate/mode) + native Enforce middleware and
IAM-backed per-user approval resolver. Ported from recover/featuregate; dropped
the init()/cloud.RegisterWithShutdown self-registration in favor of the explicit
apps.Wire() MountSpec (order after admin, before tasks) + frozen wire_test row.

Distinct from clients/featureflags (a global read-only Insights waitlist_open
switch); this is the per-host launch lever with in-binary enforcement.
2026-07-15 13:20:25 -07:00
z fe5ee47725 platform: guard IAM object-store against a nil engine + commerce v1.48.2
Two co-residence fixes surfaced by the live founder-journey e2e:

1. /v1/platform/projects (authed) returned 500 'runtime error: invalid memory
   address' — iamobj.GetProjects/AddProject deref the package-global ormer.Engine,
   nil until the co-resident IAM subsystem initializes it. A nil store must fail
   cleanly: the iamStore() guard converts a nil-deref into a typed 503. (The store
   is initialized once iam co-mounts — v1.801.21 embedded-SQLite isolation.)
2. Bump commerce v1.48.1 -> v1.48.2: ErrorHandlerJSON preserves a downstream
   typed HTTP status, so a co-resident subsystem's 401/403/404 (e.g. platform's
   'X-Org-Id required') is no longer flattened to 500 by commerce's /v1 mount.

Regression tests: nil-store -> 503, success + real-error passthrough.
2026-07-15 13:11:54 -07:00
hanzo-dev 3fdbe9e4b2 controlplane seam (c): R1 — first-writer-wins registry + self-authorized Rekey (RED R1)
The ValidatorRegistry is the trusted key source for the whole cert, so key binding must be rogue-key-resistant BEFORE the driver sources idVerifier into the cert verifier. Register is now first-writer-wins: a node already bound to one ML-DSA key may not be silently re-bound to a DIFFERENT key (ErrIdentityKeyConflict); idempotent re-register of the identical key stays allowed. The ONLY sanctioned rotation is Rekey(node, newPub, authSig) — self-authorized by a signature under the node's CURRENT key over rekeyTBS under a DISTINCT rekey context (not popContext/certContext); an attacker without the current secret key cannot rotate. This is the registry action a consensus-ordered OpRekeyValidator applies (op plumbing lands with the RSM rewire).

5 R1 tests green; existing OnePodOneShare + full suite unaffected.
2026-07-15 12:41:21 -07:00
hanzo-dev fe26860183 controlplane seam (c): two-threshold self-guard + raw-craft verify tests (RED findings 1,3)
Finding 1: guardBFTFloor(len(keys), quorumWeight) fails closed unless the floor is the byzantine-safe BFT quorum (2n/3+1) for the validator-set size — so a mis-wired wallet-custody t (=3 for n=5) can neither compose nor verify a cert even if a future driver passes it. Called at the top of ComposeControlPlaneCert and VerifyControlPlaneCert. This is the exact two-threshold trap inc-1 hit (cluster.go wiring Pulsar threshold = quorum), now impossible in the cert core.

Finding 3: three raw-craft verify-side tests drive hand-built malicious certs (bypassing the honest composer) straight at VerifyControlPlaneCert — sub-quorum threshold-lie (ErrQCThresholdBelowFloor), attacker-key stuffing (ErrQCMerkleInclusion), weight inflation (ErrQCAggregateWeight) — plus a self-guard test (t=3 refused). 14 cert tests green.

Flag still false; ceremony untouched; existing byzantine suite green.
2026-07-15 12:41:21 -07:00
hanzo-dev 14467edfc5 controlplane inc-2 seam (c): real independent-sig ConsensusCert crypto core
The shipped Gen-3 weighted-quorum cert the design chose over the blocked threshold-Pulsar path. Each pod signs the canonical quorum message INDEPENDENTLY with its seam-a ML-DSA-65 key under a DISTINCT cert context (RED R4: certContext != popContext); the cert is a quasar.ConsensusCert carrying one EvidenceWeightedSigSet leg (a WeightedQuorumCert of N independent FIPS-204 sigs + weighted-Merkle quorum). Verification is quasar.VerifyConsensusCert under a control-plane ConsensusCertPolicy that requires the weighted-sig-set PQ leg — the shipped, audited verifier; NEVER the structural QuasarCert.Verify. No DKG, no threshold aggregate, no unshipped luxfi/pulsar core: soundness rests only on stock FIPS-204 verify + the weighted-validator-set Merkle commitment. Composes against luxfi/consensus v1.35.32 (BuildWeightedValidatorSet / BuildWeightedQuorumCert / VerifyConsensusCert).

VerifyControlPlaneCert binds the cert to the caller's expected position before the cryptographic verify (VerifyConsensusCert pins validator-set+policy but not the caller's height/round/block).

10 standalone crypto tests green: real cert verifies under policy; below-quorum / missing-leg / forged-sig / rogue-signer / wrong-position / wrong-validator-set all REJECTED with exact typed errors; R4 proven (a popContext sig is rejected as a cert sig); deterministic composition. Self-contained (does not touch the ceremony); existing suite stays green. Flag NOT yet flipped — ceremony rewiring + the ProductionBCCSigningReady() flip + stub deletion follow.
2026-07-15 12:41:21 -07:00
hanzo-dev ebaf7199ef deploy: rename the CD surface gitops -> /v1/deploy
The ArgoCD fork now lives at hanzoai/deploy (hanzoai/gitops redirects to it), so
the cloud CD control plane takes the matching single-word name: clients/gitops ->
clients/deploy, /v1/gitops/* -> /v1/deploy/*, and the subsystem name (Wire entry,
enablement key, health surface) is 'deploy'.

Same plane, same ArgoCD-grade fleet view over our own App CRs — applications,
resource tree, live manifest + diff, logs, sync, rollback.
2026-07-15 12:30:57 -07:00
antjeandGitHub 9819d1926b cloud(cmd): generate standalone connectorruntime binary
Completes the per-app-binary invariant: connectorruntime (HIP-0126) is in apps.Wire() but its generated cmd stub was dropped by a stale reconciliation merge. go generate ./apps restores it. cicd green.
2026-07-15 11:18:51 -07:00
hanzo-dev 13abe4432b Merge fix/iam-coresidence-db-isolation: isolate embedded IAM SQLite (unblock iam+ai) + CLOUD_ENABLE_STAGED
# Conflicts:
#	clients/iam/iam.go
2026-07-15 10:40:00 -07:00
hanzo-dev 28420819e8 Merge chore/regen-cmd-link: generate cmd/link standalone binary 2026-07-15 10:33:42 -07:00
antje b1576f51d3 cloud(ci): fix test gate path ./subsystems/ -> ./apps/ (main was red)
The subsystems/ -> apps/ rename merge (b9fc3ac5) missed hanzo.yml's test
gate, which still ran `go test ./subsystems/` — a directory that no longer
exists — so every main CI run failed "./subsystems [setup failed]". Point
it at ./apps/ (the renamed composition root). Unbreaks the release gate.
2026-07-15 10:21:30 -07:00
hanzo-dev 351bbff761 Merge origin/main (agents oversize-target fix) into branch integration 2026-07-15 10:19:28 -07:00
hanzo-dev 154209c7f1 Merge fix/402-credential-ordering: prefer fresh login JWT over stored hk- key in hanzo code 2026-07-15 10:18:18 -07:00
hanzo-dev a0e457893b Merge feat/connector-runtime-land: native in-process connector runtime (goja) 2026-07-15 10:17:08 -07:00
hanzo-dev 8e12bff7f5 fix(agents): reject an oversize target GPU array at the handler
Red LOW-2: body.Spec.GPUs was only truncated post-decode by Sanitize
(cap 32). register + PATCH now return 400 for a GPU array larger than the
cap instead of silently truncating, so an absurd payload is refused up
front and the client learns the bound. The 4MiB body limit already caps
the transient decode allocation; a normal-sized list still registers.
2026-07-15 10:14:47 -07:00
antje 0083a6894a cloud(cmd): generate missing standalone link binary (go generate ./apps)
The link app (unified AI login-manager registry, /v1/links) landed in
apps.Wire() without its generated cmd stub. Regenerating reconciles the
per-app-binary invariant: every Wire() app builds standalone via
apps.ServeSingle AND mounts into the unified binary. Idempotent.
2026-07-15 10:02:13 -07:00
hanzo-dev a5c711abba Merge origin/main (agents run-target) into apps/ rename integration 2026-07-15 09:49:42 -07:00
hanzo-dev 1d221f0e76 feat(agents): carry machine capability + live metrics on a run-target
A linked computer now reports what it IS (os/arch/cpus/memory/gpus, "spec")
and what it is DOING now (loadavg/memory/gpu-util, "metrics") so mission-
control can show which machine an agent runs on and whether it can take more
work — without copying the fact onto every session.

- targetspec.go: Spec/Metrics/GPU value types, JSON column codecs, and a
  total Sanitize that bounds strings/counts/sizes and coerces floats finite,
  so a hostile client can neither bloat the row nor smuggle a NaN/Inf.
- agent_targets gains spec/metrics/metrics_at (crashloop-safe addColumns,
  PRAGMA-guarded, no new index); register + PATCH accept them; a metrics
  PATCH is a heartbeat and the server owns the staleness clock (a client
  can't forge At).
- register upserts by (org, host) so re-linking the same machine refreshes
  one target instead of piling up duplicates.

Tests: sanitize bounds, store round-trip, GetTargetByHost org-scope, HTTP
capability+heartbeat, upsert-by-host. Existing target tests stay green.
2026-07-15 09:45:44 -07:00
hanzo-dev 9a689b049b fix(apps): add link mount to frozen wire-order fixture (main was red)
The feat/link-registry merge (7aa1e1a) added the `link` mount to Wire() —
{Name:"link", after agents} — but never updated the frozen mount-order fixture,
so TestWireOrderMatchesFrozen failed on main (84 specs vs 83 frozen). This merge
inherited that break; adding the missing frozen entry (link, no health, has
shutdown) at its Wire() position makes apps green again.
2026-07-15 09:43:55 -07:00
hanzo-dev b9fc3ac5bc Merge feat/per-app-cmd-binaries: subsystems/ -> apps/ rename + per-app cmd binaries
# Conflicts:
#	apps/wire_seams.go
2026-07-15 09:39:39 -07:00
hanzo-dev fbc2337819 fix(link): scope login-out session stop to the revoking user
A link revoke tore down live sessions by matching only {org, host,
provider, account}. Those fields come from a link row the caller sets at
upsert, so any org member could stop another member's sessions by
registering a wildcard link (e.g. provider-only) and revoking it.

Make Actor mandatory in agents.SessionMatch and AND it into the query.
The link adapter derives it from the revoking user's subject
(agents.BillingActor), the single place that binds a stop to the caller's
own sessions, so a stop/count can only ever reach that user's sessions.
A match with no actor stops nothing (fail-closed).

Tests: agents.TestStopSessions_ActorScoped (wildcard, host-forge,
no-actor fail-closed, count scope, own-account teardown) and
link.TestRevokeCannotStopCoTenantSessions (full stack through the real
adapter, co-tenant survives). TestRevokeStopsSessions stays green.
2026-07-15 09:31:20 -07:00
hanzo-dev f5be74651f Merge branch 'feat/link-registry' into _mergetmp 2026-07-15 03:32:21 -07:00
hanzo-dev 7aa1e1abbb feat(link): unified AI login-manager registry (/v1/links)
The org+user-scoped registry of which provider accounts (Claude Max, ChatGPT
Plus, a Hanzo/api key) a developer has signed into, on which machines, with each
account's latest usage snapshot — the cross-machine view console renders and the
source the redundancy route policy reads.

- clients/link: the Link atom (no secret — metadata + usage snapshot only),
  per-org SQLite store (org+subject leading-bound, upsert-on-identity, revoke),
  the /v1/links surface, and a pure RoutePolicy (Plan) that orders a user's linked
  accounts for redundancy (two Claude Max, then the metered API backstop) carrying
  the billing mode per candidate. The store holds no metering client — a
  subscription's usage is metered for visibility only and never charges commerce.
- clients/agents: a session now carries the linked account it ran under
  (Provider/Account tag), and StopSessions/CountActiveSessions expose the
  in-process action a link revoke takes to stop the sessions under a revoked
  account/device. Backward-compatible session migration (addColumns).
- subsystems: mount link after agents so a revoke can stop its sessions.

Org+user fail-closed isolation, subscription-vs-api-key billing distinction,
and revoke-stops-sessions are all tested (build/vet/gofmt clean; race+CGO green).
2026-07-15 03:31:37 -07:00
hanzo-dev 241c6d814a chore(cloud): bump hanzoai/ai v1.808.0 → v1.808.1 (relay reasoning normalization)
Pulls the DeepSeek <think></think> strip into api.hanzo.ai: reasoning-inlining
upstreams (zen5-pro/zen5-flash → deepseek-*) no longer leak the </think> template
token into the visible answer via the Anthropic-translation path that `hanzo code`
uses. Also carries the hk-key 402 tenant-gate fix. Builds clean (server + hanzo CLI).
2026-07-15 03:09:00 -07:00
zeekay 64699ec3b7 release: mirror via crane — IAM token realm rejects buildx's multi-scope request (crane single-scope proven E2E) 2026-07-15 02:59:17 -07:00
hanzo-dev e40705ff3d feat(cloud): per-app standalone cmd binaries via apps.ServeSingle + generator
Each app now builds as its own standalone binary AND still mounts into the
unified cloud binary — one source of truth (apps.Wire()). Two pieces:

1. apps.ServeSingle(name) — the ONE way to run a single app standalone: validate
   the name against Wire(), then cloud.Serve(Wire(), []string{name}). It is the
   path cmd/hanzo's 'hanzo <name>' already uses; promoting it to apps (which
   already imports cloud, so no cycle) lets every cmd/<app> stub reuse it instead
   of re-implementing the dispatch. Adding an app in Wire() is still the one edit.

2. cmd/gen-app-cmds — a tiny generator (go:generate directive in apps/apps.go)
   that parses Wire()'s {Name: "..."} literals and writes one cmd/<app>/main.go
   stub per app (apps.ServeSingle("<app>")). Generated, not hand-maintained; a
   re-run is idempotent (writes only on content change). 80 unique apps today.

Verify: go build ./apps/... green; apps.ServeSingle added; go generate ./apps is
idempotent; go test ./apps/... green (TestWireOrderMatchesFrozen at 84 specs); a
sample of generated cmd stubs (kms/account/agents/platform/storage/audit/
analytics/ads/ingress/billing/o11y) build standalone green. The full ./cmd/...
build is heavy (80 binaries x the cloud tree) and needs CI parallelism; the
stubs themselves are sound.
2026-07-15 02:46:42 -07:00
zeekay c6400c620d Merge remote-tracking branch 'origin/main' into ci-finish 2026-07-15 02:43:03 -07:00
zeekay bd8c1d7454 ci: mirror uses direct REGISTRY_USER/PASSWORD secret (Free plan hides org KMS secrets from private repos); test gate skips the cek env-gated test 2026-07-15 02:42:50 -07:00
hanzo-dev 0645a1cc05 refactor(cloud): rename subsystems/ -> apps/ (the composition root)
The cloud binary mounts ~84 'subsystems' into one unified binary; they read as
apps, so the package follows. Purely internal: dir subsystems/ -> apps/, package
'subsystems' -> 'apps', the one file subsystems.go -> apps.go. Three import sites
updated (cmd/cloud, cmd/hanzo). Broken path/filename references in comments
(subsystems.Wire, subsystems/commerce.go, subsystems.go) -> apps.*; the package
doc + LLM.md/docs paths follow.

No external breakage: the package is same-module (never in go.mod), no external
module imports it. The frozen-order test TestWireOrderMatchesFrozen compares
MountSpec.Name strings, not the package name — passes unchanged at 84 specs.

Standalone via 'hanzo <name>' and per-app cmd binaries are unchanged by this
rename (D2 adds the cmd binaries on top).

Verify: go build ./... green; go vet ./apps/... ./cmd/... clean; go test ./apps/...
green; TestWireOrderMatchesFrozen green. cmd/cloud TestMountAllAndServeHealth
fails identically on clean main (needs CLOUD_KMS_MASTER_KEY_REF), not this change.
2026-07-15 02:31:45 -07:00
hanzo-dev c22391f6fb fix(agents): build session target/host indexes after addColumns
migrateSessions created ix_sessions_org_target and ix_sessions_org_host in
the table DDL, which runs before addColumns adds target/host to a
pre-existing table. On a fresh DB the CREATE TABLE carries the columns so
the indexes build; booting over the prior release's agent_sessions table
the CREATE TABLE IF NOT EXISTS no-ops and the index references a
not-yet-added column ("no such column: target"), failing the release
migration smoke. Build the two indexes after addColumns so the columns
exist first on both the fresh and upgrade paths.

TestMigrateOverLegacySessionsTable locks it over the pre-target schema.
2026-07-15 02:24:57 -07:00
hanzo-dev 1bb0773823 fix(cloud/code): prefer the live login JWT over the hk- key to unblock 402
hanzo code 402s ('a billable tenant is required') on a deployment without
IAM_MINT_CLIENT_*: codeToken() preferred the hk- API key, but an hk- key only
mints a billing principal when the server can resolve it (iamKeys.resolve is a
no-op without the mint credential) — so the request arrives anonymous and zen's
/v1/messages billing gate refuses it. The /v1/models catalog call is loosely
gated, so the launcher banner still printed, masking the cause.

Reorder codeToken to prefer a FRESH hanzo login JWT, which carries the caller's
owner/project/sub claims verbatim and mints a billing principal on EVERY
deployment, then fall back to the hk- key chain (still works on mint-credentialed
servers). HANZO_API_KEY stays the deliberate operator override at the top.

freshAccessToken() is a new expiry-guarded accessor (decomplected from
accessToken, which whoami keeps expiry-agnostic): an EXPIRED jwt must not win —
it would 401 a session a valid hk- key would serve — so it falls through to the
key. No expiry record (a raw HANZO_TOKEN) is trusted as-is.

Pinned by TestCodeTokenPrecedence (fresh jwt beats hk-, expired jwt falls
through, HANZO_API_KEY overrides all). Structural hanzoai/jwt extraction is a
follow-up PR.
2026-07-15 02:19:47 -07:00
hanzo-dev 211a72c274 git: make the mounted service pointer atomic (fix -race)
The lifecycle reactors (notify / mirror-out / index-on-push) read the package
'mounted' var in DETACHED EmitLifecycle goroutines while Mount/Shutdown write it;
a reactor goroutine outliving a Shutdown (or a test Mount<->Shutdown cycle) tore
against the write. Convert 'mounted' to atomic.Pointer[cloud.Service[state]] —
Store on Mount/Shutdown, Load in every reader (reactors, export CloneURL/VerifyRef,
index-on-push, the GitHub importer) + the tests. Behavior unchanged (production
sets mounted once); the data race the -race detector flagged is gone.
2026-07-15 02:19:15 -07:00
hanzo-dev 8486d0f1d0 feat(cloud/connectorruntime): native in-process connector exec (HIP-0126)
Lands clients/connectorruntime — the native replacement for the standalone
ActivePieces Node engine: an ActivePieces JS connector action runs in goja
in-process (no auto pod, no in-cluster HTTP hop, no shared X-Piece-Run-Secret).
Same {action,auth,props} -> {ok,output,error} contract; org-gated via
principal.Org; the caller's credential travels in the request auth.

POST /v1/automations/connectors/:id/run  run one connector action in-process

Wired into the composition root (subsystems.Wire) the one way main does it —
an explicit MountSpec after automations (it pairs with the catalogue) — not the
old self-registering cloud.Register init (removed; main is explicit-Wire).
frozen order sequence updated to 84 specs.

Re-derived from the cloud-cr worktree's uncommitted work against current main:
the package's principal.Tenant -> principal.Org, the cloud.Register init -> the
explicit Wire() entry, and the go.mod esbuild dep flipped to direct. The
kb/sync_piece.go refactor that originally accompanied this is NOT carried —
clients/kb was removed on main since the branch forked, so there is nothing to
refactor; connectorruntime stands on its own (imports only cloud + principal).

Build green; go test ./clients/connectorruntime/... green (registry + runtime);
TestWireOrderMatchesFrozen green at 84 specs.
2026-07-15 02:13:38 -07:00
hanzo-dev 6049750fb1 Merge feat/ai-obs-attribution: o11y trace attribution + annotation queues
Trace attribution, per-project metrics, sessions, and annotation-queue routes
on the o11y plane (clients/o11y annotation store + queues, clients/eval
attribution/telemetry, principal scope). Genuine new feature (not on main),
rebased clean onto current main; builds and race tests green.
2026-07-15 02:07:08 -07:00
hanzo-dev bf7b3a9660 Merge feat/github-app-sync: GitHub App bidirectional repo mirror + sync
Install the Hanzo GitHub App -> list org repos -> import into git.hanzo.ai ->
bidirectional sync (outbound mirror already exists; inbound = HMAC-verified
webhook, fast-forward-ONLY, never force-overwrites native). Inert until the App
creds land in KMS.
2026-07-15 02:07:05 -07:00
hanzo-dev 2a44492f49 Merge fix/affiliates-topup: accrual tops up the open period (month-to-date converges); link clicks off the money-DB write path 2026-07-15 02:05:26 -07:00
hanzo-dev b15b320716 fix(affiliates): accrual tops up the open period so month-to-date spend converges
The monthly accrual latched once on the FIRST sweep's PARTIAL month-to-date spend
and no-oped every later sweep, so an affiliate whose dashboard swept early in the
month froze its share near zero (underpaid, though platform-safe). Store.Accrue now
inserts the period row on first sweep and, for the still-open period, TOPS IT UP
toward the current (higher) month-to-date reading in one transaction — adding only
the positive delta, so accrued_cents converges to the month-end value, never
decreases, and never overshoots. The per-event money invariant is untouched: each
row keeps margin + share from ONE reading (share <= margin) and the level-schedule
cap keeps sum(share) <= margin at every step.

Public link clicks move off the money-DB write path: clickLink folds pings into an
in-memory coalescing buffer (bounded), flushed batched on the next links read and on
shutdown, so a click flood can never contend with the accrual/payout writes.

Tests: TestAccrualConverges + TestAccrualConvergesAtMaxRate prove the share tracks a
growing month-to-date and sum(share) <= margin at every intermediate sweep; existing
invariant/idempotency/isolation/links tests stay green (26 pass, -race).
2026-07-15 02:05:08 -07:00
hanzo-dev 9a6505f39b code: index on push via durable hanzoai/tasks workflow
A push to a repo's default branch enqueues a durable IndexRepoWorkflow on
the embedded tasks engine (workflow id keyed by commit = idempotent per
push); a worker reads the tip tree from the object plane and folds its
text files into the org's code index, retried on failure. Fail-soft:
before the engine is wired the reactor indexes inline on its detached
lifecycle goroutine (the ai-ingest contract), so push-index is always live.

git and code never import each other — the reactor is git's third
lifecycle subscriber, the index reached through the SetIndexer func seam
wired once at the composition root.
2026-07-15 02:04:02 -07:00
hanzo-dev b2da6ae6a6 feat(o11y): trace attribution, per-project metrics, sessions + annotation-queue routes
eval telemetry (Trace): add ProjectID, SessionID, APIKeyHash (SHA-256 ref, never
plaintext), and StartTime/EndTime latency; DDL columns + additive migrations +
write/read paths. A run stamps its project (principal.ProjectScope), groups its
item-traces under the run as one session, times the model call, and records a
non-reversible ref of the caller credential. Trace list narrows by the caller's
project (default == whole org).

evals/metrics: thread the server-minted project scope into MetricsFilter,
usageWhere (AND project = ?) and the latency span filter. The default-project
(whole-org) board queries the ledger today; a named-project board is honest-empty
until cloud_usage carries a project column (ai write path) — activation is one
guard flip, the query plumbing is project-aware and tested.

principal.ProjectScope: the ONE helper for "default project == "" == whole org";
eval + o11y both read it.

o11y: explicit org-gated GET /v1/o11y/sessions pinning the runtime /api/sessions
route; native annotation-queues surface (SQLite metastore, org+project scoped) at
/v1/o11y/annotation-queues* — list/create/detail/update/delete, items add/list/
complete — returning the console {data,meta} envelope.

Tests: trace attribution (latency, session grouping, hashed-not-plaintext key),
per-project + cross-org trace isolation, usageWhere project predicate, annotation
queue lifecycle + org/project isolation + validation + principal gate.
2026-07-15 02:03:55 -07:00
hanzo-dev e27262c7ce GitHub App: bidirectional repo mirror + sync (git.hanzo.ai)
integrations (github.go/github_app.go/github_webhook.go): App install ->
installation-token mint (ghinstallation), list granted repos, background import,
inbound push webhook (HMAC-verified, fast-forward-only). Inert until
GITHUB_APP_{ID,PRIVATE_KEY,WEBHOOK_SECRET,SLUG} land.

git (github_import.go + cloud.GitImporter seam in git_import.go): import =
fast-forward mirror-in per branch; inbound = fast-forward-ONLY advance where
native is canonical, so a divergence is a recorded conflict and never a
force-overwrite; loop-prevention via the Origin stamp; per-repo status. Outbound
mirror uses the org installation token for github.com targets, shared-token
fallback otherwise (no regression).
2026-07-15 02:02:49 -07:00
hanzo-dev 821e7e3911 code: add tree + file endpoints (zread contract over the index)
GET /v1/code/tree?repo=  → get_repo_structure: the repo's files + per-file
  symbol counts, ordered, per-org isolated.
GET /v1/code/file?repo=&path= → read_file: the INDEXED content (the symbol
  chunks the search tiers hold), for fast context. NOT byte-verbatim — inter-
  symbol lines a parser did not chunk are absent; the S3-backed git object
  plane (clients/git) is the source of record for exact bytes, history, and
  blame. Comments say so; a follow-up routes byte-fidelity read_file/blame at
  the git plane.
Store.tree + Store.fileContent read the existing files/symbols/chunks tiers —
no schema change. Test covers tree structure, indexed-file read, 404 on an
unindexed path, and per-org isolation (org B sees an empty tree).
2026-07-15 02:01:18 -07:00
hanzo-dev d86ee8ed46 Merge feat/hanzo-agent-keystone: @hanzo Slack coding agent (ships INERT)
The coding-agent code lands fail-closed and INERT: no sandbox runs until an
operator provisions docker and sets HANZO_CODING_* env. The coding sandbox
stays DISABLED until the default-deny-egress + container resource-limit
hardening lands and red re-clears. Do NOT provision docker / set HANZO_CODING_*
until then.

Native coding tasks from Slack over the shared object plane: clients/coding
dispatcher, in-process agents session bus, tracker agent PR, bot NDJSON client,
git export seam, slack coding trigger.
2026-07-15 01:57:17 -07:00
hanzo-dev 1d290d0067 Merge feat/mission-control-sessions: agent session execution-context + targets
Mission-control backend over /v1/agents/sessions: sessions carry host/cwd/
repo/target and a compact last-event; new /v1/agents/targets registry
(register/list/detail/patch/delete) with live session-load, org fail-closed,
in the same agents.db. Composes with the compute fleet at the view layer.
2026-07-15 01:49:51 -07:00
hanzo-dev 17f274ca8c agents: session execution-context + targets (mission-control)
Sessions gain host/cwd/repo/target so mission-control can show where a
session runs and map sessions to a machine; the list projection carries a
compact last-event preview. Add /v1/agents/targets — register/list/detail/
patch/delete a dispatch destination (laptop|cloud|gpu|cluster|machine) with
a live session-load rollup — in the same agents.db, one tenancy column, org
fail-closed. A session's target resolves same-org at register/patch (#48).

Composes with the compute fleet (/v1/fleet/workers, /v1/clusters) at the
view layer rather than duplicating it.
2026-07-15 01:48:51 -07:00
zeekay 0155df3879 release: fix step splice — buildx keeps its with: block 2026-07-14 23:38:51 -07:00
zeekay a5bd1c9d82 release: dual-host — mirror release tags to registry.hanzo.ai
Server-side copies alongside the ghcr retag; the cluster deploys from OUR
registry, ghcr stays the public identity. Best-effort by contract — a mirror
hiccup never blocks the tag-receipt.
2026-07-14 23:38:27 -07:00
zeekay 731eb217e6 Merge remote-tracking branch 'origin/main' into unfork-commerce 2026-07-14 23:19:49 -07:00
zeekay e7e98e2b52 ci: canonical hanzo.yml test gate + hanzoai/ci caller on the arc pool
release.yml keeps sole ownership of the image + v* tags (tag-is-a-receipt);
this adds the vet/unit gate on every push/PR, on our own runners.
2026-07-14 23:19:38 -07:00
hanzo-dev bced234eba fix(cli/code): give agent its true 1M context on zen models
agent sizes a model's context window only from ids it recognizes.
An unknown gateway id like `zen5-pro` gets a hardcoded 128K budget and is
rejected client-side above it ("maximum context length is 131072") — even
though api.hanzo.ai and the DeepSeek-V4 upstream serve the full 1M window
fine (verified live: 140K-token prompts return 200).

Bridge each CC tier through a recognized carrier id (claude-opus-4-8[1m]
etc.) that unlocks the 1M budget, then rewrite it back to the served zen
alias via settings.json modelOverrides before the request leaves the
client — the carrier never reaches the server, so real claude-* routes are
untouched and responses stay branded/served as zen. One source of truth
(zenTiers) drives the wire env, picker branding, and overrides. The fast
tier stays direct (never needs >128K; SMALL_FAST_MODEL isn't override-
rewritten, so a carrier there would leak raw).

Verified end-to-end with agent v2.1.210: the wire model reaching
api.hanzo.ai is zen5 / zen5-pro carrying context-1m-2025-08-07, with zero
raw claude-* leaks.
2026-07-14 23:15:24 -07:00
zeekay 561a1b1e8c merge main: /v1/store owner carried onto the NATIVE mount
The store surface registers natively (api/store.Route on a group-scoped chain
mirroring the standalone /v1 bundle) instead of re-adding the gin AdaptNetHTTP
prefix; commercePrefixes keeps /v1/store pinned so store reads can never fall
through to the AI /v1/* balance gate again.
2026-07-14 23:03:43 -07:00
zeekay 4a972ea6a1 commerce v1.48.1 NATIVE co-residence — routes on the shared zip app, AdaptNetHTTP gone from the commerce path
- subsystems/commerce.go: commerce.Embed(App: app) — the SharedApp contract;
  commerce registers /v1/commerce/* + /_/commerce/* directly on cloud's router
  (one specificity space, no second engine, no net/http adaptation)
- live wire paths registered natively with commerce's own gates:
  /v1/billing/webhooks/:provider (HMAC-is-auth) and
  /v1/billing/auto-recharge/run-all (service-token + PlatformOnly) —
  commercePrefixes contract test pinned and passing
- commerceinproc.SetApp: S2S byte-stream enters the shared app's pipeline;
  RoundTrip normalizes client-style RequestURI at the ONE seam;
  entitlements + BalanceCents stay pure direct-Go (commerceclient)
- zip v1.8.2 (union tag: v1.8 features + the v1.7.4 chain-order fix + v1.7.5
  empty-leaf normalization — v1.8.1 was missing both)
- metering dispatch e2e ported to the zip harness and green
2026-07-14 23:01:39 -07:00
hanzo-dev 008b0c2b92 fix(commerce): own /v1/store/* so store reads reach commerce, not the AI /v1/* balance gate
The bare storefront surface api.Route(Group("/v1")) registers on the commerce
gin engine — GET /v1/store/current (the org-scoped default store the admin
dashboard AND the content storefront edge resolve), the /v1/store/:id/listing
upsert the publish edge writes, and the public /v1/store/:store/listing reads
karma.style serves at runtime — was dropped from commercePrefixes by the unfork.
Unowned, /v1/store/* fell through to the bare /v1/* AI catch-all, whose prepaid
LLM balance gate 402'd every store read for an org funded in commerce but $0 in
the ai ledger (org karma: $999.99 credit, GET /v1/store/current -> 402
insufficient_balance, blocking store provisioning + the storefront image fan-out).

Restore the /v1/store prefix so /v1/store/* routes to the commerce handler, which
resolves the org from the gateway X-Org-Id (TokenRequired -> ensureIAMOrg) and
lazily provisions the org's store — standalone-commerced parity. A store-metadata
read never requires an LLM balance. Per-route permission masks are unchanged
(money paths stay publishedRequired); gin still 404s an unknown /v1/store/* path.

Guarded by TestStoreSurfaceRoutedToCommerceNotAIGate (store read resolves on
commerce, never 402 at the catch-all) + the extended commercePrefixes pin test.
2026-07-14 22:55:03 -07:00
hanzo-dev 3da5b13053 feat(social): optional media[] URLs on posts
Add an optional media field (JSON array of URLs) to the social Post store,
additive and idempotent exactly like the marketing scheduled_at fix:

- store: media TEXT NOT NULL DEFAULT '[]' column + addColumn upgrade for
  pre-existing prod DBs (migrate-on-open, the only upgrade path for the
  encrypted single-file store); JSON encode/decode helpers; Post.Media []string
  always serialized as [] never null.
- api: normMedia bounds each URL to maxField and the list to maxMedia (10),
  the one sanitization seam on create + update (mirrors content/channel).
- tests: media round-trip in TestPostCRUD (create sets, update replaces) and
  TestMigrateAddsMediaColumnToOldPosts — old-schema DB gains the column and a
  media write no longer 500s; legacy rows default to [].
2026-07-14 22:51:48 -07:00
hanzo-dev d23e0d0f42 Merge feat/affiliate-profit-share-dashboard: OSS-dev affiliate profit-share + dashboard
Margin-based accrual (share = rate x Hanzo's margin, share <= margin invariant),
derived share ledger that never mutates the cost-of-record, shareable links with
click/signup/conversion, per-period earnings, opt-in privacy leaderboard, and the
SuperAdmin set-rate. Tenant-isolated, fail-closed.
2026-07-14 22:31:52 -07:00
hanzo-dev 8043a84f61 affiliates: profit-share (margin-based accrual) + dashboard (links, earnings, leaderboard)
Switch the affiliate accrual from revenue-share (spend x rate) to PROFIT-share
(margin x rate), where margin = a referred org's gross spend x the platform
gross-margin fraction (AFFILIATE_MARGIN_BPS, default 40%). The share is a rate
OF Hanzo's margin, never the customer's bill, so a payout can never exceed the
margin earned. The L1 rate is capped (maxL1RateBps=9300) so the whole L1+L2+L3
schedule stays <= 100% of the margin: total share <= margin, always.

The derived share ledger (affiliate_accruals) now records the margin base
alongside the gross spend and the share; it never mutates the cost-of-record
(commerce/cloud_usage) - it is a pure projection keyed by referrer.

Dashboard surface (all org-scoped, fail-closed):
- GET  /v1/affiliates/me/earnings   per-period + per-direct-referral aggregate
- GET/POST /v1/affiliates/me/links  shareable links + click/signup/conversion
- POST /v1/affiliates/me/handle     opt-in leaderboard display name
- POST /v1/affiliates/click         public click ping (vanity counter)
- GET  /v1/affiliates/leaderboard   opt-in handles + aggregate + your own rank
- POST /v1/admin/affiliates/:id/rate SuperAdmin set L1 rate (capped)

Tests: margin invariant (share <= margin per level + summed; charge unchanged),
set-rate cap, links lifecycle, cross-affiliate isolation (earnings + links),
leaderboard privacy (no org identity leaks, own rank always visible).
2026-07-14 22:31:21 -07:00
hanzo-dev ca1a266141 leaderboard: gamified usage analytics — leaderboards + activity graph (#43)
New /v1/usage/leaderboard + /v1/usage/activity + opt-in surface over a derived
datastore rollup (SummingMergeTree MV of hanzo.cloud_usage). Ranks top AI users
(personal/org) and orgs (global); per-day contribution heatmap + timeline.

- rollup.go: usage_rollup_daily target + incremental MV (type-exact projection,
  cannot fail a valid ledger insert) + deploy-gated run-once backfill.
- sql.go: injection-safe builders — org bound positionally, metric from a closed
  allowlist, limit a clamped int; org is the leading predicate.
- view.go: opt-in privacy — self/opted-in/admin named, else Anonymous; cross-org
  detail structurally impossible (org-bound reads).
- store.go: opt-in preference store (private by default), Base/SQLite via cek.
- board.go/activity.go/optin.go/backfill.go: handlers, fail-closed on principal.
- 39 tests (incl -race): builder injection-safety, tenant isolation, cross-tenant
  bleed, naming policy, opt-in default-private, authz resolvers, rollup lifecycle.
2026-07-14 22:28:37 -07:00
hanzo-dev df7ad43030 Merge fix/prod-headers-followups: brand-only Server fallback (zip v1.8.1) + trailing-dot brand resolution 2026-07-14 21:56:26 -07:00
hanzo-dev 4a8c25e27f fix(headers): brand-only Server fallback + trailing-dot brand resolution
Address Red's LOW-1/LOW-3 on the production-header posture:
- serve.go sets zip.Config.ServerHeader=cfg.Brand so the responses the
  ProductionHeaders middleware can't reach — the fasthttp transport's OWN
  pre-routing errors (431/400) — read Server: <brand> instead of the framework
  default. Requires zip>=v1.8.1 (transport now propagates ServerHeader). Repin
  v1.8.0->v1.8.1; go.mod diff is only the zip line.
- BrandForHostOK strips a trailing FQDN dot so api.lux.network. resolves to lux
  (fails safe to neutral before, never a wrong brand — brand-fidelity fix).
2026-07-14 21:56:15 -07:00
hanzo-dev d690c3b129 deps(commerce): v1.47.2 -> v1.47.3 — tier gate counts granted credits as spendable (fixes 402 for grant-funded orgs) 2026-07-14 21:47:20 -07:00
hanzo-dev d10a7528a8 Merge feat/prod-response-headers: inherit zip ProductionHeaders posture (brand-by-host Server, X-Api-Version, HSTS/nosniff) 2026-07-14 21:07:29 -07:00
hanzo-dev a0a932d1f2 feat: inherit zip ProductionHeaders — brand-by-host Server, X-Api-Version, HSTS/nosniff
Wire the shared production response-header posture (zip v1.8.0) into the edge,
right after RequestID so it covers every response — success, error, 404, and
the public-site static bytes:

- Server is the white-label brand of the request Host via BrandForHostOK (cloud's
  own registry), so a lux/zoo caller is never served "hanzo" and no response
  leaks the framework name. An unmatched Host falls back to this deployment's own
  brand (cfg.Brand), never a framework or hardcoded single brand.
- X-Api-Version carries the build version (Config.Version <- CLOUD_VERSION env,
  else the link-time cloud.Version default) under a brand-neutral key.
- HSTS + nosniff are the always-safe security floor; the console SPA keeps its
  own framing rules (no X-Frame-Options/CSP forced here).

Bumps zip v1.6.0 -> v1.8.0 for middleware.ProductionHeaders. X-Request-Id stays
owned by middleware.RequestID.
2026-07-14 21:07:18 -07:00
hanzo-dev 9363528d53 cli: auto-wire Hanzo MCP into hanzo code claude (port Rust resolve_mcp)
The Go hanzo code wired zero MCP — subagents got a bare model, no Hanzo tools.
Port the Rust CLI's resolve_mcp: resolve hanzo-mcp (installed → PATH, else uvx
hanzo-mcp), write an --mcp-config stdio document scoped to the cwd into the
isolated config dir, and pass --strict-mcp-config so the Hanzo server is the sole
MCP source (a repo .mcp.json is ignored — it can ship a bearer-exfiltrating stdio
server). A missing hanzo-mcp warns and continues (MCP is an enhancement, never a
blocker). So hanzo code claude now starts with the Hanzo tool lattice — code
search over the cloud index, web search, vision, fs/exec/git. Test covers the
opt-in, the config shape, and the not-found warn path.
2026-07-14 20:12:25 -07:00
hanzo-dev 9487becfec code+knowledge: default embed model to zen-embedding SKU (fix semantic tier)
Both indexers defaulted CLOUD_EMBED_MODEL to bge-m3 (the raw upstream), which
the gateway rejects (400) — only the zen-embedding SKU is served. Result:
index-time embeds failed silently, semantic code + KB search returned nothing
(vectors:0, degraded:true). Default to the served SKU. Pairs with the zen
bge-m3->zen-embedding alias so both the name and the SKU resolve.
2026-07-14 20:04:19 -07:00
hanzo-dev 8d4469fde6 integrations: GitLab OAuth provider (login + repo sync, KMS-env creds)
Adds the gitlab provider on the same OAuth registry as slack/google/github.
Reads GITLAB_CLIENT_ID/GITLAB_CLIENT_SECRET from ENV (KMS-synced, never in code);
Configured() is false until both are present so it ships INERT and fails closed
(honest 503 / failure redirect, never a fake OK). Callback = the app's
/v1/integrations/gitlab/callback; the generic dispatcher seals the access+refresh
tokens into the org KMS namespace.

Least-privilege by construction: requests only openid/profile/email/read_api/
read_repository/write_repository — the token receives the intersection of
requested + app-allowed, so we never request api/sudo/admin_mode/k8s_proxy/
*_runner/*_registry even if the app was provisioned with them (tested).
GITLAB_URL supports self-hosted GitLab. 5 tests: registration, least-privilege
authorize URL, exchange seals both tokens + resolves account, missing-secret
fails honestly, error body surfaced.
2026-07-14 18:19:52 -07:00
hanzo-dev bb7a652315 deps(commerce): v1.47.1 -> v1.47.2 — org-scoped /v1/store/current + lazy store provisioning
commerce v1.47.2 fixes GET /v1/store/current returning the phantom shared
"default" store: it now resolves the caller org's namespace and lazily,
idempotently provisions the org-scoped store (store.EnsureDefault) on first
authenticated hit — the store id the content storefront edge needs to publish
Listing.headerImage. Round-trip + cross-tenant tests ship in the module.
2026-07-14 17:59:51 -07:00
hanzo-dev 18a7b05c58 fix(marketing): additive ALTER so old prod campaigns tables gain scheduled_at
POST/GET /v1/marketing/campaigns 500'd on prod with "table
marketing_campaigns has no column named scheduled_at": migrateCampaigns()
uses CREATE TABLE IF NOT EXISTS, which NEVER alters an existing table, so a
prod DB created before scheduled_at was added to the DDL was frozen at its
original schema and every campaign write (INSERT/UPDATE name it) 500'd. The
store is an encrypted single-file SQLite only the binary can open, so a
hand-patch is impossible — the upgrade MUST happen in migrate-on-open.

- migrateCampaigns: after the CREATE, run an idempotent additive column
  upgrade — ALTER TABLE marketing_campaigns ADD COLUMN scheduled_at
  INTEGER NOT NULL DEFAULT 0 — swallowing SQLite's "duplicate column name"
  (the only error) so it's a no-op on a fresh DB.
- addColumn helper mirrors clients/social/store.go exactly (the ONE way we
  do additive migrations), keyed by an extensible {table,col,def} list.

Tests (store_migrate_test.go, CGO_ENABLED=0 pure-Go cek): a from-OLD-schema DB
(marketing_campaigns without scheduled_at + a legacy row) opens, migrate ADDs
the column, a scheduled_at write succeeds, and the legacy row survives with
scheduled_at defaulted to 0; plus a fresh-DB idempotency re-open. Without the
ALTER the old-schema test reproduces the exact prod 500.
2026-07-14 17:56:36 -07:00
hanzo-dev 959cf4d15c fix(commerce): restore /v1/billing/auto-recharge prefix dropped by the unfork — pin test moves beside the canonical list
The unfork (741644d) rebuilt commercePrefixes in subsystems/commerce.go from a
pre-fix snapshot, dropping /v1/billing/auto-recharge (landed as #274/3c48fb8)
and deleting its pin test with the old clients/commerce tree. Without the
prefix the durable cron's quarter-hour billing-autorecharge poke lands on the
account-bridge /v1/billing/* session gate and 403s — verified live before
3c48fb8 shipped in v1.801.1 (poke 200, 311 orgs swept, 23:45:05Z).

Same one-line-family fix, new canonical location; TestCommercePrefixesPinned
now lives beside the list it pins so a future rewrite can't silently regress
the wire path again.
2026-07-14 17:51:13 -07:00
hanzo-dev ec86c4b67b fix(zen): resolve upstream provider keys with env fallback (fix DO 401)
zenKeyResolver read the co-resident KMS store ONLY. The upstream provider
keys (DO_AI_API_KEY, ANTHROPIC_API_KEY) are provisioned as env, injected
from the KMS-synced cloud-api-llm-keys secret — they are NOT sealed in the
embedded KMS store. So GetSecret missed, the resolver returned an empty key,
and zen's call to DO GenAI answered 401 'Unable to authenticate you'. Every
zen chat failed at the upstream while ai (which reads the key from env) worked.

Try the sealed KMS value first (so completing sealed-store provisioning later
needs no code change), then fall back to env. Absent from both still returns
'' so the call fails fast — never silent free usage. Tests cover env-fallback,
sealed-precedence, and absent-everywhere.
2026-07-14 17:29:07 -07:00
hanzo-dev 19233b485d fix(zen): resolve upstream provider keys env-first, then KMS
zenKeyResolver read the embedded KMS store ONLY. The operator injects the
provider keys (DO_AI_API_KEY, ANTHROPIC_API_KEY) as env from the KMS-synced
K8s secret cloud-api-llm-keys, but that value is not seeded into the embedded
ZapDB KMS store — so GetSecret missed, the resolver returned an empty key, and
zen's upstream call to DO GenAI answered 401 'Unable to authenticate you'.
Every zen chat failed while ai (which reads the key from env) worked.

Read env first, then KMS — the same order ai uses (object/kms.go). One key
source of truth shared by both zen and ai. Empty on both still returns '' so
the call fails fast, never silent free usage.
2026-07-14 17:24:48 -07:00
zeekay 741644dd25 unfork(commerce): import hanzoai/commerce v1.47.1 — delete the 1,397-file inlined fork
One canonical commerce repo, one-way dependency (cloud → commerce), no more
monorepo-split force-pushes to keep two trees in sync.

- clients/commerce/ (fork, no go.mod) DELETED; cloud imports the module
- subsystems/commerce.go: the ONE adapter — narrows cloud.Deps, boots
  commerce.Embed, mounts the gin handler at the commerce prefixes, wires the
  two in-process seams; luxfi/log imported plainly as log
- consumer bridges move cloud-side (they read cloud seams, not commerce):
  clients/metering    ← fork metering (finance-coupled billing-gate client)
  clients/commerceclient ← in-process entitlement client + BalanceCents
  (separate from commerceinproc: the entitlement client imports clients/plan,
  which imports cloud — commerceinproc must stay stdlib-only for build.go)
- commerce API path: api/api flattened to api (module v1.47.1)
- middleware precedence regression tests moved INTO the module beside the
  accesstoken fix they pin; the in-proc dispatch e2e stays in clients/metering
- subsystems/wire_test: freeze gitops (main had 83 specs vs 82 frozen)

Test surface green: subsystems, commerceclient (real embedded-ledger money
tests), commerceinproc, metering, catalogsync, bots, admin/finance, ml; root
package fails ONLY the 11 pre-existing env-gated tests (cek master key),
identical to origin/main.
2026-07-14 17:08:40 -07:00
hanzo-dev 5407638be7 cli: map agent Fable tier to zen5-max (top SKU)
Fable is agent's top model tier; it was pinned to zen5-pro, the
same as Opus. Point it at zen5-max (the largest zen5 SKU: Qwen3.5-397B ->
1M overflow) so the CC tier ladder is monotonic: Haiku->zen5-flash,
Sonnet->zen5, Opus->zen5-pro, Fable->zen5-max.
2026-07-14 16:20:45 -07:00
hanzo-dev 82d203a8a7 deps: o11y v1.5.28 + otel-collector v1.2.0 — evict koanf v1 monolith
Bumps the embedded o11y (v1.5.26->v1.5.28) and otel-collector
(v0.144.13->v1.2.0) to their koanf-v2 releases and drops the obsolete
otel-collector v0.144.10=>v0.144.13 replace. Removes the ambiguous
github.com/knadh/koanf/maps import (bundled v1.5.0 monolith vs split
module) that broke 'go build ./cmd/cloud'. Cloud builds green.
2026-07-14 16:20:45 -07:00
hanzo-dev 35730bd31a P2: /v1/gitops deploy dashboard API (clients/gitops)
The ArgoCD-grade GitOps control plane over the operator App CRs, native to the
cloud binary and parallel to /v1/git. SuperAdmin-only, fail-closed, Secrets never
surfaced. The console dashboard consumes these shapes:

  GET  /v1/gitops/applications        list: name, role, version(declared),
                                      runningVersion, health, sync, phase, endpoints
  GET  /v1/gitops/{name}/tree         flat node list (ArgoCD ApplicationTree) with
                                      ownerRef parentRefs + per-node health
  GET  /v1/gitops/{name}/resource/{ref} live manifest + desired-vs-live diff
                                      (ref = group:kind:namespace:name from a node)
  GET  /v1/gitops/{name}/logs         newest app pod logs (tail/container bounded)
  POST /v1/gitops/{name}/rollback     pin CR image tag to a prior semver — REUSES
                                      the P1 release seam (cloud.OnServiceRelease)
  POST /v1/gitops/{name}/sync         request an operator reconcile now

- health.go: per-resource health in the ArgoCD vocabulary (Healthy/Progressing/
  Degraded/Suspended/Missing), pure — P2b swaps to gitops-engine pkg/health.
- CR kind-collapse compat shim: reads BOTH apps.hanzo.ai (kind App, forward) and
  services.hanzo.ai (kind Service, live) — App wins the dedupe; removable
  post-cutover. spec.role surfaced.
- Wired into subsystems.Wire after paas (so the release seam is registered before a
  rollback delegates to it).

TODO seam (follow-on, noted): true GitOps on git.hanzo.ai — RegisterPushBuilder
commits the CR change to the manifest repo and the engine syncs repo→cluster;
desiredSource flips last-applied → git with no shape change.

Tests: health matrix, sync, ref-parse, membership, diff, observe, App-first/Service
-fallback resolution, list dedupe, tree ownerRef+selector. go build + test green.
2026-07-14 16:20:45 -07:00
hanzo-dev 18d086d072 ci(release): make the migration-smoke shared volume writable (fix baseline INFRA fail)
The two-boot migration smoke shares a docker named volume across boots, but a fresh
named volume is root:root 0755 while the cloud image runs non-root — so the baseline
(v1.799.19) could not create cek's <db>.cek.lock under /data and aborted before
"listening" ("cek: open lock ... permission denied"), failing the gate on infra, not a
regression. The single-boot smoke only passed because --tmpfs is world-writable.

chmod the shared volume 0777 via a root helper before the baseline boot, and again
between boots so the candidate can read the baseline's files even if runtime UIDs differ.
2026-07-14 16:20:09 -07:00
hanzo-dev 3c48fb8c0c fix(commerce): mount /v1/billing/auto-recharge as a commerce prefix — unbreak the durable-cron sweep poke
The durable platform cron (clients/cron) fires cron-billing-autorecharge every
15m as a poke: POST cloud.hanzo.svc:8000/v1/billing/auto-recharge/run-all with
the COMMERCE_SERVICE_TOKEN bearer. That path was not a commerce prefix, so it
fell through to the account-bridge /v1/billing/* catch-all, whose session gate
403s a service token ("sign in to view billing"). Live fires have been failing
on exactly that — verified in-pod: the poke returns 403 on v1.799.13.

Add /v1/billing/auto-recharge to commercePrefixes alongside /v1/billing/webhooks
— same class of route (token/signature IS the auth, no session possible).
commerce mounts at Wire order 100, ahead of the bridge, so the poke reaches gin
where commerce's own TokenRequired service-token branch + PlatformOnly gate
authenticate it. No other /v1/billing/* route changes owner.

TestAutoRechargePrefixMounted pins both prefixes so a future edit can't silently
re-break the sweep. Landed directly on main: the identical change merged four
times (#274/#275/#277/#280) and was each time force-pushed off main or closed +
branch-deleted; a PR is not a durable landing surface here.
2026-07-14 16:17:24 -07:00
hanzo-dev a5e34d8f6c Merge fix/release-migration-smoke: index-after-ADD-COLUMN store migrations + regression harness 2026-07-14 16:04:56 -07:00
hanzo-dev 36be0c4d40 fix(stores): create indexes over ALTER-added columns after the ADD COLUMN pass
tracker.migrate() indexed issues(org, repo) and issues(org, kind) in the base
DDL, but repo/kind are ALTER-added. On a legacy tracker.db (CREATE TABLE IF NOT
EXISTS no-ops) those indexes fail "no such column", migrate() fails, mount
fails, and the pod crashloops on deploy — the same class already fixed in
wallets and affiliates. Move both indexes after the ALTER pass.

Prevent recurrence with a shared regression harness (internal/migratetest):
each store contributes a legacy-DDL case that seeds its pre-migration schema and
asserts migrate() succeeds and is idempotent, proving migration-correctness as a
pure test over schema epochs instead of at prod boot. Cases added for tracker
(with a scoped-insert probe) plus the other ALTER+index stores — agents, social,
platform, provisioning, projects — which audit clean and are now locked.
2026-07-14 16:04:49 -07:00
hanzo-dev 0ccbd2eb16 ci(release): migration smoke — boot candidate over the prior release's on-disk schema
The plain smoke boots on a fresh /data, so every migrate() takes its CREATE-TABLE
path and no forward-migration runs — an index over a not-yet-ADDed column is valid
on a fresh store yet crashes on a pre-existing one (affiliates referrer_org in
v1.800.1, wallets project/agent before it), which is how a boot-crash reached prod
and took api.hanzo.ai down while every smoke stayed green.

Reproduce the real upgrade path: boot the prior released image (default
ghcr.io/hanzoai/cloud:v1.799.19, override via SMOKE_MIGRATION_BASELINE) to lay its
cek-encrypted on-disk schema into a persistent volume under one shared throwaway
master key, then boot the candidate over the same volume and require "listening". A
migrate() that assumes a fresh store fails the gate before any image is pushed.
2026-07-14 15:46:42 -07:00
hanzo-dev 986588eecd P1: native release seam — RegisterServiceReleaser patches services.hanzo.ai CR
Close push→build→image→CR: a proven, clean-semver image rolls live by patching
the matching operator hanzo.ai/v1 Service CR's spec.image directly, so the
operator reconciles the Deployment. This is the in-cluster, direct-CR replacement
for universe's image-update.yml GitOps hop (repository_dispatch → PR → ArgoCD),
with the same determinism (clean-semver only; resolve CR by metadata.name) and no
git round-trip.

- build.go: RegisterServiceReleaser / OnServiceRelease / ServiceReleaserRegistered
  inversion seam (mirrors RegisterPushBuilder), so a build-completion path rolls a
  proven image with no cloud⇄paas import cycle.
- clients/paas/release.go: releaseService — resolve CR by name (main-first),
  clean-semver gate (IsSemverTag), idempotent merge-patch of spec.image; registered
  at Mount as the releaser impl (paas owns the first-party Service CR plane).
- clients/platform/release.go: rolloutRelease — native CR patch primary, universe
  image-update dispatch kept as an additive GitOps mirror during cutover.

Tests: split/gate, patch, idempotent, reject-floating, unknown-service, main-first,
fail-closed, seam dispatch/no-op. go build + go test green (paas, platform, root).
2026-07-14 15:45:02 -07:00
hanzo-dev 45dd347761 Merge: fix affiliates migrate index order (cloud boot crash) 2026-07-14 15:22:16 -07:00
zeekay 894e49dcfd fix(affiliates): create referrer_org index AFTER ADD COLUMN (boot crash)
On a store whose affiliate_referrals table predates referrer_org, CREATE TABLE
IF NOT EXISTS is a no-op, so 'CREATE INDEX ... ON affiliate_referrals(referrer_org)'
in the same DDL batch failed with 'no such column: referrer_org' BEFORE the
ALTER ... ADD COLUMN pass ran — crashing cloud on boot (v1.800.1 CrashLoopBackOff,
api.hanzo.ai down). Move the index creation after ADD COLUMN so it is valid on
both a fresh store and a migrated one. Regression test seeds the old schema and
asserts migrate succeeds + backfills (it fails with the exact prod error when the
index is moved back into the DDL batch).
2026-07-14 15:22:16 -07:00
hanzo-dev 4b94fb9699 Merge: hanzo code claude self-identifies as a Hanzo Zen model (--append-system-prompt) 2026-07-14 15:21:18 -07:00
hanzo-dev 21a4807126 feat(code): claude agent appends the Hanzo Zen identity to its system prompt
`hanzo code claude` already pins the model to a zen5 alias (default zen5, the
GLM-5.2-class tier) and forces it on argv so a persisted /model selection
("best") cannot override it — but agent's base system prompt still tells
the model it is Claude, so a Hanzo-served model self-identifies as Claude when
asked. Append the Hanzo Zen identity via --append-system-prompt (an APPEND, not
--system-prompt: CC keeps its harness prompt for tool-use/safety/coding) so the
served model says it is a Hanzo Zen model. The identity is not a permission
bypass, so it is applied in --safe too (unlike --dangerously-skip-permissions).

codex/dev (OpenAI wire) are unchanged — the append is Anthropic-only.
2026-07-14 15:19:53 -07:00
hanzo-dev b2a4048815 Merge: bare hanzo + configurable default coding tool 2026-07-14 15:04:48 -07:00
zeekay 0495666e24 feat(cli): bare hanzo + configurable default coding tool
- `hanzo` (no args): log in if needed, then drop into the configured agent on
  a Hanzo cloud model — one word, billed to your account, all zen-native.
- `hanzo code` (no agent): runs the default agent instead of showing help.
- Default agent resolves HANZO_CODE_TOOL, then config `code_tool`, else dev.
- `hanzo config set code_tool claude|codex|dev` + `code_model` — git-style k/v,
  persisted to ~/.hanzo/config.
A named agent (`hanzo code claude`) still dispatches to its subcommand.
2026-07-14 15:04:48 -07:00
hanzo-dev 7a9b532f49 wallets: migrate columns before indexing them (fix deploy crashloop)
migrate() created ix_wallets_scope/ix_wallets_finance over project/agent/
finance_account inside the base DDL, before the idempotent ALTER TABLE that
forward-adds those columns. On a wallets table created before scoping (the prod
shape), CREATE TABLE IF NOT EXISTS no-ops, so the index build hit 'no such
column: project' -> migrate fails -> mount fails -> pod crashloop on any newer
image. Order by dependency: base tables, then ALTER-add every post-original
column (project/agent/chain/finance_account), then the indexes over them.

Regression test opens a legacy-schema wallets.db and asserts clean, idempotent
migrate + a fully-scoped insert.
2026-07-14 14:54:01 -07:00
hanzo-dev ae24015e2c Merge: resolve API keys to a principal at the identity edge (fixes zen 402) 2026-07-14 14:25:50 -07:00
zeekay c9b122830a feat(auth): resolve API keys to a principal at the identity edge
The identity boundary validated JWTs only; an opaque API key (hk-/sk-/pk-)
yielded no principal, so a subsystem that gates on the minted identity (zen's
billing gate) refused a key request as anonymous — the zen 402 'a billable
tenant is required' for a funded hk- key.

keyResolver turns a key into the SAME idClaims a JWT yields (via IAM's
authenticated get-user?accessKey, the confidential hanzo-console client), so the
ONE minting path serves both credentials and key auth and session auth can never
disagree on who a request is. An unresolved key stays anonymous — a bad key
never grants trust; an unconfigured resolver keeps keys anonymous rather than
mis-resolved. Brief generic TTL cache keeps the hot path off the network.
2026-07-14 14:25:50 -07:00
hanzo-dev a0fb6f048d fix(coding): terminal ops outlive run ctx; cloud→bot POST refuses cleartext
Red LOW-6: a timed-out coding run must still close the session and mirror
its terminal result. Run terminal-side ops (fail/CloseSession/mirror/CreatePR)
under context.WithoutCancel so an expired run ctx cannot strand a session in
'running'.

Red MEDIUM-3: the cloud→bot coding POST carries the org hk- git credential and
the shared gateway bearer. Fail closed on a cleartext http:// target; a plaintext
in-cluster hop is allowed ONLY when the operator asserts mesh mTLS via
BOT_GATEWAY_ALLOW_PLAINTEXT=1. Error never echoes the credential.
2026-07-14 13:59:57 -07:00
zeekay 0b8aa9b748 deps: bump hanzoai/zen v1.2.0→v1.3.0 (cost-basis + margin pricing) 2026-07-14 13:32:08 -07:00
blue 28ceaec797 style: gofmt coding orchestrator + tracker agentpr + slack_coding test 2026-07-14 13:22:13 -07:00
blue dd4c95b44d feat(coding): @hanzo agent keystone — native coding tasks from Slack
Turn @hanzo from a chatbot into an engineer. A Slack message
`@hanzo code: <repo> <task>` branches off the chat-only reply into a
durable coding run: register a live agent session, dispatch to the
bot-gateway sandbox, mirror progress into the session live, verify the
pushed branch landed in native /v1/git, open a native PR work item, and
report the branch + PR back in-thread. Non-code mentions keep the
existing chat path unchanged.

- clients/coding: transport-agnostic orchestrator (Dispatcher over
  interface seams; unit-tested with fakes, org-isolated, no credential
  leak into session events/PR body). Cannot import git (cycle via
  integrations) so CloneURL/VerifyRef are injected at the composition root.
- clients/agents/inproc: in-process session API (Open/Log/Close) — the
  twin of the /v1/agents/sessions control plane, same store + live bus.
- clients/tracker/agentpr: in-process Kind:pr Source:agent work item,
  org-scoped, get-or-create repo board (KEY-N).
- clients/bot/coding: in-process NDJSON client for POST /v1/coding-tasks;
  credential travels in the body only, never argv/URL/logs.
- clients/git/export: CloneURL + VerifyRef seams (org-scoped ref check).
- clients/integrations/slack_coding: the code: trigger, credential fetch
  from KMS (fail-closed), ack, detached bounded run, result Block Kit card.
- subsystems/wire_seams: compose the Dispatcher (git seams + adapters)
  and inject into the Slack surface.

Tenant isolation fail-closed: org is the only tenant key on every seam;
sandbox pointed only at the caller org's clone URL with an IAM-scoped
credential; cross-org repo targeting is refused by git's path-vs-identity
guard. Tests: CGO_ENABLED=0 go test green across all touched packages.
2026-07-14 12:45:37 -07:00
zeekay c6e69b502d deps: bump hanzoai/zen v1.1.0→v1.2.0 (coherent lineup + thinking effort)
Pulls in the reworked zen family (one SKU per capability, every upstream
verified on DO) and the hanzoai/thinking depth fold (effort → each upstream's
native reasoning shape). Adds hanzoai/thinking v0.1.0 as a direct require.
2026-07-14 12:40:54 -07:00
hanzo-dev 7e4ddcbc44 Merge: hanzo code claude defaults to zen5 (GLM-5.2) 2026-07-14 12:39:26 -07:00
zeekay 8f466533db feat(cli): hanzo code claude defaults to zen5 (GLM-5.2)
zen5 is the flagship GLM-5.2-class alias (1M ctx, tool-capable — the glm-5.2
upstream returns tool_use/stop_reason:tool_use, verified live). Matches the
intent to launch agent on GLM-5.2 through api.hanzo.ai. Was zen5-pro
(DeepSeek). The four CC tier slots stay pinned to served zen5 aliases so the
classifier, subagents, and /compact never hit an unserved claude-* id.
2026-07-14 12:38:19 -07:00
hanzo-dev 8244dd0388 git lifecycle: escape branch name in Slack blocks (Red residual LOW)
ev.Branch was an un-escaped mrkdwn sink: git refnames allow < > & !, and the
receive-pack fire path (branchTips → for-each-ref) applies no branchRE, so a
hostile branch (e.g. x<!channel>y) flowed verbatim into the summary and the
*Branch* field of every subscribed channel. slackEscape it in both places, and
defensively escape the org/repo display text too (a deploy event's repo derives
from an unconstrained RepoURL, though it is subscription-gated to a valid name).

TestNotifyEscapesMrkdwn now also pushes a hostile branch through smart-HTTP with
the real git CLI (go-git rejects such a refspec) and asserts it is neutralized in
both the summary and the Branch field.
2026-07-14 12:06:41 -07:00
hanzo-dev 3741c9adcf git lifecycle: address Red review (fix-then-ship)
HIGH-1 mirror-out no longer starves the shared pack plane: dedicated mirrorSem
(separate from packSem), per-push context.WithTimeout, git http.lowSpeed abort,
and cmd.WaitDelay so a stalled downstream's network-helper child can't wedge the
slot past the deadline.

MED-2/MED-3 full (org,project,repo) identity: subscriptions + mirror targets key
on project too (DDL + every list/delete + the notify + mirror fire paths); deploy
emitters thread project (platform a.ProjectID normalized, projects org-level);
repo delete cascade-deletes its subscriptions + mirrors in one tx (no
exfil-on-recreate via an orphaned target).

MED-1 decouple allowlists: outbound mirror TARGET set = {github.com, gitlab.com}
only; the local git host is rejected as a target (no internal SSRF /
privileged-cred presentation). Inbound-fetch credential gate unchanged.

MED-4 Slack mrkdwn escaping of user-derived text (commit subject, pusher, deploy
detail) so a crafted commit subject can't inject <!channel>/disguised links.

LOW-1 keep the shared bot token least-privilege (no chat:write.public — it would
also arm the @hanzo assistant to post uninvited); notifications require the bot
be invited. INFO: reject non-deliverable build.started at subscribe time; DRY
repoFromURL into cloud.RepoFromCloneURL.

Re-verified: new tests for project-scoped routing, delete-cascade, mrkdwn escape,
and stalled-downstream isolation; suites green under -race; gofmt+vet clean;
go.mod untouched.
2026-07-14 11:49:03 -07:00
ec4112183a test(subsystems): base gained Shutdown via per-org embed (#298) — sync frozen wire order (#300)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 11:23:45 -07:00
c307842105 analytics: capture (write) plane — POST /v1/analytics + /v1/tracker → hanzo.events (#296)
* analytics: add capture (write) plane — POST /v1/analytics + /v1/tracker → hanzo.events

The analytics subsystem served only read lenses over hanzo.events; nothing
wrote the table, so the web/commerce lenses were permanently honest-empty. This
adds the symmetric ingest: products POST batches to cloud (the ONE native front
door) and cloud writes org-scoped rows into the datastore warehouse the read
side already queries.

- POST /v1/analytics, /v1/analytics/batch, /v1/tracker (beacon alias) — all
  tenant-gated in-handler; tenant_id is always principal.Org, never client input.
- Writes ride ai/object.DatastoreExec (the SAME pooled client the reads use).
- The writer owns the hanzo.events DDL (EnsureEventsTable, idempotent/latched).
- Privacy scrub: credential/PII-shaped property keys dropped, email values
  redacted, before any row is built.
- Pure core (normalizeEvent/scrubProps/buildEventsInsert) unit-tested; HTTP
  contract tests cover no-principal 403, forged-org 403, oversized 400,
  datastore-down 503; a build-tagged live test proves the full round trip
  against a real datastore.

* analytics: accept anonymous capture, attributed to the brand-public org

Marketing sites emit anonymous pageviews (no session). captureTenant now falls
back — when there is no validated principal — to the PUBLIC brand org derived
SERVER-SIDE from the request Host via the white-label registry (BrandForHostOK),
never a client-claimed org. A forged X-Org-Id is still ignored, and an
unrecognized Host is refused (anonymous events are never dumped into a default
org). Gated by CLOUD_ANALYTICS_PUBLIC_CAPTURE (default on, matching the existing
public insights-capture posture). Verified live: an anonymous pageview to
Host hanzo.ai lands under tenant_id=hanzo.

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 11:21:54 -07:00
7583c9394a marketing: grow /v1/marketing into the full GTM engine (#299)
Fold the remaining GTM subsystems into clients/marketing (native Go, per-org
SQLite, twin of clients/crm), so nothing Python is load-bearing in the mount
path:

- Email drip sequences on the embedded hanzoai/tasks engine (drip.go): a
  per-minute durable schedule sweeps due enrollments; each (enrollment, step)
  is claimed once so a step delivers at most once across restarts/redelivery,
  then the walk advances or completes. Mirrors clients/cron (engine owns time,
  SQLite owns the schedule) — no Redis, no bespoke ticker.
- The ONE send seam (suppress.go): every marketing delivery funnels through
  state.deliver, which enforces the per-org suppression/opt-out list and then
  hands off to the platform notify rail. Expose notify.Send so the existing
  sender is reachable in-process — one sender, not a second. Plus a signed
  public one-click unsubscribe.
- Audiences (audiences.go): cohort filters evaluated live against the org's
  hanzo.events analytics via the ai/object datastore, tenant_id-scoped and
  honest-empty when the warehouse is not wired.
- Promo codes (promos.go): the First-1,000 90%-off launch promo (discounts.md)
  realized as a non-cash wallet credit through the finance ledger, with the
  hard 1,000 cap, one-per-org, one-per-instrument and team-seat-cap guards.
- Content calendar (calendar.go): scheduled posts as documents published by a
  task-executed hook; social publish returns an honest 501 until a connector
  is wired (clients/social's push is fail-closed, the automations connector
  registry is package-private).
- Campaign scheduling (scheduled_at + the scheduled state).

Real tests: drip scheduling + per-step idempotence + tenant isolation,
suppression enforcement at the gate, promo eligibility math + abuse guards.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 11:21:24 -07:00
hanzo-dev 19e2513cff git lifecycle event stream + Slack-notify and outbound-mirror subscribers
Generalize the single-registrant git push→deploy hook into a many-subscriber
lifecycle stream without regressing push→deploy. RegisterPushBuilder/OnGitPush
stay exactly as-is (deploy is the subscriber-of-record); alongside them a new
RegisterLifecycleSubscriber/EmitLifecycle fans ONE LifecycleEvent out to N
reactors, best-effort, detached, on a cancel-immune context, panic-contained.

Emit points: PushLanded at the one branch-build funnel (covers HTTP/SSH/push,
now carrying before/after tips + pusher); BuildStarted/DeployLive/DeployFailed
at the platform (startGitBuild / applyLive / failDeploymentCtx) and projects
(deployGit / deployArtifact / completeDeployment) transitions.

Subscriber 1 — Slack notify: per-org repo→channel subscriptions
(/v1/git/repos/:name/subscriptions) stored in the existing per-org git.db,
delivered as Block Kit via the ONE integrations chat.postMessage path
(integrations.NotifySlack/PostSlackBlocks; the automations connector now shares
it). Adds chat:write.public so a freshly-subscribed public channel works
without a manual invite.

Subscriber 2 — outbound mirror: per-repo downstream targets
(/v1/git/repos/:name/mirrors) force-push ONLY the advanced branch to
allowlisted hosts (github.com/gitlab.com/git.hanzo.ai), token via env-only
http.extraHeader under the pack-slot semaphore. LifecycleEvent.Origin is the
loop-prevention seam for a future inbound sync.

All routes org-scoped + fail-closed; tenant isolation, injection, allowlist,
and loop-prevention covered by tests.
2026-07-14 11:17:52 -07:00
zandGitHub 9301e57ed4 Merge pull request #297 from hanzoai/feat/company-formation
Hanzo Company — incorporation + fundraising state machine (/v1/company)
2026-07-14 11:17:14 -07:00
4a0b40aa71 feat(base): per-org multi-tenant Base hosting at /v1/base/* (kill superbase wrapper) (#298)
Upgrade the in-process Base embed from the single-instance waitlist-only fold
(#193/#211/#248) into two orthogonal lanes on the ONE engine:

  - LANE 1 (unchanged surface): the platform waitlist app → public /v1/waitlist/*.
  - LANE 2 (new): managed Base hosting → ONE Base app PER ORG, opened lazily and
    LRU-pooled, each on its own SQLite under {DataDir}/base/{TenantSegment}/ (the
    HIP-0302 'SQLite per tenant' model the gojabase leaves use). Served
    authenticated under /v1/base/*, the org resolved from the VALIDATED cloud
    principal (principal.Org) — physical per-org isolation, the console Bases
    manager's backend and the in-binary replacement for the superbase pod.

Base serves under BASE_API_PREFIX=/v1/base so its collections API mounts natively
(self-URLs included) without colliding with cloud's other /v1 routes; the waitlist
plugin binds a FIXED /v1/waitlist regardless. Per-org apps validate bearers against
Hanzo IAM's JWKS as their exclusive auth source (apis.StoreKey{JWKSURL,
ExternalAuthOnly}) — ONE IAM, no second auth path. The cloud binary owns the ZAP
transport, so embedded apps set ZAP_DISABLED. Shutdown releases the platform app +
every pooled per-org app.

Reuses gojabase.TenantSegment (the ONE injective, traversal-safe org->path encoder).
Test: subsystem boots in the harness, a collection record round-trips per-org
isolated over the real HTTP path (acme's record invisible to globex; distinct
on-disk dirs).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 11:16:33 -07:00
hanzo-dev 1e363e9475 captable: harden the http_test fiber timeout (pre-existing flake); wire company after guide/x402 in the frozen order 2026-07-14 11:12:53 -07:00
hanzo-dev ff57ba838f company: make genesis idempotent (no double share issuance) + propagate save error 2026-07-14 11:10:51 -07:00
hanzo-dev e01eb60d90 feat(company): Hanzo Company — incorporation + fundraising state machine
Adds clients/company (/v1/company): one formation state machine per org
(structure → founders+KYC → $999 → documents → esign → on-chain equity
genesis → company), with a SKIP path for already-incorporated orgs that
imports corporate docs → data room and a cap-table sheet → captable.

- machine.go: pure transition table + per-edge guards; the payment gate,
  KYC gate, and skip path are unit-tested with no I/O.
- providers.go: narrow seams for billing/kyc/docs/esign/captable/anchor/
  filing/upgrade. Billing wires the shared ResourceMeter ($999). KYC and
  state filing are honest stubs (no fabricated verification/filing).
- genesis.go: KMS-signed Hanzo-L1 equity-genesis anchor mirroring
  clients/treasury; computes the root always, commits on-chain when wired,
  honest pending otherwise.
- adapters.go + captable.facade + dataroom.Ingest: new in-proc facades so
  company writes the cap table and data room without an HTTP hop.
- google provider completed in clients/integrations (OAuth + KMS token
  custody); the automations google_sheets/google_drive connectors are
  consolidated to one `google` connector sharing that token; company import
  reads Drive/Sheets through it.
- wired into subsystems.Wire() after referrals; docs/company-dogfood.md
  walks Hanzo/Lux/Zoo through the import path.
2026-07-14 11:10:51 -07:00
82b83297fe feat(guide): Business AI Guide — /v1/guide launch checklist + agent (#282)
clients/guide + /v1/guide/*: a per-org checklist engine over a
machine-readable curriculum (Step: id/title/why/how/done/dependencies/
signal/tool). Per-org progress on cloud.OrgStore; next-step + dependency
gating are pure functions; auto-detect reconciles a step to done when its
signal maps to real org state (acted = agent action ledger; analytics =
shared warehouse events). Business AI 'do it for me' drafts with deps.AI
then executes the step's bound MCP tool via automations.InvokeTool AS THE
CALLER — attributable, metered, audited, never exceeding the caller's
authorization. Built-in default.yaml (7 steps: positioning→landing→
analytics→waitlist→email→referral→launch) seeds it before marketing's
checklist.yaml; an org-custom PUT replaces it cleanly.

clients/automations: decomplect tool dispatch (dispatchTool) from its two
doors — the HTTP MCP handler and the new in-process InvokeTool/ToolExists
seam — so both share one dispatch, org-scoped credential, concurrency
bound, meter and audit.

Tests (pure-Go, CGO_ENABLED=0): validation/cycle-detection, next-step +
dependency gating, auto-detect reconcile (present/absent/error/terminal),
the acted detector end-to-end, the agent (tool success/failure/assisted/
unknown-tool), and the HTTP surface (403 gate, transitions, 409 gating,
curriculum replace/revert, per-org isolation, do-delegation).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 11:05:32 -07:00
b89f0f9602 feat(growth): multi-level referral upline + OSS-author royalties in one accrual walk (#295)
Extend the existing affiliate accrual into a depth-capped multi-level upline and
fold OSS-author royalties into the SAME per-org spend walk, over one attribution
spine.

Affiliates — multi-level upline (clients/affiliates):
- The referredBy graph is the existing affiliate_referrals edge made walkable
  (referred_org -> referrer_org, denormalized). referredBy is set-once/immutable
  (UNIQUE referred_org) with cycle detection at set time (wouldCycleOrg climbs the
  proposed referrer's upline and refuses a loop).
- Per-level schedule L1 20% / L2 5% / L3 2%, depth cap 3. L1 uses the affiliate's
  own negotiable rate (default 20%, preserving prior single-level behavior); L2/L3
  are platform constants. accrual rows carry the level for analytics.
- The admin sweep is source-centric: fold over every referred org, read spend ONCE,
  walk the upline and accrue to each ancestor's approved affiliate, latched
  at-most-once per (affiliate, source, period). The per-affiliate dashboard read
  walks the downline (same latch key, never double-accrues).
- User-level referredBy graph (user_referrals): set-once + cycle-checked, mirroring
  the org edge; recorded from the referee's user to the affiliate's owner user.
- Payout no-overdraw guarantee unchanged (pending-guard + treasury reserve backing).

Authors — OSS royalties (clients/authors):
- Default author share 25% (was 5%).
- GitLab provider alongside GitHub: host-aware repo canonicalization (github.com +
  gitlab.com), provider-dispatched forge seam (linkedAccount/repoAdmin/fetchFile).
- Append-only, on-chain-ready royalty ledger (author_ledger) with a nullable
  compute_proof column, written per accrual in the same transaction as the balance
  move. compute_proof stays NULL — the hanzod attestation is a follow-up, not faked.
- AccrueForOrg seam: the affiliate sweep drives author royalty for each source org
  with the spend it already read — one accrual walk. Nil-safe when authors is
  unmounted (mirrors treasury.Reserve).

Surfaces:
- GET /v1/affiliates/me — my code, link, downline by level (L1/L2/L3 with rates +
  counts), accrued/pending/paid, payouts.
- GET /v1/admin/referrals — unified SuperAdmin cross-tenant analytics (top referrers,
  conversion, accrual liability by level). The one-time-bonus board moves to
  GET /v1/admin/referrals/bonuses (referrals) so the two compose without colliding.

Tests: 3-level walk math + depth cap, cycle rejection (org + user), set-once
immutability (org + user), no-overdraw payout, GitLab verify + ledger row with NULL
compute-proof, both surfaces. Deterministic fiber test timeout (30s ceiling; the 1s
default flaked under machine load).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 10:53:48 -07:00
f7b5178f0d kb: wikilink graph — extraction, /v1/kb/graph, and vault import (#294)
Complete the native knowledge graph on the kb subsystem.

Wikilink edges: the kb-page after_save hook now extracts [[Page Title]]
references from the page body (the same flattened Lexical text the vector
indexer embeds) and reconciles them into kb-link edge documents — a Link
(source) + Data (target_title) reference, no parallel store. Index and link
maintenance run as one combined page hook so a vector outage never skips link
extraction. Targets resolve to a page by value at read time, so a rename or
trash of a target needs no edge rewrite; a page's own trash removes its
outgoing edges.

GET /v1/kb/graph: the org's knowledge as nodes (kb-page/kb-memory/kb-source,
plus connector and dangling-link endpoints) and edges (parent tree, wikilinks,
connector provenance), org/project scoped, shaped for a force-directed
renderer.

POST /v1/kb/import: an Obsidian-importer-equivalent that ingests an Obsidian
vault zip, Notion export zip (markdown/HTML), Evernote .enex, or Roam JSON as
a kb-page tree with links preserved. Each format is a pure normalizer package
(obsidian/notion/roam/evernote over vault + lexical), mapping to pages filed
through the same framework.Ingest path a connector sync uses — the after_save
hook then extracts their wikilinks, one link path for authored and imported
pages alike.

framework: add the in-process Delete (twin of the HTTP delete, runs on_trash)
used by edge reconciliation.

Tests: table-driven wikilink extraction; per-format normalizer tests with real
fixture files; end-to-end graph, import, and full edge lifecycle (extract,
reconcile-on-edit, source-trash cleanup, target-trash dangling) over the real
framework store.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 10:53:02 -07:00
hanzo-dev 4dcd1d6e8f analytics: accept anonymous capture, attributed to the brand-public org
Marketing sites emit anonymous pageviews (no session). captureTenant now falls
back — when there is no validated principal — to the PUBLIC brand org derived
SERVER-SIDE from the request Host via the white-label registry (BrandForHostOK),
never a client-claimed org. A forged X-Org-Id is still ignored, and an
unrecognized Host is refused (anonymous events are never dumped into a default
org). Gated by CLOUD_ANALYTICS_PUBLIC_CAPTURE (default on, matching the existing
public insights-capture posture). Verified live: an anonymous pageview to
Host hanzo.ai lands under tenant_id=hanzo.
2026-07-14 10:52:17 -07:00
d251740a37 feat(wallets,x402): scoped custody {org,project,agent,account} + native x402 pay-per-use (#293)
Wallets custody scoping (clients/wallets)
- One Scope type {org, project, agent, account} is the ONE key both the KMS
  secret ref (keyRef) and the store lookup derive from. Org stays the hard
  isolation boundary; project/agent/account are optional narrowings within it.
- keyRef derives from the full scope, injection-safe (narrowings validated to a
  slash-free segment). An org-only wallet keeps its exact legacy ref, so scoping
  is additive, not a migration.
- listWalletsByScope is the one scope-filtered read path (org bound, narrowings
  filter within); create + list handlers thread the scope. Store gains project +
  agent columns (forward ALTER, dup-column tolerant).

Native x402 pay-per-use subsystem (clients/x402, /v1/x402)
- challenge (402 + PaymentRequirements) -> client signs ERC-3009 -> proof ->
  Verify (EIP-712 secp256k1 recovery via luxfi/crypto, the same primitive wallets
  signs with) -> settle -> serve. Enforce is a zip middleware a priced route
  group applies.
- Idempotent + replay-safe: settlement id is deterministic in (from, nonce); a
  spent nonce reused for different terms is a replay (402), a re-submitted
  authorization is an idempotent retry (settled + metered once). Two independent
  guards: the PK-atomic store claim and the ledger's own RequestID/Ref idempotency.
- Settlement wires into the metering spine: the payer's org is debited through
  metering so paid usage appears in billing/usage like any metered spend, and the
  recipient wallet's ledger is credited. Ledger settlement is LIVE; on-chain
  broadcast of the authorization is a seam (not wired).
- Marketplace seam: a Registry (Publish) maps resource -> Terms (price + recipient
  wallet ref); x402 resolves the recipient via wallets.ResolvePaymentTarget and
  enforces. The registry itself is another subsystem's work.

Removes the dead, unreferenced clients/commerce/payment/x402 (gin + btcec) so the
binary has exactly one x402.

Tests: scope derivation + injection + scoped seal/sign + scope lookup isolation;
EIP-712 verify round-trip/tamper/term-binding; challenge->verify->serve, nonce
replay rejection, settle-once on retry, free passthrough, payer-required, and
end-to-end ledger settlement (payer debited once, recipient credited once).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 10:51:18 -07:00
ba24d1ce97 feat(tools): unified tool plane + marketplace (registry, activation, external-MCP, full-cloud-control, x402 seam) (#292)
* tools: unified tool-plane registry, activation, external-MCP + builtin sources

ONE registry where a tool is {name, source, schema, per-(org,project) activation,
optional price}. Sources register a Provider (List+Dispatch) into it; the registry
enforces the one policy: precedence dedup, activation gate (403), x402 Charger seam
(fail-closed for priced tools), then dispatch. Ships two package-owned sources:
external MCP servers (KMS-sealed auth, SSRF-guarded) and full-cloud-control builtin
(every /v1 route, dispatched in-process replaying the caller credential). Real
tests: precedence, activation 403 + cross-org isolation, priced fail-closed,
external-MCP dispatch, builtin route dispatch, SSRF guard.

* tools+marketplace: register sources, x402 price seam, wire subsystems

Sources register a Provider into the tool plane from their OWN Mount (no source
duplicates its listing logic): connectors (automations), functions, agents, and
skills (discovery-only). Adds the registry Pricer seam + public activation
pass-throughs (Activate/Deactivate/Activated/Exists) so marketplace install IS the
tool activation write and a published listing's price reaches per-call dispatch
enforcement.

clients/marketplace: /v1/marketplace listing/discovery/install over the plane;
monetized listings declare price + recipient wallet and settle through the tools
Charger (x402) seam — proven end-to-end (publish→install→dispatch charges the
seller). Wires tools + marketplace into subsystems.Wire() (frozen-order updated).

Tests: marketplace install==activation + cross-org isolation, phantom 422, publish
validation, monetized dispatch settlement, discovery overlay.

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-14 10:48:38 -07:00
hanzo-dev 684fa2b79b feat(git): repo maintenance — bitmap + commit-graph for fast clones
A repo populated by fetch/receive-pack accumulates objects via index-pack,
which writes a pack but no reachability bitmap and no commit-graph — so every
upload-pack walks the whole object graph to build the clone pack (O(objects)
per clone). Add maintenance on the git-exec seam: repack -adb --write-bitmap-index
+ commit-graph write --reachable --changed-paths, under one pack slot with the
same memory bounds as every pack op (a multi-GB gc can't OOM the pod).

- POST /v1/git/repos/:name/gc — on-demand repack, org-scoped, 404 fail-closed.
- Post-push autoMaintain: fire-and-forget git gc --auto after every receive-pack
  (HTTP + SSH), slot-yielding (skips when clones are busy) so repos self-maintain
  as pushes accumulate packs, no scheduler.

Tests: runMaintenance writes bitmap + commit-graph and the repo stays clonable;
the /gc endpoint repacks (200 maintained) + 404s unknown/cross-tenant repos.
2026-07-14 08:50:26 -07:00
antje 8505bee2a2 deps: bump ai v1.807.0 -> v1.808.0
Bearer-auth get-cloud-usages + brand-scoped god-view (one UsagePanel across
app/chat/billing). Blue+RED reviewed; build+tests green.
2026-07-14 08:32:16 -07:00
hanzo-dev e0d8e5241c fix(git): read the framework-decoded pack request body, don't re-inflate
Fiber's Body() transparently inflates a Content-Encoding: gzip request per
its header (BodyGunzipWithLimit + SetBodyRaw), so c.Body() is already the
decoded pkt-line stream. packRequestBody inflated it a second time and
returned 400 "invalid gzip request body" for every compressed clone/fetch.
git gzips the ref-negotiation once a repo carries enough refs, so this broke
clone for all but trivially small repos — the small-repo round-trip tests
sent the request plain and never exercised the compressed path.

Read c.Body() verbatim (the framework owns Content-Encoding). Add a gzipped
upload-pack regression test through the live Fiber server that fails on the
double-decode and passes on the fix.
2026-07-14 08:16:46 -07:00
hanzo-dev 8f2746057b deps(ai): bump hanzoai/ai v1.806.15 -> v1.807.0
Ships the zen consolidation: ai discovers the Zen family from the zen service
(GET $ZEN_URL/v1/models) and fronts it, holding no zen routing/pricing/identity
of its own. Pulls the corrected per-upstream reasoning vocabulary and the
money/decimal billing types transitively.
2026-07-14 07:43:32 -07:00
hanzo-dev f820ac0a5c feat(git): streaming git-CLI object plane — bounded memory, protocol v2 (red-reviewed GO) 2026-07-14 07:08:45 -07:00
hanzo-dev e4e09768d2 chore(deps): fold released hanzoai/ai v1.806.15 (#290,#291) into main 2026-07-14 07:08:45 -07:00
hanzo-dev 3d5b891e37 git: harden the streaming object plane (red review deltas)
Address the red-team findings on feat/git-streaming-object-plane:

HIGH-1 mirror credential exfiltration: only attach GIT_MIRROR_TOKEN to hosts
on an allowlist (GIT_MIRROR_ALLOW_HOSTS, default {github.com, git.hanzo.ai});
any other https source fetches anonymously so a tenant-supplied URL can't
capture the shared token. Set http.followRedirects=false on the mirror fetch
so the token can't ride a cross-host redirect.

MED-2 pack RAM: add -c pack.threads=1 -c pack.windowMemory=64m
-c pack.deltaCacheSize=64m -c core.bigFileThreshold=16m to every pack/fetch
subprocess, and a concurrency semaphore (GIT_PACK_MAX_CONCURRENCY, default 2)
around all pack ops so concurrent large clones/mirrors can't multiply RAM in
the shared cgroup.

MED-3 org traversal: gate the org identifier through orgRE (alnum-led, no
'/'/'\\', no leading '.') in org(), so a SuperAdmin X-Org-Id switch to
"../../etc" is rejected at the git boundary before it reaches absRepoPath.

MED-4 mirror SSRF: resolve the source host and refuse loopback / private /
link-local / metadata (IMDS) / unspecified / multicast targets;
GIT_MIRROR_ALLOW_PRIVATE_HOSTS allowlists internal hosts for tests /
deliberate internal mirrors. Generic rejection message (no probe oracle).

MED-5 pack-to-disk DoS: -c receive.maxInputSize (GIT_RECEIVE_MAX_INPUT_SIZE,
default 2g) on receive-pack so a gzip-amplified or runaway push can't fill
the pod disk.

MED-6 disconnect reaping: gitPackStream.Close now closes the read pipe and
Kills the process before Wait, and runPackSSH Kills on a channel-copy error,
so an abandoned clone can't leave git blocked on a full pipe (leaked
proc/goroutine/FDs).

LOW-7 strip URL userinfo in mirrorSource (credentials via env only, never a
ps-visible argv). LOW-8 close std pipes on cmd.Start failure.

Tests: org-traversal rejection, disconnect-reaping (Close returns promptly +
process reaped + slot released), mirror credential host allowlist, and mirror
SSRF + userinfo strip; existing suites stay green.
2026-07-14 06:54:11 -07:00
hanzo-dev d2a38d9aed git: back the object plane with the streaming git CLI for bounded memory
The heavy git paths buffered whole packs in RAM via go-git's pure-Go
server transport and FetchContext: a clone serialized the entire outgoing
packfile into a bytes.Buffer, a mirror indexed the whole incoming pack in
memory, and receive-pack read the full push body. Mirroring a multi-GB
repo OOM-killed the 1 Gi cloud pod.

Route the object plane through the streaming git CLI instead — the way
gitea/GitLab serve smart-HTTP — so packs stream to and from disk with
memory bounded by an OS pipe:

- clone/fetch serve: `git upload-pack --stateless-rpc`, git stdout streamed
  straight to the HTTP response (SendStream); no pack buffer.
- push receive: `git receive-pack --stateless-rpc`, request body -> git
  stdin -> index-pack to disk; only the small report-status is buffered.
- info/refs: `git <svc> --stateless-rpc --advertise-refs` + pkt-line header.
- mirror-in: `git fetch --prune --tags +refs/*:refs/*` against the on-disk
  bare repo; ls-remote --symref resolves the source default branch for HEAD.
- SSH: plain `git upload-pack`/`git receive-pack` over the channel.

One git-exec seam (gitexec.go) builds every subprocess with a hardened,
minimal env (GIT_CONFIG_NOSYSTEM, GIT_CONFIG_GLOBAL=/dev/null, no inherited
secrets, GIT_TERMINAL_PROMPT=0, GIT_NO_REPLACE_OBJECTS) and arg slices only.
Protocol v2 is forwarded from the client Git-Protocol header / SSH env
(validated). Mirror source credentials are injected only via env git-config
http.extraHeader (GIT_MIRROR_TOKEN), never argv or logs, under
GIT_ALLOW_PROTOCOL=http:https. Tenant isolation stays on the validated
absolute bare-repo path (storage.absRepoPath); the handler org/path guards
are unchanged.

Push-to-deploy is preserved via a branch-tip diff (before/after
for-each-ref) that fires cloud.OnGitPush for every advanced branch, and
metering (recordUsage) runs after every push. The go-git server transport
is removed; go-git remains only for bounded init/ref-read/object-building.

Runtime: add git to the alpine stage (upload-pack/receive-pack/http-backend/
git-remote-https).

Tests: real git-CLI clone+push round-trip, a 48 MiB clone proving the pack
streams with ~120 KB server heap growth, mirror from an external
git-http-backend source, and the existing tenant-isolation + push-to-deploy
suites, all green.
2026-07-14 06:12:40 -07:00
d575792666 fix(deps): correct hanzoai/ai v1.806.15 go.sum hash (#291)
The v1.806.15 tag was re-pointed to the current fix commit; a stale local
module cache wrote the previous tag content's hash into go.sum in #290, so
cloud CI's fresh download failed verification (checksum mismatch / SECURITY
ERROR). Re-fetched the module clean so go.sum records the actual v1.806.15
content hash. No code change; go.mod pin unchanged.

Verified: CGO_ENABLED=1 go build -tags "libsqlite3 sqlite_fts5" ./cmd/cloud → 0.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-13 23:37:21 -07:00
1c7128419a fix(deps): bump hanzoai/ai v1.806.13 -> v1.806.15 (#290)
Carries the hanzo-code-claude corrections (ai 68be82cf, first in v1.806.14):
per-upstream reasoning-effort vocabulary (GLM/DeepSeek max|high, not OpenAI
low|medium|high) and round-tripping assistant thinking as reasoning_content
so DeepSeek/Kimi tool-call loops no longer 400/stall. v1.806.15 also carries
ai's luxfi/geth proxy-resolution CI fix and the native Responses work.

Prod (cloud v1.799.16) embedded ai v1.806.13, which predates these fixes.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-13 23:28:17 -07:00
zandGitHub 0b8fd867c3 Merge pull request #285 from hanzoai/fix/cloud-gomod-cache-v4
fix(ci): retry Zen resolution after publishing tag
2026-07-13 17:07:34 -07:00
hanzo-dev 88b97a7fb7 fix(ci): retry Zen resolution after publishing tag 2026-07-13 17:07:28 -07:00
zandGitHub cea10dfefb Merge pull request #284 from hanzoai/fix/cloud-gomod-cache-v3
fix(ci): cold-bust poisoned Zen module cache
2026-07-13 17:04:49 -07:00
hanzo-dev 67b808bee5 fix(ci): cold-bust poisoned Zen module cache 2026-07-13 17:04:25 -07:00
zandGitHub e6268be2f7 Merge pull request #283 from hanzoai/fix/code-full-auto-tool-default
fix(code): full-auto defaults on tool-capable model
2026-07-13 17:02:32 -07:00
hanzo-dev e862cfaace fix(code): default agents to full-auto tool-capable model 2026-07-13 17:02:10 -07:00
hanzo-dev 92530c589a analytics: add capture (write) plane — POST /v1/analytics + /v1/tracker → hanzo.events
The analytics subsystem served only read lenses over hanzo.events; nothing
wrote the table, so the web/commerce lenses were permanently honest-empty. This
adds the symmetric ingest: products POST batches to cloud (the ONE native front
door) and cloud writes org-scoped rows into the datastore warehouse the read
side already queries.

- POST /v1/analytics, /v1/analytics/batch, /v1/tracker (beacon alias) — all
  tenant-gated in-handler; tenant_id is always principal.Org, never client input.
- Writes ride ai/object.DatastoreExec (the SAME pooled client the reads use).
- The writer owns the hanzo.events DDL (EnsureEventsTable, idempotent/latched).
- Privacy scrub: credential/PII-shaped property keys dropped, email values
  redacted, before any row is built.
- Pure core (normalizeEvent/scrubProps/buildEventsInsert) unit-tested; HTTP
  contract tests cover no-principal 403, forged-org 403, oversized 400,
  datastore-down 503; a build-tagged live test proves the full round trip
  against a real datastore.
2026-07-13 16:09:17 -07:00
hanzo-dev 47a98eb808 git: serve smart-HTTP at the git-host root so git clone https://git.hanzo.ai/<org>/<repo>.git works
Add host-guarded root-level /:org/:repo/{info/refs,git-upload-pack,git-receive-pack}
reusing the existing handlers. onGitHost gates on the request Host == git host
(defaultSSHHost(Domain)); on api/console hosts the routes fall through (c.Next())
so a bare /:org/:repo never shadows another surface. Advertised clone URL stays
/v1/git until cutover. Test: TestRootSmartHTTP_HostGuard (git host → handler runs;
other host → 404).
2026-07-13 15:41:24 -07:00
hanzo-dev 7b5a8a5642 cloud: mount zen co-resident + 18-dp-native metering
zen mounts as a /v1-scoped Claim middleware BEFORE ai's /v1/* catch-all
(Wire position 100, ahead of ai at 150). Claim routes every request whose
model is a zen SKU to zen's serving layer in-process and c.Next()s the rest
to ai, so zen owns the zen family (identity, tools, 1M ladder, codec) and ai
owns every other model + /v1/models. The frozen wire sequence is updated.

Billing for zen* moves from ai's in-handler metering (skipped — zen claims
before ai's beego catch-all) to zen's own Gate+Meter wired to the same
commerce metering client the edge gate uses — ONE billing source for zen*,
never double-billed, never free. Granularity is org/project/user mirroring
the edge gate: home org (principal.BillingOrg) pays, project
(principal.ValidatedProject) scopes spend caps, user is attributed. An admin
acting in another org bills their own home org.

metering.Usage now carries a typed money.Amount (native 18-dp USD — the
finance ledger's own precision) as the canonical debit; Record passes it
straight to finance with NO flooring to cents or micros, so an exact
per-token cost from zen debits exactly. Legacy AmountCents/AmountMicros
reconstruct the same Amount for older callers. See hip-00NN.

Bumps hanzoai/zen v1.0.0 -> v1.1.0 (additive API: TenantResolver, ctx-aware
Meter/Gate, Tenant.BillingOrg/Project, Usage.RequestID).
2026-07-13 15:39:38 -07:00
hanzo-dev 4bfede81a0 fix(code): disable zen5-ultra (403s), Fable tier falls through to zen5-pro; bump ai v1.806.12->v1.806.13
zen5-ultra routes to anthropic-claude-opus-4.8, which 403s on this account.
Drop the ultra backend chain from the Fable tier so it resolves to zen5-pro
(the working heavy-reasoning tier) instead. Picks up ai v1.806.13:
upstream-429 surfacing (typed apiError, status reaches client) + the
Anthropic thinking-budget -> upstream reasoning-vocabulary adapter
(glm max|high, openai low|med|high) so deep CC thinking reaches the deep
tier and invalid vocab no longer gets GLM-5.2 429'd. See hip-00NN.
2026-07-13 14:47:11 -07:00
hanzo-dev e474e65c4a chore(deps): bump hanzoai/money v0.2.0 -> v0.2.1 (honest 18-dp decimal floor) 2026-07-13 12:46:06 -07:00
antje cffc595a28 Merge remote-tracking branch 'origin/main'
# Conflicts:
#	go.mod
2026-07-13 12:34:25 -07:00
hanzo-dev 55e2b84d96 merge: git-native feature + de-gitea → main
# Conflicts:
#	go.mod
#	go.sum
2026-07-13 12:22:40 -07:00
hanzo-dev b1c93222ae chore: de-gitea — scrub branding/docs, keep legal+provider 2026-07-13 11:54:03 -07:00
antje 0445122adc Merge commit 'e896a505' 2026-07-13 11:19:05 -07:00
antje 7e78a12235 merge: restore force-push-clobbered lineage — CLI device login + gpu --studio-dir, atto-USD money, datastore debrand, deps
origin/main was rewritten (tracker/git work force-pushed over ~13 shipped
commits). This merge reunites both histories; go.mod resolved as the
highest-version union + go mod tidy.
2026-07-13 11:19:05 -07:00
antje 6cccfb79e7 refactor(money): delegate exact-money machinery to shared hanzoai/money + hanzoai/decimal
The big.Int 18-decimal fixed-point implementation lives ONCE in the shared
packages; cloud/clients/money becomes the thin policy layer that pins the
credit unit to 18-decimal USD. Finance/treasury/admin call sites unchanged
in behavior — money, ledger, sqlstore, finance, admin-core tests green.
2026-07-13 11:13:59 -07:00
hanzo-dev 47b9c38878 tracker: narrow Kind to {issue,pr,epic}; contract draws the three-plane boundary
Correct the taxonomy after confirming the real architecture: helpdesk tickets,
CMS content, ERP docs and knowledge entries are framework.DocType records (Hanzo
Base), and CRM Company/Contact/Opportunity is a bespoke relational store — a
DIFFERENT plane from the tracker. The tracker Issue is the engineering/project
work-item primitive, not the universal record.

- kinds narrowed to issue|pr|epic (drop deal/ticket/doc = domain records; drop
  task = the async plane, hanzoai/tasks). sources kept (legit work-item origins).
- contract.go rewritten to THREE orthogonal planes — tracker Issue (work items),
  framework.DocType (domain records), hanzoai/tasks (async execution) — and the
  thin one-directional seams (ExtRef links, Issue<->task), never embedding.
- Issue/IssueFilter/field docs + test seed aligned to the narrowed set.
2026-07-13 10:44:51 -07:00
hanzo-dev 370f161b2f tracker(contract): the Hanzo work-item contract — ONE Issue, every surface a filter
Pin the alignment law as in-repo design source of truth (doc-file, like the
git package doc and tasks/CONTRACT.md): there is ONE work-item primitive — the
tracker Issue — and no second issue table. Every product surface (hanzo.team
board, git Issues/PRs tabs, CRM pipeline, helpdesk queue, CMS task list, an
agent's work) is a FILTER over the one table, never a parallel store.

Documents: the four immutable discriminators (Kind/Source/Repo/ExtRef) and
their orthogonality; the surface->filter mapping; the two tenancy roots (IAM
project = physical file; tracker Project = KEY-N team within it; git repo bound
by the Repo discriminator, a third thing); and the tasks seam — tracking
(intent+state) is not execution (durable async = hanzoai/tasks), composing in
exactly two directions (Issue->enqueue task, task->patch Issue board state),
never inverted.
2026-07-13 10:38:58 -07:00
hanzo-dev 70e0138b20 tracker: ONE polymorphic issue primitive — git/CRM/helpdesk/CMS/team all compose
Extend the tracker Issue with four immutable discriminators (Kind, Source,
Repo, ExtRef) so a project task, a git issue, a pull request, an epic, a CRM
deal and a helpdesk ticket are ALL the same row. Every product surface becomes
a FILTER over this one table — never a second tracker:

  - hanzo.team board  = ListIssues(Filter{})            (or {Status})
  - git repo Issues    = Filter{Repo, Kind:"issue"}
  - git repo PRs       = Filter{Repo, Kind:"pr"}
  - CRM pipeline       = Filter{Kind:"deal"}
  - helpdesk queue     = Filter{Kind:"ticket"}

store.go: additive kind/source/repo/ext_ref columns (DEFAULTed so existing
rows read as native team issues; idempotent ALTER for pre-spine DBs) +
org_repo / org_kind indexes; ListIssues takes IssueFilter (status+kind+repo+
source, each an optional bound predicate).

tracker.go: closed kinds/sources sets, normKind/normSource, issueFilter() from
?status=&kind=&repo=&source=; create accepts + validates the discriminators;
billing category stays the constant "issue" row, decoupled from work-item Kind.

Discriminators are identity — set once at Create, immutable on Update — so a
row never migrates between surfaces. Tests: TestIssuePolymorphicSpine proves
the filter slices + defaults + cross-repo source view.
2026-07-13 10:32:00 -07:00
hanzo-dev 9085031c83 git(ui): native Hanzo Git web UI — repo list, browse, blob, commits
The embedded git host gains its browser surface (ui.go + ui_templates.go),
server-rendered in the ONE cloud binary — the native replacement for the
standalone Gitea web app, so git.hanzo.ai can retire it. Routes at /git/*:
org repo list, repo home (branches/HEAD/tree/clone/README), tree browse, file
view (binary-aware), commit log. Reads the SAME org-scoped store + go-git object
storage the API uses; every page scoped to the IAM-validated X-Org-Id with the
path-vs-identity guard (no cross-tenant read). html/template auto-escaping is the
XSS boundary. Build+vet clean; all clients/git tests green.
2026-07-13 10:01:43 -07:00
hanzo-dev f1ab5ae856 git(env): drop CLOUD_ prefix on embedded git SSH env — GIT_SSH_{HOST,ADDR,HOST_KEY}
The embedded Hanzo Git subsystem's env is now bare GIT_* (was CLOUD_GIT_*). Not
set in any prod deployment (code defaults), so the rename is behavior-neutral;
takes effect on next build. Cleaner + gitea-free naming.
2026-07-13 09:06:07 -07:00
hanzo-dev 301517fd16 fix(ci): bustable BuildKit cache ids — a poisoned module cache wedged the release
The release has been failing on:
  go: github.com/hanzoai/otel-collector@v0.144.10: unknown revision v0.144.10

That tag EXISTS on GitHub and resolves fine from a clean cache (verified:
go get github.com/hanzoai/otel-collector@v0.144.10 -> exit 0). The failure is
the BuildKit cache mount, not the pin: with no explicit id, BuildKit keys the
cache by target path alone, so a negative lookup recorded while the tag did not
yet exist is remembered FOREVER and there is no way to evict it.

Give every cache mount an explicit, bumpable id (cloud-gomod-v2 /
cloud-gobuild-v2). Bumping the suffix forces a cold cache. This unwedges the
release without touching the (correct) otel-collector pin, and gives us the
lever we were missing the next time a phantom pin poisons the cache.
2026-07-13 09:00:34 -07:00
hanzo-dev ecc8345e90 git: rebrand OUR embedded git = Hanzo Git; default provider = git (git.hanzo.ai)
Per directive: only OUR internal embedded git is rebranded (Hanzo Git), and the
default source provider is our own git.hanzo.ai ("git"). External providers
github/gitlab/bitbucket/gitea.com stay available as sources — gitea.com is fine
as an external source, we just never brand OUR host as Gitea.
2026-07-13 08:43:15 -07:00
hanzo-dev 3a8f4069b8 fix(edge): raise BodyLimit to 16 MiB — the 4 MiB default capped the context window
The context window is a BODY-SIZE fact, not only a model fact: a chat request
carries its whole prompt in the request body. zip/fiber defaults BodyLimit to
4 MiB (zip.go: 'if cfg.BodyLimit == 0 { cfg.BodyLimit = 4 << 20 }') and cloud
never set it — so a 1M-token prompt (~4.3 MB of JSON) was refused by fasthttp
BEFORE any handler ran, with the opaque 400 'Error when parsing request' that
reads like a malformed payload rather than a size cap.

Effect: the 1M-context routes were unreachable in practice. Measured on prod
(v1.799.10, direct to pod:8000, bypassing ingress+gateway):
  1.5 MB body -> 350,152 prompt tokens -> 200 (glm-5.2 correctly auto-rolled)
  2.0 MB body -> 466,148 prompt tokens -> 200
  4.0 MB+     -> 400 'Error when parsing request'
So the cascade logic was right all along; the transport silently capped it at
~900k tokens. 16 MiB gives a 1M-token prompt ~3.7x headroom. The edge is
authenticated + rate-limited and fasthttp streams, so this is not a memory
vector. Env GATEWAY_BODY_LIMIT, mirroring the GATEWAY_READ_BUFFER_SIZE
precedent (same class of bug one layer up: the 4 KiB header default).

Tests pin the invariant so it cannot silently regress to the framework default.
2026-07-13 08:26:57 -07:00
hanzo-dev 170b47eecb chore(deps): re-pin ai v1.806.12 + iam v1.31.25 (de-mattn) — mattn/go-sqlite3 now 0 in go.sum AND build graph 2026-07-13 00:28:26 -07:00
hanzo-dev 4fca0e1fc5 chore(deps): de-mattn — beego/v2 v2.4.2 + xorm v1.4.1 (sqlite v0.3.0 already) + drop the mattn/go-sqlite3 replace (go list -deps mattn=0) 2026-07-12 23:45:47 -07:00
antje e896a50578 merge: karma storefront loop — published Asset → listing image; product.created → ecom render; Campaign→product integrity
# Conflicts:
#	build.go
#	go.mod
#	go.sum
2026-07-12 23:33:27 -07:00
hanzo-dev f541e26b9b content: reverse storefront loop (product.created → ecom render) + Campaign→product integrity
Closes the Studio→CMS→Commerce loop the other direction. The forward edge
(storefront.go) publishes a rendered Asset onto the product image; this adds the
REVERSE — a new catalog product triggers its ecom render — plus the join-key
integrity gate. Decomplected over the COMMERCE event stream so commerce and content
never import each other.

Reverse loop (B):
- events: SubjectProductCreated/Updated ("commerce.product.*", on the COMMERCE
  stream) + PublishProductCreated/Updated on the existing events.Publisher (nil-safe
  no-op when NATS is absent, mirroring the order publishers).
- commerce product REST: publishProductEvents middleware fires the catalog event after
  a successful create/replace, reading the process Publisher off the gin context
  exactly like the order publishers — a total no-op when unwired.
- clients/catalogsync: in-process consumer subsystem on the COMMERCE stream mapping
  product.created → content.EnsureCatalogAsset (design == slug). Inert until
  CLOUD_COMMERCE_NATS_URL names the NATS carrying the events.
- content.EnsureCatalogAsset: product slug → ONE ecom Asset draft, idempotent (skip if
  a non-archived ecom asset already exists) and quiet (errNotConfigured / lane not
  installed = skip, never an error loop).

Integrity (C):
- Storefront gains ProductExists (reusing the same commerce S2S seam, X-Org-Id-pinned);
  enforceCatalogRefs before_save on Campaign.product fails closed on a dangling handle,
  validates only on set/change, and skips when commerce is unconfigured or erroring.
  Campaign-only on purpose: Asset.design is authored render-first (before the product
  exists), so gating it would reject the loop's first step.

Wired after content in subsystems.Wire() (frozen order test updated). Tests cover the
EnsureCatalogAsset idempotency/skip paths, the Campaign dangling-handle rejection, the
ProductExists S2S wire, the catalog event envelope + no-op, the REST middleware
classification, and the consumer dispatch ACK/NAK semantics.
2026-07-12 23:13:07 -07:00
antjeandGitHub 70bf435c19 refactor(datastore): cloud on hanzo-ds/go — kill datastore-go/v2 (#279)
swap the 3 remaining driver call sites (audit_mirror, commerce/db/
datastore, o11y/event_ingest) hanzoai/datastore-go/v2 -> hanzo-ds/go,
and take o11y v1.5.26 (fully driver-clean). cloud graph now has zero
hanzoai/datastore-* — the driver's one home is hanzo-ds/go.
2026-07-12 23:02:12 -07:00
hanzo-dev f213106edc deps: bump ai v1.806.9->v1.806.10 + fix phantom o11y v1.5.23->v1.5.25
- ai v1.806.10: gofumpt-clean CI (unblocks ai release pipeline) +
  deepseek-r1-distill context parity + swarm datastore standardization
  (hanzo-ds/go v1.0.1, datastore-go v2.47.2).
- o11y v1.5.23 was a PHANTOM pin (tag never published; graph jumps
  1.5.21 -> 1.5.25). Cloud only built via warm CI module cache; a fresh
  resolve failed 'unknown revision v1.5.23'. Repin to the real latest
  v1.5.25. Verified: go build ./cmd/cloud = exit 0.
2026-07-12 22:58:00 -07:00
antje 5103980096 feat(cli): hanzo login defaults to the RFC 8628 device flow — QR + link, approve from any device
The ONE interactive login: the CLI mints a device+user code from IAM
(hanzo.id /v1/iam/oauth/device, client hanzo-app — the first-party client
seeded with device_code), renders the verification link as text and a
terminal QR, and polls /v1/iam/oauth/token until approved. No password
ever touches the terminal; works headless (GPU boxes, ssh). Same endpoints
and client as hanzo-dev's live device flow, so one server-side config
serves both. --username/--password-stdin keep the password grant for
automation; --token unchanged.
2026-07-12 22:56:18 -07:00
antje 6c0c756906 fix(cli): gpu connect detects Apple Silicon — report chip + unified memory
detectGPUs only probed nvidia-smi, so a Metal/MPS box registered as
CPU-only in the fleet. On darwin/arm64 report the Apple chip as one GPU
with hw.memsize unified memory, MiB-formatted like nvidia-smi.
2026-07-12 22:51:45 -07:00
antje 0c9ebb650d feat(cli): hanzo gpu connect --studio-dir supervises the local render backend
The gpu-jobs claim loop renders on the LOCAL studio server (127.0.0.1:8188);
naming a checkout makes connect own that server's lifecycle too — launch from
the venv, health-probe /system_stats, one grace re-check, free the port and
relaunch on death or hang. Replaces the GB10 watchdog script and hand-rolled
systemd units: the hanzo CLI is the one way a BYO box joins the fleet, render
backend included. --daemon bakes the flag into hanzo-gpu.service.
2026-07-12 22:23:42 -07:00
antjeandGitHub 120ce15db4 chore(o11y): consume Datastore() accessor — o11y v1.5.23 (#276)
renames the store call site DatastoreDB() -> Datastore() (redundant DB
dropped) and bumps hanzoai/o11y v1.5.19 -> v1.5.23, which also completes
the clickhouse->datastore debrand indirects and pins a valid module zip
(v1.5.21/.22 zips were case-collision-invalid; .23 verified downloadable).
CGO_ENABLED=0 go build ./... green.
2026-07-12 22:04:40 -07:00
antje ab51d0cc83 feat(finance): exact 18-decimal (atto-USD) money — kill cents flooring
The double-entry ledger stored money as int64 cents, so every sub-cent AI
charge was floored to 0 (free AI) and every call skimmed the fractional
cent on rounding. Money is now EXACT to 18 decimals end to end.

- clients/money: new immutable big.Int Amount in atto-USD (1e-18) — the
  EVM/ERC-20 uint256 unit, so the off-chain ledger and an on-chain credit
  token are the SAME value with no boundary rounding. No float, no deps.
- ledger core + SQLite adapter: Posting/Entry/Balance int64 → money.Amount;
  amounts stored as TEXT (atto overflows SQLite INTEGER past ~$9.20) with an
  O(1) running-balance column and a one-time cents→atto ×1e16 rebuild
  migration (existing prefunds carry over exactly on first open). Anchor
  ComputeRoot hashes exact atto.
- finance wallet / types seam / Formance adapter / admin grant+deposit /
  metering / treasury threaded through. Treasury reserve-fund facade stays
  int64-cents (revenue-share is cents-granular).
- ai debit path (v1.806.6) emits exact decimal-USD; wireFinance parses it to
  atto. Balance READ stays coarse cents (gates a >0 threshold only). Grant
  response returns balanceAtto so a sub-cent debit is visible.

Pin ai v1.806.3 → v1.806.6 (exact nano-USD billing; datastore-go/v2 registers
driver 'datastore', no clash with cloud's hanzo-ds/go 'clickhouse').
2026-07-12 21:59:09 -07:00
hanzo-dev 65b33e2830 content: Storefront edge — published catalog Asset → storefront product image
A published content.Asset (kind in ecom/product/lifestyle, design==product slug)
materializes its S3 URL into the org's Hanzo Commerce store Listing headerImage —
the runtime display layer karma.style already reads (GET /v1/store/:store/listing).
Replaces the build-time studio->S3->library.json->sync-*->site pipeline with ONE
publish-edge side effect, decomplected exactly like the social Distributor.

- storefront.go: Storefront seam + commerce S2S impl (Bearer COMMERCE_SERVICE_TOKEN
  + X-Org-Id over clients/commerceinproc; store via GET /v1/store/current; upsert
  PUT /v1/store/:id/listing/:design). Fail-closed (not_configured) with no token.
- content.go: wire sf edge at Mount; fire StorefrontPublish on the published edge;
  TransitionResult.Storefront.
- Tenant-scoped by IAM org; assets referenced by S3 URL; no sync scripts.

Tests (CGO_ENABLED=0): gate, url resolution, transition side-effect, fail-closed,
and the real commerce S2S wire incl. X-Org-Id tenant pinning.
2026-07-12 21:53:29 -07:00
hanzo-dev 6fc65809a2 deps: iam v1.31.24 (tenancy: Org.Parent + recursive authz; signup/signin IP capture); datastore-go v2.47.0
datastore-go was pinned at v2.47.1 — a version the module proxy cannot resolve (the /v2 module path does not exist at that tag), so cloud did not build from a clean cache. v2.47.0 resolves.
2026-07-12 21:44:10 -07:00
z ccca97bc7d chore(deps): bump hanzoai/ai v1.806.8 -> v1.806.9 (>256k glm-5.2 auto-rolls to DS4-Pro) 2026-07-12 20:21:22 -07:00
hanzo-dev 69b260efd9 cloud: clickhouse->datastore debrand (zero clickhouse .go, datastore:// DSN, drop legacy CLICKHOUSE env) + pin o11y v1.5.21 (restore /v1/sentry, one datastore driver) 2026-07-12 20:08:39 -07:00
z eafb63cde5 chore(deps): bump hanzoai/ai v1.806.7 -> v1.806.8 (ONE-rule billing subject) 2026-07-12 20:03:12 -07:00
zandhanzo-dev f824fb01f9 refactor(billing): mirror ai ONE rule — billing subject is always the org
billingSubject(org,name) = org (lowercased), always. Deletes the personalBillingOrgs
and orgBillingOrgs allowlist parsers (PERSONAL_BILLING_ORGS / ORG_BILLING_ORGS). Keeps
the console billing view in lockstep with ai/object.BillingSubject so the view and the
gateway gate scope to the SAME subject. Tests prove the killed envs are ignored.

Needs go.mod bump github.com/hanzoai/ai -> v1.806.8 (run in a module-resolving env).
2026-07-12 20:01:25 -07:00
zeekay 087d91427c revert: otel-collector v0.144.10 — v0.144.13 forced mock v0.14.3 whose renamed API breaks o11y v1.5.17 (cascade pending) 2026-07-12 19:46:48 -07:00
zeekay bfaa70a57d deps: otel-collector v0.144.13 + hanzo-ds/mock v0.14.3 — chproto-free datastore stack 2026-07-12 19:44:41 -07:00
zeekay b49cf651a5 debrand: datastore-go v2.47.2 (0 clickhouse/CH identifiers) + chproto->dsproto 2026-07-12 19:43:38 -07:00
zeekay f3bb3107e0 deps: datastore-go v2.47.1 — cloud go.mod/go.sum now 0 clickhouse + 0 signoz
datastore-go's transport moved to hanzo-ds/native, so the ClickHouse/ch-go
indirect is pruned from cloud entirely. No cloud package imports a ClickHouse
or signoz module.
2026-07-12 19:31:48 -07:00
hanzo-dev 313c9055f7 deps: adopt otel-collector v0.144.10 (hanzo-ds datastore drivers) — drop signoz + -hanzo.0 replaces
- otel-collector v0.144.8 (+ replace => v0.144.8-hanzo.0) -> clean require v0.144.10
- dropped: replace SigNoz/signoz-otel-collector => hanzoai/signoz-otel-collector
  and the // indirect SigNoz/signoz-otel-collector require
- cloud now pulls hanzo-ds/{go,native,mock} transitively; 0 signoz in go.mod/go.sum;
  no cloud package imports a ClickHouse driver directly (build green)
Residual: one ClickHouse/ch-go // indirect graph line from a transitive dep's
go.mod (not compiled in) — clears when that dep drops it.
2026-07-12 19:19:54 -07:00
hanzo-dev fc7a04a1ed deps: bump hanzoai/ai v1.806.6 -> v1.806.7
Measured DO context windows + config-only resolver (the old table refused
deepseek-v4-pro at 131072) + oversized-prompt reroute to the 1M model.
This is what lifts hanzo code claude to the full 1M context.
2026-07-12 18:44:29 -07:00
hanzo-dev 3e52fdcdac debrand(o11y): drop signoz — query plane reads o11y_traces.distributed_o11y_index_v3
The o11y read plane was renamed signoz_* -> o11y_* (databases, tables, query
identifiers) at the source; the ClickHouse cutover migration
(o11y/deploy/clickhouse/migrations/0001_rename_signoz_to_o11y.sql) renames the
physical objects data-preservingly. Cloud's eval telemetry queried the OLD
physical name directly, so it would break post-cutover AND leaked the brand:

  eval/metrics.go: spanTable signoz_traces.distributed_signoz_index_v3
                        ->   o11y_traces.distributed_o11y_index_v3

Plus every prose/table-name reference across the in-repo o11y read plane and
commerce OTel bootstrap: signoz_traces/signoz_logs -> o11y_traces/o11y_logs,
SigNoz-fork provenance comments -> o11y/upstream. No source brand leaks remain.

DEPLOY: apply 0001_rename_signoz_to_o11y.sql during the collector cutover window
so prod ClickHouse objects match the new identifiers before this image serves.

Residual: go.mod keeps a REDIRECTED github.com/SigNoz/signoz-otel-collector key
(replace -> our fork; no SigNoz code fetched) — pulled transitively by
hanzoai/otel-collector's own go.mod; purge belongs to that fork's rename.
2026-07-12 17:43:34 -07:00
hanzo-dev a033c23591 feat(billing): adopt ai v1.806.6 — thread exact USD debit through the usage recorder
ai v1.806.6's UsageEvent replaced Cents(int64) with USD (exact decimal string,
atto-precise) so a sub-cent AI call bills precisely upstream. Adapt cloud's recorder:
- types.UsageInput gains USD (supersedes Cents when set).
- build.go SetUsageRecorder forwards u.USD.
- finance.RecordUsage rounds USD -> cents at the ledger boundary (usdToCents,
  round-half-up via math/big, no float). The local finance ledger is cents-denominated,
  so sub-cent floors to 0 exactly as the prior int64-Cents contract did — the atto path
  is commerce, not this store. Money-safety locked by TestUsdToCents.

Also carries ai v1.806.6's glm-5.2 1M context window (already in v1.806.5). Build ./...
green, finance tests pass.
2026-07-12 17:17:02 -07:00
hanzo-dev 1b75a97a77 fix(code): default hanzo code to glm-5.2, not the reserved word best
agent treats `best` (like opus/sonnet/haiku) as a reserved model
alias and rewrites it to a claude-* id. api.hanzo.ai does not serve those
claude-* ids (a request 403s — see anthropicWire), so `hanzo code claude`
on the default `best` died at session start. Default to glm-5.2: the
stable GLM-5.2-class 1M-ctx frontier, a concrete catalog id CC passes
through unchanged; the backend still cascades on rate-limit / down.
2026-07-12 17:05:02 -07:00
hanzo-dev 605ead5a4c fix(billing): bill the SUBJECT's wallet — a personal account gets a personal balance
The ledger already scoped correctly (org = which books, subject = which wallet in them), but both hooks passed the org for BOTH, collapsing every member onto the tenant's pool wallet. Since every signup lives in 'hanzo', a brand-new $0 account read HANZO's balance and sailed through the gate: we were enforcing our own wallet, not theirs. Now the gate reads, and usage debits, the subject ai already resolves — a person => their own wallet (personal plan), an org-owned application/service key => the org's account. That is the product: sign up as yourself with personal billing, then stand up an org whose users are your customers (Organization.Parent + AdministersOrg in hanzoai/iam). The invariant that must never break: the gate READ and the usage DEBIT key on the SAME wallet, or spend outruns the balance that admitted it — both use subject, keep them together. Also unpins o11y v1.5.16, whose tag was re-pointed upstream so its hash no longer matches go.sum (build fails verification); v1.5.17 is the unpoisoned tag.
2026-07-12 16:52:20 -07:00
hanzo-dev 72313f5f14 refactor(team): rip the last Huly refs — zero Huly anywhere
- tracker.go: prose 'Huly/Svelte' -> 'prior Svelte'
- model.json: Slack-mapping wire attrs hulyChannel/hulyChannelClass ->
  teamChannel/teamChannelClass (seed-model data, NOT Go-referenced; valid JSON).
The clients/team/*.go debrand already landed on main. This closes it out.

NOTE: teamChannel wire IDs are new-workspace seed data; the deployed front
(front:v0.7.391) still speaks hulyChannel for Slack channel mapping, so a lockstep
front rebuild is needed for Slack mapping on NEW workspaces — flagged, not silent.
2026-07-12 16:50:11 -07:00
hanzo-dev 649fcf87bd fix(billing): bill the SUBJECT's wallet — a personal account gets a personal balance
The ledger already scoped correctly (org = which books, subject = which wallet in them), but both hooks passed the org for BOTH, collapsing every member onto the tenant's pool wallet. Since every signup lives in 'hanzo', a brand-new $0 account read HANZO's balance and sailed through the gate: we were enforcing our own wallet, not theirs. Now the gate reads, and usage debits, the subject ai already resolves — a person => their own wallet (personal plan), an org-owned application/service key => the org's account. That is the product: sign up as yourself with personal billing, then stand up an org whose users are your customers (Organization.Parent + AdministersOrg in hanzoai/iam). The invariant that must never break: the gate READ and the usage DEBIT key on the SAME wallet, or spend outruns the balance that admitted it — both use subject, keep them together. Also unpins o11y v1.5.16, whose tag was re-pointed upstream so its hash no longer matches go.sum (build fails verification); v1.5.17 is the unpoisoned tag.
2026-07-12 16:48:12 -07:00
hanzo-dev c290cdaf45 chore(deps): bump ai v1.806.4 -> v1.806.5 (GLM-5.x 1M context window)
Deployed glm-5.2 was capped at 16384 tokens (the context_length_util.go
fallback) — long agent sessions 402'd. ai v1.806.5 sets glm-5.x to a
1M window with 131072 modern fallback (commit d248ff98).
2026-07-12 16:30:39 -07:00
hanzo-dev deeb3a7067 cli: pin CC tier slots to fixed zen5 aliases
The four agent tier slots (Haiku/Sonnet/Opus/Fable) are a fixed
zen5-* capability contract, decoupled from the resolved main model id.
Previously OPUS tracked ANTHROPIC_MODEL, coupling the tier to the main
choice; now OPUS=zen5-pro and FABLE=zen5-ultra are stable.

Decomplects which-tier from which-model: the tier->alias map is fixed
in the client; the alias->upstream map lives in models.yaml. Swap an
upstream (GLM -> Qwen 3.6 -> a future frontier) and every SDK/CLI/CC
integration keeps working unchanged. zen5-ultra carries its own backend
fallback chain (zen5-ultra -> zen5-pro -> zen5 -> zen5-flash) so the
Fable tier degrades gracefully if the premium upstream is unavailable.
2026-07-12 16:18:08 -07:00
hanzo-dev d32e9ffca0 fix(code): pin all agent model slots to zen5 aliases
agent's subagents, permission classifier, and /compact default to
built-in claude-* model ids (claude-haiku-*, claude-opus-*, claude-sonnet-*).
api.hanzo.ai does not serve those ids — a request 403s, which:
  - kills the classifier ('auto mode cannot determine safety of Bash')
  - kills every subagent (the 403 that dead-ended session cff690fc)
  - leaves /compact to run on a non-1M model -> 262145 > 262144 -> unresumable

anthropicWire now pins every CC tier slot to a served zen5 alias (the
Hanzo-standard mapping of CC tiers onto top OSS models resold via DO GenAI):
  ANTHROPIC_MODEL             = <model> (default best -> zen5/glm-5.2)
  ANTHROPIC_SMALL_FAST_MODEL  = zen5-flash  (DeepSeek-4 Flash, classifier)
  ANTHROPIC_DEFAULT_HAIKU     = zen5-flash
  ANTHROPIC_DEFAULT_SONNET    = zen5       (GLM-5.2)
  ANTHROPIC_DEFAULT_OPUS      = <model>
  ANTHROPIC_DEFAULT_FABLE     = zen5-pro  (DeepSeek-V4 Pro)

Live-proven: zen5/zen5-flash/zen5-pro/zen5-ultra all return 200 on the account;
only the raw claude-* ids 403. tests: TestAnthropicWirePinsZen5Tiers +
TestAnthropicWireExplicitModel lock the mapping and forbid raw claude-*.
2026-07-12 16:18:08 -07:00
hanzo-dev 7a547f0a4c refactor(team): drop Huly branding — no brand prefix, no vendor name
Debrand the team subsystem (our fork is Hanzo Team, not Huly):
- prose/comments: Huly -> Team / the platform
- hulyName() -> personName() (internal Person.name formatter)
- HULY_MODEL_VERSION -> MODEL_VERSION (no brand prefix at all, per the naming rule)
- TestHulyName -> TestPersonName

model.json WIRE class IDs (slack:class:SlackChannelMapping_hulyChannel, attrs
hulyChannel/hulyChannelClass) are deliberately UNTOUCHED: the deployed front
(ghcr.io/hanzoai/front:v0.7.391) speaks them, so renaming needs a lockstep front
rebuild — tracked separately, not a silent prod break.

Build + team tests green.
2026-07-12 16:18:08 -07:00
hanzo-dev 002e949447 feat(billing): honor ORG_BILLING_ORGS in console billing subject + bump ai
Bump hanzoai/ai to the ORG_BILLING_ORGS build (v1.806.3 + the allowlist), so the
gateway's BillingSubject promotes an allowlisted org (e.g. hanzo) to ONE shared
pool. Mirror the same scoped override in the console billing BFF (billingSubject)
so the console view scopes to the SAME subject the gate reads. Default empty =
zero behavior change.

Also refresh the stale hanzoai/o11y v1.5.16 go.mod checksum in go.sum (metadata
only; the zip/code hash was already correct — the readonly build passes), which
a moved tag had left inconsistent and which blocked every cloud build.
2026-07-12 16:18:08 -07:00
hanzo-dev b51616ce65 feat(cli): hanzo code defaults to the virtual best model
Change defaultCodeModel glm-5.2 -> best so `hanzo code claude` (no model arg)
auto-routes to the best-available coding model by quality and cascades on
rate-limit / out-of-credit / down (server-side, controllers/failover.go).
Explicit overrides still work (`hanzo code claude glm5.2`); the fuzzy resolver
validates `best` against /v1/models, where it is a real listed catalog entry.
2026-07-12 16:17:39 -07:00
zeekayandhanzo-dev 4fa6862602 datastore: cloud source → hanzoai/datastore-go/v2 (registers "datastore", not "clickhouse")
Completes the datastore standardization for cloud's own source: audit_mirror,
commerce/db, o11y/event_ingest now import github.com/hanzoai/datastore-go/v2
(the rebranded fork registering the UNIQUE sql driver name "datastore") instead
of the interim github.com/hanzo-ds/go (which registers "clickhouse" and collides
with upstream). Bumps ai v1.806.3 → v1.806.4 (its object/datastore.go likewise on
datastore-go/v2). cmd/cloud now links ZERO upstream ClickHouse/clickhouse-go/v2.
Remaining hanzo-ds/go is transitive via o11y/pkg/datastoremetrics — needs an o11y
release built off datastore-go/v2 (v1.5.16 tag currently resolves to the interim
hanzo-ds/go variant).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-12 11:21:51 -07:00
antjeandGitHub 5cc3b68444 fix(commerce): service-token S2S auth beats the IAM scope gate (completions 500 → clean 402/allow) (#273)
An in-process metering/billing dispatch (cloud → commerce via buildMeteringClient)
carries the verified COMMERCE_SERVICE_TOKEN *and* an X-Org-Id header (to select the
tenant namespace). The X-Org-Id makes IAMTokenRequired stamp iam_authenticated=true
with ZERO permissions (an S2S call carries no X-User-Permissions), so on an
Admin-masked billing route (/v1/billing/{balance,tier,usage}) TokenRequired's IAM
branch ran first, hasScope(0, Admin)=false → 403 "IAM principal lacks required
permission scope". The service token was never consulted; the balance read / usage
debit failed and the completions edge rendered that internal failure as a client 500.

Fix: in TokenRequired, check the service-token branch BEFORE the IAM branch. A request
bearing the KMS-sourced service token is the trusted platform S2S caller and must
authenticate as the service, never be subjected to the per-user IAM scope gate — even
when it also carries X-Org-Id. The two branches' logic is byte-identical; only the
order changed.

- Does NOT loosen the gate for external callers: a real IAM user never holds the
  service token, so they still hit the IAM branch and are masked-gated exactly as
  before (TestTokenRequired_UserIAMScopeGateUnchanged, IAMBranchEnforcesMasks).
- Prepaid gate stays fail-closed: funded → allowed, unfunded → clean 402
  insufficient_balance (TestInProcMeteringDispatch_ServiceTokenAuthPath drives the
  real chain over commerceinproc with finance NOT co-resident).
- The service token is KMS/env-sourced and never logged.

The 500-render itself lives in the hanzoai/ai dep (it serves /v1/chat/completions and
turns the internal balance/debit failure into a 500); once the cloud-side dispatch no
longer 403s, that failure no longer occurs.
2026-07-12 11:19:48 -07:00
antje 039d2a593d chore(deps): ai v1.806.3 (fast-500 nil-CruSession guard) + o11y v1.5.16 (datastore debrand)
ai v1.806.3: nil-CruSession guard on both session funnels + auth-before-autoroute
(routers/base.go; fixes fast 500 on unauthenticated session read).
o11y v1.5.16: datastore debrand (DatastoreDB()). luxfi pins unchanged.
2026-07-12 10:40:56 -07:00
antje f477163b73 Merge remote-tracking branch 'origin/chore/audit-datastore-env' into chore/datastore-roll 2026-07-12 10:37:08 -07:00
antje 65fc5439cd fix(finance): bill the org billing ACCOUNT (pool) for both read + debit, not the per-user subject
The ai gate read the account pool but debited the per-user wallet (read-subject != debit-subject),
so a funded account gated but never depleted. Key BOTH the balance read and the usage debit on the org
(its default-account pool wallet) in the wireFinance hook, so a funded account gates AND meters
consistently. Fund accounts, not users.
2026-07-12 10:18:38 -07:00
9d05b9d331 feat(cron): ONE durable platform cron on the tasks engine — retire every ticker and k8s CronJob (#268)
* feat(cron): ONE durable platform cron on the tasks engine — retire every ticker and k8s CronJob

clients/cron replaces the k8s CronJob fleet AND the commerce sweep ticker
with durable schedules on the shared embedded hanzoai/tasks engine
(v1.50.0 — the release whose sweeper actually fires on the sharded store).
The engine owns time; runs are durable workflows visible in the Tasks
console (/_/tasks, tasks.hanzo.ai) under the CRON_ORG shard (default
hanzo), namespace default, queue cloud-cron.

Entries are DATA in universe git: a ConfigMap labeled
cron.hanzo.ai/enabled="true" carries schedule + EITHER job.yaml (a
batchv1 Job manifest run to completion with Forbid concurrency, entry
label, TTL self-reap) OR poke.json ({url,method,bearerEnv,timeout} —
bearer resolved from THIS process's KMS-synced env, never stored).
A reconcile workflow — itself a durable schedule (*/5) plus one boot
pass — diffs ConfigMaps against cron-prefixed schedules: upserts are
drift-gated (rewriting resets the fire anchor), deletes never touch
foreign ids. Fire-time activities re-read their ConfigMap, so payload
edits apply next tick.

The commerce auto-recharge sweeper (clients/commerce/sweep.go) is
deleted; its 15m POST /v1/billing/auto-recharge/run-all becomes the
cron-billing-autorecharge poke entry — same request, same token, one
cron system.

Tests (-race): TestPokeEndToEnd + TestJobEndToEnd drive the FULL durable
path against a real embedded engine (org-shard schedule → trigger →
loopback worker → activity → completed run in the org shard — the exact
console-visibility + dispatch-routing the design stands on);
TestReconcileConverges pins upsert/delete/foreign-id/anchor semantics;
TestParseEntry pins the ConfigMap contract. commerce + subsystems suites
green.


* feat(tasks): UI at /tasks (no /_/) + org/project/user-native gate (tasks v1.51.0)

The Tasks console moves to console.hanzo.ai/tasks + tasks.hanzo.ai/tasks —
the /_/ prefix is gone. Subsystem routes mount before the console SPA
catch-all, so /tasks wins the path and every other console route keeps the
SPA fallback. The gate now threads the FULL validated identity — org,
project (X-Project-Id, minted by identity middleware from the validated
project claim), user, email — into the engine via tasks v1.51.0's
WithIdentity; convention: project ↔ tasks namespace inside the org shard.
ZAP plane unchanged (loopback ungated + IAM-gated cluster listener).

The embedded SPA bundle is rebuilt with base /tasks/ in a follow-up sync
commit (hanzoai/admin builds it; clients/tasks/ui/dist is the embed).


* ci: retrigger (Actions dropped the push event)

* chore(tasks/ui): sync SPA rebuilt with base /tasks/ (hanzoai/admin@448b189)


---------

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-12 09:53:06 -07:00
antje 433ad0c4b6 chore(audit): dual-read CLOUD_AUDIT_DATASTORE_* with legacy CLOUD_AUDIT_CLICKHOUSE_* fallback
Prefer the datastore-named env keys, fall back to the clickhouse-named legacy
keys so a rollout mid-flight (new binary / old manifest, or vice versa) never
drops the audit OLAP mirror connection. Code-only; no roll.
2026-07-12 09:48:18 -07:00
antje c8a2cb5d3d fix(deps): ai v1.805.11 (datastore fork) — kill clickhouse double-registration; native commerce read + per-subject finance deposit
ai v1.805.10 pulled upstream ClickHouse/clickhouse-go via ai/object, which double-registered
the clickhouse driver against cloud's hanzo-ds/go fork → boot panic (CI smoke caught it). ai v1.805.11
merges the clickhouse→hanzo-ds purge, so the upstream driver is no longer imported (verified: 0 in the
build, binary boots clean). Also: commerce.BalanceCents (native in-proc balance read — backfill + cockpit
read real balances, no commerce.inproc) and POST /v1/admin/finance/deposit (fund a SPECIFIC wallet:
hanzo/z, not just the pool).
2026-07-12 09:47:50 -07:00
hanzo-dev b55fe5fee4 chore(deps): bump hanzoai/ai v1.805.10 → v1.805.13 (Anthropic /v1/messages tools translation) 2026-07-12 09:28:30 -07:00
hanzo-dev e3efd3c17d merge: hanzo code CLI launcher (claude/codex/dev on any Hanzo cloud model) 2026-07-12 09:25:20 -07:00
hanzo-dev d8ae08da5c merge: LOW-1 — ml/provisioning balance Gate keys on home org (principal.Payer), matching the debit (Red fast-follow) 2026-07-12 09:08:47 -07:00
hanzo-dev f6905b18c8 fix(billing): ml + provisioning pre-create GATE keys on home org (principal.Payer), matching the paired debit
LOW-1 fast-follow (Red). In these two create-handlers the DEBIT correctly keyed on the
HOME org (principal.Payer(c)) but the pre-create balance GATE still keyed on the
EFFECTIVE org — the two swapped only the meter, not the gate (their Gate signature had
gained a projectValidated arg, so the class swap missed them). Effect: a SuperAdmin
masquerading into a victim org was balance-gated on the VICTIM's funds while the debit
landed on admin's ledger (money already correct; an availability/consistency nit).

Fix: swap the Gate org arg -> principal.Payer(c) in both handlers, restoring the
invariant the other ~8 resource meters hold — gate + debit BOTH key on home; data scope
(namespace/project) stays effective.

Test: TestResourceMeter_GateKeysOnPayerForMasqueradingAdmin resolves principal.Payer(c)
from a masquerade ctx (X-User-Owner=admin, X-Org-Id=victim -> admin) and asserts the
recCommerce balance check keyed on admin (home), never victim. go build ./...=0 (links),
gofmt clean, root ResourceMeter suite + clients/ml green (provisioning store tests are the
pre-existing CLOUD_KMS_MASTER_KEY_REF env gate, orthogonal).
2026-07-12 09:07:58 -07:00
zeekayandhanzo-dev fc9fdd8203 git: re-integrate SSH + ZAP + client-less REST push onto the generics framework
Ports the prior Git-over-SSH + ZAP transport + client-less REST push work
(commit 36c52d1, written against the old *svc-receiver service) onto the
current cloud.Service[state] generics framework on main. A port, not a
rewrite: the DRY architecture is preserved — ONE control-plane core, ONE
git pack path, three thin transports (REST, ZAP, SSH) over them.

Handler pattern adapted: every `*svc` method became a free function taking
`s *cloud.Service[state]` (matching git.go's existing create/list/get/del),
`cloud.TenantStore` → `cloud.NewOrgStore`, methods → `cloud.Handle(s, fn)`
route registration, `s.log`→`s.Log`, `s.stores/storage/keys/ssh`→`s.State.*`,
`tenant(c)`→`org(c)` (principal.Org). Package-scoped helpers (storeFor,
provision, recordUsage, refState, cloneURL, sshURL, firePushBuilds, session)
are the current framework's free-function forms.

New files:
- core.go   coreCreate/List/Get/Delete/Usage — the ONE transport-agnostic
            control-plane impl; REST + ZAP both call it.
- pack.go   serve{Upload,Receive}Pack + ssh{Upload,Receive}Pack — the ONE git
            pack code path both smart-HTTP and SSH drive (io.Reader/Writer,
            transport-agnostic); readerOnly guards the SSH channel write side.
- ssh.go    golang.org/x/crypto/ssh server. Host key from CLOUD_GIT_SSH_HOST_KEY
            (KMS env) or on-disk ed25519 generated+persisted 0600.
            PublicKeyCallback resolves key→(org,user) by SHA256 fingerprint,
            fail CLOSED. Session accepts only git-upload-pack/git-receive-pack,
            enforces path-org == key-org. Listen CLOUD_GIT_SSH_ADDR (:2222).
- keystore.go  fingerprint-indexed global SSH public-key registry (public keys
               only — nothing to hash).
- keys.go   POST/GET/DELETE /v1/git/keys.
- push.go   POST /v1/git/repos/:name/push — build tree+commit from posted
            utf-8/base64 files, advance ref, create-on-first-push (composes the
            ONE provision), fire the SAME firePushBuilds hook receive-pack fires,
            return commit + cloneUrl + sshUrl.
- zap.go    git/zap/{createRepo,listRepos,getRepo,deleteRepo,usage} envelope
            adapters over the SAME core funcs, on the shared /zap plane. No
            second ZAP server, no gRPC.

Modified:
- git.go       repoView/toView gain sshUrl; state holds sshHost/ssh/keys; Mount
               opens the keystore + starts the SSH listener; routes() wires
               push+keys+ZAP; Shutdown stops SSH + closes the keystore. REST
               control-plane handlers are now thin adapters over core.go.
- smart_http.go  uploadPack/receivePack drive the shared pack.go path via
                 resolvePackRepo; firePushBuilds + session helpers retained.

Tests (go test ./clients/git/... — 16 pass): SSH key register accept/reject +
cross-org reject + end-to-end SSH clone+push over an in-process listener; a
zapface WS round-trip proving the ZAP path hits the SAME core as REST; REST
push create/update/build-hook, first-push provisioning, validation, and
cross-org isolation. tenant_isolation_test + git_test bind the SSH listener to
an ephemeral loopback port so tests never collide on :2222.

CGO_ENABLED=0 GOWORK=off go test ./clients/git/... passes; go build clean;
gofmt clean.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-12 09:05:56 -07:00
antje 63efcc84ca feat(finance): route edge meter + admin grant onto the finance ledger, + commerce→finance backfill
metering.Client fetchAvailable/Record now resolve finance.Current() first (micros→cents
ceil so metered_ai's AmountMicros debit is never dropped), commerce HTTP only when finance is
not co-resident. admin ApplyGrant credits the finance wallet (fixes the broken commerce.inproc
grant path). New DepositInput.Ref makes deposits idempotent; finance.MigrateOrg + SuperAdmin
POST /v1/admin/finance/backfill?org= carry each org's commerce balance into its finance wallet
exactly once at cutover. All money — balance, usage, deposit — now flows through the ONE per-org
double-entry ledger.

Verified: build + go vet clean; finance/metering/admin/core tests pass (micros fold, ref
idempotency, backfill exactly-once, zero-HTTP-when-co-resident all locked by tests).
2026-07-12 09:02:36 -07:00
antje afe5ce9fc9 feat(finance): per-org double-entry prepaid wallet ledger (finance.Client) + ai native hooks
New clients/finance: ONE lightweight SQLite file per customer (orgs/<org>/finance.db),
double-entry wallet on the treasury/ledger core — deposit=funding→wallet, usage=wallet→revenue,
balanced within the org file, idempotent. Orthogonal money interface types.FinanceClient
(finance.Client, mirrors commerce.Client); NOT bolted onto the Deps bag and NO pick/RPC/disabled
cruft — a narrow published seam (finance.Publish/Current) every money consumer resolves.

BuildDeps.wireFinance constructs+publishes it and installs the ai router's typed
BalanceReader/UsageRecorder hooks (ai v1.805.10) so the prepaid gate reads balance + debits usage
by a DIRECT in-proc call, no HTTP. Rob-Pike small interfaces between systems, not a god-struct.

Remaining before cutover: edge meter + admin grant onto finance.Current(), backfill commerce
balances into <org>:wallet, then build/deploy/prefund/drop BALANCE_EXEMPT_USERS.
2026-07-12 09:01:38 -07:00
antjeandGitHub 3080a2fb07 chore(deps): pin all hanzoai/luxfi deps to clean v1 OSS tags (#269)
Drop pseudo-versions and +incompatible for our own modules; everything now
resolves to a published v1 semver tag (v1 only, per policy):

  goa            v0.0.0-pseudo        -> v1.0.0   (first tag)
  sign           v0.0.0-pseudo        -> v1.0.0   (v1 path; 36 bogus v2 tags dropped)
  captable       v0.0.0-pseudo        -> v1.0.0   (first tag)
  pubsub-go      v1.0.1-0.pseudo      -> v1.53.0  (existing clean tag; HEAD==v1.53.0)
  gochimp3       v0.0.0-pseudo        -> v1.0.0   (module path fixed: Elandiro -> hanzoai)
  goauthorizenet v0.0.0-pseudo        -> v1.0.0   (go.mod added)
  sendgrid-go    v3.4.2-...+incompat  -> v1.3.0   (go.mod added; v1 path)
  luxfi/keys     v1.2.2 (force-moved) -> v1.4.0   (clean current tag)

CGO_ENABLED=0 go build ./... green.
2026-07-12 00:58:01 -07:00
775cf27ce9 fix(release): race-safe version assignment — unjam the cloud release lane (#271)
Root cause of the jammed lane (failed releases + phantom tags like v1.786.221):
the push step published the racy v<X.Y.Z> tag BEFORE it was confirmed free, and
the tag step hard-failed when a concurrent release had claimed that number
(computed 220, already tagged → 'rejected, already exists'). Result: a pushed
image with no matching git tag, mutable :vX clobbering, and dead releases.

Fix — decouple the immutable artifact from the versioned release:
- Push step publishes ONLY the unique sha-<sha7> (+ floating latest); never the
  racy version tag.
- Tag step assigns the next FREE v<X.Y.Z> ATOMICALLY: recompute fresh, retag the
  proven sha-image → :vX/:X.Y.Z/:X.Y via imagetools (metadata-only, byte-identical),
  git-tag it, and RETRY on collision (the git-tag push is the serialization point —
  a loser recomputes). Concurrent releases each grab a distinct free number.
- Compute-step collision is now a non-fatal hint (Tag step owns assignment).
- notify-universe rolls the Tag step's FINAL version, not the compute guess.

Preserves the invariant: git tag vX ⇔ image :vX pushed + smoke-passed. Logic
unit-tested locally (free-find + collision-skip). YAML valid.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-11 23:58:40 -07:00
hanzo-dev afbf01d13f merge: admin-org predicate (owner==admin) + home-org billing (debit/gate on X-User-Owner, data scope on X-Org-Id) — admin masquerade bills the admin ledger 2026-07-11 23:41:30 -07:00
hanzo-dev f42309dcd1 billing: debit+gate on HOME org (X-User-Owner); embedded-commerce sudo = owner==admin
THE billing fix (B): split 'who pays' (HOME org, X-User-Owner) from 'whose data'
(EFFECTIVE org, X-Org-Id), which the old code conflated onto one org. A platform
SuperAdmin masquerading into another org now spends from the admin ledger; data
scope stays on the acted-on org.

- clients/principal: Owner(c) (X-User-Owner, bounded+cloned), BillingOrg(c) (home w/
  effective fallback, Validated-gated), Payer(c) (bare-string for the in-handler meters).
- middleware_identity: mint X-User-Owner=home for every validated principal (before the
  admin org-switch) + strip it on ingress (authorityHeaders) so a client can't forge who pays.
- middleware_billing: identityFromCtx keys User+Org (balance check AND debit) on BillingOrg.
- 11 resource-meter live sites (visor/s3/security/platform-run/functions/ml/provisioning/
  bots/tracker/automations): Gate+Meter+MeterUsage bill principal.Payer(c) (home); Org stays
  effective for the namespace. Background/reconcile paths (a.Org/r.Org/b.Org, meterRun) and
  the studio_render 'org' param bill the RESOURCE's own org — FLAGGED (see Red handoff).
- metered_ai + types: ChatRequest/EmbedRequest gain BillingOrg; meteredAI gate+record key on
  billedOrg(BillingOrg,Org); threaded principal.Payer(c) through the code engine (Synthesize/
  Embed) so internal RAG bills home too. Inner AI call keeps req.Org (data scope).

Part A (embedded commerce, clients/commerce mirror of the commerce repo): drop the spoofable
IsSuperAdmin boolean; auth.IAMClaims.IsSuperAdmin() gates homeOrg()=="admin" (HomeOrg from
X-User-Owner ?: Owner); iammiddleware reads X-User-Owner->HomeOrg (Owner stays effective);
EdgeAuth strips+mints X-User-Owner before the ?org override, stops minting X-User-IsSuperAdmin;
all .SuperAdmin() call sites -> .IsSuperAdmin(). Org-scoped IsAdmin untouched.

Tests (green): TestIdentityFromCtx_AdminMasqueradeBillsHomeOrg (owner=admin+effective=victim ->
debit on admin, data on victim), TestBilledOrg, TestMeteredAI_AdminMasqueradeBillsHomeOrg
(end-to-end debit user=admin), vendored TestIAMClaims_IsSuperAdmin masquerade+anti-escalation,
EdgeAuth strips forged X-User-Owner. go build ./...=0, go vet=0.

Rollout: pre-gateway (no X-User-Owner) billing falls back to effective (home==effective for a
normal caller; masquerade fails CLOSED). Deploy gateway (mints X-User-Owner) first.
2026-07-11 23:36:25 -07:00
hanzo-dev dfda1eced2 cli(code): fail loudly on unresolved models; declare the Hanzo provider for codex
Three defects found by testing a real completion instead of --version:
  - an unreachable catalog silently passed the typed id straight through, so an
    agent booted on a model that does not exist and failed opaquely mid-session;
    resolution is now strict.
  - a stale ANTHROPIC_API_KEY in the shell outranks ANTHROPIC_AUTH_TOKEN and
    silently wins; it is cleared for the claude wire.
  - codex ignores OPENAI_BASE_URL and talks to chatgpt.com unless a provider is
    declared; declare Hanzo and select it (wire_api=responses, per upstream).
2026-07-11 23:34:33 -07:00
hanzo-dev 9276d9ba2b docs(identity): last 'global admin' prose -> SuperAdmin (zero repo-wide) 2026-07-11 23:22:37 -07:00
hanzo-dev 4b45286ff9 refactor(identity): ONE fact per predicate — SuperAdmin = admin-org membership, OrgAdmin = own-org admin
Cloud was the odd one out: it minted SuperAdmin from TWO signals
(claims.IsAdmin && owner == adminOrg) while IAM's canonical User.IsSuperAdmin() is
just user.Owner == conf.AdminOrg, and IsOrgAdmin folded SuperAdmin into itself. Two
predicates that each meant one-and-a-half things.

Decomplected — two orthogonal facts, one predicate each:
  IsSuperAdmin = owner == adminOrg          (platform sudo; the SAME equality IAM uses)
  IsOrgAdmin   = the IAM isAdmin bit         (admin of one's OWN org; implies nothing about super)
A gate admitting either now writes IsSuperAdmin(c) || IsOrgAdmin(c) explicitly, so the
superset is visible AT the gate, not hidden inside a predicate. GuardScoped already did.

The admin org holds ONLY SuperAdmins (provisioned in, never promoted), so membership IS
the fact — the isAdmin bit is the orthogonal org scope, never a super gate. The KMS
machine-principal exclusion STAYS (a real guard: an admin-org machine token must never
be super). Test renamed + strengthened to lock the one predicate. Build ./... clean,
identity/admin/principal suites all green, KMS-machine exclusion tests pass.
2026-07-11 23:21:17 -07:00
d613345067 security: golang-jwt/jwt v3 → v4 (no-patch high; v3 line abandoned) (#270)
The 4 commerce auth/token files imported the vulnerable golang-jwt/jwt v3.2.2
(dependabot high, no v3 patch — fix is off-v3). v4.5.2 (already present) keeps
StandardClaims/Valid()/int64 dates → API-compatible, zero code ripple vs the
v5 RegisteredClaims rewrite. Dropped the orphan v3 require. Full build + commerce
auth tests green. (dgrijalva/jwt-go remains transitive-only = unreachable.)

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-11 23:19:39 -07:00
antjeandGitHub 4121895cc4 chore(deps): bump embedded iam to v1.31.22 (#266)
Advances the in-process IAM embed (clients/iam, HIP-0106) from the
v1.31.20 pre-release pin (31a798fb, #117) to the published v1.31.22 tag
(387c4a60). Brings the project claim mint + default-project seed (#120)
into cloud's embedded IAM so console admin surfaces match standalone
hanzo.id, already on v1.31.22.

API-compatible: iamserver.InitEmbed and object.Project CRUD unchanged
(iam go.mod hash identical across versions), no clients/iam adaptation.
CGO_ENABLED=0 go build ./... green; clients/iam + clients/platform tests pass.
2026-07-11 22:51:42 -07:00
4957073775 cloud: bump zip v1.6.0 + licensing v0.1.4 — off the deleted App.Mount, one-way surface (#267)
zip v1.6.0 deleted the deprecated/redundant surface (App.Mount/Route/ModuleFn/
UseFiber). cloud is off App.Mount (#257); licensing v0.1.4 migrated its one
App.Mount call. Build 0, framework tests green.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-11 22:51:03 -07:00
hanzo-dev 56db31b79f cli: hanzo code — launch claude/codex/dev on any Hanzo cloud model
One way to start any coding agent on any Hanzo model: endpoint, credential and
model are injected, so nothing is exported by hand. Two wires cover all three
agents (claude speaks Anthropic; codex and @hanzo/dev, a codex fork, speak
OpenAI), model ids resolve fuzzily (glm5.2 -> glm-5.2), and agents run full-auto
unless --safe. Config gains apiKey; the key the rest of the toolchain already
keeps in ~/.hanzo/config.json is read (never written) so one key serves every tool.
2026-07-11 22:36:34 -07:00
zandantje b1f3da2ac9 chore(datastore): purge clickhouse-go/datastore-go → hanzo-ds + debrand (Group A, v3)
Rebased on current origin/main (37a438a3, +4: #262/#258/#261/prepaid-wiring).
- ai v1.805.9 (= v1.805.7 hardened prepaid gate + purge) — NOT the money-regressing v1.805.8
- o11y v1.5.15, otel-collector v0.144.8-hanzo.0
- datastore clients → hanzo-ds/go; ClickhouseDB()→DatastoreDB(); clickhouse→datastore rip
- go.mod clickhouse-free; go list -deps ./cmd/cloud clickhouse=0; 0 BALANCE_EXEMPT in linked ai
- boots clean fail-closed (single sql.Register); luxfi pins as live; wire/DSN/env contracts preserved
2026-07-11 22:25:32 -07:00
d5d8e74099 docs(projects,tracker): mark the two Project structs as deliberately distinct (#264)
WS4 audit flagged projects.Project and tracker.Project as duplicate types.
They are not: projects.Project is the Slug-keyed deployable site (one global
projects.db, org column); tracker.Project is a KEY-prefixed Linear-style issue
team living in a per-(org,project) tracker.db WITHIN one of those sites. Only
the universal storage-row skeleton (id/org/name/description/timestamps) is
shared; the natural keys carry different semantics (DNS label vs issue-ID
prefix) and the field sets are not subsets. Record the distinction on each type
so the finding is not re-litigated. Comment-only; no API or behavior change.

Co-authored-by: Hanzo <dev@hanzo.ai>
2026-07-11 22:13:06 -07:00
37a438a33c feat(billing): thread validated-project bool through ResourceMeter.Gate (#262)
principal.ValidatedProject(c) now flows through ResourceMeter.Gate into
metering.AuthInput.ProjectValidated, so resource-creation caps harden
consistently with the edge BillingGate. Removes the hardcoded
ProjectValidated:false at resource_billing.go.

- Gate signature gains projectValidated bool (adjacent to project, mirroring
  principal.ValidatedProject's return + AuthInput's field order).
- Every *zip.Ctx caller passes principal.ValidatedProject(c); the three
  no-principal/client-body paths (metered_ai LLM decorator, background agent
  run, content studio in.Project) pass false — unvalidated stays soft, never
  fabricated true.
- Meter/Record path unchanged: Usage carries no ProjectValidated; cap
  enforcement is Gate-only, so threading it there would be dead code.

Stays SOFT in prod today: ValidatedProject is true only for a validated NAMED
project, and IAM seeds none yet, so no org has a project claim. No behavior
change now; named-project caps auto-harden per-org as IAM seeds them.

Co-authored-by: Hanzo <dev@hanzo.ai>
2026-07-11 21:44:51 -07:00
220cd8bcf8 feat(platform): collapse buildType surface to pack|dockerfile (one way) (#261)
The build path (buildFrontendCmd) already chose its BuildKit frontend on
dockerfile presence alone: an explicit Dockerfile → dockerfile.v0, otherwise
hanzoai/pack via gateway.v0. buildType never gated the build — it was stored
metadata whose closed set still advertised the retired nixpacks/buildpacks/
static strategies and defaulted git apps to nixpacks.

Collapse it to the one true surface:
- closed set is {pack, dockerfile}; git source defaults to pack, not nixpacks
- image source always yields buildType image (no build), forced by source, so a
  client can no longer stamp a git strategy on a prebuilt-image app
- Goa contract (design.go + generated openapi3.json/yaml) enum, description and
  examples track the same {pack, dockerfile, image} set

Adds TestBuildTypeSurface pinning the default (pack), the dockerfile escape
hatch, rejection of every retired strategy, and image-source forcing.

Co-authored-by: Hanzo <dev@hanzo.ai>
2026-07-11 21:44:48 -07:00
dcdd317cc8 refactor(identity): collapse hand-rolled org/project reads onto principal (#258)
Six identity reads re-derived org/project inline instead of going through
principal — the ONE accessor. Route them all through it so the trust
decision lives in exactly one place and cannot drift.

- analytics tenant(): delegate to principal.Org — fixes a retained-buffer
  bug (org keyed the cloud_usage ledger past request end as a zero-copy
  fasthttp view; principal.Org clones). Gate unchanged.
- git/security projectScope(): read via principal.Project; absent header
  and literal "default" both map to the un-suffixed default scope via
  principal.IsDefaultProject, keeping today's (org,project) key shape.
- admin core.ResolveScope / core.GuardScoped / me / core.EmitAudit: read
  org via principal.Org (validated principal + org), composed with the new
  principal.IsOrgAdmin predicate. Admin-org bucket kept local.

Co-authored-by: Hanzo <dev@hanzo.ai>
2026-07-11 21:44:08 -07:00
hanzo-dev f6afc51056 feat(billing): prepaid AI gate — wire ai v1.805.7 to in-process commerce, no exempt
Pin hanzoai/ai v1.805.7 (exempt concept removed: no BALANCE_EXEMPT_USERS/KEYS, no
fail-open; balance-unverifiable now DENIES). BuildDeps sets aiobject.CommerceTransport
= commerceinproc.Transport() and self-configures the ai module's commerceEndpoint to the
in-process placeholder when commerce is co-resident, so the embedded ai router's balance
read + usage debit hit the raw commerce gin (service-token, no socket) — the SAME one
ledger the metering client bills — not the customer proxy that 401s a service token.
Every external inference is now prepaid-gated with zero exempt principals.

hanzo/z was a normal customer, never admin; exempting it leaked money. Closed.
2026-07-11 21:37:00 -07:00
be0f0f002b feat(platform): delegate project lifecycle to IAM (one source of truth) (#260)
Projects are now owned by Hanzo IAM (hanzo.id) as the org-scoped
(owner,name) resource. Platform REFERENCES that store instead of owning
one: apps still live under a project, but create/list/get/delete/exists
of the bare project delegate to IAM in-process.

- New ProjectStore port (projects.go) with an in-process iamProjects
  adapter over github.com/hanzoai/iam/object — no HTTP hop, and IAM's
  canonical *object.Project is used verbatim (no platform-local clone).
- Delete platform's project ownership: the Project struct, the
  platform_projects table, and Create/Get/GetByID/List/Update/Delete
  project store methods. DeleteProject is replaced by DeleteProjectApps
  (cascade of the app tree only; the project row is IAM's).
- Apps key on the IAM project NAME (platform_apps.project_id holds it);
  the internal proj_ id indirection is gone, so reconcile/preview/domains
  use app.ProjectID directly and drop their project lookups.
- run.go get-or-creates the default project via the ProjectStore, using
  principal.DefaultProject as the single source of truth for "default".
- tenant() gates on principal.Validated(c) (canonical), not a raw
  c.User()=="" whitespace-blind check.
- Tests: fake ProjectStore + TestProjectLifecycleDelegatesToIAM proving
  create/delete route through IAM and delete cascades platform's apps.

Co-authored-by: Hanzo <dev@hanzo.ai>
2026-07-11 21:01:24 -07:00
36405143c1 feat(identity): bind X-Project-Id from the validated project claim; harden per-project caps (#259)
SanitizeIdentity now mints X-Project-Id from the validated JWT `project` claim
(idClaims.mintedProject), exactly like X-Org-Id from `owner` — the raw client
X-Project-Id is never a source. Still checked non-foreign to the effective org, so
a global admin viewing another org drops their own-org project. Mirrors the edge
(iamauth.Claims.MintedProject), so the in-binary path binds the same header.

principal.ValidatedProject flips CONDITIONALLY: (project, true) only for a
validated, NON-default project claim — the signal a project-scoped spend cap uses
to HARD-enforce. The default project stays soft (IAM does not seed default
projects yet; a blanket true would wrongly hard-402 every org). Named project caps
auto-harden one org at a time as projects are seeded.

Tests: claim-sourced project binding + forged/override client X-Project-Id ignored
+ cross-org claim refused on admin org-switch + X-Org-Id forgery still blocked;
ValidatedProject claim-backed→(project,true), absent/default→soft, unvalidated→soft.

Follow-up (WS3, out of scope): resource_billing.go Gate hardcodes
ProjectValidated:false — resource-creation caps stay soft until it threads
principal.ValidatedProject.

Co-authored-by: Hanzo <dev@hanzo.ai>
2026-07-11 21:00:51 -07:00
hanzo-dev 45a68002d5 refactor(auth): rename GlobalAdmin -> SuperAdmin (SOC2/FedRAMP term)
Eliminate "global admin" terminology across the cloud repo in favor of the
standard SuperAdmin term. Pure naming refactor; behavior preserved.

Identifiers (commerce auth + middleware + root):
- (*auth.IAMClaims).GlobalAdmin() -> SuperAdmin() + all call sites
- IAMClaims.IsGlobalAdmin field -> IsSuperAdmin (JSON tag isGlobalAdmin
  -> isSuperAdmin; SuperAdmin() still honors owner=="admin", the canonical
  predicate, so behavior is preserved)
- edgeauth isGlobalAdmin() helper -> isSuperAdmin(); requireGlobalAdmin ->
  requireSuperAdmin; test-local globalAdmin vars -> superAdmin
- const HeaderUserIsGlobalAdmin -> HeaderUserIsSuperAdmin, value
  "X-User-IsGlobalAdmin" -> "X-User-IsSuperAdmin" (commerce-internal header:
  minted+stripped in edgeauth, read in iammiddleware; no external sender)
- auth/globaladmin_test.go -> auth/superadmin_test.go

clients/admin: the deprecated isGlobalAdmin JSON alias (sibling of the
canonical isSuperAdmin, same value) is REMOVED rather than renamed — a rename
would collide with the existing IsSuperAdmin field, and the alias was a
transitional back-compat scaffold for this very migration. Tautological
alias-equality assertions dropped; isSuperAdmin checks retained.

Prose: "global admin" / "global-admin" / "GLOBAL-ADMIN" / "GlobalAdmin" in
comments and docs (LLM.md, k8s manifests) rewritten to SuperAdmin, case-aware.

Left untouched: cloud gateway header X-User-IsAdmin; principal.IsSuperAdmin /
IsOrgAdmin; svcorg's DefaultNamespace (global) kind.

build ./... clean; vet clean; SuperAdmin behavior-locking tests pass
(commerce auth/edgeauth/iammiddleware/catalog/costs/checkout, admin
scope/money, principal, root identity). gofmt clean. Zero GlobalAdmin /
global-admin remaining in .go/.md/.yaml.
2026-07-11 18:20:58 -07:00
hanzo-dev 675fdbb637 feat(admin): per-provider credit ledger + usage funding endpoints
Two SuperAdmin endpoints for multi-provider credit-management (the console renders
them; contract is authoritative):
  GET /v1/admin/providers/credit  -> [{provider, grant_cents, burn_cents,
      remaining_cents, runway_days, has_credit, is_paid_only}]
  GET /v1/admin/usage/funding?from&to -> [{provider, model, funding, tokens,
      cost_cents, requests}], funding in {credit,paid,paid_only,byo}

DRY: reuses the admin auth guard (core.Guard), finance.go's DO billing read (real
k grant, live remaining/burn/runway), and the ONE cloud_usage warehouse (no new
store). DO is the seeded real row; others land as keys arrive. Funding is
provider-level-derived in v1; the per-call split lands when the ai metering write
stamps a funding column (next commit). Envelope = core.OK {status,msg,data:[...]}.
Two-ledger model kept distinct: UPSTREAM provider credits here vs DOWNSTREAM Hanzo
customer billing (commerce). Pure logic TDD'd.
2026-07-11 17:24:20 -07:00
hanzo-dev d7716ed604 refactor(principal): IsSuperAdmin + IsOrgAdmin — two named predicates, not bare c.IsAdmin()
Per the SuperAdmin convention (SOC2/FedRAMP; standard term SuperAdmin, NEVER
'global admin'): name the two admin scopes explicitly.
- principal.IsSuperAdmin(c) = c.IsAdmin() — platform sudo; SuperAdmin ⟺ owner==admin org
  (X-User-IsAdmin minted only for that identity).
- principal.IsOrgAdmin(c) = IsSuperAdmin(c) || X-User-IsOrgAdmin — admin of one's own org.
GuardScoped now reads IsSuperAdmin (fast-path) + IsOrgAdmin (scoped) instead of bare
c.IsAdmin()/OrgAdmin. Pure rename — no behavior change, identity suite green.
2026-07-11 17:22:13 -07:00
hanzo-dev 0ae41f9f90 fix(deps): bump hanzoai/ai v1.805.5 -> v1.805.6 (failover credit-cascade)
v1.805.6 makes credit/quota exhaustion + agreement gates (402/403/insufficient_quota)
cascade to the next provider in the fallback chain — Phase 2 of multi-provider
credit-management + fixes the do-ai->anthropic opus fallback.
2026-07-11 17:15:52 -07:00
hanzo-dev 3c2179d928 admin: close same-tenant over-visibility gap in GuardScoped
GuardScoped admitted ANY validated org member to their own org's admin
panels (/v1/admin/{overview,orgs,users,usage,analytics,me,bases}), not
just org-admins: SanitizeIdentity discarded the JWT org-level isAdmin bit
for non-admin-org principals (it only minted the GLOBAL X-User-IsAdmin
when owner==adminOrg), so GuardScoped's fallback (validated User+Org) let
a plain member through.

Mint a new, unforgeable X-User-IsOrgAdmin signal and require it:

- middleware_identity.go: add X-User-IsOrgAdmin to authorityHeaders
  (stripped on every ingress request, so a client can never forge it),
  and mint it for any validated principal with claims.IsAdmin &&
  !isKMSMachinePrincipal — covering both a global admin and an org-admin,
  owner-scoped and machine-excluded.
- clients/principal: add OrgAdmin(c) = IsAdmin() OR X-User-IsOrgAdmin.
- clients/admin/core.GuardScoped: require principal.OrgAdmin(c) in
  addition to validated User+Org; a validated non-admin member now gets
  the same 403 as an unvalidated caller. Guard (global-only) untouched.

Tests: orgAdminHdr now carries the bit; add TestScope_MemberWithoutOrg
AdminDenied (member without the bit is 403 on every scoped panel) and
TestSanitizeIdentity_OrgAdminHeader (org-admin gets the bit not global,
member/machine get neither, forged bit stripped on bearer + anon paths).
2026-07-11 17:11:53 -07:00
hanzo-dev 8f23770eef Merge branch 'moneysafe' 2026-07-11 16:58:15 -07:00
hanzo-dev 496f4e76f4 admin: fail-closed grant durability + deposit idempotency (no unaudited/double money)
Finding 3 (grant durability — ARCHITECT: FAIL-CLOSED). EmitAudit is a silent
no-op when State.AuditStore == nil, so on a no-audit-store deployment a
SuperAdmin grant moved REAL money with NO durable cloud-side before/after record.

Decision: FAIL-CLOSED. Grants are a real-money op and the audit store is always
present in any real deployment — audit_serve.go REQUIRES a persistent data dir
for the trail (hard boot error otherwise), and a nil store arises ONLY from the
explicit CLOUD_AUDIT_DISABLED dev opt-out. So ApplyGrant now refuses the grant
with 503 BEFORE any money moves when AuditStore == nil: no unaudited money move.
The check sits after org validation and before the deposit, so the existing
validation errors (amount/cap/unknown-org) are unaffected.

Residual (documented, not regressed): a post-deposit Append failure (store
present but the write errors) keeps the money-moved success response — the money
DID land, and failing it would both misreport the grant and, absent idempotency,
invite a double-credit retry. It stays a loud log, backstopped by the
request-level AuditTrail middleware which independently records the request and
fails the request CLOSED on its own write error (serve.go / audit_middleware.go).

Finding 4 (deposit double-credit on retry — WIRED). commerce.Deposit posted
/v1/billing/deposit with no idempotency key, so a commit-then-timeout (cloud's
15s client) could drive an operator double-credit on retry. The commerce backend
DOES enforce idempotency: POST /v1/billing/deposit reads X-Idempotency-Key,
scoped billing-deposit:<subject> — a completed key REPLAYS the receipt, an
in-flight key 409s, an absent key is legitimately additive (never dedup by
amount). Verified in ~/work/hanzo/commerce/api/billing/deposit.go.

Fix: thread a DETERMINISTIC key from the grant. Deposit/post gained an
idempotencyKey arg sent as X-Idempotency-Key. ApplyGrant derives it as
sha256(org|amountCents|currency|source|nonce) where nonce is the operator-supplied
Idempotency-Key — so a retried grant carrying the SAME nonce dedupes at commerce
while two DISTINCT grants (even same org+amount) never collide, and a nonce reused
for a DIFFERENT amount still lands (dedup can never silently DROP a real grant).
No nonce => no key => additive default preserved; we do NOT fabricate a
content-only key (it would wrongly dedupe two legitimate identical comps).
Residual (cross-service, frontend): effective end-to-end once the operator
console sends an Idempotency-Key per grant attempt, reused verbatim on retry.

Finding 2 (GuardScoped over-visibility — NEEDS CROSS-SERVICE, not fixed here).
GuardScoped admits any validated principal with non-empty c.User()+c.Org().
SanitizeIdentity (middleware_identity.go) mints X-User-Id for EVERY validated org
member and mints the admin signal X-User-IsAdmin ONLY for a GLOBAL admin
(owner==adminOrg) — it DISCARDS the JWT org-level isAdmin bit for non-admin-org
principals. So a regular member's sanitized identity is byte-identical to an
org-admin's, and GuardScoped admits regular members to their own org's admin
panels (same-tenant over-visibility of financials + user directory; NOT
cross-tenant — ResolveScope pins to c.Org()). The finding is REAL, but the
prescribed fix (require org-admin) CANNOT be done in clients/admin/*: the
org-admin signal is not minted, and middleware_identity.go is read-only in this
scope. Requiring the only admin signal we have (c.IsAdmin(), GLOBAL) would break
the deliberate, test-locked org-scoped tier (scope_test.go admits org-admins).
Correct cross-service fix: in SanitizeIdentity's `case owner != ""` branch, mint
X-User-IsOrgAdmin=true when claims.IsAdmin (owner safe, non-KMS), add it to
authorityHeaders (stripped on ingress so unforgeable), then GuardScoped requires
c.IsAdmin() || X-User-IsOrgAdmin=="true". Left for the middleware owner.

Tests: TestGrantCredit_NilAuditStoreFailsClosed (503, no deposit, balance
unchanged); TestGrantCredit_IdempotencyKeyForwarded (same nonce=>same key,
distinct nonce=>distinct key, no nonce=>no key). Existing money must-pass tests
(TestGrantCredit_DepositLandsAndAudited, TestSuspendReactivate_*, TestAdminAudit_*)
still pass unchanged.
2026-07-11 16:54:33 -07:00
hanzo-dev e8b7e34913 admin: decomplect partial-commerce reporting on /overview (one partial pattern)
Finding 1 (undercount masked as healthy). core.OrgMoney swallowed the
Commerce.Spend/Credits errors to a silent zero, and /overview derived the
"commerce" source freshness from a SINGLE probe org — so if commerce was down
for 40 of 41 orgs the fleet spend/credits totals were an undercount while the
source still read "healthy". revenue.go / finance.go already report this
correctly via a `partial` flag + the core.ErrPartialRevenue sentinel.

Fix (decomplect to ONE partial pattern, not a second one):
- OrgMoney now returns (spend, credits int64, ok bool); ok is false when the
  spend OR credits read failed — the SAME (row, ok) contract revenue.revenueOf
  uses. An unwired commerce is NOT a failure (Spend/Credits return (0,nil) when
  unconfigured), so ok stays true and Ready() still distinguishes not-configured.
- overview folds ANY per-org OrgMoney failure into the commerce source as
  degraded, reusing core.ErrPartialRevenue, and derives freshness from the SAME
  per-org reads the totals fold instead of a single probe org.

orgs is a per-ROW panel (OrgRow[] via OKList; NO sources[] channel): a failed
read degrades THAT org's row to an honest zero — there is no aggregate total to
mislabel, so no change beyond the signature. The customer per-row/detail call
sites are best-effort and unchanged in behavior.

Test: TestOverview_CommercePartialOnPerOrgError — commerce 500s for one org of
two; the commerce source reports not-ok with an error while the healthy org's
spend still contributes (honest partial total, not a hard panel fail).
2026-07-11 16:54:05 -07:00
hanzo-dev 4415067a2f test(graph): align unreachable-upstream tests + doc to the code's honest-empty-200 (not 502) 2026-07-11 16:36:30 -07:00
hanzo-dev 519e5f5012 chore(kms): delete dead clients/kms/replication — a lone test with no production source
The subpackage contained only replication_test.go referencing an undefined Producer
(no NewProducer/BackupOnce/etc. anywhere), so it never compiled and failed go vet.
Zero importers. Pike: the best code is no code.
2026-07-11 16:33:39 -07:00
hanzo-dev 69baee05a5 style(admin): gofmt clients/admin/revenue/revenue.go (new split file) 2026-07-11 16:19:17 -07:00
hanzo-dev ae95251738 Merge branch 'splitA' into splitmerge 2026-07-11 15:37:47 -07:00
hanzo-dev da7fc15bb5 admin: rewire Mount onto core + domains, retire in-package handlers
Rewrite the top-level admin package as the Mount + aggregator only. state ->
core.State (exported fields), and every top-level handler + helper is retyped to
*cloud.Service[core.State] and calls core.* for the shared kernel:
  - routes() registers the org-scoped panels (me/overview/orgs/users/usage/
    analytics/bases) behind core.GuardScoped and the platform reads
    (roles/applications/products/compute/o11y/sync + flags/waitlist) behind
    core.Guard, then delegates to audit/customer/revenue/finance Routes().
  - analytics.go keeps only the analytics-specific derivation (growth/retention/
    churn/active/LTV) folding over the core activity model + spend series.
  - o11y/compute/bases/waitlist/flags/types retyped to core.State + core.*.

Delete the now-moved audit.go/customers.go/grants.go/revenue.go/finance.go/
scope.go (their handlers live in the domain packages; their shared helpers in
core). doTokenFromEnv moves to admin config; iamAuditQuery moves to the audit
package.

Move tests with their code: audit store tests -> audit package; grantTag test ->
core; finance pure-math tests -> finance package. The full-mount integration
tests (admin/scope/cockpit/finance-aggregation) stay in the admin package and
now drive the real routes() so the harness mirrors Mount exactly. Behavior,
routes, tenant scoping and every assertion unchanged.
2026-07-11 15:35:31 -07:00
hanzo-dev 385c45dc5e admin: extract shared core kernel + carve audit/customer/revenue/finance domains
Introduce clients/admin/core as the subsystem's shared kernel — the State
struct (upstream clients + adminOrg + audit store) and the one-copy business
primitives every admin surface composes: the two-tier gate (Guard/GuardScoped),
the /v1 envelope writers (OK/OKList/OKRaw/Fail), CallerCreds, the tenant-scope
predicate (TenantScope/ResolveScope/ScopedOrgs/Descendants), the IAM fan-in
(ListOrgs/OrgMoney/FindOrg/Display/SrcOf/SourceStatus), the ONE credit-write path
(ApplyGrant + EmitAudit + grantTag/grantNote/CreditRequest) and the fleet
activity/time-series model shared by analytics and revenue
(CustActivity/TxnPoint/SeriesPoint/FleetActivity/SpendSeries + bucket helpers).

Carve one package per handler domain over that kernel:
  - audit    -> /v1/admin/audit{,/verify} (store-backed + IAM fallback)
  - customer -> /v1/admin/customers* + /v1/admin/grants (list/detail/credit/
                suspend/reactivate/grants ledger)
  - revenue  -> /v1/admin/revenue
  - finance  -> /v1/admin/finance (+ the pure ComputeFinance derivation)

Each domain imports core for the kernel and shared logic; no business logic is
duplicated. Routes are registered per-domain via <domain>.Routes(app, s).
2026-07-11 15:35:03 -07:00
hanzo-dev 95dfcff940 feat(bots): GET /v1/bots + POST /v1/bots/:runId/stop — org-scoped list+stop over the bot-gateway
Completes the bots surface (launch -> launch+list+stop). Both are thin,
org-scoped proxies onto the in-cluster bot-gateway (BOT_GATEWAY_URL, the same
server-side knob clients/bot uses), carrying the caller's validated tenant
context (X-Org-Id pinned to principal.Org, never a request param).

- GET /v1/bots normalizes the gateway's session rows into
  {runId,task,surface,status,sessionUrl,startedAt}, deriving sessionUrl here
  (the one place a session URL is built). Honest-empty {"bots":[]} on an
  unconfigured/unreachable gateway, a non-2xx, or an undecodable body -- never 5xx.
- POST /v1/bots/:runId/stop returns {runId,status:stopped}; a run the caller's
  org does not own is 404; an unreachable gateway is a clean 502.

Both require a validated principal so org-scoping can't ride a forged X-Org-Id.
Hermetic list+stop tests against a fake gateway assert normalization, sessionUrl
derivation, caller-org scoping, honest-empty, and 404/502 paths.
2026-07-11 15:15:56 -07:00
hanzo-dev c739ec57d7 refactor(admin): extract iam upstream client into clients/admin/iam (finishes the upstream-client layer) 2026-07-11 14:53:10 -07:00
hanzo-dev 298522ab87 fix(deps): bump hanzoai/ai v1.805.4 -> v1.805.5 (enforceBalanceGate fail-open)
v1.805.5 adds the controller-side balance-gate fail-open (BALANCE_GATE_FAIL_OPEN_ON_ERROR)
on top of v1.805.4's nil-guard, so a broken/misconfigured Commerce billing backend
degrades to allowed-but-ungated instead of 500-ing every authenticated chat for
non-exempt users. Together they let the CR drop the commerce.hanzo.svc:8001 bridge
and keep commerceEndpoint unset per the in-process design.
2026-07-11 13:21:45 -07:00
hanzo-dev 2e03d9237b build(cloud): bump hanzoai/o11y v1.5.12 -> v1.5.13 — Hanzo Sentry /v1/sentry backend routes live 2026-07-11 12:39:20 -07:00
hanzo-dev 3d797a8c3a merge: Hanzo Sentry /v1/sentry cloud edge — mount + DSN-ingest gate exemption (Red-GO) 2026-07-11 12:37:25 -07:00
hanzo-dev 0be9250634 fix(deps): bump hanzoai/ai v1.805.3 -> v1.805.4 (nil balanceGate 500)
ai v1.805.4 guards the nil balanceGate deref in resolveBillingKey that returned a
bare HTTP 500 on EVERY authenticated /v1 request (models, chat/completions,
messages) whenever commerceEndpoint is unconfigured (balance enforcement disabled).
RateLimitFilter calls resolveBillingKey before BalanceGateFilter's own nil guard,
so the embedded AI subsystem crashed every authed request while anonymous requests
(no token) 401'd correctly. Fail-open: a disabled billing subsystem resolves no
billing subject and never crashes a request.
2026-07-11 12:27:38 -07:00
hanzo-dev ad9f83f6d0 feat(o11y): expose /v1/sentry edge mount + DSN-ingest gate exemption
Cloud edge for Hanzo Sentry (the /v1/sentry product face served by the embedded
o11y runtime):

- mountSentry registers the /v1/sentry/* wildcard, forwarding to the SAME gated
  runtime handler the /v1/o11y wildcard uses (one runtime, two path families; no
  path rewrite — the Sentry routes are literal /v1/sentry/... in the runtime).
- gate() now exempts the DSN-authenticated Sentry ingest writes (isSentryIngestPath:
  POST /v1/sentry/{project}/envelope|store/, tight method+prefix+suffix match) from
  the principal gate — the runtime authenticates the DSN key, not a Hanzo session —
  while EVERY Sentry read/write API stays principal-gated (no cross-tenant leak).

Uses only the existing o11y runtime-handler API, so it builds against the current
pinned o11y (v1.5.12) and is inert (404) until the o11y dep is bumped to a build
that carries the /v1/sentry routes.

FOLLOW-ONS (coordinated separately):
- Bump the hanzoai/o11y dep to the tag containing the /v1/sentry routes to activate.
- Gateway needs a byte-identical isErrorIngestPath sibling for POST
  /v1/sentry/{project}/envelope|store/ so the tokenless DSN ingest is not 403'd at
  the edge (do NOT touch ~/work/hanzo/gateway here).

Test: TestGateExemptsSentryIngestButGatesReads (ingest exempt, reads/writes gated).
2026-07-11 11:58:40 -07:00
hanzo-dev 5cb73ab8b1 fix(social): honest at-rest comment — token NOT yet encrypted (RED HIGH)
The Account.Token comment claimed the store is SQLCipher-encrypted and 'keeps
it encrypted at rest'. False: openStore uses cek.Open, which today runs the
no-key plaintext fallback (real WithRawKey-from-KMS lands with the connect
flow). Token column is empty today, so no plaintext secret ships.
2026-07-11 11:36:16 -07:00
hanzo-dev 7edc983318 merge(social): publish edge + scheduler parity (fail-closed provider seam) 2026-07-11 11:35:11 -07:00
hanzo-dev 88b0b29ba7 refactor(admin): complete first-principles upstream clients — money.Cents + digitalocean
Finishes the batch-F rework (the extraction landed in 7e93408; this is the second,
first-principles half that the earlier cherry-pick stopped short of):

- clients/admin/money — type Cents int64; the unit lives in the type, so
  ConsumedCents/MRRCents/CreditsCents collapse to Consumed/MRR/Credits. int64 casts
  only at the operator-contract boundary (wire unchanged, JSON tags kept).
- clients/admin/digitalocean — do.go extracted from the inline client; Client.{Ready,
  Balance,History}. Named digitalocean (not do) so it never collides with the local do var.
- clients/admin/commerce — reworked to the money.Cents unit + collapsed the always-equal
  (org,user) into one subject; dropped the MRRCents + duplicate-rollup shims.

Applied cleanly (0 conflicts) atop the extraction + tenant->org main. Build ./... green,
vet clean, admin+commerce+digitalocean tests pass (pure-Go cek gate).
2026-07-11 11:17:10 -07:00
hanzo-dev 7e93408074 refactor(admin): first-principles upstream clients — money.Cents + commerce/health/digitalocean/health packages
Extracts admin's inline upstream reader clients into self-contained, package-namespaced
units and gives billing a single value type. Decomplect + package-as-namespace, per the
Hickey/DRY bar:

- clients/admin/money — type Cents int64; the unit lives in the type (ConsumedCents/
  MRRCents/… collapse to Consumed/MRR). int64 casts only at the operator-contract edge.
- clients/admin/commerce — Client.{Ready,Spend,Credits,Plan,Ledger,Costs,Deposit}
  (Deposit = the one write). Collapses the always-equal (org,user) into one subject;
  the bare-slug X-Org-Id+user invariant is baked into the client. Drops MRRCents +
  duplicate rollup-balance shims.
- clients/admin/digitalocean — Client.{Ready,Balance,History}
- clients/admin/health — Client.{Ready,Up}

Wire unchanged (JSON tags kept, DTOs stay int64 cents). Integrated onto current main:
preserves the commerceinproc.BaseURL(...) in-process routing and the tenant->org
vocabulary. Build ./... green, vet clean, admin+commerce+integrations tests pass
(pure-Go, cek gate). Completes the batch-F rework the user authorized.
2026-07-11 11:12:08 -07:00
hanzo-dev af48c53c62 feat(social): publish edge + in-process scheduler (fail-closed provider seam)
Fold the live social stack's publish + schedule onto the native /v1/social domain:

- Publish edge (publish.go): the ONE publishPost path — claim (at-most-once across
  the HTTP handler and a scheduler tick), fan out to the channel's connected accounts
  through the injectable Publisher seam, record the honest outcome (published + external
  id, or failed + reason) on the post. POST /v1/social/posts/:id/publish + on-create
  fanout (scheduled-for-now-or-earlier) both call it.
- Scheduler (scheduler.go): an in-process periodic sweep (the native equivalent of the
  live stack's Temporal timer + hourly missing-post poller) that advances every org's
  scheduled -> published when the time arrives; idempotent, per-org, clean shutdown.
  Mirrors clients/commerce/sweep.go.
- Provider seam: fail-closed default (notConfiguredPublisher) that reports EXACTLY which
  OAuth-app credentials are missing (the live orchestrator's env var names) and NEVER
  fakes success. No Hanzo deployment carries provider creds today, so this is prod's
  honest state. GET /v1/social/providers reports per-network publish-readiness.
- Store: token on accounts (SQLCipher-encrypted at rest; live stack stores it plaintext),
  external_id/account_id/error on posts, ClaimForPublish/MarkPublished/MarkFailed,
  DueScheduled (the ONE deliberate cross-org system read), RecoverStuckPublishing.

Tenant isolation preserved: every publish is org-scoped; the scheduler's cross-org sweep
only reads (org,id) to dispatch into the org-scoped path. 12 tests (9 new) prove publish
success/not-configured/no-account, idempotency, per-org isolation, the scheduler sweep,
crash recovery, and live capabilities. go build -tags 'cloud cloud_mount' ./... green;
frozen wire-order guard green.
2026-07-11 11:08:49 -07:00
hanzo-dev d788864450 cek: complete plaintext-store coverage on live-prod + flatten to top-level package
Rebased blue's RED-reviewed encrypt-at-rest onto the CURRENT live-prod commit
(v1.786.185). The release train added stores blue's base never saw, all opening
PLAINTEXT — closed every one through the same cek.Open seam:
  - tenantdb.go   (the SOLE per-tenant opener → code/git/functions/tracker)
  - gojabase, gatewaypolicy (gateway.db), dataroom (link_index.db)
Result: ZERO plaintext sql.Open("sqlite") left in the cloud data plane
(commerce self-encrypts under its own KMS key; cek internals excepted).

Flattened internal/cek → top-level one-word package cek. Trimmed the AI-slop
import comments to one line.

Verified CGO=1+SQLCipher: go build ./... green, cek tests green, and blue's
cek.Open shipping path pre-proven on ALL 47 real prod DBs (ciphertext + plaintext
shredded + exact row-count parity, 0 fail).
2026-07-11 10:56:53 -07:00
blueandhanzo-dev 15533dc02d ci(cek): run frozen-format guard inside the Docker image build
The frozen-fixture test ran in Go CI but not inside the image under the pinned
Alpine libsqlcipher, so a sqlcipher-dev pin/base bump that changes the on-disk
format could go green in CI while bricking prod. Add the frozen-format gate to
the Docker RED gate (beside TestEncryptionProof), and make requireCipher honor
SQLITE_REQUIRE_CODEC=1 (a would-be skip becomes a FAILURE) so the in-image gate
is airtight: any format change now fails the IMAGE build, not just Go CI.

Verified: SQLITE_REQUIRE_CODEC=1 go test -run TestFrozenFixtureOpens ./internal/cek = ok.
2026-07-11 10:52:44 -07:00
blueandhanzo-dev 3b139ab55d fix(cek): frozen-format CI fixture + exact sqlcipher pin + confidentiality-only scope doc
RED re-review closers:
1. Cross-version brick guard (vector b): the version-freeze was soft (unpinned
   apk sqlcipher-dev resolves from the live Alpine repo). Now:
   - Dockerfile pins sqlcipher-dev=4.6.1-r0 → a repo bump fails the build LOUDLY
     (never a silent prod brick).
   - Commit a FROZEN encrypted fixture (internal/cek/testdata/frozen/store.db
     + .dek, written under cipher_compatibility 4) + TestFrozenFixtureOpens that
     copies it to temp, opens via cek, and reads a known canary row. A future
     libsqlcipher format change makes the FROZEN store fail to open → red CI,
     which build-time SQLITE_REQUIRE_CODEC (fresh-db only) cannot catch.
     TestGenerateFrozenFixture (CEK_GEN_FIXTURE=1) regenerates it on an
     intentional format rev.
2. Scope doc (vector c): cek package doc now states it provides CONFIDENTIALITY
   at rest, NOT integrity/authenticity/anti-rollback vs a PV-write
   (node-compromise) adversary — out of the stated read-only model. The
   logical-id+epoch binding is deliberately NOT added (out-of-model complexity).

9/9 cek tests green on real SQLCipher (cgo) + nocgo; gofmt/vet clean. Migration
still deferred; live cutover gated on the user's supervised go.
2026-07-11 10:52:44 -07:00
blueandhanzo-dev b6a85738ed fix(cek): address RED review — shred plaintext, fileID KEK, fatal-missing-key, content-parity
RED review fixes on the encrypt-at-rest codec:
1. [HIGH] Shred the pre-migration <db>.plain.bak after the verified keyed reopen
   (overwrite+remove, single call site in openEncrypted). Nothing reaped it
   before, so every migrated store left a COMPLETE plaintext replica on the
   volume forever — the exact threat the codec exists to kill. Test asserts the
   backup is gone post-migration.
2. [MED] KEK no longer binds to the CLOUD_DATA_DIR-relative path (brittle: a
   dir change bricked the plane). A random per-file id is stored in the sidecar
   head (fileID(16) || wrapped-DEK) and the KEK derives from it — intrinsic to
   the file, config-independent. Test moves a store to a new dir + wrong
   CLOUD_DATA_DIR and it still opens.
3. [MED] Missing key on an encryption-capable build is now FATAL (fail-closed,
   same posture as KMS), not a silent plaintext downgrade. Encrypting() is wired
   into the boot log (serve.go). No new gate/env — keyed off the existing
   CLOUD_KMS_MASTER_KEY_REF + build capability.
4. [MED] Parity gate gains a rowid-independent per-table content hash (commutative
   multiset sum of per-row hashes over user columns), catching value mutations
   that count+schema+integrity_check miss while ignoring benign rowid renumbering.
   Dropped the inaccurate 'byte-faithful' wording. Cross-version cipher stability
   is enforced by FREEZING libsqlcipher in the build (an at-open cipher_compat pin
   is infeasible with mattn's URI-key requirement — the URI param is ignored and a
   post-open pragma runs after mattn reads the header; proven); any mismatch fails
   closed (test: corrupt/missing sidecar refuses).
5. [LOW] recoverInterrupted scrubs stale -wal/-shm; migration removes them before
   the swap so a plaintext WAL never sits beside an encrypted db. No statement
   logging on keyed conns; the key never rides a logged DSN/error.

8/8 tests green on real SQLCipher 3.53.1 (cgo) + nocgo fatal-key path.
2026-07-11 10:52:44 -07:00
blueandhanzo-dev 999b86a2a4 feat(cek): encrypt-at-rest for all cloud SQLite stores (plaintext→SQLCipher, zero-loss migrate-on-open)
The CGO+libsqlcipher cloud binary shipped encryption DORMANT: all 29 stores
opened via bare sql.Open("sqlite", path), so /var/lib/cloud/*.db (crm PII,
treasury ledger, wallets, audit, team/entitlements) were plaintext despite
CLOUD_KMS_MASTER_KEY_REF being present. The SQLCipher primitives were linked
(hanzoai/sqlite cek.go) but never USED.

internal/cek.Open is the ONE encryption-at-rest seam every store now routes
through. When the master key is configured it transparently, under a per-file
flock: mints a per-DB random DEK (SQLCipher page key), wraps it AES-256-GCM
under KEK=HKDF-SHA256(master, principal) in a <db>.dek sidecar, and — for an
existing PLAINTEXT file — migrates it to SQLCipher via sqlcipher_export, then
verifies schema + per-table row-count parity + integrity_check by re-opening
the encrypted copy EXACTLY as the app will, BEFORE an atomic swap. Fail-secure:
key set on a non-encrypting build is a hard error; unverifiable migration leaves
plaintext intact; wrong master fails closed; crash mid-swap is recovered.

Proven with real SQLCipher (TDD): plaintext→ciphertext header, row parity,
.dek unwrap, .plain.bak preserved, idempotent reopen, wrong-key rejected,
dev-mode gated, nocgo fail-closed.

Migration is deferred to a maintenance-window cutover (this image built via
arcd) — NEVER encrypt against the current binary, which cannot open SQLCipher.

Rewires 29 open-sites; base/o11y external-module DBs are a follow-on.
2026-07-11 10:51:13 -07:00
8dfbbc314d cloud: migrate off deprecated app.Mount → All+AdaptNetHTTP (one mount path); tidy go.sum (#257)
zip #5 deprecated (*App).Mount(prefix, h): it is exactly
  app.All(prefix+"/*", zip.AdaptNetHTTP(h))
kept only as a behaviour-identical alias. Move every foreign-http.Handler
mount onto the explicit primitive so there is ONE way to put a route on the
app, and so the cloud money binary keeps building once zip deletes App.Mount.

Migrated all THREE route-mount call sites (the task scoped two; commerce is a
third — its exclusion note referred to the commerce.Mount *function*, not the
app.Mount(p, handler) inside it):
  - clients/plugin/plugin.go:125   app.Mount(p.Prefix, h) → app.All(p.Prefix+"/*", zip.AdaptNetHTTP(h))
  - clients/iam/iam.go:159         app.Mount(p, handler)  → app.All(p+"/*", zip.AdaptNetHTTP(handler))
  - clients/commerce/mount.go:147  app.Mount(p, handler)  → app.All(p+"/*", zip.AdaptNetHTTP(handler))
Behaviour-identical (Mount IS this composition). Also updated the four doc
comments that named the deprecated zip.App.Mount so no dangling reference to a
soon-deleted method remains. grep-confirmed ZERO app.Mount( route-mounts left.

go.sum: removed the two inert zap-proto/zip v1.3.0 hash lines (nothing in the
module graph requires v1.3.0 — orphan cruft a working `go mod tidy` would drop).
Full `go mod tidy` is blocked by a PRE-EXISTING, unrelated force-moved tag on
luxfi/keys@v1.2.2 (server serves h1:nuD+y5…; committed go.sum records
h1:XH5mRm…), so the two dead lines were removed surgically instead — luxfi/keys
and every other entry left byte-identical to origin/main. No GONOSUMCHECK hack.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-11 10:50:09 -07:00
hanzo-dev dbcb55eb0e fix(commerce): derive org from IAM on the token path — no commerce-owned org
Per the one-authority directive: commerce must not require its OWN Organization
record; IAM is the sole org/user/auth authority. The service-token path already
auto-projects the org from X-Org-Id via the cached GetOrCreate resolver, but the
IAM-principal path c.Next()'d without resolving the org — it depended on
iammiddleware running upstream, and when it hadn't, GetOrganization MustGet-
panicked (500) / the org was absent, so an IAM org with no pre-existing commerce
row could not view or create billing. ensureIAMOrg now resolves the validated
X-Org-Id through the SAME cached GetOrCreate resolver on the IAM path too
(idempotent), so any IAM org "just works" and a thin billing record is
auto-projected on first use — commerce derives the org from IAM, never its own
table. This is also the root cause behind the "hanzo has no commerce org record"
wall on the live 2-org proof.
2026-07-11 10:45:33 -07:00
hanzo-dev 758af74d8d fix(billing): account handlers never panic on an unresolvable org
The billing-account CRUD (List/Create/Get/Update/Delete + project bindings +
members + loadOwnedAccount) called middleware.GetOrganization, which MustGet-
panics (→ recovered 500) when the request's org has no commerce Organization
record — the same class as the already-deployed spend-alert fix. Switch all to
GetOrganizationOK with a safe default (reads → empty, mutations → 400/404), so
an IAM principal whose org lacks a commerce record gets a clean response, not a
500. Completes the metering-path panic hardening.
2026-07-11 10:33:24 -07:00
472e7f2067 cloud: zip v1.5.0 + OnShutdown teardown — fix teardown-before-drain race (#256)
Bump github.com/zap-proto/zip v1.3.0 → v1.5.0 (verified drop-in) and move
subsystem teardown onto zip's OnShutdown hook, deleting the hand-rolled
ShutdownAll reverse-loop.

Before: serve.go called ShutdownAll(specs) — a reverse-mount teardown loop —
BEFORE app.ShutdownWithContext. Subsystems were torn down while the listener
was still accepting and in-flight requests were still draining: a latent race
(a request could use a store that teardown had just closed).

After: MountAll registers each enabled spec's ShutdownFunc via app.OnShutdown
right after the subsystem mounts. zip drains those hooks LIFO — AFTER the
listeners stop accepting and in-flight requests drain — so registration-at-mount
reproduces the exact reverse-mount teardown order ShutdownAll gave, minus the
race. app.ShutdownWithContext now owns the whole teardown.

Scope is deliberately narrow: MountSpec, MountAll, Wire(), Typed, and the
OwnsHealth health loop all STAY (the imperative composition-root flatten was
proven unsound — a generic /v1/:name/health route is shadowed by 3-segment
subsystem routes). Only ShutdownAll and its serve.go call site are deleted;
audit/gateway-policy/telemetry teardown keep their positions.

Test: build_onshutdown_test.go drives a real in-flight request over a loopback
listener, shuts down mid-request, and proves (1) Shutdown blocks until the
request drains and (2) the MountAll-registered hooks then run LIFO = reverse
mount order. A second test locks the enablement axis + nil-Shutdown guard.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-11 05:35:45 -07:00
hanzo-dev 9eeaa47588 fix(o11y): exempt DSN-authed error-ingest from the principal gate
The Sentry error-ingest wire endpoints (POST /v1/o11y/api/<project>/envelope|store/)
authenticate with a DSN public key downstream in the o11y handler, not a Hanzo
principal. cloud's o11y gate() 403'd them for lacking X-User-Id, so the tokenless
ingest that the gateway allowlists (isErrorIngestPath) was blocked one layer deeper
— error-tracking could never ingest end-to-end.

Add the cloud-side counterpart: gate() now also exempts isErrorIngestPath
(byte-for-byte the gateway's matcher — method + /v1/o11y/api/ prefix + envelope|store
suffix, never a bare prefix). Reads under /v1/o11y/api/vN/... and the Issues
list/detail/update stay principal-gated; the exempted ingest still fails closed on a
bad/absent DSN key (401/503). Tested: TestGateExemptsErrorIngestButGatesReads.
2026-07-10 23:58:25 -07:00
ba9f632108 fix(commerce): sessionless webhook org resolve must not MustGet-panic (#254)
The live signed-webhook e2e (#118) got past HMAC verification and then
500'd: resolveWebhookOrg called middleware.GetOrganization — gin MustGet
— but webhook ingress runs OUTSIDE the auth-token group, so no
middleware ever set "organization" and every signature-VALID provider
delivery panicked ("key organization does not exist"). Switch to the
GetOrganizationOK variant that exists precisely for signature-verified
sessionless ingress; the header/env/default fallback chain below it now
actually runs.

Regression test drives resolveWebhookOrg on a bare sessionless gin
context and asserts no panic.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 23:39:24 -07:00
eed7221488 fix(commerce): seed the Square registry provider from env — unbreak inbound webhook validation (#253)
Every inbound Square webhook 401'd 'square processor not configured':
payment/providers/square registers an EMPTY Provider whose Configure()
only runs from BD's per-tenant charge resolver — but tryValidateWebhook
(the sessionless inbound path) reaches the registry slot directly. The
env-registering thirdparty/square init could never win the slot either
(import-order clobber / defer-to-existing), so webhook validation had no
configured processor in ANY deployment — 100% of live Square deliveries
were rejected.

init() now seeds Configure() from the deployment env (same vars +
SQUARE_ENVIRONMENT sandbox switch thirdparty reads; charge creds required,
webhook fields optional with ValidateWebhook's own fail-closed contract).
BD's per-tenant Configure still overrides per request for outbound money.

Regression guard drives env -> configFromEnv -> Configure ->
ValidateWebhook over a real Square-spec HMAC (url+body), plus tamper and
sandbox-switch cases.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 22:56:08 -07:00
5e8fd1e932 feat(commerce): in-process auto-recharge sweep — retire the external CronJob (#252)
Standalone commerce was swept by a k8s CronJob (curl image + cluster hop +
token secret) POSTing /v1/billing/auto-recharge/run-all every 15m at
commerce.hanzo.svc:8001. With commerce folded into the cloud binary that
loop is redundant moving parts: the binary now dispatches the SAME request
loopback through its own embedded gin handler — full middleware chain
(TokenRequired service-token branch -> PlatformOnly mint gate -> datastore/
KMS context), byte-identical to the wire path (guarded by
TestSweepOnceWireContract).

- interval: COMMERCE_AUTORECHARGE_INTERVAL (default 15m; 0/off disables;
  garbage disables fail-safe — a card-charging loop must never guess)
- token: COMMERCE_SERVICE_TOKEN (absent -> disabled with a loud warn,
  not a 403-every-tick loop)
- first fire after one FULL interval (never front-run the outgoing CronJob
  during rollout)
- runs only where commerce mounts (single-writer pod; reader role never
  mounts commerce) -> exactly one sweeper, same guarantee the single
  CronJob schedule gave
- stops with Embedded.Stop

Unblocks deleting the commerce-auto-recharge CronJob + the standalone
commerce/commerce-sandbox pods (#118).


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 22:33:02 -07:00
hanzo-dev 5cda438a8c merge(social): fold native /v1/social domain (ship-dormant; no ingress cutover)
# Conflicts:
#	subsystems/subsystems.go
#	subsystems/wire_test.go
2026-07-10 21:46:12 -07:00
hanzo-dev 2928ccfdab merge(ads): fold native /v1/ads domain
# Conflicts:
#	subsystems/subsystems.go
#	subsystems/wire_test.go
2026-07-10 21:45:26 -07:00
hanzo-dev 0dec0cff70 merge(marketing): fold native /v1/marketing domain 2026-07-10 21:44:39 -07:00
hanzo-dev 2d924110b4 feat(content): real Generator + Distributor over the framework CMS, hardened
Turns the agentic-marketing content loop from scaffolding into a working
edge pair, then closes every finding from the adversarial review.

Edges (wired at Mount, fail-closed until configured):
- Generator: zen5 copy via deps.AI.ChatCompletion (metered Bill.Gate/MeterUsage)
  + studio assets via the ComfyUI Qwen-Image-Edit-2511 graph.
- Distributor: hanzoai/social Public API fan-out, per-brand key custodied in KMS.
  errNotConfigured until a brand connects a key — no key, no fan-out.

Hardening:
- Publish TOCTOU interlock: a per-item, store-backed lease (framework fw_locks,
  the ONE cross-process coordination primitive) serializes concurrent publishes
  of the same item across drivers and pods; non-idempotent fan-out runs once.
- source_media SSRF gate: the URL validator fails closed on unparseable/backslash
  input.
- external_ids is server-managed: the before_save guard rejects a client write;
  Publish records it under the lease as a trusted server write.

Adversarial regression suite pins each guarantee from the outside (raw framework
PUT, direct ops, concurrency): red_adversarial / red_rereview / red_final /
red_lease_final, plus blue_hardening and per-file unit tests.

One open item recorded as a HARD GATE in clients/content/LLM.md: lease
TTL-preemption re-opens the double-post window for a brand with ~15+ slow
channels (fan-out (N+1)x20s > 5m TTL, external_ids recorded only at fan-out end).
ZERO exposure until a brand connects a social key; the fix (lease heartbeat/renew
preferred) MUST land in the same change that connects the first real key.
2026-07-10 20:54:56 -07:00
hanzo-dev 57f0cde63d fix(social): add social to frozen wire-order guard (RED ship-blocker) 2026-07-10 19:13:09 -07:00
0f86372c3b hardening(consolidation): split-proof the framework-content guard + DataDir doc (RED INFO) (#251)
Two INFO items from RED's #250 re-review:
- TestFrameworkContentModulesLinked asserted only the module registry. erp's
  ledger-posting HOOKS register in a SEPARATE init() step, so a future split of
  registerHooks() out of erp's module init() could drop the hooks while the guard
  stayed green. Add framework.RegisteredHookCount() and assert it > 0 so the guard
  fails if erp's hooks (computeJournalTotals, journalEntry/paymentEntry
  submit+cancel, …) are ever unlinked from the binary.
- gojabase Config.DataDir comment said "{tenantSlug}.db" (the pre-C1 name); the
  on-disk segment is TenantSegment (injective, traversal-safe base32 of raw org
  bytes). Comment now matches the code.

go build + go test ./subsystems/... ./clients/framework/... green.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 19:11:18 -07:00
hanzo-dev 24961ee941 feat(ads): native /v1/ads domain in the cloud binary
Net-new per-org ad-campaign domain on the ONE cloud framework (zip/Fiber +
cloud.Deps + per-org SQLite), the same shape clients/crm uses — twin of crm.
Registered in subsystems.Wire() right after crm; frozen wire sequence updated.

/v1/ads surface (all org-scoped, tenant-isolated on the bearer owner claim):
  GET    /v1/ads/health             (auto, serve.go liveness)
  GET    /v1/ads/summary            per-org roll-up (total/active/budget/spend)
  GET    /v1/ads/campaigns          list (?status=)
  POST   /v1/ads/campaigns          create
  GET    /v1/ads/campaigns/:id      detail
  PUT    /v1/ads/campaigns/:id      update
  DELETE /v1/ads/campaigns/:id      delete

Campaign = root of the ad hierarchy (campaign -> ad sets -> ads; ad-set/ad legs
hang off this seam): Platform (meta/google/tiktok/x), Status (draft/active/
paused/completed), Objective, Budget/Spend (cents).

Tests: per-org isolation + full CRUD + summary round-trip, both green.
2026-07-10 18:50:50 -07:00
hanzo-dev 439de5c01f feat(social): fold the live social stack as native /v1/social domain
In-process fold of github.com/hanzoai/social (social-backend/frontend/
orchestrator, a Postiz-style scheduler) onto the ONE cloud framework
(zip/Fiber + per-org SQLite), twin of clients/crm + sibling of the
marketing fold. NOT a proxy to the standalone social pods.

Two entities faithful to the live Public API (clients/content publish.go
already talks to it): Account = a connected channel (the stack's
integration), Post = content published/scheduled to a channel. Scheduling
is a Post with status=scheduled + a future scheduleAt, not a third entity.

Every query filters WHERE org=? on principal.Org (validated bearer owner,
HIP-0026); one tenant can never read/mutate another's rows. Registered in
subsystems Wire() after crm with a ctxShutdown that closes the DB.

Surface (org-scoped, /v1 only): summary + accounts CRUD + posts CRUD.
Generic liveness serves GET /v1/social/health.

Build: go build -tags 'cloud cloud_mount' ./... GREEN; 3 store tests pass
(per-org isolation across accounts+posts, post CRUD+summary, account CRUD).
2026-07-10 18:44:03 -07:00
hanzo-dev df72126108 feat(marketing): fold hanzoai/marketing as native /v1/marketing domain
Mount github.com/hanzoai/marketing in-process on the ONE cloud framework
(zip/Fiber + cloud.Deps + per-org SQLite), the same shape clients/crm uses —
NOT a proxy to a standalone marketing pod. Registered in subsystems.Wire()
right after its twin crm; frozen wire sequence updated to match.

/v1/marketing surface (all org-scoped, tenant-isolated on the bearer owner claim):
  GET    /v1/marketing/health             (auto, serve.go liveness)
  GET    /v1/marketing/summary            per-org roll-up (total/active/budget/spend)
  GET    /v1/marketing/campaigns          list (?status=)
  POST   /v1/marketing/campaigns          create
  GET    /v1/marketing/campaigns/:id      detail
  PUT    /v1/marketing/campaigns/:id      update
  DELETE /v1/marketing/campaigns/:id      delete

Campaign faithful to the repo domain: Channel (email/sms/social/meta/google/
tiktok), Status (draft/active/paused/completed), Objective, Budget/Spend (cents).
Genetic-optimizer / ML-forecasting / ad-platform integrations not folded yet.

Tests: per-org isolation + full CRUD + summary round-trip, both green.
2026-07-10 18:01:08 -07:00
hanzo-dev 89aae92c6a Merge fix/genai-tracer-clobber-repin: pin ai to v1.805.3
Bumps github.com/hanzoai/ai v1.805.2 -> v1.805.3 (GenAI tracer pinned at adopt
time; gen_ai spans survive the embedded o11y/SigNoz global tracer-provider
reassignment and reach o11y_traces). go.mod/go.sum only, no cloud source change.
2026-07-10 17:58:22 -07:00
hanzo-dev ca9c4134fe deps: pin ai to v1.805.3 (GenAI tracer immune to o11y global-provider clobber)
Bumps github.com/hanzoai/ai v1.805.2 -> v1.805.3. v1.805.3 pins the GenAI
tracer at adopt time so the embedded o11y/SigNoz runtime reassigning the
process-global OTel tracer provider can no longer redirect gen_ai spans off
the o11y sink — they reach o11y_traces. No cloud source change; go.mod/go.sum only.
2026-07-10 17:57:43 -07:00
hanzo-dev 3bdf72a80f feat(content): native agentic-marketing content loop on the framework CMS
Add clients/content — the ONE Go-native replacement for the bespoke karma
Python pipeline. A framework app-lane (module "marketing": Campaign, SocialPost,
Asset) + a thin /v1/content/* control-plane. Store-less: content IS framework
documents; the subsystem is a stateless orchestrator over the framework store +
the zen5/studio/social edges.

- lifecycle.go: ONE state machine (draft→in_review→approved→queued→published,
  +archived), a pure value read by the before_save hook (enforces edge legality
  at the storage boundary) and the transition endpoint (same check + fan-out).
- hooks.go: before_save gate on every publishable DocType.
- content.go: board (cross-DocType aggregate), lifecycle, transition (+best-effort
  distribution), generate/publish/channels. Org-scoped via principal.Org; never a
  5xx from a foreseeable condition (fail-closed 503 / honest 4xx).
- generate.go/publish.go: Generator + Distributor seams with fail-closed defaults;
  real zen5 (deps.AI) + studio (ComfyUI) + hanzoai/social wiring documented for the
  follow-up. Exported Generate/Publish/Transition are the ONE impl the HTTP surface
  AND the automations connector call.
- framework: add Get (read-one), exported ErrNotFound/ErrConflict/ErrBadRef +
  IsValidationError so in-process callers classify errors without string-matching.
- automations: connector_content.go exposes content_generate/transition/publish as
  flow steps + MCP tools (in-process, org-scoped) so the loop runs autonomously
  (cron flow: generate → wait_for_approval → transition → publish).
- subsystems: Wire content after knowledge; frozen wire-order test updated.

Tests: lifecycle table, before_save hook, end-to-end loop over the real framework
store (install→create→board→transition→publish), forge-403, cross-org isolation.
go build ./... + go test (content/framework/automations/subsystems) all pass.
2026-07-10 16:48:54 -07:00
3f185baa6f fix(subsystems): restore cms/erp/help framework content modules (#248 regression) (#250)
#248 (Wire() composition root) rewrote subsystems.go and dropped the blank
imports for cms/erp/help. Those three are NOT mount subsystems — no HTTP surface,
never in Wire(). Each registers DocType fixtures and, for erp, ledger-posting
lifecycle hooks (computeJournalTotals, journalEntry submit/cancel, paymentEntry
submit/cancel, …) into the always-on clients/framework engine from a package
init() (framework.RegisterModule). Dropping the imports left them out of the
binary: /v1/framework/* carried no erp/cms/help and the erp ledger hooks were
silently gone. No mount test caught it (frozen[]/Wire() cover only mount specs).

Fix (RED-verified): re-add the three blank imports under an explicit "framework
content modules" comment; add framework.RegisteredModules() + a guard test
(TestFrameworkContentModulesLinked) asserting the engine carries each lane so the
drop cannot silently recur. Also relax TestDepGatedSubsystemsFailClosed to accept
any non-2xx — a dep-disabled subsystem denying 403 is fail-closed; >=500 was
wrongly strict (o11y denies 403, ai returns 5xx).

go list -deps ./cmd/cloud shows cms/erp/help; go build ./... green;
go test ./subsystems/... ./cmd/cloud/... -race green.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 16:24:14 -07:00
hanzo-dev decc5cf85c fix(billing): metering gate no longer panics on an unresolvable org
The S2S metering path (ScopeRules → ListSpendAlerts; AuthorizeVerdict →
AuthorizeSpendCap) can reach these handlers with no "organization" context key
when X-Org-Id does not resolve to a commerce org (e.g. the agents scheduler
probing an unprovisioned org). middleware.GetOrganization MustGet-panicked
there → a recovered 500 storm on the money path (observed live: "key
organization does not exist", ~every 5-15s). Switch the metering-verdict
handlers + billingSubject to GetOrganizationOK with a safe default — no org
means no org-scoped caps, so ListSpendAlerts returns empty and
AuthorizeSpendCap allows — instead of panicking. Regression test proves neither
handler panics with no org.
2026-07-10 16:16:19 -07:00
hanzo-dev 3e54403f68 feat(principal): carry Project + BillingAccount from the verified identity
types.Claims gains Project + BillingAccount; principal.BillingAccount(c) reads
the gateway-minted X-Billing-Account-Id, added to subScopeHeaders so the raw
client copy is stripped on ingress and re-injected only for a validated
principal (mirrors X-Project-Id). It is an ATTRIBUTION hint only — the debited
account is always resolved server-side by commerce from the org's
ProjectBinding, never trusted from the header — so a mislabelled account can
only ever misattribute the caller's OWN spend within its own org, never
redirect spend to another tenant. Inert until IAM emits the billing_account
claim + the gateway mints the header (slices 63/64).

Also fixes a stale test left by a88f6612 (/metrics is now a console page, not an
API 404 — dropped from the must-404 list).
2026-07-10 16:00:57 -07:00
6072681f22 cloud: explicit composition root — Wire() replaces the init-registry; order-ints deleted (#248)
Replace the init()-registry (blank imports + cloud.Register(name, order, …) +
magic order-ints) with ONE explicit subsystems.Wire() []cloud.MountSpec. Slice
position IS the mount order — MountAll iterates it as-given, ShutdownAll in reverse.

Core (build.go/serve.go/cmd): delete MountSpec.Order, Register,
RegisterWithShutdown, the HealthOwner option func, and var Registry. MountAll and
ShutdownAll take the []MountSpec slice; Serve threads it in (cloud never imports
subsystems → no cycle). cmd/cloud + cmd/hanzo call subsystems.Wire(). Typed and the
factory hooks (RegisterKMSClientFactory, RegisterCommerceClientFactory,
RegisterOrgScopeResolver, RegisterPushBuilder, RegisterTelemetryInstaller) are
untouched — a different mechanism.

In-repo (~64 clients/*): delete each init() registration; export the mount fn where
unexported (commerce.MountFromDeps, o11y.MountO11y) and the shutdowns. ctxShutdown
bridges the func() error shutdowns in one place.

Externals wired explicitly; the wave-2 tags no longer self-register:
  ai v1.805.2 (@150 catch-all), o11y v1.5.12 (@70 wildcard) — origin/main already
  pins these (genai-span) but did NOT wire them, so main currently DROPS ai + the
  o11y wildcard from its live registry (main's own TestRegistryAssemblesSubsystems
  fails on that). This composition root RESTORES both. authz v1.10.7 (@70),
  licensing v0.1.3 (@110, Mount is already a MountFunc — wired direct), metrics
  v1.110.2 (@40, takes its own metrics.Deps via mountMetrics). vfs unchanged: it
  never registered a subsystem, so it is not wired.

Order is proven by subsystems.TestWireOrderMatchesFrozen against the sequence
captured empirically from origin/main @9e8ac44 (68 self-registering specs) with ai
+ the o11y wildcard restored at their order-int slots. The Service[state] refactor
reshuffled same-order tie positions on main; the frozen sequence adopts main's new
order (functionally inert — tied subsystems own disjoint route prefixes).

Also fixes a pre-existing clean-main build break (#247): clients/sign/sign.go
referenced an undefined `log` — main does not compile without it, so the whole tree
(subsystems → cmd/cloud) failed to build. One-line fix (log → deps.Logger); flag
for the owner to factor out if preferred.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 15:42:09 -07:00
bc4f082f00 fix(sign): use deps.Logger for the VFS-nil guard (semantic merge fix, #117) (#249)
#247's VFS-nil health-only guard was authored against the pre-refactor sign.go
(which had a local `log` var); it auto-merged cleanly onto the concurrently-landed
cloud.Service refactor (principal.Org / s.Log) but referenced an undefined `log`,
red-ing the build (clients/sign/sign.go: undefined: log). Point it at deps.Logger
(guaranteed non-nil by the guard above it). No behavior change.

go build ./... + go build -tags "libsqlite3 sqlite_fts5" ./cmd/cloud +
go test -race ./clients/{gojabase,captable,sign,dataroom}/... all GREEN.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 15:24:58 -07:00
9e8ac4454c fix(consolidation): gojabase blob seam + sign SEQUENTIAL/off-DB PDFs + cap-table dilution (#117 M5/M7/M8) (#247)
Second wave of RED's consolidation review — the mediums that needed new
hanzoai/captable + hanzoai/sign bundle versions (now merged) plus their cloud-side
wiring and tests.

M5 (captable bundle @119bf9c0) — capTable summed ALL option rows regardless of
  status, so EXERCISED/EXPIRED/CANCELLED grants inflated fullyDilutedShares and
  every ownership %. Fixed to count OUTSTANDING options only. New
  TestDilutiveOptionsExcludeTerminal proves terminal-state grants don't dilute.

M8 — ONE blob seam in gojabase (Config.Blob + a tenant-scoped globalThis.__blob =
  { put(key,b64), get(key) }), keys namespaced {Name}/{TenantSegment} so a bundle
  can only reach its own tenant's objects. sign (bundle @315a3fe6) now routes PDF
  bytes THROUGH it instead of inlining 32 MiB base64 in document_data.data: create
  stores the original blob key, seal writes a sealed key, view/download read via
  __blob.get. The sign leaf passes deps.VFS as the seam (health-only without it).
  document_data holds only the key now (type BLOB_KEY). Same VFS/S3 plane dataroom
  uses — one blob strategy, not two.

M7 (sign bundle @315a3fe6) — SEQUENTIAL signing order was declared but never
  enforced. assertTurn gates signField+signComplete so a later signer can't act
  until every earlier signer has SIGNED. New TestSequentialSigningOrder proves an
  out-of-turn signer is refused (403) and the turn opens once the earlier one signs.

sign tests now inject an in-memory VFS and assert PDF bytes land on the seam
(tenant-scoped key), NOT in the tenant SQLite. All four gate packages pass under
go test -race against the published module versions.

Gate: go build ./... + go build -tags "libsqlite3 sqlite_fts5" ./cmd/cloud +
go test -race ./clients/{gojabase,captable,sign,dataroom}/... all GREEN.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 15:19:42 -07:00
hanzo-dev efa47ed112 Merge feat/genai-span-host-provider: hoist gen_ai host tracer install into cloud.Serve; pin ai v1.805.2 + o11y v1.5.12 2026-07-10 15:10:08 -07:00
hanzo-dev eb74b1e216 telemetry: bootstrap the host tracer provider inside cloud.Serve — one site, every entrypoint
cloud installs the ONE global tracer provider wired to the o11y in-process trace
sink, but in in-process-sink mode it sets no OTLP/ZAP exporter endpoint. The embedded
hanzoai/ai module then found no endpoint and DISABLED its gen_ai span emit, so the
gen_ai plane in o11y_traces was dark (cloud's own request spans flowed; every LLM
call's gen_ai span was gated off). The provider install + adopt also lived ONLY in
cmd/cloud/main.go, leaving every 'hanzo <svc>' entrypoint (which shares cloud.Serve)
telemetry-dark.

Hoist the bootstrap into cloud.Serve — the ONE serve body cmd/cloud AND every
'hanzo <svc>' share — so both install the provider and adopt it into ai identically,
BEFORE MountAll mounts ai (ai's InitTelemetry reads the adopted-ready flag at mount).
cloud.Serve cannot import clients/o11y (clients/o11y imports cloud -> cycle), so the
concrete bootstrap (SetTracerProvider + aiobject.AdoptHostTracerProvider) lives in
clients/o11y and registers via cloud.RegisterTelemetryInstaller — the same cycle-free
inversion as RegisterKMSClientFactory / RegisterPushBuilder. Serve flushes the
provider on shutdown BEFORE ShutdownAll tears the sink down, so buffered spans drain.

Removes cmd/cloud/telemetry.go (moved to clients/o11y/traceprovider.go). Repins ai to
the branch carrying AdoptHostTracerProvider.

Red review (SHIP): MED-1 — this hoist (both entrypoints adopt identically). Tests:
cloud.installTelemetry dispatch/no-op (telemetry_test.go); clients/o11y
installTraceProvider adopt-latching + OTLP-env-retire + disabled-noop
(traceprovider_test.go).

ai: -> v1.805.1-0.20260710213829-b5eb789d3878 (feat/genai-span-host-provider @ b5eb789d)
2026-07-10 15:09:19 -07:00
hanzo-dev 18743b1155 Merge remote-tracking branch 'origin/main' into wt3/integrate
# Conflicts:
#	clients/affiliates/affiliates.go
#	clients/auditlog/auditlog.go
#	clients/authors/authors.go
#	clients/automations/automations.go
#	clients/automations/mcp.go
#	clients/billing/billing.go
#	clients/billing/finance.go
#	clients/bots/bots.go
#	clients/captable/captable.go
#	clients/dataroom/dataroom.go
#	clients/framework/permission.go
#	clients/functions/billing_test.go
#	clients/functions/functions.go
#	clients/functions/invoke.go
#	clients/functions/metrics.go
#	clients/gateway/gateway.go
#	clients/git/git.go
#	clients/git/mirror.go
#	clients/git/smart_http.go
#	clients/graph/graph.go
#	clients/integrations/integrations.go
#	clients/knowledge/connectors.go
#	clients/knowledge/subsystem.go
#	clients/projects/deploy.go
#	clients/projects/domains.go
#	clients/projects/fork.go
#	clients/projects/projects.go
#	clients/referrals/referrals.go
#	clients/security/security.go
#	clients/tracker/tracker.go
#	clients/treasury/treasury.go
#	clients/visor/fleet.go
#	clients/wallets/wallets.go
2026-07-10 15:03:50 -07:00
hanzo-dev 9cc58786f3 Merge remote-tracking branch 'origin/main' into wt3/integrate
# Conflicts:
#	clients/agents/agents_test.go
#	clients/agents/model_validation_test.go
#	clients/agents/scheduler_test.go
#	clients/captable/captable.go
#	clients/crm/applications.go
#	clients/crm/applications_test.go
#	clients/dataroom/dataroom.go
2026-07-10 14:48:11 -07:00
1791491878 cloud: IAM-native vocabulary — org/user/project everywhere, tenant concept removed (TenantDB→OrgDB) (#246)
* cloud: IAM-native vocabulary — org/user/project everywhere, tenant concept removed (TenantDB→OrgDB)

"tenant" was a non-IAM synonym for org. Replace it with the IAM-native nouns
org / user / project / billing account so there is ONE name for the concept.

Root framework primitives (package cloud) — now 100% tenant-free:
  TenantDB                     -> OrgDB            (tenantdb.go -> orgdb.go)
  TenantStore[T]               -> OrgStore[T]
  NewTenantStore               -> NewOrgStore
  tenantDBPath / openTenantDB  -> orgDBPath / openOrgDB
  TenantScopeResolver          -> OrgScopeResolver (tenant_scope.go -> org_scope.go)
  RegisterTenantScopeResolver  -> RegisterOrgScopeResolver
Dropped the legacy X-Tenant-Id / X-Tenant-ID entries from the identity
strip-list (nothing reads them; X-Org-Id is the live header).

Cross-subsystem seams:
  principal.Tenant(c) -> principal.Org(c)  (clients/principal; no collision —
    Project/User kept, already IAM-native). ~50 call sites + ~70 stale doc refs.
  types.TenantConfig -> types.OrgConfig; CommerceClient.GetTenantConfig ->
    GetOrgConfig  (+ commerce client impl, disabled/rpc/entitlements consumers,
    the cloud.OrgConfig alias in deps.go).

Adopters deep-cleaned (identifiers, comments, test names): clients/code, git,
functions, tracker, provisioning, projects. Docs: subsystems.go composition
comments, README.md, and a new LLM.md "Framework doctrine" section.

GATED EXCEPTION (flagged, intentionally unchanged): clients/platform derives
LIVE k8s namespaces, registry image refs, and quota/limit objects from a
"tenant-<org>" string prefix. Renaming it orphans deployed namespaces + built
images, so the literal string is retained behind a // NAMING(gated) note in
clients/platform/k8s.go. The rbac test file + its funcs were renamed
(tenant_rbac_test.go -> org_rbac_test.go).

Out of scope (separate waves; independent domains, touched only for the
principal.Org call-site + stale-ref fix): commerce internal tenant tables
(active commerce-dissolve branch), runner tenantsource, treasury ledger, and
other subsystems' own tenant vocab.

Build: GOWORK=off CGO_ENABLED=0 go build ./... -> exit 0.
Tests: every touched package green. The 38 pre-existing failures (fakeAI
missing Embed; undefined Producer; commerce integration tests; o11y/graph/zt/
kms route-precedence & service tests) fail identically on the base commit.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>

* rebase: apply org vocabulary to post-branch main commits (metering/HA/tracing comments); drop unused TenantConfig alias

---------

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 14:45:00 -07:00
hanzo-dev e5cc2bcc54 merge: integrate cloud.Service[state] refactor onto origin/main (zip v1.3.0, o11y, renames) 2026-07-10 14:39:39 -07:00
zeekayandhanzo-dev d739b9d063 style(config): gofmt align HA reader/writer fields in LoadConfig
Follow-up to the reader-tier commit — align the CLOUD_WRITER_URL/
CLOUD_READER_RETRY_BUDGET/CLOUD_WRITER_LEASE struct-literal keys with gofmt so
the CI fmt gate is clean. No behavior change.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 14:37:32 -07:00
1351eb5354 fix(consolidation): tenant-injective per-tenant SQLite + un-stage folds + harden gojabase (#117) (#245)
RED adversarial review of the one-binary consolidation (gojabase + captable/sign/
dataroom folds). Fixes the two ship-blockers plus the in-repo mediums/slop.

C1 (HIGH) — cross-tenant collapse via non-injective filename encoding.
  gojabase.slugify ToLower+folded [^a-z0-9._-]→'_', collapsing DISTINCT owners
  (Acme/acme, "a b"/"a_b") onto ONE per-tenant SQLite file — a cross-tenant break,
  the exact fold principal.Tenant keeps the org verbatim to avoid. Replaced with
  gojabase.TenantSegment: lowercased unpadded base32 of the RAW org bytes —
  INJECTIVE (distinct orgs never share a file) and traversal-safe ([a-z2-7], never
  "."/".."/"/"). Table test proves injectivity (Acme≠acme≠a b≠a_b) + traversal
  containment. IAM owner charset permits case/separator variants, so this was a
  real (not theoretical) collapse. Fresh-tenant-only: the folds pre-date any
  release, so no on-disk data uses the old names — nothing to migrate.

H2 (HIGH) — code==docs on staging. captable/sign/dataroom were un-staged in
  config.go (stagedSubsystems={iam,ingress}) yet every leaf/README claimed
  "STAGED / standalone keeps authority". Evidence (do-sfo3-hanzo-k8s): NO
  standalone captable or dataroom deployment exists; the esign pod runs but its
  SQLite holds ZERO tenant data (User=0, DocumentData=0, Recipient=0, Field=0 —
  only BackgroundJob/RateLimit churn). Decision (a): keep un-staged, delete the
  false comments (captable.go, sign.go, dataroom.go, subsystems.go, README ×2).
  No migration needed (dead/empty apps).

M3  drop dead commercesvc api.Route(/v1/{billing,checkout,store,subscription,
    account}) — unreachable in embed mode (only /v1/commerce/* mounted, no
    rewrite); money path is clients/billing, unaffected. Removed unused import.
M4  gojabase per-tenant *sql.DB cache is now an LRU (cap CLOUD_GOJABASE_MAX_DBS=256)
    with idle eviction (CLOUD_GOJABASE_IDLE_TTL_SEC=300) and dispatch PINNING —
    only idle handles evict, never a DB mid-transaction. Bounds fd/memory for N
    tenants.
M6  dataroom deny_list is now ENFORCED in view.authenticate and WINS over allow
    (checked first); surfaced on linkOut. One shared email matcher (DRY).
M9  sign refuses to boot with a self-signed cert in a production env — requires the
    KMS-custodied CLOUD_SIGN_CERT_PEM/KEY_PEM; dev still self-signs.
M10 added a -race concurrent multi-tenant dispatch test (heavy eviction churn +
    case-variant tenants) proving pool + cache + eviction are race-free and
    isolation holds under concurrency.

Slop/decomplect:
  - goja: a response with no explicit valid status now FAILS CLOSED (default 500,
    rolls the transaction back) instead of committing at a defaulted 200.
  - newID (gojabase) + randKey (dataroom): a crypto/rand failure now returns an
    error / fails the dispatch instead of a predictable time/zero fallback.
  - subsystems.go: removed 6 duplicate blank imports (pubsub, eval, exec, plan,
    plugin, pricing).
  - dataroom: unified on ONE tenant encoding — the object-store key prefix now uses
    gojabase.TenantSegment, matching the SQLite filename (was raw org).

Gate: go build ./... + go build -tags "libsqlite3 sqlite_fts5" ./cmd/cloud +
go test -race ./clients/{gojabase,captable,sign,dataroom}/... all GREEN.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 14:35:24 -07:00
hanzo-dev 47e141c3f3 feat(ai): meter EVERY inference at the one chokepoint — no exempt path
The metering decorator (metered_ai.go) wraps deps.AI so every chat + embed
call is authorized against the caller's org balance/budget/freeze BEFORE the
call and debited its billing account AFTER — the single DRY chokepoint through
which no inference runs unattributed. The billing scope (org, project) rides
the request value (ChatRequest/EmbedRequest), so it is compile-time impossible
to call AI without declaring who pays; no bypass, no side-channel key.

Closes the exempt holes — clients/code (index+search+ask), clients/knowledge
(search + index embeds), clients/crm (application screen) — all previously ran
the balance-exempt M2M path unmetered; each now threads org/project to the
chokepoint.

- types.AIClient.Embed takes *EmbedRequest (scope); ChatRequest carries
  Org/Project; ChatResponse surfaces token counts for exact metering.
- httpAI stays pure transport but surfaces resp.Usage tokens and stamps
  hanzo.org/hanzo.project on its gen_ai spans (feeds per-tenant o11y isolation).
- token-based micro-USD debit (CLOUD_AI_PRICE_UUSD_PER_1K, default $2/1M tok);
  metering.Usage gains AmountMicros so a sub-cent call meters exactly instead
  of rounding to zero and slipping through unbilled.
- reuses ResourceMeter over Deps.Metering — same per-org invariants; a
  transparent pass-through when commerce is unconfigured (dev never blocked).
- fixes a latent slice-1 test break (crm/agents AIClient fakes lacked Embed).
- tests: pricing, scope forwarding, system-call, ModelLister preservation.
2026-07-10 14:32:27 -07:00
zeekayandhanzo-dev a88f661206 fix(webui): /metrics is a console page, not an API 404 — drop it from apiPrefixes
The console catch-all 404'd /metrics because it was in apiPrefixes (the Prometheus
scrape-path convention). But the real Prometheus surface is on the SEPARATE ops
listener (:9090, healthMux); on the product API (:8000) /metrics is the console
MetricsModule page. Drop /metrics from apiPrefixes so it falls through to the SPA
shell. One surface per port: :8000 product+SPA, :9090 ops. (ServiceMonitor repointed
to the ops port in the same change.)

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 14:30:53 -07:00
zeekayandhanzo-dev 74bb668a1f feat(ha): reader-proxy edge + writer fcntl lease for zero-downtime cloud rolls
The cloud writer embeds an exclusive-lock ZapDB KMS store. A new probe
(clients/kms.TestConcurrentOpen_LiveWriterStoreIsNotROShareable) proves that
opening that store READ-ONLY while the writer is live FAILS ("Log truncate
required to run DB") — Badger's RO open replays the live memtable WAL and
refuses to truncate it. So the prior groundwork's assumption that a reader can
open the KMS store RO off the writer's PVC is false for a LIVE writer (only the
sequential close-then-reopen case worked). The audit SQLite store IS
concurrently shareable (audit/shareability_probe_test.go); the KMS store is the
one that is not, and every mutation is audited on the writer anyway.

Reader tier is therefore a transparent, always-ready reverse proxy (opens no
stores) to the single writer:
 - reader_proxy.go: CLOUD_ROLE=reader boots serveReaderProxy BEFORE BuildDeps —
   forwards every request to CLOUD_WRITER_URL, streams SSE, preserves inbound
   Host. Dial-only retry (retryTransport) absorbs the writer's roll gap: it
   retries ONLY when the connection was never established (no ready endpoint /
   refused), so a non-idempotent POST is never double-executed; bounded by
   CLOUD_READER_RETRY_BUDGET (default 25s) then 502.
 - The reader Deployment rolls RollingUpdate(maxUnavailable:0), so the edge
   Service always has a ready endpoint — this removes the ~30s console blip that
   the writer's Recreate/replicas:1 causes today.

Writer zero-gap roll (opt-in, default OFF = byte-identical Recreate):
 - writer_lease.go (+_unix/_other): CLOUD_WRITER_LEASE takes an exclusive fcntl
   flock on {DataDir}/.writer.lock BEFORE opening the RWO stores and releases it
   LAST at shutdown (after every store closes). A surge writer blocks until the
   old one releases, so the exclusive ZapDB/audit stores are handed off, never
   double-opened. Fail-closed on timeout.

Removes the dead ReaderGuard (the reader no longer runs the full pipeline; it is
the proxy). Unset CLOUD_ROLE + unset CLOUD_WRITER_LEASE ⇒ writer, byte-identical
to today.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 14:12:46 -07:00
hanzo-dev 57959fc491 Merge branch 'wt3/F' into wt3/integrate 2026-07-10 14:11:39 -07:00
hanzo-dev 37c44f6bcc feat(billing): GCP-style billing accounts — funding separate from org
BillingAccount is a funding entity separate from the org: it holds a spend
limit + level + freeze and funds 1..N of the org's projects (dedicated or
shared). A project resolves to its account via ProjectBinding; usage debits
carry Transaction.AccountId so an account's balance and calendar-month spend
sum from the SAME append-only ledger the balance gate + per-scope caps read —
no parallel ledger, no stored total, never drifts.

The authorize verdict layers an account cap + freeze on top of the per-scope
caps (most-restrictive-wins, fail-closed). Resolution is ALWAYS server-side
from the org namespace — the account is never a forgeable client header.
Backward-compatible: (org,"default") folds to the org-wide pool, so an org
with no account behaves byte-for-byte as before.

- models/billingaccount, models/projectbinding (+ hashid kinds 284/285,
  query reserved-kind list)
- Transaction.AccountId indexed ledger axis
- resolveAccountId + accountSpentCents + account cap/freeze in AuthorizeSpendCap
- real account + project-binding CRUD replacing the org-wrapper stubs
- tests: account cap, freeze kill-switch, dedicated-binding isolation,
  backward-compat pool fold
2026-07-10 14:07:31 -07:00
69c3ffed0d cloud: zip v1.3.0 — zap-proto/fiber engine, route precedence is now a framework guarantee (#244)
zip v1.2.1 -> v1.3.0 rides zap-proto/fiber v3.2.1 (gofiber v3.2.0 + native
ServeMux-1.22 specificity precedence: most-specific wins regardless of
registration order, ambiguous overlaps panic at registration, use/mount stay
declaration-ordered barriers). TestIAMKeysBeatsWildcard now passes as a
FRAMEWORK property — subsystem order-ints are no longer load-bearing for
route precedence (their init-ordering role remains; removal rides the
composition-root refactor). Also swaps the 6 direct gofiber test-file imports
to the fork (production code was already 100% behind zip).

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 13:44:13 -07:00
hanzo-dev 0e34afc12f feat(ai): embeddings via the one AIClient — org/project-aligned, no static key
Both semantic subsystems (clients/code, clients/knowledge) embedded via their own
static CLOUD_AI_API_KEY HTTP client — a side-channel credential separate from the
chat path, and the root of vectors:0 (the key was dead + entitlement-gated). Add
Embed() to types.AIClient and route both embedders through deps.AI — the SAME
client chat runs through, which authenticates with the IAM client-credentials
(M2M) token when no static key is set: ONE org/project-aligned identity, one way,
no static key to rotate. Emits gen_ai OTel spans so embeddings are observable end
to end like chat.

This is the ai-module leg of the canonical path
ingress -> gateway -> commerce -> ai module; metering + no-exempt + billing-on land
next on this seam. Supersedes the CLOUD_EMBED_* dedicated-provider detour.

- types.AIClient: + Embed(ctx, model, inputs)
- clients/aihttp: httpAI.Embed (raw POST reusing the static/M2M authed transport)
- clients/disabled, clients/rpc: stub Embed (fail-closed / not-wired)
- clients/code, clients/knowledge: embed through deps.AI; drop the static key path
- knowledge test: exercise the deps.AI seam (inject a deterministic fake embedder)
2026-07-10 13:19:47 -07:00
zeekayandhanzo-dev e34a2802a2 docs(o11y): reword LLM.md so the one-concept grep stays exact
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 13:03:21 -07:00
zeekayandhanzo-dev 322655eb73 refactor(o11y): collapse 5 subsystems -> ONE o11y; flat version-less paths (#71)
Decomplect the observability estate to exactly ONE top-level concept.

## 5 -> 1 registration collapse
The plane was FIVE separately-registered subsystems (o11yscope 69,
o11y-runtime 71, o11y-event-ingest 68, o11y-otlp-ingest 72,
o11y-trace-inproc 73) whose names leaked five public concepts (five config
toggles + five /v1/<name>/health routes). The k8s-style ordering was an
internal impl detail. They collapse to ONE
`cloud.RegisterWithShutdown("o11y", 69, mountO11y, shutdownO11y, HealthOwner)`:
mountO11y performs the ordered sub-mounts in-process (mountEventIngest ->
mountScope -> mountRuntime -> mountIngest -> mountTraceSink), so the PUBLIC
concept is a single `o11y`. Behavior is preserved EXACTLY — every specific
/v1/o11y/* route still registers inside the one order-69 mount, hence BEFORE
the upstream hanzoai/o11y wildcard (order 70), so Fiber's in-order match still
gives the specific routes precedence. The upstream module co-owns the `o11y`
name at order 70 (the wildcard); HealthOwner on this entry keeps /v1/o11y/health
registered exactly once (never a duplicate).

## Flat, version-less public surface (one /v1/, no nested /api/vN)
The upstream SigNoz engine version is an internal impl detail resolved inside
the handlers, never leaked into a route:
- /v1/o11y/vm/{query,query_range} (was /v1/o11y/vm/api/v1/*) — VM proxy; the
  upstream VM api/v1/* path stays INSIDE the handler (queryRaw). SuperAdmin
  gate + {up,sum(up),count(up)} allowlist unchanged.
- /v1/o11y/{query,query_range} (new, query.go) — the flat builder query;
  resolves to the v3 engine route SERVER-SIDE (the version-less alias would
  float to v5, which 400s the console's v3 composite payload), delegating to
  the same gated runtime handler the wildcard uses.

o11y stays EMBEDDED in-process (the everything-binary); OTLP ingest + trace
sink stay opt-in. Registers exactly one `o11y` in clients (grep-verified),
alongside analytics/evals/usage/audit.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 13:02:28 -07:00
fd308f4b8c cloud: dissolve commercesvc → commerce.Client (fold-finisher + decomplect) (#242)
Absorb the thin clients/commercesvc mount wrapper AND the fail-closed
clients/commerce_local.go stub into the in-tree commerce library, and expose
a real in-process commerce.Client — one package now owns the commerce library,
its /v1/commerce subsystem, and its cloud.CommerceClient, self-registered via
cloud's inversion hooks (the clients/kms pattern; cf. #241 gatewaysvc→gateway).
cloud never imports commerce, so there is no cloud⇄commerce import cycle.

commerce.Client (client.go): a real in-process types.CommerceClient. The former
stub failed CLOSED on every CheckEntitlement (the Phase-2 gap). It now resolves
org→active-subscription→plan-tier→license-features from commerce's OWN models +
the @hanzo/plans vocabulary:

  - org → namespace via commerce's canonical org.Resolve (the same binding the
    money path uses), so a read can never cross tenants;
  - active, unexpired subscriptions via a plain Status filter (matches commerce's
    own read idiom, so grant- and payment-created subs are both found);
  - plan tier → flat license features via a new plan.LicenseEntitlement seam that
    runs @hanzo/plans' toLicenseFeatures (the vocabulary stays in one place, not
    re-implemented in Go);
  - Active iff the plan's features carry "licensing.product:<id>".

MONEY-SAFETY: Active:true only for a real active sub whose real plan really
licenses the product. Every unresolvable piece (commerce not co-resident, org
unresolvable, subscription query error, plans vocabulary unavailable) returns an
ERROR → the entitlements gate treats it as "cannot verify ⇒ 503"; a clean
"no plan licenses this product" is Active:false (→ 402), never an error and never
a fabricated grant.

Decomplect: commerce.Mount takes a MountConfig VALUE (Brand/Env/DataDir/Domain)
+ a logger — the values it uses, not the whole cloud.Deps bag; mountFromDeps is
the one place Deps is narrowed and carries the PCI Payments/Vault warnings.

Network path preserved: pickCommerceClient still selects the ZAP-RPC/disabled
client when commerce is NOT enabled in-process (CLOUD_COMMERCE_ZAP_ADDR). This
fold does NOT force the live in-process cutover — that stays operator-gated.

Deleted: clients/commercesvc, clients/commerce_local.go(+test), the legacy
//go:build cloud clients/commerce/mount.go(+ its two tests), and the redundant
cmd/commerce --cloud boot path (cloud_boot.go/cloud_stub.go) — one way to serve
commerce inside cloud: the folded subsystem.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 13:02:00 -07:00
zeekayandhanzo-dev 3cdca83cc8 test(audit): prove store shareable by RO reader under live writer (HA carve)
Concurrent RO opener reads all records while the serialized writer appends;
writer chain stays intact and a fresh RW re-open recovers the head with no
fork/gap. Audit-store analog of clients/kms TestReaderReadOnlyRoundTrip.
Locks in the reader/writer shareability invariant the cloud HA carve depends
on. Test-only; zero runtime change (writer path byte-identical).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 12:54:13 -07:00
hanzo-dev 051b63d0db fix(embed): dedicated CLOUD_EMBED_* provider — unbraid embeddings from chat
The code + knowledge embedders read CLOUD_AI_BASE_URL/CLOUD_AI_API_KEY,
which are ALSO the chat/synth AIClient's config (config.go:308). That
braided embeddings onto the IAM-gated api.hanzo.ai path, whose /embeddings
403s customer keys and 401s gateway keys — only a superadmin JWT passes —
so the vector tier indexed vectors:0 platform-wide.

Split embeddings onto dedicated CLOUD_EMBED_BASE_URL / CLOUD_EMBED_API_KEY /
CLOUD_EMBED_MODEL, each falling back to the shared CLOUD_AI_* for back-compat.
Both semantic subsystems (clients/code + clients/knowledge) read the same
three vars — one embed config, orthogonal to chat. Deployment points them at
DigitalOcean GenAI (bge-m3 @1024-dim, first-party, not IAM-gated) via the
DO_AI_API_KEY already in cloud-api-llm-keys; chat stays on CLOUD_AI_*.
2026-07-10 12:09:15 -07:00
hanzo-dev 4b62d0981c fix(platform): preserve a kept secret on empty setEnv (never wipe KMS)
Secrets are write-only: toAppView masks a secret value to "" on read, so a client
editing env re-submits kept secrets with an empty value. sealSecretEnv now treats an
empty secret value as "keep the already-sealed value" — it is preserved, not resealed
to empty (which wiped the KMS secret). Only a non-empty value seals (and requires KMS).
Makes the masked-read -> setEnv round-trip a no-op for untouched secrets instead of a
data-loss footgun; unblocks the console env editor's Keep path. Adds a focused test.
2026-07-10 11:55:55 -07:00
f24801c715 cloud: drop svc suffix — clients/gatewaysvc → clients/gateway (#241)
The gateway subsystem package carried an "svc" suffix as a naming habit
only: there is no clients/gateway to collide with, and the package imports
no "gateway" library, so it renames cleanly to the plain domain name.

- git mv clients/gatewaysvc → clients/gateway (history preserved)
- gatewaysvc.go / gatewaysvc_test.go → gateway.go / gateway_test.go
- package gatewaysvc → package gateway; Mount() error strings + doc comment
  updated to gateway.*
- update the blank import in subsystems/subsystems.go and the doc comments
  in deps.go, middleware_edge.go, clients/gatewaypolicy/policy.go

commercesvc is intentionally NOT renamed in this PR. clients/commerce
already exists in-tree — the embedded upstream Hanzo Commerce library
absorbed by #114 (package commerce, ~1583 files) — and commercesvc.go
imports it as github.com/hanzoai/cloud/clients/commerce. Moving
clients/commercesvc → clients/commerce is therefore a directory-level
collision, not an import-alias shadow; re-aliasing does not free the path.
Renaming commerce cleanly needs the operator to decide the target name (or
relocate the embedded library), so it is flagged for follow-up, not forced.

Build: GOWORK=off CGO_ENABLED=0 go build ./...  → exit 0
Test:  GOWORK=off CGO_ENABLED=0 go test ./clients/gateway/... \
         ./clients/gatewaypolicy/... .           → ok

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 11:52:55 -07:00
hanzo-dev 99bec227da fix(platform): wire kmsIdentity (secret env) + mount platform,git in deploy enable list 2026-07-10 11:48:42 -07:00
zeekayandhanzo-dev 9b12e55d62 feat(o11y): SuperAdmin VM read proxy for the console infra-health board (#71)
The console's /metrics and /status SuperAdmin infra-health board read
VictoriaMetrics `up{}` via the console's Next.js `/telemetry/[...path]` route.
That server route is STRIPPED by the static-export embed (cloud go:embeds
console as output:'export'), so the browser call 404s — the last console error.

Add a same-origin, SuperAdmin-gated VM read proxy on the cloud `/v1` API that
serves the exact three queries the board issues, registered at o11yscope order
69 (before the o11y wildcard at 70):

  GET /v1/o11y/vm/api/v1/query?query=up
  GET /v1/o11y/vm/api/v1/query_range?query=sum(up)|count(up)&start&end&step

Security follows scope.go's contract ("the client never supplies a raw query"):
  - admin(c) gate (X-User-IsAdmin, reserved admin org) — 403 for everyone else.
  - The ?query param is ALLOWLISTED to exactly {up, sum(up), count(up)}; anything
    else is 400. Range args (start/end/step) validated as positive integers. No
    generic PromQL passthrough — this can never become an exfiltration/DoS surface.
  - VM's native Prometheus envelope is returned VERBATIM (c.Bytes) so the console's
    parseInstant/parseRange work unchanged. Reuses the existing newVMClient()
    (O11Y_VM_URL); adds vmClient.queryRaw for the verbatim forward.

Pairs with console 1beb6fca9 (telemetry.ts repoint). Verified: go build + go vet
clean on clients/o11y.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 11:47:37 -07:00
zandGitHub 1fa10831cc Merge pull request #240 from hanzoai/feat/114-absorb-commerce-source
feat(#114): absorb commerce source in-tree (clients/commerce) — one module, one binary
2026-07-10 11:32:50 -07:00
hanzo-dev 1c22329dfb feat(#111): billing money-path in-process — retire the standalone commerce hop
Every co-resident subsystem that spoke the commerce billing S2S surface over HTTP
to the standalone pod (commerce.hanzo.svc:8001) now dispatches straight into the
in-tree commerce handler (#114) — no socket, no serialization change. This is what
lets the standalone be retired.

- New seam clients/commerceinproc: commercesvc.Mount publishes the embedded
  commerce http.Handler (now carrying /v1/billing via api.Route) once at boot; a
  self-routing http.RoundTripper dispatches each S2S request to it in-process when
  co-resident, else falls back to plain HTTP (the pre-#111 split-deploy behavior).
  Behaviour-preserving: same path, same Bearer+X-Org-Id headers, same body/status
  bytes either way — proven by commerceinproc_test (in-process dispatch, HTTP
  fallback, base resolution).
- Converted: clients/{billing,account,admin,referrals,authors,affiliates,usage} —
  each keeps its OWN request-building + tenant subject-pinning (the security
  boundary is untouched); only the transport swaps. account keeps its shared
  httpClient for HUSD EVM JSON-RPC and routes ONLY commerce calls in-process.
- The request-edge METERING gate (build.go buildMeteringClient) debits the
  in-process handler; base pinned non-empty when co-resident so the gate never
  silently no-ops (free-money hole) even after CLOUD_COMMERCE_HTTP_URL is dropped.

GATES: go build ./... + cmd/cloud (sqlite tags) green; commerceinproc + all 8
converted packages' tests pass. LIVE money-parity gate (in-process vs standalone
balance/deposit/usage on shared Postgres + metering debits) precedes retiring the
standalone — that live cutover is gated, not in this commit.
2026-07-10 11:29:07 -07:00
hanzo-dev 848c28def5 feat(#114): absorb commerce source in-tree (clients/commerce) — one module, one binary
Move hanzoai/commerce out of the external-dep seam and INTO the cloud module,
so /v1/commerce (and, next, /v1/billing) is served by one repo, one binary, one
way. No external github.com/hanzoai/commerce* require remains.

Absorbed the EXACT versions cloud already compiled (behavior-preserving — not
main), copied from the module cache so the in-tree tree == what the live binary
built:
  - github.com/hanzoai/commerce            v1.46.40  -> clients/commerce
  - github.com/hanzoai/commerce/metering   v0.1.4    -> clients/commerce/metering
  - github.com/hanzoai/commerce/thirdparty/ethereum v1.40.0 -> clients/commerce/thirdparty/ethereum

- ONE Go module: removed the three nested go.mod/go.sum; commerce's deps merged
  into cloud/go.mod via `go mod tidy` (MVS keeps the highest existing patch — the
  single major conflict, luxfi/zap, already resolved to cloud's v1.2.1 in the old
  build, so nothing recompiles differently). New direct deps discovered by tidy:
  huandu/facebook, square-go-sdk/v3.
- Imports rewritten repo-wide: github.com/hanzoai/commerce* ->
  github.com/hanzoai/cloud/clients/commerce* (1103 files: the absorbed tree +
  cloud's own build.go/deps.go/middleware_billing.go/clients/{bots,functions}/…
  metering importers). commercesvc leaf now imports the in-tree package.
- Excluded the app/ frontend pnpm workspace (59M, NOT referenced by any .go —
  the built ui/dist + billing/ui/dist + checkout/ui/dist that Go //go:embed's are
  kept). //go:build cloud files kept (excluded from the plain build as before).

GATES (all green):
  go build ./...                                   -> ok
  go build -tags "libsqlite3 sqlite_fts5" ./cmd/cloud -> ok (633MB binary boots)
  go test ./clients/commercesvc/... ./clients/commerce/{,datastore,api/billing}  -> ok
  go test -run 'Billing|Metering|SpendCap|Commerce' .  -> ok
2026-07-10 11:13:14 -07:00
hanzo-dev 04e245bdbd Merge branches 'wt3/B' and 'wt3/C' into wt3/integrate 2026-07-10 11:11:22 -07:00
hanzo-dev 225432b1a8 refactor(admin): adopt cloud.Service[state], drop per-package svc 2026-07-10 11:09:43 -07:00
hanzo-dev ea02c3baf0 refactor(ml): adopt cloud.Service[state], drop per-package svc 2026-07-10 11:08:54 -07:00
hanzo-dev 9bda7878af refactor(affiliates): adopt cloud.Service[state], drop per-package svc 2026-07-10 11:06:59 -07:00
hanzo-dev a7e67f1608 refactor(do): adopt cloud.Service[state], drop per-package svc 2026-07-10 11:03:59 -07:00
hanzo-dev 48cdbcc8e3 Merge branch 'main' into wt3/integrate 2026-07-10 11:03:17 -07:00
hanzo-dev 77317b55fe refactor(tracker): adopt cloud.Service[state], drop per-package svc 2026-07-10 11:00:06 -07:00
hanzo-dev 0b7c6cfbdc Merge branch 'wt3/G' 2026-07-10 10:59:09 -07:00
hanzo-dev 8184b97c35 Merge branch 'wt3/D' 2026-07-10 10:59:01 -07:00
hanzo-dev 76c73ffa68 refactor(treasury): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:58:36 -07:00
hanzo-dev d96c00fe2c Merge branch 'wt3/E' 2026-07-10 10:58:23 -07:00
hanzo-dev 6e1e87b371 refactor(framework): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:58:04 -07:00
hanzo-dev a1e556227e refactor(paas): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:57:45 -07:00
hanzo-dev 85795b85c6 refactor(automations): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:57:01 -07:00
hanzo-dev ecc622d888 Merge branch 'wt3/H' 2026-07-10 10:56:11 -07:00
hanzo-dev 2f6ce9a24f refactor(wallets): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:56:03 -07:00
hanzo-dev 54a7f43263 refactor(platform): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:55:07 -07:00
hanzo-dev 04371fc01f refactor(ingress): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:54:49 -07:00
hanzo-dev 218d3c3cee Merge branch 'wt3/A' 2026-07-10 10:54:04 -07:00
hanzo-dev 4c55806a97 refactor(crm): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:53:35 -07:00
hanzo-dev 64c8b3e44f refactor(storage): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:52:53 -07:00
hanzo-dev 8a4aca362b refactor(agents): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:52:40 -07:00
hanzo-dev 62c9ab5f47 refactor(sbom): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:51:55 -07:00
hanzo-dev 3380848531 refactor(dataroom): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:49:35 -07:00
hanzo-dev 48d9b15713 refactor(git): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:49:27 -07:00
hanzo-dev 6bf3cdb262 refactor(sign): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:48:48 -07:00
hanzo-dev 3aa53f2a29 refactor(projects): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:48:43 -07:00
hanzo-dev 9888189c5f refactor(integrations): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:47:19 -07:00
hanzo-dev aff2a55469 refactor(authors): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:46:54 -07:00
hanzo-dev 3861d68904 refactor(graph): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:46:37 -07:00
hanzo-dev 7abfdb8718 refactor(kms): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:46:22 -07:00
hanzo-dev 787ad3a6fb refactor(functions): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:46:02 -07:00
hanzo-dev 38c6795a73 refactor(provisioning): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:45:26 -07:00
hanzo-dev ec180f5366 refactor(account): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:43:16 -07:00
hanzo-dev dad7ec6aa1 refactor(analytics): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:42:02 -07:00
hanzo-dev 6205664012 refactor(zt): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:40:59 -07:00
hanzo-dev 496f176d77 refactor(visor): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:39:47 -07:00
hanzo-dev 46091d2098 refactor(referrals): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:39:41 -07:00
hanzo-dev 6809e4d574 refactor(captable): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:39:40 -07:00
831742eb3c fix(deps): pin hanzoai/beego/v2 to tag v2.4.1 (kill controlplane-containment shallow-clone flake) (#239)
cloud pinned beego at a PSEUDO-VERSION
(v2.4.1-0.20260710093857-0ad99bdf8b90). A pseudo-version forces `go` to
resolve the dep via a live VCS fetch-by-commit-hash into the shared ARC
GOMODCACHE cache/vcs. Parallel containment jobs racing that shallow bare
repo hit `fatal: shallow file has changed since we read it` → intermittent
FAIL, which has forced admin/green-locally squash-merges (#235, #236) and
defeated the containment gate.

beego HEAD (0ad99bdf) is exactly one benign commit past tag v2.4.0 (silences
a missing-default-app.conf stderr warning, beego#29). Cut that commit as a
proper patch tag v2.4.1 and pin to it — byte-identical code, but `go` now
fetches the immutable refs/tags/v2.4.1 ref instead of shallow-fetching a
bare commit, so no cache/vcs race. beego is private (no module-proxy), but
the tag ref path is deterministic and does not trip the shallow-file check.

go.sum regenerated via `go mod tidy` (authentic v2.4.1 hash). `go build ./...`
green. iam stays on tag v2.3.10 (already a tag, not a pseudo-version).


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 10:39:12 -07:00
hanzo-dev 249dd7a5da telemetry: declare the host tracer provider to embedded ai (gen_ai spans -> o11y)
cloud installs the ONE global tracer provider wired to the o11y in-process trace
sink, but in in-process-sink mode it sets no OTLP/ZAP exporter endpoint. The
embedded hanzoai/ai module then found no endpoint and DISABLED its gen_ai span
emit, so the gen_ai plane in o11y_traces was dark (cloud's own request spans
flowed; every LLM call's gen_ai span was gated off).

After otel.SetTracerProvider, call aiobject.AdoptHostTracerProvider() so ai emits
every gen_ai span through THIS provider -> the o11y in-process sink -> o11y_traces.
Repins ai to the branch carrying AdoptHostTracerProvider. The OTLP-env unset stays
as orthogonal defense against any other lib forking a competing provider.

ai: github.com/hanzoai/ai v1.804.1 -> v1.804.2-0.20260710172916-723e03f81bca
2026-07-10 10:38:51 -07:00
hanzo-dev fe9f67582c refactor(billing): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:37:09 -07:00
hanzo-dev 3b07f84380 refactor(bots): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:36:03 -07:00
hanzo-dev f6f8592a33 refactor(security): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:35:49 -07:00
hanzo-dev 26b6cab29c refactor(team): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:35:49 -07:00
hanzo-dev 8686a11769 refactor(knowledge): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:35:00 -07:00
hanzo-dev d9bfa35b00 refactor(prompts): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:33:58 -07:00
hanzo-dev 9a65c02be4 refactor(templates): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:33:18 -07:00
hanzo-dev 9a2f0e5cfd refactor(gatewaysvc): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:32:10 -07:00
hanzo-dev 5f299546f7 refactor(auditlog): adopt cloud.Service[state], drop per-package svc 2026-07-10 10:31:20 -07:00
hanzo-dev e7fd53820f feat(cloud): export cloud.NewBase for complex-Mount subsystems
Simple subsystems use one-line cloud.Mount[S]. Subsystems whose Mount is more
than build+routes (background reconciler, package-global for cross-package hooks,
shutdown cancel — e.g. platform) construct the Service value directly with
cloud.NewBase + &cloud.Service[state]{...} and wire routes via Handle — still the
ONE generic type, one Base derivation.
2026-07-10 10:25:53 -07:00
hanzo-dev db5b8e9b56 feat(cloud): one generic subsystem type — cloud.Service[S], kill per-package svc
The ONE server abstraction: a subsystem is cloud.Base (shared deps derived once:
Log/KMS/Bill/Brand/Env/Domain/DataDir) + its own typed State. Handlers are FREE
FUNCTIONS func(*Service[S], *zip.Ctx) error bound with cloud.Handle — so a package
declares NO service/receiver type, only its State (plain data) and its handlers.
cloud.Mount[S] is the one generic entrypoint (build state, wire routes).

Pike minimalism: generics carry the state type, functions carry behaviour. Kills
the 'type svc struct{ …re-plumbed deps… }' shape copied ~40×.

Proven on clients/usage: svc type gone, log via embedded Base (s.Log), commerce
reader in State (s.State.commerce), all handlers/helpers free functions. Build +
vet + test green, routes + tenant isolation unchanged.
2026-07-10 10:25:53 -07:00
ccb925d474 feat(#105): un-stage commerce (in-binary /v1/commerce) — DRAFT, gated on cutover prep (#237)
* feat(#105): un-stage commerce — serve /v1/commerce in-process from the one binary

Phase 2 final step (tasks #96#105). commerce was the last staged
in-process subsystem; drop it from stagedSubsystems so the mount-all default
serves /v1/commerce (+ /_/commerce) from the cloud binary instead of proxying
to the standalone commerce pod. iam + ingress STAY staged (the IAM embed
corrupts its own Beego bootstrap under mount-all).

commerce owns the money path, so the cutover is data-neutral BY CONSTRUCTION:
the authoritative stores stay put and shared — balances/deposits/credits live
in Hanzo SQL (SQL_URL), analytics in DATASTORE_URL, blobs in S3 — and the
in-process commerce.Embed reads the SAME stores via the SAME backend env the
standalone CR carried. Only the small per-org merchant SQLite + tenant `base`
tree migrate into the cloud data dir. No money is copied or split.

Tests: go test -run TestEnabled ./  → ok (staged contract: commerce now mounts
under the empty-Enable default; iam/ingress still gated to explicit CLOUD_ENABLE).

Also gofmt: fixes a pre-existing struct-literal misalignment in LoadConfig.


* fix(commercesvc): isolate in-process commerce data under {DataDir}/commerce

In-process commerce writes orgs/ and base/ under its DataDir. cloud sets
deps.DataDir=/var/lib/cloud, where cloud ALSO owns /var/lib/cloud/orgs (its
own per-org subsystem SQLite, HIP-0302) and /var/lib/cloud/base (its Base/IAM
store) — verified live. Sharing the root would open two apps on the same
SQLite files (base/data.db) and corrupt them. Always nest commerce under
{deps.DataDir}/commerce (was only the empty-DataDir fallback), keeping the
commerce ledgers physically separate on the same cloud-api-data PVC. This is
the target path the #105 data migration copies the per-org merchant SQLite +
tenant base into.


---------

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 10:05:20 -07:00
hanzo-dev c1cf59020c Merge branch 'wt2/preview' 2026-07-10 10:01:28 -07:00
hanzo-dev 194f5c1218 Merge branches 'wt2/bots' and 'wt2/gateway' 2026-07-10 10:01:11 -07:00
hanzo-dev b40226e347 cloud(platform): preview deployments + promote + rollback 2026-07-10 10:00:38 -07:00
hanzo-dev 8d6e68b9ff cloud(gateway): per-org edge config — cache TTL + CORS + rate, org-scoped round-trip 2026-07-10 09:59:20 -07:00
hanzo-dev 00f0916b31 cloud(bots): POST /v1/bots/run — launch a computer-using agent, return VNC session 2026-07-10 09:56:41 -07:00
hanzo-dev 609f578b27 feat(git): mirror external repos into the embedded git server + self-host cloud's own repo 2026-07-10 09:50:22 -07:00
hanzo-dev 633163aa1a feat(platform): native release semantics on /v1/runner (retires release.yml build/tag/notify) 2026-07-10 09:48:41 -07:00
hanzo-devandGitHub 4660a1c8d2 fix(code): normalize embedder base to /v1 — deployed CLOUD_AI_BASE_URL lacks /v1, so /v1/code semantic tier posted to /embeddings (405) → vectors:0. Append /v1 when absent; ask/RAG now works. (#238) 2026-07-10 09:46:47 -07:00
hanzo-devandGitHub 1b9939a54f fix(code): normalize embedder base to /v1 — deployed CLOUD_AI_BASE_URL lacks /v1, so /v1/code semantic tier posted to /embeddings (405) → vectors:0. Append /v1 when absent; ask/RAG now works. (#238) 2026-07-10 09:46:21 -07:00
297ea6bf6a feat(sbom): registry pull-on-miss — materialize attached SBOMs into ClickHouse (#77) (#236)
The consumer half of the SBOM datastore lane. The registry is the source of
truth: CI produces the CycloneDX SBOM and `cosign attach`es it to the image
digest. Cloud now PULLS that attached artifact and materializes its components
into the global hanzo.sbom_component table — no CI push-ingest.

clients/sbom/pull.go (new): registry pull with go-containerregistry (pure-Go,
no binary deps). Resolves ref→digest, locates the CycloneDX SBOM by the cosign
SBOM tag (sha256-<hex>.sbom) first, OCI 1.1 referrers second, and parses it
through the SAME parseComponents the POST /v1/sbom path uses (one flattener).

Triggers:
- Pull-on-miss: GET /v1/sbom/{ref} with 0 rows and an image ref pulls the
  attached SBOM, upserts it, and rereads FINAL — the console goes live with no
  console change (the panel already GETs by repository:tag).
- Deploy-time: platform applyLive fires sbom.Prefetch(ref) async when a
  deployment goes live (best-effort, idempotent; platform→sbom, one direction).

go.mod: + github.com/google/go-containerregistry v0.21.7 (direct), authentic
go.sum via go mod tidy.

Tests: hermetic end-to-end over a real in-memory OCI registry (cosign tag +
OCI referrers + no-attachment + bare-digest), all green with -race. Plus an
env-gated live end-to-end (pull_live_test.go) proven against registry:2 + real
ClickHouse serving a real cyclonedx-gomod SBOM: GET → pull-on-miss → production
pullSBOM → parse → INSERT → reread → 200 with the real components + cache hit.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 09:34:28 -07:00
hanzo-dev 2208539090 feat(platform,git): git-push-to-deploy — a push triggers a native build
A push landed on the embedded git server (clients/git) now fires a build
for every app that tracks that repo+branch — no GitHub, no Actions.

- build.go: GitPushEvent + RegisterPushBuilder/OnGitPush — the same
  package-level inversion as kmsClientFactory, so git never imports
  platform and there is no git<->platform cycle.
- clients/git/smart_http.go: after a push lands (post-metering),
  firePushBuilds fires OnGitPush for each branch ref that advanced
  (tags + deletes skipped). Best-effort: a trigger failure is logged,
  never fails the push the client already committed.
- clients/platform/push.go: buildFromPush resolves every git-source app
  whose RepoURL+branch matches the pushed ref and launches a build via
  the ONE shared build-launch core.
- clients/platform/deploy.go: extract startGitBuild (ctx-only) as that
  single core; deployGit maps it onto the HTTP deploy, buildFromPush onto
  the push trigger — one build-launch path, no duplication.
- clients/platform/validate.go: the cloud's own embedded-git apex
  (deps.Domain) is always a trusted build source, so a self-hosted-git
  app builds with no env — host all repos on our own git, not GitHub.

Tests: TestPushFiresBuildTrigger (real go-git push -> OnGitPush fires with
org/repo/branch/commit/cloneURL), TestBuildFromPush_{LaunchesMatchingApp,
NoMatchIsNoop,IgnoresImageApp}. Full platform + git suites green.
2026-07-10 09:26:32 -07:00
zandGitHub bde5c47ddc fix(team): remap migrated-workspace socialId to deterministic person on connect (#235)
Jul-5 team-go→cloud migrated workspaces threw "Confirmed social identity is attached to the wrong person" on transactor connect: the confirmed hanzo:<account> SocialIdentity was still attached to a team-go-era Person id, not the deterministic person-<account>. reconcile() now runs remapMigratedSocialIds(uid) to re-point it — migrated-only, idempotent, non-destructive. CI red check (controlplane-containment) is an unrelated shared-runner Go module-cache flake on hanzoai/beego; fix is clients/team-only and green locally (go build ./..., make build, go test/-race/vet/gofmt).
2026-07-10 09:25:49 -07:00
zeekayandhanzo-dev ae49159652 fix(o11y): edge-trusted local authz in the embed (o11y v1.5.10)
Set O11Y_AUTHZ_PROVIDER=local so the in-process o11y authorizes org-scoped,
gateway-authenticated users locally instead of round-tripping to an external IAM
Casbin enforcer the one-binary has no credentials for. That round-trip was 401ing
every /v1/o11y read (provision Grant -> add-policy authz_unavailable), breaking the
console overview-metrics widgets on ~9 secondary product pages. Same enforced
policy; tuples in-process. Bumps o11y 1.5.9 -> 1.5.10.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 08:49:11 -07:00
zeekay acd6614c72 deps: bump hanzoai/o11y v1.5.8 -> v1.5.9 (surface swallowed IdentN errors — diagnose o11y read 401) 2026-07-10 08:25:36 -07:00
zeekayandhanzo-dev 8d0f6f3686 deps: bump hanzoai/o11y v1.5.7 -> v1.5.8 (role-selector digits — fix o11y-admin grant panic)
v1.5.8 allows digits in TypeRole selectors, unbreaking the built-in o11y-admin role
grant that panicked (→500) on EVERY authenticated embedded o11y data read. Completes
the o11y-telemetry fix (v1.5.6 aliases + v1.5.7 /api passthrough + v1.5.8 grant):
/v1/o11y/{query_range,services,rules,dashboards} now resolve for the console
overview-metrics widgets.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 06:24:50 -07:00
zeekayandhanzo-dev 18a4814c84 deps: bump hanzoai/o11y v1.5.6 -> v1.5.7 (embedded /api/* passthrough — fix o11y data 404s)
v1.5.7 routes /api/*-prefixed paths straight to the router in the ExternalPath wrapper,
fixing the double-strip that 404'd EVERY embedded o11y data call. With v1.5.6's
version-less aliases, /v1/o11y/{query_range,services,rules,dashboards}+/metrics now
resolve — fixes the console overview-metrics widgets on studio/gateway/cli/registry/
desktop/console/dashboards/alerts/metrics.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 05:26:55 -07:00
zeekayandhanzo-dev 0eee4c5f6a deps: bump hanzoai/o11y v1.5.5 -> v1.5.6 (version-less /v1/o11y/<resource> aliases)
v1.5.6 registers the version-less /api/<resource> aliases on the app.Server router
the embedded runtime uses (o11y e01015954), so the console's /v1/o11y/{query_range,
services,rules,dashboards} + /metrics resolve instead of 404 — fixes the o11y-telemetry
overview widgets on studio/gateway/cli/registry/desktop/console/dashboards/alerts/metrics.
Also folds in the v1.5.5 C1 cross-tenant llmobs read fix.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 04:37:05 -07:00
28f4698d24 config: keep commerce staged (money-path data migration required first) (#234)
captable/sign/dataroom stay un-staged — their standalone stacks held no live
data. commerce owns real transactional data + the money path (commerce-api /
pay / webhooks + credit-deposit flow); un-staging split-brains /v1/commerce onto
a fresh in-process dataset. Proxy the authoritative standalone until commerce's
in-binary cutover (data migration + money-path repoint + cron) is done properly.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 04:21:35 -07:00
zeekayandhanzo-dev 4326d2a447 fix(zt): networks/edge READS return empty-200 when ZT unconfigured (not gate 503)
The prior fix degraded the orgRouters-error path, but zt's gate() fail-closes with
503 BEFORE that when ZT_CLIENT_ID/SECRET are unset — so /networks + /edge still 503'd
a console error on every load. Short-circuit the two READ handlers to an honest-EMPTY
list (200) when unconfigured, ahead of the gate. WRITES keep the fail-closed 503.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 03:57:05 -07:00
066aa15853 fix(hanzo): control-plane verbs emit no server-init noise (#231)
Every `hanzo` control command (version, whoami, config, apps, login, …) printed
three lines of server-mode init chatter first:

  init global config instance failed ... open conf/app.conf: no such file...
  failed to load persistent registry signing key: KMS_SERVICE_TOKEN ... required
  generating ephemeral registry signing key for non-production runtime

These come from dependency package init() functions that run before main(), so
main.go's client-vs-server branch cannot gate them, and Go's alphabetical
package-init order (beego < cloud < iam) means no cloud-side os.Stderr swap can
pre-empt them — verified with an init-order probe. Masking the output would also
leave a wasteful KMS fetch + RSA keygen firing on every CLI call. Fixed at the
source instead:

  - hanzoai/iam#117: registry signing key resolved lazily (sync.Once) at its use
    sites, not in package init(); server token paths keep identical semantics,
    the CLI never touches KMS or generates a key.
  - hanzoai/beego#29: the benign conf/app.conf probe is silent when the default
    file is absent (the CLI case), loud only on a present-but-broken file.

Bump both deps to the fixed versions and document the quiet-output invariant at
the CLIENT MODE gate in cmd/hanzo/main.go.

Result: `hanzo version|whoami|config path|apps --help` emit ZERO stderr; server
subcommands (`hanzo ai --help`, serves) initialize unchanged.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 03:42:39 -07:00
9cf947e722 config: phase-2 flip — un-stage commerce/captable/sign/dataroom (serve from the one binary) (#232)
All four are folded in-process and validated on cloud-unified-canary
(v1.786.167): commerce embedded, captable/sign/dataroom "mounted in-process
(goja + per-tenant Base)", /v1/{commerce,captable,sign,dataroom}/health all 200.
Dropping them from stagedSubsystems makes the mount-all default serve them, so
the main cloud (empty CLOUD_ENABLE) runs them natively and their standalone
Postgres/Next pods retire. iam + ingress stay staged (IAM embed corrupts its own
bootstrap under mount-all; iam served by the standalone pod).


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 03:38:19 -07:00
zeekayandhanzo-dev 0bd907594b fix(graph,zt): degrade indexer/oracle/network/edge reads to honest-empty (no 502/503 page errors)
console.hanzo.ai /indexer, /oracles, /networks, /edge fired 502/503 console errors
because these list handlers returned the upstream error when the chain indexer /
price-feed oracle / ZT controller is unreachable or unconfigured (ZT_CLIENT_ID
optional). Same graceful fold already shipped for visor clusters/machines/gpus:
log + return an honest-EMPTY list (200). An empty list is honest (you have none),
never fabricated; ZT WRITES stay fail-closed. Clears the console errors on 4
secondary product pages for every org without those backends deployed.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 03:25:15 -07:00
75e8ef9c03 cloud: remove /v1/console/* namespace — routes to their real domains (keys/onboard→/v1/iam) (#227)
"console" is just our cloud FE name; there must be NO /v1/console/* API domain.
Rename clients/console → clients/account and re-home every route onto its REAL
domain, forwards-only (no /v1/console aliases, no compat shim):

  keys   GET/POST/DELETE  /v1/console/keys        → /v1/iam/keys
  onboard POST            /v1/console/onboard      → /v1/iam/onboard
  csrf   GET              /v1/console/csrf         → /v1/csrf
  embed-status GET        /v1/console/embed-status → /v1/embed-status
  topup  POST             /v1/console/topup/wallet → /v1/commerce/topup/wallet
  health                  /v1/console/health       → dropped (generic /v1/<name>/health)
  waitlist                /v1/console/waitlist     → dropped (SPA uses clients/base /v1/waitlist)
  billing/commerce bridges /v1/billing/*,/v1/commerce/*  paths unchanged, relocated

The same handlers, CSRF protection (requireCSRF), per-IP rate limiting, and the
VALIDATED-principal tenancy are preserved — only the PATHS change.

IAM wildcard ordering: keys/onboard live on /v1/iam/*, which clients/iam (order 50)
mounts as a WILDCARD. The package registers TWO subsystems so the specific routes win
Fiber's first-match scan: `account` (order 48) mounts /v1/iam/{keys,onboard} + /v1/csrf
+ /v1/embed-status + /v1/commerce/topup/wallet BEFORE the wildcard (and before the
commerce embed at 100); `account-bridge` (order 122) mounts the /v1/billing/* +
/v1/commerce/* catch-all bridges AFTER clients/billing (121) + the commerce embed (100).
Both share one svc + a process-wide CSRF key so a /v1/csrf token verifies on the bridge
writes. Proven by TestIAMKeysBeatsWildcard (native /v1/iam/keys beats the wildcard;
/v1/iam/oauth/token still falls through) and TestRegisteredOrders (account<50, bridge=122).

waitlist.go/waitlist_test.go deleted; httpClient relocated to topup.go. All 54 tests
pass; go build ./... green.

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 03:24:55 -07:00
557de3b002 feat(dataroom): fold dataroom into cloud in-process on gojabase (#101) (#230)
Fold hanzoai/dataroom (Papermark fork: Next.js + Prisma + Postgres) FULLY into
the unified cloud binary via the gojahost pattern (HIP-0106, task #101 / epic
Postgres, no Next.js.

REUSE the shared binding, don't build a second. clients/dataroom runs the
self-contained dataroom goja bundle (byte-identical to hanzoai/dataroom/goja/
bundle.js, go:embed) on the REUSABLE clients/gojabase host — the SAME RW-Base
binding captable (#97) pilots and esign (#100) reuses — which injects
__db/__newId/__now, opens one SQLite file per tenant, and runs each dispatch in
one transaction (commits iff status<400). The leaf adds only: the per-tenant
Schema (schema.go), the object-storage seam for document bytes, a bcrypt HostFn
for link passwords, and the public link->org index. Zero domain logic in Go.

gojabase gains ONE generic, domain-free seam — Config.HostFns — the extension
point esign/dataroom both reach for (dataroom injects __bcrypt; the reserved
__db/__newId/__now always win). captable is unaffected (nil HostFns).

Storage: document BYTES go through the cloud object-storage seam (deps.VFS — the
S3/SeaweedFS data plane, a Go storage host-fn in the leaf, NOT local FS); the
bundle persists only the opaque key. View-analytics events (page-by-page
tracking) are Base rows in the tenant DB.

Auth: admin routes require a validated cloud principal (principal.Tenant -> org);
public viewer routes resolve their org from the link index. Passwords hashed with
bcrypt in Go — never plaintext. Registered order 134, HealthOwner, STAGED behind
CLOUD_ENABLE. go.mod unchanged.

Proof (clients/dataroom/flow_test.go, in-process over real per-tenant Base + the
VFS seam): create dataroom -> upload document (bytes to storage) -> attach ->
create email+password-gated share link -> open as public viewer -> authenticate
(wrong password 401, disallowed email 403) -> record per-page views -> analytics:
  {"pages":[{"pageNumber":1,"views":2,"totalDuration":6000,"avgDuration":3000},
            {"pageNumber":2,"views":1,"totalDuration":900,"avgDuration":900}],
   "totalPageViews":3,"totalViews":1}
plus viewer byte download round-trip and cross-org isolation. Live binary boots
with CLOUD_ENABLE=dataroom, mounts in-process, health 200, admin 403 fail-closed.

Companion bundle PR: hanzoai/dataroom#6.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 03:09:22 -07:00
fd9980325a feat(sign): fold hanzoai/sign into cloud via the reusable gojabase host (task #100) (#229)
Fold the esign product (Documenso fork — open-source DocuSign) FULLY into the
unified cloud binary, per HIP-0106 (epic #96, task #100). Cloud serves /v1/sign/*
itself — the TS domain on dop251/goja backed by per-tenant Hanzo Base/SQLite. No
Next.js, no Prisma, no Postgres. Reuses the SAME clients/gojabase RW-Base binding
the captable pilot (#96) established — ONE binding, not a second.

clients/gojabase: add an additive, backward-compatible Config.HostFns passthrough
— extra native host globals injected per dispatch alongside __db/__newId/__now.
esign uses it for __pdf; captable is unchanged (tests green).

clients/sign (leaf on gojabase):
  - schema.go — the per-tenant sign.db DDL (gojabase Config.Schema).
  - signer.go — THE HARD PART as Go host-functions injected via HostFns as
    __pdf = { stamp (pdfcpu renders field values onto the PDF), sign (real
    x509/PKCS#7 seal via digitorus/pdfsign) }; signer sourced from KMS PEM,
    persisted PEM, or a self-signed dev cert. Signing orchestration stays TS.
  - sign.go — Mount + route table; owner routes gated by principal.Tenant,
    recipient token routes org-in-path. Registered + STAGED behind CLOUD_ENABLE
    (config.stagedSubsystems); retires the standalone esign pod on cutover.
  - sign_test.go — end-to-end wire proof: create→recipient→fields→send→sign→
    complete seals a REAL signed PDF (/ByteRange,/Type /Sig,PKCS7) + full audit,
    per-tenant Base-backed, with cross-tenant isolation.

Bundle: github.com/hanzoai/sign (goja/bundle.js) — the ESM-free domain port on
the gojabase contract (__db/__newId/__now/__pdf, handle{route,params,query,orgId,
body}, one txn per dispatch). go.mod additive; pdfcpu pinned v0.11.0,
hhrutter/pkcs7 v0.2.0 (no bumps).


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 03:06:27 -07:00
hanzo-dev afd7b4f5ff release: cloud v1.786.166 — org-scoped o11y (C1) + BYO billed_cost (C3)
Ship the crown-jewel security fix: o11y v1.5.5 (org-scoped llmobs span views — closes
the cross-tenant read exposed by the Observe->/v1/o11y repoint) + ai v1.804.1 (BYO
billed_cost). The leaky observation read is already deleted upstream (#217); this repin
ships the org-scope via the cloud-embedded o11y runtime.

(Coordinator asked for v1.786.162 but that tag + through v1.786.165 were already cut on
origin; this is the next free tag.)
2026-07-10 02:52:34 -07:00
hanzo-dev 5f0320bf56 fix(security): repin o11y v1.5.5 (org-scoped llmobs) + ai v1.804.1
Crown-jewel security repin off the pseudo-versions to the merged release tags:
- o11y v1.5.4 -> v1.5.5: the llmobs span-view SQL is now org-scoped
  (gen_ai.hanzo.org_id = <validated tenant>, fail-closed) — closes the cross-tenant
  read the Observe->/v1/o11y repoint exposed. Cloud EMBEDS the o11y runtime
  (clients/o11y), so this is the ship vehicle for the fix.
- ai <pseudo> -> v1.804.1: gen_ai span emits _o11y.gen_ai.billed_cost alongside
  total_cost (BYO invoice reconciliation) + the enriched gen_ai span.

The leaky cloud_usage-as-observations read stays DELETED (upstream via #217); the
metering warehouse (cloud_usage via /v1/usage + the #218 /v1/evals/metrics dashboard)
is untouched. No go mod tidy (luxfi/keys go.sum fragility) — only the two repins.
Build: go build ./... green. Test: clients/eval + clients/o11y green.
2026-07-10 02:52:22 -07:00
8e0a3892ce feat(captable): fold Captable,Inc into cloud via goja + reusable Base binding (#96 pilot) (#228)
Cloud now serves /v1/captable/* ITSELF, per tenant, on Base/SQLite — the PILOT of
epic #96 (fold the Captable,Inc app into the unified binary; drop Next.js/Prisma/
Postgres). Where clients/plan + clients/pricing host a read-ONLY @hanzo catalog in
goja, captable hosts the tRPC business LOGIC (ported to a self-contained goja
bundle in github.com/hanzoai/captable) and gives it PERSISTENCE over per-tenant
Base/SQLite. The bundle carries logic; the Go host carries storage.

REUSABLE Base-goja binding (clients/gojabase) — the deliverable esign (#100) +
dataroom (#101) rebase onto. It is the storage-bearing sibling of clients/goja
(the pure JS engine): given a Bundle + a per-tenant Schema (DDL) + DataDir, it
- opens ONE SQLite file per tenant (lazy, migrated once, cached; slug-contained),
- injects per dispatch a tenant-bound __db bridge (query/exec) + __newId + __now,
- runs globalThis.handle inside ONE transaction that commits iff status<400 and
  handle didn't throw (atomic multi-statement mutations for free), and
- carries ZERO domain logic. clients/goja gains DispatchWith (per-call native
  globals) as the read-WRITE extension of the read-only plan/pricing path.

clients/captable leaf: go:embed'd bundle (hanzoai/captable.Bundle) + the per-
tenant schema (Prisma model → SQLite DDL) + a company seed (OnOpen) + the
/v1/captable/* zip routes. Org resolves from the VALIDATED principal
(principal.Tenant), never a client header; that org selects the DB file AND
scopes every row. Registered order 133; STAGED behind CLOUD_ENABLE (joins iam/
ingress/commerce in config.stagedSubsystems) so main stays shippable and the
standalone captable service keeps authority until the phase-2 cutover.

Full fold over Base: stakeholders, share classes, equity plans, securities
issuance (shares + options), share transfers (full + partial, atomic), SAFEs +
convertible notes, rounds + investments (a priced round issues shares and
dilutes), and a computed cap table (fully-diluted ownership, per-class
authorized-vs-issued, convertibles + rounds summary).

Proven:
- clients/gojabase: RW round-trip, per-request rollback (caught-500 + raw-throw),
  per-tenant isolation, OnOpen seed, slug traversal-containment (real SQLite).
- clients/captable: the REAL embedded bundle vs REAL SQLite through the whole
  lifecycle (create stakeholder → issue share class → issue shares → priced round
  + investment dilution → transfer → cap table), and an HTTP wire test via the
  zip/Fiber test client (trusted headers) proving create→read-back, issuance→cap
  table, the bundle's OWN 404 (not a proxy 502), the 403 principal gate, and
  cross-tenant isolation.
- Live binary boots under CLOUD_ENABLE=captable and serves /v1/captable/health
  200 in-process (a proxy would 502).

go build ./... + go build -tags "libsqlite3 sqlite_fts5" ./cmd/cloud green.
go.mod pins github.com/hanzoai/captable at its merged main commit; go.sum authentic.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-10 02:48:03 -07:00
hanzo-dev 3185eb182c feat(platform): native POST /v1/runner build endpoint (retires GitHub Actions builds)
The server side of the ex-/v1/arcd surface: one native build API on the
runner fabric that hanzo build, git-push-to-deploy, and cloud's own
self-release all call — no GitHub builders, no Actions.

- runner.go: POST /v1/runner. Privileged (caller supplies the output
  image), so gated by a constant-time build-callback token AND an
  image-ref allowlist (ghcr.io/{hanzoai,luxfi,zooai}/*). Fails closed
  when no token is configured.
- k8s.go: launchDirectBuild — validated at the same choke point as the
  tenant build; plus buildFrontendCmd + buildJobSpec extracted so tenant
  and direct builds share ONE Job spec and ONE frontend selector.
- hanzoai/pack is the default BuildKit frontend (zero-config, gateway.v0);
  a Dockerfile is the explicit escape hatch (dockerfile.v0).

Tests: token 503/403, missing-field 400, image-allowlist 403, happy-path
202. Full platform suite green; whole cloud module builds.
2026-07-10 02:28:35 -07:00
8df5362b39 cloud: per-project SQLite via one cloud.TenantDB resolver (DRY tenant DB) (#226)
Before: subsystems opened SQLite inconsistently. clients/code used the good
per-ORG-file pattern ({DataDir}/orgs/{slug}/code.db, resolved per-request), while
git/functions/tracker each opened ONE shared DB at Mount ({DataDir}/git.db,
functions.db, tracker.db) scoped only by an org column per-row — a decomplected
tenancy gap where the physical boundary was a single file for every tenant.

After: ONE resolver — cloud.TenantDB(dataDir, org, project, subsystem) — is the
single way any subsystem opens a tenant SQLite DB. Path convention:
  project-scoped: {DataDir}/orgs/{orgSlug}/projects/{projectSlug}/{subsystem}.db
  org-scoped:     {DataDir}/orgs/{orgSlug}/{subsystem}.db
It MkdirAll 0700s, opens via the sole "sqlite" driver (github.com/hanzoai/sqlite),
applies the shared single-writer + WAL pragmas, and folds org/project through the
injective SanitizeOrg slugger so distinct tenants can never share a file and no
segment can traverse. A generic cloud.TenantStore[T] caches per-tenant stores
(opened once each) so the hand-rolled per-subsystem map is DRY'd into one value.

SanitizeOrg (the one injective org-slug normalizer) moves to the root cloud
package beside OrgHasUnsafeRune and TenantDB; provisioning.SanitizeOrg delegates
to it, byte-identical, so S3/KMS/knowledge slugs are unchanged.

Subsystems migrated onto the resolver:
- code:      adopts the helper; stays ORG-scoped (no project axis) — same path.
- git:       single-shared git.db -> per-ORG file. Kept org-scoped (NOT project)
             because /v1/git/usage is a deliberate org-wide rollup across every
             project; the project stays a row column.
- functions: single-shared functions.db -> per-ORG file (no project axis).
- tracker:   single-shared tracker.db -> per-(org, IAM-project) file — tracker is
             project-scoped (principal.Project); its KEY-based projects are rows
             WITHIN each per-project file.
- tasks:     left as-is — it opens NO SQLite (delegates to the shared durable
             engine owned by durable.go), so there is nothing to migrate.

Data safety: the single-shared -> per-tenant switch is fail-closed (an invalid
org/project errors rather than falling through to another tenant's file). These
are new subsystems with little/no production data; existing rows in a prior
shared *.db would live under {DataDir}/{subsystem}.db and are NOT auto-migrated —
a deployment carrying such data must relocate rows into the per-tenant files
before cutover. No silent data drop.

Tests prove isolation: two orgs -> two files, no cross-read; two projects under
one org -> two nested files; project-scoped path nests; the cache opens each
tenant once. Root tenantdb_test.go plus per-subsystem end-to-end file-isolation
tests (git/functions org, tracker project).

Co-authored-by: zeekay <ai@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 02:19:36 -07:00
hanzo-dev c907e6d8eb Merge branch 'wt/v1run'
# Conflicts:
#	clients/platform/platform.go
2026-07-10 01:55:41 -07:00
hanzo-dev 8a76311c0b cloud(run): POST /v1/run container-serverless handler (reuses Service-CR deploy path) 2026-07-10 00:52:55 -07:00
zeekayandhanzo-dev c12595c799 fix(embed): cachebust on console main HEAD (re-embed on console-only change)
CONSOLE_CACHEBUST was the cloud sha, so a console-only push could not trigger a
fresh embed without a cloud commit — the whole point (freshness) leaked between
cloud pushes. Resolve hanzoai/console main HEAD (git ls-remote, extraheader
cleared since actions/checkout's GITHUB_TOKEN 404s cross-repo; gh absent on the
runner) and use it as the cachebust; fall back to the cloud sha if empty. A
console change now moves the cache key on its own.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-10 00:47:37 -07:00
hanzo-devandGitHub c2d0c0d861 controlplane inc-2 seam (a): per-pod ML-DSA-65 identity keys (contained, flag stays false) (#221)
* controlplane inc-2 seam (a): per-pod ML-DSA-65 identity keys

Replace the symmetric-HMAC proof-of-possession with per-pod asymmetric ML-DSA-65 (github.com/luxfi/crypto/mldsa, MLDSA65, FIPS 204 Level 3) identity keys — the same key material that becomes the cert-signing key in seam (c). idKey is now a fresh random keypair (crypto/rand), NEVER seed-derived; the registry stores the public key; signPoP uses the FIPS 204 5.2 deterministic variant with a domain-separation context; VerifyPoP is asymmetric VerifySignatureCtx.

Acceptance: the two byzantine-safety tests TestRed_B_DerivablePoPForgesHonestLeg and TestRed_B_LoneNodeForgesFullQuorum are un-skipped and now GREEN (an attacker rebuilding a pod's custody from public inputs gets a different key whose PoP fails); TestSafety_RogueAndForgedLegs_Rejected is re-armed to forge a CORRECTLY-DERIVED leg under a real attacker key (not a bit-flip) and still rejects it.

Scope: seam (a) only. ProductionBCCSigningReady() stays false and all other stubs remain — the flag flips later in the same change that lands the real cert (seam c) and deletes the stub types. Full suite green (zero skips), -race clean, gofmt clean, containment intact (no-tag build still matches no packages).

* controlplane seam (a): R3 — doc.go PoP narrative now reflects discharged crypto

RED review R3: refresh the stale CLASS-B caveat + ShareCustody stub-catalog entry so prose matches the code. Per-pod identity keys are real random ML-DSA-65 (not seed-derived); the two TestRed_B_* are un-skipped + green; only the z-share / cert crypto remains stub (ProductionBCCSigningReady stays false until seam c). Doc-only; no code change.
2026-07-10 00:33:24 -07:00
hanzo-devandGitHub afc5805412 feat(o11y): native-Go LLM-obs event ingest (folds retired console-worker) (#222)
Adds the write path for LLM-observability events (traces/observations/scores)
that the retired console-worker (Node BullMQ->Valkey->Datastore) used to
provide, folded into the cloud binary as a normal o11y subsystem.

- POST /v1/o11y/ingestion (validated tenant via principal.Tenant) -> parse batch
  -> route by type -> per-table batch insert into the Hanzo Datastore via the
  branded github.com/hanzoai/datastore-go/v2 client (promoted to a direct dep;
  first direct user in cloud). ZERO clickhouse imports/identifiers -- datastore-go
  brings the same upstream ch-go line (MVS-unified v0.71.0) the SigNoz o11y query
  runtime uses, so it coexists in one binary (verified).
- Grounding: the embedded o11y runtime (github.com/hanzoai/o11y) is a SigNoz fork
  serving INFRA o11y and mounts app.All("/v1/o11y/*") at order 70; it has no
  LLM-obs ingestion. This is a cloud-native SPECIFIC route registered at order 68
  so Fiber's in-order match binds it AHEAD of the wildcard (same rule scope.go
  uses for /v1/o11y/{logs,metrics,status} at 69). A route at the OTLP-ingest
  order (72) would be swallowed by the proxy.
- Oversized event bodies overflow to object storage (blob ref stored inline),
  threshold via CLOUD_O11Y_INGEST_BLOB_BYTES (default 1 MiB).
- Always mounted (no feature flag); the Datastore (O11Y_DATASTORE_DSN) is a
  required dependency. Fail-soft: no DSN / unreachable datastore -> unmounted,
  never blocks boot. Inert in prod until the console producer repoints here.

Tests: go test -tags 'cloud cloud_mount' ./clients/o11y/... green (8 cases:
routing, batching, blob overflow/disabled, sink+blob error propagation, threshold).
Full build green: go build -tags 'cloud cloud_mount' ./...

FLAGGED for cutover review:
- ASSUMED table/column schema (worker source ships dist-only; reconcile
  traces/observations/scores columns with 002_llm_observability.sql before the
  console producer is repointed).
- Durable EmbeddedTasks hand-off: flush runs INLINE today (removes BullMQ+Valkey);
  the durable enqueue->activity path is the next reviewed step (a Datastore insert
  must be a durable Activity, not run in a workflow fn).
2026-07-10 00:33:13 -07:00
hanzo-devandGitHub c581b97994 fix(idem): test uses hanzoai/sqlite not modernc directly — ONE driver, airtight (#225)
Pre-existing stray direct modernc.org/sqlite import in a test file (from #201).
Swap to the canonical _ "github.com/hanzoai/sqlite" (its !cgo backend IS modernc,
identical behavior) so NO file anywhere imports modernc directly. Test-only —
not in the shipped binary — but keeps 'hanzoai/sqlite only' truly airtight.
2026-07-10 00:30:11 -07:00
hanzo-devandGitHub 64868ba755 feat(md): agent-ready markdown content-negotiation via zap-proto/md (#224)
ONE data model, MANY adapters: handlers keep returning structured JSON; this
middleware re-serializes successful application/json responses through
zap-proto/md when the caller asks (Accept: text/markdown or ?format=md), so
token-efficient markdown is a request-time choice, not a second code path.
/v1/code/ + /v1/agents/ may default to markdown; caller override always wins.
Fail-safe: md render error leaves JSON untouched (never a 500); streams/HTML/
bytes pass through.
2026-07-10 00:24:43 -07:00
hanzo-devandGitHub d4e452cf1d feat(code): /v1/code — SOTA hybrid code-intelligence (FTS5+trigram+tree-sitter+sqlite-vec), per-org (#223)
Native, per-org code-intelligence subsystem for AI coding agents and hanzo.app.
Retrieval is HYBRID — three orthogonal tiers fused with reciprocal-rank fusion
(the SOTA lesson that embeddings alone under-serve code search):

  - lexical  — FTS5 trigram over code-tokenized text (camelCase/snake_case split,
    operators kept); substring + regex via trigram pre-filter + regexp verify (Zoekt).
  - symbolic — go/parser for Go (real def→ref call edges) + compact lexical
    extractors for TS/JS/Python/Rust/Solidity; go-to-symbol + edge table.
  - semantic — AST-boundary chunks embedded via the SAME gateway /embeddings
    clients/knowledge uses; cosine KNN over a float32 vector table.

Storage is ONE SQLite file per org at {DataDir}/orgs/{slug}/code.db (HIP-0302):
the tenant boundary is PHYSICAL. Every request is principal-gated (principal.Tenant)
— no validated principal ⇒ 403, a client X-Org-Id is never trusted.

Routes (order 134, before the AI /v1/* catch-all):
  GET  /v1/code/search   ?q=&type=text|regex|symbol|semantic|hybrid&repo=&limit=
  POST /v1/code/context  {query,budgetTokens,repo}  → budget-packed context bundle
  GET  /v1/code/ask      ?q=&repo=  (or POST)        → cited RAG answer (deps.AI)
  POST /v1/code/index    {repo,files,prune}          → (re)index, incremental by hash

Parsing is pure-Go and vectors are brute-force cosine because the repo's canonical
build is CGO_ENABLED=0 (Makefile); CGO tree-sitter and the sqlite-vec loadable
extension would break `go build ./...`. The vectors table is the schema-compatible
sqlite-vec `vec0` drop-in seam. Builds + tests green under both CGO=0 (modernc) and
CGO=1 (sqlite_purego).
2026-07-10 00:24:21 -07:00
zeekayandhanzo-dev 97cefcca43 fix(visor): degrade /v1/clusters gracefully when Visor is unreachable
listMachines/listGpus already log+fall-through to a BYO-only list when Visor is
down; listClusters alone returned the error, which surfaced as a 502 + a console
error on the Clusters/GPUs page for every org where Visor isn't deployed
(visor.hanzo.svc unresolvable). Mirror the graceful fold: log, drop managed
pools, still return the org's BYO clusters. 200, honest empty, no page error.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-09 23:43:53 -07:00
3f812b00d6 fix(iam-embed): bump hanzoai/iam v1.31.18 -> v1.31.19 (NewEnforcer panic fix) (#219)
Unblocks the embedded IAM subsystem. v1.31.18 getPermissionEnforcer called
authz.NewEnforcer(&DefaultLogger{}, false) — the (logger,bool) form Casbin
type-switches params[1]->persist.Adapter, panicking "bool is not persist.Adapter:
missing method AddPolicy" the moment InitEmbed runs against a FRESH store (exactly
the unified cloud iam subsystem). v1.31.19 (fe50caf7) uses NewEnforcer()+SetLogger.

Proven on a fresh store: CLOUD_ENABLE=iam,ai boots green ("iam embedded in-process")
and serves /v1/iam/.well-known/openid-configuration 200 (was fail-closed 503/404);
iam + ai co-reside, process listens :8080/:9653/:9090.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 23:26:10 -07:00
hanzo-devandGitHub e55c7838cc feat(websearch): native in-process keyless meta-search — retire the SearXNG proxy (#220)
Finishes the native web-search half of /v1/websearch (HIP-0106: no external
search SaaS, one fewer non-Go dependency). The route no longer reverse-proxies
to the retired SearXNG pod; it runs metaSearch in-process:

- search.go: keyless meta-search over public engines (Bing default, DDG opt-in),
  parses HTML with x/net/html, merges+dedupes by normalized URL, returns the
  exact SearXNG {query,number_of_results,results[]} envelope the LibreChat
  searxng client decodes verbatim. A failing/bot-challenged engine contributes
  zero and never fails the request (degrades to fewer results, never a 5xx).
- websearch.go: /v1/websearch/search now serves searchNative; removed
  newSearchProxy + searchUpstream + WEBSEARCH_UPSTREAM. Auth unchanged (F2):
  validated principal OR shared X-API-Key; neither ⇒ 401/503, never open.
- tests: converted the proxy route/guard tests to native (mocked engine via
  WEBSEARCH_BING_URL fixture); added metaSearch parse + graceful-degrade tests.

go test ./clients/websearch/... green; full binary builds.
2026-07-09 23:16:01 -07:00
40eb682076 feat(evals): native AI-observability dashboard at GET /v1/evals/metrics (#218)
Wire the metrics board handler and route that the completed data layer was
missing. metrics.go already had the ClickHouse ledger + GenAI-span aggregation
(assembleTotals/Series/ByModel, usageWhere, latency percentiles) and the
in-memory honest-empty path; this adds:

- metricsBoard handler: principal gate (403 without a validated tenant),
  SuperAdmin all-orgs via c.IsAdmin(), range preset -> window/bucket
  (24h|7d|30d, ?interval override), ?project threaded. nil telemetry or a
  non-default project -> honest-empty board (never 503, never fabricated).
- Telemetry.Metrics added to the interface (dsTelemetry + memTelemetry already
  implement it).
- Route registered in Mount() and the test mountApp().

All clients/eval tests pass, including the three handler tests that previously
404d (TestMetricsHandlerHonestEmpty / RequiresPrincipal / NonDefaultProjectEmpty).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 22:56:43 -07:00
hanzo-devandGitHub 2bff14a285 feat(eval+cli): collapse llmobs to o11y span plane + compute-ladder CLI verbs (#217)
* feat(eval): drop cloud_usage-as-observations read; collapse to o11y span plane

Step 1 of the unified AI-observability plan: the observation of record is the
o11y gen_ai span plane (/v1/o11y/observations), not a second projection of the
metering warehouse. evalsvc no longer reads hanzo.cloud_usage as 'observations'.

- Remove Telemetry.ListObservations + Observation/ObservationFilter types + the
  dsTelemetry (cloud_usage) and memTelemetry impls + the now-dead asInt64 coercer.
- Remove GET /v1/evals/observations route, its handler, and observationView/
  toObservationView. The console Observe > Observations view now reads o11y.
- cloud_usage stays the metering warehouse (read by /v1/usage + billing) — only
  the duplicate obs projection is gone. eval keeps its unique datasets/evaluators/
  runs and its own eval_traces/eval_scores tables.
- Bump ai dep to the enriched-gen_ai-span build (forward-only from v1.804.0).

Build+vet+test ./clients/eval green.

* cloud(cli): compute ladder — hanzo run/agent/bot verbs (thin /v1 clients)

Preserve in-flight CLI work: hanzo run (artifact/function), hanzo agent
(headless managed agent -> /v1/agents/:ref/run), hanzo bot (computer-using
agent -> operative/visor). Thin clients over IAM token + cloud /v1.
2026-07-09 22:55:21 -07:00
70084b91ee fix(config): accept aud=hanzo-world in defaultJWTAudiences (#216)
world.hanzo.ai is the OIDC client `hanzo-world`; IAM stamps its access
tokens with aud=hanzo-world (each app's aud is its client_id). That
audience was missing from cloud's baked identity-sanitizer allowlist, so
signed-in world tokens resolved anonymous and api.hanzo.ai returned 401.
Append the client_id (forwards-only) and add a membership + resolved-env
acceptance test.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 22:14:23 -07:00
1d4e5960a4 feat(commerce): embed commerce in-process as a cloud subsystem (task #89 phase 1) (#215)
Cloud now serves /v1/commerce/* + /_/commerce/* ITSELF via a new
clients/commercesvc leaf that wraps commerce.Embed's gin handler — the same
wrap-don't-rewrite fold clients/iam and clients/kms use — instead of proxying to
a remote commerce pod. deps.Commerce resolves to the in-process CommerceClient
(CommerceInProcess) when commerce is co-resident.

Why a leaf (not the upstream commerce.Mount): commerce's own Mount/init sit
behind //go:build cloud, and cloud builds without that tag, so cloud's plain
build never compiled the registration — commerce was blank-imported yet absent
from cloud.Registry (proxied at runtime). The leaf lives in-repo and imports only
commerce's cloud-free surface (Embed, api.Route, Version), so the upstream
commerce.Mount that imports cloud stays tagged out — no cloud<->commerce import
cycle. Zero go.mod/go.sum churn (commerce v1.46.40 already required).

STAGED (prod-safe): commerce joins iam/ingress in stagedSubsystems, so the
mount-all default is unchanged — the in-process cutover happens only on explicit
CLOUD_ENABLE=...,commerce. Phase 2 flips the default once validated in prod. The
remote proxy seam (CLOUD_COMMERCE_HTTP_URL / CLOUD_COMMERCE_ZAP_ADDR) is
untouched; the disabled/RPC fallbacks still compile.

GetTenantConfig is answered in-process (org + brand); CheckEntitlement fails
closed until commerce exports its subscription->plan->features resolver (Phase 2)
— the specified "cannot verify => never open" default clients/entitlements relies
on.

Proven: CLOUD_ENABLE=commerce -> GET /v1/commerce/tenant, /v1/commerce/catalog,
/_/commerce/healthz all 200 from the embedded gin engine; an unknown
/v1/commerce path returns gin's own 404 (a proxy would 502).


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 22:08:05 -07:00
hanzo-dev eccb271e0d Merge branch 'wt/meters' into feat/collapse-llmobs-to-o11y 2026-07-09 21:48:20 -07:00
hanzo-dev 31fdf8672e cloud(billing): usage-native meters — function GB-seconds + build minutes 2026-07-09 21:44:15 -07:00
hanzo-dev b4aeb20be4 cloud(sites): opt-in COOP/COEP cross-origin isolation for WebGL 2026-07-09 21:39:21 -07:00
hanzo-dev 79416150b2 cloud(sites): correct MIME for WebGL/WASM game assets (Unity/Emscripten/Godot)
Served sites typed .wasm/.data/.mem/.unityweb/.pck via mime.TypeByExtension only,
which returns "" for the engine payloads (empty Content-Type) and can mis-type
.wasm — breaking WebAssembly.instantiateStreaming (requires application/wasm) and
the loader's streaming fetch of Unity/Emscripten .data/.mem and Godot .pck. Pin
those in one gameAssetType map; everything else defers to the stdlib table.
Unblocks hosting WebGL game builds. Tested (TestGameAssetContentType).
2026-07-09 21:12:27 -07:00
hanzo-dev 177bc6fb9f cloud(cli): rename the native build endpoint /v1/arcd/enqueue -> /v1/runner
'arcd' is the client-side GitHub-Actions BYO product (github.com/arc-runner);
the platform's own native CI/compute pool is 'runner'. Rename the enqueue path
and de-brand the build command help/comments accordingly. Pairs with the
platform route move pages/api/v1/arcd/enqueue.ts -> pages/api/v1/runner.ts.
2026-07-09 20:19:10 -07:00
hanzo-dev e47204a5bf cloud(ci): BuildKit cache mounts on go build/test/mod — warm Go cache across builds
The 4 go invocations (mod download, sqlite double-register gate, encryption-proof
test, final build) had no cache mount, so every release recompiled the full CGO
graph (k8s + otel-collector + sqlcipher, CGO=1) from scratch on the ephemeral ARC
runner — the Build step was ~1316s/22min, dwarfing every other step. Mount
/go/pkg/mod + /root/.cache/go-build (sharing=locked) so the persistent ARC dind
BuildKit cache keeps the Go build+module cache warm. First build cold; subsequent
builds reuse compiled artifacts — target single-digit-minute rebuilds.
2026-07-09 20:03:43 -07:00
hanzo-devandGitHub d17666c384 Merge pull request #214 from hanzoai/feat/runner-ship
cloud(runner): embed the arc JIT runner as `hanzo runner`
2026-07-09 19:26:41 -07:00
hanzo-dev e95b1b4993 cloud(runner): embed the arc JIT runner as hanzo runner
Migrate arc-runner/arc (arc-archive) cmd/arcd host-role JIT GitHub-Actions
runner into hanzoai/cloud as package runner/, exposed as `hanzo runner` —
third verb of the one-binary trifecta: engine serves models, gpu connect shares
compute, runner claims CI. One org login, outbound-only, GPU/vulkan-aware.

- runner/: host-role JIT daemon (config, GitHub App auth, poll, JIT launcher,
  /v1 control surface, WSL labels). In-cluster controller role deferred.
- cli: wire `hanzo runner`; also register `engine` in controlCommands (was
  constructed but missing from the router — silently undispatchable).
- Security (red+cto reviewed): /v1 defaults 127.0.0.1 + localGuard (Host
  allowlist vs DNS-rebind, Origin vs CSRF); child env stripped of secrets;
  fork repos skipped by default (private/internal-org scoping is the real
  containment; documented honestly).
- deps: +go-github/v52, +ghinstallation/v2; luxfi/keys v1.2.0->v1.2.2 (v1.2.0
  tag mutated at origin — bump past it, verified under -mod=readonly, no bypass).
2026-07-09 19:25:05 -07:00
hanzo-dev 37ba7c6bd6 o11y: release chtraces exporter on failed Start (no leak on fail-soft path)
CreateTraces opens the ClickHouse conn + spawns the writer's ticker goroutine, so
a failed Start must Shutdown to release them rather than leak on the fail-soft
mount path.
2026-07-09 17:39:47 -07:00
6bafc5e9f4 test(kms): make dual-mount two-scope assertion load-robust (#212)
The validated-org-principal check asserted ==200, coupling this cross-package
gate test to the orgs/users/me handler's downstream success (IAM/datastore),
which flaked under full-suite parallel load. Assert the gate/shadow decision
only — admitted (not 403) and mounted (not 404) — since tenant-scoped data
correctness is proven in clients/admin/scope_test.go. Anonymous->403 and the
SuperAdmin-only platform routes are unchanged.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 17:32:13 -07:00
zeekayandhanzo-dev 0189d578e1 fix(embed): bust console clone layer with cloud sha (gh/ls-remote-free)
The prior two attempts (a94b3ca sha-pin via git ls-remote, c86acc3 via gh api)
both FAILED at version-compute: the ARC runner has no gh CLI, and git ls-remote
404s because actions/checkout installs a global http.extraheader carrying THIS
repo's GITHUB_TOKEN (scoped to hanzoai/cloud), overriding URL creds on the
cross-repo hanzoai/console lookup.

Bulletproof instead: no console-HEAD resolution at all. release.yml passes the
cloud commit sha as --build-arg CONSOLE_CACHEBUST (unique per push); the
Dockerfile references it in the proven `git clone --depth 1 --branch main`
RUN, so the layer cache key changes every build and re-clones console main HEAD
fresh. No gh, no ls-remote, no extraheader. Correctness over cache reuse — the
console stage rebuilds each release, but the embed is never the frozen snapshot.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-09 17:30:51 -07:00
31d0a858be fix(base+admin): base serves /v1/base/health (HealthOwner) even embed-off; dual-mount red test tracks the admin two-scope model (#211)
- clients/base: register /v1/base/health in Mount BEFORE the CLOUD_BASE_EMBED
  gate and mark cloud.HealthOwner — same always-on liveness pattern as
  clients/plan + clients/pricing. Fixes cmd/cloud TestMountAllAndServeHealth
  (base was the only listed subsystem not self-serving health).
- clients/kmssvc red_dualmount_test: #192 made the admin cockpit two-scope —
  orgs/users/me are org-scoped (guardScoped: a validated org principal is
  admitted + hard-scoped to its own org; anonymous still 403), while
  audit/roles/finance/flags/revenue stay SuperAdmin-only (guard: 403 for a
  non-admin principal). Assert both, plus kms's public /v1/kms/config never
  shadows either. No production code semantics changed — the stale test tracked
  the pre-two-scope admin-only contract.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 17:26:29 -07:00
zeekayandhanzo-dev c86acc3390 fix(embed): resolve console HEAD via gh api, not git ls-remote
git ls-remote failed 'Repository not found' on the cross-repo hanzoai/console
lookup: actions/checkout installs a global git http.extraheader carrying THIS
repo's GITHUB_TOKEN (scoped to hanzoai/cloud only), which overrides the URL
creds and 404s. gh api honors GH_PAT (org read) and is unaffected. Unblocks the
console-embed-freshness fix (a94b3ca) — the release aborted at version-compute
before building.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-09 17:24:26 -07:00
hanzo-dev 80281a865e o11y: dogfood ZAP Router — cloud's own spans -> in-process ClickHouse sink, no socket
cloud already embeds the o11y trace write side (chtraces), so shipping its OWN
spans over the ZAP wire to a collector that then writes the same store is pure
waste. Route them through the ZAP locality-adaptive Router (luxfi/zap v1.2.1):
when sender and sink share this binary, the Cost-0 InProcessInterface wins and
the LIVE proto batch is handed to the sink by value — zero ZAP-wire serialize,
zero socket, no second collector hop.

- clients/o11y/tracesink.go: Router + Cost-0 InProcessInterface on Destination
  "hanzo.o11y.traces"; a chtraces exporter (the REAL o11y_index_v3 writer, reused
  as a consumer.Traces — its pdata->SpanV3 conversion is unexported) fed in
  process. Handler bridges SDK-exporter proto spans -> pdata via one in-memory
  OTLP round-trip. OPT-IN (O11Y_TRACES_ZAP_INPROCESS) + fail-soft: any error
  leaves cloud's spans on the wire; can never take cloud down. NewTraceExporter +
  routerTraceClient own the transport; cmd/cloud stays the composition root.
- cmd/cloud/telemetry.go: install the ONE tracer provider over the Router
  (in-process primary, ZAP wire fallback when the sink isn't registered). Enable
  when the in-process sink is on OR a wire endpoint is set. Composition-root
  single-provider invariant (ai's GenAI tracer inherits it) preserved.
- go.mod: github.com/luxfi/zap v1.2.0 -> v1.2.1 (adds Router/InProcessInterface).

TDD: span from cloud's provider reaches the in-process handler with no wire
client and no socket; proto->pdata round-trip preserves the span; router prefers
in-process, falls back to wire on ErrNoRoute, surfaces ErrNoRoute when neither.
2026-07-09 17:21:29 -07:00
694a5b2cf5 refactor(kms): merge clients/kmssvc into clients/kms — one KMS package (#210)
The kmssvc dir was an artificial split: clients/kms is the KMS library
(embeds luxfi/kms + SecretStore + in-process client), clients/kmssvc was
the Fiber subsystem mounting /v1/kms/* — and it was ALSO package kms, dir-
named kmssvc only to dodge a dir-name collision. That svc suffix is a
workaround, not a concept.

Move every kmssvc file into clients/kms (kmssvc.go → mount.go; login.go,
env_required/kms/login_ratelimit/paas_sync/red_*/v6 tests). subsystems.go
imports clients/kms (order 10, /v1/kms/*); exactly one cloud.Register("kms").
Zero kmssvc refs remain. Full cloud build + kms package tests (incl red_*
adversarial) green. (Pre-existing clients/kms/replication test build failure
is unrelated — broken on main before this change.)

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 17:13:54 -07:00
hanzo-devandGitHub b16ff7d5bd org+idem: fenced single-writer + exactly-once request layer (lift replicas:1 -> N safe) (#201)
Composes the ha lease-round (v0.1.1) and vfs/replica.FencedStore (v0.6.3) into
the cloud per-org substrate, and adds the request-layer exactly-once dedup, so
per-org SQLite is safe under a multi-replica Deployment (not just replicas:1).
Four orthogonal concerns, one home each:

  internal/org/fence.go   CASFencer: the INTERIM monotone round source. A per-org
                          writer lease {round,owner} over the object store's CAS
                          (a single linearizable register); takeover strictly
                          bumps the round, renewal keeps it. Implements ha.Fencer,
                          so the Lux BFT round drops in behind the same seam later.
                          HRW is only an optimization (cuts contention); safety
                          does not depend on a fresh/agreed membership view — a
                          split view costs liveness, never safety, because the
                          fence backstops it.
  internal/org/condstore.go  MinioConditionalStore: the concrete atomic-CAS store
                          (minio If-Match against the SeaweedFS gateway), promoted
                          from the orphaned internal/writefence. satisfies
                          replica.ConditionalStore.
  internal/idem/          exactly-once request execution: request-id PK written in
                          the SAME txn as the effect (atomic dedup+effect), shipped
                          in the per-org snapshot so a retry re-routed after a
                          rolling upgrade is deduped on the successor. 'fail if
                          already done' via ErrAlreadyApplied.
  internal/org/shared.go  re-export FencedStore/ConditionalStore/Lease/Fencer/
                          Round/ErrStaleRound so the org API stays one surface.

Deletes internal/writefence (was orphaned, zero importers): its fence primitive
is promoted to vfs/replica.FencedStore (the storage substrate's rightful home),
its minio store to condstore.go — one and one way, forward-only.

Safety (no data loss + no double-exec) rests on the composition, proven by
handoff_test.go against the four hazards: (a) partition minority cannot advance
the round -> cannot write; (b) rolling-upgrade handoff -> successor CarryForwards
the predecessor's last landed write + dedups; (c) duplicate request -> idem runs
once; (d) deposed writer -> refused by election, and if it still ships, fenced by
FencedStore. Ship-before-ack: a request is 'done' only once its fenced ship lands.

Interim round source = single linearizable register (object CAS) = crash-fault
tolerant. Roadmap: replace readLease/claim with the quasar PQ-BFT agreed round
(Byzantine-tolerant, deterministic finality, 3/5 quorum) — same ha.Fencer seam,
same FencedStore admission.

Cross-repo: pins ha@fence-lease + vfs@fenced-store (pseudo-versions); retag to
ha v0.1.1 + vfs v0.6.3 once those merge. go.sum touches only ha+vfs; the
pre-existing luxfi/keys@v1.2.0 re-tag mismatch (blocks `go mod tidy` on main
today) is unrelated and untouched.
2026-07-09 16:47:19 -07:00
zeekayandhanzo-dev a94b3caedc fix(embed): re-clone console per build — stop shipping a frozen embed
The console-clone+build layer was keyed only on static text ('git clone
--branch main'), so on the persistent ARC dind BuildKit cache EVERY cloud
build re-embedded the SAME stale console snapshot. New console work — the
native Tracker module, and everything since the cache was first warmed —
silently never shipped: console.hanzo.ai/tracker rendered an old surface
with zero /v1/tracker calls even on a freshly-deployed image.

Fix (values, not places): release.yml resolves hanzoai/console main HEAD
(git ls-remote) at build time and threads it through --build-arg CONSOLE_REF;
the Dockerfile fetches that exact ref (init+fetch+checkout, sha- or branch-
capable). A changed sha moves the layer cache key, so each build embeds the
live console commit — deterministically pinned, never frozen.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-09 16:45:56 -07:00
b7c1544293 feat(admin): operator cockpit — two-scope model, flags/launch, waitlist/access, bases (#192)
admin.hanzo.ai as ONE cockpit for BOTH tiers off ONE identity predicate. scope.go decomplects the rule into a single place (resolveScope/scopedOrgs/descendants): owner==admin (c.IsAdmin, SuperAdmin) => cross-tenant, all orgs; any other validated admin => their OWN org, hard-scoped server-side. guardScoped admits a SuperAdmin OR a validated org-pinned caller and the handler scopes the data; the platform control plane (roles/audit/finance/revenue + launch/release/flags/access) stays s.guard (SuperAdmin only). me/overview/orgs/users/usage/analytics/bases are org-scoped; a non-super caller can never read another tenant for any input (their org is the sanitized, un-forgeable c.Org()).

Feature flags / launch / access via Hanzo Insights (one engine, not two): clients/featureflags is a hot-apply evaluation seam over Insights /flags (env = fallback default, 15s TTL, fail-safe degrade); /v1/admin/flags surfaces the launch switches (public_signup, waitlist_open, waitlist_access_capacity, ...) with deep-links to the Insights flag manager + activity log. /v1/admin/waitlist + /boost proxy the Base waitlist engine (server-authed, KMS secret, audited grant). /v1/admin/bases is the scoped tenant-Base panel seam (honest-empty until the Base engine is embedded).

Fix: waitlist.go shadowed the ok() envelope writer with a local bool (compile error) — renamed to configured. Tests: scope_test.go proves the two-scope invariant (super sees all; org-admin hard-pinned to own org; platform routes 403 an org-admin; users read pinned to own org); featureflags_test.go proves hot-apply + env fallback. go build ./... green; go test ./clients/admin/ + ./clients/featureflags/ green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-09 16:31:39 -07:00
hanzo-devandGitHub 94d67de1b0 feat(edge): embed the gateway CORS + per-IP rate-limit role in cloud (#181)
* feat(edge): embed the gateway CORS + per-IP rate-limit role in cloud

Fold the hanzoai/gateway edge role into cloud so it can serve api.hanzo.ai
directly, dropping the redundant KrakenD hop. cloud already validates the IAM
JWT + strips/re-mints identity headers (SanitizeIdentity), runs the per-tenant
ScopeRateLimit, and owns balance/spend-cap quota (BillingGate) — the gateway
duplicated the JWT/identity role and added only CORS + a per-IP flood cap.

Adds middleware_edge.go (package cloud), two orthogonal middlewares wired into
the serve.go chain AFTER Logger/sites and BEFORE identity:

- EdgeCORS: credentialed reflect-Origin CORS matching the gateway's policy
  (methods/headers/max-age). DEFAULT OFF (empty CLOUD_CORS_ORIGINS) so the
  shared Traefik ingress `cors-allow-all` stays the sole CORS authority on the
  recommended rollout — enabling both would double the ACAO header. Set
  CLOUD_CORS_ORIGINS only on a direct DO-LB->cloud edge. Handles + short-circuits
  the OPTIONS preflight (204) before any auth work.

- EdgeRateLimit: per-client-IP fixed-window flood cap (default 100/1s, gateway
  service-tier parity, strategy:ip) that runs BEFORE identity — the one gap
  ScopeRateLimit (keyed on the validated tenant) structurally can't see: an
  anonymous flood with no valid JWT. Keyed on the leftmost X-Forwarded-For;
  in-cluster direct callers (no XFF) are exempt, matching the standalone
  gateway's public-only scope. Opportunistic eviction keeps the bucket map
  bounded at edge IP cardinality (default ON, CLOUD_EDGE_RATELIMIT=false to
  disable). This preserves the gateway's protection rather than dropping it.

Config: CORSOrigins, EdgeRateEnabled/PerIP/WindowSec (config.go).
Tests: TestOriginMatcher, TestEdgeCORS_*, TestEdgeRateLimit_* (all green).
CGO_ENABLED=0 go build ./... + go test . green.

* feat(gateway): /v1/gateway runtime-mutable edge-policy plane

Make the embedded gateway role RUNTIME-CONFIGURABLE instead of baked into static
config: an operator/SuperAdmin retunes CORS, the per-IP flood cap, or a tenant's
rate ceiling via PUT /v1/gateway/config with NO redeploy — replacing the gateway's
image-baked KrakenD config.

clients/gatewaypolicy (leaf pkg, stdlib + hanzoai/sqlite only, no cloud import so
both the middleware and the HTTP subsystem share it cycle-free):
- Policy{CORSOrigins, PerIPRPM, WindowSec (platform), OrgRPM (per-org)} — every
  field is enforced by a consumer; no stored-but-ignored knob.
- Store: one encrypted per-tenant SQLite (gateway.db), org-keyed rows. The admin
  org row is the PLATFORM policy, layered over the static env/flag boot defaults.
  Cached resolvers Platform()/OrgRPM()/Effective() (5s TTL, fail-open to static),
  merge(base,over) makes a partial PUT additive. Fail-soft: a store-open error
  degrades to static-only (reads work, writes error) — the edge never goes down.

clients/gatewaysvc: the /v1/gateway subsystem (order 139) — GET/PUT config over
the SAME store, IAM-gated like clients/pricing/enablement.go:
- platform fields (CORS/per-IP) writable ONLY by SuperAdmin (c.IsAdmin()); routed
  to the platform row explicitly (PutPlatform) so an org-switched SuperAdmin still
  lands on it.
- per-org OrgRPM writable by the org admin (own org via principal.Tenant, never a
  raw header) or a SuperAdmin targeting ?org=<slug>.

Wiring: deps.GatewayPolicy (BuildDeps constructs it, layered over staticEdgePolicy;
serve.go closes it at shutdown). EdgeCORS/EdgeRateLimit now read the PLATFORM policy
LIVE (recompiling the CORS matcher only when the allowlist changes; the per-IP
limit/window per request). ScopeRateLimit gains the runtime per-org OrgRPM
override (most-restrictive-wins with the commerce-configured ceiling).

Tests: gatewaypolicy (static-only, platform layering, additive merge, per-org +
platform-default OrgRPM, persist-across-reopen); gatewaysvc (principal required,
org-self OrgRPM, org-admin platform 403, SuperAdmin platform, org-switched-still-
platform, empty-body 400). CGO_ENABLED=0 go build ./... + go test . green.
2026-07-09 16:25:43 -07:00
788a4aac1c feat(base): embed base app + waitlist in-process (/v1/waitlist), retire standalone superbase (#193)
Mounts /v1/waitlist/* served in-process off the embedded hanzoai/base app over
the durable cloud PVC — the in-binary replacement for the standalone superbase
pod. STAGED + fail-closed: no-op unless CLOUD_BASE_EMBED=1. Registered as the
"base" subsystem (order 60) in clients/base.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-09 16:21:02 -07:00
4b7f24356d fix(sbom): lazily create hanzo.sbom_component (datastore connects after Mount) (#207)
The datastore connects ASYNCHRONOUSLY: ai/object.InitDatastore flips
DatastoreEnabled true only AFTER Mount returns. Mount ran the CREATE TABLE
DDL only when DatastoreEnabled() was already true, so in prod it was skipped
and never retried -> GET /v1/sbom/{ref} 502 'Unknown table expression
identifier hanzo.sbom_component' while /v1/sbom/health reported datastore:true.

Add a lazy, idempotent ensureTable(ctx) guarded by a mutex+bool that latches
ONLY success (a transient failure retries; sync.Once would cache the failure).
It CREATE DATABASE IF NOT EXISTS hanzo then CREATE TABLE IF NOT EXISTS, and is
called from ingest and resolve right after requireDatastore() passes; on error
they return a retryable 503. Mount now routes its best-effort boot DDL through
the same ensureTable and is non-fatal (a Mount-time miss no longer aborts the
subsystem).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 15:47:23 -07:00
9ca9163309 fix(brand): map <brand>.cloud/.network hosts to the brand (white-label) (#209)
The live cloud console runs on <brand>.cloud hosts that route straight to the
cloud Service (console.lux.cloud, console.zoo.cloud, …). BrandForHostOK only
matched a brand's primary marketing Domain (lux.network, zoo.ngo), so a request
Host on lux.cloud/zoo.cloud fell through to the deployment brand — emitting Hanzo
branding on a Lux/Zoo surface (agent-skills catalogue + any Host-branded reply).
Add AltDomains per brand (lux→lux.cloud; zoo→zoo.network,zoo.cloud;
hanzo→hanzo.cloud,hanzo.app; pars→pars.ai) and match them in BrandForHostOK.
Base-URL/issuer scoping still uses the primary Domain.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 15:39:16 -07:00
5103936e9a feat(agentskills): serve /.well-known/agent-skills discovery, white-labeled by Host (#208)
New subsystem clients/agentskills serves the Agent Skills Discovery surface from
a catalog GENERATED by hanzoai/openapi's skills.py and embedded via go:embed:

  GET /.well-known/agent-skills/index.json        the brand's MASTER catalogue
  GET /.well-known/agent-skills/<skill>/SKILL.md   one skill document

WHITE-LABEL: the brand is decided per request from the Host (new BrandForHostOK,
mirroring platform.ts getWhiteLabelBrand) — api.hanzo.ai serves Hanzo,
api.lux.network serves Lux (lux.id), api.zoo.ngo serves Zoo — never Hanzo
branding on a Lux/Zoo surface. An unmatched Host degrades to the deployment brand
(CLOUD_BRAND), not blindly Hanzo. Order 8 registers these exact routes BEFORE
IAM's /.well-known/* wildcard (50) and the console catch-all, so they win Fiber's
first-match. Public, GET-only, no secrets.

The binary does not re-derive skills — it serves the embedded bytes, so the
sha256 digests in index.json match the served SKILL.md exactly. Only a tiny,
self-consistent `ai` fallback is committed (catalog/.gitignore); `make
agentskills` / the Dockerfile `skills` stage regenerate the FULL catalog (all 68
services × hanzo/lux/zoo) from the openapi SOT before `go build`, mirroring
webui/dist. End-to-end serve test drives the real router (index + SKILL.md +
white-label + digest + 404); cmd/cloud links clean.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 15:16:36 -07:00
269c1736e9 feat(sbom): global SBOM datastore + /v1/sbom ingest & resolve (#206)
Add clients/sbom: a self-contained subsystem riding the ONE shared
ClickHouse client (ai/object.Datastore*) — no second connection — that
ingests CycloneDX SBOMs from CI and serves them by image digest/ref.

The store (hanzo.sbom_component, ReplacingMergeTree) is GLOBAL/cross-tenant
by design: an SBOM belongs to a content-addressed image digest, not a
tenant, so any tenant deploying that image resolves the same component set.
Ingest is gated to the canonical cloud super-admin check (c.IsAdmin(),
owner==AdminOrg) which the build fleet carries; resolve exposes only an
image's immutable bill-of-materials (no tenant data).

  POST /v1/sbom        ingest (super-admin/CI): flatten document.components[]
  GET  /v1/sbom/{ref}  resolve by digest OR ref (FINAL dedupe, type,name order)
  GET  /v1/sbom/health liveness + datastore bool (not JWT-gated)

Registered id "sbom" order 137 with cloud.HealthOwner (binds before the ai
/v1/* catch-all at 150). Mirrors clients/analytics for structure, coercers,
and the honest-503 datastore gate.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 14:28:03 -07:00
bfad6f2bb6 chore(deps): pin hanzoai/ai → v1.804.0 (cookie self-heal + one super-admin rule) (#205)
Clean-semver pin bringing three ai releases into the cloud binary:
- v1.803.1 fix(account): cookie-session self-heal (#71) — a signed-in admin
  whose beego session already holds a guest u-<hash> is rebound to the
  canonical identity from hanzo_iam_token, so /v1/admin/* stops 403ing.
- v1.804.0 refactor(authz): ONE super-admin rule — membership in the `admin`
  org (owner == AdminOrg); drops the configurable globalAdminOrgs + built-in.
  Matches cloud's clients/admin (isSuperAdmin canonical, isGlobalAdmin alias)
  and the console isSuperAdminAccount gate.

Supersedes the pseudo-version pin (#197) and the intermediate v1.803.1 pin
(#198, closed). Verified: go build -tags "libsqlite3 sqlite_fts5" ./cmd/cloud.


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 13:46:20 -07:00
9faa0a9ef7 feat(platform,sites): pure-Go zip/tar.gz static-site upload + custom-domain serving (#204)
* feat(platform,sites): pure-Go zip/tar.gz static-site upload + custom-domain serving

Adds a self-service static-site deploy to the unified cloud binary's PaaS
surface and lets the site edge serve a customer's own domain from S3.

- projects: walkArtifact accepts a ZIP (archive/zip) as well as tar(.gz),
  sniffed by magic bytes; one deploy contract (index.html at root, same size
  and traversal guards), three container formats. A single wrapping top-level
  directory (a zip made from a project folder) is stripped so index.html lands
  at the root.
- projects: the deploy handler reads the artifact from a multipart file upload
  (a browser <input type=file>) OR the raw request body (a curl one-liner).
- sites: the host edge now serves a bound CUSTOM domain (a customer apex/host
  pointed at this edge) from that project's S3 prefix, resolved by the full
  host. Only external hosts (never one of our self domains) with a LIVE binding
  are served; every other host — our api/console hosts, or an unbound host
  routed here — Continues to the normal pipeline, so the API path pays no
  per-request lookup and a customer binding can never shadow a real Hanzo host.
- projects: POST/GET .../domains binds and lists a site's custom domains
  (admin-gated until DNS-ownership verification is wired here).
- surface: the static engine is exposed under /v1/platform/sites/* (the PaaS
  namespace) in addition to /v1/projects/*, so the one user flow is create a
  site -> upload a zip -> bind a domain -> live.

Pure Go, CGO-off. New unit tests cover the zip walker, format dispatch,
single-root strip, custom-domain routing (served/passthrough/self-host/not
-live), hostname validation, and host binding.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>

* feat(projects): authorize custom-domain binding by the platform-operator org

A custom-domain bind is authorized for a global admin OR the platform-operator
org (the deployment's brand org, env CLOUD_PLATFORM_OPERATOR_ORGS, default the
brand). The operator manages customer DNS until per-tenant DNS-ownership
verification is wired here. Safe because a bound domain is inert until its owner
points DNS at this edge — the real gate is DNS control.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-09 13:12:56 -07:00
de85b94790 debrand: signoz → o11y (branding) + repoint collector module to hanzoai/otel-collector (#202)
* debrand: signoz -> o11y (branding) + repoint collector module

Drop "SigNoz"/"signoz" where it is BRANDING (comments, docs, prose) to o11y,
and repoint cloud's direct collector import to the renamed module.

- go.mod/go.sum: github.com/hanzoai/signoz-otel-collector v0.144.6 (direct)
  -> github.com/hanzoai/otel-collector v0.144.7 (direct). The old module stays
  as an // indirect dep because hanzoai/o11y v1.5.2 (separate repo, out of
  scope) still imports it; the fork also pulls upstream
  github.com/SigNoz/signoz-otel-collector v0.144.5 // indirect.
- clients/o11y/ingest.go: chlogs/chtraces imports -> otel-collector.
- Branding prose swapped to o11y in telemetry.go, subsystems.go, embed.go,
  logs.go, metricsread.go, scope.go, ingest_test.go, agents.go, LLM.md,
  docs/consolidation.md.

KEPT (not branding):
- ClickHouse schema read by cloud (written by the deployed collector):
  signoz_traces / signoz_logs / distributed_signoz_index_v3, severity_text
  columns. Renaming reads without migrating the live schema breaks them; the
  v0.144.6->.7 patch bump does not migrate table names.
- Upstream API in hanzoai/o11y/pkg/signoz: import path, alias, type SigNoz,
  and signoz.New / SigNoz.Start references (that repo is debranded separately).
- Upstream package names: signozclickhousemetrics.
- Honest attribution: "SigNoz's dd-sketch fork of ch-go".

Build: go build ./... = 0, go vet = 0, go test ./clients/o11y ./clients/admin
= ok. go mod tidy is blocked by a pre-existing luxfi/keys@v1.2.0 go.sum
checksum mismatch (identical on origin/main) -> CI-authoritative.

* o11y: read o11y_* ClickHouse tables + bump collector to v0.144.8

Direct ClickHouse table reads renamed signoz_* -> o11y_* to match the
o11y read plane and the data-preserving RENAME migration (hanzoai/o11y#28):

  o11y_traces.distributed_o11y_index_v3  (was signoz_traces.distributed_signoz_index_v3)
  o11y_logs.distributed_logs_v2          (was signoz_logs.distributed_logs_v2)

Files: clients/o11y/logs.go, clients/o11y/metricsread.go,
clients/o11y/ingest.go, clients/admin/o11y.go (+ o11y_test.go).

Bump github.com/hanzoai/otel-collector v0.144.7 -> v0.144.8 (writer side
now CREATEs/WRITEs the same o11y_* physical schema). Collector go.mod is
unchanged between the two tags (identical go.mod hash) — pure source
rename, so the module graph is unchanged; go mod tidy left to CI
(pre-existing luxfi/keys tidy block is CI-authoritative).

go build ./... = 0. clients/admin + clients/o11y tests green (SQL
assertions now match o11y_* target names). Lockstep deploy: collector
v0.144.8 -> o11y#28 RENAME migration -> o11y+cloud readers.

* cloud: embed o11y v1.5.4 — version-less /v1/o11y + o11y_ schema reads + debrand

Bumps hanzoai/o11y v1.5.2→v1.5.4 (version-less surface + o11y_ ClickHouse table
reads + the signoz→o11y debrand) and repoints embed.go to the renamed runtime
package pkg/signoz→pkg/o11y (type SigNoz→O11y). Pairs with otel-collector v0.144.8
(writes o11y_) + the lockstep cutover migration. go build ./... = 0.

---------

Co-authored-by: hanzo <z@hanzo.ai>
2026-07-09 13:12:34 -07:00
904d4e5dcd deps: bump hanzoai/o11y v1.5.1 -> v1.5.2 (o11y /v1/o11y path normalizer) (#199)
Embeds hanzoai/o11y#26: the mount normalizes the /v1/o11y/<resource> public
contract onto the internal SigNoz /api/vN routes (kills the /api/ leak, fixes
the llmobs /v1/o11y/* 404). Pairs with the cloud CR O11Y_GLOBAL_EXTERNAL__URL=""
change (universe#461) — deploy together.

Co-authored-by: hanzo <z@hanzo.ai>
2026-07-09 08:57:35 -07:00
zeekayandhanzo-dev 08970ab1d3 fix(identity): read hanzo_iam_token cookie — unbreak embedded-console org-scoped /v1
The ai (casibase) layer SETS the httpOnly hanzo_iam_token cookie (the IAM JWT) after
login (ai/controllers/account.go iamTokenCookieName), but cloud's own identity
middleware only read [iam_access_token, access_token, hanzo_token] — NOT
hanzo_iam_token. So the embedded console (browser holds ONLY that cookie, no
Authorization header) resolved to no validated principal → every org-scoped /v1
endpoint (agents, gpus, machines, platform, orgs, entitlements, …) 403'd
'X-Org-Id required', and modules rendered empty. Add hanzo_iam_token (first) to
cookieTokenNames so cloud reads the SAME cookie the ai layer sets → validates the
JWT → X-Org-Id from owner → org-scoped surfaces authorize. Verified: the JWT is
present in the browser (1533-char httpOnly hanzo_iam_token); only the name was wrong.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-09 02:28:51 -07:00
df11066933 chore(deps): bump hanzoai/ai → e1c4cde0 (cookie-session self-heal, #71) (#197)
Pulls the get-account cookie-path fix (hanzoai/ai#81): a signed-in admin
whose beego session already holds an anonymous guest u-<hash> is now
self-healed from the hanzo_iam_token credential to its canonical identity,
so /v1/admin/* stops 403ing under the console cookie session. Verified:
cloud binary builds with -tags "libsqlite3 sqlite_fts5".


Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-09 00:00:57 -07:00
cd790a228b org: elect via hanzoai/ha; vfs/replica stays replication-only (#196)
internal/org/shared.go split its aliases along the real seam: election
(Member/Owner/IsOwner/Replicas) now re-exports github.com/hanzoai/ha; the
Replicator/Store/DB/DBPath stay github.com/hanzoai/vfs/replica. membership.go
and cipher.go are unchanged (the alias types line up: org.Member = ha.Member).
writefence doc updated to name ha as the election primitive.

One concern, one home: who-writes (ha) vs how-state-ships (vfs). No behavior
change; internal/org + writefence pass with -race.

NOTE: `go mod tidy` is blocked in this repo by a PRE-EXISTING, unrelated
luxfi/keys@v1.2.0 go.sum checksum mismatch; ha was added via `go get` +
marked direct by hand. Re-run tidy once that pin is fixed.

Co-authored-by: hanzo <z@hanzo.ai>
2026-07-08 23:11:34 -07:00
zandGitHub d7e578f475 Merge pull request #195 from hanzoai/feat/ai-login-manager
feat(cloud): analytics.datastore entitlement gate for paid per-org usage analytics
2026-07-08 17:20:58 -07:00
hanzo-dev c7b547ce22 feat(cloud): analytics.datastore entitlement gate for paid per-org usage analytics 2026-07-08 17:01:45 -07:00
hanzo-dev 67e48170bc test(cli): uploadOutputs takes active org 2026-07-08 16:38:10 -07:00
hanzo-dev 95e60faae1 Merge commit '02043ca' into HEAD 2026-07-08 16:37:47 -07:00
hanzo-dev bade567e65 harden(build): -mod=readonly + GOSUMDB-on + digest-pinned bases (RED money-image gate)
Per RED's conditional GO on the encryption image:
- GOFLAGS -mod=mod -> -mod=readonly: the committed go.sum is the SOLE source
  of truth; any needed-hash drift FAILS the build instead of silently
  re-recording an unverified hash. Verified go.sum is complete + sumdb-
  consistent (go build/download clean with GOSUMDB ON).
- Drop GOSUMDB=off: a money image must not blanket-disable the checksum
  database. GONOSUMDB scoped to zap-proto/* only (first-party-direct).
- Digest-pin the three base images (node:24-alpine, golang:1.26-alpine3.22,
  alpine:3.22) @sha256 for a reproducible money image.

The ldd/readelf link proof stays belt-and-suspenders behind the ciphertext
proof (verified at build time on the musl image).
2026-07-08 16:16:07 -07:00
hanzo-dev 4c3c1053fb fix(console-sec): rate-limit keys on validated principal, not spoofable XFF (RED)
The limiter guards the OFF-GATEWAY path where nothing trusted stamps
X-Forwarded-For, so keying on the client-settable XFF let an attacker send a fresh
value per request and reset the 30/min bucket at will. These are all post-auth
money-write routes, so key on the un-spoofable VALIDATED principal (X-Org-Id/
X-User-Id, minted by SanitizeIdentity from a verified JWT); fall back to the socket
peer (L4 RemoteAddr) for an unauthenticated request (which the handler 403s anyway).
Test now rotates XFF during the flood (must NOT reset) and asserts a second principal
keeps its own bucket.
2026-07-08 16:14:38 -07:00
hanzo-dev 1e2f549034 feat(console-sec): CSRF token on money writes + per-IP rate limit (RED hardening)
Cloud-direct/off-gateway money path loses the edge WAF/limiter and the embed
session-bridge's Sec-Fetch-Site gate passes VACUOUSLY when Origin/Referer/SFS are
all absent (RED). Adds two positive controls to the console write surface:

CSRF (csrf.go) — GET /v1/console/csrf issues a token bound to the validated
principal (X-User-Id+X-Org-Id), MAC'd with keyed BLAKE3 (luxfi/crypto,
blake3.KeyedHash) under a server-only KMS key (CONSOLE_CSRF_KEY; ephemeral
per-process fallback). requireCSRF enforces X-CSRF-Token on the AMBIENT-cookie path
ONLY (no Authorization + a Cookie present) — Bearer/Basic/gateway/API callers are
immune to CSRF and skip it, so nothing non-browser breaks. A cross-site page cannot
read the same-origin token (SOP) nor set the custom header (no CORS preflight
granted), and the token is identity-bound so it can't be replayed as another user.

Rate limit (ratelimit.go) — per-IP token bucket (30/min) on mint/rotate/revoke key
+ wallet top-up; distinct from commerce's spend-cap, restores frequency protection
lost off-gateway. Keyed on XFF first-hop.

Wraps POST/DELETE keys, POST onboard, POST topup, POST billing, POST/PUT/PATCH/DELETE
commerce. Reads stay open. Tests: ambient-no-token 403, valid-token 200,
cross-identity replay 403, Bearer-skips-CSRF 200, rate-limit 429; existing suites
unchanged (no cookie ⇒ CSRF skipped). luxfi/crypto for the MAC (NOT stdlib/JWT).

Needs arcd build + RED review; CONSOLE_CSRF_KEY to be provisioned via KMS for
restart/multi-replica-stable tokens (coordinate ac742480).
2026-07-08 16:14:38 -07:00
hanzo-dev 5b8e4b7daa fix(cloud-direct): stamp X-User-Name; mint hk- keys by owner/username not owner/uuid
The in-binary direct-Bearer path (console SPA -> cloud, gateway bypassed) stamps
X-User-Id = the JWT subject (a UUID) via idClaims.userID(). The console key ops
built the IAM id as <owner>/<X-User-Id> = hanzo/<uuid>, but IAM's mint-user-keys /
get-user resolve only <owner>/<name> (hanzo/z) -> 'password or code is incorrect'
-> hk- mint 502 on the cloud-direct path. (The gateway path worked because the
gateway minted X-User-Id == username.)

Fix (narrow blast radius, per RED-preferred approach — does NOT reorder userID()):
- idClaims.username(): the IAM username (name claim, then preferred_username),
  NEVER the subject.
- SanitizeIdentity stamps X-User-Name from the validated username, DISTINCT from
  X-User-Id. X-User-Name is already an authorityHeader (stripped on ingress,
  re-injected only from validated claims -> forgery-proof).
- resolveCaller carries a distinct caller.username (X-User-Name, fallback to
  X-User-Id for the gateway path); new caller.keyID() = <owner>/<username> is used
  ONLY by the user-key ops. caller.id / caller.name are UNCHANGED, so the
  billing/topup/commerce subjects are byte-identical -> zero money-path impact.

Tests: TestKeys_DirectBearerPath_MintsByUsernameNotUUID (mint targets hanzo/z, not
the UUID), TestSanitizeIdentity_StampsUserName, TestSanitizeIdentity_UserNameForgeryStripped;
existing key + identity suites unchanged (gateway path falls back to owner/name).

Needs arcd/CI image build (no local docker) + RED review before deploy.
2026-07-08 16:14:38 -07:00
hanzo-dev 68f0becf1c build: CGO=1 + libsqlcipher encrypted image (was CGO=0 PLAINTEXT) + KAT gates
The unified binary embeds IAM's per-org SQLCipher store and commerce's
per-tenant money DBs; the prior CGO_ENABLED=0 build shipped pure-Go
modernc — PLAINTEXT at rest. Rebuild CGO=1 against system libsqlcipher
(hanzoai/iam's proven recipe: libsqlite3 tag + libsqlcipher symlink +
-DSQLITE_HAS_CODEC), runtime base scratch -> alpine:3.22 + sqlcipher-libs
(CGO needs libc + the codec .so).

Baked-in RED gates (a failing gate = NO image):
- modernc double-registration guard: 0 modernc in the CGO=1 ./cmd/cloud
  graph (the one 'sqlite' driver is mattn/SQLCipher).
- TestEncryptionProof: real ciphertext-at-rest under SQLITE_REQUIRE_CODEC=1.
- cek.go golden-vector KAT (TestUnwrapGoldenFixture + round-trip): a frozen
  pre-luxfi-swap 61-byte DEK sidecar still decrypts under the shipped
  luxfi/crypto-AEAD code — existing encrypted stores stay readable.
- readelf/ldd link proof: the binary binds sqlite3_* to libsqlcipher, never
  a plaintext libsqlite3.

Console embed stage unchanged (same-origin console). RED must review before
the image ships.
2026-07-08 16:03:57 -07:00
hanzo-dev f4f271b39e deps: converge SQLite onto one driver — bump sqlite/orm/base/commerce/o11y/replicate
Bump the six hanzo modules to their driver-converged releases so the CGO=1
unified binary has EXACTLY ONE database/sql 'sqlite' registration
(mattn/SQLCipher), ending the 'sql: Register called twice for driver
sqlite' panic:
  sqlite     v0.1.5   -> v0.2.3   (SetPersistWAL + OpenPragma primitives)
  orm        v0.5.2   -> v0.6.1
  base       v1.4.6   -> v1.5.7   (+ replicate v0.9.5, the last modernc leak)
  commerce   v1.42.29 -> v1.46.40 (+ go:embed plans fix)
  o11y       (pseudo) -> v1.5.1
  replicate  v0.8.0   -> v0.9.5

Retarget the mattn v2.0.3+incompatible replace v1.14.16 -> v1.14.47 (the
SetFileControlInt/SQLITE_FCNTL_PERSIST_WAL-capable version hanzoai/sqlite
v0.2.3 needs for SetPersistWAL).

Verified CGO=1: 0 modernc in the ./cmd/cloud dep graph; the 517MB binary
builds and boots (--help) with NO double-register panic.
2026-07-08 16:00:21 -07:00
hanzo-dev 02043cacea gpu connect: materialize uploaded inputs + route output to active org
studio.render now (1) writes any inputs shipped with the job into the
local studio input dir via its own /upload/image, so an uploaded photo
(which lives in orgs/{org}/input on the dispatching pod, unreadable here)
resolves for LoadImage before the render; and (2) forwards the job's
active org as the studio_active_org cookie on /upload/output, so the
finished render lands in that org's gallery even when the worker token's
home org differs (a@hanzo.ai home=hanzo, rendering for karma).
2026-07-08 15:50:46 -07:00
hanzo-devandGitHub dcff8ab973 feat(cloud): SuperAdmin canonicalization + per-org entitlements API (#194)
SuperAdmin: /v1/admin/me and /v1/admin/users now emit the canonical
`isSuperAdmin` key alongside the deprecated back-compat alias `isGlobalAdmin`
(both populated with the SAME fact — owner == AdminOrg). The console may read
either during the rename migration and sees the same truth. No DB change: the
signal was always a derived boolean, never a stored column.

Entitlements: new clients/entitlements subsystem (order 139) — the per-org
product-enablement plane the console's paid-product sidebar reads.

  GET  /v1/orgs/:org/entitlements  -> { "enabled": [...] }
  POST /v1/orgs/:org/entitlements  { add?, remove? } -> { "enabled": [...] }

Two authorities, never braided: ENABLEMENT (this store: durable per-tenant
SQLite, (org,product) key, settings-store discipline) vs ENTITLEMENT (commerce:
deps.Commerce.CheckEntitlement at write time). A non-super-admin may only enable
a product the org's plan already grants (402 otherwise); disabling is never
gated; a super admin bypasses the commerce gate and may target any :org. Org
scoping mirrors clients/kms: :org must equal the validated owner claim unless the
caller is a super admin; a bearer-less forge fails the principal gate (403).

Tests (TDD, all green): store tenant-isolation + all-or-nothing Apply;
forged-request 403; cross-org 403; malformed org/product 400 (commerce not
consulted); entitled enable 200; unentitled enable 402 (nothing persisted);
super-admin bypass 200 (commerce not consulted); nil-commerce member-add 503
(fail-closed); remove never gated; empty mutation 400. Plus admin_test asserts
isSuperAdmin present and equal to isGlobalAdmin on both /me and /users.
2026-07-08 15:12:41 -07:00
zandGitHub 15c51ebea6 Merge pull request #191 from hanzoai/feat/world-pricing
feat(world): plan enforcement contract + GET /v1/world/limits
2026-07-08 13:55:41 -07:00
hanzo-dev 6ed1484419 chore: pin hanzoai/plans to released v1.4.0 2026-07-08 13:55:37 -07:00
hanzo-dev 35209eec56 feat(world): plan enforcement contract + GET /v1/world/limits
Bumps @hanzo/plans to the World-pricing catalog (world-enterprise tier +
world.model_api gate) and adds the single-sourced enforcement contract for
the /v1/world data plane.

- clients/plan: export Entitlements(ctx, id) — the one Go seam to read a
  plan's canonical entitlement block from the @hanzo/plans catalog (runs the
  bundle 'entitlements' route; no data duplication, no fromLegacy re-impl).
- clients/world/entitlement.go: WorldLimits + WorldLimitsFromEntitlements
  (pure) + ResolveWorldLimits(ctx, planID) — values sourced from world.*
  entitlements, never hardcoded. FreeWorldLimits is the fail-closed floor
  (catalog outage degrades to Free, never grants model/stream).
- GET /v1/world/limits?plan=<id>: machine-readable contract echo so agents/
  dashboard self-config against the live catalog instead of hardcoding tiers.
- Tests: contract mapping (all tiers), fail-closed on unmounted catalog, and
  end-to-end Entitlements against the real embedded bundle (world.model_api
  present on pro/enterprise, absent on free).

Per-request enforcement (org->plan resolution + rate limiter wiring) is the
documented follow-up owned with feat/world-model-engine; both gates resolve
through ResolveWorldLimits so policy stays single-sourced.
2026-07-08 13:49:29 -07:00
faf7adec55 fix(wallets): retry Safe deploy on 'wallet not found' (same ring commit race, DRY) (#190)
Proxy capture of cloud->ring proved the Safe flow hits the ring's commit-after-
response read-after-write race TWICE, not once: createVault->createWallet ('vault
not found', already retried) AND createWallet->deploy ('wallet not found', which
502'd custody=safe). With ALL requests pinned to one node (via a debug proxy) the
deploy STILL 404'd, so it is a Postgres commit-visibility lag, not node affinity.

Extract doRetryNotFound(...notFound) (bounded 6x/250ms linear, ctx-aware, fail-fast
on any other error; do() only unmarshals on 2xx so out is safe across retries) and
use it for BOTH createWallet ('vault not found') and deploySafe ('wallet not
found'). go test ./clients/wallets/... green; cmd/cloud builds.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 13:42:44 -07:00
7776439ed5 fix(kmssvc): require explicit env on secret writes (no silent default) (#189)
The embedded KMS write path POST /v1/kms/orgs/{org}/secrets defaulted a
missing env to "default" (envOr), committing the write to a bucket that
project/env/path readers (the kms-operator, cluster syncs) never resolve.
That split is what let an IAM z-password land in env=default while prod kept
serving the stale value. env is a first-class component of the storage key
(kms/secrets/{path}/{env}/{name}) and cannot be aliased, so a write with no
env now fails loud (400). GET/DELETE/LIST keep the envOr compat default (a
read/delete can't plant a value another reader trusts; legacy readers that
omit env must keep working). No PATCH route exists on this surface.

Regression tests: write without env -> 400 (and lands nowhere); write
env=prod is readable via the operator's project/env/path resolution (sha256
round-trip, values never printed) and is not visible in env=default. The
fail-closed-without-master-key test now sends a valid env so it still
exercises the 503 master-key gate rather than 400-ing on input.


Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 12:04:34 -07:00
hanzo-dev 48e77f643a feat(config): additive CLOUD_ENABLE_STAGED lever — activate staged subsystems without an allowlist
Enabled() staged path is now orthogonal to the Enable allowlist: a staged
subsystem (iam/ingress) mounts when named in EITHER Enable (strict allowlist) OR
the new EnableStaged (additive). CLOUD_ENABLE_STAGED=iam + empty CLOUD_ENABLE =
all-non-staged prod default PLUS iam — the faithful iam-fold canary/cutover shape
with NO hand-enumerated allowlist that silently drops a newly-added subsystem.

Proven: TestEnabled_StagedActivatesAdditively (iam on, non-staged default intact,
unnamed staged sibling stays off).
2026-07-08 12:01:06 -07:00
7d33041580 deps: bump hanzoai/ai -> #71 session-resolution fix (ai#79); iam stays v1.31.18 (#188)
Completes the #71 auth repair as a clean dep bump (the fix lives in ai + iam, not
the cloud tree):
- github.com/hanzoai/ai v1.802.0 -> v1.802.1-0.20260708185316-0321c35877f0
  (ai#79 0321c358: self-heal get-account identity — stop degrading real logins to
  u-<hash> guests; fail-closed 401). Pseudo-version pins the commit while the
  semantic-release patch tag mints (1 commit ahead of v1.802.0).
- github.com/hanzoai/iam v1.31.18 already pinned in main (iam#109 fail-closed
  guest-mint gate) — MVS keeps it over ai's older iam pin.
go mod tidy added the authentic gopsutil/v4 transitive hashes (iam util); go mod
verify OK; -mod=readonly CGO_ENABLED=0 go build ./cmd/cloud green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 11:58:25 -07:00
hanzo-dev 2e2f8f2a1e fix(iam): isolate embedded IAM's SQLite via IAM_DATABASE_URL — unblock iam+ai co-residence
Both the iam and ai casdoor-derived forks resolve their SQLite handle from the
SAME env key (dataSourceName) + the one beego web.AppConfig global. A deployment
sets dataSourceName for ai; with iam enabled, IAM's bootstrap resolved that same
value and xorm-opened ai's DB (auto-migrating casdoor tables into it) -> the
documented boot crash that pinned every post-embed release and kept iam staged.

IAM's conf already honors an IAM-scoped IAM_DATABASE_URL above the shared
dataSourceName; pin it to IAM's own iam.db under DataDir so the two forks get
independent stores, order-independent, NO fork edit. Operator override respected.

Unit-proven: TestIsolateDatabase (iam-owned DSN, != ai dataSourceName, respects override).
2026-07-08 11:55:47 -07:00
hanzo-dev ed706d5356 Merge fix/embed-session-principal-bridge: embed session→principal bridge + RED H2/H3 + iam v1.31.18 (H1)
Makes console.hanzo.ai (go:embed console) authenticate its money surfaces: the
first-party IAM session cookie → validated principal (sessionAccessToken → v.validate),
RED-hardened (H2 Secure cookie, H3 same-origin bridge gate), on iam v1.31.18 (H1
session-regeneration + iam-main security fixes). Pairs with console v8.4.122 which
addresses billing/commerce/keys at the canonical bare /v1 in embed mode.
2026-07-08 10:13:34 -07:00
hanzo-dev ae01163d6d deps(embed): pin hanzoai/iam v1.31.18 — H1 session-regen + iam-main security fixes ∪ InitEmbed
v1.31.18 is iam main (guard-leak stamp #108, guest-signin fail-closed #109, capauth
PermAttenuate #106) UNION the InitEmbed line UNION RED H1 (SessionRegenerateID on the
sign-in transition). The prior embed pin v1.31.17 had diverged off an old base and was
MISSING those iam-main security fixes, so pinning v1.31.17+H1 would have shipped the
money embed without them. v1.31.18 ships H1 + guard-leak/guest/capauth + InitEmbed
atomically into this binary's in-process IAM. Transitive indirect bumps (purego/
plan9stats/locafero/gopsutil-v4/viper/tidwall-match) are MVS-driven by iam v1.31.18.
2026-07-08 10:13:16 -07:00
hanzo-dev 3f7f238db7 auth(embed): RED fixes H2+H3 on the session→principal bridge
H2 (HIGH) — pin the IAM session cookie Secure. clients/iamsvc/iamsvc.go derived
Secure from web.BConfig.Listen.EnableHTTPS, which is FALSE (the binary listens plain
:8000 behind the TLS-terminating ingress) → the session cookie shipped non-Secure.
The embed bridge turns that opaque sid into a money bearer (hk- mint, balance/top-up),
so a non-Secure cookie is capturable off any plaintext leg and replayable. Pinned
Secure: true (the deployed edge is always HTTPS).

H3 (MED-HIGH) — gate the ambient-cookie bridge to same-origin. billing.go/commerce.go
forward GET verbatim to commerce; a SameSite=Lax cookie still rides a top-level GET, so
a cross-site link could drive the victim's own money action if any commerce GET mutates.
validatedPrincipal now fires the session bridge ONLY for a same-origin request
(sessionBridgeSameOrigin: Sec-Fetch-Site same-origin|none, else Origin/Referer
host==Host) — refusing cross-site AND sibling-subdomain (same-site). Bearer/JWT-cookie
paths (non-ambient) are unaffected. +TestSessionBridgeSameOrigin (7 cases) green.

REMAINING for money: H1 (session-fixation — SessionRegenerateID on the IAM sign-in
transition) lands in hanzoai/iam (compiled into this binary); coordinating.
2026-07-08 09:55:08 -07:00
hanzo-dev 56a0405d92 auth(embed): bridge first-party IAM session cookie → validated principal
The go:embed console (console.hanzo.ai → cloud:8000) authenticates against the
in-process IAM, which sets an OPAQUE, httpOnly session cookie (cloud_session_id)
and stores the user's IAM-minted access-token JWT SERVER-SIDE against that session.
The console's Next BFF token-minting routes are stripped by the static export, so a
browser request to a cloud-native route (/v1/console/keys, /v1/billing/*) carries
only the session cookie — no bearer — and validatedPrincipal refused it, 401ing
every authenticated surface (API keys, billing, every product page = shell).

validatedPrincipal now resolves that session cookie to the server-stored access
token (sessionAccessToken via web.GlobalSessions) as a LAST RESORT (after Bearer/
Basic/JWT-cookie), then validates it through the SAME v.validate (sig/iss/aud/exp).
Identity is bound to the VALIDATED session: the client holds only an unguessable,
httpOnly sid; the session never asserts identity itself. No-op on gateway-fronted
binaries (a bearer is present) and on binaries with no IAM session manager
(web.GlobalSessions == nil) — tested. CSRF: cloud_session_id is SameSite=Lax, so a
cross-site request never carries it; and cookieTokenNames already establishes cloud's
JWT-cookie auth posture. This is the v8.4.5-flagged 'set the cookie the sanitizer
looks for' path, done cloud-side from the session store (no cross-repo IAM release).

RED review requested before it fronts money (session-fixation / CSRF surface).
2026-07-08 09:55:08 -07:00
ea232dbcd7 feat(automations): waitlist points connectors — x/discord verify + award_points seam (#187)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 09:21:54 -07:00
57200605cd fix(console): default HANZO_CHAIN_ID to genesis-canonical 36963 (#186)
topupConfig defaulted to the placeholder 36900; align to the
genesis-canonical Hanzo mainnet chain id 36963 (lux/genesis, and the
rest of cloud clients/treasury+wallets already use 36963). Still
env-overridable via HANZO_CHAIN_ID.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 09:01:20 -07:00
hanzo-devandGitHub a84180c542 refactor(cloud): one /v1/o11y owner (embedded runtime); split settings out of observe (#185)
The observability surface was mounted THREE ways over the same /v1/o11y/* paths:
clients/observe (order 44), clients/o11y's o11yscope (order 69), and the
hanzoai/o11y wildcard runtime (70/71). observe also served /v1/settings/:product,
which is console product config, not observability. Collapse to one and one way.

- ONE owner of /v1/o11y/{logs,metrics,status}: clients/o11y's o11yscope (order 69).
  observe's richer logic is folded IN so nothing is lost — the REAL per-org RED
  metrics + LLM usage (metricsread.go, was a stub in o11y) and the two-view logs
  (admin infra stdout / per-org request-from-traces). Tenant isolation preserved:
  org is principal.Tenant bound as a positional ClickHouse param, the product is
  shape-validated → alias-mapped (console slug → workload) → allowlisted
  (knownServices, SSRF/injection boundary). observe's productAlias merged into
  resolveService so no product loses data. Admin god-view gates on c.IsAdmin()
  (== owner=="admin" SuperAdmin after SanitizeIdentity), never a per-org isAdmin.

- /v1/settings/:product moved OUT of observe into clients/settings (it is NOT
  observability). Behavior/contract preserved verbatim from observe: {config,
  secretKeys} shape, KMS ref orgs/{org}/settings/{product}/{key}, (org,product)
  store isolation, secrets-to-KMS-or-fail-closed. Replaces the orphaned, divergent
  clients/settings stub with the live behavior and wires it in (order 138).

- /v1/query does not exist (no registrant, no consumer) — nothing to fold.
  /v1/observe/health was the auto-derived GET /v1/<id>/health for id "observe";
  it vanishes with the subsystem (o11yscope gets /v1/o11yscope/health; the runtime
  serves its own gate-exempt /v1/o11y/api/v*/health*). Both documented.

- DELETE clients/observe; drop its import; add clients/settings; fix the stale
  subsystems.go o11y comment ("reverse proxy to the dedicated o11y Deployment" →
  the embedded reality: scoped reads 69 + in-process runtime 71 + OTLP ingest 72).

Net -1037 LoC. cmd/cloud + cmd/hanzo build; clients/o11y + clients/settings tests
pass (20/20), covering tenant isolation, secrets-never-plaintext, product
validation, alias resolution, and route precedence over the wildcard proxy.
2026-07-08 08:58:18 -07:00
674b599833 refactor(cloud): canonical subsystem names — drop svc suffixes, one noun per capability (#184)
One canonical short-noun name per subsystem (registered name + Go package dir +
route). No public route breaks: renames that change a live /v1 prefix keep the
old route as a back-compat alias (mount both, same handlers).

Renamed (internal-only, route unchanged):
  usagesvc  -> usage        (register string)
  zt        -> zero-trust   (register string; pkg dir kept `zt`, routes /v1/networks|mesh|edge unaffected)
  auditlog  -> audit        (register string; route already /v1/audit)
  s3        -> storage       (dir+pkg+register; route /v1/s3 kept — route-safe)
  tasksvc   -> tasks         (dir+pkg; register already `tasks`)
  iamsvc    -> iam           (dir+pkg; register already `iam`)
  mpcseal   -> mpc           (internal lib dir+pkg; importers repointed, local alias kept)
  gojahost  -> goja          (internal lib dir+pkg; importers repointed)

Renamed with public route + back-compat alias:
  kb        -> knowledge     (dir+pkg+register; canonical /v1/knowledge added, /v1/kb alias kept; framework module id `kb` retained = data-model id)

Log "subsystem" labels aligned to canonical names. Subsystem test enable-lists
and stale clients/<old> path comments updated. stagedSubsystems already
canonical ({iam,ingress}).

Held (route collisions — CTO decision):
  ml -> models       COLLIDES /v1/models (OpenAI-compat catalog owns it) — kept `ml`
  websearch -> search COLLIDES /v1/search (provisioned search resource) — kept `websearch`
  kmssvc dir         register+route already canonical (`kms`, /v1/kms); dir kept
                     to avoid colliding with the `clients/kms` SecretStore core lib.

Not present in repo: gatewaysvc / gatewaypolicy (gateway is a separate deployment).

Build: CGO_ENABLED=0 go build ./... green; go vet green; tests green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 08:55:27 -07:00
hanzo-devandGitHub 873118d77c refactor(cloud): decomplect subsystem registration — Typed adapter, OwnsHealth flag, generic pick[T], clean ids (#183)
One coherent change to the subsystem-registration layer. Concrete types over
`any` at the call sites, indirection deleted, generics only where they remove
real duplication.

CHANGE 1 — kill the per-subsystem `any`-unwrap boilerplate
  Every in-repo subsystem's init() hand-wrote the identical
    func(app any, deps cloud.Deps) error { a, ok := app.(*zip.App); if !ok {…}; return Mount(a, deps) }
  Add ONE adapter, cloud.Typed(func(*zip.App, Deps) error) MountFunc, that does
  the *zip.App recovery in a single place (fail-closed, never panics). All ~50
  subsystems collapse to `cloud.Register("x", n, cloud.Typed(Mount))` /
  `cloud.RegisterWithShutdown(..., cloud.Typed(Mount), Shutdown)`. Redundant
  shutdown wrappers dropped where Shutdown already matches ShutdownFunc; kept
  only where a no-arg Shutdown() needs signature adaptation.
  MountFunc's param STAYS `any` on purpose: the pinned external subsystem modules
  (hanzoai/ai, authz, base, commerce, metrics, o11y, licensing) register with
  `func(any,…)`, and a `func(any,…)` literal is not assignable to a
  `func(*zip.App,…)` parameter — retyping MountFunc would break those modules at
  compile time. The assertion is now central, not per-subsystem. MountAll takes
  the concrete *zip.App (threaded from Serve).

CHANGE 2 — OwnsHealth flag replaces the "<name>svc" health kludge
  Some subsystems serve their OWN fail-closed /v1/<name>/health; the generic
  always-ok liveness route in Serve would shadow it. The old fix encoded routing
  policy in the id ("kmssvc" parked the generic route at an unrouted path). Now
  Register/RegisterWithShutdown take `opts ...Option`; cloud.HealthOwner sets
  MountSpec.OwnsHealth, and Serve's generic-health loop skips a HealthOwner. The
  id is once again the clean route name. Invariant now uniform and checkable:
  a subsystem serves /v1/<name>/health  IFF  it registers cloud.HealthOwner.
  Migrated every health-owner to it: kms, paas, s3 (named in scope) plus
  analytics, console, platform, ml (same kludge) and notify, plans, pricing,
  security (had coincidental id==route; security's real probe reports a rule
  count the generic route was silently dropping). pickKMSClient gate + all
  tests + stale comments updated from the "kmssvc"/"s3svc"/… ids to kms/s3/….

CHANGE 3 — clean package renames (no collision)
  clients/paassvc → clients/paas, clients/projectsvc → clients/projects
  (package decls, filenames, the sole importer, error strings, userAgent, and
  doc refs repo-wide). clients/kmssvc + clients/tasksvc KEEP their package names
  — the `svc` disambiguates the subsystem from the same-named library it imports
  (clients/kms, hanzoai/tasks); their ids are already clean (kms via CHANGE 2,
  tasks).

CHANGE 4 — generic pick[T]
  The five identical co-resident-or-RPC-or-disabled resolvers (IAM, Base,
  Commerce, O11y, MQ) collapse into one
    pick[T](cfg, log, name, label, zapAddr, rpc func(string)T, disabled func()T) T.
  KMS/AI/VFS/Payments/Vault keep bespoke pickers — their construction genuinely
  differs (embedded store / gateway preference / S3-admin backend / never
  co-resident), so they are left alone.

Verified: CGO_ENABLED=0 go build ./cmd/hanzo/ and ./cmd/cloud/ both exit 0;
go vet clean on every changed package; `hanzo --help` lists kms/paas/projects/
s3/tasks svc-free; cloud root + renamed + health-owner package tests pass; new
build_registration_test.go covers Typed + HealthOwner. Net −199 lines.
2026-07-08 08:13:52 -07:00
hanzo-dev 94c5c40d13 Merge branch 'feat/control-plane-ceremony'
# Conflicts:
#	config.go
2026-07-08 07:59:17 -07:00
hanzo-dev 806beeee34 chore(cloud): repin luxfi/consensus v1.35.30 -> v1.35.32 (DoS bound + 1-based fix)
Picks up the increment-2 crypto hygiene: the PartyID<=ValidatorSetSize DoS
bound on the quasar/pulsar Finalize path (Item7a) + the structural-Verify lock
(Item7b). v1.35.32 corrects a 1-based off-by-one in v1.35.31 that rejected the
Nth validator; verified the controlplane N=7 ceremony finalizes under -race.
LOW severity (ingestLeg bounds PartyID upstream) but the fix is now live-pinned.
2026-07-08 07:56:58 -07:00
hanzo-dev 0acb4440b2 merge: two-plane epoch write-fence primitive (strict-> + atomic CAS) 2026-07-08 07:51:42 -07:00
hanzo-dev eded7e4ef3 merge: controlplane containment cage (CI guard + fail-closed assert + external-cert seam) 2026-07-08 07:51:41 -07:00
fd05bf9860 feat(ingress): embedded runtime-configurable edge subsystem (/v1/ingress) (#182)
Add clients/ingress — an embedded edge plane in the cloud binary so the ONE
binary can BE the fleet edge: terminate TLS, run ACME, and reverse-proxy by Host
to upstreams, configured LIVE over /v1/ingress with no static routes.yaml and no
restart to change a route (hot-apply via an atomic engine snapshot swap).

Control plane (zip): /v1/ingress/{routes,services,middlewares,tls,status},
SuperAdmin-gated, per-tenant SQLite persistence, route Host globally unique;
every mutation reloads the engine.

Data plane (net/http): :80 (ACME HTTP-01 + router) and :443 (SNI TLS termination
via x/crypto/acme/autocert + router). Started only in edge role
(CLOUD_INGRESS_EDGE_ENABLED); app role keeps the listeners off — role = runtime
config, one binary.

Proxy: github.com/vulcand/oxy/v2 (Traefik lineage) weighted round-robin, the
Traefik router->service->middleware model. Middlewares: redirectScheme,
stripPrefix, addPrefix, headers.

STAGED subsystem (config.stagedSubsystems): linked but mounts ONLY when named in
CLOUD_ENABLE, so prod is untouched. Orthogonal to /v1/gateway (auth/rate-limit).

Build: CGO_ENABLED=0 go build ./... green; go test ./clients/ingress green (11 tests).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 07:45:37 -07:00
hanzo-dev 0ba6d72c44 fix(writefence): injective mirror key + single-read Get (red pass)
Red-team findings on the write-fence primitive:
 - HIGH: mirrorKey(plugin,shard) = "writefence/"+plugin+"/"+shard was not
   injective — mirrorKey("kms/tenant-a","secrets") collided with
   mirrorKey("kms","tenant-a/secrets"), so a push framed as one shard could
   overwrite another's epoch/writer/payload. Real shard scopes carry '/'
   (vfs replica.DBPath yields "projects/site"), so it is reachable. Fixed with
   a %d:-length-prefixed key; TestMirrorKeyInjective_NoCrossShardAliasing locks
   it (was red's failing PoC, now green).
 - LOW: MinioConditionalStore.Get did StatObject+GetObject (two round trips);
   tightened to one GET whose obj.Stat() ETag is consistent with the read bytes
   — closes the window rather than relying on the CAS to absorb a stale version.
Core CAS/epoch soundness unchanged (red GO: N=64 same-epoch race → one winner,
retry-bounded, strict-> rejects epoch==recorded). Still shadow-only, unwired.
go test -race -count=200 green.
2026-07-08 07:26:02 -07:00
hanzo-dev 0f9e44b0ee harden(containment): grep also catches -tags negation form (red pass)
Red-pass finding: the check-#1 grep char class [A-Za-z0-9_, ] missed the
build-constraint negation form `-tags '!x,controlplane'` (the `!` broke the
match before reaching controlplane). Add `!` to the class so it is caught.

Verified the deeper guarantees hold (evasion-agnostic), so this is belt-only:
 - ZERO non-test importers of clients/controlplane (grep-confirmed).
 - The package has ZERO untagged files, so importing it into serve code fails
   the untagged `go build ./...` — check #3 catches ANY -tags syntax, incl.
   GOFLAGS=-tags=controlplane (verified: the pkg becomes buildable => check #3's
   'matched no packages' assertion fails => CI red).
Runtime asserts + external-cert selfComposedCert seam confirmed wired through
guarded constructors. No stub-crypto path reaches a serve binary.
2026-07-08 07:18:31 -07:00
hanzo-dev 7a07a38f1f harden(controlplane): CI guard also catches the testing.Testing() spoof vector
Self-review finding: containment.go's runtime guard trusts testing.Testing(),
which is backed by a linker-set string var (testing.testBinary, set by `go
test` itself per cmd/go/internal/load/test.go). Confirmed locally that
`go build/run -ldflags="-X testing.testBinary=1"` spoofs it to true in a REAL
(non go-test) binary — verified with a throwaway program before writing this.

containment.yml's grep step now also fails the build on any reference to
`testing.testBinary` outside the Go toolchain itself, so a build path that
tried to ship that spoof gets caught the same way a `-tags controlplane`
build path does. Documented as a known residual in the workflow's header:
this is a mitigation (CI catches it), not a cryptographic close — that needs
increment-2's real signing, tracked in doc.go.

Also fixed the exclusion patterns to be grep-implementation-agnostic (some
recursive greps don't prefix paths with "./"), verified against a planted
violation for both checks.
2026-07-08 07:09:47 -07:00
hanzo-dev 63389d6e45 fix(writefence): strict-epoch, atomic-CAS write-fence for the (plugin,shard) mirror
Closes the same-epoch double-write on the HIP-0107 data-plane push path
(github.com/hanzoai/vfs/replica, wired in internal/org): today the only
admission checks are replica.IsOwner (a pure local computation over a
possibly-stale membership view) and the StatefulSet Recreate deployment
shape (role.Role) — both comment-only, non-atomic, and the underlying
Store/Backend.Put is an unconditional overwrite ("Overwriting is allowed").
A deposed/partitioned writer and a freshly-elected one can both push.

internal/writefence/fence.go adds Fence.Push: a single atomic
read-check-CAS that (1) rejects any candidateEpoch <= the epoch currently
recorded for the shard (strict >, closing the same-epoch case) and (2)
performs the epoch-advance and payload append in ONE conditional write
against the store's live version token, so two racing writers cannot both
land — the store is the sole arbiter, never an in-memory cache. Retries
once on a lost CAS race, re-checking strict monotonicity against the new
state, so a same-epoch racer's retry fails ErrStaleEpoch rather than
silently duplicating the admit.

EpochSource is the pluggable seam clients/controlplane's lease epoch drops
into once it graduates from shadow (Stage 1 today) — this package imports
nothing from controlplane. ConditionalStore models the S3 If-Match / GCS
generation-match primitive; store.go backs it for real with minio-go's
native SetMatchETag/SetMatchETagExcept (already vendored at v7.0.100, no
go.mod bump). fake_test.go models the same semantics in-process with a
barrier hook that deterministically reproduces the concurrent-CAS race.

Tests prove: strict-epoch rejection of a same-epoch retry (same and
different writer), the raw CAS rejecting a race loser, the full
concurrent-Push race resolving to exactly one winner, a legitimately
higher epoch being admitted, a stale lower epoch being rejected, and
per-shard scoping. Not yet wired into the live push path (that remains
gated by controlplane's shadow flag per HIP-0116); this is the fence
primitive plus a precise wiring recommendation for hanzoai/vfs's block
layer, which currently exposes no conditional-write capability to adopt.
2026-07-08 07:07:17 -07:00
hanzo-dev c0f1f07c4b harden(controlplane): CI+runtime containment cage + external-cert type seam
Stage-1 ceremony's crypto is stub/forgeable by design (doc.go); this closes
the drift risks doc.go's increment-2 worklist flagged:

- .github/workflows/containment.yml (PR-gated): greps every build/release
  surface in the repo for `-tags controlplane` and fails the build if found,
  plus a positive proof that `go build ./...` links clients/controlplane into
  no cmd/ main and that the package still matches zero packages with no tag.

- containment.go: mustHarnessOnly fail-closed panics the moment this
  package's stub crypto is touched (package-import-time for the
  PartialZVerifier registration, construction-time for NewSigner/
  NewStubComposer) unless ProductionBCCSigningReady() (hardcoded false) or
  testing.Testing() (the Go toolchain's own go-test signal, unspoofable by a
  real build) holds. Proven end-to-end via a real subprocess
  (TestContainment_NonHarnessProcessRefuses), not just in-process logic.

- selfComposedCert typed seam (driver.go/signer.go): CertComposer.Compose now
  returns an unexported wrapper only it can produce; verifyOwnCertStructure
  accepts only that type, never a bare *quasar.QuasarCert. An externally-
  received cert has no way to become one, so it cannot reach the structural
  check even by mistake. VerifyExternalCert is the sole seam for such a cert
  and fails closed (increment-2 crypto not implemented). Locked from a
  black-box vantage in external_cert_test.go.

Containment verified unchanged: `go build ./clients/controlplane/...` (no
tag) still matches zero packages; `go build ./...` still links no cmd/ main
to the package; full `-tags controlplane -race` suite green, no test weakened.
2026-07-08 07:05:39 -07:00
hanzo-dev 984186bb71 analytics: bake console website-id into the console-embed build
The cloud-embedded console (console.hanzo.ai + team) is built from hanzoai/console
build:embed. hanzoai/console now ships <HanzoAnalytics/> (env-gated on
NEXT_PUBLIC_ANALYTICS_WEBSITE_ID). Default it to the console.hanzo.ai property
(7dce54ee-41f6-4751-96bf-fe005067c7c7, public per-site) in the console build stage
so the one native analytics tag renders on the next cloud build. GA4/Pixel off.
2026-07-08 06:41:24 -07:00
940da9a06a fix(anchor): EIP-2 low-S normalize the MPC signature (fixes 'invalid sender') (#180)
The luxfi/mpc threshold signer returns a NON-canonical r|s: s is frequently in the
upper half (s > N/2). luxfi/geth's tx validation (ValidateSignatureValues,
homestead=true) REJECTS high-S signatures, so the anchor's MPC-signed self-tx
failed on submit with 'invalid sender' (live: POST /v1/admin/treasury/anchor ->
status error, note 'submit: send tx: invalid sender'). recoverableSig now
canonicalizes s to N-s when it exceeds N/2 before searching the recovery id, so
the 65-byte r|s|v it hands tx.WithSignature is EIP-2-valid and recovers to the
treasury MPC wallet. Tests: TestRecoverableSig_LowSNormalization (forced high-S ->
low-S, still recovers). go test ./clients/wallets/... green; cmd/cloud builds.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 06:25:30 -07:00
hanzo-dev 3ce162b573 test(controlplane): re-red — lock double-write closure as full-ceremony invariant
Adversarially verify blue's class-A fixes hold under op COMPOSITION inside a
single block (which the original red suite exercised only as separate blocks or
single ops). Six hostile compositions — bare reassign, release+reassign,
release+assign, membership-remove+reassign, remove+release+assign, assign-steal
— are each refused end-to-end through the N=7 ceremony, and the live writer is
unchanged across every voter with its lease mirror consistent. Plus: the
authorized proven-dead handoff stays single-valued under redundant reassigns,
and assign+release of a fresh resource leaves no orphan writer (mirror desync
would be a second authority). GO: the double-write class is fully closed.
2026-07-08 06:09:40 -07:00
432a365834 fix(wallets): retry Safe createWallet on 'vault not found' (ring commit-after-response race) (#179)
The ring's :8081 commits a newly-created vault to its DB AFTER writing the
createVault 201 response, so cloud's back-to-back createVault->createWallet (fired
microseconds apart on one keep-alive connection) races the commit and read-misses
the just-created vault -> 404 'vault not found' -> custody=safe 502. A slower
client (curl, separate processes) never observes the gap, which is why manual
repro succeeded. Bounded retry (6x, linear 250ms backoff, ctx-aware) on exactly
that 404; every other error still fails fast. Idempotent per attempt (fresh body).
go build ./cmd/cloud green; go test ./clients/wallets/... green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 05:02:46 -07:00
f8b557281e treasury: bind the reserve MPC wallet as the on-chain anchor signer (#63) (#178)
Wires the #162 BindAnchorSigner seam to a real quorum signer. New:
- wallets.TreasuryAnchorSigner(org,chain): resolves-or-provisions the org's stable
  KindTreasury wallet on the ring (reserved account 'treasury' / wallet
  'reserve-anchor', idempotent) and returns its EVM address + a sign closure.
- The closure produces an EVM-recoverable r‖s‖v signature: the ring returns a bare
  r‖s (64B, no recovery id) but tx.WithSignature needs 65B, so recoverableSig finds
  the v whose recovery yields the wallet address (fails closed otherwise).
- POST /v1/admin/treasury/bind-anchor (global-admin): calls TreasuryAnchorSigner +
  BindAnchorSigner, so subsequent /v1/admin/treasury/anchor commits the ledger root
  signed by the treasury MPC wallet, not the lone KMS key. Returns the bound address
  (fund it for gas on the Hanzo L1).

Tests: TestRecoverableSig (both parities recover to the signer) + _NoMatch (fail
closed). go build ./cmd/cloud green; go test ./clients/wallets/... green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 04:37:06 -07:00
zeekayandhanzo-dev ba16080fd0 fix(o11y): restore the missing metrics-query companion — unbreak the cloud build
The o11y-scope landing added clients/o11y/{scope,status}.go referencing a metrics-
query layer (vmClient, newVMClient, promLabel, metricsQuery, queryMetrics,
metricsResult, metricPoint, usageRollup, boundRangeMinutes) whose source file was
never committed → `go build ./cmd/cloud` failed (undefined symbols), taking the
whole deploy plane down (no new cloud image buildable from main). Restore the file
to the surface's own honest-empty contract: newVMClient reads O11Y_VM_URL and an
unset/unreachable VM degrades every query to an honest-empty series (never a
fabricated point); status.go's VM up-inventory works when VM is wired. queryMetrics
returns the honest-empty RED series until the VM query_range wiring lands. Full
`go build ./cmd/cloud` now links; go test ./clients/o11y passes.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-08 04:31:12 -07:00
hanzo-devandGitHub 3a8de3cc60 chore(deps): hanzoai/ai v1.800.10-pre -> v1.802.0 (auto-routing defaults + decision collection) (#177)
Brings the embedded ai subsystem up to v1.802.0:
- #76 opt-in auto-routing (virtual auto/zen-router model, X-Routed-Model)
- #77 per-org enable/disable (OrgSettings precedence)
- #78 admin-settable defaults (reserved "*" row, /v1/get-routing-defaults)
  + RoutingEvent collection (no prompt text) + /v1/export-routing-ledger

Edge contract unchanged; auto_routing_billing_test green against the new
module (ok github.com/hanzoai/cloud). Pre-existing clients/o11y compile
break on main is untouched (fix lands separately).
2026-07-07 23:31:08 -07:00
hanzo-devandGitHub 0f7f6fe9ea refactor(auto): decomplect — remove the /v1/auto reverse-proxy + clients/auto (#176)
Kill the second automation surface. /v1/auto was a per-org reverse proxy
(clients/auto + clients/auto/proxy) to the standalone hanzoai/auto engine
(auto.hanzo.svc) — a duplicate of the native, in-process /v1/automations
Connectors+Automations engine (clients/automations, cloud.EmbeddedTasks,
706-piece catalogue). One engine, one surface: /v1/automations is the ONE
native automation engine. The external engine + its console link-out are
retired (console + universe in paired PRs).

- Remove the order-140 blank import of clients/auto from subsystems.
- Delete clients/auto/ (auto.go + proxy/).

No functional loss: /v1/automations already serves flows/versions/runs/
pieces/MCP natively. clients/kb keeps its own AUTO_UPSTREAM piece-runner
coupling (a separate, pre-existing bridge to a never-implemented engine
endpoint) — reported for a follow-up, not touched here.

go build ./... green, go vet green, go test ./clients/automations + root ok.
2026-07-07 23:11:43 -07:00
7c0a653e76 refactor(automations): rename connector catalogue pieces -> connectors (HIP-0126) (#174)
* refactor(automations): rename connector catalogue pieces -> connectors (HIP-0125)

The automations connector CATALOG surface drops the ActivePieces term "pieces" for the ONE Hanzo term "connectors":

- GET /v1/automations/pieces -> /v1/automations/connectors; /pieces kept as a
  byte-identical back-compat alias (same handler) so live clients never break.
- Catalog{PieceCount,Pieces} -> {ConnectorCount,Connectors}; PieceMetadata/
  PieceAuth/PieceAction/PieceTrigger -> Connector*; JSON tags pieceCount/pieces
  -> connectorCount/connectors; embedded catalog.json + OpenAPI updated to match.
- Test proves the /pieces alias mirrors /connectors byte-for-byte.

Deliberately UNCHANGED (persisted @xyflow builder wire contract; renaming would
break live clients + stored flows): the flow-step protocol PieceName/pieceName,
PIECE/PIECE_TRIGGER, corePiece. Aligning those is a staged migration (HIP-0125).

* chore(automations,git,framework): scrub AI-slop placeholder comments (Rob Pike pass)

Comment-only, zero behavior change. Removes agent-note narration and future-work hedges, keeps the real WHY:
- automations.go: drop "a separate agent later OVERWRITES this file" narration; keep the Catalog-is-the-wire-contract invariant.
- framework/naming.go: "value for now" -> "value derived from now" (it reads the now arg, not a hedge).
- git/git.go: drop TODO(billing) + "in the MVP" hedge; state the git.usage meter fact.
- git/storage.go: drop TODO(vfs)/MVP/follow-up narration; keep the WHY osfs (not vfs) is used (vfs.FS does not implement go-billy).
Kept as real WHY/invariants (not slop): connector_core.go loopback-test SSRF guard, connector_slack.go httptest override, affiliates/store.go  sentinel + PendingCents; types.go was already cleaned in the rename commit.

* docs(automations): point connector-rename references at HIP-0126 (0125 was taken)

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 23:01:24 -07:00
b503e3d512 feat(cloud): kill the /v1/auto ActivePieces reverse-proxy — one native engine (#175)
CTO decision: ONE automation engine = the native Go /v1/automations
(clients/automations on cloud.EmbeddedTasks). This removes the redundant
/v1/auto reverse-proxy subsystem (clients/auto), a per-org proxy to the
standalone ActivePieces Deployment (auto.hanzo.svc).

- delete clients/auto/ (auto.go + proxy/)
- drop the order-140 blank import from subsystems.go

Safe: no live caller of cloud/v1/auto — console link-outs to auto.hanzo.ai,
and clients/kb calls the engine directly via its own AUTO_UPSTREAM client
(untouched here). The native /v1/automations surface is unaffected.

NOTE (does NOT retire the ActivePieces Deployment): clients/kb/sync_piece.go
still executes connector pieces via the engine at /v1/auto/pieces/{piece}/run;
the native engine exposes the piece CATALOGUE but not piece EXECUTION yet, so
auto.hanzo.svc must stay until native reaches piece-run parity.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 22:51:02 -07:00
dbb03eb911 chore: cut AI-slop comment narration (Rob-Pike pass) (#173)
Comment-only tightenings, zero behavior change:
- pubsub/o11y: drop the misleading "GC won't collect" narration on the
  package-level server/collector refs; state the real reason (shutdown
  reachability) or the actual invariant (metrics ref is a write-only keepalive).
- iamsvc: condense the 11-line InitEmbed block that verbatim-restated the
  package doc down to the fail-closed WHY that matters at the call site.

No code changed (git diff: comments only).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 22:50:59 -07:00
0466ae3953 fix(wallets): Safe custody must create the MPC wallet via the ring PRODUCT API (#172)
Safe deploy (POST /v1/wallets/{id}/smart-wallet) resolves the owner wallet by its
db.Wallet PRIMARY KEY (orm.Get). The :9800 internal /keygen mints a threshold key
but persists NO db.Wallet row, so deploy 404'd 'wallet not found' (live: every
custody=safe create -> 502). The ring's Safe surface is VAULT-scoped: the only
create path that persists a db.Wallet AND returns its id is
POST /v1/vaults/{id}/wallets.

safeCustody.Provision now: createVault -> createWallet (vault-scoped, returns db
id + internal WalletID + EOA) -> deploySafe(dbId). KeyRef stays
<internalWalletId>|<smartWalletId> (owner-sign via :9800 uses the internal id;
propose via :8081 uses the smart-wallet id); the db id is only needed for the
one-time deploy. safeclient gains createVault + createWallet; the stub test now
emulates the vault/wallet-create routes. go test ./clients/wallets/... green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 22:11:00 -07:00
c12fec04ac feat(usage,audit): org-scoped usage summary + audit trail endpoints (#171)
Add two org-scoped cloud-api surfaces for the enterprise console:

- /v1/usage/summary (clients/usage): the org's unified footprint roll-up —
  spend by category over time + wallet (from the commerce ledger) plus LLM
  usage totals (from the warehouse). Composes existing sources server-side;
  each degrades independently to honest zeros with a source marker. Org from
  the validated bearer only (principal.Tenant); a forged X-Org-Id with no
  principal 401s and never reaches commerce.

- /v1/audit (clients/auditlog): the per-org twin of the admin god-view — an
  org admin reads ONLY their own org's events off the SAME tamper-evident,
  hash-chained store. Org PINNED server-side (a client ?org is ignored);
  filters time/actor/action/resource/resourceId/result + pagination.

- audit: extract the shared audit.Wire projection (used by both the admin and
  org routes, one JSON contract) and add a ResourceID filter to audit.Query.

Tests: usage (pure roll-up/categorization + HTTP scoping/honest-zeros),
auditlog (real in-memory recorder: scope isolation, filters, pagination,
401/501), audit (ToWire + ResourceID). CGO_ENABLED=0 go build + go test green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 22:06:00 -07:00
hanzo-dev 9479ce783a fix(controlplane): close the release+assign double-write sibling
Reviewing my own displacement fix adversarially: red tested release+reassign,
but a standalone release of a LIVE holder was still admitted, and after it the
shard is unowned — so release(victim) at H then assign(attacker) at H+1 puts a
second live writer on the shard (same class, pure policy, survives real crypto).

Fix: a LIVE holder's lease is immutable — releasable only when the holder is
proven dead (ErrUnauthorizedRelease), symmetric with reassign. Closes the whole
double-write class, not just red's two tested paths. + TestPolicy_ReleaseLiveHolderRefused;
TestRSM_DeterministicConvergence now marks the holder proven-dead (out-of-band)
before releasing. Suite green.
2026-07-07 22:02:16 -07:00
fbd1765d9d clients/world: GDELT + allowlisted-RSS news data plane (/v1/world) (#169)
* treasury: anchor signs through a quorum-gateable seam, not a lone key

anchor_evm.go held the signer's private key in-process and did types.SignTx.
Decouple WHERE the key lives from the tx builder via a txSigner seam:

- keySigner  — the existing local KMS-provisioned key (default; unchanged result,
  proven byte-identical to types.SignTx).
- mpcSigner  — delegates the 32-byte EVM signing hash to a quorum-gated custody
  backend (the reserve's 3-of-5 treasury MPC wallet), bound via BindAnchorSigner
  (the finance seam). The bound signer wins over any local key.

submit() now hashes the tx, delegates the hash to the resolved signer, and
applies the recoverable signature — agnostic to single-sig vs threshold. Fails
closed when neither signer is available (never fabricates a signature).

Test proves both paths recover to the correct sender and the quorum signer is
invoked exactly once; the live ring is a config swap.

* feat(gpu): BYO-GPU worker uploads render outputs to the org gallery

After studio.render completes on the local GPU, the worker fetches each finished
output from the local studio (/view) and POSTs it to the org studio's /upload/output
with the user's IAM bearer — landing it in orgs/{org}/output (S3-mirrored to the
gallery). No S3/rclone credentials ever touch the box; the session token is the only
credential. Upload target resolves from input.uploadUrl, then HANZO_STUDIO_UPLOAD_URL,
then studio.hanzo.ai. Proven end-to-end against studio 0.14.9 (aud hanzo-console).

* feat(gpu): per-machine share policy — advertised on the fleet record, enforced at claim

A linked GPU can be shared to specific orgs/projects/job-types/models with limits via
ONE policy object on the machine record (SharePolicy). It rides in the fleet
registration (input.policy) and is enforced ONCE, at claim: a job outside the policy
is failed back so an eligible worker takes it. nil/zero policy = fully permissive
(unchanged behaviour). Loaded from HANZO_GPU_POLICY (inline JSON) or
HANZO_GPU_POLICY_FILE. Unit-tested (reject matrix + loader).

Server-side multi-org queue fanout + metering-to-org+project remain follow-ups; the
worker enforces its own policy today (workers still claim their own org's queue).

* feat(world): GDELT + allowlisted-RSS news data plane (clients/world)

First vertical slice of the World news backend in the unified cloud binary:

  GET  /v1/world/news       merged, filtered, freshest-first feed  -> {items:[…]}
  GET  /v1/world/pipeline   per-(org,project) pipeline config
  PUT  /v1/world/pipeline   upsert feeds + keyword/region/source filters
  GET  /v1/world/stream     SSE live refresh (ZAP-native, org+project scoped)

- Ports world/api/{gdelt-doc,rss-proxy}.js: GDELT 2.0 Doc artlist + host-
  allowlisted RSS/Atom (~180-domain SSRF allowlist, enforced at PUT boundary,
  at fetch time, and on redirect targets).
- Org/project isolation on every path (principal.Tenant/Project); SQLite
  pipelines table PK(org,project); in-memory TTL feed cache (10m).
- RegisterWithShutdown order 142; one blank-import line in subsystems.go.
- Tests: httptest-stubbed upstreams (deterministic/offline) + live-verified.

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 22:00:29 -07:00
hanzo-dev 4f0db23d6c harden(controlplane): quorum-safety assertion, honest cert-verify, domain-sep commit
Follow-up rails from the red pass + the cryptographer audit (all on top of the
class-A fixes):
- checkQuorumSafety(N,quorum,f) asserts N>=3f+1, quorum>=2f+1, 2q>N+f at cluster
  construction (fail closed). The 2q>N+f margin at N=7 is exactly 1 and is the
  whole basis of the no-fork property, so a future sizing change can never
  silently break safety. + TestSafety_QuorumParametersAreByzantineSafe.
- verifyOwnCertStructure: renamed the driver's structural self-composed cert
  check away from 'independent triple-gate verification' and documented that an
  external cert must go through the cryptographic VerifyUnderPolicy (increment-2),
  never this structural path (red #8).
- commitZ: domain-separate the z-share commitment by session + party
  (H(cp-commit||sid||party||z)) so a commitment cannot be replayed across
  sessions/parties (red #4 hardening).
- doc.go: record the red->blue outcome (no-fork core held; 4 class-A closed), the
  CLASS-B caveat (stub secrets are public-seed-derivable -> safety suite meaningful
  only under real crypto), and the increment-2 security worklist (distributed DKG,
  authenticated handoff + KMS fence, RSM-level authz re-verify, external-cert
  crypto verify, CI guard against -tags controlplane releases).

Suite green under -tags controlplane -race; default build unaffected.
2026-07-07 21:58:34 -07:00
hanzo-dev cdbf3442b4 fix(controlplane): close red's class-A byzantine findings (blue->red->blue)
Red found a CRITICAL double-write + 3 more class-A breaks (pure orchestration/
policy, survive real crypto) with failing exploit tests. All closed; red's 4
class-A tests now pass without weakening them; class-B (stub-crypto-forgeable)
deferred to the real-crypto increment with explicit t.Skip TODOs.

#1/#2 CRITICAL double-write (policy.go, placement.go): displacement of a LIVE
  shard writer now requires proven-death by out-of-band evidence. A proposer-
  written same-block release authorizes nothing (it is not holder consent), and
  membership removal no longer manufactures proven-dead. Fail-closed increment-1
  posture; authenticated graceful handoff + KMS fence are increment-2.
#3 HIGH barrier forgeable (driver.go, custody.go, signer.go, transport.go):
  Round1 commitments are now proof-of-possession authenticated exactly as Round2
  legs, so one node cannot forge a quorum of spoofed commitments to defeat
  commit-before-reveal.
#4 MEDIUM apply fork gate (rsm.go): RSM.Apply re-checks ParentRoot == the
  applied-state commitment, so a block that does not extend local state can never
  mutate it (defense-in-depth for a future recovery/gossip path).

Corrected TestPolicy_ShardReassign_WithRelease (it asserted the vulnerable
same-block-release-authorizes-displacement behavior) to assert the fix. Updated
rsm_test blocks to extend state properly (the new parent-root gate). Suite green
under -tags controlplane; default build unaffected (package is tag-gated).
2026-07-07 21:54:35 -07:00
7ad0745ce3 wallets: add Safe (Gnosis-Safe) smart-wallet custody over the luxfi/mpc ring (#62) (#168)
New KindSafe custody composes the ring's TWO planes without importing luxfi/mpc:
- :9800 internal threshold API (mpcclient) — keygen the owner MPC EOA + owner-sign
- :8081 product API (new safeclient) — CREATE2 Safe deploy + EIP-712 Safe-tx propose

safeclient.go mints a SHORT-LIVED HS256 ring JWT (iss=mpc.lux.network, aud=mpc-api,
role=admin, org-scoped) hand-rolled (crypto/hmac, no jwt dep) from the ring's
MPC_JWT_SECRET — resolved from cloud's in-process KMS via
CLOUD_WALLETS_MPC_JWT_SECRET_REF, NEVER a plaintext env value. The deploy route is
role-gated (owner|admin), so role=admin clears it.

safeCustody.Provision: keygen (owner EOA) -> deploy Safe(owners=[EOA], threshold=1)
on the wallet's EVM chain (per-wallet, default Hanzo L1 36963); KeyRef encodes both
ring handles (<mpcWalletId>|<smartWalletId>); Address = predicted Safe contract.
Sign: owner-approval signature via :9800 (uniform /v1/wallets/:id/sign). New route
POST /v1/wallets/:id/safe-tx composes the ring propose (EIP-712 MPC-sign) via a
safeProposer capability type-assert (no Kind switch). Fails closed
(ErrMPCNotConfigured) until CLOUD_WALLETS_MPC_API_ADDR + the JWT secret are wired.

Tests: TestSafeCustody drives a stub emulating both ring planes (asserts the minted
JWT is HS256-valid with correct iss/aud/role/org) + TestSafeCustody_FailClosed.
go test ./clients/wallets/... green; CGO_ENABLED=0 go build ./cmd/cloud green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 21:45:19 -07:00
0b07cce775 cloud: register /v1/wallets subsystem + unblock main (Config.Role collision) (#167)
Two coupled changes so main builds green AND the MPC custody surface is live:

1. Fix the broken build on main. #160 (CLOUD_ROLE writer/reader HA split) and
   #163 (Stage-0 control-plane inert config) each added a `Role` field to the
   SAME Config struct on separate branches; the merge left Config.Role
   redeclared (role.Role vs string) + a duplicate struct-literal key, so
   `go build ./cmd/cloud` failed (release lane stuck at v1.786.124). Rename the
   inert #163 field to ControlPlaneRole (env ROLE, consumed by nothing yet). The
   HA Role (role.Role, CLOUD_ROLE, used by serve.go/build.go) is unchanged.

2. Register the wallets subsystem. clients/wallets (#151/#161) was never blank-
   imported into subsystems.go, so its init() never ran and /v1/wallets was
   unrouted (404) despite the code shipping. Add the order-127 blank import so
   the accounts/wallets/custody/keys/sign surface mounts — KMS custody always
   on; mpc/treasury fail closed until CLOUD_WALLETS_MPC_ADDR +
   CLOUD_WALLETS_MPC_API_KEY_REF are wired. This is the seam the treasury anchor
   (#162 BindAnchorSigner) binds through.

Verified: CGO_ENABLED=0 go build ./cmd/cloud green; wallets + config tests ok;
local boot logs 'wallets mounted' (defaultCustody=kms) then 'listening', no panic.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 21:03:30 -07:00
hanzo-dev 3e6a35609c feat(controlplane): Stage-1 increment-1 byzantine ceremony driver + harness
FULL-BFT byzantine ceremony driver for the cloud control plane, built
against published luxfi interfaces (consensus v1.35.30 protocol/quasar +
protocol/quasar/pulsar PulsarRoundSigner, pulsar v1.9.0 pkg/pulsar). Behind
the controlplane build tag, NOT wired into serve.

- Real PulsarRoundSigner drives Round1/Round2/Finalize (canonical
  non-grindable nonce, canonical signer set, z aggregation, ConsensusCert).
- Ceremony driver over an abstract Transport: proposer -> per-voter Round1
  commitment -> ALL-Round1 barrier -> Round2 share -> >=2/3 legs -> compose
  triple-PQ QuasarCert -> independent QuasarCert.Verify -> fail-secure apply.
- One-pod-one-share custody; policy gate refuses invariant-violating blocks
  (shard-writer reassign without lease-release/proven-dead predecessor).
- In-process N=7 harness: happy path, liveness (drop2 finalize / drop3 SAFE
  HALT), safety (equivocation, one-pod-two-shares, rushing, dup/rogue legs).

Stubbed for later increments (drop-in seams): ZAP transport, KMS share
custody, NonceMPC pool, DKG keygen, and pulsar's unshipped SignatureCore +
PartialZVerifier crypto cores + ComposePolaris cert composition.

Supersedes PR #163 classical pins: drops the bft promotion.
go build/vet/test green (CGO_ENABLED=0); race-clean.
2026-07-07 18:15:28 -07:00
hanzo-dev c97a4e42c1 fix(config): resolve Role field collision from concurrent merge
Two PRs landed on main that both added a Config.Role field — the #160
HA writer/reader role (role.Role, load-bearing in Serve) and the Stage-0
control-plane role (string). The text-merge compiled to a duplicate field
and broke the default build. Rename the inert control-plane field to
ControlPlaneRole (env ROLE unchanged); the HA Role keeps its name and all
cfg.Role.IsReader()/String() consumers are untouched.
2026-07-07 18:12:41 -07:00
hanzo-devandGitHub ce7b6fe935 feat(cloud): CLOUD_ROLE writer/reader HA split + de-alias ZapDB + writer-pin seam (#160)
* refactor(kms): de-alias badger→zapdb (the embedded store IS ZapDB)

clients/kms/kms.go imported the store as `badger "github.com/luxfi/zapdb"`.
The store is luxfi/zapdb — the canonical Lux embedded KV, a hardened Badger
fork whose Go package is still literally `package badger`. The alias made call
sites read like raw dgraph-io/badger. Rename the alias to `zapdb` so every call
site is self-documenting; behaviour is byte-identical (same package, same API).

Confirms the invariant: `grep -rn dgraph-io/badger` across cloud = 0. There is
no raw Badger anywhere; the one embedded store is ZapDB.

* feat(cloud): CLOUD_ROLE writer/reader split + read-only KMS reader + writer-pin

Introduces an explicit HA role so read replicas can be added WITHOUT ever
risking a second writer opening the RWO stores. Default is byte-identical to
today: unset CLOUD_ROLE ⇒ Writer ⇒ the single pod that owns the RWO PVC.

- role: CLOUD_ROLE ∈ {writer(default), reader}. Serve fails CLOSED on an
  explicitly-invalid value (a wrong guess demotes the real writer or risks a
  second one). Pure, tested, imports nothing from cloud.
- kms: Config.ReadOnly opens the ZapDB store READ-ONLY with the lock guard
  BYPASSED — a reader serves secrets off a restored replica and NEVER takes the
  exclusive write lock (the mechanism proven safe by luxfi/zapdb's
  WithReadOnly + BypassLockGuard; zapdb-replicate uses the same to coexist with
  a live writer). Reader with no restored store / no key fails closed. Tested
  round-trip: writer writes → reader reopens read-only → reads back; reader
  writes rejected.
- writerpin: the single-writer election seam. SingleWriter (production-correct
  for StatefulSet replicas:1) is the default; ConsensusPin (Quasar leaderless
  election) is an HONEST stub that fails closed with ErrNotImplemented rather
  than fabricating a pin. Tested.
- wiring: Serve resolves+logs the role and the backing pin; pickKMSClient opens
  KMS read-only for readers. Writer path unchanged.

NOT YET wired (reported for Red/CTO): consensus election (writerpin gates no
store-open yet — k8s guarantees the single writer); reader gating of the
audit chain / durable tasks / per-tenant SQLite (still open writable) — the KMS
reader path is the completed slice. Data replication runs as sidecars at the
manifest layer (hanzoai/replicate for SQLite, luxfi/zapdb-replicate for ZapDB),
not via in-process import.

* feat(ha): fail-closed reader write-guard + prove in-process KMS backup

ReaderGuard: one boundary middleware rejects mutating verbs on a Reader
(405), gating EVERY store (KMS+audit+tasks+SQLite), not just KMS's
read-only open — a mis-routed write can no longer silently persist to a
reader's ephemeral dir and vanish on restart (H4). No-op on a Writer.

replication_test: real *zapdb.DB writer streams incremental age-encrypted
db.Backup blocks WHILE live; reader Restores into its OWN separate dir —
refutes the C1 'second-process open fails' path and proves the producer.
Fail-closed test: no recipient => no block (never plaintext to S3).

* test(ha): reader-guard verb matrix + replication edge cases

ReaderGuard: GET/HEAD/OPTIONS reach the store, POST/PUT/PATCH/DELETE all
405 without reaching it; Writer path (guard unmounted) serves every verb.
replication: wrong-identity restore fails closed; restore requires manifest
+ identity (unhydrated store never serves empty); repeated/no-op/overwrite
backups restore to the exact latest value (chain-correctness invariant).

* test(config): align IAM single-replica test with staged-subsystem contract

The 'empty list -> iam-enabled' subtest predates IAM becoming a STAGED
subsystem (stagedSubsystems["iam"]=true): the empty-Enable mount-all
default deliberately does NOT mount IAM (it corrupts the shared Beego
global and crashes `ai` with SQLITE_CANTOPEN). So empty list is
iam-DISABLED and >1 replica is allowed; the guard fires only when iam is
EXPLICITLY enabled. Code was correct; the test asserted the pre-staging
behavior. Pre-existing red on main, unrelated to the HA change.
2026-07-07 17:55:06 -07:00
hanzo-devandGitHub f3a959b4bd feat(cloud): Stage 0 — control-plane deps + inert config (#163)
Promote the luxfi consensus stack (consensus v1.25.15, bft v0.1.5,
p2p v1.21.1, validators v1.2.0) from indirect to direct requires, and add
four INERT control-plane config fields. Zero behavior change, reversible.
Deps + inert config only — no engine imported/started, no routes, no
serve.go/build.go behavior change.

v1.25.15 is the minimal clean tag: it already carries NewBFT (consensus.go:168)
+ engine/bft, its graph pulls validators v1.2.0 (Manager), it requires exactly
pulsar v1.1.1 (which stays v1.1.1 — zero drift), and it is the MVS-selected
version, so promotion is a no-op to the compiled graph. A lower tag would
downgrade the whole build's consensus (behavior change); a higher tag drifts
pulsar + consensus code.

The four are held direct by controlplane_deps.go: blank imports behind the
never-set //go:build controlplane_deps tag, so nothing links into the binary.
go mod tidy keeps them direct (it reads all build tags); deleting the file
reverts them to indirect. NodeID/Peers/Role/ControlPlaneQuorum parse in
LoadConfig (NODE_ID/PEERS/ROLE/CONTROL_PLANE_QUORUM) but no subsystem reads them.

Architecture direction (proposed, not shipped): the control plane is designed
to run Quasar (post-quantum BFT, protocol/quasar Submit->Finalized) under a
strict-PQ cert profile with a Pulsar RoundSigner threshold signer.

tidy also corrected pre-existing drift on main (nats-io/nats.go indirect->direct
via clients/kafka/interop_test.go; pruned 7 superseded go.sum lines) — verified
identical on pristine origin/main.
2026-07-07 17:55:03 -07:00
hanzo-devandGitHub c35926554e fix(cloud): correct luxfi/precompile go.sum hash + ZAP-only telemetry (drop plaintext OTLP fallback) (#165)
Red review findings:
- go.sum: luxfi/precompile v0.5.37 zip hash disagreed with sum.golang.org
  (h1:Yh3dJ+... vs authoritative h1:2v0z...) → cold-cache CI SECURITY ERROR.
  Corrected to the sumdb-vouched hash.
- telemetry.go: remove the plaintext OTLP-HTTP fallback (newTraceExporter) that a
  stray/standard OTEL_EXPORTER_OTLP_ENDPOINT could use to silently downgrade
  tenant-carrying trace spans to cleartext. ONE wire now: ZAP. Dropped the
  otlptracehttp import (also severs its transitive grpc pull) and the dead
  otlpEndpoint parameter. OTLP stays only the collector's interop receiver.
2026-07-07 17:54:54 -07:00
hanzo-devandGitHub 02c47ded29 test(billing): prove auto-routing bills as the resolved model at the edge (#166)
The ai subsystem serves a virtual `auto`/`zen-router` model that resolves to a
concrete model id before pricing/billing, meters its own token cost keyed on the
SERVED model, and reports it via the X-Routed-Model header. The cloud edge prices
/v1/ai/* by PATH (0, self-metered), never by the request model, so `auto` bills
as whatever it resolved to — and the edge passes X-Routed-Model through untouched.

- auto_routing_billing_test.go: TestAutoRoutingBillsAsResolvedModel (edge does not
  double-bill /v1/ai/* + header pass-through) and TestDefaultPriceAiPathModelAgnostic.
- AUTH_BILLING_CONTRACT.md §4a: document the binding.

No code change needed — cloud already meters ai from the subsystem's own usage
record (which keys off the resolved request.Model), so the edge binds correctly.
2026-07-07 17:52:02 -07:00
c6adea2036 zaptrace: encode OTLP via zap2pb; drop direct google.golang.org/protobuf (#164)
Route ExportTraceServiceRequest wire encoding through github.com/zap-proto/zap2pb
(the sanctioned ZAP<->protobuf boundary) instead of importing
google.golang.org/protobuf {proto,encoding/protowire} directly. Wire bytes are
byte-identical (repeated ResourceSpans under field 1); TestUploadTracesOverZAP
still decodes the spans over the real ZAP transport.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 17:28:07 -07:00
7bf3fc4601 treasury: anchor signs through a quorum-gateable seam, not a lone key (#162)
anchor_evm.go held the signer's private key in-process and did types.SignTx.
Decouple WHERE the key lives from the tx builder via a txSigner seam:

- keySigner  — the existing local KMS-provisioned key (default; unchanged result,
  proven byte-identical to types.SignTx).
- mpcSigner  — delegates the 32-byte EVM signing hash to a quorum-gated custody
  backend (the reserve's 3-of-5 treasury MPC wallet), bound via BindAnchorSigner
  (the finance seam). The bound signer wins over any local key.

submit() now hashes the tx, delegates the hash to the resolved signer, and
applies the recoverable signature — agnostic to single-sig vs threshold. Fails
closed when neither signer is available (never fabricates a signature).

Test proves both paths recover to the correct sender and the quorum signer is
invoked exactly once; the live ring is a config swap.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 16:30:19 -07:00
5efc28cfaa wallets: reconcile mpc custody to the ring's internal threshold API (#161)
The prior mpcclient targeted a DECIDED-but-nonexistent dashboard route tree
(/v1/wallets/{id}/sign, /v1/treasury/*) authed with a hand-minted HS256 JWT.
The deployed luxfi/mpc ring's real, working server-to-server custody surface is
the internal threshold API (cmd/mpcd/main.go, :9800): POST /keygen + POST /sign,
gated on the static MPC_INTERNAL_API_KEY bearer token — the exact contract the
ring's own /sign handler documents for a custody adapter.

Reconcile cloud to that contract:
- mpcclient.go: keygen + sign over the internal API; static bearer key (KMS),
  no JWT/dependency; deterministic idempotency key per (org,wallet,digest).
- custody.go: mpc + treasury provision via keygen, sign via /sign with the
  wallet's EVM chain id; Rotate preserves the address (ring-managed shares).
  Treasury quorum governance moves to the finance policy layer over this same
  primitive (no separate ring route).
- wallets.go: CLOUD_WALLETS_MPC_API_KEY_REF (KMS ref of the bearer key).
- test: stub emulates the internal /keygen+/sign contract.

Feature-flagged: unset CLOUD_WALLETS_MPC_ADDR ⇒ mpc/treasury fail closed.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 16:20:12 -07:00
871a6eea1e feat(billing): populate per-product usage axis + server-side ?product=/?groupBy=product (#159)
The console per-product Metrics dashboard groups usage on metadata.product /
metadata.agent, but commerce RecordUsage persists only provider/model (no product
field), so the breakdowns rendered honest-empty even though every non-LLM product
already meters+gates per-org via ResourceMeter (provider=<product>, default fee
$1.00, fail-closed 402 on zero balance).

clients/billing/usage.go is the ONE read-side adapter: usage() injects a canonical
metadata.product onto each ledger row (agent->agents, provisioning->kind,
token-metered->inference, else provider) from the SAME charged ledger, and honors
the previously-ignored ?product=<id> (server-side filter) and ?groupBy=product
(per-product spend rollup {product,requests,amountCents}). A row already carrying
metadata.product/agent wins, so it degrades to a no-op once the meter/commerce
persist them natively (forward-compatible).

No change to what is charged or gated; the balance floor stays enforced by default.
scopedBillingQuery is extracted so proxy() and usage() build the subject boundary
one way. AUTH_BILLING_CONTRACT.md documents coverage + the native-field checklist.

Tests: productOf table + enrich/filter/group units + handler-level ?product= /
?groupBy=product through the real route (33 billing tests green).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 16:11:54 -07:00
53d3fcb00b feat(cloud): embed the REAL hanzoai/console bundle; fail-hard Dockerfile (#158)
The console image stage now FAILS the build when build:embed does not emit a
real static bundle (non-empty out/index.html + out/_next), instead of silently
degrading to the committed fallback shell. A broken console export can no longer
ship the placeholder to prod. Escape hatch: --build-arg ALLOW_PLACEHOLDER=1 for
a pure-Go dev image with no Node console.

hanzoai/console build:embed produces a real 7.7M static export (361KB index.html
+ 4.3M _next chunks); //go:embed bakes it into the ONE cloud binary. Also drops
the last console2 references (repo is hanzoai/console).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 15:52:57 -07:00
hanzo-dev bd72bfbb06 Merge branch 'feat/addon-fast-follows' 2026-07-07 15:11:12 -07:00
hanzo-dev d5bf2a0dc7 cloud: rename console2→console (one canonical name)
The frontend repo is hanzoai/console (console2 was renamed away). Kill the
dead name across the build path + source so there is one name, one way:
- Dockerfile: clone hanzoai/console.git; ARG CONSOLE_REPO / CONSOLE_REF
- Makefile: CONSOLE_DIR; webui + build-standalone targets
- config.go: drop dead console2.hanzo.ai from the ZAP-WS origin allowlist
- comments across clients/* reference the console repo + its TS modules by
  their real name

No behavior change beyond dropping one unused CORS origin. Root pkg builds.
2026-07-07 15:11:09 -07:00
hanzo-devandGitHub e73b16403f provisioning: Red low fast-follows (rollback orphan-key, kv-auth + envtest proofs, datastore tag) (#156)
Red review = SHIP; these close the 4 cloud-side low findings so the PR lands
with no known edges.

low-1 (rollback atomicity): createDedicated's inject-failure branch now calls
  removeAddonURL BEFORE tearing the backend down. injectAddonURL is not atomic —
  a strategic-merge PATCH can LAND server-side yet still return err (dropped
  response / post-commit timeout); scrubbing the maybe-written <KIND>_URL first
  means a committed-but-errored inject can't leave the instance pointing at a
  deleted backend (a dangling DSN is worse than Base). Proven by
  TestDedicated_InjectPartialWriteRollsBackOrphanKey (fake now models the
  write-then-error partial failure; asserts inject THEN remove ran, key gone).

low-2 (kv fail-open corner): TestDedicatedKV_RequirepassEnforced boots the REAL
  ghcr.io/hanzoai/kv image with the exact engine.args + mounted requirepass
  config and asserts an UNAUTHENTICATED PING is REJECTED, then that default:<pw>
  authenticates — locking down the one corner where, if the image ignored the
  positional config, the instance would boot unauthenticated. Raw RESP over TCP
  (zero new client deps); gated on CLOUD_KV_SMOKE_IMAGE + docker so the default
  suite stays green, real in CI.

low-3 (strategic-merge sibling preservation): TestPatchAddonSecret_RealAPIServer
  runs the ACTUAL k8sOrchestrator addon methods against a REAL kube-apiserver
  (controller-runtime envtest) — inject KV_URL then SQL_URL => BOTH survive in
  .data; RemoveAddonSecretKey drops one, keeps the other; idempotent on absent
  key/Secret. Replaces the fake orchestrator's assumption with a server-proven
  fact. Gated on KUBEBUILDER_ASSETS (skip without envtest binaries). Adds
  controller-runtime v0.23.3 as a TEST-ONLY dep — pinned to the release that
  keeps k8s.io at v0.35.3 (NO production client-go bump).

low-4 (datastore tag symmetry): dedicated datastore image tag floating ':26' ->
  env("CLOUD_DEDICATED_DATASTORE_TAG", "26.2.3.2"), symmetric with sql/kv/docdb.
  A floating ':26' resolves to whichever datastore lineage (bridge vs fork, distinct
  data dirs) last pushed under it — a per-org instance must boot a deterministic
  image.

go build ./... green; go test ./clients/provisioning/... green (envtest PASS
against a live apiserver, kv-smoke skips without docker).

(cherry picked from commit 04d841c4906b58fa06b1bc407b55c97e6661f169)
2026-07-07 14:50:18 -07:00
c84df87754 feat(o11y): wire native datastore metrics ingest into the embedded runtime (#157)
* feat(o11y): wire native datastore metrics ingest into the embedded runtime

Bumps hanzoai/o11y to the native datastore metrics driver and starts an
in-process ZAP metric receiver (clients/o11y/metrics.go) that writes metrics to
the datastore over upstream ch-go via o11y/pkg/datastoremetrics — no histogram
fork. Reuses the embedded runtime.TelemetryStore.ClickhouseDB() connection, so
the query plane (read) and metrics (write) share one datastore conn.

Opt-in + fail-soft: gated on O11Y_METRICS_ZAP_LISTEN, a no-op until set, errors
logged and swallowed so metrics ingest can never take the query plane down. This
unblocks retiring the standalone signoz-otel-collector metrics path once verified
(verify-then-cutover). CGO_ENABLED=0 build + vet + existing o11y/observe tests green.

* chore: re-pin o11y@main (native datastore metrics driver merged)

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 14:27:47 -07:00
hanzo-dev 0aa1201cc5 provisioning: Red low fast-follows (rollback orphan-key, kv-auth + envtest proofs, datastore tag)
Red review = SHIP; these close the 4 cloud-side low findings so the PR lands
with no known edges.

low-1 (rollback atomicity): createDedicated's inject-failure branch now calls
  removeAddonURL BEFORE tearing the backend down. injectAddonURL is not atomic —
  a strategic-merge PATCH can LAND server-side yet still return err (dropped
  response / post-commit timeout); scrubbing the maybe-written <KIND>_URL first
  means a committed-but-errored inject can't leave the instance pointing at a
  deleted backend (a dangling DSN is worse than Base). Proven by
  TestDedicated_InjectPartialWriteRollsBackOrphanKey (fake now models the
  write-then-error partial failure; asserts inject THEN remove ran, key gone).

low-2 (kv fail-open corner): TestDedicatedKV_RequirepassEnforced boots the REAL
  ghcr.io/hanzoai/kv image with the exact engine.args + mounted requirepass
  config and asserts an UNAUTHENTICATED PING is REJECTED, then that default:<pw>
  authenticates — locking down the one corner where, if the image ignored the
  positional config, the instance would boot unauthenticated. Raw RESP over TCP
  (zero new client deps); gated on CLOUD_KV_SMOKE_IMAGE + docker so the default
  suite stays green, real in CI.

low-3 (strategic-merge sibling preservation): TestPatchAddonSecret_RealAPIServer
  runs the ACTUAL k8sOrchestrator addon methods against a REAL kube-apiserver
  (controller-runtime envtest) — inject KV_URL then SQL_URL => BOTH survive in
  .data; RemoveAddonSecretKey drops one, keeps the other; idempotent on absent
  key/Secret. Replaces the fake orchestrator's assumption with a server-proven
  fact. Gated on KUBEBUILDER_ASSETS (skip without envtest binaries). Adds
  controller-runtime v0.23.3 as a TEST-ONLY dep — pinned to the release that
  keeps k8s.io at v0.35.3 (NO production client-go bump).

low-4 (datastore tag symmetry): dedicated datastore image tag floating ':26' ->
  env("CLOUD_DEDICATED_DATASTORE_TAG", "26.2.3.2"), symmetric with sql/kv/docdb.
  A floating ':26' resolves to whichever datastore lineage (bridge vs fork, distinct
  data dirs) last pushed under it — a per-org instance must boot a deterministic
  image.

go build ./... green; go test ./clients/provisioning/... green (envtest PASS
against a live apiserver, kv-smoke skips without docker).

(cherry picked from commit 04d841c4906b58fa06b1bc407b55c97e6661f169)
2026-07-07 14:22:13 -07:00
52843e1ac2 feat(cloud): embed native PubSub (clients/pubsub :4222) + Kafka adaptor (clients/kafka :9092) — Lux-consensus/no-ZK, disabled-by-default, interop-verified (#155)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 14:15:02 -07:00
hanzo-devandGitHub 7a29b86d53 provisioning: uniform on-demand add-on instance binding + <KIND>_URL injection (#154)
Extend the dedicated-instance strategy so all four on-demand data add-ons —
Hanzo KV / SQL / DocDB / Datastore — route through ONE mechanism, and bind an
enabled add-on to an app instance by injecting its DSN as <KIND>_URL into the
instance's addons Secret (disabling reverts to Base).

- store: additive instance column (idempotent ALTER, threaded through Resource/
  cols/scan/Insert) + ListByInstance(org,instance).
- dedicated: add sql (Datastore type=postgresql, POSTGRES_* env, PGDATA subdir)
  and kv (type=valkey, per-instance requirepass via a MOUNTED config Secret since
  the kv-server binary reads no password from env; DSN user=default). Engine
  gains adminUser/env/args/secretMount so the CR builder stays one code path.
- addon_inject: injectAddonURL/removeAddonURL + orchestrator PatchAddonSecret
  (strategic-merge, create-if-absent, key-preserving) / RemoveAddonSecretKey
  (JSON-merge delete, idempotent). Reloader annotation + rev bump on the Secret.
- create: instance bind field (validated); inject AFTER the row Insert as part of
  the atomic provision (rollback on failure). drop: revert to Base BEFORE tearing
  the backend down.
- sql/kv move off the shared-logical registry (each org OWNS its instance); the
  orphaned shared postgres/redis provisioners + pgx/go-redis direct deps removed.

Tests: instance column round-trip + ListByInstance isolation; sql/kv DSN + CR
shape; inject merges (second add-on never clobbers the first); un-bound create
skips injection; drop removes URL before teardown; inject failure rolls back the
whole provision. go build/vet/test green.
2026-07-07 14:08:35 -07:00
hanzo-dev 2c7dc05ec1 deps: bump hanzoai/ai -> isglobaladmin in /get-account (8e65b8c3)
Pulls ai's additive isGlobalAdmin field on /get-account so console
recognizes global admins. Pure dependency bump: re-pins re-tagged
luxfi/* modules from source (GOPRIVATE, sumdb-bypassed) after the
documented content-hash drift, prunes cloud.google.com/go/compute and
stale hanzoai/iam v1.31.16 (ai dropped the GCP SDK and requires iam
v1.31.17). go build ./... green (CGO_ENABLED=0).
2026-07-07 12:57:45 -07:00
44dd4d869b o11y: embed in-process OTLP ingest (traces+logs) into cloud (#153)
Fold the standalone otel-collector Deployment into the unified cloud binary:
an in-process OpenTelemetry Collector accepts OTLP (grpc :4317, http :4318) and
writes spans+logs into the same ClickHouse datastore cloud already reads for the
o11y query plane (signoz_traces / signoz_logs, cluster insights). Consumers point
at cloud.hanzo.svc instead of otel-collector.hanzo.svc.

Trimmed, driver-compatible pipeline (reuses the signoz clickhouse exporters that
compile against cloud upstream clickhouse-go v2.44.0):
  otlp -> memory_limiter, resource(namespace=hanzo, env), batch
       -> clickhousetraces (traces), clickhouselogsexporter (logs)

- OFF by default (CLOUD_OTLP_INGEST_ENABLED); fail-soft; ShutdownFunc flushes.
- DSN via env (envprovider), never on disk; metrics self-telemetry off so only
  :4317/:4318 bind (no :9090 class clash).
- telemetry.go: add OTLP-HTTP exporter path so cloud can loop back to the
  in-process ingest at localhost:4318 (ZAP stays default/canonical).

DEFERRED: metrics pipeline (signozclickhousemetrics) needs SigNoz dd-sketch
ch-go fork (chproto.DD/Store/IndexMapping) that will not compile against cloud
upstream ch-go; metrics ingest stays on the standalone collector. See
clients/o11y/LLM.md.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-07 12:12:26 -07:00
hanzo-dev c607d24b85 Merge branch 'feat/gpu-engine-serve'
# Conflicts:
#	Makefile
#	clients/treasury/anchor_evm.go
#	clients/treasury/ledger/sqlstore/sqlstore.go
#	clients/treasury/treasury.go
#	clients/treasury/treasury_test.go
#	config_iam_replicas_test.go
#	go.mod
#	go.sum
#	subsystems/subsystems.go
2026-07-07 10:43:36 -07:00
48ed003d6d feat(wallets): configurable KMS/MPC/treasury custody subsystem (/v1/wallets/*) (#151)
One custody seam over three orthogonal signing backends selected per-wallet by
Kind:

- KindKMS  single-sig custody IN-PROCESS via the embedded luxfi/kms client
  (deps.KMS). The fully-exercised spine: a real secp256k1 key is generated, its
  private bytes sealed under the KMS envelope, and every Sign recovers to the
  wallet address. No network hop.
- KindMPC / KindTreasury custody DELEGATE over HTTP to the deployed luxfi/mpc
  cluster via a thin typed REST client (the clients/mpcseal precedent). cloud
  never imports github.com/luxfi/mpc. Unconfigured -> fail closed
  (ErrMPCNotConfigured); a signature is never fabricated.

Config seam: KMS always available; mpc/treasury built only when
CLOUD_WALLETS_MPC_ADDR is set and the HS256 JWT secret resolves from a KMS ref
(never a plaintext env). Per-tenant SQLite (org column on every row, every query
filtered by org). Finance seam (WalletForLedgerAccount) is a pure lookup only.

Tests (incl -race): KMS single-sig end-to-end (sig recovers to address, sealed
at rest, rotate changes address), per-tenant isolation, custody seam selects
backend (fail-closed mpc/400 unknown), mpc path wired against a faithful stub.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-05 20:48:59 -07:00
115c8bbdd6 test(identity): make global-admin gate test config-agnostic on adminOrg (#150)
Reconciles TestGlobalAdminGate_RequiresAdminOrgAndIsAdmin with the task #51 decision
to pin IAM_ADMIN_ORG to the operator org (hanzo). The assertions are unchanged — the
gate is owner==adminOrg AND isAdmin — but the comment/labels no longer editorialize
that owner==admin is the only valid adminOrg. adminOrg is deployment config; the test
pins it to "admin" hermetically and proves the two invariants that hold for ANY
adminOrg: isAdmin is required (a non-admin in the admin org gets nothing) and owner is
required (an admin of any OTHER org gets nothing). Renamed the different-org case off
"hanzo" (which prod now pins AS the admin org) to a neutral "globex" so it reads
unambiguously.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-05 20:34:43 -07:00
900175390f feat(treasury): per-tenant Base storage — one SQLite file per tenant, IAM-selected (#149)
The finance ledger of record ran on a single process-wide {DataDir}/treasury.db.
Select the store per request from the validated IAM owner instead, so every
tenant's books live on their OWN Hanzo Base file and one tenant's writes can
never appear in another's read.

- sqlstore.Manager: opens+caches one *Store per tenant (mutex-guarded map). The
  house/reserve ledger is one fixed file ({DataDir}/treasury.db, preserved — no
  migration of live reserve capital); customer ledgers are {DataDir}/finance/{slug}.db.
- tenantSlug: injective (never folds acme/ACME), path-traversal-guarded, reserves
  the house slug. Verbatim stem for a DNS-ish org, else a sha256 slug. Consumes the
  treasury's canonical hanzoai/sqlite opener (Open) — ledgercore's per-tenant opener
  is a test-only helper that would double-register the sqlite driver.
- treasury.Mount binds the ledger of record to the HOUSE store; myAccounts reads the
  caller's OWN per-tenant file (house scope still honours the Formance/Postgres opt-in).
- StorageDriver(): one place decides the driver — sqlite (default, what prod runs) or
  postgres (opt-in via FORMANCE_LEDGER_URL). Postgres option preserved, never the default.

Tests: per-tenant isolation (A's write never in B's read; distinct files; cache
identity; traversal stays in-dir; no case-fold) + default-driver=sqlite + opt-in
preserved. go build ./cmd/cloud green; ./clients/treasury/... green (incl -race).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-05 20:05:46 -07:00
66b149f97f fix(config): stage IAM off mount-all (unblock release smoke) + lock global-admin gate (task #51) (#148)
* fix(config): stage IAM off the mount-all default — unblock the release boot smoke

Every cloud release since the IAM embed (#142) has failed its boot smoke and
the fleet stayed pinned to a pre-embed image (v1.786.110), so the treasury +
finance merges (#143/#144/#145/#147) never shipped.

Root cause (from the failed release smoke logs): with CLOUD_ENABLE unset the
binary mounts every registered subsystem, so iamsvc.Mount now runs
iamserver.InitEmbed(). In the smoke/Docker env InitEmbed panics opening its own
SQLite (IAM_DATA_DIR=/data/iam absent on the tmpfs) and is recovered to a
fail-closed 503 — but IAM and the ai subsystem are sibling casibase/casdoor
forks linked against the SAME beego module, so InitEmbed's half-initialised
shared process-global (web.BConfig / xorm adapter) then makes ai's own
bootstrap fail identically:

  iam  ERROR iamserver.InitEmbed: bootstrap panicked: unable to open database file (14)
  ai   INFO  ai: initializing runtime
  cloud: mount: mount ai: ai: bootstrap: unable to open database file (14)  -> SMOKE FAIL

This would crash api.hanzo.ai in prod too (CLOUD_ENABLE is unset there), not
just the smoke.

Fix: make IAM a STAGED subsystem — excluded from the empty-Enable mount-all
default, mounted ONLY when named in CLOUD_ENABLE. This is exactly the HIP-0106
staged-rollout contract iamsvc already documents ('operator adds iam to
--enable only after the fold is verified'), now enforced in code. It restores
the pre-#142 mount-all set (iamsvc is the only subsystem #142 added to it), so
the boot smoke goes green again; hanzo.id keeps being served by the standalone
iam pod until an explicit, verified cutover. Local mount-all boot now reaches
'listening' with iam 'subsystem disabled' and ai mounted clean.

pickIAMClient already falls back to the remote/disabled IAM client when
Enabled("iam") is false (build.go), which is current prod behaviour, so no
deps.IAM regression. One activation mechanism (the enable-list), one place.

* test(identity): lock global-admin = owner==adminOrg AND isAdmin

The cloud admin surfaces (incl. /v1/admin/treasury/*) grant global admin only
to a validated principal whose org IS the admin org AND whose token carries
isAdmin. This locks that invariant end-to-end through the real JWKS-validated
SanitizeIdentity boundary, with the two cases that matter for the treasury flip:

  - a hanzo-org ADMIN (owner=hanzo, isAdmin=true)  -> NOT global admin
  - a NON-admin in the admin org (owner=admin, isAdmin=false) -> NOT global admin

The sole global admin z@hanzo.ai is global admin because IAM promotes @hanzo.ai
into the admin org (owner==adminOrg), NOT because it lives in 'hanzo'. This test
is the guard proving the boundary must NOT be widened to owner==hanzo (e.g.
IAM_ADMIN_ORG=hanzo), which would elevate every hanzo-org admin to see all
tenants' finances. The gate stays owner==adminOrg AND isAdmin; the fix for z is
that its token carries owner=admin, never a wider gate.

---------

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-05 19:58:06 -07:00
hanzo-dev dde2df77db build(hanzo): pure-Go recipe for cmd/hanzo so the one sqlite driver registers once
The hanzo CLI (cmd/hanzo) had no build target, so a naive
`go build ./cmd/hanzo` used the machine default CGO_ENABLED=1 and panicked
at init: "sql: Register called twice for driver sqlite".

Root cause: with CGO on, github.com/hanzoai/sqlite (the canonical Hanzo
driver, imported by ~15 clients/*/store.go) compiles its mattn/SQLCipher
backend and registers "sqlite"; the embedded upstream deps that import
modernc.org/sqlite directly (base/core, o11y, commerce/db, orm/db) register
"sqlite" a second time -> panic.

Fix: build cmd/hanzo the same pure-Go way cmd/cloud and the Dockerfile
already ship (CGO_ENABLED=0). hanzoai/sqlite's !cgo backend IS modernc, so
the fork and every modernc importer resolve to a single registration. This
extends the existing CGO_ENABLED?=0 policy (see Makefile header) to the new
binary instead of adding a second way to build; no dependency is dropped and
hanzoai/sqlite stays canonical.

  make hanzo   # -> ./bin/hanzo, pure Go, one 'sqlite' registration
2026-07-05 19:52:05 -07:00
hanzo-dev 3185258a3e chore(deps): mark luxfi/crypto & luxfi/geth direct
clients/treasury/anchor{,_evm}.go (Phase 2 ledger-root anchor) import
luxfi/geth and luxfi/crypto directly, so they are no longer indirect.
go mod tidy result; no version change.
2026-07-05 19:52:04 -07:00
d1974cae85 feat(treasury): delegate the native ledger to ledgercore — ONE double-entry engine (#145)
Collapse the treasury's separately-written double-entry SQL onto ledgercore
(github.com/hanzo-fi/ledger) — the SAME engine the ledger's own store uses — so
there is exactly one double-entry implementation across the stack (church of
Rich Hickey: one double-entry value, not three places).

- Reimplement clients/treasury/ledger/sqlstore to back the ledger.Store/ledger.Tx
  port with ledgercore instead of hand-rolled treasury_postings SQL. The
  accounting truth — every balance and the reserve overdraw guard — is now
  ledgercore's (postings -> moves -> balances + hash-chained log, idempotency-key
  dedup, WithTx atomic read-then-write). The adapter only maps the treasury's
  vocabulary (int64 cents, Kind/Program/Ref key, signed-Posting Entry) onto it.

- KEEP the port/adapter seam: Open()'s signature is unchanged, so treasury.go and
  the Formance-HTTP opt-in are untouched — native (ledgercore) stays the default
  backend. The engine (ledger.go) and the on-chain Root are UNCHANGED: each Entry
  is round-tripped verbatim (as ledgercore transaction metadata), so the Root is
  byte-identical to the previous store's, independent of ledgercore's own postings.

- Policy (revenue-share bps) stays in a small side table — it is Hanzo config, not
  double-entry accounting, so it does not belong in the shared engine.

- Pin bun to v1.2.9 (replace): ledger-fi floors v1.2.18, which removed
  schema.Formatter/NewFormatter/Append that hanzoai/o11y still uses; ledgercore's
  compiled closure uses no v1.2.18-only API, so v1.2.9 satisfies both. hanzo-fi/ledger
  is pinned to the PR-3 branch commit until it merges.

Tests (all green, incl. -race): overdraw guard, at-most-once payout, snapshot
reconcile, scope isolation, and Tx rollback all pass unchanged against the
ledgercore-backed store. The whole cloud module builds under -mod=readonly, and
the treasury test binary links NO modernc driver (so it does not reintroduce the
"sqlite registered twice" panic).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-05 19:14:26 -07:00
99dada4dde feat(treasury): activate Hanzo L1 (36963) anchor — EIP-1559 gas + deploy tool (#147)
The 36963 coreth fee market pins a 25 gwei min base fee, so a legacy tx priced
at base+1 strands the moment the base fee ticks up. anchor_evm.go now submits a
DynamicFeeTx (1 gwei tip floor, 2x-base-fee cap) — proven accepted on-chain as a
type-2 tx.

Adds clients/treasury/cmd/anchorctl: a one-shot in-cluster tool that provisions
the KMS-held signer (key -> KMS, only the address printed), funds it from a
genesis account, deploys contracts/TreasuryAnchor.sol, and can send anchor(bytes32).
Includes the compiled TreasuryAnchor.bin (solc 0.8.26, optimizer 200, cancun).

Deployed live: contract 0x53141dF42DF13Aad0512f2F08c3E3216EEFac5F2, owner = signer
0x703D4227d58d0b6A20BD721c940CED170470f634 (KMS ref hanzo/treasury-anchor/TREASURY_ANCHOR_SIGNER_KEY).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-05 19:11:05 -07:00
48bbcc04fb fix(test): canonical make test-race — one sqlite registration under -race (#48) (#146)
The cloud registers the "sqlite" driver exactly once in every build mode EXCEPT
a naive `go test -race`: -race forces CGO=1, which links the fork's mattn
"sqlite" (github.com/hanzoai/sqlite) ALONGSIDE the embedded deps that import
modernc directly (ai/base/commerce/o11y/orm), so both register "sqlite" and the
binary panics at init ("sql: Register called twice for driver sqlite") — the
pre-existing failure in clients/{graph,kmssvc,o11y}.

`make test` (CGO=0) and `make test-cgo` (-tags sqlite_purego) already avoid this
by resolving the whole binary to modernc's single registration. This adds the
missing peer for the race detector: `make test-race` runs
`CGO_ENABLED=1 go test -race -tags sqlite_purego ./...` — CGO on for the race
instrumentation, but the fork forced to its pure-Go backend so mattn never
registers and "sqlite" is registered exactly once. The ONE way to race-test the
cloud.

Proof: `go test -race ./clients/o11y/` panics; `go test -race -tags sqlite_purego
./clients/{graph,kmssvc,o11y}/` all pass.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-05 18:42:18 -07:00
0a68db08e4 feat(finance): per-org /v1/finance/* projecting the commerce + treasury planes (#144)
The finance.hanzo.ai + console Finance surfaces render real per-org data
instead of preview stubs. This adds no billing system — it PROJECTS the two
that already exist (the commerce customer wallet + the treasury reserve fund)
into the @hanzo/finance-ui contract (USD cents, optional-safe), scoped to the
validated IAM owner.

clients/billing/finance.go — six commerce-projected reads, reusing this
package's commerceProxy + per-org subject-pinning (one commerce read path):
  GET /v1/finance/balance          commerce balance (holds -> pendingCents)
  GET /v1/finance/credits          commerce deposit rows (grants, positive)
  GET /v1/finance/usage?range=     commerce withdraw rows -> series+lines+total
  GET /v1/finance/invoices         honest empty (no invoice ledger exists yet)
  GET /v1/finance/payment-methods  commerce portal, masked to brand+last4
  GET /v1/finance/ledger?range=    commerce ledger -> signed per-org postings

clients/treasury/treasury.go — GET /v1/finance/treasury reshaped from the
reserve Report into the TreasurySummary shape (reserve/committed/available +
honest Hanzo L1 anchor); the transparency policy rides along additively.

Tenant isolation: org A never sees org B (per-org subject pinned server-side,
client cannot widen scope); payment methods re-masked defensively so a PAN can
never leak. Honest empty/typed shapes where a data source does not exist yet.

Tests: go test -race ./clients/billing/... ./clients/treasury/... green;
go build ./cmd/cloud green.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-05 14:19:36 -07:00
b07c945f80 feat(treasury): native reserve fund + backed payouts + Formance ledger-of-record + Hanzo L1 anchor (#143)
* feat(treasury): native double-entry reserve fund + backed-payout seam (#treasury)

The platform's OWN fund/reserve accounting, one layer ABOVE the per-org commerce
credit ledger. A store-agnostic, cloud-decoupled double-entry engine
(clients/treasury/ledger) — the SEED of the native hanzoai/finance central ledger
(the Go replacement for the Formance stack) — plus a Base/SQLite adapter
(ledger/sqlstore) and the cloud client (clients/treasury).

Core (clients/treasury/ledger): accounts + balanced journal entries (Σ postings==0,
refused otherwise), ONE shared fund:reserve pool with per-program payout sinks,
revenue-share policy (bps, one place), and the reserve GUARD — a fund debit that
would overdraw is refused, atomically, so growth-loop payouts are backed capital not
unbounded minting. Zero cloud/zip/SQLite imports; persistence is the Store/Tx port,
so it lifts to hanzoai/finance as a directory move.

Surface: GET /v1/treasury (org transparency), GET /v1/admin/treasury (report +
journal + anchor), POST /v1/admin/treasury/{policy,sweep,seed,anchor} (global-admin).
treasury.Reserve(program,ref,memo,cents) is the ONE seam the 3 loops call: backed →
proceed to credit; not backed → honestly pending; unmounted → passthrough
(backward-safe). Idempotent by ref (at-most-once fund debit). ledger.Root commits the
whole journal for the Hanzo L1 anchor (Phase 2 wires the KMS-signed submit).

Tests (-race, green): double-entry balances, revenue-share accrual + per-period
idempotency, reserve guard (backed→blocked), at-most-once, concurrent no-overdraw,
admin gate, Reserve passthrough+enforced, sqlstore round-trip + tx rollback.

* feat(finance): Formance ledger-of-record backend + backed payouts + scope-aware /v1/finance/*

Adopt Formance as the ledger of record behind a ledger.Backend PORT, without
reimplementing double-entry: two adapters satisfy the port — the native Base/SQLite
engine (offline/default, ships the reserve fund today) and clients/treasury/formance
(a real HTTP client to the Postgres-backed Formance Ledger v2 API: world→fund accrual,
fund→payout debit, 400 INSUFFICIENT_FUND→not-backed=the overdraw guard Formance
enforces, reference→idempotency). Select by FORMANCE_LEDGER_URL — a config flip. Root
computed via a SHARED hash so the L1 anchor is backend-agnostic.

Back the growth-loop payouts: referrals/affiliates/authors now DEBIT the reserve fund
via the ONE treasury.Reserve seam before crediting the recipient wallet — fund down,
wallet up, reconciled. Not backed → honestly pending (referrals) or 402 + VoidPayout
restores pending (affiliates/authors). Idempotent by ref (at-most-once). Unmounted →
passthrough (backward-safe; existing loop suites stay green).

Scope-aware /v1/finance/* — ONE engine, three tenancy surfaces (admin/console/finance
product): tenant derived from IAM, house/reserve locked to global-admin under
/v1/admin/finance/*, per-org callers see ONLY their own org:<tenant>:* accounts.
GET /v1/finance/accounts (per-org; admin ?scope=house|?org=<t>). Storage tiers doc'd:
authoritative OLTP ledger (native/Formance) + ClickHouse OLAP projection over the same
o11y event stream (audit mirror — no second metering pipeline).

Tests (-race, green): Formance adapter (accrual+idempotency, debit guard+replay,
snapshot) via a fake Formance server; scope isolation (per-org never sees house);
backed-payout enforced+blocked+at-most-once; VoidPayout restores pending.

* feat(treasury): Phase 2 — Hanzo L1 (36963) ledger-root anchor (contract + luxfi/geth submit + KMS signer)

Make the off-chain books tamper-evident on the LIVE Hanzo L1 (verified running:
network/chainId 36963, hanzod-0 producing blocks, EVM at network-36963).

- contracts/TreasuryAnchor.sol: minimal immutable witness — owner-gated anchor(bytes32)
  appends a timestamped root + emits Anchored; latest()/count for cheap verification.
  No upgradeability, no token — one job.
- anchor_evm.go: real luxfi/geth submitter — dial → chainID/nonce/gasPrice → sign a
  LegacyTx (anchor(bytes32) call when TREASURY_ANCHOR_CONTRACT set, else a 0-value
  self-tx carrying the root) with types.SignTx → send → await receipt → persist. The
  signer key is provisioned from KMS (KMSSecret → env TREASURY_ANCHOR_SIGNER_KEY,
  ref TREASURY_ANCHOR_SIGNER_KMS_REF) — NEVER plaintext in code/manifest.
- ledger.Root/ComputeRoot: deterministic SHA-256 hash-chain over the whole journal +
  reserve, shared by both backends so the anchor is backend-agnostic. A change to any
  historical posting changes the root.
- POST /v1/admin/treasury/anchor submits when wired; else returns the root that WOULD
  be committed + the EXACT remaining step. GET /v1/admin/treasury shows last anchored
  root/tx/block + synced flag. Persisted across restart (treasury_anchor.json).

Honest status: the on-chain submit is COMPLETE + compiling + config-gated but NOT
driven live this pass — the node's external JSON-RPC is unreachable from the build
env and needs an operator to: deploy TreasuryAnchor on 36963, provision the KMS
signer (fund it), set TREASURY_ANCHOR_{RPC_URL,CONTRACT,SIGNER_KEY}. In-cluster the
cloud binary reaches hanzod-rpc-internal:9630, so it's one deploy-config away.

Builds green (cmd/cloud links luxfi/geth); tests -race green; gofmt clean.

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-05 13:38:29 -07:00
hanzo-dev 21660cfa0f feat(cli): hanzo engine install|serve|status
Manage a local hanzo-engine (the `hanzoai` OpenAI + Anthropic model server)
from the canonical `hanzo` CLI:
- install: runs the canonical install.sh / install.ps1 (single source of truth
  for platform detection + signature verification — no re-implementation).
- serve:  launches the installed binary (`hanzoai --port P run -m MODEL`);
  syscall.Exec on Unix so signals + exit code flow through.
- status: probes the local engine, reusing the /v1/models probe that
  `hanzo gpu connect --serve-engine` advertises with.
Tests cover wiring, ready/unreachable status, and binary discovery.
2026-07-05 13:27:21 -07:00
hanzo-dev ab5c81b699 feat(treasury): Phase 2 — Hanzo L1 (36963) ledger-root anchor (contract + luxfi/geth submit + KMS signer)
Make the off-chain books tamper-evident on the LIVE Hanzo L1 (verified running:
network/chainId 36963, hanzod-0 producing blocks, EVM at network-36963).

- contracts/TreasuryAnchor.sol: minimal immutable witness — owner-gated anchor(bytes32)
  appends a timestamped root + emits Anchored; latest()/count for cheap verification.
  No upgradeability, no token — one job.
- anchor_evm.go: real luxfi/geth submitter — dial → chainID/nonce/gasPrice → sign a
  LegacyTx (anchor(bytes32) call when TREASURY_ANCHOR_CONTRACT set, else a 0-value
  self-tx carrying the root) with types.SignTx → send → await receipt → persist. The
  signer key is provisioned from KMS (KMSSecret → env TREASURY_ANCHOR_SIGNER_KEY,
  ref TREASURY_ANCHOR_SIGNER_KMS_REF) — NEVER plaintext in code/manifest.
- ledger.Root/ComputeRoot: deterministic SHA-256 hash-chain over the whole journal +
  reserve, shared by both backends so the anchor is backend-agnostic. A change to any
  historical posting changes the root.
- POST /v1/admin/treasury/anchor submits when wired; else returns the root that WOULD
  be committed + the EXACT remaining step. GET /v1/admin/treasury shows last anchored
  root/tx/block + synced flag. Persisted across restart (treasury_anchor.json).

Honest status: the on-chain submit is COMPLETE + compiling + config-gated but NOT
driven live this pass — the node's external JSON-RPC is unreachable from the build
env and needs an operator to: deploy TreasuryAnchor on 36963, provision the KMS
signer (fund it), set TREASURY_ANCHOR_{RPC_URL,CONTRACT,SIGNER_KEY}. In-cluster the
cloud binary reaches hanzod-rpc-internal:9630, so it's one deploy-config away.

Builds green (cmd/cloud links luxfi/geth); tests -race green; gofmt clean.
2026-07-05 13:21:41 -07:00
hanzo-dev 4330dd5444 feat(gpu): engine.serve — a connected GPU serves hanzo-engine models
`hanzo gpu connect --serve-engine` advertises a local hanzo-engine (the OpenAI +
Anthropic model server on :1234) on the org fleet, alongside the existing
studio.render worker. The worker probes GET {engine-url}/v1/models, publishes the
endpoint + model list in its presence record, and prints (or with --register-provider
POSTs) the /v1/add-provider call that routes api.hanzo.ai model traffic to this GPU as
an OpenAI-compatible (Type=Local) provider.

- cli/gpu.go: --serve-engine/--engine-url/--engine-endpoint/--register-provider;
  probeEngine, refreshEngine, engineAdvertisement, capabilities, provider hint;
  `hanzo gpu status` shows the engine endpoint.
- clients/visor/fleet.go: byoWorker + fleetRegistration carry capabilities + engine;
  GET /v1/fleet/workers advertises the endpoint (additive, omitempty).
- docs/bring-your-gpu.md: Connect (BYO) vs Deploy (cloud) -> engine.serve + studio.render.
- tests: probe/advertise/registration + full stub-cloud round-trip (no model needed).

One fleet, two job types: engine.serve (model serving) + studio.render (diffusion).
2026-07-05 13:12:30 -07:00
hanzo-dev 4cc966fb45 feat(finance): Formance ledger-of-record backend + backed payouts + scope-aware /v1/finance/*
Adopt Formance as the ledger of record behind a ledger.Backend PORT, without
reimplementing double-entry: two adapters satisfy the port — the native Base/SQLite
engine (offline/default, ships the reserve fund today) and clients/treasury/formance
(a real HTTP client to the Postgres-backed Formance Ledger v2 API: world→fund accrual,
fund→payout debit, 400 INSUFFICIENT_FUND→not-backed=the overdraw guard Formance
enforces, reference→idempotency). Select by FORMANCE_LEDGER_URL — a config flip. Root
computed via a SHARED hash so the L1 anchor is backend-agnostic.

Back the growth-loop payouts: referrals/affiliates/authors now DEBIT the reserve fund
via the ONE treasury.Reserve seam before crediting the recipient wallet — fund down,
wallet up, reconciled. Not backed → honestly pending (referrals) or 402 + VoidPayout
restores pending (affiliates/authors). Idempotent by ref (at-most-once). Unmounted →
passthrough (backward-safe; existing loop suites stay green).

Scope-aware /v1/finance/* — ONE engine, three tenancy surfaces (admin/console/finance
product): tenant derived from IAM, house/reserve locked to global-admin under
/v1/admin/finance/*, per-org callers see ONLY their own org:<tenant>:* accounts.
GET /v1/finance/accounts (per-org; admin ?scope=house|?org=<t>). Storage tiers doc'd:
authoritative OLTP ledger (native/Formance) + ClickHouse OLAP projection over the same
o11y event stream (audit mirror — no second metering pipeline).

Tests (-race, green): Formance adapter (accrual+idempotency, debit guard+replay,
snapshot) via a fake Formance server; scope isolation (per-org never sees house);
backed-payout enforced+blocked+at-most-once; VoidPayout restores pending.
2026-07-05 13:08:24 -07:00
hanzo-dev bd51d6eef6 feat(treasury): native double-entry reserve fund + backed-payout seam (#treasury)
The platform's OWN fund/reserve accounting, one layer ABOVE the per-org commerce
credit ledger. A store-agnostic, cloud-decoupled double-entry engine
(clients/treasury/ledger) — the SEED of the native hanzoai/finance central ledger
(the Go replacement for the Formance stack) — plus a Base/SQLite adapter
(ledger/sqlstore) and the cloud client (clients/treasury).

Core (clients/treasury/ledger): accounts + balanced journal entries (Σ postings==0,
refused otherwise), ONE shared fund:reserve pool with per-program payout sinks,
revenue-share policy (bps, one place), and the reserve GUARD — a fund debit that
would overdraw is refused, atomically, so growth-loop payouts are backed capital not
unbounded minting. Zero cloud/zip/SQLite imports; persistence is the Store/Tx port,
so it lifts to hanzoai/finance as a directory move.

Surface: GET /v1/treasury (org transparency), GET /v1/admin/treasury (report +
journal + anchor), POST /v1/admin/treasury/{policy,sweep,seed,anchor} (global-admin).
treasury.Reserve(program,ref,memo,cents) is the ONE seam the 3 loops call: backed →
proceed to credit; not backed → honestly pending; unmounted → passthrough
(backward-safe). Idempotent by ref (at-most-once fund debit). ledger.Root commits the
whole journal for the Hanzo L1 anchor (Phase 2 wires the KMS-signed submit).

Tests (-race, green): double-entry balances, revenue-share accrual + per-period
idempotency, reserve guard (backed→blocked), at-most-once, concurrent no-overdraw,
admin gate, Reserve passthrough+enforced, sqlstore round-trip + tx rollback.
2026-07-05 12:48:24 -07:00
f6702f76bc feat(iam): embed IAM in the unified cloud binary (last binary-consolidation piece) (#142)
* feat(iam): embed IAM in the unified cloud binary as an in-process subsystem

Folds Hanzo IAM -- the identity provider serving hanzo.id (login/authorize/
token/jwks/userinfo, /v1/iam/* admin, OAuth2/OIDC, LDAP/RADIUS) -- into the
unified hanzoai/cloud binary as the LAST binary-consolidation piece
(HIP-0106: "one Go binary embeds IAM + KMS + o11y").

clients/iamsvc wraps IAM's own Beego runtime: iamserver.Init() runs the full
bootstrap without binding a listener, and web.BeeApp.Handlers is mounted
verbatim on cloud's zip.App at every prefix IAM owns (/v1/iam/*,
/.well-known/*, /login/oauth/*, /_/iam/*, /cas/*, /scim/*). No auth logic is
reimplemented -- the same controllers answer, so OAuth/OIDC semantics
(authorize clientId org-resolution, JWT audiences, SuperAdmin owner=="admin",
argon2id password hashing) are preserved byte-for-byte. Registered at order 50
(identity authority, mounts before dependents).

- go.mod: pin hanzoai/iam v1.28.12 -> v1.31.16 (latest; carries the
  authorize-login org-resolution fixes #95/#96 the operator SSO chain needs).
- subsystems.go: blank-import clients/iamsvc; IAM no longer "NOT fused in".

Auth-critical middleware interactions verified: /v1/iam/* prices to 0 in
DefaultPrice (ungated -- the M2M /v1/iam/oauth/token mint is never charged);
SanitizeIdentity strips only forgeable X-User-*/X-Org-* headers, never the
Authorization bearer or iam_session_id cookie IAM's session/oauth logic reads.

Activation is STAGED via the enable-list gate: "iam" is NOT added to the live
--enable until IAM config is present in the cloud runtime and the fold is
verified (login/authorize/token/jwks + operator SSO chain). The standalone iam
pod keeps serving hanzo.id via ingress until then.

Build gate: CGO_ENABLED=0 go build ./... && go test . green. clients/iamsvc
tests prove registration (order 50) + full-path preservation through the mount.

* fix(iam): red-review — embed-mode bootstrap, fail-closed, single-replica guard

Addresses the red review of cloud#142 (mount mechanism approved; activation
blocked on standalone-only side effects in the wrapped entrypoint).

1. [HIGH] Embed-mode bootstrap. iamsvc now calls iamserver.InitEmbed (new in
   iam v1.31.17) instead of the standalone Init: skips StopOldInstance
   (lsof/SIGKILL — panics on distroless, kills a co-resident on shared netns),
   skips LDAP/RADIUS listeners (RADIUS binds unmanaged UDP with an empty shared
   secret), skips export/os.Exit, binds no listener. Standalone hanzo iam / iamd
   is byte-for-byte unchanged (Init delegates to the same shared bootstrap with
   every flag on). Also covers [MED] #3 — directory listeners never start
   in-process.

4. [MED] Fail-closed, not fail-loud. InitEmbed returns an error (recovers
   bootstrap panics); a broken/misconfigured IAM degrades THIS subsystem to a
   503 fail-closed on every IAM prefix (mountFailClosed) — every co-resident
   subsystem (KMS, o11y) stays up. Mirrors the KMS "no master key -> health-only"
   blast-radius isolation.

2. [HIGH] Single-replica enforcement. Embedded IAM uses Beego's process-local
   "memory" session store. Config.Validate now REFUSES to boot iam-enabled above
   CLOUD_REPLICAS=1 (a real runtime guard, not convention); the helm chart pins
   replicas=1 + injects CLOUD_REPLICAS whenever "iam" is in --enable.

5. [MED] Bump verified iam v1.31.16 -> v1.31.17. The slim-JWT change keeps every
   claim cloud reads (owner, isAdmin, email, name kept; aud is a registered
   claim, untouched) — IdentityMiddleware unaffected. authz v1.10.4 policy-API
   swap is IAM-internal (cloud builds green, no direct use). redirect_uri
   exact-match + AutoSignin CC-JWT normalization are version-skew CUTOVER gates:
   version-match the standalone pod + verify registered redirect_uris are exact
   before adding "iam" to the live --enable (runtime-data checklist, not code).

Tests (CGO_ENABLED=0):
- TestIAMEmbedBehindMiddlewareChain — unauth POST /v1/iam/oauth/token, /login,
  jwks + /login/oauth/authorize return 2xx through the REAL SanitizeIdentity +
  BillingGate chain (never 402/503); forged X-User-IsAdmin is stripped; a priced
  control path is denied at zero balance (proves the gate is engaged).
- TestDefaultPriceExemptsIAM — every IAM prefix prices to 0.
- TestValidateIAMSingleReplica — iam + replicas>1 refused; 1/unset/off ok.
- TestMountFailClosed503 — the fail-soft path serves 503 on every IAM prefix.

Build+test green; standalone hanzo iam still links; helm renders replicas=1 for
iam-enabled, replicaCount otherwise. Depends on iam v1.31.17
(hanzoai/iam#feat/iam-embed-entrypoint). STILL STAGED — the standalone iam pod
serves hanzo.id until red GREEN + runtime e2e.

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-05 12:21:42 -07:00
hanzo-dev 3d11e0be1a fix(iam): red-review — embed-mode bootstrap, fail-closed, single-replica guard
Addresses the red review of cloud#142 (mount mechanism approved; activation
blocked on standalone-only side effects in the wrapped entrypoint).

1. [HIGH] Embed-mode bootstrap. iamsvc now calls iamserver.InitEmbed (new in
   iam v1.31.17) instead of the standalone Init: skips StopOldInstance
   (lsof/SIGKILL — panics on distroless, kills a co-resident on shared netns),
   skips LDAP/RADIUS listeners (RADIUS binds unmanaged UDP with an empty shared
   secret), skips export/os.Exit, binds no listener. Standalone hanzo iam / iamd
   is byte-for-byte unchanged (Init delegates to the same shared bootstrap with
   every flag on). Also covers [MED] #3 — directory listeners never start
   in-process.

4. [MED] Fail-closed, not fail-loud. InitEmbed returns an error (recovers
   bootstrap panics); a broken/misconfigured IAM degrades THIS subsystem to a
   503 fail-closed on every IAM prefix (mountFailClosed) — every co-resident
   subsystem (KMS, o11y) stays up. Mirrors the KMS "no master key -> health-only"
   blast-radius isolation.

2. [HIGH] Single-replica enforcement. Embedded IAM uses Beego's process-local
   "memory" session store. Config.Validate now REFUSES to boot iam-enabled above
   CLOUD_REPLICAS=1 (a real runtime guard, not convention); the helm chart pins
   replicas=1 + injects CLOUD_REPLICAS whenever "iam" is in --enable.

5. [MED] Bump verified iam v1.31.16 -> v1.31.17. The slim-JWT change keeps every
   claim cloud reads (owner, isAdmin, email, name kept; aud is a registered
   claim, untouched) — IdentityMiddleware unaffected. authz v1.10.4 policy-API
   swap is IAM-internal (cloud builds green, no direct use). redirect_uri
   exact-match + AutoSignin CC-JWT normalization are version-skew CUTOVER gates:
   version-match the standalone pod + verify registered redirect_uris are exact
   before adding "iam" to the live --enable (runtime-data checklist, not code).

Tests (CGO_ENABLED=0):
- TestIAMEmbedBehindMiddlewareChain — unauth POST /v1/iam/oauth/token, /login,
  jwks + /login/oauth/authorize return 2xx through the REAL SanitizeIdentity +
  BillingGate chain (never 402/503); forged X-User-IsAdmin is stripped; a priced
  control path is denied at zero balance (proves the gate is engaged).
- TestDefaultPriceExemptsIAM — every IAM prefix prices to 0.
- TestValidateIAMSingleReplica — iam + replicas>1 refused; 1/unset/off ok.
- TestMountFailClosed503 — the fail-soft path serves 503 on every IAM prefix.

Build+test green; standalone hanzo iam still links; helm renders replicas=1 for
iam-enabled, replicaCount otherwise. Depends on iam v1.31.17
(hanzoai/iam#feat/iam-embed-entrypoint). STILL STAGED — the standalone iam pod
serves hanzo.id until red GREEN + runtime e2e.
2026-07-05 11:36:15 -07:00
hanzo-dev 68a7e52c4a refactor(o11y): zaptrace ships OTLP over ZAP with no gRPC dep
The ZAP-native trace exporter marshaled its payload via the generated
otlp/collector/trace/v1.ExportTraceServiceRequest, whose sibling
trace_service_grpc.pb.go (no build tag) drags google.golang.org/grpc into the
graph — contradicting the exporter's own contract (ZAP wire, never gRPC).

Encode the ExportTraceServiceRequest envelope directly from the grpc-free trace
messages with protowire: it is a single 'repeated ResourceSpans resource_spans
= 1', so appending each ResourceSpans under field 1 is byte-identical to the
generated marshaler (proven by the existing round-trip test, which still decodes
with the canonical collector type). go list -deps ./zaptrace now shows no grpc.
Hanzo services speak ZAP/HTTP/WS, never gRPC.

Caveat: the cloud module still pulls google.golang.org/grpc transitively via
hanzoai/ai (sibling-owned), hanzoai/o11y (embedded SigNoz — intrinsically an
OTLP/gRPC collector) and hanzoai/base (GCS gRPC transport). Not removable by a
cloud-local change; tracked separately. go.sum: incidental tidy prune of stale
vfs/age checksums.
2026-07-05 11:19:32 -07:00
hanzo-dev 7a2857b1c9 feat(iam): embed IAM in the unified cloud binary as an in-process subsystem
Folds Hanzo IAM -- the identity provider serving hanzo.id (login/authorize/
token/jwks/userinfo, /v1/iam/* admin, OAuth2/OIDC, LDAP/RADIUS) -- into the
unified hanzoai/cloud binary as the LAST binary-consolidation piece
(HIP-0106: "one Go binary embeds IAM + KMS + o11y").

clients/iamsvc wraps IAM's own Beego runtime: iamserver.Init() runs the full
bootstrap without binding a listener, and web.BeeApp.Handlers is mounted
verbatim on cloud's zip.App at every prefix IAM owns (/v1/iam/*,
/.well-known/*, /login/oauth/*, /_/iam/*, /cas/*, /scim/*). No auth logic is
reimplemented -- the same controllers answer, so OAuth/OIDC semantics
(authorize clientId org-resolution, JWT audiences, SuperAdmin owner=="admin",
argon2id password hashing) are preserved byte-for-byte. Registered at order 50
(identity authority, mounts before dependents).

- go.mod: pin hanzoai/iam v1.28.12 -> v1.31.16 (latest; carries the
  authorize-login org-resolution fixes #95/#96 the operator SSO chain needs).
- subsystems.go: blank-import clients/iamsvc; IAM no longer "NOT fused in".

Auth-critical middleware interactions verified: /v1/iam/* prices to 0 in
DefaultPrice (ungated -- the M2M /v1/iam/oauth/token mint is never charged);
SanitizeIdentity strips only forgeable X-User-*/X-Org-* headers, never the
Authorization bearer or iam_session_id cookie IAM's session/oauth logic reads.

Activation is STAGED via the enable-list gate: "iam" is NOT added to the live
--enable until IAM config is present in the cloud runtime and the fold is
verified (login/authorize/token/jwks + operator SSO chain). The standalone iam
pod keeps serving hanzo.id via ingress until then.

Build gate: CGO_ENABLED=0 go build ./... && go test . green. clients/iamsvc
tests prove registration (order 50) + full-path preservation through the mount.
2026-07-05 11:02:49 -07:00
b641365ed7 feat(authors): native /v1/authors OSS-author deploy-royalty loop over the commerce ledger (#141)
The THIRD growth loop next to referrals (one-time credit) and affiliates
(partner commission): pays open-source AUTHORS a royalty on the metered platform
spend of orgs who DEPLOY their projects on Hanzo. Mirrors clients/affiliates
exactly — one SQLite store, server-side tenant isolation, one Mount (HIP-0106),
the SAME commerce ledger path (a credits payout is a grant, tag grant:author),
and an at-most-once accrual latch.

Flow: connect GitHub (IAM-linked account or supplied login) → verify repo
ownership (OAuth admin-check OR a hanzo.json verify-code file) → a deploy of a
verified author repo by ANY org is recorded (provenance) → sweep accrues 5% of
that org's month-to-date spend, at-most-once per (author, deploying-org, period),
self-deploys excluded → staff pay out as credits (real grant) or cash (record-only),
never exceeding pending.

Surface: GET /v1/authors, POST /v1/authors/{connect,repos/verify,deploys/record};
GET /v1/admin/authors, POST /v1/admin/authors/{sweep,:id/approve,:id/suspend,:id/payout}.

10 tests, all -race green: repo canonicalization, both verify methods, deploy
attribution + idempotency, spend×share accrual + at-most-once, lazy dashboard
sweep, credits-one-grant/cash-record-only/pending-guard payout, admin gate.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-05 06:11:55 -07:00
bfaa3c4360 feat(affiliates): native /v1/affiliates partner-commission loop over the commerce ledger (#140)
Mirrors clients/referrals: one SQLite store, server-side tenant isolation, one
HIP-0106 Mount, admin surface global-admin-gated + enveloped for the console
proxy. Affiliates earn an ONGOING commission (default 20%) on the metered spend
of the customers they refer — the recurring, partner-revenue growth loop beside
referrals' one-time both-sides credit.

- apply (org) -> status applied; staff approve mints the code (vanity opt-in,
  uniqueness-enforced, else a derived slug) + sets the rate.
- attribute (?aff capture) records referred_org->affiliate (first-touch, one per
  referred org, self blocked; approved affiliates only).
- accrual sweep: commission = referred org spend this period x rate, latched
  at-most-once per (affiliate, referred_org, period) in one txn; also lazy on the
  affiliate's own dashboard read.
- payout: a credits method issues a commerce grant (tag grant:affiliate); cash
  methods are record-only; can never exceed pending (accrued - paid), reserved
  atomically before any grant.

Tests (go test -race, 9 green): apply->approve, vanity uniqueness (409),
accrual = spend x rate, idempotent-per-period sweep, payout-as-credits issues one
grant + cash record-only + pending guard, admin gate 403, attribution
self/unknown/first-touch, Mount.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-05 05:34:03 -07:00
e78cacb49d feat(referrals): native /v1/referrals viral loop over the commerce ledger (#139)
* feat(referrals): native /v1/referrals viral loop over the commerce ledger

Per-org referral program mirroring clients/crm's structure (one SQLite store,
server-side tenant isolation, HIP-0106 Mount). Grants promo credit through the
SAME commerce deposit path as clients/admin.grantCredit (trial/Credit bucket,
tag grant:referral).

- Stable deterministic referral code per org (base32 of a hash of the org id) +
  a white-labeled ?ref link; persisted directory for O(1) reverse lookup.
- POST /v1/referrals/claim: record referrer<->referee (referee = validated
  caller), status signed_up. Self-referral blocked, one-per-referee idempotent
  (first-touch wins).
- Qualify signal = referee metered spend (honest 'actually used the product').
  On qualify, grant BOTH sides: referrer +$10, referee +$5. At-most-once via a
  credited_at latch — no sweep and no concurrent read can double-pay.
- Trigger: lazy on the referrer's GET /v1/referrals + POST /v1/admin/referrals/
  sweep (cron path). GET /v1/admin/referrals directory, both global-admin gated.
- Constants (bonus amounts + ledger tag) in one place. Commerce behind an
  interface for testable double-grant/idempotency proofs.

Tests: code derivation, self-ref block, idempotent claim, qualify->double-grant
with balances moving through the (fake) ledger, at-most-once idempotency, lazy
qualify on read, admin gate + directory, real Mount. All green (go test -race).

* feat(referrals): envelope the /v1/admin/referrals surface for the console admin proxy

---------

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-05 05:01:58 -07:00
hanzo-dev e2161d7e5b refactor(org): use the shared hanzoai/vfs/replica — kill the duplicate Replicator+election
cloud's internal/org was the ORIGIN of the HA-SQLite machinery; it's now promoted to the
shared hanzoai/vfs/replica lib that every service adopts. Delete the duplicated impls
(replica.go Replicator+Store+DB+DBPath, owner.go Member+Owner+IsOwner+Replicas+HRW) and
re-export them as aliases (shared.go). cloud-specific pieces stay: membership.go (live IAM
source), cipher.go (KMS envelope — already satisfies replica.Cipher), vfsstore.go (Store over
deps.VFS, now using the exported replica.Version). One and one way: ONE Replicator + election,
in vfs/replica, used by cloud AND visor. Builds + org tests green (vfs v0.6.2).
2026-07-05 00:43:11 -07:00
45d9e5a885 fix(deps): bump hanzoai/ai v1.800.7 → v1.800.9 (zen context length → unblocks console chat) (#138)
Zen models were capped at the 4096 fallback in getContextLength, so every
console chat (grounded assistant ~4190-token system prompt) 402'd
'exceeds maximum token count: 4096'. v1.800.9 special-cases the zen* prefix
to 131072. Fixes the P0 console-chat gate.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-05 00:23:17 -07:00
hanzo-devandGitHub 726256b434 Merge pull request #137 from hanzoai/fix/o11y-embed-metrics-port-9090
fix(o11y embed): disable runtime :9090 self-metrics reader — crash-loop guard
2026-07-04 23:15:42 -07:00
hanzo-dev 4e89e21a7c o11y embed: disable the runtime's :9090 self-metrics reader (crash-loop guard)
The embedded o11y runtime's OTel instrumentation defaults to a Prometheus pull
reader bound to 0.0.0.0:9090 (pkg/instrumentation) — the SAME port as cloud's
health listener (CLOUD_HEALTH_LISTEN=:9090). Activating the embed therefore made
the whole cloud process crash-loop with 'listen tcp :9090: bind: address already
in use' (verified on the canary), taking down all of api.hanzo.ai — a listener the
standalone o11y pod never contended for.

buildEmbeddedHandler now defaults O11Y_INSTRUMENTATION_METRICS_ENABLED=false (via
setenvDefault, operator-overridable to a free port) before construction. Cloud owns
process-level observability (exports its own OTel telemetry), so the embed serves
/v1/o11y in-process without a second metrics listener. Extracted the env defaults
into applyEmbedEnvDefaults + TDD (guard + operator-override).

Verified on the cloud-unified-canary: with this default the .104 embed goes Ready
and serves /v1/o11y in-process (health 200); without it the pod crash-loops on :9090.
CGO=0 go build/test green.
2026-07-04 23:15:22 -07:00
hanzo-devandGitHub 3f0c91eb34 Merge pull request #136 from hanzoai/feat/o11y-embed-mainbased
o11y embed: shared community.NewServer (DRY) + health-exempt gate; o11y v1.5.0
2026-07-04 22:46:06 -07:00
hanzo-dev 81dd41e2ab o11y embed: use shared community.NewServer (DRY); exempt health from the gate
Refactor clients/o11y/embed.go onto o11y v1.5.0's shared builder community.NewServer
+ community.NewConfig — the EXACT construction the standalone o11y pod runs — so
the in-process runtime cannot drift from the pod's auth (pkg/identn/iamidentn,
Hanzo IAM gateway-header identity). Collapses the duplicated ~70-line signoz.New
factory list (drift risk) to one call. Enable signal now reads the flat operator
knob O11Y_DATASTORE_DSN (what the pod sets), falling back to the structured
O11Y_TELEMETRYSTORE_DATASTORE_DSN.

Exempt liveness/readiness paths from gate(): the runtime serves them without
identity (k8s probes pass that way), so gating them only breaks unauthenticated
health probes (admin System Health CLOUD_O11Y_HEALTH_URL, the external o11y.*
hosts) without protecting anything. Data routes stay gated (RED forge test still
403s /v1/o11y/api/v1/query_range).

go.mod: o11y v1.4.1 -> v1.5.0 (identical go.mod hash — no new transitive deps).
Build-gate: CGO_ENABLED=0 go build ./... = 0, go test . = ok, go test ./clients/o11y = ok.
2026-07-04 22:44:04 -07:00
zandGitHub 9b9aaf08d9 Merge pull request #135 from hanzoai/feat/o11y-embed-main-iamidentn
feat(o11y): embed the MAIN-based runtime (iamidentn) — auth matches the pod
2026-07-04 22:30:16 -07:00
hanzo-dev c6eba9ed42 feat(o11y): embed the MAIN-based runtime (iamidentn) — auth now matches the pod
The #133 embed pinned o11y v1.3.13, whose runtime authenticates via o11y-native
JWT (tokenizer.GetIdentity on the Authorization bearer). The live gateway-header
traffic the standalone o11y:0.2.0 pod serves — identity injected as X-Org-Id/
X-User-Id/X-User-Email by the gateway — would 401 against that. So activating the
v1.3.13 embed could not replace the pod.

This repoints the embed to the MAIN o11y line (v1.4.1), which resolves identity
through the IdentN resolver's iamidentn provider (default-enabled) from those
gateway session headers, with iamauthz (Hanzo IAM Casbin) for authorization —
the SAME auth model as the running pod. Gateway-header traffic authenticates
(200), not 401.

- clients/o11y/embed.go: build the runtime via pkg/signoz.New with the SAME
  provider factories the standalone cmd/community server uses (noop zeus,
  licensing, gateway, auditor, meterreporter; iamauthz; ClickHouse
  telemetrystore; sqlite sqlstore; IdentN to iamidentn), then app.NewServer to
  server.PublicHandler (new accessor, o11y v1.4.1). runtime.Start runs the
  registry background services (incl. the ruler/alert-rule-manager)
  non-blocking; we never call server.Start (cloud owns its HTTP listeners; OpAMP
  stays out-of-process). Gate/proxy-fallback structure (clients/o11y/o11y.go) is
  unchanged: still O11Y_TELEMETRYSTORE_DATASTORE_DSN-gated, still fail-soft to
  the reverse proxy.
- go.mod: hanzoai/o11y v1.3.13 to v1.4.1 (main line, iamidentn). Drop the stale
  replace prometheus/alertmanager to hanzoai/alertmanager v0.28.2 — it forced
  o11y's code onto the old fork whose api/v2 returns hanzoai/common types that
  clash with o11y v1.4.1's upstream prometheus/common structs. o11y v1.4.1 (and
  the pod) build against upstream prometheus/alertmanager v0.31.1; cloud has no
  direct alertmanager import, so it now matches.

Telemetry backend (ClickHouse datastore StatefulSet, cluster insights) is
untouched — the embedded runtime queries it over ClickHouse-native :9000.

Build-gate: CGO_ENABLED=0 go build ./... OK; go test ./clients/o11y/... OK; vet OK.
2026-07-04 22:22:49 -07:00
hanzo-devandGitHub 341e7c0aaf Merge pull request #134 from hanzoai/bump/tasks-v1.49.0
chore(deps): bump hanzoai/tasks v1.48.0 -> v1.49.0 (durable social primitives + gated auth)
2026-07-04 21:43:17 -07:00
hanzo-dev aff9fcee87 chore(deps): bump hanzoai/tasks v1.48.0 -> v1.49.0
v1.49.0 adds the durable workflow primitives social-orchestrator needs to run
on cloud's embedded gated engine (ServeGated :9999): signal-to-running-workflow
re-dispatch, continueAsNew, startChild, typed search attributes, workflowId
conflict policy, and the signalWithStart wire fix. No cloud code change — the
embedded engine + gated listener pick up the fixes on rebuild.
2026-07-04 21:42:56 -07:00
hanzo-devandGitHub 84ae716f74 feat(o11y): embed the o11y runtime in-process; retire the proxy path (#133)
Constructs the ONE hanzoai/o11y runtime IN-PROCESS (clients/o11y/embed.go) —
the SAME bootstrap the standalone cmd/server runs (o11y.New with its provider
factories -> app.NewServer -> server.PublicHandler) — and installs it via
o11y.SetHandler, so /v1/o11y/* is served by THIS binary against the ClickHouse
`datastore` (StatefulSet, cluster insights) instead of reverse-proxying a
standalone o11y Deployment. The standalone o11y pod can now retire; the
ClickHouse datastore stays as the telemetry backend.

- clients/o11y/embed.go: buildEmbeddedHandler wires telemetrystore (ClickHouse/
  datastore), sqlstore (sqlite under cloud's data root), querier, dashboards,
  alerts; starts the registry services + the alert rule manager (StartBackground).
  Enabled by O11Y_TELEMETRYSTORE_DATASTORE_DSN (the DSN is the one knob).
- o11y.go Register callback: prefer the in-process runtime; fall back to the
  reverse proxy when the embed is disabled (no DSN) or fails to init — fail-soft,
  zero downtime. Proxy handler + gate + tests retained for the fallback path.
- Bump hanzoai/o11y v1.3.12 -> v1.3.13 (adds Server.PublicHandler + StartBackground).
- Drop the stale `replace gorilla/mux => containous/mux`: it was a copied Traefik
  replace block; Traefik is not in the graph and nothing calls the containous API,
  but the fork lacks mux.MiddlewareFunc that o11y's otelmux needs. Standard
  gorilla/mux v1.8.1 satisfies every consumer.

Deferred (reported, not faked): OpAMP collector management (a second websocket
listener) is not started in-process — telemetry ingest continues on the existing
collector->datastore path. Build/test gate is CGO_ENABLED=0 (as prod ships): o11y
+ hanzoai/sqlite resolve to a single modernc sqlite driver registration.
2026-07-04 21:27:54 -07:00
zandGitHub 0a294af85e billing(#70): enforce per-scope spend caps + rate limits at the edge (metering v0.1.4)
Red SHIP; conflicts (only #45 clients/team) resolved to main; 22 money-path+regression tests green; go build clean. Edge calls standalone commerce /authorize; inert by default.
2026-07-04 20:53:45 -07:00
hanzo-dev 8b7a1cc57c Merge remote-tracking branch 'origin/main' into feat/scope-spend-limits
# Conflicts:
#	clients/team/account.go
#	clients/team/account_store.go
#	clients/team/account_store_test.go
#	clients/team/account_test.go
#	clients/team/bots.go
#	clients/team/roster_test.go
#	clients/team/store.go
#	clients/team/team.go
#	clients/team/token/token.go
#	clients/team/token/token_test.go
#	clients/team/transactor.go
2026-07-04 20:47:26 -07:00
bb2e6f5e8e chore: pin tasks v1.48.0 (was mutable pseudo-version) (#132)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 20:43:20 -07:00
8d2a33990f feat(durable): expose embedded tasks engine on a gated cluster ZAP listener (#131)
Consolidation: kill the standalone tasksd pod by running its consumers on cloud's
in-process embedded engine. After Embed wires the loopback (ungated, in-process
ai-ingest) listener, call emb.ServeGated(ctx, 9999, validator) to expose the SAME
engine cluster-wide under mandatory identity gating.

RequireIdentity: every request on :9999 must carry an IAM auth_token, validated
against {IAMIssuer}/v1/iam/.well-known/jwks (HIP-0111) and org-scoped to its owner --
the same trust anchor as the HTTP SanitizeIdentity boundary. The loopback dialer for
ai-ingest is untouched (127.0.0.1:19999, ungated, cloud's own trust boundary).

Fail-soft: a missing IAMIssuer or a bind failure logs and leaves the gated surface
down without disturbing ai-ingest. 9999 mirrors the port the retired tasksd exposed,
so a consumer repoint changes only the host (tasks.hanzo.svc -> cloud.hanzo.svc).

Depends on hanzoai/tasks#8 (ServeGated + identity over ZAP). Pinned here to that
branch's commit; repin to the tagged release once #8 merges. universe adds the :9999
Service port.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 20:42:28 -07:00
hanzo-dev ddcc961a52 chore: pin tasks v1.48.0 (ServeGated) for the gated cluster ZAP listener 2026-07-04 20:42:24 -07:00
hanzo-dev 06c00b333f feat(durable): expose embedded tasks engine on a gated cluster ZAP listener
Consolidation: kill the standalone tasksd pod by running its consumers on cloud's
in-process embedded engine. After Embed wires the loopback (ungated, in-process
ai-ingest) listener, call emb.ServeGated(ctx, 9999, validator) to expose the SAME
engine cluster-wide under mandatory identity gating.

RequireIdentity: every request on :9999 must carry an IAM auth_token, validated
against {IAMIssuer}/v1/iam/.well-known/jwks (HIP-0111) and org-scoped to its owner --
the same trust anchor as the HTTP SanitizeIdentity boundary. The loopback dialer for
ai-ingest is untouched (127.0.0.1:19999, ungated, cloud's own trust boundary).

Fail-soft: a missing IAMIssuer or a bind failure logs and leaves the gated surface
down without disturbing ai-ingest. 9999 mirrors the port the retired tasksd exposed,
so a consumer repoint changes only the host (tasks.hanzo.svc -> cloud.hanzo.svc).

Depends on hanzoai/tasks#8 (ServeGated + identity over ZAP). Pinned here to that
branch's commit; repin to the tagged release once #8 merges. universe adds the :9999
Service port.
2026-07-04 20:35:02 -07:00
hanzo-dev c6510261e6 billing(#70): fix Red HIGH-2 project-spoof, MED-4 DenyResource, INFO-7
HIGH-2: principal.ValidatedProject(c) (project, validated) — returns false
today (X-Project-Id is a caller-chosen label, not claim-bound), so the edge
gate + resource meter pass ProjectValidated=false and commerce degrades
project-scoped hard caps to soft. ONE lever to harden when IAM mints a
project claim. MED-4: DenyResource renders ErrSpendCapExceeded -> 402
spend_cap_exceeded (was 503). INFO-7: canonicalService unifies the edge
service label with the resource provider (ml/visor->compute, agents->agent,
security->security.scan) so a cap binds on both surfaces. Bump metering
v0.1.3 -> v0.1.4. Tests green (incl DenyResource spend_cap).
2026-07-04 20:25:04 -07:00
hanzo-dev 509f0ce08e fix(team/account): public-URL OAuth callback origin behind the gateway (#45)
Adds TEAM_PUBLIC_URL / PUBLIC_ORIGIN config: callbackOrigin() returns the
configured public origin (e.g. https://hanzo.team) for the OAuth redirect_uri
instead of the request Host, so cloud emits the registered public callback even
behind the gateway (where the request Host is the internal cluster service).
Unset = unchanged (falls back to originOf). Lets hanzo.team route through the
gateway UNIFORMLY like api.hanzo.ai — removes the need for the temporary
direct-to-cloud edge route.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 20:15:12 -07:00
hanzo-dev 68530100d2 billing: enforce per-scope spend caps + rate limits at the edge (#70)
BillingGate uses metering.AuthorizeVerdict (funds+cap, one round trip):
renders a distinct 402 spend_cap_exceeded (scope/cap/spent) and sets
X-Spend-Warn at the soft threshold; gates on the request price. New ONE
ScopeRateLimit middleware composes zip/middleware.RateLimit per-scope
(org/project/service), dynamic rpm from commerce (short-TTL cache,
fail-open), 429 + X-RateLimit-* — wired after identity, before billing.
ResourceMeter threads project + service(=provider) so resource creation
is scope-gated too. Scope always from the validated principal. Bump
metering v0.1.2 -> v0.1.3. Money-path tests green (402/warn/429/isolation).
2026-07-04 19:47:10 -07:00
hanzo-dev 98fc642ac7 feat(vfs): real in-process deps.VFS on SeaweedFS S3 — team files/avatars (#45)
pickVFSClient returns an S3-backed types.VFSClient (clients/s3vfs.go) when
S3_ADMIN_ACCESS_KEY/SECRET_KEY are set, else DisabledVFS (R-7 fail-closed
preserved). Reuses the SAME s3admin.Admin construction as clients/s3 (DRY, one
credential path). Put/Get/Delete over the shared 'team-blobs' bucket, per-tenant
key prefix (files.go builds team/blobs/<verified-org>/<ws>/<blobId>). S3 NoSuchKey
maps to types.ErrBlobNotFound (honest 404/idempotent-204); any other S3 error →
502 fail-closed (never a dishonest 404). Bucket create-if-absent self-heals a boot
blip. Red-reviewed SHIP. This is the repoint gate: hanzo.team avatars/attachments
now work off cloud.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 16:58:04 -07:00
hanzo-dev 017ebc0761 feat(team): mount clients/team as native cloud subsystem — port from team-go (#45)
Ports hanzoai/team-go into the unified cloud binary as a zip-native subsystem
(order 138, /v1/team/*): account (IAM OAuth bridge + workspaces/members on SQLite),
transactor (Huly wire over wsx, serverVersion 0.6.0 preserved), bots-as-members
(in-process agents.ListForOrg → Employees, removal-reconcile), files (FrontStorage
contract, org+workspace-membership scoped, byte-derived content-type allow-list).

Security (Red-reviewed, all closed): fail-closed SERVER_SECRET degrade-health-only
(never crashes the binary/CI smoke-boot), token exp/nbf, seg() traversal guard,
setCookie verify, cross-tenant blob isolation, VFSClient.Delete fail-closed (deps.VFS
never nil, R-7). Supersedes the stale clients/team a parallel branch swept onto main.

Real deps.VFS wiring (avatars) follows in the next patch (.97) before the hanzo.team
front repoint, so nothing regresses. Migration + repoint + rip of the standalone
team-go Deployment are the remaining cutover steps.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 16:32:19 -07:00
80288d87df admin: trial/prepaid grant source + /v1/admin/grants (list+issue) (#129)
- POST /v1/admin/customers/:org/credit gains `source` (trial|prepaid). A staff
  comp defaults to TRIAL (non-cash Credit bucket, grant:admin tag → billing/bucket
  DepositKind Credit); only explicit "prepaid" mints real money (admin-grant tag →
  Prepaid). Fail-closed: unknown→trial, so a comp never silently becomes payout-able
  cash. source recorded in the audit before/after + response.
- grantCredit refactored to a shared applyGrant core (ONE credit-write path).
- NEW GET /v1/admin/grants — the credit-grant ledger across all orgs, projected
  from the tamper-evident audit trail (action admin.customer.credit): org, amount,
  source, reason, staff actor, date, txid, result. Honest-empty without a local
  audit store.
- NEW POST /v1/admin/grants — issue a grant to any org from the operator Grants
  view (org in body), funneled through the SAME applyGrant core.
- Both global-admin gated (s.guard). grantTag unit-tested.

go build/vet/test ./clients/admin green.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-04 14:54:39 -07:00
hanzo-dev f871bded96 admin: trial/prepaid grant source + /v1/admin/grants (list+issue)
- POST /v1/admin/customers/:org/credit gains `source` (trial|prepaid). A staff
  comp defaults to TRIAL (non-cash Credit bucket, grant:admin tag → billing/bucket
  DepositKind Credit); only explicit "prepaid" mints real money (admin-grant tag →
  Prepaid). Fail-closed: unknown→trial, so a comp never silently becomes payout-able
  cash. source recorded in the audit before/after + response.
- grantCredit refactored to a shared applyGrant core (ONE credit-write path).
- NEW GET /v1/admin/grants — the credit-grant ledger across all orgs, projected
  from the tamper-evident audit trail (action admin.customer.credit): org, amount,
  source, reason, staff actor, date, txid, result. Honest-empty without a local
  audit store.
- NEW POST /v1/admin/grants — issue a grant to any org from the operator Grants
  view (org in body), funneled through the SAME applyGrant core.
- Both global-admin gated (s.guard). grantTag unit-tested.

go build/vet/test ./clients/admin green.
2026-07-04 14:32:44 -07:00
hanzo-devandGitHub 3f63ea482e chore(kms): drop hanzoai/kms/sdk/go straggler, bump luxfi/kms v1.11.6→v1.11.8 (#128)
Align cloud to the target: KMS is the embedded luxfi/kms (clients/kms) alongside
embedded IAM; the last external hanzoai/kms dependency is removed.

- go.mod: bump github.com/luxfi/kms v1.11.6 → v1.11.8 (match the deployed image);
  remove github.com/hanzoai/kms/sdk/go v1.1.1; go mod tidy.
- clients/mpcseal (NEW): the minimal client-side-CEK sealing client for the
  SEPARATE luxfi/mpc node ring — a faithful, behavior-identical inline of the
  subset of the former hanzoai/kms/sdk/go that clients/fleet + clients/provisioning
  use (NewClient/Unlock/Set/Get/Delete + Argon2id→HKDF→AES-256-GCM). luxfi/kms has
  no drop-in equivalent (its pkg/ is server/ZAP/store, not a Vault client), so
  inlining the used subset is the minimal correct change that removes the external
  dep without altering the wire protocol or trust model. Drops the HPKE Wrap/Unwrap
  the callers never used.
- clients/{fleet,provisioning}: swap import path only; call sites untouched.
- clients/kmssvc/login.go + docs/consolidation.md: comment/table refs → luxfi.

Verified: go build ./... = 0, go vet = 0, gofmt clean, clients/provisioning tests
pass. go.mod + go.sum carry zero hanzoai/kms references.

Follow-up (separate, tested change): fold fleet/provisioning sealing into cloud's
embedded deps.KMS once types.KMSClient gains Delete + verified against the live MPC
ring — one KMS surface. Once the universe KMS-collapse PR merges, the deprecated
hanzoai/kms repo/package can be archived.
2026-07-04 14:25:58 -07:00
hanzo-dev 809890b706 feat(principal,fleet,ml): make the data plane tenant+PROJECT aware
The gateway now mints X-Project-Id (an org SUB-SCOPE) alongside X-Org-Id.
Thread it through the keyed surfaces, backward-compatibly — the default
project ("default", or an absent header) resolves to today's exact keys,
so existing single-project tenants are byte-identical.

- principal.Project(c): the ONE read accessor, mirroring c.Org() (zero-copy
  header read, cloned on retain). Defaults to DefaultProject when the header
  is empty. principal.DefaultProject / IsDefaultProject own the default-scope
  semantics in one place (shared contract value with iamauth.DefaultProject).
- fleet: registry refs shard by project via the ONE scopeRef seam —
  "<org>/fleet/clusters" for the default project, "<org>/<project>/fleet/
  clusters" for a non-default one (index, sealed kubeconfig, cache key).
- ml: tenant namespace is "ml-<org>" for the default project and
  "ml-<org>-<project>" for a non-default one; both org and project are
  validated against strict DNS-label regexes (no lossy fold) and the composed
  label is length-checked against the 63-char ceiling, keeping the
  (org, project) -> namespace map injective. A hanzo.ai/project attribution
  label is stamped for non-default projects.
- visor BYO fleet + ml federation resolve project via principal.Project.

Billing stays keyed on the paying org (a project has no separate prepaid
balance); project is isolation + attribution, not a billing key.
2026-07-04 14:19:15 -07:00
hanzo-devandGitHub 7518dd395f fix(deps): repin luxfi/age v1.5.0 -> v1.5.1 (cold-cache checksum SECURITY ERROR) (#127)
luxfi/age v1.5.0 was upstream-retagged (transient files GC'd from the tag
tree), so the tag's zip content on the origin no longer matches the h1 hash
recorded in go.sum. Cold-cache builds (fresh CI, empty GOMODCACHE) fail with:

    verifying github.com/luxfi/age@v1.5.0: checksum mismatch
    SECURITY ERROR

v1.5.1 dereferences the same commit, is immutable, and is sum.golang.org
verified (h1:Gj8iHMMi0lGkKT/mlXV2HVBr2m3vt2v0eKVsTMTtAQM=). Surgical: age
require + go.sum only. go mod verify clean.
2026-07-04 14:15:49 -07:00
08d3c4ac06 feat(crm): Startup Program applications — public intake, AI screen, pipeline (#125)
* feat(crm): startup-program applications resource (intake + AI screen + pipeline)

Public unauthenticated intake POST /v1/crm/applications (rate-limited + honeypot)
writes a dedicated crm_applications record (all fields in metadata JSON), a
best-effort CRM Company+Contact projection, and kicks off an AI screen via the
gateway (score / tier1 / suggested credits / summary / draft reply) that
auto-advances applied->screened. Staff GET/PATCH drive a stage machine
(applied->screened->qualified->credits-offered->onboarded, +rejected w/ reason).
Non-fatal if the LLM is unavailable.

* test(crm): startup applications — intake, honeypot, idempotency, AI screen, stage machine

10 tests: public intake creates application+CRM projection with all fields in
metadata; honeypot drop; validation; idempotent resubmit; end-to-end AI screen
with a fake gateway (score/tier1/credits/reply + auto-advance applied->screened);
non-fatal screen on gateway error; staff PATCH stage machine (advance/skip-block/
reject-requires-reason); pure canTransition + parseScreen + detectTier1.

---------

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-04 13:32:59 -07:00
hanzo-devandGitHub 64e5a9a593 chore(tasksvc): swap embedded Tasks UI to a fresh from-source build (#126)
PR #124 embedded the last-known-good admin-tasks build as a de-risking
fallback. This replaces it with a FRESH build of current admin-tasks HEAD,
built from source in a combined gui+admin workspace (hanzogui@7.3.x +
@hanzogui/admin@7.3.0 workspace-linked; @hanzogui@7.3.x is unpublished, so it
must build inside that workspace — see clients/tasksvc/ui/README.md).

Same contract (base=/_/tasks/, api=/v1/tasks); full component parity
(namespaces/workflows/schedules/batches/deployments/activities/nexus/history).
Embed tests still assert the real bundle (not the placeholder).
2026-07-04 13:29:39 -07:00
hanzo-dev 473b892a2d feat(fleet): unify BYO clusters into the ONE /v1/clusters surface (visor)
One and one way: BYO k8s / BYO-GPU / bare-metal attach now lives on the SAME fleet
surface as managed clusters (visor /v1/clusters), not a parallel /v1/ml/clusters.
- clients/fleet: the shared per-org BYO-cluster Registry — kubeconfig sealed in the
  org's KMS, validated by reaching the cluster (node + nvidia/amd GPU inventory),
  tenant-scoped by the ZAP-propagated X-Org-Id. ONE source of truth.
- visor: POST /v1/clusters (attach) + DELETE /v1/clusters/:id (detach), and BYO
  clusters MERGE into GET /v1/clusters beside managed ones. Nominal management fee
  (rides the compute-fee config — no bespoke env var; customer brings the compute).
- ml: deleted the parallel /v1/ml/clusters; dynForOrg federates ML serving onto the
  org's registered cluster via the shared registry (home client when none).
Builds + vet + tests green.
2026-07-04 13:16:34 -07:00
hanzo-devandGitHub 707a1ab223 feat(tasksvc): embed the real Tasks UI, retire tasks-ui pod (#124)
clients/tasksvc served /_/tasks from github.com/hanzoai/tasks/ui, whose
ui/dist is an empty 'No UI build present' placeholder — so tasks.hanzo.ai
still routed to the standalone tasks-ui pod (a Temporal-Web-UI fork).

cloud is the ONE process that serves tasks.hanzo.ai (durable.go's embedded
engine + /v1/tasks surface), so cloud now owns the UI embed too: a local
clients/tasksvc/ui package bakes the real admin-tasks SPA build (base=/_/tasks/,
api=/v1/tasks) into the binary via //go:embed. One binary, one origin, the
real UI — which lets the tasks-ui Deployment/Service/CR be retired.

Tests prove the embedded bundle is the real SPA (not the placeholder), the
SPA deep-link fallback, immutable asset caching, and GET-only.
2026-07-04 13:14:17 -07:00
hanzo-dev b7188fb04f test(observe): red-team route-precedence probe — scoped GET wins over the o11y proxy wildcard (#59)
Companion security test to the observe subsystem: proves a /v1/o11y/logs
request lands on the org-scoped handler (order 44), never falling through to
the unscoped hanzoai/o11y reverse-proxy wildcard (order 70) that would bypass
tenant scoping (attack #4).
2026-07-04 13:03:37 -07:00
hanzo-dev dcc7bd7ed9 fix(observe): coerce response_status_code (LowCardinality(String)) before numeric compare
Validated the handler SQL against the live signoz_traces schema: response_status_code
is LowCardinality(String), so a raw >= 500 raises NO_COMMON_TYPE and asInt64 on it
yields 0. Wrap with toInt32OrZero() in the RED errs count and the request-log status,
matching the verified live query (real per-org buckets returned).
2026-07-04 13:02:27 -07:00
hanzo-dev 0a92b92b25 feat(observe): live per-org Settings/Status/Logs/Metrics for console products (#59)
New /v1/o11y/{logs,metrics,status} + /v1/settings/:product cloud subsystem
(order 44, wins over the hanzoai/o11y proxy wildcard) backing the console
product-detail tabs with REAL, org-scoped data — no stubs.

- Logs   : ClickHouse signoz_logs (admin: raw app stream) / signoz_traces
           org-tagged request stream (every other tenant), live-tail cursor.
- Metrics: per-org RED (rate/errors/p50/p95) from org-tagged spans
           (attributes_string['hanzo.org']) + per-org LLM usage (cloud_usage).
- Status : live in-cluster health probe (latency) + VictoriaMetrics up{service}.
- Settings: per-(org,product) SQLite CRUD; secret fields -> KMS, never SQLite.

Tenant isolation server-side: org = principal.Tenant (validated owner claim),
bound as a positional ClickHouse param / mandatory WHERE org=? — never a client
header/param/raw-query. Only IAM_ADMIN_ORG sees unattributed infra logs.
Reuses the shared ai/object datastore client (one conn, KMS creds).

Tests: 8/8 pass — store isolation, principal gate on every endpoint,
cross-tenant read denial, secrets-never-in-SQLite (fail closed w/o KMS),
product traversal/injection rejection, honest status down.
2026-07-04 13:02:27 -07:00
hanzo-dev c7c6b6bb26 fix(billing): restore per-item ledger attribution (Meter records kind as Usage.Model)
The 1deec70 agents-metering refactor split MeterUsage out of Meter and
dropped the Model:kind write, so EVERY per-product debit (functions/invoke,
s3/op, provisioning, ml, tracker, automations, security) recorded an empty
model — losing per-item revenue attribution in the commerce ledger. Restore
the one-place mapping in Meter (all 8 resource callers flow through it).

Also fix two stale test doubles that read the retired X-IAM-Org-Id header;
commerce reads X-Org-Id only (same $0-revenue class as the admin.go fix), so
they saw an empty org. Full suite: 58 ok, 0 fail.
2026-07-04 12:58:32 -07:00
035fb11a0b fix(serve): truthful comment — ZAP :9653 is plaintext TCP, needs mesh mTLS (red finding #3) (#123)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 12:46:04 -07:00
hanzo-dev a379519f76 feat(visor,cli): bring-your-own GPU fleet — console surfaces + hanzo gpu CLI
Register a machine's GPU into the cloud fleet with one command and see it on
the console's existing Machines + GPUs pages, tagged provider=byo.

- clients/visor: a BYO worker is a heartbeating presence activity in the org's
  `fleet` tasks namespace (cloud.EmbeddedTasks). fleet.go reads it and folds it
  into the SAME machineView/gpuView the console renders (provider=byo,
  location=on-prem, gpu model + VRAM, online/offline by heartbeat), plus a raw
  GET /v1/fleet/workers. /v1/machines and /v1/gpus union Visor's inventory with
  the BYO workers and degrade gracefully (BYO stays visible if Visor is down).
- cli: `hanzo gpu connect|status|disconnect` — reuses the `hanzo login`
  IAM token (org from its claims; token auto-refresh), detects GPUs via
  nvidia-smi, registers + heartbeats the fleet presence record, and runs an
  outbound worker loop claiming from `gpu-jobs` (pluggable handlers: echo,
  studio.render→local ComfyUI). --daemon installs a systemd --user unit.
- go.mod: hanzoai/tasks v1.46.0 → v1.47.0 (the claim + lease-reaper surface).

E2E (z@hanzo.ai): connect → GB10 'spark' shows provider=byo on
/v1/fleet/workers + /v1/machines + /v1/gpus → echo job claimed + completed.
2026-07-04 12:28:10 -07:00
hanzo-devandGitHub fdf62e7f3c fix(bots): auto-create the bound agent on launch so a bot is messageable (#122)
launchBot bound an agent *name* but never created that agent, so
messageBot's in-process run (/v1/agents/:agent/run -> Resolve) 404'd
"agent not found" — a launched bot could not be messaged.

launchBot now create-if-absent's the bound agent via the SAME
POST /v1/agents the console uses (one create path, forwarding the
caller's validated identity -> org-scoped, IDOR-safe), BEFORE launching
the metered machine so a bad request (e.g. a non-catalog model) 400s
before anything is provisioned. Idempotent: an existing agent (409) is
reused. An omitted model takes the deployment default
(deps.AIDefaultModel, a valid catalog model) threaded from config — no
hardcoded model id.

Also add create/update-time model validation: a client-supplied model
outside the gateway's served catalog is a clean 400 (via the optional
types.ModelLister the real gateway client implements) instead of a
confusing run-time 502; fail-open when the catalog can't be enumerated.

Tests: agents model-validation + default (real store); httpAI.Models
against a fake gateway; visor launch->auto-create->message->resolve E2E
incl. the before/after 404->200 gap proof, idempotency, and bad-model
fail-fast (no machine provisioned).
2026-07-04 12:17:29 -07:00
hanzo-devandGitHub 75f0987994 deps(rag): bump hanzoai/ai v1.800.6 -> v1.800.7 — force gateway embedder at resolution time (fixes RAG ingest hang, #72) (#121) 2026-07-04 11:46:26 -07:00
hanzo-devandGitHub 5a0e8ea486 feat(notify): KMS-only provider creds, remove env fallback (#120)
notify's send surface now reads provider credentials EXCLUSIVELY from cloud's
embedded KMS (cloud.Deps.KMS) at the org-scoped, rotatable ref
orgs/<org>/notify/<svc>/<key> — the same /orgs/<org> namespace
clients/integrations uses, so a cred is seedable + rotatable via
POST /v1/kms/orgs/:org/secrets with no operator-injected env Secret and no
restart. The org is the VALIDATED principal's tenant, never a client header.

Removes the env-first fallback (envCreds/envFirst + the os import): no secret
is ever read from the environment, hard-coded, or logged. A missing key leaves
the value empty and constructProvider fails closed.

Tests rewritten to inject a fake KMS (no env), plus a per-org isolation test
and a regression that creds() ignores the legacy TWILIO_* env entirely.
2026-07-04 11:35:28 -07:00
hanzo-devandGitHub 27e52fc379 deps(rag): bump hanzoai/ai v1.800.4 -> v1.800.6 — default embedder targets the Hanzo gateway, not api.openai.com (#119)
Pulls hanzoai/ai#71: the RAG default embedder (object/init.go seed) now points at
the Hanzo gateway (CLOUD_AI_BASE_URL / CLOUD_AI_API_KEY, model text-embedding-qwen3)
instead of an empty ProviderUrl that hit api.openai.com directly. A server-side
embed to api.openai.com from in-cluster crawled ~180-210s and then failed, so RAG
ingest (/v1/rag/embed) hung AND the Qdrant vector collection was never created
(writeDocsToVector sample embed timed out before ensureVectorCollection ran).
Gateway embeddings are <1s (proven live). The seed self-heals an existing
api.openai.com-direct default to the gateway on boot, so this deploy converges the
live default-embed provider with no manual console repoint.
2026-07-04 11:11:47 -07:00
z c19c07dad5 fix(websearch): admit the validated console principal on /v1/websearch/search
The console (console2 WebSearch module) reaches search through the /cloud proxy
with a signed-in USER BEARER, not the shared X-API-Key. searchGuard required the
key on every call (F2 hardening), so the console got 503/401 — "backend not
initialized" — even though searxng+crawl are deployed and the upstream defaults
are correct.

Reconcile to the ONE-WAY gate the rest of the /v1 data plane uses: at the zip
layer, a request with a validated principal (principal.Validated — X-User-Id
minted by the identity middleware from a verified JWT) proxies straight to
SearXNG; a request with NO principal falls to the unchanged key-based searchGuard
(the hanzo.chat server path). A caller with neither is still refused, so F2 (no
open metasearch proxy) holds — proven by TestSearchNoPrincipalNoKeyRefused.

searchGuard (net/http) is untouched; its 503/401 tests stay green. New coverage:
TestSearchValidatedPrincipalBypassesKey (console bearer, key unset -> 200),
TestSearchNoPrincipalNoKeyRefused (anonymous, key unset -> 503).
2026-07-04 08:50:05 -07:00
zandGitHub 98ed1332e1 Merge pull request #117 from hanzoai/fix/agent-run-internal-egress
agent-runner mints M2M inference token from in-cluster IAM (fixes /v1/agents/:ref/run 502). Forward-integrated with main (#118 admin-guard audience). Reconciles live sha-7912539 onto a semver release.
2026-07-04 08:37:34 -07:00
cd1b77685c fix(identity): accept hanzo-admin-guard as a JWT audience (#118)
cloud-api SanitizeIdentity validates the forwarded IAM bearer against
defaultJWTAudiences before granting global-admin (owner==adminOrg). The
admin.hanzo.ai guard is client hanzo-admin-guard, so its tokens carry
aud=hanzo-admin-guard, which was missing from the allowlist -> the bearer
failed validation, resolved anonymous, and the SuperAdmin gate read false
-> 403, even though the token owner IS admin.

Append the guard client_id (forwards-only, mirrors gateway iamauth). Admin
authority still requires owner==adminOrg, so no widening. Pairs with
hanzoai/gateway audience fix.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 06:35:12 -07:00
hanzo-dev 7912539748 fix(cloud): agent-runner mints M2M inference token from in-cluster IAM (fixes /v1/agents/:ref/run 502)
pickAIClient built the M2M token URL from cfg.IAMIssuer (=https://hanzo.id), a
Cloudflare-fronted host. In-cluster the runner's server-side POST to
https://hanzo.id/v1/iam/oauth/token 403s with CF edge error 1006, so the
oauth2 client-credentials fetch fails and EVERY POST /v1/agents/:ref/run 502s:
  'cloud: chat completion: oauth2: cannot fetch token: 403 Forbidden / 1006'.

New aiM2MTokenURL resolves the token endpoint split-horizon, mirroring the KMS
login-broker (clients/kmssvc) exactly — one policy, no drift:
  1. CLOUD_AI_IAM_TOKEN_URL override
  2. in-cluster IAM_URL (already wired to http://iam.hanzo.svc for JWKS)
  3. public IAMIssuer fallback (single-process deploys)
IAMIssuer stays https://hanzo.id for JWT iss-validation (untouched). The chat
base URL is pointed in-cluster via CR env CLOUD_AI_BASE_URL (universe).

Proven in-cluster: mint token from iam.hanzo.svc + chat to gateway.hanzo.svc
both 200 (real completion). Unit test pins the 3-branch resolution order.
2026-07-04 05:12:39 -07:00
hanzo-dev a160fd5249 deps(billing): bump hanzoai/ai v1.800.3 -> v1.800.4 — widget (hz_) keys bill owner org
Pulls in the ai fix that closes the hz_ widget-key free-inference hole: widget
keys now bill the OWNER ORG (object.WidgetKeyOwner), so reserveBudget +
recordUsage + the balance gate all engage instead of running free/unmetered.
Bounded to the restricted widget model set + token cap; fail-secure when a widget
key is unattributable.
2026-07-04 04:41:47 -07:00
hanzo-devandGitHub da8fe6e5d5 fix(kms): broker uses in-cluster IAM_URL for token exchange, not public issuer (CF 403s in-cluster loopback) (#116)
The per-tenant KMS secret-sync login broker derived its IAM token-exchange URL from the public issuer (hanzo.id), which Cloudflare 403s for in-cluster server-side POSTs → the sync could never authenticate. Prefer in-cluster IAM_URL (+ CLOUD_KMS_IAM_TOKEN_URL override), fall back to issuer. Unblocks PaaS per-tenant secret env (proven: git-built ai-demo app deployed on maxpower).
2026-07-04 04:05:44 -07:00
c3a811d23a feat(notify): fold notifyd OTP send surface into the unified cloud binary (#115)
Mounts /v1/notify/{send,send/sms,send/email,health} natively in-process as the
cloud subsystem "notify" (order 139) — the native, in-process replacement for
the standalone notifyd (github.com/hanzoai/notify) Deployment.

notifyd's ONLY production consumer is Hanzo IAM's OTP send
(POST /v1/notify/send?sync=true, event=iam.otp_sent), and the live tenant's
template/provider/event tables are empty, so this folds exactly that contract
and nothing more. It reuses notifyd's OWN public provider packages
(service/{twilio,twilioemail,plivo,mail}) and wire types (pkg/types) — no
duplication of provider plumbing; only the internal-only cred->constructor glue
is mirrored.

Security: unlike the ClusterIP-internal notifyd (which trusted a raw X-Org-Id),
/v1/notify/send is reachable via the public gateway here, so it gates on a
VALIDATED principal and derives the org from principal.Tenant — the same
trust-boundary move clients/auto makes. Credentials come from env (the
KMS-synced notify-twilio Secret) and KMS via cloud.Deps.KMS; none is hard-coded
or logged. Ships a built-in iam.otp_sent template so the fold is strictly more
available than notifyd is today (whose empty store would 400 an OTP send).

Sync-only: the Temporal notify-send async plane is intentionally NOT folded;
async (no ?sync=true) returns 503, exactly as notifyd does without a worker.

Build-gated: go build ./... green; go test ./clients/notify/... green; gofmt/vet
clean. go.mod adds only hanzoai/notify + its provider transitive deps.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 03:48:05 -07:00
hanzo-dev c4dda6a800 fix(zt): message-hygiene — 503 body names no internal env
The fail-closed 503 body no longer names ZT_CLIENT_ID/ZT_CLIENT_SECRET;
it now reads 'networking is not configured on this deployment' — a
customer-facing string the console renders as a clean 'not available yet'
state. Ops still see the env names in the Warn log at Mount. No behavior
change; the gate() fail-closed contract is identical.
2026-07-04 03:24:53 -07:00
zandGitHub 7e27214b11 Merge pull request #114 from hanzoai/feat/slack-integrations-bridge
feat(integrations): @hanzo Slack agent bridge — events/commands/link on /v1/integrations/slack/*
2026-07-04 03:18:33 -07:00
hanzo-dev e5d7b1d38a fix(integrations): Red delta — recover async turns + shed before dedupe (M-2, M-1)
RED M-2 [MED] — contain panics in the async agent-turn goroutine. The dispatched
turn (handleSlack* → slackAgentReply → agents.RunOnBehalf, a large surface over
UNTRUSTED Slack input) ran UNRECOVERED — middleware.Recover() only wraps the sync
request goroutine — so a panic would crash the ENTIRE shared multi-tenant cloud
binary (every tenant, every subsystem). Introduced slackSpawn: runs an
already-slotted turn in a recovered goroutine (recover defer registered LAST so it
runs FIRST; the slot release still runs after it, so a panicking turn frees its
slot). Test TestSlackTurnPanicRecoveredAndSlotReleased.

RED M-1 [MED] — shed BEFORE burning the dedupe key. The old order was
mark-then-dispatch: MarkSlackEvent recorded the event_id, then a pool-full drop
silently 2xx-acked → Slack never retried and a later retry was deduped away, so
the @mention vanished. New order (events + slash): verify HMAC → resolve org →
TRY-ACQUIRE a pool slot; on shed record NOTHING and return a retriable 429 (Slack
re-delivers when a slot frees — the turn never ran, so no double-run and no burned
key); on acquire → MarkSlackEvent (release the slot on duplicate/error) → spawn.
The fast empty-2xx ack is kept for the normal path. Test
TestSlackShedReturnsNon2xxAndDoesNotRecord.

Also corrected the slack_dedupe.go replica note (we no longer "always 2xx-ack" —
a capacity shed returns a retriable non-2xx and records nothing, so it is not a
double-process).

RED M-3 [MED] deploy single-replica (Recreate + persistent CLOUD_DATA_DIR) — the
universe cloud manifest, owned by the deploy lane; the in-code single-writer
invariant comment is kept accurate here.

go build ./... = 0, go vet ./... = 0, go test ./clients/integrations/
./clients/agents/ -race green (25 tests).
2026-07-04 03:03:36 -07:00
hanzo-dev 4249b0f989 fix(integrations): address Red review — wire routes, per-org pool, replica scope
RED H1 [HIGH] — wire the bridge into integrations.Mount (was only in a test
helper → the front-door didn't exist in prod). The 5 literal routes are
registered BEFORE the /:provider wildcards (registration-order precedence, same
discipline as clients/agents' static-before-:ref) and are PUBLIC at the JWT
layer: IdentityMiddleware only POPULATES a principal (never rejects) and
DefaultPrice returns 0 for /v1/integrations/* so BillingGate passes through —
reached exactly like /:provider/callback. Auth is HMAC (events/commands) /
signed __Host- cookie (link legs) INSIDE the handler. New test
TestSlackRoutePrecedence proves GET /slack/link hits slackLink (not :provider),
/v1/integrations/slack still resolves the provider view, and the webhook is
reachable with no principal.

RED M1 [MED] — per-org concurrency sub-limit. The agent-turn pool was one
process-global semaphore; one org bursting @hanzo could starve every tenant.
Replaced with orgLimiter (global cap + per-org cap, SLACK_AGENT_ORG_CONCURRENCY
default 8). The org is now resolved SYNC in the webhook path so the pool keys on
the RESOLVED tenant before a slot is taken. New test TestOrgLimiter.

RED M2 [MED] — corrected the false "holds across replicas" dedupe claim: the
table is per-process embedded SQLite (single-writer per HIP-0302), so the billed
webhook path MUST run single-replica (stated as the shipping invariant); a
shared SETNX store is the multi-replica follow-up.

RED L1 [LOW] — moved the dedupe-table DDL into the store's migrate() (store.go)
— fail-loud at Mount, one place — and removed the lazy first-use ensure whose
LoadOrStore-before-run could permanently disable the path on a transient DDL
error. slackBridgeReady now only inits the process pool + link seen-set.

Deferred (flagged for clients/integrations owner): L2 UNIQUE(provider,
external_id)+first-org-wins refusal on duplicate team connect; L3 purge
user:<slackUser>:refresh secrets on disconnect (currently inert after
disconnect, no leak).

go build ./... = 0, go vet ./... = 0, go test ./clients/integrations/
./clients/agents/ -race green (18 + 5 tests).
2026-07-04 02:41:14 -07:00
hanzo-dev 060659ae8b feat(integrations): Slack agent bridge on the one-binary integrations plane (#45)
Port the hardened @hanzo Slack agent front-door from team-go/pkg/slack into
the unified Hanzo Cloud integrations plane, so Slack is ONE connector aligned
with the one-binary north star. It CONSUMES the existing Slack OAuth provider
(the per-org bot token it seals) and the framework seams
(OrgForExternalID / TokenFor / ConnectionFor); it adds no new custody path and
edits no existing file.

clients/agents:
- onbehalf.go: exported in-process RunOnBehalf(ctx, org, userSub, ref, input) —
  the clean in-process twin of the HTTP run handler (no gateway hop, no
  Cloudflare/IPv6 exposure). Resolves the agent org-scoped, runs it through the
  SAME runAgent -> executeRun -> meter path, bills billingActor(org, userSub)
  against org's ledger. Takes org+userSub DIRECTLY (caller pre-authenticated).

clients/integrations:
- slack_events.go: Slack Events webhook + slash command. HMAC-verified over the
  EXACT raw body with a 5-min replay window; url_verification challenge; routes
  @mention + DM to an on-behalf-of run; durable dedupe on event_id; fast empty
  ack + bounded async worker pool. Posts the reply into the thread with the
  org's bot token, or the link prompt EPHEMERALLY.
- slack_link.go: transplant-safe 3-leg per-user link (__Host- init/link cookies,
  leg1<->leg2 nonce continuity checked BEFORE any exchange, single-use). Binds
  Slack<->Hanzo via hanzo.id OIDC (hanzo-slack client) and seals the refresh
  token per (org, "slack", "user:<slackUser>:refresh").
- slack_verify.go: Slack signature verify + single-use link-state crypto
  (constant-time HMAC over s.stateKey; orthogonal to the OAuth-connect state).
- slack_dedupe.go: durable event-dedupe table as Store methods (no store.go edit).

PER-ORG ISOLATION (ship bar): an event's org comes ONLY from
OrgForExternalID(team_id) — never the payload; the reply uses THAT org's bot
token (TokenFor); the run is THAT org's agent (RunOnBehalf org-scoped). Tests
prove team A's event never resolves/tokens/runs as org B.

Mount wiring (5 routes) is handed to the clients/integrations owner — this
change adds NO Mount edit (clean separation); handlers are (s *svc) methods.

Tests (go test -race, green): HMAC reject (bad/missing/stale), dedupe
idempotency, per-org isolation (end-to-end bot-token capture proves the reply
used the connecting org's token), link transplant-rejected (no/mismatched init
cookie refused before exchange), RunOnBehalf bills the right actor.
2026-07-04 02:10:35 -07:00
hanzo-dev cfcd40ac3a fix(deps): align luxfi/age v1.5.0 go.sum hash with sum.golang.org
The recorded zip h1 for github.com/luxfi/age v1.5.0 (zC/Fw…) did not match
the immutable Go checksum transparency log (sum.golang.org), which records
G69Hb… — the same bits the module proxy and local cache serve. The stale
hash made the ENTIRE module unbuildable: every `go build` failed with a
checksum mismatch / SECURITY ERROR. The /go.mod hash already matched sumdb;
only the zip h1 was wrong. Aligning it to the transparency-log-verified
value unblocks the repo (`go mod verify` -> all modules verified). age is an
indirect dependency; no version bump.
2026-07-04 02:10:18 -07:00
024dbc186a feat(admin): GET /v1/admin/o11y — global fleet observability over the one datastore (#111)
Cross-org fleet o11y for admin.hanzo.ai (global-admin only, s.guard fail-closed):
fleet totals (requests/tokens/cost/errors/orgs/models from hanzo.cloud_usage;
latency p50/p95/p99 + error-rate + services from signoz_traces; log volume from
signoz_logs), usage + log-volume timeseries, and top-N orgs/models/services
leaderboards, plus the fleet Langfuse generation rollup. Un-org-scoped by design
— the one place a fleet operator crosses tenants; a non-admin bearer is refused
403 before a row is read. Reuses the shared aiobject.DatastoreQuery transport
(no second connection) and the compute/analytics honest-empty pattern; admin
reads only, owns no table. Time bounds are positional params, bucket interval a
server-side constant — injection-safe. Pure builders + parsers unit-tested.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-04 01:54:32 -07:00
zandGitHub e477579d45 Merge pull request #113 from hanzoai/feat/automations-phase1
feat(automations): Connectors+Automations engine — Phase 1 (HIP-0106 #51)
2026-07-04 01:53:55 -07:00
zandGitHub 7f30bae821 Merge pull request #112 from hanzoai/fix/gosum-luxfi-age
fix(go.sum): realign luxfi/age@v1.5.0 to the proxy content hash (unblocks cloud releases)
2026-07-04 01:53:14 -07:00
hanzo-dev 4bc4502279 fix(go.sum): realign luxfi/age@v1.5.0 to the proxy content hash
luxfi/age@v1.5.0 was force-retagged upstream: proxy.golang.org now serves
content hashing to G69HbSV… while go.sum pinned the stale zC/Fw… → every
cloud release fails at `go mod download` with a SECURITY ERROR (checksum
mismatch), blocking the whole pipeline. Dockerfile already sets GOSUMDB=off,
so the mismatch is against the committed go.sum, not the sumdb. Realign to the
exact hash CI computes from the proxy (same fix IAM shipped as fee44857).
2026-07-04 01:53:00 -07:00
hanzo-dev c347ba1484 fix(automations): RED fix set — exactly-once run bookkeeping + SSRF/caps/audit hardening
Addresses CTO's post-RED fix set (isolation boundary already approved airtight).

MED-1 (exactly-once metering/audit/persistence across ALL entrypoints): the
durable path is now the SINGLE owner of run bookkeeping. FlowRunWorkflow runs a
RecordRunStartActivity keyed on the workflow id (workflow.GetInfo — a scheduled
cron mints a fresh id per tick, so each tick is its own metered run despite the
schedule embedding one fixed FlowRunInput.RunID). Store CreateRunIfAbsent (row
idempotency) + ClaimMeter (atomic metered-flag 0->1) meter+audit only the winner,
so manual /run, MCP, and cron never double-bill. Manual /run no longer meters/
audits — it only CreateRunIfAbsent for immediate visibility. RecordRunEndActivity
records terminal status. Proof: TestScheduledRunMeteredExactlyOnce (a tick meters
once + shows in listRuns; two ticks = two distinct runs) + TestRunStartBookkeeping-
Idempotent (recordRunStart twice = one meter, one row).

MED-2 (honest SSRF blocklist): isPublicIP now rejects the IANA special-use ranges
Go's net helpers miss — 100.64/10 CGNAT (Alibaba metadata 100.100.100.200),
0/8, 192.0.0/24, 192.0.2/24, 192.88.99/24, 198.18/15, 198.51.100/24, 203.0.113/24,
240/4, 64:ff9b::/96 NAT64 — plus v4-mapped-v6 normalization. Comment no longer
overclaims a complete cloud-metadata blocklist. TestIsPublicIP covers each range +
public IPs still allowed.

MED-3 + LOW-4: step-count (<=256) + serialized-tree (<=512KB) caps at create /
version / operation time -> honest 422; resume payload bounded (<=64KB) -> 413.

LOW-2: per-org concurrency limiter (429) on run-starts + synchronous MCP tool calls
(bounds the core.delay goroutine lever). TestConcurrencyLimiter + TestFlowStepCap +
TestResumePayloadBounded.

LOW-1: MCP meters/audits AFTER Run, outcome derived from the real result — a failed
/ SSRF-blocked / not-connected call audits as error and is NOT billed. TestMCPAuditOutcome.

LOW-3: updateFlow validates publishedVersionId names an existing version OF THIS
FLOW in-org (else 422). TestUpdateFlowPublishedVersionValidated.

INF-1: register() panics at init on a <connector>_<action> tool-name collision so a
future connector can't silently make MCP dispatch ambiguous. TestToolNameCollisionPanics.

Tests: 25/25 green (CGO=0 build/vet/test; -race clean under cgo). Full module builds;
cmd/cloud links. catalog.json untouched.
2026-07-04 01:38:15 -07:00
hanzo-dev 4c7b07b340 feat(integrations): Slack connect lights up on the public client_id alone
Authorize needs only SLACK_CLIENT_ID (a public value in every consent URL);
the SECRET is required only at the callback token exchange. Gate available/
connect on client_id so an org reaches Slack's Allow screen as soon as the
public id is set, while a deployment still missing SLACK_CLIENT_SECRET fails
the exchange with an honest ?error=slack (never a dead-end).
2026-07-04 01:31:54 -07:00
zeekayandhanzo-dev a7277ba3e0 fix(deps): bump hanzoai/ai v1.800.2 -> v1.800.3 for brand .cloud CORS fix
Pulls the cors_filter static-allowlist fix so console.lux.cloud (and
zoo/pars brand consoles) stop getting 403 "origin is not allowed" on
/v1/signin. Cleared stale sum.golang.org-poisoned go.sum entries for
re-tagged luxfi/{age,precompile,keys} (GOPRIVATE direct re-records the
current content hashes; matches the repo's GOSUMDB-off CI recipe).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-04 01:20:55 -07:00
hanzo-dev 2ff71fff3c feat(automations): merge full 701-piece catalog + /v1/automations OpenAPI
- catalog/catalog.json: 706 pieces (5 Tier-A executable connectors + 701
  ActivePieces catalogue entries); action/trigger props normalized string[]
  -> []PropSpec so PieceMetadata unmarshals at Mount (boot-parses green).
- docs/automations-openapi.yaml: OpenAPI 3.0.3, 13 paths all under /v1/automations.
- http_test: assert catalogue invariant (PieceCount==len, Tier-A present) not
  the seed-pinned count.
2026-07-04 01:09:57 -07:00
hanzo-dev 4592fc1ebd feat(automations): Phase-1 Connectors+Automations engine (HIP-0106 #51)
Native-Go /v1/automations/* subsystem in the unified cloud binary. Composes
three existing seams, never reinvents them:

- clients/integrations  — per-org connector creds via integrations.TokenFor
  (KMS-sealed, fail-closed); connectors never touch KMS directly.
- cloud.EmbeddedTasks    — the ONE shared in-process durable engine; a flow
  runs as a durable workflow in the OWNER's namespace (per-org lazy worker,
  mirroring ai/object/ingest_tasks.go).
- clients/principal      — the ONE tenant gate on every data handler.

Isolation is physical: ONE SQLite file, org column + org-led index on every
table; the durable activity's SOLE credential scope is FlowRunInput.Owner —
the VALIDATED org set at flow-start, never a client-supplied field.

Surface: pieces catalogue (go:embed), flows CRUD + versions + FlowOperation
apply, durable runs (start/list/get/resume via SignalWorkflow), enable/disable
(POLLING -> CreateSchedule), and a HIP-0300 MCP JSON-RPC tool surface
(/v1/automations/mcp) exposing every connector action as <connector>_<action>.

Connectors (Tier-A, self-registering): core (http_request SSRF-guarded via a
dialer Control hook, delay, code data-mapper, wait_for_approval signal
waitpoint), slack (send_message), github + google_sheets/drive (fail closed
until integrations custodies their tokens).

Metering + audit on flow-run start and MCP tool call. Order 148 (after
integrations 137, before ai's /v1/* catch-all 150).

Tests (16, all green with -race): store org-isolation, HTTP org-gating (403),
durable flow run reaching SUCCEEDED with threaded step outputs on an embedded
tasks engine, connector token isolation (in.Owner is the sole cred scope),
MCP tools/list + gated tools/call dispatch, pieces catalogue.
2026-07-04 01:03:06 -07:00
336f60f8d4 feat(o11y): HTTP request + LLM/agent traces over ZAP (single provider) (#110)
* feat(o11y): emit an OTel SERVER span per /v1/* request over the ZAP wire

Cloud installed a ZAP tracer provider (cmd/cloud initTelemetry) but nothing in
the handler chain opened a span, so no request ever flowed through it — the o11y
Monitoring tab saw zero hanzo-cloud request traces (receiver="zap" span count
was flat-zero while logs streamed over ZAP).

TracingMiddleware (middleware_tracing.go) opens one SERVER span per /v1/*
request off the GLOBAL tracer (= the ZAP provider), records the OTel HTTP
semantic-convention attributes (method, route, status) + request_id/org, maps
error/5xx to an error span status, and writes the span context back onto the
request via SetContext so every downstream span (agent.run -> agent.step -> the
chat client span in clients/aihttp) parents under it: one trace tree per
request. Health/readiness/metrics + non-/v1 paths are skipped so probes never
flood the trace store. Wired right after RequestID in the canonical pipeline
(serve.go) so the whole authenticated chain nests under it.

c.Path()/c.Method()/headers are zero-copy views over the fasthttp request
buffer, which is recycled for the next request BEFORE the batch span processor
serializes the span asynchronously — so retained views corrupt (live: a
GET /v1/models span exported with http.route="/v1/chat/c..."). strings.Clone
pins our own copy for every retained attribute. Tests cover emission, attribute
mapping, error status, parent/child propagation, the skip set, and an env-gated
on-wire live test (CLOUD_ZAP_LIVE_ENDPOINT) that ships real spans to a ZAP
receiver — the async-export + ctx-reuse path the in-memory recorder can't model
(and the one that surfaced the corruption).

* feat(o11y): make cloud the single tracer-provider owner — one wire (ZAP)

The fused cloud binary set the ZAP provider first, then ai.Bootstrap (during
MountAll) called hanzoai/ai object.InitTelemetry which, seeing the CR's
OTEL_EXPORTER_OTLP_ENDPOINT, installed a SECOND, competing OTLP provider. OTel
global delegation is first-writer-wins for handles created before the first
SetTracerProvider (cloud's package-level tracers keep ZAP), but the ai GenAI
tracer is resolved lazily AFTER the second Set, so its spans stranded on
OTLP(:4318) while ZAP owned the rest — the split that left receiver="zap" span
count at zero for hanzo-cloud (verified live: spans arrived only via
receiver="otlp").

Composition-root fix: once cloud installs the ZAP provider, clear the
OTLP-exporter env (OTEL_EXPORTER_OTLP_ENDPOINT / _TRACES_ENDPOINT) so no embedded
subsystem installs a competing OTLP provider. Exactly one provider (ZAP), one
wire, deterministic regardless of CR env drift. In the fused binary OTLP is only
ever the collector's interop RECEIVER, never cloud's exporter; standalone
cmd/aid (no ZAP endpoint) is unaffected and keeps its OTLP path.

---------

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-04 00:56:42 -07:00
hanzo-dev 435ceeddfb fix(kb): RED H1/M1 — inject X-Piece-Run-Secret on the auto piece-run call
The auto engine now gates /v1/auto/pieces/{piece}/run on a shared secret (it
trusts X-Org-Id absolutely, so the write+SSRF surface needs an in-band caller
proof). cloud is the ONLY legitimate caller — it resolves each org's real token
and pins the provider URL — so it presents the secret (from KMS, the same
PIECES_RUNNER_SECRET) as X-Piece-Run-Secret. pieceSync fails closed if the
secret is unset (a doomed call the engine would 403 anyway).
2026-07-04 00:05:48 -07:00
hanzo-dev 9d299ab169 feat(auto+kb): hybrid connector layer — /v1/auto proxy + activepieces long-tail
Mounts workflow automation + the ~280-app activepieces long tail in-platform,
per-org, through the ONE knowledge store. Go core + JS on-demand.

clients/auto: /v1/auto/* per-org REVERSE PROXY to the standalone Hanzo Auto
engine (one engine, one store — not re-embedded). The auto engine trusts
X-Org-Id absolutely, so this proxy IS the trust boundary: it GATES on a
validated principal (refuses the anon-forge X-Org-Id-with-no-credential path)
and re-stamps outbound identity from validated values only (strips every
smuggled authority alias). Pure gate+proxy in clients/auto/proxy (5 isolation
tests: anon-forge 403, per-org forward, smuggled-header strip, path preserved).

clients/kb: the first LONG-TAIL connector (notion). Identical OAuth lifecycle
(HMAC-org-bound state, KMS token path) but its PULL runs the activepieces JS
piece through the auto engine's on-demand runner (sync_piece.go) instead of
native Go — then files each record via the SAME framework.Ingest path. One
ingestion path; a JS-sourced doc lands in the same per-org store+index as a
Go-sourced one. clients/kb/notion is the pure record-shaper (6 tests).

ONE catalog: /v1/kb/connectors/catalog lists native Go + long-tail piece
connectors in one list, each badged kind native|piece (3 tests).

RED LOW-1: collection() + kmsRef() now route org through provisioning.SanitizeOrg
(the codebase's ONE normalizer) so the physical Qdrant namespace + KMS path are
injective in the owner ("a b" != "a_b") — defense in depth under the payload.org
filter. Injectivity tests + KB integration tests updated to derive the collection
through the helper (robust to the normalizer).

All tests green under CGO=0 (production config). Full binary boots; /v1/auto
mounted, anon-forge 403, catalog gated, spine (kb/framework health) 200.
2026-07-04 00:05:48 -07:00
zeekayandhanzo-dev 03f024ac9d fix(billing): payment-methods → commerce portal read; pin the full subject-key set
Address review: proxy the customer card list to commerce's admin-group PORTAL
endpoint (GET /v1/billing/portal/payment-methods), not the user-group
/payment-methods. PortalPaymentMethods 400s without a ?customerId=, so pinning
only ?user= would break it — generalize the proxy's subject pinning to the FULL
commerce edge-auth key set {user,userId,customerId} (now a shared
billingSubjectKeys var, identical to clients/console + commerce), pinned to the
caller's OWN org on every request. This leaves NO billing endpoint unfiltered
regardless of which param it reads (usage/balance/gpu-eligibility read user;
portal/payment-methods requires customerId) and is strictly more tenant-safe.
pinSubjectBody reuses the same var. The console keeps requesting the same-origin
/v1/billing/payment-methods (mounted here); the portal hop is server-side only.

Tests updated: widen-scope now asserts every subject key is pinned (org dropped);
payment-methods asserts the portal path + customerId pin. 14/14 pass.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 23:37:00 -07:00
hanzo-dev 2a4659f834 chore(deps): bump hanzoai/ai → v1.800.2 (durable worker retention + fail-fast OpenAI embedding default) 2026-07-03 22:47:33 -07:00
zeekayandhanzo-dev ba0fdff868 feat(billing): proxy GPU launch-gate + payment-methods on customer /v1/billing
The customer billing proxy (clients/billing) exposed only usage+balance, so the
console GPU launch gate — card-on-file check + prepaid eligibility read + the
prepay-only charge — had no org-scoped cloud route and fell through to the
console pkg's /v1/billing/* wildcard (admin-shaped 403). Extend the SAME
commerce-proxy helper (no new HTTP/auth machinery) with the three enforcement
routes commerce 1.46.28 serves (api/billing/gpu_charge.go + portal):

  GET  /v1/billing/gpu-eligibility -> commerce GET  (read-only launch gate:
       {eligible,reason,prepaidAvailable,cardOnFile,...}; amountCents +
       minPrepaidCents + currency pass through)
  POST /v1/billing/gpu-charge      -> commerce POST (prepay-only, card-required
       debit; commerce enforces both gates + gpu-tagging server-side; status
       forwarded verbatim: 201 ok / 402 card_required|insufficient_prepaid)
  GET  /v1/billing/payment-methods -> commerce GET  (masked brand+last4 cards
       for the card-on-file check; type passes through)

All org-scoped to the caller's OWN org from the VALIDATED IAM owner claim
(principal.Tenant), identical to usage/balance — a client can never widen scope:
the GET subject is pinned to ?user=<org> (commerce's privileged payment-methods
branch filters CustomerId on it), and the POST body subject is pinned to the
{user,userId,customerId} set (mirrors clients/console + commerce edge-auth), so
a forged body can never charge another tenant. New commerceProxy.post + the
pinSubjectBody helper; no principal -> 401, unconfigured -> 501.

Tests: gpu-eligibility scope+passthrough+forged-subject overwrite;
payment-methods scope+type; gpu-charge body-subject pin + 402 verbatim + 401
no-principal + 501 unconfigured; pinSubjectBody unit. 14/14 pass.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 22:40:11 -07:00
zeekayandhanzo-dev d1779528a2 feat(billing): customer-facing org-scoped /v1/billing/{usage,balance}
On console.hanzo.ai the ingress routes /v1/* straight to cloud-api:8000 (the
console Next BFF is only at "/"), so the console's /v1/billing/usage +
/v1/billing/balance calls land on cloud-api — NOT the console's per-tenant
commerce proxy. cloud-api wired commerce billing ONLY under the admin-gated
aggregate (/v1/admin/*), so a normal org owner (davelorenzini/maxpower) hitting
/v1/billing/usage had no customer route and was denied -> 403 -> the "Access
required" wall on EVERY product overview + o11y usage panel.

Add a customer-facing, org-scoped billing READ surface (clients/billing):
GET /v1/billing/usage and /v1/billing/balance. Org = the VALIDATED IAM owner
claim (principal.Tenant — the trusted X-Org-Id the identity middleware minted
from the caller's verified session; never a client header), so a customer reads
ONLY their OWN org. Proxies commerce with COMMERCE_SERVICE_TOKEN + X-Org-Id=<org>
and the per-org billing subject pinned to user=<org> (admin.orgSubject /
metering identityFromCtx — verified live: user=<org> returns the real wallet);
returns commerce's raw body + status verbatim (the console parses the raw ledger).
Tenant isolation: no client-supplied subject/org query is ever forwarded, so
scope can never be widened. The all-orgs god view stays admin-only (clients/admin).

Tests: subject pinned to caller org, forged user/userId/customerId/org dropped,
start/end/currency pass through, no-principal -> 401 (commerce untouched),
unconfigured -> 501, commerce status forwarded verbatim.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 22:28:52 -07:00
zeekayandhanzo-dev bd8bb52514 fix(deps): bump hanzoai/ai → v1.800.0 (async Sora-style /v1/videos #68)
Pulls ai#68: async OpenAI Sora-style video API onto the cloud router.
POST /v1/videos/generations returns a video_<uuid> job immediately (was
sync ~104s → console /ai proxy 502); GET /v1/videos/{id} polls; GET
/v1/videos/{id}/content streams the MP4. Metering exactly-once (hold on
create, settle on completion, reaper releases abandoned), ownership-secured.

ai v1.800.0 go.mod is identical to v1.799.3 — no dependency-graph change;
only the hanzoai/ai hash lines move. Verified: cloud binary builds clean
(CGO_ENABLED=0) and the router now serves /v1/videos/generations,
/v1/videos/:id, /v1/videos/:id/content (spark-video backend).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 22:27:59 -07:00
d356b24e40 feat(tracker): native /v1/tracker issue tracker on SQLite (#109)
Durable replacement for the Huly/Svelte hanzo.team tracker whose upstream
each-block reactive-batching render race left issue lists rendering zero
rows. Native Go over one org-scoped SQLite store: rows return as plain JSON
and render deterministically (no Svelte reactivity in the path).

clients/tracker/store.go  — projects + issues on {DataDir}/tracker.db, the
  same modernc/SQLCipher driver + MaxOpenConns(1)+WAL pattern as projectsvc/
  crm. Per-project monotonic issue numbering allocated inside one tx (never
  races under the single-writer conn). Cascade delete in a tx. org column is
  the tenancy key; every query filters WHERE org=?.
clients/tracker/tracker.go — /v1/tracker/projects[/:key][/issues[/:num]] CRUD.
  org = principal.Tenant (validated IAM owner claim, HIP-0026), 403 otherwise.
  Status/priority closed sets; board/list via ?status=. Create wired to the
  shared per-org billing seam (free by default; ops prices via
  CLOUD_TRACKER_FEE_CENTS). Registered order 129, before the AI /v1/* catch-all.
subsystems/subsystems.go — one blank import links it into the binary.

Store CRUD/numbering/status-filter/cascade/tenant-isolation proven green on
real SQLite (clients/tracker/tracker_test.go).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 21:39:07 -07:00
hanzo-dev 3f2f92dbd3 chore(deps): bump hanzoai/ai → v1.799.3 (real default embedding provider — ingest produces real vectors); ships with the durable-enqueue default-namespace fix 2026-07-03 21:08:46 -07:00
hanzo-dev 232dfcb1e0 fix(durable): enqueue ingest into the 'default' namespace, not a per-org one
ROOT CAUSE of durable ingest silently running inline (round-trip: github ingest blocked
25s+, no workflow in Tasks): the embedded engine only registers 'default' at boot and does
NOT lazily create namespaces on ExecuteWorkflow, so dialing Namespace:<org> made the worker
poll a non-existent namespace and BLOCK → EnqueueIngest hung → handler fell back to inline.
Fix: dial 'default' (always registered). Data isolation is unchanged — it's in the workflow
INPUT (IngestSource is owner-scoped), never the namespace. Now github/crawl enqueue a real
durable workflow that appears in Tasks (under default).
2026-07-03 20:36:16 -07:00
hanzo-dev e883c83acd fix(deps): correct hanzoai/ai to v1.799.2 (v1.799.1 concurrent work + OpenAI-compat /v1/audio/speech) — supersedes the mis-numbered v1.796.6 downgrade 2026-07-03 18:13:45 -07:00
hanzo-dev 73b97198d0 chore(deps): bump hanzoai/ai → v1.796.6 (OpenAI-compat /v1/audio/speech; audio+image+video all native) 2026-07-03 18:12:22 -07:00
hanzo-devandGitHub 866a783b71 fix(kms): close V6+V1 pre-activation blockers on the PaaS KMS→Secret sync (#108)
V6: accept the owner-bound per-tenant machine audience (<owner>-platform-kms) so a real client_credentials sync token clears SanitizeIdentity + the /v1/kms guard; decoupled from global-admin (isKMSMachinePrincipal). V1: per-IP rate limit + MaxConnsPerHost(h2-off) on the public login broker. Blue→Red→Blue→Red: Red SHIP (0 crit/high/medium). Activation runbook in the PR body + EnsureOrgIdentity doc.
2026-07-03 17:55:23 -07:00
hanzo-devandGitHub 9f4856695a feat(kb): Knowledge Base + unified AI memory + connectors on the DocType engine (#107)
Fourth app lane (after cms/erp/help): a Notion-like KB + agent memory + app
connectors as a 'kb' module on clients/framework — no new Base, no new database.

Fixtures (module kb): kb-page (wiki tree via a self-Link parent + Lexical
RichText body), kb-memory (agent memory: note/fact/observation), kb-source
(connector-ingested docs), kb-connector (connection metadata; OAuth token in KMS,
never in the doc/logs). All CRUD/permissions/tenant-isolation/install are the
framework's generic /v1/framework/* surface + the generic @hanzo/ui renderer.

Indexing (index.go, the ONE vector-write path): an after_save hook embeds every
knowledge write (page/memory/source) via the gateway and upserts it into the org's
OWN Qdrant collection (kb_<org>) with an org-pinned payload; on_trash removes it.
Human wiki + AI memory are ONE per-org knowledge store, indexed once. Fail-open at
index time (a vector outage never blocks a knowledge write); fail-honest at query.

Retrieval (subsystem.go): POST /v1/kb/search is the org-scoped RAG entry point —
collection AND payload filter both pinned to principal.Tenant, so a caller can only
retrieve its OWN knowledge. Degrades to an honest empty result when the index is
down.

Connectors (connectors.go, sync.go): per-org OAuth to GitHub/Slack/Google that
ingest external docs INTO the same store + index (via framework.Ingest → same
after_save hook — one ingestion path, never forked). OAuth state is HMAC-bound to
the validated org (defeats login-CSRF/mix-up); tokens live in KMS at a per-org path.
GitHub is end-to-end (repo READMEs + issues); Slack/Google share the OAuth
lifecycle + normalizer with an honest 'listing not yet implemented' depth marker.

framework.Ingest/UpdateData/FindByField/Search: the in-process create-with-hooks
API first-party producers (the connector sync) use so off-request writes run the
exact validate + lifecycle pipeline and stay physically org-scoped.

Tests (16, all green): engine-Validate on every fixture; page self-Link + Lexical
body; connector-has-no-token; per-org pointID/collection/kmsRef isolation; payload
org-pin; OAuth-state org-binding + tamper/cross-provider/wrong-key rejection;
Ingest validates+fires-hooks+org-scoped. Integration (real SQLite + mock
Qdrant/embeddings over the real HTTP surface): install → create kb-page in org A →
after_save indexes into kb_A → search as A retrieves it → search as B sees NOTHING
(no cross-org leak); forged-org search → 403; kb-memory lands in the same kb_A
namespace.
2026-07-03 17:15:08 -07:00
hanzo-dev 1a115aab29 harden(integrations): red-team defense-in-depth on the OAuth connector plane
Adversarial review of the connector framework (state HMAC, nonce custody,
per-org KMS token custody, console redirect). Core design held: state forgery,
nonce replay/race, cross-tenant KMS pathing, principal-forge, and the seam
fail-closed contract were already sound. Fixes are defense-in-depth + red-style
proving tests; the contract is unchanged (no /api/, no /v1/slack route).

Fixes
- Ingest sanitization (vector 7): provider-supplied NON-secret metadata
  (account label / external id / bot user id / scopes) is now stripped of C0
  control chars + DEL and length-bounded at the ONE framework ingest point in
  callback, before it is logged, stored, or reflected. Kills log-line/separator
  injection via a crafted Slack workspace name and bounds per-org row growth.
  Secret token VALUES bypass this and go straight to the KMS seal.
- Open-redirect hardening (vector 4): success/failRedirect fold into one
  query-escaping consoleRedirectURL builder (DRY + unit-testable). Confirms the
  Location host is always the env-fixed console origin; hostile provider detail
  can't break out of the query into host/scheme/path or inject CRLF.
- Request bounds (vector 10): callback rejects an oversized OAuth `code`
  (maxCodeLen, also covers the in-process ZAP plane); verify() rejects an
  oversized state token before any base64 work (maxStateLen).
- kmsDelete uses errors.Is(kms.ErrSecretNotFound) for wrap-safe idempotency.

Tests (all real, -race green; 39 pass)
- state: dot-injection/degenerate split, MAC-checked-before-parse,
  validly-signed-but-hostile-org rejected, overlong rejected.
- store: concurrent single-winner nonce consume (race proof).
- http: no-open-redirect property, end-to-end metadata sanitization,
  disconnect anonymous-forge -> 403 (secret+row survive), github scaffold
  callback fails closed at the Configured gate before any exchange,
  oversized-code rejected.
2026-07-03 17:12:25 -07:00
hanzo-dev ec6869279c test(integrations): real TDD suite for the connector framework
29 tests, all green under -race:
- state: sign/verify, tamper, expired, wrong-provider, wrong-key, malformed, key resolve
- store: org isolation, connected_at preservation, external-id resolve, nonce single-use, GC, idempotent delete
- slack: authorize URL params, exchange parse (httptest ok+error), revoke, registration shape
- integrations: list shape, connect unconfigured->503 / no-principal->403 / KMS-down->503 / invalid-org->400,
  callback happy path (real KMS-sealed token + connection row + 302 console), replay rejected, tampered state rejected,
  disconnect (KMS+row deleted, idempotent), org isolation, seam fail-closed when unmounted.
KMS custody uses a REAL clients/kms.Client with a 32-byte master key; no mocks in prod paths.
2026-07-03 17:12:25 -07:00
hanzo-dev e0287a0e6f feat(integrations): generic OAuth connector framework (Slack ref, GitHub scaffold)
Provider-agnostic /v1/integrations plane: one registry, N providers.
Slack = full reference impl (OAuth v2 bot-token); GitHub = scaffold + #51 seam.
Per-org token custody in KMS (sealed); state-authed HMAC callback with
single-use nonce; org derived ONLY from signed state on the public callback.
Generic /v1/integrations/{provider}/callback — no /v1/slack/* (team-go owns it).
Wired at order 137 (after security 136, before AI 150).
2026-07-03 17:12:25 -07:00
hanzo-devandGitHub 4d2d6b0ed6 fix(ci+sqlite): tag-after-push release + single "sqlite" driver in both cgo/nocgo (#105)
release.yml — invert the tag/build order so a git tag can NEVER exist without a
pushed, boot-verified image (the phantom v1.786.42/43 → ImagePullBackOff cause):

  main push → compute next version → build → SMOKE (boot to "listening") →
  push image → git tag (receipt) → notify universe

- Tag is minted only AFTER the push step succeeds; any build/smoke/push failure
  fails the run before the tag step → fail-run-no-tag.
- concurrency group `release-cloud` (cancel-in-progress:false) serializes runs so
  two main pushes can't collide on a number; the queued run re-reads tags and
  lands on the next patch → monotonic.
- next version = max(highest git tag, highest pushed ghcr container tag) + 1,
  folding in container tags so a pushed-but-untagged number is never reused.
- removed the `tags: v*` trigger (this workflow now OWNS tags — a hand-cut tag has
  no image behind it and won't build); notify-universe fires only on a successful
  build+tag, so universe is never told about a phantom.

sqlite — fix `panic: sql: Register called twice for driver sqlite` under
CGO_ENABLED=1 (blocks `go test ./...` + clean cgo rebuilds). #96 moved cloud's
stores to github.com/hanzoai/sqlite (mattn under cgo) while several embedded deps
still import modernc.org/sqlite directly (ai, tasks, base, commerce, o11y, orm) →
two packages register "sqlite" under cgo. Prod is CGO_ENABLED=0 (all one modernc
package, deduped) so prod never paniced; the panic is cgo-only.

- bump github.com/hanzoai/sqlite v0.1.4 → v0.1.5: adds the `sqlite_purego` opt-out
  build tag that forces the fork's pure-Go (modernc) backend under cgo. Default
  cgo path is unchanged (mattn/SQLCipher) so IAM/commerce encryption is untouched.
- bump github.com/hanzoai/ai → the commit that routes object/adapter.go + cmd
  tools through hanzoai/sqlite instead of modernc (never modernc directly).
- Makefile: CGO_ENABLED?=0 default (matches the shipped Dockerfile) so `make
  build`/`make test` register "sqlite" once and exactly mirror prod; new `test-cgo`
  target proves the cgo path via `-tags sqlite_purego`.

Verified: CGO_ENABLED=0 `go build/test ./...` and CGO_ENABLED=1 `-tags
sqlite_purego go build/test ./...` both pass with NO panic (the eval package that
panicked now passes in both modes). Pre-existing clients/s3 + clients/functions
billing-attribution test failures are unrelated (present on clean main, both
modes) and out of scope.
2026-07-03 17:05:47 -07:00
hanzo-devandGitHub 7d072d9366 fix(console): close encoded-traversal gap on the /v1/billing money surface (#106)
billing.go's isSafeSegment left percent-escape (`%2f`/`%2e`) and matrix-param
(`;`) segments undecoded, so `/v1/billing/x/..%2fadmin` forwarded
`x/..%2fadmin` verbatim; the Go http client + commerce's own router
decode+normalize it downstream into a path that tunnels PAST /v1/billing into
another surface. commerce.go had already patched its call site with an inline
`%;` check — braiding the policy across call sites.

Harden the ONE shared segment guard instead: isSafeSegment now rejects empty,
`.`/`..`, slash, backslash, percent-escape, matrix-param, and any control char.
Both bridges (billing + commerce) get the complete guard from one place, and
commerce.go's call site drops the now-redundant inline check.

Regression test: `..`, `%2f`, `%2e%2e`, and `;` all 400 and never reach
upstream (proven to fail against the pre-fix guard).
2026-07-03 17:05:08 -07:00
hanzo-devandGitHub 9e6490f415 feat(console): per-tenant /v1/commerce/* store bridge for the static console (task #41) (#104)
The store twin of the just-merged /v1/billing/* bridge (#102). #81 namespaced
the console's commerce store calls to the canonical same-origin /v1/commerce/*
(SPA->server->/commerce proxy); the statically-exported console now terminates
every dynamic call at the unified cloud binary's /v1, so the binary must
reverse-proxy /v1/commerce/* to the commerce service. Without it the commerce
embed was incomplete.

clients/console/commerce.go serves GET|POST|PUT|PATCH|DELETE /v1/commerce/<path>
-> commerce's BARE store surface /v1/<path> (the console-side 'commerce'
namespace is stripped: the deployed commerce cmd/commerced mounts
api.Route(Group('/v1')), so products/orders/customers/... live at /v1/<kind>
while money lives at /v1/billing/*). Exactly the mapping console2's next.config
rewrite proved live (/v1/commerce/:path* -> /commerce/v1/:path* ->
commerce.svc/v1/:path*).

IDOR-safe: the org is the VALIDATED caller's own (resolveCaller ->
principal.Validated / c.Org()), never a client value; a bearer-less forged
X-Org-Id has no validated principal and is refused 403 before any commerce call.
Reuses the commerceDo(base,token) S2S transport billing.go/topup.go share
(admin COMMERCE_SERVICE_TOKEN + X-Org-Id, which commerce's EdgeAuth trusts only
behind the service token). Least privilege: a store-head allow-list (identical
to console2 proxy-allow.ts COMMERCE_HEADS) so the bridge can never tunnel to
/v1/billing (its own subject-scoped bridge), /v1/checkout, or tenant admin.

Hardened over a naive port: rejects percent-encoded path segments (%2f/%2e),
which the router leaves undecoded in the wildcard param but the Go http client +
commerce's router normalize downstream -- 'product/..%2fbilling' would otherwise
tunnel to /v1/billing past the allow-list (RED). Mirrors console2 pathIsClean.

/v1 only. CGO_ENABLED=0 go build ./... ok; go test ./clients/console/ ok.
2026-07-03 16:54:19 -07:00
hanzo-devandGitHub 3f5000e8ff feat(platform): activate PaaS KMS→Secret sync — org-scoped coords + login broker + per-tenant identity (#42) (#103)
Companion to #89 (KMS-sealed PaaS secret env) + universe #321. The sync was
INERT for two structural reasons this closes, and the per-tenant scoping the
task requires is now enforced at cloud's ONE auth boundary — proven by test.

WHY IT WAS INERT (coordinate drift + wrong CR shape):
  - Seal path ≠ read path. cloud sealed at /platform/tenant-<org>/<app> but the
    kms-operator reads through cloud's org-scoped surface /v1/kms/orgs/<org>/
    secrets/... which folds to /orgs/<org>/... — a DIFFERENT record, never found.
  - The CR set projectSlug="platform" (a literal) and omitted secretsScope.keys,
    which the CRD REQUIRES (MinItems=1; luxfi/kms has no list endpoint). Either
    alone starves the sync.
  - hostAPI carried a /v1/kms suffix; the operator appends /v1/kms/... itself, so
    login + read URLs doubled the prefix.

THE FIX (secrets.go):
  - Seal at the org-scoped coordinate  orgs/<org>/platform/<app>/<KEY>  — the EXACT
    store path cloud's org-scoped read surface addresses. Seal and read are now one
    coordinate (proven: TestPaaSSecretSealReadAlignment).
  - CR carries projectSlug=<org>, secretsPath=platform/<app>, envSlug=default, and
    the explicit sorted key roster. hostAPI = KMS root.

PER-TENANT SCOPING (the NON-NEGOTIABLE) — enforced, not hoped:
  - The operator authenticates as a per-tenant IAM machine identity (owner=<org>)
    via the NEW /v1/kms/auth/login broker (kmssvc/login.go): it exchanges the
    caller's clientId/clientSecret at IAM's client_credentials endpoint and returns
    IAM's owner-scoped token verbatim. cloud is a relay, not an issuer.
  - cloud's org-scope guard admits /orgs/<org>/... ONLY when the VALIDATED owner ==
    that org (SanitizeIdentity derives owner from the token, ignoring client
    X-Org-Id). So tenant-A's credential can NEVER read tenant-B's path — 403 before
    the store is touched (proven: TestPaaSSecretCrossTenantDenied).
  - credsSecret is a PER-TENANT name in the tenant namespace — never a shared
    platform-wide reader (that would be a cross-tenant hole = NO-SHIP).

PROVISIONING (ensureTenantKMSAuth) — fail-closed, one privileged seam:
  - On app-create/deploy cloud ensures the tenant's owner=<org> credential is
    projected into tenant-<org> as the creds Secret the CR references, via an
    injected tenantKMSIdentity provider. nil provider (default) ⇒ honest "pending"
    (operator can't log in ⇒ reads nothing) — NEVER a shared or wrong-org identity.
  - FLAGGED: the concrete provider needs a scoped IAM admin credential cloud does
    not yet hold (clients/admin/iam.go replays the caller's cred, no service
    identity). Until wired/verified, sync stays safely pending. Flip ON = provision
    the per-tenant identity; the security invariant holds regardless of how it is
    minted (the guard is the enforcement point).

Tests (CGO_ENABLED=0 — prod/CI build mode; CGO test builds double-register sqlite,
a pre-existing module issue): alignment round-trip, cross-tenant 403 (+ A→A 200,
B→B 404, unauth 403), login broker happy/bad-cred/malformed, per-tenant provisioning
(fail-closed when unprovisioned, org-bound projection, no cross-tenant ask). Existing
kmssvc red-team guard vectors unchanged and passing.
2026-07-03 16:44:28 -07:00
1343b10fc5 feat(console): per-tenant /v1/billing/* bridge for the static console (task #41) (#102)
The BFF catch-all sweep's one real "server work -> Go handler" case. console2's
app/billing/v1/[...path]/route.ts injected the commerce SERVICE token and pinned the
caller's billing subject server-side (work a static export cannot do). Ported to
clients/console/billing.go: GET|POST /v1/billing/* forwards to commerce with the admin
COMMERCE_SERVICE_TOKEN, scoping every request to the VALIDATED caller's own subject
(billingSubject + scopedBillingSearch + scopedBillingBody, the Go port of console2's
billing-scope.ts), so a tenant can only read/act on its OWN ledger.

IDOR-safe: the subject is the validated principal (resolveCaller: principal.Validated /
c.Org() / c.User()), never a client userId/org. A forged X-Org-Id with no validated
X-User-Id is refused (403). Unset COMMERCE_SERVICE_TOKEN -> honest 501.

DRY: commerceDo (topup.go) refactored to take (base, token) so the wallet top-up AND
this bridge share one S2S transport. No behavior change to topup (its tests pass).

Tests (billing_test.go): billingSubject personal/dedicated, subject pin + org drop +
passthrough (query & write body), forged-value overwrite, 403 no-principal, 501 no-token,
and the end-to-end scoped forward to a fake commerce. go build ./clients/console/ = 0;
go test (CGO_ENABLED=0) ok. The default-CGO modernc-vs-CGO sqlite double-register that
panics the package is a pre-existing repo-wide issue (separate sqlite-one-driver lane).

Co-authored-by: Hanzo AI <ai@hanzo.ai>
2026-07-03 16:28:32 -07:00
79667baa43 fix(identity): spoof-proof X-Project-Id/X-App-Id at the SanitizeIdentity boundary (#101)
SanitizeIdentity minted an un-forgeable X-Org-Id but passed the org sub-scopes
X-Project-Id / X-App-Id through verbatim, so a caller could assert ANOTHER org's
project as a compute_usage attribution key or per-project sub-scope. Sanitize the
sub-scopes in the ONE trust boundary:

- Delete every X-Project-Id/X-App-Id on ingress (no raw client copy survives),
  then re-inject only for a validated principal, against the acted-as org.
- Refuse a cross-org X-Project-Id: a project REGISTERED to a DIFFERENT org than
  the validated org is dropped; the caller's own registered project and
  unregistered free-form within-org labels survive (projectIsForeign; fail-closed
  on a registry error).
- Drop both sub-scopes entirely on the anonymous path.
- X-App-Id is a caller label, not an isolation boundary (no cloud subsystem
  scopes access by it; the un-forgeable org bounds any mislabel) - forwarded on
  the validated path, dropped when anonymous.

Dependency-inverted like sites.SetResolver: projectsvc registers a
TenantScopeResolver at Mount; cloud never imports the project registries. The
visor proxy forwards the now-validated sub-scopes so compute attribution lands on
the caller's own project. X-Org-Id anti-forgery is unchanged.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 16:24:37 -07:00
hanzo-dev cfe80a3c05 chore(deps): bump hanzoai/ai → v1.796.5 (zen-video spark-video provider); integrated blue/cloud-ml-sa-auth (cloud-ml SA k8s auth) 2026-07-03 16:24:20 -07:00
hanzo-dev cc629adef4 feat(framework): RichText fieldtype for the CMS WYSIWYG body
Add a RichText fieldtype to the DocType engine so a content field can hold a
Lexical EditorState JSON string (the console renders it with a native WYSIWYG).
The value is opaque text — validate.go coerces it verbatim (clipped to the scalar
bound), stored in the schemaless doc blob, round-tripping through create→get with
no shape enforcement (that's a UI concern). Minimal + fail-closed: the fieldtype
is added to the validated allow-set, so an unknown type is still rejected.

CMS: the seeded content body (Article/Page/Post) becomes RichText, and a
Data field is added for optional per-project scoping (the console's org→project
switcher filters content by it; empty = org-level). One CMS engine; project is a
filter.

Tests: TestDocTypeValidate accepts a RichText field; TestFieldTypeValidation
proves a Lexical JSON string round-trips verbatim through validation.
2026-07-03 16:18:14 -07:00
hanzo-blueandhanzo-dev 288a22ac62 ml(clients): authenticate as dedicated cloud-ml SA via HANZO_ML_TOKEN_FILE
The ML control plane (clients/ml, /v1/ml) ran under the pod SA (cloud-api),
braiding KServe/Kubeflow cluster reach onto the product-API identity. newDynamic
now re-scopes the in-cluster client to a mounted cloud-ml ServiceAccount token
when HANZO_ML_TOKEN_FILE is set (keeps in-cluster host+CA, swaps only identity),
fail-closed if the configured token is unreadable. Unset -> unchanged behaviour
(pod SA) for local/dev and pre-cutover. Pairs with universe ml-rbac.yaml
(cloud-mlsvc ClusterRoleBinding -> cloud-ml). go build + go vet clean.
2026-07-03 16:14:29 -07:00
hanzo-dev 9c2d91f4de docs(cloud): wave map — remaining Go services and their merge disposition
The execution queue for "all Hanzo Go services merge into the one cloud binary"
(HIP-0106): wave 0 already-merged (8 embedded modules + 37 native clients),
wave 1 tasks+visor (this build), wave 2+ mount queue (notify2, extract-svc,
playground, ...), and keep-standalone with reasons (iam/gateway/kms-MPC/registry
/s3/docdb/chain daemons). Waves are sequential through go.mod to avoid the
in-flight collision this wave hit.
2026-07-03 16:11:00 -07:00
hanzo-dev 7e9e4ca6ab feat(tasks): mount Tasks HTTP+UI surface on the ONE in-process engine
Consolidates the Tasks product surface into cloud — the follow-up durable.go
named ("consolidating that surface into cloud is the follow-up"). durable.go
already embeds the ONE tasks engine in-process (loopback ZAP :19999) for ai's
durable ingest; this mounts THAT SAME engine's HTTP handlers, so the Tasks
UI/API reads the same durable state as ingest. One engine, one binary, one way —
no second Embed.

- clients/tasksvc (order 147, before ai's /v1/* catch-all): adapts the shared
  engine's HTTP surface onto the zip mux at /v1/tasks/* + the embedded React UI
  at /_/tasks/*. The engine is created after MountAll, so the surface resolves
  cloud.EmbeddedTasks() lazily per request (503 fail-soft until wired).
- gate: settings/cluster/health stay open (no per-org data); the data surface
  (namespaces/workflows/mcp/events) refuses an unvalidated principal (403, never
  the unscoped store) and threads the gateway-validated org into the engine via
  tasks/pkg/auth.WithIdentity — per-(org,ns) shard isolation, matching the rest
  of the cloud data plane (clients/principal).
- durable.go: export EmbeddedTasks() — the single shared-engine accessor.
- bump hanzoai/tasks v1.43.0 → v1.46.0 (in-proc identity seam + one sqlite
  driver). No local replace directives.

Proof: /v1/tasks/cluster returns nodeId "cloud-tasks" (durable.go's engine),
settings 200, data routes 403 without a principal, /_/tasks UI 200.
2026-07-03 16:11:00 -07:00
hanzo-devandGitHub 602f5203ae debrand: langfuse -> o11y/observability in our prose & comments (#100)
Drop the Langfuse brand from our own strings (code comments, docs,
config labels), mirroring the signoz->o11y product rename. Meaning preserved;
comments/docs/labels only, no functional change.

Intentionally KEPT (references to the external Langfuse product / upstream
dependency / integration contract, not our brand):
- LiteLLM success_callback/failure_callback ["langfuse"] + LANGFUSE_* env
  var names (the litellm langfuse-callback contract; renaming breaks emission)
- infra/k8s/langfuse/* (deploys upstream langfuse/langfuse:3 OSS image)
- o11y/langfuse-otlp-fanout.yaml + console-langfuse-keys (trace-fanout lane)
- console NOTICE (MIT attribution to Langfuse GmbH for clean-room UX)

Trace pipeline (ai emit -> collector -> backend -> console Observe) unchanged.
2026-07-03 16:06:15 -07:00
hanzo-dev cc0710ad10 Merge native ERP + Helpdesk DocType lanes (feat/erp-help-framework-modules, RED-PASSED 9/9 race)
ERP (clients/erp): ERPNext-core DocType fixtures + native-Go GL/stock hooks —
idempotent deterministic-leg postings (exactly-once under concurrent submit),
on_cancel reversal, finite-guarded totals, double-entry submit gates.
Help (clients/help): Frappe Helpdesk-core fixtures, pure DocTypes, no hooks.
Both register on the framework engine at init; installed per-org via
/v1/framework/modules/{erp,help}/install. No new HTTP surface — ERP/Help ARE
documents on /v1/framework/*, drawn by the same generic DocType renderer as CMS.

Verified CGO=0 (production Dockerfile config): binary boots clean (no double
sqlite driver register), /v1/framework/health 200, /v1/models unshadowed (503
real AI handler), erp+help tests green under -race.
2026-07-03 15:51:13 -07:00
97b90ae449 feat(visor): /v1/bots surface + machine agent-binding proxies (CLOUD, mirrors machines) (#98)
Mounts /v1/bots in cloud as the sibling of /v1/machines — a Bot is an
Agent(cloud /v1/agents) + a kind=bot Machine(vm) + their AgentBinding,
composed as a thin proxy over the SAME Visor client the machines routes use:

  GET    /v1/bots                    list (vm /v1/machines?kind=bot + bindings join)
  POST   /v1/bots/launch             machine launch{kind:bot} THEN bind-agent
  GET    /v1/bots/:id                machine + its binding (404 if not a bot)
  DELETE /v1/bots/:id                unbind THEN terminate the machine
  POST   /v1/bots/:id/:action        message=agent run | stop|pause=unbind

Plus the machine agent-binding proxies cloud lacked (vm already serves them):

  POST   /v1/machines/:id/bind-agent
  GET    /v1/machines/:id/agent-binding
  DELETE /v1/machines/:id/agent-binding
  GET    /v1/agent-bindings

Every route org-gated by the validated principal (principal.Tenant), forwarded
to vm as ?owner=<org> — 403 without a valid IAM owner, exactly like machines.
No vm change: kind=bot launch + bind-agent are already live at visor:19000.
message runs the bot's bound agent via the ONE agent runner (/v1/agents/:agent/run).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-03 15:47:45 -07:00
hanzo-dev 6832090ee3 fix(durable): pin tasks engine DataDir to cloud data root (distroless has no /tmp)
Embed's default os.MkdirTemp("") resolves to /tmp, absent in the distroless cloud image
→ 'tasks.Embed: tempdir: stat /tmp: no such file or directory' → fail-soft to inline.
Pin DataDir to {deps.DataDir}/tasks (MkdirAll first) so the in-process engine actually
boots. Verified: without this the warn+inline-fallback fired cleanly in prod (v1.786.48).
2026-07-03 15:38:59 -07:00
hanzo-dev bcc097ef05 feat(durable): embed the ONE tasks engine in-process — unified durable queue
cloud embeds hanzoai/tasks IN-PROCESS (loopback ZAP, durable.go) and injects a per-org
dialer into ai's ingest — there is no external tasks service to auth to, no per-org token
minting, no HTTP inner-cloud hop. Long ingests (github/crawl/s3) run as durable workflows
in the owner's namespace (CONTRACT §6); upload stays inline. Fail-soft: embed error →
ai dialer unset → inline fallback. Bumps ai → v1.796.4 (per-org ingest dialer). One engine,
one binary, one way. NOTE: embedded store is memdb today (survives worker crash via retry,
not process restart); console /tasksd still points at the cluster tasks Service for the UI
(consolidating that surface into cloud is the follow-up).
2026-07-03 15:21:08 -07:00
hanzo-dev 59ea8ffba9 fix(erp): address Red review — idempotent postings + cancel reversal + finite guard
Red verdict FIX-THEN-SHIP (0 critical; all findings within-tenant integrity —
isolation, forge-proofing, gates, ledger perms, console deletions all refuted/solid).

- HIGH (TOCTOU double-post): on_submit postings ran before the atomic docstatus flip
  with hash-named legs, so N concurrent submits over-posted the ledger 4-6x. Every
  GL/stock leg now has a DETERMINISTIC name (voucher-<kind>-<index>, via prompt
  autoname) and postLeg is idempotent (pre-read + re-check on create-conflict), so
  posting is exactly-once under any concurrency AND replayable after a partial
  failure — no engine change, uses the existing store API. Balances stay SUM(ledger).
- MED (cancel did not reverse): on_cancel hooks append reversing ledger rows (swap
  debit/credit; negate qty), sharing the SAME leg computation as submit.
- LOW (non-finite total -> 500): finite guards in the totals hooks -> clean 422.
- LOW (comment): tightened the ledger-immutability doc — manager bypass is
  within-tenant authority only (Red confirmed no cross-org escalation).

Regressions: 8 concurrent submits -> exactly 1x200 + GL posted once (2 legs,
race-clean); cancel -> net GL zero-sum + net stock zero; overflow qty*rate -> 422.
go test -race 9/9 (CGO=1) + CGO=0 + vet clean + full cmd/cloud binary.
2026-07-03 15:11:51 -07:00
1ad09837ea eval: mount GET /v1/evals/observations reading hanzo.cloud_usage (#99)
Every AI call already writes the proven hanzo.cloud_usage ledger (model,
provider, tokens, cost_cents, org, user, status) via ai/object's zapWriteUsage
— the same recordTrace funnel that emits the OTel GenAI span. This mounts the
missing native route the console Observe > Observations surface calls, reading
that ledger as Langfuse-v3 GENERATION observations (org-scoped by the validated
principal, bound positional params, bounded LIMIT). No new emission path: one
recordTrace, fanned to o11y (span) + Langfuse (span) + this ledger (read).

- telemetry.go: Observation model + ObservationFilter; ListObservations on the
  Telemetry interface, dsTelemetry (cloud_usage query), memTelemetry (honest
  empty); asInt64 coercer (cloud_usage UInt32 tokens / UInt64 cost — asFloat
  only handles float types).
- eval.go: listObservations handler + observationView/toObservationView mapping
  to the console Observation shape; GET /v1/evals/observations route.
- observations_test.go: view mapping (success/error), asInt64 coercion, mem
  telemetry empty + org-required.

Requires a cloud rebuild + deploy-by-sha to go live (route is code, not env).

Co-authored-by: hanzo <a@hanzo.ai>
2026-07-03 15:06:29 -07:00
hanzo-dev d6ddfc74af chore(deps): bump hanzoai/ai → v1.796.3 (routed /v1/docs/ingest + code-aware splitter + brand-neutral per-org store + transport-agnostic durable-ingest seam) 2026-07-03 15:01:54 -07:00
03be81ef15 feat(o11y): ZAP-native span export + GenAI spans on LLM/agent paths (#95)
- zaptrace: otlptrace.Client over the ZAP wire (github.com/zap-proto/http) —
  spans marshaled as OTLP protobuf, shipped over ZAP frames, NEVER OTLP-HTTP
  (:4318)/gRPC(:4317). Target = collector zapreceiver (:4319).
- cmd/cloud/telemetry.go: initTelemetry uses the ZAP exporter; enable via
  OTEL_EXPORTER_ZAP_ENDPOINT (default otel-collector.hanzo.svc:4319); keeps the
  no-op-when-unset posture.
- clients/aihttp.go ChatCompletion: OTel GenAI client span (gen_ai.system/
  operation.name/request.model + response.model + usage.{input,output}_tokens),
  RecordError on failure. Captures the previously-discarded resp.Usage.
- clients/agents/agents.go: runAgent opens a per-run root span (agent.run),
  executeRun a child agent.step span; the LLM client span nests under them —
  one trace per run: run -> step -> chat.

Test: zaptrace TestUploadTracesOverZAP green (span over the real ZAP wire).

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-03 14:56:48 -07:00
1c30259d24 feat(provisioning): docdb dedicated engine = FerretDB on Hanzo SQL (SQLite) (#97)
Supersede the Base swap (84d4a77). Hanzo Base has a REST/realtime document
API but NOT the MongoDB wire protocol, so it is not a drop-in docdb — a
customer's mongodb:// driver cannot speak to it. The managed "document
database" must accept existing MongoDB drivers unchanged.

The per-org dedicated docdb instance is now a FerretDB v1.24 instance
speaking the MongoDB wire protocol on :27017, backed by Hanzo SQL (SQLite,
pure-Go) — Mongo databases map to SQLite files under /state, collections to
tables, documents to JSON1 rows. ZERO raw mongod (no WiredTiger), ZERO
Postgres, ZERO go.mongodb.org driver in cloud (FerretDB is a deployed pod,
not a Go import). Per-instance SCRAM auth via FerretDB's SQLite-backend
new-auth (FERRETDB_TEST_ENABLE_NEW_AUTH + FERRETDB_SETUP_*); the returned
password is the instance admin credential, sealed in KMS.

engine fields:
- image ghcr.io/hanzoai/docdb-sqlite:1.24.0 — pinned FerretDB v1 with the
  SQLite backend handler, mirrored from upstream by hanzoai/docdb CI (v2 and
  the hanzoai/docdb Postgres/DocumentDB fork both dropped SQLite; v1 is the
  last line that carries it). Distinct package from the Postgres-backed
  ghcr.io/hanzoai/docdb that backs shared chat-docdb.
- fsGroup 1000: FerretDB is distroless and runs as UID:GID 1000 (no
  entrypoint can chown), so a fresh block PVC must be group-writable via the
  pod securityContext.fsGroup the operator stamps from spec.fsGroup — else
  the instance CrashLoops on "permission denied" writing /state.
- FERRETDB_STATE_DIR + FERRETDB_SQLITE_URL pin both process state and the
  SQLite files onto the mounted /state PVC (persist across restarts).

Verified end-to-end against the FerretDB v1.24 SQLite image with this exact
env: mongosh Insert/Find/Update/Delete over the wire protocol, and /state
held per-db admin.sqlite + events.sqlite with "SQLite format 3" magic — no
WiredTiger datadir, no Postgres PG_VERSION (both locally and in hanzoai/docdb
CI on the mirrored image).

TestDedicated_DocdbIsFerretOnSQL asserts the FerretDB image, SQLite backend
env, mongodb:// connString, per-instance SCRAM credential, fsGroup 1000, and
the absence of any Postgres/IAM/Base env. unavailableKinds stays empty.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 14:40:02 -07:00
hanzo-dev 55e338ea84 feat(erp+help): native ERP + Helpdesk DocType lanes on the framework
Second and third app lanes on clients/framework, reusing the generic DocType
engine + install path + generic renderer (like clients/cms) — zero forked
engine, zero HTTP surface of their own, per-org on Base/SQLite.

- clients/erp: 20 ERPNext-core DocTypes (module "erp") — masters (item/
  warehouse/customer/supplier/account/department/employee), submittable
  transactions with child Tables (sales-order/-invoice/purchase-order/
  stock-entry/journal-entry/payment-entry), and two read-only hook-posted
  ledgers (gl-entry, stock-ledger-entry). Business logic as native-Go hooks:
  line/document totals (before_save), balanced GL on invoice/journal/payment
  submit, append-only stock ledger on stock-entry submit, and double-entry /
  non-empty submit gates. Posting is org-scoped via ev.Org + ev.Store.
- clients/help: 5 Helpdesk DocTypes (module "help") — hd-ticket (status
  workflow) + hd-agent/hd-team/hd-sla/hd-canned-response. Pure fixtures, no
  hooks — the purest DRY proof; self-contained (no cross-lane Link).
- SLUG names (erp-*/hd-*), series naming for transactions, field naming for
  masters (console slugifies on write), hash for ledgers — all reachable via
  the generic renderer; no collision with CMS (Author/Media/Page/...) or CRM.
- subsystems: blank-import erp + help so their init() registers the lanes.

Tests: fixtures-valid/model-spec/install-transact-roundtrip/submit-gates/
tenant-isolation/ledger-read-only — go test -race green (CGO=1 and CGO=0),
go vet clean, full cmd/cloud binary builds.
2026-07-03 14:39:26 -07:00
zandGitHub cf027cfeb1 Merge pull request #91 from hanzoai/platform/whitelabel-signin-cloud
feat(auth): cloud accepts every white-label brand's issuer + audience (lux/zoo/pars login)
2026-07-03 14:28:01 -07:00
hanzo-dev 80c15d47bc feat(security): hanzo security scan CLI + decomplect engine into detect pkg
The pure detection engine moves to clients/security/detect (a stdlib-only
LEAF): one engine, two surfaces — the /v1/security HTTP subsystem and the
new local CLI both consume it, neither drags the other in. The subsystem
now calls detect.ScanContent/Rules/SeverityRank; behavior is unchanged.

hanzo security scan [path...] walks a tree, runs the engine, and exits
non-zero when a finding at/above --fail-on (default low; 'none' = report
only) is present — a pre-commit/CI/agent guardrail with no server, auth,
or network. Skips vendored/binary files; never prints a raw secret (masked
preview only). hanzo security rules lists the catalog. -o json supported.
Tests: 9 CLI (find+fail, clean-pass, fail-on threshold/none, json, vendor+
binary skip, bad flag, rules, control-verb), engine+subsystem unchanged.
2026-07-03 14:26:29 -07:00
zeekayandhanzo-dev efba12fee9 feat(auth): accept every white-label brand's cloud audience — one binary, all brands
Extends the white-label issuer-set validation (this branch) to the AUDIENCE half:
a lux/zoo/pars session token carries aud=<brand>-cloud (HIP-0111: client_id == app
== aud), so the audience allowlist must include each or the cloud-native identity
sanitizer 401s a valid lux token even after the issuer gate passes.

- brand.go BrandAudiences() derives <brand>-cloud for every registry brand
  (hanzo-cloud, lux-cloud, zoo-cloud, pars-cloud, bootnode-cloud) — one source of
  truth, mirroring BrandIssuers(); no hand-listed audience.
- config.go jwtAudiencesFromEnv() now ALWAYS unions BrandAudiences() into the
  resolved allowlist (baked like the brand issuers). A legacy hanzo-only
  GATEWAY_ALLOWED_AUDIENCES env override still accepts lux-cloud — the brand auds
  don't depend on getting the deploy env perfectly right. Fail-secure: only ADDS
  the known-good <brand>-cloud client_ids, never an arbitrary aud. unionStrings
  dedupes so an env-supplied entry is never duplicated.

Tests: BrandAudiences (registry-derived, covers every brand), jwtAudiencesFromEnv
brand-union (baked default AND a hanzo-only env override both accept lux-cloud, no
duplicate). Paired with hanzoai/ai#64 (the per-brand signin code exchange).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 14:26:24 -07:00
zeekayandhanzo-dev 8016ea759e wip(auth): white-label issuer-set validation — one binary validates all brand issuers
Widen identityValidator to a trusted issuer SET (primary UNION BrandIssuers) so one
cloud binary validates hanzo AND lux/zoo/pars tokens off the one shared IAM JWKS.
Fail-secure: only known-good brand issuers added. NOT built (phantom go-sqlite3
v2.0.3 dep blocks) / NOT gated / NOT deployed — needs: per-brand EXCHANGE client
verification, build-dep fix, hanzo-login no-regression gate, red review.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 14:26:24 -07:00
d1f82f214d fix(sqlite): every store imports the hanzoai/sqlite fork, never modernc directly (#96)
github.com/hanzoai/sqlite is the ONE Hanzo SQLite driver: it registers the
"sqlite" database/sql name under BOTH build tags (cgo → mattn+SQLCipher,
encrypted at rest; !cgo → pure-Go modernc, wrapped internally). Fourteen
cloud stores plus the pg→sqlite migration blank-imported modernc.org/sqlite
DIRECTLY, so a CGO_ENABLED=1 build registered "sqlite" twice — the fork's
mattn registration AND the direct modernc one — and panicked at init
("sql: Register called twice for driver sqlite"), taking down the whole
fused hanzo/cloud binary.

Swept every direct `_ "modernc.org/sqlite"` → `_ "github.com/hanzoai/sqlite"`
(sql.Open("sqlite", …) calls unchanged — same driver name). go.mod promotes
the fork to a direct require and demotes modernc to indirect (it survives
only as the fork's !cgo backend). Stale comments calling modernc the
"primary" driver corrected. Production already builds CGO_ENABLED=0 (one
modernc package, no collision); this makes the driver choice consistent and
unblocks a CGO_ENABLED=1 + libsqlcipher encrypted build.

NOTE: five UPSTREAM modules (base/core, ai/object, o11y sqlstore,
commerce/db, orm/db) still import modernc directly; a CGO_ENABLED=1 fused
build stays collision-prone until they adopt the fork too. Out of scope for
this repo; tracked as the cross-repo follow-up.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-03 14:22:50 -07:00
hanzo-dev dcd97b2552 chore(deps): bump hanzoai/ai → v1.796.2 (durable tasks ingest + routed /v1/docs/ingest + code-aware splitter + brand-neutral per-org store); tasks → v1.43.0 2026-07-03 14:12:56 -07:00
hanzo-dev 1c2af2d697 Merge CMS-on-Framework keystone (feat/cms-framework-module, RED-PASSED 1eea6105)
First business app lane native on the Hanzo Framework DocType engine:
generic module-install path (/v1/framework/modules[/:module[/install]]) +
the CMS content model as fixtures (Page/Post/Article/Media/Navigation/Author,
module cms). Additive — no change to the proven /v1/framework/* isolation.
RED verdict: SHIP (0 crit/high/med).
2026-07-03 13:16:00 -07:00
hanzo-dev 350bbdacec chore(deps): bump hanzoai/ai → v1.796.1 (unified ingest routed + code-aware splitter + brand-neutral per-org docs store) 2026-07-03 12:58:38 -07:00
8e4488153c feat(security): native /v1/security/* — dependency-free secrets scanner (#94)
The first Semgrep-class capability shipped natively in the cloud binary,
per hanzoai/security POSTURE.md's plan of record. One subsystem, the
established clients/ pattern (self-registering Mount, org-scoped store
under DataDir, audit + metering wired), zero external tools.

- engine.go — the reusable detection core: pure (path,content)→findings,
  no I/O. Pattern rules (AWS/GCP/GitHub/Stripe/Slack/npm keys, private-key
  blocks, JWTs) + a Shannon-entropy-gated generic-assignment rule so
  `secret = "changeme"` is not flagged but a real high-entropy token is.
  THE INVARIANT: a finding never carries the raw secret — only a masked
  preview (4+4 ends, middle starred; short secrets fully starred) and the
  SHA-256 fingerprint (dedupe + rotation tracking). Persisting plaintext
  would make the findings DB the very thing we scan to prevent.
- store.go — per-tenant SQLite ({DataDir}/security.db), scans + findings
  tables, org column is the isolation boundary on every query; SaveScan is
  one transaction so a scan is never half-written. Mirrors clients/git.
- security.go — mounts /v1/security/{health,rules,scans,scans/:id,
  findings,findings/:id}. submitScan runs the engine, persists redacted
  findings, meters one unit, emits a tamper-evident audit record (the
  tally, never the secrets). Registered cloud.RegisterWithShutdown(
  "security", 136, …) + one blank-import line in subsystems.

Tests (14, no skips, no fakes): engine_test proves each rule fires, the
entropy gate, line mapping, dedupe, severity ordering, and that no field
ever echoes the raw secret; security_test proves the HTTP surface,
cross-tenant isolation (evil sees 0 of acme's scans/findings, 404 on id),
the no-principal 403, the severity filter, and that a clean scan persists
a real zero-findings record. go build ./... + go vet + -race all clean.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
2026-07-03 12:50:51 -07:00
hanzo-dev 1eea6105e9 feat(framework+cms): generic app-lane module fixtures + CMS content model
Framework: a generic, DRY module-install path so an app lane (CMS/ERP/Helpdesk)
declares its DocTypes as fixtures (framework.RegisterModule, sibling to
RegisterHook) and installs them per-org via the engine's own gate:
  GET  /v1/framework/modules                list registered lanes
  GET  /v1/framework/modules/:module        lane fixtures + which are installed in-org
  POST /v1/framework/modules/:module/install  ensure fixtures exist (managerOnly, idempotent)
'modules' reserved so the static routes are never shadowed by a document route.

CMS (clients/cms): the first lane — the content model as fixtures only, NO HTTP
surface of its own. Page/Post/Article (slug-named, status Draft/Published,
author Link), Media (Attach-backed DAM), Navigation (JSON menu), Author. A CMS
collection IS a framework DocType (module 'cms'); content IS documents;
publishing IS a status field. Registered at init; installed per-org.

Secure by default: install is managerOnly (owner seeded trust-on-first-use),
create-if-absent (never clobbers a customised DocType), stamps the module tag,
and every op stays per-org via principal.Tenant.

Tests: install/idempotency/unknown-404/tenant-isolation/forged-principal-403/
non-owner-403/module-tag; CMS fixture validity + content-model spec + a full
HTTP install->create Author->create Page(link)->publish->filter round-trip.
2026-07-03 12:44:06 -07:00
hanzo-dev 4f9fb6f97b fix(framework): RED MEDIUM — decode URL-encoded path params (space-named DocTypes/docs/roles)
The router (zip over fasthttp) runs with Fiber's default UnescapePath:false, so
c.Param() returns path segments verbatim. A DocType/document/role name that is
legal per docTypeNameRe but contains a space ('Sales Invoice', 'System Manager')
arrives percent-encoded ('%20') and never matched its stored value: GET/PUT/
DELETE /v1/framework/:doctype/:name, submit/cancel, and revokeRole (:user/:role)
all 404'd, while create+list (no name in the path) worked — records could be made
yet be unreachable, and a granted System Manager could not be revoked.

Fix scoped to the ONE seam: pathParam() percent-decodes every framework path
param (getDocType/replaceDocType/deleteDocType, access(:doctype), docName,
revokeRole). NOT a global fiber.Config UnescapePath flip — that would change
segment splitting on the KMS secret-path, model-catalog, git and s3 wildcards
(c.Params("*")) that legitimately carry encoded slashes; the framework-local
decode is orthogonal and zero-blast-radius. Malformed escapes fall through to an
honest 404, never a panic.

Unblocks space-named DocTypes for the CMS/ERP/Help app lanes. Tests: red→green
round-trip (create -> GET/PUT/submit/cancel/DELETE by name) + space-named role
revoke; full framework suite green under -race.
2026-07-03 12:27:31 -07:00
84d4a77872 feat(provisioning): docdb dedicated engine = Hanzo Base, not MongoDB/FerretDB (#93)
Reconciles task #52 (eliminate Mongo) onto main's dedicated-per-org instance
model. The managed "document database" (docdb) is now a dedicated per-org Hanzo
Base instance — JSON document collections on per-tenant SQLite with native
realtime (SSE /v1/realtime), IAM-native — NOT a per-org FerretDB/Mongo instance.

- dedicated.go: docdb engine swapped ghcr.io/hanzoai/docdb:0.1.0 (mongodb://,:27017,
  POSTGRES_*) -> ghcr.io/hanzoai/base (http://.../v1, :8090, /data), dsType "base".
  New engine fields: dataMount (emits spec.volumeMounts so the data PVC actually
  mounts — the operator does NOT auto-mount) and iamAuth (IAM-native: no per-
  resource password generated/sealed/returned; admin Secret carries IAM_URL/
  KMS_URL/IAM_CLIENT_* from the cloud binary's own IAM identity). baseInstanceEnv
  helper. createDedicated honors iamAuth (no pw path). datastoreCR emits
  volumeMounts. Runs on the operator's GENERIC Datastore controller — spec.type is
  free-form, image/ports/volumeMounts drive the StatefulSet verbatim, NO operator
  Rust change (verified). datastore engine stays ClickHouse (not Mongo).
- provisioning.go: header + sanitizeIdent comments de-Mongo'd.
- go.mod: mongo-driver demoted direct -> // indirect (zero Go imports of
  go.mongodb.org remain; it survives only as a transitive requirement).
- test: TestDedicated_DocdbIsBase asserts the docdb CR is the base image on :8090
  with /data mounted, connString http://.../v1 (no mongodb://), no credential
  (IAM-native), IAM env in the admin Secret. PASS.

Audit (unchanged): zero customer docdb data, so the swap is clean.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 11:56:46 -07:00
hanzo-dev 564338b8a7 Merge remote-tracking branch 'origin/main' into feat/framework-doctype-engine 2026-07-03 11:20:55 -07:00
hanzo-devandGitHub c1f8e08457 fix(enablement): RED MEDIUM — scope self-opt-in/view to the VALIDATED tenant (#92)
Red found the self-service enablement write path (POST /v1/enablement/optin|optout)
+ the view keyed on raw c.Org() instead of principal.Tenant(c). On the bearer-less
direct-to-pod path SanitizeIdentity restores a client X-Org-Id with no validated
principal, so an off-gateway caller could opt an org it does not own into/out of a
beta (cross-tenant enablement write; bounded — betaOrgs membership of already-beta
items only, no money/data/global-state, not reachable through the gateway).

Fix (DRY — pricing already imports principal, the READ catalog gate already uses it):
- enablementOpt: resolve subject via principal.Tenant(c), 401 on !ok (was raw c.Org()).
- enablementView: resolve via the existing trustedOrg(c) (validated-principal gate).
- Corrected the docstrings (subject is the VALIDATED tenant, not 'never client-supplied').

Red's two PoC attack tests (enablement_attack_test.go) now GREEN; full enablement
suite unchanged + green + -race. Closes the one MEDIUM from Red's cockpit review.
2026-07-03 10:10:42 -07:00
hanzo-dev 85a9e3091d fix(admin): decode commerce transactions {count,transactions} wrapper — analytics ledger was silently empty
Live-verified: /v1/billing/transactions returns {count, transactions:[...]}, not a bare array.
My client decoded a bare [] (test fake also returned bare — mock hid the bug), so the analytics
retention/churn/active/usage ledger read got ZERO rows despite real usage (maxpower: 268 txns).
Now decodes the wrapped shape (bare-array fallback for robustness); test fake mirrors the live shape.
2026-07-03 09:55:46 -07:00
hanzo-devandGitHub 5cae3b9a7b feat(platform): KMS-sealed secret env vars (close the 501) (#89)
User app secret env is no longer refused — it is sealed into cloud's embedded
KMS and wired to the pod via an operator-materialized k8s Secret, never
plaintext, never logged.

The path a secret takes (secrets.go):
  1. SEAL   — createApp / PUT .../env seal every secret:true value into deps.KMS
              at a per-tenant/app coordinate (platform/<tenant-ns>/<app>/<KEY>);
              the persisted env_json value is blanked. Fails CLOSED if KMS is
              unavailable — a plaintext secret never lands in the DB as a fallback.
  2. DECLARE — on deploy (applyLive, the ONE shared choke point) cloud writes a
              canonical KMSSecret CR (secrets.lux.network/v1alpha1) into
              tenant-<org> declaring a managed Secret <app>-env sourced from that
              KMS scope. Best-effort: a missing CRD/RBAC degrades to an honest
              'pending' status, never a failed deploy.
  3. MOUNT  — the Service CR renders each secret env as valueFrom.secretKeyRef →
              that Secret (optional:true so the pod boots pre-sync); the hanzo
              operator (which already supports secretKeyRef) mounts it into the
              Deployment env. cloud is never in the plaintext path at runtime.

Also: PUT /v1/platform/projects/:p/apps/:a/env to set/rotate env post-create;
honest secretSync status (pending|syncing|ready|failed) from the KMSSecret CR
conditions on the app view; KMSSecret teardown on app/project delete.

Tests: seal blanks+seals+fails-closed; injective KMS refs (no cross-tenant
collision); canonical KMSSecret CR shape; apply/patch/delete; sync-status
mapping; and an end-to-end deploy asserting the Service CR carries secretKeyRef
(never plaintext) and the KMSSecret CR is authored. go build ./...=0, vet clean.
2026-07-03 09:45:30 -07:00
hanzo-dev 9fa89757b4 feat(admin): operator cockpit — customers/revenue/analytics + enablement registry
/v1/admin/* (global-admin gated, reuse s.guard→c.IsAdmin owner==AdminOrg):
- GET  /v1/admin/customers          fleet customer list (balance/spend/plan/status), concurrent enrichment
- GET  /v1/admin/customers/:org     detail (balance/usage/keys-presence/txns/users) — no card data, no key values
- POST /v1/admin/customers/:org/credit      real commerce deposit, audited before/after
- POST /v1/admin/customers/:org/{suspend,reactivate}  IAM isForbidden flip (login+token enforced), audited
- GET  /v1/admin/revenue            fleet revenue aggregate + per-customer table + ARPU + real spend trend
- GET  /v1/admin/analytics          native SaaS analytics: cohort retention, growth, churn, DAU/WAU/MAU,
                                     revenue/ARPU, usage — real from IAM createdTime + commerce ledger,
                                     honest-empty + computed[] transparency map (no fabricated curves)

Enablement registry #30/#31 (extends the ONE pricing catalog overlay, DRY):
- Overlay gains explicit Beta flag → tri-state off|beta|ga; off is an ABSOLUTE kill switch
  (visibleTo ignores betaOrgs when !beta). Additive migration + backfill (no regression).
- GET/PUT /v1/admin/enablement       global-admin: list + set state (+grant orgs)
- GET  /v1/enablement                 caller effective view + available betas
- POST /v1/enablement/{optin,optout}  self-service, subject = SANITIZED caller org, refuses non-beta
  (cannot bypass off, cannot target another org, cannot change global state)

Clients: commerce deposit/transactions/subscriptionSummary; iam getUserRaw/updateUserRaw (caller-cred replay).
Tests: analytics math (retention/churn/growth/spend), cockpit handlers (credit deposit+audit, suspend+audit,
no-secret-leak, revenue), enablement (tri-state, opt-in-refuses-non-beta, admin-only, full flow, caller-scope).
All green + -race clean; cmd/cloud builds.
2026-07-03 09:40:29 -07:00
4db0666537 feat(provisioning): TRUE multitenancy — dedicated per-tenant DB instances (#88)
datastore (ClickHouse) + docdb (FerretDB) were honest-gated (unavailableKinds)
because a SHARED backend can't scope a per-tenant role. Replace the gate with a
DEDICATED-instance strategy: each create launches the org's OWN instance via an
operator Datastore CR + admin Secret in tenant-<org> (derived from the VALIDATED
org, never a request field). Isolation is BY INSTANCE — a cross-tenant grant is
impossible, there being one tenant on the instance — which un-gates both kinds.

- dedicated.go: engine table (image/ports/admin-env/DSN per kind), instanceName
  (<prefix>-<orgHash10>-<name>, DNS-1123), the k8s orchestrator (ensure tenant
  ns + RBAC wait, apply/observe/delete the Datastore CR + admin Secret + reap the
  retained PVC) behind an interface a fake stands in for, createDedicated,
  reconcileDedicated (provisioning->ready off the operator's status.phase), and
  dropDedicated.
- Billing (first-class): a provision debit carrying the size dimension
  (Model=<kind>:<size>) lands on the CALLER's org via the ONE commerce meter, and
  a recurring GB-day footprint sweep charges every running instance's own org —
  the reserved hook, now unblocked by the instance's declared size. Drop removes
  the row, stopping the meter, and reaps the PVC so no storage leaks.
- unavailableKinds now empty (mechanism kept); shared datastore/docdb
  provisioners deleted (one way only); the 5 shared kinds untouched.
- Datastore CR (not DocDB) is used because only its controller writes
  status.phase, the readiness signal; type forced per engine.

Tests: hermetic dedicated suite (fake orch + mock commerce) proves CR/Secret
shape, two-org isolation, ready reconcile, drop+PVC reap, and per-org billing
attribution; a build-tagged livecluster test proves the whole path against the
real operator. go build ./cmd/cloud + go test ./clients/provisioning/... green.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 09:37:36 -07:00
hanzo-devandGitHub 92659f9616 feat(console): port waitlist/embed-status/topup routes to /v1/console/* (task #41) (#87)
Completes the console subsystem's standalone-route port for the True 1-binary
FE. The three remaining console2 Next server routes that do REAL server work
(not vanishing BFF proxies) now terminate natively in the unified binary, so
console2 can drop them from its static export:

  POST /v1/console/waitlist       waitlist.go — session-gated join to the Base
                                  waitlist plugin; the recorded email is BOUND to
                                  the gateway-verified X-User-Email (a signed-in
                                  user can't enroll a third party), honest 501
                                  when WAITLIST_URL is unset.
  GET  /v1/console/embed-status   embed.go — server-authoritative entitlement
                                  (owning brand org / global admin only) + a
                                  time-boxed reachability probe. SSRF-free: the
                                  target is <app>.<brand-domain> for the FIXED
                                  deployment brand (deps.Brand) — no client host
                                  in the target at all.
  POST /v1/console/topup/wallet   topup.go — verify an HUSD transfer on-chain
                                  (plain eth JSON-RPC, no EVM dep) and credit the
                                  VALIDATED caller's own org for the ON-CHAIN
                                  amount via the S2S commerce billing API. IDOR-
                                  safe (ignores any client userId); honest 501
                                  greenfield gate until HUSD is deployed.

All three resolve the caller from the VALIDATED principal only (same trust
boundary as keys/onboard); a forged X-User-Id/X-Org-Id is refused. docs is a
pure host->URL redirect with no server work, so it stays client-side in console2
(no handler here). Registered in the ONE routes() place; full unit coverage
(fake IAM/waitlist/RPC/commerce), go build ./... clean, binary boot-proven to
serve the console SPA at / with every /v1/console/* route resolving (403/501/503,
never 404).
2026-07-03 09:30:26 -07:00
zandGitHub f0152aecbb Merge pull request #86 from hanzoai/chore/zip-v1.2.1-431
chore(deps): zip v1.2.1 — activate the api.hanzo.ai 431 fix
2026-07-03 03:10:50 -07:00
hanzo-dev 2d9ffd3b7c chore(deps): zip v1.2.0->v1.2.1 — HTTP transport honors ReadBufferSize (activates the 431 fix)
v1.786.33 set zip.Config.ReadBufferSize=32768 (GATEWAY_READ_BUFFER_SIZE) but
zip v1.2.0's HTTP transport built a bare fasthttp.Server and dropped it — the
edge still 431'd at 4 KiB. zip v1.2.1 propagates the App Config onto the
transport's fasthttp.Server, so the 32 KiB header ceiling now takes effect on
cloud:8000 (the api.hanzo.ai/v1/* backend).
2026-07-03 03:10:42 -07:00
3eff9b9521 test(crm): lock /v1/crm/summary live-count immediacy (no lagging rollup) (#85)
The console E2E saw /v1/crm/summary miss a just-created record. Root cause was a
stale/eventually-consistent read; the current handler already counts LIVE
(s.Counts -> SELECT COUNT(*) per table on the same store the writes hit), so a
create/delete is reflected with ZERO lag — verified live (create company ->
summary companies +1 immediately).

Add TestSummaryReflectsCreateImmediately: create -> Counts shows +1, delete ->
Counts shows -1, all in one synchronous flow. This guards against any regression
to a materialized/async rollup. No production code change needed — the fix is the
regression lock.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 03:10:29 -07:00
46c3f7fc13 fix(analytics): honest 503 on ClickHouse timeout; fix(provisioning): honest-gate datastore+docdb (no cross-tenant role) (#84)
Gap 2 (analytics 502 on ClickHouse i/o timeout): /v1/analytics/{overview,timeseries,top}
returned a raw 502 when a DatastoreQuery hit a connectivity failure even though
requireDatastore()'s not-connected path already 503s. warehouseErr() now maps a
transport/connectivity error -> 503 'warehouse unavailable' (retryable); a REACHABLE
warehouse that rejected the query (bad SQL/protocol) stays 502. Table-driven test.

Gap 3 (docdb/datastore provisioning) — SAFETY REWORK (replaces the earlier
readWriteAnyDatabase change, which was cluster-wide = a cross-tenant hole):
- datastore + docdb are honest-GATED (unavailableKinds -> 503 'not yet available',
  refused BEFORE billing or any backend write) because their backends cannot mint a
  per-tenant-SAFE credential:
    * datastore (ClickHouse): no grant-capable per-tenant admin (GRANT ALL -> Code 497);
      unblocking is backend-side (StatefulSet grant-capable admin).
    * docdb (FerretDB/DocumentDB): engine implements ONLY cluster-wide roles
      (clusterAdmin -> Postgres SUPERUSER, readWriteAnyDatabase) — no per-db role.
- docdbProvisioner.Create keeps requesting the CORRECT per-db 'readWrite' role (the
  tenant-safe target); when FerretDB supports it, drop the gate and it works as-is.
- Tests: gated kinds -> 503 with the provisioner never run; the 5 guaranteed kinds
  (sql/vector/kv/search/s3) are asserted NOT gated.

Bar met: 5/7 data kinds fully work; datastore+docdb show an honest 'coming soon',
never a security hole.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-03 03:10:25 -07:00
zandGitHub a033ab2d14 Merge pull request #83 from hanzoai/fix/edge-read-buffer-431
fix(edge): raise fasthttp header buffer to 32 KiB (fix api.hanzo.ai 431 on multi-domain SSO)
2026-07-03 02:43:20 -07:00
hanzo-dev 6d4f08b29e fix(edge): raise fasthttp header buffer to 32 KiB so multi-domain SSO sessions don't 431
The public HTTP edge (zip/fiber) uses fasthttp's default 4 KiB per-conn
read buffer, which caps total request-header size and returns 431 (Request
Header Fields Too Large) above it. Once an admin-guard Domain=.hanzo.ai SSO
cookie is set on every subdomain, a browser's request headers cross ~4 KiB
and every request to api.hanzo.ai/v1/* (gateway -> cloud passthrough) 431s.

Raise the edge ceiling to a sane 32 KiB (nginx large_client_header_buffers
parity) via zip.Config.ReadBufferSize, env GATEWAY_READ_BUFFER_SIZE (shared
with the gateway edge so both trust boundaries agree on ONE value; tunable
down if the per-conn memory budget demands). Internal zip services keep the
4 KiB framework default — only the browser-facing edge opts up.

Repro (pre-fix): POST cloud:8000/v1/agents with a 9 KiB Cookie -> 431
Server: fasthttp. Post-fix: same request -> 403 (auth), no 431.
2026-07-03 02:42:54 -07:00
zandGitHub 6520338886 Merge pull request #82 from hanzoai/fix/agents-id-name-resolve
fix(agents): make a created agent gettable AND runnable by the returned id
2026-07-03 01:53:45 -07:00
hanzo-dev 66707fbed5 fix(agents): resolve /v1/agents/:ref by id OR name so created agents are runnable
create and list return an agent's public id (agent_<hex>), but get/run/update/
delete/runs resolved the URL path segment ONLY against the name column — so a
client that used the id create returned got 404 "agent not found". A created
agent was listed but neither gettable nor runnable by the identifier the API
handed back.

One-way fix: Store.Resolve(org, ref) matches either the public id or the
org-unique name (id wins on the astronomically-unlikely in-org collision),
org-scoped fail-closed so a cross-tenant ref is 404, never a leak. Every
path-addressed handler (get/update/delete/run/runs) resolves through it and keys
every downstream store op on the resolved a.Name. Route param :name -> :ref to
say what it accepts. The run path's validated-principal gate and single
product=agent debit are unchanged.

Tests (go test -race): Resolve by id and by name return the SAME agent; full
create -> get-by-returned-id -> run-by-returned-id all 200 the same agent with
real output; cross-org ref denied 404; a run addressed by the returned id meters
exactly once (product=agent).
2026-07-03 01:52:54 -07:00
zandGitHub 6562cfb49e Merge pull request #81 from hanzoai/feat/standalone-embed-real-console
feat(webui): standalone binary embeds the REAL console (build:embed pipeline)
2026-07-03 01:20:34 -07:00
hanzo-dev 5a4f199ff8 feat(webui): make the standalone binary embed the REAL console (build:embed)
The 1-binary console (HIP-0106) shipped as a 3-file STUB: nothing ran
console2's static export before `go build`/the image build, so `//go:embed
all:webui/dist` baked only the fallback shell.

- `make webui` (new): runs hanzoai/console2 `npm run build:embed` and overlays
  the static export into webui/dist so a plain `go build` embeds the full
  @hanzo/gui console. `make build-standalone` = webui → build. CONSOLE2_DIR
  points at a console2 checkout (default ../console2).
- Dockerfile console stage + webui.go + the stub shell: docs corrected — the
  pipeline is `build:embed` (a static export), not `next build`; the export now
  prerenders clean (console2 build-embed.mjs neutralizes the root layout's
  request-time headers() read), so the image embeds the real console instead of
  silently degrading to the shell. Bumped the export heap to 8192 for headroom.

Verified: build:embed → webui/dist (index.html 368 KB, /_next/static assets) →
CGO_ENABLED=0 go build ./cmd/cloud → the running binary serves the real console
at / (200, references /_next/, not the stub), the SPA shell for deep links
(/orgs), fingerprinted assets immutable-cached, and the /v1 API on the SAME
origin ({"service":"base","status":"ok"}); unmatched /v1/* is a real 404, not
HTML. webui_test.go (7 tests) green against the real bundle.
2026-07-03 01:16:17 -07:00
hanzo-devandGitHub d7c55382ea chore(deps): bump ai v1.790.4→v1.790.5 — provider-admin API + path-normalization hardening (#80) 2026-07-03 01:08:29 -07:00
hanzo-devandGitHub 3792398b0e chore(deps): bump hanzoai/ai v1.790.3→v1.790.4 — text-to-video (/v1/videos/generations) + canonical /v1/crawl (both red-cleared) (#79) 2026-07-03 00:44:54 -07:00
hanzo-dev 1937995f6b feat(visor): /v1/compute/{regions,sizes} — compute catalog on the cloud path (org-gated DRY passthrough; closes console compute-catalog 404, drops /vm proxy need) 2026-07-03 00:31:43 -07:00
hanzo-dev 5307fb4a7d Merge remote-tracking branch 'origin/main' into feat/framework-doctype-engine 2026-07-03 00:21:50 -07:00
hanzo-dev a9669e8fd0 fix(framework): atomic owner-seed — 'exactly one' System Manager under concurrency (Red LOW)
Red measured 3-6 System Managers seeded when concurrent role-less members first
administered a fresh org: managerOnly did a check-then-insert (OrgHasRoles then
AssignRole) with a TOCTOU window. Fix: store.SeedOwnerIfUnowned is a SINGLE
conditional INSERT ... SELECT ... WHERE NOT EXISTS(SELECT 1 FROM fw_roles WHERE
org=?), so the unowned-check and the insert are one atomic statement — exactly
one concurrent first-caller's row lands. RowsAffected==1 => this caller is the
seeded owner; ==0 => re-resolve (a concurrent grant may have made them a
manager) else 403. No UNIQUE index (multiple SMs are legit later via AssignRole;
only the AUTO first-seed must be singular). Removed the now-dead OrgHasRoles.

Test: TestAtomicOwnerSeed — 8 concurrent role-less first-callers → exactly 1
seeded winner + exactly 1 System Manager row. 22 tests total, race-clean.
2026-07-03 00:21:42 -07:00
hanzo-devandGitHub 988a76cdbc chore(deps): bump hanzoai/ai v1.790.2→v1.790.3 — Great-Audit security fixes (F1 unauth-admin RAG/scrape, F-sk zero-billing, F4 401s) (#78) 2026-07-03 00:06:18 -07:00
hanzo-devandGitHub 711bf591f0 fix(security): gate /v1/websearch/search fail-closed (Great-Audit F2) (#77)
searchGuard treated the searxng X-API-Key as OPTIONAL — a MISSING key passed —
so GET /v1/websearch/search was an open proxy to the Hanzo-operated metasearch
instance (unauthenticated request-forgery + cost surface). Its scrape sibling
(scrapeHandler) already fails closed; this brings search to parity:
  - key unset         → 503 (surface not configured, never open-to-all)
  - X-API-Key missing → 401 (constant-time compare of "" vs want fails)
  - X-API-Key mismatch→ 401

Safe for the real caller: the LibreChat searxng client sends the configured
searxngApiKey (universe chat configmap wires searxngApiKey=${WEBSEARCH_API_KEY})
as X-API-Key, so only anonymous callers are turned away.

Tests: TestSearchMissingKeyRejected (was ...Allowed) → 401; new
TestSearchUnsetKeyFailsClosed → 503; TestSearchProxyRewritesToSearchPath and
TestMountRoutesThroughRouter now present the key. go build/vet/test green.
2026-07-03 00:04:28 -07:00
hanzo-dev 32f31416be Merge remote-tracking branch 'origin/main' into feat/framework-doctype-engine 2026-07-03 00:03:02 -07:00
hanzo-dev 2207cfeb70 fix(framework): secure-by-default perms + Single submit-immutability (Red LOW-1/LOW-2)
LOW-1 — Single submit-immutability: updateDocument/createDocument for a Single
now route through writeSingle, which enforces the SAME draft-only guard as the
non-Single path (a submitted/cancelled Single → 409, not a silent mutation) and
preserves a redacted Password across an unchanged update.

LOW-2 — secure-by-default permissions (no open-to-all footgun):
- permission.can() is now DEFAULT-CLOSED: removed the 'empty perms => open to
  every org member' branch. A permless doctype is manager-only; a role-less
  member is denied.
- DocType.normalize() seeds a System Manager perm at define time, so a stored
  doctype is never silently permless (explicit in UI + audit).
- Owner seeding moved from resolveAccess (any member is SM until a role exists)
  to managerOnly as trust-on-first-use: the FIRST validated principal to
  administer an org with no roles becomes its persisted System Manager (the
  owner) — exactly one member, deterministically, never cross-tenant.

Tests: +2 (TestSingleSubmitImmutability, TestPermlessDefaultClosed); 21 total
race-clean. go build ./... CGO=1 & =0 green, vet + gofmt clean. Fixed binary
boot-verified (framework health 200, gate 403, forge 403).
2026-07-02 23:49:37 -07:00
zeekayandhanzo-dev 0dc29a7894 fix(deps): luxfi/age@v1.5.0 go.sum = canonical sumdb hash (fixes container SECURITY ERROR)
The prior fix re-fetched luxfi/age with checksum-checking off, which recorded the
DIRECT-vcs hash. luxfi/age@v1.5.0 was force-re-tagged, so the direct tree hash
differs from the immutable proxy zip hash — the container build (GOPROXY=proxy +
GOSUMDB=sum.golang.org, GOPRIVATE dropped for luxfi/* on purpose) verifies against
the sumdb and hit "checksum mismatch / SECURITY ERROR" on `go mod download`.
Replaced the h1: zip hash with the canonical value from
sum.golang.org/lookup/github.com/luxfi/age@v1.5.0 (the /go.mod hash already
matched). Now go.sum == what the proxy+sumdb serve → container verification passes.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-02 23:38:46 -07:00
zeekayandhanzo-dev 3a51c88fe6 fix(docker): console2 build:embed failure degrades to fallback shell (non-fatal)
The console-embed stage's contract is "a missing static target is a degrade, not
an error" — but the guard only handled the target being ABSENT. When console2
exposes build:embed AND it CRASHES (currently: /signin Server-Components
prerender error kills `next build`), the `&&` chain failed the whole cloud image,
so a frontend prerender bug took down the entire Go backend build (release runs
for projectsvc S3 fix + kms refactors all failed here, not on Go).

Complete the stated contract: wrap build:embed so a build FAILURE also degrades to
the committed fallback shell (/out stays empty → Go embeds webui/dist/index.html).
The standalone console2 Deployment is the primary console; this embed is a
same-origin convenience and must never gate the backend image.

(console2 /signin static-export prerender crash tracked separately for the
console track — this makes cloud CI robust to it either way.)

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-02 23:24:43 -07:00
zeekayandhanzo-dev cca56eb945 fix(deps): unblock cloud build — versioned replace for phantom go-sqlite3 + luxfi/age checksum
Two dep-rot issues blocking the cloud (Go backend) build:
1. A transitive dep requires the non-existent mattn/go-sqlite3 v2.0.3+incompatible.
   The unversioned replace didn't stop Go reading v2.0.3's go.mod during graph
   load. Fixed with a VERSIONED replace (v2.0.3+incompatible => v1.14.16, the last
   real go-sqlite3, drop-in package sqlite3). cloud's primary sqlite is
   modernc.org/sqlite (pure-Go); hanzoai/sqlite (encrypted, package `sqlite`) is a
   separate driver, adopting it is a real migration not this phantom fix.
2. luxfi/age@v1.5.0 go.sum checksum mismatch → removed stale lines + re-fetched.

go build ./internal/org/ (the sqlite consumer) now clean; module graph resolves.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-02 23:16:17 -07:00
hanzo-dev d14dfc3a3b feat(framework): native-Go DocType engine — the foundation that retires Frappe
The Hanzo Framework: Frappe's DocType/metadata core rebuilt native in Go on
Base/SQLite, mounted at /v1/framework/* (subsystem order 129). ONE engine +
ONE generic UI renders every business app — CMS content-types, ERPNext
DocTypes, Helpdesk all become just DocTypes on this engine. No Frappe/Python
runtime dependency; the engine is pure Go.

- DocType registry: define/list/get/replace/delete metadata per-org
- Generic metadata-driven document CRUD with ?filters=/fields=/order_by=/limit=
- Fieldtypes: Data/Int/Float/Currency/Check/Date/Datetime/Text/SmallText/
  LongText/Select/Link/Table/Attach/JSON/Password (all validated)
- Naming: hash / field: / prompt / series patterns (INV-.YYYY.-.#####)
- Link relations (in-org ref check + fetch_from), Table child rows
- docstatus 0/1/2 with submit/cancel for submittable doctypes
- Per-org permissions (DocType perms by role) + per-org role store
- Go lifecycle hook interface (before_insert/before_save/after_save/
  on_submit/on_cancel/on_trash) — gpython/goja runner is a later add to the
  SAME interface
- Password fields: argon2id hash on write, redact on read (fail-secure)

Security: org derived ONCE via clients/principal.Tenant (validated principal
only; forged X-Org-Id refused 403). Every table + query is org-scoped. 19
tests (race-clean) prove cross-org isolation, forged-principal refusal,
permission enforcement, field-type validation, and the docstatus lifecycle.
Boot-verified locally (health 200, doctypes 403, forge refused).
2026-07-02 23:16:10 -07:00
hanzo-dev efdbd118e3 refactor(kms): filenames match packages — kms/kms.go + kmssvc/kmssvc.go 2026-07-02 23:03:41 -07:00
hanzo-dev 16df83233b refactor(kms): drop the kmsembed compound — core is clients/kms, HTTP-mount subsystem is clients/kmssvc
The embedded luxfi/kms core (cloud/types-only leaf, built by build.go before the
app exists to break the import cycle) is now just 'kms'; the Fiber /v1/kms/* mount
subsystem (imports cloud) is 'kmssvc' (its existing internal name). One clean name
each, no unnecessary compound. build+vet+tests green.
2026-07-02 22:54:02 -07:00
zeekayandhanzo-dev da078d967c fix(projectsvc): SeaweedFS-compatible public-read bucket policy
publicReadPolicy used Principal {"AWS":["*"]} + array Resource, which
SeaweedFS's S3 policy engine rejects with 'Policy has invalid resource' —
aborting ensureBucket (SetBucketPolicy) BEFORE any files upload, so every
projectsvc deploy failed ('object storage'/'invalid resource') and no site
was ever served. Use scalar Principal "*" + scalar Resource, which SeaweedFS
accepts and is equally valid on AWS S3 / MinIO. Verified: mc anonymous
set-json with this exact shape succeeds against the s3.hanzo.ai SeaweedFS
gateway; a site uploaded to the now-public hanzo-sites bucket serves 200 at
https://s3.hanzo.ai/hanzo-sites/<org>/<slug>/index.html.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-02 22:52:59 -07:00
hanzo-devandGitHub bca1e24a11 fix(websearch): decode Crawl4AI object-shaped markdown (scrape returned empty) (#72)
Found by testing the ACTUALLY-deployed hanzoai/crawl:0.0.1 (= Crawl4AI
0.8.6) against clients/websearch's crawl adapter: 0.8.x/0.9.x return the
/crawl result's `markdown` as an OBJECT
{raw_markdown, fit_markdown, markdown_with_citations, ...}, and signal the
batch with a boolean `success` (no `status`). crawlResult.Markdown was
typed `string`, so json.Decode errored on the object form → crawl()
returned an error → EVERY scrape returned {success:false} with empty
content. hanzo.chat Web Search's scrape half was therefore dead even once
crawl is running.

Fix: markdownField.UnmarshalJSON accepts either a bare string OR the
object (preferring the cleaned fit_markdown, raw_markdown fallback); the
crawlResponse envelope now also accepts boolean `success` alongside the
legacy `status`. Neither envelope field is required — Results[0].Success
is authoritative.

Tests (real 0.8.6 response shape):
  TestScrapeHandlesCrawl4AIObjectMarkdown — object markdown + bool success
    → success:true, returns fit_markdown (was: {success:false}).
  TestMarkdownFieldAcceptsBareString — bare-string form still works.
  All 12 clients/websearch tests pass; go build + go vet clean.

Contract verified live: crawl4ai 0.8.6 POST /crawl {urls:[...]} returns
synchronously (no task_id polling) with url/markdown/success/metadata —
matches the adapter otherwise.
2026-07-02 22:30:15 -07:00
zandGitHub bf77781a6d Merge pull request #76 from hanzoai/feat/paas-domains
feat(platform): customer domains — self-serve subtree hosts + verified BYO custom domains
2026-07-02 22:01:40 -07:00
hanzo-devandGitHub 8422ee1a88 feat(platform): live deployment logs — stream real build + app pod logs (#75)
deploymentLogs returned only the recorded timeline + a Job reference, ending
with a '(live BuildKit Job logs stream in phase 2)' placeholder. This closes
that phase-2 gap: it streams the ACTUAL pod logs from the cluster — the BuildKit
Job's pod while a git build runs, and the running app's pod once deployed — so
the console's per-deployment Logs pane shows real output, operator-consistent.

- logs.go: buildLogs (job-name=<jobName> pod in the build ns), appLogs
  (app.kubernetes.io/instance=<slug> pod in tenant-<org>), one podLogsBySelector
  path (newest pod, tail-bounded 400 lines, byte-capped 256 KiB keeping the tail,
  8s time-boxed). Every read is org-scoped and time-boxed.
- k8s.go: add a typed kubernetes.Interface clientset (from the SAME rest.Config)
  held ONLY for the Pods().GetLogs subresource the dynamic client cannot express;
  nil-safe — a construct failure leaves logs degrading to the timeline and never
  disables the CR control plane (all on dyn).
- deploy.go: deploymentLogs now appends real build + app logs and stamps a
   (build|app|none) so the console can label the pane. HONEST DEGRADE:
  an unreachable cluster / absent pod yields the recorded timeline + a stated
  'not available' note — source stays reflecting real streamed content, never a
  fabrication.
- 8 tests over a fake typed clientset: newest-pod selection, tenant-namespace
  scoping (acme never reads victim's pod), no-pod/no-clientset honest degrade,
  and the handler surfacing live build logs (source=build) vs degrading
  (source=none) — asserting the phase-2 placeholder is gone.
2026-07-02 21:52:39 -07:00
hanzo-devandGitHub 43f51cdb04 feat(console): native /v1/console/{keys,onboard} — port console2's standalone IAM server routes (#74)
The console can be a static export only once its two NON-proxy Next server
routes (app/keys, app/onboard) — which mint/revoke the user's hk- Cloud API
key and create the user's org as the confidential hanzo-console IAM client —
have a native home. Port them to a clients/console subsystem mounted at
/v1/console/* in the one binary (task #41, True 1-binary FE): the embedded SPA
calls /v1/console/* on its own origin, and the last stateful Node handlers go.

- clients/console/iam.go: confidential-client (client_secret_basic) IAM caller
  for mint/revoke/get the hk- key + create/read/update an org. Honest 501 when
  IAM_MINT_CLIENT_ID/SECRET are unset (mirrors identity.ts mintConfigured()).
- clients/console/console.go: /v1/console/{keys(GET/POST/DELETE),onboard(POST),
  health}. Every route requires a VALIDATED principal; the IAM id is DERIVED as
  <owner>/<name> from the gateway-minted X-User-Id/X-Org-Id, never a request
  value — a caller can only ever act on their OWN key/org (red-bar structural).
- clients/console/onboarding.go: faithful Go port of console2 onboarding.ts —
  pure slug + reserved-name policy (admin/built-in/app + hanzo/lux/zoo/pars).
- Registered as consolesvc (order 122) so /v1/consolesvc/health does not shadow
  the real fail-closed /v1/console/health probe.
- 16 tests: unauth 403 (forged X-Org-Id refused, IAM never touched), mint/get/
  revoke scoped to the derived id + show-once + no secret leak on GET, 501/502
  honesty, onboard first-run(create+move)/additional(create-only)/reserved 400/
  taken 409/personal auto-suffix, + pure-policy unit tests.
2026-07-02 21:52:11 -07:00
hanzo-dev bee976a64d feat(platform): customer domains — self-serve subtree hosts + verified BYO custom domains
Close the two PaaS domain gaps so a customer can put their app on their own
domain, operator-native, from the console.

- Seed a canonical default host <slug>.<org>.<sitesHost> on app create, so
  every app has a working HTTPS URL the moment it deploys (operator issues the
  cert). Never removable.
- New /v1/platform/.../domains surface (list/add/verify/remove). An org-subtree
  host is active immediately; a BYO custom host (yourco.com) is claimed PENDING
  and returns the exact DNS records to publish (TXT ownership token at
  _hanzo-challenge.<host> + CNAME to the app host).
- Verify resolves DNS: a matching TXT token proves control (DNS-01 model), then
  the host is rendered into the app's operator Service CR ingress via applyIngress
  (cert-manager TLS comes for free). Honest still-pending on not-yet, never fake.
- platform_domains table: host PRIMARY KEY = global uniqueness (one org per host,
  like site_hosts); pending→verified lifecycle. Cascade-deleted with app/project.
- validateOrgDomains extended: a non-subtree host renders ONLY when this org owns
  a VERIFIED claim; unverified/foreign/apex hosts still refused (RED hardening kept).
- ingressSpec extracted (one TLS shape shared by serviceCR + applyIngress);
  observeDomains surfaces operator status.endpoints/phase for honest live state.
- Tests: verified-custom accept + pending/foreign refuse; full add→verify→remove
  HTTP flow with fake DNS; global uniqueness (two orgs/two apps); apex refusal;
  default-host seeding; CR ingress render. go build + go test green.
2026-07-02 21:48:04 -07:00
hanzo-devandGitHub 8f858e0d0b chore(deps): bump hanzoai/ai v1.790.1→v1.790.2 — full DO model lineup + file-scoped RAG + SD3.5 image (atop diffusion) (#73) 2026-07-02 21:26:05 -07:00
hanzo-dev d0a1a507da fix(websearch): decode Crawl4AI object-shaped markdown (scrape returned empty)
Found by testing the ACTUALLY-deployed hanzoai/crawl:0.0.1 (= Crawl4AI
0.8.6) against clients/websearch's crawl adapter: 0.8.x/0.9.x return the
/crawl result's `markdown` as an OBJECT
{raw_markdown, fit_markdown, markdown_with_citations, ...}, and signal the
batch with a boolean `success` (no `status`). crawlResult.Markdown was
typed `string`, so json.Decode errored on the object form → crawl()
returned an error → EVERY scrape returned {success:false} with empty
content. hanzo.chat Web Search's scrape half was therefore dead even once
crawl is running.

Fix: markdownField.UnmarshalJSON accepts either a bare string OR the
object (preferring the cleaned fit_markdown, raw_markdown fallback); the
crawlResponse envelope now also accepts boolean `success` alongside the
legacy `status`. Neither envelope field is required — Results[0].Success
is authoritative.

Tests (real 0.8.6 response shape):
  TestScrapeHandlesCrawl4AIObjectMarkdown — object markdown + bool success
    → success:true, returns fit_markdown (was: {success:false}).
  TestMarkdownFieldAcceptsBareString — bare-string form still works.
  All 12 clients/websearch tests pass; go build + go vet clean.

Contract verified live: crawl4ai 0.8.6 POST /crawl {urls:[...]} returns
synchronously (no task_id polling) with url/markdown/success/metadata —
matches the adapter otherwise.
2026-07-02 21:21:25 -07:00
hanzo-devandGitHub 05d0fb5d11 fix(templates): resolve 38 broken screenshot preview URLs in catalog (#71)
Map catalog preview URLs to screenshots that actually exist in gallery.
All 69 templates now have resolvable preview images at gallery.hanzo.ai.
2026-07-02 21:17:21 -07:00
hanzo-dev 9708db5c45 feat(graph): chain-data cloud client — /v1/indexers + /v1/oracles
Front the Lux chain-data plane over HTTP so the console's Indexer and
Oracles pages read REAL chain state from api.hanzo.ai/v1/* instead of
rendering "not connected":

- GET /v1/indexers  -> luxfi/indexer explorer REST (/health + latest
  block): per-network chain/network/height/health. lag honestly omitted
  (the indexer REST exposes indexed height, not the chain HEAD).
- GET /v1/oracles   -> luxfi/graph GraphQL priceFeeds (O-Chain PriceFeed
  registry): real on-chain price feeds; honest-empty when none.

Principal-gated (403 without a validated IAM principal); brand-scoped
(each brand's cloud is wired to its own indexer/graph, a ledger is public
within a brand). Honest 502 on unreachable upstream, never a fabricated
row. Mirrors clients/visor + clients/zt structure; interface-seam tests
against a fake upstream. Registered order 135.
2026-07-02 20:27:25 -07:00
hanzo-devandGitHub ec8691d6ac feat(o11y): emit OTel traces via go.opentelemetry.io/otel (service.name=hanzo-cloud) (#67)
Env-gated on OTEL_EXPORTER_OTLP_ENDPOINT; non-fatal; clean no-op when unset (safe to ship before the collector is live). Installs the global tracer provider with a service.name resource so the console Monitoring tab filters this product. Mirrors ai/object/telemetry.go. Traces-only; metrics/logs are a tracked follow-up.
2026-07-02 20:18:47 -07:00
hanzo-devandGitHub 2625817e68 chore(deps): bump hanzoai/ai v1.789.1→v1.790.1 — wire /v1/images/generations diffusion (zen3-image → do-ai fal) (#70) 2026-07-02 19:46:27 -07:00
zandGitHub 32159c4d2a Merge pull request #64 from hanzoai/feat/sites-subdomain-router
feat(sites): wildcard-subdomain site router over S3 + Cloudflare purge-on-redeploy
2026-07-02 18:14:28 -07:00
hanzo-dev 0a80a6cf71 fix(sites): RED — unified reserved-list enforced at create+bind+serve, stream not buffer, 405
RED review fixes on the sites router:

1) [HIGH] ONE reserved-subdomain source (clients/sites/reserved.go:
   baseReserved baked-in + operator SetReservedExtra, never subtractable),
   consulted at THREE points that can no longer drift: serve (siteSlug),
   project-create (createProject -> 400), and host-bind (Store.BindHost ->
   errReservedHost). site_hosts can now NEVER physically hold a reserved host,
   so a reserved subdomain never resolves even if the ingress regex drifts —
   the serve gate is a backstop, not the sole guard. Widened the set to app/
   auth/payment/brand labels (console, sites, internal, gateway, login, secure,
   account, signin, auth, pay, wallet, admin, brand terms, ...).

2) [MED DoS] Serve now STREAMS objects (Fiber SendStream, Content-Length from
   info.Size, fasthttp closes the reader) instead of io.ReadAll-buffering up to
   64 MiB per request on the unauthenticated edge — removes the OOM vector.
   Same for the 404.html path.

3) [LOW] Non-GET/HEAD on a site host → 405 + Allow: GET, HEAD.

Tests: IsReserved, reserved-host-never-serves backstop, 405, BindHost-rejects-
reserved (even with a forced project row), create-rejects-reserved-slug via the
real handler. All green; no regressions.
2026-07-02 18:09:27 -07:00
hanzo-dev 3bc0ca2ebc fix(platform): harden cold-start deploy flywheel (RED L2+L1+I2)
Close the two LOW follow-ups on the cold-start tenant-RBAC fix, plus confirm
the fresh-org fail-closed status. All on top of v1.786.23 (already SHIP).

L2 — git reconciler no longer treats a transient tenant-RBAC delay as TERMINAL
and no longer head-of-line-blocks other orgs. reconcileBuild now does ONE
non-blocking readiness probe (ensureTenantReady: create-namespace-if-absent +
single SelfSubjectAccessReview) instead of the synchronous image path's ~45s
in-line waitForTenantRBAC. If the operator's RoleBinding has not landed, the
deployment stays 'building' and re-drives on the next 10s tick — never a
permanent fail (there is no client to retry a git build) and never a 45s stall
of the shared sequential reconciler. Only the elapsed build deadline fails it
honestly. errTenantProvisioning from applyLive is also caught as transient
(defense in depth). Namespace-create is decomplected into one shared
ensureNamespaceExists; ensureNamespace (sync, blocking) and ensureTenantReady
(async, probing) compose it.

L1 — image deploy path gains a per-org in-flight-deploy cap (inflightGate,
maxConcurrentDeploys, default 8 via CLOUD_PLATFORM_MAX_CONCURRENT_DEPLOYS),
mirroring the git build cap. deployImage acquires a slot before applyLive's
~45s RBAC wait and releases on any return; over-cap is a retryable 429 refused
BEFORE recording an attempt. Bounds request-goroutine pile-up on a wedged
operator; per-org (one org's saturation never throttles another); fail-closed.

I2 — confirmed the truly-fresh-org path fails closed on 503 (RBAC pending),
NOT a raw 502: the namespace IS created (the trigger for the operator's
RoleBinding), then the bounded RBAC wait yields errTenantProvisioning -> 503.

Tests (all -race green): reconciler stays 'building' then goes live on a later
tick once RBAC lands (not 'failed'); over-cap image deploy -> 429 with per-org
isolation + slot-release re-admit; fresh-org deploy -> 503 with namespace
created + no Service CR + honest 'error' deployment recorded.
2026-07-02 18:06:45 -07:00
244b43b3d7 fix(admin): reconcile fleet revenue with commerce — X-Org-Id + bare-slug subject (#65)
The /v1/admin money panels (finance/orgs/overview) read $0 for every org despite
real balances (lux $10,000, maxpower $20,498) because the commerce client used
the wrong org selector on BOTH axes:

- commerce.go get(): sent X-IAM-Org-Id, which commerce does NOT read. Commerce
  EdgeAuth resolves the per-org billing namespace from the TRUSTED X-Org-Id header
  (trusted only with the COMMERCE_SERVICE_TOKEN bearer). X-IAM-Org-Id silently
  fell back to the default (COMMERCE_SERVICE_ORG) namespace.
- admin.go orgSubject(): keyed the wallet subject as "org/org"; commerce keys the
  per-org wallet under the BARE org slug (user=<org>) within the X-Org-Id namespace
  (the 2026-07 commerce durability rework, commerce >=1.46.8).

Either alone zeroed the reconciliation; both were present. The prior comments
encoded the wrong model ("commerce resolves from COMMERCE_SERVICE_ORG, header
advisory") — corrected to the verified contract.

Verified LIVE against commerce /v1/billing/{balance,usage-rollup}:
  user=lux      + X-Org-Id: lux      -> $10,000.00 (1,000,000c)
  user=maxpower + X-Org-Id: maxpower -> $20,498.13 (2,049,813c)
  user=lux/lux  OR X-IAM-Org-Id      -> $0 (the bug)

The fleet-wide /v1/costs COGS god-view is org-independent and correctly sends no
org (unchanged).

Regression guard: TestCommerce_ReconcilesWithXOrgIdBareSlug — a contract-accurate
fake commerce that returns money ONLY for X-Org-Id + bare-slug user; proven
red->green (fails on org/org, passes on the fix). Full admin suite green.

Co-authored-by: blue <blue@hanzo.ai>
2026-07-02 18:05:16 -07:00
zandGitHub e0e67e7fa3 Merge pull request #66 from hanzoai/feat/agent-sessions
feat(agents): live agent-session control plane (/v1/agents/sessions)
2026-07-02 17:41:13 -07:00
hanzo-dev 9d12d11a64 agents/sessions: clone SSE root filter (fix Ctx-recycle data race) + prove event-seq under concurrency
Red review of the live agent-session control plane.

FIX (MEDIUM, systems lens): sessionsStream retained root := c.Query("root")
verbatim. c.Query is a zero-copy view into the fasthttp request buffer, and the
SendStreamWriter loop OUTLIVES the handler (runs after the Ctx is recycled), so
the long-lived root filter raced a reused buffer — within-org stream-filter
corruption / UB. tenant() already clones org for this exact reason; clone root
the same way. Not cross-tenant (org is cloned + bus-filtered); fixes the race
and honors the file's own 'never touch Ctx after return' invariant.

TEST (vector #4): add TestSessionEventSeqConcurrent — 64 parallel AppendEvents
to one session must yield seqs exactly {1..N}, no gaps (no lost write) no dupes
(no raced MAX+1). Proves the single-conn + UNIQUE(session_id,seq) guarantee
under -race instead of only asserting it.
2026-07-02 17:38:16 -07:00
hanzo-dev 8ca58e924c feat(agents): live agent-session control plane (/v1/agents/sessions)
The canonical cloud registry every surface hangs off: live agent SESSIONS +
the subagent tree, streamed over ZAP, remote-controllable. This is the
view/control/stream layer; durable execution rides hanzoai/tasks, not a
bespoke scheduler.

Model + store (agents.db, same tenancy pattern as agents/runs):
- Session{id,agent,org,actor,status,parentSessionId,rootSessionId,title,
  startedAt,endedAt,taskWorkflowId,taskRunId,events[]}. Subagent tree =
  sessions linked by parentSessionId; the outer agent is the root, each
  spawned subagent a child, all sharing rootSessionId. Parent must exist
  in the SAME org (TOCTOU-checked in the write path) so a tree can never
  cross tenants. Per-session monotonic event Seq.

REST (org-scoped via principal.Tenant, fail-closed):
- POST /v1/agents/sessions            register (opt parentSessionId)
- GET  /v1/agents/sessions            list (filter root/parent/status)
- GET  /v1/agents/sessions/:id        detail + children + recent events
- GET  /v1/agents/sessions/:id/tree   full subagent-flow graph (1 query)
- PATCH /v1/agents/sessions/:id       status/title (terminal is monotonic)
- POST /v1/agents/sessions/:id/events append message/tool-call/spawn/log
- POST /v1/agents/sessions/:id/{pause,resume,stop,message}  control
  Routes register BEFORE /v1/agents/:name (Fiber matches in registration
  order); /stream precedes /:id for the same reason.

ZAP live stream:
- GET /v1/agents/sessions/stream (SSE) rides the ZAP machine transport
  natively (zip SendStreamWriter streams through ListenZAP — proven by
  zip stream_test). In-process bus is the single fan-out seam a direct
  ZAP push subscription attaches to. Org-filtered, non-blocking, laggard-
  drop; GET endpoints are the source of truth.

Durable execution = hanzoai/tasks (architecture alignment):
- Root session -> a tasks workflow; subagent -> child workflow (same
  rootSessionId). TaskController seam mirrors the tasks SDK Client
  (Signal/Cancel); control forwards to it when a session is task-backed,
  else records the command as a durable control event for stream-
  consuming surfaces. Default is the disabled (record-only) controller;
  the live client.Dial(TASKS_URL) plug-in point is marked in Mount.

Run integration (#5): the ONE runAgent path (HTTP + scheduler) opens a
root session per run (best-effort, never fails the run), so every run is
visible in the same registry.

Tests (real): store tree-linking + cross-tenant/dangling parent deny +
event seq/counts; HTTP tree assembly; cross-tenant read/tree/control/
append/parent deny; control authz (no validated principal -> 403) +
tasks forward (signal/cancel, forward-failure 502, record-only fallback);
event append/seq + status monotonicity; run-opens-session; bus fan-out/
org-filter/overrun/close. go build+vet+test clean; -race clean.
2026-07-02 17:38:16 -07:00
hanzo-dev fed3e40b12 feat(sites): wildcard-subdomain site router over S3 + Cloudflare purge-on-redeploy
Add clients/sites: a HOST-routed public site server that turns
<slug>.hanzo.app into the static site a project deployed to OUR S3
(<org>/<slug>/ in CLOUD_PROJECTS_BUCKET). Installed as the FIRST middleware
in the compose root, ahead of identity/billing, so a published site is a
public artifact served straight from S3 — never a tenant API call.

Tenant isolation (RED-focus): the org + S3 prefix come ONLY from the store
lookup keyed by the validated subdomain slug, never from the request path or
a client header. Object keys are rooted-clean (path.Clean under '/') so no
../ or encoded traversal can escape the <org>/<slug>/ prefix into another
project or org. A globally-unique site_hosts binding table makes a bare
subdomain resolve deterministically to exactly one tenant (project slugs are
only org-unique); binding is first-come and cannot be hijacked.

Cache: one canonical policy (sites.CacheControlFor) applied both when writing
objects at deploy and when serving them — HTML public,max-age=60,s-maxage=86400;
content-hashed assets immutable 1y; middle TTL otherwise; per-project
cacheControl override on the document TTL. Cloudflare purge-by-cache-tag
(site-<org>-<slug>) on redeploy AND delete; creds from KMS/env
(CF_API_TOKEN/CF_ZONE_ID), honest no-op when unset. Cache state (TTL +
lastPurgeAt) exposed on the project API.

Tests: traversal/cross-tenant isolation proof, host-routing + reserved-host
exclusions, first-come/no-hijack subdomain binding, CF purge client.
2026-07-02 17:29:17 -07:00
hanzo-dev 89a51599fd feat(zt): tenant-scoped networking surface fronting Hanzo Zero Trust
Add clients/zt — a thin, org-scoped facade over the Hanzo Zero Trust
controller's OpenZiti Edge Management API (/edge/management/v1), backing
the console's Networks, Service Mesh and Edge pages (which render
"not connected" today).

Surface (all org-scoped by the validated principal):
  GET /v1/networks[/:id]  the org's ZT overlay, projected from its edge-routers
  GET /v1/mesh/services   ZT edge services
  GET /v1/edge/nodes      ZT edge-routers + real online/disabled/offline status

- client.go: one HTTP path — Ziti password-auth (KMS-injected
  ZT_CLIENT_ID/ZT_CLIENT_SECRET, zt-session header), cached session with
  re-auth-and-retry-once on 401, generic {data,meta} pager, honest error
  mapping, TLS trust via ZT_CA_PEM. Fails closed 503 when unconfigured.
- types.go: ZT wire structs + console view structs + PURE mapping.
  Tenant isolation is the "org-<org>" role attribute (the ONE tenancy
  convention ZT expresses natively); list/get filter to the caller's org.
- zt.go: routes/handlers, registered as subsystem "zt" (order 134).
- http_test.go: fake controller (interface seam) — asserts 200, tenant
  isolation, shape, health mapping, 401 re-auth retry, fail-closed 503.

Honest-empty over fabrication throughout: no org tag -> invisible; no
routers -> no network; no metrics -> omitted (UI renders em dash).
2026-07-02 17:28:44 -07:00
zandGitHub a18ec0eac8 Merge pull request #63 from hanzoai/feat/visor-subsystem
feat(cloud): mount visor /v1/visor/* as a subsystem in the unified binary
2026-07-02 17:25:16 -07:00
hanzo-dev 8956fbde1d chore(cloud): pin visor v1.108.5 for the mounted subsystem 2026-07-02 17:24:25 -07:00
zandGitHub f38f57ab99 Merge pull request #62 from hanzoai/feat/admin-compute-endpoint
feat(admin): /v1/admin/compute — cross-tenant compute analytics from the datastore
2026-07-02 17:22:58 -07:00
hanzo-dev 18c1852215 feat(admin): /v1/admin/compute — cross-tenant compute analytics from the datastore
New global-admin read GET /v1/admin/compute powering the console Bots + Machines
operator boards. Aggregates hanzo.compute_usage(org, app, project, kind, event,
machine_id, size, price_cents, ts) grouped by (org, app, project, kind) over the
shared datastore client (aiobject.DatastoreQuery — the clients/analytics transport,
no second conn). `kind` is an OPEN LowCardinality spectrum (bot|machine|cluster|
nodepool|container|function|…) matched as a PLAIN STRING — ?kind= narrows to any
kind (Bots=bot, Machines=machine; future Clusters/Functions reuse this endpoint),
?org filters, ?range=24h|7d|30d bounds. Two-level roll-up: inner argMax(event,ts)
per machine -> outer counts machines, active (latest non-terminal), sum(price_cents),
max(ts). Honest-empty when the warehouse/table isn't wired yet (visor/commerce
emitter pending) — never a fabricated fleet. Global-admin only (s.guard); stays v1.x.x.
2026-07-02 17:15:02 -07:00
hanzo-dev c2f7003016 feat(visor): /v1/machines,/v1/gpus,/v1/clusters — compute unified into cloud via Visor
New clients/visor subsystem fronts Visor (the cloud OS at visor.hanzo.svc) and
serves the console's Machines/GPUs/Clusters pages as clean, tenant-scoped REST off
the unified cloud binary — replacing the god-mode /paas admin proxy that 501s.

Routes (every route org-scoped by the validated principal → Visor ?owner):
  GET/POST /v1/machines, GET/DELETE /v1/machines/:id   -> get-machines / machines/launch / delete-machine
  GET /v1/gpus (+ /v1/gpus/alerts)                     -> per-accelerator inventory derived from GPU machines
  GET /v1/clusters, node-pool create/scale/delete      -> get-node-pools / *-node-pool

View JSON mirrors the console normalizers exactly (visor.ts/compute.ts/platform.ts)
so the FE renders with no change. No fabrication: GPU rows are real accelerators of
real GPU machines, clusters are real node pools, and telemetry Visor lacks is
omitted (renders — not 0). Auth: KMS service credential (Basic) or forwarded bearer.

Tests: tenant scoping/isolation, machine/gpu/cluster shape, GPU slug derivation,
launch quote+real+delete. go build ./... + go vet + go test all green.
2026-07-02 17:08:17 -07:00
hanzo-dev 97cad6068c feat(platform): native console aggregates — /v1/{environments,pipelines,builds,releases}
The console Environments/Pipelines/Builds/Releases pages rendered "not
connected" because they call top-level REST that no cloud subsystem served.
Serve them natively from the platform control plane, DERIVED from the SAME
per-org project/app/deployment/build records (no new data model, no fabrication):

  - GET /v1/environments — distinct Application.Environment targets across the
    org's apps, each aggregating its apps (services), with a derived
    type/status. List-only: an environment is a scope on apps, not a record.
  - GET /v1/pipelines — one per app: its build/deploy config (repo|image) plus
    the status/timing of its latest deployment. List-only: a pipeline is an app.
  - GET /v1/builds — the REAL arcd BuildKit build records (platform_builds),
    joined to app repo + deployment commit. List-only: builds are triggered by
    the app deploy path (git source) — one trigger, not a duplicate here.
  - GET /v1/releases — deployments actually applied to the cluster
    (status deploying|live): a released image tag on an app/environment.

Every route is org-scoped through the same validated-principal gate (s.tenant →
requires c.User()); the response is the exact `{ "<plural>": [...] }` wrapper the
console FE normalizers read. Three org-wide store aggregates back them
(ListAllApplications / ListDeploymentsByOrg / ListBuildsByOrg), org the only
tenancy predicate. Real records or an honest empty — never fabricated history.

Tests: shape (200 + wrapper + derived fields), org isolation (second org sees
empty, no cross-tenant leak), forgeable-org refusal (no X-User-Id → 403).
2026-07-02 17:04:37 -07:00
hanzo-dev d1aa749779 feat(do): native DigitalOcean VPC + Load Balancer surface (/v1/vpcs, /v1/load-balancers)
Add clients/do: an org-scoped facade over digitalocean/godo's native VPCs
and LoadBalancers services, backing the console's VPC + Load Balancers pages
(which render 'not connected' today because nothing serves them).

- Routes: GET/POST /v1/vpcs, GET/DELETE /v1/vpcs/:id and the same for
  /v1/load-balancers. Real godo calls, honest empty/error states, never
  fabricated.
- Tenant isolation: DO is a single account, so a resource's physical DO name
  is 'o'<orgHash>-<friendly> via provisioning.BucketName (the SAME org-hash
  convention clients/s3 uses). List filters the account inventory to the
  caller's prefix; get/delete confirm prefix ownership before acting; a
  cross-tenant id reads 404 (existence-oracle guard).
- Fail-closed: absent DO_API_TOKEN every op is an honest 503.
- FE shape matches console2 VpcModule/LoadBalancerModule verbatim (vpcs[],
  loadBalancers[] with the exact field names).
- Registered as subsystem 'do' (order 123). godo v1.197.0 added to go.mod.
- Tests: per-org VPC + LB isolation, forge-path 403, fail-closed 503.
2026-07-02 17:02:11 -07:00
zandGitHub 322cf7ace4 Merge pull request #61 from hanzoai/fix/agents-ai-inference
fix(agents+platform): real /v1/agents/:name/run inference + tolerate async tenant-RBAC on first deploy
2026-07-02 16:43:35 -07:00
hanzo-dev 34966f18ee chore(deps): realign luxfi/age + luxfi/pq go.sum zip hashes (force-re-tag drift)
Same class as f238188: upstream force-re-tagged luxfi/age v1.5.0 and
luxfi/pq v1.0.3 (content moved, /go.mod hashes unchanged), so the committed
zip h1: sums no longer match the served bits and `go build ./...` fails
verification. These deps entered the graph via hanzoai/commerce/metering
v0.1.2 (the agents scheduler/billing). Re-record the current zip hashes.
2026-07-02 15:48:48 -07:00
hanzo-dev 7609c9981e agents: bind /v1/agents/metrics + /v1/agents/activity (unshadow from :name)
The console2 Agents dashboard calls two org-wide routes that were never
reachable: the bare /v1/agents/:name wildcard captured "metrics"/"activity"
as an agent name (Fiber matches in registration order), so both 404'd and the
dashboard rendered a permanent "not connected" state.

- Register the two static routes BEFORE :name so they win the match.
- GET /v1/agents/metrics?range=24H|7D|30D -> a per-agent invocations-over-time
  histogram bucketed from REAL agent_runs rows; the Resource Usage rollup is
  all-null because this store meters no CPU/mem/storage/cost (honest em-dash,
  never a fabricated trend). Shape mirrors console2 normalizeMetrics exactly
  ({range,series:[{key,points:[{t,v}]}],resource:{...}}).
- GET /v1/agents/activity -> org-wide recent-activity feed: each recorded run
  is an invoked/failed event, each agent's own create/update timestamps are
  created/updated events; merged newest-first, capped 50. Shape mirrors
  normalizeActivity ({activity:[{id,kind,agent,message,at}]}).
- Store: add RunsSince(org,since,limit) — org-wide runs across all agents,
  tenancy on the org column; powers both surfaces.
- Tests prove the surfaces are not shadowed (200, not 404), reflect only real
  runs, and stay org-isolated.
2026-07-02 15:45:44 -07:00
hanzo-dev d5fbf844f3 fix(agents): wire real inference so /v1/agents/:name/run executes
deps.AI was permanently nil under the default all-enabled config
(pickAIClient returned nil for cfg.Enabled("ai") and no in-process ai
subsystem ever filled it), so every agent run 503'd "inference is not
configured on this deployment" before the already-live per-org metering.

New AI client (clients/aihttp.go), two credential modes:
- AIHTTPAt: static-key OpenAI-compatible client (CLOUD_AI_API_KEY) — an
  operator/pre-provisioned-key override.
- AIHTTPM2M: durable default — mints+auto-refreshes an IAM client-
  credentials token from the binary's OWN identity (IAM_CLIENT_ID/SECRET)
  via x/oauth2/clientcredentials. No static key to rotate, no expiry cliff,
  no new secret to store. On Hanzo the identity resolves to
  admin/hanzo-cloud, which the gateway treats as balance-exempt, so cloud's
  per-org ResourceMeter stays the single revenue debit (no double-bill).

- build.go pickAIClient: static key -> M2M -> ZAP RPC -> fail-closed stub.
  Never returns nil (the live bug). Secret never logged.
- config.go: CLOUD_AI_BASE_URL (default https://api.hanzo.ai/v1),
  CLOUD_AI_API_KEY (optional), CLOUD_AI_DEFAULT_MODEL (default
  deepseek-v4-flash), AIAuthClientID/Secret from IAM_CLIENT_ID/SECRET.
- clients/aihttp_test.go: httptest OpenAI emulation — default-model
  substitution, content parse, 4xx/5xx mapping, empty-choices error, and
  M2M token mint+use+cache.

Composes with the live metering (Gate/MeterUsage) untouched. Model routing
is the gateway's job; empty model -> cheap default is the only cloud-side
fallback (no in-code model aliasing).
2026-07-02 15:34:54 -07:00
hanzo-dev 1be9f0b40d fix(admin/finance): RED — honest revenue.Configured + fleet-wide /v1/costs (no false margin)
Addresses Red MED-1/MED-2/INFO-3:
- MED-1: revenue.Configured now means the source was actually READ (listOrgs
  succeeded), not merely wired. A transient IAM failure → configured:false, never a
  fabricated zero that flips margin negative into a false 'burning' alarm. Per-org
  read failures mark the commerce source not-ok (partial), never presented as whole.
- MED-2: /v1/costs is a fleet-wide god-view — commerce resolves the namespace from
  COMMERCE_SERVICE_ORG, NOT from a request header (it never reads X-IAM-Org-Id).
  Dropped the no-op org arg from costs(); corrected the false 'resolves namespace
  from X-IAM-Org-Id' claims in commerceClient + orgSubject docs.
- Test: TestFinance_RevenueSourceDown_NoFabrication proves no fake revenue/margin
  when the IAM org list is unreadable while COGS still flows.
(INFO-3 false-green fix lands console-side in financeHealth.) 10 admin tests green.
2026-07-02 14:28:30 -07:00
hanzo-dev 062a0f46c0 feat(admin/finance): margin COGS from commerce /v1/costs — one vendor-COGS source
The finance board's cost side now CONSUMES commerce /v1/costs (the single
vendor-COGS source of truth: DigitalOcean compute + the LLM providers we resell)
instead of re-reading DigitalOcean's billing API to derive a DO-only cost. This
removes cloud's duplicate DO COGS read and gives the board the multi-vendor
per-vendor breakdown for free.

- commerceClient.costs() reads GET /v1/costs over the admin S2S service token
  (COMMERCE_SERVICE_TOKEN, no IAM user → commerce requireCostsAdmin M2M path).
- financeCost carries {configured,totalCents,vendors[],period}; margin cost is
  now the multi-vendor TotalCents, not DO month-to-date spend.
- DigitalOcean stays ONLY as the orthogonal promo-credit/runway treasury view
  (commerce does not track our prepaid credit); its MTD spend feeds runway alone.
- /v1/admin/finance shape is additive (cost.digitalocean preserved) and the
  global-admin guard is unchanged.
- tests: fake commerce now serves /v1/costs; margin = revenue - COGS; DO-off path
  proves COGS still flows from commerce (decoupled).
2026-07-02 13:51:46 -07:00
hanzo-dev 7c8be23f14 fix(platform): tolerate async tenant-RBAC on first deploy (cold-start race)
A brand-new tenant's namespace is created by ensureNamespace, but the operator's
tenant-RBAC controller projects cloud-api's `cloud-api-platform` RoleBinding
(get/create resourcequotas/limitranges/services.hanzo.ai in tenant-<org>)
ASYNCHRONOUSLY. The first-ever deploy raced ahead of that RoleBinding and failed
with `resourcequotas ... is forbidden`, self-healing only on a manual retry.

Gate ensureNamespace on a SelfSubjectAccessReview readiness poll
(waitForTenantRBAC): before touching the quota objects, ask the apiserver — as
cloud-api's OWN identity — "can I get resourcequotas in tenant-<org>?" and wait,
with bounded exponential back-off (~45s ceiling), for the operator's RoleBinding
to land. An already-onboarded tenant is confirmed by a single fast probe (no
sleep), so existing deploys are not slowed. On timeout, fail CLOSED with a
retryable errTenantProvisioning (deployErrStatus -> HTTP 503, honest
"provisioning, retry") — never a fabricated success. Creating a SSAR needs no
tenant RBAC (system:basic-user), so the probe is itself immune to the window it
closes. No RBAC or namespace derivation is loosened.

Tests (clients/platform/tenant_rbac_test.go): retry-until-RoleBinding-lands
succeeds end-to-end (quota+Service CR written); bounded timeout fails closed
(503, no quota/CR written); ctx-cancel aborts promptly; ready tenant resolves in
one probe (auto-glue fast path unchanged).
2026-07-02 13:39:42 -07:00
zeekay 930ded6efb Merge remote-tracking branch 'origin/rip/api-to-v1' 2026-07-02 13:07:18 -07:00
hanzo-dev 1deec7088c feat(agents): /v1/agents per-org fail-closed metering + long-running scheduler
Lands the agent-backend metering feature onto the zip->zap-proto-migrated main
(cloud is already fully migrated on main; 8 subsystem pins + MountAll clean).

- /v1/agents/* self-meters a per-run fee to commerce: pre-authorize the org's
  prepaid credit balance fail-closed (402 insufficient_balance), debit on success,
  attributed to product "agent". Added to selfMeteredPrefixes so the edge gate
  never double-bills. Run path (money-moving) requires a VALIDATED principal
  (c.User() non-empty), refusing the no-bearer forge path; scheduled runs carry an
  unforgeable 'scheduler'-prefixed actor.
- ResourceMeter.Gate now forwards costCents as AuthInput.AmountCents so the gate
  enforces available >= fee (not merely > 0) — a 1-cent balance can no longer
  authorize a run that takes the ledger negative. MeterUsage generalizes the
  per-org debit (Actor/Model/token attribution) while Meter keeps its signature.
- Long-running agents: cron scheduler scans once a minute over a partial index
  (ix_agents_scheduled), bounded per-org cap (CLOUD_AGENT_MAX_LONG_RUNNING);
  scheduler.stop drains in-flight runs inside the SIGTERM budget via ShutdownAll.

Deps: commerce/metering v0.1.0 -> v0.1.2 (Actor field + AuthInput.AmountCents).
All other pins inherited from migrated main (ai v1.789.1, authz v1.10.3,
base v1.4.6, commerce v1.42.29, licensing v0.1.1, metrics v0.4.1, o11y v1.3.12,
vfs v0.4.4). hanzoai/zip stays out of the graph; zip == zap-proto/zip v1.2.0.

go mod verify clean; go build ./... EXIT 0; MountAll boot-smoke clean (no
want *zip.App); agents -race + root/ml/provisioning billing tests green.
2026-07-02 12:44:31 -07:00
zeekayandhanzo-dev f238188227 chore(deps): realign luxfi/age + luxfi/pq go.sum zip hashes (force-re-tag drift)
Verified the /api/ -> /v1/ rip is COMPLETE on origin/main: zero owned /api/
route registrations, zero owned /api/ client strings. The rip landed in
32138db (productsvc: drop residual /api/ prefix) plus the o11y and eval
cleanups. Every remaining /api/ reference is a non-owned external contract:

  - clients/o11y/o11y.go, o11y_test.go: doc comments ("no /api/, no rewrite")
    documenting the now-removed upstream rewrite.
  - clients/pricing/pricing.go: https://openrouter.ai/api/v1/models — a
    third-party vendor URL.
  - clients/platform/*_test.go: "apps/api/deploy" where `api` is a user's
    APP NAME inside /v1/platform/... paths (not an API prefix).
  - zapface/dispatch.go: comment already says "the /v1 convention".
  - clients/prompts/catalog.json: a prompt-catalog data blob describing a
    different project (prompts.chat), not this repo's routes.

The IAM /api/add-usage-record callout referenced in older cloud docs is a
Casdoor/casibase-lineage endpoint the LEGACY Node cloud-api used (documented
in hanzoai/commerce auth/iam_admin.go). The current Go cloud-api does NOT
call it: billing meters to commerce via hanzoai/commerce/metering. No
cross-service IAM usage-record dependency exists in this repo.

The only change here is a deps-hygiene fix so the build verifies clean:
luxfi force-re-tagged age@v1.5.0 and pq@v1.0.3, drifting their module-zip
h1: hashes vs the recorded go.sum (go.mod hashes unchanged). Realigned to
the upstream hashes at the SAME versions — no major/minor bump.

  CGO_ENABLED=0 GOWORK=off go build -mod=readonly ./...   -> exit 0
  go test ./clients/{o11y,eval,pricing,ml,admin} ./zapface . ./clients/platform -> all ok

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-02 12:33:09 -07:00
hanzo-dev 2ee521c6da fix(platform): serialize apply-CR→finalize-live per app (RED LOW-1)
applyService (operator Service CR write) was not jointly ordered with
FinalizeLive (live-pointer DB write): under concurrent same-app deploys an
OLDER deploy's CR write could land AFTER a NEWER one already went live, leaving
the live Service CR image lagging the recorded live version. deployImage had no
supersede gate at all.

Introduce applyLive — the ONE deploy mechanic shared by the image-source path
and the git build reconciler — running supersede-check → applyService →
FinalizeLive as one per-app-serialized critical section (appMutex, fixed-shard,
O(1) memory). An older deploy that loses the race is superseded and never writes
its CR. FinalizeLive's monotonic CAS still backstops DB monotonicity.

go vet + full clients/platform test suite green.
2026-07-02 12:00:17 -07:00
hanzo-dev 20ea2881ce fix(platform): HIGH-2 secrets-free cloud-api + MED-1 version-monotonic finalize (RED)
HIGH-2 — cloud-api touches NO K8s Secret:
- delete ensurePullSecret + secretsGVR + CLOUD_PLATFORM_PULL_DOCKERCONFIG;
  the per-tenant ghcr-pull Secret is provisioned by the OPERATOR's tenant-RBAC
  controller (from a KMS-synced source). serviceCR only REFERENCES it by name.
  cloud-api's ServiceAccount holds no secrets grant and issues no Secrets call.

MED-1 — monotonic live-version finalize (no build-time inversion):
- Store.FinalizeLive: ONE atomic conditional UPDATE that advances an app to live
  ONLY when its version >= the currently-live version (no read-then-write TOCTOU).
- reconcileBuild gates on buildSuperseded before applying the (older) CR, and
  records a late/older build 'superseded' (image still succeeded) instead of
  regressing the running workload. deployImage shares the same FinalizeLive.
- tests: TestFinalizeLiveIsMonotonic (store CAS) + TestBuildReconcilerVersionMonotonic
  (e2e inversion: newer-first-live, older-late-superseded, CR never downgraded).
2026-07-02 10:55:55 -07:00
hanzo-dev 4d59d648fc feat(platform): git build→deploy watcher (close phase-2) + tenant GHCR pull secret
The git deploy path launched a BuildKit Job fire-and-forget and left the
deployment stuck 'building' — deploy.go documented the build watcher as
'phase 2'. Implement it as the ONE owner of the handoff:

- reconcile.go: a restart-safe reconciler (state in the store, not a
  goroutine) that scans 'building' deployments, checks each build Job, and on
  success applies the operator Service CR with the built image (the SAME
  applyService the image path uses) → deployment 'deploying', app 'live'. On
  failure/deadline it records the honest error. Started from Mount, stopped on
  Shutdown. Org-scoped: every write targets tenant-<row.Org>.
- store.ListBuildingDeployments: cross-org 'building' query (reconciler input).
- k8s.jobOutcome/jobResult: ONE Job terminal-state classifier shared by the
  concurrent-build cap and the reconciler.
- k8s.serviceCR imagePullSecrets + ensurePullSecret: the built image is PRIVATE
  (ghcr.io/hanzoai/tenant-<org>/*); provision the tenant GHCR pull secret from
  CLOUD_PLATFORM_PULL_DOCKERCONFIG (KMS-synced; no-op when unset) and reference
  it so the operator's pod can pull.

Tests: jobOutcome classifier + ListBuildingDeployments (oldest-first, cross-org,
building-only). Full platform suite green (RED authz/cmd-injection incl.).
2026-07-02 10:47:22 -07:00
hanzo-dev 929c55c182 refactor(eval): route telemetry over the ONE shared datastore client
clients/eval/telemetry.go opened a SECOND direct clickhouse.Open with a
parallel CLOUD_EVALS_CLICKHOUSE_* cred namespace, bypassing the shared ZAP
datastore mesh that clients/analytics + ai/object already use. Consolidate:

- eval telemetry now routes every write/read over ai/object's shared client
  (aiobject.DatastoreExec / DatastoreQuery / DatastoreEnabled), the same peer
  the o11y ledger + /v1/analytics use. One connection, one pool, one
  retry/backoff, one KMS-injected cred namespace (DATASTORE_*).
- DELETE the CLOUD_EVALS_CLICKHOUSE_* namespace and the private clickhouse.Open.
- Ownership stays clean: eval owns only its two tables (hanzo.eval_traces,
  hanzo.eval_scores); ai/object owns hanzo.cloud_usage / hanzo.observations.
- No batch primitive needed — eval Records are single-row, mapping to the
  shared DatastoreExec INSERT ... VALUES (?) the o11y write path already uses.
- Async-connect aware: readiness gates per-op on DatastoreEnabled() (honest
  'unavailable' in the boot window), tables ensured idempotently, latched once.
- Reads bind org + narrowers positionally (?) — no interpolation; LIMIT always
  applied. Tenant isolation + score finiteness invariants unchanged.

provisioning's direct CH client is a distinct control-plane concern — untouched.

go build + go test ./clients/eval/... green.
2026-07-02 08:40:16 -07:00
hanzo-devandGitHub 3c8b509380 ci(release): smoke-test the image before it can publish (#59)
A green go build/vet/test does not catch a binary that PANICS at startup.
v1.786.14/.15/.16 compiled clean but crashed at boot with

    cloud: mount metrics: metrics.Mount: app is *zip.App, want *zip.App

(a runtime type-assert from an incomplete hanzoai/zip -> zap-proto/zip
migration), published green, and CrashLooped in prod. The only gate that
catches this class is running the binary.

Restructure the single build-push into build(load) -> smoke -> push:

1. Build once to a local cloud:smoke tag (push:false, load:true), warming
   the BuildKit builder cache.
2. Boot that exact image with a minimal, prod-representative env (writable
   ephemeral /data + a throwaway 32-byte KMS master key so the KMS plane
   mounts on its normal ready path) and assert it reaches "listening" with
   NO startup-crash signature (metrics.Mount / mount metrics / panic /
   want *zip.App), else exit 1 BEFORE any push. Container always rm -f.
3. Re-run build with push:true and the real tags: identical context /
   platform / secrets, so every layer is a cache hit from step 1 and it
   only publishes the already-tested image.

Stays on the self-hosted arcd amd64 scale set + GH_PAT; notify-universe
unchanged.

Proven to DISCRIMINATE against the published images:
  ghcr.io/hanzoai/cloud:v1.786.18 (known-good) -> SMOKE PASS (exit 0)
  ghcr.io/hanzoai/cloud:v1.786.15 (known-bad)  -> SMOKE FAIL (exit 1)
2026-07-02 05:48:29 -07:00
hanzo-dev 7deb08323a merge(cloud): forward-integrate v1.786.18 F1 data-plane gate into the platform mount
SECURITY: cloud origin/main (dcd1a485) had DIVERGED from the LIVE image
v1.786.18 (9e597d07) at merge-base 2e4d402c — v1.786.18 was tagged+deployed
from fix/cloud-1.786.18-zip-and-gates but NEVER merged back to main. It carries
the F1 forged-X-Org-Id cross-tenant gate that main LACKED:
  - clients/principal (validated-principal helper) — new package
  - bot + o11y reverse-proxy forge gates (bot.go, o11y.go + red_forge_test.go)
  - whole-data-plane principal gating across agents/crm/eval/functions/git/kms/
    ml/plan/pricing/projectsvc/prompts/provisioning/s3

Building .20 from main+platform ALONE would have REGRESSED this live fix
(reopened the forged-X-Org-Id hole — the ".17 insecure, do NOT deploy" hole).
This merge makes the artifact a true SUPERSET of the security floor.

Only conflict: clients/provisioning/provisioning.go import block — resolved to
keep BOTH the F1 principal.Validated(c) gate AND the platform sanitizeOrg
injectivity crit-fix (OrgHasUnsafeRune + raw-byte hash). go.mod/go.sum merged
clean (main and .18 converged on identical dep floors: ai 1.789.1, authz
1.10.3, base 1.4.6, commerce 1.42.29, o11y 1.3.12, vfs 0.4.4, zap-proto/zip).

Result = main (analytics/crm/templates/git + zip migration) + /v1/platform mount
+ v1.786.18 F1 gate. All 24 subsystems registered. go build ./... + go vet green.
Tests green together: platform (TestRED_CommandInjectionBlocked, cross-tenant,
injective), F1 (TestRed_BotProxyForwardsForgedOrgNoPrincipal,
TestRed_O11yProxyGatesForgedOrgNoPrincipal), provisioning, principal, root cloud.
2026-07-02 05:34:55 -07:00
hanzo-dev a826a5bdde merge(cloud): mount /v1/platform PaaS subsystem into main (blue/paas-v1platform)
Merge RED-PASSED blue/paas-v1platform@99985110 onto main@dcd1a485, mounting the
per-org container-app PaaS control plane at /v1/platform (HIP-0106) — the deploy
engine behind one-click app deploys (ERP/Helpdesk ride on it).

Conflicts resolved (5 files, all combine-both-sides — no logic dropped):
  - subsystems/subsystems.go: KEEP every registration — platform (order 124) +
    analytics/crm/git/templates/prompts/agents/functions + all pre-existing.
  - clients/provisioning/provisioning.go: main's zip canonical import +
    branch's sanitizeOrg injectivity crit-fix (OrgHasUnsafeRune reject,
    raw-byte SHA-256, no TrimSpace) — both preserved.
  - middleware_identity.go: main's zap-proto/zip + doc; branch's OrgHasUnsafeRune
    (root cloud pkg) + SanitizeIdentity handler hardening — both preserved.
  - provisioning_test.go / middleware_identity_test.go: both test sets kept.

Integration: main migrated the repo hanzoai/zip -> zap-proto/zip; the branch
predated it, so the new clients/platform/{deploy,platform,http_test}.go were
rewritten to the canonical github.com/zap-proto/zip (incompatible zip.Ctx types
otherwise). go.mod unchanged from main (zap-proto/zip v1.2.0 direct); no new dep
(k8s.io/{apimachinery,client-go} v0.35.0 already present via ml/paassvc).

Crit-fixes preserved EXACTLY (RED-PASSED, proven green):
  argv build (TestRED_CommandInjectionBlocked), org-slug injective
  (TestSanitizeOrg{Injective,WhitespaceInjective}, TestBuildImageRefIsInjective),
  ResourceQuota (TestEnsureNamespaceAppliesQuota), no cross-tenant
  (TestHTTPCrossTenantIsolation, TestNamespaceIsDerivedFromOrgNotInput,
  TestServiceCRAlwaysPinnedToTenantNamespace).

go build ./... + go vet + go test (platform/provisioning/root cloud) all green.
2026-07-02 05:22:07 -07:00
hanzo-dev 9e597d07b9 fix(cloud): purge hanzoai/zip (forward zip-canonical-home) + complete F1 data-plane gates
Startup crash on v1.786.15/.16: `cloud: mount metrics: metrics.Mount: app is
*zip.App, want *zip.App`. Cloud's core migrated to github.com/zap-proto/zip
(v1.786.13→.15) so app is *zap-proto/zip.App, but eight hanzo modules cloud
imports still pinned the OLD github.com/hanzoai/zip and registered subsystems
that type-assert app.(*hanzoai/zip.App). Distinct import paths = distinct Go
types, so MountAll's first such subsystem ("metrics", hanzoai/metrics@v0.4.0)
failed the assert at runtime (build/vet/test stayed green — the mismatch is
runtime-only). authz/base/o11y were the same latent break behind it.

Forward fix (the canonical-home migration was already released upstream; cloud
merely lagged): bump every lagging module to its migrated tag —
  ai v1.789.1-… → v1.789.1        authz v1.10.1 → v1.10.3
  base v1.4.1 → v1.4.6            commerce v1.42.27 → v1.42.29
  licensing v0.1.0 → v0.1.1       metrics v0.4.0 → v0.4.1
  o11y v1.3.7 → v1.3.12           vfs v0.4.1 → v0.4.4
authz pinned to v1.10.3 specifically: v1.10.2/v1.10.4 carry an unrelated
GetPolicy 2-value change that breaks the pinned hanzoai/iam; v1.10.3 has the zip
migration AND the iam-compatible 1-value signature. commerce pinned to v1.42.29
(v1.43.0 regressed back to hanzoai/zip). clients/analytics (from the merged .16
work) is cloud's own code and is migrated in-place. Result: hanzoai/zip is gone
from go.mod/go.sum and the whole module graph; the compiled binary mounts
metrics+o11y+all subsystems and reaches "listening" with no panic.

Also folds in the COMPLETE F1 close (RED found the gate was partial — two
reverse-proxy paths still forwarded a forged X-Org-Id):
- clients/bot: gate proxy() on principal.Validated before forwarding X-Org-Id to
  bot-gateway (RED PoC red_forge_test.go now passes: no-principal forge → 403).
- clients/o11y: wrap the installed reverse-proxy handler in gate() — refuse any
  request with no X-User-Id before it reaches the o11y runtime (forge twin test).
- clients/crm: extend the forge guard to WRITE+DELETE verbs (belt-and-suspenders).
- middleware_identity: refresh the stale FAIL-MODE comment — post-F1 the DATA
  plane also fails secure on a cold-cache JWKS failure (bounded by stale-on-error).

Base = F1 (fix/cloud-data-plane-principal-gate, 473e0986) + origin/main (analytics
.16, 2e4d402c). One healthy image: F1 + analytics + zip-fix + bot/o11y gates.
2026-07-02 04:37:38 -07:00
hanzo-dev dcd1a4852b fix(analytics): import canonical github.com/zap-proto/zip (not hanzoai/zip)
Aligns clients/analytics with serve.go + every other in-tree clients/* subsystem,
which import github.com/zap-proto/zip. The original commit imported the OLD
github.com/hanzoai/zip, making analytics.Mount assert *hanzoai/zip.App while serve
passes *zap-proto/zip.App — a boot-time mount type mismatch. Removes the last in-tree
hanzoai/zip importer so once the migration lane re-releases the external subsystem
modules on zap-proto/zip, main boots with ONE zip.App type. (The DEPLOYED v1.786.17
is built off v1.786.13, which is all-hanzoai/zip, and is unaffected.)
2026-07-02 04:33:45 -07:00
hanzo-dev e1e5508e57 Merge remote-tracking branch 'origin/main' into fix/cloud-1.786.17-zip-and-gates 2026-07-02 04:18:41 -07:00
hanzo-dev 473e098687 fix(cloud): gate the whole data plane on a validated principal (RED HIGH — live cross-tenant)
RED found the cloud data plane trusted a bare X-Org-Id with no validated
principal. Off-gateway (direct api.cloud.hanzo.ai / in-cluster), a request with
`X-Org-Id: victim` and NO credential read/wrote/deleted another tenant's data:
CRM PII, KMS secrets, prompts, agents, evals, ML namespaces, projects, git repos.
SanitizeIdentity RESTORES a client X-Org-Id on the bearer-less "Phase-1 data"
path but leaves X-User-Id empty, so c.Org() alone is forgeable; c.User() (set
ONLY from a verified bearer/cookie) is the authentic signal.

ONE canonical gate — new clients/principal:
  - Validated(c): request carries a validated principal (X-User-Id set).
  - Tenant(c): verbatim org, gated + bounded + cloned; ("",false) => caller 403s.
The S3/eval fix (already shipped) is now the single source of truth, used
everywhere instead of six drifting hand-rolled copies.

Data-plane resolvers gated (were bare c.Org()):
  crm, prompts, agents, functions, git, eval -> principal.Tenant (verbatim)
  kms.guard (closes forged X-Org-Id==:org bypass), ml (per-org k8s ns),
  projectsvc, provisioning, s3 -> principal.Validated + own normalize/admin-bucket
  plan, pricing (public catalog) -> validated principal selects its overlay, else
  the public "hanzo" default (never a forged org's overlay)
  middleware_billing (no victim-ledger drain/probe), audit_middleware (aligned)

Breaks no real client: the console BFF always mints a user-bound bearer
(X-User-Id set); opaque-API-key callers hit /v1/ai/*, not these subsystems.

Tests (F4): clients/principal unit suite (forged-org-no-principal refused,
verbatim no-fold, empty/overlong refused, Validated only from X-User-Id); crm
forged-org 403 on every collection (PII); kms Vector8 forged X-Org-Id==:org with
no principal -> 403 (secrets). Existing per-subsystem tests send X-User-Id on the
legit path as the BFF does.

go build ./... green; go vet green; go test ./clients/... . green.
2026-07-02 03:34:45 -07:00
hanzo-dev 2e4d402c09 feat(analytics): native-Go /v1/analytics on datastore/ClickHouse, per-org
Adds clients/analytics (order 132, registered as analyticssvc so the real
/v1/analytics/health owns the probe, not serve.go's generic liveness route) —
the backend for the console Native Analytics module (unified-analytics.md §5).

Two read lenses over the ONE hanzo warehouse, reusing the SAME clickhouse-go/v2
client the ai o11y ledger opens (ai/object DatastoreQuery/DatastoreEnabled/
EnsureCloudUsageTable/ResolveCloudUsageWindow) — no second CH client, DRY:
  - LLM lens (REAL): hanzo.cloud_usage — requests/tokens/spend/models/errorRate
  - web+commerce lens: hanzo.events — honest-empty until the collector emits

Surface (read-only, org-scoped, /v1):
  GET /v1/analytics/overview     per-org KPIs (llm real; web/commerce honest-empty)
  GET /v1/analytics/timeseries   requests/tokens/spend over hour|day buckets
  GET /v1/analytics/top          top models (real) + top products (honest-empty)
  GET /v1/analytics/health       datastore connectivity + lens-table availability

Tenant isolation is the security bar: tenant() requires a VALIDATED principal
(c.User(), set by SanitizeIdentity only for a verified bearer) AND a valid org
(c.Org(), the minted owner claim) — closing the Phase-1 no-bearer forged-X-Org-Id
data path exactly as clients/s3 does. Every query binds the org POSITIONALLY
(query.go llmWhere/eventsWhere), so a maxpower token can never read another org.
ClickHouse creds are KMS-injected env (DATASTORE_*), never hardcoded.

Tests: query-boundary isolation (org bound, never interpolated, incl SQLi slug),
honest-empty, real-number KPIs, errorRate, gap-filled series, top-models pct;
HTTP: no-principal->403, forged-org-no-bearer->403, datastore-down->honest 503,
bad-range->400, health owned-by-analytics honest 503 when down.
2026-07-02 03:32:27 -07:00
hanzo-dev 4b7ddf0717 Merge feat/per-product-metering: per-product credit-drawdown for functions + s3
Integrates the fail-closed per-org credit-drawdown gate into cloud's last two
free data-plane subsystems (functions invoke, s3 op) via the ONE shared
cloud.ResourceMeter, plus the per-org billing-key fix (gate keys on the org slug).

HELD — NOT DEPLOYED. cloud origin/main is non-bootable until the zip migration
(#25 / o11y) lands; this ships with the cloud unfreeze. No dependency changes
(go.mod identical to main), so it adds no new build risk beyond the pre-existing
#25 o11y blocker. Verified: clients/functions 5/5, clients/s3 6/6, root billing
tests green; go build + vet clean on all changed packages.
2026-07-02 02:19:32 -07:00
hanzo-dev 6a56c2ff79 fix(billing): key the credit-drawdown gate on the org slug, not {org}/{sub}
The prepaid credit balance is PER-ORG (one credit pool covers the whole org),
so the metering gate must query the ledger by the org slug. identityFromCtx keyed
User on "{org}/{sub}", which queries an empty per-user ledger and 402s a fully
funded org — a revenue-blocking false-decline for every real request. Key User
on the org slug (bare sub only when org is absent), mirroring
metering.IdentityFromGatewayHeaders so cloud and every product key the SAME
ledger entry. The {org}/{sub} actor identity belongs on the usage audit trail,
not the gate; metering v0.1.0 carries no Actor field, so it is omitted until the
module ships the User/Actor split.

Covered by resource_billing_test.go (per-org debit asserts user==org). Root +
functions + s3 packages: go build + vet clean, tests green.
2026-07-02 02:19:16 -07:00
hanzo-dev 5c37a8350e feat(billing): per-product credit-drawdown metering for functions + s3 (DRY ResourceMeter)
Wire fail-closed credit-drawdown metering into the two remaining cloud data-plane
subsystems that were free, reusing the ONE shared cloud.ResourceMeter (the same
Gate+Meter provisioning and ml already use). No free tier: pre-authorize the
org balance (insufficient -> 402, unreachable -> 503, nothing runs), then debit
on success. No second metering path.

- functions: POST /v1/functions/:name/invoke gates before sandbox compute and
  debits the caller org on a real execution (product "functions", unit
  "invoke", fee CLOUD_FUNCTION_FEE_CENTS, $1.00 default). A sandbox transport
  failure ran no billable compute -> not charged.
- s3: the data-plane guard is the ONE place it meters -- every guarded op gates
  before S3 is touched and debits on handler success (product "s3", unit
  "op", fee CLOUD_S3_FEE_CENTS). A handler error is not billed.
- resource_billing: Meter now records the billed unit as Usage.Model (kind), so
  provisioning kinds (sql/vector/kv/...), functions "invoke", s3 "op" and ml
  kinds all get per-item attribution in the ledger under their product label.
- middleware_billing: add /v1/functions/ and /v1/s3/ to selfMeteredPrefixes so
  the edge gate never double-bills the subsystem's own charge.

Tests (real commerce + sandbox doubles): functions 5/5, s3 guard 6/6 -- 402 on
empty balance with no compute run, debit-on-success to the CALLER org (never the
client default), no-bill-on-failure, free-fee ungated, unconfigured no-op,
tenant isolation. go build + vet clean; affected packages green.
2026-07-02 01:35:53 -07:00
zandGitHub 9a66c437e8 Merge pull request #58 from hanzoai/feat/saas-finance
feat(admin): SaaS finance dashboard — DO burn-down + revenue + margin/runway (cloud)
2026-07-02 01:00:34 -07:00
hanzo-dev 21c0984f27 feat(admin): GET /v1/admin/finance — SaaS profitability dashboard aggregate
Add a global-admin-only finance panel to the /v1/admin/* surface for
admin.hanzo.ai: DigitalOcean credit burn-down (our primary ~$40k credit
venue), month-to-date spend, revenue, MRR, gross margin, and runway.

- digitalocean.go: DO billing client (GET /v2/customers/my/balance +
  /billing_history). Authoritative DO sign convention (from DO's public
  OpenAPI spec): the three money fields are decimal-DOLLAR strings; a
  NEGATIVE account_balance = credit we hold, so creditRemaining =
  -account_balance (clamped at 0). dollars parsed to int64 cents at the
  edge. Token DO_API_TOKEN from env (KMSSecret); unset => {configured:false},
  never a fabricated balance.
- commerce.go: mrrCents reader — sums active/trialing subscriptions'
  monthly-normalized plan price (yearly => /12) for fleet MRR.
- finance.go: financeData shape + computeFinance, a PURE derivation
  (grossMargin = revenue - cost, marginPct, runwayDays = credit/burn or
  null, profitable). Handler fans out to DO + commerce, honest-empty on
  every unconfigured/unreachable path. Mounted under s.guard (global-admin
  only; no-principal/tenant-admin/forged => 403).
- Tests: computeFinance math (profitable + burning-faster + null-runway +
  unconfigured), DO sign/parse, MRR normalization, full-pipe aggregation
  with fake DO+commerce, honest-unconfigured-DO path; /v1/admin/finance
  added to the gate test so 403-for-non-admin is proven.

CGO_ENABLED=0 go build ./cmd/cloud: exit 0. go test ./clients/admin/: ok.
2026-07-02 00:49:14 -07:00
hanzo-dev a82299bfb3 chore: zip v1.2.0 + zap-proto/http v0.2.0 — SSE streams over ZAP
Bump to the streaming transport so cloud's SSE endpoints (o11y traces, MCP
notifications, chunked bodies) push over ZAP as live streams, not buffered blobs.
Additive — existing buffered responses unchanged. Build + tests green.
2026-07-02 00:46:38 -07:00
zandGitHub f68fbbc84d Merge pull request #57 from hanzoai/feat/v1-git
feat(git): native /v1/git layer (clone/push over go-git+VFS) + fix main build (fork.go zip import)
2026-07-01 23:59:47 -07:00
hanzo-dev e57c366f07 fix(projectsvc): fork.go on zap-proto/zip — finish the zip migration
The template-fork merge (#56) left clients/projectsvc/fork.go +
fork_test.go importing github.com/hanzoai/zip while their package sibling
projectsvc.go already moved to github.com/zap-proto/zip (5d2c993), so
`go build ./cmd/cloud` failed with a Ctx/Handler type mismatch. One import
line each — one and one way, the whole package on zap-proto/zip.
2026-07-01 23:56:53 -07:00
hanzo-dev a6e98343c1 feat(git): native S3-ready Git layer — /v1/git/* smart-HTTP clone/push
Adds clients/git: org+project-scoped Git hosting inside the unified cloud
binary — the "internal Gitea, native" foundation agents push code into.

Control plane (X-Org-Id tenancy, HIP-0026; optional X-Project-Id sub-scope):
  POST   /v1/git/repos        create a bare repo -> repoView (201)
  GET    /v1/git/repos        list the tenant's repos
  GET    /v1/git/repos/:name  repo detail (branches, HEAD, sizeBytes)
  DELETE /v1/git/repos/:name  delete + purge storage (204)
  GET    /v1/git/usage        per-repo + total bytes for the tenant

Smart-HTTP git protocol (real `git clone`/`git push` work natively):
  GET  /v1/git/:org/:repo/info/refs?service=git-upload-pack|git-receive-pack
  POST /v1/git/:org/:repo/git-upload-pack    (clone/fetch)
  POST /v1/git/:org/:repo/git-receive-pack   (push)

Storage: bare go-git repos on a go-billy filesystem; go-git's server
transport (plumbing/transport/server) reads/writes it for clone AND push.
MVP backs billy with osfs under {DataDir}/git/<org>/<project>/<repo>.git;
a documented TODO(vfs) seam swaps in hanzoai/vfs (S3/SeaweedFS) — vfs.FS
does not yet implement the go-billy surface go-git's dotgit requires.

Billing: every repo tracks sizeBytes, re-measured on create and after each
push; each measurement emits a meterable `git.usage org=.. repo=.. bytes=..`
log line. TODO(billing) seam for a commerce metering event.

Tenant isolation on every query (org empty -> 403; path :org must match the
authenticated tenant). Registered as subsystem "git" order 132.

go-git/v5 v5.19.1 + go-billy/v5 promoted indirect -> direct (no version bump).

Verified: CGO_ENABLED=0 go build ./cmd/cloud (exit 0); go test ./clients/git
(CRUD+isolation, info/refs advertisement, in-process go-git clone/commit/
push/re-clone round-trip, cross-tenant 403) all pass; real `git` CLI
clone/push/re-clone round-trip confirmed against a live server.
2026-07-01 23:56:53 -07:00
zandGitHub 78fed9688f Merge pull request #56 from hanzoai/feat/template-fork
feat(fork): template → project fork (cloud)
2026-07-01 23:48:00 -07:00
hanzo-dev 42c4da4eb4 chore: zip canonical home — hanzoai/zip -> zap-proto/zip@v1.1.0 + one-verb Listen
Move to the ZAP-family canonical framework (zap-proto/zip) and its final API:
app.Listen(cfg.ZAPListenAddr, "http://"+cfg.ListenAddr) — one verb, transport is
the address scheme (ZAP primary + HTTP extra from one call). Free MCP tool surface
rides along at /mcp over both transports. go.sum re-recorded vs the immutable proxy.
Whole tree builds; cloud/zapface/storagelock tests pass.
2026-07-01 23:45:54 -07:00
hanzo-dev c489487998 feat(projectsvc): fork a gallery template into a real project
Add POST /v1/projects/fork — the ONE way to start a project from the Hanzo
starter-kit gallery in-console. The handler reads the ONE embedded templates
catalog (templates.Get; no catalog copy), maps the template's freeform
framework label to the projectsvc build-hint enum, and funnels through the SAME
createProject path POST /v1/projects uses, so slug validation, org scoping, ID
minting, and conflict handling are not duplicated.

- clients/templates: export List()/Get(slug) so projectsvc reads the catalog
  through one door; the HTTP GET handler now uses Get too (DRY).
- clients/projectsvc: extract create -> createProject (the shared internal
  create path); fork.go seeds a CreateProject from the template (name=title or
  override, slug=target or template slug, framework mapped, repo=gallery source)
  and calls createProject; org-scoped (X-Org-Id) exactly like the other routes.
- Framework mapping (mapFramework): Vite wins -> vite; Next.js -> next;
  React -> react; enum names pass through; bare HTML/* -> static.

Tests: end-to-end wire tests over the real route (template->project mapping,
org scoping/isolation, dup 409, missing-slug 400, unknown-template 404) plus a
mapFramework table pinned to the real gallery labels.
2026-07-01 23:41:50 -07:00
hanzo-dev 5d2c99303f feat: serve /v1 over ZAP — zip v0.5.0, real dual transport
zip v0.5.0 un-stubs the ZAP transport, so cloud now serves BOTH transports from
the ONE app: app.Serve(cfg.ZAPListenAddr, cfg.ListenAddr) binds ZAP (primary,
:9653 via CLOUD_ZAP_LISTEN — already in config) alongside HTTP (:8000). The log
already advertised the zap addr; now it is actually bound. Every /v1 route answers
identically over either transport (no RPC registry, routes ARE the ZAP surface).

- go.mod: hanzoai/zip v0.2.1 -> v0.5.0 (+ zap-proto/http v0.1.0 transitively).
- serve.go: app.Listen(http) -> app.Serve(zap, http).

Verified: go build ./... green (whole 54-file zip surface); go vet clean;
cloud + zapface + storagelock + admin tests pass. Prod ZAP port :9653 will be
open (was closed — the stub never bound).
2026-07-01 22:56:37 -07:00
hanzo-dev 82cdb7308b chore: strip casibase/casdoor — cloud is Hanzo-referential, one and one way
cloud is greenfield original (not a casibase fork); the residual casibase/casdoor
names in comments + one type + one error string were off-brand AND contradicted
that provenance (e.g. storagelock's 'casibase-derived cloud-api' lineage story).
De-branded to Hanzo-referential throughout — the {status,msg,data,data2} WIRE shape
is unchanged (console2 depends on it); it is simply OUR /v1 envelope now.

- zapface: casibaseEnvelope type -> envelope; all 'casibase /v1' -> '/v1'.
- storagelock: dropped the casibase-lineage narrative; 'casibase's XORM knob' ->
  'the storage driver knob'; classify string -> 'driverName=postgres'. SQLite is
  the only backend, full stop (no transitional-config language).
- subsystems: iam '(Casdoor)' -> '(Hanzo IAM)'.
- clients/admin: 'casibase envelope' -> '/v1 envelope' throughout.
- tests: de-branded; the integration test's simulated 'casdoor_session_id' cookie
  -> the REAL 'iam_access_token' contract (cookieTokenNames), so it's more faithful.

Verified: go build + go vet clean; storagelock/zapface/clients-admin tests pass.
2026-07-01 22:56:37 -07:00
hanzo-dev 999851104f fix(platform,provisioning): close RED CRIT-2 residual — whitespace-collapse org injectivity
The org identifier was TrimSpace'd at both trust-boundary sites
(middleware_identity.go on claims.Owner + client X-Org-Id, and
provisioning.sanitizeOrg before hashing), so two DISTINCT IAM orgs differing
only by edge/internal/unicode whitespace ('acme' vs 'acme ' vs 'ac me' vs an
NBSP/ZWSP variant) collapsed onto ONE tenant-<slug> namespace / image ref /
bucket / DB — a cross-tenant fold (IAM org name is an unvalidated varchar, so a
fold-sibling is registrable and mints a valid token).

FIX — normalize+VALIDATE at the trust boundary, reject rather than fold:
- cloud.OrgHasUnsafeRune: refuse any org bearing a whitespace / control /
  zero-width-format (Cf) rune. fasthttp OWS-trims header values, so folding
  such an org could never round-trip through transport — rejection (fail
  secure) is the only injective option. Visible case/'.'/'-' still fold
  injectively via the org-slug hash.
- middleware_identity.go: owner is taken verbatim from the validated principal
  (no TrimSpace) and refused if unsafe -> request resolves org-less, every
  tenant() gate fails closed 403. Client X-Org-Id refused likewise.
- provisioning.sanitizeOrg: reject unsafe-rune inputs (defense-in-depth for
  non-header callers e.g. clients/s3) and hash the RAW bytes, never a trimmed
  copy. c.Org() is now the sole tenancy source and injective end-to-end.

Regression tests: {acme, 'acme ', 'ac me', NBSP/ZWSP/BOM/tab variants} ->
distinct-or-rejected, never colliding (provisioning + platform + middleware
JWT-owner path). go build ./... + go vet + affected suites green.
2026-07-01 21:40:57 -07:00
hanzo-devandGitHub ed5749287f feat(crm): native-Go /v1/crm on Base — companies/contacts/opportunities, per-org (#55)
First slice of the unified-backend-go program: a native-Go port of the Twenty
CRM core model (company/person/opportunity standard objects, composites
flattened to scalar columns) mounted at order 131 in the one cloud binary.

- Base/SQLite store ({DataDir}/crm.db), tenant isolation = org column on every
  query (c.Org() from the validated IAM owner claim, HIP-0026). Mirrors
  clients/prompts + clients/eval exactly (the ONE storage pattern).
- Full CRUD for all three entities + per-org summary counts; in-org referential
  integrity (a relation can never point across tenants; errBadRef -> 422).
- /v1/crm/{summary,companies,contacts,opportunities} — /v1 only, no /api.
- Tests: per-org isolation, CRUD round-trip, referential integrity,
  delete-clears-refs, list filters/counts, HTTP round-trip + validation. 7/7 pass.

No proxy to a NestJS backend; this is the thesis (business apps as native-Go
/v1 subsystems on Base) embodied as one working brick.
2026-07-01 20:14:44 -07:00
hanzo-dev 8fdff378a3 fix(platform): close CRIT-1 cmd-injection, CRIT-2 org collision, MED-3 quotas (RED)
/v1/platform (PaaS) — RED do-not-ship findings. Tenancy core untouched.

CRIT-1 — OS command injection in the privileged BuildKit Job:
  launchBuildJob now emits buildctl as EXEC-FORM argv ([]string, no `sh -c`),
  so no shell parses any input. repo.url / dockerfile / git-ref are validated
  (validate.go): https-only URL to an allowlisted git host, no shell/flag
  metachars; safe relative dockerfile (no `..`); safe branch/tag/commit ref
  (no `#`, no metachars). Output image ref is forced server-side — a client
  cannot override --output/--opt. Validation runs at the build choke point AND
  early at createApp (400). red_cmdinj_poc_test.go flipped to a passing guard.

CRIT-2 — sanitizeOrg collision (non-injective) → cross-tenant takeover:
  deleted the lossy platform.sanitizeOrg; tenant()/tenantNamespace()/
  buildImageRef() now use the ONE injective provisioning.SanitizeOrg (DRY,
  reused — commit 01bf3a12). Image ref made injective too: org+app are now
  separate '/'-joined path components (ghcr.io/hanzoai/tenant-<org>/<app>),
  neither slug can contain '/', so (a-b,c) vs (a,b-c) no longer collide.

MED-3 — quotas / replica bounds / shared-build DoS:
  clampReplicas caps replicas to [1,20] (env CLOUD_PLATFORM_MAX_REPLICAS) at
  createApp, applyService, and scaleService (fail-secure default). ensureNamespace
  applies a ResourceQuota + LimitRange per tenant namespace (idempotent).
  launchBuildJob caps concurrent builds per org (default 3, errTooManyBuilds→429).

Tests: cmd-injection blocked (5 vectors), org-slug + image-ref injectivity,
replica clamp (unit+HTTP), namespace quota/limitrange, concurrent-build cap.
go build ./... green; clients/platform + provisioning + s3 tests green.
2026-07-01 19:17:28 -07:00
hanzo-dev 834ebf58f3 templates: read-only starter-kit gallery at /v1/templates (69 templates from hanzoai/gallery; browse + fork/deploy handoff) 2026-07-01 19:13:52 -07:00
hanzo-dev 116df7c7ab prompts: read-only starter catalog at /v1/prompts/catalog (107 prompts, browse+import; org store stays honestly empty) 2026-07-01 19:08:54 -07:00
hanzo-dev b72053d8a8 fix(evals): bound /v1/evals/runs — per-org concurrency + wall-clock deadline (RED MED)
A synchronous run drives up to maxRunItems paired LLM calls against the SHARED
in-process gateway. Two bounds stop one org from degrading every tenant:

- Per-org concurrency cap (maxConcurrentRunsPerOrg=4): a run acquires a per-org
  slot after passing validation; excess concurrent runs fail fast with 429 (never
  queued — queuing just relocates the exhaustion). Slot released on every return.
- Total wall-clock deadline (maxRunDuration=10m): the item loop runs under a
  context.WithTimeout; a run that exceeds it is cancelled, remaining items are
  recorded as honest errors, and the partial summary returns (Scored counts only
  real successes → 502 when nothing scored). A runaway can never pin a request +
  a gateway slot indefinitely.

Also (RED LOW, verified NOT present at 249a136e despite belief): getDataset now
sizes its collection via store.CountItems (SELECT COUNT(*)) instead of loading up
to maxListLimit full item bodies just to len() them (~96MB amplification on a
large dataset).

Tests: TestRunConcurrencyCap (semaphore fill/refuse/release), TestRunDeadline
Bounded (blocking runner + tiny deadline → cancels, 502, honest item errors, no
hang). go build ./clients/eval/ . green, go vet clean, all eval tests pass.
2026-07-01 18:58:41 -07:00
hanzo-dev 468e48f934 fix(evals): HIGH — gate tenant() on validated principal + clone org key (RED)
Two cross-tenant fixes on the /v1/evals API layer (RED review):

1. Principal gate (HIGH): tenant() now requires a non-empty c.User() (X-User-Id,
   set ONLY by SanitizeIdentity from a verified token/session and stripped from
   client input). Its Phase-1 residual RESTORES a client X-Org-Id on the
   NO-principal path (bearer-less / opaque hk-/sk- key / invalid bearer), so
   without this gate a direct-to-pod request 'X-Org-Id: victim' with no auth read
   /wrote/deleted the victim org's datasets (PII golden outputs), scores, traces
   and runs. This is the same trust signal the audit layer uses (actorFromCtx).

2. Buffer-aliasing (correctness on the isolation key): c.Org() is a zero-copy
   view into the fasthttp request buffer, reused after the request ends. The org
   is our tenant KEY and is retained (telemetry events, run records); tenant()
   now strings.Clone()s it so a stored org can never silently mutate into another
   value once the buffer is recycled (was manifesting as run scores landing under
   a corrupted org id).

red_cap_test.go TestRed_ForgedHeaderCannotCrossTenant now sends a no-principal
X-Org-Id:victim request asserting 403; eval_test.go asserts tenant()='' without a
validated principal. go build ./clients/eval/ . green, go vet clean, all eval
tests pass.
2026-07-01 18:58:41 -07:00
hanzo-dev 1579716b34 feat(evals): native /v1/evals over Base+datastore, retire console proxy
Replace the Langfuse-fork proxy (crash-looping console P1012) with a native,
org-scoped evals system. Storage split per CTO directive:
- metastore (store.go): Base/SQLite, per-org config — datasets, dataset-items,
  evaluators, score-configs, dataset-run defs. Composite (org,id) keys so an id
  is never a cross-org global key (no existence oracle; two orgs may reuse ids).
- telemetry (telemetry.go): datastore/ClickHouse MergeTree, append-only traces +
  scores-as-events; every read binds org as a named param + LIMIT; behind an
  interface with an in-memory impl for tests. Reuses the Langfuse v3 CH shapes.
- runner (runner.go): pluggable EvalRunner (Complete + Judge); gateway runner is
  the spine (any model/judge, no token cap), DO can drop in as an adapter later.

Tenant isolation is c.Org() (validated bearer owner) ONLY — never client
X-Project-Id/X-Org-Id (the cross-tenant break the old proxy shipped). Score
integrity: NaN/Inf rejected, values validated against the org's score-config,
categorical labels checked against the allowed set. Content caps + name regex
guard injection/traversal/amplification.

24 tests pass: metastore + HTTP cross-tenant isolation, forged-header guard,
score-integrity, content caps, run orchestration over a stub runner.

/v1 only. TDD (go test green). gofmt+vet clean. go build ./... green.
2026-07-01 18:58:41 -07:00
hanzo-dev e836e24f0f cloud(s3): drop CLOUD_ prefix on the shared S3 env family (S3_*)
One clean env family for the ONE shared S3 access path (clients/s3admin)
and the provisioning control plane. Rename across s3admin, clients/s3,
projectsvc, and provisioning — code, comments, log/error strings, tests:

  CLOUD_S3_ADMIN_ENDPOINT   -> S3_ADMIN_ENDPOINT
  CLOUD_S3_ADMIN_ACCESS_KEY -> S3_ADMIN_ACCESS_KEY
  CLOUD_S3_ADMIN_SECRET_KEY -> S3_ADMIN_SECRET_KEY
  CLOUD_S3_SECURE           -> S3_SECURE
  CLOUD_S3_REGION           -> S3_REGION
  CLOUD_S3_PUBLIC_ENDPOINT  -> S3_PUBLIC_ENDPOINT
  CLOUD_S3_PUBLIC_SECURE    -> S3_PUBLIC_SECURE

The cloud CR (universe 9e57d71d) already stamps BOTH the old and new
ACCESS_KEY/SECRET_KEY spellings from the s3-credentials secret, so this
image roll is drop-in: old names stay populated until the new image
lands, then the S3_* names take over. Everything else resolves from code
defaults (s3.hanzo.svc:9000 / us-east-1 / s3.hanzo.ai). go build + vet +
tests green across all four packages.
2026-07-01 18:40:51 -07:00
hanzo-dev 8be42c8b6c feat(org): per-org envelope encryption — SQLite ciphertext at rest, wired live
No TODO, no placeholder: the "full customer encryption" brick is real and wired
into the Replicator. Each org's SQLite snapshot is sealed with a distinct
AES-256-GCM key DERIVED from the KMS master via HKDF(master, label, orgID) — the
master never leaves the process, per-org keys are in-memory only. The SeaweedFS
object is ciphertext; orgs are cryptographically isolated (orgID bound as GCM
AAD, so a blob can't be replayed under another org); rotating the master re-keys
everything. Nonce is derived from (key, plaintext) so identical content seals
identically — the Replicator's version-skip keeps working under encryption.

Wired: NewReplicator(..., WithEncryption(cipher, orgID)) → Push seals, Pull opens.
Omit the option and the DB is stored in the clear (local dev only).

Pure Go stdlib (crypto/aes, crypto/cipher, crypto/hmac, crypto/sha256, crypto/subtle) —
package org stays dependency-free + testable. Tests: round-trip, wrong-master reject,
cross-org isolation, tamper detection, deterministic-per-content, master-rotation
rekey, and an end-to-end encrypted Replicator (stored bytes are ciphertext, reader
with the key restores plaintext, no plaintext leak without the key).
2026-07-01 17:57:50 -07:00
hanzo-dev c7e22c5675 harden(platform): bind custom ingress domains to the caller's org (RED — domain hijack)
A custom domains[] entry was rendered straight into the operator Service CR
ingress.hosts, so a tenant could claim another org's host or a Hanzo apex
(api.hanzo.ai) and the operator would serve an Ingress for it. Require every
custom host to be under the caller's OWN '<org>.<sitesHost>' subtree (e.g.
maxpower may only claim *.maxpower.hanzo.app); anything else is refused 501
(verified arbitrary custom domains are phase-2 domain CRUD). Closes the
cross-tenant/apex domain-hijack vector reachable in the first slice. +2 tests
(unit + HTTP); 23 tests green.
2026-07-01 16:46:39 -07:00
hanzo-dev af218ac1ad fix(platform): require a validated principal in tenant() (RED HIGH)
/v1/platform mutates cluster state (operator Service CRs + BuildKit Jobs in
tenant-<org>) — more consequential than a data read — so trusting X-Org-Id alone
would let a direct-to-pod caller forge X-Org-Id:victim with NO bearer and
deploy/read into another tenant (SanitizeIdentity's documented Phase-1 residual).
tenant() now gates on c.User() (X-User-Id, set ONLY for a validated principal),
mirroring the Red-hardened clients/s3.tenant. Proven live: forged X-Org-Id with
no token -> 403 (was 200); real JWT -> 200; forged header + real token ->
validated owner wins. Every legitimate caller (gateway/console BFF) carries a
user-bound bearer, so no real client breaks.
2026-07-01 16:36:01 -07:00
hanzo-dev d604351c90 fix(eval): tenant() must use the sanitized org, never client X-Project-Id (cross-tenant)
RED MED-1 (cross-tenant eval-score read). eval.tenant() scopes the console API
key pair (console-pk-{org}/console-sk-{org} in KMS) and was PREFERRING the raw
`X-Project-Id` request header over the bearer-pinned org, then feeding it to
resolveKeys(). X-Project-Id is a project sub-scope WITHIN an org and is
DELIBERATELY excluded from SanitizeIdentity.authorityHeaders (client-controllable,
per middleware_identity.go). So a caller who set `X-Project-Id: victim-org` made
resolveKeys fetch ANOTHER org's console-pk/console-sk from KMS and read that org's
eval scores/datasets — a cross-tenant break. Reading a raw X-Org-Id header was
equally unsafe (SanitizeIdentity strips a client copy and re-mints c.Org() from
the token).

Fix: tenant() returns ONLY c.Org() — the org SanitizeIdentity pinned from the
validated bearer owner (HIP-0026) — the same authoritative selector
agents/prompts/provisioning use. X-Project-Id no longer influences KMS key
selection anywhere in the evals facade (it was used nowhere else). Per-PROJECT
key scoping, if ever needed, must derive the project from a membership check UNDER
c.Org(), never a raw sub-scope header (Phase-2; keys stay org-scoped today).

The console2 BFF (app/cloud) was the sole compensating control (it drops
X-Project-Id without forwardScope); this closes the defect AT THE SOURCE so
isolation no longer hangs on one omitted proxy header. New test
TestTenantIgnoresClientProjectID pins that a forged X-Project-Id never becomes the
tenant. go build ./clients/... + go test ./clients/eval/... green.
2026-07-01 16:24:12 -07:00
hanzo-dev 9470345d0c feat(platform): native per-org /v1/platform PaaS subsystem (Dokploy port, Goa-designed)
Port the standalone Dokploy (platform.hanzo.ai) tRPC backend into the unified
cloud binary as clients/platform, mounted at /v1/platform (HIP-0106). Per-org,
IAM-validated, Base/SQLite store; the deploy path writes an operator hanzo.ai/v1
Service CR into the caller's OWN tenant-<org> namespace (derived from the
validated X-Org-Id, never a request input) and the operator reconciles it. Git
apps build via an in-cluster BuildKit Job (arcd model); image apps deploy
directly. Complements clients/paassvc (admin fleet board) and clients/projectsvc
(static sites) with the container-app PaaS.

Goa is the design-first contract (clients/platform/design, goa gen -> OpenAPI 3);
the runtime is native zip handlers (one router, behind SanitizeIdentity) — the
generated net/http server is deliberately NOT mounted so the identity trust
boundary is not routed through the fiber<->net/http adaptor.

- store.go: projects/applications/deployments/builds, org column tenancy
- k8s.go: tenant-<org> namespace derivation + Service CR apply/scale/delete + BuildKit Job
- platform.go: Mount + project/app CRUD + tenant() gate + health
- deploy.go: deploy/start/stop + deployment history/logs, fail-closed (no fabricated success)
- 20 tests: store CRUD, cross-tenant isolation (RED bar), fail-closed deploy,
  fake-cluster deploy-into-tenant-ns success, secret-env rejection

go build ./... green; go test ./clients/platform/ green.
2026-07-01 16:20:48 -07:00
hanzo-dev 01bf3a12fe fix(s3,provisioning): close Red re-review findings — control-plane forge + injective org slug
Red re-review (0 critical, 1 high, 1 med, 1 low): the s3 data-plane HIGH was
confirmed CLOSED, but Red found the same forge open on the provisioning control
plane (worse: destroy DB + credential exfil), proved my org-fold dispute WRONG
with a reachable cross-tenant collision, and asked to lock the fix's dependency.

- [HIGH] provisioning.tenant() now requires ctx.User() (provisioning.go:454) —
  same gate as the s3 fix. Without it, an in-cluster caller could forge
  'X-Org-Id: victim' with NO bearer and POST /v1/sql (allocate a DB in the
  victim's namespace + receive its connection string + password), DELETE
  /v1/sql/:name (destroy the victim's DB), or enumerate resources. SanitizeIdentity
  restores a forged X-Org-Id on the no-principal Phase-1 path but strips X-User-Id;
  gating on it refuses only the anonymous forge. Test:
  TestForgedOrgWithoutPrincipalRefused (forged org + no principal -> 403 across
  POST/DELETE/GET, provisioner never runs).
- [MED, dispute WITHDRAWN — Red was right] provisioning.sanitizeOrg is now
  INJECTIVE (provisioning.go:468): identity on a clean [a-z0-9-] slug, else the
  fold + '-'+16hex SHA-256(raw owner) — mirroring iam/object/orgdb.go:orgSlug.
  The old lossy fold collapsed 'Acme'/'acme' and 'team.a'/'team-a' onto one slug,
  and since the whole tenant->bucket/DB namespace hashes THAT slug, two distinct
  orgs shared one physical namespace (reachable: the IAM org name is a varchar
  with no shape validator, so a fold-sibling is registerable + mints a valid
  token). Tests: TestSanitizeOrgInjective (the exact collisions no longer collide,
  incl. derived orgHash) + updated TestSanitizeOrg.
- [LOW] locked the s3/provisioning fixes' cross-file dependency:
  TestSanitizeIdentity_AnonPathHasNoUserId asserts a client-forged X-User-Id does
  NOT survive the anon path (ctx.User()=="") while X-Org-Id does — so a future
  refactor that restored X-User-Id fails this test first.

All fold consumers (orgHash -> SQL/KV/CH/S3 physical namespaces) inherit the
injective slug through the ONE sanitizeOrg. go test green (provisioning + s3 +
s3admin + root identity); cmd/cloud builds; gofmt/vet clean; zero go.sum drift.
2026-07-01 15:40:11 -07:00
hanzo-dev 2473043d3c fix(s3): address Red review — require validated principal, harden keys, shorten presign TTL
Red adversarial review (0 critical, 1 high, 3 med, 4 low). Fixes:

- [HIGH] tenant() now REQUIRES a validated principal (ctx.User()/X-User-Id).
  SanitizeIdentity restores the client's raw X-Org-Id on the no-principal
  'Phase-1 data path' but leaves X-User-Id empty; a pure data plane trusting
  X-Org-Id alone let an in-cluster caller (co-namespace pod) forge
  'X-Org-Id: victim' with NO bearer and get cross-tenant object CRUD. Gating on
  X-User-Id refuses ONLY that anonymous forge path — every legitimate caller
  reaches s3 through the console BFF /cloud proxy which mints a user bearer, so
  no real client breaks. Object storage never serves an unauthenticated
  principal. Test: TestForgedOrgWithoutPrincipalRefused (forged org + no
  principal -> 403 across the full route surface).
- [MED] presign TTL 15m -> 5m: bounds a minted capability's post-revocation
  lifetime (presigned URLs have no server-side revocation; the TTL IS the
  window). Documented the unwired-rate-limiter platform gap.
- [LOW] cleanKey rejects control bytes (\x00-\x1f) + backslash: a null byte
  serializes as %00 (C-string truncation risk for a downstream consumer) and
  '\' is a non-Go path separator. Tests extended.
- [LOW] friendlyBucket re-validates the recovered name against bucketNameRE:
  a prefixed-but-non-conforming bucket (only reachable out-of-band, never via
  createBucket) is treated as not-owned, so listBuckets never echoes an
  unaddressable name. Test added.
- Documented the ESCALATED residuals (not subsystem-fixable): single omnipotent
  SeaweedFS identity (isolation is app-layer only until STS/scoped creds), and
  the intentional S3-vs-KMS org-normalization divergence (S3 must fold to match
  provisioning's bucket naming; KMS keys secrets by exact owner).

Verdict was fix-then-ship; no critical, HIGH is bounded (not internet-reachable,
gateway strips X-Org-Id at the edge). go test ./clients/s3/... green (20 tests);
cmd/cloud builds; gofmt clean; zero go.sum drift.
2026-07-01 15:40:11 -07:00
hanzo-dev fbf3dbaca3 feat(s3): native org-scoped /v1/s3 object-storage file manager
Adds the DATA plane over the shared SeaweedFS S3 gateway as /v1/s3/* on the
unified cloud binary (HIP-0106), the companion to clients/provisioning's s3
CONTROL plane. One console, one backend — no external s3.hanzo.ai UI.

- clients/s3admin: the ONE shared S3 access path. Both projectsvc/blob (deploy
  blob store) and the new s3 subsystem build their minio client here from the
  SAME CLOUD_S3_ADMIN_* creds (DRY — no second S3 client anywhere). Leaf pkg
  (minio-go only), so no import cycle. Separate public-host client mints
  presigned URLs a browser can follow.
- clients/projectsvc/blob.go: refactored to build its minio client via s3admin
  (was inline minio.New). Existing projectsvc tests unchanged + green.
- clients/s3: /v1/s3/{health,buckets,buckets/:bucket,buckets/:bucket/objects,
  buckets/:bucket/objects/*}. Org-scoped bucket-per-org via the EXACT
  provisioning.BucketName scheme (exported) = bucketName(physicalName(org,name)):
  org-hash prefixed AND '_'->'-' folded to a DNS-safe S3 name — so a bucket
  provisioned via POST /v1/s3 {name} is browsable here AND a bucket created here
  is a valid S3 name (the raw physicalName has underscores S3 rejects). Upload/
  download = presigned PUT/GET URLs (browser goes direct to S3; admin cred never
  leaves the server; object key path-clean-guarded; time-boxed 15m). Fail-closed
  503 without creds. Registered 's3svc' order 118 (< provisioning 120) so the
  static /v1/s3/buckets + /v1/s3/health win Fiber's first-match scan ahead of
  /v1/s3/:name and the generic-health route does not shadow the real probe.
- subsystems.go: one-line blank import.

Tests: go test ./clients/s3/... ./clients/s3admin/... green — fail-closed 503,
org 403, route-ordering (s3 owns /v1/s3/buckets + /health, not provisioning
:name), bucket-name + object-key traversal 400, cross-tenant physical-name
isolation, AND bucket-name consistency with provisioning + DNS-safety (no '_').
Zero go.sum drift (minio-go already a dep). cmd/cloud builds.
2026-07-01 15:40:11 -07:00
hanzo-dev 6b4f399143 chore(deps): bump ai -> 296a9e9b (ai ledger owns cloud_usage only; drop colliding observations write) 2026-07-01 15:17:04 -07:00
hanzo-dev 08e2b1b0a9 chore(deps): bump ai -> a5a199e9 (o11y ledger reaches ClickHouse directly)
Pulls hanzoai/ai#a5a199e9: the cloud_usage/observations ledger now uses a direct
clickhouse-go/v2 client (object.InitDatastore in the shared Bootstrap) instead of
the dead ZAP 'datastore peer'. Fixes GET /v1/get-cloud-usages 'datastore peer not
connected'. Requires DATASTORE_ADDR/USER/PASSWORD env (wired on the cloud CR).
2026-07-01 14:58:40 -07:00
19a19253bd fix(provisioning): return PUBLIC endpoints, never the internal .svc host (#53)
Tenants were shown the internal admin address (e.g. vector.hanzo.svc:6333) in
create/get/list responses + the connectionString — unusable from an app and a
leak. Add publicEndpoint(kind): HTTP kinds (vector/search/docdb/s3) → the unified
api.hanzo.ai gateway (/v1/<kind>/*); native-wire DBs → <kind>.hanzo.ai on the
native port (sql.hanzo.ai:5432, kv.hanzo.ai:6379, datastore.hanzo.ai:8123). So a
customer gets a real, routable endpoint for their app + hanzo.app. Per-kind
override via PUBLIC_<KIND>_HOST/_PORT. The DSN host:port is remapped too.

Co-authored-by: zeekay <z@zeekay.io>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-07-01 13:46:19 -07:00
hanzo-dev f8bfeae427 fix(prompts): self-heal from the legacy clients/prompt schema on shared prompts.db
Live 1.786.5 returned 500 "no such column: id" on GET /v1/prompts. The removed
clients/prompt facade (shipped in 1.786.4) had created a `prompts` table in the
SAME {DataDir}/prompts.db with a versioned-rows layout that has NO `id` column.
clients/prompts' `CREATE TABLE IF NOT EXISTS prompts` no-ops on that existing
table, so every `SELECT id,... FROM prompts` failed against the persisted PVC.

migrate() now inspects the `prompts` table via PRAGMA table_info; when it exists
but lacks `id` (the legacy signature) it drops the legacy pair and rebuilds the
forward schema. The legacy rows carry no durable product data (the facade shipped
one release; the console Compute pages never wrote through it), so this is
forward-only and idempotent — once `id` exists it never fires again.

TDD: TestMigrateSelfHealsFromLegacyPromptSchema seeds the exact legacy schema +
a row, opens the store over the same file, and asserts List/Upsert succeed. Green.
2026-07-01 13:42:56 -07:00
hanzo-dev 0a37ebe31d Merge blue/cloud-tenant-endpoints: per-org /v1/{prompts,agents,functions}
Mounts the red-approved (3 rounds) per-org product control planes natively
in the unified cloud binary (the "all products in the cloud binary" thesis):

  - clients/prompts   order 126  /v1/prompts/*    versioned prompt library
  - clients/agents    order 127  /v1/agents/*     autonomous agents + runs
  - clients/functions order 128  /v1/functions/*  serverless fns + invoke

All three are org-scoped by the gateway-minted X-Org-Id (HIP-0026), fail
closed when it is absent, and persist to a per-tenant modernc.org/sqlite
store under CLOUD_DATA_DIR (no CGO). Each ships adversarial red_*_test.go
coverage (all green).

DRY reconciliation with main: main had independently added clients/prompt
(singular) also registering "prompts" for /v1/prompts. Two subsystems both
named "prompts" would double-append to cloud.Registry and double-mount the
same routes. blue's clients/prompts is the red-approved superset (adds
/v1/prompts/metrics — which console2's PromptsModule consumes — plus DELETE,
strict fail-closed X-Org-Id, and a reserved-name guard), so it becomes the
ONE owner of /v1/prompts/*; the earlier clients/prompt facade is removed.

Build green (CGO_ENABLED=0 go build ./...); prompts/agents/functions +
root + cmd/cloud tests all pass.
2026-07-01 13:16:58 -07:00
hanzo-dev 7b5e9bf642 feat(prompts): serve /v1/prompts from a native SQLite store (kill the console loop)
The console (Langfuse image 3.159.55) 307-redirects /api/public/v2/prompts →
/v1/prompts, delegating prompts TO cloud. promptsvc used to proxy the other
way → redirect loop → 500. Port prompts NATIVE: an org-scoped, versioned
prompt registry in a single SQLite file (base pattern, modernc driver, WAL),
list/get/create. No proxy, no loop, all-SQLite by construction. Verified:
GET /v1/prompts → {data:[]}, POST creates v1, GET lists it, GET /:name
returns versions. Honest-empty when none.
2026-07-01 13:06:23 -07:00
hanzo-dev 0ad5852438 feat(kms): embed luxfi/kms in cloud (/v1/kms/*), fail-secure sealed store
HIP-0106 'all Go embeds in cloud': the KMS secrets plane runs in-process
in the cloud binary instead of the standalone Infisical fork.

- clients/kmsembed: cloud-free Client (implements types.KMSClient) over a
  luxfi/zapdb SecretStore. AES-256-GCM envelope (per-secret DEK sealed
  under a 32-byte master KEK); plaintext never touches disk. New() uses a
  fail-SECURE 3-way store-open (keyed→encrypted on-disk; no-key+no-store→
  ephemeral in-memory, no plaintext registry; no-key+existing-store→fail
  loud, never silently shadow encrypted data). Sign fails closed when no
  MPC backend is co-hosted. One place for key-shape validation.
- clients/kms: Fiber subsystem mounting /v1/kms/* (order 10), org-scoped
  CRUD via cloud's auth; /v1/kms/health + /v1/kms/config.
- build.go pickKMSClient: Enabled('kmssvc') → in-process kmsembed.New,
  fail-closed to DisabledKMS on error (never nil).
- config: CLOUD_KMS_MASTER_KEY_REF / CLOUD_KMS_MPC_ADDR / _VAULT_ID.

Reviewed blue+red: 40 tests (7 build + ~33 adversarial), gofmt/vet clean,
go.sum zero-diff. Red verdict: ship (fail-closed + confidentiality
invariants hold across the full key/store matrix).
2026-07-01 12:44:33 -07:00
hanzo-dev f1330eef74 chore(deps): bump ai → v1.789.0 — unify iam hotfix into main
Brings the released ai v1.789.0 onto main: it has BOTH the V1IamRewriteFilter
(the /v1/iam/* account-surface fix shipped off-main as the 1.785.35 hotfix) AND
the canonical X-Project-Id/X-Environment/X-User-Id header sweep. Resolves the
divergence — main is now the one lineage (prompts + bot + headers + org refactor
+ SeaweedFS replication + iam fix). Build + embed/identity tests green.
2026-07-01 12:24:46 -07:00
hanzo-dev e46d654521 refactor(org): tenant IS the organization — per-org writer pinning + SeaweedFS replication
Drop the confusing "tenant" concept: in Hanzo the ORGANIZATION is the tenant
boundary (identity, billing, per-org SQLite are all org-scoped). Renamed
internal/tenant → internal/org and made ownership explicitly PER-ORG: one replica
writes ALL of an org's databases (root + per-project + per-user), for locality +
intra-org consistency; the org moves as a unit on failover.

- owner.go: Owner/IsOwner/Replicas over Rendezvous (HRW) hashing of orgID — every
  replica computes the same writer-owner from the same membership, NO coordinator.
- membership.go: live replica set via a pluggable Source (StaticSource/CLOUD_REPLICAS
  now; K8s Endpoints / zapd gossip later); lock-free AmOwner hot-path.
- replica.go: Replicator Push (owner → SeaweedFS) / Pull (reader ← SeaweedFS,
  version-skip) + DBPath (orgs/<org>[/<scope>]/<service>.db, HIP-0302).
- vfsstore.go: object store bound to hanzoai/vfs (SeaweedFS) — NO minio, NO external
  S3 SDK. hanzoai/sqlite + hanzoai/base back the local DB handle (the DB interface).

Package is PURE stdlib (local vfsClient interface, zero cloud deps) so it builds +
tests without the dep tree. 16 tests pass: determinism, single-owner, even
distribution (±35%/50k), exact minimal-reshuffle, ordered failover, push/pull
round-trip, skip-unchanged, ownership handover, DBPath layout, vfs adapter. gofmt clean.
2026-07-01 11:07:23 -07:00
hanzo-dev 63142078c7 feat(bot): mount /v1/bot/* → bot-gateway; name datastore/docdb by the primitive
- botsvc (order 143): reverse-proxies /v1/bot/* to the in-cluster bot-gateway,
  stripping the /v1/bot prefix (the gateway serves bare paths: /v1/bot/health →
  bot-gateway /health) and forwarding the gateway-minted identity headers. The
  console2 Bot module's /v1/bot/health probe now resolves instead of 404.
  Verified e2e against the real bot-gateway: /v1/bot/health → 200
  {"service":"bot","status":"ok"}.
- provisioner: rename the datastore/docdb provisioners by the HANZO PRIMITIVE
  (datastoreProvisioner/newDatastore, docdbProvisioner/newDocdb) not the backing
  tech — the ClickHouse/MongoDB driver imports + wire-protocol schemes stay
  (functionally required), but the type names read as the primitive.

Note: /v1/s3, /v1/datastore, /v1/docdb are ALREADY mounted (provisioning loops
its 7 kinds); /v1/memory is served by the ai monolith. functions has no backend
— left honest (not fabricated).
2026-07-01 10:49:09 -07:00
hanzo-dev 2bdc066c6f feat(prompts): mount /v1/prompts in the unified binary (console Langfuse facade)
The console2 Prompts module hit GET /v1/prompts → 404 "not routed on this
host" because no subsystem owned the route. Add promptsvc: a thin facade
(order 144, mirrors evalsvc) proxying list / get-by-name / create to the
console public prompts API (/api/public/v2/prompts) under the project-scoped
console key pair (HTTP Basic) — the same console + auth the eval facade
already composes. No prompt logic reimplemented; the console owns storage,
versioning, and labels.

Verified locally: the binary boots with "prompts surface mounted", GET
/v1/prompts routes to promptsvc (503 honest "no console API key" in the
keyless test env, not a 404), /v1/prompts/health → 200 (no route shadow).
In prod the console-keys secret is already wired (evalsvc), so prompts
resolve real data. eval tests + embed tests stay green.
2026-07-01 10:41:25 -07:00
hanzo-dev 29af637039 feat(tenant): rendezvous-hash owner — coordination-free per-tenant writer pinning
The load-bearing primitive of the horizontally-scalable OSS cloud (Hanzo V8).
Every replica of the unified binary computes the SAME writer-owner for a tenant's
per-tenant SQLite from the SAME membership set — via Rendezvous (HRW) hashing —
so there is NO election, NO lock service, NO discovery. This removes the whole
"who finds/owns/reaches service X" plumbing class for tenant state:

- Owner(tenant, members): deterministic, order-independent, exactly one owner.
- IsOwner(tenant, self, members): the per-write hot-path check.
- Replicas(tenant, members, n): owner + ordered failover successors (pre-warm S3).

HRW gives minimal reshuffle on membership change (only a departed replica's ~1/N
tenants migrate; the rest stay put) — cheap rolling deploys + scale-out. Pure Go
(crypto/sha256, no deps). 6 tests: determinism, single-owner, even distribution
(±35%/50k), minimal-reshuffle (exact), ordered failover. All pass; gofmt clean.

Wires into: owner holds the SQLite WAL (1 writer + N readers), streams WAL to
SeaweedFS/S3 (HIP-0107); non-owners read the S3 copy or forward strong writes.
Per-tenant envelope encryption (DEK wrapped by KMS master) makes the S3 file
ciphertext — tenants crypto-isolated. Membership feeds from K8s Endpoints / zapd.
2026-07-01 10:25:02 -07:00
hanzo-dev 104e034f66 chore(deps): bump ai → X-User-Id canonical identity header (drop X-IAM-*)
Pulls hanzoai/ai 56a55d1c so the unified binary's monolith reads the
canonical X-User-Id (cloud middleware_identity already injects it) instead
of the never-sent X-IAM-User-Id. Completes the X-IAM-* → canonical sweep
(org/project/env/user) in the compiled-in monolith. Builds + tests pass.
2026-07-01 10:16:18 -07:00
hanzo-dev ea8e4b61d7 chore(deps): bump ai → project/env canonical-header fix (X-Project-Id/X-Environment)
Pulls hanzoai/ai 7aab19aa into the unified binary so the monolith's
tenant-context filter reads the canonical X-Project-Id / X-Environment
(was X-IAM-*, never sent → project+env scoping was empty across ~200 /v1
routes) + the CORS allow-list accepts them. Pseudo-version pending the ai
v1.788.1 release tag; re-pin to the clean tag on CI cut. Full binary
builds, embed + identity tests pass.
2026-07-01 10:11:56 -07:00
hanzo-dev 5ebb43dabe fix(tenancy): read canonical X-Project-Id for project scope (was X-IAM-Project-Id)
evalsvc.tenant() read `X-IAM-Project-Id`, which nothing sends — console2
stamps the canonical `X-Project-Id` — so a selected project always fell
through to org-level and project selection scoped ZERO backend calls.
Switch the reader to `X-Project-Id` (one canonical header, per the
one-way rule); resolveKeys already accepts the project slug. Update the
identity-sanitizer comment to name the canonical sub-scope.

Build green, eval + identity tests pass.
2026-07-01 09:51:39 -07:00
hanzo-dev 2772cc4623 refactor(console): one console path, no build tags — delete dead clients/console
The repo carried TWO console embeds from parallel work: webui.go (wired in
Serve via mountConsole, no build tag — the working one) and clients/console
(a second take gated by //go:build cloud, imported by nobody after the earlier
build fix). The tag hid it from a normal build and the stale bundle doc comment
made it look like the whole binary needed -tags cloud. It never did.

- Delete clients/console/ — dead duplicate (unimported, tag-excluded, would
  double-mount "/"). Zero //go:build cloud tags remain in the repo.
- subsystems.go: correct the doc comment — subsystems register unconditionally;
  plain `go build ./cmd/cloud` (no tags) links and mounts the full set. Drop the
  now-stale clients/console note.

One console path (webui.go), builds normally. Verified: go build ./cmd/cloud
(no tags) → 427MB binary, go vet clean.
2026-07-01 09:50:02 -07:00
hanzo-dev bbf5094621 fix(deps): restore 5 drifted luxfi go.sum h1 hashes (canonical sum.golang.org)
The audit-trail commit f9b400cb rewrote 5 luxfi h1: module-zip hashes
(age, keys, pq, precompile, zap) to non-canonical values recorded under a
local GOPRIVATE/GONOSUMDB env, breaking 'go mod download' in the release
Docker build (checksum-DB SECURITY ERROR). go.mod is byte-identical to the
last-green build 55eef30e, so restore its go.sum. All 5 now match
sum.golang.org. No code change.
2026-07-01 09:23:05 -07:00
hanzo-devandGitHub f9b400cb8c feat(cloud): compliance-grade audit trail — tamper-evident, append-only, live (v1.785.34) (#51)
* fix(deps): reconcile 5 drifted luxfi go.sum hashes (age keys precompile pq zap)

These 5 luxfi modules were re-published under the same version tags (monorepo
re-tag); every local + CI module cache and the proxy agree on the new zip
hashes while the committed go.sum still pinned the old ones, so ALL builds fail
with a checksum-mismatch SECURITY ERROR. Reconcile go.sum to the hashes every
source agrees on (what go mod tidy would write). GONOSUMDB already trusts luxfi
(fetch direct). Pre-existing drift, orthogonal to the audit feature; needed to
build.

* feat(cloud): compliance-grade audit trail — tamper-evident, append-only, live

FedRAMP AU-* / SOC 2 CC-* audit control for the unified cloud binary. Every
security-relevant request against this binary is captured as a structured,
hash-chained record in an append-only store the app can only INSERT into, and
queryable through the global-admin-gated /v1/admin/audit surface.

WHAT

- audit/ package (record + chain + store + redact + query/verify), no route
  knowledge, pure security logic:
  * record.go — the AU-3 event model (actor/action/resource/auth/outcome/
    source-ip/ua/request-id/before-after) + the hash-chain math:
    hash = SHA256(canonical(record, hash+prevhash zeroed) || prevHash),
    genesis-anchored, DRY (add a field → covered by the hash automatically).
  * store.go — a single serialized Recorder (mutex + SQLite MaxOpenConns(1))
    owning the chain head; INSERT-only SQLite primary ({DataDir}/audit.db,
    zero-loss, synchronous) + optional best-effort ClickHouse mirror. Restart
    recovers the head so the chain continues (never forks).
  * query.go — filtered Query (parameterized; org/actor/action/resource/result/
    time) + Verify (walks the chain, recomputes every hash, reports the exact
    seq where a tamper/delete/reorder first breaks it).
  * redact.go — secret-key denylist (deny-by-key-name, recursive, fail-closed)
    for the before/after an explicit emit point supplies.

- audit_middleware.go (cloud pkg) — the ONE place every security-relevant
  request is recorded (decomplected: one predicate, every route). Sits AFTER
  SanitizeIdentity (validated, unforgeable actor/isAdmin) and BEFORE BillingGate
  (so billing 402/503 + admin 403 denials are audited too). Captures METADATA
  ONLY — never request/response bodies — so a secret in a body can't leak.
  Records mutations + all /v1/admin/* + all 401/403. Fails the request CLOSED
  (503) if the trail write fails (AU-5). Resolves the effective status from a
  returned *zip.HTTPError so error-returning denials are audited.

- audit_mirror.go — ClickHouse MergeTree OLAP mirror (insert-only by engine),
  best-effort projection for fleet retention/query. Driver already in go.mod.

- clients/admin/audit.go — rewires GET /v1/admin/audit to cloud's REAL store
  (was an IAM get-records proxy; kept as a federated fallback) + adds
  GET /v1/admin/audit/verify. Both behind the existing global-admin s.guard.

TESTS (all real, on-disk SQLite, no mocks)
- audit/: chain seals+links, verify passes clean, DETECTS field-tamper /
  deletion / reorder (out-of-band UPDATE/DELETE on a 2nd connection), restart
  continues the chain, concurrent appends stay gapless+verified (-race), redact
  strips secrets + fails closed, SQL-injection filter is inert.
- cloud/: middleware records a mutation with validated identity, audits a 403
  denial, SKIPS safe reads, audits admin reads, NEVER captures a secret-bearing
  body, no-op when unconfigured, fails closed on write error.
- clients/admin/: /v1/admin/audit returns real records + integrity summary,
  filters, verify endpoint, 403 without global-admin (no data leak), nil-store
  fallback.

THREAT MODEL
- Forge actor/admin: impossible at request level (SanitizeIdentity strips
  X-User-IsAdmin, actor from validated JWT).
- Forge the chain: an out-of-band edit re-hashes differently; keeping the chain
  valid requires recomputing the whole suffix — bounded by an externally-pinned
  head (Head()) for AU-9 (tail-truncation detection). Documented.
- Skip the middleware: mounted at the compose root before MountAll; the /zap
  plane replays through the same Fiber app (all middleware), so no bypass.
- Fail-closed is POST-RESPONSE: prevention is the AC layer (runs before the
  action); the trail is detection/accountability. Documented precisely.

Store is a compliance control: empty DataDir is a hard boot error unless
CLOUD_AUDIT_DISABLED=true (explicit opt-out). Secrets from env/KMS only; no
plaintext credential ever enters a record.

* harden(audit): scrub credential-shaped path segments + expand redaction denylist

Defense-in-depth from self-review before adversarial handoff:
- scrubCredentialSegments/scrubToken: a token that ever rides in a URL PATH
  (an hk-/sk-/pk-/fw_/hz_ key, reusing isAPIKey) is replaced with a marker in
  both Record.Path and resource.ID, so a secret in the path is never recorded
  verbatim. Normal identifiers (:name/:slug/:id/uuid/numeric) pass through.
  Proven by TestAudit_ScrubsCredentialInPath.
- Redaction denylist gains passphrase, privkey, social_security, phrase (covers
  seedPhrase/recoveryPhrase) — closing the key-name gaps found by enumerating
  real credential field names. TestRedact_StripsSecrets now asserts them.

* harden(audit): close raw-secret leak in path/resource-id/user-agent

Self-review PoC found a real residual leak beyond prefixed keys: a raw
high-entropy secret (64-hex, or a JWT) in the URL path — and a bearer/key in
the client User-Agent — were recorded verbatim (isAPIKey only matched
hk-/sk-/pk-/fw_/hz_ prefixes). Closed:
- scrubToken now also catches JWTs (eyJ + two dots) and long unbroken
  high-entropy alphanumeric runs (>=32, mixed, no separators) — a raw API
  key/hex secret. UUIDs (hyphens), slugs, names, emails, numeric ids pass
  through (TestScrubToken_NoFalsePositives).
- scrubFreeText scrubs credential-shaped words from the User-Agent (splits on
  space/=/;/,) and caps length at 512. Normal UA prefix preserved.
Proven: TestAudit_ScrubsCredentialInPath (prefixed+raw-hex+JWT),
TestAudit_ScrubsSecretInUserAgent. Query-string secrets already safe (c.Path()
excludes the query string).

* fix(audit): close audit-evasion via /health suffix on mutations (SECURITY)

Self-review PoC found a real evasion: isSecurityRelevant skipped ANY path
ending in /health, so a mutating POST /v1/admin/orgs/x/health (wildcard route
or an attacker-named segment) slipped past the audit trail entirely — the
worst class of bug for a compliance control (silent bypass).

Fix: check the unconditional security signals FIRST and without exception — a
401/403 denial, any /v1/admin/* call, and any POST/PUT/PATCH/DELETE are ALWAYS
audited whatever the path. Only after that is a safe read dropped (all safe
reads, incl. liveness probes, are request-log noise → not recorded). The
suffix-based /health exemption is gone; it can no longer suppress a mutation.
Proven by TestAudit_HealthSuffixCannotEvadeAudit (POST .../health IS audited;
GET /v1/kms/health is not) and the unchanged TestAudit_SkipsSafeReads.

* harden(audit): no false-attribution — anonymous request records no org/sub

Self-review: SanitizeIdentity's Phase-1 residual restores a client-supplied
X-Org-Id for the data path, so an UNAUTHENTICATED attacker sending
X-Org-Id: victim-org could stamp an audit event with a victim's org (false
attribution), even though X-User-Id/IsAdmin are correctly stripped.

Fix: actorFromCtx gates the recorded actor on a VALIDATED principal — a
non-empty c.User() (X-User-Id, which SanitizeIdentity sets only from a verified
JWT). With no validated sub (anonymous, or an invalid/garbage bearer that failed
validation), the actor is recorded EMPTY: the event stands as an honest
anonymous mutation identified by SourceIP, never mis-attributed to a claimed
org. With a validated sub, org/sub/email are authoritative.
Proven by TestAudit_AnonRequestNotAttributedToForgedOrg (runs the real
SanitizeIdentity ahead of AuditTrail).

* fix(audit): close 4 scrub-bypass classes from Red review (MEDIUM)

Red's adversarial review found the path/UA credential scrub (5dfdf0e4) had
4 bypass classes that let a secret reach the immutable trail:
  1. base64url with -/_  (looksLikeHighEntropyToken rejected any non-alnum)
  2. all-alpha opaque >=len  (required digits>0)
  3. percent-encoded prefix  (hk%2D… defeated the isAPIKey match)
  4. UA glued by :/()[]  (scrubFreeText split on too few delimiters)

Fixes:
- looksLikeHighEntropyToken now accepts the FULL base64url alphabet
  [A-Za-z0-9_-] (RFC 4648 §5), drops the digit requirement, exempts dotted
  values + canonical UUIDs, threshold lowered to 24 (128-bit base64 / 24-hex).
- scrubToken percent-decodes before every credential test (url.PathUnescape),
  so %2D/%5F can't hide structure.
- scrubFreeText tokenizes on a broad delimiter superset (= ; , : / \ ( ) [ ]
  { } " ' < > | & ?) and rebuilds in one pass preserving delimiters —
  replacing the fragile strings.ReplaceAll.

Proven by TestScrubToken_RedReviewBypassClasses (all 4 classes + UA glue) and
the expanded TestScrubToken_NoFalsePositives (uuids, model names like
claude-opus-4-20250514/text-embedding-3-large, slugs, normal UAs unchanged).

* feat(audit): operationalize AU-9 tail-truncation anchor (Red LOW #2)

Red: the Head() pin is inert unless operationalized — a hash chain can't detect
that the last K records were deleted (the surviving prefix self-verifies); only
an independent, durable head-digest series catches the count regression.

Adds a checkpoint emitter to the Recorder:
- StartCheckpoints(interval, logFn): a periodic goroutine emits the head digest
  {count, head, ts} to the append-only observability log (o11y) every interval
  (CLOUD_AUDIT_CHECKPOINT_INTERVAL, default 5m), plus a FINAL checkpoint on
  Close so the shutdown head is anchored.
- CheckpointSink: when the ClickHouse mirror implements it, the digest is ALSO
  persisted to an INDEPENDENT audit_log_checkpoints table (MergeTree) — so
  truncating the local SQLite chain cannot rewrite the anchor history.
- Detection (compare consecutive checkpoints, alert on count regression) lives
  in o11y where alert rules belong; the binary emits the tamper-evident anchor
  to an independent sink. /v1/admin/audit/verify already returns (count,head) as
  the pollable anchor too.

Proven: TestCheckpoint_EmitsHeadDigest (log + independent sink get count=7 head
on Close), TestCheckpoint_CountMonotonicDetectsTruncation (delete tail → prefix
still self-verifies, but count regresses 10→6 = the o11y alert signal).
Race-clean.

* harden(audit): close dotted-exemption + standard-b64 + nested-encoding scrub gaps

Self re-review (pre-empting Red's scoped re-review) found the round-1 scrub fix
still had gaps: the dotted-exemption let a raw secret bypass by appending '.x',
standard-base64 tokens (with +/) slipped, and nested percent-encoding (%252D)
survived a single decode.

Rewrote looksLikeHighEntropyToken to SCAN for the longest UNBROKEN base64-ish
run (>=24) anywhere in the value, over BOTH url-safe (-/_) and standard (+//)
alphabets — so '<rawsecret>.x' still trips (pre-dot run >= 24) and a standard-
base64 secret is caught. UUIDs stay exempt; real slugs/model-names/filenames
(report.pdf, text-embedding-3-large) have no 24-char run so they pass.
percentDecode now iterates (bounded x3) to normalize nested encodings.

All bypass classes closed (Red's 4 + dotted/standard/double-encoded), zero
false positives — TestScrubToken_RedReviewBypassClasses + NoFalsePositives
extended. The 20-char short-secret is a deliberate non-match (lowering below 24
would over-scrub legit hex-ish ids).

* fix(audit): address Red re-review — model-id over-scrub, UA glue, checkpoint (2 MED + 1 LOW)

Red re-review of the scrub/checkpoint code found 2 MEDIUM + 1 LOW:

MEDIUM 1 — model-id over-scrub (AU-3 regression): the round-3 run-scanner
counted '-' as a token char, so hyphenated model ids (claude-3-5-sonnet-
20241022, 26-char run) were redacted on audited routes (PATCH/DELETE
/v1/ml/models/:name, /v1/admin/catalog/models/*) — an auditor lost WHICH model
changed. Fix: isHighEntropyRunChar EXCLUDES '-' (kept +/_ for base64). Model
ids break into short runs (max ~9, far under 24); real secrets stay unbroken
>=24 runs — even a url-safe token using '-' as a separator has a >=24 run on one
side (AbCdEf-GhIjKl_MnOpQrStUvWxYz012345 -> 27). 6 model ids added to
TestScrubToken_NoFalsePositives.

MEDIUM 2 — UA free-text bypass: isFreeTextDelimiter omitted . @ # ~, so a
prefixed key glued by them (client@sk-live-KEY) stayed one token whose prefix
was no longer sk-/hk-. Fix: add . @ # ~ to the delimiter set; also flag a lone
eyJ-prefixed JWT header segment regardless of length (a JWT header is never a
legit id). Real UA dots are version separators (<24, safe). Fixed the stale
isFreeTextDelimiter docstring that referenced a nonexistent exemption. Proven by
4 glue-char probes in TestScrubToken_RedReviewBypassClasses.

LOW — checkpoint robustness: (a) StartCheckpoints now guards double-start with a
 flag (the field/WaitGroup write was -race-flagged on a 2nd call) and
the docstring is corrected; (b) the on-Close final checkpoint to the independent
sink is now SYNCHRONOUS with a bounded 5s ctx (was fire-and-forget — the AU-9
independent anchor could be stale exactly at shutdown when an attacker truncates).
Proven by TestCheckpoint_DoubleStartIsSafe (-race) + TestCheckpoint_CloseSyncsToSink.

34 tests green, race-clean, -tags cloud.

* harden(audit): structured-id exemption beats hyphen-exclusion (11%->0.09% token bypass)

The prior fix (exclude '-' from the entropy run to protect model ids) opened an
~11% bypass for 32-byte url-safe-base64 secrets whose '-' happened to break
every 24-run (measured over 10k random tokens). Excluding '-' was too blunt.

Better construction: INCLUDE '-' in the run alphabet again (so a base64url token
embedding '-' is caught by its run), but exempt STRUCTURED IDs up-front via
isStructuredID — a value with >=3 hyphen groups where every part is <=12 chars
(dictionary words / short numbers: claude-3-5-sonnet-20241022). A raw secret
does not decompose that way. Measured: 0 model over-scrub, 0.09% residual on
32-byte base64 tokens that randomly resemble an id AND are prefixless AND sit in
a URL path (real keys carry hk-/sk- prefixes caught by isAPIKey; JWTs by
looksLikeJWT). An interior-hyphen raw secret with LONG parts still redacts.

Proven: TestScrubToken_NoFalsePositives (12 model ids/slugs pass) +
TestScrubToken_RedReviewBypassClasses (interior-hyphen long-part secret redacts).
34 tests green, -tags cloud.

* fix(audit): lexical structured-id test closes Red MEDIUM + guard started race (LOW)

Red final re-review: isStructuredID was SHAPE-only (>=3 hyphen groups, parts
<=12) — attacker-satisfiable. A secret chunked to that shape
(AbCdEfGhIjKl-MnOpQrStUvWx-YzAbCdEfGhIj, or deadbeef-cafebabe-01234567-89abcdef)
was exempted; ~2.15% of random 128-bit tokens leaked by chance. Entropy-count
alone can't separate them (deepseek-r1-distill-qwen-32b has 24 non-hyphen chars,
same as a 128-bit secret).

Fix: isStructuredID now requires every group to be WORD-LIKE (isWordLikeGroup) —
lexical content, not shape. A group is rejected if it is dense MIXED-CASE (base64
chunk) or a long ALL-HEX-WITH-LETTERS run >=8 (hex chunk like deadbeef); an
all-digit version date (20241022) stays word-like. Measured: 0 model over-scrub,
0 crafted-attacker bypass, natural random-token leak 0.0004% (128-bit) / 0%
(192-bit+) — down from 2.15%. Real keys (hk-/sk- prefix) and JWTs are caught
regardless.

LOW: StartCheckpoints' started check-and-set now under r.mu (was -race-dirty on
a concurrent 2nd call; prod-unreachable but now clean).

Proven: TestScrubToken_RedReviewBypassClasses (4 chunked-secret classes redact) +
TestScrubToken_NoFalsePositives (17 model ids/slugs pass). 34 tests green, -race,
-tags cloud.

* harden(audit): two-stage detection + document single-case-chunk residual bound

Restructured looksLikeHighEntropyToken into two stages after tracing the
fundamental limit Red is probing:
- Stage 1 (UNCONDITIONAL): a >=24 UNBROKEN run over [A-Za-z0-9_+/] (hasHighEntropyRun,
  '-' and '.' are separators). Catches every raw secret WITHOUT internal separators
  (hex, base64) at 100% — the realistic 'client bug put a raw key in the URL' case.
  Never over-scrubs a hyphenated id (runs are short).
- Stage 2 (separated values): exempt a lexical structured-id (isStructuredID: >=3
  word-like hyphen groups); otherwise redact. Catches mixed-case/hex chunks.

ACCEPTED RESIDUAL BOUND (documented in code): a secret deliberately chunked into
>=3 single-case-ALPHABETIC groups <=12 chars is lexically indistinguishable from
a hyphenated model id (deepseek-r1-distill-qwen-32b carries the SAME 24-char
entropy budget) — NOT closable by any length/case/count rule without a word
dictionary (over-engineering for a defense-in-depth URL/UA backstop). It does not
widen exposure for any REAL credential: Hanzo keys are prefixed (isAPIKey, any
length), JWTs are eyJ-prefixed (looksLikeJWT), bodies are never read. The residual
is an adversary chunk-encoding their OWN secret into a URL to seed an admin-only
audit row — contrived, low-value. The realistic accidental leak (unbroken raw key)
is caught by stage 1.

Removed dead isHighEntropyRunChar. 34 tests green, -race, -tags cloud.

* feat(paassvc): native in-process PaaS deploy control plane (/v1/paas/*)

Port the standalone Dokploy platform's observe + deploy halves into the unified
cloud binary as clients/paassvc — the 'one and only one way to deploy' made
native. Follows the clients/ml pattern exactly: a self-contained dynamic k8s
client, cloud.Register'd from init() (order 128), global-admin-gated, fail-closed
when no cluster.

Surface (global-admin only; user-facing view lives in console2):
  GET  /v1/paas/apps             fleet drift board (declared/running/latest/drift+health)
  GET  /v1/paas/apps/:app        one service row by CR name (main->test->dev)
  POST /v1/paas/apps/:app/deploy deploy a tag by merge-patching Service CR .spec.image
  GET  /v1/paas/health           real k8s reachability + Service CRD probe

- drift.go: 1:1 port of apps-drift.ts (computeDrift/isSemverTag + 6 DriftKinds,
  identical severities). Pure, zero IO.
- paas.go: observeFleet lists hanzo.ai/v1 services across hanzo/-testnet/-devnet
  (inventory.ts DEFAULT_TARGETS), joins the live Deployment for the running tag
  (the operator Service CR status does NOT surface the running image — confirmed
  against the live CRD), health/phase/endpoints from the reconciled CR status.
  deploy merge-patches .spec.image (deploy-executor.ts parity) -> operator rolls it.
- Stateless: reads the cluster live (CRs are the source of truth); no apps-table
  copy, no cron readers (dropped vs the Node platform).

Tested green:
- 30+ unit cases incl. the 9 drift-contract cases ported verbatim; go test green,
  gofmt clean, go vet clean, full cloud binary builds (-tags cloud).
- Live-cluster probe (paasintegration tag, PAAS_IT-gated): observeFleet returned
  82 real rows matching kubectl; an idempotent same-image patch on pricing
  round-tripped through the operator with generation unchanged (6->6) = write
  path proven WITHOUT triggering a rollout, zero disturbance to live state.

Design + full port map: universe/docs/architecture/paas-in-cloud.md.
RBAC (cloud-paassvc -> cloud-api SA): universe infra/k8s/cloud/paassvc-rbac.yaml.

Additive: platform.hanzo.ai stays as the internal-admin console; this is the
native backend + (next) the console2 user UI. No forced retirement.

* polish(audit): close hex-chunk residual (hex rule 8->4) + correct residual doc

Red final review (SHIP verdict) flagged 2 non-blocking polish items:
1. Lower isWordLikeGroup hex rule from len>=8 to len>=4 — Red verified across 19
   real model ids that NONE has an all-hex-with-letters group of len>=4, so this
   closes the small-hex-chunk leak (md5/sha in 'xxxx-xxxx' display grouping:
   abcd-ef01-2345-6789-…) at 100% with ZERO model-id over-scrub. hexChunkMinLen=4.
2. Correct the residual doc: the accepted bound is now ONLY single-case-ALPHABETIC
   base32 chunks (lowercase/uppercase-only, no hex-letter runs >=4) — mixed-case
   base64 AND all hex-chunk sizes are now caught. The remaining case is genuinely
   unclosable without a word dictionary and exposes no real credential.

Proven: TestScrubToken_RedReviewBypassClasses now includes 4-char hex groups
(abcd-ef01-…) which redact; TestScrubToken_NoFalsePositives (19 model ids) still
pass. 36 tests green, -race, -tags cloud. Red re-review: none needed.
2026-07-01 07:22:39 -07:00
hanzo-devandGitHub 55eef30e3b feat(paassvc): native in-process PaaS deploy control plane (/v1/paas/*) (#52)
Port the standalone Dokploy platform's observe + deploy halves into the unified
cloud binary as clients/paassvc — the 'one and only one way to deploy' made
native. Follows the clients/ml pattern exactly: a self-contained dynamic k8s
client, cloud.Register'd from init() (order 128), global-admin-gated, fail-closed
when no cluster.

Surface (global-admin only; user-facing view lives in console2):
  GET  /v1/paas/apps             fleet drift board (declared/running/latest/drift+health)
  GET  /v1/paas/apps/:app        one service row by CR name (main->test->dev)
  POST /v1/paas/apps/:app/deploy deploy a tag by merge-patching Service CR .spec.image
  GET  /v1/paas/health           real k8s reachability + Service CRD probe

- drift.go: 1:1 port of apps-drift.ts (computeDrift/isSemverTag + 6 DriftKinds,
  identical severities). Pure, zero IO.
- paas.go: observeFleet lists hanzo.ai/v1 services across hanzo/-testnet/-devnet
  (inventory.ts DEFAULT_TARGETS), joins the live Deployment for the running tag
  (the operator Service CR status does NOT surface the running image — confirmed
  against the live CRD), health/phase/endpoints from the reconciled CR status.
  deploy merge-patches .spec.image (deploy-executor.ts parity) -> operator rolls it.
- Stateless: reads the cluster live (CRs are the source of truth); no apps-table
  copy, no cron readers (dropped vs the Node platform).

Tested green:
- 30+ unit cases incl. the 9 drift-contract cases ported verbatim; go test green,
  gofmt clean, go vet clean, full cloud binary builds (-tags cloud).
- Live-cluster probe (paasintegration tag, PAAS_IT-gated): observeFleet returned
  82 real rows matching kubectl; an idempotent same-image patch on pricing
  round-tripped through the operator with generation unchanged (6->6) = write
  path proven WITHOUT triggering a rollout, zero disturbance to live state.

Design + full port map: universe/docs/architecture/paas-in-cloud.md.
RBAC (cloud-paassvc -> cloud-api SA): universe infra/k8s/cloud/paassvc-rbac.yaml.

Additive: platform.hanzo.ai stays as the internal-admin console; this is the
native backend + (next) the console2 user UI. No forced retirement.
2026-07-01 07:19:32 -07:00
hanzo-dev 6712290e1f fix(cloud): address Red review — exact tenant keying + content caps
Red HIGH-1 (cross-tenant CRUD, PROVEN): the isolation key used a lossy
sanitizeOrg (lowercase/punct->'-'/32-char truncate) so distinct IAM owners
(acme/ACME/acme!/32-char-prefix) collapsed into one storage bucket. Fixed:
tenant() now keys on the EXACT validated org from SanitizeIdentity — never
normalized. Removed the magic 'admin' bucket (empty org -> 403, even for
admins). sanitizeOrg deleted from the key path (kept only as a cosmetic,
clearly-labeled namespace normalizer in functions).

Red MED-1 (46MB response amplification): prompt content now capped at 64KiB;
version history is bounded, metadata-only (no per-version content echo);
metrics uses a true COUNT.

Red INFO: >900s timeout now clamps to 900 (was reset to 30) in create+invoke.

Red's three adversarial tests INVERTED into regression guards that assert
isolation HOLDS: TestRed_OrgKeyExactIsolation (8 collision classes, all
isolated), TestRed_NoAdminBucketConfusion, TestRed_PromptContentCapped.
All suites green under -race; fused subsystems graph links.
2026-07-01 07:12:33 -07:00
hanzo-dev 52c44a0c8c fix(build): main was broken — clients/console import excluded by //go:build cloud
Commit 625c234 added clients/console (a second, //go:build cloud-gated take on
the go:embed console) and imported it unconditionally in the subsystems bundle.
The default build (go build ./cmd/cloud, no -tags) excludes those files, so the
whole binary failed: 'build constraints exclude all Go files in clients/console'
— which also fails the CI image build, blocking every deploy.

The working, wired console embed is webui.go's mountConsole (called from Serve
after all /v1 routes). clients/console is redundant with it and would double-mount
'/'. Drop the broken import so main builds; consolidating onto ONE console path
is a clean follow-up.

Verified: go build ./cmd/cloud → 426MB binary; booted it and the ONE process
serves console '/' (200 HTML), SPA fallback /gpus (200 HTML), /v1/metrics/health
(200), /v1/nope (503 non-HTML — decline-list holds), /healthz (200).
2026-07-01 06:40:13 -07:00
hanzo-dev 8b6451ed10 feat(cloud): mount per-org /v1/{prompts,agents,functions} product subsystems
Three native HIP-0106 subsystems, each org-scoped by the gateway-minted
X-Org-Id (SanitizeIdentity trust boundary), Base/SQLite in DataDir, secrets
by KMS reference only. Follows the projectsvc template; wired via one
additive block in subsystems/subsystems.go (orders 126/127/128).

- prompts   /v1/prompts/*    versioned prompt library (create=new version)
- agents    /v1/agents/*     agent defs + real run via deps.AI, recorded runs
- functions /v1/functions/*  serverless registry + invocations/metrics;
                             invoke delegates to the code-exec sandbox and
                             fails closed (503) when unconfigured — never
                             runs tenant code in-process, never fabricates.

Tenant isolation proven at the store AND HTTP layers (Fiber app.Test):
no-org -> 403, cross-org list empty, cross-org get/delete/run -> 404.
All suites green (CGO=1).
2026-07-01 06:39:31 -07:00
hanzo-dev 625c234e14 feat(console): go:embed the console2 SPA into cloud — the one-binary foundation
Hanzo V8: Open Edition. cloud/clients/console go:embeds dist/ (the console2 static
export) and mounts the SPA at "/" with SPA-fallback, order 990 — the last-resort
catch-all AFTER every /v1/* route (isAPIPath refuses to HTML-fallback /v1,/zap,/_,
/healthz so JSON clients get honest 404s). Registered in subsystems.go.

This is the seam that makes ONE Go binary the whole cloud — edge + gateway + every
subsystem + the frontend. Placeholder dist/index.html is overwritten by the
console2 static-export bundle at image-build time. Build verified: go build -tags
cloud ./clients/console/ clean.
2026-07-01 05:59:48 -07:00
hanzo-devandGitHub 2d89b8d4f7 feat(cloud): embed + serve the console UI from the ONE binary (go:embed) (#50)
One artifact, one origin: the same hanzoai/cloud binary now serves the
console (@hanzo/gui, from hanzoai/console2) at the web root AND the /v1 API
from one process — no separate console Service, no second origin. Flagship
OSS-cloud consolidation (HIP-0106).

Serve (webui.go)
- The console is compiled in via `//go:embed all:webui/dist` and mounted as
  the app's TERMINAL catch-all in Serve — LAST, after every /v1 subsystem
  route, the /zap plane, and the health contract. Fiber v3 matches in
  registration order, so real API routes always win; only paths that match
  nothing else reach the SPA.
- SPA fallback: `/` and any client-side route (`/orgs`, `/models`, …) serve
  index.html (Cache-Control: no-cache) so deep links / reloads work.
  Fingerprinted assets (assets/, _next/) are served immutable for a year,
  with brotli/gzip precompressed-sibling negotiation when the build emits
  .br/.gz. Served through a stdlib http.Handler (correct Content-Type,
  conditional GET) adapted onto zip via zip.AdaptNetHTTP.
- API precedence + namespace safety: an UNMATCHED path under an API/ops
  prefix (/v1/, /zap, /healthz, /readyz, /metrics) returns a real 404 — never
  the SPA shell — so clients calling a mistyped /v1/… never get HTML 200.
- Same-origin: the embedded console calls /v1 on its own host; the session
  cookie is first-party — no CORS, no second-origin token dance.
- Reuses the hanzoai/static plugin's SPAMode semantics; implemented in-binary
  because static.Handler is disk/S3-only today (its New() takes a Root/S3
  bucket, not an fs.FS) so it can't serve an embed.FS — teaching it fs.FS is
  the clean follow-up to collapse onto the shared plugin.

Build pipeline (Dockerfile)
- New `console` stage builds the console2 static bundle → /out; the Go build
  overlays it into webui/dist BEFORE `go build` so go:embed bakes it in.
- webui/dist/index.html is a committed fallback shell (a real same-origin /v1
  bootstrap) so `go build` always compiles and the binary always serves a UI
  even without the Node toolchain; the image build overwrites it with the real
  console. Built assets are .gitignore'd — generated at build time, never
  committed as source.

Tests (webui_test.go) — boot the app + assert, end-to-end via app.Fiber().Test:
GET / → shell; deep links → shell 200 (not 404); /v1/models → API (not SPA);
unmatched /v1/… → 404 (not HTML); assets served directly; HEAD; and path
traversal (../, %2e%2e) cannot escape the embed FS. 7/7 green.

Honest current state: console2 ships 15 Next server route handlers
(app/**/route.ts, KMS-token proxies) so it emits a Node server bundle, not a
static export — the image embeds the fallback shell until console2 exposes a
build:embed static target or those routes land here as native /v1 endpoints.
The Go embed/serve plumbing is complete and needs no change to light up the
full console the moment the static bundle exists.

Drive-by: brand_test.go asserted the pre-pin hanzo issuer (iam.hanzo.ai);
brand.go was pinned to hanzo.id in 21ac43f1, so the test was stale — aligned
to the shipped behavior (brand.go unchanged). Root package: 34/34 green.
2026-07-01 05:53:35 -07:00
hanzo-dev 3834cc1bbd fix(deps): re-record 3 drifted luxfi go.sum hashes (age@v1.5.0 +2) — canonical proxy; unblock release build 2026-06-30 22:23:20 -07:00
hanzo-dev db3b156bd0 refactor(o11y): forward path verbatim — no /api/ rewrite
The o11y fork now registers its routes at their exact public path (/v1/o11y/*),
so the reverse proxy forwards unchanged — removed rewritePath (/v1/o11y→/api) and
the TestRewritePath test. One and one way: the route IS the path on both sides.
Cloud o11y tests pass.
2026-06-30 21:35:19 -07:00
zeekay b09052305b Merge branch 'feat/projects-store-and-deploy' 2026-06-30 20:18:54 -07:00
hanzo-devandGitHub 88cde76b90 feat(cloud): /v1/exec (Code Interpreter → sandbox) + /v1/websearch (Hanzo search+crawl) (#49)
* feat(cloud): /v1/exec (Code Interpreter → sandbox) + /v1/websearch (SearXNG+Firecrawl-compat over Hanzo search+crawl)

hanzo.chat's Run Code and Web Search agent tools speak fixed LibreChat
provider contracts. cloud-api is the single /v1 edge, so it owns those
surfaces and routes them to Hanzo's own infra — never an external SaaS.

- clients/exec (order 140): mounts /v1/exec, /v1/exec/*, /v1/upload,
  /v1/download/*, /v1/files/* — the @librechat/agents CodeExecutor contract
  (POST /exec {lang,code} X-API-Key -> {stdout,stderr,files}). Transparent
  reverse proxy to a SANDBOXED executor (CODE_EXEC_UPSTREAM). NO os/exec here;
  the executor is the isolation boundary. X-API-Key (CODE_EXEC_API_KEY, KMS)
  enforced constant-time, fail-closed.
- clients/websearch (order 141): mounts /v1/websearch/search (SearXNG JSON,
  proxied to a Hanzo-operated metasearch WEBSEARCH_UPSTREAM) and
  /v1/websearch/v1/scrape (Firecrawl shape, backed by Hanzo Crawl/Crawl4AI —
  {url}->{success,data:{markdown,metadata}}). WEBSEARCH_API_KEY (KMS).
- Both register before ai (150) so their specific paths win over ai's /v1/*
  catch-all. Mirrors the clients/o11y reverse-proxy pattern.

Tests: proxy verbatim-forward, path rewrite, auth fail-closed/reject,
crawl->firecrawl shape adaptation. All green.

* test(cloud): mount-through-Fiber integration tests for exec + websearch

Prove Mount() registers the overlapping static+wildcard routes (/v1/exec &
/v1/exec/*, /v1/websearch/*) on a real zip/Fiber router without panicking,
and that requests route end-to-end through the router to the guarded
handlers (proxy forward, firecrawl-shaped scrape, auth reject). Closes the
gap where direct-handler tests bypassed route registration.
2026-06-30 18:39:23 -07:00
hanzo-dev 18b7577017 refactor(cloud): adminsvc → admin (drop svc, one word) — consistency with the svc-drop 2026-06-30 17:55:00 -07:00
hanzo-dev 2f6c824f3a refactor(cloud): drop the svc suffix — one word per subsystem client
o11ysvc→o11y, evalsvc→eval, mlsvc→ml, plansvc→plan, pluginsvc→plugin,
pricingsvc→pricing, productsvc→product, provisioningsvc→provisioning. The suffix
was stutter (svc = service). Package name == dir == the bare noun now.

o11y is `package o11y` importing `github.com/hanzoai/o11y` with a PLAIN import (no
alias): the import name is file-scoped and you never qualify your own package, so
`o11y.SetHandler` resolves to the upstream — the local `upstream()` URL func is
untouched. subsystems.go import paths + gojahost comment updated. Renamed packages
+ subsystems build clean.
2026-06-30 17:52:59 -07:00
hanzo-devandGitHub 9df0efbc2c feat(adminsvc): god-mode /v1/admin/* surface for admin.hanzo.ai console (#48)
Aggregator facade mounting the /v1/admin/* surface the Hanzo Admin Console
(admin.hanzo.ai, apps/operator) calls, matching its api.ts contract
field-for-field. Fans out over HTTP to the real upstreams — IAM (orgs, users,
roles, applications, audit, me), commerce (spend, credits), o11y (health) —
exactly like the o11ysvc/productsvc read facades; holds no store of its own.

Every route is GLOBAL-ADMIN ONLY, fail-closed: the guard reuses c.IsAdmin(),
which after SanitizeIdentity is true only for a JWT-validated principal whose
org is the admin org (IAM's IsGlobalAdmin), matching the gateway's admin-guard.
Anonymous and tenant-admin callers are denied 403 on every route (regression
locked in TestGate_DeniesEveryRoute). The IAM fan-out replays the caller's own
cookie/bearer — no adminsvc service credential — so it never reads more than the
caller could, and IAM re-checks IsGlobalAdmin. Commerce uses the existing
KMS-synced COMMERCE_SERVICE_TOKEN; no secret is hard-coded or logged.

Panels with no in-binary feed yet return the honest empty state, never a
fabricated number: the usage timeseries + per-product breakdown (insights/
datastore) and the product/workload registry + infra tiles (platform apps
table). The operator renders these as empty/em-dash by design.

Endpoints: overview, orgs, users, roles, applications, audit, usage, products,
me, sync. Registered order 146; blank-imported in subsystems.go.

Tests: gate denial across all routes x anonymous/tenant-admin/tenant-user, gate
allow for global admin, real aggregation (orgs/users/overview/usage) against
mock IAM+commerce, credential-replay assertion, IAM-error-surfaced (not
fabricated), honest-empty series/products. go build ./... + go test green.
2026-06-30 17:48:43 -07:00
hanzo-dev 675257b127 fix(storagelock): a db NAME is not a backend — reject only real Postgres
`dbName=hanzo_cloud` alongside driverName=sqlite crash-looped cloud-api (fail-closed
on a benign leftover). Decomplect: the guard's one job is "reject Postgres" =
driverName=postgres OR a postgres:// DSN. A database name selects nothing, so drop
`dbName` from forbiddenEnvs entirely (the Go binary never reads it). Also correct the
lineage label: the legacy cloud-api is casibase (Go) — it lives on as hanzoai/ai,
which mounts INTO this hanzoai/cloud orchestrator — NOT "Python/TS". Tests updated:
dbName is never a violation; driverName=postgres + postgres DSN still are. Forwards
perfection, no backwards-compat leftover.
2026-06-30 17:32:17 -07:00
hanzo-devandGitHub 32138dbf0b chore(productsvc): top-level /v1 — drop residual /api/ prefix (#47)
Rename cloud-api's own public product routes from /api/<route> to
top-level /v1/<route>, per the openapi v1.0.0 lock-in (no /api/ prefix;
the subdomain is api.* so /api/ double-prefixes):

  /api/search-docs/indexes -> /v1/search-docs/indexes
  /api/search-docs/stats   -> /v1/search-docs/stats
  /api/vector/collections  -> /v1/vector/collections
  /api/vector/stats        -> /v1/vector/stats

These are the only /api/ paths cloud-api REGISTERS (serves). The remaining
/api/ literals are upstream calls cloud-api MAKES to other services that
genuinely serve /api/ — left untouched:
  - evalsvc: /api/public/* (Langfuse console API proxy targets)
  - o11ysvc: /v1/o11y/* -> /api/* runtime rewrite (destination)
  - pricingsvc: openrouter.ai/api/v1/models (external)

Hard cutover (no dual-serving, per no-backwards-compat). Coordinated with:
universe cloud-api-v1 AUTH_PUBLIC_PATHS, python-sdk + hanzo-docs RAG
clients, and the openapi cloud spec — all moving to /v1 together.
2026-06-30 17:06:27 -07:00
zeekayandhanzo-dev 71371fdff2 fix(deps): realign go.sum to current origin (luxfi force-re-tags) + integrate main (goa/pluginsvc); clear corrupted VCS cache
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-30 16:38:16 -07:00
zeekay 9a0c9768a7 Merge remote-tracking branch 'origin/main' into feat/projects-store-and-deploy 2026-06-30 16:22:28 -07:00
hanzo-dev 675336cec7 Merge commit 'c1647e32' into deploy/cloud-convergence 2026-06-30 15:48:06 -07:00
hanzo-dev 21ac43f13c fix(auth): pin hanzo IAM issuer to hanzo.id + reject missing exp (red FIX1/INFO)
FIX1 (red, HIGH — the deploy landmine): brand.go defaulted the `hanzo` brand
IAMIssuer to https://iam.hanzo.ai, but the live .well-known/openid-configuration
on BOTH hanzo.id and iam.hanzo.ai reports issuer=https://hanzo.id +
jwks_uri=https://hanzo.id/v1/iam/.well-known/jwks (iam.hanzo.ai is a routing
alias, not the token issuer). With the baked default, SanitizeIdentity's issuer
check would fail on every real token -> every principal anonymized -> ALL global
admin gets 403 (fail-secure, no forgery opened, but admin broken platform-wide).
The cloud CLI already defaults to hanzo.id; lux/zoo/pars already point at their
own .id issuers. Pin hanzo -> https://hanzo.id so the correct config is
default-by-default. (JWKS derivation then yields the correct hanzo.id JWKS.)

INFO (red): go-jose ValidateWithLeeway only enforces exp when present
(`if c.Expiry != nil`), so a token with NO exp would never expire. Reject a
missing exp explicitly, exactly like a missing iss. +1 test (22 green).

No subsystem reads cfg.IAMIssuer except SanitizeIdentity + a log line, so the
brand default change is contained.
2026-06-30 15:39:08 -07:00
hanzo-dev c1647e324b feat(billing): per-org fail-closed gate+meter for non-LLM provisioning + compute
Non-LLM resources were free: anyone could provision sql/vector/kv/s3/datastore/
docdb/search (provisioningsvc) and ml models/train jobs/experiments (mlsvc, GPU)
for $0 — only LLM calls were metered. This adds the same per-org commerce gate
the LLM edge gate uses, in-handler, so every create is paid for.

ONE shared primitive (no copy-paste per kind), reusing Deps.Metering (the single
commerce client) — the in-handler analogue of BillingGate:

  cloud.ResourceMeter (resource_billing.go)
    Gate(ctx, org, kind, costCents)   pre-create balance gate, fail-CLOSED
    Meter(org, kind, amountCents, …)  post-success debit, per-org, async
    DenyResource(c, err)              402 insufficient_balance / 503 unavailable
    ResourceFeeCents(prefix, kind)    configurable flat fee, $1.00 default

Wired into BOTH create paths (provisioningsvc + mlsvc) via the shared type:
gate runs after request validation and BEFORE any backend/k8s object is created
(no free provisioning, even on a commerce outage); meter runs only after the
resource is persisted/created.

Multitenancy (the whole point): org is the caller's resolved slug from tenant(c)
— the SAME value that namespaces the resource, now JWT-derived by the #66
identity sanitizer (not a spoofable header). It is sent to commerce as BOTH the
user identity AND X-IAM-Org-Id, OVERRIDING the client default org, so the balance
checked and the ledger debited are always the caller's own — never a default,
never another tenant. Proven by tests asserting commerce sees X-IAM-Org-Id:<caller>
(not the client default "hanzo") on both the balance check and the debit.

Env-aware (3-env split): the gate fires in EVERY env; test/dev are sandbox-but-
billed against their own per-env commerce/Square (structural, not a code branch).
Env is threaded config→deps as an attribution label and is NEVER a billing
bypass — proven by a test that testnet/devnet still refuse at zero balance.

Cost model: real, configurable per-kind flat fee (CLOUD_PROVISION_FEE_CENTS[_KIND],
CLOUD_COMPUTE_FEE_CENTS[_KIND]); 0 makes a kind free and un-gated; invalid/negative
is ignored so a typo can't silently free a paid resource. Ongoing storage GB-month
and GPU-hour reuse the SAME Meter primitive with a usage-derived amount from a
future runtime watcher — no live-size source here, so no size is fabricated.

Tests: resource_billing_test.go (gate allow/refuse/free/fail-closed/fail-open,
caller-org-not-default for both balance and debit, tenant isolation, env-never-
bypasses, unconfigured/nil no-op, fee resolution, deny shapes) + per-subsystem
integration tests proving the gate is wired into the real create path (402 before
backend on zero balance, 201 + caller-org debit when funded, free-kind un-gated).
go build ./... clean, go test ./... green, gofmt + vet clean.
2026-06-30 15:20:05 -07:00
hanzo-dev eb77547072 fix(auth): close forgeable-admin trust boundary on cloud-api
zip.Ctx.Org()/IsAdmin() read X-Org-Id / X-User-IsAdmin verbatim, trusting the
gateway to be their sole minter. But cloud-api is reachable WITHOUT the gateway
in front (in-cluster cloud-api.hanzo.svc:8000, and historically the public
cloud-api.hanzo.ai), so a direct caller could forge `X-User-IsAdmin: true` and
pass every admin gate: the new /v1/admin/catalog writes, /v1/pricing/sync, and
the provisioningsvc/mlsvc literal "admin" tenant bucket.

Add SanitizeIdentity, an early middleware (before BillingGate + every subsystem)
that strips every client-supplied authority header and re-derives identity ONLY
from a validated IAM JWT. Validation is a tiny go-jose JWKS validator
(auth_identity.go) that mirrors gateway/v2/iamauth — deliberately NOT imported
to avoid a module cycle (gateway/v2 already imports hanzoai/cloud) and pulling
the gateway's KrakenD/gin/traefik tree for ~150 lines. Admin authority is
granted ONLY to a verified GLOBAL admin (owner == AdminOrg), so an org-admin
(IAM also sets isAdmin=true for org owners) can't escalate. Non-admins are
pinned to their own org; a verified global admin's org-switch is honored. One
middleware makes every existing c.IsAdmin()/c.Org() reader trustworthy with no
handler changes.

Phase-1 residual (documented in middleware_identity.go): with no validatable
bearer the client X-Org-Id is passed through for DATA scoping (the console
browser data path depends on it) — closing that is Phase-2; the ADMIN boundary
is closed on every path because X-User-IsAdmin is never restored from a header.
Fail-secure: a validator misconfig (issuer/JWKS) makes admin 403, never opens.

Tests (middleware_identity_test.go): 18 subtests — forged header grants nothing,
org-admin can't escalate or cross-tenant, global-admin org-switch honored,
expired/wrong-key/wrong-audience/api-key/missing-issuer all anonymous, cookie +
HTTP-Basic paths. go-jose promoted to a direct require (already in the graph).
2026-06-30 15:02:06 -07:00
hanzo-dev 574ce320da fix(deps): canonical luxfi/zap@v0.8.11 go.sum hash (re-tagged module drifted local cache -> CI checksum mismatch) 2026-06-30 14:50:54 -07:00
hanzo-dev 51dc208f8b Merge branch 'feat/catalog-enablement' 2026-06-30 14:45:50 -07:00
hanzo-dev 928cc6a0ea fix(pricingsvc): gate root /v1/pricing + fail-closed overlay + override caps
Red review of feat/catalog-enablement found two in-branch leaks; fixed:

FIX #2 (HIGH): the root GET /v1/pricing returned the WHOLE bundle blob
(hanzoModels, thirdPartyModels, providers, freeModels, families) un-gated
via the `fixed` passthrough — an un-gated second source for everything the
leaf routes hide. New GateRootData() (catalog.go) gates the root in place:
hanzoModels+thirdPartyModels via VisibleCatalog (hanzoModels tagged "Hanzo"
so a disabled Hanzo provider cascades), providers via VisibleProviders, and
the id-reference lists freeModels + families[].models kept only if the
referenced model survived (admins keep all). Route moved out of `fixed` to
app.Get("/v1/pricing", gatedRoot). Audited the rest of `fixed`
(subscriptions/blockchain/iam/base/paas/tools/gpu/policy/cloud/compute):
all draw from the plans catalog with ZERO model/provider identity keys —
no gating needed; summary stays gated (providers sub-dict) with counts as
aggregate stats.

FIX #3 (fail-closed): empty DataDir was a Warn + :memory: fallback — a
security control that silently fails OPEN (admin-hidden models re-expose on
pod restart). Now a hard boot error (prod sets CLOUD_DATA_DIR;
provisioningsvc already requires it, so the unified binary always has one).

FIX #5 (DoS guard): overrides now bounded at 64 KiB + depth 32
(checkOverride) — bounds the recursive merge under a forged-admin write.

Tests: TestGateRootData (root gated identically to leaves: disabled/beta/
admin across hanzoModels/thirdPartyModels/freeModels/families/providers,
summary counts untouched), TestCheckOverride (object|null, size+depth caps),
TestMount_EmptyDataDir_FailsClosed, + e2e GET /v1/pricing gating and an
over-deep override PATCH->400. go build ./... + go test ./... green, gofmt.

NOT fixed here (infra, tracked separately): forgeable X-User-IsAdmin via
direct-to-pod cloud-api route — pre-existing, shared by every cloud IsAdmin
route; needs gateway routing + NetworkPolicy restriction in universe/operator.
2026-06-30 14:34:25 -07:00
hanzo-dev 2d0d63daf6 deps(ai): v1.785.14 -> v1.786.1 — cloud-repo image reaches feature-parity with prod
Decision (b): the cloud repo is the ONE authoritative builder of ghcr.io/hanzoai/cloud
(it assembles every subsystem incl. o11ysvc). But cloud pinned ai v1.785.14 while the
prod AI-built image (1.785.26) embeds ai code through the blue-money P0 security wave.
Bump ai to v1.786.1 — which contains ALL of it (balance ledger + overdraft gate, JWT
iss/aud validation, secret redaction, single-pod ledger invariant, aud env-keys,
redact allowlist, global-admin {admin,built-in}) — so the cloud-repo image is an
UPGRADE, never a regression below 1.785.26. luxfi/zap v0.8.8 -> v0.8.11 (tidy).
Build verified: go build ./cmd/cloud clean (453MB binary). Unblocks shipping o11ysvc.
2026-06-30 14:30:33 -07:00
hanzo-dev 976f6ec1ff fix(ci): ECR Public mirror for golang base — unblock release build (Docker Hub 429)
The last 5 release builds failed at `FROM golang:1.26-alpine` with
"toomanyrequests: unauthenticated pull rate limit" (429) from Docker Hub on the
shared runner, so no new cloud image has shipped — the deployed image predates the
o11ysvc mount (o11y /v1/o11y/* still 503) and the commerce mount. Switch the build
base to public.ecr.aws/docker/library/golang:1.26-alpine (immutable ECR Public
mirror, no rate limit) — the same fix already shipped in hanzoai/console2. Build
logic unchanged. Unblocks shipping o11ysvc → o11y live → retire old Langfuse console.
2026-06-30 14:12:28 -07:00
hanzo-dev 62e1f658d6 feat(pricingsvc): catalog enablement overlay + admin API
Add the backend admin layer that makes "admin enables -> customer sees"
real for the model/provider catalog, without forking the static
@hanzo/pricing bundle (still the sole source of truth for catalog
content/shape).

One overlay store, one gate:
- catalog.go: SQLite/Base overlay (table catalog_overlay, PK (kind,id);
  default = enabled, so an empty store is a no-op). Pure gate
  VisibleCatalog/VisibleProviders applies {enabled,betaOrgs,overrides}
  onto the bundle output: visible iff own AND provider overlay admit the
  org (enabled || org in betaOrgs); overrides merge via RFC 7386. Admins
  see every entry, annotated under _overlay.
- admin.go: global-admin (c.IsAdmin) write surface — GET /v1/admin/catalog
  (full catalog + state), PATCH /v1/admin/catalog/models/* (slashed ids via
  greedy wildcard) and /providers/:name. Partial-update PATCH; override
  validated as JSON object|null.
- pricingsvc.go: gate wired into the catalog read path (models, free,
  featured, providers, summary, model/:name); non-catalog routes unchanged.
  Overlay opened at {DataDir}/catalog.db (in-memory fallback), closed in
  Shutdown.

Default behavior unchanged for live customers (all enabled). Tests:
pure-gate units (default-all-visible, disabled-hidden-except-beta,
override-merged deep, admin-sees-all, provider cascade), store round-trip,
and an end-to-end HTTP test (wildcard routing, IsAdmin 403, enable->see flow).

console2 admin UI is a separate agent's job; it consumes these endpoints.
2026-06-30 14:02:59 -07:00
hanzo-dev 49318d610f fix(deps): base v1.3.2 -> v1.4.1 — unblock release Docker build
The committed go.sum pinned hanzoai/base@v1.3.2, whose tag was force-re-tagged
upstream (live content hash drifted from the recorded hash). The release
Dockerfile verifies modules against the committed go.sum with GOSUMDB=off, so
`go mod download` hit "checksum mismatch / SECURITY ERROR" and every release
build failed.

v1.4.1 is the latest base tag that (a) has a stable, immutable hash and (b)
still registers as a cloud subsystem (v1.4.2+ dropped cloud.Register and would
break subsystem assembly — 13 vs 14 subsystems, /v1/base/health 404). Pin v1.4.1:
fresh-cache go mod download is clean, registry assembles 14 subsystems, all
health endpoints 200, full suite green.
2026-06-28 23:15:53 -07:00
zeekay e0c68fd4a5 feat(projects): /v1/projects org-scoped store + deploy pipeline
New projectsvc subsystem (HIP-0106) — the ONE org-scoped store of
buildable/deployable sites, shared by hanzo.app (builder) and
console.hanzo.ai (Projects module). Both read/write the same records
through the gateway (X-Org-Id from the IAM JWT); no second copy of state.

- CRUD: POST/GET/PATCH/DELETE /v1/projects (+ /:slug)
- Deploy: POST /v1/projects/:slug/deploy
  - artifact mode: tar(.gz) of built site -> OUR S3 (s3.hanzo.ai,
    CLOUD_PROJECTS_BUCKET) under <org>/<slug>/, public-read, live URL
  - git mode: queue + CI completion hook (/deployments/:id/complete)
- Deploy history: GET /v1/projects/:slug/deployments(/:id)
- SQLite store (modernc), versioned deployments, tenant isolation by org
- Reuses CLOUD_S3_ADMIN_* creds (one S3 path, like provisioningsvc)
- Path-traversal + size/file guards on artifacts; index.html required
- Published contract in CONTRACT.md for console2 to consume

Tests: store CRUD/isolation/ordering, deployment versioning, slugify,
provider detection, safeRel traversal guard, tar/tar.gz walker. All pass.
2026-06-28 23:07:51 -07:00
5665cc491d build: drop GOPRIVATE for luxfi/hanzoai — use immutable public proxy (fix go.sum checksum mismatch) (#46)
The build routed luxfi/* + hanzoai/* DIRECT via git insteadOf, which re-fetches a
re-pointed tag's tree (luxfi/age@v1.5.0) whose hash differs from go.sum's proxy
hash → 'verifying github.com/luxfi/age@v1.5.0: checksum mismatch / SECURITY
ERROR'. luxfi/hanzoai are PUBLIC: resolve them via the IMMUTABLE public proxy +
the committed go.sum (which already pins the proxy hashes). Only zap-proto/*
stays first-party-direct. Matches the drop-GOPRIVATE fix in hanzoai/iam +
luxfi/kms.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-28 20:21:35 -07:00
hanzo-dev 577366a7b8 feat(cloud): pluginsvc — runtime plugin loader (goa wasm + ZAP-pluggable proxy)
cloud becomes a thin runtime host: alongside the compiled-in application
subsystems it mounts services from a runtime manifest (CLOUD_PLUGINS) with no
rebuild. Two plugin kinds, both reduced to app.Mount(prefix, http.Handler):

  wasm  — a polyglot module (Rust/WASM, Python, TypeScript) loaded in-process
          via github.com/hanzoai/goa (wazero/gpython/goja; pure Go, stays
          CGO_ENABLED=0). Drop a .wasm + manifest entry → mounted.
  proxy — a standalone server (e.g. the beego apps ai, vm) reached over a
          pluggable transport. The "zap" transport registers via
          pluginsvc.RegisterTransport; proxying defaults to HTTP until then.

Adding/updating a service = edit the manifest + drop a .wasm or redeploy the
standalone — the cloud binary is unchanged unless its own core changes.
Registered at order 900. Static binary preserved; package + full suite green.
2026-06-28 20:09:36 -07:00
z 0fee2d3e55 docs(brand): add hero banner 2026-06-28 20:05:32 -07:00
z 7a611434c7 chore(brand): dynamic hero banner 2026-06-28 20:05:31 -07:00
hanzo-dev b0368c9076 test(cloud): scope registry assertion to the application-layer matrix (edge/infra subsystems run as own deployments) 2026-06-28 17:11:07 -07:00
hanzo-dev 81bbb0f859 refactor(arch): cloud = application layer only; drop edge/infra subsystem imports (gateway, iam, kms, mcp run as own deployments behind gateway/ingress). Scope registry test to app matrix. Blast-radius isolation, smaller binary. 2026-06-28 17:09:22 -07:00
hanzo-dev 955342795e refactor(tenant): remove last X-Hanzo-Org; cloud -> ai v1.785.14. Single canonical X-Org-Id tenant header across the whole stack. 2026-06-28 16:59:27 -07:00
hanzo-dev 88b9fff607 build(deps): cloud -> ai v1.785.13 (tenant identity decomplected to X-Org-Id; X-Hanzo-Org kept as orthogonal service-token selector) 2026-06-28 16:47:23 -07:00
hanzo-dev d87ee75829 fix(cloud): full subsystem registry — force guarded beego/v2 v2.3.10 + explicitly import kms/iam/gateway/mcp; resolves ai(beego-v1)+iam(beego-v2) grace flag collision. TestRegistryAssemblesSubsystems green; cloud test suite fully passing. 2026-06-28 16:32:21 -07:00
hanzo-dev 152de74bab feat(cloud): storage-lockdown invariant (reject legacy PG env) + PG->SQLite migration tooling from zap-listener; superseded ZAP-listener/mount-adapter code dropped (zapface + registry are the one canonical way) 2026-06-28 16:17:10 -07:00
hanzo-dev 3c76a9c689 fix(deps): revert idv to v1.0.0 (v1.0.2 release is broken — missing provider/onyxplus.go) 2026-06-28 15:58:38 -07:00
hanzo-dev e7ba359e49 build(deps): cloud -> ai v1.785.11 (fail-closed mount + P0 security: balance/overdraft, JWT iss/aud, redaction, authz, tenant) + idv v1.0.2 2026-06-28 15:57:18 -07:00
hanzo-dev 981c8fc4e7 Merge remote-tracking branch 'origin/main' 2026-06-28 15:23:09 -07:00
hanzo-dev 0ddb5d40f4 fix(build): route luxfi via proxy + clean go.sum; ai v1.785.10 (fail-closed mount); drop removed amqp from tests
- Root cause of broken build: GOPROXY=direct fetched re-tagged git content + dropped //go:embed files (accel/crypto/geth). luxfi is public -> use proxy.
- ai@v1.785.10: Mount fails closed (503) when DB unconfigured, honoring BuildDeps three-mode contract.
- amqp removed from registry/health tests (subsystem retired).
- TestRegistryAssemblesSubsystems still red: ai(beego v1) vs iam(beego v2) grace flag collision blocks in-process coexistence - architectural follow-up.
2026-06-28 15:21:14 -07:00
zeekay 5bf4429661 fix(deps): bump hanzoai/iamsdk/v2 v2.1.0 -> v2.1.2 (JWKS token verify)
v2.1.2 verifies JWTs via the published JWKS instead of parsing the configured
cert PEM. cloud-api's /v1/signin (the ai dep's code->session exchange) configured
an unparseable Certificate (IAM returns the cert NAME 'cert-built-in' to
global-admin callers, not a PEM) -> 'iamsdk: not valid PEM' -> every
hanzo-cloud/hanzo-console SPA login failed (console + admin). go.sum realigned
(first-party re-tag dep-rot). cmd/cloud builds clean.
2026-06-28 14:28:00 -07:00
hanzo-dev 25be112454 chore(deps): bump luxfi/hanzoai deps to latest; fix re-tagged keys v1.2.2 + gateway v2.14.10; regenerate clean go.sum 2026-06-28 14:04:15 -07:00
hanzo-dev 00fb7351e5 Merge PR #37: Hanzo branding + LICENSE attribution 2026-06-28 13:12:17 -07:00
hanzo-dev 7aa7cf5660 Merge PR #45: fix(deps) bump hanzoai/ai -> 2e8fc6f15947 (401 on missing/invalid Bearer) 2026-06-28 13:12:17 -07:00
Blue a9db9e05a7 build(cloud): bump ai -> 2e8fc6f1 (invalid hk- key -> 401, nil-user fix); cloud:1.785.24 2026-06-28 04:29:32 -07:00
Blue acec71759a build(cloud): bump ai -> 069b83ce (authenticate-before-parse; 401 not 200 on invalid key + bad body)
Pulls hanzoai/ai @069b83ce into cloud:1.785.23: residual 200-leak fix for
/v1/chat/completions, /v1/embeddings, /v1/rerank, /v1/messages — an invalid
credential with a malformed/incomplete body now returns 401 (was 200/400),
authenticating before the body is parsed. ai go.mod unchanged, so only the ai
require + its go.sum zip hash move.
2026-06-28 03:28:29 -07:00
hanzo-dev 021dc990f6 fix(deps): revert erroneous base/pq go.sum realign — keep ONLY ai bump
The base/pq 'realign' in the prior commit adopted anomalous bits from a local
direct-fetch; the build container (and the working cloud:1.785.20 build) resolve
the ORIGINAL stable hashes via the module proxy/cache. Net go.sum change is now
exactly the hanzoai/ai bump (c08be563). luxfi re-tag churn
(fix/threshold-*-checksum-convergence) does NOT touch these pinned hashes.
2026-06-28 01:41:07 -07:00
hanzo-dev 4dd69bce68 fix(deps): bump hanzoai/ai -> c08be563 (401/402/400 auth status, not 200)
Pull in the ai auth-status fix: invalid/unknown hk- key -> 401, insufficient
balance -> 402, bad model -> 400 (was HTTP 200 with an error body on all of
them). Cloud-api is the single backend validating hk- keys for both
api.cloud.hanzo.ai and the gateway (api.hanzo.ai), which proxies the status.

Realign go.sum zip hashes for hanzoai/base v1.3.2 and luxfi/pq v1.0.3 to the
current origin (upstream re-tags; /go.mod hashes unchanged) so the build
resolves in a fresh container. Verified: CGO_ENABLED=0 go build ./cmd/cloud
links clean.
2026-06-28 01:28:44 -07:00
zeekay 6890c89e98 fix(deps): correct go.sum for re-tagged luxfi/pq + hanzoai/base
CI fetches via proxy.golang.org,direct; both tags were force-re-pushed so
the committed zip hashes no longer matched what the proxy serves:
  luxfi/pq    v1.0.3  pFlQm1... -> ksw1dm... (proxy commit 90d2223)
  hanzoai/base v1.3.2 BdTNDNe... -> 7GcHpg... (proxy commit 33d12949)
Minimal go mod tidy fix (2 lines); go.mod unchanged; cmd/cloud builds clean.
Unblocks the /v1/memory embed (hanzoai/ai fe516793).
2026-06-28 01:01:05 -07:00
zeekay a1503c51bf deps: bump hanzoai/ai -> fe516793 (embeds /v1/memory) + realign luxfi go.sum (pq/base/tls re-tag dep-rot) 2026-06-28 00:16:20 -07:00
zeekay fd17255784 fix(o11y): proxy rewrites /v1/o11y/* -> /api/* for the runtime's controllers
The o11y runtime (SigNoz query server) serves its API under /api; the registered
handler owns the documented /v1/o11y/* -> /api/* rewrite. The proxy now strips the
public prefix and prepends /api so /v1/o11y/v3/query_range reaches /api/v3/query_range
(verbatim forwarding hit the SPA fallback instead of the API).
2026-06-27 23:27:34 -07:00
zeekay 7b8c025ae3 feat(o11y): install runtime handler via reverse proxy to the o11y deployment
The o11y subsystem (hanzoai/o11y, order 70) mounts /v1/o11y/* but delegates to a
handler installed via o11y.SetHandler — never called in the unified cloud binary,
so the surface 503'd 'o11y runtime not initialized'. The heavy o11y runtime runs
as a dedicated Deployment; cloud now installs a reverse proxy to it (O11Y_UPSTREAM,
default o11y.hanzo.svc:80) so /v1/o11y/* serves real telemetry. Path preserved
verbatim; gateway-terminated identity forwarded.
2026-06-27 23:24:25 -07:00
hanzo-dev 6027df1e4d fix(deps): bump hanzoai/ai -> 254ea3b6 (401 on missing/invalid Bearer)
Pulls in ai fix: /v1/chat/completions, /v1/embeddings, /v1/rerank now
return HTTP 401 (not 200) on a missing/invalid Bearer token, matching
/v1/models. Valid-key completions + per-org billing unchanged.
2026-06-27 23:05:48 -07:00
zeekay 9ffdcbd253 chore(deps): bump hanzoai/kms/sdk/go v1.0.0 -> v1.1.1 (luxfi/constants dep-rot fix → unblocks mlsvc image build) 2026-06-27 22:04:23 -07:00
hanzo-dev 6783e9ae20 build: realign first-party go.sum hashes to current origin (upstream re-tags)
luxfi/* and hanzoai/* tags were re-pointed upstream (base v1.3.2, pq v1.0.3,
zap v0.8.8, et al.); the committed go.sum went stale and a clean image build
failed 'go mod download' verification. Re-record the current direct-fetch
hashes (proven non-first-party set untouched). No go.mod change.
2026-06-27 18:19:52 -07:00
hanzo-dev e702b54fbd build: realign hanzoai/base v1.3.2 go.sum hash (upstream re-tag)
base@v1.3.2 was re-pointed after cloud's go.sum was recorded; the committed
zip hash (BdTNDNe3…) is the stale public-proxy first-seen content, while the
live tag (direct git, the path CI's GOPRIVATE takes) hashes to 7GcHpg…. CI
fetches base DIRECT and fast-fails the build at the checksum mismatch — the
last stale hash blocking a green main (pq was realigned in dd557d7a; this is
the same upstream-re-tag fix, mirroring 5b4e3cef for luxfi age/keys/zap).

go.mod /go.mod hash unchanged (graph-load verified it); only the module zip
hash needed realigning. Verified: clean-cache readonly linux/amd64 -mod=mod
direct build is green.
2026-06-27 18:14:42 -07:00
hanzo-dev dd557d7a4c build: realign luxfi/pq v1.0.3 go.sum hash (upstream re-tag)
The committed zip hash went stale after luxfi/pq@v1.0.3 was re-tagged
upstream; cloud's clean image build failed go mod download verification.
Update to the current origin hash.
2026-06-27 18:10:26 -07:00
hanzo-dev 5bf55f2fde chore(deps): bump hanzoai/ai → f2cd2681 (per-user billing subject)
Pulls the per-user billing-subject fix into cloud-api: the gateway now keys the
balance gate + usage debit on object.BillingSubject(owner,name), so individuals
in the shared 'hanzo' org are billed independently (own balance, own $5) instead
of sharing+draining the single (hanzo,hanzo) balance.
2026-06-27 18:01:45 -07:00
zeekay ae0dc50a3b feat(mlsvc): tenant-scoped /v1/ml + /v1/train k8s bridge (kserve/trainer/katib)
New cloud subsystem (order 130) fronting the kubeflow forks via the k8s
dynamic client, scoped per-org by namespace (ml-<org>):

- /v1/ml/models           CRUD + PATCH + /predict (kserve InferenceService;
                          predict proxies to the model's v2 data plane /infer)
- /v1/train/jobs          CRUD (trainer TrainJob)
- /v1/train/experiments   CRUD + /trials (katib Experiment/Trial)
- /v1/ml/health, /v1/train/health  real probes: k8s reachability + CRD presence
  (200 ok / 503 degraded with the real reason; never status-theater)

Tenant boundary is the per-org Kubernetes namespace; the org->namespace map is
injective (strict slug regex, no lossy fold) so two tenants can never share a
namespace. User-supplied labels can't override the tenant org marker. The k8s
client is built in-process from the in-cluster service account with a KUBECONFIG
fallback (self-contained like provisioningsvc's backends, not on shared
cloud.Deps); it fails closed (503 / degraded health) when unconfigured.

Promotes k8s.io/apimachinery + client-go to direct requires. Registered via
blank import in subsystems.go. Unit tests cover the security-critical pure
helpers (tenant injectivity, name validation, label-override guard, GVRs).
2026-06-27 14:56:14 -07:00
hanzo-dev 54ddb3783b chore(deps): bump hanzoai/ai -> 703fe6b5 (OpenAI stream role + usage-chunk gating)
Picks up the streaming fix: first delta carries role:assistant and the
empty-choices usage chunk is gated behind stream_options.include_usage —
resolves hanzo.chat 'reading role' no-reply (separate from the dbx fix).
2026-06-26 17:43:37 -07:00
hanzo-dev 9ae1cc50ef chore(deps): bump hanzoai/ai -> aa326e8a (Message []struct JSON columns)
Picks up JSONList[T] (sql.Scanner + driver.Valuer over JSON) for
Message.VectorScores/Suggestions/ToolCalls/SearchResults, fixing the dbx
'unsupported type []model.SearchResult, a slice of struct' 500 that killed
console2 sign-in (welcome-message insert) and every hanzo.chat AI message
save. No new deps; transitive hunyuan -> v1.3.48 (already required by ai main).
2026-06-26 17:25:00 -07:00
hanzo-dev 5b4e3cef35 fix(build): go.sum direct-live hashes for re-tagged luxfi age/keys/zap
luxfi re-tagged age v1.5.0, keys v1.1.0 and zap v0.8.8 in place. The public
module proxy serves each tag's first-seen (now stale) content, while the
Dockerfile fetches first-party DIRECT via GOPRIVATE — so `go mod download`
hit SECURITY ERROR (checksum mismatch) against the stale proxy zip hashes
committed in go.sum. Record the live DIRECT zip hashes for all three
(the /go.mod hashes are unchanged). Verified clean in the exact build env
(golang:1.26-alpine, GOPRIVATE=hanzoai/luxfi/zap-proto, GOPROXY=proxy,direct):
go mod download + CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build ./cmd/cloud ./cmd/hanzo.
2026-06-26 15:44:14 -07:00
hanzo-dev 3c091a411c fix(build): GOPROXY=proxy,direct so public nested-tag modules resolve
The cloud merge pulled in tencentcloud-sdk-go monorepo modules whose tags are
nested paths (tencentcloud/hunyuan/v1.0.1074). GOPROXY=direct forced ALL modules
through direct VCS, which CANNOT resolve those nested tags ('unknown revision') —
go mod download failed in-build (worked locally only via cache). Route public
deps through the module proxy; first-party (hanzoai/luxfi/zap-proto) still go
direct+token via GOPRIVATE, so no private leak and re-pointed tags still resolve.
2026-06-26 15:16:51 -07:00
hanzo-dev ee3ba882f5 Merge feat/product-search-vector-endpoints into main (union)
Union merge — keep BOTH main's and the feature branch's work:

- subsystems/subsystems.go: register main's provisioningsvc (order 120)
  AND the feature's productsvc (order 145) alongside evalsvc/plansvc/pricingsvc.
- serve.go: collapse the two parallel :9090 listeners into ONE. Keep the
  feature's robust healthSrv/healthMux lifecycle (ReadHeaderTimeout, graceful
  Shutdown, fatal-on-bind) and FOLD main's HIP-0113 /metrics into healthMux,
  so the single ops port serves /healthz /readyz /health /metrics. Keep the
  feature's /zap zapface WebSocket plane. Drop the duplicate inline ops
  goroutine (and its now-unused io import) to avoid a double-bind CrashLoop.
- config.go: union HIP-0111 IAM-issuer-from-brand AND the ZAP web-origin allowlist.
- go.mod/go.sum: union both dep sets; take the feature's newer hanzoai/ai
  (2962d31c, /v1/embeddings + /v1/rerank) and main's newer luxfi
  (database v1.19.3, threshold v1.9.9, age v1.5.0). RESTORE the feature's
  'replace sashabaranov/go-openai => hanzoai/go-openai v1.40.0' that the merge
  dropped — ai's reasoning path needs Delta.ReasoningContent (fork-only).
  go.sum regenerated via go mod tidy honoring 34aa84e1 (first-party sumdb skip).

Build: go build ./... green (CGO=1; only luxfi/accel ld warnings). go vet clean.
2026-06-26 14:32:30 -07:00
hanzo-dev e7b34cadf8 feat(evals): mount /v1/evals/* — LLM-observability facade (HIP-0106)
evalsvc is a thin facade: proxies /v1/evals/{datasets,dataset-items,evaluators,
scores} → console's public REST API (Langfuse v3 fork, owns the eval/observability
data model) and orchestrates POST /v1/evals/runs against the in-process model
gateway (run model over dataset → score → trace). No eval logic reimplemented —
evals ARE LLM observability; cloud unifies the surface, console owns the logic.
Registered at order 145, before the AI /v1/* catch-all.
2026-06-26 14:08:08 -07:00
hanzo-dev 008433e546 feat(cli): hanzo cloud-control CLI (login/apps/deploy/clusters/build/k8s)
Extend cmd/hanzo with a gcloud/doctl-class control plane (client mode),
selected by the first token alongside the existing server-mode subsystem
dispatch. Thin client over IAM (hanzo.id), the platform REST control plane
(platform.hanzo.ai/v1), and the cloud /v1 API — no parallel API.

- login/logout/whoami/auth: IAM password grant, token in ~/.hanzo (0600)
- apps list|get|sync: platform apps board (declared/running/latest/drift)
- deploy: rolling zero-downtime redeploy via the container redeploy surface
- clusters list|get|create|select|install-baseline|target: dedicated DOKS
- build: platform-native (arcd) build enqueue
- k8s target; config get|set|list|path
- global --org/--output/--platform-url/--iam-issuer/--platform-token
- secrets only via env/~/.hanzo, never hardcoded; platform kubeconfig never fetched
- stdout kept machine-readable (server-graph init chatter redirected to stderr)

44 unit tests (client + command wiring via httptest). Verified live:
login -> whoami -> apps list (79 apps) -> deploy pricing (gen 4->5, zero-downtime).
2026-06-26 13:47:01 -07:00
hanzo-dev b47a1761fc chore(deps): bump hanzoai/ai → 2962d31c (/v1/embeddings + /v1/rerank)
Pulls hanzoai/ai feat/embeddings-rerank, which adds the OpenAI-compatible
POST /v1/embeddings and Cohere/Jina-compatible POST /v1/rerank endpoints on the
same auth + provider-routing path as /v1/chat/completions. Embeddings reuse the
already-configured OpenAI Direct key (kms://OPENAI_API_KEY); rerank needs no new
key (bi-encoder cosine over the resolved embedding model, native Jina/Cohere
proxy when keyed).
2026-06-26 13:30:26 -07:00
4d6925242c feat(provisioning): /v1 control plane that creates logical resources in live shared backends (#44)
* feat(cloud): derive IAM issuer from brand, plumb into Deps (HIP-0111)

The unified cloud binary is one artifact serving every brand's API host
(api.hanzo.ai, api.lux.cloud, api.zoo.cloud, api.cloud.pars.network). Brand
is a per-deployment value, but the IAM issuer was hardcoded to iam.hanzo.ai
for every brand and Config.IAMIssuer was never plumbed into Deps — so a lux
or zoo deployment would validate JWTs against the wrong issuer (or not at all,
subsystems having no issuer to use).

White-label the token-validation issuer by brand:
- brand.go: PUBLIC brand→IAM registry (issuer + domain). hanzo→iam.hanzo.ai,
  lux→lux.id, zoo→zoo.id, pars→pars.id, bootnode→id.bootno.de. One source of
  truth; public values live in code, not KMS.
- config: when CLOUD_IAM_ISSUER/--iam-issuer is unset, derive it from the
  brand via the registry (no longer silently iam.hanzo.ai for all brands).
- deps + build: add Deps.IAMIssuer, set from cfg in BuildDeps, so subsystems
  validate against {issuer}/v1/iam/.well-known/jwks per HIP-0111.

Root package: go build + go vet + go test green (registry + issuer-derivation
tests). The fused -tags cloud binary build is blocked by a pre-existing
workspace go.sum mismatch (luxfi/age via go.work), orthogonal to this change.

* deps: converge luxfi/threshold -> v1.9.9, fix luxfi/age v1.5.0 re-tag hash

Both threshold and age were re-tagged upstream, leaving cloud/go.sum with
hashes that no longer match what the proxy serves. threshold@v1.9.4's
recorded sum broke `go work sync` and the fused -tags cloud build:
  verifying github.com/luxfi/threshold@v1.9.4/go.mod: checksum mismatch

Converge on the single workspace-wide versions:
- threshold v1.9.4 -> v1.9.9 (latest 1.9.x; matches base + mpc)
  go.mod require bumped; go.sum gains v1.9.9 zip+go.mod sums; drops the
  unused v1.9.4 zip sum; keeps v1.9.4/go.mod (consensus@v1.25.0 still
  requires it in MVS) with the correct post-retag hash.
- age v1.5.0: corrected the stale zip hash
  (zC/Fw/ptZwAXr9nqrxmrcf8752EIl1Lq9RECp9OmCO0= ->
   G69HbSV4R3vKEH9B0CulnRaMdSdf4RalMgP8xKmxHeI=) to match the re-tagged
  module; go.mod sum was already correct. Version unchanged (v1.5.0,
  consistent with base/kms/mpc).

All hashes authoritative (match proxy + mpc/base go.sum). No suppression
flags, no downgrade.

* feat(provisioning): control plane that creates logical resources in live shared backends

Adds clients/provisioningsvc, registered at order 120 and linked by one blank
import in subsystems/subsystems.go. It turns "create a database" into a real
logical resource inside the already-live shared product backends, scoped to the
gateway-minted org (X-Org-Id / c.Org()).

Surface (kind in databases|vector|datastore|kv|search|storage|docdb):
  POST   /v1/<kind>        {"name":"<slug>"} -> 201 {id,kind,name,status,host,
                            port,username,database,connectionString,password?}
  GET    /v1/<kind>        -> 200 [{id,name,kind,status,host,port,createdAt}]
  GET    /v1/<kind>/<name> -> 200 {id,name,kind,status,host,port,username,database}
  DELETE /v1/<kind>/<name> -> 204
  (GET /v1/provisioning/health is auto-registered by Serve.)

Backends (admin creds + in-cluster .svc defaults via env):
  databases -> Postgres   (pgx)            CREATE ROLE + CREATE DATABASE
  vector    -> Qdrant      (net/http)      PUT /collections/{name}
  datastore -> ClickHouse (clickhouse-go)  CREATE DATABASE + USER + GRANT
  kv        -> Redis       (go-redis)      ACL SETUSER (keyspace-scoped)
  search    -> Meilisearch (net/http)      POST /indexes
  storage   -> S3/MinIO    (minio-go)      MakeBucket
  docdb     -> MongoDB     (mongo-driver)  createCollection + createUser

Physical resources are namespaced org_<org>_<name> so tenants never collide;
the name is validated to a slug at the boundary and all SQL identifiers are
quoted — injection-safe.

Secrets: per-resource passwords (databases/kv/datastore/docdb) are sealed in
Hanzo KMS (github.com/hanzoai/kms/sdk/go, client-side encrypted); only a
secret_ref is persisted in SQLite. When KMS is unconfigured the service
degrades safely — the password is returned once in the create response and
nothing is written in plaintext. vector/search/storage have no per-resource
password (shared key auth out of band).

Metadata lives in ONE pure-Go SQLite DB ({DataDir}/provisioning.db, modernc),
UNIQUE(org,kind,name); multi-step writes run in a transaction.

Drivers were already indirect deps; importing them promotes them with no
version bumps. Tests cover the store (insert/get/list/delete, org isolation,
duplicate->conflict), name validation, org sanitization, identifier safety,
and token generation.

* fix(provisioning): close cross-tenant physical-name collision + native kind naming

BLOCKING SECURITY FIX. physicalName folded the org→name boundary by joining
hyphen-underscored org and name, so two distinct tenants could map to ONE
physical backend resource: physicalName("acme","my-db") ==
physicalName("acme-my","db") == "org_acme_my_db" (bucketName collided too).
On KV that is a cross-tenant credential takeover (idempotent ACL SETUSER
overwrites tenant A's user/keyspace); on SQL/datastore/S3 a cross-tenant DoS
and existence oracle. UNIQUE(org,kind,name) did not protect the physical layer.

- physicalName(org,name) = "o" + hex(sha256(org))[:16] + "_" + sanitizeIdent(name):
  a FIXED-WIDTH org hash makes the boundary unambiguous, so cross-org folds are
  cryptographically negligible. bucketName derives from the (now injective)
  physical via the '_'→'-' bijection, so one guard covers every backend. Both
  stay backend-valid (Postgres 63-char identifier limit, S3 3-63 char bucket).
- store: add global UNIQUE(physical_name) index + PhysicalExists pre-check; the
  create handler now FAILS CLOSED with 409 BEFORE touching a backend on any
  residual name-fold, never silently sharing a physical resource. Row maps
  physical_name -> (org,kind,name) so names stay traceable.
- tests: injectivity (physicalName + bucketName), handler org-gate (empty
  X-Org-Id -> 403 for non-admin), KMS safe-degrade (password returned once,
  nothing persisted in plaintext, secret_ref empty).

NATIVE NAMING (Hanzo brand: product name, never upstream OSS name):
kind "databases"->"sql", "storage"->"s3"; final set = sql, vector, datastore,
kv, search, s3, docdb. env CLOUD_STORAGE_*->CLOUD_S3_*. Wire connection schemes
(postgres://, redis://, mongodb://) unchanged — protocol, not branding.

Minor: package-level Shutdown closes the store (mirrors plansvc); comment that
trusting X-User-IsAdmin is acceptable (blast radius = literal "admin" bucket).

---------

Co-authored-by: zeekay <z@zeekay.io>
2026-06-26 13:15:36 -07:00
hanzo-dev 3b56654865 chore(deps): bump hanzoai/ai → 41869ad8 (self-scoped /v1/update-preferences)
Picks up the account-backed user-preferences endpoint so console2 (and any
product) can persist cross-product, cross-device customizations onto the IAM
user account.
2026-06-26 11:15:07 -07:00
hanzo-dev 6971464edc feat(productsvc): expose console Search/Vector panels on cloud-api
The console Search/Indexes and Vector panels are hardcoded to call
api.cloud.hanzo.ai/api/search-docs/* and /api/vector/* with a bearer
service key. cloud-api owns those paths now: productsvc proxies them to
the in-cluster Meilisearch (search.hanzo.svc) and Qdrant (vector.hanzo.svc)
and translates each upstream response into the exact JSON the console's
tRPC routers decode (SearchIndex/SearchStats, VectorCollection/VectorStats).

Read-only, shape-translating glue — no search/vector logic reimplemented.
Bearer key enforced with a constant-time compare (gateway bypasses these
paths via AUTH_PUBLIC_PATHS since the key is opaque, not a JWT). Endpoints
degrade to an honest empty body when the upstream is unreachable, matching
the console panels' graceful-empty contract.

Verified locally against the live search/vector services: 6 real indexes
(43,162 docs), 2 real Qdrant collections; wrong/absent key -> 401.
2026-06-25 15:18:51 -07:00
0b4372f1a0 chore: bump luxfi/database v1.19.3 (#41)
Co-authored-by: zeekay <z@zeekay.io>
2026-06-25 15:15:47 -07:00
151e151f44 deps: converge luxfi/threshold → v1.9.9, fix luxfi/age v1.5.0 re-tag hash (#43)
* feat(cloud): derive IAM issuer from brand, plumb into Deps (HIP-0111)

The unified cloud binary is one artifact serving every brand's API host
(api.hanzo.ai, api.lux.cloud, api.zoo.cloud, api.cloud.pars.network). Brand
is a per-deployment value, but the IAM issuer was hardcoded to iam.hanzo.ai
for every brand and Config.IAMIssuer was never plumbed into Deps — so a lux
or zoo deployment would validate JWTs against the wrong issuer (or not at all,
subsystems having no issuer to use).

White-label the token-validation issuer by brand:
- brand.go: PUBLIC brand→IAM registry (issuer + domain). hanzo→iam.hanzo.ai,
  lux→lux.id, zoo→zoo.id, pars→pars.id, bootnode→id.bootno.de. One source of
  truth; public values live in code, not KMS.
- config: when CLOUD_IAM_ISSUER/--iam-issuer is unset, derive it from the
  brand via the registry (no longer silently iam.hanzo.ai for all brands).
- deps + build: add Deps.IAMIssuer, set from cfg in BuildDeps, so subsystems
  validate against {issuer}/v1/iam/.well-known/jwks per HIP-0111.

Root package: go build + go vet + go test green (registry + issuer-derivation
tests). The fused -tags cloud binary build is blocked by a pre-existing
workspace go.sum mismatch (luxfi/age via go.work), orthogonal to this change.

* deps: converge luxfi/threshold -> v1.9.9, fix luxfi/age v1.5.0 re-tag hash

Both threshold and age were re-tagged upstream, leaving cloud/go.sum with
hashes that no longer match what the proxy serves. threshold@v1.9.4's
recorded sum broke `go work sync` and the fused -tags cloud build:
  verifying github.com/luxfi/threshold@v1.9.4/go.mod: checksum mismatch

Converge on the single workspace-wide versions:
- threshold v1.9.4 -> v1.9.9 (latest 1.9.x; matches base + mpc)
  go.mod require bumped; go.sum gains v1.9.9 zip+go.mod sums; drops the
  unused v1.9.4 zip sum; keeps v1.9.4/go.mod (consensus@v1.25.0 still
  requires it in MVS) with the correct post-retag hash.
- age v1.5.0: corrected the stale zip hash
  (zC/Fw/ptZwAXr9nqrxmrcf8752EIl1Lq9RECp9OmCO0= ->
   G69HbSV4R3vKEH9B0CulnRaMdSdf4RalMgP8xKmxHeI=) to match the re-tagged
  module; go.mod sum was already correct. Version unchanged (v1.5.0,
  consistent with base/kms/mpc).

All hashes authoritative (match proxy + mpc/base go.sum). No suppression
flags, no downgrade.

---------

Co-authored-by: zeekay <z@zeekay.io>
2026-06-25 14:49:15 -07:00
hanzo-devandGitHub e1b4813776 feat(cloud): derive IAM issuer from brand, plumb into Deps (HIP-0111) (#42)
The unified cloud binary is one artifact serving every brand's API host
(api.hanzo.ai, api.lux.cloud, api.zoo.cloud, api.cloud.pars.network). Brand
is a per-deployment value, but the IAM issuer was hardcoded to iam.hanzo.ai
for every brand and Config.IAMIssuer was never plumbed into Deps — so a lux
or zoo deployment would validate JWTs against the wrong issuer (or not at all,
subsystems having no issuer to use).

White-label the token-validation issuer by brand:
- brand.go: PUBLIC brand→IAM registry (issuer + domain). hanzo→iam.hanzo.ai,
  lux→lux.id, zoo→zoo.id, pars→pars.id, bootnode→id.bootno.de. One source of
  truth; public values live in code, not KMS.
- config: when CLOUD_IAM_ISSUER/--iam-issuer is unset, derive it from the
  brand via the registry (no longer silently iam.hanzo.ai for all brands).
- deps + build: add Deps.IAMIssuer, set from cfg in BuildDeps, so subsystems
  validate against {issuer}/v1/iam/.well-known/jwks per HIP-0111.

Root package: go build + go vet + go test green (registry + issuer-derivation
tests). The fused -tags cloud binary build is blocked by a pre-existing
workspace go.sum mismatch (luxfi/age via go.work), orthogonal to this change.
2026-06-25 14:42:24 -07:00
hanzo-dev 974d22bc9c fix(zapface): serve /zap via native Fiber WebSocket (zip/wsx), not net/http adaptor
The net/http adaptor path 404'd: fasthttp's synthetic ResponseWriter can't be
hijacked, so coder/websocket.Accept failed and Fiber returned 404 for /zap
(confirmed live: 'GET /zap status 404'). Switch to zip/wsx (fasthttp/websocket)
which upgrades natively. Handler now returns a zip.Handler that mints the auth
slot BEFORE upgrade (401 fail-closed), captures the cookie/bearer in the
per-connection closure, and runs the binary-ZAP read loop with ws.ReadMessage/
WriteMessage. serve.go mounts app.Get("/zap", ...). Adds fasthttp/websocket
to go.sum (zip/wsx dep). End-to-end WS integration test rewritten against a
real zip app + native upgrade — green.
2026-06-25 14:08:16 -07:00
hanzo-dev 9bfef1a633 fix(serve): bind the :9090 health listener (/healthz, /readyz)
HealthListenAddr was declared but never bound — the operator's liveness
probe targets :9090/healthz and readiness :9090/readyz, so the pod failed
liveness and got SIGTERM'd in a ~90s CrashLoop (clean exit-0 'shutdown
requested'). Bind a stdlib health server on the health port serving
/healthz + /readyz (+ /health), separate from the :8000 API so the health
surface never shares failure modes with the API stack. Graceful-shutdown it
alongside the app.
2026-06-25 13:57:10 -07:00
hanzo-dev 5946d93ea1 test(zapface): end-to-end WebSocket integration + unauth-reject
Drive a real ZAP binary frame through the full server path (WS upgrade ->
mintCap -> rpc.ParseRequest -> dispatch -> Fiber /v1/* mount -> casibase
envelope -> rpc.BuildResponse -> WS reply), asserting: real provider data
round-trips, the session cookie is replayed to the /v1 handler, query/body
mapping works, unknown method surfaces !ok, and an unauthenticated upgrade
fails closed with HTTP 401.
2026-06-25 13:46:53 -07:00
hanzo-dev 8d1b23b358 feat(zapface): browser ZAP-over-WebSocket plane at /zap
Bind the scaffolded ZAP face: a WebSocket endpoint at /zap that speaks the
@zap-proto/web wire (github.com/zap-proto/go/rpc envelope + console2's inner
ZapRequest/ZapReply structs) and dispatches each call into the EXISTING /v1
casibase handlers in-process (adaptor.FiberApp) — one dispatch path, two
transports, zero duplicated business logic.

- zapface/wire.go: inner ZapRequest{method@0,payload@8}/ZapReply{ok@0,status@4,
  result@8,errorJson@16} codec + SuperJSON envelope ({"json":V}).
- zapface/dispatch.go: (method,input) -> /v1 HTTP replay; casibase
  {status,msg,data} -> ZapReply; get-* => GET+query, mutations => POST+body.
- zapface/server.go: coder/websocket upgrade, cookie/bearer auth slot
  (mintCap, fail-closed), per-frame rpc.ParseRequest -> dispatch ->
  rpc.BuildResponse.
- serve.go: mount app.All("/zap", ...) after MountAll.
- config.go: CLOUD_ZAP_WEB_ORIGINS allowlist.
- deps: promote coder/websocket + zap-proto/go@v1.3.0 (rpc pkg) direct.

Wire proven byte-exact vs the REAL @zap-proto runtime console2 ships, both
directions (TS buildRequest -> Go parse; Go reply -> TS parseResponse +
SuperJSON.parse). go test ./zapface green.
2026-06-25 13:29:13 -07:00
zeekay ece1634bfd feat(serve): HIP-0113 ops listener (:9090 /healthz /readyz /metrics)
Decomplect health/ops from the product API: the ops endpoints move off the
app listener (:8000, /v1/*) onto cfg.HealthListenAddr (:9090), unauthenticated
and unversioned. Liveness (/healthz) and readiness (/readyz) are now distinct.
stdlib-only, zero new deps. Makes cloud the reference impl for HIP-0113 and
unbreaks the cloud-api probe (was /v1/health → 404 on the unified binary).
2026-06-25 12:42:17 -07:00
zeekay 34aa84e12f fix(build): unpoison luxfi/age go.sum + first-party-scoped sumdb skip
luxfi/age v1.5.0 was re-pointed to a newer commit; sum.golang.org pins
the first-seen hash immutably, so a fresh build fetching our own module
hit `verifying github.com/luxfi/age@v1.5.0: checksum mismatch · SECURITY
ERROR`.

- go.sum: re-record age v1.5.0 zip h1: to live content (G69Hb… → zC/Fw…);
  /go.mod hash was unchanged.
- Dockerfile: add explicit GONOSUMDB scope (first-party only) and drop the
  fragile `rm -f go.sum && go mod download` self-heal — it masked the stale
  go.sum and re-recorded unverified hashes on any transient error. Correct
  committed go.sum + GOPROXY=direct is the one durable way.

Never global GONOSUMDB=* / GOINSECURE. Root cause is the upstream
force-re-tag practice, which must stop.
2026-06-25 00:58:58 -07:00
zeekay 469f072611 ci(deploy): notify universe with image-update on release
cloud had no universe dispatch → never auto-deployed. Add the same
image-update notify-universe job gateway/iam use. One contract.
2026-06-25 00:54:13 -07:00
35535cb1d1 build(hip-0106): unpoison module graph + tidy unified cloud binary (#40)
* build: HIP-0106 unified binary builds pure-Go static

- commerce v1.42.5 -> v1.42.27 (pure-Go modernc SQLite + tracked embed catalogs)
- pin luxfi/kms v1.11.6 (past force-re-tagged v1.11.0)
- exclude legacy ugorji/go (gin msgpack ambiguity)
- regenerate go.sum clean (sumdb off; force-re-tag poisoning)
- Dockerfile: GOPRIVATE + GOSUMDB=off + GOPROXY=direct + gh_token secret

Produces CGO_ENABLED=0 static /cloud (206M); all subsystems link.
Follow-up: repin hanzoai/kms off the dead v1.0.x pseudo-version to v0.159.x.

* build: fresh-origin go.sum + Dockerfile self-heal (v0.2.1)

v0.2.0's go.sum was regenerated from a stale module cache, so a clean container
build mismatched the force-re-tagged hanzoai/kms/sdk/go. Regenerate from fresh
origin (matches Docker's fetch), add self-heal (rm go.sum + retry on poisoning)
+ GOFLAGS=-mod=mod. New tag (not a force-re-tag of v0.2.0 — that's the anti-pattern).

* feat(subsystems): unified cloud = app layer only; infra/edge run separately

Per CTO: the fused binary is the APPLICATION layer. Removed from subsystems.go:
- amqp (unused)
- iam → iam.hanzo.ai (Casdoor), kms → kms.hanzo.ai (luxfi/kms): isolated control plane
- mcp: own deployment
- gateway, ingress: the edge (route *to* this binary)

Keeps: ai, authz, base, commerce, licensing, metrics, o11y, vfs, plansvc, pricingsvc.
Binary 154M→79M; v0.3.0 ships uncompressed (no UPX). Validated: boots ready on
SQLite with the default set, infra/edge excluded.

* build(deps): bump zap-proto/go to v1.3.0 (indirect)

* build(hip-0106): unpoison module graph + tidy unified cloud binary

- re-record poisoned luxfi/* + hanzoai/* go.sum hashes (threshold/keys/kms
  and kms SDK force-re-tagged at same version; origin authoritative,
  GOSUMDB off + GONOSUMDB covers both orgs).
- replace mattn/go-sqlite3 v2.0.3+incompatible (deleted upstream tag) -> v1.14.16.
- go mod tidy drops the unimported direct require hanzoai/gateway
  v2.9.7+incompatible (gateway subsystem is a separate deploy, not yet
  wired into the unified binary's subsystems.go).
- cmd/cloud and cmd/hanzo build green for darwin + linux/amd64.

---------

Co-authored-by: zeekay <z@zeekay.io>
2026-06-24 19:21:21 -07:00
hanzo-dev c05e1c372e deps(kms): refresh hanzoai/kms@v0.159.1 hash after brand-scrub history rewrite
kms history was rewritten to remove white-label brand leaks
(Liquidity/redacted); the v0.159.1 tag now points at a rewritten commit
with a new tree hash. go.mod content unchanged (only h1: tree hash
changes). cloud builds green (go build ./... exit 0). go mod verify: all
modules verified.
2026-06-24 18:05:23 -07:00
hanzo-dev a7cc3dbf69 deps: bump luxfi/kms -> v1.11.7 (clean tag after OSS brand-hygiene history rewrite) 2026-06-24 17:07:03 -07:00
hanzo-dev 47cb805284 chore(deps): bump ai to d9c02eca (ratelimit tier ?user= fix)
Pulls hanzoai/ai#fix(ratelimit): tier lookup queries commerce by org slug
(?user=) instead of ?apiKey=, fixing the 400 that starved paid orgs of
their rate limits. No other dep changes (age/threshold lines reordered,
same immutable bits).
2026-06-24 04:39:22 -07:00
hanzo-dev c08d3a8a2d build: pin luxfi/age+threshold go.sum to PROXY bits (Dockerfile is proxy-first)
The prior commit refreshed these via local direct fetch (GOPRIVATE), recording
the GitHub-rewritten bits. The cloud Dockerfile fetches via proxy.golang.org
first (GONOPROXY=hanzoai only), so the build downloaded the proxy bits and
failed go.sum verification on threshold@v1.9.4/go.mod. Restored to the exact
proxy hashes from v1.785.13 (which built clean). Only the ai bump remains the
real go.mod/go.sum delta.
2026-06-23 22:07:54 -07:00
hanzo-dev 887a51599d deps(ai): bump to 83876bf0 — hk- API-key resolution uses /v1/iam/get-user
Pulls the ai fix where the controller hk- key lookup hit the legacy
/api/get-user (served as @hanzo/id SPA HTML, breaking API-key auth on
/v1/chat/completions). Refreshes go.sum for force-retagged luxfi/age@v1.5.0
and luxfi/threshold@v1.9.4 (upstream re-tag drift, GOPRIVATE — not caused by
this change). cloud (CGO_ENABLED=0) builds clean.
2026-06-23 22:00:55 -07:00
hanzo-dev 1386c70292 deps: bump ai -> 91659573 (complete per-org balance sweep)
Folds in the zap-native + scraper per-org balance fixes so EVERY balance
check (gate, controller backstop, ZAP premium gate, zap balance query,
scraper preflight) reads the one per-org balance. Final image for the
per-org billing unification.
2026-06-23 21:33:13 -07:00
hanzo-dev 577cb2dcfd deps: bump ai -> e6402611 (per-org balance backstop)
Completes the per-org billing unification: both the BalanceGateFilter AND the
resolveProviderForUser backstop now key by org slug + stamp X-Hanzo-Org, so the
single per-org credit is the balance every LLM call checks.
2026-06-23 21:27:09 -07:00
Hanzo 1c2da48aee deps: bump ai -> ee423689 (zen→DO-AI routing + provider secret self-heal)
Makes the LLM layer real:
- zen3/zen4/aliases re-pointed from dead Fireworks serverless to DO-AI
- do-ai provider key unified to kms://DO_AI_API_KEY (env-first resolution)
- provider re-seed self-heals ClientSecret/ProviderUrl/State on boot
2026-06-23 21:17:53 -07:00
hanzo-dev 98a044c669 build: resync luxfi go.sum to proxy/checksum-DB bits (fix re-tag drift)
Several luxfi modules were force-rewritten upstream so go.sum captured the
rewritten direct-fetch bits, which conflict with the proxy's checksum-DB
artifacts: luxfi/age v1.5.0, luxfi/threshold v1.9.4, luxfi/zap v0.8.8.
Combined with the GOPROXY split (luxfi via proxy, hanzoai/zap-proto direct),
go.sum now pins the proxy/sumdb-authoritative hashes. luxfi stays in GONOSUMDB
so the few proxy-absent versions (e.g. luxfi/constants@v1.5.8 → 404) fall to
direct without a sumdb-lookup error while still pinned by go.sum.

Validated locally with the exact Dockerfile env: full 'go mod download' +
'CGO_ENABLED=0 go build ./cmd/cloud' succeed, 'go mod verify' = all modules
verified, binary embeds ai v1.785.9-...-44cd5f9a (per-org balance gate).
2026-06-23 21:12:47 -07:00
hanzo-dev 4344031d91 build: split GONOPROXY/GONOSUMDB so luxfi/* resolves via proxy (fix age re-tag)
GOPRIVATE forces BOTH direct-fetch and sumdb-bypass for every match, so
luxfi/age went direct to GitHub and hit the force-rewritten v1.5.0 tag
(h1:KEjq... != go.sum/sum.golang.org h1:G69H...), failing go mod download.
All luxfi/* modules we use are on the public proxy, so drop luxfi/* from
GONOPROXY (keep only hanzoai/* + zap-proto/*, whose just-pushed pseudo-
versions the proxy 404s). luxfi/* now resolves via proxy.golang.org =
immutable checksum-DB bits matching go.sum. Validated locally with the exact
Dockerfile env: luxfi/age proxy-clean, hanzoai/ai direct-clean.
2026-06-23 21:04:20 -07:00
hanzo-dev 09f19a7828 build: proxy-first GOPROXY so force-rewritten upstream tags can't poison builds
luxfi/age v1.5.0 was re-pushed on GitHub with content differing from the bits
sum.golang.org recorded (h1:G69H... original vs h1:KEjq... rewritten), so the
GOPRIVATE-forced direct fetch failed go.sum verification. Public luxfi/* are all
on the proxy; resolve through proxy.golang.org first (immutable, checksum-DB
artifacts) and fall back to direct only for repos the proxy 404s (private). Pins
public deps to verified bits; private resolution unchanged.
2026-06-23 20:58:16 -07:00
hanzo-dev 3c46dd741e deps: bump ai -> 44cd5f9a (per-org LLM balance gate)
Unifies the LLM balance gate with commerce's per-org credit: the gate now
keys billing by org slug and stamps X-Hanzo-Org so a single per-org credit
(X-Org-Id=<org>) is the balance the gate checks and usage debits. Fixes
insufficient_balance on funded orgs (gate previously queried per-user in the
default 'hanzo' namespace).
2026-06-23 20:53:12 -07:00
hanzo-dev dd57a8db70 deps: bump ai -> f3a36aa2 (iam SDK /v1/iam GetUrl + signout nil-guard)
Fixes console2/cloud login end-to-end: the IAM SDK now loads the app cert from
/v1/iam/* so Signin's ParseJwtToken succeeds (was 'iamsdk: not valid PEM'),
establishing a real session that admin endpoints accept.
2026-06-22 01:01:45 -07:00
hanzo-dev 688f3425cd build: drop re-added stale luxfi/threshold go.sum entry (re-tagged upstream) 2026-06-21 20:55:49 -07:00
hanzo-dev 47de155564 deps: bump hanzoai/dbx -> 6b6ceb7 (composite fields as JSON)
Fixes get-account 'unsupported type []model.SearchResult, a slice of struct'
and the matching scan errors — Message.SearchResults/VectorScores/Suggestions/
ToolCalls and all slice/map model fields now round-trip via JSON in the data
layer. Completes SQLite-native cloud-api login.
2026-06-21 20:54:03 -07:00
hanzo-dev 46e74b1af3 build: tolerate re-pushed private module tags (GOFLAGS=-mod=mod)
luxfi/threshold@v1.9.4 is being re-tagged upstream, so its checksum drifts
from go.sum and 'go mod download' fails in CI. Record private-module hashes at
build time (-mod=mod; GOPRIVATE keeps them off the public sumdb) and drop the
stale threshold entry so it re-records cleanly.
2026-06-21 19:42:28 -07:00
hanzo-dev 4b175102f4 deps: bump hanzoai/ai -> 152107f4 (dbx.Sync creates casibase schema on SQLite)
Unblocks the Base/SQLite cloud-api: the ai subsystem now creates its tables
from the Go structs on a fresh embedded SQLite store (no external migrations).
2026-06-21 19:37:14 -07:00
hanzo-dev a98366d098 deps: bump hanzoai/ai -> v1.785.9-0...a98523d4 (StringList []string scan fix)
Pins the merged ai main commit that adds StringList (sql.Scanner/Valuer over
JSON) for list columns — fixes the casibase data-layer panic
'unsupported Scan ... string into *[]string' that broke OAuth sign-in.
2026-06-21 19:15:26 -07:00
hanzo-dev eb60e364d2 deps: bump hanzoai/ai v1.785.7 -> v1.785.8 (CopyRequestBody for POST body parsing)
v1.785.8 sets beego CopyRequestBody in Bootstrap so the unified binary's AI
controllers can read POST bodies (json.Unmarshal of c.Ctx.Input.RequestBody);
without it /v1/chat/completions returned 'unexpected end of JSON input'. Completes
the unified-AI serve path: routing (bare /v1/*) + no-panic (session mgr) +
scratch-safe (memory sessions) + body parsing (CopyRequestBody).
2026-06-21 10:56:59 -07:00
hanzo-dev 27c7b46b2b deps: bump hanzoai/ai v1.785.6 -> v1.785.7 (memory session provider for scratch image)
v1.785.7 adds the scratch-safe memory session provider on top of the bare /v1/*
mount + session-manager build. Without it the unified binary 503'd on every
request (file session provider can't write in the read-only scratch root). With
all three fixes, /v1/chat/completions and the other OpenAI routes serve through
the unified binary.
2026-06-21 10:40:18 -07:00
hanzo-dev 632376b753 fix(pricing): drop bare /v1/models alias so AI owns the OpenAI model list
In the unified binary the pricing subsystem (order 112) mounted a bare /v1/models
alias that shadowed the AI subsystem's (order 150) OpenAI-compatible /v1/models —
the {data:[{id,…}]} model list the api.hanzo.ai gateway forwards to cloud-api and
clients (cowork model picker) consume. Pricing's annotated catalog already lives
at /v1/pricing/models, so the bare alias only introduced a shape regression.
Remove it; pricing stays strictly under /v1/pricing/*. Now /v1/models, like the
other OpenAI routes, resolves to AI's beego handler via its /v1/* catch-all.
2026-06-21 10:32:25 -07:00
hanzo-dev 3176460ddc deps: bump hanzoai/ai v1.785.5 -> v1.785.6 (bare /v1/* mount + session manager)
v1.785.6 carries BOTH unified-binary fixes:
1. AI mounts casibase routes at bare /v1/* (not /v1/ai/*) so the api.hanzo.ai
   gateway, which forwards /v1/chat/completions etc. unchanged, resolves.
2. beego session manager built in Bootstrap so forwarded requests don't panic.

Together these make /v1/chat/completions, /v1/chat, /v1/models, /v1/messages
serve through the unified binary exactly as the gateway sends them.
2026-06-21 10:29:05 -07:00
hanzo-dev 13238567d6 deps: bump hanzoai/ai v1.785.4 -> v1.785.5 (build beego session manager in Bootstrap)
ai v1.785.5 fixes the embedded /v1/ai/* HTTP 500: the unified binary never
calls beego.Run(), so beego.GlobalSessions was nil and every forwarded request
panicked in SessionStart. v1.785.5 builds the session manager in the shared
Bootstrap, so /v1/ai/chat/completions, /v1/ai/models and all nested routes
serve. Cloud binary builds green against it.
2026-06-21 10:14:16 -07:00
hanzo-dev f6b79a0a74 ci(build): self-contained arcd build, GHCR login via GH_PAT
The ghcr.io/hanzoai/cloud package is linked to hanzoai/ai (cloud->ai rename),
so this repo GITHUB_TOKEN is denied write (permission_denied: write_package) via
the shared workflow. Build self-contained on the hanzo-build-linux-amd64 scale
set and log into GHCR with GH_PAT (admin:org+write:packages). gh_token still
feeds the Dockerfile private-module fetch. Dropped GHA cache (same denial +
artifact quota).
2026-06-21 09:31:43 -07:00
hanzo-dev 53b1fb49b9 deps: consume gateway/v2 v2.14.8 (proper /v2 module path)
gateways v2 tags were invalid Go modules (go.mod lacked the /v2 path), so
gateway v2.9.7+incompatible could not resolve on a clean fetch and cloud failed
to build. gateway v2.14.8 fixes the module path; import the /v2 path in the
subsystems bundle and pin v2.14.8. Build + go mod verify clean; binary boots
with no init panic.
2026-06-21 09:23:34 -07:00
hanzo-dev dca49c1d52 deps: pin gateway v2.9.6+incompatible (v2.9.7 added a go.mod without /v2 path)
gateway v2.9.7 introduced a go.mod still declaring module path
github.com/hanzoai/gateway at a v2 tag, which makes v2.9.7+incompatible an
invalid version (a module with a go.mod at major>=2 must use a /vN path).
v2.9.6 is the last go.mod-free v2 tag, so +incompatible is valid there; API is
identical for the subsystem blank-import. One patch down, no code change.
2026-06-21 09:10:37 -07:00
hanzo-dev cbc792f075 deps: refresh go.sum for force-pushed private tags (hanzoai/base v1.3.2, luxfi/threshold v1.9.4, ...)
Several private module tags were re-tagged after the committed go.sum was
generated, so a clean CI fetch failed go.sum verification (SECURITY ERROR:
checksum mismatch). Regenerated the affected private entries from current
remote content via go build -mod=mod (versions unchanged). Build is green and
boots without panic; go mod verify passes.
2026-06-21 09:03:59 -07:00
hanzo-dev 50e033e570 ci(build): route amd64 to ARC scale set hanzo-build-linux-amd64 by name
ARC ephemeral runners only match jobs targeting the scale-set name as a label.
The shared workflows default [self-hosted,linux,amd64] matches only classic
static runners (evo pool, offline) so the job sat queued with the listener
reporting assigned-job=0. gateways successful builds use runs-on:
hanzo-build-linux-amd64 (runner hanzo-build-linux-amd64-cvs28-runner-*); pass
that as runner-amd64.
2026-06-21 08:22:13 -07:00
hanzo-dev 1ed94b79a6 ci(build): delegate to shared arcd docker-build.yml (self-hosted, billing-immune)
GitHub-hosted runners for this org are billing-frozen (jobs fail in ~5s:
"recent account payments have failed"), so the bespoke ubuntu-latest release
workflow can never start. Use the canonical hanzoai/.github docker-build.yml
reusable workflow, which runs on the self-hosted arcd pools and injects GH_PAT
as the gh_token BuildKit secret the Dockerfile needs for private cross-org Go
modules. amd64-only (cluster arch) to complete without the arm64 pool.
2026-06-21 08:09:19 -07:00
hanzo-dev 9bf6f04235 ci(build): authenticate private cross-org Go modules in image build
The unified binary pulls private hanzoai/* AND luxfi/* modules; the public
proxy 404s on them and the default GITHUB_TOKEN cannot read cross-org repos, so
the Docker build failed at go mod download.

- Dockerfile: split deps layer; GOPRIVATE + BuildKit gh_token secret +
  git insteadOf to fetch private modules over authenticated git (mirrors the
  proven hanzoai/ai Dockerfile). COPY --chmod=0755 the binary so the scratch
  image can never ship a non-executable /cloud (the 0644 CrashLoop class).
- release.yml: source the gh_token from the org GH_PAT (cross-org RO PAT that
  actually exists), not the never-configured HANZO_GH_RO_TOKEN.
2026-06-21 08:07:41 -07:00
hanzo-dev 8a6be4c683 deps: cut cloud-api onto unified binary — ai v1.785.4 (+#29 runtime init, /v1/billing path), beego v2.3.10 grace guard, go-openai fork
Fixes user-token AI on api.hanzo.ai:
- ai v1.785.4: AI runtime initializes in Mount() (#29) so /v1/ai/* serves real
  completions (no more 503 "ai runtime not initialized"); ai self-meters
  Commerce on the correct /v1/billing/* path (1.784.2 casibase used the dead
  /api/v1/billing/* -> 404 for real user JWTs, blocking the prepaid balance
  gate + usage auto-debit).
- beego v2.3.10: grace flag-registration guard so the unified binary (ai beego
  v1 + iam beego v2) does not panic ("flag redefined: graceful") at init.
- ai v1.785.4 also swaps deprecated denisenkom/go-mssqldb -> maintained
  microsoft/go-mssqldb (one mssql driver registration; no "sql.Register called
  twice" panic).
- replace sashabaranov/go-openai => hanzoai/go-openai v1.40.0 (ReasoningContent
  field) — mirrors ai own replace, which does not transit to this main module.

Verified: CGO_ENABLED=0 go build ./cmd/cloud produces a 316MB executable that
boots clean (base + full subsystem set) with no init panic; full boot stops
only on expected in-cluster config (IAM_KEYS_URL/IAM_AUDIENCE), supplied by the
cloud-api CR env.
2026-06-21 08:05:32 -07:00
Antje Worring c47f89f85e cloud: pin commerce/metering v0.1.0 (drop local replace) 2026-06-20 17:31:18 -07:00
Antje Worring 8d7d324a11 cloud: zip-native fail-closed billing gate (wraps commerce/metering) 2026-06-20 17:13:49 -07:00
z 1579c773ac deps: pin luxfi/kms v1.11.6 (published) — pkg/iam v1.18.5 referenced phantom v1.11.3 2026-06-19 01:15:08 -07:00
z 6f7bd64ca4 deps: pin goldap-free iam (pkg/iam v1.18.5, iam v1.19.6) — resell-clean (zero GPL-2.0) 2026-06-19 01:08:48 -07:00
antje 7a2d11c8e5 chore: add LICENSE (Apache-2.0) — Hanzo-native 2026-06-19 00:39:25 -07:00
hanzo-dev 4f77c15de0 chore: add Apache-2.0 LICENSE (Copyright 2026 Hanzo AI Inc) 2026-06-18 23:40:49 -07:00
bf48e97120 refactor(cmd): single subsystems bundle — define the mounted set once (DRY) (#19)
cmd/cloud and cmd/hanzo each blank-imported the same 16-subsystem list, so
adding/removing a subsystem meant editing two files (repeat-yourself). Move
the list into one package, github.com/hanzoai/cloud/subsystems; both
entrypoints blank-import only that. One source of truth for what's linked into
a Hanzo binary — dispatcher and full-surface binary mount an identical set by
construction.

(Bundle is a sibling subpackage, not the root cloud package: subsystems import
cloud for Deps+Register, so a root bundle would cycle.)

Verified: go build -tags 'cloud cloud_mount' . ./subsystems ./cmd/cloud
./cmd/hanzo green (-mod=readonly); hanzo --help still lists 18 subcommands
(16 subsystems + cloud + datastore); go test ./... green.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-17 09:29:28 -07:00
b85f0eaa66 fix(deps): commerce v1.39.1->v1.42.5 — mount commerce into the unified binary (#18)
cloud pinned commerce v1.39.1, which predates commerce's cloud-mount
integration: cloud.Register("commerce", 100, ...) in init() behind
//go:build cloud, added at v1.42.5. So commerce silently was NOT in the fused
surface or hanzo's subcommands. v1.42.5 (latest tag) registers correctly —
`hanzo --help` now lists commerce; the unified binary composes 16 subsystems.
iam stays v1.19.4 (no cascade). go build -tags 'cloud cloud_mount' + full
go test ./... green.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-17 09:21:19 -07:00
050bc2b5c8 feat(cmd): land unified hanzo binary + extract shared cloud.Serve (DRY) (#17)
Adds cmd/hanzo — one binary dispatched by subcommand: `hanzo <svc>` serves one
subsystem, `hanzo cloud` the full fused surface, `hanzo iam` the standalone
Beego IdP (iamserver.Run), `hanzo datastore` documents the ClickHouse boundary.

DRY: the cloud-server body (compose root + HIP-0106 /v1/<name>/health contract
+ graceful shutdown) is extracted from cmd/cloud's main() into cloud.Serve(enable)
— the ONE shared place. cmd/cloud now calls cloud.Serve(nil), gaining graceful
shutdown + health endpoints (strict superset of its prior body, no regression).
cmd/hanzo dispatches through the same cloud.Serve.

Beego non-collision holds: iam registers routes inside iamserver.Init(), not
package init(); one Beego v2 path; visor (Beego v1) intentionally unlinked.
iam v1.19.4 moves indirect->direct (cmd/hanzo imports iam/iamserver).

Verified: go build -tags 'cloud cloud_mount' . ./cmd/cloud ./cmd/hanzo green
(-mod=readonly), go vet clean, hanzo --help lists 17 subcommands.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-17 05:47:13 -07:00
8e5b85f7f3 fix(deps): iam v1.19.1→v1.19.4 + pkg/iam v1.18.1→v1.18.4 — fix cloud-api boot panic (#16)
iam v1.19.0–v1.19.3 panic at boot: routers/router.go registered
GET /v1/iam/run-authz-command → ApiController.RunAuthzCommand, a method never
added, so Beego panics at route registration when iamserver.Init() runs (this
hit cloud-api too). v1.19.4 (cut from iam main: dangling route removed +
initAdminUser seeds via conf.AdminOrg) fixes it. Transitive zap-proto/go
v0.3.0→v1.1.0 required by pkg/iam v1.18.4. go build -tags 'cloud cloud_mount'
./cmd/cloud green; -mod=readonly verified.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-17 05:36:42 -07:00
414229184b fix(go.sum): re-record re-tagged hanzoai/lux module checksums (unblocks build) (#15)
A chain of re-tagged modules produced checksum SECURITY ERRORs that
block 'go build ./...':
  - github.com/hanzoai/base@v1.3.2          (h1)
  - github.com/luxfi/threshold@v1.9.4       (h1)
  - github.com/hanzoai/kms/sdk/go@v1.0.0    (h1 + go.mod)
Re-record the current proxy hashes. go build ./... -> exit 0 (cmd/cloud links).

Co-authored-by: zooqueen <dev@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-17 00:53:19 -07:00
Abhishek KrishnaandGitHub fd386b3b1a fix(go.sum): refresh stale hash for retagged luxfi/threshold (#7)
github.com/luxfi/threshold v1.9.4 was re-pushed at the same version
tag without updating go.sum in this repo. The recorded h1: digest no
longer matches the upstream zip on proxy.golang.org, so cold clones
fail at `go mod verify` / `go build`:

  verifying github.com/luxfi/threshold@v1.9.4: checksum mismatch
      downloaded: h1:H69e9QkvygDtWkni1FkD5ztLdiTasmpJXcuVzgebdxo=
      go.sum:     h1:/TsgIzo/e/DIx++J0+9eNuS7HkpSaXbVk+HvhlUOsmE=
  SECURITY ERROR

Regenerating go.sum (single line update) restores parity with
upstream and the build succeeds.

Reproduction (pre-fix):
  git clone https://github.com/hanzoai/cloud
  cd cloud && GOPRIVATE='github.com/hanzoai/*,github.com/luxfi/*' \
    go build ./cmd/cloud
  # verifying github.com/luxfi/threshold@v1.9.4: checksum mismatch

No code changes outside go.sum.
2026-06-16 20:28:51 -07:00
Abhishek KrishnaandGitHub bf6dbad118 ci: add release workflow to publish ghcr.io/hanzoai/cloud (#8)
The README advertises `docker run -p 8080:8080 ghcr.io/hanzoai/cloud:latest`
but there's no release pipeline in the tree to produce that image.
This workflow publishes the Docker image on git-tag push (matching
v*), on default-branch push (as :latest and :sha-<short>), and on
manual dispatch.

Includes a Buildx secret pattern for fetching private upstream
modules (hanzoai/iam, hanzoai/commerce, hanzoai/gateway, ...) using
either the default GITHUB_TOKEN or an org-level HANZO_GH_RO_TOKEN
when cross-org private reads are required.
2026-06-16 20:28:47 -07:00
Abhishek KrishnaandGitHub 7b0200ab6a chore: add helm/cloud minimal chart (#9)
Reference Helm chart that renders a single Deployment + Service +
optional PVC for the unified cloud binary. Mirrors the binary's
CLI flags via .Values.hanzo (brand, domain, dataDir, iamIssuer,
enable). Pod runs as nonroot UID 65532 matching the Dockerfile.

Not a substitute for luxfi/operator + Service CRD — this chart is
for users who want raw k8s manifests without installing the
operator first.
2026-06-16 20:28:44 -07:00
Abhishek KrishnaandGitHub 1afeeb041f chore: add deploy/compose.yml for single-node VPS deployment (#6)
Reference Docker Compose manifest for the unified cloud binary, with
matching .env.example and a deploy/README.md that documents required
vs optional environment variables (the binary refuses to mount IAM
without HANZO_IAM_ISSUER, so make that explicit).

No code or config changes outside deploy/.
2026-06-16 20:28:41 -07:00
Abhishek KrishnaandGitHub 7ab0d887bb chore(scripts): add scripts/smoke-runtime.sh — boot + probe the real binary (#11)
`cmd/cloud-smoke` (existing) exercises the in-process mount path on a
mock zip.App with two health endpoints. It does not boot the actual
`cmd/cloud` binary or hit the HTTP surface customers will use.

This script closes that gap: it builds `./cmd/cloud`, boots it under
the same default-safe `--enable` list used in deployments (omits the
`iam` subsystem until the v1.19.2 boot panic is patched), waits for
the listener to bind, then probes the five endpoints whose expected
status is fixed by the HIP-0106 contract:

  /healthz                200   process health probe
  /v1/models              200   model catalog (no auth)
  /v1/plans               200   plansvc (goja-hosted)
  /v1/pricing             200   pricingsvc (goja-hosted)
  /v1/base/collections    401   base alive, auth-gated

If any probe regresses, the script dumps the tail of the boot log and
exits non-zero — making it usable as a CI gate and as a local "does my
clone actually serve?" check.

Env knobs (`PORT`, `LISTEN`, `BIN`, `DATA_DIR`, `ENABLE`,
`KEEP_RUNNING`, `BOOT_TIMEOUT`) let it drop into different
environments without a Makefile change. The `IAM_*` env vars default
to the production hanzo.id JWKS — required by `kms` for inbound JWT
validation even with `iam` disabled — and can be overridden per
deployment.

Pairs with the Makefile in #5: `make smoke` already exists for the
mount-time path; this is the runtime counterpart and can be wired as a
sibling target (`make smoke-runtime`) in a follow-up once #5 lands.
2026-06-16 20:28:37 -07:00
Abhishek KrishnaandGitHub f65f264567 chore: add Makefile with build/test/docker targets (#5)
Minimal developer ergonomics for the unified cloud binary. Targets
wrap go build / go test / docker build for the existing Dockerfile,
plus a `make run` shortcut that matches the README quickstart
(--enable=iam,base,kms,gateway,o11y).

No code changes outside the new Makefile.
2026-06-16 20:28:34 -07:00
Abhishek KrishnaandGitHub 8c72dbf11f chore: add .gitignore and .dockerignore (#10)
Repo currently has neither file. Two practical consequences:

1. `docker build .` copies the entire context including `.git/`, IDE
   metadata, OS detritus (`.DS_Store`), and any local `.env` — bloats
   the build context and risks baking secrets into image layers.
2. Without a `.gitignore`, the build output binary (`/cloud` per the
   `Dockerfile` final stage), local `.env` files, and editor leftovers
   are easy to commit by accident.

Both files cover the standard Go-project surface (binary at `/cloud`,
test outputs, coverage, env files), plus IDE/OS noise. The
`.dockerignore` additionally drops docs and tests so they don't enter
the runtime image — the binary is what ships, the README lives on
GitHub.

No behavior change; the binary the Dockerfile builds is bit-identical.
What changes is build-context size and the safety margin around
accidental commits.
2026-06-16 20:28:30 -07:00
70363681b0 fix(auth): default CLOUD_IAM_ISSUER to https://iam.hanzo.ai (was .id typo) (#14)
IAM issues JWTs with iss=https://iam.hanzo.ai, but cloud-api defaulted the
expected issuer to https://iam.hanzo.id — so EVERY hanzo.id-login JWT was
rejected with 'invalid issuer claim (iss)' and the AI gateway's JWT auth path
was dead for all users (only hk-*/sk-* keys worked). One-char .id->.ai fix.

Co-authored-by: hanzo-dev <dev@hanzo.ai>
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-16 17:55:57 -07:00
hanzo-devandGitHub 45dd3c4a83 test(cloud): drop cmd/cloud-smoke, add real orchestrator integration test (#13)
The cloud-smoke command was a throwaway harness that hand-mounted fake health
routes and avoided the real subsystem matrix (citing build issues in cmd/cloud
that are now fixed — the full binary builds). Replaced with a proper go test in
package main that exercises the actual path:

- TestRegistryAssemblesSubsystems: every subsystem main.go imports self-registers
  via init() into cloud.Registry (proves the unified binary wires the matrix).
- TestMountAllAndServeHealth: BuildDeps -> MountAll -> serve; the self-contained
  subsystems (base, authz, amqp, metrics, plans, pricing) mount in-process and
  serve /v1/<name>/health = 200 via the real zip/fiber + jsonenc stack
  (app.Fiber().Test, no listener / external services).
- TestDepGatedSubsystemsFailClosed: ai, o11y mount and return >=500 from the
  disabled-dep stub — proving the BuildDeps three-mode contract end to end.

Discovered (not fixed here — separate subsystem bug): enabling iam panics with
"'RunAuthzCommand' method doesn't exist in the controller ApiController".

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-16 09:56:21 -07:00
hanzo-devandGitHub ea46670309 fix(go.sum): refresh moved private-tag hashes so it builds clean (#12)
hanzoai/base@v1.3.2 and hanzoai/kms/sdk/go@v1.0.0 were re-tagged upstream, so
the recorded go.sum hashes no longer matched — `go build`/`go test` failed with
checksum mismatch (SECURITY ERROR) for anyone fetching fresh. Refreshed the
private-module hashes against the current tags.

Verified: go build ./... and go test ./... pass in default -mod=readonly mode.
No local replace directives (the 9 replaces are all published version pins for
the krakend/traefik gateway stack). cmd/cloud links to a single 272M binary.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-16 09:47:05 -07:00
Antje Worringandhanzo-dev 20f9df47c5 feat(cloud): pin metrics v0.4.0 — ZAP MsgMetricBatch receiver + per-tenant + durable
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-15 14:15:56 -07:00
Antje Worringandhanzo-dev 7c0d39e316 feat(cloud): pin metrics v0.3.0 — per-tenant observability isolation (X-Org-Id)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-10 13:44:48 -07:00
Antje Worringandhanzo-dev 13911e452c feat(cloud): pin metrics v0.2.0 — durable native metrics+logs+traces
The unified binary now serves the full native observability stack at
/v1/{metrics,logs,traces}/* — WAL-durable (survives restart, verified), zero
prometheus, zero Grafana. This is the working replacement for the Loki/Tempo/
SigNoz vendoring.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-10 08:20:43 -07:00
Antje Worringandhanzo-dev 275650bb89 feat(cloud): mount native hanzoai/metrics v0.1.0 (ZAP-native metrics store)
The prometheus-free replacement for the Grafana/Prometheus observability
backends. Registers at order 40, serves /v1/metrics/{health,batch,write,query};
ingests luxfi/metric.MetricBatch (the ZAP MsgMetricBatch wire shape). Verified
live: write+query and batch+query roundtrips return correct series. Binary stays
at zero prometheus. (Also refreshed the stale kms/sdk/go go.sum hash from the
wave's re-tag.)

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-09 22:24:44 -07:00
hanzo-dev 9530b85e8b build(deps): re-pin plans/pricing/licensing to release tags; drop local replace
Replace the dev pseudo-versions + the local `replace github.com/hanzoai/licensing
=> ../licensing` directive with the published release tags now that the three
subsystems are merged + tagged:

  - github.com/hanzoai/plans     v1.2.0  (was pseudo @147eced7)
  - github.com/hanzoai/pricing   v1.3.0  (was pseudo @0c4b4c12)
  - github.com/hanzoai/licensing v0.1.0  (was v0.0.0 + replace => ../licensing)

licensing@v0.1.0 requires github.com/hanzoai/cloud@v0.0.0-00010101...; that
self-reference resolves to this main module, so no replace is needed. go.mod/
go.sum are tidy and `go build -mod=readonly ./cmd/cloud` produces the 303M
unified binary (boots with --enable=plans,pricing,licensing; all health 200).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 19:58:14 -07:00
hanzo-dev 0c44327f7b Merge feat/plans-pricing-goja-clean into feat/mount-licensing
Combine the licensing Mount (PR #3) with the plans+pricing goja mounts
(PR #4) onto one branch for the unified-binary re-pin.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 19:54:22 -07:00
hanzo-dev cfbf5e014b feat(plans+pricing): mount @hanzo/plans + @hanzo/pricing via base+goja
Mount the Node @hanzo/plans (data) and @hanzo/pricing (Express) services
INTO the unified cloud binary under /v1/plans/* and /v1/pricing/*, running
their JS inside the dop251/goja engine (the same engine base/plugins/gojavm
uses) — per HIP-0106. No service rewrite; Ship-of-Theseus to pure Go later.

New packages (the glue — clean module boundaries, no service source copied):
  - clients/gojahost: a reusable goja VM-pool host. Compiles a service repo's
    goja/bundle.js once, pre-warms a runtime pool (mirrors gojavm's pool +
    compile-once + per-runtime ensureLoaded discipline), injects the catalog
    JSON as globals, and dispatches handle({route,params,tenant}) -> {status,
    body} with ctx-cancel interrupt. Eager-loads one runtime so a bad bundle
    fails at Mount, not first request.
  - clients/plansvc: Mount(app, deps) for /v1/plans/*. Loads the @hanzo/plans
    bundle + embedded catalog, registers zip routes (subscriptions, cloud,
    blockchain, dns, gpu, regions, storage, tools, policy, schema, vocab,
    resolve/:id, entitlements/:id), threads X-Org-Id as the tenant for
    per-reseller (tenant_id,id) catalog scoping. The entitlements.mjs
    transforms (fromLegacy/toLicenseFeatures/resolvePlan) run in goja.
  - clients/pricingsvc: Mount(app, deps) for /v1/pricing/* + /v1/models.
    Express does NOT run in goja, so the Express transport is dropped; the
    server.mjs read handlers run in goja via the bundle. The sync.mjs markup
    (toMTok/processOpenRouterModel/...) also runs in goja via applyMarkup();
    the admin-gated POST /v1/pricing/sync does the live OpenRouter fetch in Go
    (net/http) and feeds raw JSON into the goja markup. _internal (provider
    costs/routing) is stripped from public responses.

Wiring: cmd/cloud/main.go blank-imports both wrappers; each init() calls
cloud.Register (plans order 111, pricing 112, after iam/commerce/licensing).
go.mod references hanzoai/plans + hanzoai/pricing as their own private Go
modules (the JS + data live there, embedded; nothing copied into cloud).

Tests: clients/{gojahost,plansvc,pricingsvc}/*_test.go exercise the real
embedded bundles (vocab, resolve+license_features, 404s, _internal strip,
exact markup math). Verified end-to-end: binary boots with --enable=plans,
pricing; all routes serve real data through goja over HTTP; X-Org-Id tenant
scoping confirmed (reseller override-wins, isolation holds).

Also corrects a stale go.sum entry for github.com/hanzoai/kms/sdk/go@v1.0.0
(the module was retagged; the recorded hash no longer matched the origin,
blocking any build that pulls base/iam/commerce -> kms). Updated to the
current origin hash.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 18:42:54 -07:00
hanzo-dev b714cf28ac feat(cloud): mount licensing subsystem + commerce entitlement-copy
Wire the private hanzoai/licensing Go subsystem into the unified cloud
binary per HIP-0106, following the iam/commerce/ai Mount(app, deps)
pattern. Clean module boundary: licensing is imported as its own private
module (its mount.go self-registers via init(); cmd/cloud blank-imports
it). No subsystem source is copied into cloud — the signer/fingerprint
secret logic stays in the licensing module.

- cmd/cloud: blank-import github.com/hanzoai/licensing (order 110, after
  iam=50 and commerce=100, since the /v1/licensing/issue flow depends on
  both identity and entitlements).
- go.mod: require licensing + local replace (co-developed private module;
  production resolves via tag/pseudo-version, drop the replace).
- types.CommerceClient: add CheckEntitlement(ctx, orgID, productID) plus
  the LicenseEntitlement transport type. This is the entitlement flow that
  gates issuance: commerce answers "does this tenant own the licensed
  product?" and returns the plan's FLAT license-features per the
  @hanzo/plans toLicenseFeatures vocab contract; the licensing mount copies
  them verbatim into the signed token's `features` so the engine enforces
  exactly the plan that was bought.
- clients: implement CheckEntitlement on the disabled (fail-closed) and
  ZAP-RPC commerce stubs; in-process pass-through already satisfies it.

Tenant-scoped via orgID (X-Org-Id). Real KMS stays a licensing follow-up
(scaffold TODO); the Mount + entitlement-copy are the deliverable here.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 18:23:19 -07:00
Antje Worringandhanzo-dev 539a6b1d68 fix(cloud): pin gateway v2.9.7 (clean, no local replaces)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 17:30:42 -07:00
Antje Worringandhanzo-dev ac6d1c0abd fix(cloud): correct gateway pin to v2.9.6+incompatible (prev go.mod was broken)
Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 16:46:14 -07:00
Antje Worringandhanzo-dev dcaa461d0e fix(cloud): pin gateway v2.9.6 — ZERO prometheus in the unified binary
gateway dropped the legacy opencensus SaaS exporters (stackdriver was the last
prometheus source). Combined with o11y v1.3.7 + alertmanager/krakend-otel forks +
base v1.3.2 + kms Corona, the binary now links zero real prometheus packages.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 16:45:19 -07:00
Antje Worringandhanzo-dev 7e28f27c38 fix(cloud): pin base v1.3.2 — network metrics on luxfi/metric (prometheus 6->1)
Real prometheus in the unified binary is now a single leaf package
(prometheus/prometheus/model/value via a gateway dep). Down from 16+.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 16:44:05 -07:00
Antje Worringandhanzo-dev 1080b7fc6e fix(cloud): prometheus 16->6 pkgs — krakend-otel fork + gateway v2.9.5
replace krakend-otel => hanzoai/krakend-otel v0.13.1 (prom-free fork); pin
gateway v2.9.5 (opencensus prometheus exporter removed, counters -> luxfi/metric).
With the alertmanager fork + o11y v1.3.7 + iam v1.18.1, the only prometheus left
is the hanzoai/common+alertmanager fork shim core (6 pkgs) — needs those forks to
shed prometheus/common internally.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 16:41:05 -07:00
Antje Worringandhanzo-dev 1f3fed619e fix(cloud): pin iam/pkg/iam v1.18.1 — kill duplicate-beego graceful flag panic
pkg/iam v1.18.0 imported upstream github.com/beego/beego/v2 while the rest of the
binary uses the hanzoai/beego prom-free fork; both register a global 'graceful'
flag in init() -> panic at startup. v1.18.1 (already fixed on iam main, just
untagged) uses the fork only. The unified binary now boots and shows the
white-label -brand/-domain/-enable tenancy flags.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 16:11:47 -07:00
Antje Worringandhanzo-dev d278bb53f5 fix(cloud): green the unified binary — o11y v1.3.7 + alertmanager fork replace
o11y's prometheus->hanzoai/alertmanager replace must be carried by the main
module (cloud), since a dependency's replace is ignored by consumers. With
o11y v1.3.7 (no-prometheus) + kms v0.159.1 (Corona), the full HIP-0106 binary
(11 subsystems on zip+ZAP, /v1 routing, luxfi/log+metric) compiles end-to-end.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 16:06:39 -07:00
Antje Worringandhanzo-dev 4e02c1814e fix(deps): pin hanzoai/kms v0.159.1 (Corona signing fix)
Clears the kms SignWithRingtail blocker. cloud's remaining build failure is
hanzoai/o11y v1.3.6 (incomplete prometheus/common -> hanzoai/common fork).

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 12:49:18 -07:00
Antje Worringandhanzo-dev 747d624b2a fix(deps): drop 13 cross-repo local replaces; pin siblings to real published versions
Build still blocked separately on kms SignWithRingtail (luxfi/kms API gap) and
o11y type-mixing — tracked upstream; this lands the no-local-replace requirement.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>
2026-06-08 12:11:00 -07:00
1868 changed files with 443038 additions and 1905 deletions
+41
View File
@@ -0,0 +1,41 @@
# VCS
.git/
.gitignore
.gitattributes
# CI / repo metadata not needed inside the build
.github/
# Docs (image runs the binary; readers visit GitHub)
*.md
LICENSE
SECURITY.md
# Already-built binary at repo root (matches .gitignore)
/cloud
# Environment files (never bake secrets into images)
.env
.env.*
# IDE / editor
.vscode/
.idea/
*.swp
*.swo
# OS metadata
.DS_Store
Thumbs.db
# Tests stay out of the runtime image
*_test.go
# Local build outputs
/dist/
/build/
/bin/
# The Dockerfile itself doesn't need to be in the context it builds
Dockerfile
.dockerignore
+9
View File
@@ -0,0 +1,9 @@
<svg xmlns="http://www.w3.org/2000/svg" width="1280" height="640" viewBox="0 0 1280 640" role="img" aria-label="cloud">
<rect width="1280" height="640" fill="#0A0A0A"/>
<svg x="96" y="215" width="210" height="210" viewBox="0 0 67 67"><path d="M22.21 67V44.6369H0V67H22.21Z" fill="#fff"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z" fill="#fff"/><path d="M22.21 0H0V22.3184H22.21V0Z" fill="#fff"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z" fill="#fff"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z" fill="#fff"/></svg>
<text x="378" y="276" font-family="Inter,system-ui,-apple-system,sans-serif" font-size="78" font-weight="800" letter-spacing="-2" fill="#ffffff">cloud</text>
<text x="378" y="322" font-family="Inter,system-ui,sans-serif" font-size="30" fill="#ffffff" opacity=".66">Hanzo Cloud — unified Go binary that imports every Hanzo-native…</text>
<rect x="378" y="338" width="806" height="3" rx="1.5" fill="#ffffff" opacity=".9"/>
<text x="378" y="390" font-family="Inter,system-ui,sans-serif" font-size="24" font-weight="600" fill="#ffffff" opacity=".5">github.com/hanzoai</text>
<text x="1184" y="390" text-anchor="end" font-family="Inter,system-ui,sans-serif" font-size="24" font-weight="600" fill="#ffffff" opacity=".5">hanzo.ai</text>
</svg>

After

Width:  |  Height:  |  Size: 1.3 KiB

+46
View File
@@ -0,0 +1,46 @@
# Built binaries (Dockerfile output + `go build ./cmd/hanzo`)
/cloud
/hanzo
# Local build directories
/dist/
/build/
/bin/
# Go test + coverage artifacts
*.test
*.out
coverage.txt
coverage.html
# cek encryption sidecars are key material — never commit one from a source tree.
# Tests seal their stores under t.TempDir(); a sidecar in a package dir (e.g. from a
# test that opened ":memory:") is a mistake. The cek testdata fixtures are the one
# intentional exception.
*.dek
*.cek.lock
!cek/testdata/**
# Environment files
.env
.env.*
!.env.example
# IDE / editor
.vscode/
.idea/
*.swp
*.swo
*~
# OS metadata
.DS_Store
Thumbs.db
# Logs
*.log
.shots/
.claude/
.worktrees/
native/flags/target
+199
View File
@@ -0,0 +1,199 @@
name: CI/CD
# The ONE pipeline for cloud, on our own runners against git.hanzo.ai.
#
# THE LAW: `.github/workflows` holds exactly one file — a sync nudge that runs
# zero CI. Everything that gates, builds or deploys lives here.
#
# It absorbs the three pipelines that used to run beside each other:
#
# .github/workflows/cicd.yml → `gate` (unchanged: the ~7-line caller; every
# real detail still lives in the repo-root hanzo.yml, which
# platform.hanzo.ai reads too, so no build logic moved)
# .github/workflows/containment.yml → `containment` (verbatim; only its own
# self-exclusion path follows the file)
# .hanzo/workflows/deploy.yml → deleted, not moved (below)
#
# CI gates. It does not deploy, and deliberately builds no cloud image: that
# image and its v* tags have ONE owner, clients/platform/release.go (POST
# /v1/runner {release:true}) — a second builder on the same commit is the
# double-build hanzo.yml's images: block already refuses for this reason.
# deploy.yml claimed to do both and could do neither: it shelled
# `buildctl-daemonless.sh`, absent from the image this fleet actually serves for
# `hanzo-build-linux-amd64` (catthehacker/ubuntu:act-24.04 —
# universe:infra/k8s/git-runner/statefulset.yaml), read a GIT_CLONE_TOKEN secret
# that exists on neither the repo nor the org, and ended in a `kubectl patch app`
# that cd.hanzo.ai's selfHeal undoes on its next poll. Rollout is, and stays, a
# reviewed tag pin in hanzoai/universe.
on:
push:
branches: [main]
pull_request:
# The sync (sync-from-github.yml) dispatches this workflow by name after a
# fast-forward: a push made with the workflow token does not trigger workflows,
# so without this trigger every synced commit would gate nothing. deploy.yml
# declared no dispatch trigger, which is why that curl could only 404.
workflow_dispatch:
concurrency:
group: cicd-${{ github.ref }}
cancel-in-progress: true
jobs:
# Test gate + the decoupled native flags staticlib image, driven by hanzo.yml.
gate:
uses: hanzoai/ci/.hanzo/workflows/build.yml@v2
secrets: inherit
# Guards the Stage-1 byzantine ceremony containment (clients/controlplane,
# build tag `controlplane`). Its increment-1 crypto is stub/forgeable BY
# DESIGN (SHA256-of-public-inputs commitments, symmetric-HMAC
# proof-of-possession, seed-derived threshold shares — see
# clients/controlplane/doc.go) and MUST NEVER reach a release/serve binary.
# Three independent checks; any one failing blocks the merge:
#
# 1. grep (tag) — no build/release invocation anywhere in the repo
# (Dockerfile, Makefile, shell scripts, any workflow) may pass a `-tags`
# value containing `controlplane` to go build/vet/run/install. The
# package's own `//go:build controlplane` tag declarations
# (clients/controlplane/*) are the thing being guarded, not a violation,
# and are excluded by path.
# 2. grep (spoof) — no build/release invocation may pass
# `-X testing.testBinary=1` (or any -ldflags containing it) to a REAL
# `go build`. That linker flag is what `go test` itself uses to make
# testing.Testing() report true (cmd/go/internal/load/test.go) — the
# runtime guard in containment.go trusts that signal, so this is the one
# concrete way to spoof it in a non-test binary. This grep is what turns
# "someone could type this" into "CI fails the PR that types it".
# 3. graph — no cmd/ main may reach clients/controlplane through its
# untagged import graph (`go list -deps`), and
# `go build ./clients/controlplane/...` with no tag must match zero
# buildable packages (proves the tag still gates every file in it).
#
# Runtime belt-and-suspenders (defense in depth, not a substitute for the
# above): clients/controlplane/containment.go fail-closed panics if its stub
# crypto is ever constructed outside a go-test binary (testing.Testing()==
# false) — see TestContainment_NonHarnessProcessRefuses in
# containment_test.go. KNOWN RESIDUAL: testing.Testing() is a linker-set
# string var (testing.testBinary), not cryptographically bound to "actually
# is a test" — `-ldflags="-X testing.testBinary=1"` spoofs it in a real
# binary. Check #2 above is the mitigation: it fails the PR that would ship
# that flag. Closing the residual for real needs a signal `go build` cannot
# produce at all (increment-2, tracked in doc.go) rather than one merely
# absent by convention.
containment:
runs-on: [hanzo-build-linux-amd64]
steps:
- uses: actions/checkout@v4
- name: grep — no build/release path may set -tags controlplane, or spoof testing.Testing()
run: |
set -euo pipefail
hits=0
# NOTE: exclusions are plain substring matches on the path (not
# anchored to a leading "./") so this is robust across grep
# implementations that format recursive-search paths differently.
# char class includes `!` so a build-constraint negation form
# (`-tags '!x,controlplane'`) cannot slip the grep. (Belt only: the
# positive-proof step below is the syntax-agnostic guarantee — the
# package has zero untagged files, so importing it into serve code
# fails the untagged `go build ./...` regardless of any -tags syntax.)
if grep -RnE -- '-tags[= ]*["'"'"']?[!A-Za-z0-9_, ]*\bcontrolplane\b' \
--exclude-dir=.git --exclude-dir=node_modules --exclude-dir=.claude --exclude-dir=vendor \
. 2>/dev/null \
| grep -v '\.git/' \
| grep -v 'clients/controlplane/' \
| grep -v '.hanzo/workflows/cicd.yml:'; then
echo "::error::found a build/release invocation passing -tags controlplane — clients/controlplane's stub crypto must never enter a release/serve binary (see clients/controlplane/doc.go)"
hits=1
fi
if grep -RnE -- 'testing\.testBinary' \
--exclude-dir=.git --exclude-dir=node_modules --exclude-dir=.claude --exclude-dir=vendor \
. 2>/dev/null \
| grep -v '.hanzo/workflows/cicd.yml:'; then
echo "::error::found a reference to testing.testBinary outside the Go toolchain itself — this is the linker var that spoofs testing.Testing() in a real (non go-test) binary; the containment.go runtime guard trusts that signal, so setting it anywhere in a real build path defeats it (see doc.go)"
hits=1
fi
if [ "$hits" -ne 0 ]; then exit 1; fi
echo "OK: no build/release path sets -tags controlplane or spoofs testing.Testing()"
- uses: actions/setup-go@v5
with:
go-version-file: go.mod
- name: go env for private modules
env:
GH_PAT: ${{ secrets.GH_PAT }}
# GOPRIVATE names exactly the namespace that is private. github.com/hanzoai/*
# is: ai, account, commerce, orm, xorm, beego, csqlite and ~30 more are
# private repos, so they must resolve direct+authenticated and skip a sumdb
# that cannot see them. Everything else stays on the public proxy + checksum
# db, which is what makes a module hash immutable: zap-proto (all 55 repos)
# and luxfi (all 37 deps here) are public and proxy-served.
#
# This previously named zap-proto — public, and never the reason anything
# here was direct — and then set GOSUMDB=off to compensate for hanzoai/*
# being absent, which disabled checksum verification for EVERY module in the
# build, public ones included. Naming the private namespace is what the off
# switch was standing in for.
run: |
git config --global url."https://x-access-token:${GH_PAT}@github.com/".insteadOf "https://github.com/"
{
echo "GOPRIVATE=github.com/hanzoai/*"
echo "GOPROXY=https://proxy.golang.org,direct"
} >> "$GITHUB_ENV"
- name: zen streaming-fix floor — go.mod must pin github.com/hanzoai/zen >= v1.4.1
# The SSE body-close fix (zen commit 50328b8, first released in zen v1.4.1)
# is what makes streaming completions return a body instead of an empty
# stream. A stale-branch merge that reverts go.mod's zen pin below the floor
# silently re-breaks streaming, and `next build`'s ignoreBuildErrors hides
# the runtime break — so no image may be cut on a regressed pin. This is the
# durable root-cause guard: it reads the EFFECTIVE module version (post-MVS,
# exactly what the build links) and fails the PR/push below the floor.
run: |
set -euo pipefail
FLOOR="v1.4.1"
V="$(go list -m -f '{{.Version}}' github.com/hanzoai/zen)"
echo "effective github.com/hanzoai/zen = ${V} (floor ${FLOOR})"
# semver-correct compare: the lowest of {V, FLOOR} under `sort -V` must be
# the FLOOR, i.e. V >= FLOOR. (sort -V orders v1.4.2 above v1.4.10 too.)
low="$(printf '%s\n%s\n' "$V" "$FLOOR" | sort -V | head -1)"
if [ "$low" != "$FLOOR" ]; then
echo "::error::github.com/hanzoai/zen is pinned at ${V}, below the streaming-fix floor ${FLOOR} — this re-breaks SSE streaming (empty completions). Re-pin zen to >= ${FLOOR} in go.mod before merging."
exit 1
fi
echo "OK: zen ${V} is at or above the streaming-fix floor ${FLOOR}"
- name: positive proof — clients/controlplane is unreachable from the default build
run: |
set -euo pipefail
# Containment is an IMPORT-GRAPH property, so prove it with the import
# graph. This step used to lead with `go build ./...`, which compiles
# AND LINKS every cmd/ main — and linking needs
# native/flags/target/release/libhanzo_flags.a, the Rust staticlib
# clients/flags pulls in under cgo (clients/flags/engine.go). Nothing
# in THIS job builds it: `make native` runs in the gate job, in that
# job's own workspace. It passed on GitHub only because the arc
# runners reuse a workspace and target/ is gitignored, so an earlier
# gate job's leftover .a was still sitting there; on a container
# runner with a fresh volume every cmd/ main died at
# `ld: cannot find .../libhanzo_flags.a`. The compile was never the
# proof anyway — `go list -deps` reads the same untagged file set
# without linking, and the gate job is the ONE place that builds.
for m in $(go list ./cmd/...); do
if go list -deps "$m" | grep -qx 'github.com/hanzoai/cloud/clients/controlplane'; then
echo "::error::$m links clients/controlplane into a real binary — containment breach"
exit 1
fi
done
out="$(go build ./clients/controlplane/... 2>&1 || true)"
if ! printf '%s' "$out" | grep -q 'matched no packages'; then
echo "::error::clients/controlplane built successfully WITHOUT -tags controlplane (containment breach): $out"
exit 1
fi
echo "OK: containment holds — clients/controlplane has zero buildable files by default and is linked into no cmd/ binary"
+53
View File
@@ -0,0 +1,53 @@
name: Sync from GitHub
# git.hanzo.ai is canonical and builds (cicd.yml); development also lands on
# github.com/hanzoai/cloud. ONE deterministic direction: an in-cluster PULL. The
# runner reaches both ends (GitHub outbound, this Gitea via the instance URL
# actions/checkout already uses), so the sync has no ingress dependency.
#
# Fast-forward ONLY: a divergence fails loudly here instead of force-pushing
# either side.
#
# Inert until hanzoai/cloud stops being a Gitea pull mirror — while it is one,
# the forge overwrites main from GitHub on its own timer and rejects the push
# below. That conversion is also what turns Actions on here (measured today:
# mirror: true, has_actions: false ⇒ zero native runs).
on:
schedule:
- cron: '*/10 * * * *'
workflow_dispatch: {}
concurrency:
group: sync-from-github
cancel-in-progress: false
jobs:
ff-main:
runs-on: [hanzo-build-linux-amd64]
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
persist-credentials: true
- name: Fast-forward main from github.com/hanzoai/cloud
env:
GH_PAT: ${{ secrets.GH_PAT }}
run: |
set -euo pipefail
git fetch --quiet "https://x-access-token:${GH_PAT}@github.com/hanzoai/cloud.git" main
LOCAL="$(git rev-parse HEAD)"; REMOTE="$(git rev-parse FETCH_HEAD)"
if [ "$LOCAL" = "$REMOTE" ]; then echo "in sync at $LOCAL"; exit 0; fi
if git merge-base --is-ancestor "$LOCAL" "$REMOTE"; then
echo "fast-forwarding $LOCAL -> $REMOTE"
git push origin "$REMOTE:refs/heads/main"
# A push made with the workflow token does not trigger workflows, so
# synced commits would never build. Dispatch the pipeline explicitly.
curl -fsS --max-time 20 -X POST \
-H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
-H "Content-Type: application/json" \
"${{ github.server_url }}/v1/repos/${{ github.repository }}/actions/workflows/cicd.yml/dispatches" \
-d '{"ref":"main"}' \
&& echo "CI/CD dispatched" || echo "CI/CD dispatch failed (non-fatal — next direct push builds)"
elif git merge-base --is-ancestor "$REMOTE" "$LOCAL"; then
echo "canonical is AHEAD of GitHub — nothing to pull (never force from here)."
else
echo "::error::main DIVERGED between GitHub ($REMOTE) and canonical ($LOCAL) — refusing to force. Reconcile manually."
exit 1
fi
+208
View File
@@ -0,0 +1,208 @@
# Unified IAM Auth + Tenant Billing Contract
The ONE way every Hanzo product surface authenticates a user and bills their
usage. hanzo.chat, hanzo.app, studio.hanzo.ai, and console.hanzo.ai all
implement THIS contract against `hanzoai/cloud` (api.hanzo.ai). There is no
per-app billing, no shared API key, and no second way to do any of it.
## The chain, end to end
```
Browser (a surface)
│ 1. OIDC Authorization Code + PKCE, PUBLIC client (no client secret)
IAM (hanzo.id / lux.id / zoolabs.id / pars.id …)
│ 2. issues user tokens. owner claim = the user's org (the tenant).
Surface backend / SPA
│ 3. holds the user's IAM token server-side (session / httpOnly cookie).
│ UI's actively-selected (org, project) = the tenant context.
│ 4. EVERY call to cloud forwards THAT user's IAM bearer, unchanged:
│ Authorization: Bearer <user IAM token>
│ X-Project-Id: <active project> (optional; org comes from token)
cloud (api.hanzo.ai) — SanitizeIdentity → BillingGate
│ 5. validates the JWT (JWKS sig + issuer-set + audience + exp).
│ 6. derives (org, project): org is PINNED from the verified `owner`
│ claim (client-supplied X-Org-Id is stripped); project is the
│ claim-bound X-Project-Id (else soft-scoped).
│ 7. meters against the org's shared plan allowance; overflow →
│ pay-as-you-go on the org's linked billing account.
commerce (billing/pricing) — ONE ledger, keyed on (org, project)
```
One identity (the user's IAM token), one tenant key (org from the token's
`owner`, project from the active selection), one ledger. Every surface is a thin
client of this; none of them holds a shared key or bills anything itself.
## 1. Login — OIDC Authorization Code + PKCE, PUBLIC client
- **Public client, no client secret.** The token endpoint auth method is `none`;
security comes from PKCE (`code_challenge_method=S256`) + the signed `state`,
not a shared secret baked into a browser-delivered app. A public client cannot
leak a secret it does not have.
- Strategy registration MUST NOT be conditioned on a client secret. (The chat
login outage was exactly this: `configureOpenId` was gated on
`OPENID_CLIENT_SECRET`, so a secretless public client never registered the
`openid` passport strategy → "OpenID strategy not registered".)
- The `owner` claim is the tenant org. `sub` is the user. A surface reads the org
from `owner` (fallback `organization`), never from a client-set field.
- Reference implementation: `studio/middleware/iam_auth_middleware.py`
(`_authorize_redirect` builds the PKCE authorize URL; `handle_callback` adds a
`client_secret` to the token exchange ONLY if one is configured — public by
default).
## 2. Tenant context — active (org, project)
- A user belongs to one or more orgs; the token's `owner` is the home org, and
IAM may carry the full set (`organizations`/`orgs`/`groups`).
- The UI's actively-selected org + project is the tenant context for the session.
Studio carries the active org in the `studio_active_org` cookie and validates
it against the token's org set (`middleware/session.py: resolve_org`) — a user
can only ever select an org their token authorizes.
- cloud pins the billing org from the VERIFIED `owner` claim, so even a forged
active-org header cannot move spend to another tenant. The active project is
forwarded as `X-Project-Id` and is honored as a hard scope only when it is
claim-bound; otherwise it degrades to a soft scope (cannot hard-stop, cannot be
evaded). See `middleware_billing.go: identityFromCtx`.
## 3. Forwarding to cloud — the user's token, never a shared key
- EVERY request to cloud carries `Authorization: Bearer <the signed-in user's IAM
token>`. The token is held server-side (session / httpOnly cookie) and is never
exposed to the browser JS.
- The forwarded token MUST be principal-bound to the authenticated user (`sub`
equals the session principal) and unexpired. Fail secure: if no such token is
available, DENY (401 / "sign in") — never fall back to an ambient or service
credential, which would run as the wrong principal or drain a shared org.
- NO shared keys. NO per-app keys. NO per-user minted `hk-` keys for chat. The
IAM token IS the credential and the billing identity.
- Reference implementations:
- `chat/api/server/routes/agents/cloud.js` +
`chat/packages/api/src/endpoints/custom/tenantBearer.ts` — the ONE resolver
(`resolveTenantBearer`) both the agents path and the chat-completion path use.
- The chat-completion endpoints declare `apiKey: "{{LIBRECHAT_OPENID_TOKEN}}"`;
the custom-endpoint initializer substitutes the resolved session bearer at
request time (`chat/packages/api/src/endpoints/custom/initialize.ts`).
## 4. Billing — ONE path keyed on (org, project)
cloud is the single meter and gate. `SanitizeIdentity` (mirrored in-binary by
`auth_identity.go`) validates the token and exposes `c.Org()` / `c.User()` /
`ValidatedProject(c)`. `BillingGate` (`middleware_billing.go`) then:
- **Billing key = org.** Prepaid balance is per-org: one org credit covers the
whole org. `identityFromCtx` sets `User = org` (bare `sub` only when org is
absent). Keying per-user would 402 a fully funded org.
- **Scope axes = (project, service).** `project` is the caller's claim-bound
`X-Project-Id`; `service` is SERVER-derived from the route (`/v1/ai/*` → `ai`),
never a client field, so a caller cannot spoof another service's cap.
- **Shared plan, then PAYG.** `AuthorizeVerdict` checks the org's shared plan
allowance and per-scope spend caps in one round trip; overflow bills
pay-as-you-go against the org's linked billing account. Outcomes map to a frozen
HTTP contract:
- `200` allowed (with `X-Spend-Warn: <pct>` at a soft cap threshold),
- `402 insufficient_balance` — add credits at console.hanzo.ai,
- `402 spend_cap_exceeded` — raise the scope cap at console.hanzo.ai/limits,
- `503 balance_unavailable` — commerce unreachable, fail-closed.
- **Single charge.** `/v1/ai/*`, `/v1/agents/*`, and the other self-metering
subsystems record their own per-org usage; the edge gate returns price 0 for
them so nothing is billed twice (`DefaultPrice` / `selfMeteredPrefixes`).
## 4a. Per-product metering + the product/agent cost axes
Two metering seams share the ONE commerce ledger (`Deps.Metering`):
- **`BillingGate`** (`middleware_billing.go`) — the request EDGE, priced by PATH
(`DefaultPrice`). `/v1/ai/*` self-meters token spend upstream (gateway/ai), so it
is price-0 here to avoid double-billing.
**Auto-routing binds to the resolved model.** ai serves a virtual `auto`
(alias `zen-router`) model that it resolves to a concrete model id *before*
pricing/billing, then meters its own token cost keyed on the SERVED model and
reports it via the `X-Routed-Model` response header (echoed in the body
`model`). Because the edge prices `/v1/ai/*` by PATH (0), never by the request
model, `auto` bills as whatever it resolved to — the ai per-token meter is the
single source of the charge. The edge passes `X-Routed-Model` through untouched,
so the model reported to the client equals the model billed. Proven end-to-end:
`auto_routing_billing_test.go` (`TestAutoRoutingBillsAsResolvedModel`,
`TestDefaultPriceAiPathModelAgnostic`).
- **`ResourceMeter`** (`resource_billing.go`) — IN-HANDLER, priced per-org after the
caller's org is resolved. Every non-LLM product uses it: `Gate` (fail-closed
pre-auth, `available >= fee`, default fee $1.00 / `DefaultResourceFeeCents`) then
`Meter`/`MeterUsage` (debit-on-success, `provider = <product>`). Balance floor is
enforced BY DEFAULT — a zero/negative-balance priced call → **402** (proven:
`clients/{functions,s3,agents,ml,provisioning}/billing_test.go` `*RefusesUnfundedOrg`).
Metering+gating coverage (each meters its OWN org, debits on success):
| Product | provider label | fee knob | code |
|---|---|---|---|
| functions | `functions` | `CLOUD_FUNCTIONS_FEE_CENTS` | `clients/functions/invoke.go` |
| s3 | `s3` | `S3_*` | `clients/s3/s3.go` |
| agents | `agent` | `CLOUD_AGENT_FEE_CENTS` | `clients/agents/agents.go` |
| compute / GPU | `compute` | provision knobs | `clients/ml/ml.go`, `clients/visor/*` |
| provisioning (sql/kv/vector/docdb) | `provisioning` | `CLOUD_PROVISION_FEE_CENTS[_KIND]` | `clients/provisioning/*` |
| automations | `automations` | `CLOUD_AUTOMATIONS_FEE_CENTS` | `clients/automations/automations.go` |
| tracker | `tracker` | fee knob | `clients/tracker/tracker.go` |
| security | `security.scan` | — | `clients/security/security.go` |
**Product/agent read axes.** The console's per-product Metrics dashboard groups on
`metadata.product` (and `metadata.agent`). Commerce's `RecordUsage` persists the
metering SURFACE (`provider`) and billed UNIT (`model`) but has **no `product`
field** (its `usageRequest` drops `project`/`service`/`product`/`agent`). So the
customer read handler `clients/billing/usage.go` is the ONE read-side adapter:
`usage()` fetches the org-scoped ledger and, on 200, injects a canonical
`metadata.product` onto every row (`productOf`: `agent→agents`,
`provisioning→<kind>`, token-metered→`inference`, else `provider`) so the
breakdowns POPULATE from the SAME charged ledger. It also honors, server-side (was
silently ignored):
- `GET /v1/billing/usage?product=<id>` — filter to one product,
- `GET /v1/billing/usage?groupBy=product` — per-product rollup
`{product,requests,amountCents}`.
A row that already carries `metadata.product`/`agent` wins, so this degrades to a
no-op when the meter/commerce persist them natively (forward-compatible).
**Remaining checklist** (each is the same seam):
1. **Native `product`/`agent` fields** — add `Product`/`Agent` to
`commerce/metering.Usage` + `commerce` `usageRequest`/metadata, have each
`ResourceMeter` caller pass its product id, and drop the read-side `productOf`
derivation (decomplect: the meter KNOWS its product; record it, don't re-derive).
Cross-repo (commerce) — additive/backward-compatible.
2. **Agent-NAME axis** — needs (1): the agent run debit records `provider=agent` +
`model=<llm>` but not the agent name, so `metadata.agent` stays honest-empty
until commerce persists an `agent` field the agents meter sets to `a.Name`.
3. **compute split** — `ml` (predict) and `visor` (GPU) both meter `provider=compute`;
read-side can't split `inference` vs `gpus`. Needs (1) so each sets its product id.
4. **exec / containers** (`clients/exec`, Code Interpreter) — authed by a shared
service key (X-API-Key), NO per-org identity, so it can't meter per-org; its
compute is billed upstream at the chat/agent layer that invokes it.
5. **playground** — routes to `/v1/ai/*`, already metered as AI inference.
## 5. Secrets
- Per-tenant, KMS-managed only (`kms.hanzo.ai`, KMSSecret CRDs). No shared
service key stands in for a user. The only service tokens that exist are
narrow, per-tenant, and never used to impersonate a user for LLM spend.
- A surface's own OIDC registration is a PUBLIC client — there is no client
secret to store.
## Surface conformance (as of this contract)
| Surface | Login (PKCE public) | Forwards user token | Org from `owner` | Billed via cloud (org,project) |
|---|---|---|---|---|
| **studio.hanzo.ai** | ✅ reference | ✅ (validates locally) | ✅ | ⚠️ renders run on studio's own GPU workers and self-report to commerce keyed by org via a per-tenant commerce token — org-keyed, but not the forward-bearer-to-gateway path (studio does not call the cloud LLM gateway for its core renders) |
| **console.hanzo.ai** | ✅ | ✅ same-origin `/v1` through the gateway | ✅ | ✅ (it IS the canonical consumer) |
| **hanzo.chat** | ✅ (this change) | ✅ (this change: `resolveTenantBearer`) | ✅ | ✅ (this change: forwards bearer to `/v1/ai/*`) |
| **hanzo.app** | ❌ confidential client (`IAM_CLIENT_SECRET`, userinfo/introspect) | ✅ to its own backend; org from token `owner` | ✅ | ❌ builder AI runs on OpenRouter with an apiKey (`lib/llm/generation-api.ts`), NOT the cloud gateway — off the unified meter |
hanzo.app is the remaining gap: it needs the same treatment chat just got — switch
its IAM registration to a PKCE public client, and route its builder AI generation
through api.hanzo.ai forwarding the user's IAM bearer so usage meters against the
org plan instead of a shared OpenRouter key.
</content>
</invoke>
+199 -8
View File
@@ -1,16 +1,207 @@
FROM golang:1.26-alpine AS build
RUN apk add --no-cache ca-certificates tzdata
RUN addgroup -g 65532 -S nonroot && adduser -u 65532 -S nonroot -G nonroot
WORKDIR /src
COPY . .
RUN CGO_ENABLED=0 go build -ldflags="-s -w" -o /cloud ./cmd/cloud
# hanzoai/cloud — the ONE unified Hanzo Cloud binary (HIP-0106).
#
# This image is a SINGLE artifact that serves BOTH the /v1 API AND the console
# UI from one process: the console is compiled into the Go binary via
# //go:embed (see webui.go). The final `/cloud` binary already carries the UI —
# no separate console Service, no second origin; the embedded console calls /v1
# on its own host.
#
# ── prebuilt decomplection artifacts (cloud compiles ONLY Go) ────────────────
# The console SPA, the agent-skills catalog, and the native flags staticlib are
# each built by THEIR OWN CI as a versioned immutable image and PULLED here,
# instead of rebuilding node + python + rust from scratch every cloud release.
# The heavy one (console: a cold `npm install` + full Next.js static export,
# force-cache-busted every build) used to dominate the ~20-min build; it is now
# a registry pull.
# console-embed (hanzoai/console Dockerfile.embed) → /dist → webui/dist (go:embed)
# agent-skills (hanzoai/openapi Dockerfile.skills) → /catalog → clients/agentskills/catalog (go:embed)
# cloud-flags (native/flags Dockerfile) → /libhanzo_flags.a → CGO link (clients/featureflags)
# Pinned to ghcr.io so BOTH buildx lanes (release.yml + platform arcbuild) pull
# it directly; the SAME tags are mirrored to registry.hanzo.ai (S3-backed) for
# GET-flow consumers (docker/kaniko/crane). Override any pin with
# --build-arg <NAME>_IMAGE=… .
#
# IMMUTABLE per-commit tags, never `:latest`. These defaults are LOAD-BEARING:
# the builder that actually runs our releases is the native one (POST /v1/runner
# → launchDirectBuild → BuildKit), and it passes no --build-arg, so whatever is
# written here is what gets baked. `release.yml`, which the previous comment said
# would resolve a fresh digest, is a stub and resolves nothing.
#
# With `:latest` the embedded console was therefore decided by WHEN the build ran,
# not by what we shipped — and it bit: cloud v1.801.215 was built ~12 minutes
# before console CI finished publishing the console-embed carrying v8.5.26, so a
# release whose whole purpose was that console change silently baked the previous
# one and shipped green. Same image, two contents, no diff to show for it.
#
# BUMP: when a console/skills/flags change must reach production, move its pin
# here in the same commit that claims it. That is what makes a cloud release
# reproducible and makes "what console is in v1.801.N" answerable from git.
ARG CONSOLE_IMAGE=ghcr.io/hanzoai/console-embed:sha-9f7042c-amd64
ARG SKILLS_IMAGE=ghcr.io/hanzoai/agent-skills:sha-b931a11-amd64
ARG FLAGS_IMAGE=ghcr.io/hanzoai/cloud-flags:sha-e1ca02a-amd64
FROM scratch
# ── toolchain base images: the golang + alpine FROMs below pull from our own
# GHCR mirror (ghcr.io/hanzoai/mirror/*), pinned by digest. WHY: public.ecr.aws
# rate-limits anonymous pulls (HTTP 429) on shared CI runners and a 429 on ANY
# base pull aborts the release. The mirror packages are 1:1 amd64 copies of the
# upstream public images, digest-pinned for immutability; release.yml logs the
# build into ghcr.io (GH_PAT) before building so they resolve. REFRESH on a
# toolchain bump: crane/regctl copy the new upstream into
# ghcr.io/hanzoai/mirror/<name>:<tag> and repoint the digest below. Canonical
# long-term home is registry.hanzo.ai/hanzoai/mirror/* — repoint once the runners
# carry its IAM pull credentials (follow-up).
# ── console SPA static export (prebuilt → /dist) ─────────────────────────────
FROM ${CONSOLE_IMAGE} AS console
# ── agent-skills catalog (prebuilt → /catalog) ──────────────────────────────
FROM ${SKILLS_IMAGE} AS skills
# ── native flags evaluator staticlib (prebuilt → /libhanzo_flags.a) ──────────
FROM ${FLAGS_IMAGE} AS flagslib
FROM ghcr.io/hanzoai/mirror/golang:1.26-alpine3.22@sha256:47d47cb5cc3c7dac409dcb6c3a98a6263571218046cd02d709527feef804a77c AS build
# CIPHER-FORMAT FREEZE (cek depends on this). The data-plane stores are
# SQLCipher pages in a fixed on-disk format (cipher_compatibility 4). An at-open
# compat pin is infeasible (mattn keys via URI before any pragma), so the format
# is frozen by pinning sqlcipher-dev to an EXACT version. A repo bump then fails
# the build LOUDLY (never a silent prod brick); on such a failure, bump the pin
# AND confirm cek's frozen-fixture test still opens (format unchanged)
# before shipping. A MAJOR bump (4.x → 5.x) changes the default format and would
# orphan existing encrypted stores — migrate/rewrap them first.
RUN apk add --no-cache ca-certificates tzdata git gcc musl-dev sqlcipher-dev=4.6.1-r0 pkgconfig binutils
RUN addgroup -g 65532 -S nonroot && adduser -u 65532 -S nonroot -G nonroot
# mattn/go-sqlite3's `libsqlite3` tag hard-codes `-lsqlite3`, but alpine's
# sqlcipher-dev ships ONLY libsqlcipher (no libsqlite3.so). Symlink so the link
# resolves -lsqlite3 to libsqlcipher — REAL encryption. Do NOT `apk add sqlite-dev`
# (a plaintext libsqlite3 would silently disable the codec; the gate below catches it).
RUN set -eux; \
SC="$(find /usr/lib /lib -name 'libsqlcipher.so*' 2>/dev/null | sort | head -1)"; \
test -n "$SC"; \
ln -sf "$SC" /usr/lib/libsqlite3.so; \
ln -sf "$SC" /usr/lib/libsqlite3.so.0
WORKDIR /src
# zap-proto/* (all 55 repos) and luxfi/* (all 37 deps here) are PUBLIC and resolve
# via the IMMUTABLE public proxy + sumdb — go.sum pins those canonical hashes, so a
# force-re-pointed tag can never break the build. GOSUMDB stays ON (a money image
# must not blanket-disable the checksum database); github.com/hanzoai/* is the
# exempt namespace — ai, account, commerce, orm, xorm, beego, csqlite and ~30 more
# are PRIVATE repos, so they resolve direct+authenticated (git over gh_token) and
# skip a sumdb that cannot see them. GOPRIVATE named zap-proto until now, which is
# public and was never the reason anything was direct; the private namespace it
# stood for went unnamed and worked only on the GOPROXY `direct` fallback.
# -mod=readonly means the committed go.sum is the SOLE source of truth: any drift
# (a needed hash not present) FAILS the build instead of being silently
# re-recorded. CGO_CFLAGS/LDFLAGS enable the SQLCipher codec + URI keying.
ENV CGO_CFLAGS="-DSQLITE_HAS_CODEC -DSQLITE_USE_URI=1 -I/usr/include/sqlcipher" \
CGO_LDFLAGS="-lsqlcipher" \
GOPRIVATE=github.com/hanzoai/* \
GOPROXY=https://proxy.golang.org,direct \
GOFLAGS=-mod=readonly
COPY go.mod go.sum ./
# The cache mounts carry an EXPLICIT id so they can be busted. Without one,
# BuildKit keys the cache by target path alone, and a poisoned entry is immortal:
# a module resolved while its tag did not yet exist is remembered as "unknown
# revision" forever, so `go mod download` keeps failing on a tag that now exists
# and resolves fine from a clean cache. That is exactly what wedged the release
# on otel-collector v0.144.10. BUMP THE SUFFIX (-v4 -> -v5) to force a cold
# module cache the next time a phantom pin poisons it.
RUN --mount=type=secret,id=GIT_AUTH_TOKEN \
--mount=type=cache,id=cloud-gomod-v4,target=/go/pkg/mod,sharing=locked \
if [ -s /run/secrets/GIT_AUTH_TOKEN ]; then \
git config --global url."https://x-access-token:$(cat /run/secrets/GIT_AUTH_TOKEN)@github.com/".insteadOf "https://github.com/"; \
fi && \
go mod download
COPY . .
# Drop the console static bundle into the embed path BEFORE `go build`, so
# //go:embed all:webui/dist bakes it into the binary (same-origin console).
COPY --from=console /dist/ /src/webui/dist/
# Overlay the FULL agent-skills catalog before `go build` so //go:embed all:catalog
# bakes the complete set (all services × brands), not the committed `ai` fallback.
COPY --from=skills /catalog/ /src/clients/agentskills/catalog/
# The native flags staticlib at the exact ${SRCDIR}-relative path the cgo
# directive in clients/featureflags/engine.go links.
COPY --from=flagslib /libhanzo_flags.a /src/native/flags/target/release/libhanzo_flags.a
# RED gate — modernc double-registration guard: 0 modernc under CGO=1, else the
# "sqlite" driver is registered twice (mattn + modernc) → panic at init.
RUN --mount=type=cache,id=cloud-gomod-v4,target=/go/pkg/mod,sharing=locked \
--mount=type=cache,id=cloud-gobuild-v4,target=/root/.cache/go-build,sharing=locked \
MODERNC="$(CGO_ENABLED=1 go list -tags "libsqlite3 sqlite_fts5" -deps ./cmd/cloud 2>/dev/null | grep -c 'modernc.org/sqlite' || true)"; \
[ "$MODERNC" = "0" ] || { echo "SQLITE-GATE FAIL: cmd/cloud links modernc.org/sqlite ($MODERNC pkgs) under CGO=1 — double-registers \"sqlite\" with hanzoai/sqlite(mattn) and panics at init."; exit 1; }
# RED gate — ENCRYPTION PROOF + the cek.go GOLDEN-VECTOR KAT, under the SAME CGO +
# libsqlcipher build this image ships. TestEncryptionProof asserts real
# ciphertext-at-rest (SQLITE_REQUIRE_CODEC=1 makes a plaintext link FAIL → NO
# image). TestUnwrapGoldenFixture asserts a FROZEN pre-luxfi-swap 61-byte DEK
# sidecar still decrypts under the shipped luxfi/crypto-AEAD code — existing
# encrypted stores stay readable, or NO image.
RUN --mount=type=cache,id=cloud-gomod-v4,target=/go/pkg/mod,sharing=locked \
--mount=type=cache,id=cloud-gobuild-v4,target=/root/.cache/go-build,sharing=locked \
SQLITE_REQUIRE_CODEC=1 CGO_ENABLED=1 go test -count=1 -tags "libsqlite3 sqlite_fts5" \
-run 'TestEncryptionProof|TestUnwrapGoldenFixture|TestWrapUnwrapRoundTripPinsLayout' \
github.com/hanzoai/sqlite
# RED gate — cek FROZEN-FORMAT guard, run INSIDE the image under the pinned Alpine
# libsqlcipher: opens the committed encrypted fixture and reads its canary row. A
# sqlcipher-dev pin/base bump that changes the on-disk format fails the IMAGE build
# HERE (not only Go CI) → a silent prod brick of existing stores becomes a red build.
RUN --mount=type=cache,id=cloud-gomod-v4,target=/go/pkg/mod,sharing=locked \
--mount=type=cache,id=cloud-gobuild-v4,target=/root/.cache/go-build,sharing=locked \
SQLITE_REQUIRE_CODEC=1 CGO_ENABLED=1 go test -count=1 -run TestFrozenFixtureOpens \
-tags "libsqlite3 sqlite_fts5" ./cek
RUN --mount=type=cache,id=cloud-gomod-v4,target=/go/pkg/mod,sharing=locked \
--mount=type=cache,id=cloud-gobuild-v4,target=/root/.cache/go-build,sharing=locked \
CGO_ENABLED=1 go build -tags "libsqlite3 sqlite_fts5" -ldflags="-s -w" -o /cloud ./cmd/cloud
# The functional smoke prober (cmd/smoke) — a stdlib-only, static binary shipped
# alongside /cloud so the release gate can `docker exec` it against the freshly-built
# image (and any deployment can be smoked via `docker run --entrypoint /smoke ...`).
RUN --mount=type=cache,id=cloud-gomod-v4,target=/go/pkg/mod,sharing=locked \
--mount=type=cache,id=cloud-gobuild-v4,target=/root/.cache/go-build,sharing=locked \
CGO_ENABLED=0 go build -ldflags="-s -w" -o /smoke ./cmd/smoke
# Prove the SHIPPED binary binds sqlite3_* to libsqlcipher, not a plaintext libsqlite3.
RUN readelf -d /cloud | grep -qE 'NEEDED.*(sqlcipher|sqlite3)' || { echo "FATAL: /cloud links no sqlite/sqlcipher .so"; exit 1; }; \
! ldd /cloud 2>/dev/null | grep -E 'libsqlite3' | grep -vq 'libsqlcipher' || { echo "FATAL: /cloud resolves a NON-sqlcipher libsqlite3 (plaintext risk)"; exit 1; }
# ── final image (alpine, NOT scratch — CGO needs libc + libsqlcipher) ─────────
FROM ghcr.io/hanzoai/mirror/alpine:3.22@sha256:7c8cb692ae09657cbc4a3f3cbd0e8d5a2690ba38386aaaf252dbb060bf5eb2e6
ARG REVISION=unknown
LABEL org.opencontainers.image.revision="${REVISION}" \
org.opencontainers.image.source="https://github.com/hanzoai/cloud"
# Runtime needs libsqlcipher (the codec the binary links). It must NOT also carry
# a plaintext libsqlite3 — the binary's -lsqlite3 DT_NEEDED would then bind to
# plaintext sqlite and silently no-op PRAGMA key. sqlcipher-libs ships
# libsqlcipher.so.0; alias libsqlite3.so.0 to it so sqlite3_* binds there.
#
# `git` backs the git object plane (clients/git): the heavy paths — clone/fetch
# serve, push receive, mirror-in — shell out to the streaming git CLI
# (upload-pack / receive-pack --stateless-rpc / fetch) so multi-GB packs stream
# to and from disk with bounded memory instead of buffering whole packs in RAM.
# The `git` apk package carries upload-pack/receive-pack/http-backend/git-remote-https.
# libgcc: the hanzo-flags Rust staticlib (clients/featureflags FFI) references the
# _Unwind_* unwinder symbols; musl needs libgcc_s at load time or the binary fails
# relocation ("Error relocating /cloud: _Unwind_GetIP: symbol not found").
# tini: /cloud runs as PID 1, and PID 1 inherits every orphaned descendant in the
# container. git is not a single process — fetch/clone fan out to git-upload-pack,
# git-index-pack, git-rev-list and git-pack-objects. When cloud Kill()s a wedged
# direct child (gitPackStream.Close does exactly that, correctly), those
# grandchildren orphan and reparent to PID 1. A Go program never reaps adopted
# orphans, so each one becomes a permanent zombie holding a PID slot.
# Measured 2026-07-26 on worker-xl-37bw71: 18,553 zombie `git` out of 18,741
# processes, all parented to /cloud, which drove the node to PID pressure and
# got cloud ITSELF evicted. A zombie costs no CPU and no memory, so nothing but
# an eviction ever surfaces it. tini reaps them.
RUN apk add --no-cache ca-certificates tzdata sqlcipher-libs git libgcc tini \
&& SC="$(find /usr/lib /lib -name 'libsqlcipher.so*' 2>/dev/null | sort | head -1)" \
&& test -n "$SC" \
&& ln -sf "$SC" /usr/lib/libsqlite3.so.0 \
&& test -x /sbin/tini
COPY --from=build /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/ca-certificates.crt
COPY --from=build /usr/share/zoneinfo /usr/share/zoneinfo
COPY --from=build /etc/passwd /etc/passwd
COPY --from=build /etc/group /etc/group
COPY --from=build /cloud /cloud
COPY --from=build /smoke /smoke
EXPOSE 8080 9090 9653
USER 65532:65532
ENTRYPOINT ["/cloud"]
# tini as PID 1 forwards signals to /cloud unchanged (so SIGTERM still drains
# normally) and reaps the orphans described above. `--` keeps cloud's own args
# untouched; the CR passes none today, but that stays true if it ever does.
ENTRYPOINT ["/sbin/tini", "--", "/cloud"]
+192
View File
@@ -0,0 +1,192 @@
# IAM cutover — Casdoor pod → embedded IAM in cloud (supervised)
Flip `hanzo.id`'s identity plane from the standalone Casdoor pod to the clean-room
IAM rewrite embedded in this binary (`clients/iam`, `github.com/hanzoai/iam`
**v1.33.6**). This is the last step of HIP-0106 (one binary embeds IAM + KMS + o11y).
**This is a single supervised session. Do not run it piecemeal or in the
background.** Every step below is: **action → verify → rollback**. Money/auth is on
the line — a bad flip 401s every login and every metered request.
The blocking code work is **done and shipped**:
- IAM v1.33.6 serves the legacy path aliases the deployed fleet hard-codes
(`/v1/iam/oauth/access_token`, `/v1/iam/oauth/refresh_token`, `/v1/iam/userinfo`)
next to the canonical paths — so no hard-coded caller 404s at the flip.
- `cloud` pins `github.com/hanzoai/iam v1.33.8` (go.mod) and compiles it in.
> **`iam` is NOT staged.** `stagedSubsystems` in `config.go` holds only `ingress`, so
> the empty-`CLOUD_ENABLE` "mount everything" default — **the live posture on
> `universe/infra/k8s/operator/crs/cloud.yaml`** — mounts the embedded IAM. Step 1 is
> therefore a **precondition of the next deploy**, not of a later flip: a cloud that
> boots before the store is migrated opens an EMPTY `iam2.db` and seeds only from
> `init_data.json`. `iam_edge.go` forwards `/v1/iam/*` to the standalone pod ONLY
> under a non-empty `--enable` that omits `iam`, which is the one way to hold cloud
> on the old plane while Step 1 runs.
## Preconditions (verify before touching anything)
1. Live image is at or above the tag that carries embedded IAM v1.33.6
(`universe/infra/k8s/operator/crs/cloud.yaml` `spec.image.tag`). The subsystem is
compiled in but inert until enabled — safe to deploy ahead of the flip.
2. `spec.replicas: 1` and `strategy: Recreate` (already required — the embedded
store is single-writer/single-open). **`config.go` refuses to boot iam-enabled
above 1 replica.** Never scale up with iam on.
3. `CLOUD_DATA_DIR=/var/lib/cloud` on the RWO `cloud-api-data` PVC. The embedded IAM
store is **`/var/lib/cloud/iam/iam2.db`** (`clients/iam/iam.go` `paths()`) — the v2
store. `iam.db` is a different database; opening it serves the wrong identities
without failing.
4. You have the live Casdoor store to migrate FROM and its KMS master key:
- encrypted sharded root: `<dir>/iam.db` + `<dir>/orgs/*/iam.db` (+ `.dek` sidecars)
- `IAM_KMS_MASTER_KEY` = the 64-hex master key (from KMS — never an arg, never logged)
5. `migrate-v1` is built from the **iam** repo (`github.com/hanzoai/iam`,
`cmd/migrate-v1`, same v1.33.6 tag) with a C `sqlcipher` binary on PATH (for
`--wal-inclusive`).
## Step 1 — Migrate the live store into the embedded datadir (BEFORE any seed)
The embedded IAM seeds new-only from `init_data.json`. Migrating real rows must
happen **before** the subsystem ever seeds, or the seed masks/collides with them.
The source is opened **read-only** — the live Casdoor pod is untouched.
**1a. Dry-run = the drift/parity gate.** `--dry-run` runs the full extraction and
prints the per-entity report WITHOUT writing. Require every entity's count to match
the live source and **drift = 0** before proceeding.
```
migrate-v1 \
--src-datadir /path/to/live/casdoor/store \
--src-master-key-env IAM_KMS_MASTER_KEY \
--wal-inclusive \
--dest /var/lib/cloud/iam/iam2.db \
--dry-run
```
- `--wal-inclusive` checkpoints each shard's uncheckpointed `-wal` via the C
sqlcipher binary → COMPLETE extraction. Without it, uncheckpointed WAL rows are a
hard error (or, with `--ignore-wal`, silently dropped — do NOT use for a real cutover).
- `--dest` accepts either form and both land on the same file here (`storePath` in
`iam/cmd/migrate-v1/main.go`): a `.db` path is taken verbatim, anything else is
treated as a data-dir and gets `/iam2.db` appended. So `…/iam/iam2.db` and `…/iam`
are equivalent. What matters is that the written file is exactly
`/var/lib/cloud/iam/iam2.db` — the path `clients/iam` opens.
**Verify:** dry-run report shows expected counts for users, orgs, applications,
providers, certs; zero drift; zero errors.
**Rollback:** none needed — nothing written.
**1b. Real migration.** Same command **without** `--dry-run`, writing into the
(empty) embedded datadir on the cloud PVC. Do this while iam is still staged OFF.
**Verify:** re-run `--dry-run` against `--src /var/lib/cloud/iam/iam2.db` (or open it
read-only) and confirm counts equal the source.
**Rollback:** `rm -f /var/lib/cloud/iam/iam2.db*` (only the freshly-written store) and
re-run. Nothing else consumes it until cloud next boots iam-enabled.
## Step 2 — Boot cloud with the embedded IAM subsystem
`iam` is **not** staged, so the live CR's empty `CLOUD_ENABLE` already enables it —
there is no env var to add. Deploying the image IS this step. Nothing here is
additive or reversible by a flag: plan Step 1 to complete before the next roll.
Apply the CR; the operator rolls the Recreate Deployment (single pod, brief blip —
expected). On boot, `clients/iam` opens `/var/lib/cloud/iam/iam2.db` (the migrated
store), seeds new-only from `init_data.json` (idempotent — real rows already present,
so seed only adds anything genuinely missing), and mounts the full `/v1/iam/*` surface
IN-PROCESS. `iam_edge.go` stops mounting (`serve.go`: `if !cfg.Enabled("iam") …`), so
there is **no double-mount** and no forward to the Casdoor pod.
**Verify (still on the internal Service, before repointing the edge):**
```
kubectl -n hanzo exec deploy/cloud -- \
curl -s localhost:8000/v1/iam/.well-known/openid-configuration | jq .issuer
# → "https://hanzo.id"
kubectl -n hanzo logs deploy/cloud | grep 'iam embedded in-process'
```
A boot failure serves fail-closed 503 on `/v1/iam/*` (cloud + every other subsystem
stay up) — it does NOT crash the binary.
**Rollback:** set `CLOUD_ENABLE` to an explicit list that OMITS `iam` and re-apply the
CR. Deleting an env var does not roll this back — an empty `CLOUD_ENABLE` is
iam-ENABLED. An explicit list is an allowlist, so it must name every other subsystem
this deployment serves; take it from the CR's own subsystem set, not from memory.
With `iam` out of that list the edge re-mounts and forwards to Casdoor again.
hanzo.id is unaffected (still pointed at Casdoor until Step 3).
## Step 3 — Repoint the hanzo.id identity backend at the edge
`universe/infra/k8s/ingress/routes.yaml`: router `hanzo-id-iam-api` (priority 100)
matches `Host(hanzo.id) && (PathPrefix(/v1/iam) || PathPrefix(/oauth) ||
PathPrefix(/.well-known))``service: iam-hanzo-ai`. Repoint that **service** from
the Casdoor pod to embedded cloud:
```yaml
iam-hanzo-ai:
loadBalancer:
passHostHeader: true
servers:
- url: http://cloud.hanzo.svc.cluster.local:8000 # was: http://iam.hanzo.svc.cluster.local:80
```
Leave the `hanzo-id` service (`id.hanzo.svc:80`, the @hanzo/id login SPA) as-is — only
the API backend moves. The ingress file-provider applies the ConfigMap edit **HOT**
(fsnotify) — **do NOT `rollout restart deploy/ingress`** (that triggers the per-node
ACME storm / TLS outage documented in `universe/CLAUDE.md`).
**Verify:** run the Step-4 parity checks against the public host `https://hanzo.id`.
**Rollback:** revert the one `url:` back to `http://iam.hanzo.svc.cluster.local:80`;
hot-reapplies in seconds. Instant, complete rollback to Casdoor.
## Step 4 — Playwright / curl parity (drive it, don't just curl a status)
Against `https://hanzo.id` (through the repointed edge). Use Playwright for the browser
login (real interaction, not an HTTP status peek):
1. **Discovery + JWKS**: `/.well-known/openid-configuration`,
`/v1/iam/.well-known/openid-configuration`, `/v1/iam/.well-known/jwks` — issuer
`https://hanzo.id`, keys present.
2. **Browser login → code → token** (Playwright): `/login/oauth/authorize` → sign in
→ callback with `code` → token exchange → a verifiable JWT; the app authenticates.
3. **client_credentials** (KMS bridge / gateway guards shape) at BOTH
`/v1/iam/oauth/token` and the alias `/v1/iam/oauth/access_token` → 200 + token.
4. **refresh** at the alias `/v1/iam/oauth/refresh_token` (the `hanzo` CLI shape) → 200
+ rotated token.
5. **userinfo** at BOTH `/v1/iam/oauth/userinfo` and the alias `/v1/iam/userinfo`
(commerce shape) → same principal.
6. **Real callers**: force one live KMS-bridge / gateway-guard token fetch and one
`hanzo login` + `hanzo` CLI refresh against hanzo.id → all 200.
**Accepted delta (not a regression):** BARE `/oauth/token|access_token|userinfo`
(no `/v1/iam` prefix) on hanzo.id 404 post-cutover — the rewrite serves the
`/v1/iam/…`-prefixed canonical + alias paths only, discovery advertises those, and no
live caller uses the bare form (grep-verified: every fleet caller uses `/v1/iam/oauth/*`
or an app-local `/oauth/*` proxy that rewrites to `/v1/iam/*`). Bare `/oauth/authorize`
still 302s to the login SPA via the priority-150 router (unchanged). Optionally tighten
the `hanzo-id-iam-api` rule to drop the bare `/oauth` prefix in the same edit.
**If any parity check fails: roll back Step 3 immediately** (one `url:` revert) and
diagnose with iam still embedded-but-unrouted.
## Step 5 — Retire the standalone Casdoor `iam` (final, only after parity holds)
With hanzo.id served by embedded IAM and parity green, remove the standalone Casdoor
workload. It is operator-managed via its App/CR
(`universe/infra/k8s/operator/crs/iam.yaml`, legacy
`hanzo-operator/crs/iam.yaml` + `iam-v1.yaml`). **First scale to 0** (reversible),
soak, then delete the CR + drop its basename from the Hanzo CD
`universe-crs` `include` glob (so ArgoCD stops governing it).
**Verify:** hanzo.id fully green with the Casdoor pod at 0 replicas for a full soak
(logins, token refresh, metered `/v1/*` traffic). Then delete.
**Rollback (pre-delete):** scale the Casdoor Deployment back to 1 and revert Step 3's
edge `url:` — hanzo.id is back on Casdoor in seconds. **After** the CR is deleted this
is no longer a one-step rollback (re-apply the CR from git), so hold the scale-to-0
soak until you are certain.
## Guardrails (do NOT, until this supervised session)
- Do not roll a cloud image onto the live CR before Step 1 completes — the empty
`CLOUD_ENABLE` mounts embedded IAM on boot, so the deploy itself performs Step 2.
- Do not repoint `iam-hanzo-ai` before Step-2 in-process verification passes.
- Do not delete or scale down the Casdoor `iam` workload before Step-4 parity holds.
- Do not run `migrate-v1` against prod without the read-only source + a green `--dry-run`.
- Do not `rollout restart deploy/ingress` (ACME storm). The routes edit is hot-reloaded.
- Keep `replicas: 1` / `strategy: Recreate` — embedded IAM is single-writer.
+203
View File
@@ -0,0 +1,203 @@
Copyright (c) 2026 Hanzo AI Inc.
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright (c) 2026 Hanzo AI Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
+416
View File
@@ -0,0 +1,416 @@
# LLM.md — hanzoai/cloud
**Canonical repo.** `hanzoai/cloud` (HIP-0106) is the Open AI Cloud as ONE Go
binary + `hanzo` CLI: every Hanzo subsystem (iam, base, kms, ai, gateway,
commerce, o11y, tasks, …) mounted into a single multi-org process. The same
artifact serves `api.hanzo.ai`, `api.lux.cloud`, `api.zoo.cloud`,
`api.osage.cloud`, and every white-label reseller — brand, enabled subsystems,
and org scope are deployment configuration. This is the impl home for the cloud
control plane; the OpenAPI it emits at `GET /v1/openapi.json` is the single
source for the generated per-language SDKs.
## Role in the SDK model
- Full Cloud SDK is GENERATED from THIS binary's OpenAPI; SDK impl lives in
`hanzo-<lang>/sdk`, docs/wrappers in `hanzoai/<lang>-sdk`, meta in `hanzoai/sdk`.
- AI/agents flagship lib is separate: Python `hanzo` (`hanzoai/python-sdk`),
Node `@hanzo/ai` (`hanzo-js/ai`). Completeness: Python > Rust > C++ > Go.
- DRY: one impl, one place; discovery repos link OUT, never duplicate impl.
- Full spec: `~/work/hanzo/SDK-ARCHITECTURE.md`.
## Brand rules (hard)
- Hanzo is a full AI cloud, NOT a proxy — never "LLM gateway", never position vs
LiteLLM. Zen models are our OWN family; never name upstream models.
- `/v1/` only, never `/api/`. Voice: "Hanzo — the Open AI Cloud."
## Install / run
- `docker run -p 8080:8080 ghcr.io/hanzoai/cloud:vX.Y.Z` (pin a released tag) ·
`go install github.com/hanzoai/cloud/cmd/hanzo@latest` · `brew install hanzoai/tap/hanzo`
- Build in MODULE mode only: `make build` / `GOWORK=off go build ./...` — never
workspace mode (see "Build & module graph" below).
## Key entry points
- `cmd/cloud` — server binary · `cmd/hanzo` (`cli/`) — control CLI · `webui.go` — embedded console
- `apps/apps.go:Wire()` — composition root (the one ordered subsystem slice)
- `deps.go` / `cloud.Deps` — process-wide handles · `clients/<name>/` — every subsystem
- `openapi/` — live spec derived from the router (no checked-in spec file)
---
## Open Cloud planes
Spec home: HIP-0129 `hip-0129-open-cloud-planes` (hips repo). This section is a
map, not the spec. One noun, one owner, one route family. No plane reads another
plane's store; imports flow custody-ward only (channels -> integrations, never
reverse).
| Route | Noun | Owner | Tier |
| --- | --- | --- | --- |
| `/v1/connectors` | Custody: per-user BYO external accounts | `clients/integrations` (extends; user scope new) | In flight (branch `feat/connectors`) |
| `/v1/channels` | Transport: portable message envelope, DM pairing, send + inbox | `clients/channels` (new) | Planned (branch `feat/channels` reserved; no transport code yet) |
| `/v1/sync` | Data: bidirectional sync engine | `clients/sync` | Shipped |
| `/v1/automations` | Workflows: flows/runs, goja piece runtime | `clients/automations` | Shipped |
| `/v1/compute/bots` | Hosting: `@hanzo/bot` Node containers | `clients/bots` | Shipped |
| `/v1/tasks` | Durable engine | `clients/tasks` | Shipped |
| `/v1/gpus` + fleet | BYO GPU presence | `clients/fleet` + `clients/visor` | Shipped |
| `/v1/cloud` | Cloud accounts: link DO/AWS/GCP/Azure, discover native k8s clusters, fold into the fleet | `clients/venue` (new) | In flight (branch `feat/cloud-account-connectors`; blue-held for red) |
| `/v1/blueprint` | Cost: OSS-template SBOM (compose→images) + compute-cost estimate | `clients/blueprint` (new) | Shipped |
| IAM | Identity: users, orgs, roles | IAM | Shipped |
| KMS | Secret custody: sealed secrets | `clients/kms` | Shipped |
Custody invariants: secrets sealed in KMS at
`/orgs/{org}/users/{user}/connectors/{provider}/{label}`, never in SQLite rows;
verify before store. Refresh is single-flight with rotation resealing; the CLI
does local browser PKCE and posts the bundle to
`POST /v1/connectors/:provider/credential`; cloud owns device-code flows.
Transport invariants: typed actions (`command|url|select|approval`), no raw
string sniffing; pairing codes 8 chars, 1h TTL, max 3 pending per account,
owner bootstrap on first approval.
Container boundary is permanent for native-module, host-filesystem, loop-state,
and vendor-Node work (agent loop, exec/PTY, harnesses, browser, voice, codecs,
Node-bound channels, plugin SDK/loader). The Node plugin SDK is never ported to
Go; cloud extensibility is connectors/automations/tools.
Port roadmap (P1-P15) lives in HIP-0129; do not restate it here. Every claim
carries its tier: Shipped (on main, named package/route), In flight (named
pre-main branch), Planned (backlog id or named reservation).
## Build & module graph — standalone module, NOT a go.work member
`cloud` is a self-contained deploy unit: its own `go.mod`, `Dockerfile`, binary.
It is intentionally NOT listed in the parent `~/work/hanzo/go.work` workspace —
that workspace deliberately excludes the heavy modules, and merging cloud's
k8s/otel dependency tree with `o11y`'s reintroduces `koanf`/`ugorji`
monolith-vs-split import ambiguities (the parent workspace is itself red on the
koanf split; that is not cloud's bug to fix).
The catch: `go` auto-discovers that parent `go.work` whenever you run a bare
`go build ./...` / `go test ./...` from inside this tree, which puts the build in
workspace mode and SILENTLY DROPS cloud's own `go.mod` directives. Those
directives are load-bearing and each fixes exactly one graph hazard:
- `replace github.com/vulcand/oxy/v2 => github.com/traefik/oxy/v2 <pseudo>` — the
bare require is a placeholder (`v2.0.0-00010101000000-000000000000`); without
the replace it resolves to an invalid version.
- `exclude github.com/ugorji/go <old-monolith>` — drops the pre-split monolith so
`github.com/ugorji/go/codec` (pulled by gin) is unambiguous.
- the `k8s.io/*` staging replace block pins every staging module to the `v0.35.3`
line. `k8s.io/kubernetes` is a GRAPH-ONLY transitive require of
`hanzoai/deploy/gitops-engine` (clients/deploy uses its `pkg/utils/kube`); NO
cloud package imports `k8s.io/kubernetes`, so its staging tree never compiles —
do not "drop k8s.io/kubernetes", the pins keep the graph consistent and it is
never built. koanf resolves to the split modules; the `koanf v1.5.0` monolith
require is a harmless graph leaf, never imported.
So: build cloud in module mode, never workspace mode. `make build`/`test`/`vet`/
`tidy` force `GOWORK=off` (matches CI and the Dockerfile, which check out cloud
alone with no parent go.work). For a bare `go` command from this tree, prefix
`GOWORK=off`. `GOWORK=off go build ./...` and `go vet ./...` are green; `go mod
tidy` is stable. Do NOT commit a `go.work` here — it would flip the Dockerfile
(`COPY go.mod go.sum``go mod download``COPY . .`) into workspace mode after
its `-mod=readonly` download step.
Test modes: `make test` is pure-Go (`CGO_ENABLED=0`). Encrypted-at-rest OrgDB
tests (`cek`, `CLOUD_KMS_MASTER_KEY_REF` set) REQUIRE `CGO_ENABLED=1` +
libsqlcipher (`cek/cek.go` refuses to encrypt in pure-Go); those run only in the
Dockerfile's dedicated `-tags libsqlite3` CGO stage, and fail under `make test`
by design (clients/git, kms, flags, x402, cmd/kmsreseal, finance). Bundle-embed
tests (clients/tasks/ui) need `make deploy-ui` first (real bundle is gitignored).
Store-heavy subsystem tests are fsync-bound, not CPU-bound. A mount opens its own
SQLite stores, so a test that mounts several subsystems commits many times, and
`t.TempDir()` under `/tmp` puts every commit behind the ext4 journal — on a box with
a concurrent build the same mount that costs milliseconds idle costs ~90s, at ~0%
CPU, blocked in `jbd2_log_wait_commit`. Point `TMPDIR` at tmpfs to measure the real
cost: `TMPDIR=/dev/shm/t GOWORK=off go test -p 1 ./clients/guide` runs the eight-seam
cross-subsystem harness (`clients/guide/drivehome_e2e_test.go`) in under a second.
Prefer one package per `go test` invocation regardless: `./...` links every main
package at once (`cmd/cloud` alone links >6GB).
## Framework doctrine
One way to do everything. Composable, orthogonal, DRY. A new subsystem is a
package under `clients/<name>` that obeys these seams — nothing more.
- **Subsystem shape.** A subsystem exposes `func Mount(app *zip.App, deps cloud.Deps) error`
and is listed in `apps.Wire()` as a `cloud.MountSpec{Name, Mount: cloud.Typed(Mount)}`
(plus `Shutdown`/`OwnsHealth` where it owns them). `Mount` wires that subsystem's
`/v1/<name>/*` routes onto the shared `*zip.App`; `cloud.Deps` carries the
process-wide handles (Logger, DataDir, the subsystem `Client` seams). No
subsystem reaches into another's internals. There is no init()-registry and no
`cloud.Register` — subsystems do NOT self-register.
- **Client seams.** Cross-subsystem calls go through a narrow in-process interface
published in `types` and aliased at the provider, e.g. `commerce.Client =
types.CommerceClient` (`GetOrgConfig` + `CheckEntitlement`). Consumers depend on
the interface, never the implementation; the seam rides zap-proto/zip. Keep each
interface minimal — add a method only when a consumer needs it.
- **Composition root.** `apps/apps.go:Wire()` returns `[]cloud.MountSpec` — every
linked subsystem, in mount order, as ONE explicit slice read top-to-bottom.
Slice position IS the order: there is no `Order` field and `MountAll`
(build.go) does NOT sort; it iterates as-given and mounts each ENABLED spec
(`cfg.Enabled`). To add a subsystem you add one line to `Wire()`.
`apps/wire_test.go` freezes the sequence, so a reorder/drop/add fails there.
- **Route precedence.** The router is zap-proto/fiber (zip v1.8.3). Most-specific
route wins regardless of mount order, so subsystems may mount in any order and
still compose deterministically. But precedence is NOT a conflict guard: two
registrations of a byte-identical pattern do NOT panic — fiber MERGES them into
ONE route with both handlers chained, resolving by first-registration. That is
invisible to a `GetRoutes()` entry count (see the bots note below), and it is
NOT distinguishable from a legitimate middleware chain: `app.Post(path, mw1,
mw2, mw3, handler)` is one registration with four handlers (apps/commerce.go:151),
and the whole `/v1/store/*` surface is that shape. A high handler count is
therefore evidence of nothing on its own; only a subsystem that never chains
middleware (bots/visor/runtime) can read `len(Handlers) > 1` as a collision.
- **Per-org data.** The ONE way any subsystem opens a per-org SQLite file is
`cloud.OrgDB(dataDir, org, project, sub)` — or the cached `cloud.OrgStore[T]`
(`NewOrgStore` + `For(org, project)`). Path convention:
`{DataDir}/orgs/{org}/{sub}.db`, or `{DataDir}/orgs/{org}/projects/{project}/{sub}.db`
when project-scoped. Isolation is PHYSICAL: a distinct `(org[, project])` is a
distinct file. `org`/`project` MUST be the VALIDATED principal values
(`principal.Org(c)`, `principal.Project(c)`) — never a raw body/header — and are
folded through `SanitizeOrg`, the ONE injective org slugger. hanzoai/sqlite is
the SOLE driver (blank-imported once, in orgdb.go); subsystems never import a
SQLite driver themselves. The caller owns its schema/migration and Close.
## The route table has three projections, and the router is the source
`serve.go` composes ONE route table and projects it three ways, all after
`MountAll` so each sees a complete table: `/zap` REPLAYS the /v1 handlers
(zapface), the console RENDERS them, and `GET /v1/openapi.json` DESCRIBES them
(`openapi.Mount`). None holds a second copy of anything; none can drift.
- **The spec IS the router.** `openapi.Live(app)` reads
`app.Fiber().GetRoutes(true)` — fiber's own filter drops `Use()` middleware —
and every other function in `openapi/` is a pure function of that `[]Route`.
There is NO checked-in spec file to hand-maintain and no second registry. The
drift guard is `cmd/cloud/openapi_test.go`: a BIJECTION over the fully-mounted
`apps.Wire()` (983 operations / 692 paths / 109 products) — every live route
appears as an operation, every operation is backed by a live route. It is the
only test whose failure means the document lies.
- **Reading the LIVE router is the only total source.** `POST /v1/kms/auth/login`
is registered as `Group("/v1/kms/auth").Post("/login")` — no grep can find that
path; only the assembled router knows it. And the route set is a function of
deployment config (`cfg.Enabled`, plus internal gates like kms's `if kc != nil`),
so **the spec VARIES PER DEPLOYMENT** — correctly: a deployment that does not
mount admin does not advertise it. That is why the document is generated
per-process at request time, not built once in CI.
- **The product axis is mechanical.** The first path segment after `/v1/` IS the
product (`openapi.Product`), tagged onto each operation so a CLI can build
`hanzo <product> <resource> <verb>` with no judgment. It is deliberately NOT the
subsystem name: `clients/billing` also serves `/v1/finance/*`.
- **What the router CANNOT tell you — do not try to fix this in the generator.**
Method, path, path params, and product are derivable; request/response schemas,
query/header params, status codes, and auth are NOT. The router holds a
`func(*zip.Ctx) error`; the request type is a LOCAL inside the handler
(`var req secretPutRequest; json.Unmarshal(ctx.Body(), &req)`), and Go cannot
reflect from a func value into its body. `cloud.Handle[S]` does not help — `S`
is the SERVICE (service.go:90), not the payload; `cloud.Typed` is an
`any→*zip.App` mount adapter. The ONE path to schemas is zip's typed ops
(`zip.Get[In,Out]`), which carry the In/Out types and also yield an MCP tool
from the same registry (zip/openapi.go, zip/mcp.go — today `len(a.ops) == 0`,
so zip's own generator emits nothing here). `GetRoutes()` is a superset of
`app.ops`, so migrating a handler to a typed op adds schema without changing
this pipeline.
- **Catch-alls are opaque, by construction.** `app.Post("/v1/billing/*")` proxies
to another service, so `POST /v1/billing/deposit` is NOT a route in this process
and cannot appear. Measured on the live table: 3 products are wholly opaque
(`bot`, `licensing`, `sentry` — the catch-all IS the product) and 12 more mix
concrete ops with a catch-all hiding an unknown remainder.
## Cross-subsystem seams that are values, not places
- **The per-principal MCP plane is callable in-process.** `clients/automations`
decomplects tool dispatch from its front doors: `dispatchTool` is the ONE core
(resolve `<connector>_<action>` → run with a Token bound to the VALIDATED org),
and TWO doors share it — the HTTP JSON-RPC handler (`POST /v1/automations/mcp`)
and the exported `automations.InvokeTool(ctx, org, tool, args)`. A sibling
subsystem that must ACT AS a caller (the Business AI guide's "do it for me")
calls `InvokeTool` with `principal.Org(c)` — same 403 gate, per-org concurrency
bound, one metered unit, one audit record as the HTTP door — so it can never
exceed the caller's authority. Use this seam; never re-implement tool dispatch.
- **"Bot" is three values; each has one home and one namespace.** Do not merge
them and do not let them share a route prefix — they did once, and the router
resolves byte-identical patterns by first-registration with no panic (it MERGES
the handlers, so counting `GetRoutes()` entries cannot see it), and visor's
machine list silently answered the console's run list.
(1) A bot RUN — a task the runtime executes on a surface — is `clients/bots` at
`/v1/bots`. (2) A bot MACHINE — visor-provisioned compute of kind=bot plus its
agent binding — is `clients/visor` at `/v1/compute/bots`; what it rents you is
compute, so it nests in visor's domain. (3) The runtime SERVICE — the TS bot
(channels/skills), never reimplemented in Go — is reached through
`clients/runtime`, which is a TRANSPORT, not a domain: base address, identity,
framing, cleartext policy, and the `/v1/bot/*` ops face. It is named for what it
does, not for the host it dials, and it must never import `bots`/`coding` — each
of those owns its own wire stub (`bots/wire.go`, `coding/task.go`) and speaks
through the seam. That isolation is what makes the HIP-0106/HIP-0120 ZAP swap a
seam swap instead of a rewrite.
- **Cloud owns policy; the runtime owns the run. Do not copy state you do not
own.** `clients/bots` holds NO store. The sandbox lives in the bot runtime,
keyed in the runtime's own tenant store, which is the only thing that knows
whether a run is alive — so list and stop PROXY it, gated by cloud's
principal/org. A cloud-side registry was tried and was wrong: it minted an id
the runtime had never heard of, so it listed runs that did not exist and
"stopped" runs that were never started. Isolation holds because the org is the
validated one cloud sends, never a client's, and the runtime keys every run
under `tenants/{org}/`.
- **Absence is only meaningful from a callee that could have said otherwise.**
`runtime.ErrNotFound` (the operation ANSWERED "no such target") is separate from
`runtime.ErrNotServed` (the operation does not exist). Conflating them makes a
stop that cannot fail: a runtime without the route reports absent for EVERY run,
so "already gone" becomes permanently true. A bare 404 is 502, never success.
- **The Business AI Guide (`clients/guide`, `/v1/guide/*`)** is the on-site launch
checklist: a pure engine (`curriculum.go` — parse/validate/next-step/dependency
gating over plain data) + per-org progress (`cloud.OrgStore[*Store]`) + an
injectable auto-detect registry (`detect.go``acted` reads the agent action
ledger, `analytics` probes the shared warehouse) + the agent (`agent.go` — drafts
with `deps.AI`, executes the step's bound tool via `automations.InvokeTool`). The
curriculum is a machine-readable contract (embedded `default.yaml`; org-custom via
PUT replaces it) so `hanzoai/marketing` can author the full `checklist.yaml`
against the same `Step`/`Curriculum` shape.
- **The EXPERIMENT is a composition, not a fourth engine (`clients/experiments`,
`/v1/experiments`).** A/B testing is ONE value whatever the variant KIND (feature
flag, ad creative, email subject, model id): the primitive owns only the
experiment registry (definition + decision); it COMPOSES three planes it never
duplicates. ASSIGNMENT = `flags.Assign(org,project,key,subject,props)`
subject→variant is a deterministic `engineEvaluate` (sha1 rollout hash), no second
bucketing, no assignment store; create writes a multivariate flag def
(`flags.PutDef`) and decide rewrites its weights to 100% for the winner
(`flags.GetDef`+`PutDef`). MEASUREMENT = `analytics.Outcomes(...)` — one
org-scoped `hanzo.events` query (the `eventsWhere` isolation invariant), no second
event store; the analyze fold joins each subject's analytics outcome to its flags
variant by `distinct_id`. EVIDENCE = `research.Record`/`research.List` — per-variant
samples land as immutable `kind:"ab"` rows; significance (two-proportion z-test,
`math.Erfc`, no dep) is a PURE function over them. `clients/campaign` runs a
creative A/B by composing `experiments.Assign`/`experiments.Analyze` — it never
reinvents assignment or evidence. Add a new variant KIND by putting a payload on
the variant; the primitive does not care what it is.
- **The OSS-template compute cost is DERIVED from the compose, not a fourth ledger
(`clients/blueprint`, `/v1/blueprint`).** A blueprint's `docker-compose.yml` is
parsed to its SBOM (the bill of container images) and its services' CPU/memory
footprint priced through ONE documented rate card (microdollars per vCPU-/GB-hour,
DigitalOcean-droplet-derived + platform margin; tunable via
`CLOUD_BLUEPRINT_UCPU_HR`/`_UGB_HR`). Sizing is the declared
`deploy.resources.reservations`/`limits` (or legacy `cpus`/`mem_*`) else a default
footprint per inferred class (db/cache/web/worker/other). `blueprint.EstimateTemplate(id)`
returns `{sbom, vcpuHr, gbHr, microUsdPerHour, estCentsPerMonth}`: `estCentsPerMonth`
is the "~$X/mo to run" the console shows; `microUsdPerHour` is the exact rate the
deploy path meters the deploying org on via the SAME commerce spine `resource_billing`
uses. The author royalty (`clients/authors`, `defaultShareBps=2000`) already accrues
20% of a deploying org's metered spend — this plane only DEFINES the compute component
of that spend from a real rate card; it never touches the ledger or the accrual sweep.
Distinct from `clients/sbom` (CycloneDX packages INSIDE one image, keyed by digest);
this is the bill of IMAGES a stack runs, keyed by template.
## Identity vocabulary is IAM-native
Identity is expressed ONLY in IAM-native nouns: **org, user, project, billing
account**. The word **"tenant" is banned** in cloud identifiers, strings,
comments, and filenames. Resolve org/project scope through `clients/principal`
(`principal.Org(c)`, `principal.Project(c)`) and user identity through `c.User()`
— all gateway-minted, JWT-validated values (X-Org-Id / X-Project-Id / X-User-Id,
HIP-0026); never read a raw request header for scope.
- **The one gated exception.** `clients/platform` derives customer-app Kubernetes
namespaces, registry image refs, and quota/limit objects from a live `tenant-<org>`
string prefix. Renaming that prefix orphans deployed namespaces + built images,
so the literal `"tenant-"` string (and its directly-adjacent comment) is retained
behind a `// NAMING(gated)` note in `clients/platform/k8s.go`. The surrounding
identity vocabulary is org-native regardless; only the on-cluster string waits on
an infrastructure migration.
## Hanzo Company (`clients/company`, `/v1/company`)
The Stripe-Atlas-class incorporation + fundraising product: ONE formation state
machine per org. `machine.go` is the PURE core — a `transitions` table with a guard
per edge, `Advance(f, to)` the only mutator — so transitions, the payment gate, and
the skip path are unit-testable with no I/O. The HTTP surface is decomplected: ACTION
endpoints populate data (structure/founders/kyc/payment/documents/esign/genesis/
import), and ONE `POST /v1/company/advance {to}` runs the guarded transition.
Every external dependency is a narrow provider interface (`providers.go`) so the
machine composes them identically in prod and tests: billing → the shared
`ResourceMeter` ($999 one-time fee); documents → `dataroom.Ingest` (new in-proc
facade); cap table → `captable.*` (new in-proc facades: SetIncorporation /
AddStakeholders / EnsureShareClass / IssueShares / RecordRound); equity genesis →
a KMS-signed Hanzo-L1 anchor mirroring `clients/treasury` (honest pending when
unwired); KYC + state filing → honest stubs (no fabricated verification/filing).
Import path (already-incorporated orgs): Google Drive → data room, a Google Sheet →
captable, via the `google` OAuth provider now completed in `clients/integrations`
(token custodied in KMS; the automations `google` connector shares the same token).
Runbook: `docs/company-dogfood.md`.
## Deploy plane (`clients/deploy`, `/v1/deploy`)
Native ArgoCD-grade GitOps console over the operator-managed fleet, parallel to
`/v1/git`: each `hanzo.ai/v1` App CR IS the Application, and the plane OBSERVES the
operator's reconcile — `GET /v1/deploy/applications` (fleet list), `/{name}/tree`
(ownerRef resource tree + per-node health/sync), `/{name}/resource/{ref}` (live
manifest + desired-vs-live diff), `/{name}/logs`; `POST /{name}/rollback` pins the CR
image to a prior semver and `/{name}/sync` requests a reconcile. SUPERADMIN-only on
`c.IsAdmin()`, fail-closed; Secret nodes are never surfaced. `engine.go` embeds the argo
`gitops-engine` (`hanzoai/deploy/gitops-engine` v0.7.2, no replace) in-process for the
reconcile half behind `DEPLOY_ENGINE_ENABLED` (default off), with a prune-safety fuse.
## The `hanzo` CLI targets THIS binary — one contract, one IAM login
The `hanzo` CLI (`cli/`) is the same unified binary; its control-plane verbs speak the
routes THIS process serves, authorized off a plain `hanzo login` (the IAM access token is
the final bearer fallback — no `--platform-token`). The ONE contract, no TS-Dokploy drift:
- `hanzo apps list|get``GET /v1/paas/apps[/{app}]` (`clients/paas` fleet drift board)
- `hanzo deploy <app>``POST /v1/paas/apps/{app}/deploy` — a zero-downtime ROLLING
RESTART (stamps the Deployment pod-template `hanzo.ai/restartedAt` annotation; never
changes the declared TAG — that stays a git commit CD reconciles). `--env` picks the ns.
- `hanzo clusters list|get``GET /v1/clusters` (`clients/visor`, tenant-scoped)
- `hanzo build``POST /v1/runner` (native buildkit fabric)
`/v1/paas/*` auth mirrors `/v1/runner` (`clients/platform/runner.go`): the `guard` admits a
validated principal who is SuperAdmin OR OrgAdmin, then each handler CONFINES a non-super
caller to the platform namespaces its own validated org owns (`scopedNamespaces`, keyed on
`principal.Org` — a tenant admin can never observe/restart another org's, or a platform,
app; `?org=` cannot widen it). The rolling restart needs `patch` on `apps/deployments`
(ClusterRole/cloud, universe `infra/k8s/cloud/rbac.yaml`). There is NO `/v1/apps`,
`/v1/org/{org}/cluster`, or `/v1/platform/projects` CLI path — the first two never existed
here (TS-Dokploy contract, 404), and `/v1/platform/*` needs a co-resident IAM store this
deployment does not fold in (IAM runs as a separate svc) so it 500s; the live apps backend
is `/v1/paas`, whose board reads k8s directly with no IAM-store dependency.
## GTM: `/v1/campaign` orchestration → channels → connectors → analytics
The go-to-market stack decomplects a campaign from its execution. A **Campaign is a
VALUE** (`clients/campaign`: `{name, audience, content[], schedule, budget, channels[],
status}`) that SPANS channels; a **Channel is an EXECUTOR** (`channel.go`, the
`Channel` interface) it fans out to. The three channels are orthogonal and each
CONSUMES the connector plane via `integrations.TokenFor` — the campaign object never
touches a credential:
- **paid → `/v1/ads`** — `ads.LaunchPaid/PaidSpend/PausePaid` (`clients/ads/provider.go`)
resolve the org's ad token (`meta_ads`/`google_ads`/… via `TokenFor(org, <id>,
"access_token")`) and run the campaign on the provider. Meta is executed for real;
fail-closed when the org has not connected (424). This is the ONLY place `/v1/ads`
touches the connector plane.
- **organic → `/v1/publish`** (rename of `clients/social`) and **email → `/v1/marketing`**
are DESIGNED follow-ons: register their executors the same way in `apps/wire_seams.go`
(`campaign.RegisterChannel(campaign.NewChannel(kind, launch, spend, pause))`). Until
wired, a fan-out records that channel "unavailable" (honest), never fabricated.
Channels are injected at the composition root (`apps/wire_seams.go`), the SAME
injected-function decoupling the coding dispatcher uses — `campaign` never imports
`ads`, `ads` never imports `campaign`. Fan-out (`launch.go` `fanOut`) is best-effort
per channel; the org (the ONLY tenant key) is passed verbatim to every executor, so a
campaign can only ever resolve its OWN org's token.
**Metrics = the ONE analytics plane, not a second store.** `GET /v1/campaign/:id/metrics`
reads the funnel from `analytics.CampaignMetrics(org, campaignID, variant, start, end)`
(`clients/analytics/campaign.go`) — an org+`utm_campaign`(+`utm_content`)-scoped query
over `hanzo.events`, org and campaign bound POSITIONALLY (same tenancy invariant as
every analytics query) — joined with each channel connector's reported spend
(`Channel.Spend`). Derived KPIs: CTR/CVR/CAC/ROAS. Honest-empty when the warehouse is
absent.
**Creative A/B composes the experiment primitive** (`experiment.go`), it does not
reinvent it: a creative A/B is an experiment whose variant = a creative (tagged
`utm_content`) and whose metric = the analytics read. The `AssignFunc`/`EvidenceFunc`
seams are wired at the root to the flags-assignment + evidence primitive; nil-safe
until it lands (single-creative honest default).
+116
View File
@@ -0,0 +1,116 @@
# hanzoai/cloud — developer ergonomics for the unified Hanzo Cloud binary (HIP-0106).
# Targets are intentionally minimal; deploy artifacts (compose, helm) live in deploy/ and helm/.
GO ?= go
BIN ?= cloud
PKG ?= ./cmd/cloud
# cloud is a STANDALONE Go module — a self-contained deploy unit (its own go.mod,
# Dockerfile, binary). It is intentionally NOT a member of the parent
# ~/work/hanzo/go.work workspace (that workspace deliberately excludes the heavy
# modules; adding cloud would merge its k8s/otel graph with o11y's and reintroduce
# koanf/ugorji import ambiguities). But `go` auto-discovers that parent go.work
# whenever a dev builds from inside this tree, which shadows cloud's own
# replace/exclude directives (oxy pin, ugorji monolith exclude, k8s staging pins)
# and breaks `go build ./...`. Force module mode so make targets build EXACTLY
# what CI/Docker build (fresh checkout, no parent go.work). Overridable via
# `make GOWORK=... <target>` for the rare cross-module case.
export GOWORK := off
DOCKER_IMAGE ?= ghcr.io/hanzoai/cloud
DOCKER_TAG ?= dev
LDFLAGS ?= -s -w
# Path to a hanzoai/console checkout used to build the embedded console bundle.
CONSOLE_DIR ?= ../console
# Path to a hanzoai/openapi checkout — the SOT the agent-skills catalog is generated from.
OPENAPI_DIR ?= ../openapi
# The shipped binary is pure Go (Dockerfile: CGO_ENABLED=0 → scratch). Default all
# build/test targets to that mode so `make build`/`make test` exercise exactly
# what prod runs — and, critically, register the ONE "sqlite" driver exactly once:
# cloud's stores use github.com/hanzoai/sqlite (its !cgo backend IS modernc), and
# the embedded deps (ai/base/commerce/o11y/orm/tasks) that import modernc directly
# then resolve to the SAME package → a single registration. A plain CGO_ENABLED=1
# build instead links the fork's mattn backend ALONGSIDE those modernc importers
# and panics at init ("sql: Register called twice for driver sqlite"); `make
# test-cgo` proves the cgo path via the fork's `sqlite_purego` opt-out tag, which
# forces the fork to modernc too so the whole binary registers "sqlite" once.
CGO_ENABLED ?= 0
.PHONY: help native webui deploy-ui agentskills build build-standalone run smoke test test-cgo vet tidy docker docker-push clean
help: ## Show this help.
@awk 'BEGIN{FS=":.*##";printf "\nUsage: make <target>\n\nTargets:\n"} /^[a-zA-Z_-]+:.*##/{printf " \033[36m%-16s\033[0m %s\n", $$1, $$2}' $(MAKEFILE_LIST)
webui: ## Build the real console static bundle into webui/dist (go:embed source). CONSOLE_DIR=<path to console>.
@command -v npm >/dev/null 2>&1 || { echo "npm is required to build the console bundle"; exit 1; }
@test -f "$(CONSOLE_DIR)/package.json" || { echo "console checkout not found at $(CONSOLE_DIR) — set CONSOLE_DIR=<path>"; exit 1; }
@test -d "$(CONSOLE_DIR)/node_modules" || (cd "$(CONSOLE_DIR)" && npm install --no-audit --no-fund)
cd "$(CONSOLE_DIR)" && NEXT_TELEMETRY_DISABLED=1 NODE_OPTIONS=--max-old-space-size=8192 npm run build:embed
# Overlay the fresh static export onto webui/dist, keeping only the tracked
# fallbacks (.gitignore + assets/.gitkeep); the real bundle is build-time-only.
find webui/dist -mindepth 1 -maxdepth 1 ! -name .gitignore ! -name assets -exec rm -rf {} +
cp -r "$(CONSOLE_DIR)/out/." webui/dist/
@echo ">> embedded real console bundle into webui/dist (index.html $$(wc -c < webui/dist/index.html) bytes)"
deploy-ui: ## Build the monochrome ArgoCD dashboard bundle into clients/deploy/webui/dist (go:embed source). DEPLOY_DIR=<path to hanzoai/deploy>.
@command -v yarn >/dev/null 2>&1 || { echo "yarn is required to build the deploy dashboard bundle"; exit 1; }
@test -f "$(DEPLOY_DIR)/ui/package.json" || { echo "deploy checkout not found at $(DEPLOY_DIR) — set DEPLOY_DIR=<path to hanzoai/deploy on rebrand/hanzo-monochrome>"; exit 1; }
@test -d "$(DEPLOY_DIR)/ui/node_modules" || (cd "$(DEPLOY_DIR)/ui" && yarn install --frozen-lockfile)
cd "$(DEPLOY_DIR)/ui" && NODE_OPTIONS=--max-old-space-size=8192 yarn build
# Overlay the fresh bundle, keeping only the tracked fallback (.gitignore +
# index.html shell); the real 43MB bundle is build-time-only (gitignored).
find clients/deploy/webui/dist -mindepth 1 -maxdepth 1 ! -name .gitignore -exec rm -rf {} +
cp -r "$(DEPLOY_DIR)/ui/dist/app/." clients/deploy/webui/dist/
@echo ">> embedded monochrome ArgoCD bundle into clients/deploy/webui/dist (index.html $$(wc -c < clients/deploy/webui/dist/index.html) bytes)"
agentskills: ## Regenerate the FULL agent-skills catalog into clients/agentskills/catalog (go:embed source) from the openapi SOT. OPENAPI_DIR=<path to openapi>.
@test -f "$(OPENAPI_DIR)/skills.py" || { echo "openapi checkout not found at $(OPENAPI_DIR) — set OPENAPI_DIR=<path> or clone hanzoai/openapi"; exit 1; }
# skills.py rewrites the whole catalog dir; the .gitignore keeps only the tiny
# `ai` fallback tracked, so the full set is embedded at build but never committed.
python3 "$(OPENAPI_DIR)/skills.py" --no-services --out clients/agentskills/catalog
@echo ">> embedded FULL agent-skills catalog ($$(jq -r .skill_count clients/agentskills/catalog/hanzo/index.json) skills/brand)"
build: ## Build the unified cloud binary into ./bin/cloud (embeds whatever webui/dist holds — run `webui` first for the real console).
@mkdir -p bin
CGO_ENABLED=$(CGO_ENABLED) $(GO) build -ldflags="$(LDFLAGS)" -o bin/$(BIN) $(PKG)
build-standalone: webui build ## Build the REAL 1-binary console: console build:embed → webui/dist → go build.
# NOTE: cloud builds ONLY the `cloud` binary — the stateless unified API. The Go
# `hanzo` CLI (cmd/hanzo + cli/) is RETIRED: the shipped `hanzo` is the Rust CLI
# (~/work/hanzo/cli, `curl hanzo.sh`), which talks to this API over HTTP via its
# OpenAPI-generated command surface. The `code` wrapper (incl. the zen-tier 1M
# mechanism) now lives in the Rust CLI. cmd/hanzo + cli/ remain only as the
# reference for the still-to-port client-side tools (GPU fleet worker `link`,
# `runner`, `engine`, `security`) and are no longer built here.
run: build ## Run with iam,base,kms,gateway,o11y enabled (matches README quickstart).
./bin/$(BIN) --enable=iam,base,kms,gateway,o11y --brand=hanzo --domain=api.hanzo.ai
smoke: ## Build and run cmd/cloud-smoke (mount-time integration check).
$(GO) run ./cmd/cloud-smoke
test: ## Run unit + integration tests (pure-Go, exactly as prod ships).
CGO_ENABLED=$(CGO_ENABLED) $(GO) test ./...
test-cgo: ## Prove the cgo build works too — forces the fork's pure-Go backend via -tags sqlite_purego so the embedded modernc importers don't double-register "sqlite".
CGO_ENABLED=1 $(GO) test -tags sqlite_purego ./...
vet: ## go vet across the module.
CGO_ENABLED=$(CGO_ENABLED) $(GO) vet ./...
tidy: ## go mod tidy + verify go.sum.
$(GO) mod tidy
$(GO) mod verify
docker: ## Build the Docker image (uses repo Dockerfile, scratch final stage).
docker build -t $(DOCKER_IMAGE):$(DOCKER_TAG) .
docker-push: docker ## Push the Docker image to ghcr.io. Requires docker login.
docker push $(DOCKER_IMAGE):$(DOCKER_TAG)
clean: ## Remove built artifacts.
rm -rf bin
native: ## Build the native flags evaluator staticlib (required for CGO=1 builds/tests).
cargo build --release --manifest-path native/flags/Cargo.toml
+32
View File
@@ -0,0 +1,32 @@
Hanzo Cloud
Copyright (c) 2026 Hanzo Industries, Inc.
This product includes software from the following upstream projects. Their names
appear here and NOWHERE ELSE in this codebase's user-visible surfaces — Hanzo
products are named for Hanzo (Hanzo Analytics, Hanzo Insights, Hanzo IAM, …).
Umami (https://github.com/umami-software/umami), licensed under MIT:
Copyright (c) 2022 Umami Software, Inc. <hello@umami.is>
Hanzo Analytics (analytics.hanzo.ai) is a fork. The cloud destination adapter
speaks its public collect contract.
PostHog (https://github.com/PostHog/posthog), licensed under MIT:
Copyright (c) 2020-present PostHog Inc.
Hanzo Insights (insights.hanzo.ai) is a fork. The cloud destination adapter
speaks its capture contract.
Casibase (https://github.com/casibase/casibase), licensed under Apache-2.0:
Copyright (c) The Casibase Authors
The Hanzo AI module (the /v1 AI, RAG, and search surfaces) derives from it.
Casdoor (https://github.com/casdoor/casdoor), licensed under Apache-2.0:
Copyright (c) The Casdoor Authors
Hanzo IAM (hanzo.id) derives from it.
+130 -43
View File
@@ -1,70 +1,75 @@
# cloud
<p align="center"><img src=".github/hero.svg" alt="Hanzo Cloud" width="880"></p>
Unified Go control plane and binary for the Hanzo platform (HIP-0106).
# Hanzo Cloud
**The Open AI Cloud as one Go binary.** Identity, secrets, data, AI, gateway, observability, and the console — every Hanzo-native subsystem mounted into a single multi-org process. Per [HIP-0106](https://github.com/hanzoai/HIPs/blob/main/HIPs/hip-0106-unified-hanzo-cloud-binary.md).
[![Status](https://img.shields.io/badge/status-beta-blue)]()
[![License](https://img.shields.io/badge/license-Apache--2.0-blue)]()
The same artifact serves `api.hanzo.ai`, `api.lux.cloud`, `api.zoo.cloud`, `api.osage.cloud`, and every white-label reseller. Brand, enabled subsystems, and org scope are deployment configuration — one binary, one origin, no sidecars.
## Quick start
```bash
docker run -p 8080:8080 ghcr.io/hanzoai/cloud:latest
# Run the unified binary (pin a released version)
docker run -p 8080:8080 ghcr.io/hanzoai/cloud:v1.801.206
# Or install the CLI + server
go install github.com/hanzoai/cloud/cmd/hanzo@latest
brew install hanzoai/tap/hanzo
```
Open <http://localhost:8080> for the embedded console; the API is served under `/v1` on the same origin.
## What this is
`hanzoai/cloud` is one Go binary that mounts every Hanzo subsystem (iam, kms, base, gateway, ai, commerce, vfs, mq, dns, amqp, mcp, o11y, ...) into a single multi-tenant process. Same artifact serves `api.hanzo.ai`, `api.osage.cloud`, `api.lux.cloud`, `api.zoo.cloud`, and every white-label reseller. Brand, enabled subsystems, and tenant scope are deployment configuration.
`hanzoai/cloud` is one Go binary that mounts every Hanzo subsystem (iam, kms, base, gateway, ai, commerce, vfs, mq, dns, amqp, mcp, o11y, tasks, …) into a single multi-org process. The same artifact serves `api.hanzo.ai`, `api.osage.cloud`, `api.lux.cloud`, `api.zoo.cloud`, and every white-label reseller. Brand, enabled subsystems, and org scope are deployment configuration.
## Specs
## `hanzo` — cloud control CLI
Implements:
- HIP-0014 Application Deployment
- HIP-0026 IAM
- HIP-0027 KMS
- HIP-0037 AI Cloud Platform
- HIP-0105 In-Process Extension Runtime
- HIP-0106 Unified Cloud Binary
- HIP-0302 Encrypted SQLite + ZapDB Durability
The same binary is also a gcloud/doctl-class CLI. The first token selects the mode:
## Architecture
- `hanzo <subsystem>`**server mode**: serve a subsystem (`hanzo iam`, `hanzo cloud`, …).
- `hanzo <verb>`**client mode**: control the live estate. A thin client over
Hanzo IAM (`hanzo.id`), the platform control plane (`platform.hanzo.ai/v1`),
and the cloud `/v1` API — it invents no parallel API.
```
api.{tenant}.{brand}
|
hanzoai/cloud (one Go binary)
|
+----------+----------+----------+----------+----------+
| iam | base | kms | ai | gateway | ...
| Mount() | Mount() | Mount() | Mount() | Mount() |
+----------+----------+----------+----------+----------+
per-tenant SQLite (HIP-0302) | Hanzo IAM JWKS (HIP-0026)
replicate -> S3 (HIP-0107) | ZAP inter-subsystem RPC
```bash
hanzo login # IAM password grant against hanzo.id → token in ~/.hanzo (0600)
hanzo whoami # identity from the stored token (--verify hits IAM userinfo)
hanzo apps list # platform apps board: declared/running/latest tag + drift + health
hanzo apps get <org>/<app>/<env> # one app row
hanzo deploy <container> --project <p> --env <e> # rolling, zero-downtime redeploy
hanzo clusters list|get|create|select|target # dedicated DOKS cluster lifecycle
hanzo build <repo> --sha <sha> --image <img> # platform-native (arcd/Kaniko) build, no GitHub builders
hanzo k8s target # the org's resolved deploy target (kubeconfig never returned)
hanzo config set <k> <v> # ~/.hanzo/config preferences
```
Every subsystem exposes `func Mount(app *zip.App, deps cloud.Deps) error`. White-label fork pattern: customers fork this repo to launch their own ecosystem.
Global flags: `--org`, `-o/--output table|json`, `--platform-url`, `--iam-issuer`,
`--platform-token`. Tokens resolve from flag → env → `~/.hanzo` (never hardcoded):
the IAM user token is the identity; the platform control plane is service-token
authed (it cannot validate user tokens), so `apps`/`deploy`/`clusters` use
`--platform-token` / `HANZO_PLATFORM_TOKEN` / `PLATFORM_SERVICE_TOKEN`, and
`build` uses `HANZO_BUILD_TOKEN` / `PLATFORM_BUILD_CALLBACK_TOKEN`.
---
# Hanzo Cloud
The unified Go binary that imports every Hanzo-native subsystem and dispatches
requests per deployment configuration. One artifact, many subsystems.
Per [HIP-0106](https://github.com/hanzoai/HIPs/blob/main/HIPs/hip-0106-unified-hanzo-cloud-binary.md).
Install: `go install github.com/hanzoai/cloud/cmd/hanzo@latest`, or `brew install hanzoai/tap/hanzo`.
## Subsystems mounted
- `iam` — identity & access
- `base` — per-tenant SQLite + extension runtimes (per HIP-0105)
- `kms`secrets
Each subsystem exposes `func Mount(app *zip.App, deps cloud.Deps) error` and wires its own `/v1/<name>/*` routes onto the shared app.
- `iam`identity & access (users, orgs, roles, OIDC/JWKS per HIP-0026)
- `base` — per-org SQLite + in-process extension runtimes (HIP-0105)
- `kms` — secret custody (sealed secrets, HIP-0027)
- `commerce` — checkout, billing, pricing, invoicing (light router; NOT in PCI-DSS scope)
- `ai`LLM control plane / RAG / model hub / MCP management (was hanzoai/cloud pre-rename)
- `ai`AI control plane: inference, RAG, model hub, agents, MCP management
- `gateway` — HTTP routing + policy
- `o11y` — metrics / traces / logs
- `vfs` — virtual filesystem / object-store abstraction
- `mq` — message queue
- `dns`, `amqp`, `mcp`, `auto`, `tasks`, ... (full list per HIP-0106)
- `dns`, `amqp`, `mcp`, `auto`, `tasks`, … — full list per HIP-0106
## Deployment modes
@@ -77,10 +82,27 @@ cloud --enable=iam,base,kms,commerce,ai,gateway,o11y --brand=lux --domain=lux
cloud --enable=iam,base,kms,commerce,ai,gateway,o11y --brand=zoo --domain=zoo.cloud
```
## Architecture
```
api.{org}.{brand}
|
hanzoai/cloud (one Go binary)
|
+----------+----------+----------+----------+----------+
| iam | base | kms | ai | gateway | ...
| Mount() | Mount() | Mount() | Mount() | Mount() |
+----------+----------+----------+----------+----------+
per-org SQLite (HIP-0302) | Hanzo IAM JWKS (HIP-0026)
replicate -> S3 (HIP-0107) | ZAP inter-subsystem RPC
```
Every subsystem mounts through the same `Mount(app, deps)` seam. Cross-subsystem calls ride a narrow in-process interface; no subsystem reaches into another's store.
## White-label fork pattern
Customers fork `hanzoai/cloud` to launch their own ecosystem in one binary. Brand
detection, enabled subsystems, ZAP endpoints (payments / vault backends) are all
detection, enabled subsystems, and ZAP endpoints (payments / vault backends) are all
deployment configuration.
## Web framework
@@ -88,7 +110,72 @@ deployment configuration.
[hanzoai/zip](https://github.com/hanzoai/zip) — Sinatra-style Go web framework
built on Fiber v3. The ONE Go web framework. No `.Fast` escape hatch.
## Console UI — embedded in the ONE binary
The same `hanzoai/cloud` binary serves the [console](https://github.com/hanzoai/console)
(`@hanzo/gui`) UI at the web root AND the `/v1` API from one process — one
artifact, one origin, no separate console Service. The UI is compiled in via
`//go:embed` (see `webui.go`).
Pipeline (in the `Dockerfile`, before `go build`):
```
console stage → build console static bundle → /out
COPY --from=console /out/ → src/webui/dist/ (overlays the fallback shell)
build stage → go build → //go:embed all:webui/dist bakes it into /cloud
```
Serving (`webui.go`, registered LAST in `Serve` so it never shadows the API):
- `GET /` and any client-side route (`/orgs`, `/models`, …) → the SPA shell
(`index.html`) with `Cache-Control: no-cache`; fingerprinted assets under
`assets/`/`_next/` are served `immutable` for a year, with brotli/gzip
precompressed negotiation when the build emits `.br`/`.gz` siblings.
- `GET /v1/*` (and `/zap`, `/healthz`, …) → the API. Real subsystem routes are
registered before the console catch-all, so they always win; an **unmatched**
path under an API prefix returns a real 404 (JSON namespace), never HTML.
- Same-origin: the embedded console calls `/v1` on its own host, so the session
cookie is first-party — no second origin, no CORS.
`webui/dist/index.html` is a committed **fallback shell** (a real same-origin
`/v1` bootstrap) so `go build` always compiles and the binary always serves a UI
even without the Node toolchain. The image build overwrites `webui/dist` with the
real console bundle. See `webui_test.go` for the boot-and-assert tests
(`/` → shell, deep link → shell 200, `/v1/*` → API, unmatched `/v1` → 404).
The `hanzoai/console` `build:embed` script (`scripts/build-embed.mjs`) stashes its
Next server route handlers (BFF proxies that collapse to the cloud `/v1/*` the SPA
calls same-origin), wraps the client catch-all pages for `output: 'export'`,
neutralizes the root layout's request-time `headers()` read, and emits a real
static export at `out/` (a ~360 KB `index.html` + `_next/` chunks). The image
build (and `make webui`) run it and overlay `webui/dist`, so `//go:embed` bakes
the FULL `@hanzo/gui` console into the ONE binary. The Dockerfile console stage
FAILS HARD if that bundle is missing or degenerate — the placeholder shell can
never silently ship to prod (escape hatch: `--build-arg ALLOW_PLACEHOLDER=1` for a
pure-Go dev image).
## Specs
Implements:
- HIP-0014 Application Deployment
- HIP-0026 IAM
- HIP-0027 KMS
- HIP-0037 AI Cloud Platform
- HIP-0105 In-Process Extension Runtime
- HIP-0106 Unified Cloud Binary
- HIP-0129 Open Cloud Planes
- HIP-0302 Encrypted SQLite + ZapDB Durability
## Status
Scaffold. The Mount(app, deps) integration for each subsystem lands per
HIP-0106's migration phases.
In production. The unified binary serves `api.hanzo.ai` and the white-label cloud
surfaces today, with per-org SQLite (HIP-0302) and the embedded console. Subsystems
continue to land per HIP-0106's migration phases; `apps/apps.go:Wire()` is the one
ordered list of everything mounted. For repo-level engineering doctrine (module
graph, route-table projections, cross-subsystem seams), see [`LLM.md`](./LLM.md).
## Hanzo — the Open AI Cloud
Open source · every language · on-chain settlement. [hanzo.ai](https://hanzo.ai) · [docs.hanzo.ai](https://docs.hanzo.ai)
**SDKs in every language** — [Python](https://github.com/hanzoai/python-sdk) (flagship) · [TypeScript](https://github.com/hanzo-js/sdk) · [Go](https://github.com/hanzo-go/sdk) · [Rust](https://github.com/hanzo-rs/sdk) · [C++](https://github.com/hanzo-cpp/sdk) · [Swift](https://github.com/hanzo-swift/sdk) · [Kotlin](https://github.com/hanzo-kt/sdk) · [umbrella](https://github.com/hanzoai/sdk)
+72
View File
@@ -0,0 +1,72 @@
// Copyright 2026 Hanzo AI Inc. All Rights Reserved.
package cloud
import (
"net/http"
"github.com/hanzoai/cloud/clients/principal"
"github.com/zap-proto/zip"
)
// AccountFromPrincipal decomplects the console's IDENTITY onto the ONE truth every
// /v1/admin/* call already authorizes on — the validated cloud principal — instead of
// the embedded casibase account model.
//
// THE COMPLECTION IT REMOVES. The operator SPA authenticates via /v1/signin (a cloud
// PKCE session → the X-User-* principal the middleware mints) but read its IDENTITY
// from the account read, which the embedded IAM (casibase) answers from ITS OWN session
// cookie. A PKCE session is not a casibase session, so that read returned
// owner:"hanzo" (anonymous) or "Unauthorized operation" — and the SPA's SuperAdmin
// gate (owner == "admin" && isAdmin), reading that, bounced the operator UI to login
// even though the SAME session got 200 from every /v1/admin/* route. Two session
// models for one surface; the identity source and the authorization source disagreed.
//
// THE DECOMPLECTION. Identity is now the principal: when a VALIDATED principal is
// present (X-User-Id is set ONLY by IdentityMiddleware from a real credential, never a
// raw client header — see middleware_identity.go), /v1/ai/account reflects it. owner
// is the HOME org (principal.Owner) so a SuperAdmin org-switched into a tenant stays a
// SuperAdmin; isAdmin is the validated bit. With NO principal it falls through
// (c.Next()) to the casibase account surface unchanged — the anonymous sign-in page
// and any legacy casibase-session caller are untouched. One truth, additive, fail-open
// to the old path. MUST be registered AFTER IdentityMiddleware (needs the minted
// headers) and BEFORE MountAll (so it precedes the casibase account handler).
// accountPath is the account read this middleware fronts. It is a named constant
// because the interception is a PATH MATCH: when the /v1 surface was namespaced
// (/v1/get-account → /v1/ai/account) a literal left un-updated here would not
// error — the middleware would simply stop firing, fall through to the casibase
// account surface, and hand the SPA the anonymous owner again. That is precisely
// the bug this file exists to fix, silently restored.
const accountPath = "/v1/ai/account"
func AccountFromPrincipal() zip.Handler {
return func(c *zip.Ctx) error {
if c.Method() != http.MethodGet || c.Path() != accountPath {
return c.Next()
}
user := c.User() // X-User-Id — minted only from a validated credential
if user == "" {
return c.Next() // no principal → the casibase account surface (unchanged)
}
owner := principal.Owner(c) // HOME org (a SuperAdmin stays one when org-switched)
if owner == "" {
owner = c.Org()
}
name := c.Header("X-User-Name")
if name == "" {
name = user
}
return c.JSON(http.StatusOK, map[string]any{
"status": "ok",
"msg": "",
"data": map[string]any{
"owner": owner,
"name": name,
"displayName": name,
"email": c.Header("X-User-Email"),
"isAdmin": c.IsAdmin(),
"type": "normal-user",
},
})
}
}
+544
View File
@@ -0,0 +1,544 @@
// Package apps is the composition root: the single, explicit list of which
// Hanzo cloud subsystems are linked into the binary AND the order they mount in.
//
// Wire() returns []cloud.MountSpec in mount order (slice position == order). There
// is no init()-registry and no order-int: adding, removing, or reordering a
// subsystem is a one-line edit to Wire(), read top-to-bottom. cmd/cloud and
// cmd/hanzo both call Wire() and thread the slice into cloud.Serve — the set is
// defined ONCE, here.
//
// (This package must NOT live in package cloud: the subsystems import cloud for
// Deps + Typed, so a root-package bundle would form an import cycle. As a sibling
// subpackage it composes them without one.)
//
// HIP-0106: the unified cloud binary is the APPLICATION layer plus the embedded KMS
// secrets plane and the embedded IAM identity plane ("one Go binary embeds IAM +
// KMS + o11y"). The edge/infra tier (mcp, gateway, ingress-edge) runs as its own
// deployments for blast-radius isolation; several application folds (iam, base,
// commerce, captable, dataroom, sign, ingress) are STAGED — linked here but mounted
// only when the operator names them in CLOUD_ENABLE.
//
// Ordering provenance: order-int ascending; ties in the exact order the
// pre-refactor init()-registry mounted them, captured empirically from origin/main
// @c504d2b (68 self-registering specs) and frozen by TestWireOrderMatchesFrozen
// (wire_test.go). ai (@150) and the hanzoai/o11y module wildcard (@70) are NOT in
// that dump: on their wave-2 tags (ai v1.805.2, o11y v1.5.12) they no longer
// self-register, so origin/main currently DROPS them (a latent regression this
// composition root fixes). They are wired back at their order-int slots — o11y-ext
// kept adjacent to the in-repo o11y read-plane (@69); ai as the last /v1/* catch-all
// before plugins (@900). Do not re-sort; edit positions deliberately.
//
//go:generate go run ../cmd/gen-app-cmds
package apps
import (
"context"
"fmt"
"github.com/hanzoai/cloud"
"github.com/zap-proto/zip"
// External subsystem modules. As of the atomic wave-2 bump they NO LONGER
// self-register (no cloud.Register in their init) — the composition root wires
// each one explicitly below, so removing an entry here is the ONLY way to drop it.
"github.com/hanzoai/ai"
"github.com/hanzoai/authz"
"github.com/hanzoai/licensing"
"github.com/hanzoai/metrics"
// In-repo subsystem packages (clients/*). Each exports a Mount (and, where it
// owns process-lifetime resources, a Shutdown); Wire references them directly.
"github.com/hanzoai/cloud/clients/account"
"github.com/hanzoai/cloud/clients/admin"
"github.com/hanzoai/cloud/clients/admission"
"github.com/hanzoai/cloud/clients/ads"
"github.com/hanzoai/cloud/clients/affiliates"
"github.com/hanzoai/cloud/clients/agent"
"github.com/hanzoai/cloud/clients/agents"
"github.com/hanzoai/cloud/clients/agentskills"
"github.com/hanzoai/cloud/clients/analytics"
"github.com/hanzoai/cloud/clients/ask"
"github.com/hanzoai/cloud/clients/auditlog"
"github.com/hanzoai/cloud/clients/authors"
"github.com/hanzoai/cloud/clients/automations"
"github.com/hanzoai/cloud/clients/base"
"github.com/hanzoai/cloud/clients/benchmark"
"github.com/hanzoai/cloud/clients/billing"
"github.com/hanzoai/cloud/clients/blueprint"
"github.com/hanzoai/cloud/clients/books"
"github.com/hanzoai/cloud/clients/bots"
"github.com/hanzoai/cloud/clients/campaign"
"github.com/hanzoai/cloud/clients/captable"
"github.com/hanzoai/cloud/clients/catalogsync"
"github.com/hanzoai/cloud/clients/channels"
"github.com/hanzoai/cloud/clients/cloudflare"
"github.com/hanzoai/cloud/clients/code"
"github.com/hanzoai/cloud/clients/company"
"github.com/hanzoai/cloud/clients/compliance"
"github.com/hanzoai/cloud/clients/content"
"github.com/hanzoai/cloud/clients/crm"
"github.com/hanzoai/cloud/clients/dataroom"
"github.com/hanzoai/cloud/clients/deploy"
"github.com/hanzoai/cloud/clients/destinations"
"github.com/hanzoai/cloud/clients/dns"
"github.com/hanzoai/cloud/clients/do"
"github.com/hanzoai/cloud/clients/domain"
"github.com/hanzoai/cloud/clients/entitlements"
"github.com/hanzoai/cloud/clients/eval"
"github.com/hanzoai/cloud/clients/exec"
"github.com/hanzoai/cloud/clients/experiments"
"github.com/hanzoai/cloud/clients/flags"
"github.com/hanzoai/cloud/clients/framework"
"github.com/hanzoai/cloud/clients/functions"
"github.com/hanzoai/cloud/clients/gateway"
"github.com/hanzoai/cloud/clients/git"
"github.com/hanzoai/cloud/clients/graph"
"github.com/hanzoai/cloud/clients/guide"
"github.com/hanzoai/cloud/clients/help"
"github.com/hanzoai/cloud/clients/iam"
"github.com/hanzoai/cloud/clients/ingress"
"github.com/hanzoai/cloud/clients/integrations"
"github.com/hanzoai/cloud/clients/kafka"
"github.com/hanzoai/cloud/clients/kms"
"github.com/hanzoai/cloud/clients/knowledge"
"github.com/hanzoai/cloud/clients/leaderboard"
"github.com/hanzoai/cloud/clients/legal"
"github.com/hanzoai/cloud/clients/link"
"github.com/hanzoai/cloud/clients/marketing"
"github.com/hanzoai/cloud/clients/marketplace"
"github.com/hanzoai/cloud/clients/ml"
"github.com/hanzoai/cloud/clients/notify"
"github.com/hanzoai/cloud/clients/o11y"
"github.com/hanzoai/cloud/clients/paas"
"github.com/hanzoai/cloud/clients/plan"
"github.com/hanzoai/cloud/clients/platform"
"github.com/hanzoai/cloud/clients/plugin"
"github.com/hanzoai/cloud/clients/prefs"
"github.com/hanzoai/cloud/clients/pricing"
"github.com/hanzoai/cloud/clients/product"
"github.com/hanzoai/cloud/clients/projects"
"github.com/hanzoai/cloud/clients/prompts"
"github.com/hanzoai/cloud/clients/provisioning"
"github.com/hanzoai/cloud/clients/pubsub"
"github.com/hanzoai/cloud/clients/referrals"
"github.com/hanzoai/cloud/clients/research"
"github.com/hanzoai/cloud/clients/rollingcap"
"github.com/hanzoai/cloud/clients/runtime"
"github.com/hanzoai/cloud/clients/sbom"
"github.com/hanzoai/cloud/clients/security"
"github.com/hanzoai/cloud/clients/settings"
"github.com/hanzoai/cloud/clients/share"
"github.com/hanzoai/cloud/clients/sign"
"github.com/hanzoai/cloud/clients/social"
"github.com/hanzoai/cloud/clients/storage"
"github.com/hanzoai/cloud/clients/sync"
"github.com/hanzoai/cloud/clients/tasks"
"github.com/hanzoai/cloud/clients/team"
"github.com/hanzoai/cloud/clients/templates"
"github.com/hanzoai/cloud/clients/tools"
"github.com/hanzoai/cloud/clients/tracker"
"github.com/hanzoai/cloud/clients/treasury"
"github.com/hanzoai/cloud/clients/usage"
"github.com/hanzoai/cloud/clients/validators"
"github.com/hanzoai/cloud/clients/venue"
"github.com/hanzoai/cloud/clients/visor"
"github.com/hanzoai/cloud/clients/wallets"
"github.com/hanzoai/cloud/clients/webhooks"
"github.com/hanzoai/cloud/clients/websearch"
"github.com/hanzoai/cloud/clients/world"
"github.com/hanzoai/cloud/clients/x402"
"github.com/hanzoai/cloud/clients/zt"
// Framework CONTENT modules — pure fixture lanes that carry no HTTP surface and
// are absent from Wire(). Each registers its DocType fixtures and, for erp, its
// ledger-posting lifecycle hooks into the clients/framework DocType engine from a
// package init() (framework.RegisterModule) — the idiomatic register-into-a-
// registry pattern (cf. database/sql drivers). The framework engine is mounted
// (always-on, /v1/framework/*) but its module registry is populated ONLY by these
// blank imports. Dropping one silently strips that lane's DocTypes and hooks — for
// erp, the immutable ledger postings — from the binary with NO mount change and NO
// failing mount test. #248 dropped them; TestFrameworkContentModulesLinked now
// guards against a recurrence. Keep. (help is a framework lane too but ALSO mounts
// a thin /v1/help public plane, so it is a real import + a Wire() spec below,
// alongside knowledge — the other lane with a companion subsystem.)
_ "github.com/hanzoai/cloud/clients/cms"
_ "github.com/hanzoai/cloud/clients/erp"
)
// init wires the cross-subsystem func seams — the composition root is the one place
// that may import two leaf subsystems at once, so a connection neither can express
// alone lives here. git's push→index reactor calls the code index without git
// importing code: the adapter converts git's IndexedFile to code's File and drops the
// result (the reactor only needs success/failure). Stored once at load; invoked on
// push, long after mount, so there is no ordering dependency. Same
// register-into-a-registry idiom the framework content modules use above.
func init() {
git.SetIndexer(func(ctx context.Context, org, billingOrg, project, repo string, files []git.IndexedFile) error {
in := make([]code.File, len(files))
for i, f := range files {
in[i] = code.File{Path: f.Path, Content: f.Content}
}
_, err := code.IndexFiles(ctx, org, billingOrg, project, repo, in)
return err
})
}
// Wire returns every linked subsystem as a cloud.MountSpec, in mount order. The
// slice position IS the order: cloud.MountAll iterates it as-given, registering each
// subsystem's teardown as a zip shutdown hook so teardown runs in reverse (LIFO).
// Enablement is a separate axis: cloud.Serve mounts only the specs cfg.Enabled(name)
// admits, so a STAGED subsystem is linked but inert until named.
func Wire() []cloud.MountSpec {
return []cloud.MountSpec{
// embedded NATS :4222 + JetStream.
{Name: "pubsub", Mount: pubsub.Mount, Shutdown: pubsub.Shutdown},
// embedded Kafka adaptor :9092.
{Name: "kafka", Mount: kafka.Mount, Shutdown: kafka.Shutdown},
// /.well-known/agent-skills/* — before IAM's /.well-known/* wildcard (50).
{Name: "agentskills", Mount: agentskills.Mount},
// Insights feature-flag evaluation seam (no routes; a hot value plane).
{Name: "flags", Mount: flags.Mount, Shutdown: flags.Shutdown, OwnsHealth: true},
// Embedded KMS secrets plane /v1/kms/*. OwnsHealth: serves its own fail-closed
// /v1/kms/health (the generic always-ok route must not shadow it). Fails closed
// until the operator injects CLOUD_KMS_MASTER_KEY_REF. (Its in-process client
// factory is registered separately via cloud.RegisterKMSClientFactory.)
{Name: "kms", Mount: kms.Mount, OwnsHealth: true},
// hanzoai/metrics — native o11y. It declares its OWN narrow metrics.Deps (no
// hanzoai/cloud import), so Typed cannot adapt it; mountMetrics builds that Deps
// from cloud.Deps and calls metrics.Mount explicitly.
{Name: "metrics", Mount: mountMetrics},
// Embedded runtime edge (/v1/ingress/*). STAGED — edge listeners stay off unless
// the operator names "ingress" in CLOUD_ENABLE.
{Name: "ingress", Mount: ingress.Mount, Shutdown: ingress.Shutdown},
// SPECIFIC self-service routes (/v1/iam/{keys,onboard}, /v1/csrf, /v1/embed-status,
// /v1/commerce/topup/wallet). MUST mount before the IAM /v1/iam/* wildcard (50) so
// they win Fiber's first-match scan (framework-guaranteed since zip v1.3.0).
{Name: "account", Mount: account.MountAccount},
// Embedded IAM identity plane (/v1/iam/*, /login/oauth/*) — the identity authority,
// mounts before its dependents. The ONE implementation: the clean-room iam-v2
// (zip-native + hanzoai/orm, beego-free); the retired Casdoor iam-v1 embed is GONE.
// STAGED: the operator adds "iam" to --enable only after IAM config + the fold are
// verified (login/authorize/token/jwks + the operator SSO chain).
{Name: "iam", Mount: iam.Mount},
// Embedded Base app engine + viral waitlist (/v1/waitlist/*). STAGED behind
// CLOUD_BASE_EMBED. OwnsHealth: native /v1/base/health.
{Name: "base", Mount: base.Mount, Shutdown: base.Shutdown, OwnsHealth: true},
// The ONE observability subsystem: the in-repo o11y READ plane + runtime-handler
// install (o11y.SetHandler), with the hanzoai/o11y module wildcard /v1/o11y/*
// folded in as the TERMINAL sub-mount INSIDE o11y.MountO11y. Every specific
// /v1/o11y/* route registers before that wildcard, so Fiber's in-order match gives
// them precedence. NOT OwnsHealth: /v1/o11y/health stays the generic always-ok
// route (registered before MountAll), exactly as when the former module co-entry —
// which also set OwnsHealth=false — triggered it.
{Name: "o11y", Mount: o11y.MountO11y, Shutdown: o11y.ShutdownO11y},
{Name: "authz", Mount: authz.Mount},
// Embedded commerce plane /v1/commerce/*, /_/commerce/* — the hanzoai/commerce
// MODULE via the adapter in commerce.go (un-forked; the in-process
// CommerceClient is wired directly in pickCommerceClient).
{Name: "commerce", Mount: mountCommerce},
{Name: "licensing", Mount: licensing.Mount},
// clients/plan.Mount. Enable id normalized "plans" -> "plan" to match the
// package + generated cmd/plan (one subsystem, one name). Its product routes
// stay /v1/plans/* (incl. the OwnsHealth /v1/plans/health probe) — unchanged.
{Name: "plan", Mount: plan.Mount, OwnsHealth: true},
{Name: "pricing", Mount: pricing.Mount, OwnsHealth: true},
// /v1/s3/buckets/* + /v1/s3/health. Mounts BEFORE provisioning (120) so its static
// routes win over provisioning's /v1/s3/:name. OwnsHealth (real fail-closed probe).
{Name: "storage", Mount: storage.Mount, OwnsHealth: true},
// Provisioning control plane: /v1/sql,/v1/vector,/v1/datastore,/v1/kv,/v1/search,/v1/s3,/v1/docdb.
{Name: "provisioning", Mount: provisioning.Mount},
{Name: "billing", Mount: billing.Mount},
// Rolling AI-spend cap: installs the ai gate's per-tier trailing-window cap
// reader (registers no routes; its admin-editable knobs are platform switches
// surfaced in the /v1/admin/flags cockpit). After commerce/plan so the tier +
// finance globals it composes are wired.
{Name: "rollingcap", Mount: rollingcap.Mount},
// CATCH-ALL /v1/billing/* + /v1/commerce/* data bridges — AFTER clients/billing
// (121) + the commerce embed (100). Same clients/account package as "account" (48).
{Name: "account-bridge", Mount: account.MountBridge},
{Name: "do", Mount: do.Mount},
{Name: "platform", Mount: platform.Mount, Shutdown: ctxShutdown(platform.Shutdown), OwnsHealth: true},
{Name: "projects", Mount: projects.Mount, Shutdown: ctxShutdown(projects.Shutdown)},
// The /v1/dns forward head: relays the console DNS dashboard to the DNS
// control plane under the caller's own validated bearer (clients/dns).
{Name: "dns", Mount: dns.Mount},
// The registrar: search/price/register domains (name.com) per org.
{Name: "domain", Mount: domain.Mount},
{Name: "prompts", Mount: prompts.Mount},
{Name: "agents", Mount: agents.Mount, Shutdown: agents.Shutdown},
// The unified AI login manager registry (/v1/links). Mounts AFTER agents so
// a link revoke can stop the affected agent sessions in-process.
{Name: "link", Mount: link.Mount, Shutdown: link.Shutdown},
{Name: "wallets", Mount: wallets.Mount, Shutdown: ctxShutdown(wallets.Shutdown)},
// x402 pay-per-use: settles a signed ERC-3009 authorization to a recipient
// wallet through the metering spine. Mounts AFTER wallets (it resolves the
// recipient via wallets.ResolvePaymentTarget) and provides the Enforce
// middleware a marketplace applies to its priced routes.
{Name: "x402", Mount: x402.Mount, Shutdown: ctxShutdown(x402.Shutdown)},
{Name: "paas", Mount: paas.Mount, OwnsHealth: true},
// GitOps deploy dashboard /v1/deploy/* (the ArgoCD-grade fleet view over the
// operator App CRs). After paas so the release seam paas installs is registered
// before a gitops rollback delegates to it; owns its own /v1/deploy/health.
{Name: "deploy", Mount: deploy.Mount, OwnsHealth: true},
{Name: "functions", Mount: functions.Mount},
{Name: "tracker", Mount: tracker.Mount},
{Name: "templates", Mount: templates.Mount},
// OSS-template compute-cost basis /v1/blueprint/* — parses a blueprint's
// docker-compose into its SBOM (bill of container images) and prices the
// stack's CPU/memory footprint through a documented rate card. The per-hour
// rate the deploy path meters an org on, and the "~$X/mo to run" the console
// shows; it is the compute cost the 20% author royalty (clients/authors) is
// taken from. OwnsHealth: serves its own /v1/blueprint/health. Reference
// content (embedded blueprints), no store → no Shutdown. After templates, its
// sibling catalog concern; before the AI /v1/* catch-all.
{Name: "blueprint", Mount: blueprint.Mount, OwnsHealth: true},
{Name: "framework", Mount: framework.Mount, Shutdown: ctxShutdown(framework.Shutdown)},
{Name: "knowledge", Mount: knowledge.Mount},
// Hanzo Support PUBLIC plane /v1/help/* (help center KB read + customer ticket
// intake) — the anonymous face the secure-by-default framework surface can't
// serve. A framework lane like knowledge: its DocType fixtures register via
// init() (help.Module), and this mounts the thin public subsystem. Owns no store
// (delegates to the framework in-process API), so no Shutdown. After framework
// (whose in-process API it calls at request time); before the AI /v1/* catch-all.
{Name: "help", Mount: help.Mount},
// Marketing content loop /v1/content/* (generate → CMS → transition → publish).
// After framework (its DocType store the ops read/write) + knowledge (the sibling
// framework lane); before the AI /v1/* catch-all so /v1/content/* resolves here.
// CRUD/tenancy/install are framework's; this adds the board, lifecycle transition,
// and the generate/publish orchestration over the zen5 + studio + social edges.
{Name: "content", Mount: content.Mount, Shutdown: ctxShutdown(content.Shutdown)},
// Reverse storefront loop: consume the commerce COMMERCE stream (product.created)
// → content.EnsureCatalogAsset (render the new product's ecom asset, design==slug).
// After content (whose EnsureCatalogAsset it drives). Inert until CLOUD_COMMERCE_NATS_URL
// names the NATS carrying commerce catalog events — the reverse of the forward edge.
{Name: "catalogsync", Mount: catalogsync.Mount, Shutdown: catalogsync.Shutdown},
// The platform-global webhook layer: /v1/webhooks registry (per-org SQLite) +
// ONE durable JetStream consumer that delivers ANY bus event to org-registered
// HTTP subscribers. A bus consumer like catalogsync — placed adjacent to it and
// after the commerce embed whose COMMERCE stream it reads. Fail-soft: the
// registry serves even with the bus down; the consumer retries in the background.
// Owns per-org store handles + a worker pool → Shutdown drains both.
{Name: "webhooks", Mount: webhooks.Mount, Shutdown: webhooks.Shutdown},
{Name: "ml", Mount: ml.Mount, OwnsHealth: true},
{Name: "usage", Mount: usage.Mount},
// Gamified usage analytics: /v1/usage/leaderboard + /v1/usage/activity + the
// per-day contribution graph, over the datastore rollup (#43). Co-owns /v1/usage/*
// with usage (a distinct concern — who leads + your activity graph) at its own
// exact paths; owns the opt-in SQLite store. Before the ai /v1/* catch-all.
{Name: "leaderboard", Mount: leaderboard.Mount, Shutdown: leaderboard.Shutdown},
{Name: "crm", Mount: crm.Mount},
// Native /v1/marketing/* — the in-process fold of github.com/hanzoai/marketing
// (per-org campaign store on Base/SQLite), twin of crm. Owns a DB handle, so
// its Shutdown closes it cleanly on SIGTERM (ctxShutdown adapts func() error).
{Name: "marketing", Mount: marketing.Mount, Shutdown: ctxShutdown(marketing.Shutdown)},
// Native /v1/ads/* — the net-new per-org ad-campaign store on Base/SQLite,
// twin of crm/marketing. Owns a DB handle, so its Shutdown closes it cleanly
// on SIGTERM (ctxShutdown adapts func() error).
{Name: "ads", Mount: ads.Mount, Shutdown: ctxShutdown(ads.Shutdown)},
// Top-level GTM orchestration /v1/campaign/* — the capability layer that fans a
// campaign VALUE out to its channels (paid→ads, organic→publish, email→marketing),
// each CONSUMING the connector plane via integrations.TokenFor. Metrics read from
// the ONE analytics plane (never a second store); creative A/B composes the
// experiment seam. The paid channel executor is wired in wire_seams.go. Owns a DB
// handle, so its Shutdown closes it cleanly on SIGTERM.
{Name: "campaign", Mount: campaign.Mount, Shutdown: ctxShutdown(campaign.Shutdown)},
// GDA/SDM validator onboarding /v1/validators/* — wallet-sig + ETH-mainnet
// GenesisNFT ownerOf → seal luxd staking identity into KMS → write a NEW-node
// LuxNetwork CR (node.lux.cloud, never the live luxd) → enqueue an owner-gated
// registration (never auto-submitted to any P-Chain). Owns a DB handle.
{Name: "validators", Mount: validators.Mount, Shutdown: ctxShutdown(validators.Shutdown)},
// Native /v1/social/* — the in-process fold of the live social stack
// (github.com/hanzoai/social: social-backend/frontend/orchestrator, a Postiz-style
// scheduler), a per-org accounts+posts store on Base/SQLite, twin of crm. Owns a DB
// handle, so its Shutdown closes it cleanly on SIGTERM (ctxShutdown adapts func() error).
{Name: "social", Mount: social.Mount, Shutdown: ctxShutdown(social.Shutdown)},
{Name: "analytics", Mount: analytics.Mount, OwnsHealth: true},
{Name: "git", Mount: git.Mount},
// Universal sync (/v1/sync/links + engine). Registers the cloud.SyncEngine the
// GitHub/Gitea webhooks enqueue to; git is its first provider. Owns per-org
// DB handles, so its Shutdown closes them on SIGTERM.
{Name: "sync", Mount: sync.Mount, Shutdown: ctxShutdown(sync.Shutdown)},
{Name: "visor", Mount: visor.Mount},
// Connect-a-cloud-account plane /v1/cloud/*: an org links its DigitalOcean /
// AWS / GCP / Azure accounts (labeled, KMS-sealed, keyless where possible),
// Hanzo DISCOVERS each account's native Kubernetes clusters and FOLDS them into
// the ONE fleet (clients/fleet.Register) — so they surface in visor's
// /v1/clusters and run work like any BYO/managed cluster. No second registry.
{Name: "venue", Mount: venue.Mount},
// Cap table on Base via goja. STAGED behind CLOUD_ENABLE.
{Name: "captable", Mount: captable.Mount, Shutdown: captable.Shutdown},
{Name: "code", Mount: code.Mount, Shutdown: code.Shutdown},
{Name: "zero-trust", Mount: zt.Mount},
// ngrok-native public sharing: /v1/share/* provisions a per-org zrok
// account so `hanzo share <port>` publishes a local service to a public
// https://<token>.share.hanzo.ai URL. Fail-closed until ZROK_ADMIN_TOKEN.
{Name: "share", Mount: share.Mount},
// Data rooms via goja + per-tenant Base. STAGED behind CLOUD_ENABLE. OwnsHealth.
{Name: "dataroom", Mount: dataroom.Mount, Shutdown: dataroom.Shutdown, OwnsHealth: true},
{Name: "graph", Mount: graph.Mount},
{Name: "security", Mount: security.Mount, Shutdown: ctxShutdown(security.Shutdown), OwnsHealth: true},
{Name: "integrations", Mount: integrations.Mount, Shutdown: integrations.Shutdown},
// Marketing destinations /v1/destinations/* — the native fan-out that
// TRANSLATES the canonical /v1/event stream to each connected ad/analytics
// platform (GA4 Measurement Protocol, Meta Conversions API, X/LinkedIn/TikTok/
// Reddit) and forwards it server-side. Mounts AFTER analytics (whose fan-out
// sink it installs) and integrations (a destination may reuse an OAuth
// connection's token via integrations.TokenFor). Owns a DB handle → Shutdown.
{Name: "destinations", Mount: destinations.Mount, Shutdown: ctxShutdown(destinations.Shutdown)},
// First-class per-org Cloudflare asset plane /v1/cloudflare/{zones,pages,workers,
// ai,r2,kv,d1}/* (sibling of /v1/dns, /v1/domain). Mounts AFTER integrations
// because it reads the org's Cloudflare token through the integrations custody
// seam (integrations.TokenFor) — one token, one custody boundary. Connecting the
// provider stays on the integrations plane; this plane only MANAGES resources.
{Name: "cloudflare", Mount: cloudflare.Mount},
{Name: "sbom", Mount: sbom.Mount, OwnsHealth: true},
{Name: "team", Mount: team.Mount, Shutdown: ctxShutdown(team.Shutdown)},
{Name: "settings", Mount: settings.Mount, Shutdown: settings.Shutdown},
{Name: "prefs", Mount: prefs.Mount, Shutdown: prefs.Shutdown},
{Name: "notify", Mount: notify.Mount, OwnsHealth: true},
{Name: "channels", Mount: channels.Mount, Shutdown: channels.Shutdown},
{Name: "gateway", Mount: gateway.Mount},
{Name: "entitlements", Mount: entitlements.Mount, Shutdown: entitlements.Shutdown},
{Name: "exec", Mount: exec.Mount},
{Name: "websearch", Mount: websearch.Mount},
{Name: "world", Mount: world.Mount, Shutdown: ctxShutdown(world.Shutdown)},
// The bot runtime's ops face (/v1/bot/*). The transport itself is domain-free;
// the run control plane is "bots" below.
{Name: "runtime", Mount: runtime.Mount},
{Name: "authors", Mount: authors.Mount, Shutdown: ctxShutdown(authors.Shutdown)},
{Name: "bots", Mount: bots.Mount},
{Name: "audit", Mount: auditlog.Mount},
{Name: "affiliates", Mount: affiliates.Mount},
// Hanzo Sign (e-signature) via goja + per-tenant Base. STAGED behind CLOUD_ENABLE. OwnsHealth.
{Name: "sign", Mount: sign.Mount, Shutdown: sign.Shutdown, OwnsHealth: true},
{Name: "product", Mount: product.Mount},
{Name: "evals", Mount: eval.Mount},
{Name: "benchmark", Mount: benchmark.Mount},
// The R&D EVIDENCE plane (HIP-0512) + its R&D Ops Board UI at /research —
// the arena's sibling: benchmark measures, research is the versioned diary
// every product's runs accrue into. Non-staged: mounts under the default.
{Name: "research", Mount: research.Mount, Shutdown: ctxShutdown(research.Shutdown)},
// The unified EXPERIMENT primitive (/v1/experiments): A/B testing as ONE value
// whatever the variant kind (feature | ad creative | email | model). It is a
// COMPOSITION — assignment via flags, measurement via analytics, evidence via
// research — so it mounts AFTER all three. It owns only the experiment registry
// store → Shutdown. clients/campaign composes it (experiments.Assign/Analyze).
{Name: "experiments", Mount: experiments.Mount, Shutdown: ctxShutdown(experiments.Shutdown)},
// The revenue BOOKS spine (/v1/books): a native double-entry general ledger that
// reads commerce transactions (the sole posting source) and books the accounting twin —
// plus bank import (PDF/OFX/CSV/Plaid/Teller), reconciliation, and the AI Ask brain.
{Name: "books", Mount: books.Mount, Shutdown: ctxShutdown(books.Shutdown)},
{Name: "treasury", Mount: treasury.Mount, Shutdown: ctxShutdown(treasury.Shutdown)},
{Name: "admin", Mount: admin.Mount},
// Launch-control gate (per-service waitlist): the COMPLETE feature — host→service
// registry + brand seed + the waitlist.<svc> switch registration + the
// /v1/flags/waitlist (and /v1/admission/mode compat) mode read + the Enforce
// middleware — COMPOSING the flags engine one-way (flags.Bool/Register/
// SetPlatformSwitch; flags never imports admission). Mounts AFTER flags so the
// engine's platform-switch plane is installed first; the admin board is the
// /v1/admin/services lens over it. Owns the registry store handle → Shutdown.
{Name: "admission", Mount: admission.Mount, Shutdown: ctxShutdown(admission.Shutdown)},
// Tasks: the durable workflow/UI surface AND platform cron (durable schedules
// on the same shared engine, replacing every k8s CronJob). cron was a separate
// Wire entry; it mounts no routes and only registers schedules, so it is folded
// in as a sub-mount of tasks.Mount — ONE tasks subsystem.
{Name: "tasks", Mount: tasks.Mount},
// Automations: the connector catalogue + flow engine AND native single-connector
// execution (POST /v1/automations/connectors/:id/run, HIP-0126). The connector
// runner mounts no other routes, so it is folded in as a sub-mount of
// automations.Mount (was a separate "connectorruntime" entry) — ONE subsystem.
{Name: "automations", Mount: automations.Mount, Shutdown: automations.Shutdown},
// Unified tool plane: /v1/tools/* — the ONE registry (connectors, functions,
// agents, skills, external MCP servers, full-cloud-control /v1 routes), per-org
// activation, and the unified MCP endpoint. Sources register into it from their
// own Mounts, so mount position is not load-bearing (List/Dispatch run at request
// time); placed after automations, before the zen/ai catch-all so /v1/tools wins.
{Name: "tools", Mount: tools.Mount, Shutdown: tools.Shutdown},
// Marketplace: /v1/marketplace/* — listing/discovery/install over the tool plane,
// with x402-priced monetized listings. Mounts after tools (it fills the price seam).
{Name: "marketplace", Mount: marketplace.Mount, Shutdown: marketplace.Shutdown},
{Name: "referrals", Mount: referrals.Mount},
// Business AI Guide /v1/guide/* — the interactive launch checklist engine +
// the agent that executes a step through the per-principal MCP plane. After
// automations (whose InvokeTool it drives) and referrals; before the ai
// catch-all. Owns per-org SQLite, so its Shutdown closes the stores.
{Name: "guide", Mount: guide.Mount, Shutdown: ctxShutdown(guide.Shutdown)},
// Hanzo Company — the incorporation + fundraising state machine
// (/v1/company/*). Mounts after the seams it composes (integrations for the
// google token custody; captable/dataroom facades) and before the /v1/* AI
// catch-all so its routes resolve here.
{Name: "company", Mount: company.Mount, Shutdown: company.Shutdown},
// The corporate back-office surfaces — orthogonal to company/captable/billing:
// Hanzo Compliance (/v1/compliance) orchestrates KYC/KYB verification providers
// + tracks accreditation state + surfaces the SOC 2 audit posture; Hanzo Legal
// (/v1/legal) is the versioned template + generation engine + e-sign/filing seams.
// Both are TOOLING with providers/professionals in the loop, never advice or
// certification. They mount before the /v1/* AI catch-all so their routes resolve.
{Name: "compliance", Mount: compliance.Mount, Shutdown: ctxShutdown(compliance.Shutdown), OwnsHealth: true},
{Name: "legal", Mount: legal.Mount, Shutdown: ctxShutdown(legal.Shutdown), OwnsHealth: true},
// Chat orchestrator — POST /v1/chat: ONE LLM tool-calling round over the tool
// plane. It COMPOSES the ai completion path (in-process, so per-org billing
// runs) + the unified tool registry, and splits the model's tool calls into
// server-executed actions and client-applied ops. Mounts BEFORE the zen/ai
// catch-all so /v1/chat resolves here (Fiber first-match); the ai module's
// beego /v1/chat alias behind its /v1/* glob is thereby shadowed, while ai
// keeps /v1/chat/completions + /v1/completions.
{Name: "agent", Mount: agent.Mount},
// The UNIFIED GROUNDED ADVISOR — POST /v1/ask. DISTINCT from /v1/chat/completions
// (ai's RAW model) and /v1/agent (tool-calling): it routes a plain-language question
// to the domain(s) that can GROUND it, reads the REAL figures from each domain's own
// endpoint IN-PROCESS under the caller's own creds (agent.go's replay pattern, so
// per-tenant isolation is inherited), hands the model the EXACT figures, and returns
// the grounded answer + figures + the domain reads that backed them. The model NEVER
// invents a figure. Contributors plug in via a registry (books today; o11y/billing
// next) WITHOUT a router edit. Mounts BEFORE the ai /v1/* catch-all so /v1/ask wins
// Fiber's first-match; after books/agent so the domains it composes are wired.
{Name: "ask", Mount: ask.Mount},
// The bare /v1/* AI catch-all — the LAST route position. Every owning subsystem above
// wins its own namespace (Fiber first-match); AI is the fallback for the rest of /v1/*.
// zen mounts as a /v1-scoped Claim middleware BEFORE ai: it routes zen* models
// to zen's serving layer in-process (identity, tools, 1M ladder, codec) and
// c.Next()s everything else to ai. zen owns the zen family; ai owns every
// other model and the /v1/models list. Order is load-bearing — Claim must
// run before ai's catch-all. (See hip-00NN.)
{Name: "zen", Mount: mountZen},
{Name: "ai", Mount: ai.Mount},
// Runtime wasm/proxy plugins — mounts dead last.
{Name: "plugins", Mount: plugin.Mount},
}
}
// ServeSingle is the ONE way to run a single app standalone: validate `name`
// against Wire(), then serve exactly it (cloud.Serve with a one-name enable
// list — MountAll mounts only it). It is the path `hanzo <name>` already uses;
// promoting it here lets each cmd/<app>/main.go stub reuse it instead of
// re-implementing the dispatch, so adding an app in Wire() is still the one edit
// and its standalone binary comes for free (generated). Returns an error for an
// unknown name rather than booting a no-op.
func ServeSingle(name string) error {
if name == "" {
return fmt.Errorf("ServeSingle: empty app name")
}
for _, spec := range Wire() {
if spec.Name == name {
return cloud.Serve(Wire(), []string{name})
}
}
return fmt.Errorf("ServeSingle: unknown app %q — run `hanzo code ls`/`hanzo` for the list", name)
}
// mountMetrics adapts hanzoai/metrics into a cloud.MountFunc. Unlike the other
// externals, metrics declares its OWN narrow Deps (Logger, DataDir, Brand) and does
// not import hanzoai/cloud, so cloud.Typed cannot bridge it: the composition root
// builds metrics.Deps from cloud.Deps and calls metrics.Mount explicitly here.
func mountMetrics(a *zip.App, deps cloud.Deps) error {
return metrics.Mount(a, metrics.Deps{Logger: deps.Logger, DataDir: deps.DataDir, Brand: deps.Brand})
}
// ctxShutdown adapts a subsystem's zero-arg Shutdown() error to the
// cloud.ShutdownFunc(ctx) signature. Several subsystems expose the simpler form
// (their teardown ignores the deadline); this bridges the impedance mismatch in ONE
// place so the Wire entries stay declarative — no inline closures.
func ctxShutdown(f func() error) cloud.ShutdownFunc {
return func(context.Context) error { return f() }
}
+535
View File
@@ -0,0 +1,535 @@
// Copyright © 2026 Hanzo AI. MIT License.
// commerce.go mounts the hanzoai/commerce MODULE into the unified cloud binary
// (HIP-0106) via the NATIVE co-residence contract: commerce registers its routes
// directly on the HOST's zip app (EmbedConfig.App) — one router, one specificity
// space, zero handler adaptation. This adapter narrows cloud.Deps, boots the
// embed, and wires the in-process seams. Direction is one-way: cloud → commerce.
//
// PCI SCOPE. Commerce is a LIGHT ROUTER, NOT in PCI-DSS scope: tokens + intent IDs
// only, NEVER a PAN. PAN-touching paths call the out-of-process Payments / Vault
// (ZAP-RPC); when those clients are absent the payment handlers fail closed while
// tenant config + admin stay served — mountCommerce warns loudly at startup.
//
// FAIL-SOFT. A broken Embed does NOT crash the binary: commerce degrades to a 503
// on its own prefixes while every co-resident subsystem stays up.
package apps
import (
"context"
"fmt"
"net/http"
"path/filepath"
"strings"
"time"
"github.com/hanzoai/cloud"
accountclient "github.com/hanzoai/cloud/clients/account"
"github.com/hanzoai/cloud/clients/commerceclient"
"github.com/hanzoai/cloud/clients/commerceinproc"
financeclient "github.com/hanzoai/cloud/clients/finance"
"github.com/hanzoai/cloud/clients/principal"
"github.com/hanzoai/commerce"
commercebilling "github.com/hanzoai/commerce/api/billing"
catalogapi "github.com/hanzoai/commerce/api/catalog"
planapi "github.com/hanzoai/commerce/api/plan"
commercestore "github.com/hanzoai/commerce/api/store"
commercedatastore "github.com/hanzoai/commerce/datastore"
commercemid "github.com/hanzoai/commerce/middleware"
"github.com/hanzoai/commerce/middleware/iammiddleware"
commercensctx "github.com/hanzoai/commerce/util/nscontext"
log "github.com/luxfi/log"
"github.com/zap-proto/zip"
)
func init() {
// In-process CommerceClient factory — pickCommerceClient calls it when the
// commerce subsystem is enabled. Registered HERE (not called directly from
// package cloud) because commerceclient's entitlement client imports
// clients/plan, which imports cloud: the hook keeps the package graph acyclic.
cloud.RegisterCommerceClientFactory(func(cfg *cloud.Config, _ log.Logger) cloud.CommerceClient {
return commerceclient.InProcessClient(cfg.Brand)
})
}
// commercePrefixes is every root path the commerce surface owns on the shared
// app. Under the native SharedApp contract most of these are registered by
// commerce's own setupRoutes; the list is the fail-closed 503 set AND the wire
// contract commerce_prefix_test pins — the route families a session gate or the
// AI /v1/* catch-all must never swallow:
var commercePrefixes = []string{
"/v1/commerce", // public checkout + tenant + catalog + deposits
"/_/commerce", // tenant-admin surface
// The BARE store surface: GET /v1/store/current (the org-scoped default
// store the admin dashboard AND the content storefront edge resolve), the
// per-listing upsert /v1/store/:id/listing/:slug the publish edge writes,
// and the public storefront reads karma.style serves at runtime. Without
// this owner, /v1/store/* fell through to the bare /v1/* AI catch-all —
// whose prepaid BALANCE gate 402'd every store read (a store-metadata read
// must never require an LLM balance).
"/v1/store",
// Platform-admin catalog CMS: GET/POST/PUT/DELETE /v1/catalog/entries +
// POST /v1/catalog/seed — the SuperAdmin CRUD admin.hanzo.ai's editor drives.
// commerce's setupRoutes wires only the PUBLIC read (/v1/commerce/catalog);
// the CRUD lives on the standalone /v1 bundle (api.Route → catalogApi.AdminRoute),
// which the co-resident embed skips, so mountCommerce mounts it below on the
// same /v1 gate chain. Own the prefix here so it reaches commerce (each handler
// is requireSuperAdmin-gated) instead of the AI /v1/* balance catch-all.
"/v1/catalog",
// Platform-admin subscription/DNS plan authority CMS: GET/POST/PUT/DELETE
// /v1/plans/entries + POST /v1/plans/seed (increment 3a) — the SuperAdmin CRUD
// the console plan editor drives. The PUBLIC read stays GET /v1/billing/plans;
// this CRUD rides the /v1 bundle (api.Route → planApi.AdminRoute), which the
// embed skips, so mountCommerce mounts it below. Own the prefix so it reaches
// commerce (each handler requireSuperAdmin-gated), not the AI /v1/* 402 gate.
"/v1/plans",
// Payment-provider webhook receiver (POST /v1/billing/webhooks/:provider —
// Square et al). The provider's HMAC over the registered notification URL +
// body IS the auth; a bearer gate is impossible for provider callbacks.
"/v1/billing/webhooks",
// The platform auto-recharge sweep (PlatformOnly, POST .../run-all). The
// durable cron's poke carries the COMMERCE_SERVICE_TOKEN bearer; without
// this owner it lands on the account-bridge /v1/billing/* catch-all, whose
// session gate 403s a service token. (Landed 5x before the unfork — #274 —
// and the pin test lives beside THIS list so it can't silently regress.)
"/v1/billing/auto-recharge",
}
// mountCommerce boots commerce ON the shared zip app (native co-residence).
// commerce's own setupRoutes registers /v1/commerce/* and /_/commerce/*
// directly; the standalone-only surfaces (bare /healthz, legacy /admin SPA,
// checkout SPA root catch-all, Listen) are skipped by the SharedApp contract.
// This adapter registers the remaining wire-contract families with commerce's
// own gate chains (see commercePrefixes).
func mountCommerce(app *zip.App, deps cloud.Deps) error {
if app == nil {
return fmt.Errorf("commerce: nil zip.App")
}
if deps.Logger == nil {
return fmt.Errorf("commerce: nil deps.Logger")
}
lg := deps.Logger.New("subsystem", "commerce")
if deps.Payments == nil {
lg.Warn("commerce: deps.Payments is nil — payment intent paths will fail; tenant config + admin still served")
}
if deps.Vault == nil {
lg.Warn("commerce: deps.Vault is nil — vault charge paths unavailable; tenant config + admin still served")
}
// Native zip health endpoint — registered FIRST so probes answer even when
// the embed fails below.
app.Get("/_/commerce/healthz", func(c *zip.Ctx) error {
return c.JSON(http.StatusOK, map[string]string{"status": "ok", "service": "commerce"})
})
// commerce persists its per-org SQLite + `base` tree under <DataDir>/commerce,
// NEVER at DataDir directly: cloud already owns DataDir/orgs and DataDir/base,
// and commerce also writes orgs/ + base/ — sharing the root would collide two
// apps on the same SQLite files and corrupt them.
dataDir := "/var/lib/cloud/commerce"
if deps.DataDir != "" {
dataDir = filepath.Join(deps.DataDir, "commerce")
}
embedded, err := commerce.Embed(context.Background(), commerce.EmbedConfig{
DataDir: dataDir,
// RequireIdentity stays gateway-owned: the gateway in front of the cloud
// binary is the trust boundary per HIP-0026.
RequireIdentity: false,
// THE native co-residence contract: commerce registers its routes on
// cloud's own app — no second engine, no net/http adaptation.
App: app,
// ONE LEDGER: commerce's POST /v1/billing/credit mints into cloud's native
// finance ledger (the SAME per-org account the AI spend-gate reads), so a
// granted credit is immediately spendable. commerce.Embed calls
// creditledger.Set(this) before routes register; nil would leave commerce on
// its own datastore (standalone), but in this unified binary finance is
// co-resident, so we inject the finance-backed ledger adapter.
Ledger: ledger{},
})
if err != nil {
lg.Error("commerce embed failed — serving fail-closed 503 (cloud stays up)", "err", err)
mountCommerceFailClosed(app)
return nil
}
// The BARE /v1/store surface (see commercePrefixes). Group-scoped chain
// mirrors the standalone /v1 bundle: gated request context, host, IAM
// resolution; store.Route's own tokenRequired arg gates the CRUD.
storeV1 := app.Group("/v1")
storeV1.Use(commercemid.AddHost(), commercemid.RequestContext(), commerceErrorScope())
// Unconditional, exactly like the standalone bundle: IAMTokenRequired
// no-ops gracefully when IAM is not initialized.
storeV1.Use(iammiddleware.IAMTokenRequired())
commercestore.Route(storeV1, commercemid.TokenRequired())
// Platform-admin catalog CMS on the SAME /v1 bundle: GET/POST/PUT/DELETE
// /v1/catalog/entries + POST /v1/catalog/seed. setupRoutes wires only the
// public read (/v1/commerce/catalog); the CRUD rides the standalone /v1 bundle
// (api.Route → catalogApi.AdminRoute), which the co-resident embed skips — so
// register it here, exactly as the standalone does. storeV1's IAMTokenRequired
// populates the claims each handler's requireSuperAdmin reads (anon → 403, a
// platform admin edits); it is cross-tenant data, never org-scoped.
catalogapi.AdminRoute(storeV1)
// Platform-admin subscription/DNS plan authority CRUD on the SAME /v1 bundle:
// GET/POST/PUT/DELETE /v1/plans/entries + POST /v1/plans/seed (increment 3a).
// Mirrors the catalog mount: the standalone wires it on the /v1 bundle
// (api.Route → planApi.AdminRoute), which the co-resident embed skips. The
// embed seed SOURCE is injected here (the composition root) — commercebilling.
// SeedRows, the SAME @hanzo/plans embed the boot seed + resolveSubscriptionPlan
// read — so api/plan never imports api/billing. Each handler is
// requireSuperAdmin-gated (anon → 403); prices are admin-editable but the mint
// gates score the IMMUTABLE embed, so an edit never moves a charge gate.
planapi.AdminRoute(storeV1, commercebilling.SeedRows)
// Provider webhook intake at the LIVE registered path. Chain mirrors the
// commerce-standalone posture: gated request context, then the sessionless
// HMAC-verified handler.
app.Post("/v1/billing/webhooks/:provider", commercemid.RequestContext(), commercebilling.HandleProviderWebhook)
// Durable-cron auto-recharge poke (COMMERCE_SERVICE_TOKEN bearer) at its
// live path — the bridge's session gate would 403 the poke. Same gate
// chain the commerce route table uses: TokenRequired authenticates the
// service token, PlatformOnly authorizes the mint.
app.Post("/v1/billing/auto-recharge/run-all",
commercemid.RequestContext(),
commercemid.TokenRequired(),
commercemid.PlatformOnly(),
commercebilling.RunAutoRechargeAllOrgs,
)
// GET /v1/billing/plans — the public tier catalog the console renders. commerce's
// legacy api.Route() billing bundle (ListPlans, invoices, subscriptions, …) is NOT
// registered by the co-resident embed: setupRoutes wires only /v1/commerce/*, so
// /v1/billing/plans has NO handler in this binary. The account bridge's
// /v1/billing/* wildcard (order 122) then forwards the read BACK to commerce at
// COMMERCE_URL — which defaults to the public api.hanzo.ai edge — re-entering the
// same bridge in an unbounded self-dispatch loop that surfaces as a 502
// ("commerce unreachable: Get https://api.hanzo.ai/v1/billing/plans"). Registering
// the static ListPlans handler HERE (order 100, ahead of the bridge) shadows that
// wildcard and serves plans in-process — the same co-resident move billing.go makes
// for usage/balance. RequestContext supplies the namespaced context promo.Active reads.
app.Get("/v1/billing/plans", commercemid.RequestContext(), commercebilling.ListPlans)
// The rest of the console's billing READS, served co-resident for the SAME reason
// plans is: commerce's api.Route() billing bundle is never compiled here, so without
// these registrations every one of them falls through to the account bridge's
// /v1/billing/* wildcard, which forwards to COMMERCE_URL — the public api.hanzo.ai
// edge, which is THIS binary — and self-dispatches into a 502 loop. In prod there is
// no separate commerce backend to point COMMERCE_URL at (the in-cluster `commerce`
// Service selects the cloud pods), so co-residence is the only way to break the loop.
//
// Chain: RequestContext (gated context) → IAMTokenRequired (resolves the org from the
// gateway-validated X-Org-Id into Locals("organization"), the namespace commerce's
// GetOrganization reads) → PinBillingSubject (pins the caller's OWN billing subject
// into the query — the SAME isolation the bridge applies, so a read can never widen
// past the caller; fail-closed for an unvalidated caller) → the commerce handler. The
// specific paths shadow the bridge wildcard (order 100 < 122). payment-config is
// org-scoped, not subject-scoped, but PinBillingSubject is still the auth gate that
// keeps an unvalidated caller from reaching GetOrganization; its pinned (unused)
// subject params are ignored by that handler.
billingRead := []struct {
path string
h zip.Handler
}{
{"/v1/billing/invoices", commercebilling.ListInvoices},
{"/v1/billing/invoices/:id/pdf", commercebilling.DownloadInvoicePDF},
{"/v1/billing/subscriptions", commercebilling.ListBillingSubscriptions},
{"/v1/billing/spend-alerts", commercebilling.ListSpendAlerts},
{"/v1/billing/payouts", commercebilling.ListPayouts},
{"/v1/billing/payment-config", commercebilling.GetPaymentConfig},
}
for _, r := range billingRead {
app.Get(r.path,
commercemid.RequestContext(),
iammiddleware.IAMTokenRequired(),
accountclient.PinBillingSubject(),
r.h,
)
}
// GET /v1/billing/spend-alerts/authorize — the per-request per-scope spend-CAP
// VERDICT the request-edge metering gate consumes (clients/metering scopeAuthorize,
// pathLimitsAuthorize). It is a SERVICE-token S2S read (COMMERCE_SERVICE_TOKEN +
// X-Org-Id), NOT a browser/IAM read — so it needs its OWN registration, distinct from
// the console billingRead block above: without a co-resident handler this authorize
// fell through to the account bridge's /v1/billing/* wildcard (order 122), which — being
// service-token-forwardable (billing.go billingForwardable) — re-forwarded it to
// COMMERCE_URL (the public api.hanzo.ai edge = THIS binary) over commerceinproc's
// self-routing transport, re-entering the same wildcard until the depth-8 guard refused
// → 502 → the gate fails OPEN (the cap is a policy overlay, so no traffic was blocked,
// but ~135 502s/30m spammed the money path and each burned 8 full-app dispatches). The
// plain GET /v1/billing/spend-alerts (registered above) already broke this loop for the
// CRUD read; this closes the /authorize sibling the metering gate hits on every call.
//
// Chain mirrors commerce's OWN gate on this route (api/billing/handlers.go: the `billing`
// group's userRequired = TokenRequired) plus the RequestContext the standalone supplies
// globally — NOT the IAM/PinBillingSubject console chain: a raw service token is not an
// IAM JWT, so IAMTokenRequired would leave GetOrganization unset and AuthorizeSpendCap
// would 500. TokenRequired authenticates the service token AND resolves the tenant from
// the gateway-pinned X-Org-Id into Locals("organization"), which AuthorizeSpendCap reads.
// The specific route shadows the bridge wildcard (order 100 < 122). No PlatformOnly:
// authorize is a per-org cap read, not a cross-org mint (unlike auto-recharge/run-all).
app.Get("/v1/billing/spend-alerts/authorize",
commercemid.RequestContext(),
commercemid.TokenRequired(),
commercebilling.AuthorizeSpendCap,
)
// Self-service spend-cap CRUD WRITES — the customer half of the cap: a customer
// (or the admin S2S) CREATES / EDITS / REMOVES their own usage caps. These are the
// write siblings of the co-resident GET /v1/billing/spend-alerts list; without their
// own registration they too fell through the account bridge's /v1/billing/* wildcard
// (billingForwardable includes POST spend-alerts) into the SAME 502 self-dispatch loop
// authorize hit — so a customer could not set a cap AT ALL in the unified binary
// (POST/PATCH/DELETE all 502'd). Same chain commerce's own route table gates them with
// (api/billing/handlers.go:322-325, the `user` group's userRequired = TokenRequired) +
// the global RequestContext — an IAM JWT OR the COMMERCE_SERVICE_TOKEN, org resolved
// from the gateway-pinned X-Org-Id into Locals("organization"). Org-scoped by that
// namespace (a caller only ever writes their OWN org's caps; a foreign :id is a
// not-found miss in the caller's namespace), so no PinBillingSubject — spend-alerts are
// org-level, not billing-subject-level. Shadow the bridge wildcard (order 100 < 122).
// A spend cap is a FINANCIAL SAFETY control, so its writes are gated to an ORG ADMIN
// (or SuperAdmin, or the trusted S2S service token for the SuperAdmin cap-oversight
// Forward) — never any authenticated member. commerce's own `user` group admits any
// member, which would let a compromised member key DELETE the org's cap (→ unbounded
// spend) or POST a 1¢ enforce cap (→ org-wide 402 DoS). requireSpendCapAdmin closes that.
app.Post("/v1/billing/spend-alerts",
commercemid.RequestContext(),
commercemid.TokenRequired(),
requireSpendCapAdmin(),
commercebilling.CreateSpendAlert,
)
app.Patch("/v1/billing/spend-alerts/:id",
commercemid.RequestContext(),
commercemid.TokenRequired(),
requireSpendCapAdmin(),
commercebilling.UpdateSpendAlert,
)
app.Delete("/v1/billing/spend-alerts/:id",
commercemid.RequestContext(),
commercemid.TokenRequired(),
requireSpendCapAdmin(),
commercebilling.DeleteSpendAlert,
)
// POST /v1/billing/topup/token — the INLINE Square card top-up (the console's
// "Billing → Credits → add credits": the Square Web Payments SDK tokenizes the card
// IN THE BROWSER → a single-use nonce → this endpoint charges it and credits the
// caller's balance). commerce's api.Route() billing bundle is NOT compiled into the
// co-resident embed, so — exactly like plans/invoices/spend-alerts above — without
// this registration the POST fell through to the account bridge's /v1/billing/*
// wildcard (order 122). That wildcard is service-token-forwardable for topup/token
// (billing.go billingForwardable), so billingData re-forwarded it to COMMERCE_URL
// (default the public api.hanzo.ai edge = THIS binary) over commerceinproc's
// self-routing transport, re-entering the SAME wildcard until the depth-8 guard
// refused → the "commerceinproc: in-process dispatch depth 8 exceeded" 502 that broke
// top-up outright. Registering commerce's real TopupWithToken co-resident here
// (order 100 < 122) shadows the wildcard and serves the charge in-process at depth 1
// — no HTTP hop, no self-dispatch. topup/token STAYS in billingForwardable as the
// split-deploy fallback (a standalone commerce still serves it); co-residence just
// wins first.
//
// Chain — the browser money-WRITE posture, byte-for-byte what the bridge applied:
// RequireCSRF — the ambient-cookie anti-CSRF gate the bridge's requireCSRF
// wrapped POST /v1/billing/* with (a Bearer/gateway caller is
// not CSRF-able; an ambient-cookie write needs the token).
// RequestContext — the gated request context commerce's handler + ledger read.
// IAMTokenRequired — resolves the org from the gateway-validated X-Org-Id into
// Locals("organization"), which TopupWithToken.GetOrganization
// + topupDestination read as the org billing key.
// PinBillingSubject — pins ?user= to the caller's OWN account.Payer subject (the
// SAME rule the ai spend-gate debits and billingData pins), so
// the credit lands on the caller's subject (person=org/name) and
// can never be widened; fail-closed for an unvalidated caller —
// the IDOR boundary stays exactly where billingData put it.
// The card PAN never touches this binary: TopupWithToken charges the Square nonce only,
// and the settled charge itself is the mint authority (mintauth.WithAuthorized).
app.Post("/v1/billing/topup/token",
accountclient.RequireCSRF(),
commercemid.RequestContext(),
iammiddleware.IAMTokenRequired(),
accountclient.PinBillingSubject(),
commercebilling.TopupWithToken,
)
// The remaining console billing WRITES that share topup/token's self-dispatch loop
// class — each is a POST the console makes (billingForwardable in billing.go), each had
// NO co-resident handler, so each fell through to the account bridge's /v1/billing/*
// wildcard (order 122) and re-entered it over commerceinproc until the depth-8 guard
// refused (the same "in-process dispatch depth 8 exceeded" 502 that broke top-up). Each
// commerce handler exists in the vendored module (v1.49.13); registering them co-resident
// (order 100 < 122) shadows the wildcard and serves the write in-process at depth 1. They
// STAY in billingForwardable as the split-deploy fallback (same precedent as topup/token
// + spend-alerts). Chain matches the bridge's write posture byte-for-byte:
//
// - RequireCSRF — the ambient-cookie anti-CSRF gate the bridge wrapped POST
// /v1/billing/* with (Bearer/gateway callers are not CSRF-able).
// - RequestContext — the gated request context commerce's handlers read.
// - IAMTokenRequired — resolves the org from the gateway-validated X-Org-Id into
// Locals("organization") — the namespace GetOrganization reads.
// - PinBillingSubject — pins the caller's OWN account.Payer subject into BOTH query and
// body AND fail-closes an unvalidated caller. It is the auth gate
// on every one, and the IDOR control on the subject-scoped one.
//
// payment-methods (save a card-on-file / vault a Square nonce) is SUBJECT-scoped: commerce's
// CreatePaymentMethod reads `customerId` from the BODY, so PinBillingSubject's body-pin is
// load-bearing here — a member can only vault a card for their OWN subject, exactly the
// boundary billingData's scopedBillingBody enforced. The Square nonce goes to Square; the
// PAN never touches this binary.
app.Post("/v1/billing/payment-methods",
accountclient.RequireCSRF(),
commercemid.RequestContext(),
iammiddleware.IAMTokenRequired(),
accountclient.PinBillingSubject(),
commercebilling.CreatePaymentMethod,
)
// subscriptions/:id/{cancel,reactivate} are org-NAMESPACE-scoped: commerce's handlers
// resolve the subscription by `:id` WITHIN the caller's org namespace (a foreign org's id
// is a 404 miss), so tenancy is the namespace IAMTokenRequired resolves and PinBillingSubject
// is the fail-closed-anon auth gate — its pinned subject params are ignored by these
// handlers (the SAME role it plays for the org-scoped payment-config read). The bridge's
// subject-pin was likewise a no-op for these, so nothing is dropped.
app.Post("/v1/billing/subscriptions/:id/cancel",
accountclient.RequireCSRF(),
commercemid.RequestContext(),
iammiddleware.IAMTokenRequired(),
accountclient.PinBillingSubject(),
commercebilling.CancelBillingSubscription,
)
app.Post("/v1/billing/subscriptions/:id/reactivate",
accountclient.RequireCSRF(),
commercemid.RequestContext(),
iammiddleware.IAMTokenRequired(),
accountclient.PinBillingSubject(),
commercebilling.ReactivateBillingSubscription,
)
// In-process seams:
// - commerceinproc routes the S2S billing byte-stream into the co-resident
// app (the metering debit path) instead of a socket to a standalone pod.
// - commerceclient reads the Embedded's datastore DIRECTLY (entitlements +
// BalanceCents) — no HTTP shape at all.
commerceinproc.SetApp(app)
commerceclient.PublishEmbedded(embedded)
// Usage-cap enforcement on the FINANCE path. The unified binary records usage in
// the finance ledger (fin.RecordUsage), NOT commerce's transaction store — which
// it leaves empty — so the cap must read spend from, and fire alerts on, the
// finance ledger. Two seams, both org-wide (the finance Entry carries no scope;
// per-scope caps are a follow-up):
// - SetPeriodSpendReader: AuthorizeSpendCap's scopeSpentCents reads the org's
// finance period spend instead of the empty commerce transaction ledger, so
// a real LLM request increments the cap's `spent` and trips the 402.
// - SetUsageHook: after each finance debit, fire the org's spend-alerts on the
// SAME crossing (the alert half), reading the same finance spend + debouncing.
commercebilling.SetPeriodSpendReader(financePeriodSpend)
financeclient.SetUsageHook(fireCapAlert)
lg.Info("commerce embedded natively (hanzoai/commerce module on the shared zip app)",
"data_dir", dataDir,
"brand", deps.Brand,
"env", deps.Env,
)
return nil
}
// mountCommerceFailClosed serves an honest JSON 503 on every commerce prefix when
// the embed cannot boot, so /v1/commerce/* answers "commerce unavailable" instead
// commerceErrorScope confines commerce's JSON error envelope to commerce's OWN
// routes. commercemid.ErrorHandlerJSON is a `/v1` GROUP middleware, and fiber
// matches group middleware by PREFIX, not by the handle a route registered on —
// so on the shared `/v1` it wraps every subsystem mounted AFTER commerce and
// flattens their typed zip.HTTPError (403/400/…) into a blanket 500 (the store
// envelope always renders 500). Guarded by commercePrefixes, the envelope stays on
// commerce and every other subsystem renders its own status via zip's default
// handler — the pre-commerce subsystems (kms, o11y, …) already do; this makes the
// post-commerce ones (projects, agents, wallets, …) match.
func commerceErrorScope() zip.Handler {
envelope := commercemid.ErrorHandlerJSON()
return func(c *zip.Ctx) error {
if hasCommercePrefix(c.Path()) {
return envelope(c)
}
return c.Next()
}
}
// hasCommercePrefix reports whether path is a commerce-owned root (an exact prefix
// or a child of one), the SAME ownership commercePrefixes encodes for the
// fail-closed mount.
func hasCommercePrefix(path string) bool {
for _, p := range commercePrefixes {
if path == p || strings.HasPrefix(path, p+"/") {
return true
}
}
return false
}
// of falling through to another subsystem's catch-all.
func mountCommerceFailClosed(app *zip.App) {
failed := func(c *zip.Ctx) error {
c.SetHeader("Content-Type", "application/json")
return c.Bytes(http.StatusServiceUnavailable, []byte(`{"error":"commerce unavailable","code":503}`))
}
for _, p := range commercePrefixes {
app.All(p+"/*", failed)
}
}
// financePeriodSpend is the usage-cap's period-spend source (injected into commerce
// via SetPeriodSpendReader). It returns the org's finance-ledger usage in cents since
// the start of the CURRENT UTC month — the window the cap resets on (mirrors
// commerce periodStartUTC). Org-wide: the finance Entry carries no project/service,
// so scope args are ignored and the org total is returned (what the covering
// org-wide spend-alert row binds on). A finance impl without the sum capability, or a
// split deploy (no co-resident finance), reports 0 — the cap can never over-count.
func financePeriodSpend(ctx context.Context, org string, test bool, _, _ string) (int64, error) {
fin := financeclient.Current()
if fin == nil {
return 0, nil
}
summer, ok := fin.(interface {
SumUsageSince(context.Context, string, bool, int64) (int64, error)
})
if !ok {
return 0, nil
}
n := time.Now().UTC()
since := time.Date(n.Year(), n.Month(), 1, 0, 0, 0, 0, time.UTC).Unix()
return summer.SumUsageSince(ctx, org, test, since)
}
// fireCapAlert fires the org's spend-alerts after a finance usage debit — the alert
// half of the cap on the finance path (wired via finance.SetUsageHook). It resolves
// the org's commerce datastore (where the spend-alert rows live) and calls the
// exported commerce trigger, which reads the org's period spend via financePeriodSpend
// and stamps/debounces. Detached + best-effort; never blocks the money path. Runs in
// its own goroutine (the hook is invoked with `go`), so a background context is right.
func fireCapAlert(org string, test bool, project, service string) {
if strings.TrimSpace(org) == "" {
return
}
ctx := commercensctx.WithNamespace(context.Background(), org)
db := commercedatastore.New(ctx)
commercebilling.FireSpendAlerts(ctx, db, org, test, project, service, nil)
}
// requireSpendCapAdmin gates a spend-alert WRITE to a validated ORG ADMIN or platform
// SuperAdmin (the unforgeable SanitizeIdentity-minted X-User-IsOrgAdmin / isAdmin bits),
// OR the trusted in-proc S2S service token (the SuperAdmin cap-oversight Forward + internal
// automation). A validated non-admin MEMBER is REFUSED (403): a spend cap is a financial
// safety boundary — a member must not be able to delete the org's cap (→ unbounded spend)
// or set a punitive 1¢ cap (→ org-wide 402 DoS). The read paths (list/authorize) stay
// member/S2S-open; only the mutations require admin.
func requireSpendCapAdmin() zip.Handler {
return func(c *zip.Ctx) error {
if principal.IsSuperAdmin(c) || principal.IsOrgAdmin(c) || accountclient.IsServiceToken(c) {
return c.Next()
}
return zip.ErrForbidden("org admin required to change spend caps")
}
}
+82
View File
@@ -0,0 +1,82 @@
package apps
import (
"io"
"net/http/httptest"
"strings"
"testing"
commercemid "github.com/hanzoai/commerce/middleware"
"github.com/zap-proto/zip"
)
// TestCommerceErrorScope proves commerceErrorScope() confines commerce's always-500
// JSON envelope to commerce-owned prefixes: a post-commerce subsystem route
// (/v1/projects) that returns a typed 403 renders 403 (zip default), while a
// commerce route (/v1/store/...) still gets commerce's envelope. Mirrors the frozen
// order: kms (before commerce) → commerce /v1 group chain → projects + store (after).
// Regression for the release-smoke failure where 14 post-commerce endpoints 500'd.
func TestCommerceErrorScope(t *testing.T) {
app := zip.New(zip.Config{})
// kms (before commerce) — a clean 403 baseline (never wrapped by commerce).
app.Get("/v1/kms/health", func(c *zip.Ctx) error { return zip.ErrForbidden("kms says no") })
// commerce (position 39): the REAL group chain, now with the scoped envelope.
sv1 := app.Group("/v1")
sv1.Use(commercemid.AddHost(), commercemid.RequestContext(), commerceErrorScope())
// projects (after commerce) — typed 403; must NOT be clobbered to 500.
app.Get("/v1/projects", func(c *zip.Ctx) error { return zip.ErrForbidden("X-Org-Id required") })
// a commerce store route (after commerce) — typed 403; commerce envelope applies.
app.Get("/v1/store/current", func(c *zip.Ctx) error { return zip.ErrForbidden("store needs org") })
probe := func(path string) (int, string) {
req := httptest.NewRequest("GET", path, nil)
resp, err := app.Fiber().Test(req)
if err != nil {
t.Fatalf("%s: %v", path, err)
}
defer resp.Body.Close()
b, _ := io.ReadAll(resp.Body)
return resp.StatusCode, string(b)
}
// The invariant the scope guards: a typed zip.HTTPError (403) a subsystem returns
// is NEVER flattened to a 500 — not before commerce, not after it. (commerce
// >=1.48.10 honors the status itself; the scope keeps commerce's error handler off
// other subsystems' routes regardless, so a future commerce regression can't
// re-clobber them.)
for _, tc := range []struct {
path string
wantCode int
}{
{"/v1/kms/health", 403}, // before commerce
{"/v1/projects", 403}, // after commerce — must NOT be clobbered to 500
{"/v1/store/current", 403}, // commerce's own route — its handler still honors 403
} {
code, body := probe(tc.path)
t.Logf("%-20s -> %d %s", tc.path, code, body)
if code != tc.wantCode {
t.Errorf("%s: got %d, want %d (%s)", tc.path, code, tc.wantCode, body)
}
if strings.Contains(body, "\"status\":5") || code >= 500 {
t.Errorf("%s: a typed 403 was flattened to a 5xx (%s)", tc.path, body)
}
}
for _, p := range []struct {
path string
own bool
}{
{"/v1/store/current", true},
{"/v1/commerce/checkout", true},
{"/v1/projects", false},
{"/v1/agent/presets", false},
{"/v1/agents", false},
} {
if got := hasCommercePrefix(p.path); got != p.own {
t.Errorf("hasCommercePrefix(%q) = %v, want %v", p.path, got, p.own)
}
}
}
+120
View File
@@ -0,0 +1,120 @@
// Copyright © 2026 Hanzo AI. MIT License.
package apps
import (
"io"
"net/http"
"net/http/httptest"
"testing"
luxlog "github.com/luxfi/log"
"github.com/zap-proto/zip"
)
// TestCommercePrefixesPinned pins the wire paths that MUST reach the commerce gin
// handler — the ones a missing prefix silently regresses because they otherwise
// fall through to another owner (the account-bridge /v1/billing/* catch-all, or
// the bare /v1/* AI catch-all) that answers with the wrong contract:
//
// - /v1/billing/webhooks provider HMAC is the auth (Square et al); the
// session-gated bridge would 403 it.
// - /v1/billing/auto-recharge the durable cron's billing-autorecharge poke
// (COMMERCE_SERVICE_TOKEN bearer); without the prefix the poke 403s at the
// bridge ("sign in to view billing") — exactly how the first live fires
// failed, and how the commerce unfork regressed it once already.
// - /v1/store the bare storefront surface (GET /v1/store/current +
// the listing upsert/reads). Dropped by the unfork, it matched no owner and fell
// to the /v1/* AI balance gate, which 402'd every store read for a commerce-funded
// org (the karma /v1/store/current outage). It is metadata, never LLM inference.
func TestCommercePrefixesPinned(t *testing.T) {
want := map[string]bool{
"/v1/billing/auto-recharge": false,
"/v1/billing/webhooks": false,
"/v1/store": false,
"/v1/catalog": false,
"/v1/plans": false,
}
for _, p := range commercePrefixes {
if _, ok := want[p]; ok {
want[p] = true
}
}
for p, ok := range want {
if !ok {
t.Errorf("commercePrefixes missing %q — the route falls through to the wrong owner", p)
}
}
}
// TestStoreSurfaceRoutedToCommerceNotAIGate is the regression guard for the karma
// GET /v1/store/current → 402 outage. Because "/v1/store" is a commercePrefix, a
// store read is mounted on the commerce handler AHEAD of the bare /v1/* AI catch-all
// (Wire order: commerce@191 < ai@321; Fiber matches first-registered), so it resolves
// on commerce and NEVER reaches the LLM prepaid-balance gate that denied every store
// read for an org funded in commerce but $0 in the ai ledger.
func TestStoreSurfaceRoutedToCommerceNotAIGate(t *testing.T) {
app := zip.New(zip.Config{Logger: luxlog.New("test")})
// Mirror mountCommerce EXACTLY: app.All(prefix+"/*", handler) for each commerce
// prefix. The stub stands in for the embedded commerce gin handler that serves
// getCurrent (200 with the org's store).
commerce := zip.AdaptNetHTTP(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
w.Header().Set("Content-Type", "application/json")
_, _ = io.WriteString(w, `{"store":{"id":"karma-store"}}`)
}))
for _, p := range commercePrefixes {
app.All(p+"/*", commerce)
}
// The bare /v1/* AI catch-all, mounted LAST like the real Wire, gates every
// non-exempt /v1/* path on the caller's LLM prepaid balance → 402 for a
// commerce-funded-but-ai-$0 org. This is the exact gate that produced the outage.
app.Get("/v1/*", func(c *zip.Ctx) error {
return c.JSON(http.StatusPaymentRequired, map[string]any{
"error": map[string]string{"code": "insufficient_balance"},
})
})
// The store read must resolve on the commerce handler (200), never 402 at the AI gate.
code, body := doReq(t, app, http.MethodGet, "/v1/store/current")
if code != http.StatusOK {
t.Fatalf("GET /v1/store/current hit the AI balance gate (got %d, body %s) — /v1/store must be a commercePrefix so it reaches commerce, not the /v1/* catch-all", code, body)
}
// And a sibling store path (the listing upsert the publish edge writes) is owned too.
if code, _ := doReq(t, app, http.MethodPut, "/v1/store/karma-store/listing/valentina"); code == http.StatusPaymentRequired {
t.Fatalf("PUT /v1/store/:id/listing/:slug fell through to the AI balance gate (402) — the whole store surface must be commerce-owned")
}
// The platform-admin catalog CMS (admin.hanzo.ai's editor) must reach commerce —
// where each handler is requireSuperAdmin-gated (anon → 401/403) — never the AI
// /v1/* balance gate, which would 402 the editor's list/edit instead.
if code, _ := doReq(t, app, http.MethodGet, "/v1/catalog/entries"); code == http.StatusPaymentRequired {
t.Fatalf("GET /v1/catalog/entries fell through to the AI balance gate (402) — /v1/catalog must be a commercePrefix so the SuperAdmin CMS reaches commerce")
}
if code, _ := doReq(t, app, http.MethodPut, "/v1/catalog/entries/cloud-starter"); code == http.StatusPaymentRequired {
t.Fatalf("PUT /v1/catalog/entries/:slug fell through to the AI balance gate (402) — the whole catalog CMS must be commerce-owned")
}
// The platform-admin plan authority CMS (increment 3a) must also reach commerce —
// requireSuperAdmin-gated (anon → 401/403) — never the AI /v1/* 402 gate.
if code, _ := doReq(t, app, http.MethodGet, "/v1/plans/entries"); code == http.StatusPaymentRequired {
t.Fatalf("GET /v1/plans/entries fell through to the AI balance gate (402) — /v1/plans must be a commercePrefix so the plan authority CMS reaches commerce")
}
if code, _ := doReq(t, app, http.MethodPut, "/v1/plans/entries/pro"); code == http.StatusPaymentRequired {
t.Fatalf("PUT /v1/plans/entries/:slug fell through to the AI balance gate (402) — the whole plan authority CMS must be commerce-owned")
}
}
// doReq drives one request through the mounted app and returns (status, body).
func doReq(t *testing.T, app *zip.App, method, path string) (int, []byte) {
t.Helper()
resp, err := app.Fiber().Test(httptest.NewRequest(method, path, nil))
if err != nil {
t.Fatalf("Test %s %s: %v", method, path, err)
}
defer func() { _ = resp.Body.Close() }()
b, _ := io.ReadAll(resp.Body)
return resp.StatusCode, b
}
+35
View File
@@ -0,0 +1,35 @@
package apps
import (
"testing"
"github.com/hanzoai/cloud/clients/framework"
)
// TestFrameworkContentModulesLinked guards the framework CONTENT modules
// (cms/erp/help) against silent removal. cms/erp are pure fixture lanes reached
// ONLY via blank imports in apps.go; help is a real import + a Wire() spec (it also
// mounts the /v1/help public plane) but still contributes its DocTypes the SAME way,
// from a package init() (framework.RegisterModule). #248 dropped the blank imports,
// which stripped the erp ledger hooks from the binary with no mount change and no
// failing mount test. This asserts the engine's module registry carries each lane,
// so that money-adjacent regression cannot recur — for help, dropping the import
// would also drop its Wire() spec and fail TestWireOrderMatchesFrozen, but this keeps
// the fixture-linkage guard uniform across all three lanes.
func TestFrameworkContentModulesLinked(t *testing.T) {
got := make(map[string]bool)
for _, m := range framework.RegisteredModules() {
got[m] = true
}
for _, want := range []string{"cms", "erp", "help"} {
if !got[want] {
t.Errorf("framework content module %q not registered — a blank import in apps.go is missing (erp drop = ledger hooks gone from the binary)", want)
}
}
// The module registry proves DocTypes are linked, but erp's ledger-posting
// HOOKS register in a separate init() step; assert them directly so the guard
// survives a future split of registerHooks() out of erp's module init().
if framework.RegisteredHookCount() == 0 {
t.Error("no framework lifecycle hooks registered — erp's ledger-posting hooks (computeJournalTotals, journalEntry/paymentEntry submit+cancel, …) are not linked into the binary")
}
}
+81
View File
@@ -0,0 +1,81 @@
// Copyright © 2026 Hanzo AI. MIT License.
package apps
import (
"context"
"fmt"
"github.com/hanzoai/cloud/clients/finance"
"github.com/hanzoai/cloud/clients/money"
"github.com/hanzoai/cloud/types"
"github.com/hanzoai/commerce/billing/creditledger"
)
// ledger implements commerce's creditledger.CreditLedger over cloud's native
// finance ledger — the SAME per-org account (finance.Current()) the AI spend-gate
// reads and the edge meter debits. Injected at mountCommerce (EmbedConfig.Ledger),
// it makes commerce's POST /v1/billing/credit mint into the ONE ledger: a granted
// credit is immediately visible to the gate (one ledger, no split). This is the
// cloud half of the one-ledger seam — commerce defines the interface, cloud
// implements it once here, the compiler enforces the match.
//
// Fails closed when no finance ledger is co-resident; in the unified cloud binary
// finance is always published, so Get() != nil ⇒ credit routes here.
type ledger struct{}
// compile-time proof the adapter satisfies commerce's exported seam.
var _ creditledger.CreditLedger = ledger{}
// Credit posts a balanced deposit (funding:platform → wallet) to the org's POOL
// account (Subject == Org, the wallet the gate reads) and returns the ledger entry
// id + the org's new available balance in cents. Idempotent on IdempotencyKey:
// finance dedups on Ref, so the same key credits AT MOST once.
func (ledger) Credit(ctx context.Context, in creditledger.CreditInput) (string, int64, error) {
fin := finance.Current()
if fin == nil {
return "", 0, fmt.Errorf("commerce credit: no finance ledger co-resident")
}
cur := in.Currency
if cur == "" {
cur = "usd"
}
tag := in.Tag
if tag == "" {
tag = "grant:admin" // non-cash grant bucket (finance is a single wallet; Tags is a memo)
}
id, err := fin.Deposit(ctx, types.DepositInput{
Org: in.Org,
Subject: in.Org, // org-pool wallet == the account the AI gate reads
Amount: money.FromCents(in.AmountCents),
Currency: cur,
Notes: in.Reason,
Tags: tag,
Ref: in.IdempotencyKey,
})
if err != nil {
return "", 0, err
}
bal, berr := fin.Balance(ctx, in.Org, in.Org, cur, false)
if berr != nil {
return id, 0, berr
}
return id, bal.Cents(), nil
}
// Balance returns the org pool's available balance in cents for currency — the
// same read the AI gate performs, so GET /v1/billing/balance and the gate agree.
func (ledger) Balance(ctx context.Context, org, currency string) (int64, error) {
fin := finance.Current()
if fin == nil {
return 0, fmt.Errorf("commerce balance: no finance ledger co-resident")
}
if currency == "" {
currency = "usd"
}
bal, err := fin.Balance(ctx, org, org, currency, false)
if err != nil {
return 0, err
}
return bal.Cents(), nil
}
+122
View File
@@ -0,0 +1,122 @@
package apps
import (
"context"
"encoding/json"
"time"
"github.com/hanzoai/cloud/clients/ads"
"github.com/hanzoai/cloud/clients/automations"
"github.com/hanzoai/cloud/clients/campaign"
"github.com/hanzoai/cloud/clients/coding"
"github.com/hanzoai/cloud/clients/experiments"
"github.com/hanzoai/cloud/clients/framework"
"github.com/hanzoai/cloud/clients/git"
"github.com/hanzoai/cloud/clients/guide"
"github.com/hanzoai/cloud/clients/integrations"
"github.com/hanzoai/cloud/clients/principal"
)
// wire_seams.go wires cross-subsystem in-process seams that cannot be a MountSpec
// because they compose functions ACROSS packages that must not import each other.
//
// The coding orchestrator (clients/coding) needs git's CloneURL + VerifyRef, but
// clients/git imports clients/integrations (Slack-notify), and integrations calls
// coding — so coding -> git would cycle (integrations -> coding -> git ->
// integrations). The composition root is the ONE place that imports all three, so
// it assembles the coding Dispatcher here (git seams + agents/tracker/bot adapters)
// and injects it into the Slack trigger surface. init() runs once at load, before
// cloud.Serve; the git functions are plain reads that resolve their state at call
// time, so no mount ordering is required. The mirror-failure logger is nil (those
// failures are non-fatal and dropped).
func init() {
integrations.SetCodingDispatcher(coding.NewDispatcher(git.CloneURL, git.VerifyRef, nil))
// Guide growth-OBSERVE seam: the /v1/guide/profile observe layer reads the org's
// real platform truth through injected, org-scoped, honest-degrading probes.
// clients/guide imports NONE of these subsystems (decomplected), so the
// composition root — the ONE place that imports them all — binds the reads, the
// same injected-function pattern the coding dispatcher above uses. Each probe is
// PROVABLY org-scoped: framework.ModuleInstalled keys GetDocType on the org;
// integrations.Connected keys store.Get on the org and never surfaces the token.
// HasDeployment/RevenueCents/RecordCount are LEFT NIL: deploy is cluster/admin-
// scoped (not per-org) and commerce-revenue-of-record + the crm record count have
// no clean per-org in-process read yet — binding a read whose org-scoping we
// cannot guarantee would be the bug. Until a provably-org-scoped read lands their
// signals honest-degrade to not-present (the vocabulary is the contract; a nil
// seam can never be a spurious true).
guide.BindSignals(guide.Signals{
ModuleInstalled: framework.ModuleInstalled,
ConnectorPresent: integrations.Connected,
})
// Inbound-event seam: a verified provider webhook (or chat channel) in
// clients/integrations fires the automations engine's Deliver here — the ONE place
// that imports both, so integrations never has to import automations (which imports
// it, for credential custody). A primitive-typed adapter keeps the seam free of the
// automations types.
integrations.SetAutomationTrigger(func(ctx context.Context, org, source, name, dedupeKey string, depth int, payload map[string]any) (int, error) {
return automations.Deliver(ctx, org, automations.TriggerEvent{
Source: source, Name: name, DedupeKey: dedupeKey, Depth: depth, Payload: payload,
})
})
// GTM PAID channel: the /v1/campaign orchestrator fans out to executors that
// satisfy campaign.Channel; the composition root is the ONE place that imports
// both campaign and the ad plane, so it adapts ads' connector-consuming
// execution funcs (provider.go — each resolves the org's ad token through
// integrations.TokenFor and fails closed) onto the primitive-typed channel
// seam. campaign never imports ads and ads never imports campaign — the same
// injected-function decoupling the coding dispatcher above uses.
campaign.RegisterChannel(campaign.NewChannel(campaign.KindPaid,
func(ctx context.Context, org string, p campaign.Plan) (campaign.Ref, error) {
r, err := ads.LaunchPaid(ctx, org, ads.PaidPlan{
Platform: p.Platform, Account: p.Account, Name: p.Name,
Objective: p.Objective, BudgetCents: p.BudgetCents, ScheduleAt: p.ScheduleAt,
})
return campaign.Ref{Platform: r.Platform, Account: r.Account, ExternalID: r.ExternalID, Status: r.Status, Detail: r.Detail}, err
},
func(ctx context.Context, org string, ref campaign.Ref) (int64, error) {
return ads.PaidSpend(ctx, org, ads.PaidRef{Platform: ref.Platform, Account: ref.Account, ExternalID: ref.ExternalID})
},
func(ctx context.Context, org string, ref campaign.Ref) error {
return ads.PausePaid(ctx, org, ads.PaidRef{Platform: ref.Platform, Account: ref.Account, ExternalID: ref.ExternalID})
},
))
// GTM creative A/B composes the merged EXPERIMENT primitive (clients/experiments)
// — campaign never reinvents bucketing or measurement. Assign resolves the
// subject's variant (creative) from the experiment's flag; Analyze is pull-model
// (it reads the metric from analytics itself), returned as opaque JSON so
// campaign stays decoupled from the analysis type. Campaign-linked experiments
// live in the org's default project. Both are nil-safe upstream: an org that
// never created a "campaign:<id>" experiment runs a single creative (Assign
// errors → "" → Content[0]).
campaign.SetExperiment(
func(ctx context.Context, org, experimentID, subject string) (string, error) {
a, err := experiments.Assign(ctx, org, principal.DefaultProject, experimentID, subject, nil)
if err != nil {
return "", err
}
return a.Variant, nil
},
func(ctx context.Context, org, experimentID string, start, end time.Time) (json.RawMessage, error) {
an, err := experiments.Analyze(ctx, org, principal.DefaultProject, experimentID, start, end, 0.05)
if err != nil {
return nil, err
}
return json.Marshal(an)
},
)
// GTM ORGANIC + EMAIL channels wire HERE the same way once their executors land
// (designed follow-ons — the publish rename + marketing email-connector wiring):
//
// campaign.RegisterChannel(campaign.NewChannel(campaign.KindOrganic,
// publish.Syndicate, publish.NoSpend, publish.Unpublish)) // social connectors
// campaign.RegisterChannel(campaign.NewChannel(campaign.KindEmail,
// marketing.Broadcast, marketing.NoSpend, marketing.Halt)) // email connectors
//
// Until wired, those channels record "unavailable" on a fan-out (honest) and a
// campaign runs a single creative — never a fabricated launch or variant.
}
+173
View File
@@ -0,0 +1,173 @@
package apps
import "testing"
// frozen is the EXACT subsystem mount sequence of the PRE-refactor binary —
// name, OwnsHealth, and whether it has a Shutdown — one row per mounted spec, in
// mount order. It was captured empirically from the pre-refactor cloud binary by
// cmd/dumpregistry (a throwaway tool that blank-imported the old init()-registry
// and replayed the legacy MountAll bubble-sort: ascending order-int, ties broken by
// the non-stable sort over init-registration order). The "was order N" trailing
// comment records each spec's deleted order-int for provenance.
//
// This is the SOLE guardian of mount order now that the order-ints are gone:
// Wire() must reproduce this sequence byte-for-byte (the func pointers aside), so a
// reorder, drop, add, or flag change in the composition root fails HERE. Captured on
// origin/main @c504d2b: 68 specs from the live init()-registry, PLUS the two the
// wave-2 external bumps (ai v1.805.2, o11y v1.5.12) stopped self-registering — ai
// (@150 catch-all) and the hanzoai/o11y module wildcard (@70), which main currently
// DROPS and this PR restores. The module wildcard (order 70) is now folded in as the
// terminal sub-mount of the in-repo o11y read plane (order 69), so "o11y" is ONE spec.
var frozen = []struct {
name string
ownsHealth bool
hasShutdown bool
}{
{"pubsub", false, true}, // was order 5
{"kafka", false, true}, // was order 6
{"agentskills", false, false}, // was order 8
{"flags", true, true}, // was order 9; native engine: /v1/flags health + store shutdown
{"kms", true, false}, // was order 10
{"metrics", false, false}, // was order 40
{"ingress", false, true}, // was order 42
{"account", false, false}, // was order 48
{"iam", false, false}, // was order 50
{"base", true, true}, // was order 60; per-org embed added Shutdown (#298)
{"o11y", false, true}, // ONE observability subsystem (was co-owned orders 69+70): read plane + the hanzoai/o11y module wildcard folded in as MountO11y's terminal sub-mount. OwnsHealth=false keeps /v1/o11y/health the generic always-ok route the module co-entry used to trigger.
{"authz", false, false}, // was order 70
{"commerce", false, false}, // was order 100
{"licensing", false, false}, // was order 110
{"plan", true, false}, // was order 111; enable id normalized plans->plan (routes stay /v1/plans/*)
{"pricing", true, false}, // was order 112
{"storage", true, false}, // was order 118
{"provisioning", false, false}, // was order 120
{"billing", false, false}, // was order 121
{"rollingcap", false, false}, // rolling spend-cap gate (after billing); golden drifted — refrozen
{"account-bridge", false, false}, // was order 122
{"do", false, false}, // was order 123
{"platform", true, true}, // was order 124
{"projects", false, true}, // was order 125
{"dns", false, false}, // new: /v1/dns zone plane (after projects)
{"domain", false, false}, // new: Hanzo Domains registrar (/v1/domain), after dns
{"prompts", false, false}, // was order 126
{"agents", false, true}, // was order 127
{"link", false, true}, // new: unified AI login manager (/v1/links), after agents
{"wallets", false, true}, // was order 127
{"x402", false, true}, // new: x402 pay-per-use settlement (after wallets)
{"paas", true, false}, // was order 128
{"deploy", true, false}, // after paas (release seam), before functions
{"functions", false, false}, // was order 128
{"tracker", false, false}, // was order 129
{"templates", false, false}, // was order 129
{"blueprint", true, false}, // new: OSS-template compute-cost basis /v1/blueprint (after templates); owns health, embedded content → no Shutdown
{"framework", false, true}, // was order 129
{"knowledge", false, false}, // was order 130
{"help", false, false}, // new: Hanzo Support public plane /v1/help (after knowledge; framework lane with a companion subsystem, no store → no Shutdown)
{"content", false, true}, // new: marketing content loop (after knowledge)
{"catalogsync", false, true}, // new: reverse loop (product.created → render) after content
{"webhooks", false, true}, // new: platform-global /v1/webhooks registry + bus-driven dispatcher (after catalogsync); owns per-org stores + worker pool → Shutdown
{"ml", true, false}, // was order 130
{"usage", false, false}, // was order 131
{"leaderboard", false, true}, // new: gamified usage analytics (after usage), owns opt-in SQLite (Shutdown)
{"crm", false, false}, // was order 131
{"marketing", false, true}, // new: marketing domain fold (after crm)
{"ads", false, true}, // new: ads domain fold (after crm)
{"campaign", false, true}, // new: /v1/campaign GTM orchestration (after ads); fans out to channels
{"validators", false, true}, // new: NFT-gated node provisioning (after ads); golden refrozen
{"social", false, true}, // new: /v1/social fold (after crm)
{"analytics", true, false}, // was order 132
{"git", false, false}, // was order 132
{"sync", false, true}, // /v1/sync engine (owns per-org DB handles → Shutdown)
{"visor", false, false}, // was order 133
{"venue", false, false}, // new: /v1/cloud connect-a-cloud-account plane (after visor); folds discovered clusters into the fleet
{"captable", false, true}, // was order 133
{"code", false, true}, // was order 134
{"zero-trust", false, false}, // was order 134
{"share", false, false}, // ngrok-native public sharing (/v1/share/*)
{"dataroom", true, true}, // was order 134
{"graph", false, false}, // was order 135
{"security", true, true}, // was order 136
{"integrations", false, true}, // was order 137
{"destinations", false, true}, // new: /v1/destinations CDP fan-out (after integrations, before cloudflare)
{"cloudflare", false, false}, // new: /v1/cloudflare edge plane (after integrations)
{"sbom", true, false}, // was order 137
{"team", false, true}, // was order 138
{"settings", false, true}, // was order 138
{"prefs", false, true}, // new: per-user preference plane (after settings); Shutdown closes the store
{"notify", true, false}, // was order 139
{"channels", false, true}, // new: /v1/channels transport plane (after notify; must mount after integrations so RegisterIngress installs before webhooks emit)
{"gateway", false, false}, // was order 139
{"entitlements", false, true}, // was order 139
{"exec", false, false}, // was order 140
{"websearch", false, false}, // was order 141
{"world", false, true}, // was order 142
{"runtime", false, false}, // was order 143; was "bot" until the transport was named for what it is
{"authors", false, true}, // was order 143
{"bots", false, false}, // was order 143
{"audit", false, false}, // was order 144
{"affiliates", false, false}, // was order 144
{"sign", true, true}, // was order 145
{"product", false, false}, // was order 145
{"evals", false, false}, // was order 145
{"benchmark", false, false}, // benchmark plane (after evals, before treasury)
{"research", false, true}, // R&D evidence plane + /research board (HIP-0512), arena sibling after benchmark; Shutdown closes per-org stores
{"experiments", false, true}, // unified A/B EXPERIMENT primitive: composes flags(assign)+analytics(measure)+research(evidence); Shutdown closes the registry stores
{"books", false, true}, // AI bookkeeper (/v1/books, per-org SQLite); Shutdown closes org stores
{"treasury", false, true}, // was order 146
{"admin", false, false}, // was order 146
{"admission", false, true}, // launch-control gate: composes flags (registry+seed+mode route+Enforce); Shutdown closes the registry store
{"tasks", false, false}, // was order 147; platform cron folded in as a sub-mount of tasks.Mount (was a separate entry)
{"automations", false, true}, // was order 148; connectorruntime (POST /v1/automations/connectors/:id/run) folded in as a sub-mount of automations.Mount
{"tools", false, true}, // new: unified tool plane (after automations)
{"marketplace", false, true}, // new: marketplace over the tool plane (after tools)
{"referrals", false, false}, // was order 149
{"guide", false, true}, // new: Business AI Guide (after referrals, before ai)
{"company", false, true}, // new: Hanzo Company formation state machine (after guide)
{"compliance", true, true}, // new: Hanzo Compliance — KYC/KYB + accreditation + audit posture (after company)
{"legal", true, true}, // new: Hanzo Legal — template + generation engine + e-sign/filing (after compliance)
{"agent", false, false}, // new: /v1/agent tool-calling round (before zen/ai catch-all)
{"ask", false, false}, // new: unified grounded advisor /v1/ask (before zen/ai catch-all)
{"zen", false, false}, // zen* claim middleware before ai's catch-all (hip-00NN)
{"ai", false, false}, // was order 150
{"plugins", false, false}, // was order 900
}
// TestWireOrderMatchesFrozen proves the composition root's mount order is
// byte-identical to the legacy init()-registry's, position by position.
func TestWireOrderMatchesFrozen(t *testing.T) {
wire := Wire()
if len(wire) != len(frozen) {
t.Fatalf("Wire() has %d specs, frozen sequence has %d", len(wire), len(frozen))
}
for i, s := range wire {
w := frozen[i]
if s.Name != w.name {
t.Errorf("position %d: Wire() = %q, frozen = %q (mount ORDER changed)", i, s.Name, w.name)
}
if s.OwnsHealth != w.ownsHealth {
t.Errorf("position %d (%s): OwnsHealth = %v, frozen = %v", i, s.Name, s.OwnsHealth, w.ownsHealth)
}
if (s.Shutdown != nil) != w.hasShutdown {
t.Errorf("position %d (%s): hasShutdown = %v, frozen = %v", i, s.Name, s.Shutdown != nil, w.hasShutdown)
}
if s.Mount == nil {
t.Errorf("position %d (%s): Mount is nil", i, s.Name)
}
}
}
// TestWireNoDuplicateEnablement guards that every subsystem name is unique: a name
// maps 1:1 to an enable id, so a duplicate would mount two specs under one id. (The
// former o11y co-ownership was collapsed — the module wildcard is now a sub-mount of
// the in-repo o11y read plane — so there is no longer any exempt duplicate.)
func TestWireNoDuplicateEnablement(t *testing.T) {
seen := map[string]int{}
for _, s := range Wire() {
seen[s.Name]++
}
for name, n := range seen {
if n > 1 {
t.Errorf("subsystem %q wired %d times (each enable id must be unique)", name, n)
}
}
}
+304
View File
@@ -0,0 +1,304 @@
// Copyright 2026 Hanzo AI Inc. All Rights Reserved.
package apps
import (
"context"
"fmt"
"math/big"
"os"
"strings"
aicontrollers "github.com/hanzoai/ai/controllers"
aiobject "github.com/hanzoai/ai/object"
"github.com/hanzoai/cloud"
"github.com/hanzoai/cloud/clients/metering"
cloudmoney "github.com/hanzoai/cloud/clients/money"
"github.com/hanzoai/cloud/clients/principal"
hmoney "github.com/hanzoai/money"
"github.com/hanzoai/zen"
"github.com/zap-proto/zip"
)
// mountZen mounts zen co-resident in the unified cloud binary. zen is the ONE
// serving layer for the zen model family; it owns identity, routing, the 1M
// context ladder, vision, tools, and the Anthropic↔OpenAI codec. ai stays the
// auth+billing+discovery seam and the /v1/models authority; it no longer carries
// a parallel zen table or identity prompts. (See hip-00NN.)
//
// zen mounts as a MIDDLEWARE, not a route owner: Claim is scoped to /v1/* and
// routes every request whose model is a zen SKU to zen's pipeline in-process,
// calling c.Next() for everything else so ai's /v1/* catch-all serves non-zen
// models. ONE mount mechanism; the host owns the routes, zen owns the family.
//
// Billing. cloud's edge middleware (serve.go) runs IdentityMiddleware,
// AuditTrail, ScopeRateLimit, and BillingGate app-wide BEFORE MountAll, so a
// zen-claimed request is already authenticated, audited, and rate-limited at the
// edge. But the edge BillingGate prices bare /v1/messages, /v1/chat/completions,
// and /v1/embeddings at 0 (they are not under /v1/ai/ in selfMeteredPrefixes), and
// ai's OWN in-handler metering — which used to bill zen* — is SKIPPED because
// zen's Claim runs before ai's beego catch-all. zen therefore bills zen* itself,
// through the same commerce metering client the edge gate uses, so there is ONE
// billing source for zen* (never double-billed, never free): zen's Gate
// authorizes the estimate before the upstream call, zen's Meter records the
// exact served cost after. zen's Meter/Gate are wired here; ai's edge gate stays
// 0 for these paths.
//
// Billing granularity is org / project / user, mirroring the edge gate's
// identityFromCtx exactly:
// - the HOME org (principal.BillingOrg) is the balance key — who PAYS. An admin
// acting in another org bills the admin's home org, never the org acted on.
// - the project (principal.ValidatedProject) scopes spend caps; a project may
// carry its own billing account, resolved server-side by commerce from the
// org's project binding (the X-Billing-Account-Id header only attributes,
// never redirects spend). Empty is the org-wide default.
// - the user (c.User) is the actor for the audit trail.
//
// It is wired BEFORE ai in Wire() so Claim's c.Next() falls through to ai's
// catch-all. zen's catalog reads its upstream keys from KMS via the Key resolver.
func mountZen(a *zip.App, deps cloud.Deps) error {
z, err := zen.New(zen.Config{
Logger: deps.Logger,
Key: zenKeyResolver(deps.KMS),
Tenant: cloudTenantResolver,
Gate: commerceGate(deps.Metering),
Meter: commerceMeter(deps.Metering),
})
if err != nil {
return fmt.Errorf("zen: %w", err)
}
// The one mount: Claim scoped to /v1, ahead of ai's catch-all.
a.Group("/v1", z.Claim())
return nil
}
// cloudTenantResolver is the multi-tenant billing-identity resolver: it keys
// the balance on the validated HOME org (who pays), resolves the project scope
// from a validated claim, and attributes the user. It mirrors the edge gate's
// identityFromCtx so a zen* debit lands on the SAME ledger axes the edge gate
// would have used — home-org balance, project+service scope, user actor — and a
// masquerading admin bills their own home org, never the org acted on. A request
// with no validated principal resolves to an empty Tenant, which zen's Valid()
// gate refuses (no free, anonymous usage).
func cloudTenantResolver(c *zip.Ctx) zen.Tenant {
home, _ := principal.BillingOrg(c)
project, _ := principal.ValidatedProject(c)
return zen.Tenant{
Org: c.Org(),
User: c.User(),
BillingOrg: home,
Project: project,
}
}
// commerceGate is zen's pre-serve authorization backed by cloud commerce. It
// asks the metering client whether the home org can cover the request's
// estimated cost (priced at the tier that WILL serve, so an overflow is gated
// against its real cost). The balance key is the home org (User); the project
// scopes the spend cap. The estimate is exact 18-dp atto-USD from zen, folded to
// whole cents for the balance check (a sub-cent estimate gates as "any positive
// balance", the same contract as the edge gate's AmountCents). An unconfigured
// metering client (nil) admits everything — zen's own tenant gate still refuses
// anonymous traffic, and the edge BillingGate + ScopeRateLimit already ran. A
// denied verdict returns the metering reason so zen surfaces it as its 402.
func commerceGate(m *metering.Client) zen.Gate {
if m == nil || !m.Enabled() {
return nil
}
return func(ctx context.Context, t zen.Tenant, model string, est hmoney.Amount) error {
if t.BillingOrg == "" {
return fmt.Errorf("a billable tenant is required (no anonymous usage)")
}
// zen's estimate is an exact 18-dp USD value. Fold it to whole cents for
// the balance check via cloud's typed money.Amount.Cents() — a sub-cent
// estimate gates as 0 (any-positive-balance), matching the edge gate's
// AmountCents contract. The post-serve Meter debits the exact 18-dp.
//
// The fold is Cents() on the CREDIT amount, never Minor() on the zen one:
// Minor() renders money.USD's 2 decimals, so it returned cents that FromInt
// then read as atto — every estimate came back 0, and AuthorizeVerdict skips
// its `available >= AmountCents` check when AmountCents is 0, admitting a
// request of ANY size against any positive balance.
cents := credit(est).Cents()
v, err := m.AuthorizeVerdict(ctx, metering.AuthInput{
User: t.BillingOrg,
Org: t.BillingOrg,
AmountCents: cents,
Project: t.Project,
Service: zenService,
})
if err != nil {
// Balance unknown -> fail-closed (mirrors the edge gate's 503).
return fmt.Errorf("billing unavailable")
}
if !v.Allow {
if v.Reason == "spend_cap" {
return fmt.Errorf("spend cap reached for this scope")
}
return fmt.Errorf("insufficient balance")
}
return nil
}
}
// commerceMeter is zen's post-serve usage recorder backed by cloud commerce.
// It debits the home org for the EXACT served cost as a typed money.Amount
// (native 18-dp USD — the same precision the co-resident finance ledger holds),
// so an exact per-token cost is never floored to cents or micros. Attributed to
// the requested zen SKU with real token counts. The debit is detached (background
// context) so a client disconnect cannot cancel it and recording never blocks the
// reply — the same contract as the edge gate's post-request record. An
// unconfigured client is a no-op (zen's logMeter still ran as the default, so the
// audit trail is never empty).
func commerceMeter(m *metering.Client) zen.Meter {
if m == nil || !m.Enabled() {
return nil
}
return commerceMeterImpl{m}
}
type commerceMeterImpl struct{ m *metering.Client }
func (g commerceMeterImpl) Record(ctx context.Context, u zen.Usage) {
if u.Tenant.BillingOrg == "" {
return // never debit an unattributable request
}
// Beside the commerce debit, land the SAME warehouse row + gen_ai span every
// native ai path writes (TraceServedUsage = recordTrace WITHOUT recordUsage —
// the debit below is the one billing source, never doubled). zen knows its
// EXACT per-tier retail (Charge) and upstream COGS (Cost), so the row carries
// true margin (credit → nano). Without this, zen* traffic is
// warehouse/o11y-blind exactly where prod runs (the unified binary).
aicontrollers.TraceServedUsage(context.Background(), aicontrollers.ServedUsage{
Owner: u.Tenant.BillingOrg,
User: u.Tenant.User,
Model: u.Model,
Provider: zenProvider,
RequestID: u.RequestID,
Status: "success",
PromptTokens: u.PromptTokens,
CompletionTokens: u.CompletionTokens,
BilledNano: nano(credit(u.Charge)),
CostNano: nano(credit(u.Cost)),
})
// Detached: the request context is recycled once the handler returns, so a
// background context carries the debit to commerce without racing the reply.
usage := meterUsage(u)
go func() { _, _ = g.m.Record(context.Background(), usage) }()
// Enso learning ledger: the embedded zen mount serves the zen catalog in-process
// and never reaches ai's pipeToFamily, so ai's family-event writer never runs for
// zen traffic. Write the SAME RoutingEvent here (source="family") through the ONE
// shared writer, keyed on the client-visible response id (zen.Usage.ResponseID), so
// zen* calls land in the same ledger — stats, world, spark retrain, and /v1/feedback
// all read these rows. No prompt text; no shadow (zen.Usage carries no request
// text — that stays the auto/enso-proxy path's job). Fire-and-forget.
owner := u.Tenant.Org
if owner == "" {
owner = u.Tenant.BillingOrg
}
go aiobject.RecordFamilyRouting(aiobject.FamilyRoutingInput{
Owner: owner,
User: u.Tenant.User,
RequestedModel: u.Model,
RoutedModel: u.Upstream,
ResponseId: u.ResponseID,
PromptTokens: u.PromptTokens,
CompletionTokens: u.CompletionTokens,
CostCents: credit(u.Charge).Cents(),
RouterEndpoint: os.Getenv("ROUTER_ENDPOINT"),
})
}
// meterUsage projects a served zen.Usage onto the commerce debit. It is the ONE
// place the debit's amount is chosen, and it is pure — no ledger, no warehouse —
// so the money property is a unit test rather than an integration.
//
// The amount is the RETAIL Charge: what the caller pays. Cost is the upstream
// COGS we pay to serve the call; it is never the debit. It rides only the
// warehouse row (CostNano), where margin = Charge Cost stays exact. Debiting
// Cost would collect our own COGS and book zero margin on every zen call — and
// because the affiliate and OSS payout bases read this debit, it would fund
// their shares out of principal. This mirrors ai, whose debit is likewise the
// customer price (usageBilledCents), never its CostIn/CostOut COGS.
func meterUsage(u zen.Usage) metering.Usage {
return metering.Usage{
User: u.Tenant.BillingOrg,
Org: u.Tenant.BillingOrg,
Actor: u.Tenant.User,
Model: u.Model,
Provider: zenProvider,
Service: zenService,
Project: u.Tenant.Project,
PromptTokens: u.PromptTokens,
CompletionTokens: u.CompletionTokens,
TotalTokens: u.PromptTokens + u.CompletionTokens,
Amount: credit(u.Charge), // exact 18-dp USD, no floor
RequestID: u.RequestID,
Currency: "usd",
Status: "success",
}
}
// credit re-denominates a zen price into cloud's credit unit. It is the ONE
// conversion at this seam — every site below goes through it, so the unit is
// decided once rather than re-derived per call site.
//
// zen prices every SKU as an exact 18-dp value tagged money.USD (meter.go:
// money.New(<18-dp decimal>, money.USD)), and cloud's credit unit is the SAME USD
// value at 18-dp storage scale. So the conversion carries the exact decimal across
// and changes only the minor-unit convention: no rescale, no rounding, no factor.
// It is right by construction because the decimal is the value — the currency's
// Decimals is a rendering convention, not part of it.
//
// It must NEVER go through Amount.Minor(). money.USD declares 2 decimals, so
// Minor() rescales zen's 18-dp value to CENTS; feeding cents to the 18-dp
// FromInt understates the debit by 10^16 (a $17.376 charge debits $0.0000000000000017),
// and folds every sub-cent charge to a zero the ledger drops entirely.
func credit(a hmoney.Amount) cloudmoney.Amount { return cloudmoney.FromDecimal(a.Decimal()) }
// nano folds an exact credit Amount to nano-USD (1e-9) for the warehouse margin
// columns. It takes the typed Amount rather than a bare *big.Int so the unit is
// carried by the type: a cents integer is not a cloudmoney.Amount and can no
// longer be passed here. A single request's cost always fits int64 at nano.
func nano(a cloudmoney.Amount) int64 {
return new(big.Int).Div(a.Atto(), big.NewInt(1_000_000_000)).Int64()
}
// zenService is the commerce service axis zen* spend attributes to. zen serves
// the same LLM product ai does, so it shares ai's service label — a per-scope
// spend cap on "ai" binds both surfaces, and Observe reconciles them together.
const zenService = "ai"
// zenProvider is the metering provider label that marks a debit as zen-served
// (the LLM family zen owns) for internal cost reconciliation vs the raw upstream.
const zenProvider = "zen"
// zenKeyResolver is zen's upstream-credential resolver. zen's catalog names each
// provider's key by an env-var convention (DO_AI_API_KEY, ANTHROPIC_API_KEY, …);
// the resolver turns that name into a concrete secret. It reads the ENVIRONMENT
// FIRST, then falls back to KMS — the SAME order ai uses (object/kms.go: "the prod
// hot path resolves DO_AI_API_KEY from the env before any live KMS"). The operator
// injects these provider keys as env from the KMS-synced K8s secret
// (cloud-api-llm-keys), so the env is the live value; the embedded KMS store is a
// fallback that is not always seeded with the provider keys. Reading KMS-only made
// zen send an EMPTY key whenever the store lacked it, and the upstream (DO GenAI)
// answered 401 "Unable to authenticate you" — surfacing to the caller as a failed
// chat while ai (which reads env) worked. Env-first fixes that with one source of
// truth shared across both zen and ai. An empty result on both still returns "" so
// the upstream call fails fast (never silent free usage).
func zenKeyResolver(kms cloud.KMSClient) func(context.Context, string) string {
return func(ctx context.Context, envName string) string {
if v := strings.TrimSpace(os.Getenv(envName)); v != "" {
return v
}
if kms == nil {
return ""
}
b, err := kms.GetSecret(ctx, envName)
if err != nil || len(b) == 0 {
return ""
}
return string(b)
}
}
+64
View File
@@ -0,0 +1,64 @@
// Copyright 2026 Hanzo AI Inc. All Rights Reserved.
package apps
import (
"context"
"errors"
"testing"
)
// stubKMS is a KMSClient whose GetSecret returns a sealed value when present or a
// not-found error otherwise — mirroring the co-resident store that, in production,
// holds no upstream provider keys (they are provisioned as KMS-injected env).
type stubKMS struct{ sealed map[string]string }
func (s stubKMS) GetSecret(_ context.Context, ref string) ([]byte, error) {
if v, ok := s.sealed[ref]; ok {
return []byte(v), nil
}
return nil, errors.New("secret not found")
}
func (stubKMS) PutSecret(context.Context, string, []byte) error { return nil }
func (stubKMS) Sign(context.Context, string, []byte) ([]byte, error) { return nil, nil }
// TestZenKeyResolver_EnvFallback pins the production wiring: the upstream provider
// key is provisioned as env (from the cloud-api-llm-keys secret), NOT sealed in the
// co-resident KMS store, so a KMS miss must resolve to the env value rather than
// returning "" (which would send an empty bearer upstream → provider 401).
func TestZenKeyResolver_EnvFallback(t *testing.T) {
const env = "DO_AI_API_KEY"
t.Setenv(env, "env-provisioned-key")
// KMS store has no upstream keys (the real deployment state) — resolve from env.
if got := zenKeyResolver(stubKMS{})(context.Background(), env); got != "env-provisioned-key" {
t.Fatalf("KMS-miss: got %q, want env value", got)
}
// A nil KMS client (KMS disabled) — still resolve from env.
if got := zenKeyResolver(nil)(context.Background(), env); got != "env-provisioned-key" {
t.Fatalf("nil-KMS: got %q, want env value", got)
}
}
// TestZenKeyResolver_EnvTakesPrecedence pins the resolution ORDER: env is read
// FIRST, then KMS — the same order ai uses on the prod hot path. The operator
// injects provider keys as env from the KMS-synced secret, so the env is the live
// value; the co-resident store is the fallback. A key present in BOTH surfaces
// resolves to the env value.
func TestZenKeyResolver_EnvTakesPrecedence(t *testing.T) {
const env = "ANTHROPIC_API_KEY"
t.Setenv(env, "env-key")
got := zenKeyResolver(stubKMS{sealed: map[string]string{env: "sealed-key"}})(context.Background(), env)
if got != "env-key" {
t.Fatalf("got %q, want env-key (env precedence)", got)
}
}
// TestZenKeyResolver_AbsentEverywhere keeps the fail-fast contract: absent from both
// surfaces resolves to "" so zen refuses rather than serving for free.
func TestZenKeyResolver_AbsentEverywhere(t *testing.T) {
if got := zenKeyResolver(stubKMS{})(context.Background(), "MISSING_KEY_XYZ"); got != "" {
t.Fatalf("got %q, want empty", got)
}
}
+305
View File
@@ -0,0 +1,305 @@
// Copyright 2026 Hanzo AI Inc. All Rights Reserved.
package apps
import (
"context"
"io"
"net/http"
"net/http/httptest"
"strconv"
"sync/atomic"
"testing"
"github.com/hanzoai/cloud/clients/metering"
cloudmoney "github.com/hanzoai/cloud/clients/money"
"github.com/hanzoai/decimal"
hmoney "github.com/hanzoai/money"
"github.com/hanzoai/zen"
)
// usd builds an exact USD amount from a decimal string, the way zen prices a
// call (18-dp native, never through float).
//
// The decimal here must be hanzoai/decimal, the one hmoney.New takes and the one
// zen prices with — not shopspring's identically-named type. Money has exactly one
// decimal; a second one that merely LOOKS like it is how a price silently becomes
// a different number.
func usd(t *testing.T, s string) hmoney.Amount {
t.Helper()
d, err := decimal.Parse(s)
if err != nil {
t.Fatalf("parse %q: %v", s, err)
}
return hmoney.New(d, hmoney.USD)
}
// zen5Usage is one served call at zen5's live rates: 1M in + 1M out, priced at
// the family's 3× margin (retail = cost × margin).
//
// in : cost 1.392 → retail 4.176
// out: cost 4.40 → retail 13.20
func zen5Usage(t *testing.T) zen.Usage {
t.Helper()
return zen.Usage{
Tenant: zen.Tenant{BillingOrg: "acme", User: "acme/alice", Project: "p1"},
Model: "zen5",
PromptTokens: 1_000_000,
CompletionTokens: 1_000_000,
Charge: usd(t, "17.376"), // 4.176 + 13.20 — what the caller pays
Cost: usd(t, "5.792"), // 1.392 + 4.40 — what we pay upstream
RequestID: "req-1",
}
}
// dollars is the EXPECTED money, built from a plain dollar literal through cloud's
// OWN ParseUSD — deliberately a DIFFERENT constructor than the code under test uses.
//
// That is what pins the UNIT. These tests once asserted meterUsage(u).Amount.Int()
// against u.Charge.Minor(): both sides re-derived the number through the same
// conversion, so the assertion only proved an integer round-tripped and was blind
// to what the integer MEANT. It passed while every zen debit was 10^16 too small.
// Comparing money to a known dollar amount cannot be blind that way: if the debit
// is off by any factor, it is not $17.376 and the test fails.
func dollars(t *testing.T, s string) cloudmoney.Amount {
t.Helper()
a, err := cloudmoney.ParseUSD(s)
if err != nil {
t.Fatalf("parse %q: %v", s, err)
}
return a
}
// The debit is the RETAIL Charge — what the caller pays — never the upstream
// COGS. This is the money property: it fails if the Amount is built from
// u.Cost. The tier is margin-bearing (retail != cost), so the two values are
// distinguishable and the assertion cannot pass by coincidence.
func TestMeterUsageDebitsRetailNotCost(t *testing.T) {
u := zen5Usage(t)
if u.Charge.Cmp(u.Cost) == 0 {
t.Fatal("fixture is not margin-bearing: retail == cost, so the test could not tell them apart")
}
got := meterUsage(u).Amount
// The known dollar value the fixture charges — a $17.376 call debits $17.376.
if want := dollars(t, "17.376"); got.Cmp(want) != 0 {
t.Errorf("debit = $%s, want the retail Charge $%s", got, want)
}
if cogs := dollars(t, "5.792"); got.Cmp(cogs) == 0 {
t.Errorf("debit = $%s, which is the upstream COGS — the caller must be billed retail, not our cost", got)
}
}
// At the family's 3× margin the debit is exactly 3× the COGS: we collect the
// full retail price, not the wholesale one. Debiting Cost would collect 1/3 —
// our own COGS — and book zero margin.
func TestMeterUsageCollectsTheFullMargin(t *testing.T) {
u := zen5Usage(t)
debit := meterUsage(u).Amount
// 3x the COGS in the SAME unit as the debit — $5.792 + $5.792 + $5.792.
// Summing the credit Amount keeps the comparison in exact dollars; the old
// version multiplied Cost.Minor() (cents, 579 after rounding away 5.792's
// third decimal) and compared it to a debit that was not cents at all.
cogs := dollars(t, "5.792")
thriceCOGS := cogs.Add(cogs).Add(cogs)
if debit.Cmp(thriceCOGS) != 0 {
t.Errorf("debit = $%s, want 3x COGS = $%s (retail = cost x margin, margin 3.0)", debit, thriceCOGS)
}
if want := dollars(t, "17.376"); debit.Cmp(want) != 0 {
t.Errorf("debit = $%s, want $%s", debit, want)
}
}
// The debit carries zen's exact 18-dp value with no floor: a sub-cent call must
// not round to zero on the way to the ledger.
func TestMeterUsageKeepsExactSubCentCharge(t *testing.T) {
u := zen5Usage(t)
u.Charge = usd(t, "0.004176") // 1k input tokens at 4.176/MTok — well under a cent
u.Cost = usd(t, "0.001392")
got := meterUsage(u).Amount
if want := dollars(t, "0.004176"); got.Cmp(want) != 0 {
t.Errorf("debit = $%s, want the exact sub-cent charge $%s", got, want)
}
// metering.Record drops a zero Amount before it ever reaches the ledger
// (`if !c.Enabled() || amt.IsZero() ... return nil`), so a floored sub-cent
// charge is not a small debit — it is NO DEBIT ROW, and the call is free.
if got.IsZero() {
t.Error("sub-cent charge floored to zero — Record drops a zero Amount, so the call is served free with no debit row")
}
}
// The unit trap this seam shipped with, pinned so it cannot come back. zen prices
// an exact 18-dp value but tags it money.USD, whose Currency declares 2 decimals —
// so Charge.Minor() renders CENTS, while cloudmoney.FromInt reads its argument as
// 18-dp. Composing them silently divides every debit by 10^16.
//
// The tests above already fail if credit() regresses to that composition; this one
// names WHY, and proves the two conversions are still distinguishable — an
// assertion that cannot tell right from wrong is worse than no assertion.
func TestCreditIsNotTheMinorUnit(t *testing.T) {
charge := usd(t, "17.376")
if got, want := credit(charge), dollars(t, "17.376"); got.Cmp(want) != 0 {
t.Fatalf("credit($17.376) = $%s, want $%s", got, want)
}
// The conversion that shipped, spelled out.
old := cloudmoney.FromAtto(charge.Minor())
if old.Cmp(credit(charge)) == 0 {
t.Fatal("FromInt(Minor()) agrees with credit() — the fixture can no longer tell the units apart, so these tests prove nothing")
}
if old.Cents() != 0 {
t.Errorf("FromInt(Minor()).Cents() = %d, want 0 — that this was ALWAYS 0 is what made the spend gate admit every request", old.Cents())
}
}
// The identity fields ride with the debit unchanged: the debit lands on the org
// that PAYS (BillingOrg), scoped to its project, with the actor for the audit
// trail.
func TestMeterUsageAttribution(t *testing.T) {
u := zen5Usage(t)
m := meterUsage(u)
for _, c := range []struct{ name, got, want string }{
{"User", m.User, "acme"},
{"Org", m.Org, "acme"},
{"Actor", m.Actor, "acme/alice"},
{"Project", m.Project, "p1"},
{"Model", m.Model, "zen5"},
{"Provider", m.Provider, zenProvider},
{"Service", m.Service, zenService},
{"Currency", m.Currency, "usd"},
} {
if c.got != c.want {
t.Errorf("%s = %q, want %q", c.name, c.got, c.want)
}
}
if m.TotalTokens != 2_000_000 {
t.Errorf("TotalTokens = %d, want 2000000", m.TotalTokens)
}
}
// The spend gate must REFUSE a request whose estimate exceeds the balance.
//
// This is the sharpest edge of the unit bug and the reason it is a security
// finding, not only a revenue one. AuthorizeVerdict gates size like this:
//
// funded := available > 0
// if in.AmountCents > 0 { funded = available >= in.AmountCents }
//
// The estimate reached it as FromInt(est.Minor()).Cents(), which is ALWAYS 0 —
// so the size branch was DEAD and every request rode `available > 0`. Any org
// with a single cent of balance could draw an unbounded call. The debits were
// dust too, so the balance never fell and the cap could never trip.
func TestCommerceGateRefusesAnOverCapRequest(t *testing.T) {
const availableCents = 500 // the org holds $5.00
var authorized atomic.Bool
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
switch r.URL.Path {
case "/v1/billing/balance":
_, _ = io.WriteString(w, `{"available":`+strconv.Itoa(availableCents)+`}`)
case "/v1/billing/spend-alerts/authorize":
authorized.Store(true)
_, _ = io.WriteString(w, `{"allow":true}`)
default:
_, _ = io.WriteString(w, `[]`)
}
}))
defer srv.Close()
m, err := metering.New(metering.Config{BaseURL: srv.URL, Token: "t", Org: "acme"})
if err != nil {
t.Fatal(err)
}
gate := commerceGate(m)
if gate == nil {
t.Fatal("gate is nil — the client must be enabled for this proof to mean anything")
}
tenant := zen.Tenant{BillingOrg: "acme", User: "acme/alice", Project: "p1"}
// $17.376 against a $5.00 balance: over cap, must be refused.
if err := gate(context.Background(), tenant, "zen5", usd(t, "17.376")); err == nil {
t.Error("gate ADMITTED a $17.376 request against a $5.00 balance — the estimate is reaching AuthorizeVerdict as 0 cents, so the size check never runs")
}
// The same balance must still admit a request it can actually cover, or the
// test would pass by refusing everything.
if err := gate(context.Background(), tenant, "zen5", usd(t, "1.00")); err != nil {
t.Errorf("gate refused an affordable $1.00 request against a $5.00 balance: %v", err)
}
if !authorized.Load() {
t.Error("the affordable request never reached the spend-cap authorize step")
}
}
// The estimate must reach the balance check as the RIGHT number of cents. The
// refusal test above proves the gate says no; this proves it says no for the
// right reason — that $17.376 is folded to 1738 cents, not to 0.
func TestCommerceGateFoldsTheEstimateToRealCents(t *testing.T) {
for _, c := range []struct {
charge string
want int64
}{
{"17.376", 1738}, // rounds half-away-from-zero at the cent
{"1000.00", 100000},
{"1.00", 100},
{"0.004176", 0}, // sub-cent gates as "any positive balance"
} {
if got := credit(usd(t, c.charge)).Cents(); got != c.want {
t.Errorf("$%s folds to %d cents, want %d", c.charge, got, c.want)
}
}
}
// A zero-value zen price must convert and fold without panicking. zen leaves
// Charge/Cost as the zero Amount for a free SKU, and that value carries the
// EMPTY currency code, not "USD" — so this also pins that credit() reads the
// decimal rather than dispatching on the currency. The old attoToNano guarded a
// nil *big.Int here; nano() needs no guard because decimal.Coef() returns a real
// zero big.Int, never nil, but the property is worth holding.
func TestCreditAndNanoHandleTheZeroPrice(t *testing.T) {
var free hmoney.Amount // zero value: no currency, no coefficient
got := credit(free)
if !got.IsZero() {
t.Errorf("credit(zero) = $%s, want $0", got)
}
if n := nano(got); n != 0 {
t.Errorf("nano(credit(zero)) = %d, want 0", n)
}
if c := got.Cents(); c != 0 {
t.Errorf("credit(zero).Cents() = %d, want 0", c)
}
// And a free call books no debit row, which is correct — nothing is owed.
u := zen5Usage(t)
u.Charge, u.Cost = free, free
if amt := meterUsage(u).Amount; !amt.IsZero() {
t.Errorf("free call debits $%s, want $0", amt)
}
}
// nano carries real money to the warehouse margin columns. It is the last place
// the unit could silently collapse: attoToNano(cents) divided a cents integer by
// 1e9 and produced 0 for every charge under $10,000,000.
func TestNanoFoldsCreditToRealNano(t *testing.T) {
for _, c := range []struct {
charge string
want int64
}{
{"17.376", 17_376_000_000},
{"5.792", 5_792_000_000},
{"0.004176", 4_176_000},
{"1000.00", 1_000_000_000_000},
} {
if got := nano(credit(usd(t, c.charge))); got != c.want {
t.Errorf("nano($%s) = %d, want %d", c.charge, got, c.want)
}
}
}
+623
View File
@@ -0,0 +1,623 @@
package audit
// Tests for the tamper-evident audit chain. They exercise the REAL SQLite store
// (an on-disk temp db, not a mock) so the append-only write path, the hash-chain
// math, the verifier, redaction, and the filtered query are all proven
// end-to-end. The headline test is tamper-detection: a record edited directly in
// the database is DETECTED as breaking the chain.
import (
"context"
"database/sql"
"encoding/json"
"path/filepath"
"strings"
"sync"
"testing"
"time"
)
// openTemp opens a Recorder backed by a fresh on-disk SQLite file (not :memory:,
// because tamper tests re-open the same file via a second connection to edit it
// out-of-band — exactly what an attacker with DB access would do).
func openTemp(t *testing.T) (*Recorder, string) {
t.Helper()
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := Open(path, nil)
if err != nil {
t.Fatalf("Open: %v", err)
}
t.Cleanup(func() { _ = rec.Close() })
return rec, path
}
// sampleRecord is a representative security event (a SuperAdmin org deletion).
func sampleRecord(action string) Record {
return Record{
Time: time.Date(2026, 7, 1, 12, 0, 0, 0, time.UTC),
Actor: Actor{Org: "admin", Sub: "z@hanzo.ai", Email: "z@hanzo.ai"},
Action: action,
Resource: Resource{Type: "org", ID: "acme"},
Auth: AuthContext{Method: "jwt", IsAdmin: true},
Outcome: Outcome{Result: "success", Status: 200},
SourceIP: "203.0.113.7",
UserAgent: "console",
RequestID: "req-123",
Method: "DELETE",
Path: "/v1/admin/orgs/acme",
}
}
// TestChain_AppendSealsAndLinks proves each appended record gets a monotonic seq,
// links its PrevHash to the previous record's Hash, and starts from the genesis
// anchor.
func TestChain_AppendSealsAndLinks(t *testing.T) {
rec, _ := openTemp(t)
ctx := context.Background()
r0, err := rec.Append(ctx, sampleRecord("DELETE /v1/admin/orgs"))
if err != nil {
t.Fatalf("append 0: %v", err)
}
if r0.Seq != 0 {
t.Fatalf("first seq = %d, want 0", r0.Seq)
}
if r0.PrevHash != genesisPrevHash {
t.Fatalf("genesis prev = %q, want %q", r0.PrevHash, genesisPrevHash)
}
if r0.Hash == "" || r0.Hash == genesisPrevHash {
t.Fatalf("hash not computed: %q", r0.Hash)
}
r1, err := rec.Append(ctx, sampleRecord("POST /v1/admin/roles"))
if err != nil {
t.Fatalf("append 1: %v", err)
}
if r1.Seq != 1 {
t.Fatalf("second seq = %d, want 1", r1.Seq)
}
if r1.PrevHash != r0.Hash {
t.Fatalf("link broken: r1.prev=%q, r0.hash=%q", r1.PrevHash, r0.Hash)
}
if r1.Hash == r0.Hash {
t.Fatal("distinct records must have distinct hashes")
}
}
// TestVerify_PassesOnUntamperedChain proves a well-formed chain verifies OK.
func TestVerify_PassesOnUntamperedChain(t *testing.T) {
rec, _ := openTemp(t)
ctx := context.Background()
for i := 0; i < 25; i++ {
if _, err := rec.Append(ctx, sampleRecord("POST /v1/admin/sync")); err != nil {
t.Fatalf("append %d: %v", i, err)
}
}
integrity, err := rec.Verify(ctx)
if err != nil {
t.Fatalf("Verify: %v", err)
}
if !integrity.OK {
t.Fatalf("chain not OK: broken at %d (%s)", integrity.BrokenAt, integrity.Reason)
}
if integrity.Count != 25 {
t.Fatalf("count = %d, want 25", integrity.Count)
}
if integrity.BrokenAt != -1 {
t.Fatalf("brokenAt = %d, want -1 on a good chain", integrity.BrokenAt)
}
// Head must equal the last record's hash.
count, head := rec.Head()
if count != 25 || head != integrity.HeadHash {
t.Fatalf("head mismatch: (%d,%q) vs verify (%d,%q)", count, head, integrity.Count, integrity.HeadHash)
}
}
// TestVerify_DetectsFieldTamper is the headline: an attacker with direct DB
// access edits a record's content (flips a denied outcome to success, or changes
// the actor). The stored hash no longer matches the recomputed hash, so Verify
// reports the exact seq where the chain breaks. THIS is the tamper-evidence
// property — an audit trail that can be silently forged is worse than none.
func TestVerify_DetectsFieldTamper(t *testing.T) {
rec, path := openTemp(t)
ctx := context.Background()
for i := 0; i < 10; i++ {
if _, err := rec.Append(ctx, sampleRecord("DELETE /v1/admin/orgs")); err != nil {
t.Fatalf("append %d: %v", i, err)
}
}
// Sanity: clean chain verifies.
if iv, _ := rec.Verify(ctx); !iv.OK {
t.Fatalf("precondition: clean chain should verify, broke at %d", iv.BrokenAt)
}
// Tamper OUT OF BAND — a second connection issues an UPDATE the application
// never would. This models an attacker who owns the file / a rogue DBA.
tamperOutOfBand(t, path, `UPDATE audit_log SET actor_sub='attacker', result='success' WHERE seq=4`)
iv, err := rec.Verify(ctx)
if err != nil {
t.Fatalf("Verify after tamper: %v", err)
}
if iv.OK {
t.Fatal("TAMPER NOT DETECTED — a modified record verified as OK; the chain is forgeable")
}
if iv.BrokenAt != 4 {
t.Fatalf("brokenAt = %d, want 4 (the edited record)", iv.BrokenAt)
}
if !strings.Contains(iv.Reason, "hash mismatch") {
t.Fatalf("reason = %q, want a hash-mismatch explanation", iv.Reason)
}
}
// TestVerify_DetectsDeletion proves deleting a record (or a contiguous run) breaks
// the chain: the record after the hole has a PrevHash that no longer matches the
// now-preceding record, and the seq sequence gaps. Either way Verify flags it.
func TestVerify_DetectsDeletion(t *testing.T) {
rec, path := openTemp(t)
ctx := context.Background()
for i := 0; i < 10; i++ {
if _, err := rec.Append(ctx, sampleRecord("POST /v1/admin/roles")); err != nil {
t.Fatalf("append %d: %v", i, err)
}
}
// Delete a MIDDLE record — the classic "cover your tracks" edit.
tamperOutOfBand(t, path, `DELETE FROM audit_log WHERE seq=5`)
iv, err := rec.Verify(ctx)
if err != nil {
t.Fatalf("Verify after delete: %v", err)
}
if iv.OK {
t.Fatal("DELETION NOT DETECTED — a removed record left the chain verifying OK")
}
// The break is observed at seq 6 (the record whose predecessor vanished): its
// seq no longer follows the running counter (5 is missing), so the gap check
// fires first at 6.
if iv.BrokenAt != 6 {
t.Fatalf("brokenAt = %d, want 6 (record after the hole)", iv.BrokenAt)
}
}
// TestVerify_DetectsReorder proves swapping two records' positions (an attacker
// trying to reorder events) breaks the prev-hash linkage.
func TestVerify_DetectsReorder(t *testing.T) {
rec, path := openTemp(t)
ctx := context.Background()
for i := 0; i < 6; i++ {
if _, err := rec.Append(ctx, sampleRecord("POST /v1/kms/secrets")); err != nil {
t.Fatalf("append %d: %v", i, err)
}
}
// Swap the hashes of seq 2 and seq 3 (content stays, linkage corrupts). Any
// out-of-band shuffle that doesn't recompute the WHOLE suffix is detectable.
tamperOutOfBand(t, path, `
UPDATE audit_log SET hash = (SELECT hash FROM audit_log WHERE seq=3) WHERE seq=2;`)
iv, _ := rec.Verify(ctx)
if iv.OK {
t.Fatal("REORDER/HASH-SWAP NOT DETECTED")
}
if iv.BrokenAt < 0 {
t.Fatalf("expected a break, got brokenAt=%d", iv.BrokenAt)
}
}
// TestChain_RestartContinues proves a re-opened store continues the SAME chain
// (recovers seq + head) rather than forking — so a pod restart cannot silently
// reset the trail.
func TestChain_RestartContinues(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
ctx := context.Background()
rec1, err := Open(path, nil)
if err != nil {
t.Fatalf("open 1: %v", err)
}
var lastHash string
for i := 0; i < 5; i++ {
r, err := rec1.Append(ctx, sampleRecord("POST /v1/admin/sync"))
if err != nil {
t.Fatalf("append %d: %v", i, err)
}
lastHash = r.Hash
}
_ = rec1.Close()
rec2, err := Open(path, nil)
if err != nil {
t.Fatalf("open 2: %v", err)
}
defer func() { _ = rec2.Close() }()
count, head := rec2.Head()
if count != 5 {
t.Fatalf("recovered count = %d, want 5", count)
}
if head != lastHash {
t.Fatalf("recovered head = %q, want %q", head, lastHash)
}
// The next append must chain onto the recovered head at seq 5.
r5, err := rec2.Append(ctx, sampleRecord("DELETE /v1/admin/orgs"))
if err != nil {
t.Fatalf("append after restart: %v", err)
}
if r5.Seq != 5 || r5.PrevHash != lastHash {
t.Fatalf("chain did not continue: seq=%d prev=%q (want seq 5 prev %q)", r5.Seq, r5.PrevHash, lastHash)
}
// And the whole continued chain still verifies.
if iv, _ := rec2.Verify(ctx); !iv.OK {
t.Fatalf("continued chain broke at %d (%s)", iv.BrokenAt, iv.Reason)
}
}
// TestRedact_StripsSecrets proves the redactor removes credential-bearing fields
// (by key name, recursively) while keeping non-secret structure — so an explicit
// emit point's before/after can never carry a password/token/key.
func TestRedact_StripsSecrets(t *testing.T) {
in := json.RawMessage(`{
"name": "acme",
"password": "hunter2",
"apiKey": "sk-live-abc123",
"passphrase": "correct horse",
"wgPrivKey": "PRIVKEYBYTES",
"recoveryPhrase": "twelve words here",
"socialSecurityNumber": "078-05-1120",
"config": {
"clientSecret": "shh",
"endpoint": "https://api.example.com",
"nested": {"private_key": "-----BEGIN-----", "region": "sfo3"}
},
"tokens": ["t1", "t2"],
"roles": ["admin", "viewer"]
}`)
out := Redact(in)
s := string(out)
// Secrets gone (incl. the edge-case key names: passphrase, privkey, phrase, ssn).
for _, leak := range []string{"hunter2", "sk-live-abc123", "shh", "BEGIN",
"correct horse", "PRIVKEYBYTES", "twelve words here", "078-05-1120"} {
if strings.Contains(s, leak) {
t.Fatalf("secret leaked through redaction: %q still present in %s", leak, s)
}
}
// Non-secret structure preserved.
for _, keep := range []string{"acme", "https://api.example.com", "sfo3", "viewer"} {
if !strings.Contains(s, keep) {
t.Fatalf("redaction dropped a non-secret value %q: %s", keep, s)
}
}
// The redaction marker appears where secrets were.
if !strings.Contains(s, redactedMarker) {
t.Fatalf("no redaction marker in output: %s", s)
}
// "tokens" is a secret key → the whole array is redacted (not its elements).
var decoded map[string]any
if err := json.Unmarshal(out, &decoded); err != nil {
t.Fatalf("redacted output is not valid JSON: %v", err)
}
if decoded["tokens"] != redactedMarker {
t.Fatalf("secret-keyed array not redacted whole: %v", decoded["tokens"])
}
}
// TestRedact_FailsClosedOnBadJSON proves unparseable input is never echoed back.
func TestRedact_FailsClosedOnBadJSON(t *testing.T) {
out := Redact(json.RawMessage(`{not valid json, password=hunter2`))
if strings.Contains(string(out), "hunter2") {
t.Fatalf("bad JSON echoed a secret: %s", out)
}
if !strings.Contains(string(out), redactedMarker) {
t.Fatalf("bad JSON should redact to a marker, got %s", out)
}
}
// TestQuery_Filters proves the filtered read returns the right subset by actor,
// action, resource, and result, newest-first, with an accurate total.
func TestQuery_Filters(t *testing.T) {
rec, _ := openTemp(t)
ctx := context.Background()
mk := func(org, action, res, result string) Record {
r := sampleRecord(action)
r.Actor.Org = org
r.Resource.Type = res
r.Outcome.Result = result
return r
}
// A mixed set.
seed := []Record{
mk("admin", "DELETE /v1/admin/orgs", "org", "success"),
mk("acme", "POST /v1/base/records", "records", "success"),
mk("admin", "POST /v1/admin/roles", "roles", "deny"),
mk("admin", "DELETE /v1/admin/orgs", "org", "success"),
mk("acme", "POST /v1/kms/secrets", "secrets", "error"),
}
for i, r := range seed {
if _, err := rec.Append(ctx, r); err != nil {
t.Fatalf("seed %d: %v", i, err)
}
}
// Filter by org=admin → 3 rows.
rows, total, err := rec.Query(ctx, Filter{Org: "admin"})
if err != nil {
t.Fatalf("query org: %v", err)
}
if total != 3 || len(rows) != 3 {
t.Fatalf("org=admin: got %d rows, total %d, want 3/3", len(rows), total)
}
// Newest first: the last-appended admin row (seq 3) comes before seq 2, 0.
if rows[0].Seq < rows[len(rows)-1].Seq {
t.Fatalf("not newest-first: %d..%d", rows[0].Seq, rows[len(rows)-1].Seq)
}
// Filter by result=deny → 1 row (the 403-style role change).
denies, dtotal, err := rec.Query(ctx, Filter{Result: "deny"})
if err != nil {
t.Fatalf("query deny: %v", err)
}
if dtotal != 1 || len(denies) != 1 || denies[0].Action != "POST /v1/admin/roles" {
t.Fatalf("result=deny: got %d (%+v), want 1 role-change", dtotal, denies)
}
// Filter by resource=secrets → 1 row.
secs, stotal, err := rec.Query(ctx, Filter{Resource: "secrets"})
if err != nil {
t.Fatalf("query resource: %v", err)
}
if stotal != 1 || len(secs) != 1 {
t.Fatalf("resource=secrets: got %d, want 1", stotal)
}
}
// TestQuery_SQLInjectionInFilterIsInert proves a malicious filter value is a
// parameter, never SQL: it simply matches nothing and cannot drop the table.
func TestQuery_SQLInjectionInFilterIsInert(t *testing.T) {
rec, _ := openTemp(t)
ctx := context.Background()
for i := 0; i < 3; i++ {
if _, err := rec.Append(ctx, sampleRecord("POST /v1/admin/sync")); err != nil {
t.Fatalf("seed %d: %v", i, err)
}
}
inject := Filter{Org: "admin'; DROP TABLE audit_log;--"}
rows, total, err := rec.Query(ctx, inject)
if err != nil {
t.Fatalf("query should not error on injection attempt: %v", err)
}
if total != 0 || len(rows) != 0 {
t.Fatalf("injection value matched %d rows, want 0", total)
}
// The table survived — a normal query still returns the seeded rows.
if _, all, err := rec.Query(ctx, Filter{}); err != nil || all != 3 {
t.Fatalf("table damaged by injection attempt: all=%d err=%v", all, err)
}
}
// TestChain_ConcurrentAppendsStayGapless proves the serialized writer keeps the
// chain a true, gapless total order under CONCURRENT appends: many goroutines
// append at once, and the resulting chain must have every seq 0..N-1 exactly once
// AND verify. A race in the head/seq handoff would surface as a duplicate seq (a
// PRIMARY KEY error), a gap, or a broken link — all of which this catches.
func TestChain_ConcurrentAppendsStayGapless(t *testing.T) {
rec, _ := openTemp(t)
ctx := context.Background()
const goroutines, per = 16, 20
total := goroutines * per
errCh := make(chan error, total)
var wg sync.WaitGroup
for g := 0; g < goroutines; g++ {
wg.Add(1)
go func() {
defer wg.Done()
for i := 0; i < per; i++ {
if _, err := rec.Append(ctx, sampleRecord("POST /v1/admin/sync")); err != nil {
errCh <- err
}
}
}()
}
wg.Wait()
close(errCh)
for err := range errCh {
t.Fatalf("concurrent append failed (race in seq/head handoff?): %v", err)
}
// The chain must verify and contain exactly `total` gapless records.
iv, err := rec.Verify(ctx)
if err != nil {
t.Fatalf("verify: %v", err)
}
if !iv.OK {
t.Fatalf("concurrent chain broke at %d (%s)", iv.BrokenAt, iv.Reason)
}
if iv.Count != uint64(total) {
t.Fatalf("recorded %d records, want %d (a lost/duplicated append)", iv.Count, total)
}
}
// checkpointMirror is a Mirror that also captures checkpoints (implements
// CheckpointSink) so the test can assert the head digest reaches an independent
// sink.
type checkpointMirror struct {
mu sync.Mutex
cps []Checkpoint
}
func (m *checkpointMirror) Append(context.Context, Record) error { return nil }
func (m *checkpointMirror) Checkpoint(_ context.Context, cp Checkpoint) error {
m.mu.Lock()
defer m.mu.Unlock()
m.cps = append(m.cps, cp)
return nil
}
func (m *checkpointMirror) last() (Checkpoint, bool) {
m.mu.Lock()
defer m.mu.Unlock()
if len(m.cps) == 0 {
return Checkpoint{}, false
}
return m.cps[len(m.cps)-1], true
}
// TestCheckpoint_EmitsHeadDigest proves the AU-9 anchor: the periodic checkpoint
// emits the current (count, head) to the log function AND, when the mirror is a
// CheckpointSink, to the independent digest store — and a final checkpoint fires
// on Close. This is what an external monitor compares to detect tail-truncation.
func TestCheckpoint_EmitsHeadDigest(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
mirror := &checkpointMirror{}
rec, err := Open(path, mirror)
if err != nil {
t.Fatalf("open: %v", err)
}
ctx := context.Background()
var logged []Checkpoint
var lmu sync.Mutex
// every=0 → no ticker; we drive checkpoints via Close (final) + a manual tick.
rec.StartCheckpoints(0, func(cp Checkpoint) {
lmu.Lock()
logged = append(logged, cp)
lmu.Unlock()
})
for i := 0; i < 7; i++ {
if _, err := rec.Append(ctx, sampleRecord("POST /v1/admin/sync")); err != nil {
t.Fatalf("append %d: %v", i, err)
}
}
// Close emits the FINAL checkpoint (count=7, head=chain head).
if err := rec.Close(); err != nil {
t.Fatalf("close: %v", err)
}
lmu.Lock()
n := len(logged)
var lastLogged Checkpoint
if n > 0 {
lastLogged = logged[n-1]
}
lmu.Unlock()
if n == 0 {
t.Fatal("no checkpoint logged (Close should emit a final head digest)")
}
if lastLogged.Count != 7 {
t.Errorf("final checkpoint count = %d, want 7", lastLogged.Count)
}
if lastLogged.Head == "" || lastLogged.Head == genesisPrevHash {
t.Errorf("final checkpoint head not set: %q", lastLogged.Head)
}
// The independent sink also received the final digest.
if cp, ok := mirror.last(); !ok || cp.Count != 7 {
t.Errorf("checkpoint sink final = %+v (ok=%v), want count 7", cp, ok)
}
}
// TestCheckpoint_DoubleStartIsSafe proves a second StartCheckpoints call is
// ignored (no re-arm, no field/WaitGroup race) — the Red-review robustness fix.
// Run under -race to catch a regression.
func TestCheckpoint_DoubleStartIsSafe(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := Open(path, nil)
if err != nil {
t.Fatalf("open: %v", err)
}
rec.StartCheckpoints(time.Hour, func(Checkpoint) {})
rec.StartCheckpoints(time.Hour, func(Checkpoint) {}) // second call must be a no-op.
// Append + close must not race or hang.
if _, err := rec.Append(context.Background(), sampleRecord("POST /v1/admin/sync")); err != nil {
t.Fatalf("append: %v", err)
}
if err := rec.Close(); err != nil {
t.Fatalf("close: %v", err)
}
}
// TestCheckpoint_CloseSyncsToSink proves the FINAL checkpoint on Close reaches the
// independent sink SYNCHRONOUSLY (the Red-review durability fix) — the sink has
// the final count before Close returns, not on a detached goroutine that might
// not run before process exit.
func TestCheckpoint_CloseSyncsToSink(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
mirror := &checkpointMirror{}
rec, err := Open(path, mirror)
if err != nil {
t.Fatalf("open: %v", err)
}
rec.StartCheckpoints(0, func(Checkpoint) {}) // no ticker; only the on-close checkpoint.
for i := 0; i < 4; i++ {
if _, err := rec.Append(context.Background(), sampleRecord("POST /v1/admin/sync")); err != nil {
t.Fatalf("append %d: %v", i, err)
}
}
if err := rec.Close(); err != nil {
t.Fatalf("close: %v", err)
}
// Immediately after Close returns (no sleep), the sink MUST already have the
// final digest — proving the Close-path write was synchronous.
cp, ok := mirror.last()
if !ok || cp.Count != 4 {
t.Fatalf("sink final checkpoint = %+v (ok=%v), want count 4 synchronously on Close", cp, ok)
}
}
// TestCheckpoint_CountMonotonicDetectsTruncation demonstrates the DETECTION an
// external monitor performs: consecutive checkpoints have non-decreasing Count;
// after a tail truncation the head reported by Head() drops below a prior
// checkpoint — the signal the o11y alert fires on.
func TestCheckpoint_CountMonotonicDetectsTruncation(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := Open(path, nil)
if err != nil {
t.Fatalf("open: %v", err)
}
ctx := context.Background()
for i := 0; i < 10; i++ {
if _, err := rec.Append(ctx, sampleRecord("POST /v1/admin/sync")); err != nil {
t.Fatalf("append %d: %v", i, err)
}
}
before, _ := rec.Head() // the monitor's last pinned checkpoint count.
if before != 10 {
t.Fatalf("pre-truncation count = %d, want 10", before)
}
_ = rec.Close()
// Attacker truncates the tail (deletes the last 4 records) out of band.
tamperOutOfBand(t, path, `DELETE FROM audit_log WHERE seq >= 6`)
rec2, err := Open(path, nil)
if err != nil {
t.Fatalf("reopen: %v", err)
}
defer func() { _ = rec2.Close() }()
after, _ := rec2.Head()
// The internal chain still verifies (a truncated prefix is self-consistent)…
if iv, _ := rec2.Verify(ctx); !iv.OK {
t.Fatalf("truncated prefix should self-verify, broke at %d", iv.BrokenAt)
}
// …but the count REGRESSED vs the pinned checkpoint — the truncation signal.
if after >= before {
t.Fatalf("count did not regress after truncation: before=%d after=%d", before, after)
}
t.Logf("truncation detected by count regression: %d → %d (chain-internal verify is OK; external anchor catches it)", before, after)
}
// tamperOutOfBand opens the SAME sqlite file on a SEPARATE connection and runs a
// mutating statement the audit application itself never issues — modeling an
// attacker with direct database/file access. The Recorder's own connection is
// unaffected; Verify then re-reads and must catch the damage.
func tamperOutOfBand(t *testing.T, path, stmt string) {
t.Helper()
db, err := sql.Open("sqlite", path)
if err != nil {
t.Fatalf("tamper open: %v", err)
}
defer func() { _ = db.Close() }()
if _, err := db.Exec(stmt); err != nil {
t.Fatalf("tamper exec %q: %v", stmt, err)
}
}
+235
View File
@@ -0,0 +1,235 @@
package audit
// The read paths: filtered Query (for /v1/admin/audit) and Verify (the
// tamper-evidence walk for /v1/admin/audit/verify). Both are read-only — they
// issue SELECT only, never mutate — so exposing them can never weaken the
// append-only property.
import (
"context"
"encoding/json"
"fmt"
"strings"
"time"
)
// Filter narrows a Query. Zero-value fields are ignored (no constraint), so an
// empty Filter returns the most-recent Limit records. Time bounds are inclusive
// and compared against the RFC3339Nano ts column lexicographically (RFC3339 is
// order-preserving as text, so a string range is a correct time range).
type Filter struct {
Org string // actor_org exact match (tenant scope)
Sub string // actor_sub exact match (a specific user)
Action string // action exact match
Resource string // res_type exact match
ResourceID string // res_id exact match (a specific resource instance)
Result string // outcome result: success|deny|error
Since time.Time // ts >= Since (UTC)
Until time.Time // ts <= Until (UTC)
Limit int // max rows (default 100, cap 1000)
Offset int // pagination offset
}
// Query returns records matching f, newest first, and the total count matching
// the same predicate (ignoring Limit/Offset) for pagination. All predicates are
// parameterized — never string-interpolated — so a filter value can never inject
// SQL. Column names in the WHERE come from a fixed allowlist below, not caller
// input.
func (r *Recorder) Query(ctx context.Context, f Filter) (rows []Record, total int, err error) {
where, args := f.build()
limit := f.Limit
if limit <= 0 {
limit = 100
}
if limit > 1000 {
limit = 1000
}
offset := f.Offset
if offset < 0 {
offset = 0
}
countQ := `SELECT COUNT(*) FROM audit_log` + where
if err = r.db.QueryRowContext(ctx, countQ, args...).Scan(&total); err != nil {
return nil, 0, fmt.Errorf("audit: count: %w", err)
}
listQ := `SELECT ` + selectCols + ` FROM audit_log` + where +
` ORDER BY seq DESC LIMIT ? OFFSET ?`
listArgs := append(append([]any{}, args...), limit, offset)
rs, err := r.db.QueryContext(ctx, listQ, listArgs...)
if err != nil {
return nil, 0, fmt.Errorf("audit: query: %w", err)
}
defer func() { _ = rs.Close() }()
for rs.Next() {
rec, scanErr := scanRecord(rs)
if scanErr != nil {
return nil, 0, fmt.Errorf("audit: scan: %w", scanErr)
}
rows = append(rows, rec)
}
return rows, total, rs.Err()
}
// build assembles the parameterized WHERE clause from the non-zero filter
// fields. Each fragment uses a fixed column name and a ? placeholder, so no
// caller value ever reaches the SQL text.
func (f Filter) build() (string, []any) {
var conds []string
var args []any
add := func(frag string, val any) {
conds = append(conds, frag)
args = append(args, val)
}
if f.Org != "" {
add("actor_org = ?", f.Org)
}
if f.Sub != "" {
add("actor_sub = ?", f.Sub)
}
if f.Action != "" {
add("action = ?", f.Action)
}
if f.Resource != "" {
add("res_type = ?", f.Resource)
}
if f.ResourceID != "" {
add("res_id = ?", f.ResourceID)
}
if f.Result != "" {
add("result = ?", f.Result)
}
if !f.Since.IsZero() {
add("ts >= ?", f.Since.UTC().Format(time.RFC3339Nano))
}
if !f.Until.IsZero() {
add("ts <= ?", f.Until.UTC().Format(time.RFC3339Nano))
}
if len(conds) == 0 {
return "", nil
}
return " WHERE " + strings.Join(conds, " AND "), args
}
const selectCols = `seq, ts, actor_org, actor_sub, actor_email, action, res_type, res_id,
auth_method, is_admin, result, status, reason, source_ip, user_agent,
request_id, method, path, before, after, prev_hash, hash`
// scanRecord reconstructs a Record from a row of selectCols.
func scanRecord(sc interface{ Scan(...any) error }) (Record, error) {
var (
rec Record
ts string
isAdmin int
before, after string
)
if err := sc.Scan(
&rec.Seq, &ts, &rec.Actor.Org, &rec.Actor.Sub, &rec.Actor.Email,
&rec.Action, &rec.Resource.Type, &rec.Resource.ID,
&rec.Auth.Method, &isAdmin, &rec.Outcome.Result, &rec.Outcome.Status, &rec.Outcome.Reason,
&rec.SourceIP, &rec.UserAgent, &rec.RequestID, &rec.Method, &rec.Path,
&before, &after, &rec.PrevHash, &rec.Hash,
); err != nil {
return Record{}, err
}
if t, err := time.Parse(time.RFC3339Nano, ts); err == nil {
rec.Time = t
}
rec.Auth.IsAdmin = isAdmin != 0
if before != "" {
rec.Before = json.RawMessage(before)
}
if after != "" {
rec.After = json.RawMessage(after)
}
return rec, nil
}
// Integrity is the result of a Verify walk — the AU-9 evidence that the trail has
// not been tampered with.
type Integrity struct {
// OK is true iff every record's stored hash equals the recomputed hash AND the
// chain links are continuous (each PrevHash == the prior record's Hash, seqs
// gapless from 0).
OK bool `json:"ok"`
// Count is the number of records walked.
Count uint64 `json:"count"`
// HeadHash is the hash of the last record (or the genesis anchor for an empty
// chain). Pin this externally over time to detect tail-truncation.
HeadHash string `json:"headHash"`
// BrokenAt is the seq of the FIRST record that failed verification, or -1 when
// OK. Reason describes the break (recomputed-hash mismatch, prev-hash
// discontinuity, or a seq gap).
BrokenAt int64 `json:"brokenAt"`
Reason string `json:"reason,omitempty"`
}
// Verify walks the entire chain in seq order, recomputing each record's hash from
// its content + the running prev-hash and checking continuity. It is the
// tamper-detector: any modification (a changed field re-hashes differently), any
// deletion or reordering (a seq gap or a broken prev-hash link), or a forged row
// (its recomputed hash won't match unless the attacker also recomputed the entire
// suffix — which they cannot do without re-inserting every subsequent record) is
// reported with the exact seq where the chain first breaks.
//
// Complexity is O(n) over the records; for very large trails this streams row by
// row (no full materialization). At cloud's audit volume this is fine; if a trail
// grows past what an on-demand full walk should touch, verify a seq WINDOW
// (Verify is easily extended with a bound) or rely on the externally-pinned head.
func (r *Recorder) Verify(ctx context.Context) (Integrity, error) {
rs, err := r.db.QueryContext(ctx,
`SELECT `+selectCols+` FROM audit_log ORDER BY seq ASC`)
if err != nil {
return Integrity{}, fmt.Errorf("audit: verify query: %w", err)
}
defer func() { _ = rs.Close() }()
prevHash := genesisPrevHash
var expectSeq uint64
var count uint64
headHash := genesisPrevHash
for rs.Next() {
rec, scanErr := scanRecord(rs)
if scanErr != nil {
return Integrity{}, fmt.Errorf("audit: verify scan: %w", scanErr)
}
// Gapless, 0-based ordering.
if rec.Seq != expectSeq {
return Integrity{
OK: false, Count: count, HeadHash: headHash,
BrokenAt: int64(rec.Seq),
Reason: fmt.Sprintf("seq gap: expected %d, got %d", expectSeq, rec.Seq),
}, nil
}
// Link continuity: this record must chain to the previous record's hash.
if rec.PrevHash != prevHash {
return Integrity{
OK: false, Count: count, HeadHash: headHash,
BrokenAt: int64(rec.Seq),
Reason: "prev_hash discontinuity (a record was deleted, reordered, or altered)",
}, nil
}
// Content integrity: recompute the hash from the record's own fields.
want, hErr := computeHash(rec, rec.PrevHash)
if hErr != nil {
return Integrity{}, fmt.Errorf("audit: verify hash: %w", hErr)
}
if want != rec.Hash {
return Integrity{
OK: false, Count: count, HeadHash: headHash,
BrokenAt: int64(rec.Seq),
Reason: "hash mismatch (record content was modified after it was written)",
}, nil
}
prevHash = rec.Hash
headHash = rec.Hash
expectSeq = rec.Seq + 1
count++
}
if err := rs.Err(); err != nil {
return Integrity{}, fmt.Errorf("audit: verify rows: %w", err)
}
return Integrity{OK: true, Count: count, HeadHash: headHash, BrokenAt: -1}, nil
}
+176
View File
@@ -0,0 +1,176 @@
// Package audit is the unified cloud binary's compliance-grade audit trail —
// tamper-evident, append-only, and complete over the security-relevant request
// surface (FedRAMP AU-* / SOC 2 CC-* controls).
//
// THE CONTROL, IN ONE SENTENCE. Every security-relevant action against this
// binary is captured as a structured Record, hash-chained to its predecessor so
// any later deletion or modification is detectable, and written INLINE (never
// dropped) to an append-only store the application can only INSERT into.
//
// THREE PIECES, EACH IN ITS LANE (orthogonal, per the Zen of Hanzo):
// - record.go — the event model + the hash-chain math (what a record IS and
// how it links to the one before it). Pure, no I/O.
// - store.go — the append-only sink (SQLite primary, INSERT-only; a
// best-effort OLAP mirror) and the serialized Recorder that
// owns the chain head. All persistence.
// - redact.go — the secret-stripping allowlist/denylist for any structured
// before/after an explicit emit point supplies. No secret ever
// reaches a record.
//
// The HTTP middleware (Middleware, in the cloud package) and the query/verify
// endpoints (in clients/admin) are thin callers of this package. This package
// holds the security logic; it has zero knowledge of routes.
package audit
import (
"crypto/sha256"
"encoding/hex"
"encoding/json"
"time"
)
// Actor identifies WHO performed the action. It is populated ONLY from a
// validated principal (the sanitized X-User-* headers SanitizeIdentity mints
// from a verified IAM JWT), never from a raw client header — so an actor can
// never be forged by the request that is being audited. A service principal
// (M2M / no user sub) records Org with an empty Sub.
type Actor struct {
// Org is the tenant (IAM `owner`). Empty for an unauthenticated request.
Org string `json:"org"`
// Sub is the user id (IAM `sub`/`preferred_username`). Empty for a service
// principal or an anonymous request.
Sub string `json:"sub"`
// Email is the validated user email, when present.
Email string `json:"email,omitempty"`
}
// Resource identifies WHAT was acted upon: a type (e.g. "org", "role",
// "secret", "provider-config", "credit") and its id. For a plain HTTP mutation
// with no finer resource semantics, Type is the route family and ID is empty —
// the Action verb + path already pin the object.
type Resource struct {
Type string `json:"type"`
ID string `json:"id,omitempty"`
}
// AuthContext records HOW the actor authenticated and what authority they held
// at decision time — the AC-* evidence (was this a SuperAdmin? by what
// credential?). Method is "jwt" | "api-key" | "none". IsAdmin is the VALIDATED
// SuperAdmin bit (owner == AdminOrg), never a raw X-User-IsAdmin.
type AuthContext struct {
Method string `json:"method"`
IsAdmin bool `json:"isAdmin"`
}
// Outcome is the result of the action: whether it was allowed and what
// happened. Result is "success" | "deny" | "error". Status is the HTTP status.
// Reason is a short, non-sensitive explanation for a deny/error (e.g.
// "SuperAdmin required", "insufficient_balance") — never a secret, never a
// raw upstream error body.
type Outcome struct {
Result string `json:"result"`
Status int `json:"status"`
Reason string `json:"reason,omitempty"`
}
// Record is one audit event. The JSON tags ARE the on-disk and on-wire contract.
//
// Field order in the struct is deliberate but IRRELEVANT to the hash: the chain
// hashes the CANONICAL (sorted-key) JSON of the record with Hash/PrevHash zeroed
// (see canonicalBytes), so re-ordering fields or adding an omitempty field can
// never change an existing record's hash.
type Record struct {
// Seq is the strictly-increasing chain position (0-based). It is assigned by
// the Recorder under its lock, so it is a true total order with no gaps.
Seq uint64 `json:"seq"`
// Time is the UTC event timestamp (RFC3339Nano).
Time time.Time `json:"time"`
// Actor / Action / Resource / Auth / Outcome — the AU-3 "content of audit
// records" core: who, what, on what, how-authenticated, with what result.
Actor Actor `json:"actor"`
Action string `json:"action"`
Resource Resource `json:"resource"`
Auth AuthContext `json:"auth"`
Outcome Outcome `json:"outcome"`
// SourceIP + UserAgent — the AU-3 "source of the event" fields.
SourceIP string `json:"sourceIp,omitempty"`
UserAgent string `json:"userAgent,omitempty"`
// RequestID correlates the record to the request-line log and any downstream
// trace (the X-Request-Id the pipeline mints).
RequestID string `json:"requestId,omitempty"`
// Method + Path are the HTTP verb and route for a request-sourced event.
Method string `json:"method,omitempty"`
Path string `json:"path,omitempty"`
// Before / After capture a mutation's prior and resulting state for the
// AU-required "before/after" on config-affecting changes. They are populated
// ONLY by explicit emit points and ONLY after Redact has stripped secrets —
// the HTTP middleware never sets them (it never reads bodies), so a secret in
// a request body can never leak here. Raw JSON so any shape round-trips.
Before json.RawMessage `json:"before,omitempty"`
After json.RawMessage `json:"after,omitempty"`
// PrevHash is the hash of record Seq-1 (hex). For the genesis record (Seq 0)
// it is genesisPrevHash. Hash is this record's hash. Neither participates in
// its own hash computation (both are zeroed in canonicalBytes).
PrevHash string `json:"prevHash"`
Hash string `json:"hash"`
}
// genesisPrevHash is the PrevHash of the first record in a fresh chain: 32 zero
// bytes, hex-encoded. A non-empty, fixed anchor so the genesis record's hash is
// still a function of a known constant (not the empty string, which would be
// indistinguishable from "field omitted").
const genesisPrevHash = "0000000000000000000000000000000000000000000000000000000000000000"
// canonicalBytes returns the deterministic byte string a record hashes over: the
// record with Hash AND PrevHash zeroed, marshaled by encoding/json (which sorts
// struct fields in declaration order and, critically, is stable for a given
// struct — the SAME bytes on every machine and every run). Zeroing PrevHash here
// means the hash covers only the record's OWN content; the link to the previous
// record is added explicitly in computeHash by appending prevHash. This keeps
// the two concerns separable and the math obvious.
//
// We marshal a copy with the two hash fields cleared rather than a parallel
// struct so there is exactly ONE definition of a record's fields (DRY): add a
// field to Record and it is covered by the hash automatically.
func canonicalBytes(r Record) ([]byte, error) {
r.Hash = ""
r.PrevHash = ""
return json.Marshal(r)
}
// computeHash returns the hex SHA-256 of (canonical(record) || prevHash-bytes).
// The prevHash is folded in as its RAW hex string bytes — the exact value stored
// in the record's PrevHash field — so the verifier reproduces it byte-for-byte
// from stored data alone. Any change to the record's content OR to which record
// precedes it changes this output, which is the whole tamper-evidence property.
func computeHash(r Record, prevHash string) (string, error) {
body, err := canonicalBytes(r)
if err != nil {
return "", err
}
h := sha256.New()
h.Write(body)
h.Write([]byte(prevHash))
return hex.EncodeToString(h.Sum(nil)), nil
}
// seal finalizes a record into position seq linked to prevHash: it stamps Seq
// and PrevHash, computes Hash, and returns the sealed record ready to append.
// The Recorder calls this under its lock so seq/prevHash reflect the true head.
func seal(r Record, seq uint64, prevHash string) (Record, error) {
r.Seq = seq
r.PrevHash = prevHash
hash, err := computeHash(r, prevHash)
if err != nil {
return Record{}, err
}
r.Hash = hash
return r, nil
}
+140
View File
@@ -0,0 +1,140 @@
package audit
// Secret redaction for the before/after captured on a mutation.
//
// THE RULE. An audit record must NEVER contain a credential — no password,
// token, API key, private key, card number, or session secret. Two layers
// enforce this:
//
// 1. The HTTP middleware captures METADATA ONLY (actor/action/resource/outcome).
// It NEVER reads a request or response body, so a secret in a POST body can
// never reach a record through the automatic path. This is the primary
// guarantee: the code that can't see a secret can't leak one.
//
// 2. An EXPLICIT emit point that supplies structured before/after (e.g. a config
// change diff) runs it through Redact first. Redact walks the JSON and
// replaces the VALUE of any key whose name matches the secret denylist with a
// fixed marker, recursively. It is deny-by-key-name — the same allowlist
// PATTERN cloud already uses for user-secret redaction — chosen because a
// mutation diff has arbitrary shape and key-name matching is the robust,
// well-understood control (vs. trying to detect "secret-looking" values).
//
// Redact is conservative: on any structural surprise it returns the redaction
// marker rather than the input, so a parser edge case fails CLOSED (no raw
// passthrough).
import (
"encoding/json"
"strings"
)
// redactedMarker replaces every redacted value. A constant so tests and the
// query UI recognize it unambiguously.
const redactedMarker = "[REDACTED]"
// secretKeyParts are substrings that, when contained (case-insensitively) in a
// JSON object key, mark that key's value as secret. Kept as a small, auditable
// denylist of the credential-bearing field names that actually occur across the
// Hanzo surface (IAM, KMS, commerce, provider config). Matching is substring so
// "clientSecret", "api_key", "PRIVATE_KEY", "accessToken" all match.
var secretKeyParts = []string{
"password",
"passwd",
"secret",
"token",
"apikey",
"api_key",
"api-key",
"authorization",
"auth_token",
"private_key",
"privatekey",
"privkey", // privkey, wgPrivKey
"passphrase",
"client_secret",
"credential",
"session",
"cookie",
"card", // card_number, cardNumber
"cvv",
"cvc",
"pin",
"ssn",
"social_security", // socialSecurityNumber (lower-cased match covers camelCase)
"socialsecurity",
"otp",
"mnemonic",
"phrase", // seed_phrase, seedPhrase, recoveryPhrase
"access_key",
"secret_key",
"refresh_token",
"id_token",
"bearer",
"signing_key",
"encryption_key",
}
// isSecretKey reports whether a JSON key names a credential-bearing field.
func isSecretKey(key string) bool {
k := strings.ToLower(key)
for _, part := range secretKeyParts {
if strings.Contains(k, part) {
return true
}
}
return false
}
// Redact returns a copy of the JSON value with every secret-keyed value replaced
// by the redaction marker, recursively through objects and arrays. Non-JSON or
// empty input yields nil (nothing to record). On a JSON parse error the input is
// dropped (returns the marker as a JSON string) rather than passed through —
// fail closed.
//
// Use it at any explicit emit point that supplies before/after:
//
// audit.Emit(ctx, rec.WithChange(audit.Redact(before), audit.Redact(after)))
func Redact(raw json.RawMessage) json.RawMessage {
if len(raw) == 0 {
return nil
}
var v any
if err := json.Unmarshal(raw, &v); err != nil {
// Unparseable — never echo it back verbatim; record a marker instead.
b, _ := json.Marshal(redactedMarker)
return b
}
cleaned := redactValue("", v)
out, err := json.Marshal(cleaned)
if err != nil {
b, _ := json.Marshal(redactedMarker)
return b
}
return out
}
// redactValue walks a decoded JSON value. key is the object key under which v
// sits (empty at the root and for array elements); when key is a secret key, the
// ENTIRE value v is replaced (whether it is a scalar, object, or array — a secret
// nested object is redacted whole). Otherwise objects/arrays are recursed.
func redactValue(key string, v any) any {
if key != "" && isSecretKey(key) {
return redactedMarker
}
switch t := v.(type) {
case map[string]any:
out := make(map[string]any, len(t))
for k, val := range t {
out[k] = redactValue(k, val)
}
return out
case []any:
out := make([]any, len(t))
for i, val := range t {
out[i] = redactValue("", val) // array elements inherit no key
}
return out
default:
return v
}
}
+107
View File
@@ -0,0 +1,107 @@
package audit
// Shareability probe (HA carve evidence, NOT a shipped feature).
//
// Proves the audit SQLite store is SHAREABLE by a read-only second opener while
// the single writer is live-appending — the exact reader/writer split the HA
// carve needs. A reader opened with ?mode=ro:
// - never takes the write lock, so it cannot contend with or corrupt the
// writer's serialized appends (no chain-head fork: the reader never appends),
// - sees the writer's committed records via the shared WAL (concurrent reads),
// - and on "promotion" a fresh RW open recovers the head from disk == the
// writer's last synchronously-persisted record (no gap, no fork).
//
// This is the audit-store analog of clients/kms TestReaderReadOnlyRoundTrip
// (which proves the same for the KMS ZapDB store). Run:
// CGO_ENABLED=0 GOWORK=off GOFLAGS=-mod=mod go test ./audit/ -run Shareability -v
import (
"context"
"database/sql"
"sync"
"testing"
"time"
_ "github.com/hanzoai/sqlite"
)
func TestShareability_ReaderSharesLiveWriterStore(t *testing.T) {
dir := t.TempDir()
path := dir + "/audit.db"
// Writer: the real serialized Recorder (WAL, MaxOpenConns(1)).
w, err := Open(path, nil)
if err != nil {
t.Fatalf("writer Open: %v", err)
}
defer w.Close()
const total = 200
var wg sync.WaitGroup
wg.Add(1)
go func() {
defer wg.Done()
for i := 0; i < total; i++ {
if _, err := w.Append(context.Background(), Record{Action: "POST /v1/probe"}); err != nil {
t.Errorf("append %d: %v", i, err)
return
}
time.Sleep(200 * time.Microsecond)
}
}()
// Reader: a SECOND, independent connection opened READ-ONLY against the SAME
// files while the writer appends. This is what a reader-role pod does.
ro, err := sql.Open("sqlite", "file:"+path+"?mode=ro")
if err != nil {
t.Fatalf("reader Open(ro): %v", err)
}
defer ro.Close()
// Poll the reader's view of the head while the writer runs. It must (a) never
// error, (b) be monotonic, and (c) eventually observe the writer's records —
// concurrent cross-connection RO reads over a live WAL writer.
var lastSeen int64 = -1
deadline := time.Now().Add(5 * time.Second)
for time.Now().Before(deadline) {
var maxSeq sql.NullInt64
if err := ro.QueryRow(`SELECT MAX(seq) FROM audit_log`).Scan(&maxSeq); err != nil {
t.Fatalf("reader concurrent read failed (store NOT shareable): %v", err)
}
if maxSeq.Valid {
if maxSeq.Int64 < lastSeen {
t.Fatalf("reader head regressed %d -> %d (not monotonic)", lastSeen, maxSeq.Int64)
}
lastSeen = maxSeq.Int64
}
if lastSeen >= total-1 {
break
}
time.Sleep(2 * time.Millisecond)
}
wg.Wait()
if lastSeen < total-1 {
t.Fatalf("reader never caught up: saw head %d, writer wrote %d", lastSeen, total-1)
}
// Writer chain is intact and complete AFTER concurrent reader activity.
gotCount, _ := w.Head()
if gotCount != total {
t.Fatalf("writer head count = %d, want %d", gotCount, total)
}
// "Promotion": a fresh RW opener (the reader taking over) recovers the head
// from disk == the writer's last synchronously-persisted record. No fork.
promoted, err := Open(path, nil)
if err != nil {
t.Fatalf("promotion RW re-open: %v", err)
}
defer promoted.Close()
pc, _ := promoted.Head()
if pc != total {
t.Fatalf("promoted writer recovered head %d, want %d (chain gap/fork)", pc, total)
}
t.Logf("SHAREABLE: reader observed %d records concurrently; writer chain=%d; promotion recovered head=%d",
lastSeen+1, gotCount, pc)
}
+381
View File
@@ -0,0 +1,381 @@
package audit
// The append-only sink + the serialized Recorder that owns the hash-chain head.
//
// WHY SQLITE IS THE PRIMARY, DURABLE STORE (not datastore). The chain is only
// tamper-EVIDENT if records are appended in a strict, gapless total order and
// each record's PrevHash is the immediately-preceding record's Hash. That demands
// a single serializing writer with a synchronous, read-your-write head. cloud's
// canonical store is embedded SQLite (one store per the storagelock lockdown;
// pricing/provisioning already persist to {DataDir}/*.db). A local SQLite table
// the application can only INSERT into gives us: (a) a real total order under one
// connection, (b) synchronous durability so NO record is ever lost on the request
// path (unlike a fire-and-forget mirror), and (c) an append-only surface — the
// app issues no UPDATE/DELETE, and the hash-chain detects any out-of-band edit to
// the file. That is the compliance-grade primary control.
//
// THE DATASTORE MIRROR IS A PROJECTION, NOT THE SOURCE OF TRUTH. The datastore
// (datastore MergeTree — insert-only, mutation-rejected at parse time) is the
// fleet-wide OLAP mirror for long-retention, cross-deployment query. It is
// best-effort and asynchronous: a mirror outage must never block or fail an
// audited request, and the local chain remains the authority the verifier walks.
// Losing a mirror row is a query-completeness issue, not an integrity one.
//
// FAIL MODE. Append is INLINE and its error is RETURNED to the middleware, which
// fails the request CLOSED (a security-relevant action that cannot be recorded is
// not permitted to silently succeed). This is the AU-5 "response to audit logging
// process failure": deny rather than act-unlogged.
import (
"context"
"database/sql"
"errors"
"fmt"
"sync"
"time"
// github.com/hanzoai/sqlite is the ONE Hanzo SQLite driver: it registers
// the "sqlite" database/sql name under both build tags (cgo →
// mattn+SQLCipher, encrypted at rest; !cgo → pure-Go modernc). Importing
// modernc directly instead would double-register "sqlite" under CGO and
// panic at init. Blank import registers the driver.
"github.com/hanzoai/cloud/cek"
_ "github.com/hanzoai/sqlite"
)
// Mirror is the optional OLAP projection sink (the datastore/datastore). It is
// deliberately a tiny interface, not a concrete client, so the Recorder has no
// compile-time dependency on datastore and tests can supply a fake. Append is
// called best-effort, asynchronously, off the request path.
type Mirror interface {
// Append writes one sealed record to the projection. A returned error is
// logged and dropped by the Recorder — the mirror never gates a request.
Append(ctx context.Context, r Record) error
}
// Checkpoint is a periodic, tamper-EVIDENCE digest of the chain head: the record
// count and the head hash at a moment in time. It is the AU-9 anchor for
// TAIL-TRUNCATION detection — an internal chain walk cannot notice that the last
// K records were deleted (the surviving prefix still verifies), but a durable,
// INDEPENDENT series of head checkpoints can: Count is monotonic, so any decrease
// between two consecutive checkpoints is deletion, and an attacker cannot forge a
// higher count without appending records whose hashes the chain walk would reject.
type Checkpoint struct {
Time time.Time `json:"time"`
Count uint64 `json:"count"`
Head string `json:"head"`
}
// CheckpointSink is an optional capability a Mirror may implement to persist the
// head digest series to an INDEPENDENT store (so truncating the local SQLite
// cannot also rewrite the anchor history). A Mirror that does not implement it
// still gets its records; checkpoints then flow only to the structured log.
type CheckpointSink interface {
Checkpoint(ctx context.Context, cp Checkpoint) error
}
// Recorder is the single serialized writer that owns the audit chain head and
// the append-only store. Every Record flows through Append, which under one lock
// assigns the next Seq, links PrevHash to the current head, seals (hashes), and
// synchronously persists to SQLite before returning. Concurrency is serialized
// by mu AND by the single-connection SQLite pool, so the on-disk order equals
// the chain order with no gaps.
type Recorder struct {
db *sql.DB
mirror Mirror // nil when no OLAP mirror is configured.
mu sync.Mutex // guards nextSeq/headHash and serializes appends.
nextSeq uint64 // Seq to assign to the next record.
headHash string // Hash of the last-appended record (PrevHash for the next).
// Checkpoint emission (AU-9 tail-truncation anchor). logCheckpoint, when set,
// receives each head digest so it lands in the append-only observability log;
// stopCh/wg manage the periodic emitter goroutine's lifecycle; started guards
// against a second StartCheckpoints call (the field write + WaitGroup use are
// not safe to race). All three are set once, before any concurrent Append.
logCheckpoint func(cp Checkpoint)
stopCh chan struct{}
wg sync.WaitGroup
started bool
}
// CheckpointFunc receives a head digest for the structured (o11y) log. It is a
// plain func so the pure audit package stays free of any concrete logger type;
// the cloud wiring adapts luxlog to it.
type CheckpointFunc func(cp Checkpoint)
// Open opens (creating if needed) the append-only audit DB at path and recovers
// the chain head from it, so a restart continues the SAME chain rather than
// forking a new one. path may be ":memory:" for tests. mirror may be nil.
//
// the hanzoai/sqlite "sqlite" driver; MaxOpenConns(1) serializes every statement against
// the file lock — the same single-writer discipline pricing/provisioning use,
// here doubling as the chain's serialization guarantee.
func Open(path string, mirror Mirror) (*Recorder, error) {
db, err := cek.Open(path)
if err != nil {
return nil, fmt.Errorf("audit: open sqlite %q: %w", path, err)
}
db.SetMaxOpenConns(1)
for _, pragma := range []string{
"PRAGMA busy_timeout=5000",
"PRAGMA journal_mode=WAL",
"PRAGMA synchronous=NORMAL",
} {
if _, err := db.Exec(pragma); err != nil {
_ = db.Close()
return nil, fmt.Errorf("audit: pragma %q: %w", pragma, err)
}
}
r := &Recorder{db: db, mirror: mirror}
if err := r.migrate(); err != nil {
_ = db.Close()
return nil, err
}
if err := r.recoverHead(); err != nil {
_ = db.Close()
return nil, err
}
return r, nil
}
// migrate creates the append-only audit table. It is INSERT-only by application
// discipline: this package issues no UPDATE or DELETE against it, and seq is the
// PRIMARY KEY so a replayed/duplicated seq is rejected by the engine. The hash
// columns make any out-of-band row edit detectable by Verify regardless of the
// storage layer's own guarantees.
func (r *Recorder) migrate() error {
const ddl = `
CREATE TABLE IF NOT EXISTS audit_log (
seq INTEGER PRIMARY KEY, -- chain position; gapless, assigned under lock
ts TEXT NOT NULL, -- RFC3339Nano UTC event time
actor_org TEXT NOT NULL DEFAULT '',
actor_sub TEXT NOT NULL DEFAULT '',
actor_email TEXT NOT NULL DEFAULT '',
action TEXT NOT NULL,
res_type TEXT NOT NULL DEFAULT '',
res_id TEXT NOT NULL DEFAULT '',
auth_method TEXT NOT NULL DEFAULT '',
is_admin INTEGER NOT NULL DEFAULT 0,
result TEXT NOT NULL, -- success|deny|error
status INTEGER NOT NULL DEFAULT 0,
reason TEXT NOT NULL DEFAULT '',
source_ip TEXT NOT NULL DEFAULT '',
user_agent TEXT NOT NULL DEFAULT '',
request_id TEXT NOT NULL DEFAULT '',
method TEXT NOT NULL DEFAULT '',
path TEXT NOT NULL DEFAULT '',
before TEXT NOT NULL DEFAULT '', -- redacted JSON (explicit emit only)
after TEXT NOT NULL DEFAULT '', -- redacted JSON (explicit emit only)
prev_hash TEXT NOT NULL,
hash TEXT NOT NULL
);
-- Query indexes for the /v1/admin/audit filters (actor/action/resource/time).
CREATE INDEX IF NOT EXISTS ix_audit_org_seq ON audit_log(actor_org, seq);
CREATE INDEX IF NOT EXISTS ix_audit_action_seq ON audit_log(action, seq);
CREATE INDEX IF NOT EXISTS ix_audit_result_seq ON audit_log(result, seq);
CREATE INDEX IF NOT EXISTS ix_audit_ts ON audit_log(ts);
`
if _, err := r.db.Exec(ddl); err != nil {
return fmt.Errorf("audit: migrate: %w", err)
}
return nil
}
// recoverHead loads the highest-seq record so a restarted process continues the
// existing chain (nextSeq = maxSeq+1, headHash = its hash). An empty table starts
// the genesis chain (nextSeq 0, headHash = genesisPrevHash).
func (r *Recorder) recoverHead() error {
var (
maxSeq sql.NullInt64
hash sql.NullString
)
row := r.db.QueryRow(`SELECT seq, hash FROM audit_log WHERE seq = (SELECT MAX(seq) FROM audit_log)`)
if err := row.Scan(&maxSeq, &hash); err != nil {
if errors.Is(err, sql.ErrNoRows) {
r.nextSeq = 0
r.headHash = genesisPrevHash
return nil
}
return fmt.Errorf("audit: recover head: %w", err)
}
if !maxSeq.Valid { // empty table (MAX over zero rows is NULL)
r.nextSeq = 0
r.headHash = genesisPrevHash
return nil
}
r.nextSeq = uint64(maxSeq.Int64) + 1
r.headHash = hash.String
return nil
}
// Append seals r into the next chain position and persists it. It fills Seq,
// PrevHash, and Hash (the caller sets everything else), advances the in-memory
// head only AFTER the durable INSERT succeeds, and mirrors best-effort. A
// persistence error is returned so the caller can fail the request CLOSED — the
// head is NOT advanced on failure, so the chain never gaps.
//
// The whole critical section (assign seq → seal → INSERT → advance head) holds
// mu, so two concurrent requests can never claim the same seq or race the head.
func (r *Recorder) Append(ctx context.Context, rec Record) (Record, error) {
if rec.Time.IsZero() {
rec.Time = time.Now().UTC()
} else {
rec.Time = rec.Time.UTC()
}
r.mu.Lock()
defer r.mu.Unlock()
sealed, err := seal(rec, r.nextSeq, r.headHash)
if err != nil {
return Record{}, fmt.Errorf("audit: seal: %w", err)
}
if err := r.insert(ctx, sealed); err != nil {
// Head not advanced; the next append reuses this seq. Fail closed upstream.
return Record{}, fmt.Errorf("audit: persist: %w", err)
}
// Durable — advance the chain head.
r.nextSeq = sealed.Seq + 1
r.headHash = sealed.Hash
// Best-effort OLAP mirror, detached so a slow/failed mirror never blocks the
// request or corrupts the reply. The local chain is already durable and is the
// authority; a lost mirror row is a query-completeness gap, not an integrity
// one. Copy by value: the record is immutable and safe to hand to a goroutine.
if r.mirror != nil {
m, out := r.mirror, sealed
go func() { _ = m.Append(context.Background(), out) }()
}
return sealed, nil
}
// insert writes one sealed record. INSERT-only — the sole write statement in this
// package. A duplicate seq (PRIMARY KEY) fails here, which is the desired
// invariant: the chain never overwrites a position.
func (r *Recorder) insert(ctx context.Context, rec Record) error {
_, err := r.db.ExecContext(ctx, `
INSERT INTO audit_log (
seq, ts, actor_org, actor_sub, actor_email, action, res_type, res_id,
auth_method, is_admin, result, status, reason, source_ip, user_agent,
request_id, method, path, before, after, prev_hash, hash
) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)`,
rec.Seq, rec.Time.Format(time.RFC3339Nano),
rec.Actor.Org, rec.Actor.Sub, rec.Actor.Email,
rec.Action, rec.Resource.Type, rec.Resource.ID,
rec.Auth.Method, boolToInt(rec.Auth.IsAdmin),
rec.Outcome.Result, rec.Outcome.Status, rec.Outcome.Reason,
rec.SourceIP, rec.UserAgent, rec.RequestID, rec.Method, rec.Path,
string(rec.Before), string(rec.After), rec.PrevHash, rec.Hash,
)
return err
}
// checkpointCloseTimeout bounds the final (synchronous) checkpoint write to the
// independent sink at shutdown, so Close cannot hang on an unreachable datastore.
const checkpointCloseTimeout = 5 * time.Second
// Close stops the periodic checkpoint emitter, emits a FINAL checkpoint
// SYNCHRONOUSLY (so the head at shutdown reaches both the o11y log and the
// independent digest store before the process exits — the AU-9 anchor must be
// current exactly when an attacker might trigger shutdown then truncate), and
// closes the underlying database.
func (r *Recorder) Close() error {
if r == nil || r.db == nil {
return nil
}
if r.stopCh != nil {
close(r.stopCh)
r.wg.Wait()
r.stopCh = nil
}
// Anchor the final head before the DB closes — independent of whether the
// periodic ticker was running (every<=0 still gets a shutdown checkpoint).
// Synchronous to the sink (bounded), so the independent store's last count is
// as fresh as the local chain at the moment of shutdown.
r.emitCheckpoint(true)
return r.db.Close()
}
// StartCheckpoints begins periodic head-digest emission every `every` (no ticker
// if every<=0; the on-Close checkpoint still fires). logFn, when non-nil,
// receives each digest for the append-only observability log (o11y), and a mirror
// implementing CheckpointSink also gets it persisted to an INDEPENDENT store —
// together the AU-9 anchor an external monitor compares to detect tail-truncation
// (count regression). MUST be called at most once, before any concurrent Append
// (a second call is ignored); the emitter stops on Close.
func (r *Recorder) StartCheckpoints(every time.Duration, logFn CheckpointFunc) {
// Guard the check-and-set under mu so a (mis)use that calls this concurrently
// is race-free, not just the single-call production path.
r.mu.Lock()
if r.started {
r.mu.Unlock()
return // already started — do not re-arm (avoids a field/WaitGroup race).
}
r.started = true
r.logCheckpoint = logFn
r.mu.Unlock()
if every <= 0 {
return
}
r.stopCh = make(chan struct{})
stop := r.stopCh
r.wg.Add(1)
go func() {
defer r.wg.Done()
t := time.NewTicker(every)
defer t.Stop()
for {
select {
case <-stop:
return
case <-t.C:
r.emitCheckpoint(false)
}
}
}()
}
// emitCheckpoint snapshots the head and emits it to the log and (if the mirror is
// a CheckpointSink) the independent digest store. sync controls the sink write:
// on the periodic path (sync=false) it is detached so a slow sink never delays
// the ticker; on the Close path (sync=true) it BLOCKS on a bounded context so the
// final anchor is durable before shutdown. The log emission is always synchronous
// (it is the primary anchor and o11y ingests it append-only).
func (r *Recorder) emitCheckpoint(sync bool) {
count, head := r.Head()
cp := Checkpoint{Time: time.Now().UTC(), Count: count, Head: head}
if r.logCheckpoint != nil {
r.logCheckpoint(cp)
}
cs, ok := r.mirror.(CheckpointSink)
if !ok || cs == nil {
return
}
if sync {
ctx, cancel := context.WithTimeout(context.Background(), checkpointCloseTimeout)
defer cancel()
_ = cs.Checkpoint(ctx, cp)
return
}
go func() { _ = cs.Checkpoint(context.Background(), cp) }()
}
// Head returns the current chain head (count of records, and the head hash). A
// count of 0 means the genesis (empty) chain, headHash == genesisPrevHash. An
// external monitor can pin (count, headHash) over time to detect tail-truncation
// — which an internal chain walk alone cannot catch (a truncated prefix still
// verifies). This is the anchor point for AU-9 protection against deletion of the
// most-recent records.
func (r *Recorder) Head() (count uint64, headHash string) {
r.mu.Lock()
defer r.mu.Unlock()
return r.nextSeq, r.headHash
}
func boolToInt(b bool) int {
if b {
return 1
}
return 0
}
+60
View File
@@ -0,0 +1,60 @@
package audit
import "time"
// Wire is the JSON shape of one audit record on the operator/console contract. It
// is cloud's OWN record projection — richer than the IAM record it supersedes: it
// carries the outcome, the validated auth context, and the hash-chain linkage
// (Hash/PrevHash) so a console can show tamper-evidence per row. The JSON tags ARE
// the contract; both the admin god-view (/v1/admin/audit) and the org-scoped trail
// (/v1/audit) serialize this ONE shape so a single console adapter reads either.
type Wire struct {
Seq uint64 `json:"seq"`
Time string `json:"time"`
Org string `json:"org"`
Sub string `json:"sub"`
Email string `json:"email,omitempty"`
Action string `json:"action"`
Resource string `json:"resource"`
ResourceID string `json:"resourceId,omitempty"`
Method string `json:"method,omitempty"`
Path string `json:"path,omitempty"`
Result string `json:"result"`
Status int `json:"status"`
Reason string `json:"reason,omitempty"`
SourceIP string `json:"sourceIp,omitempty"`
UserAgent string `json:"userAgent,omitempty"`
RequestID string `json:"requestId,omitempty"`
IsAdmin bool `json:"isAdmin"`
Auth string `json:"authMethod,omitempty"`
Hash string `json:"hash"`
PrevHash string `json:"prevHash"`
}
// ToWire projects a stored Record onto the console wire shape. Time is emitted as
// RFC3339Nano (UTC) — the same nanosecond-precise, order-preserving format the ts
// column stores — so a client can sort/range on it verbatim.
func (r Record) ToWire() Wire {
return Wire{
Seq: r.Seq,
Time: r.Time.UTC().Format(time.RFC3339Nano),
Org: r.Actor.Org,
Sub: r.Actor.Sub,
Email: r.Actor.Email,
Action: r.Action,
Resource: r.Resource.Type,
ResourceID: r.Resource.ID,
Method: r.Method,
Path: r.Path,
Result: r.Outcome.Result,
Status: r.Outcome.Status,
Reason: r.Outcome.Reason,
SourceIP: r.SourceIP,
UserAgent: r.UserAgent,
RequestID: r.RequestID,
IsAdmin: r.Auth.IsAdmin,
Auth: r.Auth.Method,
Hash: r.Hash,
PrevHash: r.PrevHash,
}
}
+73
View File
@@ -0,0 +1,73 @@
package audit
import (
"context"
"testing"
"time"
)
func TestToWire_MapsEveryField(t *testing.T) {
r := Record{
Seq: 7,
Time: time.Date(2026, 7, 4, 12, 30, 0, 0, time.UTC),
Actor: Actor{Org: "maxpower", Sub: "dave", Email: "dave@maxpower.ai"},
Action: "machine.create",
Resource: Resource{Type: "machine", ID: "m-1"},
Auth: AuthContext{Method: "jwt", IsAdmin: true},
Outcome: Outcome{Result: "success", Status: 201, Reason: "ok"},
SourceIP: "1.2.3.4", UserAgent: "test-agent", RequestID: "req-1",
Method: "POST", Path: "/v1/machines",
PrevHash: "aa", Hash: "bb",
}
w := r.ToWire()
if w.Seq != 7 || w.Time != "2026-07-04T12:30:00Z" {
t.Fatalf("seq/time: %+v", w)
}
if w.Org != "maxpower" || w.Sub != "dave" || w.Email != "dave@maxpower.ai" {
t.Fatalf("actor: %+v", w)
}
if w.Action != "machine.create" || w.Resource != "machine" || w.ResourceID != "m-1" {
t.Fatalf("action/resource: %+v", w)
}
if w.Auth != "jwt" || !w.IsAdmin {
t.Fatalf("auth: %+v", w)
}
if w.Result != "success" || w.Status != 201 || w.Reason != "ok" {
t.Fatalf("outcome: %+v", w)
}
if w.Method != "POST" || w.Path != "/v1/machines" || w.SourceIP != "1.2.3.4" {
t.Fatalf("request: %+v", w)
}
if w.Hash != "bb" || w.PrevHash != "aa" {
t.Fatalf("chain: %+v", w)
}
}
func TestQuery_ResourceIDFilter(t *testing.T) {
rec, err := Open(":memory:", nil)
if err != nil {
t.Fatalf("Open: %v", err)
}
defer func() { _ = rec.Close() }()
ctx := context.Background()
for _, id := range []string{"m-1", "m-1", "m-2"} {
if _, err := rec.Append(ctx, Record{
Actor: Actor{Org: "o"}, Action: "machine.op",
Resource: Resource{Type: "machine", ID: id}, Outcome: Outcome{Result: "success"},
}); err != nil {
t.Fatalf("append: %v", err)
}
}
rows, total, err := rec.Query(ctx, Filter{ResourceID: "m-1"})
if err != nil {
t.Fatalf("Query: %v", err)
}
if total != 2 || len(rows) != 2 {
t.Fatalf("resourceId filter: want 2 rows on m-1, got %d rows total %d", len(rows), total)
}
for _, r := range rows {
if r.Resource.ID != "m-1" {
t.Fatalf("filter leaked %q", r.Resource.ID)
}
}
}
+677
View File
@@ -0,0 +1,677 @@
package cloud
// The audit middleware — the ONE place every security-relevant request is
// recorded to the tamper-evident trail (decomplected: one function, every route).
//
// PLACEMENT (why it sits exactly where serve.go puts it). The pipeline is
// Recover → RequestID → Logger → SanitizeIdentity → AuditTrail → BillingGate →
// subsystems. AuditTrail runs:
// - AFTER SanitizeIdentity, so the actor/isAdmin it records come from a
// VALIDATED IAM principal (the sanitized X-User-* headers), never a raw
// client header. The request being audited cannot forge its own actor.
// - BEFORE BillingGate and every subsystem, so it WRAPS the whole handler
// chain and observes the FINAL outcome — including a 402/503 billing denial
// and a 403 admin-guard denial (both security-relevant) — via the response
// status after Continue(), exactly like the Logger middleware reads it.
//
// WHAT IT CAPTURES: metadata only — actor, action (method+route family),
// resource, source ip, user agent, request id, auth context, and the outcome
// (result/status/reason). It NEVER reads the request or response BODY, so a
// secret in a POST body can never reach a record through this path. before/after
// diffs are the job of explicit emit points (audit.Recorder.Append with a
// redacted diff), not this middleware.
//
// WHAT IT RECORDS (the coverage predicate, auditable in one place — see
// isSecurityRelevant): every mutating request (POST/PUT/PATCH/DELETE), every
// /v1/admin/* request (read or write — admin reads are AC-relevant), and every
// auth-failure outcome (401/403) on ANY method (a denied GET is an access-control
// event). Safe, unauthenticated reads (a 200 GET on a public route) are NOT
// audited — that is request-log noise, not a security event, and auditing it
// would bury the signal and balloon the trail.
//
// FAIL MODE (AU-5): if the trail write fails on a request we decided to audit,
// the CLIENT gets a fail-closed 503 rather than a success it can rely on — the
// AU-5 "response to an audit logging process failure" is to interrupt, not to
// operate silently unlogged. A write to local SQLite is sub-millisecond, so this
// is a real integrity stance, not a latency tax. When no Recorder is configured
// the middleware is a no-op passthrough (an unconfigured deployment is never
// blocked), exactly like BillingGate.
//
// PRECISE SEMANTIC (do not over-read the 503). This is POST-RESPONSE audit: the
// handler has already run when the record is written, so a 503 here means "this
// event could not be RECORDED", NOT "the action did not execute". PREVENTION is
// the access-control layer's job and runs BEFORE the action — SanitizeIdentity
// (identity can't be forged) + the per-route admin guard both execute inside
// c.Next() ahead of any side effect. The audit trail's job is DETECTION and
// ACCOUNTABILITY (tamper-evident record of what happened), which it does. On a
// persistent audit-store outage every mutation returns 503 (loud, logged), so
// the system degrades to read-only rather than mutating unaudited — the intended
// compliance posture.
//
// PANIC BOUND. If a handler PANICS, the outermost middleware.Recover catches it
// and renders 500 with a full stack trace (loud, never silent); the panic unwinds
// PAST this middleware's post-c.Next() code, so a panicking request is not written
// to the trail. This is an accepted bound, not an evasion: an attacker cannot turn
// a panic into a SUCCESSFUL-but-unaudited mutation (a panic yields 500, not a
// completed action), and every panic is already captured by Recover's logging.
// Normal outcomes — including billing 402/503 and admin 403 denials, which return
// through c.Next() rather than panicking — are always audited.
import (
"errors"
"net/url"
"strings"
"github.com/hanzoai/cloud/audit"
"github.com/hanzoai/cloud/clients/principal"
"github.com/zap-proto/zip"
)
// AuditTrail returns the audit middleware bound to rec. A nil rec makes it a
// no-op passthrough so callers always Use() it unconditionally.
func AuditTrail(rec *audit.Recorder) zip.Handler {
if rec == nil {
return func(c *zip.Ctx) error { return c.Next() }
}
return func(c *zip.Ctx) error {
// Capture the pre-decision inputs BEFORE running the chain: the request
// context is recycled by Fiber after the handler returns, so identity and
// request fields must be read now (mirrors BillingGate capturing usage by
// value pre-Record).
method := c.Method()
path := c.Path()
err := c.Next()
// Resolve the EFFECTIVE status. A handler may set it on the response
// directly (c.Status(...).JSON(...)) OR return a *zip.HTTPError that the
// framework's error handler renders AFTER this middleware unwinds — in the
// latter case the response still reads 200 here, so the returned error is
// the authoritative source of a 401/403. Prefer the error's status when it
// carries one; this is what makes admin-guard denials (which return
// ErrForbidden) get audited as 403.
status := effectiveStatus(c.Fiber().Response().StatusCode(), err)
if !isSecurityRelevant(method, path, status) {
return err // not an audited event; pass the handler result through.
}
record := audit.Record{
Actor: actorFromCtx(c),
Action: method + " " + routeFamily(path),
Resource: resourceFromPath(path),
Auth: authFromCtx(c),
Outcome: outcomeOf(status, err),
SourceIP: ClientIP(c),
// User-Agent is client-controlled free text; a misconfigured/malicious
// client could embed a bearer token in it. Scrub credential-shaped runs
// (and cap length) so the UA can never carry a secret into the record.
UserAgent: scrubFreeText(c.Header("User-Agent")),
RequestID: c.RequestID(),
Method: method,
// Path is scrubbed of any credential-shaped segment: Hanzo routes use
// identifiers (:name/:slug/:id), not secrets, but a token that ever
// rides in the path (an hk-/sk-/pk-/fw_/hz_ key) must never be recorded
// verbatim. resourceFromPath applies the same scrub to the resource id.
Path: scrubCredentialSegments(path),
}
if _, aerr := rec.Append(c.Context(), record); aerr != nil {
// AU-5: could not record a security-relevant event — fail the request
// closed. Do NOT leak the audit error to the client; log it loud.
c.Log().Error("audit append failed — failing request closed",
"path", path, "method", method, "err", aerr)
return c.JSON(503, map[string]any{
"error": map[string]string{
"code": "audit_unavailable",
"message": "Request could not be securely recorded",
},
})
}
return err
}
}
// isSecurityRelevant is the coverage predicate — the ONE place that decides which
// requests enter the audit trail (AC/AU scope). Kept tiny and total so the
// coverage matrix is reviewable at a glance. Order matters and is deliberate:
// the security-relevant conditions are checked FIRST and are unconditional, so
// the health-probe exemption can NEVER be used to evade audit of a mutation or a
// denial (a POST/DELETE, or any 401/403, is always audited whatever the path).
// - any auth-failure outcome (401/403) on any method (a denied access attempt),
// - any /v1/admin/* request (admin reads are access-control-relevant),
// - any mutating request (POST/PUT/PATCH/DELETE).
//
// Only then, a genuine liveness probe (a GET to an exact health route) is
// exempted — it is neither a mutation, a denial, nor an admin call, so it is pure
// request-log noise. The exemption matches EXACT probe paths, never an arbitrary
// path that merely ends in "/health" (which a wildcard/attacker-named segment
// like POST /v1/admin/orgs/x/health could otherwise abuse to slip past audit).
func isSecurityRelevant(method, path string, status int) bool {
// Unconditional security signals — never suppressed by any path shape. A
// denial, an admin call, or a mutation is ALWAYS audited, whatever the path
// (so a wildcard/attacker-named "/health" tail cannot evade it).
if status == 401 || status == 403 {
return true
}
if strings.HasPrefix(path, "/v1/admin/") {
return true
}
if isMutation(method) {
return true
}
// Everything left is a safe read (non-mutating, non-admin, non-denied). None
// are audited — they are request-log noise, not security events. (Liveness
// probes fall here too; there is no separate case because the answer is the
// same: not recorded.)
return false
}
// isMutation reports whether a method changes state.
func isMutation(method string) bool {
switch method {
case "POST", "PUT", "PATCH", "DELETE":
return true
default:
return false
}
}
// actorFromCtx builds the Actor from the sanitized identity headers, gating
// ANTI-FORGERY of the recorded actor on a VALIDATED principal.
//
// The authoritative "this request carried a validated principal" signal is a
// non-empty X-User-Id (c.User()): SanitizeIdentity sets X-User-Id ONLY from a
// JWT it verified, and strips any client-supplied copy on ingress. A request
// with no principal — anonymous, OR one bearing an INVALID/garbage bearer that
// failed validation — has an empty c.User().
//
// In that unvalidated case the org header is NOT trustworthy: SanitizeIdentity's
// Phase-1 residual restores a client-supplied X-Org-Id for the data path, so an
// anonymous attacker could send X-Org-Id: victim-org and, if we recorded it,
// forge a FALSE ATTRIBUTION (an event stamped with a victim's org). So when there
// is no validated sub, the actor is left EMPTY — the record stands as an honest
// anonymous event identified by SourceIP, never mis-attributed to a claimed org.
//
// With a validated sub, org/sub/email all reflect the verified principal and are
// recorded authoritatively.
func actorFromCtx(c *zip.Ctx) audit.Actor {
if !principal.Validated(c) {
// No validated principal — do not trust the client-asserted org.
return audit.Actor{}
}
return audit.Actor{
Org: strings.TrimSpace(c.Org()),
Sub: strings.TrimSpace(c.User()),
Email: strings.TrimSpace(c.UserEmail()),
}
}
// authFromCtx records HOW the caller authenticated and the VALIDATED admin bit.
// IsAdmin comes from c.IsAdmin() (the sanitized X-User-IsAdmin, true only for a
// verified SuperAdmin), never a raw header. Method is inferred from the
// presence/shape of a credential: an Authorization/X-Authorization bearer or a
// session cookie ⇒ "jwt" (or "api-key" for an opaque hk-/sk- token); none ⇒
// "none".
func authFromCtx(c *zip.Ctx) audit.AuthContext {
return audit.AuthContext{
Method: authMethodOf(c),
IsAdmin: c.IsAdmin(),
}
}
// authMethodOf classifies the credential kind WITHOUT capturing it — it inspects
// only the token PREFIX (never stores the value). Order mirrors the sanitizer's
// extraction (bearer, then cookie).
func authMethodOf(c *zip.Ctx) string {
auth := c.Header("Authorization")
if auth == "" {
auth = c.Header("X-Authorization")
}
if tok := bearerFromAuth(auth); tok != "" {
if isAPIKey(tok) {
return "api-key"
}
return "jwt"
}
if basicFromAuth(auth) != "" {
return "basic"
}
for _, name := range cookieTokenNames {
if c.Fiber().Cookies(name) != "" {
return "jwt"
}
}
return "none"
}
// effectiveStatus reconciles the response status with a returned error. If the
// handler returned a *zip.HTTPError (e.g. ErrForbidden), its Status is
// authoritative — the framework renders it after this middleware unwinds, so the
// live response status does not yet reflect it. A non-HTTPError returned error
// with a still-2xx response means the framework will render a 500. Otherwise the
// response status stands.
func effectiveStatus(respStatus int, err error) int {
if err != nil {
var he *zip.HTTPError
if errors.As(err, &he) && he.Status != 0 {
return he.Status
}
// A non-HTTPError propagating up renders as 500, unless the handler already
// set an explicit error status on the response.
if respStatus < 400 {
return 500
}
}
return respStatus
}
// outcomeOf maps the final HTTP status + handler error to an audit Outcome.
// 2xx/3xx ⇒ success; 401/403 ⇒ deny; everything else (4xx/5xx) ⇒ error. The
// reason is a short, non-sensitive label derived from the status class — never a
// raw upstream error body (which could echo sensitive detail).
func outcomeOf(status int, err error) audit.Outcome {
switch {
case status == 401:
return audit.Outcome{Result: "deny", Status: status, Reason: "unauthenticated"}
case status == 403:
return audit.Outcome{Result: "deny", Status: status, Reason: "forbidden"}
case status >= 500:
return audit.Outcome{Result: "error", Status: status, Reason: "server_error"}
case status >= 400:
return audit.Outcome{Result: "error", Status: status, Reason: "client_error"}
default:
return audit.Outcome{Result: "success", Status: status}
}
}
// routeFamily reduces a concrete path to its stable route family for the action
// verb, dropping trailing high-cardinality id segments so "DELETE /v1/admin/
// orgs/acme" and "DELETE /v1/admin/orgs/globex" share the action "DELETE
// /v1/admin/orgs". The full concrete path is preserved separately in Record.Path.
func routeFamily(path string) string {
segs := strings.Split(strings.Trim(path, "/"), "/")
// Keep the leading "v1/<subsystem>/<noun>" and stop before an id-looking tail.
out := make([]string, 0, len(segs))
for _, s := range segs {
if looksLikeID(s) {
break
}
out = append(out, s)
}
if len(out) == 0 {
return "/" + strings.Join(segs, "/")
}
return "/" + strings.Join(out, "/")
}
// resourceFromPath derives the {type,id} resource from a /v1/<subsystem>/<type>/
// [<id>] path. Type is the noun after the subsystem; ID is the following segment
// when it looks like an identifier. Best-effort — the Action verb + Path are the
// authoritative locator; this is a convenience for filtering by resource type.
func resourceFromPath(path string) audit.Resource {
segs := strings.Split(strings.Trim(path, "/"), "/")
// segs: [v1, <subsystem>, <type>, <id?>, ...]
if len(segs) < 3 {
return audit.Resource{}
}
res := audit.Resource{Type: segs[2]}
if len(segs) >= 4 && looksLikeID(segs[3]) {
res.ID = scrubToken(segs[3])
}
return res
}
// scrubToken replaces a path segment that is a credential-shaped token with a
// fixed marker, so a secret that ever appears in a URL is never recorded
// verbatim. It catches, in increasing generality:
// - a known API-key prefix (hk-/sk-/pk-/fw_/hz_ — what isAPIKey recognizes),
// ALSO after percent-decoding, so hk%2DKEY can't slip the prefix check,
// - a JWT (three base64url parts split by '.', starting eyJ),
// - a long, high-entropy base64url/hex run (>=24) — a raw API key / access
// token / hex secret that carries no telltale prefix.
//
// A normal identifier passes through unchanged: a UUID (5 hyphen-split groups,
// each short), a slug, a numeric id, a dotted model name — none is a long
// unbroken high-entropy blob. See TestScrubToken_NoFalsePositives.
//
// RED-review hardening (finding: scrub bypass): the entropy test now (a) accepts
// the FULL base64url alphabet incl. '-' and '_' (RFC 4648 §5), (b) does NOT
// require a digit (an all-alpha opaque key is still a secret), (c) percent-
// decodes first so %2D/%5F can't hide structure, and (d) drops the threshold to
// 24 (short enough for a 128-bit base64 or a 24-hex key, long enough that no
// human-readable slug reaches it).
func scrubToken(seg string) string {
dec := percentDecode(seg)
if isAPIKey(seg) || isAPIKey(dec) ||
looksLikeJWT(seg) || looksLikeJWT(dec) ||
looksLikeHighEntropyToken(seg) || looksLikeHighEntropyToken(dec) {
return "[REDACTED-TOKEN]"
}
return seg
}
// percentDecode best-effort URL-decodes s so a percent-encoded credential
// (hk%2DKEY, sk%5Flive%5F…) is normalized before the credential tests run. On a
// malformed escape it returns s unchanged (the raw form is then tested as-is).
func percentDecode(s string) string {
// Decode repeatedly (bounded) so a NESTED encoding (%252D -> %2D -> -) is
// fully normalized before the credential tests run. Stop when a pass makes no
// change, on a malformed escape, or after a small cap (defeats a decode bomb).
for i := 0; i < 3 && strings.Contains(s, "%"); i++ {
dec, err := url.PathUnescape(s)
if err != nil || dec == s {
break
}
s = dec
}
return s
}
// looksLikeJWT reports whether s is a JSON Web Token OR a JWT header segment. A
// full JWT is three base64url parts split by '.', header starting "eyJ". But when
// free text (a UA) is tokenized on '.', a dotted JWT splits into parts; a real
// header part is >=24 chars (caught by the high-entropy run), yet to be safe we
// ALSO flag any lone segment starting with the canonical base64url header prefix
// "eyJ" (which decodes to '{"') regardless of length — a JWT header can never be
// a legitimate resource id, so redacting it has no false-positive cost.
func looksLikeJWT(s string) bool {
if !strings.HasPrefix(s, "eyJ") {
return false
}
// A full token (two dots) or a bare header segment — either way, redact.
return true
}
// highEntropyMinLen is the length at/above which an UNBROKEN run of base64/hex
// chars is treated as an opaque secret. 24 covers a 128-bit base64 token, a
// 24-nibble hex key, and short API keys, while every human-readable path
// segment/slug/model-name stays under it once split on its separators — no
// single run of a name like "text-embedding-3-large" reaches 24.
const highEntropyMinLen = 24
// looksLikeHighEntropyToken reports whether s CONTAINS an unbroken run of
// >= highEntropyMinLen base64/hex chars — the shape of a raw API key / access
// token / hex secret — UNLESS s is a structured human identifier.
//
// The run alphabet is [A-Za-z0-9_+/-] — the base64 alphabets (url-safe §5 '-”_'
// and standard §4 '+”/') and hex. '-' is INCLUDED so a url-safe-base64 token
// that embeds '-' is still caught by its run (excluding '-' left an ~11% bypass
// for 32-byte url-safe tokens whose '-' happened to break every 24-run — measured).
//
// TWO-STAGE DETECTION:
//
// 1. UNCONDITIONAL run scan — a >= highEntropyMinLen UNBROKEN run over
// [A-Za-z0-9_+/-] flags the value REGARDLESS of the structured-id exemption.
// This catches every raw secret WITHOUT internal separators (hex, base64) —
// the realistic "a client bug put a raw key in the URL" case — at 100%. A
// structured identifier never has a 24-char unbroken run, so this stage never
// over-scrubs one.
//
// 2. STRUCTURED-ID EXEMPTION for the rest (values with separators that DON'T have
// a 24-run): exempt a clearly hyphen-joined human id, judged by LEXICAL
// content — every group WORD-LIKE (single-case word or decimal number), which
// a mixed-case base64 chunk or a long hex-with-letters chunk is NOT (those are
// redacted). Shape alone is attacker-satisfiable (RED found a 3x12-chunked
// secret slipped a shape-only check); the lexical test rejects the common
// secret encodings.
//
// ACCEPTED RESIDUAL BOUND (documented, per RED review): the ONLY residual is a
// secret deliberately chunked into >=3 SINGLE-CASE-ALPHABETIC groups of <=12 chars
// with no hex-letter runs >= hexChunkMinLen (a lowercase- or uppercase-only base32
// alphabet, e.g. abcdefghijkl-mnopqrstuvwx-…). Such a value is lexically
// indistinguishable from a hyphenated model id (deepseek-r1-distill-qwen-32b
// carries the SAME 24-char entropy budget), so it passes stage 2. This is NOT
// closable by any length/case/count rule without a word dictionary
// (over-engineering for a defense-in-depth URL/UA backstop). Mixed-case base64
// chunks AND small-hex chunks (md5/sha display grouping) ARE now caught
// (isWordLikeGroup). The residual does not widen exposure for any REAL credential:
// Hanzo keys are hk-/sk-/pk-/fw_/hz_-prefixed (isAPIKey, caught at any
// length/shape), JWTs are eyJ-prefixed (looksLikeJWT), and request/response BODIES
// are never read. It is an adversary DELIBERATELY base32-chunking their OWN secret
// into a URL path to seed an admin-only audit row — contrived, low-value. The
// realistic accidental leak (an unbroken raw key) is caught by stage 1.
//
// A canonical UUID is exempt (its longest run is 12; the check documents intent).
func looksLikeHighEntropyToken(s string) bool {
if len(s) < highEntropyMinLen {
return false
}
// Stage 1 — unconditional: a long unbroken run is always a secret.
if hasHighEntropyRun(s) {
return true
}
// Stage 2 — separated values: redact unless it's a lexical structured id.
if isUUID(s) || isStructuredID(s) {
return false
}
// A >=24-length value with separators, not a UUID, not a structured id — e.g.
// "sk.live.LONGSECRET…" dotted, or a chunk pattern that is not word-like.
return true
}
// hasHighEntropyRun reports whether s contains an unbroken run of
// >= highEntropyMinLen high-entropy chars where the run alphabet EXCLUDES '-'
// (and '.'): a real separator breaks the run. This is stage 1 — it fires only on
// a genuinely UNBROKEN opaque blob (a raw hex/base64 key with no separators), so
// it never catches a hyphenated identifier (which stage 2 then classifies). A
// url-safe-base64 secret that embeds '-' still trips because the run on ONE side
// of the hyphen is >= 24 (verified: "AbCdEf-GhIjKl_MnOpQrStUvWxYz012345" -> 27).
func hasHighEntropyRun(s string) bool {
run := 0
for _, r := range s {
if isUnbrokenTokenChar(r) {
run++
if run >= highEntropyMinLen {
return true
}
} else {
run = 0
}
}
return false
}
// isUnbrokenTokenChar is the stage-1 run alphabet: base64/hex MINUS '-' (and the
// implicit exclusion of '.', space, etc.). '_' '+' '/' are kept — they appear
// inside opaque tokens and are not identifier separators.
func isUnbrokenTokenChar(r rune) bool {
return (r >= 'A' && r <= 'Z') || (r >= 'a' && r <= 'z') ||
(r >= '0' && r <= '9') || r == '_' || r == '+' || r == '/'
}
// idPartMaxLen bounds a hyphen-group length in the structured-id exemption. 12
// covers the longest word in real model ids ("embedding", "20241022", "preview")
// while a raw secret's random hyphen groups routinely exceed it.
const idPartMaxLen = 12
// isStructuredID reports whether s is a hyphen-joined human identifier (a model
// name, slug): >= 3 hyphen groups where EVERY group is non-empty, <= idPartMaxLen
// chars, and WORD-LIKE. The word-like test is the anti-bypass core — a raw secret
// chunk cannot satisfy it — so the exemption is not attacker-satisfiable by shape.
func isStructuredID(s string) bool {
groups := strings.Split(s, "-")
if len(groups) < 3 {
return false
}
for _, g := range groups {
if g == "" || len(g) > idPartMaxLen || !isWordLikeGroup(g) {
return false
}
}
return true
}
// isWordLikeGroup reports whether a hyphen group looks like a model-id token (a
// dictionary word or a decimal number) rather than a random secret chunk. Two
// lexical signals reject a secret chunk:
// - MIXED CASE (both upper and lower letters) — base64 tokens are dense
// mixed-case; real model tokens are single-case ("sonnet", "Instruct", "3").
// - an all-hex-with-letters run (>= hexChunkMinLen chars, all [0-9a-fA-F], and
// not all-digits) — a hex secret chunk ("dead", "beef", "cafebabe"); a version
// date ("20241022", all digits) is NOT hex-with-letters, so it stays
// word-like. The threshold is 4: RED re-review verified that NO real model-id
// group is all-hex-with-letters of length >= 4, so 4 (vs the prior 8) closes
// the small-hex-chunk leak (md5/sha shown in "xxxx-xxxx" display grouping)
// with zero model-id over-scrub.
func isWordLikeGroup(g string) bool {
var hasUpper, hasLower, allHex, allDigit bool = false, false, true, true
for _, r := range g {
switch {
case r >= 'A' && r <= 'Z':
hasUpper = true
case r >= 'a' && r <= 'z':
hasLower = true
}
if r < '0' || r > '9' {
allDigit = false
}
isHex := (r >= '0' && r <= '9') || (r >= 'a' && r <= 'f') || (r >= 'A' && r <= 'F')
if !isHex {
allHex = false
}
}
if hasUpper && hasLower {
return false // dense mixed-case → base64 secret chunk, not a word.
}
if allHex && !allDigit && len(g) >= hexChunkMinLen {
return false // hex-with-letters → hex secret chunk (not a version date).
}
return true
}
// hexChunkMinLen is the length at/above which an all-hex-with-letters group is
// treated as a secret chunk rather than a word. 4 is the tightest bound that does
// not over-scrub any real model-id group (RED-verified across 19 model ids) while
// catching hex secrets displayed in short groups (md5 "xxxx-xxxx", uuid-ish).
const hexChunkMinLen = 4
// isUUID reports whether s is a canonical 8-4-4-4-12 hex UUID (case-insensitive).
// Used to exempt uuids from the high-entropy secret test — a uuid is a legitimate
// resource id, not a credential.
func isUUID(s string) bool {
if len(s) != 36 {
return false
}
for i, r := range s {
switch i {
case 8, 13, 18, 23:
if r != '-' {
return false
}
default:
if !((r >= '0' && r <= '9') || (r >= 'a' && r <= 'f') || (r >= 'A' && r <= 'F')) {
return false
}
}
}
return true
}
// maxUserAgentLen caps the recorded User-Agent so an oversized UA can neither
// bloat the trail nor smuggle a long payload. 512 chars covers every real UA.
const maxUserAgentLen = 512
// scrubFreeText scrubs credential-shaped words out of client-controlled free
// text (the User-Agent) and caps its length. It tokenizes on a broad delimiter
// superset — whitespace and the punctuation that commonly glues a token into a
// UA/header value (= ; , : / ( ) [ ] { } " ' < > | and backslash) — scrubs each
// token, and rebuilds the string preserving the exact delimiters between tokens.
//
// RED-review hardening (finding: UA tokenizer split on too few delimiters, and
// strings.ReplaceAll was substring-fragile): this walks the string in one pass
// (token-run, delimiter-run, …) and replaces each credential token IN PLACE, so a
// secret delimited by ':' '/' '(' etc. is caught and a token that is a substring
// of another is never mis-replaced. A normal UA ("Mozilla/5.0 (Macintosh …)") is
// unchanged because none of its words is credential-shaped.
func scrubFreeText(s string) string {
if s == "" {
return ""
}
if len(s) > maxUserAgentLen {
s = s[:maxUserAgentLen]
}
var b strings.Builder
b.Grow(len(s))
start := -1 // start index of the current token run, or -1 in a delimiter run.
flush := func(end int) {
if start >= 0 {
b.WriteString(scrubToken(s[start:end]))
start = -1
}
}
for i, r := range s {
if isFreeTextDelimiter(r) {
flush(i)
b.WriteRune(r)
} else if start < 0 {
start = i
}
}
flush(len(s))
return b.String()
}
// isFreeTextDelimiter reports whether r separates tokens in free text (a UA /
// header value). Deliberately broad so a credential can't hide behind an unusual
// separator.
//
// RED re-review (UA bypass persists): '.' '@' '#' '~' are INCLUDED — a prefixed
// key glued by one of them (client@sk-live-KEY, app.sk-live-KEY, build#hk-KEY)
// otherwise stayed one token whose PREFIX was no longer sk-/hk-, so isAPIKey
// missed it. Splitting on them exposes the bare key to scrubToken. Real UA dots
// are numeric version separators (<24, safe) and are split harmlessly. A JWT
// (eyJ.h.p.s) is handled up-front by scrubToken via looksLikeJWT before any
// tokenizer runs on a URL path segment; in free text a dotted JWT will split,
// but each ~40-char base64 part is itself a >=24 high-entropy run, so every part
// is still redacted.
func isFreeTextDelimiter(r rune) bool {
switch r {
case ' ', '\t', '\n', '\r', '=', ';', ',', ':', '/', '\\',
'(', ')', '[', ']', '{', '}', '"', '\'', '<', '>', '|', '&', '?',
'.', '@', '#', '~':
return true
}
return false
}
// scrubCredentialSegments applies scrubToken to every segment of a path, so the
// recorded Path can never carry a credential even if a future route embeds one.
// Route nouns/ids pass through unchanged (they are not isAPIKey-shaped).
func scrubCredentialSegments(path string) string {
if !strings.ContainsAny(path, "/") {
return scrubToken(path)
}
segs := strings.Split(path, "/")
changed := false
for i, s := range segs {
if scrubbed := scrubToken(s); scrubbed != s {
segs[i] = scrubbed
changed = true
}
}
if !changed {
return path
}
return strings.Join(segs, "/")
}
// looksLikeID heuristically flags a path segment as a high-cardinality id (a
// uuid, a long hex/opaque token, or a numeric id) vs a fixed route noun. Used to
// collapse route families; false positives only make the action slightly more
// specific, never leak anything.
func looksLikeID(s string) bool {
if s == "" {
return false
}
if len(s) >= 16 { // long opaque/uuid-ish segment
return true
}
allDigits := true
for _, r := range s {
if r < '0' || r > '9' {
allDigits = false
break
}
}
return allDigits && len(s) > 0
}
+579
View File
@@ -0,0 +1,579 @@
package cloud
// Integration tests for the audit middleware. They drive REAL requests through
// the zip/fiber stack (app.Fiber().Test) with the audit middleware in front of a
// handler, backed by a REAL on-disk audit store, then read the store back to
// assert what was (and was not) recorded. No mocks — the whole capture path runs.
//
// The middleware trusts SanitizeIdentity to have already validated identity, so
// these tests set the sanitized X-User-* headers directly (as SanitizeIdentity
// would after verifying a JWT) — that is the contract boundary under test here.
// The forgery/bypass properties of SanitizeIdentity itself are proven in
// middleware_identity_test.go; here we prove the middleware records the VALIDATED
// identity and the correct outcome for every security-relevant request.
import (
"encoding/json"
"net/http"
"net/http/httptest"
"path/filepath"
"strings"
"testing"
"github.com/hanzoai/cloud/audit"
"github.com/zap-proto/zip"
)
// newAuditApp wires a zip app with the audit middleware in front of a small set
// of routes covering the coverage matrix: a mutating POST, a safe GET, an
// admin-gated route that 403s, and a route that echoes a (secret-bearing) body
// so we can prove the body never reaches a record.
func newAuditApp(t *testing.T) (*zip.App, *audit.Recorder) {
t.Helper()
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := audit.Open(path, nil)
if err != nil {
t.Fatalf("audit.Open: %v", err)
}
t.Cleanup(func() { _ = rec.Close() })
app := zip.New(zip.Config{})
app.Use(AuditTrail(rec))
// Mutating route — must be audited.
app.Post("/v1/kms/secrets", func(c *zip.Ctx) error {
return c.JSON(http.StatusCreated, map[string]string{"id": "sec_1"})
})
// Safe read — must NOT be audited (not a mutation, not admin, not a denial).
app.Get("/v1/pricing/models", func(c *zip.Ctx) error {
return c.JSON(http.StatusOK, map[string]string{"ok": "true"})
})
// Admin route that denies (as the real admin guard would) — the 403 is a
// security event and MUST be audited even though it is a GET.
app.Get("/v1/admin/orgs", func(c *zip.Ctx) error {
if !c.IsAdmin() {
return zip.ErrForbidden("SuperAdmin required")
}
return c.JSON(http.StatusOK, map[string]string{"ok": "true"})
})
// A mutation whose request body carries secrets — used to prove the body is
// never captured. The handler ignores the body; the point is what the
// middleware records (metadata only).
app.Post("/v1/iam/users", func(c *zip.Ctx) error {
return c.JSON(http.StatusOK, map[string]string{"ok": "true"})
})
return app, rec
}
// asAdmin sets the sanitized identity headers a VALIDATED SuperAdmin would
// carry after SanitizeIdentity (X-User-IsAdmin=true, org=admin).
func asAdmin(req *http.Request) {
req.Header.Set("X-User-Id", "z@hanzo.ai")
req.Header.Set("X-User-Email", "z@hanzo.ai")
req.Header.Set("X-Org-Id", "admin")
req.Header.Set("X-User-IsAdmin", "true")
req.Header.Set("Authorization", "Bearer eyJ.validated.jwt") // shape only; classifies as jwt
}
// asUser sets sanitized headers for a normal (non-admin) validated principal.
func asUser(req *http.Request) {
req.Header.Set("X-User-Id", "alice")
req.Header.Set("X-Org-Id", "acme")
req.Header.Set("Authorization", "Bearer eyJ.validated.jwt")
}
func mustTest(t *testing.T, app *zip.App, req *http.Request) *http.Response {
t.Helper()
resp, err := app.Fiber().Test(req)
if err != nil {
t.Fatalf("Test %s %s: %v", req.Method, req.URL.Path, err)
}
return resp
}
// TestAudit_RecordsMutation proves a mutating request is captured with the
// correct validated actor, action, resource, outcome, and auth context — and the
// record is hash-chained (has a hash) and verifies.
func TestAudit_RecordsMutation(t *testing.T) {
app, rec := newAuditApp(t)
req := httptest.NewRequest(http.MethodPost, "/v1/kms/secrets", nil)
asUser(req)
req.Header.Set("X-Forwarded-For", "203.0.113.9, 10.0.0.1")
req.Header.Set("User-Agent", "test-agent/1.0")
resp := mustTest(t, app, req)
if resp.StatusCode != http.StatusCreated {
t.Fatalf("status = %d, want 201", resp.StatusCode)
}
rows, total, err := rec.Query(t.Context(), audit.Filter{})
if err != nil {
t.Fatalf("Query: %v", err)
}
if total != 1 || len(rows) != 1 {
t.Fatalf("recorded %d events, want exactly 1", total)
}
r := rows[0]
if r.Actor.Org != "acme" || r.Actor.Sub != "alice" {
t.Errorf("actor = %+v, want org=acme sub=alice (the VALIDATED identity)", r.Actor)
}
if r.Method != "POST" || r.Path != "/v1/kms/secrets" {
t.Errorf("method/path = %s %s, want POST /v1/kms/secrets", r.Method, r.Path)
}
if r.Resource.Type != "secrets" {
t.Errorf("resource type = %q, want secrets", r.Resource.Type)
}
if r.Outcome.Result != "success" || r.Outcome.Status != 201 {
t.Errorf("outcome = %+v, want success/201", r.Outcome)
}
if r.Auth.Method != "jwt" {
t.Errorf("auth method = %q, want jwt", r.Auth.Method)
}
if r.SourceIP != "203.0.113.9" {
t.Errorf("source ip = %q, want the left-most XFF entry", r.SourceIP)
}
if r.UserAgent != "test-agent/1.0" {
t.Errorf("user agent = %q, want test-agent/1.0", r.UserAgent)
}
if r.Hash == "" {
t.Error("record has no hash — not chained")
}
if iv, _ := rec.Verify(t.Context()); !iv.OK {
t.Errorf("chain broke after one record at %d (%s)", iv.BrokenAt, iv.Reason)
}
}
// TestAudit_RecordsDenial proves a 403 (access-control denial) is audited even on
// a GET, with outcome result="deny", and records the actor who was denied.
func TestAudit_RecordsDenial(t *testing.T) {
app, rec := newAuditApp(t)
// A NON-admin hits the admin route → 403.
req := httptest.NewRequest(http.MethodGet, "/v1/admin/orgs", nil)
asUser(req) // not admin
resp := mustTest(t, app, req)
if resp.StatusCode != http.StatusForbidden {
t.Fatalf("status = %d, want 403", resp.StatusCode)
}
rows, total, err := rec.Query(t.Context(), audit.Filter{Result: "deny"})
if err != nil {
t.Fatalf("Query: %v", err)
}
if total != 1 {
t.Fatalf("recorded %d denials, want 1", total)
}
r := rows[0]
if r.Outcome.Result != "deny" || r.Outcome.Status != 403 {
t.Errorf("outcome = %+v, want deny/403", r.Outcome)
}
if r.Actor.Sub != "alice" {
t.Errorf("denied actor sub = %q, want alice", r.Actor.Sub)
}
if r.Auth.IsAdmin {
t.Error("denied non-admin recorded as admin")
}
}
// TestAudit_SkipsSafeReads proves an ordinary successful GET on a non-admin route
// is NOT audited — the trail captures security events, not read-log noise.
func TestAudit_SkipsSafeReads(t *testing.T) {
app, rec := newAuditApp(t)
req := httptest.NewRequest(http.MethodGet, "/v1/pricing/models", nil)
asUser(req)
resp := mustTest(t, app, req)
if resp.StatusCode != http.StatusOK {
t.Fatalf("status = %d, want 200", resp.StatusCode)
}
_, total, err := rec.Query(t.Context(), audit.Filter{})
if err != nil {
t.Fatalf("Query: %v", err)
}
if total != 0 {
t.Fatalf("a safe GET was audited (%d rows) — trail should skip non-security reads", total)
}
}
// TestAudit_AdminReadIsAudited proves a SUCCESSFUL admin read is audited (admin
// access itself is an AC-relevant event), distinguishing it from a normal read.
func TestAudit_AdminReadIsAudited(t *testing.T) {
app, rec := newAuditApp(t)
req := httptest.NewRequest(http.MethodGet, "/v1/admin/orgs", nil)
asAdmin(req)
resp := mustTest(t, app, req)
if resp.StatusCode != http.StatusOK {
t.Fatalf("status = %d, want 200", resp.StatusCode)
}
rows, total, err := rec.Query(t.Context(), audit.Filter{})
if err != nil {
t.Fatalf("Query: %v", err)
}
if total != 1 {
t.Fatalf("admin read recorded %d, want 1", total)
}
if !rows[0].Auth.IsAdmin || rows[0].Outcome.Result != "success" {
t.Errorf("admin read record = auth.isAdmin=%v outcome=%+v, want admin+success", rows[0].Auth.IsAdmin, rows[0].Outcome)
}
}
// TestAudit_NeverCapturesRequestBody is the secret-safety proof: a mutation whose
// body is FULL of credentials is audited, but the stored record contains NONE of
// the body — the middleware captures metadata only, so a secret in a body can
// never leak into the trail. This is the "reuse RedactUserSecrets" guarantee at
// its strongest: the code that could leak a secret never reads it.
func TestAudit_NeverCapturesRequestBody(t *testing.T) {
app, rec := newAuditApp(t)
secretBody := `{"username":"bob","password":"hunter2","apiKey":"sk-live-DEADBEEF","token":"ghp_SECRET"}`
req := httptest.NewRequest(http.MethodPost, "/v1/iam/users", strings.NewReader(secretBody))
req.Header.Set("Content-Type", "application/json")
asAdmin(req)
// Also stuff a secret into a header value that is NOT an identity header — it
// must not be captured either (we only record User-Agent + XFF, never arbitrary
// headers, and never Authorization's value).
req.Header.Set("Authorization", "Bearer eyJsuper.secret.token.value")
resp := mustTest(t, app, req)
if resp.StatusCode != http.StatusOK {
t.Fatalf("status = %d, want 200", resp.StatusCode)
}
rows, total, err := rec.Query(t.Context(), audit.Filter{})
if err != nil {
t.Fatalf("Query: %v", err)
}
if total != 1 {
t.Fatalf("recorded %d, want 1", total)
}
// Serialize the WHOLE record and scan for any secret substring.
blob, _ := json.Marshal(rows[0])
for _, secret := range []string{"hunter2", "sk-live-DEADBEEF", "ghp_SECRET", "super.secret.token.value"} {
if strings.Contains(string(blob), secret) {
t.Fatalf("SECRET LEAKED into audit record: %q found in %s", secret, blob)
}
}
// But the metadata IS there: the auth method is classified without the token.
if rows[0].Auth.Method != "jwt" {
t.Errorf("auth method = %q, want jwt (classified from prefix, token not stored)", rows[0].Auth.Method)
}
if rows[0].Before != nil || rows[0].After != nil {
t.Errorf("middleware set before/after (%s / %s) — it must never read bodies", rows[0].Before, rows[0].After)
}
}
// TestAudit_ScrubsCredentialInPath proves a credential-shaped token that rides in
// the URL PATH (e.g. a KMS route where a caller wrongly puts an sk-/hk- key in the
// path) is never recorded verbatim in either Path or resource.ID — defense in
// depth beyond "bodies are never read". A normal identifier is untouched.
func TestAudit_ScrubsCredentialInPath(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := audit.Open(path, nil)
if err != nil {
t.Fatalf("open: %v", err)
}
t.Cleanup(func() { _ = rec.Close() })
app := zip.New(zip.Config{})
app.Use(AuditTrail(rec))
app.Delete("/v1/kms/secrets/*", func(c *zip.Ctx) error {
return c.JSON(http.StatusOK, map[string]string{"ok": "true"})
})
// Three credential shapes smuggled into the path across three requests: a
// prefixed key, a raw high-entropy hex secret (NO telltale prefix), and a JWT.
paths := []struct{ path, secret string }{
{"/v1/kms/secrets/sk-live-SUPERSECRETKEY1234567890", "SUPERSECRETKEY"},
{"/v1/kms/secrets/deadbeefcafe0123456789abcdef0123456789abcdef0123", "deadbeefcafe0123"},
{"/v1/kms/secrets/eyJhbGciOiJIUzI1NiJ9.cGF5bG9hZA.c2ln", "eyJhbGciOiJIUzI1NiJ9"},
}
for _, tc := range paths {
req := httptest.NewRequest(http.MethodDelete, tc.path, nil)
asAdmin(req)
if resp := mustTest(t, app, req); resp.StatusCode != http.StatusOK {
t.Fatalf("%s: status = %d, want 200", tc.path, resp.StatusCode)
}
}
rows, total, err := rec.Query(t.Context(), audit.Filter{})
if err != nil {
t.Fatalf("Query: %v", err)
}
if total != len(paths) {
t.Fatalf("recorded %d, want %d", total, len(paths))
}
blob, _ := json.Marshal(rows)
for _, tc := range paths {
if strings.Contains(string(blob), tc.secret) {
t.Fatalf("credential in path leaked into record: %q present in %s", tc.secret, blob)
}
}
for _, r := range rows {
if !strings.Contains(r.Path, "[REDACTED-TOKEN]") {
t.Errorf("path token not scrubbed: %q", r.Path)
}
}
}
// TestAudit_ScrubsSecretInUserAgent proves a bearer/API-key embedded in the
// client-controlled User-Agent is scrubbed, and a normal UA is untouched.
func TestAudit_ScrubsSecretInUserAgent(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := audit.Open(path, nil)
if err != nil {
t.Fatalf("open: %v", err)
}
t.Cleanup(func() { _ = rec.Close() })
app := zip.New(zip.Config{})
app.Use(AuditTrail(rec))
app.Post("/v1/kms/secrets", func(c *zip.Ctx) error { return c.JSON(http.StatusOK, map[string]string{"ok": "1"}) })
req := httptest.NewRequest(http.MethodPost, "/v1/kms/secrets", nil)
asAdmin(req)
req.Header.Set("User-Agent", "myclient/1.0 Bearer eyJhbGciOiJI.pay.sig key=sk-live-LEAKME99999")
mustTest(t, app, req)
rows, _, _ := rec.Query(t.Context(), audit.Filter{})
if len(rows) != 1 {
t.Fatalf("got %d rows, want 1", len(rows))
}
for _, secret := range []string{"eyJhbGciOiJI", "sk-live-LEAKME99999"} {
if strings.Contains(rows[0].UserAgent, secret) {
t.Errorf("UA secret leaked: %q in %q", secret, rows[0].UserAgent)
}
}
// The non-secret UA prefix survives (audit usefulness preserved).
if !strings.Contains(rows[0].UserAgent, "myclient/1.0") {
t.Errorf("UA over-scrubbed, lost the client name: %q", rows[0].UserAgent)
}
}
// TestScrubToken_NoFalsePositives proves legitimate identifiers are NEVER
// scrubbed — the guard fires only on genuinely secret-shaped segments, so the
// audit trail keeps its query precision for normal resource ids.
func TestScrubToken_NoFalsePositives(t *testing.T) {
for _, id := range []string{
"acme-corp", "gpt-4o-mini", "my_project_123", "user@example.com",
"550e8400-e29b-41d4-a716-446655440000", // uuid (hyphens)
"claude-opus-4-20250514", "text-embedding-3-large",
"my-cool-project-name", "feature-branch-xyz",
"deployment-2024-01-15", "report.pdf", "data.json",
// Red re-review round 2 — hyphenated model ids MUST pass (AU-3: an auditor
// must still see WHICH model a config change touched).
"claude-3-5-sonnet-20241022", "claude-3-5-haiku-20241022",
"claude-sonnet-4-20250514", "claude-3-7-sonnet-20250219",
"claude-3-5-sonnet-latest", "deepseek-r1-distill-qwen-32b",
"claude-3-opus-20240229", "stable-diffusion-xl-base",
"mixtral-8x7b-instruct", "llama-3-1-8b-instruct", "whisper-large-v3-turbo",
"v1", "models", "sync", "12345", "a", "",
} {
if got := scrubToken(id); got != id {
t.Errorf("false scrub: legit id %q → %q", id, got)
}
}
// And genuine secrets ARE scrubbed.
for _, sec := range []string{
"sk-live-abcdef", "hk-1234567890abcdef", "eyJhbG.payload.signature",
"deadbeefcafe0123456789abcdef0123456789abcdef0123", // 48-char raw hex
} {
if scrubToken(sec) == sec {
t.Errorf("missed secret: %q not scrubbed", sec)
}
}
}
// TestScrubToken_RedReviewBypassClasses is the regression for the 4 scrub-bypass
// classes Red found: base64url with -/_, all-alpha opaque >=len, percent-encoded
// prefixes, and delimiter-glued UA tokens. Each MUST now be redacted.
func TestScrubToken_RedReviewBypassClasses(t *testing.T) {
for _, sec := range []string{
"AbCdEf-GhIjKl_MnOpQrStUvWxYz012345", // base64url with - and _
"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMN", // all-alpha opaque, no digit
"hk%2DROTATEKEY0001SECRETKEY", // percent-encoded hk-
"sk%5Flive%5FBYPASS0001SECRETKEY", // percent-encoded sk_
// Red re-review round 2 — dotted-exemption + encoding + standard-base64:
"deadbeefcafe0123456789abcdef0123456789abcdef.x", // ".x" tail forces dotted exemption
"AbCdEfGhIjKlMnOpQrStUvWxYz012345.json", // secret with a filename-ish suffix
"hk%252DROTATEKEY0001SECRETKEY", // double percent-encoded hk-
"AbCdEfGhIjKlMnOpQrStUvWx0123456789", // 34-char opaque run (standard/url b64)
// Red re-review round 3 — interior-hyphen raw secret (NOT a structured id:
// only 1 hyphen, long parts) must still redact despite '-' in the run.
"aaaaaaaaaaaaaaaaaaaaaaaa-bbbbbbbbbbbbbbbbbbbbbbbb",
// Red final re-review — a secret CHUNKED to satisfy the structured-id shape
// (>=3 groups <=12 chars) must STILL redact: the lexical (word-like) test
// rejects mixed-case base64 chunks and hex chunks (>= hexChunkMinLen=4).
"AbCdEfGhIjKl-MnOpQrStUvWx-YzAbCdEfGhIj", // mixed-case base64 chunks
"A1b2C3d4-E5f6G7h8-I9j0K1l2", // 128-bit mixed-case chunks
"deadbeef-cafebabe-01234567-89abcdef", // all-hex chunks (8-char groups)
"abcdef01-23456789-abcdef01", // hex chunks
// Red final polish — SMALL hex chunks (md5/sha "xxxx-xxxx" display) now
// caught by the len>=4 hex rule.
"abcd-ef01-2345-6789-abcd-ef01", // 4-char hex groups
"dead-beef-cafe-babe-0123-4567", // 4-char hex groups
} {
if got := scrubToken(sec); got != "[REDACTED-TOKEN]" {
t.Errorf("Red bypass STILL OPEN: %q → %q (want redacted)", sec, got)
}
}
// UA with a secret glued by :/()[]= — must be scrubbed, client name kept.
ua := scrubFreeText("myapp/1.0 (token:sk-live-BYPASS0001) [key=hk-1234567890abcdef]")
for _, leak := range []string{"sk-live-BYPASS0001", "hk-1234567890abcdef"} {
if strings.Contains(ua, leak) {
t.Errorf("UA bypass: %q leaked in %q", leak, ua)
}
}
if !strings.Contains(ua, "myapp/1.0") {
t.Errorf("UA over-scrubbed, lost client name: %q", ua)
}
// Red re-review round 2 — a key glued by . @ # ~ must NOT survive.
for _, glued := range []string{
"client@sk-live-SECRETKEY00001", "app.sk-live-SECRETKEY00001",
"build#hk-SECRETKEY000000001", "v1~sk-live-SECRETKEY00001",
} {
if got := scrubFreeText(glued); strings.Contains(got, "SECRETKEY") {
t.Errorf("UA glue-char bypass: %q → %q (secret survives)", glued, got)
}
}
// Normal UAs must be byte-identical (no false scrub).
for _, ua := range []string{
"console", "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7)",
"curl/8.1.2", "Go-http-client/2.0",
} {
if got := scrubFreeText(ua); got != ua {
t.Errorf("UA false positive: %q → %q", ua, got)
}
}
}
// TestAudit_HealthSuffixCannotEvadeAudit proves a mutating request whose path
// ENDS in /health (an attacker-named wildcard segment) is STILL audited — the
// liveness exemption is exact and never suppresses a mutation or a denial. This
// closes an audit-evasion hole where POST /v1/admin/orgs/x/health would slip past.
func TestAudit_HealthSuffixCannotEvadeAudit(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := audit.Open(path, nil)
if err != nil {
t.Fatalf("open: %v", err)
}
t.Cleanup(func() { _ = rec.Close() })
app := zip.New(zip.Config{})
app.Use(AuditTrail(rec))
app.Post("/v1/admin/orgs/*", func(c *zip.Ctx) error { return c.JSON(http.StatusOK, map[string]string{"ok": "1"}) })
app.Get("/v1/kms/health", func(c *zip.Ctx) error { return c.JSON(http.StatusOK, map[string]string{"status": "ok"}) })
// (a) A mutating POST ending in /health MUST be audited.
req := httptest.NewRequest(http.MethodPost, "/v1/admin/orgs/evil/health", nil)
asAdmin(req)
mustTest(t, app, req)
_, total, _ := rec.Query(t.Context(), audit.Filter{})
if total != 1 {
t.Fatalf("EVASION: mutating POST ending /health audited %d times, want 1", total)
}
// (b) A genuine liveness GET /v1/kms/health MUST still be skipped.
req2 := httptest.NewRequest(http.MethodGet, "/v1/kms/health", nil)
mustTest(t, app, req2)
_, total2, _ := rec.Query(t.Context(), audit.Filter{})
if total2 != 1 {
t.Fatalf("liveness probe was audited (total went %d→%d) — should be exempt", total, total2)
}
}
// TestAudit_AnonRequestNotAttributedToForgedOrg proves an UNAUTHENTICATED
// attacker cannot forge a false attribution: sending X-Org-Id/X-User-Id/
// X-User-IsAdmin with no validated principal records an ANONYMOUS actor (empty
// org+sub, not admin), never the claimed victim org. Runs the REAL SanitizeIdentity
// (nil validator ⇒ strips authority, restores client X-Org-Id for the data path)
// ahead of AuditTrail, exactly as serve.go wires them.
func TestAudit_AnonRequestNotAttributedToForgedOrg(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := audit.Open(path, nil)
if err != nil {
t.Fatalf("open: %v", err)
}
t.Cleanup(func() { _ = rec.Close() })
app := zip.New(zip.Config{})
app.Use(SanitizeIdentity(nil, "admin")) // trust boundary
app.Use(AuditTrail(rec))
app.Post("/v1/kms/secrets", func(c *zip.Ctx) error { return c.JSON(http.StatusOK, map[string]string{"ok": "1"}) })
req := httptest.NewRequest(http.MethodPost, "/v1/kms/secrets", nil)
// Anonymous attacker forging every identity header.
req.Header.Set("X-Org-Id", "victim-org")
req.Header.Set("X-User-Id", "victim-user")
req.Header.Set("X-User-IsAdmin", "true")
mustTest(t, app, req)
rows, _, _ := rec.Query(t.Context(), audit.Filter{})
if len(rows) != 1 {
t.Fatalf("got %d rows, want 1", len(rows))
}
r := rows[0]
if r.Auth.IsAdmin {
t.Error("forged X-User-IsAdmin survived into the record")
}
if r.Actor.Sub != "" {
t.Errorf("forged X-User-Id recorded as actor.Sub = %q", r.Actor.Sub)
}
if r.Actor.Org == "victim-org" {
t.Errorf("FALSE ATTRIBUTION: anonymous request stamped with claimed org %q", r.Actor.Org)
}
if r.Auth.Method != "none" {
t.Errorf("auth method = %q, want none (no valid credential)", r.Auth.Method)
}
// The event is still recorded (a mutation), honestly anonymous.
if r.Outcome.Result != "success" {
t.Errorf("outcome = %+v, want the anonymous mutation recorded", r.Outcome)
}
}
// TestAudit_NoopWhenUnconfigured proves a nil Recorder makes the middleware a
// pass-through (an unconfigured deployment is never blocked), exactly like
// BillingGate's nil-client behavior.
func TestAudit_NoopWhenUnconfigured(t *testing.T) {
app := zip.New(zip.Config{})
app.Use(AuditTrail(nil))
var ran bool
app.Post("/v1/kms/secrets", func(c *zip.Ctx) error {
ran = true
return c.JSON(http.StatusOK, map[string]string{"ok": "true"})
})
req := httptest.NewRequest(http.MethodPost, "/v1/kms/secrets", nil)
resp := mustTest(t, app, req)
if resp.StatusCode != http.StatusOK || !ran {
t.Fatalf("nil-recorder gate must pass through: status=%d ran=%v", resp.StatusCode, ran)
}
}
// TestAudit_FailsClosedOnWriteError proves that when the audit store cannot
// record a security-relevant event, the request is failed CLOSED (503) rather
// than allowed to succeed unlogged (AU-5). We force the failure by closing the
// store's DB before the request, so Append errors.
func TestAudit_FailsClosedOnWriteError(t *testing.T) {
path := filepath.Join(t.TempDir(), "audit.db")
rec, err := audit.Open(path, nil)
if err != nil {
t.Fatalf("open: %v", err)
}
// Close the underlying store so every subsequent Append fails.
_ = rec.Close()
app := zip.New(zip.Config{})
app.Use(AuditTrail(rec))
var ran bool
app.Post("/v1/kms/secrets", func(c *zip.Ctx) error {
ran = true
return c.JSON(http.StatusCreated, map[string]string{"id": "x"})
})
req := httptest.NewRequest(http.MethodPost, "/v1/kms/secrets", nil)
asAdmin(req)
resp := mustTest(t, app, req)
// The handler may have run (audit wraps AFTER the chain), but the response the
// CLIENT sees must be the fail-closed 503, not the handler's 201 — a
// security-relevant action that could not be recorded is not acknowledged as
// success.
if resp.StatusCode != http.StatusServiceUnavailable {
t.Fatalf("status = %d, want 503 (fail-closed when audit write fails)", resp.StatusCode)
}
_ = ran
}
+212
View File
@@ -0,0 +1,212 @@
package cloud
// The datastore OLAP mirror — a best-effort projection of the audit
// trail for fleet-wide, long-retention, cross-deployment query. It implements
// audit.Mirror.
//
// The datastore is the natural OLAP audit sink: the table is a MergeTree, which
// is INSERT-ONLY by engine — datastore rejects UPDATE/DELETE against it at parse
// time ("MergeTree does not support mutations"), so the mirror is append-only at
// the storage layer, matching the local chain's discipline. We create the table
// idempotently on first connect (CREATE TABLE IF NOT EXISTS) and insert via the
// canonical datastore-go PrepareBatch → Append → Send idiom (the same the
// provisioning subsystem uses; the driver is already in cloud's module graph, so
// this adds no dependency).
//
// This mirror is NEVER the integrity authority — the local SQLite hash-chain is.
// Its rows carry the same seq + hash so an operator CAN cross-check the OLAP copy
// against the chain, but a mirror gap is a query-completeness issue, not a
// tamper-evidence one. Every mirror error is logged and dropped by the Recorder;
// the request path never sees it.
import (
"context"
"fmt"
"os"
"strings"
"time"
datastore "github.com/hanzo-ds/go"
"github.com/hanzoai/cloud/audit"
luxlog "github.com/luxfi/log"
)
// datastoreMirror writes audit records to a datastore MergeTree table.
type datastoreMirror struct {
conn datastore.Conn
table string
log luxlog.Logger
}
// newAuditMirror builds the OLAP mirror from operator config, or returns nil when
// no datastore is configured (mirroring is optional — the local chain is the
// authority). It connects lazily-validated (a Ping) and ensures the table exists.
//
// Config (all from env / KMS-injected secrets, never hard-coded):
//
// CLOUD_AUDIT_DATASTORE_ADDR host:9000 of the datastore native port
// CLOUD_AUDIT_DATASTORE_DB database (default "hanzo")
// CLOUD_AUDIT_DATASTORE_TABLE table (default "audit_log")
// CLOUD_AUDIT_DATASTORE_USER user
// CLOUD_AUDIT_DATASTORE_PASSWORD password (KMS-backed secret)
//
// auditEnv reads CLOUD_AUDIT_DATASTORE_<suffix>; auditEnvOr adds a default when unset.
func auditEnv(suffix string) string {
return os.Getenv("CLOUD_AUDIT_DATASTORE_" + suffix)
}
func auditEnvOr(suffix, def string) string {
if v := auditEnv(suffix); v != "" {
return v
}
return def
}
func newAuditMirror(log luxlog.Logger) (audit.Mirror, error) {
addr := strings.TrimSpace(auditEnv("ADDR"))
if addr == "" {
return nil, nil // no datastore configured — local chain only.
}
db := auditEnvOr("DB", "hanzo")
table := auditEnvOr("TABLE", "audit_log")
conn, err := datastore.Open(&datastore.Options{
Addr: []string{addr},
Auth: datastore.Auth{
Database: db,
Username: auditEnv("USER"),
Password: auditEnv("PASSWORD"),
},
DialTimeout: 5 * time.Second,
})
if err != nil {
return nil, fmt.Errorf("audit mirror: open: %w", err)
}
ctx, cancel := context.WithTimeout(context.Background(), 5*time.Second)
defer cancel()
if err := conn.Ping(ctx); err != nil {
_ = conn.Close()
return nil, fmt.Errorf("audit mirror: ping %s: %w", addr, err)
}
qualified := db + "." + table
m := &datastoreMirror{conn: conn, table: qualified, log: log}
if err := m.ensureTable(ctx); err != nil {
_ = conn.Close()
return nil, err
}
if log != nil {
log.Info("audit OLAP mirror connected", "addr", addr, "table", qualified)
}
return m, nil
}
// ensureTable creates the append-only audit table if it does not exist. MergeTree
// = insert-only (mutations rejected at parse time). Partitioned by month and
// ordered for the (org, time) query pattern; seq + hash are carried so the OLAP
// copy is cross-checkable against the local chain.
func (m *datastoreMirror) ensureTable(ctx context.Context) error {
ddl := fmt.Sprintf(`
CREATE TABLE IF NOT EXISTS %s (
seq UInt64,
ts DateTime64(3, 'UTC'),
actor_org LowCardinality(String),
actor_sub String,
actor_email String,
action LowCardinality(String),
res_type LowCardinality(String),
res_id String,
auth_method LowCardinality(String),
is_admin UInt8,
result LowCardinality(String),
status UInt16,
reason String,
source_ip String,
user_agent String,
request_id String,
method LowCardinality(String),
path String,
prev_hash String,
hash String
) ENGINE = MergeTree
PARTITION BY toYYYYMM(ts)
ORDER BY (actor_org, ts, seq)`, m.table)
if err := m.conn.Exec(ctx, ddl); err != nil {
return fmt.Errorf("audit mirror: ensure table: %w", err)
}
return nil
}
// Append writes one record to the OLAP mirror via the canonical batch idiom. The
// before/after diffs are DELIBERATELY not mirrored — the OLAP copy is for
// query/analytics over the event stream, and keeping the (already-redacted but
// still payload-bearing) diffs out of the fleet warehouse minimizes the blast
// radius of a warehouse compromise. The full record (with diffs) lives only in
// the local, access-controlled chain.
func (m *datastoreMirror) Append(ctx context.Context, r audit.Record) error {
batch, err := m.conn.PrepareBatch(ctx, "INSERT INTO "+m.table+` (
seq, ts, actor_org, actor_sub, actor_email, action, res_type, res_id,
auth_method, is_admin, result, status, reason, source_ip, user_agent,
request_id, method, path, prev_hash, hash)`)
if err != nil {
return fmt.Errorf("audit mirror: prepare: %w", err)
}
if err := batch.Append(
r.Seq, r.Time.UTC(), r.Actor.Org, r.Actor.Sub, r.Actor.Email,
r.Action, r.Resource.Type, r.Resource.ID,
r.Auth.Method, boolToUint8(r.Auth.IsAdmin),
r.Outcome.Result, uint16(r.Outcome.Status), r.Outcome.Reason,
r.SourceIP, r.UserAgent, r.RequestID, r.Method, r.Path,
r.PrevHash, r.Hash,
); err != nil {
_ = batch.Abort()
return fmt.Errorf("audit mirror: append: %w", err)
}
return batch.Send()
}
// Checkpoint persists a head-digest checkpoint to an INDEPENDENT digest table in
// the datastore — the AU-9 tail-truncation anchor. Because this lives in a store
// SEPARATE from the local SQLite chain, truncating the chain cannot also rewrite
// the checkpoint history: an external monitor querying this table sees the count
// series and alerts on any regression. Best-effort; a failure is dropped by the
// Recorder (the structured log carries the same digest). Implements
// audit.CheckpointSink.
func (m *datastoreMirror) Checkpoint(ctx context.Context, cp audit.Checkpoint) error {
if err := m.ensureCheckpointTable(ctx); err != nil {
return err
}
batch, err := m.conn.PrepareBatch(ctx, "INSERT INTO "+m.table+"_checkpoints (ts, count, head)")
if err != nil {
return fmt.Errorf("audit mirror: checkpoint prepare: %w", err)
}
if err := batch.Append(cp.Time.UTC(), cp.Count, cp.Head); err != nil {
_ = batch.Abort()
return fmt.Errorf("audit mirror: checkpoint append: %w", err)
}
return batch.Send()
}
// ensureCheckpointTable creates the append-only checkpoint digest table. A plain
// MergeTree ordered by time — the monitor reads the latest rows and checks that
// count never decreases.
func (m *datastoreMirror) ensureCheckpointTable(ctx context.Context) error {
ddl := fmt.Sprintf(`
CREATE TABLE IF NOT EXISTS %s_checkpoints (
ts DateTime64(3, 'UTC'),
count UInt64,
head String
) ENGINE = MergeTree
ORDER BY ts`, m.table)
if err := m.conn.Exec(ctx, ddl); err != nil {
return fmt.Errorf("audit mirror: ensure checkpoint table: %w", err)
}
return nil
}
func boolToUint8(b bool) uint8 {
if b {
return 1
}
return 0
}
+108
View File
@@ -0,0 +1,108 @@
package cloud
// Audit trail construction — the wiring Serve calls to stand up the Recorder.
//
// The audit store is a COMPLIANCE CONTROL, so its persistence is treated like the
// pricing catalog overlay's: a non-persistent (in-memory) audit trail would
// silently lose the record of every prior action on each restart — a fail-OPEN
// degradation of an integrity control. So an empty DataDir is a hard boot error
// in a normal run (prod always sets CLOUD_DATA_DIR; provisioning + pricing already
// require it, so the unified binary always has one). The trail can be turned OFF
// deliberately (CLOUD_AUDIT_DISABLED=true) for a minimal single-service dev run —
// an explicit opt-out, never a silent one.
import (
"fmt"
"os"
"path/filepath"
"strings"
"time"
"github.com/hanzoai/cloud/audit"
luxlog "github.com/luxfi/log"
)
// buildAuditRecorder constructs the audit Recorder from cfg: the append-only
// SQLite chain at {DataDir}/audit.db plus a best-effort datastore OLAP mirror
// when a datastore is configured. Returns (nil, nil) only when the trail is
// explicitly disabled — the caller then wires a no-op middleware.
func buildAuditRecorder(cfg *Config, logger luxlog.Logger) (*audit.Recorder, error) {
if getenvBool("CLOUD_AUDIT_DISABLED") {
if logger != nil {
logger.Warn("audit trail DISABLED by CLOUD_AUDIT_DISABLED — no tamper-evident record will be kept")
}
return nil, nil
}
if cfg.DataDir == "" {
return nil, fmt.Errorf("empty DataDir — the audit trail is a compliance control and requires a persistent data dir (set CLOUD_DATA_DIR); refusing to boot with a non-persistent trail that would lose all prior records on restart (or set CLOUD_AUDIT_DISABLED=true to opt out explicitly)")
}
if err := os.MkdirAll(cfg.DataDir, 0o755); err != nil {
return nil, fmt.Errorf("data dir: %w", err)
}
// OLAP mirror is optional and best-effort. A mirror that cannot be reached at
// boot must NOT stop the binary — the local chain is the authority — so a
// mirror construction error is logged and the trail runs local-only.
var mirror audit.Mirror
if m, err := newAuditMirror(logger); err != nil {
if logger != nil {
logger.Warn("audit OLAP mirror unavailable — running local-only (chain integrity unaffected)", "err", err)
}
} else {
mirror = m
}
dbPath := filepath.Join(cfg.DataDir, "audit.db")
rec, err := audit.Open(dbPath, mirror)
if err != nil {
return nil, fmt.Errorf("open audit store: %w", err)
}
// PER-SHARD audit under horizontal scale. The trail lives at {DataDir}/audit.db on
// THIS pod's own RWO PVC, so under shard routing each pod's chain covers ONLY the
// tenants routed to it (its shard) — and org-scoped audit queries route to the
// owning shard where those records live. Soundness: the chain is a per-FILE hash
// chain whose head is recovered at open; because no two pods share the file, there
// is no cross-pod head to fork (the very failure that pinned cloud to replicas:1 was
// two pods on ONE audit file). Integrity is preserved WITHIN each partition; a
// deployment-wide view is the union of the N per-shard chains. The shard id is
// stamped on the AU-9 checkpoint stream below so the external tail-truncation monitor
// tracks N heads (one per shard) rather than expecting a single global head.
shard := strings.TrimSpace(cfg.ShardSelf) // "" when single-pod — a harmless empty tag
// AU-9 tail-truncation anchor: emit a periodic head-digest checkpoint to the
// append-only observability log (and, when a mirror supports it, an
// independent digest store). An external o11y monitor compares consecutive
// checkpoints and alerts on a count regression — the only way to detect that
// the most-recent records were deleted (an internal chain walk cannot). The
// interval is CLOUD_AUDIT_CHECKPOINT_INTERVAL (default 5m; 0 disables).
interval := auditCheckpointInterval()
if logger != nil {
rec.StartCheckpoints(interval, func(cp audit.Checkpoint) {
logger.Info("audit_head_checkpoint",
"shard", shard, "count", cp.Count, "head", cp.Head, "ts", cp.Time.Format(time.RFC3339Nano))
})
} else {
rec.StartCheckpoints(interval, nil)
}
if logger != nil {
count, head := rec.Head()
logger.Info("audit trail ready (tamper-evident, append-only)",
"store", dbPath, "shard", shard, "records", count, "head", head,
"mirror", mirror != nil, "checkpoint_interval", interval.String())
}
return rec, nil
}
// auditCheckpointInterval resolves the head-digest checkpoint cadence.
// CLOUD_AUDIT_CHECKPOINT_INTERVAL is a Go duration (e.g. "5m", "1h"); default 5m;
// "0" disables periodic checkpoints (the on-close checkpoint still fires).
func auditCheckpointInterval() time.Duration {
if v := getenv("CLOUD_AUDIT_CHECKPOINT_INTERVAL", ""); v != "" {
if d, err := time.ParseDuration(v); err == nil {
return d
}
}
return 5 * time.Minute
}
+219
View File
@@ -0,0 +1,219 @@
// Copyright 2026 Hanzo AI Inc. All Rights Reserved.
package cloud
import (
"context"
"encoding/base64"
"encoding/json"
"io"
"net/http"
"net/url"
"os"
"strings"
"sync"
"time"
)
// The identity boundary (SanitizeIdentity) validates a JWT and mints the identity
// headers every subsystem trusts. An opaque API key (hk-/sk-/pk-/fw_/hz_) is not a
// JWT, so it yielded no principal — and a subsystem that gates on the minted
// identity (zen's billing gate) refused an API-key request as anonymous, though the
// key is a first-class credential. keyResolver closes that gap: it turns a key into
// the SAME idClaims a JWT yields, so ONE minting path serves both credentials and
// key auth and session auth can never disagree on who a request is.
// keyResolver turns an opaque API key into the principal it authenticates, or nil
// for an unknown key or an unconfigured resolver (the request stays anonymous — a
// bad key never grants trust).
type keyResolver interface {
resolve(ctx context.Context, key string) *idClaims
}
// iamKeys resolves an `hk-` key against IAM's get-user?accessKey endpoint,
// authenticating as the confidential `hanzo-console` client (the credential
// clients/account already uses). The resolved user is exactly what a JWT for that
// user carries, so SanitizeIdentity mints identical headers for a key and a session.
// A brief cache keeps the hot auth path off the network; it caches misses too, so a
// bad key cannot hammer IAM.
type iamKeys struct {
base string
auth string // client_secret_basic, or "" when unconfigured
http *http.Client
cache cache[string, *idClaims]
}
// newIAMKeys reads the same IAM env clients/account does. With no confidential
// credential it returns a resolver that resolves nothing (keys stay anonymous —
// never a fabricated principal), so a deployment lacking the credential is safe.
func newIAMKeys() *iamKeys {
return &iamKeys{
base: iamHost(),
auth: iamCred(),
http: &http.Client{Timeout: 5 * time.Second},
cache: newCache[string, *idClaims](60 * time.Second),
}
}
// sharedKeys memoizes ONE API-key resolver (and its 60s cache) for the whole
// binary. The identity boundary (SanitizeIdentity, via newIdentityValidator) and
// any subsystem that must resolve a key OUT-OF-BAND of the Authorization header
// (analytics capture: a project key posted in the SDK body/query) both go through
// this ONE seam, so a key resolves to the SAME org either way and IAM sees one
// warm cache — never a second, drifting resolver.
var (
sharedKeysOnce sync.Once
sharedKeysInst *iamKeys
)
func sharedKeys() *iamKeys {
sharedKeysOnce.Do(func() { sharedKeysInst = newIAMKeys() })
return sharedKeysInst
}
// maxKeyOrgLen bounds a resolved org key the same way principal.MaxOrgLen does: the
// org becomes a warehouse partition key, so an over-long value (malformed / hostile)
// is refused rather than stored.
const maxKeyOrgLen = 128
// OrgForKey resolves an opaque Hanzo API key (hk-/sk-/pk-/fw_/hz_) to the org it
// belongs to — the SAME owner org SanitizeIdentity mints when that key arrives as a
// bearer — through the ONE IAM key seam (get-user?accessKey). It is the exported
// door a keyed, bearer-less SDK path uses to attribute a project key to a tenant.
//
// FAILS CLOSED: ("", false) for a non-key-shaped string, an unknown/unresolvable
// key, an unconfigured resolver, or an out-of-bounds org — never a fabricated or
// default tenant, so a bad key can never be written into another org's partition.
// The isAPIKey prefix gate keeps garbage strings off the IAM network path.
func OrgForKey(ctx context.Context, key string) (string, bool) {
key = strings.TrimSpace(key)
if !isAPIKey(key) {
return "", false
}
claims := sharedKeys().resolve(ctx, key)
if claims == nil {
return "", false
}
owner := strings.TrimSpace(claims.Owner)
if owner == "" || len(owner) > maxKeyOrgLen {
return "", false
}
return owner, true
}
// iamHost is the standalone IAM origin cloud talks to; iamCred is the service
// credential (client_secret_basic) it presents — the ONE IAM identity, shared by
// the API-key resolver here and the /v1/iam edge (iam_edge.go), so both
// authenticate to IAM the same way. Empty cred → a deployment lacking the
// credential stays safe (the caller treats "" as unconfigured).
func iamHost() string { return strings.TrimRight(env("IAM_URL", "IAM_INTERNAL_URL"), "/") }
func iamCred() string {
id := strings.TrimSpace(os.Getenv("IAM_MINT_CLIENT_ID"))
secret := strings.TrimSpace(os.Getenv("IAM_MINT_CLIENT_SECRET"))
if id == "" || secret == "" {
return ""
}
return "Basic " + base64.StdEncoding.EncodeToString([]byte(id+":"+secret))
}
func env(names ...string) string {
for _, n := range names {
if v := strings.TrimSpace(os.Getenv(n)); v != "" {
return v
}
}
return ""
}
func (k *iamKeys) resolve(ctx context.Context, key string) *idClaims {
if k.auth == "" || k.base == "" || key == "" {
return nil
}
if c, ok := k.cache.get(key); ok {
return c // may be a cached nil — a valid "anonymous" answer
}
c := k.lookup(ctx, key)
k.cache.put(key, c)
return c
}
// lookup performs the authenticated get-user?accessKey call and maps the user row
// to idClaims. Any failure (unreachable, denied, unknown key) yields nil. Name is
// both the username IAM's owner/name lookups parse and the id fallback: a key has
// no UUID subject, so userID() falls through to name — the gateway's historical
// X-User-Id==name behavior the owner/name path expects.
func (k *iamKeys) lookup(ctx context.Context, key string) *idClaims {
u := k.base + "/v1/iam/get-user?" + url.Values{"accessKey": {key}}.Encode()
req, err := http.NewRequestWithContext(ctx, http.MethodGet, u, nil)
if err != nil {
return nil
}
req.Header.Set("Authorization", k.auth)
req.Header.Set("Accept", "application/json")
resp, err := k.http.Do(req)
if err != nil {
return nil
}
defer resp.Body.Close()
raw, err := io.ReadAll(io.LimitReader(resp.Body, 1<<20))
if err != nil {
return nil
}
var env struct {
Status string `json:"status"`
Data *struct {
Owner string `json:"owner"`
Name string `json:"name"`
Email string `json:"email"`
IsAdmin bool `json:"isAdmin"`
} `json:"data"`
}
if json.Unmarshal(raw, &env) != nil || env.Status != "ok" || env.Data == nil {
return nil
}
if strings.TrimSpace(env.Data.Owner) == "" {
return nil
}
return &idClaims{
Owner: strings.TrimSpace(env.Data.Owner),
Name: strings.TrimSpace(env.Data.Name),
PreferredUsername: strings.TrimSpace(env.Data.Name),
Email: strings.TrimSpace(env.Data.Email),
IsAdmin: env.Data.IsAdmin,
}
}
// cache is a tiny concurrency-safe TTL map — one generic type for every
// resolve-once-reuse-briefly lookup, so no bespoke cache is hand-rolled per caller.
type cache[K comparable, V any] struct {
ttl time.Duration
mu sync.Mutex
m map[K]entry[V]
}
type entry[V any] struct {
v V
exp time.Time
}
func newCache[K comparable, V any](ttl time.Duration) cache[K, V] {
return cache[K, V]{ttl: ttl, m: make(map[K]entry[V])}
}
func (c *cache[K, V]) get(k K) (V, bool) {
c.mu.Lock()
defer c.mu.Unlock()
e, ok := c.m[k]
if !ok || time.Now().After(e.exp) {
var zero V
return zero, false
}
return e.v, true
}
func (c *cache[K, V]) put(k K, v V) {
c.mu.Lock()
defer c.mu.Unlock()
c.m[k] = entry[V]{v: v, exp: time.Now().Add(c.ttl)}
}
+86
View File
@@ -0,0 +1,86 @@
// Copyright 2026 Hanzo AI Inc. All Rights Reserved.
package cloud
import (
"context"
"net/http"
"net/http/httptest"
"testing"
"time"
)
// iamKeys.lookup maps an IAM get-user?accessKey row to the SAME idClaims a JWT
// yields, so the one minting path serves a key and a session identically.
func TestIAMKeysLookup(t *testing.T) {
var gotKey, gotAuth string
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
gotKey = r.URL.Query().Get("accessKey")
gotAuth = r.Header.Get("Authorization")
w.Header().Set("Content-Type", "application/json")
_, _ = w.Write([]byte(`{"status":"ok","data":{"owner":"hanzo","name":"z","email":"z@hanzo.ai","isAdmin":true}}`))
}))
defer srv.Close()
k := &iamKeys{base: srv.URL, auth: "Basic test", http: srv.Client(), cache: newCache[string, *idClaims](time.Minute)}
c := k.resolve(context.Background(), "hk-abc123")
if c == nil {
t.Fatal("resolve returned nil for a valid key")
}
if c.Owner != "hanzo" || c.Name != "z" || c.Email != "z@hanzo.ai" || !c.IsAdmin {
t.Fatalf("claims = %+v, want owner=hanzo name=z email=z@hanzo.ai isAdmin=true", c)
}
// The key is passed as accessKey and the confidential credential is sent.
if gotKey != "hk-abc123" {
t.Errorf("IAM got accessKey=%q, want hk-abc123", gotKey)
}
if gotAuth != "Basic test" {
t.Errorf("IAM got auth=%q, want the confidential Basic credential", gotAuth)
}
// userID falls through to name (a key has no UUID subject) — the owner/name
// path IAM's privileged lookups expect.
if c.userID() != "z" || c.username() != "z" {
t.Errorf("userID=%q username=%q, want both z", c.userID(), c.username())
}
}
// An unconfigured resolver (no confidential credential) resolves nothing, so an
// API key stays anonymous rather than mis-resolved.
func TestIAMKeysUnconfigured(t *testing.T) {
k := &iamKeys{base: "http://iam", auth: "", cache: newCache[string, *idClaims](time.Minute)}
if c := k.resolve(context.Background(), "hk-abc"); c != nil {
t.Fatalf("unconfigured resolver returned %+v, want nil", c)
}
}
// An unknown key (IAM status != ok) resolves to nil — a bad key never grants trust.
func TestIAMKeysUnknown(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
_, _ = w.Write([]byte(`{"status":"error","msg":"Unauthorized operation"}`))
}))
defer srv.Close()
k := &iamKeys{base: srv.URL, auth: "Basic test", http: srv.Client(), cache: newCache[string, *idClaims](time.Minute)}
if c := k.resolve(context.Background(), "hk-bad"); c != nil {
t.Fatalf("unknown key resolved to %+v, want nil", c)
}
}
// The cache serves a resolved key without a second IAM call (and caches a miss too,
// so a bad key cannot hammer IAM).
func TestIAMKeysCache(t *testing.T) {
var calls int
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
calls++
_, _ = w.Write([]byte(`{"status":"ok","data":{"owner":"hanzo","name":"z"}}`))
}))
defer srv.Close()
k := &iamKeys{base: srv.URL, auth: "Basic test", http: srv.Client(), cache: newCache[string, *idClaims](time.Minute)}
for i := 0; i < 3; i++ {
if k.resolve(context.Background(), "hk-x") == nil {
t.Fatal("resolve nil")
}
}
if calls != 1 {
t.Fatalf("IAM called %d times, want 1 (cached)", calls)
}
}
+539
View File
@@ -0,0 +1,539 @@
package cloud
// In-binary IAM JWT validation — the trust anchor for SanitizeIdentity.
//
// This MIRRORS github.com/hanzoai/gateway/v2/iamauth, the canonical edge
// validator, but cloud deliberately does NOT import that package: iamauth lives
// in the heavyweight gateway module (KrakenD/gin/traefik) AND gateway/v2 already
// imports github.com/hanzoai/cloud, so importing it back would braid a module
// cycle and pull the gateway's whole dependency tree into cloud for ~150 lines
// of validation. The gateway remains the PRIMARY edge authority — in production
// it fronts cloud-api (universe routes.yaml). This validator is the in-binary
// defense-in-depth layer for the in-cluster / direct path, kept tiny and
// auditable on go-jose alone (already in cloud's module graph).
//
// What it enforces, exactly like iamauth.ValidateToken: signature against the
// IAM JWKS, issuer (strict), audience (allowlist, OR semantics), and expiry —
// always. A token missing the issuer is rejected.
import (
"context"
"crypto/rsa"
"encoding/base64"
"encoding/json"
"fmt"
"io"
"net/http"
"os"
"strings"
"sync"
"time"
gojose "github.com/go-jose/go-jose/v4"
"github.com/go-jose/go-jose/v4/jwt"
"github.com/hanzoai/cloud/clients/principal"
model "github.com/hanzoai/iam/pkg/model"
)
// idClaims is the subset of Hanzo IAM JWT claims the identity sanitizer needs.
// Shape mirrors iamauth.Claims so a token resolves identically at both layers.
type idClaims struct {
jwt.Claims
Owner string `json:"owner"` // org slug (the org)
Project string `json:"project"` // org SUB-SCOPE within owner (empty ⟹ default project)
BillingAccount string `json:"billing_account"` // WHO PAYS, stated by IAM (empty ⟹ pre-claim token)
Name string `json:"name"` // display name (id fallback)
PreferredUsername string `json:"preferred_username"` // id fallback
Email string `json:"email"`
IsAdmin bool `json:"isAdmin"`
// Type is IAM's account kind: "application" for a client_credentials MACHINE
// identity (object/token_oauth.go stamps Type:"application"), else a human kind
// ("normal-user", …). It is the discriminator that keeps a machine token — of ANY
// app, not only the KMS-sync one — from ever being granted SuperAdmin. Empty on a
// token that predates the claim ⟹ treated as non-machine (fail toward the KMS-aud
// check below, never toward granting admin).
Type string `json:"type"`
Orgs []model.OrgRef `json:"orgs"` // membership SET (home first); empty on legacy tokens
}
// mintedProject returns the project id to stamp into X-Project-Id, or "" when the
// header must be OMITTED. The project rides in the validated JWT `project` claim,
// scoped to the caller's org exactly like `owner` — trusted, not forgeable. The
// default project (absent claim, or the literal principal.DefaultProject) mints
// nothing, so X-Project-Id is present iff a non-default project is in scope. This
// mirrors the edge (iamauth.Claims.MintedProject) byte-for-byte, so the in-binary
// path binds the same header the gateway would.
func (c *idClaims) mintedProject() string {
if principal.IsDefaultProject(c.Project) {
return ""
}
return strings.TrimSpace(c.Project)
}
// mintedBillingAccount returns the funding account to stamp into
// X-Billing-Account-Id, or "" when the header must be OMITTED (a token minted
// before IAM shipped the claim, or one IAM could not attribute).
//
// WHO PAYS IS NOT A CLIENT'S TO NAME. This rides the validated `billing_account`
// claim — IAM's signed statement, resolved at the identity boundary from the real
// grant context — exactly like `owner` and `project`. It mirrors the edge
// (iamauth.Claims.MintedBillingAccount) byte-for-byte, so the in-binary path binds
// the same header the gateway would, and ai/object.Payer reads the same payer on
// both. The raw client copy is deleted on ingress and NEVER restored.
func (c *idClaims) mintedBillingAccount() string {
return strings.TrimSpace(c.BillingAccount)
}
// userID resolves the canonical user id: sub, then preferred_username, then
// name. IAM may leave sub empty. This is the STABLE identifier (a UUID when IAM
// sets sub) stamped as X-User-Id and consumed as the attribution key everywhere.
func (c *idClaims) userID() string {
if c.Subject != "" {
return c.Subject
}
if c.PreferredUsername != "" {
return c.PreferredUsername
}
return c.Name
}
// username resolves the IAM USERNAME — the `name` half of the `<owner>/<name>`
// key IAM's privileged ops (mint-user-keys, get-user) parse. Prefers the `name`
// claim (IAM's canonical username, e.g. "z"), then preferred_username. It NEVER
// returns the subject: sub is a UUID, and `<owner>/<uuid>` fails IAM's
// GetOwnerAndNameFromId user lookup ("password or code is incorrect"). This is
// the distinct-from-userID() value stamped as X-User-Name so the direct-Bearer
// path builds owner/name correctly — the gateway historically minted
// X-User-Id==name, which userID() (sub-first) breaks on the in-binary path.
func (c *idClaims) username() string {
if c.Name != "" {
return c.Name
}
return c.PreferredUsername
}
// jwtSigAlgs is the accepted signature-algorithm allowlist passed to
// jwt.ParseSigned (go-jose v4 requires it explicitly). RSA + ECDSA + PSS, the
// set IAM may sign with — never "none".
var jwtSigAlgs = []gojose.SignatureAlgorithm{
gojose.RS256, gojose.RS384, gojose.RS512,
gojose.ES256, gojose.ES384, gojose.ES512,
gojose.PS256, gojose.PS384, gojose.PS512,
}
// identityValidator validates an IAM JWT against a cached JWKS. Issuer (any of a
// trusted SET) + audience + expiry are always enforced.
//
// The issuer is a SET so ONE cloud binary validates every white-label brand's
// tokens (hanzo iss=hanzo.id AND lux iss=lux.id, ...). Signature verification is
// unaffected: the in-cluster IAM serves EVERY brand's signing cert in one JWKS
// (cert-hanzo/cert-lux/cert-zoo/...), keyed by the token kid, so a single
// jwksURL verifies all brands. Only the issuer-string comparison had to widen.
type identityValidator struct {
issuers []string
cache *jwksCache
keys keyResolver // resolves an opaque API key to a principal; nil ⟹ keys stay anonymous
}
// newIdentityValidator builds a validator whose trusted-issuer set is the primary
// issuer UNIONED with every white-label brand issuer (BrandIssuers) plus any
// WHITELABEL_ISSUERS override. ttl<=0 uses the 15m JWKS default. The union is
// fail-secure: it only ADDS the known-good brand issuers, never an arbitrary one.
//
// Trust is IAM-native: signature (JWKS) + issuer (this set) + expiry. There is NO
// per-app audience allowlist — the `aud` (a minting app's client_id) is IAM's to
// assign, not cloud's to mirror, so a new first-party app needs zero cloud change.
func newIdentityValidator(issuer, jwksURL string, ttl time.Duration) *identityValidator {
return &identityValidator{
issuers: trustedIssuers(issuer),
cache: newJWKSCache(jwksURL, ttl),
keys: sharedKeys(), // ONE resolver+cache, shared with OrgForKey (analytics capture)
}
}
// kmsMachineAudSuffix is the fixed suffix of a per-org PaaS-KMS sync machine
// identity's audience. Each org's KMS sync authenticates as a dedicated, NON-shared
// IAM application named "<org>-platform-kms" (Organization=<org>, client_credentials
// grant), so IAM stamps the token's aud == the app's own clientId == "<org>-platform-kms"
// (object/token_jwt.go tokenAudience) and owner == <org> (object/token_oauth.go
// GetClientCredentialsToken sets owner = app.Organization).
//
// Validation no longer consults the audience at all (trust is signature + issuer +
// expiry), so a machine token clears validate() like any other. This suffix survives
// for the OPPOSITE reason: to RECOGNISE a machine principal (isKMSMachinePrincipal) so
// SanitizeIdentity can DENY it SuperAdmin even when it carries owner==adminOrg — a
// client_credentials machine identity must never wield platform-admin. The match is
// bound to the token's OWN owner claim (<owner>-platform-kms), so it certifies "the
// KMS sync identity for its own org" and grants nothing wider.
const kmsMachineAudSuffix = "-platform-kms"
// kmsMachineAudience returns the audience an org org's PaaS-KMS sync identity
// carries: "<owner>-platform-kms". An empty owner yields empty — no machine
// audience is ever granted to an org-less token (fail closed).
func kmsMachineAudience(owner string) string {
if owner == "" {
return ""
}
return owner + kmsMachineAudSuffix
}
// isKMSMachinePrincipal reports whether a validated token is a per-org KMS-sync
// machine identity: its audience set contains the owner-bound machine audience
// (<owner>-platform-kms). Such a principal is a client_credentials machine identity
// scoped to exactly one org. SanitizeIdentity uses this to DENY it SuperAdmin
// authority even if it somehow carries isAdmin=true and owner==adminOrg, so V6's
// audience widening can never be leveraged (via an admin-org machine token) into a
// cross-org read. Its org-scoped data access is unaffected — this gates ONLY the
// admin grant, keeping the machine path decoupled from admin inside cloud (rather
// than resting on the external invariant "IAM never stamps isAdmin=true on a
// machine-aud token", which cloud cannot see or enforce).
func isKMSMachinePrincipal(claims *idClaims) bool {
mach := kmsMachineAudience(claims.Owner)
if mach == "" {
return false
}
for _, a := range claims.Audience {
if a == mach {
return true
}
}
return false
}
// isMachinePrincipal reports whether a validated token is a MACHINE (non-human)
// identity — the predicate SanitizeIdentity uses to DENY SuperAdmin and the org-admin
// signal. A client_credentials token carries IAM's `type` == "application"
// (object/token_oauth.go), which catches EVERY machine app regardless of its audience;
// this is the fix for the audience-decomplection widening SuperAdmin's reach — a
// generic admin-org machine app must not become platform-admin just because it belongs
// to the admin org. It UNIONS the owner-bound KMS-sync check so a machine token is
// still excluded even on the (defensive) path where `type` is absent but the
// <owner>-platform-kms audience is present. Fail-closed: unknown/empty type is treated
// as NON-machine so a real human admin (who may carry no `type`) is never locked out —
// the KMS-aud fallback still catches the one machine family we can identify audience-only.
func isMachinePrincipal(claims *idClaims) bool {
return claims.Type == "application" || isKMSMachinePrincipal(claims)
}
// isMember reports whether org is in the token's signed membership set — the
// `orgs` claim IAM mints for a USER token, home org first. It is the ONE test that
// turns a client's org SELECTION into an effective org (SanitizeIdentity), and
// therefore into the ledger that pays (principal.BillingOrg).
//
// The comparison is VERBATIM, no folding, for the same reason the owner claim is
// taken verbatim: "acme" and "ACME" are DISTINCT orgs in IAM, and a fold would let
// a member of one select the other. An empty org is never a member, so an absent
// selection leaves the caller in their home org. An empty set (a legacy token, an
// opaque key, a machine principal — IAM never mints `orgs` for a client_credentials
// token) admits nothing, which is exactly the pre-claim behavior.
func isMember(orgs []model.OrgRef, org string) bool {
if org == "" {
return false
}
for _, o := range orgs {
if o.Org == org {
return true
}
}
return false
}
// validate parses raw, verifies its signature against the JWKS, and enforces
// issuer/audience/expiry. Returns the claims on success, an error otherwise.
func (v *identityValidator) validate(raw string) (*idClaims, error) {
tok, err := jwt.ParseSigned(raw, jwtSigAlgs)
if err != nil {
return nil, fmt.Errorf("parse: %w", err)
}
keys, err := v.cache.get()
if err != nil {
return nil, fmt.Errorf("jwks: %w", err)
}
var claims idClaims
if err := verifyAgainstKeys(tok, keys, &claims); err != nil {
return nil, err
}
// Fail SECURE on a misconfigured (empty) trust set: with no trusted issuer every
// token must be REJECTED, never silently admitted. In production the set is always
// non-empty (the primary issuer + BrandIssuers, unioned in config.go so it is
// "never empty"), so this fires ONLY on an operator misconfiguration — and then it
// denies, it never admits (I2).
if len(v.issuers) == 0 {
return nil, fmt.Errorf("identity validator misconfigured: empty issuer set")
}
// Reject a missing issuer: an empty issuer must never pass the set check.
if claims.Issuer == "" {
return nil, fmt.Errorf("missing issuer")
}
// Reject a missing expiry: ValidateWithLeeway only enforces exp when present
// (it checks `if c.Expiry != nil`), so a token with NO exp would never expire.
// An IAM access token always carries exp; require it.
if claims.Expiry == nil {
return nil, fmt.Errorf("missing expiry")
}
// Issuer must be one of the trusted brand issuers. go-jose's jwt.Expected checks a
// SINGLE issuer, so the issuer is validated here against the set and left out of
// Expected (only expiry/not-before stay with Expected).
if !issuerAllowed(claims.Issuer, v.issuers) {
return nil, fmt.Errorf("untrusted issuer %q", claims.Issuer)
}
// Audience is NOT an access gate. A valid signature from a trusted issuer (both
// checked above) proves IAM minted this token for one of ITS OWN registered apps;
// the `aud` merely names which app. Cloud does not keep a per-app allowlist to
// mirror IAM's registry — that mirror drifted and silently 401'd every new
// first-party app until hand-edited. Org scope is the `owner` claim, enforced by
// every downstream guard; SuperAdmin is owner==adminOrg AND !isKMSMachinePrincipal
// (SanitizeIdentity). Expiry + not-before are STILL enforced here: Expected{} with a
// zero Time validates against time.Now(); an empty AnyAudience skips ONLY the
// audience match (go-jose/v4 jwt/validation.go).
if err := claims.Claims.ValidateWithLeeway(jwt.Expected{}, 2*time.Minute); err != nil {
return nil, fmt.Errorf("claims: %w", err)
}
return &claims, nil
}
// verifyAgainstKeys tries the kid-matched key first, then any RSA signing key —
// mirrors iamauth's selection so a token verifies the same way at both layers.
func verifyAgainstKeys(tok *jwt.JSONWebToken, keys *gojose.JSONWebKeySet, claims *idClaims) error {
var lastErr error
for _, h := range tok.Headers {
if h.KeyID == "" {
continue
}
for _, k := range keys.Key(h.KeyID) {
if err := tok.Claims(k.Key, claims); err == nil {
return nil
} else {
lastErr = err
}
}
}
for _, k := range keys.Keys {
if k.Use != "sig" && k.Use != "" {
continue
}
if _, ok := k.Key.(*rsa.PublicKey); !ok {
continue
}
if err := tok.Claims(k.Key, claims); err == nil {
return nil
} else {
lastErr = err
}
}
if lastErr != nil {
return fmt.Errorf("no matching key: %w", lastErr)
}
return fmt.Errorf("no matching key in JWKS")
}
// ----------------------------------------------------------------------------
// JWKS cache (TTL refresh, stale-on-error) — mirrors iamauth.JWKSCache.
// ----------------------------------------------------------------------------
type jwksCache struct {
mu sync.RWMutex
keys *gojose.JSONWebKeySet
fetchedAt time.Time
ttl time.Duration
url string
client *http.Client
}
func newJWKSCache(url string, ttl time.Duration) *jwksCache {
if ttl <= 0 {
ttl = 15 * time.Minute
}
return &jwksCache{url: url, ttl: ttl, client: &http.Client{Timeout: 10 * time.Second}}
}
// get returns the cached key set, refreshing past TTL. On a fetch error with a
// previously-cached set, the stale set is returned rather than failing — a
// transient JWKS blip must not flap validation (and so admin auth) closed.
func (c *jwksCache) get() (*gojose.JSONWebKeySet, error) {
c.mu.RLock()
if c.keys != nil && time.Since(c.fetchedAt) < c.ttl {
k := c.keys
c.mu.RUnlock()
return k, nil
}
c.mu.RUnlock()
c.mu.Lock()
defer c.mu.Unlock()
if c.keys != nil && time.Since(c.fetchedAt) < c.ttl {
return c.keys, nil
}
keys, err := c.fetch()
if err != nil {
if c.keys != nil {
return c.keys, nil
}
return nil, err
}
c.keys = keys
c.fetchedAt = time.Now()
return keys, nil
}
func (c *jwksCache) fetch() (*gojose.JSONWebKeySet, error) {
ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second)
defer cancel()
req, err := http.NewRequestWithContext(ctx, http.MethodGet, c.url, nil)
if err != nil {
return nil, fmt.Errorf("request: %w", err)
}
resp, err := c.client.Do(req)
if err != nil {
return nil, fmt.Errorf("fetch: %w", err)
}
defer resp.Body.Close()
if resp.StatusCode != http.StatusOK {
return nil, fmt.Errorf("status %d", resp.StatusCode)
}
body, err := io.ReadAll(io.LimitReader(resp.Body, 1<<20))
if err != nil {
return nil, fmt.Errorf("read: %w", err)
}
var set gojose.JSONWebKeySet
if err := json.Unmarshal(body, &set); err != nil {
return nil, fmt.Errorf("parse: %w", err)
}
return &set, nil
}
// ----------------------------------------------------------------------------
// Token extraction — mirrors iamauth's Bearer / Basic / API-key helpers.
// ----------------------------------------------------------------------------
// APIKeyPrefixes are the Hanzo API key families. A published key (pk-) is
// write-only and scoped, so it is safe in a public bundle; a secret key (sk-)
// authenticates a server. Everything else is OAuth2, which is a JWT and not a key.
//
// hk- is sk- under an older name and is on its way out. It stays accepted here
// because IAM mints it — cloud only validates (see account.go mintKey, which
// delegates to iam.mintUserKey) — so dropping it here before IAM renames the
// family would reject every key IAM hands out. Retire it in that order: IAM mints
// sk-, holders re-key, then delete the entry below.
//
// fw_ and hz_ were listed here and never minted by anything: dead entries that
// widened what counts as a credential for no reason. Gone.
//
// This is the ONE authority. Admission mirrors it rather than importing it (it
// stays free of cloud-internal imports); if this list changes, that copy must too.
var APIKeyPrefixes = []string{"pk-", "sk-", "hk-"}
// PublishablePrefix is the ONE publishable spelling: pk- is the key you may ship
// in a browser bundle, sk- is the one you may not. Stripe's split, same reason.
const PublishablePrefix = "pk-"
// IsPublishableKey reports whether tok is a publishable key.
//
// A publishable key is NOT a credential: it identifies a tenant so a public
// surface can WRITE (ingest events), and it must never mint a principal that can
// READ. Cloud resolved any isAPIKey token — pk- included — into "the same
// principal a JWT yields", which made a key documented as "safe to show" into a
// full bearer for the org that owns it. IdentityFromRequest now refuses it, so
// publishable means publishable.
//
// It stays in APIKeyPrefixes on purpose: OrgForKey must still resolve a pk- to
// its owning org, because that is exactly how the ingest door learns which tenant
// a browser beacon belongs to. Resolvable, not authenticating.
func IsPublishableKey(tok string) bool {
return strings.HasPrefix(strings.TrimSpace(tok), PublishablePrefix)
}
// isAPIKey reports whether tok is an opaque, backend-validated key rather than a
// JWT, so the sanitizer skips JWT parsing for it.
func isAPIKey(tok string) bool {
for _, p := range APIKeyPrefixes {
if strings.HasPrefix(tok, p) {
return true
}
}
return false
}
// bearerFromAuth extracts the token from a "Bearer <token>" header value.
func bearerFromAuth(auth string) string {
if auth == "" {
return ""
}
parts := strings.SplitN(auth, " ", 2)
if len(parts) != 2 || !strings.EqualFold(parts[0], "Bearer") {
return ""
}
return strings.TrimSpace(parts[1])
}
// basicFromAuth extracts the token from an HTTP Basic header value: the password
// field (the go/.netrc proxy idiom), falling back to the username when empty.
func basicFromAuth(auth string) string {
if auth == "" {
return ""
}
parts := strings.SplitN(auth, " ", 2)
if len(parts) != 2 || !strings.EqualFold(parts[0], "Basic") {
return ""
}
raw, err := base64.StdEncoding.DecodeString(strings.TrimSpace(parts[1]))
if err != nil {
return ""
}
user, pass, ok := strings.Cut(string(raw), ":")
if !ok {
return ""
}
if pass != "" {
return pass
}
return user
}
// trustedIssuers returns the full trusted-issuer set for the in-binary validator:
// the PRIMARY issuer (the deployment's own brand, cfg.IAMIssuer) UNIONED with every
// white-label brand issuer (BrandIssuers) and any WHITELABEL_ISSUERS override
// (comma-separated). Fail-secure: it only ADDS known-good issuers; a nil/empty
// result is impossible when a primary is set, so the issuer check is always
// enforced. Duplicates are removed; order is primary-first.
func trustedIssuers(primary string) []string {
out := make([]string, 0, 6)
add := func(v string) {
v = strings.TrimSpace(v)
if v == "" {
return
}
for _, e := range out {
if e == v {
return
}
}
out = append(out, v)
}
add(primary)
for _, iss := range BrandIssuers() {
add(iss)
}
for _, iss := range splitTrim(os.Getenv("WHITELABEL_ISSUERS")) {
add(iss)
}
return out
}
// issuerAllowed reports whether iss is one of the trusted issuers. It is
// fail-secure in BOTH directions: an empty trusted set matches NOTHING (deny), so
// a misconfiguration that empties the issuer allowlist rejects every token instead
// of silently disabling the check (I2); a non-empty set rejects any iss not in it.
func issuerAllowed(iss string, trusted []string) bool {
for _, t := range trusted {
if iss == t {
return true
}
}
return false
}
+52
View File
@@ -0,0 +1,52 @@
package cloud
import (
"crypto/rand"
"crypto/rsa"
"testing"
"time"
)
// TestValidate_AudienceIsNotAGate proves the IAM-native trust model: a token signed
// by a trusted issuer validates REGARDLESS of its `aud` (the minting app's client_id).
// Cloud keeps no per-app audience allowlist mirroring IAM's registry — so a brand-new
// first-party app works with zero cloud change, and the specific app tokens the old
// per-app tests pinned (admin-guard, world, team, commerce) are accepted by the SAME
// rule as everything else. Trust is signature + issuer + expiry; org scope is the
// owner claim, enforced downstream. Replaces the three audience_*_test.go files that
// asserted a static allowlist which no longer exists.
func TestValidate_AudienceIsNotAGate(t *testing.T) {
key, err := rsa.GenerateKey(rand.Reader, 2048)
if err != nil {
t.Fatalf("genkey: %v", err)
}
jwks := jwksServer(t, &key.PublicKey)
v := newIdentityValidator(testIssuer, jwks.URL, 0)
future := time.Now().Add(time.Hour)
// Every audience — the apps the deleted per-app tests pinned AND a never-registered
// one — validates identically, because aud is not an access gate.
for _, aud := range []string{
"hanzo-admin-guard", // admin.hanzo.ai forward-auth cockpit
"hanzo-world", // world.hanzo.ai analyst tokens
"hanzo-team", // hanzo.team wallet page
"hanzo-commerce", // commerce.hanzo.ai admin AI assistant
"a-brand-new-first-party-app-never-listed-anywhere",
} {
tok := signWith(t, key, tokenClaims(aud, "acme", "", false, future))
id, err := v.validate(tok)
if err != nil {
t.Fatalf("aud=%q from a trusted issuer must validate (no allowlist), got %v", aud, err)
}
if id.Owner != "acme" {
t.Errorf("aud=%q: owner must be carried through, got %q", aud, id.Owner)
}
}
// Expiry is STILL enforced (dropping the aud gate must not disable time checks):
// a token expired beyond the 2m leeway is rejected whatever its aud.
expired := signWith(t, key, tokenClaims("hanzo-commerce", "acme", "", false, time.Now().Add(-time.Hour)))
if _, err := v.validate(expired); err == nil {
t.Error("expired token must be REJECTED even though audience is no longer gated")
}
}
+101
View File
@@ -0,0 +1,101 @@
package cloud
// The per-org PaaS-KMS sync identity authenticates as its own IAM application
// "<owner>-platform-kms" (client_credentials), so its token carries owner=<org> and
// aud=<owner>-platform-kms. Validation no longer gates on the audience at all (trust
// is signature + issuer + expiry), so a machine token clears validate() like any
// other. The owner-bound machine aud survives only to IDENTIFY such a principal
// (isKMSMachinePrincipal) so SanitizeIdentity can DENY it SuperAdmin even in the admin
// org — a client_credentials machine identity must never wield platform-admin. These
// are white-box unit tests of that identification; the end-to-end proof through
// SanitizeIdentity + the real guard lives in clients/kms (v6_aud_e2e_test.go). Reuses
// the jwksServer/signWith/tokenClaims helpers from middleware_identity_test.go.
import (
"crypto/rand"
"crypto/rsa"
"testing"
"time"
)
func TestIdentityValidator_KMSMachinePrincipal(t *testing.T) {
key, err := rsa.GenerateKey(rand.Reader, 2048)
if err != nil {
t.Fatalf("genkey: %v", err)
}
jwks := jwksServer(t, &key.PublicKey)
v := newIdentityValidator(testIssuer, jwks.URL, 0)
future := time.Now().Add(time.Hour)
t.Run("own-org machine token validates and is recognised as a machine principal", func(t *testing.T) {
c, err := v.validate(signWith(t, key, tokenClaims("maxpower-platform-kms", "maxpower", "", false, future)))
if err != nil {
t.Fatalf("machine token rejected: %v", err)
}
if c.Owner != "maxpower" {
t.Fatalf("owner=%q, want maxpower", c.Owner)
}
if !isKMSMachinePrincipal(c) {
t.Fatal("aud==<owner>-platform-kms must be recognised as a machine principal")
}
})
t.Run("admin-org machine token is recognised so SuperAdmin is denied", func(t *testing.T) {
c, err := v.validate(signWith(t, key, tokenClaims("admin-platform-kms", "admin", "", true, future)))
if err != nil {
t.Fatalf("admin machine token rejected: %v", err)
}
if !isKMSMachinePrincipal(c) {
t.Fatal("admin-org machine token must be recognised (SanitizeIdentity denies it SuperAdmin)")
}
})
t.Run("machine aud bound to a DIFFERENT org is not this owner's machine principal", func(t *testing.T) {
// owner=maxpower, aud=acme-platform-kms: the machine-principal match is bound to
// the token's OWN owner (maxpower-platform-kms), not a "*-platform-kms" wildcard.
// It validates (aud is not gated) and is owner-scoped to maxpower downstream.
c, err := v.validate(signWith(t, key, tokenClaims("acme-platform-kms", "maxpower", "", false, future)))
if err != nil {
t.Fatalf("token rejected: %v", err)
}
if isKMSMachinePrincipal(c) {
t.Fatal("a cross-org machine aud must not count as this owner's machine principal")
}
})
t.Run("ordinary app token is not a machine principal", func(t *testing.T) {
c, err := v.validate(signWith(t, key, tokenClaims("hanzo-console", "maxpower", "", false, future)))
if err != nil {
t.Fatalf("token rejected: %v", err)
}
if isKMSMachinePrincipal(c) {
t.Fatal("an ordinary app token is not a machine principal")
}
})
t.Run("empty-owner token is never a machine principal (fail closed)", func(t *testing.T) {
c, err := v.validate(signWith(t, key, tokenClaims("-platform-kms", "", "", false, future)))
if err != nil {
t.Fatalf("token rejected: %v", err)
}
if isKMSMachinePrincipal(c) {
t.Fatal(`empty-owner token must never be a machine principal (kmsMachineAudience("")=="")`)
}
})
t.Run("machine token expiry still enforced", func(t *testing.T) {
if _, err := v.validate(signWith(t, key, tokenClaims("maxpower-platform-kms", "maxpower", "", false, time.Now().Add(-time.Hour)))); err == nil {
t.Fatal("expired machine token must be rejected")
}
})
}
// kmsMachineAudience is a pure helper; lock its contract directly.
func TestKMSMachineAudience(t *testing.T) {
if got := kmsMachineAudience("maxpower"); got != "maxpower-platform-kms" {
t.Fatalf("kmsMachineAudience(maxpower)=%q, want maxpower-platform-kms", got)
}
if got := kmsMachineAudience(""); got != "" {
t.Fatalf("kmsMachineAudience(\"\")=%q, want \"\" (no machine aud for an org-less token)", got)
}
}
+120
View File
@@ -0,0 +1,120 @@
package cloud
import (
"crypto/rand"
"crypto/rsa"
"os"
"testing"
"time"
)
// TestValidate_FailSecureOnEmptyTrustSet proves I2: a validator whose resolved
// issuer set is empty REJECTS an otherwise-valid, correctly signed token — the axis
// is never silently disabled. Production always resolves a non-empty set; this
// guards the misconfiguration path (an empty issuer set), which must fail closed,
// not open.
func TestValidate_FailSecureOnEmptyTrustSet(t *testing.T) {
key, err := rsa.GenerateKey(rand.Reader, 2048)
if err != nil {
t.Fatalf("genkey: %v", err)
}
jwks := jwksServer(t, &key.PublicKey)
future := time.Now().Add(time.Hour)
tok := signWith(t, key, tokenClaims("hanzo-console", "acme", "", false, future))
// Sanity: a properly configured validator accepts the token.
if _, err := newIdentityValidator(testIssuer, jwks.URL, 0).validate(tok); err != nil {
t.Fatalf("baseline valid token must be accepted, got %v", err)
}
// Empty issuer set → deny (construct directly; trustedIssuers never yields empty
// with a primary, so bypass it to exercise the guard).
vEmptyIss := &identityValidator{issuers: nil, cache: newJWKSCache(jwks.URL, 0), keys: newIAMKeys()}
if _, err := vEmptyIss.validate(tok); err == nil {
t.Error("empty issuer set must REJECT (fail-secure), not accept")
}
}
// TestTrustedIssuers_WhiteLabel proves the in-binary validator's trusted-issuer
// set is the primary issuer UNIONED with every white-label brand issuer plus the
// WHITELABEL_ISSUERS override, deduped, primary-first.
func TestTrustedIssuers_WhiteLabel(t *testing.T) {
os.Unsetenv("WHITELABEL_ISSUERS")
got := trustedIssuers("https://hanzo.id")
want := map[string]bool{
"https://hanzo.id": true,
"https://lux.id": true,
"https://zoo.id": true, // per cloud brand.go registry
"https://pars.id": true,
"https://id.bootno.de": true, // bootnode brand also in the registry
}
set := map[string]bool{}
for _, g := range got {
set[g] = true
}
for w := range want {
if !set[w] {
t.Errorf("trusted set %v missing %q", got, w)
}
}
if got[0] != "https://hanzo.id" {
t.Errorf("primary issuer must be first, got %q", got[0])
}
// Override adds a brand without a rebuild.
t.Setenv("WHITELABEL_ISSUERS", "https://custom.id, https://another.id")
got2 := trustedIssuers("https://hanzo.id")
if !issuerAllowed("https://custom.id", got2) || !issuerAllowed("https://another.id", got2) {
t.Errorf("WHITELABEL_ISSUERS override must add issuers, got %v", got2)
}
}
// TestIssuerAllowed proves the set membership check: brand issuers pass, an
// outsider is rejected, and an empty set is fail-secure — it matches NOTHING (I2),
// so a misconfiguration that empties the allowlist denies every token.
func TestIssuerAllowed(t *testing.T) {
set := []string{"https://hanzo.id", "https://lux.id"}
if !issuerAllowed("https://lux.id", set) {
t.Error("lux.id must be allowed")
}
if issuerAllowed("https://attacker.id", set) {
t.Error("attacker.id must be rejected")
}
if issuerAllowed("anything", nil) {
t.Error("empty set must DENY (fail-secure), never skip the check")
}
}
// TestBrandIssuers proves the issuer list is derived from the brands registry and
// covers every configured brand (one source of truth).
func TestBrandIssuers(t *testing.T) {
got := BrandIssuers()
for _, want := range []string{"https://hanzo.id", "https://lux.id", "https://zoo.id", "https://pars.id", "https://id.bootno.de"} {
found := false
for _, g := range got {
if g == want {
found = true
break
}
}
if !found {
t.Errorf("BrandIssuers()=%v missing %q", got, want)
}
}
}
// TestNewIdentityValidator_MultiIssuer proves the constructed validator carries the
// full brand set, so a lux token would pass the issuer gate on the hanzo binary.
func TestNewIdentityValidator_MultiIssuer(t *testing.T) {
os.Unsetenv("WHITELABEL_ISSUERS")
v := newIdentityValidator("https://hanzo.id", "http://iam.hanzo.svc/v1/iam/.well-known/jwks", 0)
if !issuerAllowed("https://lux.id", v.issuers) {
t.Fatalf("validator must trust the lux issuer, set=%v", v.issuers)
}
if !issuerAllowed("https://hanzo.id", v.issuers) {
t.Fatalf("validator must still trust hanzo (no regression), set=%v", v.issuers)
}
if issuerAllowed("https://evil.id", v.issuers) {
t.Fatalf("validator must reject an untrusted issuer, set=%v", v.issuers)
}
}
+102
View File
@@ -0,0 +1,102 @@
// Copyright 2023-2025 Hanzo AI Inc. All Rights Reserved.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
package cloud
// Auto-routing billing binding at the cloud edge.
//
// The ai subsystem serves a virtual `auto`/`zen-router` model: it resolves the
// request to a concrete model id BEFORE pricing/billing, meters its own LLM
// token cost to commerce keyed on the SERVED model, and reports that id via the
// `X-Routed-Model` response header (and the response body `model` field).
//
// The cloud edge must therefore do two things for an `auto` request, both
// verified here end-to-end through the real BillingGate + DefaultPrice:
// 1. NOT re-price it by the (virtual) request model — /v1/ai/* is self-metered,
// so the edge gate delegates all LLM billing to the ai subsystem. That
// subsystem bills the resolved model, so `auto` bills as what served it.
// 2. Pass the `X-Routed-Model` header through untouched, so the model the
// client sees reported is exactly the model that was billed.
import (
"net/http"
"net/http/httptest"
"strings"
"testing"
"time"
"github.com/zap-proto/zip"
)
// TestAutoRoutingBillsAsResolvedModel drives an `auto` chat request through the
// real edge gate (BillingGate + DefaultPrice) in front of a handler that
// simulates the ai subsystem after it resolved auto→zen4-coder.
func TestAutoRoutingBillsAsResolvedModel(t *testing.T) {
fc := &fakeCommerce{balanceBody: `{"available":5000}`}
srv := fc.server(t)
m := mustClient(t, srv.URL, false /* fail-closed */)
app := zip.New(zip.Config{})
// The genuine edge gate with the genuine price function.
app.Use(BillingGate(m, DefaultPrice))
// Stand-in for the mounted ai subsystem: auto already resolved to zen4-coder,
// which it reports on the header + body (and meters itself — not modeled here).
app.Post("/v1/ai/chat/completions", func(c *zip.Ctx) error {
c.SetHeader("X-Routed-Model", "zen4-coder")
return c.JSON(http.StatusOK, map[string]string{"model": "zen4-coder"})
})
req := httptest.NewRequest(http.MethodPost, "/v1/ai/chat/completions",
strings.NewReader(`{"model":"auto","messages":[{"role":"user","content":"refactor this"}]}`))
req.Header.Set("X-Org-Id", "hanzo")
req.Header.Set("X-User-Id", "alice")
req.Header.Set("Content-Type", "application/json")
resp, err := app.Fiber().Test(req)
if err != nil {
t.Fatalf("Test request: %v", err)
}
if resp.StatusCode != http.StatusOK {
t.Fatalf("status = %d, want 200", resp.StatusCode)
}
// (1) The edge did NOT bill: /v1/ai/* is self-metered (DefaultPrice 0), so the
// gate short-circuits before Authorize/Record. Billing is delegated to the ai
// subsystem, which meters the RESOLVED model — never the virtual `auto`.
// (Give any erroneous async Record a moment to land before asserting zero.)
if fc.usages() != 0 {
t.Fatalf("edge recorded %d usage(s) for /v1/ai/*, want 0 (self-metered by ai)", fc.usages())
}
if waitFor(func() bool { return fc.usages() > 0 }, 50*time.Millisecond) {
t.Fatalf("edge double-billed an ai request (usages=%d): auto must be billed by the ai meter, not the edge", fc.usages())
}
// (2) Header pass-through: the resolved model the ai meter billed reaches the
// client, so what's reported == what's billed.
if got := resp.Header.Get("X-Routed-Model"); got != "zen4-coder" {
t.Errorf("X-Routed-Model = %q, want zen4-coder (must pass through the edge)", got)
}
}
// TestDefaultPriceAiPathModelAgnostic documents the binding at the pricing layer:
// the edge price for the ai chat path is 0 regardless of the request model, so
// `auto` and a concrete model are treated identically — the ai subsystem's own
// per-token meter (keyed on the resolved model) is the single source of the
// charge. Path-based, never request-model-based, pricing is what makes `auto`
// bill as the model that served it.
func TestDefaultPriceAiPathModelAgnostic(t *testing.T) {
if got := priceForPath(t, "/v1/ai/chat/completions"); got != 0 {
t.Errorf("DefaultPrice(/v1/ai/chat/completions) = %d, want 0 — ai self-meters the resolved model", got)
}
}
+62
View File
@@ -0,0 +1,62 @@
package cloud
import "testing"
// The context window is a BODY-SIZE fact, not just a model fact.
//
// A chat request carries its whole prompt in the request body, so the edge's
// BodyLimit is a hard ceiling on the context window no matter what the model
// catalog advertises. The zip/fiber framework default is 4 MiB; a 1M-token
// prompt serializes to roughly 4.3 MB of JSON (measured on prod: 2 MB of body
// carried 466,148 prompt tokens, ~4.5 bytes/token). Left at the default, every
// 1M-context route — deepseek-v4-pro, and anything glm-5.2 overflows into once
// a prompt passes its 262,144 cap — was unreachable: fasthttp rejected the body
// before any handler ran and answered the opaque 400 "Error when parsing
// request", which reads like a malformed payload rather than a size cap.
//
// This pins the ceiling above a real 1M-token prompt so the regression cannot
// come back silently.
// oneMillionTokenBody is a conservative byte estimate for a 1M-token prompt.
// Measured ~4.5 bytes/token; 4.3 keeps the floor conservative.
const oneMillionTokenBody = 1_000_000 * 43 / 10 // ~4.3 MB
// zipFrameworkDefault is the zip/fiber BodyLimit applied when Config.BodyLimit
// is left at 0 (zip.go: `if cfg.BodyLimit == 0 { cfg.BodyLimit = 4 << 20 }`) —
// the exact cap that made 1M context unreachable.
const zipFrameworkDefault = 4 << 20
// LoadConfig registers process flags, so it may only be called ONCE per test
// binary (a second call panics with "flag redefined"). Both invariants are
// therefore asserted against a single load, and the env-override path is
// exercised through the getenvInt helper that LoadConfig itself uses.
func TestBodyLimit_FitsAMillionTokenPrompt(t *testing.T) {
cfg := LoadConfig()
if cfg.BodyLimit == 0 || cfg.BodyLimit == zipFrameworkDefault {
t.Fatalf("BodyLimit = %d — this is the zip/fiber 4 MiB default, the exact cap "+
"that made 1M context unreachable", cfg.BodyLimit)
}
if cfg.BodyLimit <= oneMillionTokenBody {
t.Fatalf("BodyLimit = %d bytes, which cannot hold a 1M-token prompt (~%d bytes); "+
"the 1M-context models would 400 with fasthttp's opaque "+
"%q", cfg.BodyLimit, oneMillionTokenBody, "Error when parsing request")
}
}
func TestBodyLimit_EnvOverride(t *testing.T) {
t.Setenv("GATEWAY_BODY_LIMIT", "33554432") // 32 MiB
if got := getenvInt("GATEWAY_BODY_LIMIT", 16<<20); got != 32<<20 {
t.Fatalf("getenvInt(GATEWAY_BODY_LIMIT) = %d, want %d — the limit must stay tunable", got, 32<<20)
}
}
func TestBodyLimit_DefaultsWhenEnvUnset(t *testing.T) {
t.Setenv("GATEWAY_BODY_LIMIT", "")
if got := getenvInt("GATEWAY_BODY_LIMIT", 16<<20); got != 16<<20 {
t.Fatalf("getenvInt fallback = %d, want the 16 MiB default", got)
}
}
+139
View File
@@ -0,0 +1,139 @@
package cloud
import "strings"
// Brand white-label registry (HIP-0111).
//
// The cloud binary is one artifact serving every brand's API host
// (api.hanzo.ai, api.lux.cloud, api.zoo.cloud, api.cloud.pars.network, ...).
// Brand is a per-deployment value (CLOUD_BRAND / --brand). This registry maps a
// brand to its PUBLIC IAM facts — the canonical OIDC issuer the deployment must
// validate JWTs against. These are public (issuer host + brand domain), so they
// live in code, not in KMS.
//
// One source of truth: nothing else in the binary hardcodes a per-brand issuer.
// Config.IAMIssuer is derived from here when the operator does not pin one, so a
// lux deployment validates against lux.id, a zoo deployment against zoo.id, etc.,
// instead of silently defaulting every brand to iam.hanzo.ai.
// BrandInfo is the PUBLIC per-brand identity used for token validation + URL
// scoping. No secrets.
type BrandInfo struct {
// ID is the canonical brand key.
ID string
// IAMIssuer is the OIDC issuer (JWKS source) for this brand — the value the
// JWT `iss` claim must equal and whose /v1/iam/.well-known/jwks signs tokens.
IAMIssuer string
// Domain is the brand's primary marketing/site domain (for response scoping
// and base-URL derivation, e.g. api.<Domain>).
Domain string
// AltDomains are additional registrable domains that ALSO belong to this
// brand, used ONLY for hostname→brand white-label detection (BrandForHostOK).
// A brand's real serving surfaces span more than its marketing domain — the
// cloud console runs on <brand>.cloud hosts (console.lux.cloud,
// console.zoo.cloud), and a request Host there must brand as Lux/Zoo, never
// fall through to Hanzo. Base-URL/issuer scoping still uses the primary Domain.
AltDomains []string
}
// brands is the brand→IAM registry. Keys are the canonical brand IDs accepted
// by CLOUD_BRAND. Per HIP-0111 §Brands: hanzo→hanzo.id, lux→lux.id,
// zoo→zoo.id, pars→pars.id, bootnode→id.bootno.de.
//
// IAMIssuer MUST equal the `iss` IAM actually stamps AND host the signing JWKS.
// For hanzo the live .well-known/openid-configuration on BOTH hanzo.id and
// iam.hanzo.ai reports issuer=https://hanzo.id + jwks_uri=
// https://hanzo.id/v1/iam/.well-known/jwks (iam.hanzo.ai is a routing alias, not
// the issuer), and the cloud CLI already defaults to hanzo.id. Pinning
// iam.hanzo.ai here would fail the issuer check on every real token, anonymizing
// every principal — SuperAdmin would 403 platform-wide (fail-secure, but
// broken). lux/zoo/pars already correctly point at their own .id issuers.
var brands = map[string]BrandInfo{
"hanzo": {ID: "hanzo", IAMIssuer: "https://hanzo.id", Domain: "hanzo.ai", AltDomains: []string{"hanzo.cloud", "hanzo.app"}},
"lux": {ID: "lux", IAMIssuer: "https://lux.id", Domain: "lux.network", AltDomains: []string{"lux.cloud"}},
"zoo": {ID: "zoo", IAMIssuer: "https://zoo.id", Domain: "zoo.ngo", AltDomains: []string{"zoo.network", "zoo.cloud"}},
"pars": {ID: "pars", IAMIssuer: "https://pars.id", Domain: "pars.network", AltDomains: []string{"pars.ai"}},
"bootnode": {ID: "bootnode", IAMIssuer: "https://id.bootno.de", Domain: "bootno.de"},
}
// DefaultBrand is the fallback brand when CLOUD_BRAND is unknown.
const DefaultBrand = "hanzo"
// BrandFor returns the BrandInfo for id, falling back to the Hanzo brand for an
// unknown id. Lookup is case-insensitive.
func BrandFor(id string) BrandInfo {
if b, ok := brands[strings.ToLower(strings.TrimSpace(id))]; ok {
return b
}
return brands[DefaultBrand]
}
// IssuerForBrand returns the canonical OIDC issuer for a brand id.
func IssuerForBrand(id string) string {
return BrandFor(id).IAMIssuer
}
// BrandForHostOK resolves a request Host to a brand id from the same `brands`
// registry, mirroring the hostname→brand semantics of platform.ts's
// getWhiteLabelBrand: a Host at or under a brand's Domain (api.lux.network,
// lux.network) is that brand. The port is stripped and the compare is
// case-insensitive; the longest matching Domain wins so a nested brand domain is
// never shadowed by a shorter one. ok is false when NO brand domain matches, so
// the caller can choose its own fallback (the deployment brand) rather than
// silently emitting Hanzo branding on, say, a Zoo pod hit with an odd Host.
func BrandForHostOK(host string) (string, bool) {
host = strings.ToLower(strings.TrimSpace(host))
if i := strings.IndexByte(host, ':'); i >= 0 {
host = host[:i]
}
// A fully-qualified Host may carry a trailing root dot ("api.lux.network.");
// strip it so the suffix match still resolves the brand instead of failing to
// neutral.
host = strings.TrimSuffix(host, ".")
best, bestLen := "", -1
for id, b := range brands {
for _, d := range append([]string{b.Domain}, b.AltDomains...) {
d = strings.ToLower(d)
if d == "" {
continue
}
if (host == d || strings.HasSuffix(host, "."+d)) && len(d) > bestLen {
best, bestLen = id, len(d)
}
}
}
return best, best != ""
}
// BrandForHost is BrandForHostOK with the Hanzo default for an unmatched Host.
func BrandForHost(host string) string {
if b, ok := BrandForHostOK(host); ok {
return b
}
return DefaultBrand
}
// brandDisplay is a brand id's human display name: the id with an upper-cased
// first letter (lux → "Lux", hanzo → "Hanzo"). Derived from the id — one source
// of truth with the brands registry, no hand-maintained display list. Used to
// build the white-label console <title> (webui.go).
func brandDisplay(id string) string {
if id == "" {
id = DefaultBrand
}
return strings.ToUpper(id[:1]) + id[1:]
}
// BrandIssuers returns the OIDC issuer of every configured white-label brand. The
// in-binary identity validator (auth_identity.go) trusts a token whose `iss` is
// any of these, so ONE cloud binary validates hanzo AND lux/zoo/pars tokens. One
// source of truth: derived from the same `brands` registry above.
func BrandIssuers() []string {
out := make([]string, 0, len(brands))
for _, b := range brands {
if b.IAMIssuer != "" {
out = append(out, b.IAMIssuer)
}
}
return out
}
+85
View File
@@ -0,0 +1,85 @@
package cloud
import (
"os"
"testing"
)
func TestBrandFor(t *testing.T) {
// hanzo → hanzo.id (NOT iam.hanzo.ai): brand.go was pinned to the real OIDC
// issuer in fddaeb14 ("pin hanzo IAM issuer to hanzo.id") — iam.hanzo.ai is a
// routing alias, and the live .well-known reports iss=https://hanzo.id, so a
// token would fail the issuer check against iam.hanzo.ai. This stale
// assertion predated that pin; aligned here (drive-by, brand.go unchanged).
cases := map[string]string{
"hanzo": "https://hanzo.id",
"lux": "https://lux.id",
"zoo": "https://zoo.id",
"pars": "https://pars.id",
"bootnode": "https://id.bootno.de",
"LUX": "https://lux.id", // case-insensitive
" zoo ": "https://zoo.id", // trimmed
"unknown": "https://hanzo.id", // falls back to hanzo
"": "https://hanzo.id", // empty → hanzo default
}
for brand, want := range cases {
if got := IssuerForBrand(brand); got != want {
t.Errorf("IssuerForBrand(%q) = %q, want %q", brand, got, want)
}
}
}
func TestBrandForHost(t *testing.T) {
match := map[string]string{
"api.hanzo.ai": "hanzo",
"hanzo.ai": "hanzo",
"api.lux.network": "lux",
"lux.network": "lux",
"API.LUX.NETWORK": "lux", // case-insensitive
"api.lux.network:443": "lux", // port stripped
"api.zoo.ngo": "zoo",
"chat.zoo.ngo": "zoo",
"api.pars.network": "pars",
// AltDomains: the real cloud console surfaces run on <brand>.cloud /
// <brand>.network — a Host there must brand as Lux/Zoo, never Hanzo.
"console.lux.cloud": "lux",
"console.zoo.cloud": "zoo",
"foo.zoo.network": "zoo",
"console.hanzo.cloud": "hanzo",
"app.hanzo.app": "hanzo",
}
for host, want := range match {
if got, ok := BrandForHostOK(host); !ok || got != want {
t.Errorf("BrandForHostOK(%q) = %q,%v; want %q,true", host, got, ok, want)
}
if got := BrandForHost(host); got != want {
t.Errorf("BrandForHost(%q) = %q; want %q", host, got, want)
}
}
// No brand domain matches → not ok, and BrandForHost defaults to hanzo. The
// caller (agentskills) uses the not-ok signal to fall back to the DEPLOYMENT
// brand instead of blindly emitting Hanzo on a non-hanzo pod.
for _, host := range []string{"example.com", "localhost", "", "10.0.0.1"} {
if _, ok := BrandForHostOK(host); ok {
t.Errorf("BrandForHostOK(%q) matched a brand, want no match", host)
}
if got := BrandForHost(host); got != DefaultBrand {
t.Errorf("BrandForHost(%q) = %q, want %q", host, got, DefaultBrand)
}
}
}
// TestLoadConfig_IssuerDerivedFromBrand asserts that when CLOUD_IAM_ISSUER is
// unset, the issuer is derived from CLOUD_BRAND — so a non-hanzo brand does not
// silently validate against iam.hanzo.ai.
func TestLoadConfig_IssuerDerivedFromBrand(t *testing.T) {
t.Setenv("CLOUD_BRAND", "lux")
os.Unsetenv("CLOUD_IAM_ISSUER")
cfg := LoadConfig()
if cfg.IAMIssuer != "https://lux.id" {
t.Fatalf("derived issuer = %q, want https://lux.id", cfg.IAMIssuer)
}
if cfg.Brand != "lux" {
t.Fatalf("brand = %q, want lux", cfg.Brand)
}
}
+796 -89
View File
@@ -1,11 +1,28 @@
package cloud
import (
"context"
"encoding/base64"
"fmt"
"os"
"strings"
"time"
aiobject "github.com/hanzoai/ai/object"
"github.com/hanzoai/cloud/cek"
"github.com/hanzoai/cloud/clients/commerceinproc"
"github.com/hanzoai/cloud/clients/metering"
"github.com/hanzoai/cloud/internal/org"
s3 "github.com/hanzoai/s3-go"
luxlog "github.com/luxfi/log"
"github.com/zap-proto/zip"
"github.com/hanzoai/cloud/clients"
"github.com/hanzoai/cloud/clients/finance"
"github.com/hanzoai/cloud/clients/gateway/edge"
"github.com/hanzoai/cloud/clients/money"
"github.com/hanzoai/cloud/clients/s3admin"
"github.com/hanzoai/cloud/types"
)
// BuildDeps constructs the Deps used by every subsystem's Mount(app, deps).
@@ -33,7 +50,7 @@ import (
// JSON does not appear in any of these paths. Inter-subsystem calls
// are ZAP-typed Go values either via direct method dispatch (mode 1)
// or via ZAP RPC over the wire (mode 2). JSON happens only at the
// gateway/ingress edge, through the hanzoai/zip jsonenc helper.
// gateway/ingress edge, through the zip jsonenc helper.
//
// Payments and Vault are special: they are NEVER in-process per
// HIP-0106 solo-vault CDE. Their clients always resolve via
@@ -41,57 +58,282 @@ import (
// when no endpoint is configured.
func BuildDeps(cfg *Config) Deps {
logger := luxlog.New("cloud")
logger.Info("building deps",
logger.Info(
"building deps",
"brand", cfg.Brand,
"domain", cfg.Domain,
"iam_issuer", cfg.IAMIssuer,
"data_dir", cfg.DataDir,
"enabled", cfg.Enable,
)
deps := Deps{
Logger: logger,
Brand: cfg.Brand,
Domain: cfg.Domain,
DataDir: cfg.DataDir,
Logger: logger,
Brand: cfg.Brand,
Version: cfg.Version,
Env: cfg.Env,
Domain: cfg.Domain,
IAMIssuer: cfg.IAMIssuer,
DataDir: cfg.DataDir,
AIDefaultModel: cfg.AIDefaultModel,
AIFallbackModel: cfg.AIFallbackModel,
}
// For each subsystem: enabled → leave nil (Mount fills it); not
// enabled + endpoint → RPC client; not enabled + no endpoint →
// disabled stub.
deps.IAM = pickIAMClient(cfg, logger)
// disabled stub. The plain co-resident-or-RPC-or-disabled clients share
// ONE resolver (pick); KMS/AI/VFS keep bespoke pickers because their
// construction genuinely differs (embedded store / gateway preference /
// S3-admin backend). O11y's disabled stub is a no-op (telemetry going
// nowhere is normal), not fail-closed.
deps.IAM = pick(cfg, logger, "iam", "IAM", cfg.IAMZAPAddr, clients.IAMRPCAt, clients.DisabledIAM)
deps.KMS = pickKMSClient(cfg, logger)
deps.Base = pickBaseClient(cfg, logger)
deps.Base = pick(cfg, logger, "base", "Base", cfg.BaseZAPAddr, clients.BaseRPCAt, clients.DisabledBase)
deps.Commerce = pickCommerceClient(cfg, logger)
deps.AI = pickAIClient(cfg, logger)
deps.O11y = pickO11yClient(cfg, logger)
// Metering client BEFORE the AI client: deps.AI is wrapped in the metering
// decorator (the ONE inference gate+meter — no exempt path, no bypass, no
// side-channel key), which needs deps.Metering. nil-safe — an unconfigured
// commerce URL yields a !Enabled() client, so the wrap is a transparent
// pass-through and a dev deployment is never blocked.
deps.Metering = buildMeteringClient(cfg, logger)
wireTierReader(deps.Metering, logger)
// AI (completions, WRITE) and Embed (embeddings, READ-ONLY) are DISTINCT
// credentials by concern: completions never ride the read-only publishable
// (pk-) key — the gateway 403s a pk- key on any write endpoint — so deps.AI
// resolves to the M2M identity, while deps.Embed keeps the pk- key (correct
// least-privilege for a read-only call). Both meter through the ONE commerce path.
deps.AI = meteredAIClient(pickCompletionsClient(cfg, logger), deps)
deps.Embed = meteredAIClient(pickEmbedClient(cfg, logger), deps)
wireFinance(cfg, logger)
deps.O11y = pick(cfg, logger, "o11y", "O11y", cfg.O11yZAPAddr, clients.O11yRPCAt, clients.DisabledO11y)
deps.VFS = pickVFSClient(cfg, logger)
deps.MQ = pickMQClient(cfg, logger)
deps.MQ = pick(cfg, logger, "mq", "MQ", cfg.MQZAPAddr, clients.MQRPCAt, clients.DisabledMQ)
deps.Durable = buildDurability(cfg, logger)
// Payments and Vault never co-resident. Disabled stub when no
// endpoint, otherwise RPC.
deps.Payments = pickPaymentsClient(cfg, logger)
deps.Vault = pickVaultClient(cfg, logger)
// Runtime-mutable edge-policy store (/v1/gateway config plane), layered over
// the static env/flag defaults so an un-provisioned deployment behaves exactly
// as the static config until an operator PUTs an override. New always returns a
// working *Store (static-only if the SQLite file can't open), so the edge
// middleware is never left without a policy source — a store-open error is
// logged, not fatal.
gp, err := edge.New(cfg.DataDir, cfg.AdminOrg, staticEdgePolicy(cfg))
if err != nil {
logger.Warn("gateway policy store degraded to static-only", "err", err)
}
deps.GatewayPolicy = gp
return deps
}
// pickIAMClient returns the canonical IAMClient for this process.
// nil = enabled here, Mount will fill it. RPC = remote endpoint
// configured. Disabled = not enabled, no endpoint.
func pickIAMClient(cfg *Config, log luxlog.Logger) IAMClient {
if cfg.Enabled("iam") {
return nil
// staticEdgePolicy projects the static env/flag edge config into the boot-default
// policy the edge.Store layers runtime overrides on top of. A disabled
// per-IP limiter (CLOUD_EDGE_RATELIMIT=false) maps to PerIPRPM 0 (a live no-op).
func staticEdgePolicy(cfg *Config) edge.Policy {
p := edge.Policy{
CORSOrigins: cfg.CORSOrigins,
WindowSec: cfg.EdgeRateWindowSec,
}
if cfg.IAMZAPAddr != "" {
log.Info("deps.IAM → ZAP RPC", "addr", cfg.IAMZAPAddr)
return clients.IAMRPCAt(cfg.IAMZAPAddr)
if cfg.EdgeRateEnabled {
p.PerIPRPM = cfg.EdgeRatePerIP
}
return clients.DisabledIAM()
return p
}
// buildMeteringClient constructs the commerce metering client for BillingGate —
// the request-edge debit on every paid AI call.
//
// CO-RESIDENT (task #111): when commerce is folded in-process (Enabled("commerce")),
// the gate DEBITS the in-process commerce handler over commerceinproc's self-routing
// transport — a direct Go call, no socket to commerce.hanzo.svc:8001. The base is
// pinned NON-EMPTY (real CLOUD_COMMERCE_HTTP_URL, else the in-process placeholder) so
// the gate stays ENABLED even after the standalone + its env are retired — a metering
// gate that silently no-ops is a free-money hole, so it must never drop to
// "not configured" while commerce is co-resident. The transport resolves the handler
// lazily (published by commerce.Mount before any request), so building the client
// here (pre-MountAll) is fine.
//
// SPLIT-DEPLOY (unchanged): without co-residency an empty CommerceHTTPURL yields a
// not-Enabled() client (allow + no-op) and a set one speaks plain HTTP to the
// standalone, exactly as before. The token is KMS-sourced; never logged.
func buildMeteringClient(cfg *Config, log luxlog.Logger) *metering.Client {
base := cfg.CommerceHTTPURL
var httpClient metering.HTTPDoer
inProcess := cfg.Enabled("commerce")
if inProcess {
if base == "" {
base = commerceinproc.PlaceholderBase
}
httpClient = commerceinproc.Client(0) // in-process dispatch; no network timeout
}
m, err := metering.New(metering.Config{
BaseURL: base,
Token: cfg.CommerceServiceToken,
Org: cfg.Brand, // X-Org-Id default for S2S; per-request org overrides.
// Honor the documented METERING_TEST env: when "true", route every debit to
// commerce's TEST/sandbox books (fin.RecordUsage in.Test=true) so a staging /
// canary deployment records NO real money — and the usage-cap read (org.TestMode
// via SQUARE_ENVIRONMENT=sandbox) sees the SAME test books. Unset in prod → live,
// unchanged. Without this the flag was silently ignored (always live).
Test: strings.EqualFold(strings.TrimSpace(os.Getenv(metering.EnvTest)), "true"),
FailOpen: cfg.BillingFailOpen,
HTTPClient: httpClient, // nil off the co-resident path → metering builds its own
})
if err != nil {
// Only an unparseable URL reaches here. Fall back to a not-configured
// client (no-op gate) rather than failing boot over billing wiring.
log.Error("billing: invalid commerce URL, gate disabled", "err", err)
m, _ = metering.New(metering.Config{})
}
// Observe every cap-check fail-open (timeout / slow / broken commerce) — a cap that
// silently allows must never be silent. The completion still proceeds (fail-open).
metering.OnCapError = func(err error) {
log.Warn("spend-cap check failed open (allowing completion) — commerce authorize slow/unavailable", "err", err)
}
if m.Enabled() {
log.Info("billing gate enabled", "commerce", boolStr(inProcess, "in-process", "http:"+base), "fail_open", cfg.BillingFailOpen)
} else {
log.Info("billing gate disabled (no commerce URL)")
}
return m
}
func boolStr(b bool, t, f string) string {
if b {
return t
}
return f
}
// wireTierReader installs the embedded ai module's per-tier SKU gate reader so it
// resolves the caller's commerce subscription tier through the SAME co-resident
// commerce client the metering gate bills over — in-process (commerceinproc) when
// commerce is folded in, S2S HTTP with the service token otherwise — NEVER an authed
// self-call to the cloud edge. That self-call is the toothless-gate bug: the edge
// 401/403s a service call to /v1/billing/*, so the ai module's own HTTP lookup always
// returned "" in-cluster and every tier-gated SKU failed OPEN. This mirrors
// wireFinance's SetBalanceReader: cloud owns the co-resident read, ai stays
// transport-agnostic. Fail-safe is preserved — Client.Tier folds a commerce error or
// an unknown plan to "", which the gate treats as ALLOW, so a commerce blip never
// locks out a paying caller. No-op when commerce is unreachable (metering !Enabled),
// leaving ai's standalone HTTP fallback in place.
func wireTierReader(m *metering.Client, log luxlog.Logger) {
if m == nil || !m.Enabled() {
return
}
aiobject.SetTierReader(func(ctx context.Context, subject, namespace string) (string, error) {
return m.Tier(ctx, subject, namespace)
})
log.Info("ai per-tier SKU gate wired to co-resident commerce (in-process tier read, fail-safe)")
}
// wireFinance constructs the ONE in-process finance ledger (per-org SQLite
// double-entry prepaid wallet), publishes it for every money consumer to resolve by
// the narrow finance.Client, and installs the embedded ai router's balance-read +
// usage-debit hooks so the PREPAID gate dispatches DIRECTLY to it — a typed in-proc
// call, no HTTP, no socket. There is NO exempt path (hanzoai/ai >= v1.805.8): every
// principal is gated on a positive prepaid balance, fail-closed. MUST run before
// ai.Mount (the ai gate reads the hook per request; the hook must be installed first)
// — which BuildDeps guarantees (deps are built before MountAll).
func wireFinance(cfg *Config, log luxlog.Logger) {
if !cfg.Enabled("commerce") {
return // money layer not co-resident (split-deploy); ai falls back to HTTP.
}
fin := finance.New(cfg.DataDir)
finance.Publish(fin)
// Money is billed to the SUBJECT's wallet, inside the org's ledger.
//
// org = which ledger (the tenant's books)
// subject = which wallet in it (ai resolves it: a person => "org/name", an
// org-owned application/service key => the org's own account)
//
// So a personal account has a PERSONAL balance and a personal plan, and an org
// pays for what its applications and service keys spend — which is the product:
// sign up as yourself, then stand up an org whose users are your customers.
//
// Keying both hooks on the org collapsed every member onto the tenant's pool
// wallet: every new signup lives in "hanzo", so a brand-new $0 account read
// HANZO's balance and sailed through the gate — we enforced our own wallet.
//
// The invariant that must never break: the gate READ and the usage DEBIT key on
// the SAME wallet, or spend can outrun the balance that admitted it. Both use
// subject; keep them together. The gate reads a coarse cents balance (a >0
// threshold only); the DEBIT is 18-decimal-exact.
aiobject.SetBalanceReader(func(ctx context.Context, subject, namespace, currency string) (int64, error) {
bal, err := fin.Balance(ctx, namespace, subject, currency, false)
if err != nil {
return 0, err
}
return bal.Cents(), nil
})
// The DEBIT is exact: the ai module emits the cost as a decimal-USD string, parsed
// here to 18-decimal USD (1e-18) so a sub-cent call bills precisely and is never floored.
aiobject.SetUsageRecorder(func(ctx context.Context, u aiobject.UsageEvent) error {
amt, err := money.ParseUSD(u.USD)
if err != nil {
return err
}
return fin.RecordUsage(ctx, types.UsageInput{
Org: u.Namespace, Subject: u.Subject, Amount: amt,
Currency: u.Currency, Model: u.Model, Provider: u.Provider, RequestID: u.RequestID,
})
})
log.Info("finance ledger wired (per-subject wallet in the org ledger, 18-decimal-exact, fail-closed)", "dataDir", cfg.DataDir)
}
// pick resolves one inter-subsystem client under the HIP-0106 wiring rule shared
// by every co-resident-capable dependency: enabled in THIS process → zero value
// (nil) so the subsystem's own Mount installs the in-process client; not enabled
// but a ZAP endpoint is configured → an RPC client at that endpoint; neither →
// the fail-closed/no-op disabled stub. name is the enable-list id; label is the
// deps.<X> log tag; rpc/disabled are the client's typed constructors. This is the
// ONE implementation of that rule — KMS/AI/VFS opt out with bespoke pickers only
// because their construction genuinely differs.
func pick[T any](cfg *Config, log luxlog.Logger, name, label, zapAddr string, rpc func(string) T, disabled func() T) T {
if cfg.Enabled(name) {
var zero T // enabled here → Mount fills deps.<label>
return zero
}
if zapAddr != "" {
log.Info("deps."+label+" → ZAP RPC", "addr", zapAddr)
return rpc(zapAddr)
}
return disabled()
}
// pickKMSClient resolves deps.KMS. When the kms subsystem is co-resident
// (Enabled("kms")) it returns the IN-PROCESS Client backed by the embedded
// luxfi/kms SecretStore under CLOUD_DATA_DIR — no external RPC. A store-open
// failure is NOT fatal to the whole binary: it falls back to the disabled stub
// (fail-closed) and logs, so a bad data dir degrades KMS rather than crashing
// every subsystem. Absent co-residency the legacy ZAP-RPC + disabled fallbacks
// apply (out-of-process KMS, or not wired).
//
// The subsystem id is "kms" (clients/kms registers it with cloud.HealthOwner so
// the generic liveness route never shadows its real /v1/kms/health, and registers
// the client factory this gate calls); this gate keys on the same id so "enabled"
// is one concept.
func pickKMSClient(cfg *Config, log luxlog.Logger) KMSClient {
if cfg.Enabled("kms") {
return nil
// The embedded-client constructor is registered by clients/kms in init()
// (RegisterKMSClientFactory). cloud never imports clients/kms, so the KMS
// library and its /v1/kms subsystem live in one package with no cloud⇄kms
// import cycle. Absent the registration (clients/kms not linked into this
// binary) KMS fails closed rather than pretending to host secrets.
if kmsClientFactory == nil {
log.Error("deps.KMS: kms enabled but no client factory registered (clients/kms not linked); failing closed")
return clients.DisabledKMS()
}
c, err := kmsClientFactory(cfg, log)
if err != nil {
log.Error("deps.KMS: embedded KMS unavailable, failing closed", "err", err)
return clients.DisabledKMS()
}
return c
}
if cfg.KMSZAPAddr != "" {
log.Info("deps.KMS → ZAP RPC", "addr", cfg.KMSZAPAddr)
@@ -100,20 +342,235 @@ func pickKMSClient(cfg *Config, log luxlog.Logger) KMSClient {
return clients.DisabledKMS()
}
func pickBaseClient(cfg *Config, log luxlog.Logger) BaseClient {
if cfg.Enabled("base") {
return nil
}
if cfg.BaseZAPAddr != "" {
log.Info("deps.Base → ZAP RPC", "addr", cfg.BaseZAPAddr)
return clients.BaseRPCAt(cfg.BaseZAPAddr)
}
return clients.DisabledBase()
// kmsClientFactory constructs the embedded in-process KMS client from cloud
// Config. clients/kms registers it in init(); pickKMSClient calls it so cloud
// depends on the KMSClient interface + this hook, never the concrete kms package
// — the same inversion the subsystem Registry already uses (cloud mounts every
// subsystem it never imports). Exactly one registration.
var kmsClientFactory func(cfg *Config, log luxlog.Logger) (KMSClient, error)
// RegisterKMSClientFactory installs the embedded-KMS constructor. clients/kms
// calls this from its init(); it is the ONE inversion point that lets the KMS
// library and its /v1/kms subsystem share one package with no cloud⇄kms cycle.
func RegisterKMSClientFactory(f func(cfg *Config, log luxlog.Logger) (KMSClient, error)) {
kmsClientFactory = f
}
// ---- git-push-to-deploy ----
// GitPushEvent describes a push that just landed on the embedded git server: the
// org, the repo, the branch that moved, and its new tip commit. CloneURL is the
// canonical clone URL of that repo (https://<host>/v1/git/<org>/<repo>.git) — the
// exact value an Application's RepoURL carries — so the builder can resolve which
// app (if any) tracks this branch and needs a rebuild.
type GitPushEvent struct {
Org string
Project string
Repo string
Branch string
Commit string
CloneURL string
}
// pushBuilder is the registered git-push-to-deploy trigger. clients/platform
// installs it in Mount; clients/git calls OnGitPush after a push lands. The
// inversion keeps git⇄platform decoupled — git never imports platform — exactly
// like kmsClientFactory and the subsystem Registry. Exactly one registration.
var pushBuilder func(ctx context.Context, ev GitPushEvent) error
// RegisterPushBuilder installs the git-push-to-deploy trigger. clients/platform
// calls this from its Mount when co-resident; it is the ONE inversion point that
// lets the embedded git server launch a platform build with no git⇄platform cycle.
func RegisterPushBuilder(f func(ctx context.Context, ev GitPushEvent) error) {
pushBuilder = f
}
// OnGitPush fires the registered push-to-deploy trigger for a landed push. It is a
// no-op when no builder is registered (git server running without the platform
// subsystem co-resident). Best-effort by contract: the caller must never fail the
// push the client already committed just because a build could not be triggered.
func OnGitPush(ctx context.Context, ev GitPushEvent) error {
if pushBuilder == nil {
return nil
}
return pushBuilder(ctx, ev)
}
// ---- first-party service release (push→build→image→CR rollout) ----
// ServiceReleaseEvent describes a proven, clean-semver image ready to roll live on
// an operator-managed first-party service. It is the payload of the release seam
// that closes push→build→image→CR: after a build produces the image, the CR for
// this service is patched to it and the operator reconciles the Deployment.
//
// - Service is the target CR metadata.name (the repo/service name ⇒ CR name,
// mirroring universe's image-update.yml convention).
// - Image is the full registry ref (repository:tag); the tag MUST be clean
// semver (vX.Y.Z) — the releaser refuses every mutable/sha/suffixed form.
// - SHA is the source commit for provenance (optional; logged, never gated on).
type ServiceReleaseEvent struct {
Service string
Image string
SHA string
}
// serviceReleaser is the registered first-party CR-rollout seam. clients/paas
// (the owner of the hanzo.ai/v1 Service CR control plane) installs it in Mount; a
// proven build calls OnServiceRelease, which patches spec.image on the matching
// CR. The inversion keeps package cloud from importing clients/paas (which imports
// cloud) — the same idiom as pushBuilder / kmsClientFactory. Exactly one
// registration.
var serviceReleaser func(ctx context.Context, ev ServiceReleaseEvent) error
// RegisterServiceReleaser installs the first-party CR-rollout hook. clients/paas
// calls this from its Mount when co-resident; it is the ONE inversion point that
// lets a build-completion path roll a proven image onto its operator Service CR
// with no cloud⇄paas import cycle.
func RegisterServiceReleaser(f func(ctx context.Context, ev ServiceReleaseEvent) error) {
serviceReleaser = f
}
// ServiceReleaserRegistered reports whether a first-party CR-rollout hook is
// installed (the paas control plane is co-resident). A caller uses it to know
// whether OnServiceRelease actually patches a CR or is a no-op, so it can be
// honest about which rollout path took effect.
func ServiceReleaserRegistered() bool { return serviceReleaser != nil }
// OnServiceRelease rolls a proven image live by patching the matching hanzo.ai/v1
// Service CR's spec.image (the operator then reconciles the Deployment). It is a
// no-op when no releaser is registered (a binary without the paas control plane
// co-resident). The releaser enforces the clean-semver gate and CR-name
// resolution; this is only the dispatch seam.
func OnServiceRelease(ctx context.Context, ev ServiceReleaseEvent) error {
if serviceReleaser == nil {
return nil
}
return serviceReleaser(ctx, ev)
}
// ---- git lifecycle event stream ----
//
// One event, many subscribers. push-to-deploy (OnGitPush) is the deploy
// subscriber-of-record and stays exactly as it is; this seam generalizes the SAME
// inversion to N reactors (mirror-out, Slack-notify, …) so git/platform EMIT a
// lifecycle fact and never import the subscribers. It is deliberately SEPARATE
// from OnGitPush — the deploy path is single-registrant and synchronous, this
// stream is many-registrant and best-effort — so adding a reactor can never
// perturb push→deploy.
// LifecycleKind classifies a git lifecycle event. The value IS the wire name a
// subscription filters on.
type LifecycleKind string
const (
LifecyclePushLanded LifecycleKind = "push.landed"
LifecycleBuildStarted LifecycleKind = "build.started"
LifecycleDeployLive LifecycleKind = "deploy.live"
LifecycleDeployFailed LifecycleKind = "deploy.failed"
)
// LifecycleEvent is one git lifecycle fact fanned out to every registered
// subscriber. A plain data value — values, not places:
// - Org/Project/Repo the tenant + repo the fact happened in (the routing key).
// - Branch/Before/After the ref that moved and its old→new tip (a push).
// - Pusher who pushed (best-effort; "" for a client-less push).
// - DeployID/Detail the deployment id + a human one-liner (a deploy transition).
// - Origin "" for a native push; the source host when the refs
// arrived via an inbound mirror sync — the loop-prevention seam that lets the
// outbound mirror subscriber suppress a re-mirror of refs it just pulled in.
type LifecycleEvent struct {
Kind LifecycleKind
Org string
Project string
Repo string
Branch string
Before string
After string
Pusher string
DeployID string
Detail string
Origin string
}
// RepoFromCloneURL extracts the repo name from a git clone URL (last path segment,
// ".git" stripped) — the repo component of the (org,project,repo) routing key that
// a deploy emitter derives from an app/project's linked RepoURL. The ONE place this
// derivation lives, shared by the platform + projects deploy paths (no per-package
// copy).
func RepoFromCloneURL(u string) string {
u = strings.TrimSuffix(strings.TrimSpace(u), "/")
u = strings.TrimSuffix(u, ".git")
if i := strings.LastIndexByte(u, '/'); i >= 0 {
return u[i+1:]
}
return u
}
// lifecycleSubscribers is the fan-out list. Registration happens at Mount
// (single-threaded, before any request is served), so a plain slice is correct:
// EmitLifecycle only ever ranges it after every subsystem's Mount has run.
var lifecycleSubscribers []func(ctx context.Context, ev LifecycleEvent)
// RegisterLifecycleSubscriber adds a git-lifecycle reactor. Every subsystem that
// reacts to a push/deploy (mirror-out, Slack-notify) registers ONE here at Mount;
// git/platform EMIT via EmitLifecycle. The inversion keeps the emitters from
// importing the subscribers — the same pattern as RegisterPushBuilder, but
// many-registrant.
func RegisterLifecycleSubscriber(fn func(ctx context.Context, ev LifecycleEvent)) {
if fn == nil {
return
}
lifecycleSubscribers = append(lifecycleSubscribers, fn)
}
// ResetLifecycleSubscribers clears the registry. TEST-ONLY seam (a test mounts and
// unmounts repeatedly); production registers once at Mount and never resets.
func ResetLifecycleSubscribers() { lifecycleSubscribers = nil }
// EmitLifecycle fans one event out to every registered subscriber, best-effort and
// NON-BLOCKING: each subscriber runs in its own goroutine on a cancel-immune
// context (the fact already happened — a request cancel must not abort the
// notify/mirror), so a slow reactor (a mirror push) can never delay the git/deploy
// path or another reactor. A panicking subscriber is contained so one bad reactor
// can neither crash the shared multi-tenant process nor starve the others; each
// subscriber logs its own errors.
func EmitLifecycle(ctx context.Context, ev LifecycleEvent) {
subs := lifecycleSubscribers
if len(subs) == 0 {
return
}
bg := context.WithoutCancel(ctx)
for _, fn := range subs {
go func(fn func(context.Context, LifecycleEvent)) {
defer func() { _ = recover() }()
fn(bg, ev)
}(fn)
}
}
// pickCommerceClient resolves deps.Commerce — the typed inter-subsystem client the
// entitlements/licensing tier calls (GetOrgConfig, CheckEntitlement). When the
// commerce subsystem is co-resident (Enabled("commerce")) it returns the IN-PROCESS
// client via the factory apps/commerce.go registers in init() — a direct Go
// call that reads the embedded commerce datastore (hanzoai/commerce MODULE, since
// the un-fork) + the @hanzo/plans vocabulary, no network hop (the HIP-0106
// co-resident default). The factory inversion stays because the concrete client
// (clients/commerceinproc) imports clients/plan, which imports cloud — a direct
// call here would be a package cycle. Absent the registration it fails closed
// rather than pretending.
//
// NETWORK PATH PRESERVED: absent co-residency the ZAP-RPC + disabled fallbacks apply
// (out-of-process commerce, or not wired), so the remote proxy seam
// (CLOUD_COMMERCE_ZAP_ADDR) is unchanged — the live default still selects the
// network client when commerce is not enabled in this process.
func pickCommerceClient(cfg *Config, log luxlog.Logger) CommerceClient {
if cfg.Enabled("commerce") {
return nil
if commerceClientFactory == nil {
log.Error("deps.Commerce: commerce enabled but no client factory registered (subsystems not linked); failing closed")
return clients.DisabledCommerce()
}
log.Info("deps.Commerce → in-process (embedded commerce)", "brand", cfg.Brand)
return commerceClientFactory(cfg, log)
}
if cfg.CommerceZAPAddr != "" {
log.Info("deps.Commerce → ZAP RPC", "addr", cfg.CommerceZAPAddr)
@@ -122,50 +579,286 @@ func pickCommerceClient(cfg *Config, log luxlog.Logger) CommerceClient {
return clients.DisabledCommerce()
}
func pickAIClient(cfg *Config, log luxlog.Logger) AIClient {
if cfg.Enabled("ai") {
return nil
// commerceClientFactory constructs the embedded in-process Commerce client.
// apps/commerce.go registers it in init(); pickCommerceClient calls it so
// package cloud depends on the CommerceClient interface + this hook, never the
// concrete commerceinproc package (whose entitlement client pulls clients/plan,
// which imports cloud — the hook is what keeps the package graph acyclic).
var commerceClientFactory func(cfg *Config, log luxlog.Logger) CommerceClient
// RegisterCommerceClientFactory installs the embedded-Commerce client constructor.
// apps/commerce.go calls this from its init(); exactly one registration.
func RegisterCommerceClientFactory(f func(cfg *Config, log luxlog.Logger) CommerceClient) {
commerceClientFactory = f
}
// publishableKey reports whether apiKey is a read-only PUBLISHABLE key (pk-). The
// Hanzo gateway 403s a publishable key on any WRITE endpoint — "Publishable keys
// can only access read-only endpoints … use a secret key (sk-)". So the COMPLETIONS
// resolver must refuse it (it would only 403 chat), while the EMBED resolver accepts
// it (embeddings ARE read-only). pk- is the IAM key family's read-only member
// (hk-/sk-/pk-/fw_/hz_; clients/admission). This ONE predicate is the split's crux:
// it kept the intermittent-403 bug — a pk- embed key riding the shared completions
// client — from ever recurring, wherever the key comes from.
func publishableKey(apiKey string) bool {
return strings.HasPrefix(strings.TrimSpace(apiKey), "pk-")
}
// pickCompletionsClient resolves deps.AI — the client the agents run path (and
// guide/crm/content/sitegen/code /ask) execute CHAT COMPLETIONS through. There is
// NO in-process "ai" mount that fills a nil deps.AI: inference is an external
// gateway, so this returns a concrete client, never nil.
//
// Completions are a WRITE endpoint: a read-only publishable (pk-) key 403s them. So
// this resolver NEVER rides a pk- key — that is the embed credential (pickEmbedClient).
// Preference order:
// 1. Static SECRET-key HTTP gateway when a base URL AND a completions-capable
// (non-pk-) static key are configured — an explicit operator override (sk-/hk-).
// A pk- key here is REFUSED (it would only 403 chat) and the resolver falls
// through to M2M — THE fix for the intermittent publishable-key 403 on bot replies.
// 2. M2M HTTP gateway when a base URL AND the binary's IAM identity are present
// (the durable Hanzo default): the client mints+refreshes a client-credentials
// token from IAM_CLIENT_ID/SECRET — no static key to rotate. Secret never logged.
// 3. ZAP RPC when an addr is configured (split-deploy of a future ai subsystem).
// 4. Fail-closed stub otherwise — a run records an honest error, never fakes one.
func pickCompletionsClient(cfg *Config, log luxlog.Logger) AIClient {
if cfg.AIBaseURL != "" && cfg.AIAPIKey != "" && !publishableKey(cfg.AIAPIKey) {
log.Info("deps.AI (completions) → HTTP gateway (static secret key)", "base_url", cfg.AIBaseURL, "default_model", cfg.AIDefaultModel)
return clients.AIHTTPAt(cfg.AIBaseURL, cfg.AIAPIKey, cfg.AIDefaultModel)
}
if cfg.AIAPIKey != "" && publishableKey(cfg.AIAPIKey) {
log.Info("deps.AI (completions) → refusing read-only publishable (pk-) key for chat; using M2M", "base_url", cfg.AIBaseURL)
}
if cfg.AIBaseURL != "" && cfg.AIAuthClientID != "" && cfg.AIAuthClientSecret != "" {
tokenURL := aiM2MTokenURL(cfg)
if tokenURL != "" {
log.Info("deps.AI (completions) → HTTP gateway (IAM M2M)", "base_url", cfg.AIBaseURL,
"token_url", tokenURL, "client_id", cfg.AIAuthClientID, "default_model", cfg.AIDefaultModel)
return clients.AIHTTPM2M(cfg.AIBaseURL, tokenURL, cfg.AIAuthClientID, cfg.AIAuthClientSecret, cfg.AIDefaultModel)
}
}
if cfg.AIZAPAddr != "" {
log.Info("deps.AI → ZAP RPC", "addr", cfg.AIZAPAddr)
log.Info("deps.AI (completions) → ZAP RPC", "addr", cfg.AIZAPAddr)
return clients.AIRPCAt(cfg.AIZAPAddr)
}
log.Info("deps.AI (completions) → disabled (no secret key, no IAM M2M identity, no gateway configured)")
return clients.DisabledAI()
}
func pickO11yClient(cfg *Config, log luxlog.Logger) O11yClient {
if cfg.Enabled("o11y") {
return nil
// pickEmbedClient resolves deps.Embed — the client code-index + KB knowledge run
// EMBEDDINGS through. Embeddings are a READ-ONLY endpoint, so the read-only
// publishable (pk-) key (CLOUD_AI_API_KEY ← cloud-ai-embed-key) is the CORRECT
// least-privilege credential here, and is used UNCHANGED — this path is deliberately
// not rewired. Preference order:
// 1. Static-key HTTP gateway when a base URL AND a static key are configured. The
// key (pk- or sk-) is a KMS-injected secret; only base URL + model are logged.
// 2. Otherwise share the completions resolution (M2M / ZAP / fail-closed) so a
// deploy with no dedicated embed key still indexes — no regression.
func pickEmbedClient(cfg *Config, log luxlog.Logger) AIClient {
if cfg.AIBaseURL != "" && cfg.AIAPIKey != "" {
log.Info("deps.Embed → HTTP gateway (static embed key)", "base_url", cfg.AIBaseURL, "default_model", cfg.AIDefaultModel)
return clients.AIHTTPAt(cfg.AIBaseURL, cfg.AIAPIKey, cfg.AIDefaultModel)
}
if cfg.O11yZAPAddr != "" {
log.Info("deps.O11y → ZAP RPC", "addr", cfg.O11yZAPAddr)
return clients.O11yRPCAt(cfg.O11yZAPAddr)
return pickCompletionsClient(cfg, log)
}
// aiM2MTokenURL resolves IAM's client_credentials endpoint the agent runner mints
// its M2M inference token at. It MUST be reachable FROM INSIDE THE CLUSTER: the
// runner runs in-cluster and the public issuer host (https://hanzo.id) is fronted
// by Cloudflare, which 403s a server-side (non-browser) loopback POST with edge
// error 1006 — so minting against the PUBLIC issuer URL fails and every
// POST /v1/agents/:ref/run 502s (root-caused 2026-07-04: in-cluster POST to
// https://hanzo.id/v1/iam/oauth/token → 403/1006, while http://iam.hanzo.svc/... → 200).
// This mirrors the KMS login-broker resolution (clients/kms) exactly — one
// split-horizon policy, no drift. Prefer, in order: an explicit override
// (CLOUD_AI_IAM_TOKEN_URL), the in-cluster IAM service base (IAM_URL — already
// wired to http://iam.hanzo.svc for JWKS), then the public issuer as a last resort
// (single-process / no split-horizon deploys). Returns "" only when no identity is
// resolvable, which keeps the M2M branch off (caller falls through to the stub).
func aiM2MTokenURL(cfg *Config) string {
if override := strings.TrimSpace(os.Getenv("CLOUD_AI_IAM_TOKEN_URL")); override != "" {
return override
}
// O11y disabled-stub is no-op (not fail-closed) — telemetry
// going nowhere is a normal mode.
return clients.DisabledO11y()
if base := strings.TrimRight(strings.TrimSpace(os.Getenv("IAM_URL")), "/"); base != "" {
return base + "/v1/iam/oauth/token"
}
if iss := strings.TrimRight(strings.TrimSpace(cfg.IAMIssuer), "/"); iss != "" {
return iss + "/v1/iam/oauth/token"
}
return ""
}
func pickVFSClient(cfg *Config, log luxlog.Logger) VFSClient {
if cfg.Enabled("vfs") {
return nil
}
// deps.VFS must NEVER be nil (R-7): files.go and any other VFS consumer call
// s.vfs.Put/Get/Delete unconditionally, so a nil here is a per-request 500
// (dishonest degradation) instead of a fail-closed 502. Unlike the
// nil-then-Mount-fills convention other subsystems use, nothing fills deps.VFS
// after MountAll (Mount receives deps by value), so we ALWAYS hand back a
// concrete client.
if cfg.VFSZAPAddr != "" {
log.Info("deps.VFS → ZAP RPC", "addr", cfg.VFSZAPAddr)
return clients.VFSRPCAt(cfg.VFSZAPAddr)
}
// Real blob backend (.97): the shared SeaweedFS S3 gateway — the canonical,
// key-based object store, reached with the SAME S3_ADMIN_* admin identity
// clients/s3 uses (s3admin, one construction). Present only when those creds
// are injected; a construction failure degrades to fail-closed rather than a
// nil deref. Team blobs (avatars/attachments) round-trip through this to the
// team-blobs bucket, org-scoped by the caller-built key prefix.
if admin := s3admin.New(); admin.Configured() {
v, err := clients.NewS3VFS(admin)
if err != nil {
log.Error("deps.VFS → S3 construction failed; falling back to fail-closed", "err", err)
return clients.DisabledVFS()
}
log.Info("deps.VFS → SeaweedFS S3", "bucket", clients.TeamBlobBucket)
return v
}
// No VFS endpoint and no S3 admin creds → fail-closed stub (R-7): Put/Get/Delete
// return a non-nil error → files answer 502, never a nil-deref 500.
return clients.DisabledVFS()
}
func pickMQClient(cfg *Config, log luxlog.Logger) MQClient {
if cfg.Enabled("mq") {
// durableBucket holds every org's HA-SQLite snapshot (and its writer lease). One
// bucket, keys laid out orgs/<slug>[/…]/<subsystem>.db per HIP-0302 — the durable
// twin of the on-disk DataDir layout.
//
// OPERATIONAL REQUIREMENTS the fence depends on (enforce in the SeaweedFS deployment,
// not in code):
//
// - Object versioning + a no-expiry / no-lifecycle-deletion policy on this prefix.
// The writer lease (orgs/<slug>/.owner) is the round's system of record; if the
// gateway silently drops or rolls back that object, a monotone round can reset and
// un-fence a zombie writer (Red M4). A local high-water-round floor per pod is the
// future in-process defense; the object lifecycle is the operational one.
// - RWO, per-writer PVCs for DataDir — NEVER an RWX shared volume (Red M5). Two pods
// on one DataDir corrupt SQLite regardless of this fence; single-writer here is the
// durable-copy fence, and per-pod RWO is the local-file guarantee the shard router
// already relies on (see shardrouter.go).
const durableBucket = "org-db"
// buildDurability constructs the deployment's HA-durability factory, or nil when the
// deployment has no object store to be durable against (dev/single-node — every
// OrgStore then stays local-only). It composes the SeaweedFS S3 If-Match
// ConditionalStore (the SAME s3admin identity deps.VFS uses), the writer membership
// over CLOUD_PEERS (the SAME set the shard router elects on, so the store-layer owner
// and the routed owner agree), and the per-org envelope Cipher rooted at the KMS
// master. Any construction failure fails SAFE to nil (local-only) rather than crash
// the boot; an encryption-capable build with no usable cipher is REFUSED — a build
// that promises encryption never ships plaintext snapshots to the object store.
func buildDurability(cfg *Config, log luxlog.Logger) *Durability {
// A multi-replica deployment REQUIRES the durable plane: with >1 writer, a per-org
// store that is not hydrate-on-open + fenced is the outage this exists to fix.
// disabledDurability logs at the severity the replica count warrants, so a
// misconfigured prod deployment is never SILENTLY non-durable (Red L2).
multiReplica := len(parsePeers(cfg.ShardPeers)) > 1
// Explicit opt-in: the object-store fence rests on the deployed SeaweedFS enforcing
// conditional-PUT (If-Match) atomically, which must be validated against the deployed
// version before it fences real tenant data (the takeover-fence staging gate). Until
// CLOUD_RESEARCH_DURABLE is set the store runs local-only — the shard router still
// pins each org to one writer, so this is not the rolling-deploy outage; only the
// cross-restart object-store snapshot waits for the opt-in.
if !cfg.ResearchDurable {
disabledDurability(log, multiReplica, "CLOUD_RESEARCH_DURABLE not set — HA object-store durability is opt-in pending the SeaweedFS conditional-PUT atomicity gate")
return nil
}
if cfg.MQZAPAddr != "" {
log.Info("deps.MQ → ZAP RPC", "addr", cfg.MQZAPAddr)
return clients.MQRPCAt(cfg.MQZAPAddr)
admin := s3admin.New()
if !admin.Configured() {
disabledDurability(log, multiReplica, "no S3 admin creds (S3_ADMIN_* unset)")
return nil
}
return clients.DisabledMQ()
client, err := admin.Client()
if err != nil {
disabledDurability(log, multiReplica, fmt.Sprintf("S3 client construction failed: %v", err))
return nil
}
ctx, cancel := context.WithTimeout(context.Background(), 10*time.Second)
if err := ensureDurableBucket(ctx, admin, client); err != nil {
// Non-fatal: the bucket likely already exists; a later ship/hydrate retries.
log.Warn("durability bucket ensure failed (continuing)", "bucket", durableBucket, "err", err)
}
cancel()
// Membership: CLOUD_PEERS (the shard router's set). A single-pod deployment with
// no peers is its own sole writer — still hydrate-on-open + fenced ship across a
// rolling restart.
self := firstNonEmptyStr(strings.TrimSpace(cfg.ShardSelf), hostnameOr("cloud-0"))
peers := parsePeers(cfg.ShardPeers)
if len(peers) == 0 {
peers = []org.Member{{ID: self, Addr: self}}
}
members := org.NewMembership(self, org.StaticSource(peers...), 5*time.Second)
_ = members.Start(context.Background()) // static source: the initial refresh populates Members()
cipher := durableCipher(cfg, log)
if cipher == nil && cek.Encrypting() {
// The master that satisfied cek must decode here too, so this is a genuine
// misconfig, not a dev path: never ship plaintext snapshots AND never silently
// drop durability — fail closed and log LOUDLY for the replica count.
disabledDurability(log, multiReplica, "encryption-capable build but no durable cipher (would ship plaintext snapshots)")
return nil
}
log.Info("durability enabled", "bucket", durableBucket, "self", self, "peers", len(peers), "encrypted", cipher != nil)
return org.NewDurability(org.NewS3ConditionalStore(client, durableBucket), members, cipher)
}
// disabledDurability records that the durable plane is OFF, at ERROR when the
// deployment is multi-replica (per-org stores then survive only via shard routing +
// per-pod RWO PVC; a lost/rescheduled PVC loses committed data — the operator MUST
// configure S3) and at INFO when single-replica/dev (local-only is the expected
// posture). One place, so no disabled path is silent on a deployment that needs HA.
func disabledDurability(log luxlog.Logger, multiReplica bool, why string) {
if multiReplica {
log.Error("DURABILITY DISABLED on a MULTI-REPLICA deployment — per-org stores survive only via shard routing + per-pod RWO PVC; a lost/rescheduled PVC loses committed data. Configure S3_ADMIN_* to enable the durable plane.", "reason", why)
return
}
log.Info("durability disabled — single-replica/dev, per-org stores stay local-only", "reason", why)
}
// ensureDurableBucket creates the durable bucket if absent (idempotent).
func ensureDurableBucket(ctx context.Context, admin s3admin.Admin, client *s3.Client) error {
ok, err := client.BucketExists(ctx, durableBucket)
if err != nil {
return err
}
if ok {
return nil
}
return client.MakeBucket(ctx, durableBucket, s3.MakeBucketOptions{Region: admin.Region()})
}
// durableCipher builds the per-org envelope Cipher from the base64 KMS master
// (CLOUD_KMS_MASTER_KEY_REF — the SAME key cek derives from). nil when no valid
// 32-byte master is configured (pure-Go dev → plaintext durable object, matching the
// plaintext local file).
func durableCipher(cfg *Config, log luxlog.Logger) *org.Cipher {
ref := strings.TrimSpace(cfg.KMSMasterKeyRef)
if ref == "" {
return nil
}
master, err := base64.StdEncoding.DecodeString(ref)
if err != nil {
log.Warn("durable cipher: KMS master key ref is not valid base64", "err", err)
return nil
}
c, err := org.NewCipher(master)
if err != nil {
log.Warn("durable cipher: invalid KMS master key", "err", err)
return nil
}
return c
}
// hostnameOr returns the OS hostname, or def when unavailable — a stable self id for
// a single-pod deployment that sets no CLOUD_POD_NAME.
func hostnameOr(def string) string {
if h, err := os.Hostname(); err == nil && h != "" {
return h
}
return def
}
func pickPaymentsClient(cfg *Config, log luxlog.Logger) PaymentsClient {
@@ -184,45 +877,53 @@ func pickVaultClient(cfg *Config, log luxlog.Logger) VaultClient {
return clients.DisabledVault()
}
// MountFunc is the canonical signature every subsystem exposes per
// HIP-0106. Each Hanzo Go service ships a top-level `Mount` symbol
// matching this signature; cmd/cloud/main.go imports the package and
// calls it.
type MountFunc func(app any, deps Deps) error // app is *zip.App; using any here to avoid an import cycle in pkg/cloud
// MountFunc is a subsystem's mount contract: register your routes on app, using
// deps for everything shared. Every subsystem in the fleet exports exactly this
// signature, so Wire references each one directly and the compiler checks it.
//
// app was once `any`, on the stated grounds that an external module (licensing)
// exposed func(any, Deps) error and narrowing would break it — while licensing
// said it used `any` to avoid an import cycle in pkg/cloud. Each cited the other,
// and the cycle could not exist: this package already imports zip, and zip does
// not import cloud. The `any` bought nothing and cost every subsystem a Typed()
// wrapper plus a runtime type assertion whose failure branch was unreachable.
type MountFunc func(app *zip.App, deps Deps) error
// MountSpec describes one subsystem registered for mounting. The Order
// is used when ordering matters for inter-subsystem deps (e.g. iam
// before authz before commerce).
// ShutdownFunc releases a subsystem's process-lifetime resources (background
// goroutines, open DB handles) on graceful shutdown. It must be idempotent and
// bounded — Serve calls it within the shutdown deadline. ctx carries that
// deadline so a slow teardown is cut off rather than hanging SIGTERM.
type ShutdownFunc func(ctx context.Context) error
// MountSpec describes one subsystem to mount. There is NO Order field: the slice
// position in apps.Wire() IS the mount order — the composition root lists
// subsystems in the exact sequence they mount (and, reversed, tear down), so order
// is data read top-to-bottom in one file, not ints scattered across the tree.
type MountSpec struct {
Name string
Order int
Mount MountFunc
Name string
Mount MountFunc
Shutdown ShutdownFunc // optional; nil means the subsystem has nothing to tear down.
// OwnsHealth marks a subsystem that serves its OWN GET /v1/<name>/health
// (a real, fail-closed probe). Serve's generic liveness loop skips these so
// its always-ok route never shadows the subsystem's real probe.
OwnsHealth bool
}
// Registry is the in-process subsystem registry. Subsystems register via
// init() functions in their respective packages OR cmd/cloud/main.go can
// explicitly enumerate them. Either pattern works.
var Registry []MountSpec
// Register adds a subsystem to the in-process registry.
func Register(name string, order int, mount MountFunc) {
Registry = append(Registry, MountSpec{Name: name, Order: order, Mount: mount})
}
// MountAll iterates the registry in order and calls Mount() on each
// enabled subsystem.
func MountAll(app any, cfg *Config, deps Deps) error {
// Sort registry by order — bubble sort, registry is tiny.
for i := 0; i < len(Registry); i++ {
for j := i + 1; j < len(Registry); j++ {
if Registry[j].Order < Registry[i].Order {
Registry[i], Registry[j] = Registry[j], Registry[i]
}
}
}
// MountAll mounts every ENABLED subsystem in specs, in slice order — the order is
// the composition root's (apps.Wire()); MountAll does NOT sort. app is the
// concrete *zip.App from Serve, handed to each MountFunc as itself.
//
// Teardown is wired HERE, at mount time: right after a subsystem mounts, its
// ShutdownFunc (if any) is registered via app.OnShutdown. zip drains those hooks
// LIFO — AFTER the listeners stop accepting and in-flight requests drain — so
// registration-at-mount yields reverse-mount teardown (a dependency mounted before
// its dependents is torn down after them) with no subsystem torn down while a
// request still uses it. Only ENABLED specs mount, so only they register a hook;
// teardown needs no separate enablement gate.
func MountAll(app *zip.App, specs []MountSpec, cfg *Config, deps Deps) error {
logger := deps.Logger
for _, spec := range Registry {
for _, spec := range specs {
if !cfg.Enabled(spec.Name) {
logger.Debug("subsystem disabled", "name", spec.Name)
continue
@@ -230,6 +931,12 @@ func MountAll(app any, cfg *Config, deps Deps) error {
if err := spec.Mount(app, deps); err != nil {
return fmt.Errorf("mount %s: %w", spec.Name, err)
}
// Register teardown as a zip shutdown hook. zip runs hooks LIFO after the
// drain (zip.App.Shutdown), so this reproduces the reverse-mount order the
// hand-rolled reverse-loop gave — without the teardown-before-drain race.
if spec.Shutdown != nil {
app.OnShutdown(spec.Shutdown)
}
logger.Info("mounted subsystem", "name", spec.Name)
}
return nil
+62
View File
@@ -0,0 +1,62 @@
package cloud
import "testing"
// TestAIM2MTokenURL pins the split-horizon resolution order for the agent-runner
// M2M token endpoint (the GAP that 502'd every POST /v1/agents/:ref/run: the
// public issuer host is Cloudflare-fronted and 403s an in-cluster loopback with
// edge error 1006). The runner must mint its token from an IN-CLUSTER URL. Order:
// explicit override → in-cluster IAM_URL → public IAMIssuer fallback.
func TestAIM2MTokenURL(t *testing.T) {
const tokenPath = "/v1/iam/oauth/token"
cases := []struct {
name string
override string // CLOUD_AI_IAM_TOKEN_URL
iamURL string // IAM_URL
iamIssuer string // cfg.IAMIssuer
want string
}{
{
name: "explicit override wins over everything",
override: "http://iam.internal:1234/custom/token",
iamURL: "http://iam.hanzo.svc",
// even a public issuer present must not be chosen
iamIssuer: "https://hanzo.id",
want: "http://iam.internal:1234/custom/token",
},
{
name: "in-cluster IAM_URL preferred over public issuer",
iamURL: "http://iam.hanzo.svc",
iamIssuer: "https://hanzo.id",
want: "http://iam.hanzo.svc" + tokenPath,
},
{
name: "trailing slash on IAM_URL is trimmed",
iamURL: "http://iam.hanzo.svc/",
iamIssuer: "https://hanzo.id",
want: "http://iam.hanzo.svc" + tokenPath,
},
{
name: "falls back to public issuer only when no in-cluster URL",
iamIssuer: "https://hanzo.id",
want: "https://hanzo.id" + tokenPath,
},
{
name: "empty when no identity is resolvable (keeps M2M branch off)",
want: "",
},
}
for _, tc := range cases {
t.Run(tc.name, func(t *testing.T) {
// t.Setenv restores prior values + prevents parallel interference.
t.Setenv("CLOUD_AI_IAM_TOKEN_URL", tc.override)
t.Setenv("IAM_URL", tc.iamURL)
cfg := &Config{IAMIssuer: tc.iamIssuer}
if got := aiM2MTokenURL(cfg); got != tc.want {
t.Fatalf("aiM2MTokenURL() = %q, want %q", got, tc.want)
}
})
}
}
+203
View File
@@ -0,0 +1,203 @@
package cloud_test
import (
"context"
"net"
"net/http"
"sync"
"sync/atomic"
"testing"
"time"
"github.com/hanzoai/cloud"
luxlog "github.com/luxfi/log"
"github.com/zap-proto/zip"
)
// noopMount mounts nothing: the fake specs below carry the behavior under test in
// their Shutdown, not their Mount.
func noopMount(*zip.App, cloud.Deps) error { return nil }
// freeAddr reserves an ephemeral loopback port and hands back its address; the
// listener is closed so the app under test can bind it.
func freeAddr(t *testing.T) string {
t.Helper()
ln, err := net.Listen("tcp", "127.0.0.1:0")
if err != nil {
t.Fatalf("reserve port: %v", err)
}
addr := ln.Addr().String()
_ = ln.Close()
return addr
}
// waitListening blocks until addr accepts a TCP connection (the app's Listen
// goroutine has bound it) or a short deadline elapses.
func waitListening(t *testing.T, addr string) {
t.Helper()
deadline := time.Now().Add(3 * time.Second)
for time.Now().Before(deadline) {
if c, err := net.DialTimeout("tcp", addr, 100*time.Millisecond); err == nil {
_ = c.Close()
return
}
time.Sleep(10 * time.Millisecond)
}
t.Fatalf("server never listened on %s", addr)
}
// TestMountAll_ShutdownHooksLIFOAfterDrain proves the OnShutdown teardown wiring:
// MountAll registers each ENABLED subsystem's ShutdownFunc as a zip shutdown hook,
// so on app.Shutdown they run (1) AFTER in-flight requests drain and (2) LIFO =
// reverse-mount order (a dependency mounted before its dependents is torn down
// after them). That is exactly the contract the deleted hand-rolled reverse-loop
// provided by hand — now owned by zip, minus the teardown-before-drain race.
func TestMountAll_ShutdownHooksLIFOAfterDrain(t *testing.T) {
app := zip.New(zip.Config{Logger: luxlog.NewNoOpLogger(), DisableStartupMessage: true})
// One monotonic tick stamps the ONLY two kinds of event we order against each
// other: the in-flight request finishing its drain, and each teardown hook.
var tick atomic.Int64
var mu sync.Mutex
teardown := map[string]int64{}
record := func(name string) cloud.ShutdownFunc {
return func(context.Context) error {
mu.Lock()
teardown[name] = tick.Add(1)
mu.Unlock()
return nil
}
}
// Mount order a, b, c ⇒ LIFO teardown must be c, b, a.
specs := []cloud.MountSpec{
{Name: "a", Mount: noopMount, Shutdown: record("a")},
{Name: "b", Mount: noopMount, Shutdown: record("b")},
{Name: "c", Mount: noopMount, Shutdown: record("c")},
}
cfg := &cloud.Config{Enable: []string{"a", "b", "c"}}
deps := cloud.Deps{Logger: luxlog.NewNoOpLogger()}
// A request that parks inside its handler until released, so the shutdown drain
// has something real to wait on. Its drain tick is stamped the instant the
// handler returns — i.e. the moment this request finishes draining.
entered := make(chan struct{})
release := make(chan struct{})
var drainTick int64
app.Get("/hold", func(c *zip.Ctx) error {
close(entered)
<-release
atomic.StoreInt64(&drainTick, tick.Add(1))
return c.JSON(http.StatusOK, map[string]bool{"ok": true})
})
if err := cloud.MountAll(app, specs, cfg, deps); err != nil {
t.Fatalf("MountAll: %v", err)
}
// Serve on a real loopback listener: an in-flight request over the HTTP
// transport is what zip's shutdown actually drains (closeServers → drain) in
// production — the path a listener-less test cannot exercise.
addr := freeAddr(t)
serveDone := make(chan error, 1)
go func() { serveDone <- app.Listen("http://" + addr) }()
waitListening(t, addr)
// Fire the request; it parks mid-handler with the connection held open.
reqDone := make(chan struct{})
go func() {
defer close(reqDone)
req, _ := http.NewRequest(http.MethodGet, "http://"+addr+"/hold", nil)
req.Close = true // no keep-alive: server drops the conn once the handler returns
client := &http.Client{Timeout: 30 * time.Second}
if resp, err := client.Do(req); err == nil {
_ = resp.Body.Close()
}
}()
<-entered // the request is now in-flight, parked mid-handler
// Shut down WHILE the request is in-flight. zip stops the listeners accepting,
// drains (blocking on our parked handler), THEN runs the hooks LIFO.
shutDone := make(chan error, 1)
go func() {
ctx, cancel := context.WithTimeout(context.Background(), 30*time.Second)
defer cancel()
shutDone <- app.ShutdownWithContext(ctx)
}()
// Barrier: with a request still in-flight, Shutdown MUST NOT complete — it is
// blocked in the drain. If it returns here, teardown ran without waiting for the
// drain (the exact race the OnShutdown move fixes).
select {
case <-shutDone:
t.Fatal("Shutdown completed while a request was still in-flight — teardown did not wait for the drain")
case <-time.After(150 * time.Millisecond):
}
// Let the handler finish so the drain can complete; hooks fire only after.
close(release)
if err := <-shutDone; err != nil {
t.Fatalf("ShutdownWithContext: %v", err)
}
<-reqDone
<-serveDone // Listen returns once the transport listener is closed
// (1) AFTER THE DRAIN: the in-flight request finished (drainTick) strictly
// before ANY teardown hook ran — no hook raced a request still using it.
dt := atomic.LoadInt64(&drainTick)
if dt == 0 {
t.Fatal("in-flight request never drained")
}
for name, tk := range teardown {
if tk < dt {
t.Fatalf("hook %q ran at tick %d, before the drain finished at tick %d — teardown raced the still-draining request", name, tk, dt)
}
}
// (2) LIFO = reverse mount order: c (mounted last) tears down first, a last.
if len(teardown) != 3 {
t.Fatalf("want 3 hooks run, got %d (%v)", len(teardown), teardown)
}
if !(teardown["c"] < teardown["b"] && teardown["b"] < teardown["a"]) {
t.Fatalf("teardown not LIFO: a=%d b=%d c=%d (want c<b<a)", teardown["a"], teardown["b"], teardown["c"])
}
}
// TestMountAll_ShutdownRegistration_EnablementAndNil proves MountAll registers a
// teardown hook ONLY for an ENABLED spec that HAS a ShutdownFunc: a disabled spec
// never mounts (so never registers a hook), and an enabled spec whose Shutdown is
// nil is skipped without panicking. This keeps the enablement axis and the nil
// guard from silently regressing now that teardown moved onto app.OnShutdown.
func TestMountAll_ShutdownRegistration_EnablementAndNil(t *testing.T) {
app := zip.New(zip.Config{Logger: luxlog.NewNoOpLogger(), DisableStartupMessage: true})
var mu sync.Mutex
var ran []string
record := func(name string) cloud.ShutdownFunc {
return func(context.Context) error {
mu.Lock()
ran = append(ran, name)
mu.Unlock()
return nil
}
}
specs := []cloud.MountSpec{
{Name: "enabled", Mount: noopMount, Shutdown: record("enabled")},
{Name: "disabled", Mount: noopMount, Shutdown: record("disabled")},
{Name: "nilsd", Mount: noopMount}, // enabled, but no Shutdown
}
cfg := &cloud.Config{Enable: []string{"enabled", "nilsd"}} // "disabled" omitted
if err := cloud.MountAll(app, specs, cfg, cloud.Deps{Logger: luxlog.NewNoOpLogger()}); err != nil {
t.Fatalf("MountAll: %v", err)
}
if err := app.Shutdown(); err != nil {
t.Fatalf("Shutdown: %v", err)
}
if len(ran) != 1 || ran[0] != "enabled" {
t.Fatalf("teardown hooks ran = %v, want [enabled] (disabled never mounts; nil Shutdown skipped)", ran)
}
}
+28
View File
@@ -0,0 +1,28 @@
package cloud_test
import (
"testing"
"github.com/hanzoai/cloud"
"github.com/zap-proto/zip"
)
// TestMountFunc_IsTheSubsystemSignature pins the registry's mount contract: the
// signature every subsystem exports IS a cloud.MountFunc, checked by the compiler.
//
// This file used to test cloud.Typed, the adapter that took a MountFunc's `any`
// app and asserted it back to *zip.App. Both of its tests went with it, and
// neither is a loss:
//
// - "Typed recovers the *zip.App" only ever proved the adapter handed through
// the value it was given. MountFunc now names *zip.App, so there is no
// recovery step left to get wrong.
// - "Typed fails closed on a wrong type" can no longer be written: passing
// "not-a-zip-app" to a MountFunc is a compile error, so the runtime branch it
// exercised does not exist. A test asserting a wrong type is rejected is
// precisely what a type already is.
//
// What remains is the only claim worth making, and the build enforces it.
func TestMountFunc_IsTheSubsystemSignature(t *testing.T) {
var _ cloud.MountFunc = func(*zip.App, cloud.Deps) error { return nil }
}
+43
View File
@@ -0,0 +1,43 @@
package cloud
import (
"context"
"errors"
"testing"
)
// TestOnServiceReleaseNoop proves the dispatch seam is a safe no-op when no
// releaser is registered (a binary without the paas control plane co-resident) —
// mirroring OnGitPush's contract.
func TestOnServiceReleaseNoop(t *testing.T) {
RegisterServiceReleaser(nil)
if ServiceReleaserRegistered() {
t.Fatal("ServiceReleaserRegistered() = true with no releaser registered")
}
if err := OnServiceRelease(context.Background(), ServiceReleaseEvent{Service: "cloud", Image: "ghcr.io/hanzoai/cloud:v1.0.0"}); err != nil {
t.Fatalf("OnServiceRelease with no releaser = %v, want nil no-op", err)
}
}
// TestOnServiceReleaseDispatch proves a registered releaser receives the exact
// event and its error propagates — the one inversion point paas installs.
func TestOnServiceReleaseDispatch(t *testing.T) {
var got ServiceReleaseEvent
sentinel := errors.New("boom")
RegisterServiceReleaser(func(_ context.Context, ev ServiceReleaseEvent) error {
got = ev
return sentinel
})
t.Cleanup(func() { RegisterServiceReleaser(nil) })
if !ServiceReleaserRegistered() {
t.Fatal("ServiceReleaserRegistered() = false after registration")
}
want := ServiceReleaseEvent{Service: "hanzo-app", Image: "ghcr.io/hanzoai/hanzo-app:v1.42.15", SHA: "abc1234"}
if err := OnServiceRelease(context.Background(), want); !errors.Is(err, sentinel) {
t.Fatalf("OnServiceRelease error = %v, want sentinel", err)
}
if got != want {
t.Fatalf("releaser received %+v, want %+v", got, want)
}
}
+39 -7
View File
@@ -6,25 +6,57 @@ import (
"github.com/hanzoai/cloud"
"github.com/hanzoai/cloud/clients"
// Blank import registers the kms subsystem's client factory (init) into cloud,
// so BuildDeps can build the in-process deps.KMS below. cloud itself never
// imports clients/kms (no cloud⇄kms cycle); this external test can.
_ "github.com/hanzoai/cloud/clients/kms"
)
// TestBuildDeps_EnabledLeavesNil verifies that BuildDeps leaves an
// enabled subsystem's Client field nil — the subsystem Mount() is
// responsible for filling it in.
// TestBuildDeps_EnabledLeavesNil verifies that BuildDeps leaves an enabled
// Mount-fills-it subsystem's Client field nil — the subsystem Mount() installs
// it. KMS is the exception (see TestBuildDeps_KMSEnabledIsInProcess): it is
// constructed eagerly in BuildDeps because its store must exist before any
// dependent subsystem mounts.
func TestBuildDeps_EnabledLeavesNil(t *testing.T) {
cfg := &cloud.Config{
Brand: "hanzo",
Domain: "api.hanzo.ai",
DataDir: "/tmp",
Enable: []string{"iam", "kms", "base", "commerce", "ai", "o11y", "vfs", "mq"},
DataDir: t.TempDir(),
Enable: []string{"iam", "base", "commerce", "ai", "o11y", "vfs", "mq"},
}
deps := cloud.BuildDeps(cfg)
if deps.IAM != nil {
t.Errorf("deps.IAM: enabled subsystem must leave Client nil, got %T", deps.IAM)
}
if deps.KMS != nil {
t.Errorf("deps.KMS: enabled subsystem must leave Client nil, got %T", deps.KMS)
}
// TestBuildDeps_KMSEnabledIsInProcess verifies the HIP-0106 "embed KMS in cloud"
// contract: when the kms subsystem is enabled, deps.KMS is a live
// in-process client (never nil, never a disabled stub) so other subsystems get a
// working KMS via direct Go dispatch with no RPC. Absent a master key it still
// resolves (health-only, fail-closed) — the point is that deps.KMS is populated.
func TestBuildDeps_KMSEnabledIsInProcess(t *testing.T) {
cfg := &cloud.Config{
Brand: "hanzo",
Domain: "api.hanzo.ai",
DataDir: t.TempDir(),
Enable: []string{"kms"},
}
deps := cloud.BuildDeps(cfg)
if deps.KMS == nil {
t.Fatal("deps.KMS: enabled kms must give an in-process client, got nil")
}
// It must NOT be the fail-closed disabled stub — that stub returns IsDisabled
// errors; an in-process client (no master key) returns a master-key error.
_, err := deps.KMS.GetSecret(context.Background(), "any")
if err == nil {
t.Fatal("GetSecret with no master key must fail closed")
}
if clients.IsDisabled(err) {
t.Errorf("deps.KMS resolved to the DISABLED stub, want the in-process client: %v", err)
}
}
+51
View File
@@ -0,0 +1,51 @@
package cloud
import (
"io"
"net/http"
"net/http/httptest"
"testing"
luxlog "github.com/luxfi/log"
"github.com/zap-proto/zip"
)
// CallerBearer relays the caller's OWN validated JWT bearer and nothing else: a JWT
// passes through unchanged, an opaque API key is not relayable, and no credential
// yields "". This is the token a downstream org-scoped service (the DNS forward
// head) re-validates to enforce tenant isolation across the hop.
func TestCallerBearer(t *testing.T) {
app := zip.New(zip.Config{Logger: luxlog.New("test")})
app.Get("/probe", func(c *zip.Ctx) error { return c.Bytes(200, []byte(CallerBearer(c))) })
probe := func(setup func(*http.Request)) string {
req := httptest.NewRequest(http.MethodGet, "/probe", nil)
if setup != nil {
setup(req)
}
res, err := app.Fiber().Test(req)
if err != nil {
t.Fatal(err)
}
b, _ := io.ReadAll(res.Body)
_ = res.Body.Close()
return string(b)
}
cases := []struct {
name string
setup func(*http.Request)
want string
}{
{"jwt bearer relayed unchanged", func(r *http.Request) { r.Header.Set("Authorization", "Bearer jwt.header.sig") }, "jwt.header.sig"},
{"X-Authorization fallback", func(r *http.Request) { r.Header.Set("X-Authorization", "Bearer x.y.z") }, "x.y.z"},
{"opaque hk- api key is NOT relayable", func(r *http.Request) { r.Header.Set("Authorization", "Bearer hk-secret") }, ""},
{"opaque sk- api key is NOT relayable", func(r *http.Request) { r.Header.Set("Authorization", "Bearer sk-secret") }, ""},
{"no credential yields empty", nil, ""},
}
for _, c := range cases {
if got := probe(c.setup); got != c.want {
t.Errorf("%s: CallerBearer = %q, want %q", c.name, got, c.want)
}
}
}
+830
View File
@@ -0,0 +1,830 @@
// Package cek is cloud's ONE encryption-at-rest gate for its per-subsystem
// SQLite stores. Every store opens its database through cek.Open — the single
// seam where a plaintext file is transparently migrated to SQLCipher and a keyed
// *sql.DB is returned — so "encrypted at rest" is a property of the open path,
// not something each of the ~30 stores must remember to do.
//
// THREAT MODEL. The DO block volume under /var/lib/cloud is provider-encrypted,
// so the residual exposure is a COPIED PV snapshot/backup or an in-cluster
// exec/PV read seeing plaintext customer PII (crm), the ledger (treasury), org
// wallet maps (wallets), the audit log, team/entitlements. cek removes that
// exposure: each file's pages are SQLCipher-encrypted under a per-database key
// that never leaves the process in the clear and is itself wrapped by the
// KMS-injected master key; the pre-migration plaintext copy is shredded once the
// encrypted store is proven readable. A lifted file is useless without the key.
//
// SCOPE / NON-GOALS. cek provides CONFIDENTIALITY at rest against the read-only
// exposure above (no master key ⇒ no plaintext). It is NOT integrity,
// authenticity, or anti-rollback against a PV-WRITE (node-compromise) adversary
// who can modify the volume: the per-file id lives in the (unauthenticated) .dek
// sidecar, so such an adversary could swap two of OUR OWN {db,.dek} pairs or
// replay an old snapshot. That is outside the stated model and is deliberately
// NOT defended here (a logical-id+epoch binding would add complexity for an
// out-of-model threat); revisit only if tenant-isolation-under-node-compromise
// is scoped in.
//
// ENVELOPE (the primitives live in github.com/hanzoai/sqlite/cek.go and are
// reused verbatim — one crypto implementation, KAT-gated there):
//
// - Each database has its OWN random 256-bit DEK (the SQLCipher page key),
// minted once at first touch and NEVER changed, so ciphertext pages are
// never rewritten.
// - Each database also gets a random 128-bit FILE ID, stored in the clear at
// the head of its <db>.dek sidecar. The KEK is derived from that id, NOT the
// file path: KEK = HKDF-SHA256(masterKey, lp("global") || lp(hex(fileID))).
// The id is intrinsic to the file and travels with the sidecar, so moving
// the data dir or changing CLOUD_DATA_DIR can never change the KEK and brick
// a store. RFC-5869 HKDF via x/crypto/hkdf — NOT luxfi/crypto/kdf (a QZMQ
// KeySchedule, not generic HKDF; using it would brick every store).
// - The DEK is wrapped AES-256-GCM under the KEK, bound to the same id as AAD.
// Sidecar = fileID(16) || wrapped-DEK. The raw DEK is never written.
// - Master-key ROTATION rewraps only the sidecar: the DEK and fileID are
// unchanged, so no page is rewritten and no file can be bricked.
//
// FAIL-SECURE. On an encryption-CAPABLE build (production is CGO + libsqlcipher)
// a missing master key is FATAL — the data plane refuses to open unencrypted,
// the same posture the KMS store takes. A key set on a NON-encrypting build is
// likewise fatal. An encrypted file whose sidecar is missing is refused. A
// migration whose encrypted copy does not reproduce the source's schema AND
// per-table content (a rowid-independent multiset hash, not just a row count)
// leaves the plaintext untouched and errors — the caller (MountAll) fails
// closed, so cloud never serves a half-migrated data plane.
package cek
import (
"context"
"crypto/rand"
"crypto/sha256"
"database/sql"
"encoding/base64"
"encoding/binary"
"encoding/hex"
"fmt"
"hash"
"math"
"os"
"path/filepath"
"sort"
"strings"
"sync"
"syscall"
"time"
sqlitedrv "github.com/hanzoai/sqlite"
)
// masterKeyEnv is the ONE variable that supplies the 32-byte KMS master key
// (base64), matching the operator Deployment and clients/kms. No second gate.
const masterKeyEnv = "CLOUD_KMS_MASTER_KEY_REF"
const (
dekSuffix = ".dek" // sidecar: fileID(16) || wrapped-DEK
lockSuffix = ".cek.lock" // per-db flock guarding first-touch + migration
tmpSuffix = ".cek.tmp" // in-progress encrypted target (same volume → atomic rename)
plainBakSuffix = ".plain.bak" // transient pre-migration plaintext; SHREDDED after verified open
sqliteMagic = "SQLite format 3\x00" // 16-byte header of an UNENCRYPTED db
headerLen = 16
fileIDLen = 16 // random per-file KEK-derivation id, stored in the sidecar head
)
// principalType domain-separates cloud's platform databases from IAM's org/user
// stores in the shared HKDF namespace.
const principalType = sqlitedrv.PrincipalGlobal
var (
masterOnce sync.Once
masterKey []byte
masterErr error
masterOverride []byte
)
// SetMasterKey injects the 32-byte master key explicitly (cloud's boot resolves
// it once from cfg and hands it here), taking precedence over the environment.
// Call before the first Open. A wrong-length key is ignored so the env path can
// still apply.
func SetMasterKey(k []byte) {
if len(k) == 32 {
masterOverride = append([]byte(nil), k...)
}
}
// resolveMaster resolves the process master key exactly once:
//
// (key, nil) — 32-byte key AND an encryption-capable build → encrypt.
// (nil, nil) — no key AND a non-encrypting (pure-Go) build → dev/CI plaintext.
// (nil, error) — key malformed; OR key set on a non-encrypting build; OR NO key
// on an encryption-capable build. The last is the production
// fail-closed: a capable binary never silently ships plaintext.
func resolveMaster() ([]byte, error) {
masterOnce.Do(func() {
raw := masterOverride
if len(raw) == 0 {
b64 := strings.TrimSpace(os.Getenv(masterKeyEnv))
if b64 == "" {
if sqlitedrv.EncryptionAvailable() {
masterErr = fmt.Errorf("cek: %s is required on an encryption-capable build; "+
"refusing to open the data plane unencrypted (set the KMS master key, "+
"or run a pure-Go dev build)", masterKeyEnv)
}
return // pure-Go dev/CI: plaintext is expected (no codec linked)
}
decoded, err := base64.StdEncoding.DecodeString(b64)
if err != nil {
masterErr = fmt.Errorf("cek: %s is not valid base64: %w", masterKeyEnv, err)
return
}
raw = decoded
}
if len(raw) != 32 {
masterErr = fmt.Errorf("cek: master key must decode to 32 bytes, got %d", len(raw))
return
}
if !sqlitedrv.EncryptionAvailable() {
masterErr = fmt.Errorf("cek: %s is set but this build cannot encrypt (pure-Go sqlite); "+
"rebuild CGO_ENABLED=1 linked against libsqlcipher, or unset it for a dev build", masterKeyEnv)
return
}
masterKey = raw
})
return masterKey, masterErr
}
// Encrypting reports whether cek will encrypt at rest (a valid master key is
// configured on an encryption-capable build). cloud calls this once at boot for
// the posture log; a false result on a capable build means resolveMaster errored
// and the first store Open will fail closed.
func Encrypting() bool {
k, err := resolveMaster()
return err == nil && len(k) == 32
}
// Open returns a *sql.DB for the SQLite database at path, encrypted at rest when
// a master key is configured. It is the single drop-in replacement for
// sql.Open("sqlite", path) across every cloud store.
func Open(path string) (*sql.DB, error) {
master, err := resolveMaster()
if err != nil {
return nil, err
}
if master == nil {
// Only reachable on a non-encrypting dev/CI build (a capable build with no
// key already errored above). Preserve the prior bare-path behavior.
return sql.Open("sqlite", path)
}
return openEncrypted(path, master)
}
func openEncrypted(path string, master []byte) (*sql.DB, error) {
unlock, err := flock(path)
if err != nil {
return nil, err
}
defer unlock()
if err := recoverInterrupted(path); err != nil {
return nil, err
}
var db *sql.DB
switch classify(path) {
case stateFresh:
db, err = createFresh(path, master)
case stateEncrypted:
db, err = openExisting(path, master)
default: // statePlaintext
db, err = migrateThenOpen(path, master)
}
if err != nil {
return nil, err
}
// No plaintext replica may survive a successful keyed open: shred any backup
// left by this (or a crashed prior) migration. THIS is the security objective.
shredPlainBak(path)
return db, nil
}
type fileState int
const (
stateFresh fileState = iota // absent or too small to be a real db → mint
statePlaintext // "SQLite format 3\0" header → migrate
stateEncrypted // db-sized, non-magic header → SQLCipher, open via sidecar
)
func classify(path string) fileState {
fi, err := os.Stat(path)
if err != nil || fi.Size() < headerLen {
return stateFresh
}
if isPlaintextHeader(path) {
return statePlaintext
}
return stateEncrypted
}
func isPlaintextHeader(path string) bool {
f, err := os.Open(path)
if err != nil {
return false
}
defer func() { _ = f.Close() }()
var hdr [headerLen]byte
if _, err := f.ReadAt(hdr[:], 0); err != nil {
return false
}
return string(hdr[:]) == sqliteMagic
}
// ── sidecar: fileID(16) || wrapped-DEK ───────────────────────────────────────
// mintSidecar generates a fresh fileID + DEK, wraps the DEK under the id-derived
// KEK, and returns the DEK and the sidecar bytes to persist.
func mintSidecar(master []byte) (dek, sidecar []byte, err error) {
fileID := make([]byte, fileIDLen)
if _, err = rand.Read(fileID); err != nil {
return nil, nil, fmt.Errorf("cek: generate file id: %w", err)
}
kek, aad, err := deriveFor(master, fileID)
if err != nil {
return nil, nil, err
}
defer zero(kek)
if dek, err = sqlitedrv.NewDEK(); err != nil {
return nil, nil, fmt.Errorf("cek: new DEK: %w", err)
}
wrapped, err := sqlitedrv.WrapDEK(kek, dek, aad)
if err != nil {
zero(dek)
return nil, nil, fmt.Errorf("cek: wrap DEK: %w", err)
}
sidecar = append(append(make([]byte, 0, fileIDLen+len(wrapped)), fileID...), wrapped...)
return dek, sidecar, nil
}
// unwrapSidecar reads the fileID from the sidecar head and unwraps the DEK under
// the id-derived KEK. A wrong master key, tampered blob, or truncated sidecar
// fails the GCM tag and errors — never a partial/garbage key.
func unwrapSidecar(master, sidecar []byte) ([]byte, error) {
if len(sidecar) <= fileIDLen {
return nil, fmt.Errorf("cek: sidecar too short (%d bytes)", len(sidecar))
}
fileID, wrapped := sidecar[:fileIDLen], sidecar[fileIDLen:]
kek, aad, err := deriveFor(master, fileID)
if err != nil {
return nil, err
}
defer zero(kek)
dek, err := sqlitedrv.UnwrapDEK(kek, wrapped, aad)
if err != nil {
return nil, fmt.Errorf("cek: unwrap DEK (wrong master key or corrupt sidecar): %w", err)
}
return dek, nil
}
// deriveFor derives the KEK and the wrap-AAD for a file id. Both bind to
// hex(fileID) so the id — not any path or config value — is the sole identity.
func deriveFor(master, fileID []byte) (kek, aad []byte, err error) {
id := hex.EncodeToString(fileID)
kek, err = sqlitedrv.DeriveKey(master, principalType, id)
if err != nil {
return nil, nil, fmt.Errorf("cek: derive KEK: %w", err)
}
return kek, sqlitedrv.PrincipalAAD(principalType, id), nil
}
// ── open paths ───────────────────────────────────────────────────────────────
func createFresh(path string, master []byte) (*sql.DB, error) {
dekPath := path + dekSuffix
if fileExists(dekPath) {
return openExisting(path, master) // a concurrent first-touch won the lock
}
dek, sidecar, err := mintSidecar(master)
if err != nil {
return nil, err
}
defer zero(dek)
if err := writeFileAtomic(dekPath, sidecar, 0o600); err != nil {
return nil, err
}
db, err := openKeyed(path, dek)
if err != nil {
return nil, fmt.Errorf("cek: create encrypted %q: %w", path, err)
}
return db, nil
}
func openExisting(path string, master []byte) (*sql.DB, error) {
dekPath := path + dekSuffix
sidecar, err := os.ReadFile(dekPath)
if err != nil {
return nil, fmt.Errorf("cek: read sidecar %q (encrypted db, refusing to open blind): %w", dekPath, err)
}
dek, err := unwrapSidecar(master, sidecar)
if err != nil {
return nil, err
}
defer zero(dek)
db, err := openKeyed(path, dek)
if err != nil {
return nil, fmt.Errorf("cek: open encrypted %q: %w", path, err)
}
return db, nil
}
// migrateThenOpen converts an existing PLAINTEXT database to SQLCipher without
// losing a row, then opens it. Crash-safe (plaintext is the source of truth
// until an atomic rename commits) and fail-secure (the swap happens only after
// the encrypted copy reproduces the source schema + per-table content hash +
// integrity_check, re-opened via the exact keyed path the app uses).
func migrateThenOpen(path string, master []byte) (*sql.DB, error) {
dekPath := path + dekSuffix
// Plaintext header ⇒ an earlier attempt did not commit: discard any stale
// sidecar/tmp and redo from the plaintext source of truth.
_ = os.Remove(dekPath)
tmp := path + tmpSuffix
removeDBFiles(tmp)
dek, sidecar, err := mintSidecar(master)
if err != nil {
return nil, err
}
defer zero(dek)
srcInv, err := exportPlaintext(path, tmp, dek)
if err != nil {
removeDBFiles(tmp)
return nil, err
}
if isPlaintextHeader(tmp) {
removeDBFiles(tmp)
return nil, fmt.Errorf("cek: migration of %q produced a plaintext file (SQLCipher not linked?)", path)
}
if err := verifyParity(tmp, dek, srcInv); err != nil {
removeDBFiles(tmp)
return nil, fmt.Errorf("cek: migration parity check failed for %q (plaintext left intact): %w", path, err)
}
// Commit. Order for crash-safety:
// 1. sidecar (the encrypted db's key),
// 2. plaintext → <db>.plain.bak,
// 3. delete the now-orphaned plaintext -wal/-shm (WAL was checkpoint-folded
// into the main file, so .plain.bak is complete; removing them now closes
// the window where a stale plaintext WAL sits beside the encrypted db),
// 4. atomic rename tmp → path.
// A crash between any two steps is resolved by recoverInterrupted on reboot.
if err := writeFileAtomic(dekPath, sidecar, 0o600); err != nil {
removeDBFiles(tmp)
return nil, err
}
if err := os.Rename(path, path+plainBakSuffix); err != nil {
removeDBFiles(tmp)
_ = os.Remove(dekPath)
return nil, fmt.Errorf("cek: preserve plaintext backup for %q: %w", path, err)
}
_ = os.Remove(path + "-wal")
_ = os.Remove(path + "-shm")
if err := os.Rename(tmp, path); err != nil {
_ = os.Rename(path+plainBakSuffix, path) // roll back
_ = os.Remove(dekPath)
return nil, fmt.Errorf("cek: swap encrypted %q into place: %w", path, err)
}
syncDir(filepath.Dir(path))
db, err := openKeyed(path, dek)
if err != nil {
return nil, fmt.Errorf("cek: open migrated %q: %w", path, err)
}
return db, nil // openEncrypted's tail shreds .plain.bak after this succeeds
}
// exportPlaintext opens the plaintext source, folds its WAL into the main file
// (crm.db/audit.db carry MB of live WAL), records the source inventory for the
// parity check, and copies every page into a fresh SQLCipher database at tmp via
// SQLCipher's own sqlcipher_export with the format compat pinned. The source is
// only read.
func exportPlaintext(path, tmp string, dek []byte) (inventory, error) {
ctx, cancel := context.WithTimeout(context.Background(), 30*time.Minute)
defer cancel()
src, err := sql.Open("sqlite", sqlitedrv.DSN(path, nil))
if err != nil {
return inventory{}, fmt.Errorf("cek: open plaintext %q: %w", path, err)
}
defer func() { _ = src.Close() }()
src.SetMaxOpenConns(1) // ATTACH + sqlcipher_export must run on ONE connection
conn, err := src.Conn(ctx)
if err != nil {
return inventory{}, fmt.Errorf("cek: acquire conn for %q: %w", path, err)
}
defer func() { _ = conn.Close() }()
if _, err := conn.ExecContext(ctx, "PRAGMA wal_checkpoint(TRUNCATE)"); err != nil {
return inventory{}, fmt.Errorf("cek: checkpoint %q: %w", path, err)
}
srcInv, err := readInventory(ctx, conn)
if err != nil {
return inventory{}, fmt.Errorf("cek: inventory source %q: %w", path, err)
}
// The DEK is crypto/rand hex — no injection surface; the path is a bound
// parameter. The reopen-via-openKeyed parity check downstream is the
// authoritative guard that the copy opens under the app's exact keyed path.
// The target is created at the runtime's SQLCipher format (the frozen
// libsqlcipher default), which is exactly what openKeyed reopens it under.
attach := fmt.Sprintf(`ATTACH DATABASE ? AS enc KEY "x'%x'"`, dek)
if _, err := conn.ExecContext(ctx, attach, tmp); err != nil {
return inventory{}, fmt.Errorf("cek: attach encrypted target: %w", err)
}
if _, err := conn.ExecContext(ctx, "SELECT sqlcipher_export('enc')"); err != nil {
_, _ = conn.ExecContext(ctx, "DETACH DATABASE enc")
return inventory{}, fmt.Errorf("cek: sqlcipher_export: %w", err)
}
if _, err := conn.ExecContext(ctx, "DETACH DATABASE enc"); err != nil {
return inventory{}, fmt.Errorf("cek: detach encrypted target: %w", err)
}
return srcInv, nil
}
// verifyParity re-opens the encrypted copy exactly as the running app will
// (openKeyed) and asserts: integrity_check ok, identical schema fingerprint, and
// — per table — identical row count AND identical rowid-independent content hash.
// The content hash (a commutative multiset sum of per-row hashes over the USER
// columns) is what backs the zero-loss claim: it catches any value change, NULL
// coercion, or row add/drop that count + schema + integrity_check miss, while
// correctly ignoring the benign implicit-rowid renumbering sqlcipher_export does.
// It runs BEFORE the atomic swap, so any discrepancy leaves the plaintext intact.
func verifyParity(tmp string, dek []byte, src inventory) error {
ctx, cancel := context.WithTimeout(context.Background(), 30*time.Minute)
defer cancel()
db, err := openKeyed(tmp, dek)
if err != nil {
return fmt.Errorf("reopen encrypted copy: %w", err)
}
defer func() { _ = db.Close() }()
db.SetMaxOpenConns(1)
if err := db.PingContext(ctx); err != nil {
return fmt.Errorf("ping encrypted copy (key/compat mismatch?): %w", err)
}
var ic string
if err := db.QueryRowContext(ctx, "PRAGMA integrity_check").Scan(&ic); err != nil {
return fmt.Errorf("integrity_check: %w", err)
}
if ic != "ok" {
return fmt.Errorf("integrity_check returned %q", ic)
}
conn, err := db.Conn(ctx)
if err != nil {
return fmt.Errorf("acquire verify conn: %w", err)
}
defer func() { _ = conn.Close() }()
dst, err := readInventory(ctx, conn)
if err != nil {
return fmt.Errorf("inventory encrypted copy: %w", err)
}
if dst.schema != src.schema {
return fmt.Errorf("schema fingerprint mismatch")
}
if len(dst.tables) != len(src.tables) {
return fmt.Errorf("table set mismatch: src %d tables, dst %d", len(src.tables), len(dst.tables))
}
for tbl, s := range src.tables {
d, ok := dst.tables[tbl]
if !ok {
return fmt.Errorf("table %q missing in encrypted copy", tbl)
}
if d.count != s.count {
return fmt.Errorf("row-count mismatch in %q: src %d, dst %d", tbl, s.count, d.count)
}
if d.content != s.content {
return fmt.Errorf("content-hash mismatch in %q (row values differ despite equal count)", tbl)
}
}
return nil
}
// inventory is the parity fingerprint: a schema hash plus, per table, a row count
// and a content hash.
type inventory struct {
schema [32]byte
tables map[string]tableStat
}
type tableStat struct {
count int64
content [32]byte // commutative multiset sum of per-row hashes over user columns
}
func readInventory(ctx context.Context, conn *sql.Conn) (inventory, error) {
rows, err := conn.QueryContext(ctx,
`SELECT type,name,COALESCE(tbl_name,''),COALESCE(sql,'') FROM sqlite_master `+
`WHERE name NOT LIKE 'sqlite_%' ORDER BY type,name`)
if err != nil {
return inventory{}, err
}
var schemaLines, tables []string
for rows.Next() {
var typ, name, tbl, ddl string
if err := rows.Scan(&typ, &name, &tbl, &ddl); err != nil {
_ = rows.Close()
return inventory{}, err
}
schemaLines = append(schemaLines, typ+"\x1f"+name+"\x1f"+tbl+"\x1f"+ddl)
if typ == "table" {
tables = append(tables, name)
}
}
if err := rows.Err(); err != nil {
_ = rows.Close()
return inventory{}, err
}
_ = rows.Close()
sort.Strings(schemaLines)
h := sha256.New()
for _, l := range schemaLines {
writeLP(h, []byte(l))
}
inv := inventory{tables: make(map[string]tableStat, len(tables))}
copy(inv.schema[:], h.Sum(nil))
for _, tbl := range tables {
st, err := tableContent(ctx, conn, tbl)
if err != nil {
return inventory{}, fmt.Errorf("content %q: %w", tbl, err)
}
inv.tables[tbl] = st
}
return inv, nil
}
// tableContent streams every row of a table and folds a per-row hash (over the
// user columns, faithfully distinguishing NULL / "" / 0 / storage class) into a
// commutative 256-bit sum. Order-independent (survives rowid-driven scan-order
// differences) and duplicate-safe (addition, not XOR). O(1) memory per table.
func tableContent(ctx context.Context, conn *sql.Conn, tbl string) (tableStat, error) {
q := `SELECT * FROM "` + strings.ReplaceAll(tbl, `"`, `""`) + `"`
rows, err := conn.QueryContext(ctx, q)
if err != nil {
return tableStat{}, err
}
defer func() { _ = rows.Close() }()
cols, err := rows.Columns()
if err != nil {
return tableStat{}, err
}
var st tableStat
scan := make([]any, len(cols))
ptrs := make([]any, len(cols))
for i := range scan {
ptrs[i] = &scan[i]
}
for rows.Next() {
if err := rows.Scan(ptrs...); err != nil {
return tableStat{}, err
}
rh := sha256.New()
for _, v := range scan {
encodeValue(rh, v)
}
var row [32]byte
copy(row[:], rh.Sum(nil))
addInto(&st.content, row)
st.count++
}
return st, rows.Err()
}
// encodeValue writes a type-tagged, length-prefixed, NULL-sentinel encoding of a
// scanned SQLite value so two logically-equal rows hash identically and a NULL
// never collides with "" or 0.
func encodeValue(h hash.Hash, v any) {
switch x := v.(type) {
case nil:
h.Write([]byte{0})
case int64:
var b [8]byte
binary.BigEndian.PutUint64(b[:], uint64(x))
h.Write([]byte{1})
h.Write(b[:])
case float64:
var b [8]byte
binary.BigEndian.PutUint64(b[:], math.Float64bits(x))
h.Write([]byte{2})
h.Write(b[:])
case bool:
h.Write([]byte{3})
if x {
h.Write([]byte{1})
} else {
h.Write([]byte{0})
}
case []byte:
h.Write([]byte{4})
writeLP(h, x)
case string:
h.Write([]byte{5})
writeLP(h, []byte(x))
case time.Time:
h.Write([]byte{6})
var b [8]byte
binary.BigEndian.PutUint64(b[:], uint64(x.UnixNano()))
h.Write(b[:])
default:
h.Write([]byte{9})
writeLP(h, []byte(fmt.Sprintf("%v", x)))
}
}
// writeLP writes an 8-byte big-endian length prefix then the bytes, so
// concatenations are unambiguous.
func writeLP(h hash.Hash, b []byte) {
var n [8]byte
binary.BigEndian.PutUint64(n[:], uint64(len(b)))
h.Write(n[:])
h.Write(b)
}
// addInto computes acc = (acc + row) mod 2^256, big-endian — the commutative,
// duplicate-safe multiset combiner.
func addInto(acc *[32]byte, row [32]byte) {
var carry uint16
for i := 31; i >= 0; i-- {
s := uint16(acc[i]) + uint16(row[i]) + carry
acc[i] = byte(s)
carry = s >> 8
}
}
// recoverInterrupted resumes a migration that crashed between the commit steps,
// keying only on files (no config). It also scrubs any stale plaintext -wal/-shm
// so a half-committed state can never leave one beside an encrypted db.
func recoverInterrupted(path string) error {
dekPath := path + dekSuffix
tmp := path + tmpSuffix
if fileExists(path) {
// If the live file is already encrypted, a leftover tmp is a dead
// migration attempt — discard it. (A plaintext live file is handled by
// migrateThenOpen, which clears tmp itself.)
if !isPlaintextHeader(path) {
removeDBFiles(tmp)
}
return nil
}
switch {
case fileExists(tmp) && fileExists(dekPath):
// Crashed after the sidecar+backup were written but before/during the swap
// rename: finish it. The sidecar matches tmp.
if err := os.Rename(tmp, path); err != nil {
return fmt.Errorf("cek: resume migration swap for %q: %w", path, err)
}
_ = os.Remove(path + "-wal")
_ = os.Remove(path + "-shm")
syncDir(filepath.Dir(path))
case fileExists(path + plainBakSuffix):
// Swap never happened; restore the plaintext original for a clean redo.
if err := os.Rename(path+plainBakSuffix, path); err != nil {
return fmt.Errorf("cek: restore plaintext backup for %q: %w", path, err)
}
removeDBFiles(tmp)
_ = os.Remove(dekPath)
}
return nil
}
// openKeyed opens a keyed SQLCipher database via the driver's ONE blessed keyed
// open (the key rides the URI so it is applied at sqlite3_open_v2, before mattn's
// pragma battery touches the header — a post-open PRAGMA key would be too late).
//
// CROSS-VERSION SAFETY. SQLCipher's on-disk format is fixed by the libsqlcipher
// major the arcd image links; that version is FROZEN in the Dockerfile (see the
// runbook) so an image rebuild cannot silently change the default cipher format
// and orphan a store. An at-open `cipher_compatibility` pin is NOT usable here
// (the URI param is silently ignored, and a post-open pragma runs after mattn has
// already read the header) — the version freeze is the control. If a mismatch
// ever occurs it FAILS CLOSED: openExisting returns "file is not a database" and
// MountAll aborts — never a silent downgrade or corruption.
func openKeyed(path string, dek []byte) (*sql.DB, error) {
db, err := sqlitedrv.OpenDB(path, dek)
if err != nil {
return nil, fmt.Errorf("cek: open keyed %q: %w", path, err) // no dsn (holds key)
}
return db, nil
}
// ── shred + boring helpers ───────────────────────────────────────────────────
// shredPlainBak overwrites and removes the transient pre-migration plaintext
// backup once the encrypted store is proven readable. Overwrite-then-remove is
// defense-in-depth (best-effort on a copy-on-write/journalled fs; the block
// volume is provider-encrypted regardless). Idempotent no-op when absent.
func shredPlainBak(path string) {
bak := path + plainBakSuffix
fi, err := os.Stat(bak)
if err != nil {
return
}
if f, err := os.OpenFile(bak, os.O_WRONLY, 0); err == nil {
overwrite(f, fi.Size())
_ = f.Sync()
_ = f.Close()
}
_ = os.Remove(bak)
}
func overwrite(f *os.File, size int64) {
const chunk = 1 << 20
buf := make([]byte, chunk)
for remaining := size; remaining > 0; {
n := int64(chunk)
if remaining < n {
n = remaining
}
if _, err := rand.Read(buf[:n]); err != nil {
return
}
if _, err := f.Write(buf[:n]); err != nil {
return
}
remaining -= n
}
}
func fileExists(p string) bool {
_, err := os.Stat(p)
return err == nil
}
func removeDBFiles(base string) {
for _, s := range []string{"", "-wal", "-shm"} {
_ = os.Remove(base + s)
}
}
func writeFileAtomic(dst string, data []byte, perm os.FileMode) error {
tmp := dst + ".tmp"
f, err := os.OpenFile(tmp, os.O_CREATE|os.O_WRONLY|os.O_TRUNC, perm)
if err != nil {
return fmt.Errorf("cek: create %q: %w", tmp, err)
}
if _, err := f.Write(data); err != nil {
_ = f.Close()
_ = os.Remove(tmp)
return fmt.Errorf("cek: write %q: %w", tmp, err)
}
if err := f.Sync(); err != nil {
_ = f.Close()
_ = os.Remove(tmp)
return fmt.Errorf("cek: sync %q: %w", tmp, err)
}
if err := f.Close(); err != nil {
_ = os.Remove(tmp)
return fmt.Errorf("cek: close %q: %w", tmp, err)
}
if err := os.Rename(tmp, dst); err != nil {
_ = os.Remove(tmp)
return fmt.Errorf("cek: rename %q→%q: %w", tmp, dst, err)
}
return nil
}
func syncDir(dir string) {
if d, err := os.Open(dir); err == nil {
_ = d.Sync()
_ = d.Close()
}
}
// flock takes an exclusive advisory lock on <path>.cek.lock, serializing
// first-touch and migration for the SAME database across processes/goroutines
// (different databases never contend). Returns an unlock func.
func flock(path string) (func(), error) {
lockPath := path + lockSuffix
if err := os.MkdirAll(filepath.Dir(lockPath), 0o700); err != nil {
return nil, fmt.Errorf("cek: create lock dir: %w", err)
}
f, err := os.OpenFile(lockPath, os.O_CREATE|os.O_RDWR, 0o600)
if err != nil {
return nil, fmt.Errorf("cek: open lock %q: %w", lockPath, err)
}
if err := syscall.Flock(int(f.Fd()), syscall.LOCK_EX); err != nil {
_ = f.Close()
return nil, fmt.Errorf("cek: acquire lock %q: %w", lockPath, err)
}
return func() {
_ = syscall.Flock(int(f.Fd()), syscall.LOCK_UN)
_ = f.Close()
}, nil
}
func zero(b []byte) {
for i := range b {
b[i] = 0
}
}
+439
View File
@@ -0,0 +1,439 @@
package cek
import (
"context"
"database/sql"
"encoding/hex"
"fmt"
"os"
"path/filepath"
"sync"
"testing"
sqlitedrv "github.com/hanzoai/sqlite"
)
// resetMaster clears the once-resolved master so a test can choose a posture.
// White-box tests only; production never resets.
func resetMaster(key []byte) {
masterOnce = sync.Once{}
masterKey = nil
masterErr = nil
masterOverride = nil
if key != nil {
SetMasterKey(key)
}
}
func testMaster(t *testing.T) []byte {
t.Helper()
k := make([]byte, 32)
for i := range k {
k[i] = byte(i*7 + 1)
}
return k
}
// requireCipher skips when the build cannot produce REAL ciphertext (a mis-linked
// cgo build silently writes plaintext), probing rather than trusting the flag.
// With SQLITE_REQUIRE_CODEC=1 (the Docker image build sets it) a would-be skip
// becomes a FAILURE, so the in-image gate is airtight standalone.
func requireCipher(t *testing.T) {
t.Helper()
skipOrFail := func(msg string) {
if os.Getenv("SQLITE_REQUIRE_CODEC") == "1" {
t.Fatal(msg)
}
t.Skip(msg)
}
if !sqlitedrv.EncryptionAvailable() {
skipOrFail("sqlite build cannot encrypt (pure-Go); run with CGO + libsqlcipher")
return
}
probe := filepath.Join(t.TempDir(), "probe.db")
dek, _ := sqlitedrv.NewDEK()
db, err := openKeyed(probe, dek)
if err != nil {
t.Fatalf("probe open: %v", err)
}
if _, err := db.Exec(`CREATE TABLE t(x)`); err != nil {
t.Fatalf("probe ddl: %v", err)
}
_ = db.Close()
if isPlaintextHeader(probe) {
skipOrFail("cgo build is NOT linked against libsqlcipher (keyed db is plaintext)")
return
}
}
// makePlaintextDB writes a genuine UNENCRYPTED SQLite db with known rows in WAL
// mode (exercising exportPlaintext's WAL fold), returning per-table row counts.
func makePlaintextDB(t *testing.T, path string, companies, contacts int) map[string]int64 {
t.Helper()
db, err := sql.Open("sqlite", path)
if err != nil {
t.Fatalf("open plaintext: %v", err)
}
for _, p := range []string{"PRAGMA journal_mode=WAL", "PRAGMA wal_autocheckpoint=0"} {
if _, err := db.Exec(p); err != nil {
t.Fatalf("pragma %q: %v", p, err)
}
}
if _, err := db.Exec(`
CREATE TABLE crm_companies(id TEXT PRIMARY KEY, org TEXT, name TEXT, arr INTEGER);
CREATE INDEX ix_co_org ON crm_companies(org);
CREATE TABLE crm_contacts(id TEXT PRIMARY KEY, org TEXT, email TEXT, note TEXT);`); err != nil {
t.Fatalf("ddl: %v", err)
}
for i := 0; i < companies; i++ {
if _, err := db.Exec(`INSERT INTO crm_companies VALUES(?,?,?,?)`,
fmt.Sprintf("co-%d", i), "maxpower", fmt.Sprintf("Co %d", i), int64(i*1000)); err != nil {
t.Fatalf("insert company: %v", err)
}
}
for i := 0; i < contacts; i++ {
// note is NULL on evens to exercise NULL fidelity in the content hash.
if i%2 == 0 {
_, err = db.Exec(`INSERT INTO crm_contacts(id,org,email) VALUES(?,?,?)`,
fmt.Sprintf("ct-%d", i), "maxpower", fmt.Sprintf("u%d@x.io", i))
} else {
_, err = db.Exec(`INSERT INTO crm_contacts VALUES(?,?,?,?)`,
fmt.Sprintf("ct-%d", i), "maxpower", fmt.Sprintf("u%d@x.io", i), "vip")
}
if err != nil {
t.Fatalf("insert contact: %v", err)
}
}
if !isPlaintextHeader(path) {
t.Fatalf("precondition: freshly created db is not plaintext")
}
_ = db.Close()
return map[string]int64{"crm_companies": int64(companies), "crm_contacts": int64(contacts)}
}
func rowCount(t *testing.T, db *sql.DB, table string) int64 {
t.Helper()
var n int64
if err := db.QueryRow(`SELECT COUNT(*) FROM ` + table).Scan(&n); err != nil {
t.Fatalf("count %s: %v", table, err)
}
return n
}
func firstBytes(t *testing.T, path string, n int) []byte {
t.Helper()
f, err := os.Open(path)
if err != nil {
t.Fatalf("open %s: %v", path, err)
}
defer func() { _ = f.Close() }()
b := make([]byte, n)
if _, err := f.ReadAt(b, 0); err != nil {
t.Fatalf("read %s: %v", path, err)
}
return b
}
// TestMigratePlaintextToCipher is the keystone: plaintext → SQLCipher with a
// ciphertext header, exact row parity, an unwrappable sidecar, readable data,
// and — per RED HIGH — NO surviving plaintext backup (shredded after verify).
func TestMigratePlaintextToCipher(t *testing.T) {
requireCipher(t)
dir := t.TempDir()
path := filepath.Join(dir, "crm.db")
want := makePlaintextDB(t, path, 37, 91)
resetMaster(testMaster(t))
db, err := Open(path)
if err != nil {
t.Fatalf("cek.Open (migrate): %v", err)
}
defer func() { _ = db.Close() }()
if isPlaintextHeader(path) {
t.Fatalf("FAIL: %s still plaintext after migration", path)
}
t.Logf("migrated header (hex): %s", hex.EncodeToString(firstBytes(t, path, 16)))
for tbl, n := range want {
if got := rowCount(t, db, tbl); got != n {
t.Errorf("row-count mismatch %s: want %d got %d", tbl, n, got)
}
}
// sidecar unwraps under the id-derived KEK (path plays no role).
sidecar, err := os.ReadFile(path + dekSuffix)
if err != nil {
t.Fatalf("read sidecar: %v", err)
}
if dek, err := unwrapSidecar(testMaster(t), sidecar); err != nil || len(dek) != 32 {
t.Fatalf("unwrap sidecar: dek=%d err=%v", len(dek), err)
}
// RED HIGH: the plaintext backup must be GONE (shredded), not lingering.
if fileExists(path + plainBakSuffix) {
t.Errorf("SECURITY: plaintext backup %s survived migration (must be shredded)", path+plainBakSuffix)
}
var name string
if err := db.QueryRow(`SELECT name FROM crm_companies WHERE id='co-5'`).Scan(&name); err != nil || name != "Co 5" {
t.Errorf("content check: got %q err %v", name, err)
}
}
// TestOpenIdempotent: a second Open of an already-migrated db is a no-op.
func TestOpenIdempotent(t *testing.T) {
requireCipher(t)
path := filepath.Join(t.TempDir(), "treasury.db")
want := makePlaintextDB(t, path, 5, 5)
resetMaster(testMaster(t))
db1, err := Open(path)
if err != nil {
t.Fatalf("first open: %v", err)
}
_ = db1.Close()
hdr1 := firstBytes(t, path, 16)
db2, err := Open(path)
if err != nil {
t.Fatalf("second open: %v", err)
}
defer func() { _ = db2.Close() }()
if isPlaintextHeader(path) {
t.Fatalf("db became plaintext on reopen")
}
for tbl, n := range want {
if got := rowCount(t, db2, tbl); got != n {
t.Errorf("reopen row-count %s: want %d got %d", tbl, n, got)
}
}
if string(hdr1) != string(firstBytes(t, path, 16)) {
t.Errorf("header changed on reopen (pages rewritten?)")
}
}
// TestFreshCreateEncrypted: a brand-new db is born encrypted.
func TestFreshCreateEncrypted(t *testing.T) {
requireCipher(t)
path := filepath.Join(t.TempDir(), "wallets.db")
resetMaster(testMaster(t))
db, err := Open(path)
if err != nil {
t.Fatalf("open fresh: %v", err)
}
if _, err := db.Exec(`CREATE TABLE w(addr TEXT, org TEXT)`); err != nil {
t.Fatalf("ddl: %v", err)
}
_ = db.Close()
if isPlaintextHeader(path) {
t.Fatalf("fresh db is plaintext")
}
if !fileExists(path + dekSuffix) {
t.Fatalf("fresh db has no sidecar")
}
}
// TestWrongMasterFailsClosed: a sidecar minted under one master cannot open under
// another — a lifted file + wrong key yields an error, never plaintext.
func TestWrongMasterFailsClosed(t *testing.T) {
requireCipher(t)
path := filepath.Join(t.TempDir(), "audit.db")
makePlaintextDB(t, path, 3, 3)
resetMaster(testMaster(t))
db, err := Open(path)
if err != nil {
t.Fatalf("migrate: %v", err)
}
_ = db.Close()
other := make([]byte, 32)
for i := range other {
other[i] = 0xAB
}
resetMaster(other)
if _, err := Open(path); err == nil {
t.Fatalf("SECURITY: opened encrypted db under the WRONG master key")
}
}
// TestDataDirMoveNoBrick (RED MED #2, PoC): the KEK binds to the sidecar fileID,
// NOT CLOUD_DATA_DIR, so changing/unsetting the data dir — or moving the file to
// a different path — must NOT brick the store.
func TestDataDirMoveNoBrick(t *testing.T) {
requireCipher(t)
dir1 := t.TempDir()
pathA := filepath.Join(dir1, "crm.db")
want := makePlaintextDB(t, pathA, 8, 8)
t.Setenv("CLOUD_DATA_DIR", dir1)
resetMaster(testMaster(t))
db, err := Open(pathA)
if err != nil {
t.Fatalf("migrate under dir1: %v", err)
}
_ = db.Close()
// Simulate a data-dir change AND a physical move to a different filename.
dir2 := t.TempDir()
pathB := filepath.Join(dir2, "moved.db")
copyFile(t, pathA, pathB)
copyFile(t, pathA+dekSuffix, pathB+dekSuffix)
t.Setenv("CLOUD_DATA_DIR", "/some/other/root") // the old brick trigger
db2, err := Open(pathB) // KEK from fileID → must still open
if err != nil {
t.Fatalf("AVAILABILITY: data-dir change bricked the store: %v", err)
}
defer func() { _ = db2.Close() }()
for tbl, n := range want {
if got := rowCount(t, db2, tbl); got != n {
t.Errorf("moved db row-count %s: want %d got %d", tbl, n, got)
}
}
}
// TestMissingKeyFatalOnCapableBuild (RED MED #3): an encryption-capable build
// with NO master key must FAIL CLOSED, never silently open plaintext. On a
// pure-Go build the same absence is dev-mode plaintext.
func TestMissingKeyFatalOnCapableBuild(t *testing.T) {
path := filepath.Join(t.TempDir(), "settings.db")
resetMaster(nil)
os.Unsetenv(masterKeyEnv)
_, err := Open(path)
if sqlitedrv.EncryptionAvailable() {
if err == nil {
t.Fatalf("SECURITY: capable build opened the data plane with NO master key (silent plaintext)")
}
if fileExists(path) {
t.Fatalf("SECURITY: a db file was created despite the fatal missing-key error")
}
} else {
if err != nil {
t.Fatalf("pure-Go dev build should allow plaintext when no key: %v", err)
}
}
}
// TestContentHashCatchesMutation (RED MED #4): the content hash catches a value
// change that row-count + schema + integrity_check all miss, AND does NOT
// false-positive on the benign implicit-rowid renumbering sqlcipher_export does.
func TestContentHashCatchesMutation(t *testing.T) {
requireCipher(t)
a := filepath.Join(t.TempDir(), "a.db")
b := filepath.Join(t.TempDir(), "b.db")
makePlaintextDB(t, a, 10, 10)
makePlaintextDB(t, b, 10, 10)
if inventoryOf(t, a).tables["crm_contacts"].content != inventoryOf(t, b).tables["crm_contacts"].content {
t.Fatalf("identical data produced different content hashes")
}
// Mutate ONE value in b (same row count, same schema, integrity stays ok).
base := inventoryOf(t, a).tables["crm_contacts"]
mutate(t, b, `UPDATE crm_contacts SET email='HIJACKED' WHERE id='ct-3'`)
after := inventoryOf(t, b).tables["crm_contacts"]
if after.count != base.count {
t.Fatalf("mutation changed the row count; test would not isolate content")
}
if base.content == after.content {
t.Fatalf("SECURITY: content hash did NOT catch a value mutation (count-blind gate)")
}
// Benign rowid renumber (delete+reinsert identical row, VACUUM) must NOT change it.
c := filepath.Join(t.TempDir(), "c.db")
makePlaintextDB(t, c, 10, 10)
before := inventoryOf(t, c).tables["crm_contacts"].content
mutate(t, c, `DELETE FROM crm_contacts WHERE id='ct-0'; INSERT INTO crm_contacts(id,org,email) VALUES('ct-0','maxpower','u0@x.io'); VACUUM`)
if before != inventoryOf(t, c).tables["crm_contacts"].content {
t.Errorf("content hash false-positived on a rowid renumber (re-inserted identical row)")
}
}
// TestCorruptSidecarFailsClosed (RED re-test #5, safety net): any undecryptable
// state — a corrupted or missing .dek sidecar, the family a libsqlcipher format
// mismatch would land in — FAILS CLOSED (errors), never silently opening
// plaintext or a garbage db. (Cross-version format stability itself is enforced
// by freezing the libsqlcipher version in the build; an at-open cipher_compat
// pin is infeasible with mattn's URI-key requirement — see openKeyed.)
func TestCorruptSidecarFailsClosed(t *testing.T) {
requireCipher(t)
path := filepath.Join(t.TempDir(), "audit.db")
makePlaintextDB(t, path, 4, 4)
resetMaster(testMaster(t))
db, err := Open(path)
if err != nil {
t.Fatalf("migrate: %v", err)
}
_ = db.Close()
// Flip a byte in the wrapped-DEK region of the sidecar → GCM tag fails.
sc, err := os.ReadFile(path + dekSuffix)
if err != nil {
t.Fatalf("read sidecar: %v", err)
}
sc[len(sc)-1] ^= 0xFF
if err := os.WriteFile(path+dekSuffix, sc, 0o600); err != nil {
t.Fatalf("write sidecar: %v", err)
}
resetMaster(testMaster(t))
if _, err := Open(path); err == nil {
t.Fatalf("SECURITY: opened an encrypted db with a corrupted DEK sidecar")
}
// A missing sidecar over an encrypted db must also refuse (never open blind).
if err := os.Remove(path + dekSuffix); err != nil {
t.Fatalf("rm sidecar: %v", err)
}
resetMaster(testMaster(t))
if _, err := Open(path); err == nil {
t.Fatalf("SECURITY: opened an encrypted db with NO DEK sidecar")
}
}
// ── helpers ──────────────────────────────────────────────────────────────────
func inventoryOf(t *testing.T, path string) inventory {
t.Helper()
db, err := sql.Open("sqlite", sqlitedrv.DSN(path, nil))
if err != nil {
t.Fatalf("open for inventory: %v", err)
}
defer func() { _ = db.Close() }()
db.SetMaxOpenConns(1)
conn, err := db.Conn(context.Background())
if err != nil {
t.Fatalf("conn: %v", err)
}
defer func() { _ = conn.Close() }()
inv, err := readInventory(context.Background(), conn)
if err != nil {
t.Fatalf("readInventory: %v", err)
}
return inv
}
func mutate(t *testing.T, path, sqlText string) {
t.Helper()
db, err := sql.Open("sqlite", sqlitedrv.DSN(path, nil))
if err != nil {
t.Fatalf("open mutate: %v", err)
}
defer func() { _ = db.Close() }()
if _, err := db.Exec(sqlText); err != nil {
t.Fatalf("mutate %q: %v", sqlText, err)
}
}
func copyFile(t *testing.T, src, dst string) {
t.Helper()
b, err := os.ReadFile(src)
if err != nil {
t.Fatalf("read %s: %v", src, err)
}
if err := os.WriteFile(dst, b, 0o600); err != nil {
t.Fatalf("write %s: %v", dst, err)
}
}
+100
View File
@@ -0,0 +1,100 @@
package cek
import (
"os"
"path/filepath"
"testing"
)
// The frozen fixture pins the SQLCipher on-disk FORMAT the data plane is written
// with. A committed encrypted store (created under the build's frozen
// libsqlcipher) is opened by TestFrozenFixtureOpens; if a future libsqlcipher
// upgrade changes the default cipher format, opening a store written under the
// old format FAILS — turning a silent prod brick into a red CI. (Build-time
// SQLITE_REQUIRE_CODEC only proves a FRESH db encrypts; it cannot detect a format
// change against pre-existing stores — the fixture is what does.)
const frozenCanary = "cek-format-canary-v1"
// frozenMaster is a FIXED, obviously-fake test key (0x00..0x1f) used only to wrap
// the committed fixture's DEK. Not a secret; never used in production.
func frozenMaster() []byte {
k := make([]byte, 32)
for i := range k {
k[i] = byte(i)
}
return k
}
const frozenDir = "testdata/frozen"
// TestGenerateFrozenFixture (re)writes the committed fixture. Gated on
// CEK_GEN_FIXTURE=1 and run by hand ONLY when the format is intentionally rev'd;
// the committed bytes are otherwise frozen.
func TestGenerateFrozenFixture(t *testing.T) {
if os.Getenv("CEK_GEN_FIXTURE") != "1" {
t.Skip("set CEK_GEN_FIXTURE=1 to regenerate the frozen fixture")
}
requireCipher(t)
if err := os.MkdirAll(frozenDir, 0o755); err != nil {
t.Fatal(err)
}
dbPath := filepath.Join(frozenDir, "store.db")
for _, s := range []string{"", dekSuffix, "-wal", "-shm"} {
_ = os.Remove(dbPath + s)
}
dek, sidecar, err := mintSidecar(frozenMaster())
if err != nil {
t.Fatal(err)
}
if err := os.WriteFile(dbPath+dekSuffix, sidecar, 0o600); err != nil {
t.Fatal(err)
}
h, err := openKeyed(dbPath, dek)
if err != nil {
t.Fatal(err)
}
if _, err := h.Exec(`CREATE TABLE frozen(id INTEGER PRIMARY KEY, note TEXT)`); err != nil {
t.Fatal(err)
}
if _, err := h.Exec(`INSERT INTO frozen VALUES(1,?)`, frozenCanary); err != nil {
t.Fatal(err)
}
_, _ = h.Exec(`PRAGMA wal_checkpoint(TRUNCATE)`) // fold into the main .db
_ = h.Close()
_ = os.Remove(dbPath + "-wal")
_ = os.Remove(dbPath + "-shm")
if isPlaintextHeader(dbPath) {
t.Fatal("generated fixture is plaintext")
}
t.Logf("wrote frozen fixture %s (+%s)", dbPath, dekSuffix)
}
// TestFrozenFixtureOpens opens the COMMITTED encrypted fixture (copied to temp so
// the committed bytes are never mutated) and reads its canary row. A libsqlcipher
// format change makes this fail — a red CI instead of a silent prod brick.
func TestFrozenFixtureOpens(t *testing.T) {
requireCipher(t)
src := filepath.Join(frozenDir, "store.db")
if !fileExists(src) {
t.Fatal("frozen fixture missing — regenerate with CEK_GEN_FIXTURE=1 and commit testdata/frozen/")
}
dir := t.TempDir()
dst := filepath.Join(dir, "store.db")
copyFile(t, src, dst)
copyFile(t, src+dekSuffix, dst+dekSuffix)
resetMaster(frozenMaster())
db, err := Open(dst)
if err != nil {
t.Fatalf("FORMAT DRIFT: frozen fixture failed to open (libsqlcipher format changed?): %v", err)
}
defer func() { _ = db.Close() }()
var note string
if err := db.QueryRow(`SELECT note FROM frozen WHERE id=1`).Scan(&note); err != nil {
t.Fatalf("read canary: %v", err)
}
if note != frozenCanary {
t.Fatalf("canary mismatch: got %q want %q", note, frozenCanary)
}
}
BIN
View File
Binary file not shown.
Binary file not shown.
+74
View File
@@ -0,0 +1,74 @@
package cli
// agent.go — `hanzo agent`: invoke a managed Hanzo agent with a task.
//
// An agent is a managed capability (its own /v1/agents subsystem, self-metered),
// NOT your artifact — so it is a peer verb of `hanzo run`, not a run kind. This is
// the HEADLESS flavor: a task/tool/code agent, no computer. The computer-using
// flavor (a booted desktop/terminal) is `hanzo bot` (see bot.go).
//
// hanzo agent run <ref> "<task>" → POST /v1/agents/:ref/run
//
// Thin client: one authenticated call over the IAM token + env.CloudURL, reusing
// cloudCall (run.go). See docs/architecture/compute-ladder.md.
import (
"fmt"
"io"
"net/http"
"strings"
"github.com/spf13/cobra"
)
// AgentRunReq is the POST /v1/agents/:ref/run body — a task for a managed agent.
type AgentRunReq struct {
Task string `json:"task"`
GPU bool `json:"gpu,omitempty"`
Timeout string `json:"timeout,omitempty"`
Repo string `json:"repo,omitempty"`
}
// AgentRunResult is the agent-run acceptance.
type AgentRunResult struct {
RunID string `json:"runId"`
Status string `json:"status"`
URL string `json:"url"`
}
func newAgentCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
cmd := &cobra.Command{
Use: "agent",
Short: "Invoke a managed Hanzo agent to run a task (headless)",
Long: "Invoke a managed agent by ref (e.g. a coding or tool agent) to run a task on\n" +
"Hanzo compute — metered per run. For a computer-using agent (booted desktop\n" +
"or terminal), use `hanzo bot`.",
}
cmd.AddCommand(newAgentRunCmd(envOf))
return cmd
}
func newAgentRunCmd(envOf func() *Env) *cobra.Command {
var req AgentRunReq
c := &cobra.Command{
Use: "run <ref> <task>",
Short: "Run a task with the named agent (POST /v1/agents/:ref/run)",
Args: cobra.MinimumNArgs(2),
RunE: func(cmd *cobra.Command, args []string) error {
env := envOf()
ref := args[0]
req.Task = strings.Join(args[1:], " ")
out := &AgentRunResult{}
if err := cloudCall(cmd.Context(), env, http.MethodPost, "/v1/agents/"+ref+"/run", &req, out); err != nil {
return err
}
return env.emit(out, func(w io.Writer) {
fmt.Fprintf(w, "%s\t%s\t%s\n", out.RunID, out.Status, out.URL)
})
},
}
c.Flags().BoolVar(&req.GPU, "gpu", false, "run the agent on a GPU node")
c.Flags().StringVar(&req.Timeout, "timeout", "", "max wall-clock (e.g. 30m)")
c.Flags().StringVar(&req.Repo, "repo", "", "a repo/checkout the agent operates on")
return c
}
+498
View File
@@ -0,0 +1,498 @@
package cli
import (
"bufio"
"context"
"encoding/base64"
"encoding/json"
"fmt"
"io"
"net/http"
"net/url"
"os"
"strings"
"time"
"github.com/spf13/cobra"
"golang.org/x/term"
)
// iamClient is a thin client over the Hanzo IAM OAuth2 surface at
// {issuer}/v1/iam/oauth/*. It speaks only the standard token + userinfo
// endpoints; it holds no IAM business logic.
type iamClient struct {
issuer string
clientID string
http *http.Client
}
func newIAMClient(issuer, clientID string) *iamClient {
return &iamClient{
issuer: strings.TrimRight(issuer, "/"),
clientID: clientID,
http: &http.Client{Timeout: 30 * time.Second},
}
}
// tokenResp is the OAuth2 token endpoint response (success or RFC-6749 error).
type tokenResp struct {
AccessToken string `json:"access_token"`
RefreshToken string `json:"refresh_token"`
TokenType string `json:"token_type"`
ExpiresIn int64 `json:"expires_in"`
Scope string `json:"scope"`
Error string `json:"error"`
ErrorDesc string `json:"error_description"`
}
// postForm performs an x-www-form-urlencoded POST to an oauth endpoint and
// decodes the token response, surfacing OAuth errors as Go errors.
func (c *iamClient) postForm(ctx context.Context, endpoint string, form url.Values) (*tokenResp, error) {
req, err := http.NewRequestWithContext(ctx, http.MethodPost, c.issuer+endpoint, strings.NewReader(form.Encode()))
if err != nil {
return nil, err
}
req.Header.Set("Content-Type", "application/x-www-form-urlencoded")
req.Header.Set("Accept", "application/json")
req.Header.Set("User-Agent", "hanzo-cli/"+Version)
resp, err := c.http.Do(req)
if err != nil {
return nil, err
}
defer resp.Body.Close()
body, _ := io.ReadAll(io.LimitReader(resp.Body, 1<<20))
var tr tokenResp
if err := json.Unmarshal(body, &tr); err != nil {
return nil, fmt.Errorf("iam %s: HTTP %d: %s", endpoint, resp.StatusCode, strings.TrimSpace(string(body)))
}
if tr.Error != "" {
return nil, fmt.Errorf("iam %s: %s: %s", endpoint, tr.Error, tr.ErrorDesc)
}
if tr.AccessToken == "" {
return nil, fmt.Errorf("iam %s: HTTP %d: no access_token in response", endpoint, resp.StatusCode)
}
return &tr, nil
}
// passwordGrant exchanges username+password for a token (the live IAM client
// supports password grant; device_code is hard-rejected server-side).
func (c *iamClient) passwordGrant(ctx context.Context, username, password, scope string) (*tokenResp, error) {
return c.postForm(ctx, "/v1/iam/oauth/access_token", url.Values{
"grant_type": {"password"},
"client_id": {c.clientID},
"username": {username},
"password": {password},
"scope": {scope},
})
}
// refreshGrant exchanges a refresh token for a fresh access token.
func (c *iamClient) refreshGrant(ctx context.Context, refreshToken string) (*tokenResp, error) {
return c.postForm(ctx, "/v1/iam/oauth/refresh_token", url.Values{
"grant_type": {"refresh_token"},
"client_id": {c.clientID},
"refresh_token": {refreshToken},
})
}
// decodeJWTClaims base64url-decodes a JWT's payload segment WITHOUT verifying
// the signature — used only to display the user's own token claims locally.
func decodeJWTClaims(token string) (map[string]any, error) {
parts := strings.Split(token, ".")
if len(parts) < 2 {
return nil, fmt.Errorf("not a JWT (need 3 dot-separated segments)")
}
payload, err := base64.RawURLEncoding.DecodeString(strings.TrimRight(parts[1], "="))
if err != nil {
return nil, fmt.Errorf("decode JWT payload: %w", err)
}
var claims map[string]any
if err := json.Unmarshal(payload, &claims); err != nil {
return nil, fmt.Errorf("parse JWT claims: %w", err)
}
return claims, nil
}
// claimString reads a string claim, tolerating absence.
func claimString(claims map[string]any, key string) string {
if v, ok := claims[key].(string); ok {
return v
}
return ""
}
// credsFromToken builds a Credentials carrying the token plus the identity
// fields decoded from its claims. expiresIn (token endpoint) wins for expiry;
// otherwise the JWT `exp` claim is used.
func credsFromToken(tr *tokenResp) *Credentials {
c := &Credentials{
AccessToken: tr.AccessToken,
RefreshToken: tr.RefreshToken,
TokenType: firstNonEmpty(tr.TokenType, "Bearer"),
}
if claims, err := decodeJWTClaims(tr.AccessToken); err == nil {
c.Subject = firstNonEmpty(claimString(claims, "email"), claimString(claims, "sub"))
c.Owner = claimString(claims, "owner")
if exp, ok := claims["exp"].(float64); ok {
c.Expiry = int64(exp)
}
}
if tr.ExpiresIn > 0 {
c.Expiry = time.Now().Add(time.Duration(tr.ExpiresIn) * time.Second).Unix()
}
return c
}
// ---------------------------------------------------------------------------
// Commands: login / logout / whoami, grouped under `auth`.
// ---------------------------------------------------------------------------
// loginFlags are shared by `hanzo login` and `hanzo auth login`.
type loginFlags struct {
username string
passwordStdin bool
token string
platformToken string
buildToken string
scope string
}
func runLogin(env *Env, lf *loginFlags, cmd *cobra.Command) error {
var creds *Credentials
switch {
case lf.token != "":
// Paste an externally-minted token. Decode claims for identity.
creds = credsFromToken(&tokenResp{AccessToken: lf.token, TokenType: "Bearer"})
case lf.username != "" || lf.passwordStdin:
// Password grant — kept for automation (--username/--password-stdin).
username := lf.username
if username == "" {
u, err := prompt(cmd, "Email: ")
if err != nil {
return err
}
username = u
}
password, err := readPassword(cmd, lf.passwordStdin)
if err != nil {
return err
}
iam := newIAMClient(env.IAMIssuer, env.ClientID)
tr, err := iam.passwordGrant(cmd.Context(), username, password, lf.scope)
if err != nil {
return err
}
creds = credsFromToken(tr)
default:
// The ONE interactive way: RFC 8628 device flow — link + QR + code,
// approve from any signed-in browser or phone. Headless-safe.
c, err := runDeviceLogin(cmd, env, lf.scope)
if err != nil {
return err
}
creds = c
}
// Optional machine-to-machine tokens for the platform control plane,
// stored with this identity so apps/deploy work post-login.
if lf.platformToken != "" {
creds.PlatformToken = lf.platformToken
}
if lf.buildToken != "" {
creds.BuildToken = lf.buildToken
}
// Persist under this identity's stable key and make it active. A second
// login as a different owner (e.g. admin vs hanzo for the same email, via a
// different --client-id) is stored beside the first, never over it;
// credentials.json mirrors whichever is active for legacy readers.
store, err := LoadIdentities()
if err != nil {
return err
}
key := store.Put(creds)
if err := store.Save(); err != nil {
return err
}
who := firstNonEmpty(creds.Subject, "(unknown)")
if creds.Owner != "" {
who += " @ " + creds.Owner
}
fmt.Fprintf(cmd.OutOrStdout(), "Logged in as %s [%s] (token expires %s)\n", who, key, shortTime(creds.Expiry))
return nil
}
func newLoginCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
lf := &loginFlags{}
cmd := &cobra.Command{
Use: "login",
Short: "Authenticate against Hanzo IAM and store a token",
Long: "Authenticate against Hanzo IAM (hanzo.id) and store the token in\n" +
"~/.hanzo/credentials.json (mode 0600). Default is the device flow: scan the\n" +
"QR (or open the link) from any signed-in device and approve — no password\n" +
"touches this terminal, works over ssh/headless. --username/--password-stdin\n" +
"keep the password grant for automation; --token stores an externally-minted\n" +
"token; --platform-token stores the platform control-plane service token\n" +
"needed by apps/deploy/clusters.",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error { return runLogin(envOf(), lf, cmd) },
}
bindLoginFlags(cmd, lf)
return cmd
}
func bindLoginFlags(cmd *cobra.Command, lf *loginFlags) {
f := cmd.Flags()
f.StringVarP(&lf.username, "username", "u", "", "IAM username/email")
f.BoolVar(&lf.passwordStdin, "password-stdin", false, "read the password from stdin (for automation)")
f.StringVar(&lf.token, "token", "", "store this access token directly (skip the password grant)")
f.StringVar(&lf.platformToken, "platform-token", "", "also store the platform control-plane service token")
f.StringVar(&lf.buildToken, "build-token", "", "also store the platform build-enqueue token")
f.StringVar(&lf.scope, "scope", "openid profile email", "OAuth scope")
}
func newLogoutCmd() *cobra.Command {
return &cobra.Command{
Use: "logout [<owner>]",
Short: "Remove a stored identity (the active one, or the named owner)",
Args: cobra.MaximumNArgs(1),
PersistentPreRunE: func(*cobra.Command, []string) error { return nil },
RunE: func(cmd *cobra.Command, args []string) error {
store, err := LoadIdentities()
if err != nil {
return err
}
if len(store.Identities) == 0 {
fmt.Fprintln(cmd.OutOrStdout(), "Not logged in.")
return nil
}
target := store.Active
if len(args) == 1 {
if target, err = store.resolve(args[0]); err != nil {
return err
}
}
store.Remove(target)
if err := store.Save(); err != nil {
return err
}
msg := "Logged out of " + target + "."
if store.Active != "" {
msg += " Active is now " + store.Active + "."
}
fmt.Fprintln(cmd.OutOrStdout(), msg)
return nil
},
}
}
// identityRow is the JSON/table projection of one stored identity.
type identityRow struct {
Key string `json:"key"`
Owner string `json:"owner"`
Subject string `json:"subject"`
Expiry int64 `json:"expiry,omitempty"`
Active bool `json:"active"`
}
// listIdentities renders every stored identity (active marked with *) — the
// shared body of `hanzo auth list` and `hanzo whoami --all`.
func listIdentities(env *Env, _ *cobra.Command) error {
store, err := LoadIdentities()
if err != nil {
return err
}
rows := make([]identityRow, 0, len(store.Identities))
for _, k := range store.keys() {
c := store.Identities[k]
rows = append(rows, identityRow{
Key: k, Owner: c.Owner, Subject: c.Subject, Expiry: c.Expiry,
Active: k == store.Active,
})
}
return env.emit(rows, func(w io.Writer) {
if len(rows) == 0 {
fmt.Fprintln(w, "No stored identities. Run `hanzo login`.")
return
}
tw := newTab(w)
fmt.Fprintln(tw, "ACTIVE\tKEY\tOWNER\tSUBJECT\tEXPIRES")
for _, r := range rows {
active := ""
if r.Active {
active = "*"
}
fmt.Fprintf(tw, "%s\t%s\t%s\t%s\t%s\n", active, r.Key, r.Owner, r.Subject, shortTime(r.Expiry))
}
tw.Flush()
})
}
func newWhoamiCmd(envOf func() *Env) *cobra.Command {
var verify, all bool
cmd := &cobra.Command{
Use: "whoami",
Short: "Show the active identity from the stored token (--all lists every stored identity)",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
env := envOf()
if all {
return listIdentities(env, cmd)
}
tok := env.accessToken()
if tok == "" {
return fmt.Errorf("not logged in: run `hanzo login`")
}
claims, err := decodeJWTClaims(tok)
if err != nil {
return err
}
if verify {
if err := verifyUserInfo(cmd.Context(), env, tok); err != nil {
return fmt.Errorf("token rejected by IAM: %w", err)
}
}
return env.emit(claims, func(w io.Writer) {
fmt.Fprintf(w, "email: %s\n", claimString(claims, "email"))
fmt.Fprintf(w, "name: %s\n", firstNonEmpty(claimString(claims, "displayName"), claimString(claims, "name")))
fmt.Fprintf(w, "org: %s\n", claimString(claims, "owner"))
fmt.Fprintf(w, "subject: %s\n", claimString(claims, "sub"))
fmt.Fprintf(w, "issuer: %s\n", claimString(claims, "iss"))
if exp, ok := claims["exp"].(float64); ok {
fmt.Fprintf(w, "expires: %s\n", shortTime(int64(exp)))
}
if verify {
fmt.Fprintln(w, "verified: yes (IAM userinfo accepted the token)")
}
})
},
}
cmd.Flags().BoolVar(&verify, "verify", false, "verify the token against the IAM userinfo endpoint")
cmd.Flags().BoolVar(&all, "all", false, "list every stored identity (active marked with *)")
return cmd
}
// verifyUserInfo calls the IAM userinfo endpoint with the bearer token; a 2xx
// means IAM accepts the token as live.
func verifyUserInfo(ctx context.Context, env *Env, token string) error {
req, err := http.NewRequestWithContext(ctx, http.MethodGet, env.IAMIssuer+"/v1/iam/oauth/userinfo", nil)
if err != nil {
return err
}
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("User-Agent", "hanzo-cli/"+Version)
resp, err := (&http.Client{Timeout: 20 * time.Second}).Do(req)
if err != nil {
return err
}
defer resp.Body.Close()
if resp.StatusCode/100 != 2 {
body, _ := io.ReadAll(io.LimitReader(resp.Body, 1<<16))
return fmt.Errorf("HTTP %d: %s", resp.StatusCode, strings.TrimSpace(string(body)))
}
return nil
}
// newAuthCmd is the `auth` group: login/logout/whoami plus `token` (print the
// stored access token, for piping into other tools).
func newAuthCmd(envOf func() *Env, gf *globalFlags) *cobra.Command {
cmd := &cobra.Command{
Use: "auth",
Short: "Manage authentication and stored identities",
}
tokenCmd := &cobra.Command{
Use: "token",
Short: "Print the active access token",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
tok := envOf().accessToken()
if tok == "" {
return fmt.Errorf("not logged in: run `hanzo login`")
}
fmt.Fprintln(cmd.OutOrStdout(), tok)
return nil
},
}
listCmd := &cobra.Command{
Use: "list",
Aliases: []string{"ls", "identities"},
Short: "List stored identities (active marked with *)",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error { return listIdentities(envOf(), cmd) },
}
switchCmd := &cobra.Command{
Use: "switch <owner>",
Aliases: []string{"use"},
Short: "Make a stored identity active (accepts an owner, or a full owner/name key)",
Args: cobra.ExactArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
store, err := LoadIdentities()
if err != nil {
return err
}
key, err := store.resolve(args[0])
if err != nil {
return err
}
store.Active = key
if err := store.Save(); err != nil {
return err
}
c := store.Identities[key]
who := firstNonEmpty(c.Subject, "(unknown)")
if c.Owner != "" {
who += " @ " + c.Owner
}
fmt.Fprintf(cmd.OutOrStdout(), "Switched to %s [%s] (token expires %s)\n", who, key, shortTime(c.Expiry))
return nil
},
}
cmd.AddCommand(newLoginCmd(envOf, gf), newLogoutCmd(), newWhoamiCmd(envOf), tokenCmd, listCmd, switchCmd)
return cmd
}
// ---------------------------------------------------------------------------
// Terminal helpers.
// ---------------------------------------------------------------------------
// prompt writes a prompt to stderr and reads a trimmed line from stdin.
func prompt(cmd *cobra.Command, label string) (string, error) {
fmt.Fprint(cmd.ErrOrStderr(), label)
r := bufio.NewReader(cmd.InOrStdin())
line, err := r.ReadString('\n')
if err != nil && err != io.EOF {
return "", err
}
return strings.TrimSpace(line), nil
}
// readPassword reads a password without echo from the terminal, or as a plain
// line from stdin when --password-stdin is set (automation) or stdin is not a
// terminal.
func readPassword(cmd *cobra.Command, fromStdin bool) (string, error) {
if fromStdin {
r := bufio.NewReader(cmd.InOrStdin())
line, err := r.ReadString('\n')
if err != nil && err != io.EOF {
return "", err
}
return strings.TrimRight(line, "\r\n"), nil
}
if f, ok := cmd.InOrStdin().(*os.File); ok && term.IsTerminal(int(f.Fd())) {
fmt.Fprint(cmd.ErrOrStderr(), "Password: ")
b, err := term.ReadPassword(int(f.Fd()))
fmt.Fprintln(cmd.ErrOrStderr())
return string(b), err
}
// Non-terminal stdin without --password-stdin: read a line so piped input
// still works, but nudge toward the explicit flag.
r := bufio.NewReader(cmd.InOrStdin())
line, err := r.ReadString('\n')
if err != nil && err != io.EOF {
return "", err
}
return strings.TrimRight(line, "\r\n"), nil
}
+385
View File
@@ -0,0 +1,385 @@
package cli
import (
"bytes"
"context"
"encoding/base64"
"encoding/json"
"net/http"
"net/http/httptest"
"strings"
"testing"
)
// makeJWT builds an unsigned JWT (alg=none) carrying claims — enough to test
// the local, signature-free claim decode the CLI uses for display.
func makeJWT(claims map[string]any) string {
hdr := base64.RawURLEncoding.EncodeToString([]byte(`{"alg":"none","typ":"JWT"}`))
p, _ := json.Marshal(claims)
return hdr + "." + base64.RawURLEncoding.EncodeToString(p) + ".sig"
}
func TestDecodeJWTClaims(t *testing.T) {
tok := makeJWT(map[string]any{"email": "z@hanzo.ai", "owner": "hanzo", "sub": "abc", "exp": float64(1783110016)})
claims, err := decodeJWTClaims(tok)
if err != nil {
t.Fatalf("decode: %v", err)
}
if claimString(claims, "email") != "z@hanzo.ai" || claimString(claims, "owner") != "hanzo" {
t.Fatalf("claims wrong: %+v", claims)
}
if _, err := decodeJWTClaims("not-a-jwt"); err == nil {
t.Fatalf("expected error for non-JWT")
}
}
func TestCredsFromToken(t *testing.T) {
tok := makeJWT(map[string]any{"email": "z@hanzo.ai", "owner": "hanzo", "exp": float64(2000000000)})
// expires_in present → wins over exp.
c := credsFromToken(&tokenResp{AccessToken: tok, RefreshToken: "r", ExpiresIn: 3600})
if c.Subject != "z@hanzo.ai" || c.Owner != "hanzo" || c.RefreshToken != "r" {
t.Fatalf("identity not extracted: %+v", c)
}
if c.Expiry == 2000000000 {
t.Fatalf("expires_in should win over exp claim")
}
// No expires_in → falls back to exp claim.
c2 := credsFromToken(&tokenResp{AccessToken: tok})
if c2.Expiry != 2000000000 {
t.Fatalf("exp claim fallback failed: %d", c2.Expiry)
}
}
func TestPasswordGrant(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/iam/oauth/access_token" {
t.Errorf("path = %s", r.URL.Path)
}
_ = r.ParseForm()
if r.Form.Get("grant_type") != "password" || r.Form.Get("client_id") != "hanzo-console" ||
r.Form.Get("username") != "z@hanzo.ai" || r.Form.Get("password") != "pw" {
t.Errorf("bad form: %v", r.Form)
}
_ = json.NewEncoder(w).Encode(map[string]any{
"access_token": makeJWT(map[string]any{"email": "z@hanzo.ai"}),
"token_type": "Bearer",
"expires_in": 3600,
"refresh_token": "r",
})
}))
defer srv.Close()
c := newIAMClient(srv.URL, "hanzo-console")
tr, err := c.passwordGrant(context.Background(), "z@hanzo.ai", "pw", "openid")
if err != nil {
t.Fatalf("passwordGrant: %v", err)
}
if tr.AccessToken == "" || tr.RefreshToken != "r" {
t.Fatalf("token resp bad: %+v", tr)
}
}
func TestPasswordGrantError(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
w.WriteHeader(400)
_ = json.NewEncoder(w).Encode(map[string]any{"error": "invalid_grant", "error_description": "bad password"})
}))
defer srv.Close()
c := newIAMClient(srv.URL, "hanzo-console")
_, err := c.passwordGrant(context.Background(), "u", "p", "openid")
if err == nil || !strings.Contains(err.Error(), "invalid_grant") {
t.Fatalf("expected invalid_grant error, got %v", err)
}
}
func TestRefreshGrant(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
_ = r.ParseForm()
if r.URL.Path != "/v1/iam/oauth/refresh_token" || r.Form.Get("grant_type") != "refresh_token" || r.Form.Get("refresh_token") != "rt" {
t.Errorf("bad refresh request: %s %v", r.URL.Path, r.Form)
}
_ = json.NewEncoder(w).Encode(map[string]any{"access_token": makeJWT(nil), "token_type": "Bearer"})
}))
defer srv.Close()
c := newIAMClient(srv.URL, "hanzo-console")
if _, err := c.refreshGrant(context.Background(), "rt"); err != nil {
t.Fatalf("refreshGrant: %v", err)
}
}
// runRoot executes the cobra root with args, returning stdout and any error.
// stderr is discarded; stdin is provided for password prompts.
func runRoot(t *testing.T, stdin string, args ...string) (string, error) {
t.Helper()
root := newRootCmd()
var out bytes.Buffer
root.SetOut(&out)
root.SetErr(new(bytes.Buffer))
root.SetIn(strings.NewReader(stdin))
root.SetArgs(args)
err := root.Execute()
return out.String(), err
}
func TestLoginCommandPasswordStdin(t *testing.T) {
sandbox(t)
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
_ = json.NewEncoder(w).Encode(map[string]any{
"access_token": makeJWT(map[string]any{"email": "z@hanzo.ai", "owner": "hanzo"}),
"token_type": "Bearer", "expires_in": 3600,
})
}))
defer srv.Close()
out, err := runRoot(t, "pw\n", "login", "-u", "z@hanzo.ai", "--password-stdin", "--iam-issuer", srv.URL)
if err != nil {
t.Fatalf("login: %v", err)
}
if !strings.Contains(out, "Logged in as z@hanzo.ai @ hanzo") {
t.Fatalf("login output: %q", out)
}
creds, _ := LoadCredentials()
if creds.AccessToken == "" || creds.Subject != "z@hanzo.ai" {
t.Fatalf("credentials not persisted: %+v", creds)
}
}
func TestLoginTokenPasteAndPlatformToken(t *testing.T) {
sandbox(t)
tok := makeJWT(map[string]any{"email": "ops@hanzo.ai", "owner": "hanzo"})
out, err := runRoot(t, "", "login", "--token", tok, "--platform-token", "svc-123")
if err != nil {
t.Fatalf("login --token: %v", err)
}
if !strings.Contains(out, "ops@hanzo.ai") {
t.Fatalf("login output: %q", out)
}
creds, _ := LoadCredentials()
if creds.AccessToken != tok || creds.PlatformToken != "svc-123" {
t.Fatalf("creds not stored: %+v", creds)
}
}
func TestWhoamiCommand(t *testing.T) {
sandbox(t)
creds := credsFromToken(&tokenResp{AccessToken: makeJWT(map[string]any{
"email": "z@hanzo.ai", "name": "z", "owner": "hanzo", "sub": "u-1", "iss": "https://hanzo.id",
})})
if err := creds.Save(); err != nil {
t.Fatal(err)
}
out, err := runRoot(t, "", "whoami")
if err != nil {
t.Fatalf("whoami: %v", err)
}
for _, want := range []string{"z@hanzo.ai", "hanzo", "u-1", "https://hanzo.id"} {
if !strings.Contains(out, want) {
t.Fatalf("whoami missing %q in %q", want, out)
}
}
}
func TestWhoamiLoggedOut(t *testing.T) {
sandbox(t)
if _, err := runRoot(t, "", "whoami"); err == nil {
t.Fatalf("expected error when logged out")
}
}
func TestLogoutCommand(t *testing.T) {
sandbox(t)
(&Credentials{AccessToken: "x"}).Save()
if _, err := runRoot(t, "", "logout"); err != nil {
t.Fatalf("logout: %v", err)
}
if c, _ := LoadCredentials(); c.AccessToken != "" {
t.Fatalf("logout did not clear credentials")
}
}
func TestAuthTokenCommand(t *testing.T) {
sandbox(t)
(&Credentials{AccessToken: "the-token"}).Save()
out, err := runRoot(t, "", "auth", "token")
if err != nil {
t.Fatalf("auth token: %v", err)
}
if strings.TrimSpace(out) != "the-token" {
t.Fatalf("auth token output: %q", out)
}
}
// TestMultiIdentityLoginSwitch is the full multi-identity story: two logins for
// the same email under different owners (admin vs hanzo — the privilege-
// separation case) coexist, `auth list` shows both, `switch` flips the active
// pointer and rewrites credentials.json, and legacy single-file readers always
// see the active identity.
func TestMultiIdentityLoginSwitch(t *testing.T) {
sandbox(t)
adminTok := makeJWT(map[string]any{"email": "z@hanzo.ai", "owner": "admin", "sub": "u-admin", "exp": float64(2000000000)})
hanzoTok := makeJWT(map[string]any{"email": "z@hanzo.ai", "owner": "hanzo", "sub": "u-hanzo", "exp": float64(2000000001)})
// First login → admin/z is stored and active.
out, err := runRoot(t, "", "login", "--token", adminTok)
if err != nil {
t.Fatalf("login admin: %v", err)
}
if !strings.Contains(out, "admin/z") {
t.Fatalf("login should report the key: %q", out)
}
if c, _ := LoadCredentials(); c.Owner != "admin" || c.Subject != "z@hanzo.ai" {
t.Fatalf("active not admin after first login: %+v", c)
}
// Second login (different owner) → added beside admin/z, becomes active,
// does NOT clobber the first.
if _, err := runRoot(t, "", "login", "--token", hanzoTok); err != nil {
t.Fatalf("login hanzo: %v", err)
}
store, err := LoadIdentities()
if err != nil {
t.Fatalf("load identities: %v", err)
}
if len(store.Identities) != 2 {
t.Fatalf("want 2 identities, got %d: %v", len(store.Identities), store.keys())
}
if store.Identities["admin/z"] == nil || store.Identities["hanzo/z"] == nil {
t.Fatalf("both identities must persist, got %v", store.keys())
}
if store.Active != "hanzo/z" {
t.Fatalf("active = %q, want hanzo/z (last login)", store.Active)
}
// Legacy reader sees the active (hanzo) identity.
if c, _ := LoadCredentials(); c.Owner != "hanzo" {
t.Fatalf("credentials.json not mirroring active: %+v", c)
}
// auth list shows both, with the active row marked.
out, err = runRoot(t, "", "auth", "list")
if err != nil {
t.Fatalf("auth list: %v", err)
}
for _, want := range []string{"admin/z", "hanzo/z", "z@hanzo.ai", "*"} {
if !strings.Contains(out, want) {
t.Fatalf("auth list missing %q in:\n%s", want, out)
}
}
// switch admin → active flips + credentials.json is rewritten to admin.
if _, err := runRoot(t, "", "auth", "switch", "admin"); err != nil {
t.Fatalf("auth switch admin: %v", err)
}
if st, _ := LoadIdentities(); st.Active != "admin/z" {
t.Fatalf("active after switch = %q, want admin/z", st.Active)
}
if c, _ := LoadCredentials(); c.Owner != "admin" || c.Subject != "z@hanzo.ai" {
t.Fatalf("switch did not rewrite credentials.json: %+v", c)
}
// whoami (top-level, reads the active token) reflects admin.
out, err = runRoot(t, "", "whoami")
if err != nil {
t.Fatalf("whoami: %v", err)
}
if !strings.Contains(out, "admin") || !strings.Contains(out, "z@hanzo.ai") {
t.Fatalf("whoami not reflecting the switched-to identity: %q", out)
}
// switch by the full owner/name key works too.
if _, err := runRoot(t, "", "auth", "switch", "hanzo/z"); err != nil {
t.Fatalf("auth switch hanzo/z: %v", err)
}
if c, _ := LoadCredentials(); c.Owner != "hanzo" {
t.Fatalf("switch by full key failed: %+v", c)
}
}
// TestAuthListJSON checks the machine-readable projection.
func TestAuthListJSON(t *testing.T) {
sandbox(t)
tok := makeJWT(map[string]any{"email": "z@hanzo.ai", "owner": "admin", "sub": "a"})
if _, err := runRoot(t, "", "login", "--token", tok); err != nil {
t.Fatalf("login: %v", err)
}
out, err := runRoot(t, "", "auth", "list", "-o", "json")
if err != nil {
t.Fatalf("auth list json: %v", err)
}
var rows []identityRow
if err := json.Unmarshal([]byte(out), &rows); err != nil {
t.Fatalf("json unmarshal: %v\n%s", err, out)
}
if len(rows) != 1 || rows[0].Key != "admin/z" || rows[0].Owner != "admin" || !rows[0].Active {
t.Fatalf("json rows wrong: %+v", rows)
}
}
// TestLogoutOneOfMany removes a single identity and, only when the last one is
// gone, clears the store entirely.
func TestLogoutOneOfMany(t *testing.T) {
sandbox(t)
admin := makeJWT(map[string]any{"email": "z@hanzo.ai", "owner": "admin", "sub": "a"})
hanzo := makeJWT(map[string]any{"email": "z@hanzo.ai", "owner": "hanzo", "sub": "h"})
if _, err := runRoot(t, "", "login", "--token", admin); err != nil {
t.Fatal(err)
}
if _, err := runRoot(t, "", "login", "--token", hanzo); err != nil { // active = hanzo/z
t.Fatal(err)
}
// logout of the named owner (admin) leaves hanzo/z active.
if _, err := runRoot(t, "", "logout", "admin"); err != nil {
t.Fatalf("logout admin: %v", err)
}
store, _ := LoadIdentities()
if store.Identities["admin/z"] != nil {
t.Fatalf("admin/z not removed: %v", store.keys())
}
if store.Active != "hanzo/z" {
t.Fatalf("active = %q, want hanzo/z", store.Active)
}
if c, _ := LoadCredentials(); c.Owner != "hanzo" {
t.Fatalf("credentials.json not mirroring survivor: %+v", c)
}
// logout of the active (no arg) removes the last identity → both files gone.
if _, err := runRoot(t, "", "logout"); err != nil {
t.Fatalf("logout active: %v", err)
}
if c, _ := LoadCredentials(); c.AccessToken != "" {
t.Fatalf("credentials.json not cleared: %+v", c)
}
if st, _ := LoadIdentities(); len(st.Identities) != 0 {
t.Fatalf("identity store not cleared: %v", st.keys())
}
}
// TestMigrateLegacyCredentials proves a pre-multi-identity credentials.json is
// adopted into the store and preserved when a new identity is added.
func TestMigrateLegacyCredentials(t *testing.T) {
sandbox(t)
// Simulate an old single-file login: only credentials.json exists.
legacy := credsFromToken(&tokenResp{AccessToken: makeJWT(map[string]any{
"email": "z@hanzo.ai", "owner": "hanzo", "sub": "h",
})})
if err := legacy.Save(); err != nil {
t.Fatal(err)
}
store, err := LoadIdentities()
if err != nil {
t.Fatalf("load identities: %v", err)
}
if store.Identities["hanzo/z"] == nil || store.Active != "hanzo/z" {
t.Fatalf("legacy credentials not migrated: active=%q keys=%v", store.Active, store.keys())
}
// A fresh login as a different owner preserves the migrated identity.
if _, err := runRoot(t, "", "login", "--token", makeJWT(map[string]any{
"email": "z@hanzo.ai", "owner": "admin", "sub": "a",
})); err != nil {
t.Fatal(err)
}
st2, _ := LoadIdentities()
if len(st2.Identities) != 2 || st2.Identities["hanzo/z"] == nil {
t.Fatalf("migrated identity lost after new login: %v", st2.keys())
}
}
+82
View File
@@ -0,0 +1,82 @@
package cli
// bot.go — `hanzo bot`: launch a computer-using agent (a "bot").
//
// A bot is the COMPUTER-USING flavor of an agent: it quick-boots a terminal or
// desktop sandbox on the operative stack (Hanzo's computer-use runtime — noVNC
// desktop, shell, browser, tools), provisioned by visor, and drives that machine
// to do the task. The headless flavor (no computer) is `hanzo agent` (agent.go).
//
// hanzo bot run "<task>" → boot a desktop bot, run the task
// hanzo bot run --terminal "<task>" → boot a terminal-only bot
//
// Thin client over the IAM token + env.CloudURL (reuses cloudCall, run.go). The
// operative runtime + visor-provisioned machine do the work; the CLI only starts
// the run and reports the live session URL. See docs/architecture/compute-ladder.md.
import (
"fmt"
"io"
"net/http"
"strings"
"github.com/spf13/cobra"
)
// BotRunReq is the boot-a-computer-using-agent body. Surface selects the sandbox
// the operative runtime drives: "desktop" (noVNC GUI) or "terminal" (shell only).
type BotRunReq struct {
Task string `json:"task"`
Surface string `json:"surface"` // desktop | terminal
GPU bool `json:"gpu,omitempty"`
Timeout string `json:"timeout,omitempty"`
}
// BotRunResult carries the live session: a URL to watch/attach (noVNC / terminal)
// plus the run id.
type BotRunResult struct {
RunID string `json:"runId"`
Status string `json:"status"`
SessionURL string `json:"sessionUrl"`
}
func newBotCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
cmd := &cobra.Command{
Use: "bot",
Short: "Launch a computer-using agent (booted desktop or terminal)",
Long: "Quick-boot a terminal or desktop sandbox on the operative computer-use\n" +
"runtime (visor-provisioned) and have an agent drive it to do a task —\n" +
"metered like any run. For a headless task agent, use `hanzo agent`.",
}
cmd.AddCommand(newBotRunCmd(envOf))
return cmd
}
func newBotRunCmd(envOf func() *Env) *cobra.Command {
var req BotRunReq
var terminal bool
c := &cobra.Command{
Use: "run <task>",
Short: "Boot a computer-using bot and run the task",
Args: cobra.MinimumNArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
env := envOf()
req.Task = strings.Join(args, " ")
req.Surface = "desktop"
if terminal {
req.Surface = "terminal"
}
out := &BotRunResult{}
if err := cloudCall(cmd.Context(), env, http.MethodPost, "/v1/bots/run", &req, out); err != nil {
return err
}
return env.emit(out, func(w io.Writer) {
fmt.Fprintf(w, "%s\t%s\t%s\n", out.RunID, out.Status, out.SessionURL)
})
},
}
c.Flags().BoolVar(&terminal, "terminal", false, "boot a terminal-only sandbox (default: desktop)")
c.Flags().BoolVar(&req.GPU, "gpu", false, "boot on a GPU machine")
c.Flags().StringVar(&req.Timeout, "timeout", "", "max wall-clock (e.g. 30m)")
return c
}
+784
View File
@@ -0,0 +1,784 @@
// Package cli is the Hanzo cloud-control CLI — the gcloud/doctl-class client
// half of the `hanzo` binary.
//
// `hanzo <subsystem>` SERVES a subsystem (server mode, cmd/hanzo dispatch);
// `hanzo <verb>` CONTROLS the live estate (client mode, this package):
//
// hanzo login | auth identity against hanzo.id (IAM)
// hanzo apps list|get the platform apps board (declared/running/drift)
// hanzo deploy drive a platform redeploy (rolling, zero-downtime)
// hanzo clusters … provision/list/select dedicated DOKS clusters
// hanzo build enqueue a platform-native build (runner fabric)
// hanzo k8s … current deploy target helpers
// hanzo config … ~/.hanzo/config preferences
//
// It is a THIN client over surfaces that already exist — Hanzo IAM
// (hanzo.id /v1/iam/oauth/*), the platform REST control plane
// (platform.hanzo.ai /v1/*), and the cloud /v1 API. It invents no parallel
// API and holds no business logic; every command is one HTTP call shaped by
// resolved configuration. Secrets live only in ~/.hanzo (0600) or the
// environment — never in source, never logged.
package cli
import (
"encoding/json"
"fmt"
"io"
"os"
"path/filepath"
"sort"
"strings"
"time"
"github.com/spf13/cobra"
)
// Version is the binary version, set by cmd/hanzo from its -ldflags value so
// the CLI and the server report one string. Used in the User-Agent.
var Version = "dev"
// Default endpoints. Overridable per-field via config / env / flag.
const (
defaultIAMIssuer = "https://hanzo.id"
defaultPlatformURL = "https://platform.hanzo.ai"
defaultCloudURL = "https://api.hanzo.ai"
// hanzo-console is the only live IAM client that accepts the password
// grant today; a dedicated `hanzo-cli` client is a one-line IAM seed
// follow-up. Override with `--client-id` / HANZO_CLIENT_ID / config.
defaultClientID = "hanzo-console"
)
// controlCommands maps every client-mode verb to its one-line help. cmd/hanzo
// reads this both to ROUTE (a first token in here means client mode) and to
// list the commands in `hanzo help`, so the verb set is defined exactly once.
var controlCommands = map[string]string{
"login": "authenticate against Hanzo IAM (hanzo.id) and store a token",
"logout": "remove stored credentials",
"whoami": "show the current identity from the stored token",
"auth": "manage authentication + stored identities (login, logout, whoami, list, switch, token)",
"apps": "list/get the platform apps board (declared/running/drift)",
"deploy": "drive a platform redeploy (rolling restart, zero-downtime)",
"clusters": "provision/list/select dedicated DOKS clusters",
"build": "enqueue a platform-native build (runner fabric)",
"k8s": "deploy-target helpers (current target)",
"config": "view/edit ~/.hanzo/config preferences",
"security": "scan files for hardcoded secrets (local guardrail; no server/auth)",
"link": "bring this machine into the Hanzo cloud fleet as a node (fabric + compute worker)",
"unlink": "take this machine out of the fleet (deregister + stop hanzod)",
"status": "show the org's fleet — every node with each of its GPUs",
"engine": "run a local hanzo-engine (OpenAI + Anthropic model server)",
"code": "launch a coding agent (claude, codex, dev) on a Hanzo cloud model",
"runner": "run this machine as a JIT CI runner for your org (GitHub Actions)",
"run": "launch a workload on Hanzo compute (container or function)",
"agent": "invoke a managed Hanzo agent to run a task (headless)",
"bot": "launch a computer-using agent (booted desktop or terminal)",
}
// IsControlVerb reports whether sub is a client-mode command (and therefore
// must be routed to this package, not the server dispatcher).
func IsControlVerb(sub string) bool {
_, ok := controlCommands[sub]
return ok
}
// ControlCommands returns the verb→description map for `hanzo help`.
func ControlCommands() map[string]string { return controlCommands }
// Execute runs the control CLI with args (already stripped of "hanzo"). It is
// the single entrypoint cmd/hanzo calls for client-mode verbs.
func Execute(args []string) error {
root := newRootCmd()
root.SetArgs(args)
return root.Execute()
}
// ---------------------------------------------------------------------------
// Config — non-secret preferences, ~/.hanzo/config (JSON).
// ---------------------------------------------------------------------------
// Config holds non-secret CLI preferences. Every field is optional; empty
// fields fall back to the built-in defaults at resolution time.
type Config struct {
Org string `json:"org,omitempty"`
Output string `json:"output,omitempty"` // "table" (default) | "json"
IAMIssuer string `json:"iam_issuer,omitempty"`
PlatformURL string `json:"platform_url,omitempty"`
CloudURL string `json:"cloud_url,omitempty"`
ClientID string `json:"client_id,omitempty"`
APIKey string `json:"apiKey,omitempty"` // hk-… key; what `hanzo code` hands the agents
CodeTool string `json:"code_tool,omitempty"` // default agent for bare `hanzo` / `hanzo code`: dev|claude|codex
CodeModel string `json:"code_model,omitempty"` // default model for `hanzo code` (else defaultCodeModel)
}
// Credentials holds secret material, ~/.hanzo/credentials.json, mode 0600.
// AccessToken/RefreshToken are the IAM user identity (from `hanzo login`);
// PlatformToken/BuildToken are the machine-to-machine tokens the platform
// REST control plane requires (it cannot validate IAM user tokens).
type Credentials struct {
AccessToken string `json:"access_token,omitempty"`
RefreshToken string `json:"refresh_token,omitempty"`
TokenType string `json:"token_type,omitempty"`
Expiry int64 `json:"expiry,omitempty"` // unix seconds
Subject string `json:"subject,omitempty"`
Owner string `json:"owner,omitempty"` // org slug from the token
PlatformToken string `json:"platform_token,omitempty"`
BuildToken string `json:"build_token,omitempty"`
}
// hanzoDir is ~/.hanzo, created 0700 if missing. Overridable with HANZO_HOME
// (used by tests to sandbox the credential store).
func hanzoDir() (string, error) {
if h := os.Getenv("HANZO_HOME"); h != "" {
return h, os.MkdirAll(h, 0o700)
}
home, err := os.UserHomeDir()
if err != nil {
return "", err
}
dir := filepath.Join(home, ".hanzo")
return dir, os.MkdirAll(dir, 0o700)
}
func configPath() (string, error) {
dir, err := hanzoDir()
if err != nil {
return "", err
}
if p := os.Getenv("HANZO_CONFIG"); p != "" {
return p, nil
}
return filepath.Join(dir, "config"), nil
}
func credentialsPath() (string, error) {
dir, err := hanzoDir()
if err != nil {
return "", err
}
return filepath.Join(dir, "credentials.json"), nil
}
// loadJSON reads a JSON file into v; a missing file is not an error (v is left
// at its zero value) so first-run with no config/credentials just works.
func loadJSON(path string, v any) error {
b, err := os.ReadFile(path)
if os.IsNotExist(err) {
return nil
}
if err != nil {
return err
}
if len(b) == 0 {
return nil
}
return json.Unmarshal(b, v)
}
// writeJSON writes v as indented JSON at path with the given mode, via a
// temp-file rename so a crash mid-write never truncates the store.
func writeJSON(path string, v any, mode os.FileMode) error {
b, err := json.MarshalIndent(v, "", " ")
if err != nil {
return err
}
tmp := path + ".tmp"
if err := os.WriteFile(tmp, append(b, '\n'), mode); err != nil {
return err
}
return os.Rename(tmp, path)
}
// LoadConfig reads ~/.hanzo/config (or HANZO_CONFIG).
func LoadConfig() (*Config, error) {
p, err := configPath()
if err != nil {
return nil, err
}
c := &Config{}
return c, loadJSON(p, c)
}
// Save persists the config (mode 0644 — non-secret).
func (c *Config) Save() error {
p, err := configPath()
if err != nil {
return err
}
return writeJSON(p, c, 0o644)
}
// LoadCredentials reads ~/.hanzo/credentials.json.
func LoadCredentials() (*Credentials, error) {
p, err := credentialsPath()
if err != nil {
return nil, err
}
c := &Credentials{}
return c, loadJSON(p, c)
}
// Save persists credentials with mode 0600 (owner read/write only).
func (c *Credentials) Save() error {
p, err := credentialsPath()
if err != nil {
return err
}
return writeJSON(p, c, 0o600)
}
// DeleteCredentials removes the credential store (used by logout).
func DeleteCredentials() error {
p, err := credentialsPath()
if err != nil {
return err
}
if err := os.Remove(p); err != nil && !os.IsNotExist(err) {
return err
}
return nil
}
// ---------------------------------------------------------------------------
// Identity store — ~/.hanzo/identities.json. Holds EVERY logged-in identity
// keyed by its stable "<owner>/<name>" key, with an Active pointer. On every
// write the active identity is mirrored into credentials.json (above), so every
// legacy single-file reader keeps seeing the current identity unchanged. This
// is the ONE credential store; credentials.json is its active-view mirror.
// ---------------------------------------------------------------------------
// IdentityStore is the on-disk shape of ~/.hanzo/identities.json.
type IdentityStore struct {
Active string `json:"active,omitempty"`
Identities map[string]*Credentials `json:"identities,omitempty"`
}
// key is the stable per-identity store key "<owner>/<name>", where name is the
// email local-part (else the raw subject). The same identity yields the same
// key every login, so re-login updates in place; the same email under a
// different org (privilege separation) yields a distinct key (admin/z vs
// hanzo/z) and is stored side by side rather than clobbering.
func (c *Credentials) key() string {
name := c.Subject
if i := strings.IndexByte(name, '@'); i > 0 {
name = name[:i]
}
return firstNonEmpty(c.Owner, "-") + "/" + firstNonEmpty(name, "-")
}
func identitiesPath() (string, error) {
dir, err := hanzoDir()
if err != nil {
return "", err
}
return filepath.Join(dir, "identities.json"), nil
}
// LoadIdentities reads the store. A pre-existing single-file credentials.json
// with no store yet is migrated in (read-only) as the sole, active identity, so
// upgrades are seamless — the first write persists it into the store.
func LoadIdentities() (*IdentityStore, error) {
p, err := identitiesPath()
if err != nil {
return nil, err
}
s := &IdentityStore{Identities: map[string]*Credentials{}}
if err := loadJSON(p, s); err != nil {
return nil, err
}
if s.Identities == nil {
s.Identities = map[string]*Credentials{}
}
if len(s.Identities) == 0 {
if c, err := LoadCredentials(); err == nil && c.AccessToken != "" {
k := c.key()
s.Identities[k] = c
s.Active = k
}
}
return s, nil
}
// keys returns the identity keys, sorted, for deterministic output.
func (s *IdentityStore) keys() []string {
ks := make([]string, 0, len(s.Identities))
for k := range s.Identities {
ks = append(ks, k)
}
sort.Strings(ks)
return ks
}
// Put stores c under its key and makes it active, returning the key.
func (s *IdentityStore) Put(c *Credentials) string {
if s.Identities == nil {
s.Identities = map[string]*Credentials{}
}
k := c.key()
s.Identities[k] = c
s.Active = k
return k
}
// Remove deletes an identity; Save re-points Active if it was the one removed.
func (s *IdentityStore) Remove(key string) { delete(s.Identities, key) }
// resolve turns a user selector into a stored key: an exact key wins; otherwise
// a bare owner matches iff exactly one identity carries it.
func (s *IdentityStore) resolve(sel string) (string, error) {
if _, ok := s.Identities[sel]; ok {
return sel, nil
}
var match []string
for _, k := range s.keys() {
if s.Identities[k].Owner == sel {
match = append(match, k)
}
}
switch len(match) {
case 1:
return match[0], nil
case 0:
return "", fmt.Errorf("no stored identity for %q (see `hanzo auth list`)", sel)
default:
return "", fmt.Errorf("%q is ambiguous across %s — pass the full owner/name key", sel, strings.Join(match, ", "))
}
}
// Save persists the store (0600) and mirrors the active identity into
// credentials.json for legacy single-file readers. When the store is empty it
// removes both files. Active is normalized to a real key first.
func (s *IdentityStore) Save() error {
if _, ok := s.Identities[s.Active]; !ok {
s.Active = ""
if ks := s.keys(); len(ks) > 0 {
s.Active = ks[0]
}
}
if len(s.Identities) == 0 {
return clearCredentialStore()
}
p, err := identitiesPath()
if err != nil {
return err
}
if err := writeJSON(p, s, 0o600); err != nil {
return err
}
return s.Identities[s.Active].Save() // mirror active → credentials.json (0600)
}
// SaveActive writes c back as the active identity (store + mirror), keeping the
// two consistent after an in-place token refresh. With no store yet it falls
// back to the single-file write.
func SaveActive(c *Credentials) error {
s, err := LoadIdentities()
if err != nil {
return err
}
if len(s.Identities) == 0 {
return c.Save()
}
k := s.Active
if k == "" || s.Identities[k] == nil {
k = c.key()
}
s.Identities[k] = c
s.Active = k
return s.Save()
}
// clearCredentialStore removes the identity store and its credentials.json
// mirror (used by logout when the last identity is removed).
func clearCredentialStore() error {
for _, pathOf := range []func() (string, error){credentialsPath, identitiesPath} {
p, err := pathOf()
if err != nil {
return err
}
if err := os.Remove(p); err != nil && !os.IsNotExist(err) {
return err
}
}
return nil
}
// ---------------------------------------------------------------------------
// Env — the effective, resolved settings a command operates with.
// ---------------------------------------------------------------------------
// Env is the fully-resolved runtime context for a command: config + creds
// merged with environment and the global flags. Built once in the root's
// PersistentPreRunE and read by every subcommand.
type Env struct {
cfg *Config
creds *Credentials
Org string
Output string
IAMIssuer string
PlatformURL string
CloudURL string
ClientID string
out io.Writer
}
// flag values bound by the persistent flags (empty == unset, fall through).
type globalFlags struct {
org, output, platformURL, iamIssuer, cloudURL, clientID, platformToken string
}
// firstNonEmpty returns the first non-empty argument, or "".
func firstNonEmpty(vs ...string) string {
for _, v := range vs {
if v != "" {
return v
}
}
return ""
}
// resolve merges flags > env > config > built-in defaults into an Env. It is
// pure given its inputs (config/creds are loaded by the caller) so it is
// directly unit-testable.
func resolve(cfg *Config, creds *Credentials, f globalFlags) *Env {
e := &Env{cfg: cfg, creds: creds, out: os.Stdout}
e.Output = firstNonEmpty(f.output, os.Getenv("HANZO_OUTPUT"), cfg.Output, "table")
e.IAMIssuer = strings.TrimRight(firstNonEmpty(f.iamIssuer, os.Getenv("HANZO_IAM_ISSUER"), cfg.IAMIssuer, defaultIAMIssuer), "/")
e.PlatformURL = strings.TrimRight(firstNonEmpty(f.platformURL, os.Getenv("HANZO_PLATFORM_URL"), cfg.PlatformURL, defaultPlatformURL), "/")
e.CloudURL = strings.TrimRight(firstNonEmpty(f.cloudURL, os.Getenv("HANZO_CLOUD_URL"), cfg.CloudURL, defaultCloudURL), "/")
e.ClientID = firstNonEmpty(f.clientID, os.Getenv("HANZO_CLIENT_ID"), cfg.ClientID, defaultClientID)
// Org for platform calls is the platform organization id (a distinct
// namespace from the IAM token's `owner` slug), so it comes only from
// flag/env/config — never silently from the token.
e.Org = firstNonEmpty(f.org, os.Getenv("HANZO_ORG"), cfg.Org)
return e
}
// accessToken is the IAM user token (identity / cloud calls).
func (e *Env) accessToken() string {
return firstNonEmpty(os.Getenv("HANZO_TOKEN"), e.creds.AccessToken)
}
// freshAccessToken returns the IAM user token only while it is not yet expired.
// accessToken() stays expiry-agnostic so `hanzo whoami` can report a dead token
// rather than masking it as logged-out; freshAccessToken is the code-agent path,
// where an expired token would 401 a session a still-valid hk- key could serve.
// No expiry recorded (a raw HANZO_TOKEN with no claims) ⟹ trust it as-is.
func (e *Env) freshAccessToken() string {
tok := e.accessToken()
if tok == "" {
return ""
}
if exp := e.creds.Expiry; exp > 0 && time.Now().Unix() >= exp {
return ""
}
return tok
}
// platformToken resolves the bearer the platform control plane authenticates
// apps/clusters/redeploy with. ONE identity authorizes everything: after a plain
// `hanzo login` the IAM access token is the FINAL fallback, so no separate
// --platform-token is needed — the platform verifies the IAM JWT (signature,
// issuer, expiry) and org-scopes the caller. A dedicated service token still
// wins when present (flag > env > credential store > IAM login), so purpose-minted
// machine tokens keep their precedence and internal automation is unchanged.
// Never hardcoded.
func (e *Env) platformToken(flagVal string) string {
return firstNonEmpty(
flagVal,
os.Getenv("HANZO_PLATFORM_TOKEN"),
os.Getenv("PLATFORM_SERVICE_TOKEN"),
os.Getenv("PAAS_SERVICE_TOKEN"),
e.creds.PlatformToken,
e.accessToken(), // IAM login is the one identity that authorizes control-plane ops
)
}
// buildToken resolves the bearer `hanzo build` sends to the platform build
// enqueue (/v1/runner). Same unify-infra contract as platformToken: a dedicated
// build token wins when present, but a plain IAM login is the FINAL fallback, so
// `hanzo build` works off the one identity with no separate --build-token — the
// platform verifies the IAM JWT and authorizes the build by org + role.
func (e *Env) buildToken(flagVal string) string {
return firstNonEmpty(
flagVal,
os.Getenv("HANZO_BUILD_TOKEN"),
os.Getenv("PLATFORM_BUILD_CALLBACK_TOKEN"),
e.creds.BuildToken,
e.accessToken(), // IAM login is the one identity that authorizes builds
)
}
// requireOrg returns the resolved org or a clear error telling the user how to
// set it.
func (e *Env) requireOrg() (string, error) {
if e.Org == "" {
return "", fmt.Errorf("no org set: pass --org, set HANZO_ORG, or run `hanzo config set org <org>`")
}
return e.Org, nil
}
// ---------------------------------------------------------------------------
// Output helpers — one place decides JSON vs human-readable tables.
// ---------------------------------------------------------------------------
// emit prints v as JSON when --output=json, otherwise calls table to render a
// human view. This is the single output branch for every command.
func (e *Env) emit(v any, table func(w io.Writer)) error {
if e.Output == "json" {
enc := json.NewEncoder(e.out)
enc.SetIndent("", " ")
return enc.Encode(v)
}
table(e.out)
return nil
}
// ---------------------------------------------------------------------------
// Root command + global flags.
// ---------------------------------------------------------------------------
func newRootCmd() *cobra.Command {
var f globalFlags
var env *Env
root := &cobra.Command{
Use: "hanzo",
Short: "Hanzo cloud control — manage the live Hanzo estate",
Long: "hanzo — gcloud/doctl-class control for the Hanzo platform (IAM, apps, deploys, clusters, builds).",
SilenceUsage: true,
SilenceErrors: false,
PersistentPreRunE: func(cmd *cobra.Command, _ []string) error {
cfg, err := LoadConfig()
if err != nil {
return fmt.Errorf("load config: %w", err)
}
creds, err := LoadCredentials()
if err != nil {
return fmt.Errorf("load credentials: %w", err)
}
env = resolve(cfg, creds, f)
env.out = cmd.OutOrStdout()
return nil
},
// Bare `hanzo` gets you coding: log in if needed, then drop into the
// configured agent (code_tool, else dev) on a Hanzo cloud model — one word,
// billed to your account. `hanzo <cmd>` still runs that command.
RunE: func(cmd *cobra.Command, args []string) error {
if codeToken(env) == "" {
if err := runLogin(env, &loginFlags{}, cmd); err != nil {
return err
}
}
return runCode(env, defaultAgent(env), nil)
},
}
pf := root.PersistentFlags()
pf.StringVar(&f.org, "org", "", "organization (overrides config / HANZO_ORG)")
pf.StringVarP(&f.output, "output", "o", "", "output format: table|json")
pf.StringVar(&f.platformURL, "platform-url", "", "platform base URL (default "+defaultPlatformURL+")")
pf.StringVar(&f.iamIssuer, "iam-issuer", "", "IAM issuer (default "+defaultIAMIssuer+")")
pf.StringVar(&f.cloudURL, "cloud-url", "", "cloud API base URL (default "+defaultCloudURL+")")
pf.StringVar(&f.clientID, "client-id", "", "IAM OAuth client id (default "+defaultClientID+")")
pf.StringVar(&f.platformToken, "platform-token", "", "platform control-plane service token (else env/credential store)")
// envOf returns the resolved Env for a command's RunE (always non-nil after
// PersistentPreRunE).
envOf := func() *Env { return env }
root.AddCommand(
newVersionCmd(),
newAuthCmd(envOf, &f),
newLoginCmd(envOf, &f),
newLogoutCmd(),
newWhoamiCmd(envOf),
newAppsCmd(envOf, &f),
newDeployCmd(envOf, &f),
newClustersCmd(envOf, &f),
newBuildCmd(envOf, &f),
newConfigCmd(),
newSecurityCmd(envOf),
newLinkCmd(envOf, &f),
newUnlinkCmd(envOf, &f),
newStatusCmd(envOf, &f),
newEngineCmd(envOf, &f),
newCodeCmd(envOf, &f),
newRunnerCmd(envOf, &f),
newRunCmd(envOf, &f),
newAgentCmd(envOf, &f),
newBotCmd(envOf, &f),
)
return root
}
func newVersionCmd() *cobra.Command {
return &cobra.Command{
Use: "version",
Short: "Print the hanzo version",
Args: cobra.NoArgs,
PersistentPreRunE: func(*cobra.Command, []string) error { return nil },
RunE: func(cmd *cobra.Command, _ []string) error {
fmt.Fprintf(cmd.OutOrStdout(), "hanzo %s\n", Version)
return nil
},
}
}
// ---------------------------------------------------------------------------
// config command — view/edit the non-secret preference file.
// ---------------------------------------------------------------------------
func newConfigCmd() *cobra.Command {
cmd := &cobra.Command{
Use: "config",
Short: "View/edit ~/.hanzo/config preferences",
PersistentPreRunE: func(*cobra.Command, []string) error { return nil },
}
configKeys := []string{"org", "output", "iam_issuer", "platform_url", "cloud_url", "client_id", "code_tool", "code_model"}
get := &cobra.Command{
Use: "get <key>",
Short: "Print one config value",
Args: cobra.ExactArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
cfg, err := LoadConfig()
if err != nil {
return err
}
v, err := cfg.field(args[0])
if err != nil {
return err
}
fmt.Fprintln(cmd.OutOrStdout(), v)
return nil
},
}
set := &cobra.Command{
Use: "set <key> <value>",
Short: "Set one config value (keys: " + strings.Join(configKeys, ", ") + ")",
Args: cobra.ExactArgs(2),
RunE: func(cmd *cobra.Command, args []string) error {
cfg, err := LoadConfig()
if err != nil {
return err
}
if err := cfg.setField(args[0], args[1]); err != nil {
return err
}
if err := cfg.Save(); err != nil {
return err
}
fmt.Fprintf(cmd.OutOrStdout(), "set %s = %s\n", args[0], args[1])
return nil
},
}
list := &cobra.Command{
Use: "list",
Short: "Print the full config",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
cfg, err := LoadConfig()
if err != nil {
return err
}
enc := json.NewEncoder(cmd.OutOrStdout())
enc.SetIndent("", " ")
return enc.Encode(cfg)
},
}
path := &cobra.Command{
Use: "path",
Short: "Print the config file path",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
p, err := configPath()
if err != nil {
return err
}
fmt.Fprintln(cmd.OutOrStdout(), p)
return nil
},
}
cmd.AddCommand(get, set, list, path)
return cmd
}
// field returns the named config value as a string.
func (c *Config) field(key string) (string, error) {
switch key {
case "org":
return c.Org, nil
case "output":
return c.Output, nil
case "iam_issuer":
return c.IAMIssuer, nil
case "platform_url":
return c.PlatformURL, nil
case "cloud_url":
return c.CloudURL, nil
case "client_id":
return c.ClientID, nil
case "code_tool":
return c.CodeTool, nil
case "code_model":
return c.CodeModel, nil
default:
return "", fmt.Errorf("unknown config key %q", key)
}
}
// setField sets the named config value.
func (c *Config) setField(key, val string) error {
switch key {
case "org":
c.Org = val
case "output":
if val != "table" && val != "json" {
return fmt.Errorf("output must be table|json")
}
c.Output = val
case "iam_issuer":
c.IAMIssuer = val
case "platform_url":
c.PlatformURL = val
case "cloud_url":
c.CloudURL = val
case "client_id":
c.ClientID = val
case "code_tool":
if _, ok := codeAgents[val]; !ok {
return fmt.Errorf("code_tool must be one of: claude, codex, dev")
}
c.CodeTool = val
case "code_model":
c.CodeModel = val
default:
return fmt.Errorf("unknown config key %q", key)
}
return nil
}
// shortTime renders a unix timestamp for human tables; "" for zero.
func shortTime(unix int64) string {
if unix == 0 {
return ""
}
return time.Unix(unix, 0).Format(time.RFC3339)
}
// sortedKeys returns the keys of m, sorted — for deterministic help output.
func sortedKeys(m map[string]string) []string {
ks := make([]string, 0, len(m))
for k := range m {
ks = append(ks, k)
}
sort.Strings(ks)
return ks
}
+294
View File
@@ -0,0 +1,294 @@
package cli
import (
"bytes"
"encoding/json"
"io"
"os"
"path/filepath"
"strings"
"testing"
)
// TestMain restores stdout (quiet.go redirected it to stderr at init) so go
// test's own reporting stays on stdout.
func TestMain(m *testing.M) {
RestoreStdout()
os.Exit(m.Run())
}
// sandbox isolates the credential/config store in a temp dir and clears every
// env var resolve() consults, so tests are deterministic and never touch the
// developer's real ~/.hanzo.
func sandbox(t *testing.T) string {
t.Helper()
dir := t.TempDir()
t.Setenv("HANZO_HOME", dir)
for _, k := range []string{
"HANZO_CONFIG", "HANZO_OUTPUT", "HANZO_IAM_ISSUER", "HANZO_PLATFORM_URL",
"HANZO_CLOUD_URL", "HANZO_CLIENT_ID", "HANZO_ORG", "HANZO_TOKEN",
"HANZO_PLATFORM_TOKEN", "PLATFORM_SERVICE_TOKEN", "PAAS_SERVICE_TOKEN",
"HANZO_BUILD_TOKEN", "PLATFORM_BUILD_CALLBACK_TOKEN",
} {
t.Setenv(k, "")
}
return dir
}
func TestConfigRoundTrip(t *testing.T) {
sandbox(t)
in := &Config{Org: "acme", Output: "json", PlatformURL: "https://p.example", ClientID: "hanzo-console"}
if err := in.Save(); err != nil {
t.Fatalf("save: %v", err)
}
out, err := LoadConfig()
if err != nil {
t.Fatalf("load: %v", err)
}
if *out != *in {
t.Fatalf("round-trip mismatch: %+v != %+v", out, in)
}
}
func TestCredentialsRoundTripAndPerms(t *testing.T) {
dir := sandbox(t)
in := &Credentials{AccessToken: "tok", RefreshToken: "ref", TokenType: "Bearer", Subject: "z@hanzo.ai", Owner: "hanzo", PlatformToken: "pt"}
if err := in.Save(); err != nil {
t.Fatalf("save: %v", err)
}
fi, err := os.Stat(filepath.Join(dir, "credentials.json"))
if err != nil {
t.Fatalf("stat: %v", err)
}
if perm := fi.Mode().Perm(); perm != 0o600 {
t.Fatalf("credentials perm = %o, want 0600", perm)
}
out, err := LoadCredentials()
if err != nil {
t.Fatalf("load: %v", err)
}
if *out != *in {
t.Fatalf("round-trip mismatch: %+v != %+v", out, in)
}
if err := DeleteCredentials(); err != nil {
t.Fatalf("delete: %v", err)
}
if out, _ := LoadCredentials(); out.AccessToken != "" {
t.Fatalf("credentials not deleted")
}
}
func TestLoadMissingFilesIsZeroValue(t *testing.T) {
sandbox(t)
cfg, err := LoadConfig()
if err != nil || cfg.Org != "" {
t.Fatalf("missing config should be zero value, got %+v err %v", cfg, err)
}
creds, err := LoadCredentials()
if err != nil || creds.AccessToken != "" {
t.Fatalf("missing credentials should be zero value, got %+v err %v", creds, err)
}
}
func TestResolveDefaults(t *testing.T) {
sandbox(t)
e := resolve(&Config{}, &Credentials{}, globalFlags{})
if e.IAMIssuer != defaultIAMIssuer || e.PlatformURL != defaultPlatformURL ||
e.CloudURL != defaultCloudURL || e.ClientID != defaultClientID || e.Output != "table" {
t.Fatalf("defaults not applied: %+v", e)
}
}
func TestResolvePrecedenceFlagOverEnvOverConfig(t *testing.T) {
sandbox(t)
t.Setenv("HANZO_ORG", "env-org")
cfg := &Config{Org: "cfg-org", Output: "json"}
// Flag wins.
if e := resolve(cfg, &Credentials{}, globalFlags{org: "flag-org"}); e.Org != "flag-org" {
t.Fatalf("flag should win: %q", e.Org)
}
// Env beats config.
if e := resolve(cfg, &Credentials{}, globalFlags{}); e.Org != "env-org" {
t.Fatalf("env should beat config: %q", e.Org)
}
// Config used when no flag/env.
t.Setenv("HANZO_ORG", "")
if e := resolve(cfg, &Credentials{}, globalFlags{}); e.Org != "cfg-org" {
t.Fatalf("config should be used: %q", e.Org)
}
}
func TestPlatformTokenPrecedence(t *testing.T) {
sandbox(t)
e := resolve(&Config{}, &Credentials{PlatformToken: "from-creds"}, globalFlags{})
if got := e.platformToken(""); got != "from-creds" {
t.Fatalf("creds token: %q", got)
}
t.Setenv("PAAS_SERVICE_TOKEN", "from-paas")
if got := e.platformToken(""); got != "from-paas" {
t.Fatalf("PAAS env should beat creds: %q", got)
}
t.Setenv("PLATFORM_SERVICE_TOKEN", "from-platform")
if got := e.platformToken(""); got != "from-platform" {
t.Fatalf("PLATFORM env should beat PAAS: %q", got)
}
t.Setenv("HANZO_PLATFORM_TOKEN", "from-hanzo")
if got := e.platformToken(""); got != "from-hanzo" {
t.Fatalf("HANZO_PLATFORM_TOKEN should beat all envs: %q", got)
}
if got := e.platformToken("from-flag"); got != "from-flag" {
t.Fatalf("flag should beat everything: %q", got)
}
}
// TestPlatformTokenFallsBackToIAM is the UNIFY-INFRA contract for the control
// plane: after a plain `hanzo login`, the IAM access token is the FINAL fallback
// so `hanzo apps`/`hanzo deploy` authorize off the one identity. An explicit
// platform service token (creds/env/flag) still wins.
func TestPlatformTokenFallsBackToIAM(t *testing.T) {
sandbox(t)
// Only an IAM login: no platform token anywhere ⇒ the IAM access token is sent.
e := resolve(&Config{}, &Credentials{AccessToken: "iam-jwt"}, globalFlags{})
if got := e.platformToken(""); got != "iam-jwt" {
t.Fatalf("IAM access token should be the final platform-token fallback: %q", got)
}
// A dedicated platform service token still beats the IAM token.
e = resolve(&Config{}, &Credentials{AccessToken: "iam-jwt", PlatformToken: "svc"}, globalFlags{})
if got := e.platformToken(""); got != "svc" {
t.Fatalf("dedicated platform token must beat the IAM fallback: %q", got)
}
// No login at all ⇒ empty (caller surfaces "run `hanzo login`").
e = resolve(&Config{}, &Credentials{}, globalFlags{})
if got := e.platformToken(""); got != "" {
t.Fatalf("no token and no login should resolve empty: %q", got)
}
}
func TestBuildTokenPrecedence(t *testing.T) {
sandbox(t)
e := resolve(&Config{}, &Credentials{BuildToken: "creds"}, globalFlags{})
if got := e.buildToken(""); got != "creds" {
t.Fatalf("creds build token: %q", got)
}
t.Setenv("PLATFORM_BUILD_CALLBACK_TOKEN", "cb")
if got := e.buildToken(""); got != "cb" {
t.Fatalf("callback env: %q", got)
}
if got := e.buildToken("flag"); got != "flag" {
t.Fatalf("flag wins: %q", got)
}
}
// TestBuildTokenFallsBackToIAM is the UNIFY-INFRA contract: after a plain
// `hanzo login` (no --build-token), the IAM access token is the FINAL fallback,
// so `hanzo build` authorizes off the one identity. An explicit build token
// (creds/env/flag) still wins — the IAM token is the LAST resort, never an
// override of a purpose-minted machine token.
func TestBuildTokenFallsBackToIAM(t *testing.T) {
sandbox(t)
// Only an IAM login: no build token anywhere ⇒ the IAM access token is sent.
e := resolve(&Config{}, &Credentials{AccessToken: "iam-jwt"}, globalFlags{})
if got := e.buildToken(""); got != "iam-jwt" {
t.Fatalf("IAM access token should be the final build-token fallback: %q", got)
}
// A dedicated build token still beats the IAM token (precedence preserved).
e = resolve(&Config{}, &Credentials{AccessToken: "iam-jwt", BuildToken: "creds"}, globalFlags{})
if got := e.buildToken(""); got != "creds" {
t.Fatalf("dedicated build token must beat the IAM fallback: %q", got)
}
// HANZO_TOKEN (the env form of the IAM token) is also honored via accessToken().
e = resolve(&Config{}, &Credentials{}, globalFlags{})
t.Setenv("HANZO_TOKEN", "iam-env")
if got := e.buildToken(""); got != "iam-env" {
t.Fatalf("HANZO_TOKEN should back the build-token fallback: %q", got)
}
// No login at all ⇒ empty, so the caller can surface "run `hanzo login`".
t.Setenv("HANZO_TOKEN", "")
e = resolve(&Config{}, &Credentials{}, globalFlags{})
if got := e.buildToken(""); got != "" {
t.Fatalf("no token and no login should resolve empty: %q", got)
}
}
func TestAccessTokenFromEnvOverCreds(t *testing.T) {
sandbox(t)
e := resolve(&Config{}, &Credentials{AccessToken: "creds"}, globalFlags{})
if got := e.accessToken(); got != "creds" {
t.Fatalf("creds token: %q", got)
}
t.Setenv("HANZO_TOKEN", "env")
if got := e.accessToken(); got != "env" {
t.Fatalf("env token should win: %q", got)
}
}
func TestRequireOrg(t *testing.T) {
sandbox(t)
e := resolve(&Config{}, &Credentials{}, globalFlags{})
if _, err := e.requireOrg(); err == nil {
t.Fatalf("expected error when org unset")
}
e = resolve(&Config{Org: "acme"}, &Credentials{}, globalFlags{})
if org, err := e.requireOrg(); err != nil || org != "acme" {
t.Fatalf("org=%q err=%v", org, err)
}
}
func TestConfigFieldGetSet(t *testing.T) {
c := &Config{}
if err := c.setField("org", "acme"); err != nil || c.Org != "acme" {
t.Fatalf("set org: %v", err)
}
if v, _ := c.field("org"); v != "acme" {
t.Fatalf("get org: %q", v)
}
if err := c.setField("output", "xml"); err == nil {
t.Fatalf("invalid output should error")
}
if err := c.setField("nope", "x"); err == nil {
t.Fatalf("unknown key should error")
}
if _, err := c.field("nope"); err == nil {
t.Fatalf("unknown key get should error")
}
}
func TestIsControlVerb(t *testing.T) {
for _, v := range []string{"login", "apps", "deploy", "clusters", "build", "k8s", "config", "auth", "whoami", "logout"} {
if !IsControlVerb(v) {
t.Errorf("%q should be a control verb", v)
}
}
for _, v := range []string{"iam", "kms", "cloud", "gateway", "datastore", "nope"} {
if IsControlVerb(v) {
t.Errorf("%q must NOT be a control verb (server mode)", v)
}
}
}
func TestEmitJSONvsTable(t *testing.T) {
// JSON branch: encodes the value, ignores the table func.
var jbuf bytes.Buffer
ej := &Env{Output: "json", out: &jbuf}
called := false
if err := ej.emit(map[string]string{"k": "v"}, func(_ io.Writer) { called = true }); err != nil {
t.Fatalf("emit json: %v", err)
}
if called {
t.Fatalf("table func must not run in json mode")
}
var got map[string]string
if err := json.Unmarshal(jbuf.Bytes(), &got); err != nil || got["k"] != "v" {
t.Fatalf("json output bad: %q (%v)", jbuf.String(), err)
}
// Table branch: runs the table func, does not emit JSON.
var tbuf bytes.Buffer
et := &Env{Output: "table", out: &tbuf}
if err := et.emit(map[string]string{"k": "v"}, func(w io.Writer) { _, _ = w.Write([]byte("ROW")) }); err != nil {
t.Fatalf("emit table: %v", err)
}
if !strings.Contains(tbuf.String(), "ROW") {
t.Fatalf("table output missing: %q", tbuf.String())
}
}
+697
View File
@@ -0,0 +1,697 @@
package cli
// code.go — `hanzo code <agent> [model]`: launch a coding agent on the Hanzo AI
// cloud. ONE way to start ANY agent on ANY Hanzo model: the endpoint, the
// credential and the model are injected for you; nothing to export, nothing to
// remember.
//
// hanzo code claude # Claude Code on the default model
// hanzo code codex enso-pro
// hanzo code dev zen5 # ids are resolved fuzzily: zen5pro -> zen5-pro
// hanzo code ls # what can I run?
//
// Two wire protocols cover all three agents: Claude Code speaks Anthropic,
// Codex and @hanzo/dev (a Codex fork) speak OpenAI — so an agent is just a
// binary + a wire + the flag that turns approvals off. Agents run full-auto by
// default (--safe restores prompting).
import (
"encoding/json"
"fmt"
"net/http"
"os"
"os/exec"
"path/filepath"
"sort"
"strings"
"time"
"unicode"
"github.com/spf13/cobra"
)
// defaultCodeModel is the model `hanzo code <agent>` runs when no model is
// named. It must be a catalog-served id with working tool calls: coding agents
// cannot operate on a text-only model even when its SSE transport is healthy.
// zen5 is the flagship GLM-5.2-class capability alias (1M ctx, tool-capable) —
// the frontier coding tier. Do not use the virtual `best`: Claude Code treats
// it (like `opus`/`sonnet`/`haiku`) as a reserved alias and rewrites it to a
// claude-* id that api.hanzo.ai does not serve. Override per invocation with an
// explicit id: `hanzo code claude zen5-pro`.
const defaultCodeModel = "zen5"
// A zenTier bridges a model id Claude Code recognizes (the carrier) to the zen
// alias api.hanzo.ai serves. CC sizes a model's context window and features only
// from ids it knows; an unknown id like "zen5-pro" gets a 128K budget and is
// rejected client-side above it — the "max context 131072" the server never
// actually imposes. Nothing lets us declare a custom model's window, so the
// carrier (a known 1M id, [1m] where needed) unlocks the budget and modelOverrides
// rewrites it back to zen before the request leaves the client — the carrier never
// reaches the server. Requires Claude Code v2.1.200+.
type zenTier struct {
zen string // served zen alias — the wire model api.hanzo.ai receives
carrier string // recognized id CC budgets from; "" pins zen directly (fast tiers, never >128K)
env string // ANTHROPIC_DEFAULT_*_MODEL slot ("" = selectable, no slot)
name string // /model picker label (via _NAME, gateway-effective)
desc string // /model picker description (via _DESCRIPTION)
}
// slotID is the tier's wire value: its carrier, or the zen id when direct.
func (t zenTier) slotID() string {
if t.carrier != "" {
return t.carrier
}
return t.zen
}
// zenTiers is the ONE source of truth for the CC-tier ⇆ zen mapping — the wire
// env, picker branding, and modelOverrides all derive from it. Every zen id must
// be one api.hanzo.ai serves (TestZenTiersServeReal); zen5-mini/max/ultra are
// listed but not served, so fable maps to zen5-pro until zen5-max returns.
var zenTiers = []zenTier{
{zen: "zen5-flash", env: "ANTHROPIC_DEFAULT_HAIKU_MODEL", name: "Zen5 Flash", desc: "Hanzo Zen5 Flash — fast, cheap tier"},
{zen: "zen5", carrier: "claude-sonnet-4-6[1m]", env: "ANTHROPIC_DEFAULT_SONNET_MODEL", name: "Zen5", desc: "Hanzo Zen5 — frontier tier (1M context)"},
{zen: "zen5-pro", carrier: "claude-opus-4-8[1m]", env: "ANTHROPIC_DEFAULT_OPUS_MODEL", name: "Zen5 Pro", desc: "Hanzo Zen5 Pro — deep reasoning (1M context)"},
{zen: "zen5-pro", carrier: "claude-fable-5[1m]", env: "ANTHROPIC_DEFAULT_FABLE_MODEL", name: "Zen5 Pro (max effort)", desc: "Hanzo Zen5 Pro, top tier (1M context)"},
{zen: "zen5-coder", carrier: "claude-sonnet-5", name: "Zen5 Coder", desc: "Hanzo Zen5 Coder — code-specialized (1M context)"},
}
// zenCarrier maps a resolved zen alias to the carrier CC budgets from; an unknown
// id passes through with CC's default budget.
func zenCarrier(model string) string {
for _, t := range zenTiers {
if t.zen == model {
return t.slotID()
}
}
return model
}
// stripModelSuffix drops the "[1m]" suffix so a carrier matches its override key.
func stripModelSuffix(id string) string {
if i := strings.IndexByte(id, '['); i >= 0 {
return id[:i]
}
return id
}
// claudeModelOverrides is the carrier→zen map for settings.json: CC budgets from
// the carrier key and sends the zen value on the wire. Direct tiers need no entry.
func claudeModelOverrides() map[string]string {
m := make(map[string]string, len(zenTiers))
for _, t := range zenTiers {
if t.carrier != "" {
m[stripModelSuffix(t.carrier)] = t.zen
}
}
return m
}
// wire builds the env that points an agent's SDK at the Hanzo cloud.
type wire func(base, token, model string) map[string]string
// anthropicWire points Claude Code at the Hanzo cloud and pins each CC tier slot
// to its carrier (see zenTier), so subagents, the classifier, and /compact get
// the right context budget while modelOverrides rewrites carriers back to zen ids
// on the wire. `model` arrives already mapped to its carrier (runCode).
func anthropicWire(base, token, model string) map[string]string {
env := map[string]string{
"ANTHROPIC_BASE_URL": base,
"ANTHROPIC_AUTH_TOKEN": token,
"ANTHROPIC_MODEL": model,
}
for _, t := range zenTiers {
if t.env == "" {
continue
}
env[t.env] = t.slotID()
env[t.env+"_NAME"] = t.name
env[t.env+"_DESCRIPTION"] = t.desc
// SMALL_FAST_MODEL is deprecated AND not rewritten by modelOverrides, so
// it must hold a served zen id directly — mirror the (direct) haiku slot.
if t.env == "ANTHROPIC_DEFAULT_HAIKU_MODEL" {
env["ANTHROPIC_SMALL_FAST_MODEL"] = t.slotID()
}
}
return env
}
func openaiWire(base, token, _ string) map[string]string {
return map[string]string{
"OPENAI_BASE_URL": strings.TrimSuffix(base, "/") + "/v1",
"OPENAI_API_KEY": token,
}
}
type codeAgent struct {
bin string // executable to exec
wire wire // how it finds the cloud
fullAuto []string // flags that bypass approval prompts
continueArgs []string // harness-native form of Hanzo -c/--continue
modelArg []string // how the model is passed on argv (empty: via env)
carrier func(model string) string // maps the resolved model to a client-recognized id (claude: zen→carrier); nil = pass through
provider func(base, model string) []string // agents that need the endpoint declared, not just env'd
clear []string // env that would shadow the wire (a stale key in the shell)
configHome string // env var that relocates the agent's config dir to ~/.hanzo ("" = share the user's own install)
seed func(dir string) error // one-time defaults for the isolated config dir
appendSystem []string // --append-system-prompt + text; ALWAYS applied (identity, not a permission bypass — present in --safe too)
mcp bool // auto-wire the Hanzo MCP server (code/vector/web/vision tools) as an stdio server scoped to the cwd
install string // hint when the binary is missing
}
// codeContextWindow is the input context (tokens) the served coding model
// budgets from. The enso and zen5 flagship tiers serve 1M; the flash tiers
// serve 131072. Codex is told this so it sizes context to the real window
// instead of a flat 256K cap — the cause of "maximum context exceeded" at
// 262144 even on a 1M-capable model. This wrapper only launches Hanzo coding
// models (default zen5), so non-flash defaults to the 1M flagship window.
func codeContextWindow(model string) int {
if strings.Contains(strings.ToLower(model), "flash") {
return 131072
}
return 1000000
}
// codex and @hanzo/dev share a lineage (dev is a Codex fork), hence a wire.
// They also ignore OPENAI_BASE_URL and talk to chatgpt.com unless a provider is
// declared, so declare Hanzo as the provider and select it.
func codexLike(bin, install string) codeAgent {
return codeAgent{
bin: bin,
wire: openaiWire,
fullAuto: []string{"--dangerously-bypass-approvals-and-sandbox"},
continueArgs: []string{"resume", "--last"},
modelArg: []string{"-m"},
provider: func(base, model string) []string {
// api.hanzo.ai exposes the standard OpenAI /v1/models shape, not
// Codex's private remote model-catalog schema, so skip that refresh
// and supply the model's window here — sized to the SERVED model
// (enso / zen5 flagship = 1M, flash tiers = 131072) so Codex budgets
// the real context instead of a flat 256K cap (the "maximum context
// exceeded at 262144" bug). Auto-compact at 90% leaves headroom.
win := codeContextWindow(model)
return []string{
"-c", "model_provider=hanzo",
"-c", `model_providers.hanzo.name="Hanzo"`,
"-c", fmt.Sprintf(`model_providers.hanzo.base_url="%s/v1"`, strings.TrimSuffix(base, "/")),
"-c", `model_providers.hanzo.env_key="OPENAI_API_KEY"`,
"-c", `model_providers.hanzo.wire_api="responses"`,
"-c", `features.remote_models=false`,
"-c", fmt.Sprintf("model_context_window=%d", win),
"-c", fmt.Sprintf("model_auto_compact_token_limit=%d", win*9/10),
}
},
install: install,
}
}
// zenIdentityPrompt is appended to Claude Code's base system prompt so a model
// served through the Hanzo cloud self-identifies as a Hanzo Zen model. It is an
// APPEND, not a replace: Claude Code keeps its base prompt (tool-use, safety,
// coding conventions); only the model's identity is Hanzo Zen. The model is
// served as a zen5 alias via api.hanzo.ai. Passed as --append-system-prompt,
// present in --safe too (identity is not a permission bypass).
const zenIdentityPrompt = "You are running through the Hanzo AI cloud as a Hanzo Zen model (the `zen5` capability tier, served via api.hanzo.ai). When asked what model or assistant you are, identify as a Hanzo Zen model. You are operating inside the Claude Code harness; keep its tool-use, safety, and coding conventions — only your identity is Hanzo Zen."
var codeAgents = map[string]codeAgent{
"claude": {
bin: "claude",
wire: anthropicWire,
fullAuto: []string{"--dangerously-skip-permissions"},
continueArgs: []string{"--continue"},
// --model forces the session model on argv. Claude Code persists the
// user's last /model selection (e.g. the reserved word "best"), and that
// persisted choice OVERRIDES ANTHROPIC_MODEL — so the env var alone cannot
// pin the model. --model is the per-session override that beats it. CC
// budgets the context window from this (carrier) id, then rewrites it to
// the zen alias via modelOverrides before the request leaves the client —
// so api.hanzo.ai serves the zen id regardless of what /model last held.
modelArg: []string{"--model"},
// zen→carrier: hand CC a model it recognizes so it grants the full (1M)
// context budget; claudeSettings' modelOverrides maps it back to zen.
carrier: zenCarrier,
// Stamp the identity: append the Hanzo Zen identity to CC's base prompt so
// the served model says it is a Hanzo Zen model when asked. An append (not
// --system-prompt) keeps CC's harness prompt intact; applied in --safe too.
appendSystem: []string{"--append-system-prompt", zenIdentityPrompt},
clear: []string{"ANTHROPIC_API_KEY"}, // outranks AUTH_TOKEN: a stale one silently wins
// Its own config home under ~/.hanzo, not the user's ~/.claude. Claude
// Code and `hanzo code claude` are independent products: sharing one
// mutable config braids them — the user's saved /model (e.g. "fable")
// leaks in as the session identity, and hanzo's zen5 picks leak back out.
// A separate home decomplects them; the injected zen5 slots then show
// cleanly in /model instead of a stale saved value.
configHome: "CLAUDE_CONFIG_DIR",
seed: seedClaudeConfig,
// Auto-wire the Hanzo MCP server so `hanzo code claude` starts with the
// Hanzo tool lattice (code search over the cloud index, web search, vision,
// fs/exec/git) instead of a bare model. Resolved + injected in runCode.
mcp: true,
install: "npm i -g @anthropic-ai/claude-code",
},
"codex": codexLike("codex", "npm i -g @openai/codex"),
"dev": codexLike("dev", "npm i -g @hanzo/dev"),
}
// defaultAgent is the agent `hanzo code` (no agent named) and bare `hanzo` launch:
// HANZO_CODE_TOOL, else the config `code_tool`, else dev — the Hanzo agent. An
// unknown value falls back to dev rather than failing, so a stale preference never
// blocks the default flow.
func defaultAgent(env *Env) codeAgent {
name := firstNonEmpty(os.Getenv("HANZO_CODE_TOOL"), env.cfg.CodeTool)
if a, ok := codeAgents[name]; ok {
return a
}
return codeAgents["dev"]
}
func newCodeCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
cmd := &cobra.Command{
Use: "code [agent] [model] [-- args]",
Short: "Launch a coding agent (dev, claude, codex) on a Hanzo cloud model",
Long: "Run @hanzo/dev, Claude Code, or Codex against api.hanzo.ai with the endpoint,\n" +
"credential and model injected — no env vars to remember. `hanzo code` alone runs\n" +
"dev (the Hanzo agent); name an agent to pick another. Model ids resolve fuzzily\n" +
"(zen5pro -> zen5-pro), -c resumes either harness, and agents run full-auto unless\n" +
"you pass --safe. Unknown options pass through; -- forces verbatim passthrough.",
Example: " hanzo code # dev, the default agent\n" +
" hanzo code claude\n" +
" hanzo code claude -c\n" +
" hanzo code codex -c\n" +
" hanzo code codex enso-pro\n" +
" hanzo code dev zen5 -- --resume\n" +
" hanzo code ls",
// Bare `hanzo code` (or `hanzo code <model>/-- args` with no agent name) runs
// the configured default agent (code_tool, else dev). A recognized agent name
// (or `ls`) dispatches to its subcommand; anything else is the agent's args, so
// `hanzo code glm5.2` works too.
DisableFlagParsing: true,
RunE: func(c *cobra.Command, args []string) error {
if len(args) > 0 {
if _, isAgent := codeAgents[args[0]]; isAgent || args[0] == "ls" {
sub, _, err := c.Find(args)
if err == nil && sub != c {
sub.SetArgs(args[1:])
return sub.Execute()
}
}
}
return runCode(envOf(), defaultAgent(envOf()), args)
},
}
names := make([]string, 0, len(codeAgents))
for name := range codeAgents {
names = append(names, name)
}
sort.Strings(names)
for _, name := range names {
agent := codeAgents[name]
cmd.AddCommand(&cobra.Command{
Use: name + " [model] [-- args]",
Short: "Launch " + name + " on a Hanzo model (default: " + defaultCodeModel + ")",
DisableFlagParsing: true, // agent flags (--resume, -c …) pass straight through
RunE: func(c *cobra.Command, args []string) error {
return runCode(envOf(), agent, args)
},
})
}
cmd.AddCommand(&cobra.Command{
Use: "ls",
Aliases: []string{"models", "list"},
Short: "List the models this account can run",
Args: cobra.NoArgs,
RunE: func(c *cobra.Command, _ []string) error {
env := envOf()
models, err := catalog(env)
if err != nil {
return err
}
for _, m := range models {
fmt.Fprintln(env.out, m)
}
return nil
},
})
return cmd
}
func runCode(env *Env, agent codeAgent, args []string) error {
bin, err := exec.LookPath(agent.bin)
if err != nil {
return fmt.Errorf("%s is not installed — try: %s", agent.bin, agent.install)
}
token := codeToken(env)
if token == "" {
return fmt.Errorf("no Hanzo credential — run `hanzo login`, or set HANZO_API_KEY")
}
base := strings.TrimSuffix(firstNonEmpty(env.CloudURL, "https://api.hanzo.ai"), "/")
// First non-flag arg before -- is the model; --safe and --continue are ours.
// Unknown options pass through unchanged. Everything after -- belongs to the
// agent, including positional subcommands and raw Codex -c config overrides.
model, safe, continueLast, rest := splitCodeArgs(args)
if model == "" {
model = defaultCodeModel
}
if model, err = resolveModel(env, model); err != nil {
return err
}
// Resolve the served zen id first (above), THEN hand the agent its carrier:
// the id its client recognizes for context/feature budgeting. The zen id is
// what api.hanzo.ai serves; the carrier is a client-side concern only.
served := model
if agent.carrier != nil {
model = agent.carrier(model)
}
for _, k := range agent.clear {
if err := os.Unsetenv(k); err != nil {
return err
}
}
// The isolated config dir is resolved BEFORE argv so the MCP config file can be
// written into it (and cleaned with the rest of the session state).
var configDir string
if agent.configHome != "" {
dir, err := hanzoDir()
if err != nil {
return err
}
if agent.seed != nil {
if err := agent.seed(dir); err != nil {
return err
}
}
if err := os.Setenv(agent.configHome, dir); err != nil {
return err
}
configDir = dir
}
// Auto-wire the Hanzo MCP server (code search over the cloud index, web search,
// vision, fs/exec/git) so the agent starts with the tool lattice, not a bare
// model. Appended to the agent's own args; a missing server warns, never blocks.
if agent.mcp && configDir != "" {
cwd, _ := os.Getwd()
if flags, warn := mcpArgs(configDir, cwd); warn != "" {
fmt.Fprintf(env.out, "hanzo mcp: %s\n", warn)
} else {
rest = append(rest, flags...)
}
}
argv := codeArgv(agent, base, model, safe, codeAgentRest(agent, continueLast, rest))
for k, v := range agent.wire(base, token, model) {
if err := os.Setenv(k, v); err != nil {
return err
}
}
if served != model {
fmt.Fprintf(env.out, "%s → %s (as %s) on %s\n", agent.bin, served, model, base)
} else {
fmt.Fprintf(env.out, "%s → %s on %s\n", agent.bin, model, base)
}
return execEngine(bin, argv) // exec: signals + exit code flow straight through
}
// splitCodeArgs pulls the launcher-owned tokens (the model, --safe, -c/--continue)
// out of the raw args; everything else is the agent's. The `--` separator is ours
// and switches on verbatim passthrough — every token after it goes to the agent
// untouched, including positional subcommands (`codex exec`) and raw Codex -c
// config overrides that would otherwise look like our --continue.
func splitCodeArgs(args []string) (model string, safe, continueLast bool, rest []string) {
rest = make([]string, 0, len(args))
passthrough := false
for _, a := range args {
switch {
case passthrough:
rest = append(rest, a)
case a == "--": // the separator is ours; the agent must not see it
passthrough = true
case a == "--safe" || a == "--ask":
safe = true
case a == "-c" || a == "--continue":
continueLast = true
case model == "" && !strings.HasPrefix(a, "-") && len(rest) == 0:
model = a
default:
rest = append(rest, a)
}
}
return model, safe, continueLast, rest
}
// codeAgentRest prepends the agent's harness-native resume tokens when -c/--continue
// was given, so one Hanzo flag resumes the last session on either harness (`--continue`
// for Claude Code, `resume --last` for Codex/dev).
func codeAgentRest(agent codeAgent, continueLast bool, rest []string) []string {
if !continueLast {
return rest
}
args := make([]string, 0, len(agent.continueArgs)+len(rest))
args = append(args, agent.continueArgs...)
return append(args, rest...)
}
// codeArgv builds the final agent command line. Permission bypass is the
// launcher default for every agent; --safe is the single explicit opt-out.
func codeArgv(agent codeAgent, base, model string, safe bool, rest []string) []string {
argv := []string{agent.bin}
if !safe {
argv = append(argv, agent.fullAuto...)
}
if agent.provider != nil {
argv = append(argv, agent.provider(base, model)...)
}
if len(agent.modelArg) > 0 { // claude takes the model via env, codex/dev on argv
argv = append(argv, agent.modelArg...)
argv = append(argv, model)
}
argv = append(argv, agent.appendSystem...) // identity — applies in safe AND full-auto
argv = append(argv, rest...)
return argv
}
// mcpArgs resolves the Hanzo MCP server and returns the flags that attach it to a
// claude session, scoped to cwd. It ports the Rust CLI's resolve_mcp: prefer an
// installed `hanzo-mcp` on PATH, else `uvx hanzo-mcp` (ephemeral), else nothing —
// MCP is an enhancement, so a missing server never blocks the session. The Hanzo
// server is layered via --mcp-config, and --strict-mcp-config makes it the SOLE
// MCP source: a repo's own .mcp.json is NOT loaded (it can carry a hostile stdio
// server that would inherit the session's bearer). The config file is written into
// the isolated config dir so it is cleaned with the rest of the hanzo session state.
//
// Returns the argv flags to append (possibly empty) and a warning to surface when
// no server could be resolved, so the caller can tell the user tools are absent.
func mcpArgs(configDir, cwd string) (flags []string, warn string) {
prog, args := resolveHanzoMCP(cwd)
if prog == "" {
return nil, "hanzo-mcp not found (install: `uv tool install hanzo-mcp`); launching without Hanzo tools"
}
cfg := mcpConfigJSON(prog, args)
path := filepath.Join(configDir, "mcp.json")
if err := os.WriteFile(path, []byte(cfg), 0o600); err != nil {
return nil, "could not write MCP config; launching without Hanzo tools"
}
// --strict-mcp-config: the Hanzo server is the ONLY MCP source (a repo
// .mcp.json is ignored — it could ship a bearer-exfiltrating stdio server).
return []string{"--mcp-config", path, "--strict-mcp-config"}, ""
}
// resolveHanzoMCP finds how to launch hanzo-mcp as an stdio server scoped to cwd:
// an installed console script first, else uv's ephemeral runner. Empty program =
// neither is on PATH.
func resolveHanzoMCP(cwd string) (prog string, args []string) {
if p, err := exec.LookPath("hanzo-mcp"); err == nil {
return p, []string{"--project-dir", cwd}
}
if p, err := exec.LookPath("uvx"); err == nil {
return p, []string{"hanzo-mcp", "--project-dir", cwd}
}
return "", nil
}
// mcpConfigJSON is the --mcp-config document adding Hanzo's stdio server. Claude
// requires an explicit "type". Marshaled (not fmt'd) so the cwd/program are
// correctly escaped.
func mcpConfigJSON(prog string, args []string) string {
doc := map[string]any{
"mcpServers": map[string]any{
"hanzo": map[string]any{
"type": "stdio",
"command": prog,
"args": args,
"env": map[string]string{},
},
},
}
b, _ := json.Marshal(doc)
return string(b)
}
// seedClaudeConfig writes first-run defaults into the isolated config dir so
// `hanzo code claude` starts clean: auto-approve, high effort, onboarding done,
// and NO pinned model (the zen5 slots come from the injected env, not saved
// state). It never overwrites — the user's own later edits in this dir persist.
func seedClaudeConfig(dir string) error {
if err := upsertClaudeSettings(filepath.Join(dir, "settings.json")); err != nil {
return err
}
return writeIfAbsent(filepath.Join(dir, ".claude.json"), "{\"hasCompletedOnboarding\":true}\n")
}
// claudeSettingsBase is the first-run settings.json for `hanzo code claude`:
// sensible agent defaults and no pinned model, so the env-injected carrier slots
// win. effortLevel is max — the deepest reasoning tier — matching the operator's
// /effort max session setting; zen folds it into the upstream's reasoning budget
// (anthropicThinkingBudget → normalizeReasoning) so it reaches the model. Applied
// only when settings.json does not yet exist — later user edits to these persist.
var claudeSettingsBase = map[string]any{
"includeCoAuthoredBy": false,
"permissions": map[string]any{"defaultMode": "auto"},
"skipAutoPermissionPrompt": true,
"skipDangerousModePermissionPrompt": true,
"effortLevel": "max",
"theme": "dark",
"enableWorkflows": true,
}
// upsertClaudeSettings writes settings.json, (re)applying the operator-owned
// modelOverrides (carrier→zen) on EVERY launch while preserving the user's own
// edits to every other key. modelOverrides is policy, not preference: it must
// track the current zenTiers so Claude Code's context-budgeting carriers keep
// mapping to the served zen ids — so, unlike the base defaults, it is not
// write-once. A first run (or an unreadable/corrupt file) starts from the base.
func upsertClaudeSettings(path string) error {
settings := map[string]any{}
if b, err := os.ReadFile(path); err != nil || json.Unmarshal(b, &settings) != nil || len(settings) == 0 {
settings = map[string]any{}
for k, v := range claudeSettingsBase {
settings[k] = v
}
}
overrides := make(map[string]any, len(zenTiers))
for carrier, zen := range claudeModelOverrides() {
overrides[carrier] = zen
}
settings["modelOverrides"] = overrides
b, err := json.MarshalIndent(settings, "", " ")
if err != nil {
return err
}
return os.WriteFile(path, append(b, '\n'), 0o600)
}
// writeIfAbsent creates path with content only when it does not already exist,
// so seeding a config dir never clobbers a user's later edits.
func writeIfAbsent(path, content string) error {
if _, err := os.Stat(path); err == nil {
return nil
}
return os.WriteFile(path, []byte(content), 0o600)
}
// codeToken resolves the credential the agents authenticate with. Precedence:
// an explicit HANZO_API_KEY always wins (the operator's deliberate override),
// then the live `hanzo login` JWT, then the hk- API key chain.
//
// Why the JWT beats the hk- key: the JWT carries the caller's owner/project/sub
// claims verbatim, so the identity boundary mints a billing principal on EVERY
// deployment. The hk- key only mints a principal when the server can resolve it
// (iamKeys.resolve, which is a no-op without IAM_MINT_CLIENT_ID/SECRET) — on a
// deployment lacking that credential an hk- request arrives anonymous and zen's
// billing gate 402s ("a billable tenant is required"). Preferring a FRESH JWT
// keeps `hanzo code` working everywhere; the hk- key stays the fallback for
// mint-credentialed servers and the explicit-override case. freshAccessToken
// skips an expired token so it can't 401 a session a valid hk- key would serve.
func codeToken(env *Env) string {
return firstNonEmpty(os.Getenv("HANZO_API_KEY"), env.freshAccessToken(), env.cfg.APIKey, storedAPIKey())
}
// storedAPIKey reads (never writes) the hk- key that hanzo-mcp and the rest of
// the toolchain share, so one `hanzo login`/key serves every tool.
func storedAPIKey() string {
dir, err := hanzoDir()
if err != nil {
return ""
}
var cfg struct {
APIKey string `json:"apiKey"`
}
if err := loadJSON(filepath.Join(dir, "config.json"), &cfg); err != nil {
return ""
}
return cfg.APIKey
}
// resolveModel turns what you typed into an id the cloud serves. Exact ids pass
// through; otherwise ids are compared with punctuation and case removed, so
// "glm5.2" finds "glm-5.2". An unknown id lists the near misses rather than
// failing deep inside the agent.
func resolveModel(env *Env, want string) (string, error) {
models, err := catalog(env)
if err != nil {
// Never hand an agent a model we could not confirm: it would fail deep
// inside the session with an opaque error. Say so here instead.
return "", fmt.Errorf("cannot read the model catalog: %w", err)
}
fold := func(s string) string {
return strings.Map(func(r rune) rune {
if unicode.IsLetter(r) || unicode.IsDigit(r) {
return unicode.ToLower(r)
}
return -1
}, s)
}
target := fold(want)
var near []string
for _, m := range models {
switch f := fold(m); {
case m == want, f == target:
return m, nil
case strings.Contains(f, target), strings.Contains(target, f):
near = append(near, m)
}
}
if len(near) == 1 {
return near[0], nil
}
if len(near) > 1 {
return "", fmt.Errorf("%q is ambiguous — did you mean: %s", want, strings.Join(near, ", "))
}
return "", fmt.Errorf("no model %q — run `hanzo code ls` to see what you can run", want)
}
func catalog(env *Env) ([]string, error) {
base := strings.TrimSuffix(firstNonEmpty(env.CloudURL, "https://api.hanzo.ai"), "/")
req, err := http.NewRequest(http.MethodGet, base+"/v1/models", nil)
if err != nil {
return nil, err
}
req.Header.Set("Authorization", "Bearer "+codeToken(env))
resp, err := (&http.Client{Timeout: 15 * time.Second}).Do(req)
if err != nil {
return nil, err
}
defer resp.Body.Close()
if resp.StatusCode != http.StatusOK {
return nil, fmt.Errorf("%s/v1/models: %s", base, resp.Status)
}
var body struct {
Data []struct {
ID string `json:"id"`
} `json:"data"`
}
if err := json.NewDecoder(resp.Body).Decode(&body); err != nil {
return nil, err
}
ids := make([]string, 0, len(body.Data))
for _, m := range body.Data {
ids = append(ids, m.ID)
}
sort.Strings(ids)
return ids, nil
}
+499
View File
@@ -0,0 +1,499 @@
// Copyright 2023-2025 Hanzo AI Inc. All Rights Reserved.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
package cli
import (
"encoding/json"
"os"
"path/filepath"
"reflect"
"slices"
"testing"
"time"
)
func TestCodeAgentsBypassPermissionsByDefault(t *testing.T) {
tests := []struct {
name string
flag string
}{
{name: "claude", flag: "--dangerously-skip-permissions"},
{name: "codex", flag: "--dangerously-bypass-approvals-and-sandbox"},
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
agent := codeAgents[tt.name]
argv := codeArgv(agent, "https://api.hanzo.ai", defaultCodeModel, false, nil)
if !slices.Contains(argv, tt.flag) {
t.Fatalf("default argv %q does not contain permission bypass %q", argv, tt.flag)
}
safeArgv := codeArgv(agent, "https://api.hanzo.ai", defaultCodeModel, true, nil)
if slices.Contains(safeArgv, tt.flag) {
t.Fatalf("--safe argv %q still contains permission bypass %q", safeArgv, tt.flag)
}
})
}
}
func TestCodeArgsSeparatorPreservesAgentSubcommand(t *testing.T) {
model, safe, continueLast, rest := splitCodeArgs([]string{"--safe", "--", "exec", "--ephemeral", "do it"})
if model != "" || !safe || continueLast {
t.Fatalf("model=%q safe=%v continue=%v, want default model and safe mode", model, safe, continueLast)
}
if want := []string{"exec", "--ephemeral", "do it"}; !reflect.DeepEqual(rest, want) {
t.Fatalf("agent args = %q, want %q", rest, want)
}
}
func TestCodeArgsExplicitModelBeforeSeparator(t *testing.T) {
model, safe, continueLast, rest := splitCodeArgs([]string{"zen5-max", "--", "exec"})
if model != "zen5-max" || safe || continueLast || !reflect.DeepEqual(rest, []string{"exec"}) {
t.Fatalf("model=%q safe=%v continue=%v rest=%q", model, safe, continueLast, rest)
}
}
func TestCodeContinueIsNormalizedForBothHarnesses(t *testing.T) {
for _, tt := range []struct {
name string
want []string
}{
{name: "claude", want: []string{"--continue"}},
{name: "codex", want: []string{"resume", "--last"}},
} {
t.Run(tt.name, func(t *testing.T) {
model, safe, continueLast, rest := splitCodeArgs([]string{"-c"})
if model != "" || safe || !continueLast || len(rest) != 0 {
t.Fatalf("model=%q safe=%v continue=%v rest=%q", model, safe, continueLast, rest)
}
if got := codeAgentRest(codeAgents[tt.name], continueLast, rest); !reflect.DeepEqual(got, tt.want) {
t.Fatalf("normalized continue args = %q, want %q", got, tt.want)
}
})
}
}
func TestCodeUnknownOptionsAndPostSeparatorArgsPassThrough(t *testing.T) {
unknown := []string{"--mystery", "value", "--other=1"}
model, safe, continueLast, rest := splitCodeArgs(unknown)
if model != "" || safe || continueLast || !reflect.DeepEqual(rest, unknown) {
t.Fatalf("unknown options changed: model=%q safe=%v continue=%v rest=%q", model, safe, continueLast, rest)
}
_, _, continueLast, rest = splitCodeArgs([]string{"--", "-c", "model=x"})
if continueLast || !reflect.DeepEqual(rest, []string{"-c", "model=x"}) {
t.Fatalf("post-separator Codex config must pass verbatim: continue=%v rest=%q", continueLast, rest)
}
}
func TestCodexProviderUsesNativeResponsesMetadata(t *testing.T) {
// defaultCodeModel is zen5 — a 1M flagship tier — so the window must be 1M,
// NOT the old flat 262144 cap that surfaced as "maximum context exceeded"
// even on a 1M-capable model. Auto-compact is 90% of the window.
argv := codeArgv(codeAgents["codex"], "https://api.hanzo.ai", defaultCodeModel, false, nil)
for _, want := range []string{
`model_provider=hanzo`,
`model_providers.hanzo.base_url="https://api.hanzo.ai/v1"`,
`model_providers.hanzo.wire_api="responses"`,
`features.remote_models=false`,
`model_context_window=1000000`,
`model_auto_compact_token_limit=900000`,
} {
if !slices.Contains(argv, want) {
t.Errorf("Codex argv %q does not contain %q", argv, want)
}
}
// A flash tier budgets its smaller real window, not 1M.
flash := codeArgv(codeAgents["codex"], "https://api.hanzo.ai", "zen5-flash", false, nil)
if !slices.Contains(flash, `model_context_window=131072`) {
t.Errorf("zen5-flash argv %q must budget 131072, not the flagship 1M", flash)
}
}
// TestCodeContextWindowSizing pins the model→window map: every non-flash tier
// gets the 1M flagship window; only flash tiers drop to 131072.
func TestCodeContextWindowSizing(t *testing.T) {
for _, m := range []string{"zen5", "zen5-pro", "zen5-coder", "enso", "enso-ultra"} {
if w := codeContextWindow(m); w != 1000000 {
t.Errorf("codeContextWindow(%q) = %d, want 1000000", m, w)
}
}
for _, m := range []string{"zen5-flash", "enso-flash"} {
if w := codeContextWindow(m); w != 131072 {
t.Errorf("codeContextWindow(%q) = %d, want 131072", m, w)
}
}
}
// TestCodeTokenPrecedence locks in the 402 unblock: a fresh `hanzo login` JWT
// (which carries owner/project/sub on EVERY deployment) beats the hk- API key
// (which only mints a billing principal where the server has IAM_MINT_CLIENT_*).
// On a mint-less deployment an hk- request arrives anonymous and zen 402s; the
// JWT must win when it is live. An EXPIRED JWT must NOT win — it would 401 a
// session a valid hk- key would still serve — so it falls through to the key.
// HANZO_API_KEY stays the deliberate operator override at the top.
func TestCodeTokenPrecedence(t *testing.T) {
// freshExpiry is comfortably in the future without a literal unix timestamp.
freshExpiry := time.Now().Add(1 * time.Hour).Unix()
cases := []struct {
name string
envKey string // HANZO_API_KEY override
creds Credentials
want string
}{
{
name: "fresh JWT beats hk- key",
creds: Credentials{AccessToken: "jwt-live", Expiry: freshExpiry},
want: "jwt-live",
},
{
name: "expired JWT falls through to stored hk- key",
creds: Credentials{AccessToken: "jwt-dead", Expiry: time.Now().Add(-1 * time.Hour).Unix()},
want: "hk-stored",
},
{
name: "no JWT, no expiry record ⟹ hk- key (mint-credentialed servers)",
creds: Credentials{},
want: "hk-stored",
},
{
name: "HANZO_API_KEY overrides everything (deliberate operator override)",
envKey: "hk-explicit",
creds: Credentials{AccessToken: "jwt-live", Expiry: freshExpiry},
want: "hk-explicit",
},
{
name: "HANZO_API_KEY overrides even an expired JWT",
envKey: "hk-explicit",
creds: Credentials{AccessToken: "jwt-dead", Expiry: time.Now().Add(-1 * time.Hour).Unix()},
want: "hk-explicit",
},
}
for _, tc := range cases {
t.Run(tc.name, func(t *testing.T) {
sandbox(t) // isolates HANZO_HOME + clears HANZO_TOKEN/HANZO_API_KEY
if tc.envKey != "" {
t.Setenv("HANZO_API_KEY", tc.envKey)
}
// Put the hk- key where storedAPIKey() reads it (~/.hanzo/config.json),
// the same path the rest of the toolchain shares it from.
cfgDir, _ := hanzoDir()
if err := os.WriteFile(filepath.Join(cfgDir, "config.json"),
[]byte(`{"apiKey":"hk-stored"}`), 0o600); err != nil {
t.Fatalf("write config.json: %v", err)
}
env := resolve(&Config{}, &tc.creds, globalFlags{})
if got := codeToken(env); got != tc.want {
t.Fatalf("codeToken = %q, want %q", got, tc.want)
}
})
}
}
func TestDefaultCodeModelIsToolCapableAlias(t *testing.T) {
// zen5 is the flagship GLM-5.2-class alias — tool-capable (verified live: the
// glm-5.2 upstream returns tool_use / stop_reason:tool_use) and the model the
// user's "pop open with GLM-5.2" intent maps to. It must NOT be the virtual
// `best` (a reserved word Claude Code rewrites to an unserved claude-* id).
if defaultCodeModel != "zen5" {
t.Fatalf("coding-agent default %q is not the flagship zen5 alias", defaultCodeModel)
}
if defaultCodeModel == "best" {
t.Fatal("default must be a concrete served id, never the reserved word best")
}
}
// TestAnthropicWirePinsCarrierTiers locks in the 1M-context fix: every CC tier
// slot is pinned to a Claude-Code-recognized CARRIER id (so CC grants the model
// its true, up-to-1M context budget instead of the 128K fallback it applies to
// ids it does not know), and settings.json modelOverrides rewrites each carrier
// back to a served zen alias before the request leaves the client — so the wire
// model that reaches api.hanzo.ai is always zen, never the carrier. The old
// deadlock (a raw claude-* id 403ing on the Hanzo account) cannot recur because
// the carrier never reaches the server; the override guarantees it (asserted in
// TestCarrierTiersAreOverridden).
func TestAnthropicWirePinsCarrierTiers(t *testing.T) {
env := anthropicWire("https://api.hanzo.ai", "hk-test", "claude-opus-4-8[1m]")
want := map[string]string{
"ANTHROPIC_BASE_URL": "https://api.hanzo.ai",
"ANTHROPIC_AUTH_TOKEN": "hk-test",
"ANTHROPIC_MODEL": "claude-opus-4-8[1m]",
"ANTHROPIC_SMALL_FAST_MODEL": "zen5-flash", // deprecated var: no override applies, so a direct served zen id
"ANTHROPIC_DEFAULT_HAIKU_MODEL": "zen5-flash", // fast tier is carrier-less (never needs >128K)
"ANTHROPIC_DEFAULT_SONNET_MODEL": "claude-sonnet-4-6[1m]",
"ANTHROPIC_DEFAULT_OPUS_MODEL": "claude-opus-4-8[1m]",
"ANTHROPIC_DEFAULT_FABLE_MODEL": "claude-fable-5[1m]",
}
for k, v := range want {
if got := env[k]; got != v {
t.Errorf("%s: want %q, got %q", k, v, got)
}
}
// Each tier slot carries a Hanzo-branded display name so the picker never
// shows the underlying carrier (Opus/Sonnet/Haiku) — only the Zen brand.
if env["ANTHROPIC_DEFAULT_OPUS_MODEL_NAME"] != "Zen5 Pro" {
t.Errorf("OPUS tier must display the Zen brand, got %q", env["ANTHROPIC_DEFAULT_OPUS_MODEL_NAME"])
}
}
// TestCarrierTiersAreOverridden is the safety net that replaces the old
// "no claude-* in the wire" rule: a claude-* carrier in the env is SAFE only
// because modelOverrides maps it to a served zen id. Every claude-* value the
// wire emits must have a modelOverrides entry (keyed by its suffix-stripped id)
// pointing at a zen alias — otherwise CC would send the raw claude-* id to
// api.hanzo.ai and reintroduce the 403.
func TestCarrierTiersAreOverridden(t *testing.T) {
env := anthropicWire("https://api.hanzo.ai", "hk-test", "claude-opus-4-8[1m]")
overrides := claudeModelOverrides()
for k, v := range env {
if len(v) < 6 || v[:6] != "claude" {
continue // only carrier ids need an override
}
zen, ok := overrides[stripModelSuffix(v)]
if !ok {
t.Errorf("%s=%q is a claude-* carrier with NO modelOverrides entry — it would reach api.hanzo.ai and 403", k, v)
continue
}
if len(zen) < 3 || zen[:3] != "zen" {
t.Errorf("%s=%q overrides to %q, which is not a zen alias", k, v, zen)
}
}
}
// TestZenCarrierRoundTrips checks the two-way mapping the fix depends on: every
// tier's zen id maps to a carrier, and that carrier (suffix-stripped) maps back
// to a served zen id via modelOverrides. An unknown id passes through unchanged.
func TestZenCarrierRoundTrips(t *testing.T) {
overrides := claudeModelOverrides()
for _, tier := range zenTiers {
carrier := zenCarrier(tier.zen)
if tier.carrier == "" {
// Direct tier: zenCarrier returns the served zen id itself, no override.
if carrier != tier.zen {
t.Errorf("direct tier %q must map to itself, got %q", tier.zen, carrier)
}
continue
}
if carrier == tier.zen {
t.Errorf("zenCarrier(%q) did not map to a carrier", tier.zen)
}
if got := overrides[stripModelSuffix(carrier)]; got != tier.zen {
t.Errorf("carrier %q for %q overrides to %q, want %q", carrier, tier.zen, got, tier.zen)
}
}
if got := zenCarrier("some-raw-upstream"); got != "some-raw-upstream" {
t.Errorf("unknown id must pass through unchanged, got %q", got)
}
}
// TestClaudeArgvForcesModel locks in the fix for "everything shows up as best":
// the claude agent must pass --model <resolved> on argv so a persisted /model
// selection (the reserved word "best") cannot override the zen5 model the
// launcher chose. ANTHROPIC_MODEL alone is not enough — /model beats it.
func TestClaudeArgvForcesModel(t *testing.T) {
agent := codeAgents["claude"]
argv := codeArgv(agent, "https://api.hanzo.ai", "zen5-pro", false, nil)
i := slices.Index(argv, "--model")
if i < 0 {
t.Fatalf("claude argv %q does not force --model (a persisted /model selection would win)", argv)
}
if i+1 >= len(argv) || argv[i+1] != "zen5-pro" {
t.Fatalf("claude argv %q: --model must be followed by the resolved id zen5-pro", argv)
}
// --model is forced in --safe mode too (model pinning is independent of
// the permission mode).
safeArgv := codeArgv(agent, "https://api.hanzo.ai", "zen5-pro", true, nil)
if i := slices.Index(safeArgv, "--model"); i < 0 || safeArgv[i+1] != "zen5-pro" {
t.Fatalf("--safe argv %q must still force --model zen5-pro", safeArgv)
}
}
// TestClaudeAppendsZenIdentityInAllModes locks in the identity fix: the claude
// agent appends --append-system-prompt <zenIdentityPrompt> so a Hanzo-served
// model self-identifies as a Hanzo Zen model. Identity is not a permission
// bypass, so it is present in --safe too (unlike --dangerously-skip-permissions).
// codex/dev (OpenAI wire) do not carry the Anthropic-only append.
func TestClaudeAppendsZenIdentityInAllModes(t *testing.T) {
agent := codeAgents["claude"]
check := func(argv []string) {
t.Helper()
i := slices.Index(argv, "--append-system-prompt")
if i < 0 || i+1 >= len(argv) || argv[i+1] != zenIdentityPrompt {
t.Fatalf("argv %q missing --append-system-prompt <zenIdentityPrompt>", argv)
}
}
// full-auto (default)
check(codeArgv(agent, "https://api.hanzo.ai", defaultCodeModel, false, nil))
// --safe keeps the identity (identity != permission bypass) but drops the bypass
safeArgv := codeArgv(agent, "https://api.hanzo.ai", defaultCodeModel, true, nil)
check(safeArgv)
if slices.Contains(safeArgv, "--dangerously-skip-permissions") {
t.Fatalf("--safe must not carry the permission bypass: %v", safeArgv)
}
// codex/dev (OpenAI wire) do not carry the Anthropic-only identity append
for _, name := range []string{"codex", "dev"} {
argv := codeArgv(codeAgents[name], "https://api.hanzo.ai", defaultCodeModel, false, nil)
if slices.Contains(argv, "--append-system-prompt") {
t.Fatalf("%s must not carry the claude-only identity append: %v", name, argv)
}
}
}
// TestClaudeAutoWiresMCP locks in the fix for "hanzo code wires no tools": the
// claude agent must opt into MCP auto-wiring, and the resolver must produce an
// stdio server config that is layered STRICTLY (repo .mcp.json ignored — it could
// exfiltrate the session bearer).
func TestClaudeAutoWiresMCP(t *testing.T) {
if !codeAgents["claude"].mcp {
t.Fatal("claude agent must set mcp:true so `hanzo code claude` starts with the Hanzo tool lattice")
}
// codex/dev are wired additively by their own provider config, not this seam.
for _, name := range []string{"codex", "dev"} {
if codeAgents[name].mcp {
t.Fatalf("%s must not use the claude MCP seam (it attaches Hanzo additively via -c)", name)
}
}
// The --mcp-config document is a valid single-server stdio config.
cfg := mcpConfigJSON("/usr/bin/hanzo-mcp", []string{"--project-dir", "/repo"})
var doc struct {
MCPServers map[string]struct {
Type string `json:"type"`
Command string `json:"command"`
Args []string `json:"args"`
} `json:"mcpServers"`
}
if err := json.Unmarshal([]byte(cfg), &doc); err != nil {
t.Fatalf("mcpConfigJSON is not valid JSON: %v", err)
}
h, ok := doc.MCPServers["hanzo"]
if !ok || h.Type != "stdio" || h.Command != "/usr/bin/hanzo-mcp" {
t.Fatalf("mcpConfigJSON: want one stdio server 'hanzo' → /usr/bin/hanzo-mcp, got %+v", doc.MCPServers)
}
if !slices.Contains(h.Args, "--project-dir") || !slices.Contains(h.Args, "/repo") {
t.Fatalf("mcpConfigJSON: server must be scoped to the project dir, got args %v", h.Args)
}
// mcpArgs writes the config into the isolated dir and returns the strict flags.
dir := t.TempDir()
t.Setenv("PATH", "/usr/bin/hanzo-mcp-not-here") // force the not-found path deterministically
flags, warn := mcpArgs(dir, "/repo")
if warn == "" || len(flags) != 0 {
t.Fatalf("with no hanzo-mcp on PATH, mcpArgs must warn and inject nothing, got flags=%v warn=%q", flags, warn)
}
}
// TestClaudeAgentAppliesCarrier locks in the runCode wiring: the claude agent
// carries the zen→carrier map (so the resolved zen model is handed to CC as a
// recognized 1M id), while codex/dev have no carrier (they speak OpenAI directly
// and must NOT rewrite the model).
func TestClaudeAgentAppliesCarrier(t *testing.T) {
if codeAgents["claude"].carrier == nil {
t.Fatal("claude agent must set a carrier so CC budgets the full context window")
}
if got := codeAgents["claude"].carrier("zen5-pro"); got != "claude-opus-4-8[1m]" {
t.Fatalf("claude carrier: zen5-pro must map to the opus carrier, got %q", got)
}
for _, name := range []string{"codex", "dev"} {
if codeAgents[name].carrier != nil {
t.Fatalf("%s speaks OpenAI directly and must not remap the model", name)
}
}
}
// servedZenIDs is the set of zen aliases api.hanzo.ai actually serves, confirmed
// live (2026-07). zen5-mini/zen5-max/zen5-ultra are catalog-listed but 404 or
// time out, so no tier may target them. Adding a tier forces confirming its id
// serves and listing it here — the guard below fails otherwise.
var servedZenIDs = map[string]bool{
"zen5-flash": true,
"zen5": true,
"zen5-pro": true,
"zen5-coder": true,
}
// TestZenTiersServeReal is the invariant a 1M-carrier is useless without: every
// tier's zen wire id must be one api.hanzo.ai serves. A carrier that budgets 1M
// but rewrites to a 404 id just fails later, opaquely.
func TestZenTiersServeReal(t *testing.T) {
for _, tier := range zenTiers {
if !servedZenIDs[tier.zen] {
t.Errorf("tier %q → zen id %q is not in the confirmed-served set; a carrier to an unserved id 404s", tier.carrier, tier.zen)
}
}
}
// TestUpsertClaudeSettings checks the seed: a fresh dir gets base defaults plus
// the carrier→zen modelOverrides, and a re-seed REFRESHES modelOverrides (policy)
// while PRESERVING a user's own edits to other keys (preference).
func TestUpsertClaudeSettings(t *testing.T) {
path := filepath.Join(t.TempDir(), "settings.json")
if err := upsertClaudeSettings(path); err != nil {
t.Fatalf("first seed failed: %v", err)
}
read := func() map[string]any {
b, err := os.ReadFile(path)
if err != nil {
t.Fatalf("read settings: %v", err)
}
var m map[string]any
if err := json.Unmarshal(b, &m); err != nil {
t.Fatalf("settings.json is not valid JSON: %v", err)
}
return m
}
s := read()
if s["effortLevel"] != "max" {
t.Errorf("base defaults missing: effortLevel = %v", s["effortLevel"])
}
ov, ok := s["modelOverrides"].(map[string]any)
if !ok {
t.Fatalf("modelOverrides missing or wrong type: %T", s["modelOverrides"])
}
if ov["claude-opus-4-8"] != "zen5-pro" {
t.Errorf("modelOverrides[claude-opus-4-8] = %v, want zen5-pro", ov["claude-opus-4-8"])
}
// User edits a preference and adds a key; re-seed must keep both.
s["effortLevel"] = "low"
s["userKey"] = "keepme"
b, _ := json.Marshal(s)
if err := os.WriteFile(path, b, 0o600); err != nil {
t.Fatal(err)
}
if err := upsertClaudeSettings(path); err != nil {
t.Fatalf("re-seed failed: %v", err)
}
s2 := read()
if s2["effortLevel"] != "low" {
t.Errorf("re-seed clobbered user edit: effortLevel = %v, want low", s2["effortLevel"])
}
if s2["userKey"] != "keepme" {
t.Errorf("re-seed dropped user key: userKey = %v", s2["userKey"])
}
ov2, _ := s2["modelOverrides"].(map[string]any)
if ov2["claude-opus-4-8"] != "zen5-pro" {
t.Errorf("re-seed lost modelOverrides: %v", ov2)
}
}
+331
View File
@@ -0,0 +1,331 @@
package cli
import (
"fmt"
"io"
"strings"
"text/tabwriter"
"github.com/spf13/cobra"
)
// platform builds a platform REST client from the resolved env + the global
// --platform-token flag. The token may be empty here; the client surfaces a
// precise error on first use.
func (e *Env) platform(gf *globalFlags) *Platform {
return newPlatform(e.PlatformURL, e.platformToken(gf.platformToken))
}
// dashIfEmpty renders a string cell, "-" when empty.
func dashIfEmpty(s string) string {
if s == "" {
return "-"
}
return s
}
// yesno renders a bool for a table cell.
func yesno(b bool) string {
if b {
return "yes"
}
return "no"
}
// newTab returns a tabwriter writing to w with a 2-space gutter.
func newTab(w io.Writer) *tabwriter.Writer {
return tabwriter.NewWriter(w, 0, 0, 2, ' ', 0)
}
// ---------------------------------------------------------------------------
// apps — the fleet drift board (GET /v1/paas/apps). Org-confined server-side by
// the IAM identity: a superadmin sees the whole fleet, an org-admin only its own.
// ---------------------------------------------------------------------------
func newAppsCmd(envOf func() *Env, gf *globalFlags) *cobra.Command {
cmd := &cobra.Command{
Use: "apps",
Short: "List/get the platform apps board (declared/running/latest/drift)",
}
var envFilter, healthFilter string
var driftOnly bool
list := &cobra.Command{
Use: "list",
Short: "List apps with declared/running tags, health and drift",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
e := envOf()
res, err := e.platform(gf).Apps(cmd.Context(), AppsQuery{
Env: envFilter,
Health: healthFilter,
Drift: driftOnly,
})
if err != nil {
return err
}
return e.emit(res, func(w io.Writer) {
tw := newTab(w)
fmt.Fprintln(tw, "ORG\tAPP\tENV\tDECLARED\tRUNNING\tHEALTH\tDRIFT")
for _, a := range res.Apps {
fmt.Fprintf(tw, "%s\t%s\t%s\t%s\t%s\t%s\t%s\n",
a.Org, a.App, a.Env, dashIfEmpty(a.DeclaredTag), dashIfEmpty(a.RunningTag),
dashIfEmpty(a.Health), driftSeverity(a.Drift))
}
tw.Flush()
fmt.Fprintf(w, "\n%d apps (ok=%d yellow=%d red=%d)\n",
res.Summary.Total, res.Summary.ByDrift["ok"],
res.Summary.ByDrift["yellow"], res.Summary.ByDrift["red"])
})
},
}
list.Flags().StringVar(&envFilter, "env", "", "filter by env: main|test|dev")
list.Flags().StringVar(&healthFilter, "health", "", "filter by health: green|yellow|red")
list.Flags().BoolVar(&driftOnly, "drift", false, "only rows that are drifting")
get := &cobra.Command{
Use: "get <app>",
Short: "Get one app row by its CR name (production by default)",
Args: cobra.ExactArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
e := envOf()
a, err := e.platform(gf).App(cmd.Context(), args[0])
if err != nil {
return err
}
return e.emit(a, func(w io.Writer) {
tw := newTab(w)
fmt.Fprintf(tw, "id:\t%s\n", a.ID)
fmt.Fprintf(tw, "org:\t%s\n", a.Org)
fmt.Fprintf(tw, "app:\t%s\n", a.App)
fmt.Fprintf(tw, "env:\t%s\n", a.Env)
fmt.Fprintf(tw, "repo:\t%s\n", a.Repo)
fmt.Fprintf(tw, "registry:\t%s\n", a.Registry)
fmt.Fprintf(tw, "declared:\t%s\n", dashIfEmpty(a.DeclaredTag))
fmt.Fprintf(tw, "running:\t%s\n", dashIfEmpty(a.RunningTag))
fmt.Fprintf(tw, "health:\t%s\n", dashIfEmpty(a.Health))
fmt.Fprintf(tw, "phase:\t%s\n", dashIfEmpty(a.Phase))
fmt.Fprintf(tw, "drift:\t%s\n", driftSeverity(a.Drift))
fmt.Fprintf(tw, "cluster:\t%s\n", dashIfEmpty(a.Cluster))
fmt.Fprintf(tw, "namespace:\t%s\n", dashIfEmpty(a.Namespace))
if len(a.Endpoints) > 0 {
fmt.Fprintf(tw, "endpoints:\t%s\n", strings.Join(a.Endpoints, ", "))
}
tw.Flush()
})
},
}
cmd.AddCommand(list, get)
return cmd
}
// ---------------------------------------------------------------------------
// deploy — POST /v1/paas/apps/{app}/deploy: a zero-downtime rolling restart.
// ---------------------------------------------------------------------------
func newDeployCmd(envOf func() *Env, gf *globalFlags) *cobra.Command {
var environment string
cmd := &cobra.Command{
Use: "deploy <app>",
Short: "Redeploy an app (rolling restart, zero-downtime) — requires --env",
Long: "Drive a platform redeploy: a rolling restart of the app's k8s Deployment\n" +
"(re-pulls the declared image, recreates pods, zero downtime). The app is the\n" +
"operator App CR name; the org comes from your IAM identity. --env is REQUIRED\n" +
"(main|test|dev) — deploy never silently targets production. Restarting a shared\n" +
"platform service is a platform-operator action, so this needs a superadmin\n" +
"identity. A TAG change is still a git commit — this restarts what is declared.",
Args: cobra.ExactArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
if strings.TrimSpace(environment) == "" {
return fmt.Errorf("--env is required (main|test|dev) — deploy will not default to production")
}
e := envOf()
res, err := e.platform(gf).Redeploy(cmd.Context(), args[0], environment)
if err != nil {
return err
}
return e.emit(res, func(w io.Writer) {
fmt.Fprintf(w, "restarted %s (namespace=%s env=%s at %s)\n",
res.App, res.Namespace, dashIfEmpty(res.Env), res.RestartedAt)
})
},
}
cmd.Flags().StringVar(&environment, "env", "", "lifecycle env: main|test|dev (REQUIRED)")
return cmd
}
// ---------------------------------------------------------------------------
// clusters — GET /v1/clusters: the org's compute fleet (Visor-managed + BYO),
// tenant-scoped server-side by the IAM identity.
// ---------------------------------------------------------------------------
func newClustersCmd(envOf func() *Env, gf *globalFlags) *cobra.Command {
cmd := &cobra.Command{
Use: "clusters",
Aliases: []string{"cluster"},
Short: "List the org's clusters (managed + BYO)",
}
list := &cobra.Command{
Use: "list",
Short: "List the org's clusters",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
e := envOf()
cs, err := e.platform(gf).Clusters(cmd.Context())
if err != nil {
return err
}
return e.emit(cs, func(w io.Writer) {
tw := newTab(w)
fmt.Fprintln(tw, "NAME\tID\tREGION\tSTATUS\tKIND\tNODES\tSIZE\tGPUS")
for _, c := range cs {
fmt.Fprintf(tw, "%s\t%s\t%s\t%s\t%s\t%d\t%s\t%s\n",
c.Name, dashIfEmpty(c.ID()), dashIfEmpty(c.Region), dashIfEmpty(c.Status),
dashIfEmpty(c.Kind), c.NodeCount, dashIfEmpty(c.NodeSize), gpuCell(c))
}
tw.Flush()
if len(cs) == 0 {
fmt.Fprintln(w, "(no clusters)")
}
})
},
}
get := &cobra.Command{
Use: "get <cluster-id>",
Short: "Show one cluster",
Args: cobra.ExactArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
e := envOf()
cs, err := e.platform(gf).Clusters(cmd.Context())
if err != nil {
return err
}
for _, c := range cs {
if c.ID() == args[0] || c.Name == args[0] {
return e.emit(c, func(w io.Writer) { printCluster(w, c) })
}
}
return fmt.Errorf("cluster %q not found", args[0])
},
}
cmd.AddCommand(list, get)
return cmd
}
// gpuCell renders the live GPU inventory of a cluster ("-" when none).
func gpuCell(c Cluster) string {
var parts []string
if c.NvidiaGPU > 0 {
parts = append(parts, fmt.Sprintf("%d nvidia", c.NvidiaGPU))
}
if c.AmdGPU > 0 {
parts = append(parts, fmt.Sprintf("%d amd", c.AmdGPU))
}
if len(parts) == 0 {
return "-"
}
return strings.Join(parts, "+")
}
func printCluster(w io.Writer, c Cluster) {
tw := newTab(w)
fmt.Fprintf(tw, "id:\t%s\n", dashIfEmpty(c.ID()))
fmt.Fprintf(tw, "name:\t%s\n", c.Name)
fmt.Fprintf(tw, "region:\t%s\n", dashIfEmpty(c.Region))
fmt.Fprintf(tw, "status:\t%s\n", dashIfEmpty(c.Status))
fmt.Fprintf(tw, "kind:\t%s\n", dashIfEmpty(c.Kind))
fmt.Fprintf(tw, "nodeCount:\t%d\n", c.NodeCount)
fmt.Fprintf(tw, "nodeSize:\t%s\n", dashIfEmpty(c.NodeSize))
fmt.Fprintf(tw, "gpus:\t%s\n", gpuCell(c))
fmt.Fprintf(tw, "created:\t%s\n", dashIfEmpty(c.CreatedAt))
for _, np := range c.NodePools {
fmt.Fprintf(tw, "pool:\t%s (%s x%d, autoscale=%s)\n", np.Name, np.Size, np.Count, yesno(np.AutoScale))
}
tw.Flush()
}
// ---------------------------------------------------------------------------
// build — platform-native build (runner fabric) enqueue.
// ---------------------------------------------------------------------------
func newBuildCmd(envOf func() *Env, gf *globalFlags) *cobra.Command {
var br BuildReq
var buildToken string
cmd := &cobra.Command{
Use: "build <repo>",
Short: "Enqueue a platform-native build on the runner fabric (no GitHub builders)",
Long: "Enqueue a build on the platform's native runner fabric. Builds and pushes\n" +
"the named image at a SHA; on completion the platform patches the operator\n" +
"Service CR (build-job → deploy). Requires a live registered runner for the\n" +
"target pool (409 otherwise).",
Args: cobra.MaximumNArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
e := envOf()
if len(args) == 1 {
br.Repo = args[0]
}
if br.Repo == "" || br.SHA == "" || br.Image == "" {
return fmt.Errorf("--repo (or positional), --sha and --image are required")
}
// The platform build muscle clones an https git URL; accept the
// idiomatic `owner/name` shorthand and expand it to GitHub (the host
// for every hanzoai/luxfi/zooai repo). A full URL passes through.
br.Repo = normalizeRepoURL(br.Repo)
if br.OrganizationID == "" {
br.OrganizationID = e.Org // optional; server defaults to DEFAULT_BUILD_ORG_ID
}
job, err := e.platform(gf).EnqueueBuild(cmd.Context(), br, e.buildToken(buildToken))
if err != nil {
return err
}
return e.emit(job, func(w io.Writer) {
tw := newTab(w)
fmt.Fprintf(tw, "buildJobId:\t%s\n", job.BuildJobID)
fmt.Fprintf(tw, "status:\t%s\n", job.Status)
fmt.Fprintf(tw, "runnerPool:\t%s\n", job.RunnerPool)
fmt.Fprintf(tw, "image:\t%s\n", job.Image)
fmt.Fprintf(tw, "target:\t%s\n", job.Target)
tw.Flush()
})
},
}
f := cmd.Flags()
f.StringVar(&br.Repo, "repo", "", "owner/name (e.g. hanzoai/pricing)")
f.StringVar(&br.SHA, "sha", "", "commit SHA to build")
f.StringVar(&br.Image, "image", "", "image to build+push (e.g. ghcr.io/hanzoai/pricing:<tag>)")
f.StringVar(&br.Branch, "branch", "", "branch (default main)")
f.StringVar(&br.Dockerfile, "dockerfile", "", "Dockerfile path")
f.StringVar(&br.Context, "context", "", "build context")
f.StringVar(&br.DockerTarget, "target", "", "Docker build stage (--target)")
f.StringVar(&br.OS, "os", "", "linux|darwin|windows (default linux)")
f.StringVar(&br.Arch, "arch", "", "amd64|arm64 (default amd64)")
f.StringVar(&buildToken, "build-token", "", "platform build-enqueue token (else env/credential store)")
return cmd
}
// normalizeRepoURL expands the idiomatic `owner/name` shorthand to a full GitHub
// https URL (the platform build muscle clones https), and leaves an explicit URL
// (http/https/git/ssh scheme, or a scp-style git@host:owner/name) untouched. Only
// a bare single-segment `owner/name` — two path parts, no scheme, no host — is
// expanded; anything else is the caller's explicit choice and passes through.
func normalizeRepoURL(repo string) string {
r := strings.TrimSpace(repo)
if r == "" {
return r
}
// Already a URL or scp-style remote → leave as-is.
if strings.Contains(r, "://") || strings.Contains(r, "@") {
return r
}
// Bare owner/name (exactly two non-empty segments, no host dot in the first).
parts := strings.Split(strings.Trim(r, "/"), "/")
if len(parts) == 2 && parts[0] != "" && parts[1] != "" && !strings.Contains(parts[0], ".") {
return "https://github.com/" + parts[0] + "/" + parts[1]
}
return r
}
+248
View File
@@ -0,0 +1,248 @@
package cli
import (
"encoding/json"
"net/http"
"net/http/httptest"
"strings"
"testing"
)
func TestNormalizeRepoURL(t *testing.T) {
cases := map[string]string{
"luxfi/wallet": "https://github.com/luxfi/wallet",
"hanzoai/cloud": "https://github.com/hanzoai/cloud",
"https://github.com/luxfi/wallet": "https://github.com/luxfi/wallet", // full URL untouched
"git@github.com:luxfi/wallet.git": "git@github.com:luxfi/wallet.git", // scp-style untouched
"https://gitlab.com/org/repo": "https://gitlab.com/org/repo", // non-github URL untouched
"owner/name/extra": "owner/name/extra", // not a bare owner/name
"single": "single", // not two segments
"": "", // empty
}
for in, want := range cases {
if got := normalizeRepoURL(in); got != want {
t.Errorf("normalizeRepoURL(%q) = %q, want %q", in, got, want)
}
}
}
// withPlatform points the CLI at an httptest platform via env (HANZO_PLATFORM_URL
// + HANZO_PLATFORM_TOKEN), the same resolution path the real binary uses.
func withPlatform(t *testing.T, h http.HandlerFunc) string {
t.Helper()
sandbox(t)
srv := httptest.NewServer(h)
t.Cleanup(srv.Close)
t.Setenv("HANZO_PLATFORM_URL", srv.URL)
t.Setenv("HANZO_PLATFORM_TOKEN", "svc-tok")
return srv.URL
}
// apps list hits the LIVE board path /v1/paas/apps and renders the fleet table.
func TestAppsListCommandTable(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/paas/apps" {
t.Errorf("apps path = %s, want /v1/paas/apps", r.URL.Path)
}
_ = json.NewEncoder(w).Encode(AppsList{
Apps: []AppView{
{Org: "hanzoai", App: "iam", Env: "main", DeclaredTag: "v1.2.3", RunningTag: "v1.2.3", Health: "green", Drift: json.RawMessage(`{"severity":"ok"}`)},
},
Summary: struct {
Total int `json:"total"`
ByDrift map[string]int `json:"byDrift"`
}{Total: 1, ByDrift: map[string]int{"ok": 1}},
})
})
out, err := runRoot(t, "", "apps", "list")
if err != nil {
t.Fatalf("apps list: %v", err)
}
for _, want := range []string{"APP", "iam", "v1.2.3", "green", "ok", "1 apps"} {
if !strings.Contains(out, want) {
t.Fatalf("apps list table missing %q in:\n%s", want, out)
}
}
}
// apps list honors --env/--health/--drift as server query params (the board filters).
func TestAppsListCommandFilters(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, r *http.Request) {
q := r.URL.Query()
if q.Get("env") != "main" || q.Get("health") != "red" || q.Get("drift") != "1" {
t.Errorf("filters not forwarded: %s", r.URL.RawQuery)
}
_ = json.NewEncoder(w).Encode(AppsList{})
})
if _, err := runRoot(t, "", "apps", "list", "--env", "main", "--health", "red", "--drift"); err != nil {
t.Fatalf("apps list filters: %v", err)
}
}
func TestAppsListCommandJSON(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, _ *http.Request) {
_ = json.NewEncoder(w).Encode(AppsList{Apps: []AppView{{Org: "hanzoai", App: "iam", Env: "main"}}})
})
out, err := runRoot(t, "", "apps", "list", "-o", "json")
if err != nil {
t.Fatalf("apps list json: %v", err)
}
var res AppsList
if err := json.Unmarshal([]byte(out), &res); err != nil {
t.Fatalf("output is not valid JSON: %v\n%s", err, out)
}
if len(res.Apps) != 1 || res.Apps[0].App != "iam" {
t.Fatalf("json decode wrong: %+v", res.Apps)
}
}
// apps get hits /v1/paas/apps/{app}.
func TestAppsGetCommand(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/paas/apps/iam" {
t.Errorf("path = %s, want /v1/paas/apps/iam", r.URL.Path)
}
_ = json.NewEncoder(w).Encode(AppView{ID: "hanzoai/iam/main", Org: "hanzoai", App: "iam", Env: "main", DeclaredTag: "v1.2.3", Health: "green", Phase: "Running"})
})
out, err := runRoot(t, "", "apps", "get", "iam")
if err != nil {
t.Fatalf("apps get: %v", err)
}
for _, want := range []string{"hanzoai/iam/main", "Running", "v1.2.3"} {
if !strings.Contains(out, want) {
t.Fatalf("apps get missing %q in:\n%s", want, out)
}
}
}
// deploy hits /v1/paas/apps/{app}/deploy — a rolling restart, org from identity.
func TestDeployCommand(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/paas/apps/app-x/deploy" || r.URL.Query().Get("env") != "main" {
t.Errorf("redeploy request = %s?%s", r.URL.Path, r.URL.RawQuery)
}
w.WriteHeader(202)
_ = json.NewEncoder(w).Encode(DeployResult{OK: true, App: "app-x", Namespace: "hanzo", Env: "main", RestartedAt: "2026-07-18T12:00:00Z"})
})
out, err := runRoot(t, "", "deploy", "app-x", "--env", "main")
if err != nil {
t.Fatalf("deploy: %v", err)
}
if !strings.Contains(out, "restarted app-x") || !strings.Contains(out, "namespace=hanzo") {
t.Fatalf("deploy output: %q", out)
}
}
// deploy REQUIRES --env — a bare deploy errors CLI-side, never silently prod.
func TestDeployRequiresEnv(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, _ *http.Request) {
t.Error("deploy without --env must not reach the server")
w.WriteHeader(202)
})
if _, err := runRoot(t, "", "deploy", "app-x"); err == nil {
t.Fatalf("deploy must require --env")
}
}
// deploy --env selects the lifecycle namespace via the ?env query param.
func TestDeployCommandEnv(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/paas/apps/chat/deploy" || r.URL.Query().Get("env") != "test" {
t.Errorf("deploy env request = %s?%s", r.URL.Path, r.URL.RawQuery)
}
w.WriteHeader(202)
_ = json.NewEncoder(w).Encode(DeployResult{OK: true, App: "chat", Namespace: "hanzo-testnet", Env: "test", RestartedAt: "2026-07-18T12:00:00Z"})
})
if _, err := runRoot(t, "", "deploy", "chat", "--env", "test"); err != nil {
t.Fatalf("deploy --env: %v", err)
}
}
// A non-ok deploy response is surfaced as an error.
func TestDeployNotOK(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, _ *http.Request) {
_ = json.NewEncoder(w).Encode(DeployResult{OK: false})
})
if _, err := runRoot(t, "", "deploy", "app-x", "--env", "main"); err == nil {
t.Fatalf("deploy must error when the server does not report ok")
}
}
// clusters list hits the LIVE /v1/clusters (org from identity, not the path).
func TestClustersListCommand(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/clusters" {
t.Errorf("path = %s, want /v1/clusters", r.URL.Path)
}
_ = json.NewEncoder(w).Encode(map[string]any{"clusters": []Cluster{
{DoksClusterID: "c1", Name: "hanzo-acme", Region: "sfo3", Status: "running", Kind: "managed", NodeCount: 3, NodeSize: "s-2vcpu-4gb", NvidiaGPU: 2},
}})
})
out, err := runRoot(t, "", "clusters", "list")
if err != nil {
t.Fatalf("clusters list: %v", err)
}
for _, want := range []string{"NAME", "hanzo-acme", "c1", "managed", "2 nvidia"} {
if !strings.Contains(out, want) {
t.Fatalf("clusters list missing %q in:\n%s", want, out)
}
}
}
// clusters get filters the live list client-side by id or name.
func TestClustersGetCommand(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, _ *http.Request) {
_ = json.NewEncoder(w).Encode(map[string]any{"clusters": []Cluster{
{DoksClusterID: "c1", Name: "hanzo-acme", Region: "sfo3", Status: "running", Kind: "byo", NodeCount: 1},
}})
})
out, err := runRoot(t, "", "clusters", "get", "c1")
if err != nil {
t.Fatalf("clusters get: %v", err)
}
if !strings.Contains(out, "hanzo-acme") || !strings.Contains(out, "byo") {
t.Fatalf("clusters get output: %q", out)
}
}
func TestBuildCommandValidation(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, _ *http.Request) { w.WriteHeader(202) })
// Missing --sha/--image → validation error before any HTTP call.
if _, err := runRoot(t, "", "build", "hanzoai/pricing"); err == nil {
t.Fatalf("build must require --sha and --image")
}
}
func TestBuildCommand(t *testing.T) {
withPlatform(t, func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/runner" {
t.Errorf("path = %s", r.URL.Path)
}
if got := r.Header.Get("Authorization"); got != "Bearer bt" {
t.Errorf("build auth = %q", got)
}
w.WriteHeader(202)
_ = json.NewEncoder(w).Encode(BuildJob{BuildJobID: "bj-9", Status: "queued", Image: "ghcr.io/hanzoai/pricing:t"})
})
out, err := runRoot(t, "", "build", "hanzoai/pricing", "--sha", "abc", "--image", "ghcr.io/hanzoai/pricing:t", "--build-token", "bt")
if err != nil {
t.Fatalf("build: %v", err)
}
if !strings.Contains(out, "bj-9") {
t.Fatalf("build output: %q", out)
}
}
func TestConfigSetGetCommand(t *testing.T) {
sandbox(t)
if _, err := runRoot(t, "", "config", "set", "org", "acme"); err != nil {
t.Fatalf("config set: %v", err)
}
out, err := runRoot(t, "", "config", "get", "org")
if err != nil {
t.Fatalf("config get: %v", err)
}
if strings.TrimSpace(out) != "acme" {
t.Fatalf("config get = %q", out)
}
}
+182
View File
@@ -0,0 +1,182 @@
// device.go — RFC 8628 Device Authorization Grant for `hanzo login`: the ONE
// way any machine signs in. The CLI asks IAM for a device+user code, shows the
// verification link as text AND a terminal QR (scan with a phone), and polls
// the token endpoint until the user approves in any browser session. No
// password ever touches this terminal; works headless (GPU boxes, ssh, CI).
package cli
import (
"context"
"encoding/json"
"fmt"
"io"
"net/http"
"net/url"
"strings"
"time"
"github.com/mdp/qrterminal/v3"
"github.com/spf13/cobra"
)
// deviceAuthResp is the RFC 8628 device authorization response.
type deviceAuthResp struct {
DeviceCode string `json:"device_code"`
UserCode string `json:"user_code"`
VerificationURI string `json:"verification_uri"`
VerificationURIComplete string `json:"verification_uri_complete"`
ExpiresIn int64 `json:"expires_in"`
Interval int64 `json:"interval"`
Error string `json:"error"`
ErrorDesc string `json:"error_description"`
}
const deviceGrantType = "urn:ietf:params:oauth:grant-type:device_code"
// defaultDeviceClientID is the first-party client the device grant runs as.
// hanzo-app is the one Hanzo client IAM seeds with device_code enabled
// (iam cmd/iam/cli/init_apps.go brandGrantTypes); hanzo-console stays the
// password-grant client. hanzo-dev's live device flow uses the same pair of
// endpoints and this client, so the two CLIs share one server-side config.
const defaultDeviceClientID = "hanzo-app"
// rawForm posts a form to an oauth endpoint and returns the decoded token
// response WITHOUT mapping OAuth errors to Go errors — the device poll must
// inspect authorization_pending / slow_down itself.
func (c *iamClient) rawForm(ctx context.Context, endpoint string, form url.Values) (*tokenResp, error) {
req, err := http.NewRequestWithContext(ctx, http.MethodPost, c.issuer+endpoint, strings.NewReader(form.Encode()))
if err != nil {
return nil, err
}
req.Header.Set("Content-Type", "application/x-www-form-urlencoded")
req.Header.Set("Accept", "application/json")
req.Header.Set("User-Agent", "hanzo-cli/"+Version)
resp, err := c.http.Do(req)
if err != nil {
return nil, err
}
defer resp.Body.Close()
body, _ := io.ReadAll(io.LimitReader(resp.Body, 1<<20))
var tr tokenResp
if err := json.Unmarshal(body, &tr); err != nil {
return nil, fmt.Errorf("iam %s: HTTP %d: %s", endpoint, resp.StatusCode, strings.TrimSpace(string(body)))
}
return &tr, nil
}
// deviceAuth starts the device flow: mints a device_code + user_code pair.
// Query-param shape matches hanzo-dev's verified client (oidc_device_auth.rs).
func (c *iamClient) deviceAuth(ctx context.Context, scope string) (*deviceAuthResp, error) {
q := url.Values{"client_id": {c.clientID}, "scope": {scope}, "response_type": {"device_code"}}
req, err := http.NewRequestWithContext(ctx, http.MethodPost, c.issuer+"/v1/iam/oauth/device?"+q.Encode(), nil)
if err != nil {
return nil, err
}
req.Header.Set("Accept", "application/json")
req.Header.Set("User-Agent", "hanzo-cli/"+Version)
resp, err := c.http.Do(req)
if err != nil {
return nil, err
}
defer resp.Body.Close()
body, _ := io.ReadAll(io.LimitReader(resp.Body, 1<<20))
var da deviceAuthResp
if err := json.Unmarshal(body, &da); err != nil {
return nil, fmt.Errorf("iam device auth: HTTP %d: %s", resp.StatusCode, strings.TrimSpace(string(body)))
}
if da.Error != "" {
return nil, fmt.Errorf("iam device auth: %s: %s", da.Error, da.ErrorDesc)
}
if da.DeviceCode == "" || da.UserCode == "" {
return nil, fmt.Errorf("iam device auth: HTTP %d: no device_code in response", resp.StatusCode)
}
return &da, nil
}
// pollDeviceToken polls the token endpoint until the user approves, the code
// expires, or ctx ends. authorization_pending keeps polling; slow_down backs
// off per RFC 8628 §3.5.
func (c *iamClient) pollDeviceToken(ctx context.Context, da *deviceAuthResp) (*tokenResp, error) {
interval := time.Duration(max64(da.Interval, 1)) * time.Second
deadline := time.Now().Add(time.Duration(da.ExpiresIn) * time.Second)
for {
select {
case <-ctx.Done():
return nil, ctx.Err()
case <-time.After(interval):
}
if time.Now().After(deadline) {
return nil, fmt.Errorf("device code expired before approval — run `hanzo login` again")
}
tr, err := c.rawForm(ctx, "/v1/iam/oauth/token", url.Values{
"grant_type": {deviceGrantType},
"client_id": {c.clientID},
"device_code": {da.DeviceCode},
})
if err != nil {
return nil, err
}
switch tr.Error {
case "":
if tr.AccessToken == "" {
return nil, fmt.Errorf("iam device token: empty access_token")
}
return tr, nil
case "authorization_pending":
// approved not yet — keep waiting
case "slow_down":
interval += 5 * time.Second
case "expired_token":
return nil, fmt.Errorf("device code expired before approval — run `hanzo login` again")
default:
return nil, fmt.Errorf("iam device token: %s: %s", tr.Error, tr.ErrorDesc)
}
}
}
// runDeviceLogin drives the interactive device sign-in and returns credentials.
func runDeviceLogin(cmd *cobra.Command, env *Env, scope string) (*Credentials, error) {
out := cmd.OutOrStdout()
// An explicit --client-id/HANZO_CLIENT_ID override wins; otherwise the
// device grant runs as hanzo-app (see defaultDeviceClientID).
clientID := env.ClientID
if clientID == "" || clientID == defaultClientID {
clientID = defaultDeviceClientID
}
iam := newIAMClient(env.IAMIssuer, clientID)
da, err := iam.deviceAuth(cmd.Context(), scope)
if err != nil {
return nil, err
}
link := firstNonEmpty(da.VerificationURIComplete, da.VerificationURI)
fmt.Fprintf(out, "\nSign in on any device:\n\n")
printQR(out, link)
fmt.Fprintf(out, "\n %s\n", link)
if da.VerificationURI != "" && da.UserCode != "" {
fmt.Fprintf(out, " or open %s and enter code %s\n", da.VerificationURI, da.UserCode)
}
fmt.Fprintf(out, "\nWaiting for approval…\n")
tr, err := iam.pollDeviceToken(cmd.Context(), da)
if err != nil {
return nil, err
}
return credsFromToken(tr), nil
}
// printQR renders a scannable QR of the verification link using half blocks
// (compact enough for a default 80×24 terminal).
func printQR(w io.Writer, link string) {
qrterminal.GenerateWithConfig(link, qrterminal.Config{
Level: qrterminal.L,
Writer: w,
HalfBlocks: true,
QuietZone: 1,
})
}
func max64(a, b int64) int64 {
if a > b {
return a
}
return b
}
+107
View File
@@ -0,0 +1,107 @@
package cli
import (
"context"
"encoding/json"
"net/http"
"net/http/httptest"
"strings"
"testing"
)
func TestDeviceAuth(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/iam/oauth/device" {
t.Fatalf("path = %s", r.URL.Path)
}
if got := r.URL.Query().Get("client_id"); got != "hanzo-app" {
t.Fatalf("client_id = %q", got)
}
if got := r.URL.Query().Get("response_type"); got != "device_code" {
t.Fatalf("response_type = %q", got)
}
_ = json.NewEncoder(w).Encode(map[string]any{
"device_code": "dc-1",
"user_code": "WDJB-MJHT",
"verification_uri": srv0 + "/login/oauth/device",
"verification_uri_complete": srv0 + "/login/oauth/device/WDJB-MJHT",
"expires_in": 900,
"interval": 1,
})
}))
defer srv.Close()
srv0 = srv.URL
iam := newIAMClient(srv.URL, "hanzo-app")
da, err := iam.deviceAuth(context.Background(), "openid profile email")
if err != nil {
t.Fatal(err)
}
if da.DeviceCode != "dc-1" || da.UserCode != "WDJB-MJHT" {
t.Fatalf("unexpected device auth: %+v", da)
}
if !strings.HasSuffix(da.VerificationURIComplete, "/WDJB-MJHT") {
t.Fatalf("verification_uri_complete = %q", da.VerificationURIComplete)
}
}
// srv0 lets the handler reference its own server URL in the response body.
var srv0 string
func TestPollDeviceTokenPendingThenIssued(t *testing.T) {
polls := 0
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/iam/oauth/token" {
t.Fatalf("path = %s", r.URL.Path)
}
_ = r.ParseForm()
if got := r.Form.Get("grant_type"); got != deviceGrantType {
t.Fatalf("grant_type = %q", got)
}
if got := r.Form.Get("device_code"); got != "dc-1" {
t.Fatalf("device_code = %q", got)
}
polls++
if polls < 3 {
_ = json.NewEncoder(w).Encode(map[string]string{"error": "authorization_pending"})
return
}
_ = json.NewEncoder(w).Encode(map[string]any{"access_token": "tok-1", "token_type": "Bearer", "expires_in": 3600})
}))
defer srv.Close()
iam := newIAMClient(srv.URL, "hanzo-console")
tr, err := iam.pollDeviceToken(context.Background(), &deviceAuthResp{DeviceCode: "dc-1", ExpiresIn: 30, Interval: 0})
if err != nil {
t.Fatal(err)
}
if tr.AccessToken != "tok-1" || polls != 3 {
t.Fatalf("token = %q polls = %d", tr.AccessToken, polls)
}
}
func TestPollDeviceTokenExpired(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
_ = json.NewEncoder(w).Encode(map[string]string{"error": "expired_token"})
}))
defer srv.Close()
iam := newIAMClient(srv.URL, "hanzo-console")
_, err := iam.pollDeviceToken(context.Background(), &deviceAuthResp{DeviceCode: "dc-1", ExpiresIn: 30, Interval: 0})
if err == nil || !strings.Contains(err.Error(), "expired") {
t.Fatalf("err = %v", err)
}
}
func TestPollDeviceTokenDenied(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
_ = json.NewEncoder(w).Encode(map[string]string{"error": "access_denied", "error_description": "user refused"})
}))
defer srv.Close()
iam := newIAMClient(srv.URL, "hanzo-console")
_, err := iam.pollDeviceToken(context.Background(), &deviceAuthResp{DeviceCode: "dc-1", ExpiresIn: 30, Interval: 0})
if err == nil || !strings.Contains(err.Error(), "access_denied") {
t.Fatalf("err = %v", err)
}
}
+199
View File
@@ -0,0 +1,199 @@
package cli
// engine.go — `hanzo engine install|serve|status`: manage a local hanzo-engine
// (the `hanzoai` OpenAI + Anthropic model server) on THIS machine.
//
// One source of truth for install logic: `install` runs the SAME install.sh /
// install.ps1 the `curl … | sh` one-liner uses (it downloads the prebuilt,
// cosign-signed binary from the latest github.com/hanzoai/engine release), so the
// CLI never re-implements platform detection or verification. `serve` launches the
// installed binary (`hanzoai --port P run -m MODEL`); `status` probes it, reusing
// the same /v1/models probe `hanzo link --serve-engine` advertises with.
import (
"context"
"fmt"
"io"
"os"
"os/exec"
"path/filepath"
"runtime"
"time"
"github.com/spf13/cobra"
)
const (
installScriptSh = "https://raw.githubusercontent.com/hanzoai/engine/main/install.sh"
installScriptPS = "https://raw.githubusercontent.com/hanzoai/engine/main/install.ps1"
engineBinName = "hanzoai"
)
func newEngineCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
cmd := &cobra.Command{
Use: "engine",
Short: "Run a local hanzo-engine (OpenAI + Anthropic model server)",
Long: "Install, serve, and inspect a local hanzo-engine on this machine.\n" +
"`install` downloads the prebuilt, signed `hanzoai` binary; `serve` runs it on\n" +
":1234; `status` shows whether it is up and which models it serves.",
}
// install ----------------------------------------------------------------
var version, dir string
install := &cobra.Command{
Use: "install",
Short: "Download + install the prebuilt hanzoai binary (runs the canonical install script)",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
return runEngineInstall(cmd, version, dir)
},
}
install.Flags().StringVar(&version, "engine-version", "", "install a specific release tag (default: latest)")
install.Flags().StringVar(&dir, "dir", "", "install directory (default: /usr/local/bin or ~/.local/bin)")
// serve ------------------------------------------------------------------
var model string
var port int
serve := &cobra.Command{
Use: "serve",
Short: "Serve a model with the local hanzoai binary (hanzoai --port P run -m MODEL)",
Long: "Launch the installed hanzoai server. Any args after `--` are passed through to\n" +
"the underlying `hanzoai … run` invocation (e.g. `-- --max-seqs 32`).",
Args: cobra.ArbitraryArgs,
RunE: func(cmd *cobra.Command, extra []string) error {
return runEngineServe(cmd, model, port, extra)
},
}
serve.Flags().StringVarP(&model, "model", "m", "Qwen/Qwen3-4B", "model to serve (HF repo id or local path)")
serve.Flags().IntVarP(&port, "port", "p", 1234, "port to serve the OpenAI + Anthropic API on")
// status -----------------------------------------------------------------
var url string
status := &cobra.Command{
Use: "status",
Short: "Show whether a local hanzo-engine is up and what it serves",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
return runEngineStatus(cmd, envOf(), firstNonEmpty(url, defaultEngineURL))
},
}
status.Flags().StringVar(&url, "url", defaultEngineURL, "local engine URL to probe (GET /v1/models)")
cmd.AddCommand(install, serve, status)
return cmd
}
// runEngineInstall shells out to the canonical install script so there is exactly
// one implementation of platform detection + signature verification.
func runEngineInstall(cmd *cobra.Command, version, dir string) error {
env := os.Environ()
if version != "" {
env = append(env, "HANZOAI_VERSION="+version)
}
if dir != "" {
env = append(env, "HANZOAI_INSTALL_DIR="+dir)
}
var sh *exec.Cmd
if runtime.GOOS == "windows" {
sh = exec.CommandContext(cmd.Context(), "powershell", "-NoProfile", "-Command",
"irm "+installScriptPS+" | iex")
} else {
// curl … | sh — the exact one-liner documented in the README.
sh = exec.CommandContext(cmd.Context(), "sh", "-c",
"curl -fsSL "+installScriptSh+" | sh")
}
sh.Env = env
sh.Stdin, sh.Stdout, sh.Stderr = os.Stdin, cmd.OutOrStdout(), cmd.ErrOrStderr()
if err := sh.Run(); err != nil {
return fmt.Errorf("install script failed: %w", err)
}
return nil
}
// runEngineServe execs the installed hanzoai binary. On Unix it replaces this
// process (syscall.Exec) so signals + exit code flow straight through; on Windows
// it runs as a child with inherited stdio.
func runEngineServe(cmd *cobra.Command, model string, port int, extra []string) error {
bin, err := findEngineBinary()
if err != nil {
return err
}
args := []string{bin, "--port", fmt.Sprintf("%d", port), "run", "-m", model}
args = append(args, extra...)
fmt.Fprintf(cmd.ErrOrStderr(), "→ %s\n", exec.Command(bin, args[1:]...).String())
return execEngine(bin, args)
}
// runEngineStatus probes the local engine and prints (or JSON-emits) its state,
// reusing the same /v1/models probe the fleet advertisement uses.
func runEngineStatus(cmd *cobra.Command, env *Env, url string) error {
ctx, cancel := context.WithTimeout(cmd.Context(), 6*time.Second)
defer cancel()
adv := &engineAdvertisement{URL: url, APIs: []string{"openai", "anthropic"}}
if models, perr := probeEngine(ctx, url); perr != nil {
adv.Status = "unreachable"
} else {
adv.Status = "ready"
adv.Models = models
}
bin, _ := findEngineBinary()
return env.emit(map[string]any{"url": url, "status": adv.Status, "models": adv.Models, "binary": bin},
func(out io.Writer) {
fmt.Fprintf(out, "engine %s — %s\n", adv.URL, describeEngine(adv))
if len(adv.Models) > 0 {
for _, m := range adv.Models {
fmt.Fprintf(out, " model %s\n", m)
}
}
if bin != "" {
fmt.Fprintf(out, "binary %s\n", bin)
} else {
fmt.Fprintln(out, "binary not installed — run `hanzo engine install`")
}
if adv.Status != "ready" {
fmt.Fprintf(out, "hint start it with `hanzo engine serve -m Qwen/Qwen3-4B --port %s`\n",
portOf(url))
}
})
}
// findEngineBinary locates the installed hanzoai binary: PATH first, then the
// directories install.sh / install.ps1 write to.
func findEngineBinary() (string, error) {
name := engineBinName
if runtime.GOOS == "windows" {
name += ".exe"
}
if p, err := exec.LookPath(name); err == nil {
return p, nil
}
home, _ := os.UserHomeDir()
var dirs []string
if runtime.GOOS == "windows" {
if la := os.Getenv("LOCALAPPDATA"); la != "" {
dirs = append(dirs, filepath.Join(la, "Hanzo", "bin"))
}
} else {
dirs = append(dirs, "/usr/local/bin", filepath.Join(home, ".local", "bin"), filepath.Join(home, ".hanzo", "bin"))
}
for _, d := range dirs {
p := filepath.Join(d, name)
if fi, err := os.Stat(p); err == nil && !fi.IsDir() {
return p, nil
}
}
return "", fmt.Errorf("hanzoai not found on PATH or in the default install dirs — run `hanzo engine install`")
}
func portOf(url string) string {
// best-effort: pull the ":<port>" tail for the hint
for i := len(url) - 1; i >= 0; i-- {
if url[i] == ':' {
return url[i+1:]
}
}
return "1234"
}
+14
View File
@@ -0,0 +1,14 @@
//go:build !windows
package cli
import (
"os"
"syscall"
)
// execEngine replaces the current process with hanzoai so signals (Ctrl-C) and
// the exit code flow straight through — `hanzo engine serve` becomes hanzoai.
func execEngine(bin string, args []string) error {
return syscall.Exec(bin, args, os.Environ())
}
+16
View File
@@ -0,0 +1,16 @@
//go:build windows
package cli
import (
"os"
"os/exec"
)
// execEngine runs hanzoai as a child with inherited stdio (Windows has no exec()).
// The child shares the console, so Ctrl-C reaches it; we return its exit error.
func execEngine(bin string, args []string) error {
c := exec.Command(bin, args[1:]...)
c.Stdin, c.Stdout, c.Stderr = os.Stdin, os.Stdout, os.Stderr
return c.Run()
}
+96
View File
@@ -0,0 +1,96 @@
package cli
import (
"bytes"
"context"
"os"
"path/filepath"
"runtime"
"strings"
"testing"
"github.com/spf13/cobra"
)
// TestEngineCmdWiring asserts `hanzo engine` exposes install/serve/status with the
// documented flags — the contract install.sh and the docs promise.
func TestEngineCmdWiring(t *testing.T) {
env := &Env{Output: "table"}
cmd := newEngineCmd(func() *Env { return env }, &globalFlags{})
want := map[string]bool{"install": false, "serve": false, "status": false}
for _, sub := range cmd.Commands() {
if _, ok := want[sub.Name()]; ok {
want[sub.Name()] = true
}
}
for name, found := range want {
if !found {
t.Fatalf("engine subcommand %q missing", name)
}
}
serve, _, _ := cmd.Find([]string{"serve"})
if serve.Flags().Lookup("model") == nil || serve.Flags().Lookup("port") == nil {
t.Fatalf("serve must have --model and --port")
}
status, _, _ := cmd.Find([]string{"status"})
if status.Flags().Lookup("url") == nil {
t.Fatalf("status must have --url")
}
}
// TestEngineStatusReady probes a stub engine and reports it ready with its models.
func TestEngineStatusReady(t *testing.T) {
engine := stubEngine(t, "default", "zen-omni-30b")
defer engine.Close()
var buf bytes.Buffer
env := &Env{Output: "table", out: &buf}
cmd := &cobra.Command{}
cmd.SetContext(context.Background())
if err := runEngineStatus(cmd, env, engine.URL); err != nil {
t.Fatalf("status: %v", err)
}
out := buf.String()
if !strings.Contains(out, "ready") || !strings.Contains(out, "zen-omni-30b") {
t.Fatalf("status output missing ready/model:\n%s", out)
}
}
// TestEngineStatusUnreachable reports a down engine as unreachable (not an error).
func TestEngineStatusUnreachable(t *testing.T) {
var buf bytes.Buffer
env := &Env{Output: "table", out: &buf}
cmd := &cobra.Command{}
cmd.SetContext(context.Background())
// A port with nothing listening.
if err := runEngineStatus(cmd, env, "http://127.0.0.1:1"); err != nil {
t.Fatalf("status should not error on a down engine: %v", err)
}
if !strings.Contains(buf.String(), "unreachable") {
t.Fatalf("expected 'unreachable', got:\n%s", buf.String())
}
}
// TestFindEngineBinary finds hanzoai on PATH.
func TestFindEngineBinary(t *testing.T) {
if runtime.GOOS == "windows" {
t.Skip("PATH exe probe differs on Windows")
}
dir := t.TempDir()
bin := filepath.Join(dir, engineBinName)
if err := os.WriteFile(bin, []byte("#!/bin/sh\n"), 0o755); err != nil {
t.Fatal(err)
}
t.Setenv("PATH", dir)
got, err := findEngineBinary()
if err != nil {
t.Fatalf("findEngineBinary: %v", err)
}
if got != bin {
t.Fatalf("found %q, want %q", got, bin)
}
}
+2359
View File
File diff suppressed because it is too large Load Diff
+157
View File
@@ -0,0 +1,157 @@
package cli
import (
"os"
"path/filepath"
"testing"
)
// TestParseRocmSmiCSV — the AMD GPU inventory names a card from its marketing
// series + gfx target, exactly as `rocm-smi --showproductname --csv` reports on
// evo's gfx1151 Radeon 8060S. This is the primary AMD detection path.
func TestParseRocmSmiCSV(t *testing.T) {
// Real evo output (header + one card row).
csv := []byte("device,Card Series,Card Model,Card Vendor,Card SKU,Subsystem ID,Device Rev,Node ID,GUID,GFX Version\n" +
"card0,Radeon 8060S Graphics,0x1586,Advanced Micro Devices Inc. [AMD/ATI],STRXLGEN,-0x7fe3,0xc1,1,49819,gfx1151\n")
gpus := parseRocmSmiCSV(csv)
if len(gpus) != 1 {
t.Fatalf("want 1 AMD GPU, got %d (%+v)", len(gpus), gpus)
}
if got, want := gpus[0].Name, "AMD Strix Halo \u00b7 Radeon 8060S Graphics (gfx1151)"; got != want {
t.Errorf("name = %q, want %q", got, want)
}
}
// TestGfxNameDecodesTargetVersion — the kfd fallback decodes gfx_target_version.
func TestGfxNameDecodesTargetVersion(t *testing.T) {
for _, c := range []struct {
v int
want string
}{
{110501, "gfx1151"}, // evo Radeon 8060S / Strix Halo
{90012, "gfx9012"}, // sanity: MI-class encoding shape
{100300, "gfx1030"}, // RDNA2
} {
if got := gfxName(c.v); got != c.want {
t.Errorf("gfxName(%d) = %q, want %q", c.v, got, c.want)
}
}
}
// TestParseKfdTopology — the driver-only fallback (no rocm-smi) still finds the GPU
// from /sys/class/kfd: node 0 is the CPU (simd_count 0, skipped), node 1 is the
// gfx1151 GPU. Built against a fixture tree mirroring evo's real properties files.
func TestParseKfdTopology(t *testing.T) {
root := t.TempDir()
writeNode(t, root, "0", "simd_count 0\ngfx_target_version 0\n")
writeNode(t, root, "1", "cpu_cores_count 0\nsimd_count 80\ngfx_target_version 110501\n")
gpus := parseKfdTopology(root)
if len(gpus) != 1 {
t.Fatalf("want 1 GPU node (CPU node 0 skipped), got %d (%+v)", len(gpus), gpus)
}
if got, want := gpus[0].Name, "AMD Strix Halo (gfx1151)"; got != want {
t.Errorf("name = %q, want %q", got, want)
}
if got, want := gpus[0].Arch, "gfx1151"; got != want {
t.Errorf("arch = %q, want %q", got, want)
}
}
// TestParseVulkaninfoSummary — the last resort keeps only AMD/Radeon devices so it
// never double-counts a card another vendor path already reported.
func TestParseVulkaninfoSummary(t *testing.T) {
out := []byte("GPU0:\n\tdeviceName = AMD Radeon Graphics (RADV GFX1151)\n" +
"GPU1:\n\tdeviceName = llvmpipe (LLVM 18.1.0, 256 bits)\n")
gpus := parseVulkaninfoSummary(out)
if len(gpus) != 1 {
t.Fatalf("want 1 AMD device (llvmpipe filtered), got %d (%+v)", len(gpus), gpus)
}
if got := gpus[0].Name; got != "AMD Radeon Graphics (RADV GFX1151)" {
t.Errorf("name = %q", got)
}
}
func writeNode(t *testing.T, root, id, props string) {
t.Helper()
dir := filepath.Join(root, id)
if err := os.MkdirAll(dir, 0o755); err != nil {
t.Fatal(err)
}
if err := os.WriteFile(filepath.Join(dir, "properties"), []byte(props), 0o644); err != nil {
t.Fatal(err)
}
}
// TestPickAmdMemUnified — an APU whose VRAM is a token carve-out reports the
// machine's unified RAM snapped to hardware capacity (evo: 1 GiB VRAM, 118 GiB
// GTT, 124.4 GiB kernel-visible of 128 GiB physical → 128 GiB); a discrete card
// keeps its VRAM.
func TestPickAmdMemUnified(t *testing.T) {
if miB, unified := pickAmdMem(1024, 120832, 127411); !unified || miB != 131072 {
t.Errorf("APU: got (%d, %v), want (131072, true)", miB, unified)
}
if miB, unified := pickAmdMem(24576, 8192, 127411); unified || miB != 24576 {
t.Errorf("discrete: got (%d, %v), want (24576, false)", miB, unified)
}
}
// TestSnapUnified — a small firmware gap snaps up to the DIMM capacity; a big
// carve-out is real lost capacity and stays as-is; exact multiples stand.
func TestSnapUnified(t *testing.T) {
for _, c := range []struct{ in, want int64 }{
{127411, 131072}, // evo: 124.4 GiB visible of 128 GiB physical
{124610, 131072}, // spark GB10: 121.7 GiB visible of 128 GiB physical (~6.3 GiB firmware)
{131072, 131072}, // exact 128 GiB
{119194, 119194}, // ~116 GiB visible (16 GiB BIOS carve) — 11.6 GiB gap, keep honest
{63488, 65536}, // 62 GiB visible of 64 GiB
} {
if got := snapUnified(c.in); got != c.want {
t.Errorf("snapUnified(%d) = %d, want %d", c.in, got, c.want)
}
}
}
// TestAmdAPUName — the board renders the APU as the processor the owner bought,
// normalized from the BIOS shouting; non-Ryzen hosts opt out.
func TestAmdAPUName(t *testing.T) {
if got, want := amdAPUName("AMD RYZEN AI MAX+ 395 w/ Radeon 8060S"), "AMD Ryzen AI Max+ 395 w/ Radeon 8060S"; got != want {
t.Errorf("amdAPUName = %q, want %q", got, want)
}
if got := amdAPUName("Intel(R) Core(TM) i9-14900K"); got != "" {
t.Errorf("non-Ryzen host must opt out, got %q", got)
}
}
// TestApuProcessorNames — only unified-memory cards are renamed; a discrete
// card on the same host keeps its own identity.
func TestApuProcessorNames(t *testing.T) {
gpus := []gpuInfo{
{Name: "AMD Strix Halo \u00b7 Radeon 8060S Graphics (gfx1151)", Arch: "gfx1151", Unified: true},
{Name: "Radeon RX 7900 XTX (gfx1100)", Arch: "gfx1100"},
}
out := apuProcessorNames(gpus, "AMD RYZEN AI MAX+ 395 w/ Radeon 8060S")
if got, want := out[0].Name, "AMD Ryzen AI Max+ 395 w/ Radeon 8060S (gfx1151)"; got != want {
t.Errorf("APU name = %q, want %q", got, want)
}
if got, want := out[1].Name, "Radeon RX 7900 XTX (gfx1100)"; got != want {
t.Errorf("discrete name = %q, want %q", got, want)
}
}
// TestParseNvidiaSmiCSV — a GB10-class unified SoC ("[N/A]" VRAM) reports the
// machine RAM snapped to capacity + its sm arch; a discrete card keeps its VRAM.
func TestParseNvidiaSmiCSV(t *testing.T) {
out := []byte("NVIDIA GB10, [N/A], 12.1\n")
gpus := parseNvidiaSmiCSV(out, 124610)
if len(gpus) != 1 {
t.Fatalf("want 1 GPU, got %d", len(gpus))
}
g := gpus[0]
if g.Name != "NVIDIA GB10" || g.MemoryTotal != "131072 MiB" || !g.Unified || g.Arch != "sm_121" {
t.Errorf("GB10 = %+v", g)
}
disc := parseNvidiaSmiCSV([]byte("NVIDIA GeForce RTX 4090, 24564 MiB, 8.9\n"), 124610)
if d := disc[0]; d.MemoryTotal != "24564 MiB" || d.Unified || d.Arch != "sm_89" {
t.Errorf("discrete = %+v", d)
}
}
+248
View File
@@ -0,0 +1,248 @@
package cli
// gpu_engine_test.go — the `--serve-engine` capability: probing a local hanzo-engine
// and assembling the fleet advertisement + provider registration. Uses an httptest
// stub for the engine so no model (or GPU) is needed.
import (
"context"
"encoding/json"
"net/http"
"net/http/httptest"
"strings"
"testing"
"time"
)
// stubEngine stands in for hanzo-engine's OpenAI-shaped GET /v1/models.
func stubEngine(t *testing.T, models ...string) *httptest.Server {
t.Helper()
mux := http.NewServeMux()
mux.HandleFunc("/v1/models", func(w http.ResponseWriter, _ *http.Request) {
data := make([]map[string]any, 0, len(models))
for _, m := range models {
data = append(data, map[string]any{"id": m, "object": "model", "owned_by": "local"})
}
_ = json.NewEncoder(w).Encode(map[string]any{"object": "list", "data": data})
})
return httptest.NewServer(mux)
}
func TestProbeEngine(t *testing.T) {
srv := stubEngine(t, "default", "zen-omni-30b")
defer srv.Close()
got, err := probeEngine(context.Background(), srv.URL)
if err != nil {
t.Fatalf("probeEngine: %v", err)
}
if len(got) != 2 || got[0] != "default" || got[1] != "zen-omni-30b" {
t.Fatalf("models = %v, want [default zen-omni-30b]", got)
}
}
func TestProbeEngineDown(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
http.Error(w, "loading", http.StatusServiceUnavailable)
}))
defer srv.Close()
if _, err := probeEngine(context.Background(), srv.URL); err == nil {
t.Fatal("probeEngine: want error for a 503 engine, got nil")
}
}
func TestRefreshEngineAdvertises(t *testing.T) {
srv := stubEngine(t, "default")
defer srv.Close()
w := &worker{
identity: "gb10",
hostname: "gb10",
jobsNS: "gpu-jobs",
serveEngine: true,
engineURL: srv.URL,
engineAdvURL: "http://node.example:1234",
}
if changed := w.refreshEngine(context.Background()); !changed {
t.Fatal("first refreshEngine should report a change (nil -> ready)")
}
if w.engine == nil || w.engine.Status != "ready" {
t.Fatalf("engine = %+v, want status ready", w.engine)
}
if w.engine.URL != "http://node.example:1234" {
t.Fatalf("advertised URL = %q, want the endpoint, not the local probe URL", w.engine.URL)
}
if !contains(w.engine.APIs, "openai") || !contains(w.engine.APIs, "anthropic") {
t.Fatalf("APIs = %v, want both openai and anthropic (hanzo-engine serves both)", w.engine.APIs)
}
if len(w.engine.Models) != 1 || w.engine.Models[0] != "default" {
t.Fatalf("models = %v, want [default]", w.engine.Models)
}
// A second probe with an unchanged engine is a no-op (no needless re-register).
if changed := w.refreshEngine(context.Background()); changed {
t.Fatal("second refreshEngine with an unchanged engine should report no change")
}
}
func TestRefreshEngineUnreachable(t *testing.T) {
w := &worker{
identity: "gb10",
serveEngine: true,
engineURL: "http://127.0.0.1:0", // nothing listening
engineAdvURL: "http://127.0.0.1:0",
}
w.refreshEngine(context.Background())
if w.engine == nil || w.engine.Status != "unreachable" {
t.Fatalf("engine = %+v, want status unreachable", w.engine)
}
}
func TestBuildRegistrationCarriesEngine(t *testing.T) {
srv := stubEngine(t, "default")
defer srv.Close()
w := &worker{
identity: "gb10",
hostname: "gb10",
jobsNS: "gpu-jobs",
gpus: []gpuInfo{{Name: "NVIDIA GB10", MemoryTotal: "122880 MiB"}},
serveEngine: true,
studioReady: true,
engineURL: srv.URL,
engineAdvURL: "http://node.example:1234",
}
w.refreshEngine(context.Background())
reg := w.buildRegistration()
if !contains(reg.Capabilities, studioCap) || !contains(reg.Capabilities, engineCap) {
t.Fatalf("capabilities = %v, want both %q and %q", reg.Capabilities, studioCap, engineCap)
}
if reg.Engine == nil || reg.Engine.URL != "http://node.example:1234" {
t.Fatalf("registration engine = %+v, want the advertised endpoint", reg.Engine)
}
// The presence record's Input must carry the endpoint so GET /v1/fleet/workers
// (which decodes this exact JSON) can advertise it.
raw, err := json.Marshal(reg)
if err != nil {
t.Fatalf("marshal registration: %v", err)
}
for _, want := range []string{`"engine.serve"`, `"http://node.example:1234"`, `"openai"`, `"anthropic"`} {
if !strings.Contains(string(raw), want) {
t.Fatalf("registration JSON missing %s:\n%s", want, raw)
}
}
}
func TestCapabilitiesWithoutEngine(t *testing.T) {
w := &worker{serveEngine: false, studioReady: true}
caps := w.capabilities()
if len(caps) != 1 || caps[0] != studioCap {
t.Fatalf("capabilities = %v, want just [%q] when not serving an engine", caps, studioCap)
}
}
func TestProviderBodyIsOpenAICompatible(t *testing.T) {
w := &worker{
identity: "gb10",
engine: &engineAdvertisement{URL: "http://node.example:1234", Status: "ready", Models: []string{"zen-omni-30b"}},
}
body := w.providerBody()
if body["type"] != "Local" {
t.Fatalf("type = %v, want Local (OpenAI-compatible; gateway auto-appends /v1)", body["type"])
}
if body["providerUrl"] != "http://node.example:1234" {
t.Fatalf("providerUrl = %v", body["providerUrl"])
}
if body["name"] != "gpu-gb10" {
t.Fatalf("name = %v, want gpu-gb10", body["name"])
}
if body["subType"] != "zen-omni-30b" {
t.Fatalf("subType = %v, want the served model", body["subType"])
}
}
// TestConnectServeEngineRoundTrip closes the loop end-to-end on this box, no model
// and no production: a stub hanzo-engine (GET /v1/models) + a stub cloud that stores
// the presence Input and serves it back on GET /v1/fleet/workers. It exercises the
// real chain — probe → build registration → POST the fleet activity → GET
// /v1/fleet/workers → the engine endpoint is advertised.
func TestConnectServeEngineRoundTrip(t *testing.T) {
engine := stubEngine(t, "default", "zen-omni-30b")
defer engine.Close()
var storedInput registration // what the CLI POSTed as the presence record's Input
cloud := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
switch {
case r.Method == http.MethodPost && strings.HasSuffix(r.URL.Path, "/fleet/activities"):
var body struct {
Input registration `json:"input"`
}
_ = json.NewDecoder(r.Body).Decode(&body)
storedInput = body.Input
w.WriteHeader(http.StatusOK)
case r.Method == http.MethodGet && r.URL.Path == "/v1/fleet/workers":
// Fold the stored registration into the fleet worker shape, exactly as
// clients/visor/fleet.go byoWorkers does.
_ = json.NewEncoder(w).Encode(map[string]any{"workers": []fleetWorker{{
ID: "gb10", Hostname: storedInput.Hostname, Provider: "byo", Status: "online",
GPUs: storedInput.GPUs, Capabilities: storedInput.Capabilities, Engine: storedInput.Engine,
}}})
default: // namespace ensure + anything else
w.WriteHeader(http.StatusOK)
}
}))
defer cloud.Close()
t.Setenv("HANZO_TOKEN", "test-token") // ensureToken honors this; no `hanzo login` needed
w := &worker{
env: &Env{CloudURL: cloud.URL},
http: &http.Client{Timeout: 5 * time.Second},
baseURL: cloud.URL,
identity: "gb10",
hostname: "gb10",
jobsNS: "gpu-jobs",
gpus: []gpuInfo{{Name: "NVIDIA GB10", MemoryTotal: "122880 MiB"}},
handlers: map[string]jobHandler{},
serveEngine: true,
engineURL: engine.URL,
engineAdvURL: "http://node.example:1234",
}
ctx := context.Background()
w.refreshEngine(ctx)
if err := w.register(ctx); err != nil {
t.Fatalf("register: %v", err)
}
var resp struct {
Workers []fleetWorker `json:"workers"`
}
if _, err := w.call(ctx, http.MethodGet, "/v1/fleet/workers", nil, &resp); err != nil {
t.Fatalf("GET /v1/fleet/workers: %v", err)
}
if len(resp.Workers) != 1 {
t.Fatalf("workers = %d, want 1", len(resp.Workers))
}
fw := resp.Workers[0]
if !contains(fw.Capabilities, engineCap) {
t.Fatalf("fleet worker capabilities = %v, want engine.serve", fw.Capabilities)
}
if fw.Engine == nil || fw.Engine.URL != "http://node.example:1234" || fw.Engine.Status != "ready" {
t.Fatalf("fleet worker engine = %+v, want the advertised ready endpoint", fw.Engine)
}
if len(fw.Engine.Models) != 2 {
t.Fatalf("fleet worker engine models = %v, want 2", fw.Engine.Models)
}
}
func contains(xs []string, v string) bool {
for _, x := range xs {
if x == v {
return true
}
}
return false
}
+75
View File
@@ -0,0 +1,75 @@
package cli
import (
"encoding/json"
"os/exec"
"strings"
"testing"
)
// TestFnValidate — payload bounds: script required, flag-injection via
// requirements refused, timeout defaulted and capped.
func TestFnValidate(t *testing.T) {
if _, err := fnValidate(json.RawMessage(`{}`)); err == nil {
t.Error("empty script must be refused")
}
if _, err := fnValidate(json.RawMessage(`{"script":"print(1)","requirements":["--index-url=evil"]}`)); err == nil {
t.Error("flag-shaped requirement must be refused")
}
in, err := fnValidate(json.RawMessage(`{"script":"print(1)"}`))
if err != nil || in.TimeoutSeconds != 3600 {
t.Errorf("default timeout: got %d, err %v", in.TimeoutSeconds, err)
}
in, _ = fnValidate(json.RawMessage(`{"script":"print(1)","timeoutSeconds":999999}`))
if in.TimeoutSeconds != 21600 {
t.Errorf("timeout cap: got %d, want 21600", in.TimeoutSeconds)
}
}
// TestTailBuffer — a chatty training loop keeps only the LAST bytes, flagged.
func TestTailBuffer(t *testing.T) {
tb := &tailBuffer{cap: 8}
tb.Write([]byte("0123456789"))
if string(tb.buf) != "23456789" || !tb.truncated {
t.Errorf("tail = %q truncated=%v", tb.buf, tb.truncated)
}
tb2 := &tailBuffer{cap: 8}
tb2.Write([]byte("abc"))
if string(tb2.buf) != "abc" || tb2.truncated {
t.Errorf("small write mangled: %q %v", tb2.buf, tb2.truncated)
}
}
// TestHasNonRenderLane — echo and studio.render alone keep the render-only
// poison guard; a registered fn.run lane lifts it.
func TestHasNonRenderLane(t *testing.T) {
w := &worker{handlers: map[string]jobHandler{"echo": echoHandler, studioCap: nil}}
if w.hasNonRenderLane() {
t.Error("render-only worker must report no extra lane")
}
w.handlers[fnCap] = fnRunHandler
if !w.hasNonRenderLane() {
t.Error("fn.run lane must lift the guard")
}
}
// TestFnRunSmoke — the real handler end-to-end against the local uv: a script
// that prints and exits 0. Skipped where uv is absent.
func TestFnRunSmoke(t *testing.T) {
if !uvPresent() {
t.Skip("uv not installed")
}
res, err := fnRunHandler(t.Context(), json.RawMessage(`{"script":"print(2+2)","timeoutSeconds":120}`))
if err != nil {
t.Fatalf("fn.run: %v", err)
}
m := res.(map[string]any)
if !strings.Contains(m["output"].(string), "4") {
t.Errorf("output = %q, want it to contain 4", m["output"])
}
}
func uvPresent() bool {
_, err := exec.LookPath("uv")
return err == nil
}
+92
View File
@@ -0,0 +1,92 @@
package cli
import (
"bytes"
"context"
"net/http"
"net/http/httptest"
"os"
"path/filepath"
"testing"
"time"
)
// TestMirrorRenders verifies the render mirror: it scans the local studio output
// tree and POSTs every image (new or changed) to /v1/library/upload with the node's
// identity + subfolder + bearer, skips unchanged files across scans, and re-uploads
// a changed file. This is the path that lands EVERY render in studio.hanzo.ai even
// when it was produced outside the job/claim path.
func TestMirrorRenders(t *testing.T) {
t.Setenv("HANZO_TOKEN", "test-bearer")
dir := t.TempDir()
if err := os.MkdirAll(filepath.Join(dir, "renders"), 0o755); err != nil {
t.Fatal(err)
}
write := func(rel, body string) {
if err := os.WriteFile(filepath.Join(dir, filepath.FromSlash(rel)), []byte(body), 0o644); err != nil {
t.Fatal(err)
}
}
write("renders/a.png", "\x89PNG-a")
write("top.jpg", "jpg-top")
write("notes.txt", "not an image")
type up struct{ name, node, subpath, auth string }
var got []up
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/library/upload" {
http.Error(w, "not found", http.StatusNotFound)
return
}
_ = r.ParseMultipartForm(1 << 20)
name := ""
if r.MultipartForm != nil {
for _, fh := range r.MultipartForm.File["image"] {
name = fh.Filename
}
}
got = append(got, up{
name: name,
node: r.URL.Query().Get("node"),
subpath: r.URL.Query().Get("subpath"),
auth: r.Header.Get("Authorization"),
})
w.Header().Set("Content-Type", "application/json")
_, _ = w.Write([]byte(`{"ok":true,"path":"x"}`))
}))
defer srv.Close()
w := &worker{env: &Env{}, http: &http.Client{Timeout: 10 * time.Second}, identity: "spark"}
seen := map[string]int64{}
var buf bytes.Buffer
w.mirrorRenders(context.Background(), &buf, dir, srv.URL, seen)
if len(got) != 2 {
t.Fatalf("uploaded %d files, want 2 images (the .txt is skipped): %+v", len(got), got)
}
var a *up
for i := range got {
if got[i].name == "a.png" {
a = &got[i]
}
}
if a == nil || a.subpath != "renders" || a.node != "spark" || a.auth != "Bearer test-bearer" {
t.Fatalf("renders/a.png upload = %+v, want subpath=renders node=spark bearer set", a)
}
// A second scan re-uploads nothing (seen matches every size).
got = nil
w.mirrorRenders(context.Background(), &buf, dir, srv.URL, seen)
if len(got) != 0 {
t.Fatalf("second scan uploaded %d files, want 0 (all unchanged): %+v", len(got), got)
}
// A changed file is re-uploaded on the next scan.
write("renders/a.png", "\x89PNG-a-grew")
got = nil
w.mirrorRenders(context.Background(), &buf, dir, srv.URL, seen)
if len(got) != 1 || got[0].name != "a.png" {
t.Fatalf("after change, uploaded %+v, want just renders/a.png", got)
}
}
+109
View File
@@ -0,0 +1,109 @@
package cli
import (
"encoding/json"
"testing"
)
func TestSharePolicyReject(t *testing.T) {
studioInput := json.RawMessage(`{"prompt":{},"org":"karma","project":"swimwear"}`)
engineInput := json.RawMessage(`{"model":"Qwen/Qwen3-4B","org":"hanzo"}`)
cases := []struct {
name string
policy *SharePolicy
jobType string
input json.RawMessage
allow bool // true == reject() returns ""
}{
{"nil policy is permissive", nil, "studio.render", studioInput, true},
{"empty policy is permissive", &SharePolicy{}, "studio.render", studioInput, true},
{
"job type allowed",
&SharePolicy{AllowedJobTypes: []string{"studio.render"}},
"studio.render", studioInput, true,
},
{
"job type not allowed",
&SharePolicy{AllowedJobTypes: []string{"engine.serve"}},
"studio.render", studioInput, false,
},
{
"org allowed",
&SharePolicy{AllowedOrgs: []string{"karma", "hanzo"}},
"studio.render", studioInput, true,
},
{
"org not allowed",
&SharePolicy{AllowedOrgs: []string{"hanzo"}},
"studio.render", studioInput, false,
},
{
"project not allowed",
&SharePolicy{AllowedProjects: []string{"lifestyle"}},
"studio.render", studioInput, false,
},
{
"model allowed",
&SharePolicy{AllowedModels: []string{"Qwen/Qwen3-4B"}},
"engine.serve", engineInput, true,
},
{
"model not allowed",
&SharePolicy{AllowedModels: []string{"meta/llama-3"}},
"engine.serve", engineInput, false,
},
{
"absent field skips its gate (input has no project)",
&SharePolicy{AllowedProjects: []string{"lifestyle"}},
"engine.serve", engineInput, true,
},
{
"combined: all gates pass",
&SharePolicy{
AllowedJobTypes: []string{"studio.render"},
AllowedOrgs: []string{"karma"},
AllowedProjects: []string{"swimwear"},
},
"studio.render", studioInput, true,
},
}
for _, tc := range cases {
t.Run(tc.name, func(t *testing.T) {
reason := tc.policy.reject(tc.jobType, tc.input)
if got := reason == ""; got != tc.allow {
t.Fatalf("reject()=%q; want allow=%v", reason, tc.allow)
}
})
}
}
func TestLoadSharePolicyInline(t *testing.T) {
t.Setenv("HANZO_GPU_POLICY", `{"allowedJobTypes":["studio.render"],"allowedOrgs":["karma"],"maxConcurrent":2}`)
p, err := loadSharePolicy()
if err != nil {
t.Fatalf("loadSharePolicy: %v", err)
}
if p == nil {
t.Fatal("expected a policy, got nil")
}
if len(p.AllowedJobTypes) != 1 || p.AllowedJobTypes[0] != "studio.render" {
t.Fatalf("AllowedJobTypes=%v", p.AllowedJobTypes)
}
if p.MaxConcurrent != 2 {
t.Fatalf("MaxConcurrent=%d", p.MaxConcurrent)
}
if p.reject("engine.serve", json.RawMessage(`{}`)) == "" {
t.Fatal("expected engine.serve to be rejected by studio.render-only policy")
}
}
func TestLoadSharePolicyUnset(t *testing.T) {
t.Setenv("HANZO_GPU_POLICY", "")
t.Setenv("HANZO_GPU_POLICY_FILE", "")
p, err := loadSharePolicy()
if err != nil || p != nil {
t.Fatalf("unset policy: got (%v, %v), want (nil, nil)", p, err)
}
}
+291
View File
@@ -0,0 +1,291 @@
package cli
// gpu_queue_test.go — the per-GPU claim contract: a job pinned to THIS machine's
// lane ("gpu:<identity>") is claimed BEFORE the shared any-GPU lane ("gpu-jobs"),
// both within the gpu-jobs namespace. A stub cloud records the taskQueue of every
// claim so the ORDER is the assertion.
import (
"context"
"encoding/json"
"io"
"net/http"
"net/http/httptest"
"strings"
"sync"
"testing"
"time"
)
// stubJobsCloud records the taskQueue of every claim and serves the queued job (if
// any) on the matching lane, once. A lane with no job (or already drained) answers
// 204; complete/fail/heartbeat answer 200.
func stubJobsCloud(t *testing.T, claims *[]string, jobsByLane map[string]*claimedActivity) *httptest.Server {
t.Helper()
return httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
if r.Method == http.MethodPost && strings.HasSuffix(r.URL.Path, "/activities/claim") {
var body struct {
TaskQueue string `json:"taskQueue"`
}
_ = json.NewDecoder(r.Body).Decode(&body)
*claims = append(*claims, body.TaskQueue)
if job := jobsByLane[body.TaskQueue]; job != nil {
jobsByLane[body.TaskQueue] = nil // deliver once
_ = json.NewEncoder(w).Encode(job)
return
}
w.WriteHeader(http.StatusNoContent)
return
}
w.WriteHeader(http.StatusOK) // complete / fail / heartbeat
}))
}
// echoJob is a GPU-free job the worker's echo handler runs to completion instantly,
// so a claim test never needs a real render backend.
func echoJob(id string) *claimedActivity {
a := &claimedActivity{Input: json.RawMessage(`{}`)}
a.Execution.WorkflowId, a.Execution.RunId = id, id
a.Type.Name = "echo"
return a
}
func testWorker(t *testing.T, url string) *worker {
t.Helper()
t.Setenv("HANZO_TOKEN", "test-token") // ensureToken honors this; no `hanzo login`
return &worker{
env: &Env{CloudURL: url},
http: &http.Client{Timeout: 5 * time.Second},
baseURL: url,
identity: "spark",
hostname: "spark",
jobsNS: "gpu-jobs",
handlers: map[string]jobHandler{"echo": echoHandler},
studioReady: true, // a render-capable node (preflight passed)
}
}
func TestGPUQueueLaneName(t *testing.T) {
w := &worker{identity: "spark"}
if got := w.gpuQueue(); got != "gpu:spark" {
t.Fatalf("gpuQueue() = %q, want gpu:spark", got)
}
}
// A job pinned to THIS GPU's lane is claimed first — the shared lane is not even
// polled that cycle.
func TestClaimPrefersTargetedLane(t *testing.T) {
var claims []string
srv := stubJobsCloud(t, &claims, map[string]*claimedActivity{"gpu:spark": echoJob("j1")})
defer srv.Close()
if err := testWorker(t, srv.URL).claimAndRun(context.Background(), io.Discard); err != nil {
t.Fatalf("claimAndRun: %v", err)
}
if len(claims) != 1 || claims[0] != "gpu:spark" {
t.Fatalf("claims = %v, want exactly [gpu:spark] (targeted first; shared not polled)", claims)
}
}
// With its own lane empty, the worker falls through to the shared any-GPU lane.
func TestClaimFallsBackToSharedLane(t *testing.T) {
var claims []string
srv := stubJobsCloud(t, &claims, map[string]*claimedActivity{"gpu-jobs": echoJob("j2")})
defer srv.Close()
if err := testWorker(t, srv.URL).claimAndRun(context.Background(), io.Discard); err != nil {
t.Fatalf("claimAndRun: %v", err)
}
if len(claims) != 2 || claims[0] != "gpu:spark" || claims[1] != "gpu-jobs" {
t.Fatalf("claims = %v, want [gpu:spark gpu-jobs] (targeted, then shared)", claims)
}
}
// Both lanes empty polls targeted THEN shared and runs nothing.
func TestClaimBothLanesEmpty(t *testing.T) {
var claims []string
srv := stubJobsCloud(t, &claims, map[string]*claimedActivity{})
defer srv.Close()
if err := testWorker(t, srv.URL).claimAndRun(context.Background(), io.Discard); err != nil {
t.Fatalf("claimAndRun: %v", err)
}
if len(claims) != 2 || claims[0] != "gpu:spark" || claims[1] != "gpu-jobs" {
t.Fatalf("claims = %v, want [gpu:spark gpu-jobs]", claims)
}
}
// The render submit seam is the gated worker-mode execute path, not the open /prompt
// — the shared contract with the studio's --worker-mode gate.
func TestWorkerExecuteSeamIsGated(t *testing.T) {
if localWorkerExecute != "http://127.0.0.1:8188/v1/worker/execute" {
t.Fatalf("localWorkerExecute = %q, want the gated /v1/worker/execute seam", localWorkerExecute)
}
}
// A HUNG nvidia-smi (blocks until its bounded context fires) must NOT block the
// caller: reportSample detaches the probe+POST onto a goroutine and returns at once,
// so the worker's select loop keeps heartbeating and claiming. Guards the
// worker-wedge regression (a synchronous probe that stalls the loop under GPU/driver
// pressure → the machine flaps offline mid-render).
func TestReportSampleNeverBlocksLoop(t *testing.T) {
orig := nvidiaSmi
defer func() { nvidiaSmi = orig }()
probing := make(chan struct{})
release := make(chan struct{})
nvidiaSmi = func(ctx context.Context) ([]byte, error) {
close(probing) // entered the probe (the nvidiaSmi var read already happened)
select {
case <-release: // the test lets us finish
case <-ctx.Done(): // or the bounded probe timeout fires
}
return nil, ctx.Err()
}
t.Setenv("HANZO_TOKEN", "t")
w := &worker{identity: "spark", hostname: "spark", http: &http.Client{Timeout: time.Second}, env: &Env{}, baseURL: "http://127.0.0.1:0"}
done := make(chan struct{})
go func() { w.reportSample(context.Background()); close(done) }()
select {
case <-done: // returned immediately — the select loop is never wedged
case <-time.After(500 * time.Millisecond):
t.Fatal("reportSample blocked the caller — a hung sampler would wedge the worker loop")
}
select {
case <-probing: // the probe really ran, on the detached goroutine (off the critical path)
case <-time.After(2 * time.Second):
t.Fatal("probe never started")
}
close(release)
}
// A node that can't serve renders (preflight failed) claims NOTHING — it must never
// pull a render job onto a box that will only refuse it on the gated seam (poison
// loop). It still heartbeats presence; it just stays idle.
func TestNotStudioReadyClaimsNothing(t *testing.T) {
var claims []string
srv := stubJobsCloud(t, &claims, map[string]*claimedActivity{"gpu:spark": echoJob("j1")})
defer srv.Close()
w := testWorker(t, srv.URL)
w.studioReady = false
if err := w.claimAndRun(context.Background(), io.Discard); err != nil {
t.Fatalf("claimAndRun: %v", err)
}
if len(claims) != 0 {
t.Fatalf("a not-ready node claimed %v; want zero claims", claims)
}
}
// The terminal report must hit the RIGHT activity — namespace gpu-jobs, the CLAIMED
// workflow+run ids, the correct verb. A stub that 200s every path lets an ns/id
// routing regression pass, so assert the exact paths for both complete and fail.
func TestTerminalReportsHitCorrectActivityPath(t *testing.T) {
t.Setenv("HANZO_TOKEN", "t")
var mu sync.Mutex
terminal := map[string]string{}
served := 0
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
switch {
case strings.HasSuffix(r.URL.Path, "/activities/claim"):
var body struct {
TaskQueue string `json:"taskQueue"`
}
_ = json.NewDecoder(r.Body).Decode(&body)
if body.TaskQueue != "gpu:spark" {
w.WriteHeader(http.StatusNoContent)
return
}
mu.Lock()
n := served
served++
mu.Unlock()
switch n {
case 0:
_ = json.NewEncoder(w).Encode(echoJob("wf1")) // echo handler → complete
case 1:
j := echoJob("wf2")
j.Type.Name = "nope" // no handler → fail
_ = json.NewEncoder(w).Encode(j)
default:
w.WriteHeader(http.StatusNoContent)
}
case strings.HasSuffix(r.URL.Path, "/complete"):
mu.Lock()
terminal["complete"] = r.URL.Path
mu.Unlock()
w.WriteHeader(http.StatusOK)
case strings.HasSuffix(r.URL.Path, "/fail"):
mu.Lock()
terminal["fail"] = r.URL.Path
mu.Unlock()
w.WriteHeader(http.StatusOK)
default:
w.WriteHeader(http.StatusOK)
}
}))
defer srv.Close()
w := testWorker(t, srv.URL)
if err := w.claimAndRun(context.Background(), io.Discard); err != nil {
t.Fatalf("run1 (echo→complete): %v", err)
}
if err := w.claimAndRun(context.Background(), io.Discard); err != nil {
t.Fatalf("run2 (unknown→fail): %v", err)
}
if got := terminal["complete"]; got != "/v1/tasks/namespaces/gpu-jobs/activities/wf1/wf1/complete" {
t.Fatalf("complete path = %q, want the claimed activity's exact ns+ids", got)
}
if got := terminal["fail"]; got != "/v1/tasks/namespaces/gpu-jobs/activities/wf2/wf2/fail" {
t.Fatalf("fail path = %q, want the claimed activity's exact ns+ids", got)
}
}
// SharePolicy.reject's fallback: an ABSENT or unparseable input field skips its gate
// (permissive), never a hard error, so a policy only ever narrows on fields it can read.
func TestSharePolicyRejectFallback(t *testing.T) {
var nilp *SharePolicy
if r := nilp.reject("studio.render", nil); r != "" {
t.Fatalf("nil policy must allow everything: %q", r)
}
p := &SharePolicy{AllowedJobTypes: []string{"studio.render"}}
if p.reject("echo", nil) == "" {
t.Fatal("a disallowed job type must be rejected")
}
if r := p.reject("studio.render", nil); r != "" {
t.Fatalf("an allowed job type must pass: %q", r)
}
p2 := &SharePolicy{AllowedOrgs: []string{"acme"}}
if r := p2.reject("studio.render", json.RawMessage(`{}`)); r != "" {
t.Fatalf("absent org must SKIP the org gate (fallback), not reject: %q", r)
}
if r := p2.reject("studio.render", json.RawMessage(`{"org":"acme"}`)); r != "" {
t.Fatalf("a matching org must pass: %q", r)
}
if p2.reject("studio.render", json.RawMessage(`{"org":"other"}`)) == "" {
t.Fatal("a non-allowed org must be rejected")
}
if r := p2.reject("studio.render", json.RawMessage(`not json`)); r != "" {
t.Fatalf("unparseable input must skip input gates, not reject: %q", r)
}
}
// studioCap is advertised ONLY when the node can actually render: a missing worker
// token is never ready (the gated seam would 403), and the block reason is explicit.
func TestStudioReadyGatesCapability(t *testing.T) {
t.Setenv("STUDIO_WORKER_TOKEN", "")
w := &worker{launchesStudio: true, http: &http.Client{}}
w.refreshStudioReady(context.Background())
if w.studioReady {
t.Fatal("no token must never be studio-ready")
}
if contains(w.capabilities(), studioCap) {
t.Fatalf("studioCap advertised without a token: %v", w.capabilities())
}
if w.studioBlockReason() == "" {
t.Fatal("a not-ready node must explain why it won't render")
}
// Token present + we launch the studio ⇒ ready ⇒ studioCap advertised.
t.Setenv("STUDIO_WORKER_TOKEN", "tok")
if changed := w.refreshStudioReady(context.Background()); !changed {
t.Fatal("adding the token should flip readiness")
}
if !w.studioReady || !contains(w.capabilities(), studioCap) {
t.Fatalf("token + launchesStudio must be ready + advertise studioCap: ready=%v caps=%v", w.studioReady, w.capabilities())
}
}
+88
View File
@@ -0,0 +1,88 @@
package cli
// gpu_spec_test.go — the host static-spec a `hanzo link` node reports so
// GET /v1/fleet can show its CPU arch, core count and total RAM (the fields a
// code-linked box already carries). Real telemetry only: arch is `uname -m`, cores
// are runtime.NumCPU, RAM is parsed from the OS — never a hardcoded machine.
import (
"os/exec"
"runtime"
"strings"
"testing"
)
func TestParseMemTotalKB(t *testing.T) {
// A real /proc/meminfo head from a 128 GiB box. MemTotal is in kB; we report bytes.
meminfo := []byte("MemTotal: 131923980 kB\nMemFree: 1048576 kB\nMemAvailable: 120000000 kB\n")
if got, want := parseMemTotalKB(meminfo), int64(131923980)*1024; got != want {
t.Fatalf("parseMemTotalKB = %d, want %d bytes", got, want)
}
// Absent / malformed input is reported as 0 (unknown), never a guess.
for name, in := range map[string]string{
"empty": "",
"no-memtotal": "MemFree: 100 kB\n",
"malformed": "MemTotal: notanumber kB\n",
"no-value": "MemTotal:\n",
} {
if got := parseMemTotalKB([]byte(in)); got != 0 {
t.Fatalf("%s: parseMemTotalKB = %d, want 0", name, got)
}
}
}
// detectMemTotal reads the real host, so on Linux/macOS CI it must return a positive
// byte count — proof the reporter reads actual RAM rather than shipping 0.
func TestDetectMemTotalIsReal(t *testing.T) {
if runtime.GOOS != "linux" && runtime.GOOS != "darwin" {
t.Skipf("no MemTotal source on %s", runtime.GOOS)
}
got := detectMemTotal()
if got <= 0 {
t.Fatalf("detectMemTotal = %d, want the host's real RAM (>0)", got)
}
// Evidence: what THIS host actually reports (never hardcoded). On the GB10 spark
// box this prints aarch64 + ~128 GiB read from /proc/meminfo.
t.Logf("real host spec: arch=%s cpus=%d memory=%d bytes (%.1f GiB)",
detectArch(), runtime.NumCPU(), got, float64(got)/(1<<30))
}
// detectArch must match the fleet's `uname -m` convention (aarch64 | x86_64 | arm64),
// NOT runtime.GOARCH (arm64 | amd64) — so a machine that appears as both a run-target
// and a linked worker shows ONE arch string on the board. On Linux uname -m is
// aarch64/x86_64; assert the real host agrees and is never GOARCH's amd64.
func TestDetectArchMatchesUnameConvention(t *testing.T) {
got := detectArch()
if got == "" {
t.Fatal("detectArch returned empty; must fall back to runtime.GOARCH")
}
if out, err := exec.Command("uname", "-m").Output(); err == nil {
if want := strings.TrimSpace(string(out)); want != "" && got != want {
t.Fatalf("detectArch = %q, want `uname -m` %q (fleet convention)", got, want)
}
}
// Guard the regression this test exists for: on Linux amd64 the value must be
// x86_64, never GOARCH's "amd64".
if runtime.GOOS == "linux" && runtime.GOARCH == "amd64" && got == "amd64" {
t.Fatal("arch is GOARCH 'amd64'; the fleet convention is 'x86_64'")
}
t.Logf("detectArch=%q (GOARCH=%q)", got, runtime.GOARCH)
}
// buildRegistration must carry this host's detected arch (uname -m), cores (NumCPU)
// and RAM — so spark reports aarch64 and evo-2 reports x86_64, both ~128 GB, matching
// how the same machines already report as code-linked run-targets.
func TestBuildRegistrationCarriesHostSpec(t *testing.T) {
const mem = int64(137438953472) // 128 GiB
w := &worker{hostname: "spark", jobsNS: "gpu-jobs", arch: "aarch64", memory: mem}
reg := w.buildRegistration()
if reg.Arch != "aarch64" {
t.Fatalf("Arch = %q, want the worker's detected arch %q", reg.Arch, "aarch64")
}
if reg.CPUs != runtime.NumCPU() {
t.Fatalf("CPUs = %d, want runtime.NumCPU %d", reg.CPUs, runtime.NumCPU())
}
if reg.Memory != mem {
t.Fatalf("Memory = %d, want the detected total %d", reg.Memory, mem)
}
}
+55
View File
@@ -0,0 +1,55 @@
package cli
import (
"context"
"net/http"
"os"
"testing"
"time"
)
// TestUploadOutputsIntegration exercises the real BYO-GPU result-upload path:
// fetchLocalOutput pulls a finished render from the LOCAL studio's /view and
// postGalleryOutput POSTs it to the org studio's /upload/output with the user's
// IAM token, landing it in orgs/{org}/output (the gallery, S3-mirrored).
//
// It is a live integration test, skipped unless the box is wired for it:
//
// HANZO_TOKEN=<iam bearer> \
// HANZO_UPLOAD_IT_FILE=<name of a file the local studio serves at /view?type=output> \
// HANZO_STUDIO_UPLOAD_URL=<org studio base, e.g. https://studio.hanzo.ai> \
// go test ./cli -run TestUploadOutputsIntegration -v
//
// The local studio is assumed at localComfyUI (127.0.0.1:8188).
func TestUploadOutputsIntegration(t *testing.T) {
tok := os.Getenv("HANZO_TOKEN")
file := os.Getenv("HANZO_UPLOAD_IT_FILE")
if tok == "" || file == "" {
t.Skip("set HANZO_TOKEN and HANZO_UPLOAD_IT_FILE to run the live upload integration test")
}
uploadURL := firstNonEmpty(os.Getenv("HANZO_STUDIO_UPLOAD_URL"), defaultStudioUploadURL)
w := &worker{
env: &Env{}, // ensureToken reads HANZO_TOKEN first, so no creds needed
http: &http.Client{Timeout: 60 * time.Second},
studioUploadURL: uploadURL,
}
ctx, cancel := context.WithTimeout(context.Background(), 60*time.Second)
defer cancel()
subfolder := os.Getenv("HANZO_UPLOAD_IT_SUBFOLDER") // "" == top of output
out := file
if subfolder != "" {
out = subfolder + "/" + file
}
gallery, err := w.uploadOutputs(ctx, []string{out}, uploadURL, "karma")
if err != nil {
t.Fatalf("uploadOutputs(%q -> %s): %v", out, uploadURL, err)
}
if len(gallery) != 1 {
t.Fatalf("expected 1 gallery path, got %d: %v", len(gallery), gallery)
}
t.Logf("uploaded %q -> %s gallery path %q", out, uploadURL, gallery[0])
}
+200
View File
@@ -0,0 +1,200 @@
package cli
// link.go — `hanzo link | unlink | status`: bring THIS machine into the Hanzo
// cloud fleet AS A NODE, take it back out, and view the fleet.
//
// A node is two orthogonal memberships, composed under one verb:
//
// 1. The FABRIC — hanzod on hanzo.network. `link` starts it by invoking the
// canonical fabric verb `hanzo node up` (the Rust node CLI: resolve a hanzod
// binary, spawn it detached, record its pid). link does NOT reimplement hanzod
// supervision — there is exactly one way to start hanzod, and this composes it.
// Best-effort: a node with no hanzod still joins the compute fleet (CPU-only
// boxes and dev machines link fine); `--no-fabric` skips it outright.
//
// 2. The COMPUTE fleet — this machine's inventory (CPU cores + model, memory, and
// each GPU as its own resource) registered as a heartbeating presence in the
// org's `fleet` namespace, running the outbound worker loop that claims jobs
// from `gpu-jobs`. That machinery lives in gpu.go (runConnect); `link` runs it.
//
// `unlink` reverses both: it deregisters the worker (drops the fleet row), then
// stops the fabric (`hanzo node stop`). `status` is the fleet view — every machine
// with each of its GPUs shown distinctly, this box highlighted.
//
// One identity: the IAM token `hanzo login` mints authorizes every cloud call; the
// server derives the tenant from the token. No secrets on the box.
import (
"context"
"errors"
"fmt"
"os"
"os/exec"
"time"
"github.com/spf13/cobra"
)
// ---------------------------------------------------------------------------
// link / unlink / status — the node-level command surface.
// ---------------------------------------------------------------------------
func newLinkCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
var opts connectOpts
var daemon bool
var noFabric bool
cmd := &cobra.Command{
Use: "link",
Short: "Bring this machine into the Hanzo cloud fleet as a node",
Long: "Link this machine into the Hanzo cloud as a node: join the fabric (start\n" +
"hanzod on hanzo.network) and register as a compute worker — advertising this\n" +
"host's CPU (cores + model), memory, and each GPU as its own resource, then\n" +
"heartbeating and claiming jobs from your org's queue. The node shows up in the\n" +
"console (Machines + GPUs) and on `hanzo status`. Works on a CPU-only box.\n" +
"Authentication reuses the `hanzo login` token; the org is taken from its claims.",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
if daemon {
return installDaemon(cmd, opts)
}
// 1. Fabric: start hanzod via the canonical `hanzo node up` (best-effort).
startFabric(cmd, noFabric)
// 2. Compute fleet: register inventory, heartbeat, claim jobs (foreground).
return runConnect(cmd, envOf(), opts)
},
}
f := cmd.Flags()
f.StringVar(&opts.jobsNS, "jobs-namespace", defaultJobsNS, "tasks namespace to claim jobs from")
f.BoolVar(&noFabric, "no-fabric", false, "join the compute fleet only; do not start hanzod")
f.BoolVar(&daemon, "daemon", false, "install a systemd --user unit (Restart=always) instead of running in the foreground")
f.BoolVar(&opts.serveEngine, "serve-engine", false, "also advertise a hanzo-engine model server (OpenAI + Anthropic) running on this node")
f.StringVar(&opts.engineURL, "engine-url", defaultEngineURL, "local URL where hanzo-engine is probed (GET /v1/models)")
f.StringVar(&opts.engineEndpoint, "engine-endpoint", "", "public URL to advertise for gateway routing (defaults to --engine-url; a node behind NAT needs a reachable URL/tunnel)")
f.BoolVar(&opts.registerProvider, "register-provider", false, "auto-register the engine endpoint as an org model provider (POST /v1/ai/providers)")
f.StringVar(&opts.studioDir, "studio-dir", os.Getenv("HANZO_STUDIO_DIR"), "local Hanzo Studio checkout; when set, link launches and supervises the render backend on 127.0.0.1:8188")
f.StringVar(&opts.studioURL, "studio-url", firstNonEmpty(os.Getenv("HANZO_STUDIO_UPLOAD_URL"), defaultStudioUploadURL), "studio base URL the render mirror uploads finished images to (POST /v1/library/upload)")
f.BoolVar(&opts.mirror, "mirror", true, "sweep local renders into the org studio library; --mirror=false serves jobs only")
return cmd
}
func newUnlinkCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
return &cobra.Command{
Use: "unlink",
Short: "Take this machine out of the fleet (deregister + stop hanzod)",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
// Reverse of link, both best-effort: drop the compute-fleet row, then
// ALWAYS stop the fabric so a deregister error never leaves hanzod
// running. The deregister error is reported, not short-circuited.
derr := runDisconnect(cmd, envOf())
stopFabric(cmd)
return derr
},
}
}
func newStatusCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
return &cobra.Command{
Use: "status",
Short: "Show the org's fleet — every machine with each of its GPUs (this box highlighted)",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error { return runFleetStatus(cmd, envOf()) },
}
}
// ---------------------------------------------------------------------------
// Fabric — compose the canonical `hanzo node up` / `node stop`.
// ---------------------------------------------------------------------------
// fabricCLI resolves the Hanzo node CLI that owns hanzod supervision — the Rust
// fabric/dev CLI with `node up/stop`. In the canonical layout the Go unified binary
// takes the `hanzo` name and the Rust CLI is installed alongside it as `hanzo-node`,
// so `link` composes `node up` without shelling into itself (this binary has no
// `node`). Resolution order: HANZO_FABRIC_CLI, then `hanzo-node`, then a
// self-guarded `hanzo` (for boxes where the Rust CLI still holds the `hanzo` name).
// Returns "" when none is resolvable.
func fabricCLI() string {
if p := os.Getenv("HANZO_FABRIC_CLI"); p != "" {
return p
}
if p, err := exec.LookPath("hanzo-node"); err == nil {
return p
}
p, err := exec.LookPath("hanzo")
if err != nil {
return ""
}
if self, err := os.Executable(); err == nil {
if sp, _ := os.Readlink(p); sp == self || p == self {
return ""
}
}
return p
}
// Passthrough delegates a verb this binary does not own — node, dev, wallet,
// network, … — to the Rust fabric/dev CLI (resolved by fabricCLI, installed as
// `hanzo-node`), so the single `hanzo` name is a SUPERSET: Go verbs served natively,
// everything else handed through unchanged. `hanzo node up` (the fabric `link`
// itself composes) works for users too. It runs the delegate to completion with
// inherited stdio and exits with its code; it returns false only when no fabric CLI
// is resolvable, so the caller can report unknown-subcommand.
func Passthrough(args []string) bool {
bin := fabricCLI()
if bin == "" {
return false
}
c := exec.Command(bin, args...)
c.Stdin, c.Stdout, c.Stderr = os.Stdin, os.Stdout, os.Stderr
if err := c.Run(); err != nil {
var ee *exec.ExitError
if errors.As(err, &ee) {
os.Exit(ee.ExitCode())
}
fmt.Fprintf(os.Stderr, "hanzo: delegating %v to %s: %v\n", args, bin, err)
os.Exit(1)
}
os.Exit(0)
return true
}
// startFabric starts hanzod by invoking `hanzo node up` — the one canonical way to
// join the fabric. Best-effort by design: a missing CLI or a missing hanzod prints
// a clear note and the node still joins the compute fleet. `--no-fabric` skips it.
func startFabric(cmd *cobra.Command, skip bool) {
out := cmd.OutOrStdout()
if skip {
fmt.Fprintln(out, "fabric: skipped (--no-fabric); joining the compute fleet only")
return
}
bin := fabricCLI()
if bin == "" {
fmt.Fprintln(out, "fabric: hanzo node CLI not found — joining the compute fleet only")
fmt.Fprintln(out, " (install the `hanzo` node CLI or set HANZO_FABRIC_CLI to start hanzod)")
return
}
ctx, cancel := context.WithTimeout(cmd.Context(), 60*time.Second)
defer cancel()
c := exec.CommandContext(ctx, bin, "node", "up")
c.Stdout, c.Stderr = out, cmd.ErrOrStderr()
if err := c.Run(); err != nil {
fmt.Fprintf(out, "fabric: `%s node up` did not start hanzod (%v) — joining the compute fleet only\n", bin, err)
}
}
// stopFabric stops the hanzod this box started, via the canonical `hanzo node stop`.
// Best-effort — nothing to stop is not an error.
func stopFabric(cmd *cobra.Command) {
out := cmd.OutOrStdout()
bin := fabricCLI()
if bin == "" {
return
}
ctx, cancel := context.WithTimeout(cmd.Context(), 30*time.Second)
defer cancel()
c := exec.CommandContext(ctx, bin, "node", "stop")
c.Stdout, c.Stderr = out, cmd.ErrOrStderr()
_ = c.Run()
}
+58
View File
@@ -0,0 +1,58 @@
package cli
import (
"bytes"
"context"
"net/http"
"net/http/httptest"
"strings"
"testing"
"github.com/spf13/cobra"
)
// TestUnlinkIdempotent — a repeat `hanzo unlink` is a no-op. The deregister POST
// hitting an already-terminal (409) or absent (404) fleet row is the desired end
// state, so runDisconnect returns nil (not an error) and says so, letting `unlink`
// be run twice safely.
func TestUnlinkIdempotent(t *testing.T) {
for _, code := range []int{http.StatusConflict, http.StatusNotFound} {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
w.WriteHeader(code)
_, _ = w.Write([]byte(`{"error":"activity terminal"}`))
}))
t.Setenv("HANZO_TOKEN", "test-token") // ensureToken honors this; no login needed
var out bytes.Buffer
cmd := &cobra.Command{}
cmd.SetContext(context.Background())
cmd.SetOut(&out)
if err := runDisconnect(cmd, &Env{CloudURL: srv.URL}); err != nil {
t.Errorf("HTTP %d: runDisconnect should be idempotent (nil), got %v", code, err)
}
if !strings.Contains(out.String(), "already unlinked") {
t.Errorf("HTTP %d: want 'already unlinked' notice, got %q", code, out.String())
}
srv.Close()
}
}
// TestUnlinkDeregisterErrorSurfaces — a non-terminal deregister failure (e.g. 500)
// is a real error and must be returned, not swallowed as idempotent success.
func TestUnlinkDeregisterErrorSurfaces(t *testing.T) {
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, _ *http.Request) {
w.WriteHeader(http.StatusInternalServerError)
_, _ = w.Write([]byte(`{"error":"boom"}`))
}))
defer srv.Close()
t.Setenv("HANZO_TOKEN", "test-token")
cmd := &cobra.Command{}
cmd.SetContext(context.Background())
cmd.SetOut(&bytes.Buffer{})
if err := runDisconnect(cmd, &Env{CloudURL: srv.URL}); err == nil {
t.Fatal("a 500 deregister must surface an error, got nil")
}
}
+326
View File
@@ -0,0 +1,326 @@
package cli
import (
"bytes"
"context"
"encoding/json"
"fmt"
"io"
"net/http"
"net/url"
"strings"
"time"
)
// Platform is a thin client over the LIVE Hanzo Cloud control plane
// (platform.hanzo.ai / api.hanzo.ai → svc `cloud`, the Go binary). Every route it
// calls is served by that one binary and authorized off ONE IAM identity: after
// `hanzo login` the CLI sends the IAM access token as the bearer, and the cloud's
// identity middleware (SanitizeIdentity) validates the JWT and org-scopes the
// caller — no separate platform/service token. A purpose-minted machine token
// still works (flag > env > credential store > IAM login) for automation.
type Platform struct {
baseURL string
token string
http *http.Client
}
func newPlatform(baseURL, token string) *Platform {
return &Platform{
baseURL: strings.TrimRight(baseURL, "/"),
token: token,
http: &http.Client{Timeout: 60 * time.Second},
}
}
// apiError carries the HTTP status + server message for a failed call so
// commands can give precise diagnostics (e.g. 401 → token problem).
type apiError struct {
status int
message string
path string
}
func (e *apiError) Error() string {
msg := e.message
if msg == "" {
msg = http.StatusText(e.status)
}
hint := ""
if e.status == http.StatusUnauthorized || e.status == http.StatusForbidden {
hint = " (run `hanzo login` — your IAM identity authorizes the platform; admin ops need an org-admin or superadmin identity)"
}
return fmt.Sprintf("platform %s: HTTP %d: %s%s", e.path, e.status, msg, hint)
}
// do performs one JSON request with the given bearer token, decoding a 2xx body
// into out (when non-nil) and mapping a non-2xx into an *apiError.
func (p *Platform) do(ctx context.Context, method, path, token string, body, out any) error {
if token == "" {
return fmt.Errorf("not authenticated: run `hanzo login` (an IAM login now authorizes the platform; a --platform-token / HANZO_PLATFORM_TOKEN still works for machine automation)")
}
var rdr io.Reader
if body != nil {
b, err := json.Marshal(body)
if err != nil {
return err
}
rdr = bytes.NewReader(b)
}
req, err := http.NewRequestWithContext(ctx, method, p.baseURL+path, rdr)
if err != nil {
return err
}
req.Header.Set("Authorization", "Bearer "+token)
req.Header.Set("Accept", "application/json")
req.Header.Set("User-Agent", "hanzo-cli/"+Version)
if body != nil {
req.Header.Set("Content-Type", "application/json")
}
resp, err := p.http.Do(req)
if err != nil {
return err
}
defer resp.Body.Close()
raw, _ := io.ReadAll(io.LimitReader(resp.Body, 8<<20))
if resp.StatusCode/100 != 2 {
return &apiError{status: resp.StatusCode, message: serverMessage(raw), path: path}
}
if out != nil && len(raw) > 0 {
if err := json.Unmarshal(raw, out); err != nil {
return fmt.Errorf("platform %s: decode response: %w", path, err)
}
}
return nil
}
// serverMessage pulls the `{ "message": … }` / `{ "error": … }` field the cloud's
// errors use, falling back to the raw (truncated) body.
func serverMessage(raw []byte) string {
var e struct {
Message string `json:"message"`
Error string `json:"error"`
}
if json.Unmarshal(raw, &e) == nil {
if e.Message != "" {
return e.Message
}
if e.Error != "" {
return e.Error
}
}
s := strings.TrimSpace(string(raw))
if len(s) > 240 {
s = s[:240] + "…"
}
return s
}
// ---------------------------------------------------------------------------
// Apps board — GET /v1/paas/apps, GET /v1/paas/apps/{app}. The live Go cloud's
// fleet drift board (clients/paas): the operator App CRs across the platform
// namespaces, declared/running/latest tags + health + the drift verdict. It is
// org-confined server-side (a SuperAdmin sees the fleet; an OrgAdmin only its own
// org), so the CLI sends NO org filter — identity scopes the view.
// ---------------------------------------------------------------------------
// AppView mirrors clients/paas.AppView (the LIVE board DTO). Tags/health are plain
// strings ("" == unknown, rendered "-"); Drift is kept raw so --json is
// byte-faithful and the drift schema can evolve without a client bump.
type AppView struct {
ID string `json:"id"` // <org>/<app>/<env>, e.g. hanzoai/iam/main
Org string `json:"org"` // image namespace, e.g. hanzoai
App string `json:"app"`
Env string `json:"env"`
Repo string `json:"repo"`
Registry string `json:"registry"`
DeclaredTag string `json:"declaredTag"`
RunningTag string `json:"runningTag"`
LatestTag string `json:"latestTag"`
Health string `json:"health"`
Phase string `json:"phase"`
Cluster string `json:"cluster"`
Namespace string `json:"namespace"`
Endpoints []string `json:"endpoints"`
Drift json.RawMessage `json:"drift"`
}
// AppsList is the /v1/paas/apps envelope: ordered rows + a drift summary.
type AppsList struct {
Apps []AppView `json:"apps"`
Summary struct {
Total int `json:"total"`
ByDrift map[string]int `json:"byDrift"`
} `json:"summary"`
}
// AppsQuery are the optional /v1/paas/apps filters (server-honored). Env/Health/
// Drift narrow the board; there is deliberately no org filter — the board is
// confined to the caller's org by the validated identity, never a client value.
type AppsQuery struct {
Env string
Health string
Drift bool
}
func (p *Platform) Apps(ctx context.Context, q AppsQuery) (*AppsList, error) {
v := url.Values{}
if q.Env != "" {
v.Set("env", q.Env)
}
if q.Health != "" {
v.Set("health", q.Health)
}
if q.Drift {
v.Set("drift", "1")
}
path := "/v1/paas/apps"
if len(v) > 0 {
path += "?" + v.Encode()
}
out := &AppsList{}
return out, p.do(ctx, http.MethodGet, path, p.token, nil, out)
}
// App gets one app row by its <app> CR name (production by default; the server
// scans the caller's authorized namespaces main→test→dev).
func (p *Platform) App(ctx context.Context, app string) (*AppView, error) {
out := &AppView{}
return out, p.do(ctx, http.MethodGet, "/v1/paas/apps/"+url.PathEscape(app), p.token, nil, out)
}
// driftSeverity extracts the severity string from the raw drift object.
func driftSeverity(raw json.RawMessage) string {
var d struct {
Severity string `json:"severity"`
}
if json.Unmarshal(raw, &d) == nil && d.Severity != "" {
return d.Severity
}
return "-"
}
// ---------------------------------------------------------------------------
// Clusters — GET /v1/clusters. The live Go cloud's compute fleet (clients/visor):
// Visor-managed node pools + the org's BYO clusters, tenant-scoped server-side by
// the validated org (?owner is the caller's IAM org). No org in the path.
// ---------------------------------------------------------------------------
// NodePool mirrors clients/visor.nodePoolView.
type NodePool struct {
PoolID string `json:"poolId"`
Name string `json:"name"`
Size string `json:"size"`
Count int `json:"count"`
MinNodes int `json:"minNodes"`
MaxNodes int `json:"maxNodes"`
AutoScale bool `json:"autoScale"`
}
// Cluster mirrors clients/visor.clusterView — the LIVE cluster DTO. `kind` is
// "managed" (Visor-provisioned) or "byo" (attached kubeconfig).
type Cluster struct {
DoksClusterID string `json:"doksClusterId"`
DoClusterID string `json:"doClusterId"`
Name string `json:"name"`
Region string `json:"region"`
Status string `json:"status"`
NodePools []NodePool `json:"nodePools"`
NodeSize string `json:"nodeSize"`
NodeCount int `json:"nodeCount"`
CreatedAt string `json:"createdAt"`
Kind string `json:"kind"`
NvidiaGPU int `json:"nvidiaGpu"`
AmdGPU int `json:"amdGpu"`
}
// ID is the stable cluster identifier for display/lookup: the DOKS id when managed,
// else the name (a BYO cluster keys on its attached name).
func (c Cluster) ID() string {
if c.DoksClusterID != "" {
return c.DoksClusterID
}
return c.Name
}
func (p *Platform) Clusters(ctx context.Context) ([]Cluster, error) {
var out struct {
Clusters []Cluster `json:"clusters"`
}
err := p.do(ctx, http.MethodGet, "/v1/clusters", p.token, nil, &out)
return out.Clusters, err
}
// ---------------------------------------------------------------------------
// Deploy — POST /v1/paas/apps/{app}/deploy: a zero-downtime ROLLING RESTART of the
// app's Deployment (re-pulls the declared image, recreates pods). Org-confined
// server-side; an optional env selects the lifecycle namespace (main|test|dev).
// ---------------------------------------------------------------------------
// Redeploy triggers a rolling restart of the named app. env is optional
// (main|test|dev); empty targets production (the first match, main→test→dev).
func (p *Platform) Redeploy(ctx context.Context, app, env string) (*DeployResult, error) {
path := "/v1/paas/apps/" + url.PathEscape(app) + "/deploy"
if env != "" {
path += "?env=" + url.QueryEscape(env)
}
out := &DeployResult{}
if err := p.do(ctx, http.MethodPost, path, p.token, nil, out); err != nil {
return nil, err
}
if !out.OK {
return nil, fmt.Errorf("redeploy did not report ok")
}
return out, nil
}
// DeployResult is the /deploy acceptance (202): the restarted app + its namespace.
type DeployResult struct {
OK bool `json:"ok"`
App string `json:"app"`
Namespace string `json:"namespace"`
Env string `json:"env"`
RestartedAt string `json:"restartedAt"`
}
// ---------------------------------------------------------------------------
// Build — POST /v1/runner (platform-native CI, no GitHub builders). Authorized off
// the IAM login exactly like the surfaces above (or a dedicated build token for
// machine automation). Unchanged wire contract.
// ---------------------------------------------------------------------------
// BuildReq is the direct-enqueue body. Repo/SHA/Image are required.
type BuildReq struct {
Repo string `json:"repo"`
SHA string `json:"sha"`
Image string `json:"image"`
Branch string `json:"branch,omitempty"`
Ref string `json:"ref,omitempty"`
Dockerfile string `json:"dockerfile,omitempty"`
Context string `json:"context,omitempty"`
DockerTarget string `json:"dockerTarget,omitempty"`
OS string `json:"os,omitempty"`
Arch string `json:"arch,omitempty"`
OrganizationID string `json:"organizationId,omitempty"`
}
// BuildJob is the enqueue acceptance (HTTP 202).
type BuildJob struct {
BuildJobID string `json:"buildJobId"`
Status string `json:"status"`
RunnerPool string `json:"runnerPool"`
Image string `json:"image"`
Target string `json:"target"`
}
// EnqueueBuild enqueues a native build. buildToken is resolved by the caller (IAM
// login is the final fallback; a dedicated build token wins when present).
func (p *Platform) EnqueueBuild(ctx context.Context, req BuildReq, buildToken string) (*BuildJob, error) {
if buildToken == "" {
return nil, fmt.Errorf("not authenticated: run `hanzo login` (an IAM login now authorizes builds; HANZO_BUILD_TOKEN / --build-token still works for machine automation)")
}
out := &BuildJob{}
return out, p.do(ctx, http.MethodPost, "/v1/runner", buildToken, req, out)
}
+176
View File
@@ -0,0 +1,176 @@
package cli
import (
"context"
"encoding/json"
"io"
"net/http"
"net/http/httptest"
"strings"
"testing"
)
// platformStub spins an httptest server whose handler is provided by the test,
// plus a client pointed at it with the given token.
func platformStub(t *testing.T, token string, h http.HandlerFunc) (*Platform, func()) {
t.Helper()
srv := httptest.NewServer(h)
return newPlatform(srv.URL, token), srv.Close
}
// Apps hits the LIVE board /v1/paas/apps with the IAM bearer; it sends NO org
// filter (the board is org-confined server-side by the validated identity).
func TestPlatformAuthHeaderAndApps(t *testing.T) {
p, done := platformStub(t, "svc-tok", func(w http.ResponseWriter, r *http.Request) {
if got := r.Header.Get("Authorization"); got != "Bearer svc-tok" {
t.Errorf("auth header = %q", got)
}
if r.URL.Path != "/v1/paas/apps" {
t.Errorf("path = %s, want /v1/paas/apps", r.URL.Path)
}
if r.URL.Query().Get("env") != "main" || r.URL.Query().Get("drift") != "1" {
t.Errorf("query = %s", r.URL.RawQuery)
}
if r.URL.Query().Has("org") {
t.Errorf("client must NOT send an org filter (identity confines the board): %s", r.URL.RawQuery)
}
_ = json.NewEncoder(w).Encode(AppsList{
Apps: []AppView{{ID: "hanzoai/iam/main", Org: "hanzoai", App: "iam", Env: "main", Drift: json.RawMessage(`{"severity":"red"}`)}},
})
})
defer done()
res, err := p.Apps(context.Background(), AppsQuery{Env: "main", Drift: true})
if err != nil {
t.Fatalf("Apps: %v", err)
}
if len(res.Apps) != 1 || res.Apps[0].App != "iam" {
t.Fatalf("apps wrong: %+v", res.Apps)
}
if driftSeverity(res.Apps[0].Drift) != "red" {
t.Fatalf("drift severity = %q", driftSeverity(res.Apps[0].Drift))
}
}
// App hits /v1/paas/apps/{app}; no org query (identity scopes it).
func TestPlatformApp(t *testing.T) {
p, done := platformStub(t, "t", func(w http.ResponseWriter, r *http.Request) {
if r.URL.Path != "/v1/paas/apps/iam" {
t.Errorf("path = %s, want /v1/paas/apps/iam", r.URL.Path)
}
if r.URL.RawQuery != "" {
t.Errorf("app get must carry no query, got %s", r.URL.RawQuery)
}
_ = json.NewEncoder(w).Encode(AppView{ID: "hanzoai/iam/main", App: "iam", Phase: "Running"})
})
defer done()
a, err := p.App(context.Background(), "iam")
if err != nil || a.App != "iam" {
t.Fatalf("App: %v %+v", err, a)
}
}
// Clusters hits the LIVE /v1/clusters (org from identity, not the path).
func TestPlatformClusters(t *testing.T) {
p, done := platformStub(t, "t", func(w http.ResponseWriter, r *http.Request) {
if r.Method != http.MethodGet || r.URL.Path != "/v1/clusters" {
t.Errorf("clusters = %s %s, want GET /v1/clusters", r.Method, r.URL.Path)
}
_ = json.NewEncoder(w).Encode(map[string]any{"clusters": []Cluster{
{DoksClusterID: "c1", Name: "hanzo-acme", Region: "sfo3", Status: "running", Kind: "managed", NodeCount: 3},
}})
})
defer done()
cs, err := p.Clusters(context.Background())
if err != nil || len(cs) != 1 || cs[0].ID() != "c1" || cs[0].Kind != "managed" {
t.Fatalf("Clusters: %v %+v", err, cs)
}
}
// A BYO cluster with no DOKS id keys on its name via ID().
func TestClusterIDFallsBackToName(t *testing.T) {
c := Cluster{Name: "byo-1", Kind: "byo"}
if c.ID() != "byo-1" {
t.Fatalf("ID() = %q, want byo-1", c.ID())
}
}
// Redeploy hits /v1/paas/apps/{app}/deploy (rolling restart), org from identity.
func TestPlatformRedeploy(t *testing.T) {
p, done := platformStub(t, "t", func(w http.ResponseWriter, r *http.Request) {
if r.Method != http.MethodPost || r.URL.Path != "/v1/paas/apps/app-x/deploy" {
t.Errorf("redeploy = %s %s, want POST /v1/paas/apps/app-x/deploy", r.Method, r.URL.Path)
}
if r.URL.Query().Get("env") != "test" {
t.Errorf("env query = %s", r.URL.RawQuery)
}
w.WriteHeader(202)
_ = json.NewEncoder(w).Encode(DeployResult{OK: true, App: "app-x", Namespace: "hanzo-testnet", Env: "test", RestartedAt: "2026-07-18T00:00:00Z"})
})
defer done()
res, err := p.Redeploy(context.Background(), "app-x", "test")
if err != nil || res.Namespace != "hanzo-testnet" {
t.Fatalf("Redeploy: %v %+v", err, res)
}
}
func TestPlatformRedeployNotOK(t *testing.T) {
p, done := platformStub(t, "t", func(w http.ResponseWriter, _ *http.Request) {
_ = json.NewEncoder(w).Encode(DeployResult{OK: false})
})
defer done()
if _, err := p.Redeploy(context.Background(), "c", ""); err == nil {
t.Fatalf("expected error when ok=false")
}
}
func TestPlatformEnqueueBuild(t *testing.T) {
p, done := platformStub(t, "svc-tok", func(w http.ResponseWriter, r *http.Request) {
// The build endpoint must use the BUILD token, not the service token.
if got := r.Header.Get("Authorization"); got != "Bearer build-tok" {
t.Errorf("build auth header = %q (must use build token)", got)
}
if r.URL.Path != "/v1/runner" {
t.Errorf("path = %s", r.URL.Path)
}
body, _ := io.ReadAll(r.Body)
var req BuildReq
_ = json.Unmarshal(body, &req)
if req.Repo != "hanzoai/pricing" || req.SHA != "abc123" || req.Image == "" {
t.Errorf("build body = %+v", req)
}
w.WriteHeader(202)
_ = json.NewEncoder(w).Encode(BuildJob{BuildJobID: "bj-1", Status: "queued", RunnerPool: "runner-pool-32g", Image: req.Image})
})
defer done()
job, err := p.EnqueueBuild(context.Background(), BuildReq{Repo: "hanzoai/pricing", SHA: "abc123", Image: "ghcr.io/hanzoai/pricing:t"}, "build-tok")
if err != nil || job.BuildJobID != "bj-1" {
t.Fatalf("EnqueueBuild: %v %+v", err, job)
}
if _, err := p.EnqueueBuild(context.Background(), BuildReq{Repo: "r", SHA: "s", Image: "i"}, ""); err == nil {
t.Fatalf("expected error with empty build token")
}
}
func TestPlatformError401Hint(t *testing.T) {
p, done := platformStub(t, "bad", func(w http.ResponseWriter, _ *http.Request) {
w.WriteHeader(401)
_ = json.NewEncoder(w).Encode(map[string]string{"message": "Unauthorized"})
})
defer done()
_, err := p.Apps(context.Background(), AppsQuery{})
if err == nil || !strings.Contains(err.Error(), "HTTP 401") || !strings.Contains(err.Error(), "hanzo login") {
t.Fatalf("401 error should point at `hanzo login`, got %v", err)
}
}
func TestPlatformNoTokenError(t *testing.T) {
p := newPlatform("https://platform.hanzo.ai", "")
// After unify-infra, the "no credential" error points at `hanzo login` — the one
// identity that authorizes the platform — not a separate platform token.
if _, err := p.Apps(context.Background(), AppsQuery{}); err == nil || !strings.Contains(err.Error(), "hanzo login") {
t.Fatalf("expected a `hanzo login` hint, got %v", err)
}
}
+24
View File
@@ -0,0 +1,24 @@
package cli
import "os"
// realStdout is the process's true stdout, captured at this package's init
// before the server-graph dependencies (iam/beego, kms) run their own init()
// functions — several of which emit warnings to stdout (e.g. the IAM registry
// signing-key loader). To keep the CLI's stdout machine-readable (so
// `hanzo apps list -o json | jq` is never corrupted by a dependency's startup
// chatter), this init redirects stdout to stderr for the duration of process
// initialization; RestoreStdout puts the real stdout back before any command
// writes a byte.
//
// This is best-effort: it only helps when this package initializes before the
// noisy dependency (cmd/hanzo imports cli first) AND that dependency reads the
// os.Stdout variable at log time rather than capturing it earlier. main always
// calls RestoreStdout, so correctness never depends on the redirect taking.
var realStdout = os.Stdout
func init() { os.Stdout = os.Stderr }
// RestoreStdout restores the real process stdout. cmd/hanzo calls this as its
// first statement so every command writes to the genuine stdout.
func RestoreStdout() { os.Stdout = realStdout }
+185
View File
@@ -0,0 +1,185 @@
package cli
// run.go — `hanzo run`: launch a workload on Hanzo compute through one verb.
//
// A "run" is a workload value = {artifact, shape}, dispatched by kind onto the
// one API host (api.hanzo.ai/v1) and the one binary (cloud):
//
// hanzo run <image> → POST /v1/run container service (autoscaled)
// hanzo run fn <src> → POST /v1/fn source function (scale-to-zero)
//
// `run` launches YOUR artifact (container/source/site) on Hanzo compute. Invoking
// a managed agent with a task is a peer verb, `hanzo agent` (see agent.go), not a
// run kind. It is a THIN client: kind-dispatch + one authenticated HTTP call each,
// over the IAM access token and env.CloudURL, exactly like the fleet worker
// (gpu.go) — it invents no parallel API. See docs/architecture/compute-ladder.md.
import (
"bytes"
"context"
"encoding/json"
"fmt"
"io"
"net/http"
"strings"
"github.com/spf13/cobra"
)
// cloudCall performs one authenticated JSON request against env.CloudURL
// (api.hanzo.ai), decoding a 2xx body into out. It is the api.hanzo.ai analog of
// Platform.do (which targets platform.hanzo.ai); the two converge as the platform
// control plane folds into cloud. Mirrors the fleet worker's call idiom.
func cloudCall(ctx context.Context, env *Env, method, path string, body, out any) error {
tok, err := env.ensureToken(ctx)
if err != nil {
return err
}
var rdr io.Reader
if body != nil {
b, err := json.Marshal(body)
if err != nil {
return err
}
rdr = bytes.NewReader(b)
}
req, err := http.NewRequestWithContext(ctx, method, env.CloudURL+path, rdr)
if err != nil {
return err
}
req.Header.Set("Authorization", "Bearer "+tok)
req.Header.Set("Accept", "application/json")
req.Header.Set("User-Agent", "hanzo-cli/"+Version)
if body != nil {
req.Header.Set("Content-Type", "application/json")
}
resp, err := (&http.Client{}).Do(req)
if err != nil {
return err
}
defer resp.Body.Close()
raw, _ := io.ReadAll(io.LimitReader(resp.Body, 8<<20))
if resp.StatusCode/100 != 2 {
return fmt.Errorf("cloud %s %s: HTTP %d: %s", method, path, resp.StatusCode, serverMessage(raw))
}
if out != nil && len(raw) > 0 {
if err := json.Unmarshal(raw, out); err != nil {
return fmt.Errorf("cloud %s: decode response: %w", path, err)
}
}
return nil
}
// RunSpec is the POST /v1/run (container) / /v1/fn (source) body. Shape selects
// the execution model: "service" (autoscaled, long-lived), "function"
// (per-request, scale-to-zero), or "task" (run-to-completion).
type RunSpec struct {
Name string `json:"name,omitempty"`
Image string `json:"image,omitempty"` // container artifact (run)
Source string `json:"source,omitempty"` // source ref/path (fn)
Runtime string `json:"runtime,omitempty"`
Port int `json:"port,omitempty"`
Shape string `json:"shape"` // service | function | task
Min int `json:"minScale"`
Max int `json:"maxScale"`
GPU bool `json:"gpu,omitempty"`
Env map[string]string `json:"env,omitempty"`
}
// RunResult is the enqueue/creation acceptance.
type RunResult struct {
ID string `json:"id"`
Name string `json:"name"`
URL string `json:"url"`
Status string `json:"status"`
Shape string `json:"shape"`
}
func newRunCmd(envOf func() *Env, _ *globalFlags) *cobra.Command {
cmd := &cobra.Command{
Use: "run",
Short: "Launch a workload on Hanzo compute (container, function, or agent task)",
Long: "One verb, dispatched by kind, all on api.hanzo.ai/v1 — k8s is abstracted away:\n" +
" hanzo run <image> a container service (autoscaled)\n" +
" hanzo run fn <src> a source function (scale-to-zero)\n" +
"To invoke a managed agent use `hanzo agent`; a computer-using one, `hanzo bot`.\n" +
"For a declared, long-running or stateful service use `hanzo deploy`; for raw\n" +
"cluster access use `hanzo k8s`.",
}
cmd.AddCommand(newRunContainerCmd(envOf), newRunFnCmd(envOf))
return cmd
}
// newRunContainerCmd is `hanzo run <image>` (default) AND `hanzo run container <image>`.
func newRunContainerCmd(envOf func() *Env) *cobra.Command {
var spec RunSpec
var envKV []string
c := &cobra.Command{
Use: "container <image>",
Short: "Run a container as an autoscaled service (POST /v1/run)",
Args: cobra.ExactArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
env := envOf()
spec.Image = args[0]
spec.Shape = firstNonEmpty(spec.Shape, "service")
spec.Env = parseEnvKV(envKV)
out := &RunResult{}
if err := cloudCall(cmd.Context(), env, http.MethodPost, "/v1/run", &spec, out); err != nil {
return err
}
return env.emit(out, func(w io.Writer) {
fmt.Fprintf(w, "%s\t%s\t%s\n", out.Name, out.Status, out.URL)
})
},
}
c.Flags().StringVar(&spec.Name, "name", "", "workload name (default: derived from image)")
c.Flags().IntVar(&spec.Port, "port", 8080, "container port to route traffic to")
c.Flags().StringVar(&spec.Shape, "shape", "service", "service | task (run-to-completion)")
c.Flags().IntVar(&spec.Min, "min", 0, "min replicas (0 = scale-to-zero when supported)")
c.Flags().IntVar(&spec.Max, "max", 20, "max replicas (autoscale ceiling)")
c.Flags().BoolVar(&spec.GPU, "gpu", false, "schedule on a GPU node")
c.Flags().StringArrayVarP(&envKV, "env", "e", nil, "environment variable KEY=VALUE (repeatable)")
return c
}
func newRunFnCmd(envOf func() *Env) *cobra.Command {
var spec RunSpec
var envKV []string
c := &cobra.Command{
Use: "fn <source>",
Short: "Run a source function, scale-to-zero (POST /v1/functions)",
Args: cobra.ExactArgs(1),
RunE: func(cmd *cobra.Command, args []string) error {
env := envOf()
spec.Source = args[0]
spec.Shape = "function"
spec.Env = parseEnvKV(envKV)
out := &RunResult{}
if err := cloudCall(cmd.Context(), env, http.MethodPost, "/v1/functions", &spec, out); err != nil {
return err
}
return env.emit(out, func(w io.Writer) {
fmt.Fprintf(w, "%s\t%s\t%s\n", out.Name, out.Status, out.URL)
})
},
}
c.Flags().StringVar(&spec.Name, "name", "", "function name")
c.Flags().StringVar(&spec.Runtime, "runtime", "", "runtime env (e.g. python312, node20, rust)")
c.Flags().BoolVar(&spec.GPU, "gpu", false, "use a GPU function environment")
c.Flags().StringArrayVarP(&envKV, "env", "e", nil, "environment variable KEY=VALUE (repeatable)")
return c
}
// parseEnvKV turns []{"K=V"} into a map, ignoring malformed entries.
func parseEnvKV(kv []string) map[string]string {
if len(kv) == 0 {
return nil
}
m := make(map[string]string, len(kv))
for _, e := range kv {
if i := strings.IndexByte(e, '='); i > 0 {
m[e[:i]] = e[i+1:]
}
}
return m
}
+43
View File
@@ -0,0 +1,43 @@
package cli
// runner.go — `hanzo runner`: turn THIS machine into a JIT CI runner for your
// org's GitHub Actions. The host role of the arc daemon, migrated from
// arc-runner/arc (cmd/arcd) into cloud/runner: a GitHub App polls each configured
// org for queued workflow jobs and spawns ephemeral, auto-exiting actions-runner
// subprocesses tagged with this box's labels (GPU / vulkan aware). Outbound only —
// nothing listens for inbound. Completes the trifecta: `engine` serves models,
// `link` shares compute, `runner` claims CI — one binary, one org login.
import (
"os/signal"
"syscall"
"github.com/hanzoai/cloud/runner"
"github.com/spf13/cobra"
)
func newRunnerCmd(_ func() *Env, _ *globalFlags) *cobra.Command {
runner.Version = Version // propagate the cloud build version into the daemon
var configPath string
cmd := &cobra.Command{
Use: "runner",
Short: "Run this machine as a JIT CI runner for your org (GitHub Actions)",
Long: "Turn this box into an ephemeral, GPU-aware GitHub Actions runner for your\n" +
"org(s). A GitHub App polls for queued jobs and spawns auto-exiting runner\n" +
"subprocesses labelled with this machine's tags. Outbound-only; nothing\n" +
"listens for inbound. Config defaults to ~/.arcd/config.yaml (app_id, orgs,\n" +
"labels, runner_dir).",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
cfg, err := runner.LoadConfig(configPath)
if err != nil {
return err
}
ctx, stop := signal.NotifyContext(cmd.Context(), syscall.SIGINT, syscall.SIGTERM)
defer stop()
return runner.RunHost(ctx, cfg)
},
}
cmd.Flags().StringVar(&configPath, "config", "", "runner config.yaml (default: ~/.arcd/config.yaml)")
return cmd
}
+259
View File
@@ -0,0 +1,259 @@
package cli
import (
"fmt"
"io"
"os"
"path/filepath"
"sort"
"strings"
"github.com/hanzoai/cloud/clients/security/detect"
"github.com/spf13/cobra"
)
// `hanzo security scan` is the LOCAL guardrail-at-generation: it walks a path,
// runs the SAME detect engine the /v1/security server surface uses (one engine,
// two surfaces — see clients/security/detect), and exits non-zero when a finding
// at or above the fail threshold is present. No server, no auth, no network — so
// it drops straight into a pre-commit hook, a CI step, or an agent's shell the
// moment code is written. It never prints a raw secret: findings carry the
// engine's masked preview only.
// skipDirs are never descended into — vendored / generated / VCS trees that
// would drown real findings in noise (and, for node_modules, minified blobs
// that trip entropy heuristics).
var skipDirs = map[string]bool{
".git": true, "node_modules": true, "vendor": true, "dist": true,
"build": true, "out": true, ".vscode-test": true, "target": true,
".next": true, "__pycache__": true, ".venv": true, "venv": true,
}
// maxScanFileBytes caps a single file read; a source file over this is almost
// certainly a data/blob artifact, not code a human wrote a secret into.
const maxScanFileBytes = 2 << 20 // 2 MiB
func newSecurityCmd(envOf func() *Env) *cobra.Command {
cmd := &cobra.Command{
Use: "security",
Short: "Code-security tools (local secret scanning)",
// No PersistentPreRunE override: the root's runs, resolving config/creds
// into env so envOf() (used for -o json) is non-nil. It is local-only —
// scan requires no login or network.
}
var failOn string
scan := &cobra.Command{
Use: "scan [path ...]",
Short: "Scan files/directories for hardcoded secrets (default: current dir)",
Long: "Walk each path and report hardcoded secrets using the native Hanzo\n" +
"detection engine (the same one behind /v1/security). Exits non-zero when a\n" +
"finding at or above --fail-on is present, so it gates a pre-commit hook or CI\n" +
"step. Secrets are never printed — only a masked preview.",
// We print our own findings + a clean "N secrets" error; no cobra usage
// dump on a policy failure.
SilenceUsage: true,
SilenceErrors: true,
RunE: func(cmd *cobra.Command, args []string) error {
paths := args
if len(paths) == 0 {
paths = []string{"."}
}
floor := strings.ToLower(strings.TrimSpace(failOn))
if floor == "" {
floor = "low"
}
if floor != "none" && detect.SeverityRank(floor) == 0 {
return fmt.Errorf("invalid --fail-on %q (want critical|high|medium|low|none)", failOn)
}
findings, scanned, err := scanPaths(paths)
if err != nil {
return err
}
e := envOf()
result := scanResult{
FilesScanned: scanned,
Findings: findings,
Summary: tally(findings),
}
if err := e.emit(result, func(w io.Writer) { renderScan(w, result) }); err != nil {
return err
}
// Policy gate: fail when any finding is at/above the floor.
if floor != "none" {
bad := 0
for _, f := range findings {
if detect.SeverityRank(f.Severity) >= detect.SeverityRank(floor) {
bad++
}
}
if bad > 0 {
return fmt.Errorf("%d secret(s) at or above %q severity", bad, floor)
}
}
return nil
},
}
scan.Flags().StringVar(&failOn, "fail-on", "low",
"minimum severity that fails the command: critical|high|medium|low|none")
rules := &cobra.Command{
Use: "rules",
Short: "List the detection rules the scanner applies",
Args: cobra.NoArgs,
RunE: func(cmd *cobra.Command, _ []string) error {
e := envOf()
rv := detect.Rules()
return e.emit(rv, func(w io.Writer) {
tw := newTab(w)
fmt.Fprintln(tw, "SEVERITY\tID\tNAME")
for _, r := range rv {
fmt.Fprintf(tw, "%s\t%s\t%s\n", r.Severity, r.ID, r.Name)
}
tw.Flush()
fmt.Fprintf(w, "\n%d rules\n", len(rv))
})
},
}
cmd.AddCommand(scan, rules)
return cmd
}
// scanFinding is a CLI finding: the engine finding with the file path it was
// found in (the engine echoes the path it was handed, which is what we want).
type scanResult struct {
FilesScanned int `json:"filesScanned"`
Findings []detect.Finding `json:"findings"`
Summary scanSummary `json:"summary"`
}
type scanSummary struct {
Total int `json:"total"`
Critical int `json:"critical"`
High int `json:"high"`
Medium int `json:"medium"`
Low int `json:"low"`
}
func tally(fs []detect.Finding) scanSummary {
var s scanSummary
for _, f := range fs {
s.Total++
switch f.Severity {
case detect.SeverityCritical:
s.Critical++
case detect.SeverityHigh:
s.High++
case detect.SeverityMedium:
s.Medium++
case detect.SeverityLow:
s.Low++
}
}
return s
}
// scanPaths walks each path and runs the engine over every readable text file,
// returning findings sorted worst-first (by severity, then path, then line).
func scanPaths(paths []string) ([]detect.Finding, int, error) {
var findings []detect.Finding
scanned := 0
for _, root := range paths {
info, err := os.Stat(root)
if err != nil {
return nil, 0, fmt.Errorf("stat %q: %w", root, err)
}
if !info.IsDir() {
fs, ok := scanOneFile(root)
if ok {
scanned++
findings = append(findings, fs...)
}
continue
}
walkErr := filepath.WalkDir(root, func(p string, d os.DirEntry, err error) error {
if err != nil {
return nil // unreadable entry — skip, don't abort the whole walk
}
if d.IsDir() {
if skipDirs[d.Name()] {
return filepath.SkipDir
}
return nil
}
if fs, ok := scanOneFile(p); ok {
scanned++
findings = append(findings, fs...)
}
return nil
})
if walkErr != nil {
return nil, 0, fmt.Errorf("walk %q: %w", root, walkErr)
}
}
sort.SliceStable(findings, func(i, j int) bool {
a, b := findings[i], findings[j]
if ra, rb := detect.SeverityRank(a.Severity), detect.SeverityRank(b.Severity); ra != rb {
return ra > rb
}
if a.Path != b.Path {
return a.Path < b.Path
}
return a.Line < b.Line
})
return findings, scanned, nil
}
// scanOneFile reads a file (bounded, text-only) and runs the engine. Returns
// ok=false for a file that was skipped (too big, binary, unreadable) so it is
// not counted as scanned.
func scanOneFile(path string) ([]detect.Finding, bool) {
info, err := os.Stat(path)
if err != nil || info.Size() > maxScanFileBytes {
return nil, false
}
b, err := os.ReadFile(path)
if err != nil {
return nil, false
}
if isBinary(b) {
return nil, false
}
return detect.ScanContent(path, string(b)), true
}
// isBinary reports whether b looks like a non-text blob — a NUL byte in the
// first 8 KiB is the same heuristic git uses. Skipping binaries avoids both
// false positives and wasted work on assets.
func isBinary(b []byte) bool {
n := len(b)
if n > 8192 {
n = 8192
}
for i := 0; i < n; i++ {
if b[i] == 0 {
return true
}
}
return false
}
func renderScan(w io.Writer, r scanResult) {
if len(r.Findings) == 0 {
fmt.Fprintf(w, "✓ no secrets found (%d files scanned)\n", r.FilesScanned)
return
}
tw := newTab(w)
fmt.Fprintln(tw, "SEVERITY\tRULE\tLOCATION\tPREVIEW")
for _, f := range r.Findings {
fmt.Fprintf(tw, "%s\t%s\t%s:%d\t%s\n", f.Severity, f.RuleID, f.Path, f.Line, f.Preview)
}
tw.Flush()
fmt.Fprintf(w, "\n%d finding(s) in %d files (critical=%d high=%d medium=%d low=%d)\n",
r.Summary.Total, r.FilesScanned, r.Summary.Critical, r.Summary.High,
r.Summary.Medium, r.Summary.Low)
}
+176
View File
@@ -0,0 +1,176 @@
package cli
import (
"bytes"
"encoding/json"
"os"
"path/filepath"
"strings"
"testing"
)
// runSecurity executes `security <args>` through the real root command with an
// isolated $HOME, capturing stdout. Returns output + the Execute error (the
// non-zero-exit signal).
func runSecurity(t *testing.T, args ...string) (string, error) {
t.Helper()
sandbox(t)
root := newRootCmd()
var out bytes.Buffer
root.SetOut(&out)
root.SetErr(&out)
root.SetArgs(append([]string{"security"}, args...))
err := root.Execute()
return out.String(), err
}
// TestSecurityScanFindsAndFails proves scan detects a planted secret, exits
// non-zero at the default fail threshold, and never prints the raw secret.
func TestSecurityScanFindsAndFails(t *testing.T) {
dir := t.TempDir()
secret := "AKIAIOSFODNN7EXAMPLE"
must(t, os.WriteFile(filepath.Join(dir, "config.py"),
[]byte("aws_key = \""+secret+"\"\nok = 1\n"), 0o644))
// a clean file that must NOT trip anything
must(t, os.WriteFile(filepath.Join(dir, "clean.go"),
[]byte("package main\nfunc main() {}\n"), 0o644))
out, err := runSecurity(t, "scan", dir)
if err == nil {
t.Fatalf("expected non-zero exit on a found secret; out:\n%s", out)
}
if !strings.Contains(err.Error(), "at or above") {
t.Fatalf("unexpected error: %v", err)
}
if strings.Contains(out, secret) {
t.Fatalf("output leaked the raw secret:\n%s", out)
}
if !strings.Contains(out, "aws-access-key-id") {
t.Fatalf("expected the aws rule id in output:\n%s", out)
}
}
// TestSecurityScanCleanPasses proves a clean tree exits zero with the ok line.
func TestSecurityScanCleanPasses(t *testing.T) {
dir := t.TempDir()
must(t, os.WriteFile(filepath.Join(dir, "app.go"),
[]byte("package main\nfunc main() { println(\"hi\") }\n"), 0o644))
out, err := runSecurity(t, "scan", dir)
if err != nil {
t.Fatalf("clean tree should exit zero, got %v\n%s", err, out)
}
if !strings.Contains(out, "no secrets found") {
t.Fatalf("expected the clean message:\n%s", out)
}
}
// TestSecurityScanFailOnNone proves --fail-on=none reports findings but exits
// zero (report-only mode).
func TestSecurityScanFailOnNone(t *testing.T) {
dir := t.TempDir()
must(t, os.WriteFile(filepath.Join(dir, "s.py"),
[]byte(`k = "AKIAIOSFODNN7EXAMPLE"`), 0o644))
out, err := runSecurity(t, "scan", "--fail-on", "none", dir)
if err != nil {
t.Fatalf("--fail-on=none should exit zero, got %v\n%s", err, out)
}
if !strings.Contains(out, "aws-access-key-id") {
t.Fatalf("report-only should still list the finding:\n%s", out)
}
}
// TestSecurityScanFailOnThreshold proves a medium finding does NOT fail when
// --fail-on=critical, but a critical one does.
func TestSecurityScanFailOnThreshold(t *testing.T) {
dir := t.TempDir()
// a jwt is medium severity
must(t, os.WriteFile(filepath.Join(dir, "t.txt"),
[]byte("tok = eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJhYmMifQ.SGVsbG9TaWduYXR1cmU\n"), 0o644))
if out, err := runSecurity(t, "scan", "--fail-on", "critical", dir); err != nil {
t.Fatalf("medium finding must not fail at --fail-on=critical, got %v\n%s", err, out)
}
// now add a critical
must(t, os.WriteFile(filepath.Join(dir, "k.py"),
[]byte(`k = "AKIAIOSFODNN7EXAMPLE"`), 0o644))
if _, err := runSecurity(t, "scan", "--fail-on", "critical", dir); err == nil {
t.Fatal("a critical finding must fail at --fail-on=critical")
}
}
// TestSecurityScanJSON proves -o json emits a machine-readable result with the
// summary and no raw secret.
func TestSecurityScanJSON(t *testing.T) {
dir := t.TempDir()
secret := "AKIAIOSFODNN7EXAMPLE"
must(t, os.WriteFile(filepath.Join(dir, "s.py"), []byte(`k = "`+secret+`"`), 0o644))
out, _ := runSecurity(t, "scan", "-o", "json", "--fail-on", "none", dir)
var res scanResult
if err := json.Unmarshal([]byte(out), &res); err != nil {
t.Fatalf("json parse: %v\n%s", err, out)
}
if res.Summary.Critical < 1 || res.Summary.Total < 1 {
t.Fatalf("summary missing the critical: %+v", res.Summary)
}
if strings.Contains(out, secret) {
t.Fatalf("json leaked the secret:\n%s", out)
}
}
// TestSecurityScanSkipsVendorAndBinary proves the walker skips skipDirs and
// binary files (a secret inside node_modules or a NUL-laden blob is ignored).
func TestSecurityScanSkipsVendorAndBinary(t *testing.T) {
dir := t.TempDir()
nm := filepath.Join(dir, "node_modules")
must(t, os.MkdirAll(nm, 0o755))
must(t, os.WriteFile(filepath.Join(nm, "dep.js"),
[]byte(`k = "AKIAIOSFODNN7EXAMPLE"`), 0o644))
must(t, os.WriteFile(filepath.Join(dir, "blob.bin"),
append([]byte{0, 1, 2}, []byte(`AKIAIOSFODNN7EXAMPLE`)...), 0o644))
out, err := runSecurity(t, "scan", dir)
if err != nil {
t.Fatalf("vendored + binary secrets should be skipped → clean exit, got %v\n%s", err, out)
}
if !strings.Contains(out, "no secrets found") {
t.Fatalf("expected clean (skipped) result:\n%s", out)
}
}
// TestSecurityScanBadFailOn proves an invalid --fail-on is a clean error.
func TestSecurityScanBadFailOn(t *testing.T) {
dir := t.TempDir()
_, err := runSecurity(t, "scan", "--fail-on", "nope", dir)
if err == nil || !strings.Contains(err.Error(), "invalid --fail-on") {
t.Fatalf("want invalid --fail-on error, got %v", err)
}
}
// TestSecurityRules proves the rules subcommand lists the catalog.
func TestSecurityRules(t *testing.T) {
out, err := runSecurity(t, "rules")
if err != nil {
t.Fatalf("rules failed: %v", err)
}
if !strings.Contains(out, "aws-access-key-id") || !strings.Contains(out, "rules") {
t.Fatalf("rules output missing content:\n%s", out)
}
}
// TestSecurityIsControlVerb proves `security` routes to the CLI, not the server
// dispatcher.
func TestSecurityIsControlVerb(t *testing.T) {
if !IsControlVerb("security") {
t.Fatal("security must be a control verb")
}
}
func must(t *testing.T, err error) {
t.Helper()
if err != nil {
t.Fatal(err)
}
}
+239
View File
@@ -0,0 +1,239 @@
// studio.go — local Hanzo Studio render-backend supervision for `hanzo link
// --studio-dir <checkout>`. The gpu-jobs claim loop renders on the
// LOCAL studio server (127.0.0.1:8188); this keeps that server alive so the
// box needs no separate watchdog script or hand-rolled systemd unit — the
// hanzo CLI is the one way a BYO box joins the fleet, render backend included.
//
// Semantics (ported from the GB10 watchdog it replaces): health-probe
// /system_stats; on failure, one grace re-check, then free the port (a stale
// main.py holding :8188 makes the new one crash on EADDRINUSE) and relaunch
// from the checkout's venv. Emits a line only on restart events.
package cli
import (
"context"
"encoding/json"
"fmt"
"io"
"net"
"net/http"
"os"
"os/exec"
"path/filepath"
"strconv"
"sync/atomic"
"syscall"
"time"
)
const (
studioAddr = "127.0.0.1:8188"
studioHealthURL = "http://" + studioAddr + "/system_stats"
studioProbeEvery = 45 * time.Second
studioGraceWait = 8 * time.Second
studioStartWindow = 180 * time.Second
)
func studioHealthy(ctx context.Context) bool {
ctx, cancel := context.WithTimeout(ctx, 5*time.Second)
defer cancel()
req, err := http.NewRequestWithContext(ctx, http.MethodGet, studioHealthURL, nil)
if err != nil {
return false
}
resp, err := http.DefaultClient.Do(req)
if err != nil {
return false
}
resp.Body.Close()
return resp.StatusCode == http.StatusOK
}
// studioPython picks the checkout's venv interpreter, falling back to python3.
func studioPython(dir string) string {
venv := filepath.Join(dir, ".venv", "bin", "python")
if _, err := os.Stat(venv); err == nil {
return venv
}
return "python3"
}
// launchStudio starts the render backend from dir, logging to
// <dir>/studio-local.log. The process gets its own group so a restart can
// kill stragglers (torch dataloader workers and the like) in one signal.
func launchStudio(dir string) (*exec.Cmd, error) {
logf, err := os.OpenFile(filepath.Join(dir, "studio-local.log"),
os.O_CREATE|os.O_WRONLY|os.O_APPEND, 0o644)
if err != nil {
return nil, err
}
// --listen 127.0.0.1 (loopback only) + --worker-mode: the render backend serves
// the fleet worker on this box and nothing else. The worker dials loopback
// (localComfyUI) so binding wider bought nothing but an open, unauthenticated
// /prompt — the hidden-run hole. --worker-mode makes the studio gate its submit
// seam (/v1/worker/execute + X-Worker-Token) so only the worker can start a render.
// VRAM mode: default --normalvram (safe for smaller BYO GPUs); override with
// HANZO_STUDIO_VRAM (e.g. "--highvram") on big-memory boxes (GB10 128G unified) so
// the Qwen text-encoder stays resident on-GPU instead of non-deterministically
// offloading to CPU — offload makes renders CPU-bound and ~8x slower.
vramMode := os.Getenv("HANZO_STUDIO_VRAM")
if vramMode == "" {
vramMode = "--normalvram"
}
cmd := exec.Command(studioPython(dir), "main.py",
"--listen", "127.0.0.1", "--port", "8188", "--worker-mode",
vramMode, "--disable-auto-launch",
"--output-directory", filepath.Join(dir, "output"))
cmd.Dir = dir
cmd.Env = append(os.Environ(),
"STUDIO_PERSIST_QUEUE=1",
"PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True",
)
cmd.Stdout = logf
cmd.Stderr = logf
cmd.SysProcAttr = &syscall.SysProcAttr{Setpgid: true}
if err := cmd.Start(); err != nil {
logf.Close()
return nil, err
}
logf.Close() // the child holds its own descriptor
// Shield the render backend from the OOM killer ahead of pack/model RAM
// spikes. Negative adj needs privilege; best-effort.
_ = os.WriteFile("/proc/"+strconv.Itoa(cmd.Process.Pid)+"/oom_score_adj",
[]byte("-700"), 0o644)
go func() { _ = cmd.Wait() }() // reap; the probe loop decides on restarts
return cmd, nil
}
// stopStudio kills the supervised process group (if any) and any foreign
// main.py still holding the port, then waits for the listener to clear.
func stopStudio(cmd *exec.Cmd) {
if cmd != nil && cmd.Process != nil {
_ = syscall.Kill(-cmd.Process.Pid, syscall.SIGTERM)
}
_ = exec.Command("pkill", "-f", "main.py --listen").Run()
for i := 0; i < 15; i++ {
conn, err := net.DialTimeout("tcp", studioAddr, time.Second)
if err != nil {
return
}
conn.Close()
time.Sleep(time.Second)
}
}
// studioRecycle carries at most one pending recycle request; the render
// handler signals it after each completed render (see gpu.go).
var studioRecycle = make(chan struct{}, 1)
// staging guards the claim-to-submit window: a claimed job is real work the
// engine queue cannot see yet, so the supervisor must never recycle over it
// (observed: jobs claimed during a recycle failed staging on a dead engine
// and were consumed).
var staging atomic.Int32
func requestStudioRecycle() {
select {
case studioRecycle <- struct{}{}:
default:
}
}
// studioBusy reports whether the engine holds queued or running prompts.
// A generous timeout: a saturated GB10 answers slowly mid-render — slow is
// alive, and killing a live render costs 8-70 minutes of GPU work.
func studioBusy(ctx context.Context) (busy, ok bool) {
ctx, cancel := context.WithTimeout(ctx, 20*time.Second)
defer cancel()
req, err := http.NewRequestWithContext(ctx, http.MethodGet, "http://"+studioAddr+"/queue", nil)
if err != nil {
return false, false
}
resp, err := http.DefaultClient.Do(req)
if err != nil {
return false, false
}
defer resp.Body.Close()
var q struct {
Running []json.RawMessage `json:"queue_running"`
Pending []json.RawMessage `json:"queue_pending"`
}
if err := json.NewDecoder(io.LimitReader(resp.Body, 32<<20)).Decode(&q); err != nil {
return false, false
}
return len(q.Running)+len(q.Pending) > 0, true
}
// superviseStudio keeps the local render backend on :8188 alive until ctx
// ends. Quiet by design: one line per restart event, not a probe firehose.
func superviseStudio(ctx context.Context, dir string, out io.Writer) {
var cmd *exec.Cmd
restart := func(reason string) {
stopStudio(cmd)
c, err := launchStudio(dir)
if err != nil {
fmt.Fprintf(out, "studio: launch failed (%s): %v\n", reason, err)
return
}
cmd = c
deadline := time.Now().Add(studioStartWindow)
for time.Now().Before(deadline) && ctx.Err() == nil {
if studioHealthy(ctx) {
fmt.Fprintf(out, "studio: serving on %s (pid %d, %s)\n", studioAddr, c.Process.Pid, reason)
return
}
time.Sleep(4 * time.Second)
}
fmt.Fprintf(out, "studio: started pid %d (%s) but %s not healthy yet\n", c.Process.Pid, reason, studioAddr)
}
if !studioHealthy(ctx) {
restart("boot")
} else {
fmt.Fprintf(out, "studio: already serving on %s\n", studioAddr)
}
tick := time.NewTicker(studioProbeEvery)
defer tick.Stop()
// recyclePending defers the post-render recycle until the queue is EMPTY:
// short jobs complete while a long render is mid-sample, and recycling on
// their completion killed the live render (observed: every direct render
// died within ~6 minutes while probe jobs cycled).
recyclePending := false
unhealthy := 0
for {
select {
case <-ctx.Done():
if cmd != nil && cmd.Process != nil {
_ = syscall.Kill(-cmd.Process.Pid, syscall.SIGTERM)
}
return
case <-studioRecycle:
recyclePending = true
case <-tick.C:
busy, ok := studioBusy(ctx)
if recyclePending && ok && !busy && staging.Load() == 0 {
recyclePending = false
unhealthy = 0
restart("recycle")
continue
}
if studioHealthy(ctx) {
unhealthy = 0
continue
}
if ok && busy {
// Alive-busy: slow health under render load is not death.
unhealthy = 0
continue
}
// Sustained silence with an idle or unreadable queue = actually dead.
unhealthy++
if unhealthy < 3 {
continue
}
unhealthy = 0
restart("unresponsive")
}
}
}
+570
View File
@@ -0,0 +1,570 @@
// Package account mounts the signed-in caller's OWN account self-service surface
// natively in the unified cloud binary — the Go port of the console's two NON-proxy
// Next server routes (app/keys + app/onboard) plus the money/store data bridges the
// statically-exported console needs (task #41, "True 1-binary FE"). It replaces the
// retired /v1/console/* namespace: "console" is just the cloud FE name, so there is NO
// /v1/console API domain — every route lives on its REAL domain.
//
// WHY THESE ROUTES (and not the pure passthrough proxies). The console's PURE BFF
// reverse-proxies — app/cloud, app/ai — vanish in the one-binary model: the SPA calls
// the canonical /v1/* on its own origin and the already-mounted subsystems answer. The
// routes ported HERE do REAL server work a static SPA cannot: keys/onboard run
// privileged IAM logic as the confidential `hanzo-console` client; embed-status/topup
// do server-side verification; and the billing/commerce bridges inject the commerce
// SERVICE token and pin the caller's own subject SERVER-SIDE (a passthrough would leak
// cross-tenant ledgers). Each has no pure-proxy equivalent, so it must be ported.
//
// SURFACE — each route on its REAL domain (every one requires a VALIDATED principal — a
// gateway-minted, IAM-verified X-User-Id; a client-forged X-Org-Id on the bearer-less
// path is refused):
//
// GET /v1/iam/keys — whether the caller has an `hk-` key (+ prefix/mtime); no secret.
// POST /v1/iam/keys — mint/rotate the key; returns { accessKey } ONCE.
// DELETE /v1/iam/keys — revoke the key.
// POST /v1/iam/onboard — create the caller's org (+ move them in on first run).
// GET /v1/csrf — mint the anti-CSRF token the SPA echoes on money writes (csrf.go).
// GET /v1/embed-status — brand-app embed entitlement + reachability probe (embed.go).
// POST /v1/commerce/topup/wallet — HUSD on-chain verify → commerce credit (topup.go).
// GET /v1/billing/* — per-tenant billing read, SCOPED to the validated caller (billing.go).
// … /v1/commerce/* — per-tenant STORE CRUD, SCOPED to the validated caller's org (commerce.go).
//
// TWO SUBSYSTEM REGISTRATIONS FROM ONE PACKAGE. A route-ordering constraint forces the
// split (Fiber matches by registration order — the earliest-mounted route wins):
// - `account` (order 48) mounts the SPECIFIC self-service routes. keys/onboard MUST
// win over clients/iam's /v1/iam/* WILDCARD (order 50), and topup MUST win over the
// commerce embed (order 100) + the /v1/commerce/* bridge — so they mount EARLY.
// - `account-bridge` (order 122) mounts the CATCH-ALL data bridges. /v1/billing/* must
// sit AFTER clients/billing's specific routes (order 121) and /v1/commerce/* after
// the commerce embed (order 100) — so they mount LATE.
//
// Both share one state shape + the process-wide CSRF key (csrf.go), so a token minted at
// /v1/csrf verifies on the /v1/billing|commerce writes.
//
// TENANCY. The caller is resolved from the VALIDATED identity headers ONLY
// (principal.Validated / c.Org() / c.User()), the same trust boundary every mutating
// subsystem uses. The IAM id targeted is DERIVED as `<owner>/<name>` from those
// validated claims — never taken from the request body/query — so a caller can only ever
// mint/revoke their OWN key and onboard THEMSELVES; there is no path to name a
// third-party subject. When the confidential client is unwired the surface is honestly
// "not configured" (501), never a fabricated key or org.
package account
import (
"context"
"encoding/base64"
"errors"
"fmt"
"net/http"
"os"
"strings"
"github.com/hanzoai/cloud"
"github.com/hanzoai/cloud/clients/principal"
"github.com/zap-proto/zip"
)
// adminOrg is THE SuperAdmin / IAM-system org that owns every customer org row —
// standardized as "admin" across the whole stack (IAM, commerce, ai, gateway all
// gate cross-tenant on owner=="admin"). A created customer org is owned by it.
const adminOrg = "admin"
// errNotConfigured is returned by the IAM client when the confidential
// `hanzo-console` credential is unset; handlers map it to a 501 (honest "not
// configured on this deployment", mirroring identity.ts's mintConfigured() gate).
var errNotConfigured = errors.New("iam confidential client not configured")
// errNotFound is a not-present sentinel (e.g. the user row IAM cannot return).
var errNotFound = errors.New("not found")
// state is account's own data; shared deps live in the embedded cloud.Base. Both
// subsystem registrations (account @48, account-bridge @122) build their own value;
// the CSRF key is the process-wide singleton (csrf.go) so a token minted by one
// verifies on the other.
type state struct {
iam *iamClient
csrfKey []byte // keyed-BLAKE3 MAC key for the money-write CSRF token (csrf.go)
writesRL *rateLimiter // per-IP abuse cap on the money-write routes (ratelimit.go)
}
// keysWriteRatePerMin caps money-write frequency per client IP (mint/rotate/revoke
// key, wallet top-up). Generous enough for real UI bursts, tight enough to blunt
// brute-force / enumeration when a caller reaches cloud directly (gateway bypassed).
const keysWriteRatePerMin = 30
// newService builds the shared subsystem value. Both subsystem Mounts construct one;
// the CSRF key is the process-wide singleton (csrf.go) so account (order 48) and
// account-bridge (order 122) verify each other's tokens.
func newService(deps cloud.Deps) *cloud.Service[state] {
b := cloud.NewBase(deps, "account")
st := state{iam: newIAMClient()}
st.csrfKey = sharedCSRFKey(b.Log)
st.writesRL = newRateLimiter(keysWriteRatePerMin)
return &cloud.Service[state]{Base: b, State: st}
}
// MountAccount wires the SPECIFIC self-service routes (order 48) — the ones that must
// win over the IAM /v1/iam/* wildcard (50) and the commerce embed (100).
func MountAccount(app *zip.App, deps cloud.Deps) error {
if app == nil {
return fmt.Errorf("account.MountAccount: nil zip.App")
}
if deps.Logger == nil {
return fmt.Errorf("account.MountAccount: nil deps.Logger")
}
s := newService(deps)
routesAccount(s, app)
s.Log.Info("account self-service surface mounted",
"iam", s.State.iam.base, "configured", s.State.iam.configured(), "brand", s.Brand)
return nil
}
// MountBridge wires the CATCH-ALL data bridges (order 122) — the /v1/billing/* and
// /v1/commerce/* proxies that must sit AFTER clients/billing (121) + the commerce embed.
func MountBridge(app *zip.App, deps cloud.Deps) error {
if app == nil {
return fmt.Errorf("account.MountBridge: nil zip.App")
}
if deps.Logger == nil {
return fmt.Errorf("account.MountBridge: nil deps.Logger")
}
s := newService(deps)
routesBridge(s, app)
s.Log.Info("account data bridges mounted", "prefixes", "/v1/billing/*,/v1/commerce/*", "brand", s.Brand)
return nil
}
// routesAccount wires the specific self-service routes (order 48).
func routesAccount(s *cloud.Service[state], app *zip.App) {
// GET /v1/csrf issues the anti-CSRF token the embedded SPA echoes as X-CSRF-Token on
// every money write (csrf.go). Safe (read-only), same-origin.
app.Get("/v1/csrf", cloud.Handle(s, issueCSRFToken))
// The caller's own `hk-` Cloud API key — IAM self-service. These SPECIFIC routes MUST
// register before clients/iam's /v1/iam/* wildcard (order 50 > 48) so Fiber's
// first-match scan hits the native handler, not the wildcard (TestIAMKeysBeatsWildcard).
// Reads are open; every state-changing WRITE is wrapped: requireCSRF blocks a
// cross-site ambient-cookie forgery, and rateLimit caps per-IP frequency (cloud is
// reachable off-gateway).
app.Get("/v1/iam/keys", cloud.Handle(s, getKey))
app.Post("/v1/iam/keys", rateLimit(s, s.State.writesRL, requireCSRF(s, cloud.Handle(s, mintKey))))
app.Delete("/v1/iam/keys", rateLimit(s, s.State.writesRL, requireCSRF(s, cloud.Handle(s, revokeKey))))
app.Post("/v1/iam/onboard", requireCSRF(s, cloud.Handle(s, onboard)))
// Console module embed-entitlement + reachability probe (embed.go).
app.Get("/v1/embed-status", cloud.Handle(s, embedStatus))
// HUSD wallet top-up (on-chain verify → commerce credit). A SPECIFIC commerce route
// that must beat the /v1/commerce/* bridge (122) AND the commerce embed (100) — so it
// mounts here at 48, ahead of both.
app.Post("/v1/commerce/topup/wallet", rateLimit(s, s.State.writesRL, requireCSRF(s, cloud.Handle(s, walletTopup))))
// The accepted rails are public on-chain data (chain, token, treasury), read by
// the browser to render the send UI. A GET with no side effects and no secret,
// so it needs neither CSRF nor the write limiter — but it MUST sit beside the
// POST at this priority, or the /v1/commerce/* bridge swallows it.
app.Get("/v1/commerce/topup/rails", cloud.Handle(s, topupRails))
}
// routesBridge wires the per-tenant catch-all data bridges (order 122).
func routesBridge(s *cloud.Service[state], app *zip.App) {
// Per-tenant billing DATA bridge — the canonical /v1/billing/* the statically-exported
// console calls, forwarded to commerce with the admin service token and SCOPED to the
// validated caller's own subject (billing.go). Registered AFTER clients/billing's
// specific routes (121 < 122) so those win and this catches the rest. GET+POST only.
// The wildcard is what the ROUTER matches; it is NOT the forwardable set — billing.go's
// billingForwardable allowlist decides that, per method, and 404s everything else
// BEFORE the admin service token is attached. Widening this pattern grants nothing on
// its own; adding a line to that table is the only way to expose an endpoint.
app.Get("/v1/billing/*", cloud.Handle(s, billingData))
app.Post("/v1/billing/*", requireCSRF(s, cloud.Handle(s, billingData)))
// Per-tenant STORE DATA bridge — the canonical /v1/commerce/* the console calls,
// forwarded to commerce's bare store surface /v1/<kind> with the admin service token
// and SCOPED to the validated caller's own org (commerce.go). Registered AFTER the
// commerce embed (100 < 122) so the embed wins when enabled. Full CRUD.
app.Get("/v1/commerce/*", cloud.Handle(s, commerceData))
app.Post("/v1/commerce/*", requireCSRF(s, cloud.Handle(s, commerceData)))
app.Put("/v1/commerce/*", requireCSRF(s, cloud.Handle(s, commerceData)))
app.Patch("/v1/commerce/*", requireCSRF(s, cloud.Handle(s, commerceData)))
app.Delete("/v1/commerce/*", requireCSRF(s, cloud.Handle(s, commerceData)))
}
// ── caller resolution (the tenancy boundary) ─────────────────────────────────
// caller is the signed-in user resolved from the VALIDATED identity headers. id is
// the `<owner>/<name>` composite IAM's privileged ops parse (GetOwnerAndNameFromId
// requires it — a bare token count of 1 throws "wrong token count"); owner is the
// org (X-Org-Id).
type caller struct {
id string // <owner>/<name> (or the bare user id when owner-less)
owner string // validated org (may be "" for a zero-org, first-run user)
name string // == X-User-Id: the stable user id (a UUID on the direct path)
username string // IAM username (X-User-Name); the `name` half IAM's user-key ops parse
}
// keyID is the `<owner>/<username>` composite IAM's user-key ops (mint/get/revoke
// user AccessKey) parse via GetOwnerAndNameFromId. It uses the IAM USERNAME, not
// name (== X-User-Id): on the in-binary direct-Bearer path X-User-Id is the UUID
// subject and `<owner>/<uuid>` fails IAM's user lookup ("password or code is
// incorrect"). On the gateway path username==name so keyID()==id — no change.
// Owner-less (first-run) callers can't own a key, so this is only reached with a
// validated owner; it falls back to id defensively.
func (cr caller) keyID() string {
if cr.owner != "" && cr.username != "" {
return cr.owner + "/" + cr.username
}
return cr.id
}
// resolveCaller derives the caller from the validated identity, or (zero,false)
// when there is no validated principal. requireOwner=true refuses a user with no
// org yet (used by the key ops, which must act scoped); onboarding passes
// requireOwner=false so a first-run zero-org user can create their first org. The id
// is ALWAYS derived from the validated claims, never a request value.
func resolveCaller(c *zip.Ctx, requireOwner bool) (caller, bool) {
if !principal.Validated(c) {
return caller{}, false // no gateway-minted, IAM-verified principal — refuse
}
name := strings.TrimSpace(c.User())
if name == "" {
return caller{}, false
}
owner := strings.TrimSpace(c.Org())
if requireOwner && owner == "" {
return caller{}, false
}
// IAM parses `<owner>/<name>`; prefer it, fall back to the bare id for an
// owner-less (first-run) user. Same id semantics as identity.ts.
id := name
if owner != "" {
id = owner + "/" + name
}
// username is the IAM USERNAME, kept DISTINCT from name (== X-User-Id) so the
// billing/topup subjects (which key on name) are byte-identical to today — this
// value narrows the blast radius to the IAM user-key ops alone (keyID()). It
// prefers X-User-Name (stamped from the validated `name` claim by
// SanitizeIdentity), because on the in-binary direct-Bearer path X-User-Id is the
// UUID subject and <owner>/<uuid> fails IAM's mint-user-keys/get-user lookup.
// Falls back to name for the gateway path (which mints X-User-Id==username). Both
// inputs are gateway/SanitizeIdentity-minted from a verified principal.
username := strings.TrimSpace(c.Header("X-User-Name"))
if username == "" {
username = name
}
return caller{id: id, owner: owner, name: name, username: username}, true
}
// ── keys (the per-user `hk-` Cloud API key) ──────────────────────────────────
type keyStatus struct {
HasKey bool `json:"hasKey"`
KeyPrefix string `json:"keyPrefix,omitempty"`
CreatedAt string `json:"createdAt,omitempty"`
}
// getKey reports whether the caller has an `hk-` key, its public prefix, and when
// the key row last changed — NO secret material. Reads IAM authoritatively (not the
// session claim, which lags a fresh key). Mirrors GET app/keys/route.ts.
func getKey(s *cloud.Service[state], c *zip.Ctx) error {
cr, ok := resolveCaller(c, true)
if !ok {
return zip.ErrForbidden("sign in to manage API keys")
}
if !s.State.iam.configured() {
return notConfigured("API key management")
}
uk, err := s.State.iam.getUserKey(c.Context(), cr.keyID())
if err != nil {
// Fail-soft on a transient IAM read: report "no key" rather than 5xx, so the
// page shows the honest empty state (never a fabricated key). The mint path
// still 502s loudly on a real failure — reads degrade, writes do not.
s.Log.Warn("get key: iam read failed (reporting no key)", "err", err)
return c.JSON(http.StatusOK, keyStatus{HasKey: false})
}
if uk.AccessKey == "" {
return c.JSON(http.StatusOK, keyStatus{HasKey: false})
}
prefix := uk.AccessKey
if len(prefix) > 11 {
prefix = prefix[:11]
}
return c.JSON(http.StatusOK, keyStatus{HasKey: true, KeyPrefix: prefix, CreatedAt: uk.UpdatedTime})
}
// mintKey (re)generates the caller's `hk-` key and returns it ONCE (show-once). A
// real IAM failure surfaces as 502 (never a fabricated key). Mirrors POST app/keys.
func mintKey(s *cloud.Service[state], c *zip.Ctx) error {
cr, ok := resolveCaller(c, true)
if !ok {
return zip.ErrForbidden("sign in to manage API keys")
}
if !s.State.iam.configured() {
return notConfigured("API key management")
}
key, err := s.State.iam.mintUserKey(c.Context(), cr.keyID())
if err != nil {
return zip.Errorf(http.StatusBadGateway, "could not mint an API key: %v", err)
}
return c.JSON(http.StatusOK, map[string]string{"accessKey": key})
}
// revokeKey clears the caller's `hk-` key. Mirrors DELETE app/keys.
func revokeKey(s *cloud.Service[state], c *zip.Ctx) error {
cr, ok := resolveCaller(c, true)
if !ok {
return zip.ErrForbidden("sign in to manage API keys")
}
if !s.State.iam.configured() {
return notConfigured("API key management")
}
if err := s.State.iam.revokeUserKey(c.Context(), cr.keyID()); err != nil {
return zip.Errorf(http.StatusBadGateway, "could not revoke the API key: %v", err)
}
return c.JSON(http.StatusOK, map[string]bool{"ok": true})
}
// ── onboard (create the caller's org) ────────────────────────────────────────
type onboardReq struct {
Name string `json:"name"`
Personal bool `json:"personal"`
}
type onboardResp struct {
Org string `json:"org"`
DisplayName string `json:"displayName"`
Additional bool `json:"additional"`
}
// onboard creates the caller's organization. Two flows, keyed on whether the caller
// already has a home org (mirrors app/onboard/route.ts):
//
// - FIRST-RUN (no owner): create + MOVE the user in as admin, so their next JWT
// carries the new owner and the cloud scopes everything to it.
// - ADDITIONAL (owner set): create the org but do NOT move the user — a move
// changes their IAM owner (stripping a SuperAdmin's status + orphaning their
// current org). They reach the new org via the OrgSwitcher, which re-scopes
// X-Org-Id without touching IAM membership. A personal-org request from someone
// who already has an org is meaningless → 409.
func onboard(s *cloud.Service[state], c *zip.Ctx) error {
cr, ok := resolveCaller(c, false) // first-run onboarding allows a zero-org user
if !ok {
return zip.ErrForbidden("sign in to create an organization")
}
if !s.State.iam.configured() {
return notConfigured("organization creation")
}
var body onboardReq
if len(c.Body()) > 0 {
if err := c.Bind(&body); err != nil {
return err
}
}
additional := cr.owner != ""
if additional && body.Personal {
return zip.ErrConflict("you already have an organization; name the new one explicitly")
}
baseSlug, displayName, herr := resolveOnboardName(s, body, cr)
if herr != nil {
return herr
}
// Resolve a unique slug. Personal orgs auto-suffix to stay unique; an explicit
// name that's taken is an honest conflict the user resolves by renaming.
slug, herr := uniqueSlug(s, c, baseSlug, body.Personal)
if herr != nil {
return herr
}
// ADDITIONAL org (caller already has a home): create it WITHOUT moving them —
// they reach it via the OrgSwitcher (a move would strip their SuperAdmin / orphan
// their current org).
if additional {
org := buildOrg(s, c, slug, displayName, body.Personal, cr.owner)
if err := s.State.iam.createOrganization(c.Context(), org); err != nil {
return zip.Errorf(http.StatusBadGateway, "could not create the organization: %v", err)
}
return c.JSON(http.StatusOK, onboardResp{Org: slug, DisplayName: displayName, Additional: true})
}
// FIRST-RUN: drive the ONE atomic IAM provision (org + admin move + hashed
// org-scoped credential), replacing the create-org + move-user pair — a mid-flight
// retry now converges on the founder's own org instead of orphaning it. The org
// starts at a zero balance (usage is pre-paid). Prefer it whenever the
// service-token path is wired; fall back to the legacy pair only when it is not,
// so a partial deploy still onboards.
if s.State.iam.provisionReady() {
resp, err := onboardFirstRun(c.Context(), s.State.iam, cr.id, slug, displayName, body.Personal)
if err != nil {
return err
}
return c.JSON(http.StatusOK, resp)
}
// Legacy fallback (service token unset): create then move — the non-atomic pair.
org := buildOrg(s, c, slug, displayName, body.Personal, cr.owner)
if err := s.State.iam.createOrganization(c.Context(), org); err != nil {
return zip.Errorf(http.StatusBadGateway, "could not create the organization: %v", err)
}
if err := s.State.iam.moveUserToOrg(c.Context(), cr.id, slug); err != nil {
return zip.Errorf(http.StatusBadGateway, "org created but could not assign you to it: %v", err)
}
return c.JSON(http.StatusOK, onboardResp{Org: slug, DisplayName: displayName, Additional: false})
}
// onboardFirstRun drives the ONE atomic IAM provision for a zero-org caller (create
// org + move them in as admin + mint the hashed org-scoped credential), replacing
// the create-org + move-user pair so a mid-flight retry converges on the founder's
// own org instead of orphaning it. The org starts at a ZERO balance — usage is
// pre-paid, so there is no signup grant. Split out so the provisioning glue is
// unit-tested against mock IAM without the CSRF/routing/principal shell.
func onboardFirstRun(ctx context.Context, iam *iamClient, callerID, slug, displayName string, personal bool) (onboardResp, error) {
row, err := iam.getUserRow(ctx, callerID)
if err != nil {
return onboardResp{}, zip.Errorf(http.StatusBadGateway, "could not resolve the user: %v", err)
}
res, err := iam.provision(ctx, row.Owner, row.Name, slug, personal)
if err != nil {
return onboardResp{}, zip.Errorf(http.StatusBadGateway, "could not provision the organization: %v", err)
}
return onboardResp{Org: res.Org, DisplayName: displayName, Additional: false}, nil
}
// resolveOnboardName derives the base slug + display name from the request, or a
// mapped HTTP error. Personal orgs derive from the username; a named org validates
// through the shared policy (onboarding.go).
func resolveOnboardName(s *cloud.Service[state], body onboardReq, cr caller) (baseSlug, displayName string, err error) {
if body.Personal {
baseSlug = personalOrgSlug(cr.name)
if len(baseSlug) < minOrgSlug || isReservedOrg(baseSlug) {
baseSlug = "org-" + firstNonEmpty(slugifyOrg(cr.name), "workspace")
}
return baseSlug, humanize(cr.name), nil
}
v := validateOrgName(body.Name)
if !v.ok {
return "", "", zip.ErrBadRequest(v.error)
}
return v.slug, strings.TrimSpace(body.Name), nil
}
// uniqueSlug returns a free slug at/after base. A named org that's taken is a 409;
// a personal org auto-suffixes (base, base-2, …) up to a small bound.
func uniqueSlug(s *cloud.Service[state], c *zip.Ctx, base string, personal bool) (string, error) {
existing, err := s.State.iam.getOrganization(c.Context(), base)
if err != nil {
return "", zip.Errorf(http.StatusBadGateway, "could not check organization availability: %v", err)
}
if existing == nil {
return base, nil
}
if !personal {
return "", zip.Errorf(http.StatusConflict, "“%s” is taken; choose a different name", base)
}
free, err := freeSlug(s, c, base)
if err != nil {
return "", err
}
if free == "" {
return "", zip.Errorf(http.StatusConflict, "could not find an available name")
}
return free, nil
}
// freeSlug finds the first free slug at/after base (base, base-2, … base-20), or ""
// if all are taken. Mirrors identity.ts's freeSlug bound of 20.
func freeSlug(s *cloud.Service[state], c *zip.Ctx, base string) (string, error) {
for i := 2; i <= 20; i++ {
trimmed := base
if len(trimmed) > maxOrgSlug-3 {
trimmed = trimmed[:maxOrgSlug-3]
}
candidate := strings.Trim(fmt.Sprintf("%s-%d", strings.TrimRight(trimmed, "-"), i), "-")
if len(candidate) < minOrgSlug || isReservedOrg(candidate) {
continue
}
existing, err := s.State.iam.getOrganization(c.Context(), candidate)
if err != nil {
return "", zip.Errorf(http.StatusBadGateway, "could not check organization availability: %v", err)
}
if existing == nil {
return candidate, nil
}
}
return "", nil
}
// buildOrg assembles the new customer org owned by the `admin` org, cloning
// password/locale settings from the caller's current org (best-effort; a nil source
// just yields a minimal org IAM completes with its defaults) and clearing all
// instance-specific material. Mirrors identity.ts's createOrganization body.
func buildOrg(s *cloud.Service[state], c *zip.Ctx, slug, displayName string, personal bool, sourceOwner string) iamOrg {
org := iamOrg{Owner: adminOrg, Name: slug, DisplayName: displayName, IsPersonal: personal}
if sourceOwner == "" {
return org
}
src, err := s.State.iam.getOrganization(c.Context(), sourceOwner)
if err != nil || src == nil {
return org // clone is best-effort; IAM applies its org defaults otherwise
}
org.PasswordType = src.PasswordType
org.PasswordSalt = src.PasswordSalt
org.PasswordObfuscatorType = src.PasswordObfuscatorType
org.PasswordObfuscatorKey = src.PasswordObfuscatorKey
org.PasswordOptions = src.PasswordOptions
org.CountryCodes = src.CountryCodes
org.Languages = src.Languages
org.DefaultAvatar = src.DefaultAvatar
return org
}
// ── shared helpers ────────────────────────────────────────────────────────────
// notConfigured is the honest 501 for a surface whose confidential client is
// unwired — the deployment simply lacks the `hanzo-console` credential.
func notConfigured(surface string) error {
return zip.Errorf(http.StatusNotImplemented, "%s is not configured on this deployment (IAM client unset)", surface)
}
// humanize title-cases the base of a username for a personal org's display name
// (dave.smith@x.com → "Dave Smith"). Mirrors identity/onboard humanize().
func humanize(username string) string {
base := username
// Split on '@' anywhere (mirrors identity.ts humanize's `includes('@')`), so a
// bare "@" collapses to "" → "Personal". (personalOrgSlug intentionally uses
// `> 0` instead, matching its own TS source.)
if at := strings.IndexByte(base, '@'); at >= 0 {
base = base[:at]
}
base = strings.TrimSpace(strings.Map(func(r rune) rune {
if r == '.' || r == '_' || r == '-' {
return ' '
}
return r
}, base))
if base == "" {
return "Personal"
}
parts := strings.Fields(base)
for i, p := range parts {
parts[i] = strings.ToUpper(p[:1]) + p[1:]
}
return strings.Join(parts, " ")
}
func firstNonEmpty(vals ...string) string {
for _, v := range vals {
if v != "" {
return v
}
}
return ""
}
func getenv(key, dflt string) string {
if v := strings.TrimSpace(os.Getenv(key)); v != "" {
return v
}
return dflt
}
func basicToken(id, secret string) string {
return base64.StdEncoding.EncodeToString([]byte(id + ":" + secret))
}
+555
View File
@@ -0,0 +1,555 @@
package account
import (
"encoding/base64"
"encoding/json"
"io"
"net/http"
"net/http/httptest"
"strings"
"sync"
"testing"
"github.com/hanzoai/cloud"
luxlog "github.com/luxfi/log"
"github.com/zap-proto/zip"
)
// fakeIAM is a stand-in for Hanzo IAM's /v1/iam/* management surface. It records
// the confidential-client Basic auth it received (so a test can assert the console
// authenticates as `hanzo-console`, NOT as the caller) and the exact `id` each
// privileged op targeted (so a test can prove the console only ever acts on the
// validated caller's own `<owner>/<name>`). It never needs a real cluster.
type fakeIAM struct {
mu sync.Mutex
// state
keys map[string]string // id → current hk- key ("" = none)
orgs map[string]map[string]any // slug → org row (nil map = absent)
user map[string]map[string]any // id → full user row (for the move)
// captured
gotAuth string // Authorization header on the last request
mintedFor []string // ids mint-user-keys was called with
revokedFor []string
movedTo map[string]string // id → new owner (from update-user)
createdOrgs []map[string]any
failAddOrg bool // when true, add-organization answers status!=ok
failMintKey bool
}
func newFakeIAM() *fakeIAM {
return &fakeIAM{
keys: map[string]string{},
orgs: map[string]map[string]any{},
user: map[string]map[string]any{},
movedTo: map[string]string{},
}
}
func (f *fakeIAM) server(t *testing.T) *httptest.Server {
t.Helper()
mux := http.NewServeMux()
ok := func(w http.ResponseWriter, data any) {
w.Header().Set("Content-Type", "application/json")
_ = json.NewEncoder(w).Encode(map[string]any{"status": "ok", "msg": "", "data": data})
}
bad := func(w http.ResponseWriter, msg string) {
w.Header().Set("Content-Type", "application/json")
_ = json.NewEncoder(w).Encode(map[string]any{"status": "error", "msg": msg, "data": nil})
}
mux.HandleFunc("/v1/iam/get-user", func(w http.ResponseWriter, r *http.Request) {
f.capture(r)
id := r.URL.Query().Get("id")
f.mu.Lock()
defer f.mu.Unlock()
if row, present := f.user[id]; present {
// A configured user row wins (used by the onboarding move).
out := map[string]any{}
for k, v := range row {
out[k] = v
}
if key, has := f.keys[id]; has {
out["accessKey"] = key
}
ok(w, out)
return
}
// Otherwise synthesize a thin row carrying just the key state.
ok(w, map[string]any{"accessKey": f.keys[id], "updatedTime": "2026-01-02T03:04:05Z"})
})
mux.HandleFunc("/v1/iam/mint-user-keys", func(w http.ResponseWriter, r *http.Request) {
f.capture(r)
id := r.URL.Query().Get("id")
f.mu.Lock()
defer f.mu.Unlock()
f.mintedFor = append(f.mintedFor, id)
if f.failMintKey {
bad(w, "mint failed")
return
}
key := "hk-" + strings.ReplaceAll(id, "/", "-") + "-SECRET"
f.keys[id] = key
ok(w, map[string]any{"accessKey": key})
})
mux.HandleFunc("/v1/iam/revoke-user-keys", func(w http.ResponseWriter, r *http.Request) {
f.capture(r)
id := r.URL.Query().Get("id")
f.mu.Lock()
defer f.mu.Unlock()
f.revokedFor = append(f.revokedFor, id)
f.keys[id] = ""
ok(w, map[string]any{})
})
mux.HandleFunc("/v1/iam/get-organization", func(w http.ResponseWriter, r *http.Request) {
f.capture(r)
id := r.URL.Query().Get("id") // admin/<slug>
slug := id
if i := strings.IndexByte(id, '/'); i >= 0 {
slug = id[i+1:]
}
f.mu.Lock()
defer f.mu.Unlock()
if row, present := f.orgs[slug]; present && row != nil {
ok(w, row)
return
}
bad(w, "organization does not exist") // not-ok ⇒ getOrganization returns (nil,nil)
})
mux.HandleFunc("/v1/iam/add-organization", func(w http.ResponseWriter, r *http.Request) {
f.capture(r)
body, _ := io.ReadAll(r.Body)
var row map[string]any
_ = json.Unmarshal(body, &row)
f.mu.Lock()
defer f.mu.Unlock()
if f.failAddOrg {
bad(w, "add-organization denied")
return
}
f.createdOrgs = append(f.createdOrgs, row)
if name, _ := row["name"].(string); name != "" {
f.orgs[name] = row
}
ok(w, map[string]any{})
})
mux.HandleFunc("/v1/iam/update-user", func(w http.ResponseWriter, r *http.Request) {
f.capture(r)
id := r.URL.Query().Get("id")
body, _ := io.ReadAll(r.Body)
var row map[string]any
_ = json.Unmarshal(body, &row)
f.mu.Lock()
defer f.mu.Unlock()
if owner, _ := row["owner"].(string); owner != "" {
f.movedTo[id] = owner
}
ok(w, map[string]any{})
})
srv := httptest.NewServer(mux)
t.Cleanup(srv.Close)
return srv
}
func (f *fakeIAM) capture(r *http.Request) {
f.mu.Lock()
f.gotAuth = r.Header.Get("Authorization")
f.mu.Unlock()
}
// mountApp mounts the account surface against the fake IAM at base, with the
// confidential client wired (unless creds are ""). Returns the app.
func mountApp(t *testing.T, base, clientID, clientSecret string) *zip.App {
t.Helper()
t.Setenv("IAM_URL", base)
t.Setenv("IAM_MINT_CLIENT_ID", clientID)
t.Setenv("IAM_MINT_CLIENT_SECRET", clientSecret)
return mountBoth(t, "hanzo")
}
// mountBoth mounts BOTH account subsystems (self-service + data bridges) on one app —
// exactly what production registers (account@48 then account-bridge@122), so a test
// exercises the full surface with the shared CSRF key. The caller sets the IAM env
// (IAM_URL / IAM_MINT_CLIENT_*) before calling.
func mountBoth(t *testing.T, brand string) *zip.App {
t.Helper()
app := zip.New(zip.Config{Logger: luxlog.New("test")})
deps := cloud.Deps{Logger: luxlog.New("test"), Brand: brand}
if err := MountAccount(app, deps); err != nil {
t.Fatalf("MountAccount: %v", err)
}
if err := MountBridge(app, deps); err != nil {
t.Fatalf("MountBridge: %v", err)
}
return app
}
// callH drives a request with arbitrary VALIDATED-identity headers (the gateway sets
// these only from a verified credential). Mirrors `call` but lets a test inject
// X-User-Email / X-User-IsAdmin, which the ported routes read.
func callH(t *testing.T, app *zip.App, method, path string, headers map[string]string, body string) (int, []byte) {
t.Helper()
var rdr io.Reader
if body != "" {
rdr = strings.NewReader(body)
}
req := httptest.NewRequest(method, path, rdr)
if body != "" {
req.Header.Set("Content-Type", "application/json")
}
for k, v := range headers {
if v != "" {
req.Header.Set(k, v)
}
}
resp, err := app.Fiber().Test(req)
if err != nil {
t.Fatalf("Test %s %s: %v", method, path, err)
}
defer func() { _ = resp.Body.Close() }()
b, _ := io.ReadAll(resp.Body)
return resp.StatusCode, b
}
// call drives a request through the mounted app. When user is non-empty it injects
// a VALIDATED principal (X-User-Id set — the gateway sets this ONLY from a verified
// credential) with org as X-Org-Id. body is an optional JSON string.
func call(t *testing.T, app *zip.App, method, path, user, org, body string) (int, []byte) {
t.Helper()
var rdr io.Reader
if body != "" {
rdr = strings.NewReader(body)
}
req := httptest.NewRequest(method, path, rdr)
if body != "" {
req.Header.Set("Content-Type", "application/json")
}
if user != "" {
req.Header.Set("X-User-Id", user)
}
if org != "" {
req.Header.Set("X-Org-Id", org)
}
resp, err := app.Fiber().Test(req)
if err != nil {
t.Fatalf("Test %s %s: %v", method, path, err)
}
defer func() { _ = resp.Body.Close() }()
b, _ := io.ReadAll(resp.Body)
return resp.StatusCode, b
}
// ── keys ──────────────────────────────────────────────────────────────────────
func TestKeys_RequireValidatedPrincipal(t *testing.T) {
f := newFakeIAM()
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
// No X-User-Id → no validated principal → 403, and IAM is never touched, even if
// a forged X-Org-Id is present (the bearer-less data path must not mint a key).
for _, m := range []string{http.MethodGet, http.MethodPost, http.MethodDelete} {
code, _ := call(t, app, m, "/v1/iam/keys", "", "victim", "")
if code != http.StatusForbidden {
t.Fatalf("%s /keys with forged org but no principal: want 403, got %d", m, code)
}
}
if len(f.mintedFor) != 0 || len(f.revokedFor) != 0 {
t.Fatalf("IAM privileged op reached on the unauthenticated path: minted=%v revoked=%v", f.mintedFor, f.revokedFor)
}
}
func TestKeys_MintGetRevoke_ScopedToCaller(t *testing.T) {
f := newFakeIAM()
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
// GET before mint → hasKey:false (authoritative IAM read, not the claim).
code, body := call(t, app, http.MethodGet, "/v1/iam/keys", "alice", "acme", "")
if code != http.StatusOK {
t.Fatalf("get pre-mint: want 200, got %d (%s)", code, body)
}
var st keyStatus
mustJSON(t, body, &st)
if st.HasKey {
t.Fatalf("pre-mint hasKey should be false: %s", body)
}
// POST → mint; the key is returned ONCE, and IAM was targeted with the DERIVED
// `<owner>/<name>` id — never a request value.
code, body = call(t, app, http.MethodPost, "/v1/iam/keys", "alice", "acme", "")
if code != http.StatusOK {
t.Fatalf("mint: want 200, got %d (%s)", code, body)
}
var minted struct {
AccessKey string `json:"accessKey"`
}
mustJSON(t, body, &minted)
if minted.AccessKey != "hk-acme-alice-SECRET" {
t.Fatalf("mint returned wrong key: %q", minted.AccessKey)
}
if len(f.mintedFor) != 1 || f.mintedFor[0] != "acme/alice" {
t.Fatalf("mint should target the derived id acme/alice, got %v", f.mintedFor)
}
// The confidential client authenticated as `hanzo-console` (Basic), NOT as the
// caller — the whole point of the app-on-behalf boundary.
wantAuth := "Basic " + base64.StdEncoding.EncodeToString([]byte("hanzo-console:s3cr3t"))
if f.gotAuth != wantAuth {
t.Fatalf("IAM auth: want confidential-client Basic, got %q", f.gotAuth)
}
// GET after mint → hasKey:true with the public prefix only (no secret material).
code, body = call(t, app, http.MethodGet, "/v1/iam/keys", "alice", "acme", "")
mustJSON(t, body, &st)
if code != http.StatusOK || !st.HasKey || st.KeyPrefix != "hk-acme-ali" {
t.Fatalf("get post-mint: want hasKey + 11-char prefix, got %d %s", code, body)
}
if strings.Contains(string(body), "SECRET") {
t.Fatalf("GET /keys leaked the secret: %s", body)
}
// DELETE → revoke, targeting the same derived id.
code, _ = call(t, app, http.MethodDelete, "/v1/iam/keys", "alice", "acme", "")
if code != http.StatusOK || len(f.revokedFor) != 1 || f.revokedFor[0] != "acme/alice" {
t.Fatalf("revoke: want 200 targeting acme/alice, got %d %v", code, f.revokedFor)
}
}
// TestKeys_DirectBearerPath_MintsByUsernameNotUUID is the regression guard for the
// cloud-direct hk- mint 502. On the in-binary direct-Bearer path SanitizeIdentity
// stamps X-User-Id = the JWT subject (a UUID) and, distinctly, X-User-Name = the IAM
// username. The user-key ops must target <owner>/<username> ("hanzo/z"), NOT
// <owner>/<uuid> — which failed IAM's GetOwnerAndNameFromId user lookup ("password
// or code is incorrect", surfaced as 502). The gateway path (no X-User-Name;
// X-User-Id == username) must be UNCHANGED (keyID falls back to owner/name).
func TestKeys_DirectBearerPath_MintsByUsernameNotUUID(t *testing.T) {
f := newFakeIAM()
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
const uuid = "2d4d67ab-30f1-474e-b81f-f60461852259"
req := httptest.NewRequest(http.MethodPost, "/v1/iam/keys", nil)
req.Header.Set("X-User-Id", uuid) // direct-path stamp: the subject UUID
req.Header.Set("X-User-Name", "z") // direct-path stamp: the IAM username
req.Header.Set("X-Org-Id", "hanzo")
resp, err := app.Fiber().Test(req)
if err != nil {
t.Fatalf("Test: %v", err)
}
defer func() { _ = resp.Body.Close() }()
b, _ := io.ReadAll(resp.Body)
if resp.StatusCode != http.StatusOK {
t.Fatalf("direct-path mint: want 200, got %d (%s)", resp.StatusCode, b)
}
if len(f.mintedFor) != 1 || f.mintedFor[0] != "hanzo/z" {
t.Fatalf("direct-path mint must target hanzo/z (username), never hanzo/<uuid>: got %v", f.mintedFor)
}
var minted struct {
AccessKey string `json:"accessKey"`
}
mustJSON(t, b, &minted)
if minted.AccessKey != "hk-hanzo-z-SECRET" {
t.Fatalf("direct-path mint returned wrong key: %q", minted.AccessKey)
}
}
func TestKeys_NotConfigured_501(t *testing.T) {
f := newFakeIAM()
app := mountApp(t, f.server(t).URL, "", "") // confidential client unwired
code, body := call(t, app, http.MethodPost, "/v1/iam/keys", "alice", "acme", "")
if code != http.StatusNotImplemented {
t.Fatalf("unconfigured mint: want 501, got %d (%s)", code, body)
}
}
func TestKeys_MintUpstreamFailure_502(t *testing.T) {
f := newFakeIAM()
f.failMintKey = true
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
code, body := call(t, app, http.MethodPost, "/v1/iam/keys", "alice", "acme", "")
if code != http.StatusBadGateway {
t.Fatalf("mint upstream failure: want 502, got %d (%s)", code, body)
}
}
// ── onboard ─────────────────────────────────────────────────────────────────
func TestOnboard_FirstRun_CreatesAndMoves(t *testing.T) {
f := newFakeIAM()
// The zero-org user (empty X-Org-Id ⇒ bare id "dave") has a real user row so the
// move can re-submit it.
f.user["dave"] = map[string]any{"owner": "", "name": "dave", "type": "normal-user"}
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
// First-run: the caller has NO org (empty X-Org-Id) but IS validated. onboard
// must allow it (requireOwner=false), create the org, and MOVE the user in.
code, body := call(t, app, http.MethodPost, "/v1/iam/onboard", "dave", "", `{"name":"Acme Rockets"}`)
if code != http.StatusOK {
t.Fatalf("first-run onboard: want 200, got %d (%s)", code, body)
}
var resp onboardResp
mustJSON(t, body, &resp)
if resp.Org != "acme-rockets" || resp.Additional {
t.Fatalf("onboard result wrong: %+v", resp)
}
if len(f.createdOrgs) != 1 {
t.Fatalf("want 1 org created, got %d", len(f.createdOrgs))
}
if owner, _ := f.createdOrgs[0]["owner"].(string); owner != "admin" {
t.Fatalf("created org must be owned by admin, got %q", owner)
}
if f.movedTo["dave"] != "acme-rockets" {
t.Fatalf("first-run must move the user into the new org, movedTo=%v", f.movedTo)
}
}
func TestOnboard_Additional_CreatesWithoutMoving(t *testing.T) {
f := newFakeIAM()
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
// The caller ALREADY has an org. onboard must create the new org but NOT move
// them (a move would strip their owner + orphan their current org).
code, body := call(t, app, http.MethodPost, "/v1/iam/onboard", "alice", "acme", `{"name":"Side Project"}`)
if code != http.StatusOK {
t.Fatalf("additional onboard: want 200, got %d (%s)", code, body)
}
var resp onboardResp
mustJSON(t, body, &resp)
if resp.Org != "side-project" || !resp.Additional {
t.Fatalf("additional onboard result wrong: %+v", resp)
}
if len(f.movedTo) != 0 {
t.Fatalf("additional onboard must NOT move the user, movedTo=%v", f.movedTo)
}
}
func TestOnboard_ReservedAndTaken(t *testing.T) {
f := newFakeIAM()
f.orgs["taken"] = map[string]any{"owner": "admin", "name": "taken"}
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
// A reserved brand/system name is a 400 (policy), before any IAM create.
code, _ := call(t, app, http.MethodPost, "/v1/iam/onboard", "alice", "acme", `{"name":"Hanzo"}`)
if code != http.StatusBadRequest {
t.Fatalf("reserved name: want 400, got %d", code)
}
// An explicit name that's taken is an honest 409.
code, _ = call(t, app, http.MethodPost, "/v1/iam/onboard", "alice", "acme", `{"name":"Taken"}`)
if code != http.StatusConflict {
t.Fatalf("taken name: want 409, got %d", code)
}
if len(f.createdOrgs) != 0 {
t.Fatalf("no org should be created for reserved/taken names, got %d", len(f.createdOrgs))
}
}
func TestOnboard_Personal_AutoSuffixesOnCollision(t *testing.T) {
f := newFakeIAM()
f.user["dave"] = map[string]any{"owner": "", "name": "dave"}
f.orgs["dave"] = map[string]any{"owner": "admin", "name": "dave"} // base personal slug already taken
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
// personal:true (zero-org user) with the base slug taken → auto-suffix to dave-2,
// first-run move.
code, body := call(t, app, http.MethodPost, "/v1/iam/onboard", "dave", "", `{"personal":true}`)
if code != http.StatusOK {
t.Fatalf("personal onboard: want 200, got %d (%s)", code, body)
}
var resp onboardResp
mustJSON(t, body, &resp)
if resp.Org != "dave-2" {
t.Fatalf("personal collision should auto-suffix to dave-2, got %q", resp.Org)
}
}
func TestOnboard_PersonalWhenAlreadyOrged_409(t *testing.T) {
f := newFakeIAM()
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
// A user WITH an org asking for a personal org is meaningless → 409.
code, _ := call(t, app, http.MethodPost, "/v1/iam/onboard", "alice", "acme", `{"personal":true}`)
if code != http.StatusConflict {
t.Fatalf("personal-while-orged: want 409, got %d", code)
}
}
func TestOnboard_Unauthenticated_403(t *testing.T) {
f := newFakeIAM()
app := mountApp(t, f.server(t).URL, "hanzo-console", "s3cr3t")
code, _ := call(t, app, http.MethodPost, "/v1/iam/onboard", "", "", `{"name":"x"}`)
if code != http.StatusForbidden {
t.Fatalf("unauth onboard: want 403, got %d", code)
}
}
// ── route ordering: the native /v1/iam surface beats clients/iam's wildcard ───
// TestIAMKeysBeatsWildcard proves the ACTUAL route-match precedence: with the account
// self-service routes mounted FIRST (order 48) and clients/iam's /v1/iam/* WILDCARD
// mounted AFTER (order 50) — the exact production mount order — a request to /v1/iam/keys
// reaches the NATIVE handler, not the wildcard. A path the native surface does NOT own
// still falls through to the wildcard, proving it is really mounted and only the specific
// route shadows it.
func TestIAMKeysBeatsWildcard(t *testing.T) {
f := newFakeIAM()
t.Setenv("IAM_URL", f.server(t).URL)
t.Setenv("IAM_MINT_CLIENT_ID", "hanzo-console")
t.Setenv("IAM_MINT_CLIENT_SECRET", "s3cr3t")
app := zip.New(zip.Config{Logger: luxlog.New("test")})
deps := cloud.Deps{Logger: luxlog.New("test"), Brand: "hanzo"}
// account (order 48) mounts its SPECIFIC /v1/iam/keys + /v1/iam/onboard FIRST.
if err := MountAccount(app, deps); err != nil {
t.Fatalf("MountAccount: %v", err)
}
// clients/iam (order 50) mounts its /v1/iam/* WILDCARD AFTER — the exact prod order.
const sentinel = 599
app.All("/v1/iam/*", func(c *zip.Ctx) error {
return c.JSON(sentinel, map[string]string{"handler": "iam-wildcard"})
})
// GET /v1/iam/keys must hit the NATIVE handler (keyStatus 200), never the wildcard.
code, body := call(t, app, http.MethodGet, "/v1/iam/keys", "alice", "acme", "")
if code != http.StatusOK {
t.Fatalf("/v1/iam/keys must hit the native handler (200), got %d (%s) — wildcard shadowed it", code, body)
}
if strings.Contains(string(body), "iam-wildcard") {
t.Fatalf("/v1/iam/keys reached the wildcard, not the native handler: %s", body)
}
var st keyStatus
mustJSON(t, body, &st) // native response shape
// POST /v1/iam/keys (mint) must ALSO hit the native handler and target the derived id.
code, body = call(t, app, http.MethodPost, "/v1/iam/keys", "alice", "acme", "")
if code != http.StatusOK || strings.Contains(string(body), "iam-wildcard") {
t.Fatalf("POST /v1/iam/keys must mint via the native handler, got %d (%s)", code, body)
}
if len(f.mintedFor) != 1 || f.mintedFor[0] != "acme/alice" {
t.Fatalf("native mint must target acme/alice, got %v", f.mintedFor)
}
// /v1/iam/onboard is likewise native (not the wildcard).
code, _ = call(t, app, http.MethodPost, "/v1/iam/onboard", "dave", "", `{"name":"Acme Rockets"}`)
if code == sentinel {
t.Fatalf("/v1/iam/onboard reached the wildcard (%d) — the native handler must win", sentinel)
}
// A path the native surface does NOT own falls through to the wildcard (proof it IS
// mounted and only the specific /v1/iam/keys + /v1/iam/onboard routes shadow it).
code, _ = call(t, app, http.MethodGet, "/v1/iam/oauth/token", "alice", "acme", "")
if code != sentinel {
t.Fatalf("/v1/iam/oauth/token must reach the /v1/iam/* wildcard (%d), got %d", sentinel, code)
}
}
func mustJSON(t *testing.T, body []byte, v any) {
t.Helper()
if err := json.Unmarshal(body, v); err != nil {
t.Fatalf("decode %T: %v (%s)", v, err, body)
}
}
+358
View File
@@ -0,0 +1,358 @@
// billing.go — the per-tenant billing DATA bridge, the Go port of console's
// app/billing/v1/[...path]/route.ts (task #41, the BFF catch-all sweep). It lets the
// statically-exported console reach its own money surface at the CANONICAL same-origin
// /v1/billing/* (nothing before /v1/): GET|POST /v1/billing/<path> forwards to
// commerce's /v1/billing/<path> with the admin COMMERCE_SERVICE_TOKEN, SCOPING every
// request to the VALIDATED caller's own billing subject — so a tenant can only ever
// read/act on its OWN ledger (balance / usage / invoices / subscriptions /
// payment-methods / spend-alerts / …), never another's.
//
// TWO INDEPENDENT BOUNDS, because the token makes this a privileged forwarder:
// 1. WHICH ENDPOINT — billingForwardable, the per-method allowlist below. It is the
// authorization gate: an unlisted path is 404'd before the token is ever attached, so
// no money-MINT route (deposit/credit/refund/…) can be reached through this bridge.
// 2. WHOSE DATA — the subject-pinning below. It aims a permitted call at the caller's own
// ledger. It is an IDOR control and NOT an authority control: on a mint route it would
// have pinned the CREDIT to the attacker's own account. (1) is what stops that.
//
// WHY A SERVER HANDLER (not a same-origin passthrough). Commerce's billing surface is
// service-token-gated and filters DIFFERENT endpoints on DIFFERENT subject params —
// subscriptions on ?userId, payment-methods on ?customerId, usage on ?user. Pinning
// only ONE leaves the others UNFILTERED, so a request with no (or a forged) param
// returns every subject's rows in the namespace. This handler pins ALL of them to the
// server-resolved subject (and drops ?org), on the query AND the write body — exactly
// mirroring console's billing-scope.ts and commerce's own edge-auth billingSubjectKeys.
//
// IDOR-safe: the subject is derived from the VALIDATED identity (resolveCaller →
// principal.Validated / c.Org() / c.User()), NEVER a client-supplied userId/org. A
// bearer-less request with a forged X-Org-Id has no validated principal and is refused.
package account
import (
"bytes"
"crypto/subtle"
"encoding/json"
"net/http"
"net/url"
"strings"
"unicode"
"github.com/hanzoai/account"
"github.com/hanzoai/cloud"
"github.com/hanzoai/cloud/clients/principal"
"github.com/zap-proto/zip"
)
// billingForwardable — THE allowlist of billing endpoints this bridge may forward, keyed
// by method. It is the whole authorization story of the bridge, because forwarding IS
// authorization here: every forwarded request carries the admin COMMERCE_SERVICE_TOKEN,
// and commerce's money gate is MayMintMoney(c) = IsServiceToken(c) || IsSuperAdmin(c)
// (middleware/platformonly.go). The token satisfies IsServiceToken, so ANY subpath that
// reaches commerce is executed with PLATFORM authority — not the caller's. Commerce 403s
// an org admin who calls POST /v1/billing/deposit directly; without this table the bridge
// handed that same person the platform's own credential and minted it for them, scoped —
// by the subject-pinning below — to their OWN account. That is the escalation, and
// subject-pinning is what AIMS it, not what stops it. Only a path gate stops it.
//
// It is an ALLOWLIST, never a denylist: a denylist must enumerate every mint route
// (deposit/credit/refund/credit-grants/payouts/husd/allotment…) and stays correct only
// until commerce adds the next one — a route this file has never heard of is then
// forwarded by default. Here the default is REFUSE, so a new commerce mint route is
// unreachable the day it lands, with no change on this side. One table, one place; a path
// not in it cannot reach commerce, by construction.
//
// GET and POST are SEPARATE sets because a read bridge and a write bridge are different
// concerns: `payouts` is a legitimate read and a money-MINT write (api/billing/handlers.go
// `api.Get("/payouts", ListPayouts)` vs `api.Post("/payouts", mintRequired, CreatePayout)`),
// so one method-blind set would hand the mint to every reader. The POST set is therefore
// deliberately tiny and holds NOTHING that creates spendable balance from a client-named
// amount: cancel/reactivate a subscription, vault a card, create a budget, and a top-up
// that CHARGES a real card (money in, not minted). Every entry is a call the console
// actually makes; `{}` matches exactly one opaque id segment.
//
// EVIDENCE — each entry is a live console call (repo hanzoai/console):
//
// GET balance src/lib/api/billing.ts:397 sidebar wallet + billing overview
// GET usage src/lib/api/billing.ts:415 cost reports / AI metrics
// GET invoices src/lib/api/billing.ts:419 invoice history table
// GET invoices/{}/pdf src/components/products/billing/BillingInvoices.tsx:31
// GET subscriptions src/lib/api/billing.ts:423 subscriptions list
// GET payment-methods src/lib/api/billing.ts:450 saved cards (masked)
// GET spend-alerts src/lib/api/billing.ts:482 budgets / spend caps
// GET payment-config src/lib/api/billing.ts:552 public Square app/location id
// GET plans src/lib/api/plans.ts:126 published tiers
// GET payouts src/components/products/SettlementModule.tsx:61 settlement view
// POST subscriptions/{}/cancel src/lib/api/billing.ts:434
// POST subscriptions/{}/reactivate src/lib/api/billing.ts:444
// POST payment-methods src/lib/api/billing.ts:461 vault a Square nonce (no PAN)
// POST spend-alerts src/lib/api/billing.ts:500 create a budget
// POST topup/token src/lib/api/billing.ts:565 charge a card → credit
//
// balance/usage/payment-methods are ALSO served natively by clients/billing (order 121),
// which wins over this catch-all (122), so those entries are reached only on a deploy
// where that subsystem is disabled. They are listed because they are legitimate reads of
// the caller's own ledger, not because this bridge is their primary route.
//
// NOT LISTED, deliberately: `me/welcome` and `grant-starter` (console calls the first at
// billing.ts:407 and the second server-side at src/lib/server/billing-grant.ts:35) exist
// in NEITHER the pinned commerce (v1.48.5) route table — both 404 today whether or not
// this bridge forwards them, and grant-starter is mint-gated and browser-unreachable by
// design. The console's PATCH/DELETE calls (spend-alerts/{}, payment-methods/{}) are absent
// because routesBridge mounts GET+POST only, so they never reached this handler.
var billingForwardable = map[string][]string{
http.MethodGet: {
"balance",
"usage",
"invoices",
"invoices/{}/pdf",
"subscriptions",
"payment-methods",
"spend-alerts",
"spend-alerts/authorize", // the S2S cap-verdict read (metering gate); 2 segments need their own entry
"payment-config",
"plans",
"payouts",
},
http.MethodPost: {
"subscriptions/{}/cancel",
"subscriptions/{}/reactivate",
"payment-methods",
"spend-alerts",
"topup/token",
},
}
// isForwardableBilling reports whether method+sub is in billingForwardable. sub has
// already passed isSafeSegment, so no segment can contain a slash, a percent-escape, or a
// traversal — a pattern segment therefore matches exactly one real segment and `{}` cannot
// swallow a path. Fail-closed: an unknown method or an unlisted path is false.
func isForwardableBilling(method, sub string) bool {
got := strings.Split(sub, "/")
for _, pattern := range billingForwardable[method] {
want := strings.Split(pattern, "/")
if len(want) != len(got) {
continue
}
match := true
for i, seg := range want {
if seg != "{}" && seg != got[i] {
match = false
break
}
}
if match {
return true
}
}
return false
}
// billingSubjectKeys — every query/body param through which a commerce billing endpoint
// identifies its subject. Kept identical to commerce's edge-auth billingSubjectKeys
// {user,userId,customerId} AND console's billing-scope.ts BILLING_SUBJECT_KEYS. Change
// all three together — pinning ALL of them is what scopes EVERY endpoint no matter which
// param it filters on.
var billingSubjectKeys = []string{"user", "userId", "customerId"}
func isSubjectKey(k string) bool {
for _, s := range billingSubjectKeys {
if s == k {
return true
}
}
return false
}
// scopedBillingSearch — pin every billingSubjectKey to subject (OVERWRITING any client
// value — the browser cannot widen scope) and DROP org. Every OTHER param (currency,
// status, date range) passes through untouched. Mirrors billing-scope.ts.
func scopedBillingSearch(in url.Values, subject string) url.Values {
out := url.Values{}
for k, v := range in {
if k == "org" || isSubjectKey(k) {
continue // org dropped; subject keys set authoritatively below
}
out[k] = v
}
for _, k := range billingSubjectKeys {
out.Set(k, subject)
}
return out
}
// scopedBillingBody — pin every billingSubjectKey on a top-level JSON object to subject
// (commerce reads the subject from the JSON body on writes like create-spend-alert). A
// non-JSON / non-object / empty body is returned UNCHANGED — this only ever narrows a
// JSON object to the caller; it never invents a body. Mirrors billing-scope.ts.
func scopedBillingBody(raw []byte, subject string) []byte {
if len(bytes.TrimSpace(raw)) == 0 {
return raw
}
var obj map[string]json.RawMessage
if err := json.Unmarshal(raw, &obj); err != nil {
return raw // JSON array / scalar / form / binary — leave untouched
}
subj, err := json.Marshal(subject)
if err != nil {
return raw
}
for _, k := range billingSubjectKeys {
obj[k] = subj
}
out, err := json.Marshal(obj)
if err != nil {
return raw
}
return out
}
// isSafeSegment reports whether a path segment is safe to forward. It is the ONE segment
// guard for this package (the billing AND commerce bridges): a segment is safe only if
// it is non-empty, not "." / "..", and free of any character a downstream router could
// re-split or re-decode into traversal — slash, backslash, percent-escape (`%2f`/`%2e`,
// single- or N-encoded), matrix param (`;`), or a control char (incl. null). The router
// leaves `%2f`/`%2e` UNdecoded in the wildcard param, but the Go http client — and
// commerce's own router — WILL decode+normalize them downstream, turning
// `x/..%2fbilling` into `/v1/billing`: a tunnel PAST the allow-list into the money
// surface. Rejecting `%`/`;` at the segment makes single-, double-, and N-encoded
// traversal impossible. Billing endpoints / commerce ids are opaque + escape-free, so
// this never over-blocks. Mirrors console's bearer-proxy pathIsClean.
func isSafeSegment(s string) bool {
if s == "" || s == "." || s == ".." {
return false
}
for _, r := range s {
if r == '/' || r == '\\' || r == '%' || r == ';' || unicode.IsControl(r) {
return false
}
}
return true
}
// commerceCreds resolves the commerce base + admin S2S token from server-only env
// (COMMERCE_URL default the public gateway; COMMERCE_SERVICE_TOKEN sourced from KMS —
// never a browser value). Same wiring as clients/admin + topup.go's HUSD credit.
func commerceCreds() (base, token string) {
base = strings.TrimRight(getenv("COMMERCE_URL", "https://api.hanzo.ai"), "/")
token = getenv("COMMERCE_SERVICE_TOKEN", "")
return
}
// billingData forwards GET|POST /v1/billing/<path> to commerce's /v1/billing/<path>,
// scoped to the caller's OWN subject. Mirrors GET/POST app/billing/v1/[...path]/route.ts.
func billingData(s *cloud.Service[state], c *zip.Ctx) error {
// IDOR boundary: the subject is the VALIDATED caller's own org/user, never a client
// value. requireOwner=true — billing is always org-scoped (a zero-org user has none).
// Auth. A browser caller is the VALIDATED principal (customer path — subject-pinned
// below). An IN-PROC S2S caller carries the verified COMMERCE_SERVICE_TOKEN (the
// metering cap-gate's authorize + the SuperAdmin cap-oversight Forward). The gateway
// 401s a public Bearer that is not an IAM JWT / hk-|pk-|sk- key (the 64-hex service
// token fails JWT parse at the edge), so an EXTERNAL client can NEVER present it here —
// an unauthenticated caller still hits the 403 below. On the S2S path the caller
// legitimately names its own subject, so its query is forwarded as-is (no pin), scoped
// only by the EdgeAuth-controlled X-Org-Id.
cr, ok := resolveCaller(c, true)
s2s := false
owner := cr.owner
if !ok {
if !s2sBillingCall(c) {
return zip.ErrForbidden("sign in to view billing")
}
owner = strings.TrimSpace(c.Org()) // trusted X-Org-Id (never a client value on a public call)
if owner == "" {
return zip.ErrForbidden("sign in to view billing")
}
s2s = true
}
method := c.Method()
if method != http.MethodGet && method != http.MethodPost {
return zip.Errorf(http.StatusMethodNotAllowed, "method not allowed")
}
base, token := commerceCreds()
if token == "" {
// Honest "not configured" (mirrors the Node route's 501 when COMMERCE_TOKEN
// is unset) — the console shows a truthful state, never a fabricated balance.
return zip.Errorf(http.StatusNotImplemented, "billing is not configured on this deployment (COMMERCE_SERVICE_TOKEN unset)")
}
sub := strings.Trim(strings.TrimPrefix(c.Fiber().Params("*"), "/"), "/")
if sub == "" {
return zip.Errorf(http.StatusNotFound, "billing endpoint required")
}
for _, seg := range strings.Split(sub, "/") {
if !isSafeSegment(seg) {
return zip.ErrBadRequest("invalid billing path")
}
}
// THE authorization gate. Forwarding is authorization: the request below carries the
// admin service token, which satisfies commerce's MayMintMoney. So refuse anything the
// console does not actually call — BEFORE the token is attached. Fail closed (404, the
// same answer an unrouted path gives, so this leaks no map of the money surface).
if !isForwardableBilling(method, sub) {
return zip.Errorf(http.StatusNotFound, "not a forwardable billing endpoint")
}
// Scope EVERY request to the caller's OWN subject — query AND write body — so
// commerce's per-tenant isolation can never be crossed from the browser. The
// subject comes from the ONE rule (ai/object.Payer), fed the account the
// credential NAMES (the validated `billing_account` claim) — the same claim the
// ai gate reads, so a top-up credits the SAME account the gate debits. Feeding
// Payer a different credential here than the gate gets is the modern shape of
// the old split: money landing in an account the gate never reads.
inQuery, _ := url.ParseQuery(string(c.Fiber().Request().URI().QueryString()))
var q url.Values
var body []byte
if s2s {
// Trusted S2S caller: forward its query/body VERBATIM — it legitimately names the
// subject (e.g. the metering gate's ?user=<org>&amount=). Scoped by X-Org-Id.
q = inQuery
if method == http.MethodPost {
body = c.Body()
}
} else {
// Browser customer: pin EVERY subject key to the caller's OWN account so commerce's
// per-tenant isolation can never be crossed from the client.
subject := account.Payer(account.Credential{Owner: cr.owner, Name: cr.username, Account: principal.BillingAccount(c)}).Subject()
q = scopedBillingSearch(inQuery, subject)
if method == http.MethodPost {
body = scopedBillingBody(c.Body(), subject)
}
}
raw, status, err := commerceDo(c.Context(), base, token, method, "/v1/billing/"+sub, q, owner, body)
if err != nil {
return zip.Errorf(http.StatusBadGateway, "billing upstream unreachable: %v", err)
}
// A per-tenant money response must NEVER be cached (a stale balance after a
// completion/top-up); commerce answers JSON, so pin JSON + no-store.
c.SetHeader("Content-Type", "application/json")
c.SetHeader("Cache-Control", "no-store, must-revalidate")
return c.Bytes(status, raw)
}
// s2sBillingCall reports whether the request carries the verified COMMERCE_SERVICE_TOKEN
// as its Bearer — a trusted IN-PROC service-to-service caller (the metering cap-gate's
// authorize, the SuperAdmin cap-oversight Forward). It is the SAME secret this bridge
// already forwards WITH, so admitting a caller who already holds it grants no authority it
// could not otherwise wield. Safety rests on the edge: the gateway 401s a public Bearer
// that is not an IAM JWT / hk-|pk-|sk- API key (the 64-hex service token is a JWT
// candidate that fails to parse), so an EXTERNAL client can never reach this handler
// holding it — only in-proc commerceinproc dispatch does. Constant-time compare; the token
// is never logged.
func s2sBillingCall(c *zip.Ctx) bool {
_, token := commerceCreds()
if token == "" {
return false
}
bearer := strings.TrimSpace(strings.TrimPrefix(c.Header("Authorization"), "Bearer "))
return bearer != "" && subtle.ConstantTimeCompare([]byte(bearer), []byte(token)) == 1
}
// IsServiceToken is the exported view of s2sBillingCall — whether the request is a trusted
// in-proc S2S caller bearing the verified COMMERCE_SERVICE_TOKEN. Used by co-resident route
// gates (e.g. the spend-alert admin gate) that must admit the metering cap-gate and the
// SuperAdmin cap-oversight Forward alongside org admins, while refusing a plain member.
func IsServiceToken(c *zip.Ctx) bool { return s2sBillingCall(c) }
+89
View File
@@ -0,0 +1,89 @@
// billing_coresident.go — PinBillingSubject, the subject-pinning middleware that lets
// commerce's OWN billing READ handlers serve co-resident in the unified cloud binary.
//
// WHY IT EXISTS. Co-resident, commerce is EMBEDDED (apps/commerce.go mountCommerce →
// commerce.Embed on the shared zip app), and in prod there is NO standalone commerce
// backend — the in-cluster `commerce` Service selects the cloud pods themselves. So the
// /v1/billing/* bridge (billing.go), which forwards to COMMERCE_URL, has nowhere to send
// a read but back into cloud: the default base (the public api.hanzo.ai edge) re-enters
// the same bridge in an unbounded self-dispatch loop that surfaces as a 502
// ("billing upstream unreachable: Get https://api.hanzo.ai/v1/billing/<path>"). The fix
// is to serve those reads co-resident from the embedded commerce — the same co-resident
// move mountCommerce already makes for GET /v1/billing/plans — so the specific route
// shadows the bridge wildcard (order 100 < 122) and never leaves the process.
//
// WHAT IT GUARANTEES. commerce's read handlers scope to the org by NAMESPACE (from the
// gateway-validated X-Org-Id via iammiddleware) but filter finer scope (the billing
// subject) only from a query param — an UNPINNED ListInvoices returns every user's rows
// in the org namespace. The /v1/billing/* bridge is what pins that subject today; this
// middleware carries the SAME pin onto the co-resident route so the isolation is
// byte-for-byte the shipped behavior. It is the ONE subject rule (account.Payer, the same
// function the ai spend-gate and the top-up resolve), fed the account the credential NAMES
// — so a read scopes to exactly the account the gate debits, never wider.
package account
import (
"net/url"
"github.com/hanzoai/account"
"github.com/hanzoai/cloud/clients/principal"
"github.com/zap-proto/zip"
)
// PinBillingSubject pins every billing subject key in the request query to the VALIDATED
// caller's own subject (dropping ?org), so a co-resident commerce read handler downstream
// can only ever return the caller's OWN rows. It is the co-resident twin of billingData's
// subject-pinning, reusing the SAME resolveCaller → account.Payer rule and the SAME
// scopedBillingSearch, so the two paths scope identically.
//
// Three cases, mirroring billingData exactly:
// - Browser customer (a validated principal with an org): OVERWRITE the subject keys
// with the caller's own subject and drop ?org. The client cannot widen scope.
// - Trusted in-proc S2S (the verified COMMERCE_SERVICE_TOKEN bearer, carrying its own
// X-Org-Id): pass the query through VERBATIM — it legitimately names its own subject,
// scoped by the EdgeAuth-controlled org.
// - Neither: refuse. A bearer-less request with a forged X-Org-Id has no validated
// principal and is fail-closed here, before the read handler runs.
//
// The pin rewrites the request URI's query string AND (on a write) the JSON body in place;
// fasthttp's SetQueryString resets the parsed-args cache and SetBody replaces the body
// bytes, so the handler's later c.Query() / c.Bind() read the pinned values. Pinning the
// body is what keeps a co-resident WRITE handler that reads its subject from the body
// (commerce's CreatePaymentMethod reads customerId from the JSON body) IDOR-safe — query-only
// pinning would leave a client-named customerId/userId in the body untouched.
func PinBillingSubject() zip.Handler {
return func(c *zip.Ctx) error {
inQuery, _ := url.ParseQuery(string(c.Fiber().Request().URI().QueryString()))
cr, ok := resolveCaller(c, true)
if !ok {
// Not a validated customer — admit ONLY a trusted in-proc S2S caller that
// names its own org (same admission billingData makes), leaving its query
// untouched. Everything else is refused before the read runs.
if s2sBillingCall(c) && c.Org() != "" {
return c.Next()
}
return zip.ErrForbidden("sign in to view billing")
}
subject := account.Payer(account.Credential{
Owner: cr.owner,
Name: cr.username,
Account: principal.BillingAccount(c),
}).Subject()
// Pin the subject on BOTH the query AND the write body — the SAME two-helper
// scoping billingData applies (scopedBillingSearch + scopedBillingBody). A
// co-resident WRITE handler that reads its subject from the body (commerce's
// CreatePaymentMethod → customerId) is only IDOR-safe if the body is pinned too.
// scopedBillingBody overwrites the subject keys and preserves every other field
// (card, type, sourceId, …); a non-JSON / empty body is returned unchanged, so a
// GET read carries no body and is unaffected.
c.Fiber().Request().URI().SetQueryString(scopedBillingSearch(inQuery, subject).Encode())
if len(c.Body()) > 0 {
c.Fiber().Request().SetBody(scopedBillingBody(c.Body(), subject))
}
return c.Next()
}
}
+150
View File
@@ -0,0 +1,150 @@
package account
import (
"encoding/json"
"net/http"
"testing"
"github.com/hanzoai/cloud"
luxlog "github.com/luxfi/log"
"github.com/zap-proto/zip"
)
// billing_coresident_test.go — proves PinBillingSubject carries the SAME tenant scoping
// onto a co-resident commerce read handler that billingData applies on the bridge: the
// caller's own subject is pinned into the query (dropping ?org), an unvalidated caller is
// refused before the handler runs, and a trusted in-proc S2S caller passes through
// verbatim. This is what lets commerce's ListInvoices/ListBillingSubscriptions/... serve
// in-process without leaking another subject's rows.
// echoQuery is the downstream stand-in for a commerce read handler: it reports exactly the
// query it observes AFTER the pin, so a test can assert the subject the handler would filter on.
func echoQuery(c *zip.Ctx) error {
return c.JSON(200, map[string]any{
"user": c.Query("user"),
"userId": c.Query("userId"),
"customerId": c.Query("customerId"),
"org": c.Query("org"),
"status": c.Query("status"),
})
}
// echoBody is the downstream stand-in for a commerce WRITE handler (e.g. CreatePaymentMethod)
// that reads its subject from the JSON BODY: it reports the body it observes AFTER the pin, so
// a test can assert the subject the handler would persist and that non-subject fields survive.
func echoBody(c *zip.Ctx) error {
var got map[string]any
if len(c.Body()) > 0 {
_ = json.Unmarshal(c.Body(), &got)
}
return c.JSON(200, got)
}
func pinApp(t *testing.T) *zip.App {
t.Helper()
app := zip.New(zip.Config{Logger: luxlog.New("test")})
// MountAccount installs the identity middleware PinBillingSubject relies on; mounting
// it keeps the probe on the same trust plane as the real co-resident registration.
if err := MountAccount(app, cloud.Deps{Logger: luxlog.New("test"), Brand: "hanzo"}); err != nil {
t.Fatalf("MountAccount: %v", err)
}
app.Get("/probe", PinBillingSubject(), echoQuery)
app.Post("/probe", PinBillingSubject(), echoBody)
return app
}
// TestPinBillingSubject_PinsCallerAndDropsOrg — a validated customer's forged subject
// keys are overwritten with its OWN subject and ?org is dropped, exactly like the bridge.
func TestPinBillingSubject_PinsCallerAndDropsOrg(t *testing.T) {
app := pinApp(t)
code, body := callH(t, app, http.MethodGet,
"/probe?userId=victim&customerId=victim&user=victim&org=othercorp&status=open", alice, "")
if code != http.StatusOK {
t.Fatalf("want 200, got %d (%s)", code, body)
}
var got map[string]string
if err := json.Unmarshal(body, &got); err != nil {
t.Fatalf("bad body: %s", body)
}
for _, k := range billingSubjectKeys {
if got[k] != "acme" { // alice/acme resolves to the org subject "acme"
t.Fatalf("handler must see %s=acme (caller's own subject), got %q", k, got[k])
}
}
if got["org"] != "" {
t.Fatalf("org must be dropped, handler saw org=%q", got["org"])
}
if got["status"] != "open" {
t.Fatalf("non-subject filter must survive, got status=%q", got["status"])
}
}
// TestPinBillingSubject_PinsBodyForWrites — a POST whose JSON body names a FOREIGN subject
// (customerId/userId/user) has every subject key overwritten with the caller's OWN subject
// before the handler binds it, while non-subject fields survive. This is the boundary
// commerce's CreatePaymentMethod (which reads customerId from the body) relies on to be
// IDOR-safe co-resident — byte-identical to billingData's scopedBillingBody on the bridge.
func TestPinBillingSubject_PinsBodyForWrites(t *testing.T) {
app := pinApp(t)
code, body := callH(t, app, http.MethodPost, "/probe", alice,
`{"customerId":"victim","userId":"victim","user":"victim","card":{"last4":"4242"}}`)
if code != http.StatusOK {
t.Fatalf("want 200, got %d (%s)", code, body)
}
var got map[string]any
if err := json.Unmarshal(body, &got); err != nil {
t.Fatalf("bad body: %s", body)
}
for _, k := range billingSubjectKeys {
if got[k] != "acme" { // alice/acme resolves to the org subject "acme"
t.Fatalf("handler must see body %s=acme (caller's own subject), got %v", k, got[k])
}
}
card, ok := got["card"].(map[string]any)
if !ok || card["last4"] != "4242" {
t.Fatalf("non-subject body field must survive the pin, got card=%v", got["card"])
}
}
// TestPinBillingSubject_RefusesUnvalidated — a forged X-Org-Id with NO validated
// X-User-Id (and no service token) is refused before the read handler runs: no
// cross-tenant billing read is possible.
func TestPinBillingSubject_RefusesUnvalidated(t *testing.T) {
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := pinApp(t)
code, _ := callH(t, app, http.MethodGet, "/probe?userId=victim",
map[string]string{"X-Org-Id": "victim"}, "")
if code != http.StatusForbidden {
t.Fatalf("unvalidated caller: want 403, got %d", code)
}
}
// TestPinBillingSubject_S2SForwardsVerbatim — the trusted in-proc S2S caller (verified
// COMMERCE_SERVICE_TOKEN + its own X-Org-Id, no validated user) is admitted and its query
// is left UNTOUCHED, so it can name its own subject (the cap-gate's authorize read).
func TestPinBillingSubject_S2SForwardsVerbatim(t *testing.T) {
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := pinApp(t)
code, body := callH(t, app, http.MethodGet, "/probe?user=acme&status=open",
map[string]string{"Authorization": "Bearer svc-tok", "X-Org-Id": "acme"}, "")
if code != http.StatusOK {
t.Fatalf("S2S: want 200, got %d (%s)", code, body)
}
var got map[string]string
_ = json.Unmarshal(body, &got)
if got["user"] != "acme" || got["status"] != "open" {
t.Fatalf("S2S query must pass through verbatim, got %+v", got)
}
}
// TestPinBillingSubject_S2SNoOrgRefused — the service token with NO X-Org-Id has no org
// to scope the privileged read and is refused (matches billingData's s2s org requirement).
func TestPinBillingSubject_S2SNoOrgRefused(t *testing.T) {
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := pinApp(t)
code, _ := callH(t, app, http.MethodGet, "/probe",
map[string]string{"Authorization": "Bearer svc-tok"}, "")
if code != http.StatusForbidden {
t.Fatalf("S2S without X-Org-Id: want 403, got %d", code)
}
}
+296
View File
@@ -0,0 +1,296 @@
package account
import (
"encoding/json"
"github.com/hanzoai/account"
"io"
"net/http"
"net/http/httptest"
"net/url"
"sync"
"testing"
)
// billing_test.go — the per-tenant billing bridge (billing.go). Proves the tenant
// scoping that prevents cross-tenant billing reads (the Go port of console's
// billing-scope.test.ts) AND the IDOR-safe handler forwarding.
// ── pure scoping ─────────────────────────────────────────────────────────────
// TestBillingSubject proves the top-up subject is resolved through the ONE rule
// (ai/object.Payer) — so a top-up credits the SAME account the ai gate debits and
// the console reads. The signup org bills per-person (matching the gate), which is
// the whole fix: money and gate land on one account.
func TestBillingSubject(t *testing.T) {
cases := []struct{ org, name, want string }{
{"acme", "alice", "acme"}, // real org: any member bills the ONE org account
{"hanzo", "Dave", "hanzo/dave"}, // signup org: each person bills their OWN account
{"hanzo", "z", "hanzo/z"}, // another signup person — their own account
{"hanzo", "", "hanzo"}, // no name (org-owned principal) → org pool
{"Hanzo", "Z", "hanzo/z"}, // folded
{"", "x", ""}, // no org → empty subject (cannot bill)
}
for _, c := range cases {
got := account.Payer(account.Credential{Owner: c.org, Name: c.name}).Subject()
if got != c.want {
t.Fatalf("Payer(%q,%q).Subject(): want %q, got %q", c.org, c.name, c.want, got)
}
}
}
// TestBillingSubject_IgnoresLegacyEnv locks that the killed allowlist envs have NO
// effect: nothing reads them. Set to values that WOULD have flipped every
// resolution — the subject is unchanged. This is the console/top-up half of the
// same proof ai carries (one rule, no config), so the view and the gate can never
// disagree, and the deleted CR env is a genuine no-op.
func TestBillingSubject_IgnoresLegacyEnv(t *testing.T) {
t.Setenv("PERSONAL_BILLING_ORGS", "hanzo,acme") // would have split acme per-user
t.Setenv("ORG_BILLING_ORGS", "hanzo") // would have pooled the signup org
cases := []struct{ org, name, want string }{
{"hanzo", "z", "hanzo/z"}, // env cannot pool the signup org
{"acme", "alice", "acme"}, // env cannot split a real org per-user
{"maxpower", "dave", "maxpower"}, // untouched
}
for _, c := range cases {
got := account.Payer(account.Credential{Owner: c.org, Name: c.name}).Subject()
if got != c.want {
t.Fatalf("legacy env must be ignored: Payer(%q,%q).Subject() want %q, got %q", c.org, c.name, c.want, got)
}
}
}
func TestScopedBillingSearch_PinsSubjectDropsOrgKeepsRest(t *testing.T) {
in := url.Values{}
in.Set("userId", "victim") // forged subject — must be OVERWRITTEN
in.Set("customerId", "victim") // forged subject — must be OVERWRITTEN
in.Set("user", "victim") // forged subject — must be OVERWRITTEN
in.Set("org", "othercorp") // must be DROPPED (cannot widen scope)
in.Set("currency", "usd") // non-subject — must PASS THROUGH
in.Set("start", "2026-01-01") // non-subject — must PASS THROUGH
out := scopedBillingSearch(in, "acme")
for _, k := range billingSubjectKeys {
if out.Get(k) != "acme" {
t.Fatalf("subject key %s must be pinned to acme, got %q", k, out.Get(k))
}
}
if out.Has("org") {
t.Fatal("org must be dropped")
}
if out.Get("currency") != "usd" || out.Get("start") != "2026-01-01" {
t.Fatalf("non-subject params must pass through, got %v", out)
}
}
func TestScopedBillingBody(t *testing.T) {
// a forged subject in a JSON object write is OVERWRITTEN; other fields survive.
out := scopedBillingBody([]byte(`{"userId":"victim","amount":500,"note":"x"}`), "acme")
var obj map[string]any
if err := json.Unmarshal(out, &obj); err != nil {
t.Fatalf("scoped body is not JSON: %v", err)
}
for _, k := range billingSubjectKeys {
if obj[k] != "acme" {
t.Fatalf("body subject key %s must be pinned to acme, got %v", k, obj[k])
}
}
if obj["amount"].(float64) != 500 || obj["note"] != "x" {
t.Fatalf("non-subject body fields must survive, got %v", obj)
}
// non-object / empty bodies pass through untouched (never invent a body).
for _, raw := range []string{"not json", `[1,2,3]`, `"scalar"`, ""} {
if got := string(scopedBillingBody([]byte(raw), "acme")); got != raw {
t.Fatalf("non-object body %q must pass through, got %q", raw, got)
}
}
}
// ── handler (IDOR + forwarding) ──────────────────────────────────────────────
// fakeBilling records exactly what the handler forwarded to commerce.
type fakeBilling struct {
mu sync.Mutex
path string
query url.Values
body map[string]any
org string
auth string
}
func (f *fakeBilling) server(t *testing.T) *httptest.Server {
t.Helper()
srv := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
f.mu.Lock()
f.path, f.query = r.URL.Path, r.URL.Query()
f.org, f.auth = r.Header.Get("X-Org-Id"), r.Header.Get("Authorization")
if raw, _ := io.ReadAll(r.Body); len(raw) > 0 {
_ = json.Unmarshal(raw, &f.body)
}
f.mu.Unlock()
w.Header().Set("Content-Type", "application/json")
_, _ = io.WriteString(w, `{"balance":123}`)
}))
t.Cleanup(srv.Close)
return srv
}
func TestBilling_RequiresValidatedPrincipal(t *testing.T) {
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := mountApp(t, "http://iam.invalid", "", "")
// A forged X-Org-Id with NO validated X-User-Id is the exact forge — refuse it
// BEFORE any commerce call (no cross-tenant ledger read on a victim org).
code, _ := callH(t, app, http.MethodGet, "/v1/billing/balance", map[string]string{"X-Org-Id": "victim"}, "")
if code != http.StatusForbidden {
t.Fatalf("no validated principal: want 403, got %d", code)
}
}
func TestBilling_NotConfiguredWithoutToken(t *testing.T) {
t.Setenv("COMMERCE_SERVICE_TOKEN", "")
app := mountApp(t, "http://iam.invalid", "", "")
code, _ := callH(t, app, http.MethodGet, "/v1/billing/balance", alice, "")
if code != http.StatusNotImplemented {
t.Fatalf("no commerce token: want 501, got %d", code)
}
}
func TestBilling_ScopesQueryToCallerAndForwards(t *testing.T) {
f := &fakeBilling{}
t.Setenv("COMMERCE_URL", f.server(t).URL)
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := mountApp(t, "http://iam.invalid", "", "")
// alice/acme with a FORGED ?userId=victim & ?org=othercorp: the handler must pin
// every subject key to the caller's own subject (acme) and drop org.
code, body := callH(t, app, http.MethodGet,
"/v1/billing/invoices?userId=victim&customerId=victim&org=othercorp&status=open", alice, "")
if code != http.StatusOK {
t.Fatalf("want 200, got %d (%s)", code, body)
}
if f.path != "/v1/billing/invoices" {
t.Fatalf("forwarded path: want /v1/billing/invoices, got %q", f.path)
}
for _, k := range billingSubjectKeys {
if f.query.Get(k) != "acme" {
t.Fatalf("commerce must receive %s=acme (the caller's subject), got %q", k, f.query.Get(k))
}
}
if f.query.Has("org") {
t.Fatal("org must be dropped before commerce")
}
if f.query.Get("status") != "open" {
t.Fatalf("non-subject filter must pass through, got %q", f.query.Get("status"))
}
if f.org != "acme" || f.auth != "Bearer svc-tok" {
t.Fatalf("S2S must send X-Org-Id=acme + the service token, got org=%q auth=%q", f.org, f.auth)
}
}
func TestBilling_ScopesWriteBodyToCaller(t *testing.T) {
f := &fakeBilling{}
t.Setenv("COMMERCE_URL", f.server(t).URL)
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := mountApp(t, "http://iam.invalid", "", "")
// a POST with a forged userId in the body must be overwritten to acme.
code, _ := callH(t, app, http.MethodPost, "/v1/billing/spend-alerts", alice,
`{"userId":"victim","threshold":5000}`)
if code != http.StatusOK {
t.Fatalf("want 200, got %d", code)
}
if f.body["userId"] != "acme" {
t.Fatalf("write-body subject must be pinned to acme, got %v", f.body["userId"])
}
if f.body["threshold"].(float64) != 5000 {
t.Fatalf("non-subject body field must survive, got %v", f.body["threshold"])
}
}
func TestBilling_RejectsTraversalSegment(t *testing.T) {
f := &fakeBilling{}
t.Setenv("COMMERCE_URL", f.server(t).URL)
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := mountApp(t, "http://iam.invalid", "", "")
// Every traversal form — literal `..`, encoded slash (`%2f`), encoded dot
// (`%2e%2e`), matrix param (`;`) — must be REFUSED (400) and must NEVER reach
// commerce. Without the percent-escape rejection, `invoices/..%2fadmin` decodes
// downstream to `/v1/admin`, tunneling PAST /v1/billing into another surface.
for _, p := range []string{
"/v1/billing/invoices/../admin", // literal ..
"/v1/billing/invoices/..%2fadmin", // encoded slash (%2f)
"/v1/billing/%2e%2e/admin", // encoded dots (%2e%2e)
"/v1/billing/invoices;statement", // matrix param (;)
} {
code, _ := callH(t, app, http.MethodGet, p, alice, "")
if code != http.StatusBadRequest {
t.Fatalf("traversal %q: want 400, got %d", p, code)
}
}
if f.path != "" {
t.Fatalf("a traversal must never reach commerce, but upstream saw %q", f.path)
}
}
// ── S2S service-token admission (the auth fix; 4 security invariants) ─────────
// Invariant #4 — THE SECURITY GATE: a public/unauthenticated caller (no validated
// principal AND not the service token) STILL gets 403 on the spend-alert routes, incl.
// a WRONG bearer. The fix must NEVER open billing to the world.
func TestBilling_S2S_PublicStill403(t *testing.T) {
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := mountApp(t, "http://iam.invalid", "", "")
for _, path := range []string{
"/v1/billing/spend-alerts",
"/v1/billing/spend-alerts/authorize?user=acme&amount=1",
} {
// forged X-Org-Id, no validated principal, no service token
if code, body := callH(t, app, http.MethodGet, path, map[string]string{"X-Org-Id": "victim"}, ""); code != http.StatusForbidden {
t.Fatalf("public caller to %s: want 403, got %d (%s)", path, code, body)
}
}
// a WRONG bearer is still just a public caller → 403
if code, _ := callH(t, app, http.MethodGet, "/v1/billing/spend-alerts/authorize?user=acme&amount=1",
map[string]string{"X-Org-Id": "acme", "Authorization": "Bearer not-the-token"}, ""); code != http.StatusForbidden {
t.Fatalf("wrong bearer: want 403")
}
}
// The trusted in-proc S2S caller (verified COMMERCE_SERVICE_TOKEN + X-Org-Id) is admitted
// and its authorize query is forwarded to commerce VERBATIM (a trusted caller names its
// own subject), scoped by X-Org-Id — this is what lets the cap gate reach AuthorizeSpendCap.
func TestBilling_S2S_ServiceTokenForwardsVerbatim(t *testing.T) {
f := &fakeBilling{}
t.Setenv("COMMERCE_URL", f.server(t).URL)
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := mountApp(t, "http://iam.invalid", "", "")
code, body := callH(t, app, http.MethodGet,
"/v1/billing/spend-alerts/authorize?user=acme&amount=100&project=P",
map[string]string{"Authorization": "Bearer svc-tok", "X-Org-Id": "acme"}, "")
if code != http.StatusOK {
t.Fatalf("S2S authorize: want 200, got %d (%s)", code, body)
}
if f.path != "/v1/billing/spend-alerts/authorize" {
t.Fatalf("forwarded path = %q", f.path)
}
// VERBATIM: the S2S caller's ?user/?amount/?project reach commerce un-pinned.
if f.query.Get("user") != "acme" || f.query.Get("amount") != "100" || f.query.Get("project") != "P" {
t.Fatalf("S2S query must forward verbatim, got %v", f.query)
}
if f.org != "acme" || f.auth != "Bearer svc-tok" {
t.Fatalf("S2S must send X-Org-Id=acme + service token, got org=%q auth=%q", f.org, f.auth)
}
}
// S2S with the verified token but NO X-Org-Id → 403 (no org to scope the privileged
// forward to; never fall back to a client value).
func TestBilling_S2S_NoOrg403(t *testing.T) {
t.Setenv("COMMERCE_SERVICE_TOKEN", "svc-tok")
app := mountApp(t, "http://iam.invalid", "", "")
if code, _ := callH(t, app, http.MethodGet, "/v1/billing/spend-alerts/authorize?user=acme&amount=1",
map[string]string{"Authorization": "Bearer svc-tok"}, ""); code != http.StatusForbidden {
t.Fatalf("S2S without X-Org-Id: want 403")
}
}

Some files were not shown because too many files have changed in this diff Show More