foolish-bandit renames Mike to Gary, but only skin-deep
A fresh fork swaps every visible "Mike" for "Gary" - while the plumbing underneath still answers to its old name.
This is the founding move of foolish-bandit's fork: rename the product. Everywhere a user can see it, "Mike" becomes "Gary." The assistant now introduces itself as Gary in chat, the sidebar and page titles read Gary, and - a nice touch for litigators - tracked-changes edits exported to Word show "Gary" as the author in the Review pane.
What hasn't changed is the machinery behind the curtain. Database tables, storage conventions, and internal naming all still use Mike's original scheme. The team kept the change deliberately shallow to avoid breaking anything, which is sensible - but anyone planning to actually deploy this should know the rebrand is cosmetic. You'll hit a few spots where the old name is baked into infrastructure defaults and have to decide whether to live with it or override at setup.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?