Feature Request: Bring back the latest pull / push time stamps in the view and maybe improve upon with activity logs?

### What

Hi there,

I switched to the new beta of Studio and one item that is kind of bugging me is the removal of the time stamps at the pull / push buttons.
Before when you hovered either of the buttons it would show you the last moment you performed that action.

Now I had to ask the AI, but preferably this would just be returned.

### Why

Because when working on a project, the next day / week I always check like; what was my last action. So I know if I still need to pull/push something and what my next steps should be.

### How

The simplest form is to just add these numbers back as they used to be.

However, it would be amazing if there is some kind of activity log like in Jetpack / WordPress.com ( https://wordpress.com/activity-log/ )
Where in the simplest version it would just be an activity log that shows your latest pulls and pushed (preferably with some type of comments)

But, I feel we can push this past simple push/pulls logs. It would be more amazing if you could also see some of the server push-pull history.
As in, in some workflows you pull from Production, you make some changes in Studio, you push it to staging where it gets tested by internal team-members/ clients. And from staging you push it to production (on WordPress.com directly)

And to really improve this setup, an additional GIT integration from respository itself where it can show commits made to the code in between the push-pull en server data would be the cherry on top of the cake.

But, it has to be filter able with some simple check marks.

Below I provided a quick sketch on how it could look:

I am genuinely curious what you think about this idea, in addition some kind of Jetpack Activity log connection (with all the information it already collects on the server) would be a nice to have, where you can switch within Studio from local history, staging history and production history in one tab.

No files, tests, or entry points are named. Start by locating the pull and push controls and any existing timestamp state, then determine whether the smallest deliverable is restoring hover timestamps or designing the broader activity log. Done should be defined before implementation because the request spans local, staging, production, and Git history with filtering.

Written by the indexing model from the issue text.