chore: release v0.16.0

[avrabe]

Summary

Cuts v0.16.0. Landed since v0.15.0:

• feat(provenance): v2 per-function code-byte ranges (#143 DWARF Phase 2 inc 1) #200 DWARF Phase 2 increment 1 — component-provenance section v2 with per-function code-byte ranges (code_range { start, end }), the anchor for DWARF address remapping. Additive v1→v2.
• fix(safety): correct LS-M-5 status to fixed (already mitigated by reject) #199 LS-M-5 status correction — the multiply-instantiated-module silent-corruption hazard was already closed by detection-and-reject; flipped open→fixed with a gate-convention regression test.

DWARF Phase 2 increments 2 (rewriter instruction-offset map) + 3 (gimli .debug_* rewrite) follow in later releases.

Test plan

• cargo check --workspace clean on 0.16.0
• 291 lib + provenance integration tests green (verified pre-bump on f6f36ee)
• CI green
• After merge: tag v0.16.0 → fifth run of the signed/attested release pipeline

🤖 Generated with Claude Code

[github-actions]

LS-N verification gate

⚠️ 35/37 verified — 2 missing regression tests

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

_{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
• LS-M-6

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