A pull whose diff spans hundreds of files no longer holds every build: the hot-file hold skips a pull wider than 60 files and names it #6235

Measured 2026-10-26: the crew's reserve says 0 startable while the map has 38 ready, unassigned issues. Every one of them is held as hot_file. Five open pulls, #4840, #5460, #5469, #5482 and #5434, are conflicted and each touches 898–1,081 files (+30,000 lines). The diffs carry main's history, not their own work. Five pulls at HOT_PULLS = 5 make 895 files hot, so any issue that names a source file waits. Without those five, 27 files are hot and most of the ready list could start.

Done when:

• [ ] In the hot-file module (src/crew, hot_files), a pull whose diff against the base tip touches more than WIDE_PULL = 60 files counts toward no file's heat.
• [ ] Such a pull is named, with its file count, where the feed shows the hot holds today (standingHot), so a person sees "too wide to count: #4840 (1,081 files)" and can close or rebase it.
• [ ] The crew-hot-files test: five pulls touching 900 files each plus one ordinary pull leave an issue that names one of those files startable. Four ordinary pulls plus one more ordinary pull on the same file still hold it.
• [ ] The crew doc's hot-file paragraph (docs, CREW) says the limit and why.

Risk: a real sweeping change, such as a rename across the tree, also goes uncounted. That is acceptable. Such a pull conflicts with everything anyway, and it is named for a person.