@kudzujs/core 0.11.4 → 0.12.1

package/PERFORMANCE.md

@@ -6,6 +6,47 @@ 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.1 Shared Layout, History, Focus, And Scroll
+
+Measured 2026-08-23 on macOS arm64 with Node 25.6.1 and Chrome
+151.0.7922.172. `RUNS=7 npm run benchmark:project-navigation` uses fresh Chrome
+profiles after the required browser journey proves hash and non-hash focus,
+explicit hash/top scroll, title/live announcements, back/forward, retained
+layout state, fresh route state, and native navigation outside the route group.
+
+The two-route session uses 16 JavaScript files totaling 58,974 raw / 22,129
+aggregate gzip bytes, an increase of 4 raw / 5 gzip bytes from `0.12.0` for the
+correct non-hash focus fallback. Navigation samples are
+`[1.5, 1.4, 1.3, 1.3, 1.3, 1.3, 1.4]` ms, with a 1.3 ms median and 1.3/1.5 ms
+minimum/maximum. The range overlaps `0.12.0`, so no latency change is claimed.
+
+The application emits 36 files totaling 106,096 raw / 38,201 aggregate gzip
+bytes with deploy SHA-256
+`4f1ce541af0794fcb17458ad37db7b32beb434f3a83cb7f949f13b3e4536fe1c`.
+Core semantic LOC remains 5,682 with no pass, primitive, or runtime-concept
+change. `/help` remains 0 B JavaScript. No AI-delivery cost comparison applies
+to this browser correctness patch.
+
+## 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

package/README.md

@@ -12,9 +12,9 @@ Kudzu compiles ordinary React-shaped TypeScript and TSX into complete static HTM
 
 *Watch: React-shaped TSX to static HTML and route-specific ESM in 22 seconds.*
 
-> Experimental `0.11.x`: the compiler API and supported TSX surface may change.
+> Experimental `0.12.x`: the compiler API and supported TSX surface may change.
 
