@kudzujs/core 0.11.0 → 0.11.1

package/PERFORMANCE.md

@@ -6,6 +6,24 @@ Reproducibility classes: `npm run benchmark`, `npm run benchmark:keyed`, `npm ru
 
 The maintained 2026-08-13 comparison used Node 24.14.0 and an Intel Core i5-9500 Linux x64 host, one warm-up, and seven alternating fresh-process samples against clean `v0.8.44`. A narrow fast path skips Kudzu semantic transformation for 450 plain `.ts` modules whose runtime edges are exclusively resolvable relative TypeScript imports or exports; all other modules retain the existing transformer. Compile median fell from 2,323.9 ms to 1,413.2 ms (39.2%) and clean-build median from 3,325.3 ms to 2,382.4 ms (28.4%); every paired sample improved. Compile peak-RSS median fell from 571.2 MiB to 552.6 MiB, while build peak RSS was 570.9 MiB versus 568.8 MiB. Compiler scratch fell from 7,328,390 to 1,971,061 bytes. Both targets emitted the same 50 static HTML files, 10,980 bytes, and deploy SHA-256 `e107d78a7f55bc8a1af0ea6e53efeffa19b3d44d21c892484d103fa346e7ba7b`. This is a source-scale compiler comparison, not a cross-framework result.
 
+## 0.11.1 Project List/Detail Consistency
+
+Measured 2026-08-22 on macOS arm64 with Node 25.6.1 and Chrome
+151.0.7922.172. `RUNS=21 npm run benchmark:project-navigation` waits for both
+route-owned list data and the layout-owned project record before measuring
+list-to-detail completion across fresh Chrome profiles.
+
+The two-route session uses 16 unique JavaScript files totaling 55,736 raw /
+21,208 aggregate gzip bytes. Navigation samples are
+`[1.0, 0.7, 0.7, 1.0, 0.9, 0.9, 0.9, 0.9, 0.8, 0.9, 0.8, 0.9, 0.9, 1.2, 0.8, 0.9, 1.1, 1.0, 1.0, 0.8, 0.8]`
+ms, with a 0.9 ms median and 0.7/1.2 ms minimum/maximum.
+
+Compared with `0.11.0`, the authored shared record effect, list/detail outputs,
+and mutation handler add 966 raw / 445 aggregate gzip session bytes. The prior
+0.8 ms median and 0.6/1.3 ms range overlap, so no latency change is claimed.
+No compiler or browser-runtime source changed, and `/help` remains 0 B
+JavaScript.
+
 ## 0.11.0 Project Owned Fetch Lifecycle
 
 Measured 2026-08-22 on macOS arm64 with Node 25.6.1 and Chrome

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.0 - Owned fetch lifecycle.** The tracked project application now owns loading, accessible HTTP errors, explicit refetch, stale completion rejection, cancellation, and route-release behavior without a query runtime. Read the [release notes](./RELEASES.md#0110---owned-fetch-lifecycle), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.11.0), or follow the [architecture packet](./docs/next-architecture/README.md).
+**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).
 
 - [Documentation](https://kudzujs.cloud/docs)
 - [Installation guide](https://kudzujs.cloud/docs#install)

package/RELEASES.md

@@ -1,5 +1,54 @@
 # Kudzu Releases
 
+## 0.11.1 - List/Detail Data Consistency
+
+Kudzu 0.11.1 proves that ordinary layout-owned state and one native fetch effect
+keep list and detail routes consistent without a query framework.
+
+### Changed in 0.11.1
+
+- Added one server-backed project record owned by the retained application
+  layout and consumed by both project routes.
+- Added a detail mutation whose confirmed result is immediately observed by the
+  list without another read.
+- Counted exactly one initial GET, one mutation POST, no navigation GETs, and one
+  document-reload GET.
+- Recorded document-lifetime retention and the absence of automatic
+  deduplication, invalidation, subscribers, and retained query caches.
+- Updated `create-kudzu@0.1.109` to generate projects on
+  `@kudzujs/core@^0.11.1`.
+
+### Output Evidence
+
+- The application fixture emits 20 files, 69,501 raw / 24,649 aggregate gzip
+  bytes, and deploy digest
+  `bc6335131b7867da2857621211919fad43ebfb9414aac711c45f0c8ed3803022`.
+- The list/detail session uses 16 unique JavaScript files totaling 55,736 raw /
+  21,208 aggregate gzip bytes; `/help` remains 0 B JavaScript.
+- Twenty-one fresh Chrome profiles record a 0.9 ms navigation median and
+  0.7/1.2 ms range after both initial fetches complete.
+- No semantic primitive, compiler pass, production compiler line, runtime
+  concept, request registry, or query runtime was added.
+
+### Validation
+
+- Required Chrome proves mutation visibility, exact request counts, retained
+  layout identity, route release, and server restoration after reload.
+- The full suite, package smoke, registry metadata, and fresh installation are
+  release gates.
+
+### Limits
+
+Shared data lasts for one document and retained layout owner. Independently
+authored fetch owners are not deduplicated; coordinated requests remain blocked
+until unrelated fixtures require the same missing contract.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.11.1
+```
+
 ## 0.11.0 - Owned Fetch Lifecycle
 
 Kudzu 0.11.0 proves browser-only server data as application-owned state, one

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

