fix(cli): meta init switched off two docs surfaces for every scaffolded project

`resolveDocsConfig` defaults `surfaces` to all four — model, api, requirements,
agent — and its comment states the reason for the last one: "Turning it on by default
is what makes the always-on agent-context pointer able to name the files: a pointer
to a page an adopter has to opt into is a pointer at nothing."

`meta init` then scaffolded `surfaces: ["model", "api"]`, switching `requirements`
and `agent` OFF for every project it creates — defeating precisely that, on the exact
projects the pointer is scaffolded into.

The scaffold now says nothing about `surfaces` and takes the default, which is also
what lets a project pick up a new surface without editing config. Safe for the same
reason the default is: both surfaces emit ZERO files for a project with nothing for
them to describe, so a scaffolded project sees no new output until it has something
to document.

The comment left in its place also names the distinction the estate loop found people
reaching for `surfaces` to express: it says what your docs ARE, not which of them you
COMMIT — a page you do not commit is exempt from `verify --docs` once it is
git-ignored.

The existing test asserted `surfaces:` was present, incidentally, while proving a
different point (docs intent goes in the `docs:` block, not the generators array).
That assertion is now the ABSENCE, with the reason attached, since the correct
scaffold says nothing there.

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

Author: dmealing

server/typescript/packages/cli/src/commands/init.ts

@@ -138,9 +138,15 @@ export default defineConfig({
     barrel(),
   ],
   docs: {
-    outDir:   "./docs",        // model + api surfaces both land here (run: meta docs)
+    outDir:   "./docs",        // every surface lands here (run: meta docs)
     layout:   "flat",          // or "package" for multi-package models
-    surfaces: ["model", "api"],
+    // surfaces defaults to ["model", "api", "requirements", "agent"] — all four.
+    // Deliberately NOT narrowed here: the requirements and agent surfaces emit ZERO
+    // files for a project that has nothing for them to describe, and the always-on
+    // agent context points at the agent/ pages by name. Scaffolding a narrower list
+    // turned that pointer into a pointer at nothing. Narrow it yourself if you want
+    // fewer docs — but note it says what your docs ARE, not which of them you commit
+    // (a page you do not commit is exempt from verify --docs once it is git-ignored).
   },
 });
 `;

server/typescript/packages/cli/test/unit/init-scaffold-config.test.ts

@@ -35,7 +35,13 @@ describe("meta init scaffolds metaobjects.config.ts", () => {
     // `docs:` config block consumed by `meta docs`, not via a deprecated generator.
     expect(body).not.toContain("apiDocsFile");
     expect(body).toContain("docs:");
-    expect(body).toContain("surfaces:");
+    // ...and does NOT narrow `surfaces`. The resolver defaults to all four, and its
+    // own rationale is that `agent` must default ON "so the always-on agent-context
+    // pointer can name the files: a pointer to a page an adopter has to opt into is a
+    // pointer at nothing." The scaffold used to write ["model", "api"], switching off
+    // `requirements` and `agent` for every scaffolded project and defeating exactly
+    // that. Asserted as an ABSENCE because the correct scaffold says nothing here.
+    expect(body).not.toMatch(/^\s*surfaces:\s*\[/m);
     expect(nextStepsBlock(true)).toContain("meta docs");
   });