@kudzujs/core 0.11.1 → 0.11.2

package/README.md

@@ -14,7 +14,7 @@ Kudzu compiles ordinary React-shaped TypeScript and TSX into complete static HTM
 
 > Experimental `0.11.x`: the compiler API and supported TSX surface may change.
 
-**Latest release: 0.11.1 - List/detail data consistency.** One layout-owned project record now remains consistent across list/detail navigation, one server mutation, and document reload with exact request counts and no query runtime. Read the [release notes](./RELEASES.md#0111---listdetail-data-consistency), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.11.1), or follow the [architecture packet](./docs/next-architecture/README.md).
+**Latest release: 0.11.2 - Request coordination evidence.** Three unrelated server-data fixtures confirm that one explicit owner, ordinary state, and owned effects remain sufficient; no request registry, cache, or query runtime was added. Read the [release notes](./RELEASES.md#0112---request-coordination-evidence), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.11.2), or follow the [architecture packet](./docs/next-architecture/README.md).
 
 - [Documentation](https://kudzujs.cloud/docs)
 - [Installation guide](https://kudzujs.cloud/docs#install)

package/RELEASES.md

@@ -1,5 +1,51 @@
 # Kudzu Releases
 
+## 0.11.2 - Request Coordination Evidence
+
+Kudzu 0.11.2 reviews three unrelated server-data fixtures and closes shared
+request coordination without adding a new semantic primitive.
+
+### Changed in 0.11.2
+
+- Reviewed the project application, TanStack Query-shaped product loading, and
+  Apache Answer/SWR-shaped question loading.
+- Machine-recorded that all three use one explicit owner, ordinary state, one
+  owned fetch effect, dependency invalidation, cleanup, and static exclusion.
+- Recorded no repeated same-key independent owners, subscriber lifetime,
+  mutation invalidation, retained query result, or cache-bound requirement.
+- Updated `create-kudzu@0.1.110` to generate projects on
+  `@kudzujs/core@^0.11.2`.
+
+### Output Evidence
+
+- The project application remains byte-identical at 20 files, 69,501 raw /
+  24,649 aggregate gzip bytes, and deploy digest
+  `bc6335131b7867da2857621211919fad43ebfb9414aac711c45f0c8ed3803022`.
+- The list/detail session remains 55,736 raw / 21,208 aggregate gzip JavaScript
+  bytes; `/help` remains 0 B JavaScript.
+- No semantic primitive, compiler pass, production compiler line, runtime
+  concept, request registry, subscriber set, invalidation graph, cache, or
+  browser byte was added.
+
+### Validation
+
+- Existing required-Chrome journeys remain the executable evidence for all
+  three reviewed fixtures.
+- The full suite, package smoke, registry metadata, and fresh installation are
+  release gates.
+
+### Limits
+
+Automatic same-key deduplication and retained query data remain unsupported.
+They require repeated executable pressure from independent owners before a
+shared primitive can be reconsidered.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.11.2
+```
+
 ## 0.11.1 - List/Detail Data Consistency
 
 Kudzu 0.11.1 proves that ordinary layout-owned state and one native fetch effect

package/docs/next-architecture/application-capability-release-plan.md

@@ -363,6 +363,13 @@ bytes over `0.11.0`. Twenty-one fresh Chrome profiles record a 0.9 ms median
 list-to-detail completion with a 0.7/1.2 ms range, overlapping the prior
 0.6/1.3 ms range; no latency change is claimed.
 
+Clean-worktree `npm run check`, 273/273 required-Chrome tests, and packed-package
+smoke passed on 2026-08-22. Release commit `5bab3fe`, tag `v0.11.1`, feature CI
+`32573961250`, the GitHub release, `@kudzujs/core@0.11.1`,
+`create-kudzu@0.1.109`, registry metadata, and a fresh registry-backed scaffold
+install/check passed. Publish workflow `32574182988` completed every version,
+package, publication, and registry gate.
+
 ### `0.11.2`: Shared Request Coordination
 
 - **Purpose:** implement only the deduplication, subscriber, and invalidation
@@ -377,6 +384,31 @@ list-to-detail completion with a 0.7/1.2 ms range, overlapping the prior
 - **Done condition:** architecture review records the reused or new primitive,
   runtime bytes, cache bound, and cleanup behavior.
 
+**Completion evidence:** architecture review covers three unrelated executable
+fixtures: the project application, TanStack Query-shaped product loading, and
+Apache Answer/SWR-shaped question loading. Every fixture has one explicit data
+owner, ordinary loading/error/data state, one native fetch effect, dependency or
+owner invalidation, exact cleanup, and static exclusion. None has two independent
+owners requesting one key, independently releasable subscribers, mutation-key
+invalidation, retained results after owner release, or a cache bound.
+
+The stop condition is met and this packet closes with no new primitive. The
+project application records `closed-no-new-primitive`, the three reviewed
+fixtures, an empty repeated-missing-contract list, and the reused semantics in
+its machine-readable capability contract. Existing fixture journeys remain the
+executable behavioral evidence. Absence of generic deduplication is not itself
+fixture pressure.
+
+This packet adds zero semantic primitives, ModuleIR kinds, compiler passes,
+production compiler lines, runtime concepts, normalization rules, adapter rules,
+public APIs, request registries, subscriber sets, invalidation graphs, caches, or
+browser bytes. One existing machine-readable contract and assertion change;
+all three existing positive fixtures remain behaviorally unchanged. The project
+application retains its 20-file, 69,501 raw / 24,649 aggregate gzip deploy and
+55,736 raw / 21,208 aggregate gzip two-route JavaScript session. Cache bound is
+not applicable because no cache exists; cleanup remains existing effect and
+route/layout owner release.
+
 ### `0.11.3`: Mutation, Optimistic Update, And Rollback
 
 - **Purpose:** complete issue create/edit/delete behavior under failure.
@@ -988,5 +1020,6 @@ release transaction where possible or document and publish a forward-fix patch.
 | `0.10.2` | Released | Preserve the published shared-layout navigation and exact route-release evidence. | None |
 | `0.10.3` | Released | Preserve the published guarded persistence recipe and zero-runtime exclusion. | None |
 | `0.11.0` | Released | Preserve the published owned-fetch lifecycle and zero-query-runtime exclusion. | None |
-| `0.11.1` | Active | Measure list/detail mutation consistency, duplicate requests, route changes, and refresh limits. | None |
-| `0.11.2` onward | Blocked | Wait for the preceding patch acceptance and release record. | Ordered dependency |
+| `0.11.1` | Released | Preserve the published single-owner consistency and exact request-count evidence. | None |
+| `0.11.2` | Active | Review two independent fixtures for the same missing coordination contract before adding semantics. | None |
+| `0.11.3` onward | Blocked | Wait for the preceding patch acceptance and release record. | Ordered dependency |

package/docs/next-architecture/versioning.md

@@ -66,7 +66,7 @@ Keep each patch behavior-preserving and independently reviewable. If a boundary
 
 ## Generator Versions
 
-`create-kudzu@0.1.109` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.11.1`.
+`create-kudzu@0.1.110` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.11.2`.
 
 ## Release Boundary
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kudzujs/core",
-  "version": "0.11.1",
+  "version": "0.11.2",
   "description": "HTML-first TSX framework with synchronous state semantics and no virtual DOM",
   "type": "module",
   "license": "MIT",