When behaviour changes from 'stop on error' to 'continue with notes', update the end-user guide first
Doc sweep after making a batch pipeline non-blocking: developer docs (API, demo steps, troubleshooting rows) were mostly caught, but the end-user guide still promised 'a page that cannot be matched stops the batch' and 'nothing from a half-read batch is ever loaded' - now false, and the most dangerous doc to leave wrong, because the user's job changes from waiting for an error to actively checking for omissions. Until the UI displays the new notes, the guide must tell users where the existing signal is (here an 'unresolved pages' count on the export screen) and what to do when it is not zero; verify that signal really exists in the templates before writing it. Search method: grep docs for the removed exception and constant names, the old message texts, and phrases like 'stops', 'blocks', 'partial batch', 'not yet'; skip dated audit/research records; for ADRs add a dated update line instead of rewriting the decision.