Harden flow advancement exit assertions

workplans/STATE-WP-0047-lifecycle-assertions-and-renormalization.md

@@ -108,7 +108,7 @@ parents blocked.
 
 ```task
 id: STATE-WP-0047-T04
-status: todo
+status: done
 priority: high
 state_hub_task_id: "3f1e49fd-0600-4124-a7bc-0c75955bac8b"
 ```
@@ -119,6 +119,11 @@ assertions. Return actionable blocking assertions when a transition is refused.
 Done when `/flows/.../advance/...` cannot bypass the same assertions the flow
 state endpoint reports as blocking.
 
+Result 2026-05-23: `FlowEngine.can_reach()` now checks current exit assertions
+before target entry assertions for real transitions. The flow advance endpoint
+returns HTTP 409 when a dependency blocks leaving `active`, even if the target
+state entry assertions pass.
+
 ## T05 - Add Renormalization Checks And Repairs
 
 ```task
@@ -169,6 +174,9 @@ from `proposed`, `ready`, and `backlog`, plus a guard test proving `blocked`
 parents stay blocked. Remaining coverage still needs flow assertion hardening
 and consistency repair tests.
 
+Progress 2026-05-23: added engine and router coverage proving flow advancement
+honors current exit assertions before moving to the target workstation.
+
 ## Acceptance Criteria
 
 - Starting task work deterministically activates the parent workstream.