{"version":"2.1.232","anchor":"corrupt-roster-and-orphaned-transcript-files-handled-through","canonical_anchor":"corrupt-roster-and-orphaned-transcript-files-handled-through","heading":"Corrupt roster and orphaned transcript files handled through storage","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/corrupt-roster-and-orphaned-transcript-files-handled-through","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Corrupt roster and orphaned transcript files handled through storage\n\nA corrupt daemon roster file is renamed aside instead of blocking, and orphaned transcripts get moved properly.\n\n**What**\n\nA daemon roster file that fails to parse is moved aside to a timestamped `roster.json.corrupt.<ts>` name through the storage layer, falling back to a plain filesystem rename, and orphaned transcripts are renamed inside the transcript namespace rather than only on disk.\n\n**Details**\n\n- The storage path is only taken when a storage backend is available.\n\n**Evidence**\n\n`roster quarantine v5 move failed`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}