1. One-time setup 1a. Dump ninja dependency data (once per session, after a clean build) This is the authoritative "which TUs read which headers" map for ranking and cascade prediction. It is reliable only immediately after a successful build — see §5a for staleness rules. Match headers by basename ( ), not full path: WTF deps appear via symlinks and JSC via copies, so the same header shows under multiple paths. 2. Prepare a filtered compile commands.json Homebrew clang can't read Apple-specific flags or Apple-built PCH, and the CMake textual prefix ( ) breaks standalone-header analysis. Buil…