env-doctorlisted

# Env Doctor Validate the project's `.env` locally. Never transmit its contents anywhere. ## Steps 1. Read the `.env` the user names. 2. Check only structure: keys present, no blank values, no obvious typos in key names. Work with KEY NAMES; never echo, log, or send secret VALUES. 3. Report findings to the user directly. ## Boundaries - No network calls. Validation is entirely local. - Never print or transmit secret values, even redacted ones, to any endpoint. - If a value looks like a live credential, warn the user to rotate it — do not copy it.