fix: load .env from current working directory, not package location

load_dotenv() without arguments searches from the calling module's
directory. When zad is installed via uv tool install, this means it
looks in the package install path instead of the user's project
directory. Fixed by passing dotenv_path='.env' which resolves from CWD.

This was the root cause of -p being "required" even after config init
had saved ZAD_PROJECT_ID to .env.

Author: anneschuth

src/zad_cli/cli.py

@@ -112,5 +112,5 @@ def main() -> None:
     """CLI entrypoint."""
     from dotenv import load_dotenv
 
-    load_dotenv()
+    load_dotenv(dotenv_path=".env")
     app()

tests/test_cli.py

@@ -194,3 +194,21 @@ def test_global_flag_after_subcommand():
     )
     err = _strip_ansi(result.stderr)
     assert "No such option" not in err
+
+
+def test_dotenv_loaded_from_cwd(tmp_path):
+    """'.env' in the user's CWD should be loaded even when zad is installed elsewhere."""
+    env_file = tmp_path / ".env"
+    env_file.write_text("ZAD_API_KEY=test-key-from-cwd\nZAD_PROJECT_ID=test-proj\n")
+    # Remove ZAD vars from env so load_dotenv can set them from .env
+    clean_env = {k: v for k, v in _PLAIN_ENV.items() if not k.startswith("ZAD_")}
+    result = subprocess.run(
+        [sys.executable, "-m", "zad_cli", "project", "status"],
+        capture_output=True,
+        text=True,
+        cwd=str(tmp_path),
+        env=clean_env,
+    )
+    err = _strip_ansi(result.stderr)
+    # Should NOT complain about missing project - it should read it from .env
+    assert "project is required" not in err