Chore: Remove .env from version control for security

- Stop tracking .env file in git (was already in .gitignore)
- .env file remains on local filesystem with PostgreSQL VM connection
- Sensitive credentials (database password, API keys) are no longer committed
- Each developer/PC can maintain their own .env with appropriate secrets

For new setup, copy .env.example to .env and fill in values.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

.claude/settings.local.json

@@ -126,7 +126,9 @@
       "Bash(rm \"prisma/dev.db\")",
       "Bash(rm -f \"prisma/dev.db-journal\")",
       "Bash(git commit -m 'Chore: Migrate database from SQLite to PostgreSQL on VM *)",
-      "Bash(git pull *)"
+      "Bash(git pull *)",
+      "Bash(git rm *)",
+      "Bash(git commit -m 'Chore: Remove .env from version control for security *)"
     ]
   }
 }