Unreadable files — what the row and the popover say

The rule, as settled: a file in a format we say we read (the docs list) that we opened and couldn't use is a failure with a reason (“we tried, and it wasn’t a transcript when we looked inside”). A file in a format we never offered, .py and .txt alike, is left alone and never changes the outcome. Where a popover is already open for a real failure, a quiet footer says what was left alone and links to the formats we read. Native approximation of ProjectRow and ProjectDiagnosticPopover; every sentence is a shipped locale key unless it is marked new copy.

Framed, product-coloured: what would ship — the sidebar row and the popover, nothing else.

Hatched edge: commentary. Not in the product.

String plan

Three pieces of copy are new. The other reasons reuse the shipped desktop.pipeline.diagnostic.reason.* keys.

Where	Text	Status
Row line, run with unreadable sessions	“5 of 6 sessions analysed”	shipped (`partialSessions`)
Row line, unreadable files that were never sessions	“2 files not analysed”	shipped (`chrome.notAnalysedCount`), new use as a row line
Popover reasons	incomplete · empty · no audio · not a recording · not a format Bristlenose reads	shipped
Popover reason, a read format with no transcript inside	No transcript in this document.	new key; shipped `notes_only` names “meeting notes”, which a guide is not
Popover footer, count	N other files left alone (plural)	new key, owner to write
Popover footer, link to the docs formats page	Supported formats	new key, owner to write; needs a stable docs URL in the website repo

Correction to what I said earlier

I said the popover’s “Done with warnings” outcome covers files that were left out. It doesn’t: it covers quotes left out of a session (leftOutCount, completedPartialAnalysed). Files that couldn’t be read have no such path, which is why Talismanic read “Partial completion”. Nothing in this page relies on that outcome.