docs: "no proprietary runtime", not "no MetaObjects dependency"

AGENTS.md, spec/README.md and the shipped codegen skill said generated code runs without any
MetaObjects dependency at runtime. It does not, in any port: generated REST tiers import the
route helpers (runtime-ts/drizzle-fastify, MetaObjects.Codegen.Runtime,
generator.spring.runtime, metaobjects.codegen.runtime), and prompt tiers import render and
extract. Checked against the adopter estate's generated trees in all five ports. What holds
is the July oversell review's row 3 ruling: entity and model code imports nothing from
MetaObjects at runtime, and the other tiers import ordinary Apache-2.0 packages. That review
fixed the README and llms mirrors; these three sites were missed.

The skill ships into every adopter stack, so the agent-context conformance goldens are
regenerated in this commit.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M1mRRB1K2WdYy82kntMQdx

Author: dmealing

AGENTS.md

@@ -4,7 +4,7 @@
 
 MetaObjects is a **cross-language metadata standard** for declaring typed entity models that drive code generation, runtime metadata access, and drift detection — across TypeScript, C#, Java, Python, and Kotlin (Kotlin runs on the JVM via `metadata-ktx` + `codegen-kotlin`).
 
-The metamodel is the **durable spine**; generated code is the **disposable artifact**. Substrate is local-first: typed metadata lives in your repo, generated code is idiomatic per-language output that runs without any MetaObjects dependency at runtime. If `@metaobjectsdev/*` disappears tomorrow, you keep working code.
+The metamodel is the **durable spine**; generated code is the **disposable artifact**. Substrate is local-first: typed metadata lives in your repo, generated code is idiomatic per-language output with **no proprietary runtime**: the generated entity and model code imports nothing from MetaObjects at runtime, and the REST, prompt, client and runtime tiers import ordinary Apache-2.0 packages you can vendor, fork or replace. If `@metaobjectsdev/*` disappears tomorrow, you keep working code.
 
 **Core vs helpers (ADR-0034 Amendment 3, 2026-09-22).** Only the core is a product promise: the metamodel, loader, canonical format and registry; runtime metadata access (the `ObjectManager` and its drivers; the HTTP adapters that mount it on a web framework are helpers, 2026-09-24 ruling); schema migrations (`meta migrate`); the drift gates (`meta verify`); prompt render and the reply parser. Every generator that writes application code into an adopter's repo — routes, controllers, ORM wiring, DTOs, forms, grids, hooks, filter allowlists — is a **reference helper**: it must compile and pass its reference fixtures, and the adopter copies it with `meta eject` and owns the copy. Mechanical test: what the tool guarantees is core; what it writes into your repo is a helper. Every port can eject: `meta eject` (TypeScript), `metaobjects eject` (Python), `mvn metaobjects:eject` (Java/Kotlin), `dotnet meta eject` (C#). When you find a generator defect, fix the reference; do not describe it as a broken core guarantee.
 
@@ -270,7 +270,7 @@ import { EntityFetcherProvider, EntityGrid } from "@metaobjectsdev/tanstack";
 
 - A custom DSL. Plain typed metadata only — Wasp's seven-year DSL-tax is the cautionary tale.
 - A spec-driven workflow like Kiro / Spec Kit. Humans don't author rich specs; Claude proposes metadata, humans review.
-- A proprietary runtime. All generated code runs without MetaObjects installed; runtime libraries are normal language-native packages.
+- A proprietary runtime. Generated entity and model code runs without MetaObjects installed; the tiers that do import a MetaObjects package (REST helpers, prompt render and extract, the web client, the runtime pillar) import normal Apache-2.0, language-native packages.
 - A prompt-to-app builder (not Lovable, Bolt, or v0). MetaObjects generates entity-shaped boilerplate; users hand-write the interesting business logic.
 - Replacing CLAUDE.md, cursor rules, or other prompt-engineering surfaces — MetaObjects complements them.
 - An LLM provider. The MCP integration is model-agnostic.

