df4dd5b1558b14677c62a544232b82d5814a95d1
SessionEventBridge.replaySnapshot ran per WS connection and appended a repair OrchestrationResumedEvent — a write side effect on a pure read path that two concurrent clients could double-append (and 'open TUI' mutated replay history). Moved to a one-shot ServerModule.repairStuckApprovalPauses() at boot; replaySnapshot is read-only again. The state it repairs comes from a fixed pre-Feb-13 bug, so no session newly enters it at runtime — boot coverage is sufficient. Note: :apps:server:test not run (core:kernel broken by concurrent work); edits are isolated and mirror the existing preRegisterPendingApprovals shape.
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%