Support directory-tree exclusions in omarchy-crash-watch

[JoNil]

Use case

During software development, crashes may be intentional or expected—for example from tests, fuzzing, and debug builds. When locally built executables live below a tree such as ~/dev, each crash currently produces a critical “Click to diagnose with AI” notification.

OMARCHY_CRASH_IGNORE can exclude executable basenames, but that is too broad for common or reused names: it also suppresses crashes from executables with the same name outside the development tree.

Suggested behavior

Add an optional directory-tree exclusion for omarchy-crash-watch, based on the full COREDUMP_EXE path. For example, configuring ~/dev would suppress a crash for:

~/dev/project/build/example

while continuing to notify for an executable outside that tree, even if it has the same basename.

It would be useful to support multiple excluded roots. Matching should respect path-component boundaries, so ~/dev matches its descendants but not ~/development. The existing OMARCHY_CRASH_IGNORE basename filter should remain available.

Scope clarification

The primary request is filtering by executable location. Interpreted programs are a separate case: a script below ~/dev may appear as /usr/bin/python or /usr/bin/node in COREDUMP_EXE, so command-line, script-path, or working-directory filtering could be considered separately if reliable metadata is available.

No diagnostic or system-specific information is needed for this feature request.