{"version":"2.1.274","anchor":"post-turn-summary-telemetryschema-gains-richer-structured-f","canonical_anchor":"post-turn-summary-telemetryschema-gains-richer-structured-f","heading":"post_turn_summary telemetry\/schema gains richer structured fields","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/post-turn-summary-telemetryschema-gains-richer-structured-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### post_turn_summary telemetry\/schema gains richer structured fields\n\nTurn-summary telemetry now carries a description, points, summary, and suggested replies\n\n**What**\n\nThe internal `post_turn_summary` event, which records data about a completed turn (one back-and-forth exchange with Claude), now includes several new fields on top of what it already tracked: `description`, `points`, `summary`, `next_why`, and `reply_options`.\n\n**Why**\n\nThis gives whatever consumes this telemetry a richer picture of what happened at the end of a turn and what might reasonably follow, rather than just a status code and a short detail string.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}