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.

I don't think those use cases are necessarily bad, there's just a little bit of a slippery slope to, say, "Git sure looks a lot like a database" and then support issues like "it's hard to manage my 3,500 automated review requests".

Adding a data point, "Foist Upon" was a surprise hit among the developers here and additionally we have successfully utilized the conduit API to take advantage of foisting

There are probably also some off-label use cases where, for example, bots create revisions on behalf of users. I'm not thrilled about these, ...

oops 😬

This promoted and has been in the Phacility cluster for a few days without issues.

Presuming this is resolved until evidence to the contrary arises.

See also T13068, which suggests rendering mentions in a special style when the user has muted the object.

That covered everything that looked low-hanging.

See T13602 for eventual followup.

See T13125 and PHI1997 for followup.

See also PHI1987 for another case of this.

• When rendering a "no view permission" hovercard, it would be nice to annotate it with an explicit "The user can't see this object" piece of context information.

• Context objects don't make it into timeline rendering engines.
• Context objects don't make it into comment previews.

The broader structural issue here is:

A second issue is that some of the "publish" behavior depends on the commit/revision relationship. This can still be sequenced correctly entirely in the publish daemon, but "close related revisions" and "publish the commit" are not entirely independent.

Will this feature come to diffusion for audit workflows?

• In previews, suggestions aren't highlighted properly (likely just missing CSS).