Close public API gaps: nameable field types, reachable no_libc, honest rule-load errors

[mnaza]

Closes #22.

Small public-API fixes; everything is additive or behavior-preserving for existing callers. New tests/public_api.rs integration test pins the surface (5 tests; total 18 lib + 5 integration, all green).

1. Types in public fields are now nameable downstream

Properties::format / os / arch and FileCapabilities::security_checks exposed types from private modules — downstream could Debug-print them but never match on them. Now re-exported from the crate root:

pub use crate::consts::{FileFormat, Os};
pub use crate::security::options::status::SecurityCheckStatus;
pub use smda::FileArchitecture;

2. FunctionCapabilities getters

address() / features() / capabilities() — fields stay private, so this is additive and non-breaking.

3. no_libc is reachable

BinarySecurityCheckOptions fields are pub(crate) and new() hard-coded no_libc: false — the documented "assume no C runtime" option could not be enabled. New builder-style method:

let opts = BinarySecurityCheckOptions::default().no_libc(true);

4. Rule loading: real parallelism + real errors

The loader thread was spawned after get_file_extractors / Extractor::from_buffer, and smda disassembles eagerly in the constructor — so join blocked immediately and ~1000 YAML rule files loaded strictly serially. The spawn now happens first, overlapping rule loading with format detection + disassembly.

Errors: Ok(Err(_)) | Err(_) => DescriptionEvaluationError threw away the actual failure (bad YAML, missing dependency…) and pointed users at the wrong thing. Now the real RuleSet::new error propagates, and a loader panic is re-thrown via resume_unwind instead of being mislabeled.

5. Strict LibCSpec::from_str

Unknown LSB versions silently became LSB5, changing fortify-check semantics (e.g. 4.0.1 typo). FromStr returns the new Error::InvalidLibCSpec; the lenient From<String> stays for compatibility; capa_cli now uses the strict parse and exits with an error message on bad input.

6. from_file(impl AsRef<Path>)

Was AsRef<str> — non-UTF-8 paths (legal on Unix) could not be analysed. &str/String callers keep compiling; conversion is to_string_lossy internally.

Verified: cargo test --all-features, cargo check --no-default-features / --features verbose, clippy --all-targets — all clean. CHANGELOG entry under [Unreleased]. Based on master; independent of #17 / #19 / #21 except for the shared [Unreleased] CHANGELOG heading.

[marirs]

conflicts