1.6.2-1

[1.6.2-1] - 2026-08-10

Fixed

• The local database mirror still could not be switched on from the UI. 1.6.2 fixed a genuine defect on that path, but not the one operators were hitting, so the symptom was unchanged: the checkbox unticked itself a few seconds after being ticked, DATA_DIR/db_mirror/ never grew past the owner.json marker written at startup, and nothing appeared in the app log or the browser console. The toggle had no change listener. Every other control in App settings registers addEventListener('change', saveAppSettings), and saveAppSettings() did read s-db-mirror-enabled into its payload — but nothing ever called it when that checkbox changed, so ticking the box issued no request at all. loadStorageStatus() then reset the box from the effective state on its next poll, which looks identical to a save being rejected. Nothing was ever persisted, which is also why restarting the container did not help, and why GET /api/storage-status reported last_sync_at: null — not a failed sync, but no attempt ever made.
  • LLAMAMAN_DB_MIRROR=1 was the only way to turn the mirror on in 1.6.1 and 1.6.2. The env var is read directly by resolve_enabled() at startup and never went through the UI path.
  • 1.6.2's merge_settings fix remains necessary: with the listener restored but that fix absent, ticking the box would persist the setting to the database and leave it inert until the next restart. Two independent defects sat on the same path, so neither fix alone made the feature work — which is why 1.6.2 changed nothing observable.