docs: use platform-neutral <home>/.dbt/ notation instead of Unix-specific ~/.dbt/

Replace hardcoded `~/.dbt/profiles.yml` with `<home>/.dbt/profiles.yml` across
all 6 doc files. Add Windows path example in the warehouses config page.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: anandgupta42

README.md

@@ -47,7 +47,7 @@ export OPENAI_API_KEY=your_key      # OpenAI
 altimate /discover
 ```
 
-`/discover` auto-detects dbt projects, warehouse connections (from `profiles.yml` — checks `DBT_PROFILES_DIR`, project directory, then `~/.dbt/`; plus Docker and environment variables), and installed tools (dbt, sqlfluff, airflow, dagster, and more). Skip this and start building — you can always run it later.
+`/discover` auto-detects dbt projects, warehouse connections (from `profiles.yml` — checks `DBT_PROFILES_DIR`, project directory, then `<home>/.dbt/`; plus Docker and environment variables), and installed tools (dbt, sqlfluff, airflow, dagster, and more). Skip this and start building — you can always run it later.
 
 > **Headless / scripted usage:** `altimate --yolo` auto-approves all permission prompts. Not recommended with live warehouse connections.
 

docs/docs/configure/warehouses.md

@@ -480,7 +480,7 @@ When discovering dbt profiles, altimate checks the following locations **in prio
 | 1 | Explicit path | If you pass a `path` parameter to the `dbt_profiles` tool |
 | 2 | `DBT_PROFILES_DIR` env var | Standard dbt environment variable — set it to the directory containing your `profiles.yml` |
 | 3 | Project-local `profiles.yml` | A `profiles.yml` in your dbt project root (next to `dbt_project.yml`) |
-| 4 | `~/.dbt/profiles.yml` | The global default location |
+| 4 | `<home>/.dbt/profiles.yml` | The global default location (e.g., `~/.dbt/` on macOS/Linux, `%USERPROFILE%\.dbt\` on Windows) |
 
 This means teams that keep `profiles.yml` in their project repo (a common pattern for CI/CD) will have it detected automatically — no extra configuration needed.
 
@@ -489,6 +489,7 @@ This means teams that keep `profiles.yml` in their project repo (a common patter
 export DBT_PROFILES_DIR=/path/to/your/project
 
 # Option 2: Just put profiles.yml next to dbt_project.yml
+# Copy from default location (macOS/Linux)
 cp ~/.dbt/profiles.yml ./profiles.yml
 altimate /discover
 ```

docs/docs/data-engineering/tools/warehouse-tools.md

@@ -53,7 +53,7 @@ env_bigquery  | bigquery | GOOGLE_APPLICATION_CREDENTIALS
 | **Git** | `git` commands (branch, remote) |
 | **dbt project** | Walks up directories for `dbt_project.yml`, reads name/profile |
 | **dbt manifest** | Parses `target/manifest.json` for model/source/test counts |
-| **dbt profiles** | Searches for `profiles.yml`: `DBT_PROFILES_DIR` env var → project root → `~/.dbt/profiles.yml` |
+| **dbt profiles** | Searches for `profiles.yml`: `DBT_PROFILES_DIR` env var → project root → `<home>/.dbt/profiles.yml` |
 | **Docker DBs** | Bridge call to discover running PostgreSQL/MySQL/MSSQL containers |
 | **Existing connections** | Bridge call to list already-configured warehouses |
 | **Environment variables** | Scans `process.env` for warehouse signals (see table below) |

docs/docs/getting-started/quickstart-new.md

@@ -34,13 +34,13 @@ altimate
 
 ### Option A: Auto-detect from dbt profiles
 
-If you have a `profiles.yml` — either in `~/.dbt/`, in your project repo, or pointed to by `DBT_PROFILES_DIR`:
+If you have a `profiles.yml` — either in your home directory's `.dbt/` folder, in your project repo, or pointed to by `DBT_PROFILES_DIR`:
 
 ```bash
 /discover
 ```
 
-Altimate searches for `profiles.yml` in this order: `DBT_PROFILES_DIR` env var → project root (next to `dbt_project.yml`) → `~/.dbt/profiles.yml`. It reads your dbt profiles and creates warehouse connections automatically. You'll see output like:
+Altimate searches for `profiles.yml` in this order: `DBT_PROFILES_DIR` env var → project root (next to `dbt_project.yml`) → `<home>/.dbt/profiles.yml`. It reads your dbt profiles and creates warehouse connections automatically. You'll see output like:
 
 ```
 Found dbt project: jaffle_shop (dbt-snowflake)

docs/docs/getting-started/quickstart.md

@@ -189,7 +189,7 @@ You can also set a smaller model for lightweight tasks like summarization:
 altimate /discover
 ```
 
-Auto-detects your dbt projects, warehouse credentials from `profiles.yml` (checks `DBT_PROFILES_DIR`, then your project directory, then `~/.dbt/profiles.yml`), running Docker containers, and environment variables (`SNOWFLAKE_ACCOUNT`, `PGHOST`, `DATABASE_URL`, etc.).
+Auto-detects your dbt projects, warehouse credentials from `profiles.yml` (checks `DBT_PROFILES_DIR`, then your project directory, then the default `<home>/.dbt/profiles.yml`), running Docker containers, and environment variables (`SNOWFLAKE_ACCOUNT`, `PGHOST`, `DATABASE_URL`, etc.).
 
 ### Manual configuration
 

docs/docs/reference/troubleshooting.md

@@ -55,7 +55,7 @@ altimate --print-logs --log-level DEBUG
 
 **Solutions:**
 
-1. **If using dbt:** Run `/discover` — it automatically finds your `profiles.yml` from `DBT_PROFILES_DIR`, your project directory, or `~/.dbt/profiles.yml`. If your `profiles.yml` is in a custom location, set `export DBT_PROFILES_DIR=/path/to/dir`.
+1. **If using dbt:** Run `/discover` — it automatically finds your `profiles.yml` from `DBT_PROFILES_DIR`, your project directory, or `<home>/.dbt/profiles.yml`. If your `profiles.yml` is in a custom location, set `DBT_PROFILES_DIR` to the directory containing it.
 2. **If not using dbt:** Add a connection via the `warehouse_add` tool, `~/.altimate-code/connections.json`, or `ALTIMATE_CODE_CONN_*` env vars.
 3. Test connectivity: use the `warehouse_test` tool with your connection name.
 4. Check that the warehouse hostname and port are reachable