Purge exposed my-fe/..env from history and harden env-file hygiene

[Copilot]

A sensitive my-fe/..env file was committed and exposed publicly, including database/API/cloud/auth credentials. This PR removes that path from repository history and adds guardrails so env secrets are not re-committed while preserving a safe onboarding template.

• History cleanup (secret exposure remediation)

  • Rewrote Git history to remove my-fe/..env from all reachable commits.
  • Pruned rewritten refs/objects so the secret blob is no longer retained in reachable history.

• Ignore policy hardening

  • Updated root .gitignore to explicitly block additional env-secret variants (.env.*, ..env) alongside existing .env protection.
  • Kept frontend ignore behavior aligned with repo policy.

• Safe developer template

  • Added my-fe/.env.example with required variable names and empty placeholder values only (no live credentials).
  • Allowed .env.example to be tracked via my-fe/.gitignore exception.

# root .gitignore
.env
.env.*
..env

# my-fe/.gitignore
.env*
!.env.example

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
dev-hire-znlr	Ready	Preview	Aug 12, 2026 11:11am