{"version":"2.1.234","anchor":"malformed-multiple-choice-payloads-no-longer-break-rendering","canonical_anchor":"malformed-multiple-choice-payloads-no-longer-break-rendering","heading":"Malformed multiple-choice payloads no longer break rendering","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/malformed-multiple-choice-payloads-no-longer-break-rendering","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Malformed multiple-choice payloads no longer break rendering\n\nA malformed multiple-choice question no longer breaks rendering.\n\n**What**\n\nThe renderer that formats an AskUserQuestion tool input for the classifier is now wrapped in error handling, rejects nonsensical `questions.length` values, and caps how many questions and options it walks.\n\n**Details**\n\n- Instead of iterating an array whose length the payload controls, it stops and emits an elision marker that reports the claimed length.\n\n**Evidence**\n\n`[\u2026 further question entries elided: reported length `\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}