[FEATURE] Mobile app has no way to browse Routines — completed sessions become unreachable once notification is dismissed

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

On mobile, tapping a Routine's completion push notification correctly opens the spawned session. However, there appears to be no entry point in the mobile app to browse Routines at all (no "Routines" list/tab/settings screen). This means:

• The push notification li、nk is a one-time path to that session.
• Once you navigate away (or if you missed/dismissed the notification), there is no way to get back to that session, or to see the list of a Routine's past firings/sessions, from mobile.
• On desktop/web this may be easier via a Routines management page, but the same isn't available on mobile.

Use case: I run an automated multi-agent dispatch system that fires Routines several times a day against GitHub issues. I rely on being able to go back and check/reference a completed Routine session later (e.g., to verify what an agent did). Right now, my only realistic way to do this is to stay on desktop and browse via list_triggers/the web UI — mobile is a dead end after the first notification tap.
Requested improvement: Add a "Routines" view to the mobile app (list of configured Routines → their fire history → the sessions they spawned), so a session can be found again after the initial notification, not just tapped once and lost.

Proposed Solution

Add a "Routines" entry point in the mobile app (e.g., a tab or menu item) that lists configured Routines and, for each one, shows its fire history with links to the sessions it spawned. This way a routine-spawned session can be found again after the initial push notification is dismissed or missed, instead of that notification being the only path to it.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

_No response_

Additional Context

_No response_