site: the "verified" page was not, and the story page still read pre-release

getting-started.html leads with "every command and output below is real — verified". Checked
against the CLI it names, three things on it were not:

- `meta init` scaffolds FIVE generators, not four. `SCAFFOLDED_GENERATOR_NAMES` is entity,
  queries, routes, barrel AND names, and the scaffolded config imports and wires
  `namesFile()`. The tree, the prose, the config excerpt and the run output all omitted it,
  so a reader following the page gets a file the page never mentions — and `names.ts` is
  exactly the kind of owned generator the page exists to sell.
- The run therefore emits five files, not four: `<Entity>.names.ts` is real output
  (`NAMES_FILE_SUFFIX = ".names.ts"`), so "4 written" and "three things per entity" were
  both short by one.
- The scaffold ships SEVEN agent skills, not six — `metaobjects-fit-assessment` was missing
  from the list.

A page whose whole credibility device is "this is a real transcript" cannot be off by one in
three places; a reader who runs it and counts concludes the rest is unverified too.

story.html still said "So I'm bringing MetaObjects back" — present-progressive, three weeks
after 1.0 shipped to all four registries. It now says it is back, and names the date.

Not changed, and worth recording because it was raised and rejected: the capability matrix
reads "Zod / Pydantic / Jakarta / DataAnnotations / Jakarta", which looks like a duplicated
cell. It is correct. Both JVM ports use it — `codegen-kotlin` emits
`jakarta.validation.constraints` — so Java and Kotlin genuinely share a validation stack.
Changing it would have replaced a true statement with an invented library name.

Author: claude

www/getting-started.html

@@ -86,19 +86,20 @@ <h3>Set up the project and the agent context</h3>
 │   ├── entity.ts                <span class="c">#   Drizzle table + Zod schemas</span>
 │   ├── queries.ts               <span class="c">#   typed data-access</span>
 │   ├── routes.ts                <span class="c">#   REST endpoints (Fastify)</span>
+│   ├── names.ts                 <span class="c">#   physical table/column name constants</span>
 │   └── barrel.ts                <span class="c">#   the index.ts re-exports</span>
 ├── metaobjects.config.ts        <span class="c"># ← targets: dialect + what to generate</span>
 ├── src/db.ts                    <span class="c"># throwing stub — swap in your DB connection</span>
 ├── CLAUDE.md                    <span class="c"># wired to auto-load the context below</span>
 ├── .metaobjects/                <span class="c"># tool state + agent docs (AGENTS.md, CLAUDE.md)</span>
-└── .claude/skills/              <span class="c"># six skills your agent now has:</span>
+└── .claude/skills/              <span class="c"># seven skills your agent now has:</span>
     ├── metaobjects-authoring/   <span class="c">#   write &amp; edit models</span>
     ├── metaobjects-codegen/     <span class="c">#   run codegen</span>
     ├── metaobjects-runtime-ui/  <span class="c">#   wire up runtime + UI</span>
     ├── metaobjects-prompts/     <span class="c">#   typed LLM prompts</span>
     ├── metaobjects-verify/      <span class="c">#   drift checks</span>
     └── metaobjects-audit/       <span class="c">#   check adoption depth</span></pre>
-          <p>Those four generators under <code>codegen/generators/</code> are the point: they're plain
+          <p>Those five generators under <code>codegen/generators/</code> are the point: they're plain
             TypeScript, copied into your project, and <strong>yours to edit</strong>. <code>meta gen</code>
             runs those local copies — not the ones inside the package — so changing the shape of the
             generated code is an ordinary edit to a file you own.</p>
@@ -172,6 +173,7 @@ <h2 class="section-label">3 · Pick your language</h2>
     entityFile(),           <span class="c">// Drizzle table + Zod schemas + typed constants</span>
     queriesFile(),          <span class="c">// typed data-access (findById, list, create…)</span>
     routesFile(),           <span class="c">// REST endpoints (Fastify)</span>
+    namesFile(),            <span class="c">// &lt;Entity&gt;Names — physical table/column constants</span>
     barrel(),               <span class="c">// src/generated/index.ts re-exports</span>
   ],
   docs: { outDir: <span class="s">"./docs"</span>, surfaces: [<span class="s">"model"</span>, <span class="s">"api"</span>] },
@@ -209,10 +211,11 @@ <h2 class="section-label">5 · Generate</h2>
   <span class="n">NEW</span>        src/generated/Task.ts
   <span class="n">NEW</span>        src/generated/Task.queries.ts
   <span class="n">NEW</span>        src/generated/Task.routes.ts
+  <span class="n">NEW</span>        src/generated/Task.names.ts
   <span class="n">NEW</span>        src/generated/index.ts
 
-  4 written</pre>
-      <p class="gs-note">That's a real run. You get three things per entity (plus a barrel):</p>
+  5 written</pre>
+      <p class="gs-note">That's a real run. You get four things per entity (plus a barrel):</p>
       <ul class="gs-note">
         <li><code>Task.ts</code> — the <strong>entity</strong>: a Drizzle table, Zod insert/update schemas, a typed
           <code>Task</code> constants object (fields, labels, validation rules), and filter/sort allowlists.</li>

www/story.html

@@ -77,7 +77,7 @@ <h1>25 years private. Now open.</h1>
 
       <p>Then AI arrived, and I watched it generate beautiful code that <strong>drifted</strong>: locally perfect inside each prompt, globally inconsistent across the system. Different field names for the same concept. Types that diverged at every boundary. Plausible APIs that didn't quite exist. The vendors didn't fix it. That's when I realized I'd been looking at the wrong problem in 2022. The job was never <em>generating</em> code — it was keeping it <strong>coherent as a system grows</strong>. Metadata is that missing spine, and AI turns out to be a far better consumer of metadata than humans ever were.</p>
 
-      <p>So I'm bringing MetaObjects back — AI-first, open source — for the first time in 25 years. And here's the honest version of how I build now: I ship software fast, with heavy AI assistance, across a whole family of products. That's exactly the situation that wrecks consistency. <strong>MetaObjects is the spine that stops it</strong> — define the model once, generate every layer from it, and let drift break the build. My other products run on it. It isn't a thesis I'm pitching you; it's what I ship on.</p>
+      <p>So MetaObjects is back — AI-first, open source — for the first time in 25 years. 1.0 shipped on 2026-09-09, on npm, PyPI, NuGet and Maven Central. And here's the honest version of how I build now: I ship software fast, with heavy AI assistance, across a whole family of products. That's exactly the situation that wrecks consistency. <strong>MetaObjects is the spine that stops it</strong> — define the model once, generate every layer from it, and let drift break the build. My other products run on it. It isn't a thesis I'm pitching you; it's what I ship on.</p>
 
       <div class="article-cta">
         <p>The full origin story — 25 years, the production systems, the AI-drift turning point — lives on my site.</p>