{"version":"2.1.224","anchor":"prototype-runs-and-publishes-now-report-their-own-telemetry","canonical_anchor":"prototype-runs-and-publishes-now-report-their-own-telemetry","heading":"Prototype runs and publishes now report their own telemetry","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/prototype-runs-and-publishes-now-report-their-own-telemetry","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Prototype runs and publishes now report their own telemetry\n\nPrototype runs and publishes now emit their own telemetry events with the artifact slug.\n\n**What**\n\nClaude Code emits two new events around prototype artifacts: one when a prototype run starts, and one when a prototype is published, carrying the artifact's slug and whether it was the first publish.\n\n**Details**\n\n- The publish event records `artifact_slug` and `is_first_publish`.\n- Neither event name exists in the previous build.\n- The functions that emit these events are new; which artifact flow calls them was not traced, so it is not clear from the build itself which user actions trigger them.\n\n**Evidence**\n\n`prototype_publish`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}