@kudzujs/core 0.11.3 → 0.12.0

package/PERFORMANCE.md

@@ -6,6 +6,45 @@ 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.0 Project Route Shell And Runtime Parameters
+
+Measured 2026-08-23 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 while the application also emits
+standalone runtime project and issue routes.
+
+The maintained enhanced session is unchanged at 16 JavaScript files totaling
+58,970 raw / 22,124 aggregate gzip bytes. Navigation samples are
+`[1.3, 1.4, 1.2, 1.4, 1.4, 1.4, 1.3, 1.3, 1.2, 1.4, 1.4, 1.3, 1.1, 1.2, 1.2, 1.2, 1.6, 1.3, 1.4, 1.4, 1.4]`
+ms, with a 1.3 ms median and 1.1/1.6 ms minimum/maximum. The range overlaps
+`0.11.4`, so no latency change is claimed.
+
+The runtime project route uses 17,905 raw / 8,455 aggregate gzip JavaScript
+bytes; its issue route uses 18,002 raw / 8,474 aggregate gzip bytes. Complete
+deploy output grows by 16 files and 28,314 raw / 11,911 aggregate gzip bytes.
+These routes reuse existing pathname parameters, layout effects, bindings, and
+native anchors. No compiler or browser-runtime source changed, and `/help`
+remains 0 B JavaScript.
+
+## 0.11.4 Project Pagination And Polling Policy
+
+Measured 2026-08-23 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. Required Chrome separately proves URL
+page/filter push and back synchronization, explicit refresh, hidden-page polling
+suppression, one visible refresh, exact cleanup, and results bounded to two rows.
+
+The two-route session uses 16 unique JavaScript files totaling 58,970 raw /
+22,124 aggregate gzip bytes. Navigation samples are
+`[1.3, 1.6, 1.3, 1.3, 1.3, 1.3, 1.2, 1.2, 1.2, 1.4, 1.3, 1.3, 1.3, 1.4, 1.3, 1.3, 1.3, 1.3, 1.2, 1.5, 1.4]`
+ms, with a 1.3 ms median and 1.2/1.6 ms minimum/maximum.
+
+Compared with `0.11.3`, the authored query controls, query-backed fetch
+dependencies, polling state/effect, and native timer/listener cleanup add 2,652
+raw / 913 aggregate gzip session bytes. The prior 0.8 ms median and 0.7/1.0 ms
+range do not overlap, so the measured 0.5 ms median increase is disclosed. No
+compiler or browser-runtime source changed, and `/help` remains 0 B JavaScript.
+
 ## 0.11.3 Project Optimistic Mutation
 
 Measured 2026-08-22 on macOS arm64 with Node 25.6.1 and Chrome
@@ -23,6 +62,11 @@ 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.
 
+A clean homepage verification rerun on the same environment recorded
+`[0.9, 0.7, 0.8, 0.9, 0.9, 0.7, 0.8, 0.9, 0.7, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.9, 0.8, 0.8, 0.9, 0.8, 0.9]`
+ms, with a 0.9 ms median and 0.7/0.9 ms range. It reproduces the release result's
+overlapping range and does not change the no-regression conclusion.
+
 ## 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.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).
