chore(release): v0.3.6 + fix Cargo.lock time conflict (#394 regression)

[avrabe]

Version bump 0.3.5 → 0.3.6 for the v0.3.6 release (SR-25/27/28 verified: pr-diagnostics fix, kilnd lib extraction, enforced merge gate).

Also fixes a main regression: dependabot #394 left the lock internally inconsistent (tract-linalg 0.21.17 needs time <0.3.42 vs pinned time 0.3.53) — it builds --locked but fails re-resolution. Pinned time to 0.3.41. rivet SR-36.

Full workspace build green. This must pass the 8 required gates before merge → then I tag v0.3.6.

🤖 Generated with Claude Code

[github-actions]

🔍 Build Diagnostics Report

Summary

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

🎯 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
• 5 new warnings in unchanged files
• 4 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).

⚠️ Cascading Warnings (Your Changes Affecting Other Files)

These warnings are in files you didn't modify:

kiln-builtins/src/lib.rs:546:7 - unexpected cfg condition name: kani (unexpected_cfgs)
kiln-builtins/src/lib.rs:295:5 - unnecessary unsafe block (unused_unsafe)
kiln-builtins/src/lib.rs:362:4 - function platform is never used (dead_code)
kiln-platform/src/simd/mod.rs:120:9 - unreachable expression (unreachable_code)
kiln-foundation/src/memory_init.rs:135:13 - non-binding let on a type that has a destructor (let_underscore_drop)

---

📊 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