jschoubben 89b6dd6080 Print why the resolver did not start, instead of that it did not ...

`systemctl is-active` exits non-zero for a unit that failed, so `must` threw
before the assertion carrying every diagnostic — and the run said only
"failed". The journal, the config, what the mesh wrote and resolv.conf are all
things the next run should not have to be re-run to see.

2026-08-31 13:11:02 +02:00

..

builds.test.ts

A machine in the mesh builds a module, and the catalogue records it

2026-08-30 04:06:23 +02:00

harness.ts

Repoint ADR references after HQ consolidated 65 records to 23

2026-08-28 23:33:46 +02:00

mesh.test.ts

Print why the resolver did not start, instead of that it did not

2026-08-31 13:11:02 +02:00

placement.test.ts

Repoint ADR references after HQ consolidated 65 records to 23

2026-08-28 23:33:46 +02:00

provisioner.test.ts

Prove a mesh credential becomes a login, against a real database

2026-08-30 01:29:46 +02:00

scenarios.test.ts

Step 2: raise a second scenario, and share the invariants

2026-08-25 00:29:59 +02:00

underlay.test.ts

Repoint ADR references after HQ consolidated 65 records to 23

2026-08-28 23:33:46 +02:00