amal66 tries to stop database drift before it reaches main

amal66 identified a mismatch between the database blueprint used for new installations and the change history used to upgrade existing deployments. The underlying database behavior was the same, but formatting differences caused the platform's comparison check to treat the two paths as different.

The proposal updates the fresh-install blueprint to match the already-issued upgrade exactly, then asks maintainers to make the comparison a required check before changes can land on the main branch. That would turn a warning that can linger into a release safeguard. The pull request closed without being merged.