Push to staging fails: object hash mismatch during delta reconstruction

Symptom

muse push staging main fails with:

object_id hash mismatch for 'sha256:4011522b96b7cd254c0d9c51bfc00a5f31cd0784105cecdea93531c451d5ff20': declared=4011522b96b7cd25… actual=42c6c95d6f4b9610…

Context

• Push contains 7 objects, 5 deltas
• Local push (to localhost:1337) succeeds cleanly
• Staging push fails at the server's hash verification step
• The staging server reconstructs a delta and gets a different hash than the client declared
• --force does not bypass it (it's a server-side integrity check, not a ref conflict)

Impact

Code is already deployed to staging via deploy.sh (image e0293abd-20260507100332). Only muse commit history is missing from the staging hub.

Likely cause

Delta reconstruction on the staging server is using a different base object than the client expected — possible object store drift between local and staging.