[orm #1] Decision: brand-consolidation with the Vike team (gate for #64)

[suleimansh]

Part of #64. Blocks every other child.

The data-layer graduation is not a code move, it is a brand decision. There are three agnostic-ish scopes in play (@gemstack, @universal-orm, @vike-data), and @universal-orm is a deliberate, co-developed npm scope. So the call is decide-with-the-Vike-team (Rom), not unilateral, gated on brand traction.

Pick one:

1. Consolidate — fold @universal-orm/* + @vike-data/universal-schema into @gemstack/orm* + @gemstack/schema. One umbrella for all agnostic engines (the Architecture.md thesis).
2. Parallel brands — keep @universal-orm as its own brand beside @gemstack; document them as siblings.
3. Defer — hold until brand traction is higher (gemstack.land cutover Attach gemstack.land custom domain to the docs site #63 is the signal building).

Evidence for the conversation: the Phase 0 spike #65 (154 tests green, zero framework coupling, JS-src-direct model preserved).

Acceptance: a decision recorded here; if (1), unblock the children below; if (2)/(3), close the rest accordingly.

[suleimansh]

Resolved (pending one final scope sync): the Vike-team naming call is to NOT bring the universal data-layer engines under the GemStack umbrella. GemStack stays the user-facing brand (AI SDK, MCP). The universal ORM/schema engines are infrastructure that sits under adapters and are not user-facing, so they keep the @universal-orm parallel brand. Consequence: no @gemstack/orm + @gemstack/schema rename.

One point to confirm before closing: whether this covers the whole engine set (orm + schema + both adapters) or only the adapter packages. Will close once that is confirmed.

[suleimansh]

Decided: keep the WHOLE universal data-layer set under @universal-orm, outside the GemStack umbrella. Synced with the Vike team and confirmed scope = the entire engine set (@universal-orm/core + the schema package + both adapters orm-memory / orm-drizzle), not just the adapter packages.

Rationale: these engines are infrastructure under the framework binding, not user-facing. GemStack stays the user-facing brand (AI SDK, MCP). No @gemstack/orm + @gemstack/schema rename.

Knock-on (tracked on #64): #67 / #68 re-scope from 'rename to @gemstack' to 'publish under @universal-orm'; PR #65's private copies on gemstack main stay dormant / unpublished; docs (#72 / PR #73) drop the data layer from the GemStack family. The vike-data single-source-of-truth rule is unaffected (no rename = no fork).