agent-context/skills/metaobjects-codegen/SKILL.md

@@ -8,9 +8,10 @@ description: Use when configuring or running MetaObjects code generation — gen
 Codegen is the first pillar: MetaObjects reads your typed metadata and emits
 **idiomatic per-language code** — entity types, DB tables/schemas, query helpers,
 REST routes, validators, payload value-objects, output parsers. The metadata is the
-durable spine; the generated code is a disposable artifact. It runs at runtime
-**without any MetaObjects dependency** — if the libraries disappeared tomorrow, you
-keep working code.
+durable spine; the generated code is a disposable artifact. It has **no
+proprietary runtime**: entity and model code imports nothing from MetaObjects, and the
+REST, prompt and client tiers import ordinary Apache-2.0 packages you can vendor or
+replace — if the libraries disappeared tomorrow, you keep working code.
 
 **Generators are reference helpers, not guarantees** (ADR-0034 Amendment 3). The core —
 metamodel, loader, `migrate`, `verify`, prompt render — is what MetaObjects guarantees.

fixtures/agent-context-conformance/java-kotlin-react-tanstack/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -8,9 +8,10 @@ description: Use when configuring or running MetaObjects code generation — gen
 Codegen is the first pillar: MetaObjects reads your typed metadata and emits
 **idiomatic per-language code** — entity types, DB tables/schemas, query helpers,
 REST routes, validators, payload value-objects, output parsers. The metadata is the
-durable spine; the generated code is a disposable artifact. It runs at runtime
-**without any MetaObjects dependency** — if the libraries disappeared tomorrow, you
-keep working code.
+durable spine; the generated code is a disposable artifact. It has **no
+proprietary runtime**: entity and model code imports nothing from MetaObjects, and the
+REST, prompt and client tiers import ordinary Apache-2.0 packages you can vendor or
+replace — if the libraries disappeared tomorrow, you keep working code.
 
 **Generators are reference helpers, not guarantees** (ADR-0034 Amendment 3). The core —
 metamodel, loader, `migrate`, `verify`, prompt render — is what MetaObjects guarantees.

fixtures/agent-context-conformance/java-react/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -8,9 +8,10 @@ description: Use when configuring or running MetaObjects code generation — gen
 Codegen is the first pillar: MetaObjects reads your typed metadata and emits
 **idiomatic per-language code** — entity types, DB tables/schemas, query helpers,
 REST routes, validators, payload value-objects, output parsers. The metadata is the
-durable spine; the generated code is a disposable artifact. It runs at runtime
-**without any MetaObjects dependency** — if the libraries disappeared tomorrow, you
-keep working code.
+durable spine; the generated code is a disposable artifact. It has **no
+proprietary runtime**: entity and model code imports nothing from MetaObjects, and the
+REST, prompt and client tiers import ordinary Apache-2.0 packages you can vendor or
+replace — if the libraries disappeared tomorrow, you keep working code.
 
 **Generators are reference helpers, not guarantees** (ADR-0034 Amendment 3). The core —
 metamodel, loader, `migrate`, `verify`, prompt render — is what MetaObjects guarantees.

fixtures/agent-context-conformance/python/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -8,9 +8,10 @@ description: Use when configuring or running MetaObjects code generation — gen
 Codegen is the first pillar: MetaObjects reads your typed metadata and emits
 **idiomatic per-language code** — entity types, DB tables/schemas, query helpers,
 REST routes, validators, payload value-objects, output parsers. The metadata is the
-durable spine; the generated code is a disposable artifact. It runs at runtime
-**without any MetaObjects dependency** — if the libraries disappeared tomorrow, you
-keep working code.
+durable spine; the generated code is a disposable artifact. It has **no
+proprietary runtime**: entity and model code imports nothing from MetaObjects, and the
+REST, prompt and client tiers import ordinary Apache-2.0 packages you can vendor or
+replace — if the libraries disappeared tomorrow, you keep working code.
 
 **Generators are reference helpers, not guarantees** (ADR-0034 Amendment 3). The core —
 metamodel, loader, `migrate`, `verify`, prompt render — is what MetaObjects guarantees.

