Psuedo-buckets/clients for data that is managed by something other than activity watch

[skewballfox]

Something that would be beneficial for integrating data with third party tools such as Atuin, or one of the self-hosted wakatime clones such as wakapi, would be a way to interact with the data as if it was a bucket. These would essentiantially be scripts that responds to queries to the server and transforms the data from the third party (to activity watch events) as requested.

This data doesn't need to be stored (locally), though it can be, as that seems an unnecessary duplication. As long as the user can operate on the data as if it was part of the data tracked by activity watch, it doesn't matter where it's originating.

A situation where it might be useful to store it permanently is when handling synchronization. The data can exist in its original form locally, and be stored as activity watch event data on the remote system integrating multiple sources. It should be the same process as transforming in response to user queries, but being sent to the remote system in the same fashion as data originating from activitywatch