chore(release): Maven Central 8.0.6

A Maven-only patch: the plugin now resolves relative generator arg paths
(<outputDir>, <finalOutputDir>, <templatesDir>, <templateRoot>) against the
module, not the shell (9928120). On 8.0.5 a multi-module build run from the
parent, or `mvn -f <module>/pom.xml` from any other directory, read templates
from and wrote generated code to the wrong place.

npm, PyPI and NuGet have no product change and stay at 1.0.5. Maven takes the
shared minor.patch 1.0.6 on npm major + 7. No `v1.0.6` tag: that tag names an npm
release (scripts/finish-release.mjs), and the site keeps building from v1.0.5
until the next full cut. The site payload and the version-bearing docs state
8.0.6 now so the tree agrees with what ships.

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

Author: dmealing

AGENTS.md

@@ -39,10 +39,10 @@ because a conformance corpus gates the ports against each other and never agains
 in ADR-0035 **Amendment 3**. Do not reintroduce a waiting gate in any form.
 
 
-**Where the versions are.** `latest` is **`1.0.5`** on npm, **`8.0.5`** on Maven Central,
+**Where the versions are.** `latest` is **`1.0.5`** on npm, **`8.0.6`** on Maven Central,
 **`1.0.5`** on PyPI and **`1.0.5`** on NuGet (the Maven major is always **npm major + 7**, so
-1.0.5 is 8.0.5). All four moved at 1.0.5, as they did at 1.0.3 and 1.0.4: every port had changed
-product code. **1.0 is CUT**: the `1.0.0-rc.5` through `rc.8` candidates, 1.0.4's `rc.1` and
+1.0.6 is 8.0.6). All four moved at 1.0.5; Maven alone took 1.0.6 (8.0.6), a plugin fix, and the
+other three sat it out, which is the convergent-publishing rule working as intended. **1.0 is CUT**: the `1.0.0-rc.5` through `rc.8` candidates, 1.0.4's `rc.1` and
 1.0.5's `rc.1` through `rc.11` are
 superseded, and npm's `next` tag is REPOINTED onto each release — not deleted, because
 `dist-tag rm` 403s for every token we hold (`docs/RELEASING.md` §4).
@@ -82,7 +82,7 @@ PyPI has had no product change since `0.25.0` — nothing is broken.
 
 **Key cross-language features shipped:** FR5 family (a/b/c/d/e + WARN envelope-shape — actionable loader errors per ADR-0009); FR-003 (Java RDB runtime persistence + projections; schema migrations are TS-only — the Java migration engine was removed); FR-006 (template.output parser-on-receipt codegen per ADR-0010 in all 5 ports); FR-008 + FR-009 (cross-port REST API contract + the nine filter operators); FR-018 (M:N relationship codegen in all 5 ports — entity navigation + idiomatic ORM wiring [Drizzle m2m / EF Core `UsingEntity` / Spring repo+JPA / Exposed / Pydantic+route as the SQLAlchemy-secondary equivalent] + REST traversal `GET /<source-plural>/{id}/<relation>` + Tier-2 docs, gated by the shared api-contract m2m corpus in both lanes + persistence-conformance; the TanStack M:N client hook is a deferred client-ergonomics follow-up); SP-H (field-subtype end-to-end hardening: every concrete `field.*` subtype write+read round-trips cross-port via the persistence `op: roundtrip` gate; cut `field.byte`/`field.short`/`field.class` non-functional stubs; cross-port filter-op reconciliation for uuid/currency); source v2 paradigm (ADR-0007); metadata-ktx Kotlin facade; per-target output directories (TS codegen).
 
