Design 38 WP4 built and proven live on all four machines; issue 209 proven live

2026-10-03 13:20:12 +02:00
parent a572868333
commit ce5f85f65e
2 changed files with 10 additions and 1 deletions
@@ -208,6 +208,14 @@ image used to carry is now declared on the host; and that the operator's account
 a prompt is a fact about the machine the mesh neither declares nor checks — true on all four today,
 and when it is not, the tool names it by how it failed, which is the only check there is until a
 record says where the fact belongs.
+*Built 2026-10-03* (mesh-tools `7152148` for issue 209, mesh-catalog `db5e7c8`). *Proven live
+2026-10-03, on all four machines*: `node-packet-filter.rules`, `reload` and `remove` answer from the
+node's runtime on each — `rules` and the module's own tool list the mesh's table, `reload` loads the
+file and answers with the table, `remove` refuses the mesh's own table by name — `docker ps` shows no
+`mesh-nftables` on any, the container's credential is gone with it, and `status` is well. One thing
+the step found is issue
+[210](../../04-ISSUES/210-the-host-re-creates-the-nodes-runtime-on-every-reconcile/00-report.md):
+the host re-creates the runtime's process on every reconcile.

 ## WP5 — The shell, on a server first