[BUG] Report idle parser worker crashes without waiting for another file #43

Type

Bug

Problem / Value

If the parser worker crashes while idle, its failure is reported only when another parse is requested. Without another file change, the user can be left unaware that the parser worker has stopped.

Context

Deferred re-review finding 🟢13 from PR #34: #34, which addresses #23. Source reviewed: 8c38f1c.

An idle crash is remembered locally, and the worker is stopped. The saved failure reaches the indexing controller through the next parse request rather than an immediate notification.

This is distinct from finding 1, which was fixed: the next parse already reports a parser failure rather than cancellation. Do not reopen that classification fix.

Reproduction

Proposed regression test: finish one parse, emit an idle worker error or exit, request no additional parse, and inspect indexing status. These steps were not executed during filing.

Acceptance criteria

• Notify the indexing controller promptly of an unexpected idle worker error or exit.
• Show a parser-failure status and explicit retry guidance without requiring a file change.
• Deliver only one failure notification and ignore expected exits caused by stopping or disposal.
• Preserve the existing next-parse failure classification and fail-stop behavior.
• Test idle error, idle exit, intentional shutdown, and later parse attempts.

Constraints/Preferences

Do not automatically restart a failed parser. Preserve the fixes for findings 1 and 2.