{"version":"2.1.27","anchor":"improved-transcript-jsonl-file-validation","canonical_anchor":"improved-transcript-jsonl-file-validation","heading":"Improved Transcript\/JSONL File Validation","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.27\/e\/improved-transcript-jsonl-file-validation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.27","markdown":"### Improved Transcript\/JSONL File Validation\n\nReading transcript files now provides clearer error messages when files are malformed:\n\n- \"No messages found in JSONL file\" - when JSONL file parses but contains no messages\n- \"No valid conversation chain found in JSONL file\" - when messages exist but no valid chain can be reconstructed\n- \"Invalid JSON in transcript file\" - when JSON parsing fails\n- \"Transcript messages must be an array\" \/ \"Transcript must be an array of messages or an object with a messages array\" - format validation\n\n**Evidence**\n\nJSONL validation (search for `\"No messages found in JSONL file\"`)"}