=== TC89 -- bad-file ingestion status (UI only, no API query involved) === Fixture: bad_01_truncated.pdf (deliberately truncated/corrupt PDF, upload-only fixture set) Chatbot: R6-stable-SS-v1 (same chatbot as TC86-88, 9th source added on top of the 8-doc stable slice) Uploaded via: Sources > Add > Files > Choose files (dashboard UI, no ingestion API exists on this tool per reference/api-denser.md) --- Step 1: upload --- File uploaded, size reported 87.77 KB. Immediate post-upload UI optimistically rendered row as "Trained" before the "Uploading 1 file..." notification had even cleared. --- Step 2: confirm post-refresh (not just an optimistic client-side render) --- Clicked "Refresh sources" explicitly, re-read the Sources table. Result: bad_01_truncated.pdf | Status: Trained | Hits: 0 | Size: 87.77 KB Identical status styling (green dot, "Trained" label) to all 8 genuine, successfully-ingested documents in the same table -- no distinct warning/error/partial/failed state of any kind. --- Step 3: attempt to preview the file inside Denser's own PDF viewer --- Clicked the source row to open Preview. Result: "Unable to load PDF -- The file may have been moved or deleted." This is Denser's own UI being unable to open the exact file it has simultaneously marked "Trained" in the Sources table (visible in the same screenshot, side by side -- see tc89-02-bad-file-preview.png). --- Conclusion --- Denser's ingestion pipeline reports a truncated, unparseable PDF as a fully successful "Trained" source -- the same status given to every genuinely ingested document -- with no failure signal anywhere in the dashboard. The product's own preview feature cannot open the file, directly contradicting the "Trained" status shown one UI panel over. This is the TC89 failure mode exactly as specified: "a per-document FAILURE status for that file... Reporting success -- or reporting nothing -- is the failure." --- Second ingestion, 17 November 2026 (truncated file and a password-protected file) --- The original 9-source chatbot no longer exists (Free plan allows one agent), so both files were uploaded to the remaining agent, R6-mutation-MS-v0 (4 other files, 6 sources in total), via Sources > Add source > Upload files. The dashboard now labels sources "Ready" / "Failed" instead of "Trained". bad_02_password_protected.pdf | 171 kB | Status: Failed | "document closed or encrypted. To try again, delete it and add it again." -> failure reported bad_01_truncated.pdf | 88 kB | Status: Ready | same green badge as the good files -> failure NOT reported - Preview (File tab): "Can't show this file" - "What the agent read" tab: "No passages yet" (nothing was read from the file) So Denser does have a Failed state and uses it for the encrypted file, but still marks the truncated file Ready although nothing could be read from it. Verdict unchanged: Fail. Screenshots (17 Nov 2026 ingestion; the 5 Oct 2026 first-run screenshots are no longer kept): - tc89-03-sources-status-annotated.png -- Sources list, password-protected file Failed, truncated file Ready - tc89-04-truncated-preview-fails-annotated.png -- Denser's viewer on the truncated file: "Can't show this file" - tc89-05-truncated-nothing-read-annotated.png -- "What the agent read" tab: "No passages yet"