Release initial batch of Halo Box Playbooks

[danielholanda]

Releasing the following playbooks.

Core (5)

• comfyui-image-gen
• lmstudio-rocm-llms
• n8n-automation-gpt-oss
• pytorch-rocm-llms
• vscode-qwen3-coder

---

Supplemental (10)

• amd-sync
• gaia-agents
• lemonade-getting-started
• llama-factory-finetuning
• ollama-getting-started
• open-webui-chat
• pytorch-finetuning
• pytorch-kernels
• speech2speech-translation
• unsloth-llms-finetuning

---

Remaining (4) — will be pushed through separate PR's

• cvml
• openclaw-lemonade-server
• vllm-inference
• clustering-rpc-server

[sreeram-11]

@danielholanda,

I added a commit here that fixes the n8n --version check on the Linux Halo runners.

On Linux Halo runners, there were two Node.js installations:

1. /usr/bin/node -> v24.15.0 (package-managed Node.js installation from NodeSource)
2. /usr/local/bin/node -> v20.19.2 (older manual Node.js installation)

Background

• The GitHub Actions shell was picking up /usr/local/bin/node first because /usr/local/bin appears before /usr/bin in PATH
• So earlier, n8n --version was passing because it was using the n8n installation associated with the older Node.js v20.19.2
• After removing the older manual Node.js installation, the runner correctly used Node.js v24.15.0
• However, the n8n installation for this Node.js setup is located at: /home/user/.npm-global/bin/n8n
• The GitHub Actions shell did not include this directory in PATH, so n8n --version started failing even though n8n was installed

Changes

• Cleaned up the Linux Halo runners to use the package-managed Node.js installation from NodeSource (Node.js v24.15.0)
• Removed the older manual Node.js installation from /usr/local/bin
• Updated the n8n test to include the npm global bin directory in PATH before running n8n

Validation

• Confirmed the Linux Halo runners now use Node.js v24.15.0.
• Confirmed the n8n test can find and run n8n --version successfully.

[sreeram-11]

#326 (comment)

• This commit was already merged into main via Adding .npm-global/bin to PATH before calling n8n #359.
• As a result, it does not appear separately in this PR.
• The changes are already present in main, so no duplicate is shown in this branch.