No description

sjcoetzeesj-coder 0717400bb0 fix(cipc): say plainly when search runs where it cannot ... CIPC/BizPortal search drives a real Chrome session through agent-browser to log into BizPortal and scrape the result pane. That toolchain exists only on the Windows dev machine; the Coolify image is a Linux container with no browser tooling (the Dockerfile header already says so). Nothing detected that up front, so a search on the deployed URL fell through to the legacy spawnSync fallback, which builds a Windows-style interpreter path even on Linux (.venv/Scripts/ plus python). The shell answered 'not found' with exit 127, extractError() found no marker line in stdout and returned 'Unknown error', and the UI rendered that over the raw shell message - a dead end with no action in it. Now the route checks for the interpreter it needs before doing any work, and returns 503 with a sentence naming the real cause and where to run the search instead. Checked per request so it cannot go stale. Verified: typecheck clean; a real enterprise search of K2022808158 on the local dev server still returns 200 in 87s with 3 directors, so the guard does not touch the working Windows path.		2026-10-20 09:00:41 +02:00
Workflow	fix(cipc): say plainly when search runs where it cannot	2026-10-20 09:00:41 +02:00
.gitignore	feat: commit Workflow app source; move CIPC credentials to env	2026-10-18 15:21:45 +02:00