[Feature]: Publish provider contracts and runtime packages #6666

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

apps/server

Problem or use case

T3 Code is doing an amazing job creating a unified API across fast-moving coding-agent harnesses. Projects that need the same session, turn, approval, and event normalization otherwise have to copy and maintain that integration work themselves.

Proposed solution

Would you consider publishing the existing provider contracts and runtime as experimental packages? They can version in lockstep with T3 Code and make breaking changes freely while this ecosystem is moving quickly.

Why this matters

This follows the UnJS philosophy: build a strong, product-independent primitive once and let the ecosystem compose it. Projects such as ViteHub could delete substantial duplicated integration code while provider compatibility work and fixes stay in one shared implementation.

Smallest useful scope

One installable package with the existing provider contracts, runtime, and a documented entry point. No new protocol, plugin system, UI package, or stability promise is needed.

Contribution

• I would be open to helping implement this.