-**Latest release: 1.0.5** (2026-09-23) — npm `1.0.5`, Maven Central `8.0.5`, PyPI `1.0.5`, NuGet `1.0.5`; a coordinated PATCH with changed product code in every port, gated by `1.0.5-rc.11` on the adopter estate (`rc-gate.sh` 7/7, contract suite 43/43 in all five ports). Carries the **core vs helpers** reframe (ADR-0034 Amendment 3 — every generator is a reference helper, and **eject ships in every port**: `metaobjects eject`, `mvn metaobjects:eject`, `dotnet meta eject`), the REST collection URL renamed to the entity name (breaking for generated routes), an unpairable M:N junction made a load error in every port, a view-only projection's REST surface in all five ports, the codegen-compile gate in every port, and the `migrate` table-rename fix. **It changes generated output**: adopters with committed generated code must run `meta gen` (see the CHANGELOG's upgrading notes).
+**Latest release: 1.0.5** (2026-09-23), plus Maven Central `8.0.6` the same day (a Maven-plugin fix; the other registries sat it out) — npm `1.0.5`, Maven Central `8.0.5`, PyPI `1.0.5`, NuGet `1.0.5`; a coordinated PATCH with changed product code in every port, gated by `1.0.5-rc.11` on the adopter estate (`rc-gate.sh` 7/7, contract suite 43/43 in all five ports). Carries the **core vs helpers** reframe (ADR-0034 Amendment 3 — every generator is a reference helper, and **eject ships in every port**: `metaobjects eject`, `mvn metaobjects:eject`, `dotnet meta eject`), the REST collection URL renamed to the entity name (breaking for generated routes), an unpairable M:N junction made a load error in every port, a view-only projection's REST surface in all five ports, the codegen-compile gate in every port, and the `migrate` table-rename fix. **It changes generated output**: adopters with committed generated code must run `meta gen` (see the CHANGELOG's upgrading notes).
 
 See `spec/roadmap.md` for the active + planned work picture.
 

CHANGELOG.md

@@ -10,6 +10,12 @@ here.**
 
 ## [Unreleased]
 
+## [1.0.6] — 2026-09-23
+
+_Maven Central `8.0.6` only. npm, PyPI and NuGet have no product change and stay at `1.0.5`
+(convergent publishing: a registry takes a number only when it publishes). `metamodelVersion`
+stays `1.0`._
+
 ### Fixed
 
 - **Maven plugin: a relative path in a generator's `<args>` resolved against the shell, not the

README.md

@@ -119,8 +119,8 @@ first-week wedge plan — and `meta init` picks up from there.
 | Language | Status | Quickstart | Source |
 |---|---|---|---|
 | TypeScript | **npm `1.0.5`** — the `@metaobjectsdev/*` packages | [`docs/ports/typescript.md`](docs/ports/typescript.md) | [`server/typescript/`](server/typescript/) · [`client/web/`](client/web/) |
-| Java | **Maven Central `8.0.5`** (`com.metaobjects:*` — the JVM major is npm major + 7) — loader + OMDB + render + Maven plugin all shipped; full conformance green | [`docs/ports/java.md`](docs/ports/java.md) | [`server/java/`](server/java/) |
-| Kotlin | **Maven Central `8.0.5`** — codegen tier on top of Java: 14 generators (entity, Exposed table, relations, repository, payload, output-parser, output-prompt, render-helper, extractor, filter-allowlist, validator, Spring config, storedProc, Spring controller); 24 / 24 persistence-conformance | [`docs/ports/kotlin.md`](docs/ports/kotlin.md) | [`server/java/codegen-kotlin/`](server/java/codegen-kotlin/) · [`server/java/metadata-ktx/`](server/java/metadata-ktx/) |
+| Java | **Maven Central `8.0.6`** (`com.metaobjects:*` — the JVM major is npm major + 7) — loader + OMDB + render + Maven plugin all shipped; full conformance green | [`docs/ports/java.md`](docs/ports/java.md) | [`server/java/`](server/java/) |
+| Kotlin | **Maven Central `8.0.6`** — codegen tier on top of Java: 14 generators (entity, Exposed table, relations, repository, payload, output-parser, output-prompt, render-helper, extractor, filter-allowlist, validator, Spring config, storedProc, Spring controller); 24 / 24 persistence-conformance | [`docs/ports/kotlin.md`](docs/ports/kotlin.md) | [`server/java/codegen-kotlin/`](server/java/codegen-kotlin/) · [`server/java/metadata-ktx/`](server/java/metadata-ktx/) |
 | C# | **NuGet `1.0.5`** — loader + conformance + EF Core codegen + render engine + `dotnet meta` CLI all shipped | [`docs/ports/csharp.md`](docs/ports/csharp.md) | [`server/csharp/`](server/csharp/) |
 | Python | **PyPI `1.0.5`** — loader + conformance + render + entity-model codegen + ObjectManager runtime shipped; schema migrations are TS-owned (ADR-0015) | [`docs/ports/python.md`](docs/ports/python.md) | [`server/python/`](server/python/) |
 

