{"version":"2.1.246","anchor":"turn-start-and-completion-go-through-a-named-lifecycle-objec","canonical_anchor":"turn-start-and-completion-go-through-a-named-lifecycle-objec","heading":"Turn start and completion go through a named lifecycle object","tier":"internal","area":"Session Loop","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/turn-start-and-completion-go-through-a-named-lifecycle-objec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Turn start and completion go through a named lifecycle object\n\nTurn start and finish go through a named lifecycle object, and starts can be aborted.\n\n**What**\n\nTurn 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.\n\n**Details**\n\n- The bridge result carries the turn attribution key unless the turn was aborted.\n- A successfully generated Haiku session title now also pushes that title to the bridge.\n\n**Evidence**\n\n`raiseTurnStart`\n\n- Area: Session Loop\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}