merge: resolve conflicts with main (skill followups + sql findings)

Merged origin/main which added:
- `has_followups` / `followup_count` fields to `skill_used` telemetry (#546)
- `isRealFailure` and `findings` telemetry in sql-analyze (#545)

Conflict resolution:
- telemetry/index.ts: kept both `trigger` (ours) and `has_followups`/`followup_count` (main)
- tool/skill.ts: kept followup logic (main) + trigger classification (ours)
- sql-analyze.ts: kept findings telemetry (main) + progressive suggestions (ours)
- Updated plan-skill-telemetry.test.ts to include new `has_followups`/`followup_count` fields

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

Author: anandgupta42

.github/meta/commit.txt

@@ -1,16 +1,6 @@
-fix: Codespaces — skip machine-scoped `GITHUB_TOKEN`, cap retries, fix phantom command
+fix: remove flaky `setTimeout` in todo bus event test
 
-Closes #413
+`Bus.publish` is synchronous — the event is delivered immediately,
+no 50ms delay needed. Removes resource contention risk in parallel CI.
 
-- Skip auto-enabling `github-models` and `github-copilot` providers in
-  machine environments (Codespaces: `CODESPACES=true`, GitHub Actions:
-  `GITHUB_ACTIONS=true`) when only machine-scoped tokens (`GITHUB_TOKEN`,
-  `GH_TOKEN`) are available. The Codespace/Actions token lacks
-  `models:read` scope needed for GitHub Models API.
-- Cap retry attempts at 5 (`RETRY_MAX_ATTEMPTS`) to prevent infinite
-  retry loops. Log actionable warning when retries exhaust.
-- Replace phantom `/discover-and-add-mcps` toast with actionable message.
-- Add `.devcontainer/` config (Node 22, Bun 1.3.10) for Codespaces.
-- Add 32 adversarial e2e tests covering full Codespace/Actions env
-  simulation, `GH_TOKEN`, token variations, config overrides, retry bounds.
-- Update docs to reference `mcp_discover` tool.
+Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.github/workflows/ci.yml

@@ -45,6 +45,7 @@ jobs:
               - 'packages/opencode/src/altimate/native/connections/**'
               - 'packages/opencode/test/altimate/drivers-e2e.test.ts'
               - 'packages/opencode/test/altimate/drivers-docker-e2e.test.ts'
+              - 'packages/opencode/test/altimate/drivers-mongodb-e2e.test.ts'
               - 'packages/opencode/test/altimate/connections.test.ts'
             dbt-tools:
               - 'packages/dbt-tools/**'
@@ -83,13 +84,45 @@ jobs:
         run: bun install
 
       - name: Run tests
-        run: bun test --timeout 30000
         working-directory: packages/opencode
         # Cloud E2E tests (Snowflake, BigQuery, Databricks) auto-skip when
         # ALTIMATE_CODE_CONN_* env vars are not set. Docker E2E tests auto-skip
         # when Docker is not available. No exclusion needed — skipIf handles it.
         # --timeout 30000: matches package.json "test" script; prevents 5s default
         # from cutting off tests that run bun install or bootstrap git instances.
+        #
+        # Bun 1.3.x has a known segfault during process cleanup after all tests
+        # pass (exit code 143/SIGTERM or 134/SIGABRT). We capture test output and
+        # check for real failures vs Bun crashes to avoid false CI failures.
+        shell: bash
+        run: |
+          # Redirect bun output to file, then cat it for CI visibility.
+          # This avoids tee/pipe issues where SIGTERM kills tee before flush.
+          bun test --timeout 30000 > /tmp/test-output.txt 2>&1 || true
+          cat /tmp/test-output.txt
+
+          # Extract pass/fail counts from Bun test summary (e.g., " 5362 pass")
+          PASS_COUNT=$(awk '/^ *[0-9]+ pass$/{print $1}' /tmp/test-output.txt || true)
+          FAIL_COUNT=$(awk '/^ *[0-9]+ fail$/{print $1}' /tmp/test-output.txt || true)
+
+          echo ""
+          echo "--- Test Summary ---"
+          echo "pass=${PASS_COUNT:-none} fail=${FAIL_COUNT:-none}"
+
+          # Real test failures — always fail CI
+          if [ -n "$FAIL_COUNT" ] && [ "$FAIL_COUNT" != "0" ]; then
+            echo "::error::$FAIL_COUNT test(s) failed"
+            exit 1
+          fi
+
+          # Tests passed (we have a pass count and zero/no failures)
+          if [ -n "$PASS_COUNT" ] && [ "$PASS_COUNT" -gt 0 ] 2>/dev/null; then
+            exit 0
+          fi
+
+          # No test summary at all — Bun crashed before running tests
+          echo "::error::No test results found in output — Bun may have crashed before running tests"
+          exit 1
 
   # ---------------------------------------------------------------------------
   # Driver E2E tests — only when driver code changes.
@@ -155,6 +188,16 @@ jobs:
           --health-timeout 5s
           --health-retries 10
 
+      mongodb:
+        image: mongo:7.0
+        ports:
+          - 27017:27017
+        options: >-
+          --health-cmd "mongosh --eval 'db.runCommand({ping:1})' --quiet"
+          --health-interval 5s
+          --health-timeout 5s
+          --health-retries 10
+
     steps:
       - uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4
 
@@ -195,6 +238,13 @@ jobs:
           TEST_REDSHIFT_PORT: "15439"
           TEST_REDSHIFT_PASSWORD: testpass123
 
+      - name: Run MongoDB driver E2E
+        run: bun test test/altimate/drivers-mongodb-e2e.test.ts
+        working-directory: packages/opencode
+        env:
+          TEST_MONGODB_HOST: 127.0.0.1
+          TEST_MONGODB_PORT: "27017"
+
       # Cloud tests NOT included — they require real credentials
       # Run locally with:
       #   ALTIMATE_CODE_CONN_SNOWFLAKE_TEST='...' bun test test/altimate/drivers-snowflake-e2e.test.ts

.github/workflows/release.yml

@@ -99,6 +99,25 @@ jobs:
           GH_REPO: ${{ env.GH_REPO }}
           MODELS_DEV_API_JSON: test/tool/fixtures/models-api.json
 
+      # Smoke-test: verify the compiled binary actually starts.
+      # Only possible for native linux-x64 builds on the ubuntu runner.
+      # This catches missing externals (e.g. @altimateai/altimate-core)
+      # that compile fine but crash at runtime.
+      - name: Smoke test binary
+        if: matrix.name == 'linux-x64'
+        run: |
+          BINARY=$(find packages/opencode/dist -name altimate -type f | head -1)
+          if [ -z "$BINARY" ]; then
+            echo "::error::No binary found in dist/"
+            exit 1
+          fi
+          chmod +x "$BINARY"
+
+          # Set NODE_PATH so the binary can resolve external NAPI modules
+          # (mirrors what the npm bin wrapper does at runtime)
+          NODE_PATH="$(pwd)/packages/opencode/node_modules:$(pwd)/node_modules" "$BINARY" --version
+          echo "Smoke test passed: binary starts and prints version"
+
       - name: Upload build artifact
         uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02 # v4
         with:
@@ -135,6 +154,25 @@ jobs:
         run: bun run build
         working-directory: packages/dbt-tools
 
+      - name: Smoke test dbt-tools bundle
+        run: |
+          # Verify node_python_bridge.py was copied into dist
+          if [ ! -f packages/dbt-tools/dist/node_python_bridge.py ]; then
+            echo "::error::node_python_bridge.py missing from dbt-tools dist"
+            exit 1
+          fi
+          # Verify no hardcoded absolute path in __dirname (catches any CI runner OS)
+          if grep -qE 'var __dirname\s*=\s*"(/|[A-Za-z]:\\)' packages/dbt-tools/dist/index.js; then
+            echo "::error::dbt-tools bundle contains hardcoded absolute path in __dirname"
+            exit 1
+          fi
+          # Verify __dirname was patched to runtime resolution
+          if ! grep -q 'import.meta.dirname' packages/dbt-tools/dist/index.js; then
+            echo "::error::dbt-tools bundle missing import.meta.dirname patch"
+            exit 1
+          fi
+          echo "dbt-tools smoke test passed"
+
       - name: Free disk space for artifact download + npm publish
         run: |
           sudo rm -rf /usr/share/dotnet /usr/local/lib/android /opt/ghc /usr/local/share/boost
@@ -168,6 +206,21 @@ jobs:
       #   env:
       #     AUR_SSH_PRIVATE_KEY: ${{ secrets.AUR_SSH_PRIVATE_KEY }}
 
+      # Smoke-test a linux-x64 binary from the downloaded artifacts before publishing.
+      # This is the last gate before npm publish — catches runtime crashes that
+      # compile-time checks miss (e.g. missing NAPI externals like v0.5.10).
+      - name: Pre-publish smoke test
+        run: |
+          BINARY=$(find packages/opencode/dist -path '*altimate-code-linux-x64/bin/altimate' -type f | head -1)
+          if [ -z "$BINARY" ]; then
+            echo "::error::No linux-x64 binary found in artifacts — cannot verify release"
+            exit 1
+          else
+            chmod +x "$BINARY"
+            NODE_PATH="$(pwd)/packages/opencode/node_modules:$(pwd)/node_modules" "$BINARY" --version
+            echo "Pre-publish smoke test passed"
+          fi
+
       - name: Publish to npm
         run: bun run packages/opencode/script/publish.ts
         env:

.opencode/skills/dbt-analyze/SKILL.md

@@ -111,7 +111,7 @@ If no manifest is available:
 1. Run `lineage_check` on the changed SQL
 2. Show column-level data flow
 3. Note: downstream impact requires a manifest
-4. Suggest: `altimate-dbt build-project` to generate one
+4. Suggest: `altimate-dbt build` to generate one
 
 ## Common Mistakes
 

.opencode/skills/dbt-analyze/references/altimate-dbt-commands.md

@@ -20,10 +20,10 @@ altimate-dbt info                          # Project name, adapter, root
 ## Build & Run
 
 ```bash
-altimate-dbt build --model <name> [--downstream]   # compile + run + test
+altimate-dbt build                                  # full project build (compile + run + test)
+altimate-dbt build --model <name> [--downstream]   # build a single model
 altimate-dbt run --model <name> [--downstream]      # materialize only
 altimate-dbt test --model <name>                     # run tests only
-altimate-dbt build-project                           # full project build
 ```
 
 ## Compile

.opencode/skills/dbt-develop/references/altimate-dbt-commands.md

@@ -20,10 +20,10 @@ altimate-dbt info                          # Project name, adapter, root
 ## Build & Run
 
 ```bash
-altimate-dbt build --model <name> [--downstream]   # compile + run + test
+altimate-dbt build                                  # full project build (compile + run + test)
+altimate-dbt build --model <name> [--downstream]   # build a single model
 altimate-dbt run --model <name> [--downstream]      # materialize only
 altimate-dbt test --model <name>                     # run tests only
-altimate-dbt build-project                           # full project build
 ```
 
 ## Compile

.opencode/skills/dbt-docs/references/altimate-dbt-commands.md

@@ -20,10 +20,10 @@ altimate-dbt info                          # Project name, adapter, root
 ## Build & Run
 
 ```bash
-altimate-dbt build --model <name> [--downstream]   # compile + run + test
+altimate-dbt build                                  # full project build (compile + run + test)
+altimate-dbt build --model <name> [--downstream]   # build a single model
 altimate-dbt run --model <name> [--downstream]      # materialize only
 altimate-dbt test --model <name>                     # run tests only
-altimate-dbt build-project                           # full project build
 ```
 
 ## Compile

.opencode/skills/dbt-test/references/altimate-dbt-commands.md

@@ -20,10 +20,10 @@ altimate-dbt info                          # Project name, adapter, root
 ## Build & Run
 
 ```bash
-altimate-dbt build --model <name> [--downstream]   # compile + run + test
+altimate-dbt build                                  # full project build (compile + run + test)
+altimate-dbt build --model <name> [--downstream]   # build a single model
 altimate-dbt run --model <name> [--downstream]      # materialize only
 altimate-dbt test --model <name>                     # run tests only
-altimate-dbt build-project                           # full project build
 ```
 
 ## Compile

.opencode/skills/dbt-troubleshoot/references/altimate-dbt-commands.md

@@ -20,10 +20,10 @@ altimate-dbt info                          # Project name, adapter, root
 ## Build & Run
 
 ```bash
-altimate-dbt build --model <name> [--downstream]   # compile + run + test
+altimate-dbt build                                  # full project build (compile + run + test)
+altimate-dbt build --model <name> [--downstream]   # build a single model
 altimate-dbt run --model <name> [--downstream]      # materialize only
 altimate-dbt test --model <name>                     # run tests only
-altimate-dbt build-project                           # full project build
 ```
 
 ## Compile

CHANGELOG.md

@@ -5,6 +5,64 @@ 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.13] - 2026-03-26
+
+### Fixed
+
+- **Pin `@altimateai/altimate-core` to exact version** — prevents npm from resolving stale cached binaries during install (#475)
+- **Flaky `dbt Profiles Auto-Discovery` tests in CI** — stabilized tests that failed intermittently due to timing issues
+
+### Changed
+
+- **Bump `yaml` from 2.8.2 to 2.8.3** — dependency update in `packages/opencode` (#473)
+
+## [0.5.12] - 2026-03-25
+
+### Added
+
+- **`altimate-dbt` auto-discover config** — `altimate-dbt` commands now auto-detect `dbt_project.yml` and Python from the current directory without requiring `altimate-dbt init` first; supports Windows paths (`Scripts/`, `.exe`, `path.delimiter`) (#464)
+- **Local E2E sanity test harness** — Docker-based test suite (`test/sanity/`) for install verification, smoke tests, upgrade scenarios, and resilience checks; runnable via `bun run sanity` (#461)
+
+### Fixed
+
+- **`altimate-dbt` commands fail with hardcoded CI path** — published binary contained a baked-in `/home/runner/work/...` path for the Python bridge; `copy-python.ts` now patches `__dirname` to use `import.meta.dirname` at runtime (#467)
+
+### Testing
+
+- 42 adversarial tests for config auto-discovery and dbt resolution: `findProjectRoot` edge cases (deep nesting, symlinks, nonexistent dirs), `discoverPython` with broken symlinks and malicious env vars, `resolveDbt` with conflicting env vars and priority ordering, `validateDbt` timeout/garbage handling, Windows constant correctness, `path.delimiter` usage, `buildDbtEnv` mutation safety
+- 484-line adversarial test suite for the `__dirname` patch: regex edge cases, ReDoS protection, mutation testing, idempotency, CI smoke test parity, bundle runtime structure validation
+
+## [0.5.11] - 2026-03-25
+
+### Fixed
+
+- **README changelog gap** — updated README to reflect releases v0.5.1 through v0.5.11; previous README only listed up to v0.5.0
+- **npm publish transient 404s** — added retry logic (3 attempts with backoff) to `publish.ts` for concurrent scoped package publishes that hit npm registry race conditions
+
+## [0.5.10] - 2026-03-24
+
+### Added
+
+- **`altimate-code check` CLI command** — deterministic SQL checks (linting, formatting, style) that run without an LLM, suitable for CI pipelines and pre-commit hooks (#453)
+- **Data-viz skill improvements** — lazy initialization, data-code separation, color contrast rules, icon semantics, field validation, and pre-delivery checklist (#434)
+
+### Fixed
+
+- **Snowflake Cortex not visible before authentication** — provider now appears in the provider list even when not yet authenticated (#447)
+- **New user detection race condition** — first-run welcome flow and telemetry events could fire out of order or be skipped entirely (#445)
+- **52 CI test failures from `mock.module` leaking across files** — test isolation fix for the new `check` command e2e tests (#460)
+- **Missing `altimate_change` marker** — added required upstream marker on `isStatelessCommand` guard to pass Marker Guard CI (#457)
+
+### Changed
+
+- **Rename Recap back to Trace** — reverted the Recap branding to Trace across 29 files for better AI model comprehension of session recording concepts (#443)
+
+### Testing
+
+- Consolidated 12 hourly test PRs into single batch: slugify, hints sort, skill formatting, batch tools, filesystem utilities, wildcard matching — 1,680 new test lines (#439)
+- `altimate-code check` unit + e2e test suites (1,687 lines) (#453)
+- Snowflake Cortex provider visibility tests (#447)
+
 ## [0.5.9] - 2026-03-23
 
 ### Fixed