Annotate a file (blame)

Annotate the current master version of src/auth.js to show who last changed each line and the commit hash. Produce a short summary of any lines touched by Claire in the last three commits, and include links to those commit messages so I can review her intent.

Before I run blame on src/auth.js for the security review, make it easier for the auditor: surface lines that touch credential handling at the top, group blame output by author with counts, and flag recent large rewrites that need reading. Highlight commits that include 'auth' or 'token' in their messages.

Security pinged me about a suspicious change in src/auth.js and pointed to a line I didn't write. I ran blame and it shows Claire changed that line three commits ago but her message was terse. I'm worried the change was an accidental regression or a quick workaround. I don't know Claire's intent and I can't risk shipping this. What's the best way to diagnose whether that line is safe and how should I approach Claire to get a proper explanation without accusing her?

On every security review we keep spending hours blaming dozens of files to track responsibility for small security-adjacent edits; this shoelaces our velocity and creates friction with engineers who feel policed. Where are we losing credibility and time in how we use blame, and what habits or team agreements should change so audits are faster and less adversarial?