GitHub pushes no longer run build/test/coverage at all — the job-level
condition previously only skipped the docker/deploy steps, so every GitHub
push still burned CI minutes on a build+test that went nowhere. GitHub gets
its own release-triggered workflow later.
Dual-engine workflow (.github/workflows/ci.yml, read by both GitHub Actions
and Gitea Actions): build, test, coverage badge on every push; on Gitea main
pushes only, build+push API/web images to the Gitea registry and redeploy
the persistent LAN stack via the shared [self-hosted, qa] runner. Replaces
the ad hoc docker-compose.deploy.yml manual workflow with
deploy/qa/docker-compose.qa.yml, pulled by CI — data volume preserved
across deploys (no -v on down), unlike mic-check's throwaway QA stack.
James Wampler