host P0.3b: durable flow log — survives restart (LIVE-VERIFIED)

The driver now persists each effect record to the blog store (string-keyed to dodge the keyword/
persist top-level split), and host/blog-load-flowlog! rebuilds the in-memory log on boot (wired into
serve.sh after load-edges!). So /flows survives a restart — closing the P0.3 gap.

LIVE PROOF: published a post on blog.rose-ash.com → /flows showed validate+notify → RESTARTED the
container (in-memory log lost) → /flows STILL showed them, reloaded from the durable store.
Round-trip also covered by a conformance test (persist → clear → reload → identical). blog 208/208,
full host conformance 599/599. Note: whole-list rewrite per effect — fine at P0 volume, cap/rotate later.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

plans/business-logic-fed-flows.md

@@ -214,6 +214,11 @@ covers everything until a DAG's cost/latency/placement forces the substrate.
   activities), so business logic can change state, which federates, which triggers more flows.
 
 ## Progress log (newest first)
+- 2026-07-02 — P0.3b DONE + LIVE-VERIFIED. The flow log is now DURABLE: the driver
+  persists string-keyed effect records to the blog store (dodging the keyword/persist top-level
+  split); host/blog-load-flowlog! rebuilds it on boot (serve.sh). Proof: published on
+  blog.rose-ash.com, RESTARTED the container, /flows still showed validate+notify (reloaded from the
+  store). blog 208/208, conformance 599/599. Whole-list rewrite per effect — cap/rotate later.
 - 2026-07-02 — P0.3 DONE + LIVE-VERIFIED. The seam wired into the live publish path: on-publish
   registry + in-process transport + host driver + the execute-fold runner, fired by the draft→
   published transition in both write handlers. Published a real post on blog.rose-ash.com → /flows