@kudzujs/core 0.16.13 → 0.16.14

package/MIGRATION_ROADMAP.md

@@ -57,7 +57,7 @@ Syntax compatibility does not mean reproducing React wholesale. Kudzu accepts th
 - stronger JavaScript failure resilience;
 - no remaining material large-route build-scaling weakness.
 
-The completed 0.9 plan defines the cross-framework comparison and release gate. The active application packet is `0.20.3` in the capability release plan below. Benchmark-only feature omission, unmatched accessibility, weighted scores that hide losses, and unrecorded environment differences do not count as proof.
+The completed 0.9 plan defines the cross-framework comparison and release gate. The active application packet is `0.20.5` in the capability release plan below. Benchmark-only feature omission, unmatched accessibility, weighted scores that hide losses, and unrecorded environment differences do not count as proof.
 
 ### 0.10.0 Through 0.21.x: Application Capability Release Train
 

package/PERFORMANCE.md

@@ -1,6 +1,20 @@
 # Performance Records
 
-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.
+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`, `npm run benchmark:source-scale`, and `npm run benchmark:ai-delivery` 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.
+
+## 0.16.14 Fair AI Delivery Evidence
+
+Measured 2026-09-01 on Linux x64 with Node 24.14.0. The deterministic protocol
+fixture records two interleaved attempts per variant, including one success and
+one retained failure each. Both variants therefore report a 50% fixture success
+rate, 50 nanos median successful cost, and 100 nanos total cost per success when
+failed attempts remain in the numerator. Successful artifacts are one 63 raw /
+66 gzip B HTML file with digest
+`0d22f579d793d0034c967c7ffa08e0b2c377bc36c959c7b4bafab587fd5dda60`.
+This validates evidence accounting only and is not a model-driven framework
+comparison. Compiler passes, runtime concepts, representative deploy output, and
+browser bytes are unchanged. Browser-disabled and required-Chrome suites pass
+297/297 tests, package smoke passes, and the runner adds no dependency.
 
 ## 0.16.13 Route Artifact Explanations
 

package/README.md

@@ -14,7 +14,7 @@ Kudzu compiles ordinary React-shaped TypeScript and TSX into complete static HTM
 
 > Experimental `0.16.x`: the compiler API and supported TSX surface may change.
 
-**Latest release: 0.16.13 - Route artifact explanations.** `kudzu explain --route <route> --json` now traces one exact emitted route from authored source and semantic ownership through its capability family and selected runtime, handler, chunk, style, and Worker bytes without exposing raw IR. Read the [release notes](./RELEASES.md#01613---route-artifact-explanations), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.16.13), or follow the [architecture packet](./docs/next-architecture/README.md).
+**Latest release: 0.16.14 - Fair AI delivery evidence.** The repository-owned AI delivery runner now pins equal Kudzu and React+Vite conditions, preserves successful and failed attempts, and records attribution, cost, source retention, acceptance, and browser artifacts without claiming a framework winner. Read the [release notes](./RELEASES.md#01614---fair-ai-delivery-evidence), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.16.14), 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,36 @@
 # Kudzu Releases
 
+## 0.16.14 - Fair AI Delivery Evidence
+
+Kudzu 0.16.14 adds a repository-owned protocol and runner for equal-condition,
+fully retained Kudzu and React+Vite delivery attempts.
+
+### Changed in 0.16.14
+
+- Adds `npm run benchmark:ai-delivery`, backed only by Node standard-library
+  process, hash, filesystem, timing, and compression APIs.
+- Pins model revision, pricing, tool permissions, prompt, budgets, adapter,
+  acceptance command, starter trees, public context, and paired attempt order.
+- Runs every attempt in an isolated starter copy, then independently reruns the
+  declared build and framework-neutral acceptance command.
+- Preserves raw adapter/build/acceptance output, final authored source, browser
+  artifacts, hashes, token/cost/tool/file/build metrics, and source retention.
+- Includes deliberate failures in the evidence and total cost-per-success
+  numerator rather than cherry-picking successful attempts.
+- Adds no compiler pass, semantic primitive, runtime concept, application API,
+  dependency, or browser byte.
+- Uses a deterministic fixture only to validate the protocol. It does not claim
+  that Kudzu outperforms React+Vite; measured tooling-cost validation remains the
+  next packet.
+- Updates `create-kudzu@0.1.139` to generate projects on
+  `@kudzujs/core@^0.16.14`.
+
+### Upgrade
+
+```sh
+npm install @kudzujs/core@^0.16.14
+```
+
 ## 0.16.13 - Route Artifact Explanations
 
 Kudzu 0.16.13 lets tools ask why one exact emitted route owns its browser bytes

package/docs/next-architecture/README.md

@@ -15,7 +15,7 @@ The completed `0.9.0` milestone is recorded in [`0.9-semantic-compression.md`](.
 
 [`1.0-large-application-compatibility-audit.md`](./1.0-large-application-compatibility-audit.md) records the first post-0.9 probes against Memos, Apache Answer, and Actual Budget. The audit finds that reduced slices build but whole-application source retention and behavior parity do not yet pass.
 
-[`application-capability-release-plan.md`](./application-capability-release-plan.md) is the authoritative post-0.9 execution queue, currently at `0.20.3`. It assigns one application-capability section to each minor release and one independently accepted evidence packet to each patch release from `0.10.0` through the `1.0.0` gate. It supersedes the provisional 0.10/0.11/0.12 tool-first ordering in the completed 0.9 handoff without rewriting that historical record.
+[`application-capability-release-plan.md`](./application-capability-release-plan.md) is the authoritative post-0.9 execution queue, currently at `0.20.5`. It assigns one application-capability section to each minor release and one independently accepted evidence packet to each patch release from `0.10.0` through the `1.0.0` gate. It supersedes the provisional 0.10/0.11/0.12 tool-first ordering in the completed 0.9 handoff without rewriting that historical record.
 
 ## Required Invariants
 

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

@@ -1881,6 +1881,21 @@ HTML, generated code, captures, and state values.
 - **Stop condition:** canonical compiler source replaces ordinary authored TSX.
 - **Done condition:** each fix has one diagnostic code and explicit preconditions.
 
+Deferred by the evidence gate without production changes or a release. A complete
+repository inventory found no recorded model prompt, model/tool version, raw
+attempt, correction cycle, token/cost trace, or repeated source edit proving any
+automatic fix useful. Existing diagnostics offer migration guidance but do not
+identify a uniquely safe edit; replacing a non-null ref initializer would change
+authored behavior. The existing lazy-state-literal normalization could support a
+narrow exact-range rewrite while preserving comments and output bytes, but no AI
+trial records it as a correction or cost reduction. Adding check/preview/write
+infrastructure now would therefore be speculative and violate the packet purpose.
+Resume this packet only after `0.20.4` records a repeated correction with one
+stable diagnostic code, a unique semantics-preserving replacement, and
+compiler-proven preconditions. No fixture, analyzer, fix command, formatter,
+compiler pass, runtime concept, browser module, package version, or release was
+added.
+
 ### `0.20.4`: AI Delivery Protocol And Runner
 
 - **Purpose:** track fair Kudzu and React+Vite delivery attempts.
@@ -1891,6 +1906,20 @@ HTML, generated code, captures, and state values.
   comparator.
 - **Done condition:** every attempt is reproducible or fully attributable.
 
+Completed by `@kudzujs/core@0.16.14` and `create-kudzu@0.1.139`. The
+repository-owned Node standard-library runner pins the model revision, pricing,
+tools, prompt, budgets, adapter, acceptance command, starter digests, optional
+public context, and paired schedule before creating isolated workspaces. It
+retains raw adapter/build/acceptance streams, final source, browser artifacts,
+hashes, attribution, token/cost/tool/file/build metrics, source retention, and
+both successful and failed attempts. The deterministic two-attempt-per-variant
+fixture proves equal ordering, one retained failure per variant, independent
+final builds, framework-neutral acceptance, and failure-inclusive cost per
+success. It is protocol evidence only and makes no Kudzu versus React+Vite
+delivery claim. No dependency, compiler pass, semantic primitive, runtime
+concept, application API, or browser byte was added. Browser-disabled and
+required-Chrome suites pass 297/297 tests, and package smoke passes.
+
 ### `0.20.5`: Tooling Cost Validation
 
 - **Purpose:** prove that diagnostics/inspect/explain/fix lower total cost per
@@ -2091,3 +2120,5 @@ release transaction where possible or document and publish a forward-fix patch.
 | `0.20.0` | Released as `0.16.11` | Preserve stable diagnostic schema/codes, authored ranges, human errors, compatibility reuse, and zero browser/output delta. | Patch release retained the `0.16.x` public version line |
 | `0.20.1` | Released as `0.16.12` | Preserve bounded deterministic reachable inventory, first-blocker retention, existing-record reuse, and zero browser/output delta. | Patch release retained the `0.16.x` public version line |
 | `0.20.2` | Released as `0.16.13` | Preserve exact emitted-route lookup, authored provenance, semantic ownership, capability/artifact byte reasons and hashes, bounded deterministic output, structured missing-route diagnostics, and zero-JavaScript explanation. | Patch release retained the `0.16.x` public version line |
+| `0.20.3` | Deferred by evidence gate | Resume only after recorded AI trials prove one repeated correction safe and useful with a stable diagnostic code and compiler-proven preconditions. | No recorded AI trials; no production change or release consumed |
+| `0.20.4` | Released as `0.16.14` | Preserve pinned equal conditions, isolated paired attempts, raw failures, independent acceptance, attribution, failure-inclusive costs, source retention, and browser artifact evidence. | Deterministic fixture validates the protocol only; no framework ranking claimed |

package/docs/next-architecture/compiler-current-architecture.md

@@ -1,6 +1,6 @@
 # Current Compiler Architecture
 
-This maps the current `0.16.13` architecture, built on the completed `0.9.0` semantic-compression release and `0.8.23` Goal A compiler foundation. The active application packet is `0.20.3`; file and function names are the stable references, while line numbers are intentionally omitted because later work may still move code.
+This maps the current `0.16.14` architecture, built on the completed `0.9.0` semantic-compression release and `0.8.23` Goal A compiler foundation. The active application packet is `0.20.5`; file and function names are the stable references, while line numbers are intentionally omitted because later work may still move code.
 
 ## Responsibility Map
 

package/docs/next-architecture/large-application-ai-native-roadmap.md

@@ -2,9 +2,9 @@
 
 ## Status
 
-Completed compiler-foundation record and longer-term plan after `0.8.35`. The [`0.9-semantic-compression.md`](./0.9-semantic-compression.md) execution queue is complete. The active queue for current work is [`application-capability-release-plan.md`](./application-capability-release-plan.md) at packet `0.20.3`. This document does not mark any remaining planned capability as supported and does not authorize a React runtime, VDOM, hydration, retained browser component tree, generic rerenderer, public store/query/resource API, SPA router, or islands.
+Completed compiler-foundation record and longer-term plan after `0.8.35`. The [`0.9-semantic-compression.md`](./0.9-semantic-compression.md) execution queue is complete. The active queue for current work is [`application-capability-release-plan.md`](./application-capability-release-plan.md) at packet `0.20.5`. This document does not mark any remaining planned capability as supported and does not authorize a React runtime, VDOM, hydration, retained browser component tree, generic rerenderer, public store/query/resource API, SPA router, or islands.
 
-[`MIGRATION_ROADMAP.md`](../../MIGRATION_ROADMAP.md) remains the product authority for product invariants and fixture-driven feature selection. [`application-capability-release-plan.md`](./application-capability-release-plan.md) is authoritative for current work order and evidence at packet `0.20.3`; this plan retains the completed foundation, deferred program, and long-term production gates. If implementation evidence changes either boundary, update the relevant document before broadening a patch.
+[`MIGRATION_ROADMAP.md`](../../MIGRATION_ROADMAP.md) remains the product authority for product invariants and fixture-driven feature selection. [`application-capability-release-plan.md`](./application-capability-release-plan.md) is authoritative for current work order and evidence at packet `0.20.5`; this plan retains the completed foundation, deferred program, and long-term production gates. If implementation evidence changes either boundary, update the relevant document before broadening a patch.
 
 ## Product Outcome
 
@@ -483,4 +483,4 @@ The first comparison is Kudzu versus React + Vite using the same agent, model, t
 
 ## Immediate Decision
 
-All listed foundation and `0.9` slices are complete. Current work continues at `0.20.3` deterministic normalize and fix under the [`application-capability-release-plan.md`](./application-capability-release-plan.md); keep ResourceIR limited to qualifying independent fixtures, and do not add range ownership, virtualization, optimistic transactions, a public adapter/store API, or a router before evidence justifies them.
+All listed foundation and `0.9` slices are complete. Current work continues at `0.20.5` tooling cost validation under the [`application-capability-release-plan.md`](./application-capability-release-plan.md); keep ResourceIR limited to qualifying independent fixtures, and do not add range ownership, virtualization, optimistic transactions, a public adapter/store API, or a router before evidence justifies them.

package/docs/next-architecture/versioning.md

@@ -1,6 +1,6 @@
 # Planned Version Sequence
 
-This is an execution sequence, not release history. `0.8.16` through `0.8.62` are completed scopes represented by package/release records. The `0.10.0` through `1.0.0` minor/patch sequence is maintained in [`application-capability-release-plan.md`](./application-capability-release-plan.md), currently at `0.20.3`; that plan supersedes the provisional tool-first 0.10/0.11/0.12 ordering in the completed 0.9 handoff.
+This is an execution sequence, not release history. `0.8.16` through `0.8.62` are completed scopes represented by package/release records. The `0.10.0` through `1.0.0` minor/patch sequence is maintained in [`application-capability-release-plan.md`](./application-capability-release-plan.md), currently at `0.20.5`; that plan supersedes the provisional tool-first 0.10/0.11/0.12 ordering in the completed 0.9 handoff.
 
 Keep each patch behavior-preserving and independently reviewable. If a boundary proves inseparable, revise this plan before combining releases; do not silently broaden a patch.
 
@@ -66,7 +66,7 @@ Keep each patch behavior-preserving and independently reviewable. If a boundary
 
 ## Generator Versions
 
-`create-kudzu@0.1.138` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.16.13`.
+`create-kudzu@0.1.139` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.16.14`.
 
 ## Release Boundary
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kudzujs/core",
-  "version": "0.16.13",
+  "version": "0.16.14",
   "description": "HTML-first TSX framework with synchronous state semantics and no virtual DOM",
   "type": "module",
   "license": "MIT",
@@ -65,6 +65,7 @@
     "benchmark:project-list-decision": "node test/project-list-decision-performance.mjs",
     "benchmark:project-state": "node test/project-state-performance.mjs",
     "benchmark:source-scale": "node test/source-scale-performance.mjs",
+    "benchmark:ai-delivery": "node test/ai-delivery-runner.mjs",
     "prepublishOnly": "npm run check && npm test",
     "deploy": "wrangler deploy",
     "preview": "wrangler dev"