To #NVDASR community: please, PLEASE don't just use an AI system to submit pull requests:
https://github.com/nvaccess/nvda/pull/19787
1/
In recent days, several NVDA screen reader pull requests were closed because NV Access realized that these PR's were written by AI without filling out the NVDA PR template:
https://github.com/nvaccess/nvda/pull/19774
https://github.com/nvaccess/nvda/pull/19775
https://github.com/nvaccess/nvda/pull/19776
2/
fix: guard oldTracker.pluralTimeout before comparison in makeMergedTrackerIfPossible by seang1121 · Pull Request #19774 · nvaccess/nvda

Fixes #19620 Summary In makeMergedTrackerIfPossible, the pluralization branch checked newTracker.pluralTimeout is not None before using it, but did not apply the same guard to oldTracker.pluralTime...

GitHub
Pull request templates exist for a number of reasons, including communicating expectations by the organization/project and to help pull request writers (humans or machines) organize thoughts and information in a structured way. In organizatoinal communication space, this means when an AI generates a PR and the template content, it is communicating the knowledge gathered by an organization that can conflict with expectations from another organization. 3/
Further, the pull request I linked to at the start of this posts chain had a major issue: the command supposedly assigned to recognie text content using an on-device model is actually unavailable; NVDA+Shift+R is NOT a global command but is defined in Excel app module to mark row/column headers for spreadsheets. Therefore, the AI must parse the entire NVDA source code next time (this takes time and resources). 4/