@kudzujs/core 0.10.0 → 0.10.2

package/PERFORMANCE.md

@@ -1,11 +1,50 @@
 # Performance Records
 
-Reproducibility classes: `npm run benchmark`, `npm run benchmark:keyed`, `npm run benchmark:native`, `npm run benchmark:module-cache`, and `npm run benchmark:source-scale` are maintained in this repository; `npm run benchmark:commerce` is a maintained paired runner over the public external storefront; older excluded-workspace sections are historical provenance only and are not current framework rankings.
+Reproducibility classes: `npm run benchmark`, `npm run benchmark:keyed`, `npm run benchmark:native`, `npm run benchmark:module-cache`, `npm run benchmark:project-navigation`, `npm run benchmark:project-state`, and `npm run benchmark:source-scale` are maintained in this repository; `npm run benchmark:commerce` is a maintained paired runner over the public external storefront; older excluded-workspace sections are historical provenance only and are not current framework rankings.
 
 `npm run benchmark:source-scale` generates its fixture outside the repository so 50,000 lines of synthetic source are not tracked. The default topology is 50 pages plus 450 route-owned imported modules. Generation is excluded from timing; fresh-process samples separately report source reads, reachable-graph discovery, source compilation, clean production build, compiler-result and deploy digests, output files/bytes, cache counters, and peak RSS. `ROUTES`, `MODULES_PER_ROUTE`, `FILLER_LINES`, `WARMUPS`, and `RUNS` may reduce or expand the fixture without changing the default acceptance floor. `TARGET_ROOT` measures another checkout; `BASELINE_ROOT` alternates that checkout with the current tree and requires identical deploy output.
 
 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.10.2 Project Shared-Layout Navigation
+
+Measured 2026-08-22 on macOS arm64 with Node 25.6.1 and Chrome
+151.0.7922.172. `npm run benchmark:project-navigation` builds the tracked
+project application, updates the layout-owned workspace state, and measures
+list-to-detail completion across seven fresh Chrome profiles. Every accepted
+sample verifies retained layout identity and the shared workspace value before
+reporting timing.
+
+The two-route session uses 10 unique JavaScript files totaling 46,418 raw /
+17,045 aggregate gzip bytes. Navigation samples are
+`[2.3, 6.5, 1.4, 1.3, 5.1, 1.3, 4.0]` ms, with a 2.3 ms median and 1.3/6.5 ms
+minimum/maximum. Both routes use the existing shared runtime family;
+`workspace` has layout lifetime while summary, collection, filter, conditional,
+saved-filter, row, and detail-draft states retain route lifetime. No compiler or
+browser runtime source changed, so no revision-to-revision performance claim is
+made.
+
+## 0.10.1 Project State Scale
+
+Measured 2026-08-22 on macOS arm64 with Node 25.6.1 and Chrome
+151.0.7922.172. `npm run benchmark:project-state` generates 1/8/32-state pages,
+requires a clean `v0.10.0` checkout through `BASELINE_ROOT`, and verifies that
+baseline and candidate deploy output is byte-identical before timing seven fresh
+headless Chrome processes per scale. The shared deploy contains 10 files,
+18,780 bytes, and digest
+`3f83712254d95f1cf59c5034f363ea906406efa1bd9539f3bb8b9a0d54a3fdc5`.
+
+| States / derived dependency edges | JavaScript raw / gzip | Commit runs (ms) | Median |
+|---:|---:|---|---:|
+| 1 / 0 | 768 / 441 B | 0.4, 0.4, 0.4, 0.5, 0.6, 0.6, 0.6 | 0.5 ms |
+| 8 / 8 | 10,935 / 4,789 B | 0.6, 0.7, 0.6, 0.6, 0.7, 0.6, 0.6 | 0.6 ms |
+| 32 / 32 | 11,341 / 4,841 B | 0.8, 0.8, 1.0, 0.9, 0.8, 1.0, 1.0 | 0.9 ms |
+
+The 1-state command-only page needs only the existing command runtime. The
+larger pages reuse the existing binding, serialization, style, and command
+runtime modules. No normalized-state runtime, new runtime family, or generic
+rerender path is added.
+
 ## 0.9 Shared State And Actions
 
 Measured 2026-08-19 on Linux x64 with Node 24.14.0 and Chrome 142.0.7444.175. Baseline `abe87ceafbf70ed8eb2618976e2d1e18c378126f` and the candidate built identical final Context/Zustand cart source.

package/README.md

@@ -14,7 +14,7 @@ Kudzu compiles ordinary React-shaped TypeScript and TSX into complete static HTM
 
 > Experimental `0.10.x`: the compiler API and supported TSX surface may change.
 
