chore: migrate non-core parts of `rig-core` to `rig`
So, now that we've acquired the rig crate name, it's now time to figure out what we actually need to add to the rig crate (and if we do actually want to migrate).
This issue is mostly left open for the sake of awareness as there is not a known issue scope yet.
rig core could be the provider integrations and rig adds Agents and all of our other abstractions. but it's an arbitrary line
rig core could be the provider integrations and rig adds Agents and all of our other abstractions. but it's an arbitrary line
I do think it might be worth adding a wholly separate crate just for providers (eg rig-providers) and then pulling both rig-core and rig-providers in for Rig given how many people are trying to make their own version of a model provider library at the moment.