Turn start and finish go through a named lifecycle object, and starts can be aborted.
What's wrong with this entry?
Turn spans are raised through raiseTurnStart and raiseTurnComplete on a shared object instead of loose functions, and turn start now receives an abort callback that cancels the turn with a "turn-abort" reason.
- The bridge result carries the turn attribution key unless the turn was aborted.
- A successfully generated Haiku session title now also pushes that title to the bridge.
raiseTurnStart
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.224
Loop file can come from stored state instead of disk
Both mention loop
-
v2.1.248
Loop keepalive is on by default
Both mention loop
-
v2.1.248
Self-pacing /loop wakeups no longer blocked by a runtime switch
Both mention loop