v0.3.0

Highlights since v0.2.0

Cross-version function relocation

When a byte pattern no longer matches a recompiled build, the Signature Maker now relocates the function by a recompile-stable handle and mints a fresh per-build AOB at the resolved address:

• Anchors: a referenced string, an imported-API set, a string-anchored caller, the C++ vtable structure (with constructor grounding for refactored tables), and an encoding fingerprint.
• Widest-path chaining through intermediate builds for the vtable anchor, each hop back-checked against the source identity.
• Per-version AOB ranges reported in the CLI report and the desktop Signature Maker.

The anchors ship with an honest, real-corpus coverage and false-positive measurement. Across a major client refactor the round-trippable anchors (import, caller, vtable) had zero confirmed wrong-address landings, coverage concentrates within a version lineage, and the residual limits of pure string anchoring across a major break are measured and documented.

Signature Maker scoring and diagnostics

Independent 0..100 sub-scores blended into a final A to F grade, graded cross-build function similarity, validated string anchors, and a negative-corpus penalty, all surfaced in the CLI JSON and the desktop workspace, alongside a structured resolve trace, a Section Map, and a Job Timeline.

Hardening

Partial-read tracking and surfacing, architecture-mismatch detection, a granular resolver with a serializable trace, @hits enforcement, and hardened Tauri file IO (allowlist, traversal and alternate-data-stream rejection, canonicalization).

Engineering

• Rust 2024 workspace, MSRV 1.95.
• CI enforces rustfmt, clippy with warnings denied, the full test suite, an MSRV check, and a cargo-audit security scan.
• A golden signature snapshot keeps generated output byte-stable across refactors.