Wired up actual deploy: push to main, and a minute later the demo is running that commit. git archive straight over ssh into a receive script — no registry, no git pull on the server, so the server never holds credentials for this repo. The one thing it refuses to do is kill a run in progress: /api/run spawns the pipeline as a subprocess, and a container restart takes it down with it. Now the script asks first, and if a run is going it stops and exits non-zero — red, on purpose, because a deploy that shipped code but didn’t put it into service has no business looking green.Rebuilding the whole thing from nothing on a clean machine found what months of running it on my own box never did. All five delivered companies 404’d after the first real run — the candidate list gets loaded once at import, a run rewrites the files under it, and the process just kept serving eight-hour-old data until somebody restarted it by hand. The “what’s missing” preflight check was lying in both directions: it called the API key missing on a machine that had it as an env var instead of a .env file, and it reported success on a machine where the industry codebook never downloaded — which doesn’t crash anything, it just prints every industry as a bare five-digit code and calls that fine.README got rewritten to lead with the one sentence the tool actually stands on, plus an ARCHITECTURE.md the code can point to instead of explaining itself in comments, a Czech translation, and an MIT licence with the honest caveat: what’s verified is that a sentence was on a page, not that it’s true.