🖋️ Scribe: Clarify .env file usage for standalone scripts

[fderuiter]

💡 What: Added a clarifying note to the README.md Configuration section regarding how .env files are loaded.

🎯 Why: While the imednet CLI automatically uses python-dotenv to load .env files, the SDK's load_config() method only checks existing environment variables (os.getenv). This mismatch creates a confusing onboarding path where a new user might copy an example script, create a .env file, and still receive an authentication error.

🧠 Cognitive Impact: Prevents a common "first-run crash" for users writing custom scripts, reducing debugging time and clarifying the boundaries between the CLI's magic behavior and the SDK's explicit requirements.

📖 Preview:

Note: imednet.load_config() only reads from existing environment variables (os.getenv). While the CLI automatically loads .env files, standalone Python scripts must explicitly call load_dotenv() from the python-dotenv package to read from a .env file before calling load_config().

---

PR created automatically by Jules for task 10636674436849639645 started by @fderuiter

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.