zeekayandHanzo Dev 04cb92929b fix: call the pipeline at the address it actually lives
hanzoai/ci keeps the reusable at .github/workflows/build.yml — the one path
both planes resolve, since github.com reads a reusable only from there and the
forge reads it too. The v1 tag moved with it, so a caller still naming
.hanzo/workflows/build.yml asks for a blob that is not in the tree:

  InsertRun: read hanzoai/ci@v1:.hanzo/workflows/build.yml: object does not exist

The caller itself stays at .hanzo/workflows/cicd.yml on purpose: github.com has
no runner for these labels, so a caller placed there could never be scheduled.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 01:14:24 -07:00

decimal

Exact, arbitrary-precision fixed-point decimal for Go. A value is coefficient × 10⁻ˢᶜᵃˡᵉ with a big.Int coefficient — no precision ceiling, no float, immutable.

Unlike int64/uint64 decimal & money libraries (which cap around 19 digits — about $9.20 at 18 decimals), this holds a fiat cent and an 18-decimal on-chain wei balance with equal exactness. 0.1 + 0.2 is exactly 0.3.

d := decimal.MustParse("6.60")
cost := decimal.New(200, 0).Mul(d).Quo(decimal.New(1_000_000, 0), 18) // 200 tokens @ $6.60/1M
cost.String() // "0.00132"  (never floored to 0)

The numeric core beneath hanzoai/money. Stdlib only. MIT OR Apache-2.0, at your option — per HIP-0137.

S
Description
Exact big.Int fixed-point decimal for Go — no precision ceiling, no float
Readme
51 KiB
Languages
Go 100%