chore(release): v0.4.3 — kilnd arg-arity correctness + kiln-component isolated build

[avrabe]

Focused patch, 2 verified artifacts.

rivet	fix
SR-53 (#443)	kilnd no longer invokes param-taking functions with zero-filled args and reports the wrong result as success — arity is enforced fail-loud on every invocation surface; a param-arity-invalid component is rejected at load (matching wasm-tools/wasmtime).
SR-54 (#446)	kiln-component compiles standalone (cargo check -p kiln-component), not only under workspace feature unification.

Workspace 0.4.2 → 0.4.3 (+16 path-dep pins + Cargo.lock; cargo build --workspace --locked verified green).

Re-verified at this commit (4c0fb50), not inherited from the PRs

addone --function (no args)   was: ✓ I32(1), exit 0   now: ✗ "expects 1 argument", exit 1
internal dbl(21) via run      I32(42)   (regression clean — internal calls unaffected)
_start (zero params)          completes (no over-rejection)
WAST arg-path slice           589 assertions pass (call 138/func 192/fac 8/call_indirect 251)
cargo check -p kiln-component compiles standalone; workspace still green

Falsification — this release is wrong if any of these is observed

• kilnd invokes a param-taking export with fewer/more args than declared and returns a result (zero-filled or truncated) instead of erroring;
• a component whose canon lift param arity differs from its backing core function runs instead of being rejected at load;
• a zero-param entry point (_start, run) is wrongly rejected;
• cargo check -p kiln-component fails to compile standalone, or cargo build --workspace --locked fails on a clean checkout.

Traceability note

Statuses are prose-verified — the convention every prior kiln release used; typed verifies links remain structurally impossible for type: requirement (pulseengine/rivet#721). #446's rotten test targets remain open (this fixes the lib isolated build only).

🤖 Generated with Claude Code

[github-actions]

🔍 Build Diagnostics Report

Summary

Metric	Base Branch	This PR	Change
Errors	0	0	0
Warnings	5	5	0

🎯 Impact Analysis

Issues in Files You Modified

• 0 new errors introduced by your changes
• 0 new warnings introduced by your changes
• 0 total errors in modified files
• 0 total warnings in modified files
• 0 files you modified

Cascading Issues (Your Changes Breaking Other Files)

• 0 new errors in unchanged files
• 0 new warnings in unchanged files
• 0 unchanged files now affected

Note: "Cascading issues" are errors in files you didn't modify, caused by your changes (e.g., breaking API changes, dependency issues).

✅ No Issues Detected

Perfect! Your changes don't introduce any new errors or warnings, and don't break any existing code.

---

📊 Full diagnostic data available in workflow artifacts

🔧 To reproduce locally:

# Install cargo-kiln
cargo install --path cargo-kiln

# Analyze your changes
cargo-kiln build --output json --filter-severity error
cargo-kiln check --output json --filter-severity warning

[codecov]

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.