{"version":"2.1.221","anchor":"task-notification-origins-carry-a-subkind","canonical_anchor":"task-notification-origins-carry-a-subkind","heading":"Task-notification origins carry a subkind","tier":"notice","area":"Terminal UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/task-notification-origins-carry-a-subkind","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Task-notification origins carry a subkind\n\nScheduled-trigger notifications no longer get merged into ordinary task notifications.\n\n**What**\n\nMessage origins are normalized before being queued or persisted, and the queue-merge comparison accounts for the new subkind.\n\n**Details**\n\n- The normalizer keeps only `kind: \"task-notification\"` plus an optional `subkind`, for example `scheduled-trigger`.\n- Queue-merge equality now compares subkinds, so scheduled-trigger notifications do not merge with ordinary ones.\n\n**Evidence**\n\n`kind: \"task-notification\", subkind: \"scheduled-trigger\"`\n\n- Area: Terminal UI\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}