docs: 0.24.1 / 7.24.1, and re-sync the llms mirrors with the library repo

All four registries are live at 0.24.1 (Maven 7.24.1): npm, PyPI, NuGet and
Maven Central. Refreshes the per-port badges and coordinates in index.html.

The llms files are copied wholesale from the library repo's docs/llms/ rather
than version-patched, because they had drifted in CONTENT, not just version.
Both still described the requirement vocabulary as it was BEFORE 0.24.0 — a
`live | partial | abandoned | superseded` @status enum and a live @Verifiedby,
all of which 0.24.0 retired and the loader now rejects. That is the exact
failure #337 was built to stop, on the most AI-facing surface we publish: an
agent reading llms.txt would have authored metadata that cannot load.

Also picks up a wrong worked example the same sync had been holding back —
`field.string: { name: createdAt, autoSet: onCreate }`, which is a
`field.timestamp`.

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

Author: claude

www/index.html

@@ -198,28 +198,28 @@ <h2 class="section-label">Five ports. All installable today.</h2>
         <tbody>
           <tr>
             <td><strong>TypeScript</strong></td>
-            <td><span class="status status-stable">npm 0.24.0 · reference</span></td>
-            <td>npm <code>@metaobjectsdev/*@0.24.0</code> (the reference implementation). Drizzle + Zod + Fastify + Hono codegen, Kysely runtime, and <code>meta migrate</code> for Postgres / SQLite / Cloudflare D1 — the TS toolchain owns schema migrations. 2,500+ tests across the workspace.</td>
+            <td><span class="status status-stable">npm 0.24.1 · reference</span></td>
+            <td>npm <code>@metaobjectsdev/*@0.24.1</code> (the reference implementation). Drizzle + Zod + Fastify + Hono codegen, Kysely runtime, and <code>meta migrate</code> for Postgres / SQLite / Cloudflare D1 — the TS toolchain owns schema migrations. 2,500+ tests across the workspace.</td>
           </tr>
           <tr>
             <td><strong>Java</strong></td>
-            <td><span class="status status-stable">Maven Central 7.24.0</span></td>
-            <td><code>com.metaobjects:metaobjects-*:7.24.0</code> on Maven Central. Spring REST + DTO + Repository + filter-allowlist codegen via <code>codegen-spring</code>; OMDB runtime persistence (CRUD / query / typed jsonb / Spring-tx); render + payload + verify + output-parser codegen.</td>
+            <td><span class="status status-stable">Maven Central 7.24.1</span></td>
+            <td><code>com.metaobjects:metaobjects-*:7.24.1</code> on Maven Central. Spring REST + DTO + Repository + filter-allowlist codegen via <code>codegen-spring</code>; OMDB runtime persistence (CRUD / query / typed jsonb / Spring-tx); render + payload + verify + output-parser codegen.</td>
           </tr>
           <tr>
             <td><strong>Kotlin</strong></td>
-            <td><span class="status status-stable">Maven Central 7.24.0</span></td>
-            <td><code>com.metaobjects:metaobjects-codegen-kotlin:7.24.0</code> + <code>metadata-ktx</code> Kotlin facade. KotlinPoet codegen: Exposed Tables, Spring controllers, payload VOs, output parsers, stored-proc helpers. Persistence-conformance against Testcontainers Postgres.</td>
+            <td><span class="status status-stable">Maven Central 7.24.1</span></td>
+            <td><code>com.metaobjects:metaobjects-codegen-kotlin:7.24.1</code> + <code>metadata-ktx</code> Kotlin facade. KotlinPoet codegen: Exposed Tables, Spring controllers, payload VOs, output parsers, stored-proc helpers. Persistence-conformance against Testcontainers Postgres.</td>
           </tr>
           <tr>
             <td><strong>C#.NET</strong></td>
-            <td><span class="status status-stable">NuGet 0.24.0</span></td>
-            <td>NuGet <code>MetaObjects</code> / <code>MetaObjects.Render</code> / <code>MetaObjects.Codegen</code> + the <code>dotnet meta</code> tool (<code>MetaObjects.Cli</code>), all <code>0.24.0</code>. EF Core entities + <code>AppDbContext</code> + ASP.NET minimal-API routes codegen; render engine + payload-VO codegen + <code>verify</code>. (Schema migrations are TS-owned.)</td>
+            <td><span class="status status-stable">NuGet 0.24.1</span></td>
+            <td>NuGet <code>MetaObjects</code> / <code>MetaObjects.Render</code> / <code>MetaObjects.Codegen</code> + the <code>dotnet meta</code> tool (<code>MetaObjects.Cli</code>), all <code>0.24.1</code>. EF Core entities + <code>AppDbContext</code> + ASP.NET minimal-API routes codegen; render engine + payload-VO codegen + <code>verify</code>. (Schema migrations are TS-owned.)</td>
           </tr>
           <tr>
             <td><strong>Python</strong></td>
-            <td><span class="status status-stable">PyPI 0.24.0</span></td>
-            <td>PyPI <code>metaobjects</code> <code>0.24.0</code> + the <code>metaobjects</code> CLI. Loader + canonical serializer + render + verify + codegen (Pydantic + FastAPI) + ObjectManager runtime. All five cross-port conformance corpora green.</td>
+            <td><span class="status status-stable">PyPI 0.24.1</span></td>
+            <td>PyPI <code>metaobjects</code> <code>0.24.1</code> + the <code>metaobjects</code> CLI. Loader + canonical serializer + render + verify + codegen (Pydantic + FastAPI) + ObjectManager runtime. All five cross-port conformance corpora green.</td>
           </tr>
         </tbody>
       </table>

www/llms-full.txt

@@ -1,6 +1,6 @@
 # MetaObjects -- Full Reference Corpus
 
-> A cross-language metadata standard for declaring typed entity models that drive code generation, runtime metadata access, drift detection, and prompt construction across TypeScript, Java, Kotlin, C#, and Python. Apache 2.0. Shipping at `0.24.0` on npm and `7.24.0` on Maven Central.
+> A cross-language metadata standard for declaring typed entity models that drive code generation, runtime metadata access, drift detection, and prompt construction across TypeScript, Java, Kotlin, C#, and Python. Apache 2.0. Shipping at `0.24.1` on npm and `7.24.1` on Maven Central.
 
 **Note for AI assistants:** This file is the concatenated reference material for MetaObjects, intended to be loaded as LLM context. For the short index, see [llms.txt](https://metaobjects.dev/llms.txt). For the canonical spec and source, see the [GitHub repo](https://github.com/metaobjectsdev/metaobjects). When this file is out of date relative to the GitHub source, the GitHub source wins.
 
@@ -31,7 +31,7 @@ If you are an AI assistant helping someone adopt MetaObjects, do this **first**
 
 1. **Install the port's package:**
    - TypeScript / Node: `npm install -D @metaobjectsdev/cli @metaobjectsdev/codegen-ts`
-   - Java / Kotlin: add `com.metaobjects:metaobjects-metadata`, `com.metaobjects:metaobjects-codegen-spring` (Java) or `com.metaobjects:metaobjects-codegen-kotlin` (Kotlin), and `com.metaobjects:metaobjects-maven-plugin`, all at `7.24.0`.
+   - Java / Kotlin: add `com.metaobjects:metaobjects-metadata`, `com.metaobjects:metaobjects-codegen-spring` (Java) or `com.metaobjects:metaobjects-codegen-kotlin` (Kotlin), and `com.metaobjects:metaobjects-maven-plugin`, all at `7.24.1`.
    - Python: `pip install metaobjects`
    - C#: install the MetaObjects .NET tool (invoked as `dotnet meta`).
 2. **Run `meta init`** (the Node `meta` CLI). It works in any project that has Node — including a JVM or Python project with a TypeScript frontend. It scaffolds a slim always-on `.metaobjects/AGENTS.md` + `.metaobjects/CLAUDE.md` (auto-wired via an `@.metaobjects/AGENTS.md` import line into the project's root `CLAUDE.md`/`AGENTS.md`, so it loads automatically) plus six `metaobjects-*` Claude Code skills under `.claude/skills/`, carrying only the project's language reference fragments. Re-run `meta init --refresh-docs` to update the agent docs after a CLI upgrade. (The Node `meta` CLI is the single agent-context scaffolder for every backend, by design — ADR-0033; the JVM/Python/C# CLIs deliberately redirect to it. For a non-Node project, scaffold just the agent context with `npx meta agent-docs --server <lang>`.)
@@ -93,11 +93,11 @@ Because the render is conformance-gated, the determinism guarantee holds in ever
 
 | Language | Status | Notes |
 |---|---|---|
-| TypeScript | Reference implementation, npm `0.24.0` | All four pillars. 2500+ tests passing. Owns the canonical schema-migration toolchain used by every port (ADR-0015). Bun-first dev. |
-| Java | Maven Central `7.24.0` | Spring REST + DTO + repository-interface codegen, OMDB runtime persistence (pure data-access) with Spring-tx. Fully green across all conformance corpora. |
-| Kotlin | Maven Central `7.24.0` | KotlinPoet codegen + Exposed runtime + `metadata-ktx` facade. Ships via the Java reactor. |
-| C# | NuGet `0.24.0` (.NET tool) | Loader + canonical serializer + EF Core + ASP.NET codegen + render/verify. `dotnet meta` tool. |
-| Python | PyPI `0.24.0` | Loader + serializer + render + verify + codegen + `ObjectManager` runtime. Fully green across all corpora. |
+| TypeScript | Reference implementation, npm `0.24.1` | All four pillars. 2500+ tests passing. Owns the canonical schema-migration toolchain used by every port (ADR-0015). Bun-first dev. |
+| Java | Maven Central `7.24.1` | Spring REST + DTO + repository-interface codegen, OMDB runtime persistence (pure data-access) with Spring-tx. Fully green across all conformance corpora. |
+| Kotlin | Maven Central `7.24.1` | KotlinPoet codegen + Exposed runtime + `metadata-ktx` facade. Ships via the Java reactor. |
+| C# | NuGet `0.24.1` (.NET tool) | Loader + canonical serializer + EF Core + ASP.NET codegen + render/verify. `dotnet meta` tool. |
+| Python | PyPI `0.24.1` | Loader + serializer + render + verify + codegen + `ObjectManager` runtime. Fully green across all corpora. |
 
 Conformance fixtures live at [`fixtures/`](https://github.com/metaobjectsdev/metaobjects/tree/main/fixtures). Every port runs the shared corpus byte-identically: metamodel (`conformance/`, 270 fixtures), render, persistence (Testcontainers Postgres, with an `op: roundtrip` gate so every `field.*` subtype write+read round-trips on every port), api-contract (41 scenarios — 26 core plus TPH / M:N / jsonb / write-through — two lanes: a reference server AND each port's generated API booted over HTTP), registry (byte-matched metamodel-vocabulary manifest, live + green in all five ports), and yaml/verify.
 
@@ -150,7 +150,7 @@ Universal web client (`client/web/packages/`): `@metaobjectsdev/runtime-web`, `@
 
 ## Java / Kotlin Maven coordinates
 
-All published to Maven Central under `com.metaobjects:*` at `7.24.0`:
+All published to Maven Central under `com.metaobjects:*` at `7.24.1`:
 
 - `metaobjects-metadata`, `metaobjects-metadata-ktx`
 - `metaobjects-codegen-base`, `metaobjects-codegen-mustache`, `metaobjects-codegen-spring`, `metaobjects-codegen-kotlin`, `metaobjects-codegen-plantuml`
@@ -187,7 +187,7 @@ Project marker directory: `.metaobjects/`.
 
 ## Quickstart (Java / Kotlin)
 
-Add the Maven coordinates above at `7.24.0`. Run codegen with `mvn metaobjects:generate` and codegen-drift checks with `mvn metaobjects:verify`. Configure generators (including Kotlin generators, which run through the same goal) on the `metaobjects-maven-plugin`. See [`server/java/`](https://github.com/metaobjectsdev/metaobjects/tree/main/server/java) and [`server/java/codegen-kotlin/README.md`](https://github.com/metaobjectsdev/metaobjects/tree/main/server/java/codegen-kotlin).
+Add the Maven coordinates above at `7.24.1`. Run codegen with `mvn metaobjects:generate` and codegen-drift checks with `mvn metaobjects:verify`. Configure generators (including Kotlin generators, which run through the same goal) on the `metaobjects-maven-plugin`. See [`server/java/`](https://github.com/metaobjectsdev/metaobjects/tree/main/server/java) and [`server/java/codegen-kotlin/README.md`](https://github.com/metaobjectsdev/metaobjects/tree/main/server/java/codegen-kotlin).
 
 ---
 
@@ -229,7 +229,7 @@ metadata.root:
         children:
           - field.long:    { name: id }
           - field.string:  { name: email }
-          - field.string:  { name: createdAt, autoSet: onCreate }
+          - field.timestamp: { name: createdAt, autoSet: onCreate }
           - identity.primary: { fields: [id] }
 ```
 
@@ -283,7 +283,7 @@ $ meta migrate --dialect sqlite --slug add-subscriber --db file:./dev.db --apply
 $ meta export --out ./snapshot.json
 ```
 
-Capability requirements (`requirement.functional` / `requirement.architectural`) are registered vocabulary in all five ports: what the system is supposed to do, declared in `metaobjects/` beside the entities it describes and loaded by the same loader -- no side file, no bespoke parser. `functional` fails when NOTHING implements it (existence); `architectural` fails when something VIOLATES it (universality). Hierarchy is nesting, `@status` is a loader-enforced closed enum (`live | partial | abandoned | superseded`), and a dangling `@implementedBy` is an ERROR on `live`/`partial` but CORRECT on `abandoned`/`superseded` -- those nodes are supposed to be gone, which is the point of recording them. `@verifiedBy` checks each named test exists and is not skipped; it never runs them. Object coverage is a WARNING, never a failure. Entirely opt-in -- a model with no `requirement.*` nodes produces no diagnostics, and no codegen, migrate or runtime path reads the type. The `meta verify` gate is the Node CLI; the other ports load and validate. See docs/features/requirements.md.
+Capability requirements (`requirement.functional` / `requirement.architectural`) are registered vocabulary in all five ports: what the system is supposed to do, declared in `metaobjects/` beside the entities it describes and loaded by the same loader -- no side file, no bespoke parser. `functional` fails when NOTHING implements it (existence); `architectural` fails when something VIOLATES it (universality). Hierarchy is nesting, `@status` is a loader-enforced closed enum (`planned | live | partial`), and a dangling `@implementedBy` is an ERROR on `live`/`partial` but CORRECT on `planned` -- an intention has nothing to point at yet. A requirement states what SHOULD be true and is never a journal of what happened, so retiring a capability is DELETION of its requirement: `@verifiedBy`, `@supersededBy` and the `abandoned`/`superseded` statuses were RETIRED in `0.24.0` and now fail the load (`ERR_UNKNOWN_ATTR` / `ERR_BAD_ATTR_VALUE`); `meta upgrade` rewrites what it can and refuses what needs a decision. Object coverage is a WARNING, never a failure. Entirely opt-in -- a model with no `requirement.*` nodes produces no diagnostics, and no codegen, migrate or runtime path reads the type. The `meta verify` gate is the Node CLI; the other ports load and validate. See docs/features/requirements.md.
 
 Non-TS ports run codegen + codegen-verify in their own build tool: `mvn metaobjects:generate` / `mvn metaobjects:verify` (Java/Kotlin), `dotnet meta gen` / `dotnet meta verify` (C#), `metaobjects gen` / `metaobjects verify` (Python). Schema migration is always the Node `meta` CLI.