Just a point of clarification more than anything else - we've been running DO 4.5 in LegacyValidate mode for as long as the 4.5 betas have been available. We recently migrated both development and production stacks to use the 4.5 full release. In the betas for 4.5, when we had an issue with table-mapped properties not aligning with the database in Domain.Build, we'd get a super-helpful error of:

Extracted schema is not equal to the target schema. Details:
Schema comparison result: NotEqual
Has unsafe actions: true
Has column type changes: false
Compatible in ValidateLegacy mode: False

Unsafe actions:
CreateNode, Path=Tables/tblFoo/Columns/Bar

Now, instead of actually getting that, we're getting a laundry list of PropertyChange and RemoveNode actions that look as if DO is trying to operate in Perform mode, without actually getting indication on what property is causing an error on Domain.Build. Is this intended functionality or just kind of an oversight? It makes it kind of a nightmare to determine what's changed between development and production databases. Is there some sort of configuration value I'm missing in order to have it go back to the way the error handling was?