Often an AI reads info that might be outdated and then assumes it is right. It doesn't really have the concept of "this is old info, maybe I shouldn't trust it". How about creating a hook for when an agent reads one of the journal files that checks the file mtime and outputs a "this content is x days old, be sure to verify it is not outdated" as additional info.

Secondly, I don't think an AI agent has any way to "skim" content. I mean it either reads all or parts of the content or it greps it. Why not do some index.md file that lists all the journal files together with a short description (inspired by the Open Knowledge Format)?

The QA guys flushed out the big bugs and many of the small ones. Without any proof, I imagine something like 99% of the customers would hit only a few bugs, that they are used to compensate for (reloading pages etc), leading to a view of the product as having good quality. I was wrong: the sw quality is poor, but the percieved quality is good. I would of course prefer to do sw of much better quality.