Flows: a review run is told the order it acts under #163
Loading…
Reference in a new issue
No description provided.
Delete branch "vinny/review-order"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A flow review job acts under the President's most recent current order (its ticket names it), but the cmonet-flow-start event took the order from job.order_id, which reviews don't have, so the flow saw order null. Live 2026-10-28: the order's own run failed while the model server was unreachable, so the flow memory never got the order's words and each later review would brief the General "no order yet" while CMOnet fenced its writes under that order. The start event now uses the ticket's order. Test: tests/flows/test_runner.py::test_a_review_run_is_told_the_order_it_acts_under; tests/flows passes. 🤖 Generated with Claude Code