ci : separate webui from server

[CISC]

Reduce CI congestion by separating WebUI from Server CI.

Due to the sequential nature of WebUI jobs it's prone to clog the CI queue, make sure it's only triggered on WebUI and Server test changes.

[allozaur]

Thanks @CISC!

[coder543]

npm run test:server seems broken. I believe that script was removed in #17969.

Codex summary of the issue

CI is failing because npm run test:server is being invoked, but the WebUI package.json no longer defines a test:server
script.

Timeline (all times in +0100):

• 3034836 (PR webui: Improve copy to clipboard with text attachments #17969, 2025-12-16 07:38:46) removed "test:server": "vitest --project=server" from tools/server/webui/package.json and updated the main test script to run test:unit instead.
• d674212 (PR ci : separate webui from server #18072, 2025-12-16 08:17:26) created the new .github/workflows/server-webui.yml and it runs npm run test:server.

Net: #17969 removed the script; #18072 exposed the mismatch by calling it in the new workflow.

[CISC]

@coder543 Indeed, that's unfortunate.

@allozaur Know what this failure is about (failed before tests)?
https://github.com/ggml-org/llama.cpp/actions/runs/20259739616/job/58199483562

[CISC]

@allozaur Can we forgo the dependent jobs altogether? I can't see why all the webui jobs can't just be steps in a single job and server-build running independently?

[allozaur]

@allozaur Can we forgo the dependent jobs altogether? I can't see why all the webui jobs can't just be steps in a single job and server-build running independently?

Sure, initial intention was to have easier tracking for points od failure on the CI, but time has shown that it might be better if we forge the jobs.