Good point, thank you for pointing it out.
Maybe a better way to phrase it is that a report from the investigator could qualify what they considered/found when they said the claims were false, baseless etc, and any evidence they found/data they had access to. (E.g. if they could look at all internal communication but their data retention policy is 6 months and this happened 7 months ago, its not the same as not finding anything)
For example, "allegations of sexual harassment were ignored or not addressed" is a wide range. It could be there were no allegations recorded from the employee (as in, they weren't reported), or they were addressed by a slap on the wrist or a "just don't do that again" to introducing workplace behaviour training, forcing the perpetrator to go through it, suspending them without pay and so on.
You are right it's not proof of no wrongdoing, but it would serve as proof that they handled things in a generally suitable manner, rather than that they managed to twist things around to check a box for the investigator.
I wonder if this will also have a reverse tail end effect.
Company uses AI (with devs) to produce a large amount of code -> code is in prod for a few years with incremental changes -> dev roles rotate or get further reduced over time -> company now needs to modernize and change very large legacy codebase that nobody really understands well enough to even feed it Into the AI -> now hiring more devs than before to figure out how to manage a legacy codebase 5-10x the size of what the team could realistically handle.
Writing greenfield code is relatively easy, maintaining it over years and keeping it up to date and well understood while twisting it for all new requirements - now that's hard.