-**Latest release: 0.11.4 - Pagination, refresh, and polling policy.** URL-owned page/filter state, exact refresh, bounded results, back/forward, and visibility-aware polling now compose from existing query signals and owned effects without a scheduler or cache. Read the [release notes](./RELEASES.md#0114---pagination-refresh-and-polling-policy), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.11.4), or follow the [architecture packet](./docs/next-architecture/README.md).
+**Latest release: 0.12.1 - Shared layout, history, focus, and scroll.** Enhanced route groups now prove retained layout state, route cleanup, back/forward history, titles, live announcements, hash and heading focus, explicit scroll policy, and native navigation outside the group. Read the [release notes](./RELEASES.md#0121---shared-layout-history-focus-and-scroll), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.12.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,100 @@
 # Kudzu Releases
 
+## 0.12.1 - Shared Layout, History, Focus, And Scroll
+
+Kudzu 0.12.1 completes the accepted same-document project route group with
+explicit history, focus, announcement, and scroll behavior.
+
+### Changed in 0.12.1
+
+- Fixed non-hash enhanced navigation so the existing heading/main focus
+  fallback runs instead of treating an empty hash as a target.
+- Proved push, back, and forward navigation with retained layout state and
+  freshly recreated route state.
+- Added route titles, a native hash anchor, and an intrinsic hash destination to
+  the maintained project application.
+- Proved polite navigation announcements, hash scrolling, top scrolling, and
+  browser-native links outside the configured route group.
+- Updated `create-kudzu@0.1.114` to generate projects on
+  `@kudzujs/core@^0.12.1`.
+
+### Output Evidence
+
+- The application emits 36 files, 106,096 raw / 38,201 aggregate gzip bytes,
+  and deploy digest
+  `4f1ce541af0794fcb17458ad37db7b32beb434f3a83cb7f949f13b3e4536fe1c`.
+- The maintained enhanced session uses 16 JavaScript files totaling 58,974 raw
+  / 22,129 aggregate gzip bytes, 4 raw / 5 gzip bytes above `0.12.0`.
+- `/help` remains complete HTML with 0 B JavaScript.
+- No semantic primitive, compiler pass, core compiler line, runtime concept,
+  public API, or browser route registry was added.
+
+### Validation
+
+- Required Chrome proves focused anchor activation, back/forward, layout
+  retention, route cleanup/reset, title/live updates, hash/heading focus, and
+  hash/top scroll behavior.
+- Seven fresh Chrome profiles record a 1.3 ms navigation median with a 1.3-1.5
+  ms range. The range overlaps `0.12.0`, so no latency change is claimed.
+- The full suite, package smoke, registry metadata, and fresh installation are
+  release gates.
+
+### Limits
+
+Enhanced navigation remains explicit and route-group scoped. Routes outside the
+group use browser-native document navigation.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.12.1
+```
+
+## 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

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

@@ -512,6 +512,40 @@ remains 0 B JavaScript.
 - **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.
@@ -523,6 +557,31 @@ remains 0 B JavaScript.
 - **Done condition:** keyboard and browser-history journeys pass with native
   recovery.
 
+**Completion evidence:** the project application adds route titles, one native
+hash anchor, and one intrinsic hash destination. Required Chrome activates the
+focused anchor, retains the layout and workspace state through push, back, and
+forward navigation, releases and recreates dirty route state, updates the title
+and polite live status, focuses hash and heading destinations, applies explicit
+hash and top scroll policies, and leaves `/help` browser-native outside the
+approved route group.
+
+The journey exposed one existing JavaScript value bug: an absent hash produced
+the empty string and prevented the nullish heading/main focus fallback. The
+navigation runtime now produces `null` for that case. This packet adds zero
+semantic primitives, ModuleIR kinds, compiler passes, core compiler lines,
+runtime concepts, normalization rules, adapter rules, or public APIs. Runtime
+source remains 351 lines. One positive application fixture gains the complete
+acceptance journey; `/help` remains 0 B JavaScript.
+
+The fixture emits 36 files totaling 106,096 raw / 38,201 aggregate gzip bytes
+with deploy SHA-256
+`4f1ce541af0794fcb17458ad37db7b32beb434f3a83cb7f949f13b3e4536fe1c`.
+The two-route session uses 16 JavaScript files totaling 58,974 raw / 22,129
+aggregate gzip bytes, 4 raw / 5 gzip bytes above `0.12.0`. Seven fresh Chrome
+profiles record a 1.3 ms navigation median with a 1.3/1.5 ms range. The range
+overlaps `0.12.0`, so no latency change is claimed. This correctness packet has
+no measured AI-delivery cost effect.
+
 ### `0.12.2`: Authentication And Permission Boundary
 
 - **Purpose:** complete login, restore, 401, logout, and permission-aware UI.
@@ -1089,5 +1148,7 @@ release transaction where possible or document and publish a forward-fix patch.
 | `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` | Released | Preserve the published optimistic rollback, duplicate prevention, navigation, and retry evidence. | None |
-| `0.11.4` | Active | Prove bounded page/filter synchronization, history, refresh, optional polling cleanup, and exact request behavior. | None |
-| `0.12.0` onward | Blocked | Wait for explicit approval after the patch-only release sequence. | User-directed minor-version boundary |
+| `0.11.4` | Released | Preserve the published bounded pagination, history, refresh, polling cleanup, and exact request-count evidence. | None |
+| `0.12.0` | Released | Preserve direct runtime entry, reload, rewrite, and native fallback evidence. | None |
+| `0.12.1` | Active | Release the completed layout/history/focus/scroll evidence. | None |
+| `0.12.2` onward | Blocked | Complete the `0.12.1` 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.112` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.11.4`.
+`create-kudzu@0.1.114` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.12.1`.
 
 ## Release Boundary
 

package/framework/navigation-runtime.js

@@ -330,7 +330,7 @@ function updateHead(incoming) {
 }
 
 function focusAndScroll(url) {
-  const hashTarget = url.hash && document.getElementById(decodeURIComponent(url.hash.slice(1)))
+  const hashTarget = url.hash ? document.getElementById(decodeURIComponent(url.hash.slice(1))) : null
   const target = hashTarget ?? routeElement("h1") ?? routeElement("main")
   if (target) {
     if (!target.hasAttribute("tabindex")) target.setAttribute("tabindex", "-1")

package/package.json

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