-**Latest release: 0.10.0 - Application capability baseline.** A tracked greenfield project application now fixes the state, browser, output, and static zero-JavaScript contract used by the capability release train. Read the [release notes](./RELEASES.md#0100---application-capability-baseline), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.10.0), or follow the [architecture packet](./docs/next-architecture/README.md).
+**Latest release: 0.10.2 - Shared-layout navigation.** The tracked project application now preserves workspace state across explicit list/detail navigation while route drafts reset, direct loads start fresh, and static routes remain outside the runtime group. Read the [release notes](./RELEASES.md#0102---shared-layout-navigation), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.10.2), 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,104 @@
 # Kudzu Releases
 
+## 0.10.2 - Shared-layout navigation
+
+Kudzu 0.10.2 extends the tracked project-management application with explicit
+list/detail navigation, layout-owned workspace state, and route-owned drafts
+using the existing navigation and shared-state semantics.
+
+### Changed in 0.10.2
+
+- Added one Context-backed application layout that lowers through existing
+  `SharedStateIR` and persists workspace selection across list/detail routes.
+- Added an exact Alpha detail route whose draft state releases on navigation and
+  initializes fresh on revisit and direct document load.
+- Added a maintained seven-profile list-to-detail navigation benchmark with
+  session JavaScript and lifetime metadata.
+- Kept `/help` and `/login` outside the navigation group; `/help` remains a
+  complete zero-JavaScript native-navigation target.
+- Updated `create-kudzu@0.1.106` to generate projects on
+  `@kudzujs/core@^0.10.2`.
+
+### Output Evidence
+
+- The application fixture emits 14 files, 57,293 raw / 19,985 aggregate gzip
+  bytes, and deploy digest
+  `1c867ee7119f7eb23b935c4506c2a46639acb75c13f0916b29c255421b0d123d`.
+- The list/detail session uses 10 unique JavaScript files totaling 46,418 raw /
+  17,045 aggregate gzip bytes; `/help` remains 0 B JavaScript.
+- Seven fresh Chrome profiles record list-to-detail completion at a 2.3 ms
+  median, with 1.3/6.5 ms minimum/maximum.
+- No semantic primitive, compiler pass, production compiler line, runtime
+  concept, store, or SPA router was added.
+
+### Validation
+
+- Required Chrome proves layout identity and workspace persistence in both
+  directions, route DOM release, fresh draft state, and direct-load reset.
+- The full suite, required-Chrome application journey, package smoke, registry
+  metadata, and fresh installation are release gates.
+
+### Limits
+
+Navigation remains explicit and group-scoped with complete-document fallback.
+This release does not add a universal SPA router, persistence, authentication,
+server data, or cross-group shared state.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.10.2
+```
+
+## 0.10.1 - Application state scale
+
+Kudzu 0.10.1 extends the tracked project-management journey across ordinary
+primitive, object, array, derived, conditional, nested keyed, and row-local
+state while retaining static-first output and existing browser capabilities.
+
+### Changed in 0.10.1
+
+- Added deterministic workspace summary replacement, project filtering, saved
+  filters, nested issue updates, conditional summary ownership, and keyed row
+  state release/remount to the greenfield application contract.
+- Added a maintained 1/8/32-state Chrome commit benchmark with exact `v0.10.0`
+  deploy comparison and runtime metadata.
+- Kept direct object-field nested-list replacement outside the accepted boundary
+  after the isolated experiment failed browser replacement.
+- Updated `create-kudzu@0.1.105` to generate projects on
+  `@kudzujs/core@^0.10.1`.
+
+### Output Evidence
+
+- The application fixture emits 12 files, 47,546 raw / 16,285 aggregate gzip
+  bytes, and deploy digest
+  `d50c9ff6dccba338559dd9e9141c4607ec62da30385658e617a86f7af3f52e0f`.
+- `/app/projects` emits 39,178 raw / 14,143 aggregate gzip JavaScript bytes;
+  `/help` remains 0 B JavaScript.
+- The generated scale deploy is byte-identical to `v0.10.0`; 1/8/32-state
+  commit medians are 0.5/0.6/0.9 ms across seven fresh Chrome processes.
+- No semantic primitive, compiler pass, browser runtime concept, normalized
+  state, or generic rerender path was added.
+
+### Validation
+
+- Required Chrome verifies derived updates, nested keyed identity, conditional
+  release/remount, keyed row state reset, and zero unrelated DOM mutations.
+- `npm run check`, the complete test suite, required-Chrome application test,
+  package smoke, registry metadata, and fresh installation are release gates.
+
+### Limits
+
+This release does not support direct object-field nested-list replacement,
+arbitrary object mutation, normalized state, shared layout state, persistence,
+authentication, or server data.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.10.1
+```
+
 ## 0.10.0 - Application capability baseline
 
 Kudzu 0.10.0 begins the application capability release train with a durable

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

@@ -163,6 +163,32 @@ is made because compiler and runtime sources are unchanged.
 - **Done condition:** the recorded scale remains within the material regression
   threshold and nearby unsupported dynamic paths fail at authored locations.
 
+**Completion evidence:** the project journey composes five ordinary route
+states: one object, two arrays, and two primitives. Six existing reactive
+bindings, one conditional owner, three keyed lists, one nested issue list, and
+one keyed row-local state cover summary replacement, filtering, derived issue
+counts, saved-filter append, conditional release/remount, keyed identity, and
+row-state release/reset. An unrelated control records zero DOM mutations. The
+route adds no semantic primitive, pass, browser runtime concept, normalized
+state, or generic rerender path; the only supported source adjustment is the
+application's use of a separate project array state at the existing keyed-list
+boundary. Direct object-field nested-list replacement remains outside this
+packet after its isolated experiment failed browser replacement, while the
+existing dynamic object-property diagnostic remains source-located.
+
+The application deploy contains 12 files, 47,546 raw / 16,285 aggregate gzip
+bytes, with SHA-256
+`d50c9ff6dccba338559dd9e9141c4607ec62da30385658e617a86f7af3f52e0f`.
+`/app/projects` uses 39,178 raw / 14,143 aggregate gzip JavaScript bytes;
+`/help` remains 0 B. The generated 1/8/32-state scale benchmark emits identical
+deploy output under `v0.10.0` and the candidate. Seven fresh Chrome processes
+record commit medians of 0.5/0.6/0.9 ms as the derived binding dependency edges
+increase from 0 to 8 to 32. Runtime JavaScript is 768/10,935/11,341 raw bytes
+and 441/4,789/4,841 aggregate gzip bytes. No material regression is present.
+Release commit `f04041b`, tag `v0.10.1`, both CI jobs, the GitHub release,
+`@kudzujs/core@0.10.1`, `create-kudzu@0.1.105`, registry metadata, and a fresh
+scaffold install/check are verified.
+
 ### `0.10.2`: Shared Layout And Cross-Route State
 
 - **Purpose:** keep workspace/session state across an explicit application
@@ -177,6 +203,27 @@ is made because compiler and runtime sources are unchanged.
 - **Done condition:** state lifetime and disposal are exact in browser tests and
   static routes receive no shared-state runtime.
 
+**Completion evidence:** the greenfield application adds one exact Alpha detail
+route and one explicit navigation group around list/detail routes. A relative
+Context hook lowers through the existing `SharedStateIR`: both routes own the
+same `workspace` layout state while list state and the detail `draft` remain
+route-owned. Required Chrome proves retained layout DOM identity, workspace
+persistence in both directions, detail DOM release, fresh draft state on
+re-entry, and initial layout/draft values in a fresh document. `/help` remains
+outside the group, retains its native anchor path, and emits complete HTML with
+0 B JavaScript.
+
+This packet adds no semantic primitive, ModuleIR kind, compiler pass, production
+compiler LOC, runtime concept, normalization rule, adapter rule, store, or SPA
+router. It adds one application layout/context module, one route, one config,
+and one positive browser journey; existing navigation-group diagnostics retain
+the nearby rejected configuration boundary. The fixture emits 14 files, 57,293
+raw / 19,985 aggregate gzip bytes, with deploy SHA-256
+`1c867ee7119f7eb23b935c4506c2a46639acb75c13f0916b29c255421b0d123d`.
+The list/detail session uses 10 unique JavaScript files totaling 46,418 raw /
+17,045 aggregate gzip bytes. Seven fresh Chrome profiles record list-to-detail
+completion at `[2.3, 6.5, 1.4, 1.3, 5.1, 1.3, 4.0]` ms, median 2.3 ms.
+
 ### `0.10.3`: Persistence Recipe And State Release
 
 - **Purpose:** prove URL, storage, and server-backed persistence without adding a
@@ -833,6 +880,7 @@ release transaction where possible or document and publish a forward-fix patch.
 
 | Patch | Status | Next exact action | Blocker |
 |---|---|---|---|
-| `0.10.0` | Release candidate | Complete commit, push, tag, GitHub release, npm publication, registry, and fresh-install verification. | Release transaction |
-| `0.10.1` | Blocked | Extend the greenfield fixture with local, object, array, and derived state scale evidence after 0.10.0 publication. | 0.10.0 release |
-| `0.10.2` onward | Blocked | Wait for the preceding patch acceptance and release record. | Ordered dependency |
+| `0.10.0` | Released | Preserve the published application baseline and release evidence. | None |
+| `0.10.1` | Released | Preserve the published state-scale evidence and explicit object-field limit. | None |
+| `0.10.2` | Active | Add the shared workspace and route-owned draft journey to the greenfield application. | None |
+| `0.10.3` 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.104` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.10.0`.
+`create-kudzu@0.1.106` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.10.2`.
 
 ## Release Boundary
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kudzujs/core",
-  "version": "0.10.0",
+  "version": "0.10.2",
   "description": "HTML-first TSX framework with synchronous state semantics and no virtual DOM",
   "type": "module",
   "license": "MIT",
@@ -60,6 +60,8 @@
     "benchmark:commerce": "node test/commerce-build-performance.mjs",
     "benchmark:module-cache": "node test/module-cache-performance.mjs",
     "benchmark:native": "node test/native-performance.mjs",
+    "benchmark:project-navigation": "node test/project-navigation-performance.mjs",
+    "benchmark:project-state": "node test/project-state-performance.mjs",
     "benchmark:source-scale": "node test/source-scale-performance.mjs",
     "prepublishOnly": "npm run check && npm test",
     "deploy": "wrangler deploy",