docs/RELEASING.md

@@ -760,7 +760,7 @@ Project `metaobjects` → **Settings → Publishing → Add a new GitHub publish
 
 The 14 `com.metaobjects:*` modules (15 artifacts, counting the parent POM) ship to **Maven Central via the Sonatype Central Portal**,
 versioned on its own major line — npm major + 7, so `7.x` while npm was `0.x` and `8.x` from the
-1.0 cut (currently `8.0.5`) — in the parent + module poms. Signed with the maintainer's GPG key.
+1.0 cut (currently `8.0.6`) — in the parent + module poms. Signed with the maintainer's GPG key.
 
 ## Procedure
 

docs/llms/llms-full.txt

@@ -1,6 +1,6 @@
 # MetaObjects -- Full Reference Corpus
 
-> Coding agents get context — rules files, memories, MCP servers — and context is advisory: nothing fails when the code stops matching it. MetaObjects gives your agent one typed model of your application — data, API, UI, prompt payloads, and what the software is supposed to do — generates each layer's code from it in TypeScript, Java, Kotlin, C# and Python with no proprietary runtime in the output, and fails your build when generated code, a prompt, or a claimed capability drifts from that model. Your hand-written logic stays yours. Apache 2.0. Shipping at `1.0.5` on npm and `8.0.5` on Maven Central.
+> Coding agents get context — rules files, memories, MCP servers — and context is advisory: nothing fails when the code stops matching it. MetaObjects gives your agent one typed model of your application — data, API, UI, prompt payloads, and what the software is supposed to do — generates each layer's code from it in TypeScript, Java, Kotlin, C# and Python with no proprietary runtime in the output, and fails your build when generated code, a prompt, or a claimed capability drifts from that model. Your hand-written logic stays yours. Apache 2.0. Shipping at `1.0.5` on npm and `8.0.6` 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.
 
@@ -35,7 +35,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 `8.0.5`.
+   - 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 `8.0.6`.
    - 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>`.)
@@ -122,8 +122,8 @@ Today the TypeScript toolchain publishes and TypeScript and Python projects cons
 | Language | Status | Notes |
 |---|---|---|
 | TypeScript | Reference implementation, npm `1.0.5` | All six pillars, and the only port that runs the requirements `meta verify` checks and publishes shared models. 2500+ tests passing. Owns the canonical schema-migration toolchain used by every port (ADR-0015). Bun-first dev. |
-| Java | Maven Central `8.0.5` | Spring REST + DTO + repository-interface codegen, OMDB runtime persistence (pure data-access) with Spring-tx. Fully green across all conformance corpora. |
-| Kotlin | Maven Central `8.0.5` | KotlinPoet codegen + Exposed runtime + `metadata-ktx` facade. Ships via the Java reactor. |
+| Java | Maven Central `8.0.6` | Spring REST + DTO + repository-interface codegen, OMDB runtime persistence (pure data-access) with Spring-tx. Fully green across all conformance corpora. |
+| Kotlin | Maven Central `8.0.6` | KotlinPoet codegen + Exposed runtime + `metadata-ktx` facade. Ships via the Java reactor. |
 | C# | NuGet `1.0.5` (.NET tool) | Loader + canonical serializer + EF Core + ASP.NET codegen + render/verify. `dotnet meta` tool. |
 | Python | PyPI `1.0.5` | Loader + serializer + render + verify + codegen + `ObjectManager` runtime. Fully green across all corpora. |
 
@@ -178,7 +178,7 @@ Universal web client (`client/web/packages/`): `@metaobjectsdev/runtime-web`, `@
 
 ## Java / Kotlin Maven coordinates
 
-All published to Maven Central under `com.metaobjects:*` at `8.0.5`:
+All published to Maven Central under `com.metaobjects:*` at `8.0.6`:
 
 - `metaobjects-metadata`, `metaobjects-metadata-ktx`
 - `metaobjects-codegen-base`, `metaobjects-codegen-mustache`, `metaobjects-codegen-spring`, `metaobjects-codegen-kotlin`, `metaobjects-codegen-plantuml`
@@ -215,7 +215,7 @@ Project marker directory: `.metaobjects/`.
 
 ## Quickstart (Java / Kotlin)
 
-Add the Maven coordinates above at `8.0.5`. 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 `8.0.6`. 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).
 
 ---