terpstra-209 gives web-chat edits a real author

Document histories now better reflect who actually proposed a change.

workflowcompliance

Anyone reviewing a document through the web chat will now have proposed revisions labelled with the person who made them, using their profile name or email address. Previously, every revision appeared to come from Mike, even when several people were involved.

It is a small change with a substantial audit-trail payoff. Lawyers and legal-ops staff can distinguish their own changes from colleagues' without guessing from the document history. Where a user profile lacks usable details, the system still falls back to Mike, so some records may remain imprecise.

So what Teams sharing legal documents should care because reliable attribution makes review, accountability and handover easier.

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from terpstra-209/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`45d8ff3d`	fix(docs): attribute web-UI tracked changes to the acting user, not "Mike"	terpstra-209	2026-08-24	↗ GitHub
commit body Web-chat edit_document hardcoded the tracked-change author to the literal string "Mike" regardless of who was signed in, unlike the Word add-in (which inherits the signed-in Word identity via Office.js). Look up the user's display_name/email instead. LOCAL PATCH (not upstream).

SHA

Subject

Author

Date

45d8ff3d

fix(docs): attribute web-UI tracked changes to the acting user, not "Mike"

terpstra-209

2026-08-24

↗ GitHub

commit body

Web-chat edit_document hardcoded the tracked-change author to the literal
string "Mike" regardless of who was signed in, unlike the Word add-in
(which inherits the signed-in Word identity via Office.js). Look up the
user's display_name/email instead. LOCAL PATCH (not upstream).

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1413.md from inside the repo you want the changes in.