Answer
Check how the install manifest was generated for that build — if the tooling that produces it wasn't run in upgrade mode (or ran against the wrong baseline), it can emit fresh-install-style annotations instead of upgrade deltas, which then causes the actual database changes to be skipped rather than applied; regenerating it correctly for an upgrade context is the fix, not troubleshooting the database changes themselves.