Decide what to do with the credo-ts-ext repo #2564

Regarding updating to latest:

I think considering different people using different extensions, if we decide to keep them together, it makes sense to update packages as per requirement (would be automatically implied in case we decide to separate them).

I saw some discussion over discord, with an intent to update the react-hooks extension. Here's the link to discussion: https://discord.com/channels/1022962884864643214/1179453305856991263/1447623209133543566 (this and subsequent messages)

I think we have it in our timeline to update credo-ts-ext to the latest version. However, there's no commitment as of now, as there are some other priorities in pipeline.

Also, would be a good idea to move packages closer to their dependent component. They seem to be a bit side lined here.

In 2025年12月18日 WG call we briefly discussed about this and the outcome from it is to probably archive credo-ts-ext repo and migrate the packages to different, more focused or related, repos:

• @amanji plans to add React Hooks to the work in progress in Bifold to upgrade to Credo 0.6.x and React Native 0.81
• Push Notifications can be moved to didcomm-mediator-credo. As of today, a Credo 0.6-compatible module has been published to npm under the name @credo-ts/didcomm-push-notifications. It supports all functionality of the previous module for FCM (APN support yet to be added, although it seems most of us are using FCM for simplicity)
• REST might be part of the main repo, as it is very good to showcase Credo features and certainly is a good starting point like it was for most of us with ACA-Py back in the day (well... it wasn't so long ago but I wanted to use that expression 😄 )
• Redux store could be deprecated unless someone is still using it
• Transport BLE we are not sure, as it is certainly related to mobile environments, so we could add it to Bifold, but it can be also at the same level of other DIDComm transport implementations. So maybe it could go to the main repo as well