@@ -317,6 +317,11 @@ Clean-worktree `npm run check`, 273/273 standard tests, the required project
 Chrome journey, the focused required-Chrome retry for the one full-suite browser
 timeout, and packed-package smoke pass on 2026-08-22.
 
+Release commit `8065d86`, tag `v0.11.0`, both CI jobs, the GitHub release,
+`@kudzujs/core@0.11.0`, `create-kudzu@0.1.108`, registry metadata, and a fresh
+registry-backed scaffold install/check passed on 2026-08-22. Publish workflow
+`32571667242` completed every version, package, publication, and registry gate.
+
 ### `0.11.1`: List And Detail Data Consistency Evidence
 
 - **Purpose:** expose the first real multi-consumer coordination limit.
@@ -329,6 +334,35 @@ timeout, and packed-package smoke pass on 2026-08-22.
 - **Done condition:** existing composition is accepted or the smallest repeated
   missing coordination contract is isolated.
 
+**Completion evidence:** one layout-owned project record composes from two
+primitive shared signals and one existing mount effect. The list and detail
+routes observe the same server-confirmed rename without another read. The
+deterministic journey records one initial GET, zero additional GETs across two
+enhanced route changes, one mutation POST, and exactly one new GET after full
+document reload. The refreshed document reconstructs revision 1 from server
+truth while route-owned detail draft state resets. `/help` remains complete HTML
+with 0 B JavaScript.
+
+Current composition is accepted. Shared data lasts for one document and retained
+layout owner; independently authored fetch owners are not deduplicated, and no
+request registry, invalidation graph, subscriber set, or retained query cache
+exists. This one fixture does not authorize `0.11.2`: it needs no coordination
+primitive after ownership is placed correctly, while the packet requires two
+additional independent fixtures to demonstrate the same missing contract.
+
+This packet adds zero semantic primitives, ModuleIR kinds, compiler passes,
+production compiler lines, runtime concepts, normalization rules, adapter rules,
+public APIs, caches, Providers, or query runtimes. One existing positive fixture
+gains list/detail consistency, counted domain requests, mutation, navigation,
+and reload cases. It emits 20 files totaling 69,501 raw / 24,649 aggregate gzip
+bytes with deploy SHA-256
+`bc6335131b7867da2857621211919fad43ebfb9414aac711c45f0c8ed3803022`.
+The two-route session uses 16 JavaScript files totaling 55,736 raw / 21,208
+aggregate gzip bytes, an authored application increase of 966 raw / 445 gzip
+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.
+
 ### `0.11.2`: Shared Request Coordination
 
 - **Purpose:** implement only the deduplication, subscriber, and invalidation
@@ -953,5 +987,6 @@ release transaction where possible or document and publish a forward-fix patch.
 | `0.10.1` | Released | Preserve the published state-scale evidence and explicit object-field limit. | None |
 | `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` | Active | Add the owned loading/error/data/refetch and stale-response journey. | None |
-| `0.11.1` onward | Blocked | Wait for the preceding patch acceptance and release record. | Ordered dependency |
+| `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 |

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.108` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.11.0`.
+`create-kudzu@0.1.109` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.11.1`.
 
 ## Release Boundary
 

package/package.json

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