Build the output.
Verify the application.

Successful compilation is not browser or accessibility proof. The README, build reference, and ordinary build success output now make that boundary explicit.

Read verification guidance Inspect the release

0compiler or runtime behavior changes

0 Bbrowser JavaScript delta

0new dependencies

0.16.27

APPLICATION VERIFICATION

Check visible behavior.
Keep evidence bounded.

BROWSER

Visible DOM, not raw strings

Binding comments and inert templates make raw HTML matching and tag stripping unreliable for rendered text. Verify relevant interactions, labels, status updates, keyboard focus, and responsive layouts. Missing tools and truncated responses are not passes; rerun affected checks after edits.

TOOLS

Optional reports rebuild

Inspect JSON and exact-route explain JSON both rebuild, including hooks and output emission. They report compiler and artifact facts, not full browser or accessibility proof, and are not a mandatory post-build sequence.

OUTPUT

A bounded success hint

Ordinary successful builds link to the build reference. Failed, quiet, and JSON builds suppress the hint. Tests preserve byte-identical fixture artifacts; compiler semantics, runtime behavior, and browser JavaScript are unchanged. The prior npm internal-document exclusions remain in place.

LIMITS

Historical evidence, not savings

Historical r8 on released 0.16.26 records Kudzu 23/25 versus React + Vite 24/25. All Kudzu outputs pass acceptance; two content attempts exceed input budgets and one unchanged React CRUD output fails acceptance. This guidance has no measured token benefit. No new benchmark, rescoring, or sandbox claim is included; 1.0.0 remains blocked.

UPGRADE

Same compiler. Clearer verification.

$npm install @kudzujs/core@^0.16.27

Build the output.Verify the application.