{"version":"2.1.238","anchor":"publish-cap-failures-get-their-own-outcome-bucket","canonical_anchor":"publish-cap-failures-get-their-own-outcome-bucket","heading":"Publish cap failures get their own outcome bucket","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/publish-cap-failures-get-their-own-outcome-bucket","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Publish cap failures get their own outcome bucket\n\nHitting a publishing cap is now logged as its own outcome rather than lumped in with unknown failures.\n\n**What**\n\nA publish failure caused by a cap is now decoded into a cap type and message and classified as `publish_capped`, separate from the pinned-version and unknown buckets. Compose paths also report a visible character count and whether the text was rewritten.\n\n**Evidence**\n\n`publish_capped`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}