keks0r

The bundling is pretty interesting, does this also work on repo level? e.g. I have added some sales skills into our company brain, but for sessions that others would do, if they are not doing sales related tasks, they would not require any of it. But I still want to be able to directly invoke one of my sales related skills directly.

One of the things that was most challenging and still rough around the edges are backfills. Doing a BC breaking schema change in a chain of materialized view and repopulating can take a week or more for a big dataset. So having stable tooling to help guide that change was super helpful for some of our past migrations.

Does this mean, that the full node compatibility purely depends on oxc for transpiling? So oxc compatibility = nub compatibility?

How does this integrate with Git? is the CRDT stack mainly for syncronizing locally? and then "snapshotted" into git? Or how would the team collaboration part of this work?