mirror of
https://github.com/hanzoai/cli.git
synced 2026-10-30 15:00:27 +00:00
zeekay
6d40e148af
`.spec-lock` was required to name a hanzoai/cloud release TAG, and a test said so. That put a second notion of "the document" in a repo whose whole design is that there is one. The document is emitted from cloud's SOURCE; a tag names a service release, which lags it. Measured today: cloud's newest tag sat two hours and four commits behind a main carrying 256 newly typed operations, so the nightly re-pin — which reads the newest tag — would have moved this repo's pin BACKWARDS onto a document that describes less than the one already committed. The tag was never the guarantee it was read as either: a tag is cut before production deploys it, which the prose beside the rule admitted in the same breath. So the lock names a COMMIT, the nightly reads main, and the deploy question is answered by the only thing that can answer it — the live evidence. That question needed a name, because the gate had been answering it with the wrong one. A generated coordinate exists because the document declares it, and the chain digests refuse a hand-edited generated.rs, so "the host denies it and NO document claims it" could never be true of one. Reporting the three routes cloud's main declares and production has not deployed yet as PHANTOMs pointed a hard failure at this repo for someone else's deploy schedule, and buried the real phantom class — the hand-written literals, which keep the name and keep failing hard. AHEAD counts them, pins them at 3, and falls on its own when cloud ships. Re-pinned onto cloud@f1d31fc1e: 2369 -> 2378 operations, 2326 -> 2335 commands, 772 -> 811 typed. The --data census moved 539 -> 524, and reading only that number tells the wrong story: 93 of the 108 no-schema writes it lost are `ai` alone (95 -> 2), which cloud did not TYPE but did finally publish — their bodies are stated and freeform, which is why freeform rose 10 -> 103. Seventeen write commands genuinely gained typed flags. CONTRADICTED is 0 for the first time; the six stale /v1/ai nouns left the document with the door that published them. UNFALSIFIABLE rises 90 -> 92 because production's table stopped naming /v1/agent at all. Prose may name a scheme now, not only a host: banning the characters `://` banned the word "otpauth://", which cloud's MFA enrollment hands back for a person to render as a QR code. What may never appear is an authority after the scheme, which is the part a client could dial.
26 lines
471 B
JSON
26 lines
471 B
JSON
{
|
|
"name": "@hanzo/cli",
|
|
"version": "1.9.47",
|
|
"description": "Hanzo CLI \u2014 manage Hanzo AI cloud resources",
|
|
"license": "MIT",
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "git+https://github.com/hanzoai/cli.git"
|
|
},
|
|
"homepage": "https://hanzo.ai",
|
|
"bin": {
|
|
"hanzo": "bin/hanzo.js"
|
|
},
|
|
"files": [
|
|
"bin/",
|
|
"install.js",
|
|
"README.md"
|
|
],
|
|
"scripts": {
|
|
"postinstall": "node install.js"
|
|
},
|
|
"engines": {
|
|
"node": ">=18"
|
|
}
|
|
}
|