I've had plenty of projects where unexpected (an often unnecesary) changes to config files break the app and it usually takes multiple rollbacks to go back to the stable version .
I've seen this specially happen in config files (.env,firestore.rules,etc) where configs are set to invalid values and unless they get caught in the file diffs they make us think the problem is with the new generated code when acutally is a base setup that has been changed.

would it be possible to flag certain files (eg .ai-ignore file) or annotate code in some way to let the coding agent know that section is "only humans allowed" and should not be changed using generated code.