Tom reads the fine print
Ask Tom who built a feature and he now searches merged pull request descriptions, not just titles, matching your keywords in any order. Authors come back with their local @handles when they are members here.
You ask Tom who added bookmarks, and back comes a pull request whose title never mentions the word. The word was buried in the description. The author line reads @alice-local, the handle that person uses on this site, rather than alice, the raw GitHub login.
Credit goes to paulinevos, who taught Tom to read past titles and to check handles before printing them. Tom splits your query into words, quotes each one, and searches both the title and body of merged production pull requests, plus non-merge commit messages. Every word must match, in any order. Each answer carries up to five pull requests and five commits, two searches per reply, cached for fifteen minutes.
The @ is earned. Tom matches each author's GitHub account number against onboarded members, skips the placeholder accounts left behind by renames, and repeats that lookup on every answer even when the GitHub results are cached, so a fresh rename or a deleted account shows up right away.
One catch. Tom searches descriptions but never gets to read them. Only the title, link, author and merge date travel back, so he can find the pull request where someone explained the feature and still not be able to tell you what that explanation said.