CLI presents extension-type integrations as unavailable even when a live IDE bridge serves them

[ralphstodomingo]

What's wrong

Three CLI surfaces treat extension-type integrations as categorically unusable, which is stale — they serve from the CLI whenever VS Code with the Altimate extension is open on the project:

1. datamate_manager list-integrations hides extension-type rows unconditionally and says they "require a live VS Code bridge and are not available from the CLI" — even when exactly such a bridge is live and the engine is serving their tools into the session.
2. The workspace attach announcement ("N of M declared integration tools available") counts only non-extension keys. Extension tools a connected bridge is actually serving appear in the tool list but are never counted or mentioned.
3. There is no signal anywhere in the CLI that dormant extension integrations come back by opening the IDE — the copy reads as a permanent capability gap.

Why it's wrong (verified end to end, 2026-09-03)

With VS Code + the Altimate extension open on a bound project, a headless run:

• discovered the extension's RPC sidecar and connected the workspace-pinned engine to it,
• registered the extension integration's 15 remote tools and passed them through the workspace allowlist into the session tool list,
• compile_model returned the compiled SQL and run_model materialized the model on the warehouse (dbt + snowflake adapter, SUCCESS 1),
• the workspace's server-side snowflake integration then read the created view back in the same session.

So "not available from the CLI" is false whenever a bridge is live, and misleading about how to get the capability when one is not.

What it should say

• With a live bridge for the project: list extension-type integrations, mark them as served via the connected VS Code window, and count them.
• Without one: keep them out of the table, but say they serve while VS Code with the Altimate extension is open on this project — a state, not an impossibility.
• The attach announcement should append the count of extension tools the bridge is actually serving; their absence stays unwarned (that is the normal no-IDE case, not "missing").