RFC: git bisect is broken by huge number of commits PRs

The Problem

I, and others, lately have tried git bisect to determine which commit caused an issue. We can't complete the bisect because we keep running across multiple (last time I gave up after 5 consecutive) commits that aren't able to compile. So at this point we have no tools other than intuition and guesstimation to determine what is wrong or where a problem started.

The Cause

The cause of the issue is PR's with large numbers of commits, probably generated by AI and never compiled, which are then merged.

A Proposed Fix

Any commit with more than 10 (?) commits gets the commits squashed since the PR will compile and then we can at least bisect down to a PR, which is better than nothing.

A Real Fix

Devs should compile each commit. If you are using AI and it generates 10 commits to fix/add a feature/problem and only the last one is compiled, then squash the commits to the last one or compile each of the intermediate commits to make sure they don't break git bisect.

The issue names no source files, tests, or entry points. Start by reading the proposed commit-squashing and compilation practices and the comment discussion; done requires an agreed, actionable approach for keeping bisect usable when intermediate commits do not compile.