What bothers me personally the most is trying to hide it. Why did you remove Claude's (or whatever you used, but looks like opus to me from the style) co-author info?
I'm willing to use (semi-)vibecoded projects under certain circumstances, but I like to know up front what I'm getting. The github contributors list makes that easy to see as long as people don't try to hide it.
I don't know if it's just solely how I use them, but when I've had Gemini commit and push things, it has never added a co-author or anything. I've recently been playing with Claude and Opus 5, and it only does it maybe 75% of the time. I truly don't know why
I don't have a good defense here, it's fair. But part of that was because of messy commit history and I wanted to have a clean commit history. Maybe it's not a good reason as well, but it was my real intention and my desire of perfectionism :) reason is that I wanted to take the full control, when ai do the commits you normally don't check the code and you loose the control, well I think it's the most important thing. But Going forward, for building trust, definitely take your recommendation. The actual design, the report schema especially, came out of around 30 interviews with people who handle backup testing as part of their job. Thank you for the feedback.