Repository navigation
cmux-tui: derive session effect workflows from journal - #9816
lawrencecchen wants to merge 4 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Found 3 test failures on Blacksmith runners: Failures
|
|
Obsolete stacked draft; see the closing note above. |
![Fix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/fix-with-codesmith-light.png)
Stacked after #9815. Depends on #9726, #9806, #9813, and #9815 landing in order. Do not merge this PR before all predecessors are reliable, gated, and landed.
Successor:
Scope:
Out of scope:
Verification:
Owner closeout:
Fixed = no durable effect workflow state -> trusted-local intent and outcome events now derive journal_session_effect_workflows.
How = closed payloads, pure reducer, and one SQLite transaction for journal event, projection update, and idempotency receipt. This is principled because later orchestrators get a source-owned state machine without process control.
Risk = host-loss detector wiring, public commands, provider resume, and fork runtime creation remain deferred to successors.