Skip to content

Fix native installer diagnostics and add cloud session handoff - #9

Draft
zeekay wants to merge 3 commits into
mainfrom
feat/cloud-parity
Draft

zeekay wants to merge 3 commits into
mainfrom
feat/cloud-parity

Conversation

@zeekay

@zeekay zeekay commented Oct 21, 2026

Copy link
Copy Markdown
Member

Fix installer output and tool naming, and add hanzo doctor for executable, authentication, GPU and optional release-integrity checks. The installer supports strict provenance verification and preserves installed binaries on verification failure. CLI delegation uses hanzo-cli, reserving hanzo-node for the network node.

Also adds authenticated cloud-session steering and follow-up handoff tracking. This is an incremental cloud workflow improvement, not full Claude feature parity.

Validation: 387 Rust unit tests, three cloud parser tests, strict clippy, shell installer fixtures, real Gen provenance verification, and live doctor authentication/GPU checks passed. Production handoff E2E currently detects that the API steering route has not reached the serving deployment; deployment validation remains required.

Release: 8.5.754. The hanzo.sh coordinator update depends on this shared installer landing first.

Testing: 385 unit tests and three cloud command tests passed; strict clippy passed with the compiler cache wrapper disabled. New production steering E2E is opt-in and awaiting API deployment.

Risk: Steering needs the matching API release; machine, timeout and effort controls use existing API fields.

How to revert: Revert this commit and publish the previous CLI behavior.
Add read-only hanzo doctor checks and strict provenance verification. Reserve hanzo-node for the network node and use hanzo-cli for control delegation. Release 8.5.754.

Testing: 387 Rust unit tests and three cloud parser tests passed; strict clippy passed; installer fixtures passed under sh and bash; real Gen strict provenance verified with GitHub CLI 2.102.1.

Risk: installer alias migration removes only the known legacy hanzo-node symlink. Strict mode requires authenticated compatible gh and available release attestations; normal mode continues to require checksums and reports unavailable provenance.

How to revert: revert this commit and republish the previous installer; install CLI v8.5.753 if necessary.
Testing: all 13 existing installer tests and strict sh/bash fixtures pass. Risk: output-only correction for verified artifacts. How to revert: revert this commit.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant