Merge branch 'main' into feat/login-auto-model-v2

Author: anandgupta42

CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.5.17] - 2026-04-02
+
+### Added
+
+- **Custom dbt `profiles.yml` path resolution** — Altimate Code now resolves `profiles.yml` using dbt's standard priority: explicit path → `DBT_PROFILES_DIR` env var → project-local `profiles.yml` → `~/.dbt/profiles.yml`. Teams using `DBT_PROFILES_DIR` in CI get zero-friction auto-discovery. Jinja `{{ env_var('NAME') }}` patterns are resolved automatically. A warning is shown when `DBT_PROFILES_DIR` is set but the file is not found. (#605)
+
+### Fixed
+
+- **ClickHouse: SQL comment injection bypass** — Comments could previously mask write statements from the read-only LIMIT guard. String literals are now stripped before comment removal to prevent false matches. (#591)
+- **ClickHouse: `LowCardinality(Nullable(...))` nullability** — Schema inspection previously reported these columns as non-nullable; now correctly detected as nullable. (#591)
+- **ClickHouse: connection lifecycle guards** — All query methods now throw a clear error if called before `connect()`, preventing cryptic TypeErrors. (#591)
+- **ClickHouse: `binds` parameter handling** — Queries with parameterized binds no longer throw a driver error; the parameter is safely ignored (ClickHouse uses `query_params` natively). (#591)
+- **Stale file retry loops on WSL and network drives** — `FileTime.read()` now uses filesystem mtime instead of wall-clock, eliminating 782-iteration retry loops caused by clock skew on WSL (NTFS-over-9P), NFS, and CIFS mounts. Set `OPENCODE_DISABLE_FILETIME_CHECK=true` as escape hatch if needed. (#611)
+- **Error classification: `file_stale` split and keyword fix** — `file_stale` is now a distinct error class; HTTP 4xx errors no longer misclassify as validation failures; restored `"does not exist"` keyword for SQL errors like `"column foo does not exist"`. (#611, #614)
+
 ## [0.5.16] - 2026-03-30
 
 ### Added

README.md

@@ -47,7 +47,7 @@ export OPENAI_API_KEY=your_key      # OpenAI
 altimate /discover
 ```
 
-`/discover` auto-detects dbt projects, warehouse connections (from `~/.dbt/profiles.yml`, Docker, 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

@@ -467,10 +467,33 @@ The `/discover` command can automatically detect warehouse connections from:
 
 | Source | Detection |
 |--------|-----------|
-| dbt profiles | Parses `~/.dbt/profiles.yml` |
+| dbt profiles | Searches for `profiles.yml` (see resolution order below) |
 | Docker containers | Finds running PostgreSQL, MySQL, SQL Server, and ClickHouse containers |
 | Environment variables | Scans for `SNOWFLAKE_ACCOUNT`, `PGHOST`, `DATABRICKS_HOST`, etc. |
 
+### dbt profiles.yml resolution order
+
+When discovering dbt profiles, altimate checks the following locations **in priority order** and uses the first one found:
+
+| Priority | Location | Description |
+|----------|----------|-------------|
+| 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 | `<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.
+
+```bash
+# Option 1: Set the environment variable
+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
+```
+
 See [Warehouse Tools](../data-engineering/tools/warehouse-tools.md) for the full list of environment variable signals.
 
 ## Testing Connections

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** | Bridge call to parse `~/.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 `~/.dbt/profiles.yml` configured:
+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 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 `~/.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,13 +55,13 @@ altimate --print-logs --log-level DEBUG
 
 **Solutions:**
 
-1. **If using dbt:** Run `altimate-dbt init` to set up the dbt integration. The CLI will use your `profiles.yml` automatically, so no separate connection config is needed.
+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
-3. Verify the role/user has the required permissions
-4. For Snowflake: ensure the warehouse is not suspended
-5. For BigQuery: check that the service account has the required IAM roles
+5. Verify the role/user has the required permissions
+6. For Snowflake: ensure the warehouse is not suspended
+7. For BigQuery: check that the service account has the required IAM roles
 
 ### MCP Server Initialization Failures
 

packages/opencode/src/altimate/native/connections/dbt-profiles.ts

@@ -95,13 +95,41 @@ function mapConfig(dbtType: string, dbtConfig: Record<string, unknown>): Connect
   return config
 }
 
+/**
+ * Resolve the profiles.yml path using dbt's standard priority order:
+ * 1. Explicit path (if provided)
+ * 2. DBT_PROFILES_DIR environment variable
+ * 3. Project-local profiles.yml (in dbt project root)
+ * 4. ~/.dbt/profiles.yml (default)
+ */
+function resolveProfilesPath(explicitPath?: string, projectDir?: string): string {
+  if (explicitPath) return explicitPath
+
+  const envDir = process.env.DBT_PROFILES_DIR
+  if (envDir) {
+    const envPath = path.join(envDir, "profiles.yml")
+    if (fs.existsSync(envPath)) return envPath
+    // Warn when DBT_PROFILES_DIR is set but profiles.yml not found there —
+    // dbt CLI would error here, we fall through for graceful discovery
+    console.warn(`[dbt-profiles] DBT_PROFILES_DIR is set to "${envDir}" but no profiles.yml found there, falling through`)
+  }
+
+  if (projectDir) {
+    const projectPath = path.join(projectDir, "profiles.yml")
+    if (fs.existsSync(projectPath)) return projectPath
+  }
+
+  return path.join(os.homedir(), ".dbt", "profiles.yml")
+}
+
 /**
  * Parse dbt profiles.yml and return discovered connections.
  *
- * @param profilesPath - Path to profiles.yml. Defaults to ~/.dbt/profiles.yml
+ * @param profilesPath - Explicit path to profiles.yml
+ * @param projectDir - dbt project root directory (for project-local profiles.yml)
  */
-export async function parseDbtProfiles(profilesPath?: string): Promise<DbtProfileConnection[]> {
-  const resolvedPath = profilesPath ?? path.join(os.homedir(), ".dbt", "profiles.yml")
+export async function parseDbtProfiles(profilesPath?: string, projectDir?: string): Promise<DbtProfileConnection[]> {
+  const resolvedPath = resolveProfilesPath(profilesPath, projectDir)
 
   if (!fs.existsSync(resolvedPath)) {
     return []

packages/opencode/src/altimate/native/connections/register.ts

@@ -409,7 +409,7 @@ register("schema.inspect", async (params: SchemaInspectParams): Promise<SchemaIn
 // --- dbt.profiles ---
 register("dbt.profiles", async (params: DbtProfilesParams): Promise<DbtProfilesResult> => {
   try {
-    const connections = await parseDbtProfiles(params.path)
+    const connections = await parseDbtProfiles(params.path, params.projectDir)
     return {
       success: true,
       connections,

packages/opencode/src/altimate/native/types.ts

@@ -908,6 +908,8 @@ export interface DbtLineageResult {
 
 export interface DbtProfilesParams {
   path?: string
+  /** dbt project root directory — used to find project-local profiles.yml */
+  projectDir?: string
 }
 
 export interface DbtProfileConnection {