@kudzujs/core 0.16.16 → 0.16.18

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -57,7 +57,7 @@ Syntax compatibility does not mean reproducing React wholesale. Kudzu accepts th
57
57
  - stronger JavaScript failure resilience;
58
58
  - no remaining material large-route build-scaling weakness.
59
59
 
60
- The completed 0.9 plan defines the cross-framework comparison and release gate. The active application packet is `0.21.2` 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.
60
+ The completed 0.9 plan defines the cross-framework comparison and release gate. The active application packet is `0.21.4` 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.
61
61
 
62
62
  ### 0.10.0 Through 0.21.x: Application Capability Release Train
63
63
 
package/PERFORMANCE.md CHANGED
@@ -2,6 +2,67 @@
2
2
 
3
3
  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.
4
4
 
5
+ ## 0.21.2 Browser Performance And Memory
6
+
7
+ Measured 2026-09-03 at revision
8
+ `fcb42ae388c733ff9098f8c4a059690a21a56ed3` on Linux x64 with Node 24.14.0,
9
+ Chrome 152.0.7977.64, an Intel i5-9500, six logical CPUs, and 31.2 GiB RAM.
10
+ These are same-revision application gates, not cross-framework or historical
11
+ regression claims. Each timing benchmark ran alone with seven fresh Chrome
12
+ profiles; the list decision rotates strategies. Median browser budgets are 100
13
+ ms for measured interactions and enhanced navigation, 1,000 ms for bounded-list
14
+ load, and 2,000 ms for the complete static 10,000-row document.
15
+
16
+ | Fixture | Metric | Raw samples | Median / budget |
17
+ |---|---|---|---:|
18
+ | 2,000 keyed rows | Append 33 | `[9.6, 13.9, 10.8, 12.3, 8.6, 8.8, 7.0]` ms | 9.6 / 100 ms |
19
+ | 2,000 keyed rows | Filter to one | `[16.0, 17.6, 20.4, 21.1, 17.6, 16.3, 16.9]` ms | 17.6 / 100 ms |
20
+ | 2,000 keyed rows | Restore 1,999 | `[66.9, 84.5, 95.3, 78.5, 94.6, 76.4, 98.1]` ms | 84.5 / 100 ms |
21
+ | 2,000 keyed rows | Reverse 2,000 | `[19.4, 18.8, 19.4, 18.7, 18.8, 27.3, 19.6]` ms | 19.4 / 100 ms |
22
+ | Project application | Table save | `[0.8, 0.9, 0.9, 0.9, 0.8, 2.8, 1.0]` ms | 0.9 / 100 ms |
23
+ | Project application | List-to-detail navigation | `[4.2, 9.5, 4.9, 4.2, 6.4, 11.7, 4.1]` ms | 4.9 / 100 ms |
24
+ | 10,000-row direct | Complete load | `[999.8, 1030.9, 982.2, 1070.1, 1047.2, 939.0, 994.3]` ms | 999.8 / 2,000 ms |
25
+ | 100-row pagination | Complete load | `[327.3, 133.9, 163.1, 145.1, 150.5, 417.1, 190.1]` ms | 163.1 / 1,000 ms |
26
+ | 100-row pagination | Next range | `[39.3, 13.3, 14.1, 22.1, 14.6, 18.1, 22.3]` ms | 18.1 / 100 ms |
27
+ | 100-row window | Complete load | `[185.1, 472.8, 247.9, 315.0, 251.7, 148.4, 260.6]` ms | 251.7 / 1,000 ms |
28
+ | 100-row window | Next range | `[23.7, 14.4, 14.0, 48.5, 19.5, 50.5, 26.7]` ms | 23.7 / 100 ms |
29
+
30
+ The keyed graph is nine JavaScript files totaling 30,048 raw / 11,748
31
+ aggregate gzip B. The project list/detail session owns 17 unique JavaScript
32
+ files totaling 81,200 raw / 27,885 aggregate gzip B; its initial list and
33
+ concrete detail route graphs are 69,178 / 24,183 and 67,702 / 23,556 raw/gzip B.
34
+ These are structural route/session artifact bytes from the exact ownership
35
+ report, not compressed network-transfer measurements from the local uncompressed
36
+ server.
37
+
38
+ The lazy editor initially owns 12,982 raw / 6,153 gzip B and defers one 250,086
39
+ raw / 80,890 gzip B CodeMirror chunk. Two route owners share that one deferred
40
+ chunk while owning 21,599 / 9,466 and 21,609 / 9,468 eager raw/gzip B; the static
41
+ sibling owns zero JavaScript. Focused required-Chrome tests pass 3/3, proving no
42
+ deferred request before activation, one native module request, reuse by later
43
+ owners, and exact conditional/document cleanup.
44
+
45
+ The 10,000-row static control retains 10,000 rows, 50,015 elements, 90,023 DOM
46
+ nodes, zero listeners, 534,292 forced-GC heap bytes, and zero JavaScript. Both
47
+ bounded strategies retain exactly 100 rows: pagination records 1,467 nodes, one
48
+ listener, and 1,423,560 median heap bytes; windowing records 1,468 nodes, two
49
+ listeners, and 1,528,288 median heap bytes. Off-range state is released and
50
+ recreated while retained-row identity remains correct.
51
+
52
+ The default endurance gate passes five warm-ups, ten stale-prefetch races, and
53
+ 30 ownership cycles in one profile. Across 101 navigations, editor
54
+ mounts/disposals balance at 71/71, browser state remains zero, documents remain
55
+ six, listeners remain seven, nodes move 164 to 165, and forced-GC heap moves
56
+ 1,969,344 to 2,049,332 bytes: a 79,988 B increase under the existing 2 MiB or
57
+ 15% alarm. No browser exception or failed request occurs. The raw ignored
58
+ artifacts are under
59
+ `test-results/endurance/2026-09-02T23-54-34-324Z/`.
60
+
61
+ The packet adds median alarms to three existing browser benchmarks and permits
62
+ the existing artifact collector to name the active packet. It changes no
63
+ production source, semantic primitive, compiler pass, runtime concept, deploy
64
+ artifact, public API, or browser byte.
65
+
5
66
  ## 0.21.1 Compiler And Route Scale
