v1.88.1

[1.88.1] - 2026-10-03 — Alrescha

Fixed

• A change to the extension list that can't get the lock says so, and records it. When
  ExtensionStateMutex times out because another change is still running, it throws
  LockContentionException (a RuntimeException, as before), so a caller can answer "busy, try
  again". The schema executor's enable() and disable() record that operation as failed, with the
  reason, instead of leaving it running.