@kudzujs/core 0.11.1 → 0.11.3

package/PERFORMANCE.md

@@ -6,6 +6,23 @@ 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.3 Project Optimistic Mutation
+
+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` retains the same
+fetch-complete list-to-detail interval; the required application journey
+separately executes optimistic failure, rollback, retry, and success.
+
+The two-route session uses 15 unique JavaScript files totaling 56,318 raw /
+21,211 aggregate gzip bytes. Navigation samples are
+`[0.7, 0.7, 0.8, 0.8, 0.9, 0.7, 0.8, 0.8, 0.8, 0.8, 0.7, 0.8, 0.9, 0.7, 0.8, 0.9, 0.8, 0.9, 1.0, 0.9, 0.7]`
+ms, with a 0.8 ms median and 0.7/1.0 ms minimum/maximum.
+
+Compared with `0.11.2`, the authored mutation status/error state, conditional
+UI, and async handler add 582 raw / 3 aggregate gzip session bytes. The prior
+0.9 ms median and 0.7/1.2 ms range overlap, so no latency change is claimed. No
+compiler or browser-runtime source changed, and `/help` remains 0 B JavaScript.
+
 ## 0.11.1 Project List/Detail Consistency
 
 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.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.3 - Optimistic mutation and rollback.** One layout-owned handler now proves optimistic list/detail state, disabled duplicate submission, exact HTTP-failure rollback, accessible error, retry, navigation, and reload without a transaction runtime. Read the [release notes](./RELEASES.md#0113---optimistic-mutation-and-rollback), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.11.3), 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,98 @@
 # Kudzu Releases
 
+## 0.11.3 - Optimistic Mutation And Rollback
+
+Kudzu 0.11.3 proves optimistic server mutation with ordinary shared state and
+one owned async handler rather than a transaction runtime.
+
+### Changed in 0.11.3
+
+- Added immediate optimistic project name/revision updates visible from list and
+  detail routes.
+- Disabled duplicate submission after the synchronous-turn optimistic commit.
+- Restored the exact prior state after an HTTP 500 and exposed an accessible
+  error.
+- Proved retry success, retained keyed row identity, enhanced navigation, and
+  server restoration after document reload.
+- Updated `create-kudzu@0.1.111` to generate projects on
+  `@kudzujs/core@^0.11.3`.
+
+### Output Evidence
+
+- The application emits 19 files, 73,202 raw / 25,057 aggregate gzip bytes, and
+  deploy digest
+  `40c68fef4eeba5ea4c1a92e9a8003b74e6a45b7a10671ee2f3e4952010117b26`.
+- The list/detail session uses 15 unique JavaScript files totaling 56,318 raw /
+  21,211 aggregate gzip bytes; `/help` remains 0 B JavaScript.
+- Twenty-one fresh Chrome profiles record a 0.8 ms navigation median and
+  0.7/1.0 ms range.
+- No semantic primitive, compiler pass, production compiler line, runtime
+  concept, transaction primitive, cache, or scheduler was added.
+
+### Validation
+
+- Required Chrome proves optimistic state, one accepted attempt after failure,
+  exact rollback, retry, identity, navigation, and reload.
+- The full suite, package smoke, registry metadata, and fresh installation are
+  release gates.
+
+### Limits
+
+The authored handler owns one mutation and snapshot. Generic transactions and
+same-turn programmatic reentrancy are not application semantics.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.11.3
+```
+
+## 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,38 @@ 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.
+
+Clean-worktree `npm run check`, 273/273 required-Chrome tests, and packed-package
+smoke passed on 2026-08-22. Release commit `0ae4d5d`, tag `v0.11.2`, CI
+`32575316981`, the GitHub release, `@kudzujs/core@0.11.2`,
+`create-kudzu@0.1.110`, registry metadata, and a fresh registry-backed scaffold
+install/check passed. Publish workflow `32575541567` completed every version,
+package, publication, and registry gate.
+
 ### `0.11.3`: Mutation, Optimistic Update, And Rollback
 
 - **Purpose:** complete issue create/edit/delete behavior under failure.
@@ -390,6 +429,30 @@ list-to-detail completion with a 0.7/1.2 ms range, overlapping the prior
 - **Done condition:** data integrity survives success, failure, navigation, and
   retry.
 
+**Completion evidence:** one layout-owned async rename handler snapshots the
+current project name/revision, writes an immediate optimistic value, disables its
+button after the synchronous-turn commit, and sends one native POST. The
+deterministic server rejects the first attempt. The handler restores the exact
+snapshot, exposes `HTTP 500` through an accessible alert, and leaves the retained
+keyed row identity unchanged. A retry from detail writes the optimistic value,
+clears the alert, commits the confirmed revision, survives list/detail
+navigation, and restores from server truth after full document reload. Counts
+record two attempts, one accepted mutation, and no mutation-triggered GET.
+
+Existing immediate setters, native async handlers, shared layout signals, and
+owner authority are sufficient. This packet adds zero semantic primitives,
+ModuleIR kinds, compiler passes, production compiler lines, runtime concepts,
+normalization rules, adapter rules, public APIs, transaction primitives, caches,
+or schedulers. One positive application fixture gains optimistic success,
+failure, rollback, disabled duplicate submission, navigation, retry, and reload
+cases. It emits 19 files totaling 73,202 raw / 25,057 aggregate gzip bytes with
+deploy SHA-256
+`40c68fef4eeba5ea4c1a92e9a8003b74e6a45b7a10671ee2f3e4952010117b26`.
+The two-route session uses 15 JavaScript files totaling 56,318 raw / 21,211
+aggregate gzip bytes, an authored application increase of 582 raw / 3 gzip bytes
+over `0.11.2`. Twenty-one fresh Chrome profiles record a 0.8 ms median with a
+0.7/1.0 ms range; no latency change is claimed.
+
 ### `0.11.4`: Pagination, Refresh, And Polling Policy
 
 - **Purpose:** complete bounded server-data loading before infinite data work.
@@ -988,5 +1051,7 @@ 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` | Released | Preserve the published no-new-primitive architecture decision and zero-byte result. | None |
+| `0.11.3` | Active | Prove optimistic mutation, exact rollback, duplicate-submit prevention, navigation, and retry. | None |
+| `0.11.4` 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.111` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.11.3`.
 
 ## Release Boundary
 

package/package.json

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