github-slack-development-digest: add Linux CI tests - #618
Open
lucbruni-amd wants to merge 6 commits into
Open
Conversation
Add hidden CI test blocks and Linux platform metadata for the GitHub-to-Slack digest playbook, following the n8n and lemonade test patterns. Coverage: prerequisite CLI checks (lemonade, node, npm, uv, agent-canvas), a Lemonade model chat health check, GitHub and Slack MCP package resolution, and a full agent-canvas launch that verifies the agent-server backend on 18000/server_info (not just the 8000 ingress, which returns 200 even when the backend is down), plus GPU cleanup. Scope to Linux only. The agent-canvas agent-server does not start via the playbook's direct npm path on Windows (reproduced on the halo runner: "The system cannot find the file specified"), and the vendor's own Windows path uses Docker instead. Windows is therefore removed from the supported, tested, required, and published platform maps and from the README.
Use max_tokens 64 in the lemonade-chat CI test so it mirrors the exact chat request shown to users in step 2 of the playbook.
Added new platforms for testing and requirements in the playbook.
sreeram-11
reviewed
Jul 27, 2026
sreeram-11
reviewed
Jul 27, 2026
sreeram-11
reviewed
Jul 27, 2026
Co-authored-by: Sreeram <s.sreeram.amd@gmail.com>
Collaborator
|
Can you please verify whether Agent Canvas is supported on Windows using Docker, and add the instructions to the playbook if it is supported? Please also address any formatting issues in the playbook. One thing I noticed is that the README.md content in this playbook is not formatted consistently with the other playbooks. In the other playbooks, sentences are generally split onto separate lines for readability and cleaner diffs. Could you please update this playbook to follow the same formatting style? |
sreeram-11
marked this pull request as ready for review
July 27, 2026 06:36
Collaborator
|
Is Windows intended to work for this playbook? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds hidden CI test blocks and Linux platform metadata to the GitHub-to-Slack Development Digest playbook, following the n8n and lemonade test patterns. Addresses #600 (sibling of #601 / #615 for the OpenHands getting-started playbook).
Scoped to Linux only: the agent-canvas agent-server does not start via the playbook's direct
npmpath on Windows (see below), so Windows is removed from the platform maps and README.What the tests cover
lemonade-version,node-npm-version,uv-version: prerequisite CLIs are present (installs are one-time runner setup, not done in CI)lemonade-chat: Lemonade serves the model (present + downloaded) and answers a deterministic chat request (mirrors playbook step 2,max_tokens: 64)agent-canvas-version: the agent-canvas CLI is on PATHagent-canvas-start: fullagent-canvaslaunch, asserts the agent-server backend is healthy on18000/server_info(not just the8000ingress, which returns 200 even when the backend is down)mcp-packages-resolve: the GitHub and Slack MCP packages resolve from the npm registry (running them needs real tokens plus UI, so out of CI scope)lemonade-unload: frees the GPU poolWhy Linux only
On a Windows halo runner,
agent-canvasstarts the ingress/static/automation processes but the agent-server exits immediately (The system cannot find the file specified), leaving/server_infoand/healthreturning 502 while/still returns 200. The vendor's own Windows quickstart uses the Docker sandbox rather than the directnpmpath this playbook documents. Windows is therefore dropped fromsupported,tested,required, andpublishedplatform maps and the Windows README blocks removed.Verification (self-hosted runners, halo-02 Linux / halo-0 Windows)
18000/server_info= 200, exit 0)8000/probe would false-pass with a dead backend, so the test now probes18000/server_infoset -euo pipefailvalidate_playbooks.py: 0 errorsTest plan
Qwen3.6-35B-A3B-GGUFon the target runners