v2.0.0
SECURITY- ·File scanning now fails closed when a target disappears, changes during inspection, cannot be read, cannot be hashed, or a detector fails. Structured, bounded coverage diagnostics replace false-clean outcomes and survive faulty event subscribers.
- ·The AMSI bridge now enforces strict string and buffer limits, bounded native-call concurrency, deterministic lifecycle synchronization, explicit overload results, and health telemetry for repeated native failures.
- ·Fleet snapshots use a stable generation, monotonic sequence, and deterministic snapshot identity. Duplicate delivery is idempotent; conflicts, stale order, unknown generations, and retired-generation replay are rejected.
- ·Accepted fleet state and its bounded telemetry audit batch commit together in one authenticated server transaction. Client progress advances only after an accepted or duplicate acknowledgement, so ambiguous failures cannot silently skip queued state.
- ·Telemetry retention rollover now emits an explicit acknowledged coverage-gap record instead of silently advancing the cursor. Queued snapshots survive restart; new source events remain memory-only until the next snapshot is durably queued and the UI states that boundary.
- ·Signed machine-authority logs and checkpoints now serialize every authenticated field in an explicit protocol order, eliminating reflection-order drift that could make a newly written authority file reject itself under concurrency.
- ·Every desktop tab now uses one responsive page-header and state vocabulary, with measured runtime layout coverage for a 1920x1080 display at 150% scaling plus compact-window behavior.
- ·Endpoint, first-party ravensoftworks.com authority, installer, portal, deployment tools, release evidence, and one-use hardware-bound Owner enrollment now share one exact v2.0.0 identity graph.
Status: v2.0.0 remains a release candidate. Public availability waits for trusted production signing, clean-VM lifecycle evidence, and independent efficacy, false-positive, performance, privacy, and penetration evaluation.
The existing Owner remains bound to the exact authorized server, device, full hardware identity, and canonical user. v2.0.0 does not add a generic hardware-ID administrator bypass.
Protection health reports measured runtime coverage and precise platform or permission failures. A configured toggle is not presented as a healthy interception boundary without evidence.
Public comparative antivirus claims still require a trusted production signature, clean-VM lifecycle evidence, independent efficacy and false-positive testing, performance measurement, and external penetration review for this exact build.