{"version":"2.1.259","anchor":"notification-enqueue-calls-gained-turnattribution","canonical_anchor":"notification-enqueue-calls-gained-turnattribution","heading":"Turn-attribution metadata added to background\/notification message sends","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/notification-enqueue-calls-gained-turnattribution","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Turn-attribution metadata added to background\/notification message sends\n\nTask notifications can now say which conversational turn they belong to via a turn-attribution option.\n\nInternal message-send call sites (task notifications, hook stop messages, WebSocket housekeeping messages) now pass a `turnAttribution` value of \"inherit\" or \"none\", and a new helper resolves `turnAttributionKey` for task-notification mode. The task-notification enqueue path also gained a second options argument carrying `turnAttribution`, with the ultrareview-failed notification explicitly passing `{ turnAttribution: \"inherit\" }`. This is internal bookkeeping to track which conversational turn a background message belongs to.\n\n- Area: Elsewhere\n- Names: `turnAttribution`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}