docs(skills): meta docs has three surfaces, and the codegen reference listed two

0.24.0 turned the requirement ledger into a documentation surface and put it in the
DEFAULT set — `surfaces: ["model", "api", "requirements"]` — but the TypeScript codegen
reference still opened "one door, two surfaces" and its command block still said "both
surfaces". An agent working from it would not know `./docs/requirements.md` and
`./docs/requirements.toon` were being written on every plain `meta docs` run, nor that
`--requirements` exists to ask for them alone.

That matters more than a missing flag usually would, because the ledger is the one
surface whose whole value is that somebody READS it. A capability declared, gated by
`verify`, and rendered into a page nobody was told about is a ledger maintained for a
reader who never arrives.

The entry also records what an empty ledger does, since the obvious guess is wrong: a
project with no requirement.* nodes writes no file AND the run says nothing about the
surface, deliberately — reporting "0 requirement pages" would advertise a surface that
never ran, which is the same mistake as the reference itself was making in the other
direction.

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

Author: dmealing

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

@@ -133,10 +133,10 @@ cross-subtype 404. Conformance-gated by `fixtures/api-contract-conformance/tph`
 (HTTP wire shape) and `fixtures/persistence-conformance/tph-*` (single-table
 runtime semantics).
 
-## Docs — `meta docs` (one door, two surfaces)
+## Docs — `meta docs` (one door, three surfaces)
 
 Documentation is NOT a `meta gen` generator. The single door is the `meta docs`
-command, which emits two cross-linked **surfaces** under one output dir (default
+command, which emits three cross-linked **surfaces** under one output dir (default
 `./docs`):
 
 - **model surface** (`./docs/<Entity>.md`, `./docs/<Template>.md`) — the neutral
@@ -146,11 +146,19 @@ command, which emits two cross-linked **surfaces** under one output dir (default
   `./docs/api/AGENT-API.md`) — the SDK/API reference: the concrete imports,
   function signatures, payload field shapes, and runnable examples for *this*
   project's generated code.
+- **requirements surface** (`./docs/requirements.md`, `./docs/requirements.toon`) —
+  the declared `requirement.*` ledger as documentation, with each entry headed by its
+  dotted path and its `title` where it has one, and each entity page naming the
+  requirements that claim it. Metadata-alone like the model surface, so it needs no
+  gen config. **On by default since 0.24.0** — a project declaring no `requirement.*`
+  nodes writes no requirements file and the run says nothing about the surface at all,
+  deliberately: reporting "0 requirement pages" would advertise a surface that never ran.
 
 ```bash
-npx meta docs                     # both surfaces → ./docs (model) + ./docs/api (api)
+npx meta docs                     # all three → ./docs (model) + ./docs/api + ./docs/requirements.*
 npx meta docs --model             # model surface only
 npx meta docs --api               # api surface only
+npx meta docs --requirements      # requirement ledger only
 npx meta docs --out ./site-docs   # write under a different root
 ```
 

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

@@ -133,10 +133,10 @@ cross-subtype 404. Conformance-gated by `fixtures/api-contract-conformance/tph`
 (HTTP wire shape) and `fixtures/persistence-conformance/tph-*` (single-table
 runtime semantics).
 
-## Docs — `meta docs` (one door, two surfaces)
+## Docs — `meta docs` (one door, three surfaces)
 
 Documentation is NOT a `meta gen` generator. The single door is the `meta docs`
-command, which emits two cross-linked **surfaces** under one output dir (default
+command, which emits three cross-linked **surfaces** under one output dir (default
 `./docs`):
 
 - **model surface** (`./docs/<Entity>.md`, `./docs/<Template>.md`) — the neutral
@@ -146,11 +146,19 @@ command, which emits two cross-linked **surfaces** under one output dir (default
   `./docs/api/AGENT-API.md`) — the SDK/API reference: the concrete imports,
   function signatures, payload field shapes, and runnable examples for *this*
   project's generated code.
+- **requirements surface** (`./docs/requirements.md`, `./docs/requirements.toon`) —
+  the declared `requirement.*` ledger as documentation, with each entry headed by its
+  dotted path and its `title` where it has one, and each entity page naming the
+  requirements that claim it. Metadata-alone like the model surface, so it needs no
+  gen config. **On by default since 0.24.0** — a project declaring no `requirement.*`
+  nodes writes no requirements file and the run says nothing about the surface at all,
+  deliberately: reporting "0 requirement pages" would advertise a surface that never ran.
 
 ```bash
-npx meta docs                     # both surfaces → ./docs (model) + ./docs/api (api)
+npx meta docs                     # all three → ./docs (model) + ./docs/api + ./docs/requirements.*
 npx meta docs --model             # model surface only
 npx meta docs --api               # api surface only
+npx meta docs --requirements      # requirement ledger only
 npx meta docs --out ./site-docs   # write under a different root
 ```
 

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

@@ -133,10 +133,10 @@ cross-subtype 404. Conformance-gated by `fixtures/api-contract-conformance/tph`
 (HTTP wire shape) and `fixtures/persistence-conformance/tph-*` (single-table
 runtime semantics).
 
-## Docs — `meta docs` (one door, two surfaces)
+## Docs — `meta docs` (one door, three surfaces)
 
 Documentation is NOT a `meta gen` generator. The single door is the `meta docs`
-command, which emits two cross-linked **surfaces** under one output dir (default
+command, which emits three cross-linked **surfaces** under one output dir (default
 `./docs`):
 
 - **model surface** (`./docs/<Entity>.md`, `./docs/<Template>.md`) — the neutral
@@ -146,11 +146,19 @@ command, which emits two cross-linked **surfaces** under one output dir (default
   `./docs/api/AGENT-API.md`) — the SDK/API reference: the concrete imports,
   function signatures, payload field shapes, and runnable examples for *this*
   project's generated code.
+- **requirements surface** (`./docs/requirements.md`, `./docs/requirements.toon`) —
+  the declared `requirement.*` ledger as documentation, with each entry headed by its
+  dotted path and its `title` where it has one, and each entity page naming the
+  requirements that claim it. Metadata-alone like the model surface, so it needs no
+  gen config. **On by default since 0.24.0** — a project declaring no `requirement.*`
+  nodes writes no requirements file and the run says nothing about the surface at all,
+  deliberately: reporting "0 requirement pages" would advertise a surface that never ran.
 
 ```bash
-npx meta docs                     # both surfaces → ./docs (model) + ./docs/api (api)
+npx meta docs                     # all three → ./docs (model) + ./docs/api + ./docs/requirements.*
 npx meta docs --model             # model surface only
 npx meta docs --api               # api surface only
+npx meta docs --requirements      # requirement ledger only
 npx meta docs --out ./site-docs   # write under a different root
 ```