CLI: Update Hypeman Go SDK to da50c337d8e3c05c89a07e9b0b25636f1b50e526

[kernel-internal]

This PR updates the Hypeman Go SDK dependency to the latest version.

SDK Update

• Updated hypeman-go to da50c337d8e3c05c89a07e9b0b25636f1b50e526

Coverage Analysis

A full enumeration of SDK methods and CLI commands was performed. No coverage gaps were found.

All 63 methods in api.md have a CLI command, and every field of every *Params struct (including nested param types such as IngressRuleParam, HealthCheckParam, VolumeMountParam, AutoStandbyPolicyParam, SnapshotCompressionConfigParam, MemoryReclaimRequestParam and CreatePushRequestParam) maps to an existing flag, positional argument, or mount-spec segment. openapi.yaml marks no endpoint with x-cli-skip, so nothing was excluded on that basis. client.Instances.Get, client.Instances.Stat, client.Volumes.NewFromArchive, client.Health.Check, client.Instances.Logs and client.Builds.Events are reached internally or through streaming variants, as documented in the mapping guide.

The API surface is unchanged by this bump: da50c33 differs from the previously pinned 134587a only in go.mod and go.sum. Both report configured_endpoints: 63 with an identical method list, and da50c33 is the merge of the 2026-10-07 vulnerability remediation, which carries transitive dependency updates only.

Still pinned to main, so two generated symbols remain absent

As with the previous bump, this pin is a main commit and therefore does not include the "Windows hypervisor primitives" generation that lives on the SDK's next branch. Two symbols the CLI needs still do not exist in the generated bindings:

Missing symbol	Used by
InstanceLogsParamsSourceSwtpm	hypeman logs --source swtpm
InstanceGPU.DevicePath	formatGPU in hypeman ps

openapi.yaml on main still specifies both (the source enum is [app, vmm, hypeman, swtpm], and device_path is on the GPU schema), so the API supports them and only the generated bindings lag. The existing workarounds on this branch are therefore retained unchanged:

• source is a string-backed enum, so the local instanceLogsSourceSwtpm constant serializes identically.
• device_path arrives in JSON.ExtraFields, so formatGPU decodes it from the raw JSON.

Both are commented at the call site and should return to typed access once next merges to main.

Verification

go build ./..., go vet ./... and go test ./... all pass. Because go mod tidy pruned 100+ now-unneeded go.sum entries, cross-compilation was also checked for windows/amd64, darwin/arm64 and linux/arm64, and go mod verify reports all modules verified.

This branch also carries a merge of main (resolving a go.sum conflict). History was preserved rather than rebased, so no force push was needed and the earlier work on the branch is intact.

Triggered by: kernel/hypeman-go@da50c33
Reviewer: @ulziibay-kernel

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 22e9c31. Configure here.}

[cursor]

Insufficient docker dependency pin

Medium Severity

go.mod now pins github.com/docker/docker to a pseudo-version instead of upgrading go-containerregistry. That keeps the old docker client on the graph, so a pin in this range may not include the docker cp fix for GHSA-rg2x-37c3-w2rh.

 

^{Triggered by learned rule: Prefer upgrading go-containerregistry over docker/docker replace pins}

^{Reviewed by Cursor Bugbot for commit 22e9c31. Configure here.}