{"version":"2.1.238","anchor":"subagent-lifecycle-events-are-published-with-no-consumer","canonical_anchor":"subagent-lifecycle-events-are-published-with-no-consumer","heading":"Subagent lifecycle events are published with no consumer","tier":"internal","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/subagent-lifecycle-events-are-published-with-no-consumer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Subagent lifecycle events are published with no consumer\n\nSubagents now announce when they finish, fail or are killed, and nothing listens yet.\n\n**What**\n\nSubagent completion, failure and kill now publish a settled event carrying the outcome (\"completed\" with a stranded-messages flag, \"failed\", or \"killed\"). Nothing in this build subscribes to it, nor to the spawned and resume-failed events; the only subagent channel with a listener is the stranded-messages one. This is groundwork with no visible effect yet.\n\n**Evidence**\n\n`agentSettled`\n\n- Area: Subagents\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}