User-view problem list
A user browsing Workflow Library can inspect a workflow and click Run, but the handoff into Run Console does not preserve a clear return path to the workflow they came from.
Observed product/UI gaps:
- The catalog row Run action only sends
route=workflow, so Run Console knows what to run but not where the user came from.
- The inspector Run workflow action has the same issue: it leaves the user in Run Console without a workflow-specific return affordance.
- Run Console already accepts a safe
returnTo query parameter, but its primary return button is labelled as a team/studio return even when the origin is Workflow Library.
- A user running a catalog workflow should be able to return to that exact workflow inspector, not just the generic catalog list.
Consensus framing
This is a frontend product/UI handoff issue. It should reuse existing runtime route builders and the existing returnTo sanitizer. It should not introduce backend/API/proto/runtime behavior, and it should not address localization consistency as a goal.
Acceptance sketch
- Workflow Library Run actions should include
returnTo=/runtime/workflows?workflow=<selected>.
- Run Console should show a source-appropriate return label when
returnTo points at Workflow Library.
- Existing team/studio return behavior should continue to work.
- Tests should cover the route builder/handoff and Runs label behavior.
No auto-merge. Target PR base must be feat/2026-05-29_ai-automation-pipeline.
User-view problem list
A user browsing Workflow Library can inspect a workflow and click Run, but the handoff into Run Console does not preserve a clear return path to the workflow they came from.
Observed product/UI gaps:
route=workflow, so Run Console knows what to run but not where the user came from.returnToquery parameter, but its primary return button is labelled as a team/studio return even when the origin is Workflow Library.Consensus framing
This is a frontend product/UI handoff issue. It should reuse existing runtime route builders and the existing
returnTosanitizer. It should not introduce backend/API/proto/runtime behavior, and it should not address localization consistency as a goal.Acceptance sketch
returnTo=/runtime/workflows?workflow=<selected>.returnTopoints at Workflow Library.No auto-merge. Target PR base must be
feat/2026-05-29_ai-automation-pipeline.