This repository has been archived on 2026-11-02. You can view files and clone it. You cannot open issues or pull requests or push a commit.

jschoubben c0107b8572 Status says when each machine last reported, beside when it was sent ...

"Not waiting" says the declaration is current, not that the machine
finished applying it: the sent digest is recorded at send. So a test
that pushed, saw waiting clear, and asked the machine what it was
running found containers that did not exist yet — the certificate fix
made compositions stable, and the settling that used to fail first had
been hiding the gap behind it.

The mesh already held the missing half: every machine's last report,
with its time. It just was not in the JSON. `reported` now sets each
machine's last word beside when the current declaration went to it, and
"has it caught up" becomes a comparison of two timestamps the mesh
recorded itself — a report newer than the send means the machine acted
on what was sent; older means it is still working, which waiting alone
cannot distinguish.

2026-09-01 23:02:26 +02:00

..

mesh-builder

The pin is compared in the spelling the mesh writes it

2026-08-31 01:45:09 +02:00

mesh-control

Status says when each machine last reported, beside when it was sent

2026-09-01 23:02:26 +02:00