Problem: in the presence of corruption, repairDatabase is lossy and almost never the right thing to use, but in the absence of corruption, repairDatabase is non-lossy and a valid way to compact a database's file set. This has lead to complex documentation, education, and customer support issues about whether and when it's safe to run the command.

Proposal: introduce a new command that does what repairDatabase currently does, but that aborts and cleans up after itself when corruption is encountered. (For the purpose of discussion, let's call this "rebuildDatabase".)
This way, we can document rebuildDatabase as a safe, non-lossy way to compact a database, and repairDatabase as the last ditch recovery mechanism that people should exercise extra care about using.

Documentation changes needed: document a new command. Clarify documentation about an old command.