{"version":"2.1.221","anchor":"monitor-completion-distinguishes-an-empty-stream","canonical_anchor":"monitor-completion-distinguishes-an-empty-stream","heading":"Monitor completion distinguishes an empty stream","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/monitor-completion-distinguishes-an-empty-stream","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Monitor completion distinguishes an empty stream\n\nA monitor that exits without output now says so and shows its exit code.\n\n**What**\n\nA monitor process that exits having emitted nothing now reports that specifically, rather than the generic stream-ended message.\n\n**Details**\n\n- The exit code is appended to the no-output message.\n- The exit-code suffix is now shared across the completed and failed strings instead of being built separately.\n\n**Evidence**\n\n`ended without producing output`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}