Changed
- Oikos → Yuvomi migration (automatic, no user action required): the SQLite database file (
oikos.db→yuvomi.db), the session cookie, browser storage keys, service-worker caches, the API-token prefix, and internal web-component/global identifiers are renamed to Yuvomi. On the first start after updating, an existing database is migrated in place, you stay signed in (the session cookie is migrated seamlessly), and stored preferences carry over. Existing Docker / Podman / Unraid / TrueNAS installations keep receiving updates without editing any configuration — the legacyghcr.io/ulsklyc/oikosimage mirror is retained permanently, and awindow.oikosalias keeps pre-rename third-party modules working. - Default database path for new installations is now
/data/yuvomi.dbacross all deploy targets (Docker Compose, Podman, Portainer, Unraid, TrueNAS, Quadlet). Existing/data/oikos.dbinstalls are migrated automatically on boot; customDB_PATHvalues are left untouched. - Database backups are now written with a
yuvomi-backup-filename prefix; previously createdoikos-backup-files remain restorable. - New API tokens use the
yuvomi_prefix; existingoikos_tokens remain valid.