Handle parse failures gracefully + save to DB

The parser fails sometimes and produces an error message. The application should handle these cases gracefully and perhaps save with a problem in the DB that the parser produces an error for it. Then the user can find these problematic cases more easily.

Start by locating the parser failure path and the database persistence entry point; the issue does not name specific files or tests. Trace how parse errors reach the user, then determine the expected stored problem state and how users should find these cases; done means failures are handled gracefully and problematic parses can be identified in the database.

Written by the indexing model from the issue text.