Move .env.example into src/ (04 Agentic CLM MicroHack)

03-Azure/01-04-AI/04_Agentic_Contract_Lifecycle_Management/challenges/challenge-01.md

@@ -201,7 +201,7 @@ point your `.env` at them using the values on your **lab dashboard**.
 **Step 3a — create your `.env`** from the template (Codespace terminal, at the repo root):
 
 ```bash
-cp .env.example .env
+cp src/.env.example .env
 ```
 
 **Step 3b — copy your dashboard values into `.env`.** Open `.env` in the Codespace editor and fill in
@@ -219,7 +219,7 @@ the values shown on your lab dashboard:
 
 > [!TIP]
 > The model names plus `AZURE_SEARCH_INDEX` (`clm-corpus`) and `AZURE_SEARCH_CONNECTION_NAME`
-> (`clm-search`) already have the right defaults in `.env.example`, so at minimum you only need to
+> (`clm-search`) already have the right defaults in `src/.env.example`, so at minimum you only need to
 > paste the two **endpoints** and the **App Insights connection string**. Paste the model names too if
 > your dashboard shows different values.
 

03-Azure/01-04-AI/04_Agentic_Contract_Lifecycle_Management/challenges/challenge-02.md

@@ -390,7 +390,7 @@ You're done when:
 | `get_contract_status` says "not found" | Use a known id (`CT-4821`, `CT-3390`, `CT-5102`, `CT-2765`, `CT-6033`) — the error message lists them. |
 | `400 … Access denied` during retrieval or setup | The Foundry account/project identities need Search reader/contributor roles, and the Search identity needs Cognitive Services User on the Foundry account. Re-run provisioning and allow time for RBAC propagation. |
 | `429 rate_limit_exceeded` on `gpt-5.4` mid-demo | Deployment throughput throttling. The demo now retries with exponential backoff and isolates each prompt (`run_agent_with_retry`), so it rides through and continues. If it persists, raise the deployment capacity or space out prompts. |
-| `Missing required environment variable 'AZURE_AI_PROJECT_ENDPOINT'` | Re-run Challenge 1's deploy (which writes `.env`) or copy `.env.example` → `.env` and fill it in. |
+| `Missing required environment variable 'AZURE_AI_PROJECT_ENDPOINT'` | Re-run Challenge 1's deploy (which writes `.env`) or copy `src/.env.example` → `.env` and fill it in. |
 
 ## 🔗 How this fits
 

03-Azure/01-04-AI/04_Agentic_Contract_Lifecycle_Management/src/clm_common/config.py

@@ -33,7 +33,7 @@ def _get(name: str, default: str | None = None, required: bool = False) -> str |
     if required and not value:
         raise RuntimeError(
             f"Missing required environment variable '{name}'. "
-            f"Run Challenge 1's deploy script or copy .env.example → .env and fill it in."
+            f"Run Challenge 1's deploy script or copy src/.env.example → .env and fill it in."
         )
     return value
 

03-Azure/01-04-AI/04_Agentic_Contract_Lifecycle_Management/src/scripts/upload_corpus_to_sharepoint.py

@@ -81,7 +81,7 @@ def get_token() -> str:
         _fail(
             "Missing SharePoint settings: "
             + ", ".join(missing)
-            + ".\n  Set them in .env (see .env.example / challenge-0 README)."
+            + ".\n  Set them in .env (see src/.env.example / challenge-0 README)."
         )
 
     from azure.identity import ClientSecretCredential

03-Azure/01-04-AI/04_Agentic_Contract_Lifecycle_Management/src/scripts/write_env.py

@@ -22,7 +22,7 @@
 REPO_ROOT = Path(__file__).resolve().parents[2]
 ENV_PATH = REPO_ROOT / ".env"
 
-# Keys sourced from Bicep outputs (via azd env). Fall back to the .env.example
+# Keys sourced from Bicep outputs (via azd env). Fall back to the src/.env.example
 # defaults for the constant-valued ones if an output is missing.
 DEFAULTS = {
     "MODEL_ORCHESTRATOR": "gpt-5.4",

03-Azure/01-04-AI/04_Agentic_Contract_Lifecycle_Management/walkthrough/challenge-01/solution-01.md

@@ -46,7 +46,7 @@ az account set --subscription "<your-subscription-id>"
 ### Task 3 · Connect to your provisioned resources
 **MicroHack event — resources are already provisioned; you don't deploy.** Point `.env` at the values on your **lab dashboard**:
 ```bash
-cp .env.example .env
+cp src/.env.example .env
 # then paste the dashboard values into .env (the two endpoints + the App Insights connection string)
 ```
 
@@ -57,7 +57,7 @@ cp .env.example .env
 | **AppInsightsConnectionString** | `APPLICATIONINSIGHTS_CONNECTION_STRING` |
 | **ModelOrchestrator / Drafting / ClauseRisk / Renewal** | `MODEL_ORCHESTRATOR` / `MODEL_DRAFTING` / `MODEL_CLAUSE_RISK` / `MODEL_RENEWAL` |
 
-The model names + `AZURE_SEARCH_INDEX` (`clm-corpus`) / `AZURE_SEARCH_CONNECTION_NAME` (`clm-search`) already default in `.env.example`, so at minimum paste the two **endpoints** + the **App Insights** string. Leave `SHAREPOINT_*` and the Challenge 5 `MICROSOFT_APP_*` / `TEAMS_*` blank for now.
+The model names + `AZURE_SEARCH_INDEX` (`clm-corpus`) / `AZURE_SEARCH_CONNECTION_NAME` (`clm-search`) already default in `src/.env.example`, so at minimum paste the two **endpoints** + the **App Insights** string. Leave `SHAREPOINT_*` and the Challenge 5 `MICROSOFT_APP_*` / `TEAMS_*` blank for now.
 
 <details>
 <summary><strong>Self-hosting? One <code>azd up</code> provisions everything and writes <code>.env</code> for you</strong></summary>