0.18.1

An Arc card no longer calls another checkout's stack its own. Fusion writes the same container names in every checkout, so only one Arc stack can run on a machine, and two checkouts serving on the same port out of their own .env answer each other's health checks: one card sat green over a project that had never been started. A card that gets an answer while Docker shows none of its own containers now says stopped and names the checkout holding the port. A stack started by hand in a terminal, with no containers at all, still counts as running.

Worth doing alongside this: give each Arc checkout its own PORT in its .env. Two of them cannot be up at once whatever the ports say, but distinct ports keep the links on each card pointing at the site that card is about.

scripts/check-arc-stack.sh in the repository prints what every configured Arc card checks - the address, the answer, who is listening on the port, and which containers belong to the checkout - for a card that still disagrees with the person looking at it.

---

The archive for this version has been removed. Install the latest release instead: it is signed and notarised, and it updates itself from there.