feat: Neon database migration & Family History feature

[ccraig09]

Summary

This PR migrates the database from local Docker PostgreSQL to Neon Serverless Postgres and implements a new Family Medical History feature.

Changes

Database Migration (Docker → Neon)

• ❌ Removed docker-compose.yml - no more Docker dependency
• ✅ Updated prisma.config.ts to load .env.local for Neon connection
• ✅ Installed neon-postgres agent skill for AI-assisted workflows

Family History Feature

• ✅ Added familyHistory JSON field to UserProfile schema
• ✅ Created server actions: getFamilyHistory, updateFamilyHistory
• ✅ Built FamilyHistoryCard UI component
• ✅ Integrated into Settings page

Testing

• ✅ Browser-tested: Login → Settings → Add entry → Data persists
• ✅ Schema pushed to Neon cloud successfully

Screenshots

Feature verified working in browser during development.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
evernest	Building	Preview, Comment	Feb 3, 2026 7:01pm

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
26776333	Triggered	PostgreSQL Credentials	13cfad5	.agent/skills/neon-postgres/references/neon-rest-api/projects.md	View secret
26776334	Triggered	PostgreSQL Credentials	13cfad5	.agent/skills/neon-postgres/references/neon-rest-api/projects.md	View secret
26776335	Triggered	Neon Api Key	13cfad5	.agent/skills/neon-postgres/references/neon-rest-api/keys.md	View secret
26776336	Triggered	PostgreSQL Credentials	13cfad5	.agent/skills/neon-postgres/references/neon-rest-api/branches.md	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[github-actions]

🤖 Hi @ccraig09, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[github-actions]

🤖 I'm sorry @ccraig09, but I was unable to process your request. Please see the logs for more details.