FinTrack - Releases

Added — Phase 1: PWA UI layout & alignment

• Login/PIN screens now vertically centered in the viewport, not just horizontally.
• Accounts, Categories, Budgets, Transfers: list rows now lay out in a responsive grid (.list-grid, same auto-fill/minmax pattern as the dashboard's stat cards) instead of one stacked column, so wide desktop screens actually get used — still collapses to a single column on mobile.
• Accounts page: account icon/emoji now renders next to the account name (icon was already a form field and saved correctly, it just was never displayed in the list — Categories already did this correctly, Accounts now matches it).
• Search/filter boxes added to the top of the Accounts and Categories pages for live client-side filtering by name.
• Settings → About App: GitHub/PayPal/Ko-fi buttons now share one .ft-btn-link class (uniform padding, border-radius, min-width) — previously GitHub used .ft-btn-outline's sizing while the other two had their own smaller inline padding.
• Currencies → Edit Currency modal: now shows "Last updated: …" under the conversion-rate field (reusing the same fx_last_rate_ts_* settings keys the Transfer and New Transaction forms already read), updated live after a successful "Fetch live rate".

Added — Phase 2: Offline caching

• Service worker precache completed: every icon size the manifest references (72–512px, maskable, apple-touch-icon) is now precached, not just 192/512 — icons could previously 404 offline even though the app shell itself loaded fine.
• Audited offline login/PIN/session flow (bootstrap → renderPinUnlock → FT_PIN.tryUnlock → enterApp): this was already built correctly — PIN unlock tries the local IndexedDB-encrypted decrypt first and only touches the network as a secondary check, session/settings-refresh calls are all wrapped so a network failure never throws past them, and the offline-inactivity wipe check reads purely from IndexedDB. No changes needed here beyond the icon caching above.
• Deliberately not caching API responses (/index.php/...) in Service Worker Cache Storage, despite "API entry points" being requested — that data is financial and already has a correct, secure offline story via encrypted IndexedDB (see pwa-db.js/pwa-crypto.js); caching it as plaintext HTTP responses in Cache Storage as well would be a real security regression, not just a style choice, so this file keeps that boundary intact.
• Service worker cache bumped again (v6 → v7).