v0.4.4 - Profile Page Fix + Multi-User Data Isolation

[PaulAtkins88]

🐛 Bug Fixes

The profile page now saves correctly and user data is properly isolated in multi-user setups.

Fixed

• 💾 Profile page: salary and fixed expenses no longer revert on every keypress — a Mantine useForm reference loop was causing the server data to overwrite in-progress edits on every keystroke (closes [BUG] Profile fields overwrite changes and fixed expenses cannot be added #24)
• 🔒 Profile data isolation: each user's profile is now stored against their own user_id primary key — previously all users shared the same row key (id='profile'), which could corrupt data in multi-user self-hosted instances

Technical

• Removed redundant Zod re-parse in profile controller (middleware already validates)

⚠️ Migration Required

This release includes a database migration that runs automatically on backend startup.

1. Back up your database before upgrading — the migration modifies the primary key of budget_profiles
2. Migration 004-budget-profiles-user-id-primary-key.sql will:
   • Delete any orphaned profile rows (rows without a matching user account)
   • Promote user_id to PRIMARY KEY
   • Drop the old id TEXT column
3. Existing profile data for authenticated users is preserved as long as their user account is intact
4. If the migration has already run (e.g. fresh install), it is safely skipped

See CHANGELOG.md for full technical details.

---

This discussion was created from the release v0.4.4 - Profile Page Fix + Multi-User Data Isolation.