v0.2.5

rudbman 0.2.5 — stronger write protection, and safer handling of failed saves and rollbacks.

• A read-shaped opening no longer hides a write from the safety checks.
  The query pane now looks inside CTEs and at the statement they lead into,
  checks the target of EXPLAIN, and recognises SELECT INTO. A modifying CTE
  or an EXPLAIN ANALYZE UPDATE goes through write confirmation and the
  read-only gate; syntax the classifier cannot place is treated
  conservatively. Database permissions remain the final protection, since a
  SELECT can still call a function with side effects.

• A failed rollback leaves the connection unavailable until reconnection.
  Restoring auto-commit after a rollback failure could commit an uncertain
  transaction. That restoration now stops, further commands are refused,
  and the error asks you to reconnect and inspect the result. Open cursors
  can still be closed. Transfers follow the same rule for a failed rollback
  of their unfinished batch.

• Failed settings and theme saves keep the previous file. Each save
  writes and syncs a separate temporary sibling before replacement, and a
  failure removes only that temporary file. The theme-store fix comes from
  the shared rugpui update.

The Windows installer keeps its existing application identity and registry
entry, so installations of 0.2.4 can be upgraded in place.

What's Changed

• Release rudbman 0.2.5 with stronger write protection by @xcomart in #43

Full Changelog: v0.2.4...v0.2.5