[BackStacked]

Requested by Himanshu · project thread

What and why

Needs mgpl-diagnostics/.github#18 merged first (shared actions).

• ci.yml: setup through mgpl-diagnostics/.github/actions/node (npm cache, MongoDB binary cache, npm ci). PgBouncer comes from actions/apt (cached .debs, retries, time limits): main's CI failed today after apt-get install pgbouncer hung 5.5 minutes on a mirror DNS outage.
• Runs on main are no longer cancelled by the next merge (cancel-in-progress only for PRs), so every main commit keeps a CI result. The job id stays ci (required check).
• New docker.yml: builds the Dockerfile (linux/amd64) on every PR and on main without pushing, with layer caching, then loads dist/index.js inside the image (every kit, report-kit's native resvg included, from the pruned node_modules). Skipped for docs/tests-only changes. Not a required check; release.yml is unchanged and still the only thing that pushes.

Type

• Refactor / tooling

Checklist

• CI green on this branch (timings in the thread)
• No real patient data, contact details or signatures

---

Generated by Claude Code

[BackStacked]

ci fails on purpose for now: Can't find 'action.yml' … for action 'mgpl-diagnostics/.github/actions/node@main'. This PR now uses the shared actions from main, and they arrive with mgpl-diagnostics/.github#18. The same workflow passed on the earlier commit, which used the branch ref. Merge .github#18 first, then re-run this check.

---

Generated by Claude Code

[BackStacked]

The shared action now loads. The re-run fails at install with No matching version found for @mgpl-diagnostics/client@^1.10.0. That requirement comes from main (#35), not from this PR. The client repo has 1.10.0 on main, but the version was never tagged or published (its latest tag is v1.9.0), so CI on main fails the same way. Publishing client 1.10.0 (tag v1.10.0) fixes both. Then re-run this check.

---

Generated by Claude Code