Problem
When a session attaches to a workspace, the toast tries to carry the whole report: which declared tools the engine could not serve, grouped by reason, with the engine's detail. On a workspace with a few gaps it reads as noise, and there is nowhere else in the TUI to see the same information afterwards.
Proposal
- The attach toast carries numbers only —
2 of 9 integration tools available · 7 need attention. Details: /workspace — and points at the menu.
/workspace gains a Status row: one line per integration the workspace declares, with what this session got from it and why not (no usable connection, server failed to start, not offered, no longer in the catalog, needs a VS Code window), the served keys, and "Open on the web" for the fix. Rows needing attention first.- The sidebar's Workspace tile shows the same counts under the workspace name once a session has attached.
Builds on the /workspace menu from #1278 and the engine's unfulfilled report from #1307.
Problem
When a session attaches to a workspace, the toast tries to carry the whole report: which declared tools the engine could not serve, grouped by reason, with the engine's detail. On a workspace with a few gaps it reads as noise, and there is nowhere else in the TUI to see the same information afterwards.
Proposal
2 of 9 integration tools available · 7 need attention. Details: /workspace— and points at the menu./workspacegains a Status row: one line per integration the workspace declares, with what this session got from it and why not (no usable connection, server failed to start, not offered, no longer in the catalog, needs a VS Code window), the served keys, and "Open on the web" for the fix. Rows needing attention first.Builds on the
/workspacemenu from #1278 and the engine's unfulfilled report from #1307.