4107a595db5c904533750ae83d5b6e9583f6479a
launchSessionRun and launchSessionResumeWithRehydrate each inlined their own copy of the freestyle phase-2 handoff with different guard sets — the run path had none, so a failed planning run still called lockAndRun and emitted a spurious ExecutionPlanRejected. Both now call one handoff that checks graph id, planning result, and an existing plan lock before locking and running phase 2.
fix: workflow inference chain — surface llama-server errors, user-turn-last, bundle-relative prompts
Description
No description provided
Languages
Kotlin
88.4%
Go
11.4%
Python
0.2%