TortoiseGitNotify toast alerts fire for ignored file changes despite filter settings

TortoiseGitNotify raises Windows toast alerts when file status changes are detected within a repository's watched path. A persistent design tension exists between surfacing meaningful changes and avoiding alert fatigue from untracked, ignored, or submodule-internal events. The feature set includes checkboxes to disable notifications for untracked files and wildcard-driven include/exclude path filters, yet the underlying status cache mode directly influences which events are observable in real time. Switching the cache to 'none' conserves resources but eliminates toast generation until a manual refresh, creating a trade-off between performance and immediacy. Windows Focus Assist or group-policy settings may further obscure alerts without indicating a configuration mismatch.

• Does the 'Notify on untracked files' setting fully suppress toast events when the status cache mode is 'none'?
• What is the interaction between include/exclude wildcard patterns and submodule working-tree change detection?
• Can Windows Focus Assist silently suppress TortoiseGitNotify toasts without altering the application's notification state?