Python bridge unavailable when altimate_engine not in active venv

[suryaiyer95]

Bug

When running /discover or sql_execute, the Python bridge fails silently because altimate_engine is not installed in the user's active virtual environment. The error message is generic and unhelpful:

The Python bridge that manages warehouse connections is currently unavailable. This is an infrastructure issue with the altimate engine runtime — not a problem with your credentials or Snowflake setup.

Steps to Reproduce

1. Have a project with a .venv that has dbt-snowflake and snowflake-connector-python installed but not altimate_engine
2. Run /discover or invoke sql_execute tool
3. Bridge fails — no actionable guidance for the user

Environment

$ which python3
/Users/surya/repos/dbt-projects/jaffle-shop/.venv/bin/python3

$ pip3 list | grep -i altimate
altimate-datapilot-cli     0.2.0    # <-- wrong package, altimate_engine is missing

Expected Behavior

• Detect that altimate_engine is missing from the active Python environment
• Provide a clear message: e.g., "altimate_engine is not installed in your active venv. Run pip install altimate-engine or let altimate-code manage its own Python environment."
• Ideally, fall back to altimate-code's managed Python environment (~/.local/share/altimate-code/engine/) instead of failing

Notes

altimate-code has its own engine installation at ~/.local/share/altimate-code/engine/ but the bridge appears to prefer the user's active venv (which python3), which may not have the engine installed.

[kulvirgit]

Fixed by PR #221 (commit 1b3a4ab) — the Python bridge was completely removed. All 73 methods are now native TypeScript, so this class of venv/path issues can no longer occur.