Using the v2 engine (packages/v2) as an embedded library — roadmap & official stance?

[Byte-n]

Hi Teable team! 👋

We're building a documentation platform and would love to embed Teable's
bitable capabilities (grid, views, formula, realtime collaboration) into our
product, using the MIT-licensed parts of the repo.

While exploring the codebase we noticed packages/v2 — a hexagonal-architecture
engine with pluggable adapters (Postgres / ShareDB / HTTP frameworks), plus
production wiring in nestjs-backend (16 @teable/v2-* workspace deps) and
the FORCE_V2_ALL rollout flag. It looks like a silent in-production migration
— very impressive work.

Since all v2 packages are currently private: true at 0.0.0 (not on npm,
no changelog), we'd like to ask before building on it:

1. Positioning — Is packages/v2 intended to become an officially supported
   embeddable engine for external products? Any plans for npm publishing,
   semantic versioning, or a GA announcement?

2. External adoption — How do you feel about third parties vendoring the
   MIT-licensed v2 packages into their own hosted products today? If we hit
   bugs or gaps along the way, are issues/PRs for this use case welcome?

3. Timeline — Roughly where does the FORCE_V2_ALL rollout stand, and when
   do you expect v2 to become the default/stable path?

For context: we'd pair the engine with @teable/sdk on the frontend and
implement the remaining OpenAPI surface (auth, permissions, attachments,
automation) on our own backend. Happy to share our integration findings and
contribute fixes upstream as we go.

Thanks for open-sourcing so much of the hard stuff — the engine + SDK split
under MIT is exactly what this ecosystem has been missing. 🙏