docs(agent-context): point TS skills at meta docs template pages

The metaobjects-prompts TS reference now tells adopter agents to run `meta docs` and read the per-template `## Template source` linked-variable section; the metaobjects-codegen TS reference clarifies meta docs (neutral, the single door) vs apiDocsFile() (SDK reference generator). TS-stack agent-context goldens regenerated; non-TS stacks unchanged.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: dmealing

agent-context/skills/metaobjects-codegen/references/typescript.md

@@ -62,6 +62,11 @@ When `apiDocsFile()` is enabled (it is in the default scaffold), **read
 imports, function signatures, payload field shapes, and runnable examples for this
 project's generated API, so you don't have to guess them.
 
+`apiDocsFile()` (a generator → `docs/api/`) is the SDK/API reference. The neutral
+model docs (one page per entity and per template, including the linked template
+source) are different: they come from the separate `meta docs` command (→ `docs/`),
+which is the single door for neutral docs — not a `meta gen` generator.
+
 From `@metaobjectsdev/codegen-ts-react`: `formFile()` → `<Entity>.form.tsx`.
 From `@metaobjectsdev/codegen-ts-tanstack`: `tanstackQuery()` → `<Entity>.hooks.ts`
 (5 React Query hooks), `tanstackGrid()` → `<Entity>.columns.tsx`,

agent-context/skills/metaobjects-prompts/references/typescript.md

@@ -95,3 +95,14 @@ build (exit 1, `(output)`-prefixed diagnostic) if a reference can't be resolved
 catching payload-VO ↔ parser drift at build time. The emitted parser imports `zod`;
 it's usually already a dependency (Drizzle / `runtime-ts` lean on it), else
 `npm i zod`.
+
+## See which fields a template consumes
+
+Run `meta docs` to emit neutral model docs to `./docs` — one page per
+`template.output` at `docs/<Template>.md`. Each template page has a
+`## Template source` section that shows the Mustache source with every `{{var}}`
+linked to that field's doc page (`docs/<Owner>.md#field-<name>`), plus a variables
+table — so you can see exactly which payload fields a template reads. Those links are
+build-time drift-gated against the render `verify()` engine, so a link can't claim a
+field that `verify()` would reject. (`meta docs` is the single door for these neutral
+docs — it's a command, not a `meta gen` generator.)

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

@@ -62,6 +62,11 @@ When `apiDocsFile()` is enabled (it is in the default scaffold), **read
 imports, function signatures, payload field shapes, and runnable examples for this
 project's generated API, so you don't have to guess them.
 
+`apiDocsFile()` (a generator → `docs/api/`) is the SDK/API reference. The neutral
+model docs (one page per entity and per template, including the linked template
+source) are different: they come from the separate `meta docs` command (→ `docs/`),
+which is the single door for neutral docs — not a `meta gen` generator.
+
 From `@metaobjectsdev/codegen-ts-react`: `formFile()` → `<Entity>.form.tsx`.
 From `@metaobjectsdev/codegen-ts-tanstack`: `tanstackQuery()` → `<Entity>.hooks.ts`
 (5 React Query hooks), `tanstackGrid()` → `<Entity>.columns.tsx`,

fixtures/agent-context-conformance/ts-react-tanstack/expected/.claude/skills/metaobjects-prompts/references/typescript.md

@@ -95,3 +95,14 @@ build (exit 1, `(output)`-prefixed diagnostic) if a reference can't be resolved
 catching payload-VO ↔ parser drift at build time. The emitted parser imports `zod`;
 it's usually already a dependency (Drizzle / `runtime-ts` lean on it), else
 `npm i zod`.
+
+## See which fields a template consumes
+
+Run `meta docs` to emit neutral model docs to `./docs` — one page per
+`template.output` at `docs/<Template>.md`. Each template page has a
+`## Template source` section that shows the Mustache source with every `{{var}}`
+linked to that field's doc page (`docs/<Owner>.md#field-<name>`), plus a variables
+table — so you can see exactly which payload fields a template reads. Those links are
+build-time drift-gated against the render `verify()` engine, so a link can't claim a
+field that `verify()` would reject. (`meta docs` is the single door for these neutral
+docs — it's a command, not a `meta gen` generator.)