+**Latest release: 0.12.0 - Project route shell and runtime parameters.** Directly addressable project and issue routes now reuse bracket file routes, pathname parameters, complete fallback HTML, generated host rewrites, and native anchors without an SPA router. Read the [release notes](./RELEASES.md#0120---project-route-shell-and-runtime-parameters), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.12.0), 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,95 @@
 # Kudzu Releases
 
+## 0.12.0 - Project Route Shell And Runtime Parameters
+
+Kudzu 0.12.0 opens the routing and application-lifetime train with directly
+addressable project and issue routes.
+
+### Changed in 0.12.0
+
+- Added bracket project and nested issue pages using supported React Router
+  `useParams()` migration syntax.
+- Emitted complete fallback HTML and pathname parameter ESM for both routes.
+- Preserved native project-to-issue links without an SPA route registry.
+- Emitted ordered host rewrite records while retaining exact-file precedence.
+- Updated `create-kudzu@0.1.113` to generate projects on
+  `@kudzujs/core@^0.12.0`.
+
+### Output Evidence
+
+- The application emits 36 files, 105,577 raw / 38,067 aggregate gzip bytes,
+  and deploy digest
+  `6a6c5985cf2a7e9649b0bbd70506357051dac995a74225b0022c5f1ecedaf2b8`.
+- The standalone project route uses 17,905 raw / 8,455 aggregate gzip
+  JavaScript bytes; the issue route uses 18,002 raw / 8,474 aggregate gzip.
+- The maintained enhanced session remains byte-identical at 58,970 raw /
+  22,124 aggregate gzip bytes, and `/help` remains 0 B JavaScript.
+- No semantic primitive, compiler pass, production compiler line, runtime
+  concept, server, or browser route registry was added.
+
+### Validation
+
+- Required Chrome proves direct project and issue entry plus issue reload.
+- The parameter module rejects invalid encoded path segments before mounting.
+- The full suite, package smoke, registry metadata, and fresh installation are
+  release gates.
+
+### Limits
+
+The deployment host must install the generated runtime rewrites. Exact emitted
+files must be checked before those fallbacks.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.12.0
+```
+
+## 0.11.4 - Pagination, Refresh, And Polling Policy
+
+Kudzu 0.11.4 completes the `0.11.x` server-data train with bounded URL-owned
+pagination and application-owned refresh policy.
+
+### Changed in 0.11.4
+
+- Synchronized project page/filter values with URL query signals and browser
+  back navigation.
+- Proved explicit refresh and exact list request counts without a query cache.
+- Added optional visibility-aware polling with interval/listener cleanup.
+- Bounded every server response to two retained rows.
+- Updated `create-kudzu@0.1.112` to generate projects on
+  `@kudzujs/core@^0.11.4`.
+
+### Output Evidence
+
+- The application emits 20 files, 77,263 raw / 26,156 aggregate gzip bytes, and
+  deploy digest
+  `a3864a5155d658e86378fce80de94e082ef0894c5db5f5793d91b4de7f359b46`.
+- The list/detail session uses 16 JavaScript files totaling 58,970 raw / 22,124
+  aggregate gzip bytes; `/help` remains 0 B JavaScript.
+- Twenty-one fresh Chrome profiles record a 1.3 ms navigation median and
+  1.2/1.6 ms range.
+- No semantic primitive, compiler pass, production compiler line, runtime
+  concept, cache, retained result store, or scheduler was added.
+
+### Validation
+
+- Required Chrome proves query push/back, bounded results, exact requests,
+  refresh, hidden polling suppression, visible refresh, and cleanup.
+- The full suite, package smoke, registry metadata, and fresh installation are
+  release gates.
+
+### Limits
+
+Polling remains authored route policy. Kudzu does not ship a universal
+scheduler, request registry, invalidation graph, or retained query cache.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.11.4
+```
+
 ## 0.11.3 - Optimistic Mutation And Rollback
 
 Kudzu 0.11.3 proves optimistic server mutation with ordinary shared state and

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

@@ -453,6 +453,13 @@ 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.
 
+Clean-worktree `npm run check`, 273/273 required-Chrome tests, and packed-package
+smoke passed on 2026-08-22. Release commit `ba6f97a`, tag `v0.11.3`, CI
+`32576861865`, the GitHub release, `@kudzujs/core@0.11.3`,
+`create-kudzu@0.1.111`, registry metadata, and a fresh registry-backed scaffold
+install/check passed. Publish workflow `32577090955` completed every version,
+package, publication, and registry gate.
+
 ### `0.11.4`: Pagination, Refresh, And Polling Policy
 
 - **Purpose:** complete bounded server-data loading before infinite data work.
@@ -465,6 +472,34 @@ over `0.11.2`. Twenty-one fresh Chrome profiles record a 0.8 ms median with a
 - **Done condition:** the exact owner and network behavior are measured and
   documented.
 
+**Completion evidence:** the project list reads page and filter from two
+existing React Router query signals and restarts its existing abortable fetch
+effect when either changes. Static updater handlers push page 2/all and page
+1/active URLs. Two browser back operations restore the prior URL, signal values,
+and bounded server results. An explicit refresh increments the same route-owned
+request signal. Optional polling owns one native interval and one
+`visibilitychange` listener; hidden events perform no work, one visible event
+performs one refresh, and disabling polling clears both owners before a later
+event. The deterministic journey records 11 total list requests across initial
+stale replacement, HTTP recovery, page/filter history, refresh, polling, and
+route remount. Every response retains at most two rows.
+
+Existing query signals, primitive state, dependency effects, abort invalidation,
+native timers/listeners, and route cleanup are sufficient. This packet adds zero
+semantic primitives, ModuleIR kinds, compiler passes, production compiler lines,
+runtime concepts, normalization rules, adapter rules, public APIs, caches,
+schedulers, or retained result stores. One positive application fixture gains
+page/filter URL ownership, history, refresh, visibility-aware polling, exact
+cleanup, request counts, and bounded-result cases. It emits 20 files totaling
+77,263 raw / 26,156 aggregate gzip bytes with deploy SHA-256
+`a3864a5155d658e86378fce80de94e082ef0894c5db5f5793d91b4de7f359b46`.
+The two-route session uses 16 JavaScript files totaling 58,970 raw / 22,124
+aggregate gzip bytes, an authored application increase of 2,652 raw / 913 gzip
+bytes over `0.11.3`. Twenty-one fresh Chrome profiles record a 1.3 ms median
+with a 1.2/1.6 ms range. The prior range does not overlap, so the 0.5 ms median
+increase is disclosed rather than presented as a no-regression result. `/help`
+remains 0 B JavaScript.
+
 ## `0.12.x`: Routing And Application Lifetime
 
 ### `0.12.0`: Project Route Shell And Runtime Parameters
@@ -477,6 +512,40 @@ over `0.11.2`. Twenty-one fresh Chrome profiles record a 0.8 ms median with a
 - **Stop condition:** an SPA route registry is introduced.
 - **Done condition:** all target routes are addressable without a browser router.
 
+**Completion evidence:** the maintained project application adds one bracket
+project page and one nested bracket issue page, both using the existing aliased
+React Router `useParams()` migration path and the existing shared application
+layout. Each fallback emits complete document structure plus only pathname
+parameter, binding, native-handler, and owned-layout capability ESM. The project
+page owns a native parameterized anchor to its first issue. The issue page owns a
+native parameterized project return. Neither standalone artifact includes the
+enhanced-navigation entry.
+
+The fixture emits the compiler-provided ordered rewrite records through its
+existing `afterBuild` host boundary. A deterministic static server checks exact
+files first, then applies those records for direct project and issue entry.
+Required Chrome proves project entry,
+issue entry, and issue reload; the generated parameter module rejects an encoded
+slash before mounting. Static HTML and artifact assertions prove the project to
+issue anchor remains native, both routes share one signature-keyed standalone
+runtime family, and `/help` remains 0 B JavaScript. Deployment still must install
+the generated rewrites; Kudzu does not add a server or browser route registry.
+
+Existing file routes, runtime pathname parameters, layout ownership, route
+bindings, native anchors, host rewrites, and browser reload are sufficient. This
+packet adds zero semantic primitives, ModuleIR kinds, compiler passes,
+production compiler lines, runtime concepts, normalization rules, adapter rules,
+or public APIs. One positive application fixture gains two route files, direct
+entry, reload, invalid-parameter rejection, native project-to-issue linkage, and
+host fallback cases. It emits 36 files totaling 105,577 raw / 38,067 aggregate
+gzip bytes with deploy SHA-256
+`6a6c5985cf2a7e9649b0bbd70506357051dac995a74225b0022c5f1ecedaf2b8`.
+The runtime project route uses 17,905 raw / 8,455 gzip JavaScript bytes and the
+issue route uses 18,002 raw / 8,474 gzip bytes. The existing two-route enhanced
+session remains byte-identical at 58,970 raw / 22,124 gzip bytes. Twenty-one
+fresh Chrome profiles record a 1.3 ms median with a 1.1/1.6 ms range; the range
+overlaps `0.11.4`, so no latency change is claimed.
+
 ### `0.12.1`: Shared Layout, History, Focus, And Scroll
 
 - **Purpose:** complete the accepted same-document application group behavior.
@@ -1053,5 +1122,7 @@ release transaction where possible or document and publish a forward-fix patch.
 | `0.11.0` | Released | Preserve the published owned-fetch lifecycle and zero-query-runtime exclusion. | None |
 | `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 |
+| `0.11.3` | Released | Preserve the published optimistic rollback, duplicate prevention, navigation, and retry evidence. | None |
+| `0.11.4` | Released | Preserve the published bounded pagination, history, refresh, polling cleanup, and exact request-count evidence. | None |
+| `0.12.0` | Active | Release the completed runtime project/issue route-shell evidence. | None |
+| `0.12.1` onward | Blocked | Wait for explicit approval after the minor-version entry release. | User-directed minor-version 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.111` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.11.3`.
+`create-kudzu@0.1.113` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.12.0`.
 
 ## Release Boundary
 

package/package.json

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