@kudzujs/core 0.12.3 → 0.12.4

package/PERFORMANCE.md

@@ -6,6 +6,28 @@ 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.12.4 Nested Layout Evidence Decision
+
+Verified 2026-08-24 on Linux x64 with Node 24.14.0 and Chrome
+142.0.7444.175. Six executable route sets fit the existing ownership model: one
+retained layout owner around one replaceable route owner, followed by existing
+conditional, keyed, effect, and DOM ownership. Zero routes prove an intermediate
+retained layout lifetime, so the packet closes by its stop condition without an
+owner chain.
+
+Generated output is byte-identical to `0.12.3`: 43 deploy files totaling 123,835
+raw / 45,379 aggregate gzip bytes with SHA-256
+`fb9d24cc01791bf80b67b659738ba62beded6ff6ce14a86a278fa4b34d088acf`.
+The two-route session remains 16 JavaScript files totaling 61,126 raw / 22,663
+aggregate gzip bytes, and `/help` remains 0 B JavaScript.
+
+Core semantic LOC remains 5,682 with zero semantic primitives, IR kinds,
+compiler passes, production compiler/runtime lines, runtime concepts, layout
+registries, disposal paths, public APIs, browser files, or browser bytes added.
+No benchmark rerun or latency comparison applies because production and
+generated code are unchanged; the published `0.12.3` 1.8 ms median and 1.5-2.4
+ms range remain provenance rather than a new claim.
+
 ## 0.12.3 Route Failure And Restoration Policy
 
 Measured 2026-08-24 on Linux x64 with Node 24.14.0 and Chrome

package/README.md

@@ -14,7 +14,7 @@ Kudzu compiles ordinary React-shaped TypeScript and TSX into complete static HTM
 
 > Experimental `0.12.x`: the compiler API and supported TSX surface may change.
 