fixtures/agent-context-conformance/ts-react-tanstack/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -8,9 +8,10 @@ description: Use when configuring or running MetaObjects code generation — gen
 Codegen is the first pillar: MetaObjects reads your typed metadata and emits
 **idiomatic per-language code** — entity types, DB tables/schemas, query helpers,
 REST routes, validators, payload value-objects, output parsers. The metadata is the
-durable spine; the generated code is a disposable artifact. It runs at runtime
-**without any MetaObjects dependency** — if the libraries disappeared tomorrow, you
-keep working code.
+durable spine; the generated code is a disposable artifact. It has **no
+proprietary runtime**: entity and model code imports nothing from MetaObjects, and the
+REST, prompt and client tiers import ordinary Apache-2.0 packages you can vendor or
+replace — if the libraries disappeared tomorrow, you keep working code.
 
 **Generators are reference helpers, not guarantees** (ADR-0034 Amendment 3). The core —
 metamodel, loader, `migrate`, `verify`, prompt render — is what MetaObjects guarantees.

fixtures/agent-context-conformance/ts-requirements/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -8,9 +8,10 @@ description: Use when configuring or running MetaObjects code generation — gen
 Codegen is the first pillar: MetaObjects reads your typed metadata and emits
 **idiomatic per-language code** — entity types, DB tables/schemas, query helpers,
 REST routes, validators, payload value-objects, output parsers. The metadata is the
-durable spine; the generated code is a disposable artifact. It runs at runtime
-**without any MetaObjects dependency** — if the libraries disappeared tomorrow, you
-keep working code.
+durable spine; the generated code is a disposable artifact. It has **no
+proprietary runtime**: entity and model code imports nothing from MetaObjects, and the
+REST, prompt and client tiers import ordinary Apache-2.0 packages you can vendor or
+replace — if the libraries disappeared tomorrow, you keep working code.
 
 **Generators are reference helpers, not guarantees** (ADR-0034 Amendment 3). The core —
 metamodel, loader, `migrate`, `verify`, prompt render — is what MetaObjects guarantees.

spec/README.md

@@ -11,7 +11,7 @@ A typed metadata standard for declaring entity models, identities, relationships
 - **Drift checks** (`meta verify`) that flag divergence between code and metadata across entity codegen, prompt templates, output parsers and live database schema — plus the compile-time breakage the generated types cause on their own.
 - **Prompt construction** *(the fourth pillar)* that makes an LLM prompt a declared, deterministic, testable artifact instead of a scattered string: a typed payload declared as a projection (so payload bloat is visible), external provider-resolved prompt text, a deterministic render that is snapshot-testable and cache-stable, and build-time prompt↔payload drift detection — conformance-gated so the guarantee holds in every language port. Render, payload value-object codegen, `verify`, parser-on-receipt and the tolerant `extract` parser ship in all five ports today; MCP exposure of declared prompts and tools is the remaining library-side piece (see [`roadmap.md`](roadmap.md)). See the FR-004 design doc under [`../docs/superpowers/specs/`](../docs/superpowers/specs/).
 
-The substrate is local-first: typed metadata lives in your repo at `metaobjects/`, generated code is idiomatic per-language output that runs **without any MetaObjects dependency at runtime**. If `@metaobjectsdev/*` packages disappeared tomorrow, your generated code keeps working.
+The substrate is local-first: typed metadata lives in your repo at `metaobjects/`, generated code is idiomatic per-language output with **no proprietary runtime**: entity and model code imports nothing from MetaObjects, and the REST, prompt, client and runtime tiers import ordinary Apache-2.0 packages. If `@metaobjectsdev/*` packages disappeared tomorrow, your generated code keeps working.
 
 ## The metamodel in one paragraph