In the future, when a board can be ordered/grouped by author or assignee (or maybe custom fields), what should dragging a card within a column do?

Some old migrations call PhabricatorSearchWorker::queueDocumentForIndexing(). This no longer works after D20200 because the PHP implementation expects a dateCreated column to exist, but it won't exist until 20190220.daemon_worker.completed.02.sql runs.

I'm looking at these storage/backend changes:

• The "<<" and ">>" indicators are rendering in places where indentation has changed but the entire line is also different. This is not intended.
• The ScopeEngine can raise an exception on diffs with partial context. We should probably just skip this feature if we're missing context.
• The indent depth indicators are probably generally too bright / high-vis.
• There's no color blind scheme for the indicators.
• The indentation indicators in one-up mode aren't great (?)

Note that T6791 has an example of a change where removing the whitespace options is going to cause a behavioral regression. Here's an example:

See PHI701. This behavior is not ideal:

I'm going to start here, and implement this proposed rule, which I think is the simpler and more intuitive of the proposals:

bin/config set should warn you when a stronger database value exists, and point you toward bin/config delete --database.