The ribbon follows each command to its stage

A command run by a script, the control channel, MCP, the command search
or the browser left the ribbon on whatever tab it showed, so an agent's
session never showed the stage it was at. `catalogue::stage_tab` is the
rule, from the catalogue: a command's entry tab, none for the Tools tab
(files, history, the model summary). The app follows it after a command
that changed the model or the results display (queries leave the ribbon
alone); a script follows its last command with a stage. A ribbon click
runs a command of the tab shown, so it never moves the ribbon: a test
checks every entry and drop-down command against its tab.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01NmAttHhUZTokgPeEJia8sm

docs/control-protocol.md

@@ -30,7 +30,12 @@ checked and clamped (drag steps, wheel lines, window size); `ui.render` refuses
 
 Commands never open forms or file pickers when run this way. `fieldcraft-cli commands` prints the
 same registry. `file.sample {name}` opens a sample (`parts`, `cantilever`, `impact`) and
-`solve.run {}` solves every step; the Results workspace comes up when a result appears.
+`solve.run {}` solves every step; the Results workspace comes up when a result appears. The
+ribbon follows the commands run here, as it does for scripts, MCP, the command search and the
+browser: a command that changes the model or the results display brings the tab where its
+toolbar entry lives (Mesh for `mesh.*`, Properties, Steps, Loads & BCs… for `model.*`, Solve,
+Results), as a click there would. Queries (`model.check`, `mesh.quality`…) and the Tools tab's
+commands (files, undo, `model.info`) leave the ribbon where it is.
 
 ## UI