test(dwarf): LS-CP-4 aliases + gate scans integration tests

[avrabe]

Summary

Two related fixes for the LS-N verification gate's coverage of LS-CP-4 ("DWARF passthrough emits address-incorrect debug info").

Fix 1: Convention aliases in dwarf_strip.rs

The file already has three tests pinning Phase 1.5's Strip-default policy (the mitigation LS-CP-4 calls for): default_strips_dwarf, passthrough_preserves_dwarf, default_is_strip. The gate just couldn't find them by name. Adds three convention aliases delegating to the existing test bodies — same pattern as PR #161's five aliases.

Fix 2: Gate scans integration tests too

tools/run_ls_verification.py was invoking cargo test --lib, which excludes <package>/tests/. Drops the --lib filter so both lib and integration-test binaries participate. One-line semantic change; the parser was already shaped to sum multiple test result: lines, so no other plumbing impact.

Gate verdict

State	Before	After
Verified	16/19	17/19
Missing	3 (LS-CP-4, LS-A-8, LS-A-9)	2 (LS-A-8, LS-A-9)
Failed	0	0

Remaining two need net-new tests, not aliases — surveyed in task #52:

• LS-A-9 (~1-2h): byte-pattern assertion on generate_async_callback_adapter emitted body for the WAIT||POLL OR-pattern
• LS-A-8 (~2-4h): adversarial 2+ resource component fixture verifying rep_func selection

Test plan

• CI green
• LS-N verification gate posts sticky comment showing 17/19 verified / 2 missing / 0 failed
• No production code paths touched; this is test/CI scaffolding only

🤖 Generated with Claude Code

[github-actions]

LS-N verification gate

⚠️ 17/19 verified — 2 missing regression tests

	count
Passed (≥1 test, all green)	17
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-A-8
• LS-A-9

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