@kudzujs/core 0.10.0 → 0.10.1

package/PERFORMANCE.md

@@ -1,11 +1,32 @@
 # 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-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.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.1 - Application state scale.** The tracked project application now proves primitive, object, array, derived, conditional, and nested keyed state ownership with measured commit scaling and a zero-JavaScript static control. Read the [release notes](./RELEASES.md#0101---application-state-scale), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.10.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,54 @@
 # Kudzu Releases
 
+## 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,29 @@ 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.
+
 ### `0.10.2`: Shared Layout And Cross-Route State
 
 - **Purpose:** keep workspace/session state across an explicit application
@@ -833,6 +856,6 @@ 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.0` | Released | Preserve the published application baseline and release evidence. | None |
+| `0.10.1` | Active | Run the full release gate and publish the accepted state-scale evidence. | None |
 | `0.10.2` 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.105` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.10.1`.
 
 ## Release Boundary
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kudzujs/core",
-  "version": "0.10.0",
+  "version": "0.10.1",
   "description": "HTML-first TSX framework with synchronous state semantics and no virtual DOM",
   "type": "module",
   "license": "MIT",
@@ -60,6 +60,7 @@
     "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-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",