fix: wire qwenpaw worker image defaults#1040
Conversation
|
CI attribution for run #1664:
The branch remains unchanged. Local |
|
CI attribution for head
The matrix therefore stops before any shard or PR-specific integration test runs. The remaining red checks are the fork-secret bootstrap issue addressed by #1026; no additional branch change is indicated by these logs. |
|
The deployment value is high because selecting the QwenPaw runtime must resolve to the dedicated Worker image across Docker, Kubernetes, and Sandbox backends. The current six-commit branch conflicts with main and spans nine files. Please rebase and squash the series into one coherent change, remove unrelated history, and verify that Helm values, controller configuration, Bash and PowerShell installers, and Sandbox defaults all render the same image contract. |
Summary
Root cause
QwenPaw runtime selection was added in #998, and each backend already has a QwenPaw-specific image branch. However, the controller config constructors never populated
QwenPawWorkerImage, and Helm never suppliedAGENTTEAMS_QWENPAW_WORKER_IMAGE. Aruntime: qwenpawWorker without an explicitspec.imagetherefore fell through to the default OpenClaw Worker image.The Embedded install path also omitted the QwenPaw image override, so
make install,make install-interactive, andmake install-embeddedcould build the local image without making it available to the controller. The installer keeps this image opt-in: normal installs do not add a QwenPaw pull until a release image default is defined.Verification
go test ./...inhiclaw-controller/with Go 1.25.0helm lint helm/hiclaw/with Helm 3.14.0helm templatewith a custom QwenPaw repository/tag, parsed as YAML to assert the exact controller environment valuebash -n install/hiclaw-install.shinstall/hiclaw-install.ps1make -nassertions forinstall,install-interactive, andinstall-embeddedgit diff --check origin/main...HEAD