Problem
Modeler API derives the "Orchestra" administration menu item from the model owner plugin and points it at entity.orchestra_workflow.collection, which is the workflow list itself. Seven links sit under that item (Import, Tenants, Statuses, Views, Settings, Audit trail, Interaction), so in the administration menu it reads as a section heading, and the only way into the list is to click that heading.
Nothing in the menu is called "Workflows". Import is one of the children, so the importer is offered while the collection it imports into is not, which is where somebody looking for the list tends to end up.
Proposed resolution
Declare a Workflows link in orchestra.links.menu.yml, under the same parent the sibling Orchestra links already use, pointing at the collection route and weighted above the Import and Settings children that Modeler API derives without a weight.
The cost is one link that repeats its parent route, and on the collection page both the parent and the child are then in the active trail. That is the trade for naming the destination in the menu instead of leaving it reachable only by clicking a section heading.
Out of scope
The local task tab on these pages reads "Models". That string is hardcoded in Modeler API's local task deriver rather than taken from the model owner, so it is not this project's to change. It would need an issue against Modeler API if that tab should follow the owner's vocabulary.
AI-Generated: Yes (Claude Code was used to help draft this issue summary and to write the fix. I reviewed both.)
Issue fork orchestra-3624847
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #3
mably commentedComment #5
mably commented