chore: release v0.13.0

[avrabe]

Summary

Cuts v0.13.0. One landed PR since v0.12.0:

• feat(p3_stream): LS-R-11 precise stream type-mismatch + fuzz layer-2 fix #191 `feat(p3_stream): LS-R-11 precise stream type-mismatch + fuzz layer-2 fix` — closes P3 async — static stream validation at build time (#94 sub-B) #142 (i) follow-up that was withdrawn from v0.12.0 (PR feat(p3_stream): static stream cycle detection at fusion time (#142 iii) #188) after the Mythos delta-pass auto-scan correctly identified a false-positive path in the role-list heuristic. The new check filters by stream-typed-import presence so sync-only connections with unrelated stream operations are correctly skipped. Bundles fuzz workflow layer-2 (CARGO_BUILD_TARGET=x86_64-unknown-linux-gnu) for the second smithy: sanitizer/libc config drift recurrence on fuzz smoke jobs #168 drift mode.

Test plan

• `cargo check --workspace` clean on 0.13.0
• All 276 `cargo test -p meld-core --lib` pass (includes 5 new LS-R-11 regression tests)
• CI green on this PR
• After merge: tag `v0.13.0` triggers `release.yml` (second run of the synth-pattern flow that landed in v0.12.0)

🤖 Generated with Claude Code

[github-actions]

LS-N verification gate

⚠️ 35/36 verified — 1 missing regression tests

	count
Passed (≥1 test, all green)	35
Failed (≥1 test failure)	0
Missing (no ls_*_NN_* test found)	1

_{Approved loss-scenarios.yaml entries are expected to have a
regression test named ls_<letter>_<num>_* (e.g. LS-A-11 →
ls_a_11_*). The gate runs each prefix via cargo test --lib --no-fail-fast and aggregates pass/fail/missing.}

Failed LS entries

(none)

Missing regression tests

• LS-R-13

_{Updated automatically by tools/post_verification_comment.py.
Source of truth: safety/stpa/loss-scenarios.yaml.}