After this change, we always execute this code for any update. This is sort-of a functional change, but likely moot or moot-adjacent in practice. Previously:

(Internally, see PHI2020.)

This is relatively ripe for implementation now that inline comments support suggested edits.

This is very old, fairly vague, and doesn't have any clear modern customer interest. I'm open to implementing it, but would like a more clear/modern customer request before pursuing it.

I'm likely to break the paths constraint for frozen API method differential.query. This was added by D2788 as a Facebook-specific patch with no rationale that I can dig up, and the author didn't have any related changes from around that time.

This is very old and I can't reproduce it, and haven't seen any other reports.

I think lint could reasonably emit two warnings about this:

For now, I fixed the explicit misinformation in audit.can-author-close-audit, at least.

There are also already a bunch of tailored messages in other context:

I looked into this briefly, but I can't find a simple way to show all the current user's database permissions.

Resource (and Phame and Phurl) domains now respond to /status/.