If this sounds like your week
When Windows Search gets in the way
developer workstations accumulate SDKs, runtimes, CLIs, and vendor tools across install folders and Downloads. Windows Search can miss executable discovery when an app is not represented cleanly in the Start Menu. npm, cargo, or Vite processes already consume CPU while the user switches between Explorer and Start.
Where tooling usually breaks
Why local-first matters
index.db, config.json, and logs stay under %APPDATA%\SearchSentinel instead of a vendor-hosted workspace. Search queries are not uploaded for AI enhancement, analytics, or ad targeting. You buy the app once and keep the search index as a local workstation asset.
Technical proof points
- WalkDir max_depth(4) - Common install dirs - App Paths - ShellExecuteW - SQLite FTS5 - BM25 ranking - 120 ms debounce