Archibald312 stops the privacy guard from crying wolf
A small fix unblocks legitimate requests that carried no documents at all, and makes upload failures actually legible.
Archibald312's fork ran a data-privacy check on every request - sensible, except it was also firing when a request had no documents attached, blocking perfectly safe calls for no reason. The fix is the obvious one: no documents, no privacy risk, so let it through. That clears a class of false alarms that had been getting in the way during testing.
The rest of the commit is about seeing failures clearly. When document uploads or an AI prompt step failed, the fork was collapsing the error into a vague one-line message and throwing away the detail underneath. Now the full error - including the buried sub-errors you get when several uploads fail at once - lands in the server logs and the response. Less guessing when something breaks.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?