6
67
 
7
68
  Measured 2026-09-01 on Linux x64 with Node 24.14.0, an Intel i5-9500, six
package/README.md CHANGED
@@ -14,7 +14,7 @@ Kudzu compiles ordinary React-shaped TypeScript and TSX into complete static HTM
14
14
 
15
15
  > Experimental `0.16.x`: the compiler API and supported TSX surface may change.
16
16
 
17
- **Latest release: 0.16.16 - Bounded compiler module cache.** Kudzu now completes the full 10,000-route, 100,000-module source-scale contract under a 10 GiB V8 heap by bounding retained canonical TypeScript AST records. Read the [release notes](./RELEASES.md#01616---bounded-compiler-module-cache), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.16.16), or follow the [architecture packet](./docs/next-architecture/README.md).
17
+ **Latest release: 0.16.18 - AI attribution integrity.** Kudzu's delivery harness now rejects successful-looking attempts that omit their raw attribution trace instead of counting them as zero-cost successes. No framework ranking is claimed; the production-shaped `0.21.4` comparison remains active. Read the [release notes](./RELEASES.md#01618---ai-attribution-integrity), open the [release page](https://github.com/kudzujs/kudzu/releases/tag/v0.16.18), or follow the [architecture packet](./docs/next-architecture/README.md).
18
18
 
19
19
  - [Documentation](https://kudzujs.cloud/docs)
20
20
  - [Installation guide](https://kudzujs.cloud/docs#install)
package/RELEASES.md CHANGED
@@ -1,5 +1,65 @@
1
1
  # Kudzu Releases
2
2
 
3
+ ## 0.16.18 - AI Attribution Integrity
4
+
5
+ Kudzu 0.16.18 makes the AI delivery evidence boundary fail closed before the
6
+ production-shaped `0.21.4` comparison.
7
+
8
+ ### Changed in 0.16.18
9
+
10
+ - Requires a recorded raw attribution trace before an AI delivery attempt can
11
+ count as a success, even when its adapter, build, and acceptance all pass.
12
+ - Retains missing-trace attempts as incomplete failures and reports zero
13
+ successes instead of synthetic zero-token, zero-cost successes.
14
+ - Keeps per-success token and monetary claims unavailable when no attributable
15
+ success exists.
16
+ - Adds a focused exit-zero/no-trace regression while preserving the existing
17
+ paired success/failure and tooling-comparison checks.
18
+ - Records the production corpus boundary: existing complete applications cover
19
+ content, forms, CRUD/shared state, and resource ownership, while the pinned
20
+ public commerce comparator remains the smallest complete paired source.
21
+ - Claims no framework ranking and leaves `0.21.4` active until five attempts per
22
+ framework and task pass the complete behavior, accessibility, build, browser,
23
+ output, maintainability, and retained-performance contract.
24
+ - Adds one harness condition and no semantic primitive, compiler pass, runtime
25
+ concept, application API, dependency, or application browser byte.
26
+ - Updates `create-kudzu@0.1.143` to generate projects on
27
+ `@kudzujs/core@^0.16.18`.
28
+
29
+ ### Upgrade
30
+
31
+ ```sh
32
+ npm install @kudzujs/core@^0.16.18
33
+ ```
34
+
35
+ ## 0.16.17 - Browser Performance Gates
36
+
37
+ Kudzu 0.16.17 turns existing browser performance and memory evidence into
38
+ maintained release alarms without changing production compiler or runtime code.
39
+
40
+ ### Changed in 0.16.17
41
+
42
+ - Enforces 100 ms median budgets for 2,000-row append, filter, restore, and
43
+ reverse operations and project table-save and enhanced-navigation actions.
44
+ - Enforces 1,000 ms bounded-list and 2,000 ms complete static 10,000-row load
45
+ budgets while preserving retained identity and fresh off-range state.
46
+ - Records exact initial, session, and lazy JavaScript ownership, including one
47
+ shared deferred CodeMirror chunk and zero JavaScript on static siblings.
48
+ - Revalidates 30 ownership cycles and 101 navigations with balanced editor
49
+ handles, stable document/listener/cache counts, and 79,988 B forced-GC heap
50
+ growth under the existing alarm.
51
+ - Keeps single-run diagnostic acceptance outside statistical median enforcement.
52
+ - Adds no semantic primitive, compiler pass, production source, runtime concept,
53
+ public API, deploy artifact, or browser byte.
54
+ - Updates `create-kudzu@0.1.142` to generate projects on
55
+ `@kudzujs/core@^0.16.17`.
56
+
57
+ ### Upgrade
58
+
59
+ ```sh
60
+ npm install @kudzujs/core@^0.16.17
61
+ ```
62
+
3
63
  ## 0.16.16 - Bounded Compiler Module Cache
4
64
 
5
65
  Kudzu 0.16.16 bounds canonical TypeScript AST retention so the complete
@@ -15,7 +15,7 @@ The completed `0.9.0` milestone is recorded in [`0.9-semantic-compression.md`](.
15
15
 
16
16
  [`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.
17
17
 
18
- [`application-capability-release-plan.md`](./application-capability-release-plan.md) is the authoritative post-0.9 execution queue, currently at `0.21.2`. 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.
18
+ [`application-capability-release-plan.md`](./application-capability-release-plan.md) is the authoritative post-0.9 execution queue, currently at `0.21.4`. 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.
19
19
 
20
20
  ## Required Invariants
21
21
 
@@ -2035,6 +2035,31 @@ runtime concept, public API, deploy artifact, or browser byte.
2035
2035
  - **Done condition:** complete features meet declared thresholds with bounded
2036
2036
  long-session growth.
2037
2037
 
2038
+ **Result:** closed through existing route artifacts, keyed ownership, enhanced
2039
+ navigation, native ESM loading, and the released endurance harness. Seven fresh
2040
+ Chrome profiles keep 2,000-row append, filter, restore, and reverse medians at
2041
+ 9.6, 17.6, 84.5, and 19.4 ms against a 100 ms median alarm. Project table save
2042
+ and list-to-detail navigation medians are 0.9 and 4.9 ms against the same alarm;
2043
+ the exact session graph owns 17 JavaScript files totaling 81,200 raw / 27,885
2044
+ aggregate gzip bytes. The static 10,000-row document loads in a 999.8 ms median
2045
+ against a 2,000 ms alarm. Pagination and windowing keep the DOM at 100 rows,
2046
+ load in 163.1 and 251.7 ms against a 1,000 ms alarm, and change range in 18.1
2047
+ and 23.7 ms against a 100 ms alarm.
2048
+
2049
+ The lazy editor retains 12,982 raw / 6,153 gzip eager bytes and one 250,086 raw
2050
+ / 80,890 gzip deferred CodeMirror chunk; two route owners share one native ESM
2051
+ module request and the static sibling remains zero JavaScript. Focused Chrome
2052
+ acceptance passes 3/3. The endurance gate passes five warm-ups, ten stale-
2053
+ prefetch races, 30 ownership cycles, and 101 navigations: editor mounts and
2054
+ disposals balance 71/71, browser state stays zero, documents and listeners stay
2055
+ at six and seven, DOM nodes move by one, and forced-GC heap grows 79,988 B under
2056
+ the existing 2 MiB or 15% alarm. No exception or failed request occurs. Three
2057
+ existing benchmark entry points now fail when their declared median budgets are
2058
+ exceeded; the artifact collector may name the current packet. Production source,
2059
+ semantic primitives, compiler passes, runtime concepts, APIs, deploy artifacts,
2060
+ and browser bytes change by zero. Exact samples and limitations are recorded in
2061
+ `PERFORMANCE.md`; no package release is consumed.
2062
+
2038
2063
  ### `0.21.3`: Package And Release Candidate
2039
2064
 
2040
2065
  - **Purpose:** verify the exact candidate as an installed product.
@@ -2044,6 +2069,35 @@ runtime concept, public API, deploy artifact, or browser byte.
2044
2069
  - **Stop condition:** version metadata changes before the exact candidate passes.
2045
2070
  - **Done condition:** the reviewed commit is independently publishable.
2046
2071
 
2072
+ **Result:** released as `@kudzujs/core@0.16.17` and
2073
+ `create-kudzu@0.1.142`. The exact versioned tree passes `npm run check`, all 301
2074
+ remaining tests after the application contract, package smoke, generator
2075
+ creation, and both registry dry runs. Tarball inspection records the expected 85
2076
+ core files and four generator files with no bundled dependencies. The Node 22
2077
+ no-browser lane initially attempted the list acceptance despite
2078
+ `KUDZU_SKIP_BROWSER`; that test now follows the existing skip contract while the
2079
+ Node 24 required-Chrome lane retains the browser acceptance.
2080
+
2081
+ Seven fresh exact-candidate Chrome profiles pass every maintained alarm. The
2082
+ project table-save/navigation medians are 0.7/3.6 ms; direct, pagination, and
2083
+ window load medians are 849.2, 166.6, and 184.5 ms; bounded range medians are
2084
+ 13.0 and 19.7 ms. The keyed benchmark also passes all four 100 ms alarms. A
2085
+ fresh endurance run balances editor mounts/disposals at 71/71 across 101
2086
+ navigations, with zero document/listener growth, one additional DOM node, and
2087
+ 144,172 B forced-GC heap growth under the 2 MiB alarm. Package contents preserve
2088
+ the existing production compiler/runtime and introduce no semantic primitive,
2089
+ pass, runtime concept, API, deploy artifact, or browser byte. The immutable
2090
+ rollback contract remains forward-only: a failed push, tag, publication, or
2091
+ registry verification keeps this packet active; a published npm version or tag
2092
+ is never moved and requires a forward-fix patch.
2093
+
2094
+ Commit `e9b33c04a7a2a382b858069910e4473800e7b70a`, tag `v0.16.17`, the
2095
+ [GitHub release](https://github.com/kudzujs/kudzu/releases/tag/v0.16.17), and
2096
+ [publish workflow](https://github.com/kudzujs/kudzu/actions/runs/33704726784)
2097
+ are complete. npm exposes core `0.16.17` and generator `0.1.142`; a fresh
2098
+ registry-generated application resolves core `0.16.17` and passes its complete
2099
+ TypeScript and Kudzu build check.
2100
+
2047
2101
  ### `0.21.4`: AI Delivery Proof
2048
2102
 
2049
2103
  - **Purpose:** run the final equal-condition comparison on production-shaped
@@ -2055,6 +2109,25 @@ runtime concept, public API, deploy artifact, or browser byte.
2055
2109
  - **Done condition:** the evidence either authorizes `1.0.0` or names the next
2056
2110
  measured blocker without changing the release criteria.
2057
2111
 
2112
+ The first independently reviewable evidence-integrity prerequisite is released
2113
+ as `@kudzujs/core@0.16.18`. A successful adapter result without its raw
2114
+ attribution trace previously remained eligible for the success-rate and median
2115
+ successful-cost denominators with synthetic zero metrics. The runner now
2116
+ requires the trace in the success predicate, retains that attempt as an
2117
+ incomplete failure, and withholds unsupported per-success claims. The focused
2118
+ three-test harness passes and the change adds one condition with no semantic
2119
+ primitive, compiler pass, runtime concept, application API, dependency, or
2120
+ application browser byte.
2121
+
2122
+ This prerequisite makes no framework ranking. Existing complete fixtures cover
2123
+ the content, forms, CRUD/shared-state, and resource/realtime task classes. The
2124
+ pinned public `kudzu-based-bench` storefront at commit
2125
+ `f2d5be1a516c539e30f7125f6870d42b1dd02ecd` remains the smallest complete paired
2126
+ commerce source. The next exact action is to freeze equivalent pre-task starters
2127
+ and complete acceptance journeys for those five classes, then run at least five
2128
+ interleaved attempts per framework and task under one model, tool, context, and
2129
+ time contract.
2130
+
2058
2131
  ## `1.0.0`: Stable Application Model
2059
2132
 
2060
2133
  `1.0.0` is authorized only after every required `0.21.x` gate passes. It means:
@@ -2198,3 +2271,6 @@ release transaction where possible or document and publish a forward-fix patch.
2198
2271
  | `0.20.5` | Closed by measured stop condition | Preserve the negative tooling-cost result and do not present structured tools as an AI cost reduction. | Tool-assisted attempts cost 16,933 more tokens per success; no release consumed |
2199
2272
  | `0.21.0` | Closed by existing semantics | Preserve the complete browser parity matrix, large-list keyboard/release acceptance, and static exclusion controls. | No production change; no release consumed |
2200
2273
  | `0.21.1` | Released as `0.16.16` | Preserve 100/1,000/10,000-route phase, RSS, output, digest, incremental-equivalence, recovery, and bounded canonical-AST retention evidence. | Full 10,000-route report has one complete measured run after two measured-stage diagnostics; no projection used |
2274
+ | `0.21.2` | Closed by existing semantics | Preserve initial/session/lazy bytes, keyed/range/navigation median alarms, and bounded endurance ownership evidence. | Same-revision absolute gates; structural artifact bytes are not compressed network transfer |
2275
+ | `0.21.3` | Released as `0.16.17` | Preserve exact package, browser, benchmark, registry, and fresh-install evidence. | One initial navigation benchmark invocation stalled at the outer timeout; its clean seven-profile rerun passed all alarms |
2276
+ | `0.21.4` | Active; attribution prerequisite released as `0.16.18` | Freeze paired production starters and complete acceptance for the five required task classes, then run at least five interleaved attempts per framework and task. | No local complete React + Vite starter set; derive four pairs from maintained complete fixtures and pin the public commerce pair |
@@ -1,6 +1,6 @@
1
1
  # Current Compiler Architecture
2
2
 
3
- This maps the current `0.16.16` 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.21.2`; file and function names are the stable references, while line numbers are intentionally omitted because later work may still move code.
3
+ This maps the current `0.16.18` 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.21.4`; file and function names are the stable references, while line numbers are intentionally omitted because later work may still move code.
4
4
 
5
5
  ## Responsibility Map
6
6
 
@@ -2,9 +2,9 @@
2
2
 
3
3
  ## Status
4
4
 
5
- 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.21.2`. 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.
5
+ 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.21.4`. 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.
6
6
 
7
- [`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.21.2`; 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.
7
+ [`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.21.4`; 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.
8
8
 
9
9
  ## Product Outcome
10
10
 
@@ -483,4 +483,4 @@ The first comparison is Kudzu versus React + Vite using the same agent, model, t
483
483
 
484
484
  ## Immediate Decision
485
485
 
486
- All listed foundation and `0.9` slices are complete. Current work continues at `0.21.2` browser performance and memory 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.
486
+ All listed foundation and `0.9` slices are complete. Current work continues at `0.21.4` AI delivery proof 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.
@@ -1,6 +1,6 @@
1
1
  # Planned Version Sequence
2
2
 
3
- 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.21.2`; that plan supersedes the provisional tool-first 0.10/0.11/0.12 ordering in the completed 0.9 handoff.
3
+ 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.21.4`; that plan supersedes the provisional tool-first 0.10/0.11/0.12 ordering in the completed 0.9 handoff.
4
4
 
5
5
  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.
6
6
 
@@ -66,7 +66,7 @@ Keep each patch behavior-preserving and independently reviewable. If a boundary
66
66
 
67
67
  ## Generator Versions
68
68
 
69
- `create-kudzu@0.1.141` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.16.16`.
69
+ `create-kudzu@0.1.143` retains the explicit install instructions and generates projects with `@kudzujs/core@^0.16.18`.
70
70
 
71
71
  ## Release Boundary
72
72
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kudzujs/core",
3
- "version": "0.16.16",
3
+ "version": "0.16.18",
4
4
  "description": "HTML-first TSX framework with synchronous state semantics and no virtual DOM",
5
5
  "type": "module",
6
6
  "license": "MIT",