Skip to content

fix(amd395): activate compatible native versions - #108

Merged
rjckkkkk merged 1 commit into
amd395-linuxfrom
sync/amd395-compatible-lifecycle
Aug 11, 2026
Merged

fix(amd395): activate compatible native versions#108
rjckkkkk merged 1 commit into
amd395-linuxfrom
sync/amd395-compatible-lifecycle

Conversation

@rjckkkkk

Copy link
Copy Markdown
Collaborator

Summary

  • sync the compatible native engine lifecycle fix from fix(engine): activate compatible native versions #107 onto the AMD395 Linux delivery branch
  • default engine ensure now reuses and activates an imported Catalog-compatible llama.cpp build
  • deployment accepts verified compatible inventory and prefers the active binary
  • exact installed versions still take precedence over compatible fallbacks

Validation

  • go test ./... -count=1
  • go vet ./...
  • go test -race ./internal/engine ./internal/knowledge ./internal/hal ./cmd/aima -count=1
  • Baiying AMD395: imported b9637 against Catalog b9330, default ensure reused and activated the same inventory ID, deploy launched that exact dist binary, health/chat returned HTTP 200, status reached running/ready/healthy, and isolated process/port/data were cleaned

After merge, the amd395-linux push workflow must produce the partner package from the merge commit.

@rjckkkkk
rjckkkkk merged commit 2cf787c into amd395-linux Aug 11, 2026
2 checks passed
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