-**Latest release: 0.12.3 - Route failure and restoration policy.** Fetch and response-body transport failures retain the current document for focused retry, while invalid documents and assets keep native fallback. Read the [release notes](./RELEASES.md#0123---route-failure-and-restoration-policy), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.12.3), or follow the [architecture packet](./docs/next-architecture/README.md).
+**Latest release: 0.12.4 - Nested layout evidence decision.** Six executable route sets fit the existing single-layout model, so Kudzu adds no speculative owner chain or browser runtime. Read the [release notes](./RELEASES.md#0124---nested-layout-evidence-decision), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.12.4), 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,52 @@
 # Kudzu Releases
 
+## 0.12.4 - Nested Layout Evidence Decision
+
+Kudzu 0.12.4 reviews executable route ownership evidence and keeps the existing
+single-layout model instead of adding a speculative nested owner chain.
+
+### Changed in 0.12.4
+
+- Reviewed the project application's list/detail/runtime routes, Apache Answer
+  route and authentication shells, Context and Zustand carts, and independent
+  navigation groups.
+- Recorded zero routes requiring an intermediate retained layout whose state,
+  effects, or DOM survive descendant replacement and dispose on subtree exit.
+- Accepted one shared layout plus static composition, route ownership, native
+  document navigation, and disjoint navigation groups as the current boundary.
+- Updated `create-kudzu@0.1.117` to generate projects on
+  `@kudzujs/core@^0.12.4`.
+
+### Output Evidence
+
+- The application remains unchanged at 43 files, 123,835 raw / 45,379 aggregate
+  gzip bytes, and deploy digest
+  `fb9d24cc01791bf80b67b659738ba62beded6ff6ce14a86a278fa4b34d088acf`.
+- The maintained enhanced session remains 16 JavaScript files totaling 61,126
+  raw / 22,663 aggregate gzip bytes; `/help` remains 0 B JavaScript.
+- No semantic primitive, IR kind, compiler pass, production compiler/runtime
+  line, runtime concept, layout registry, disposal path, or browser byte was
+  added.
+
+### Validation
+
+- The machine-readable project contract records six reviewed route sets, zero
+  qualifying routes, no owner chain, and the reused ownership semantics.
+- The full 273-test suite, package smoke, registry metadata, and fresh
+  installation are release gates.
+
+### Limits
+
+Nested retained-layout owners remain unsupported. Reconsideration requires
+three unrelated executable application routes proving the same intermediate
+lifetime and explicit deepest-first disposal order.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.12.4
+```
+
 ## 0.12.3 - Route Failure And Restoration Policy
 
 Kudzu 0.12.3 defines recovery for enhanced route failures without adding an

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

@@ -665,6 +665,39 @@ against the macOS arm64 Chrome 151 `0.12.2` samples.
 - **Done condition:** either existing layout composition is accepted or a
   minimal layout-owner chain is approved with explicit disposal order.
 
+**Completion evidence:** architecture review covers the project application's
+list, static detail, runtime project, and runtime issue routes; Apache Answer's
+questions, tags, admin, and legal route-shell reduction; its independently
+reduced authentication shell; the Context and Zustand cart reductions; and the
+two disjoint navigation-group shells. All executable evidence fits one retained
+layout owner around one replaceable route owner, followed by existing
+conditional, keyed, effect, and DOM ownership. The project runtime routes use
+native document navigation, the Answer shell is static composition, and the
+independent navigation groups require disjoint top-level owners rather than a
+nested owner chain.
+
+No reviewed route proves an intermediate layout whose DOM, state, or effects
+must survive descendant route replacement and then dispose on subtree exit.
+The qualifying evidence count is zero, below the required three unrelated
+routes. The stop condition is met: current nesting is source organization or
+static composition, so this packet accepts the existing single-layout model and
+does not authorize a layout-owner chain. A future review must first prove the
+same otherwise-inexpressible intermediate lifetime in three unrelated
+executable application routes, including leaf-before-intermediate and
+deepest-first disposal requirements.
+
+The project application records `closed-by-stop-condition`, the reviewed route
+sets, an empty qualifying-route list, and the reused ownership semantics in its
+machine-readable capability contract. This packet adds zero semantic
+primitives, ModuleIR or RouteIR kinds, compiler passes, production compiler or
+runtime lines, runtime concepts, normalization or adapter rules, public APIs,
+layout registries, disposal paths, browser files, or browser bytes. Existing
+fixtures and output remain unchanged: 43 deploy files totaling 123,835 raw /
+45,379 aggregate gzip bytes with the same deploy digest, a 61,126 raw / 22,663
+aggregate gzip two-route JavaScript session, and 0 B JavaScript on `/help`. No
+benchmark rerun or latency claim applies to a machine-readable evidence decision
+with no generated-output change.
+
 ## `0.13.x`: Forms
 
 ### `0.13.0`: Production Form And Server Validation
@@ -1204,5 +1237,6 @@ release transaction where possible or document and publish a forward-fix patch.
 | `0.12.1` | Released | Preserve the published layout/history/focus/scroll evidence. | None |
 | `0.12.2` | Released | Preserve the published authentication and permission evidence. | None |
 | `0.12.3` | Released | Preserve the published route failure, focused retry, native fallback, and precommit retention evidence. | None |
-| `0.12.4` | Active | Complete the nested layout evidence decision. | None |
-| `0.12.5` onward | Blocked | Complete the `0.12.4` release transaction first. | Ordered patch boundary |
+| `0.12.4` | Released | Preserve the published single-layout decision and zero-owner-chain evidence. | None |
+| `0.13.0` | Active | Complete the production form and server-validation packet. | None |
+| `0.13.1` onward | Blocked | Complete the `0.13.0` release transaction first. | Ordered patch boundary |

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.116` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.12.3`.
+`create-kudzu@0.1.117` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.12.4`.
 
 ## Release Boundary
 

package/package.json

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