feat: re-vendor KDNA Core 0.21.0 schema closure + web-client 0.3.0 (0…

….4.0) (#18)

Re-pin all six schemas and the runtime-contract golden to the published
0.21.0 authority (32aa3ff); regenerate browser validators; upgrade
@aikdna/kdna-web-client 0.2.2 -> 0.3.0 so 0.21.0 Runtime Capsules
(projection_report) validate end to end. Bump to 0.4.0.

Signed-off-by: aikdna <283974009+aikdna@users.noreply.github.com>
Co-authored-by: aikdna <283974009+aikdna@users.noreply.github.com>

release: prepare React 0.3.0 integration

Bind React to the accepted KDNA web and activation stack, harden browser and release boundaries, and add reproducible public verification.

Signed-off-by: aikdna <283974009+aikdna@users.noreply.github.com>

Add current JudgmentTrace React adapter (#5)

* review: preserve Phase 0-7 candidate implementation scaffold

All work from the 2026-07-11 session, preserved for independent review.
This commit captures the state BEFORE P0 fix cycle.

Known defects (see kdna-verification-report-2026-07-11.md):
- false completed/verified trace when asset not loaded
- runtime artifacts do not conform to candidate schemas
- Cluster migration produces invalid manifest
- Asset Assay pass-on-error
- React/Web adapters not exported/built
- 2 failing Cluster tests

Co-Authored-By: Claude <noreply@anthropic.com>

* feat: add current JudgmentTrace React adapter

---------

Co-authored-by: aikdna <283974009+aikdna@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>

0.1.2

[codex] Harden React package postpublish checks (#3)

[codex] Harden React package postpublish checks

0.1.0 — initial npm publish