Fixed

Managed Deep Capture keeps a proven client-to-launcher handoff alive, binds only an exact successor, and reports an incomplete handoff when none arrives within the finite wait. Its requested observation duration begins at verified client acquisition, with topology-aware defaults and plan-visible phase budgets; ordinary Capture retains its existing timing and terminal-exit behavior.

Native Deep Capture retains bounded per-connection stage and failure evidence, including client TLS success before an upstream failure and completed HTTP work before a later idle timeout. The session bundle, calibration assessment, terminal event, and manifest expose diagnostic loss and measured lifecycle phase time under the existing connection and authorization identities.

S191: Extend controlled managed-client handoff coverage for #552 and add the #558 library-first pre-inspection decision for exact game ownership. Native TCP connections and UDP associations decide from bounded client-side socket and managed process evidence before TLS or content inspection. Current public Deep Capture remains launch-chain; blind forwarding and public selection follow in separate issues. The Npcap SDK import library remains required for each live-capture build and is acquired at build time.

S192: Move Windows default user storage to the current account's .fragcap directory so ordinary and packaged launches resolve one location. Copy an unambiguous legacy SQLite store and authored profiles without removing the source, retain historical sessions at their original paths for Doctor recovery, and report selected and effective storage destinations. Align fresh-start and MSI cleanup with the new roots.

S193: Implement #559 native blind relay for middleware and unresolved owner decisions. Authenticated HTTP/1 CONNECT, HTTP/2 CONNECT, SOCKS TCP, and SOCKS UDP preserve original client-origin traffic without excluded application content or proxy-owned TLS keys. Plaintext HTTP/1 and HTTP/2 keep correct framing while suppressing excluded application exports. UDP QUIC Initial packets bypass native QUIC termination for excluded owners. Directional relay totals and frozen decisions enter bounded diagnostics. Public exact-game selection and calibration remain separate follow-up issues.

S194: Complete #560 and #561 with one scope-aware calibration and Deep Capture journey. --inspect-scope auto|game|launch-chain resolves before effects, launcher-mediated auto selects exact-game inspection with blind middleware relay, and exact scope and handling dimensions now bind compatibility facts and workflow attempts. Generated handoffs preserve the requested scope. An initial workflow may separately authorize one linked exact-game retry and packet-only evidence fallback from an unsuccessful typed inspection result, independently from lifecycle completion. Retry inheritance requires unchanged target and resolved launch authority; fallback success requires reconciled capture output, required artifacts, event delivery, and cleanup. Authorization, Targets, Doctor, human and JSON guidance, native artifacts, and Windows package certification report the same contract. Legacy facts remain history and cannot qualify scope-specific cases.

The controlled Windows setup-to-fresh-calibration regression now uses a finite launch allowance that tolerates ordinary hosted-runner scheduling, instead of racing a one-second startup budget. Product timeout defaults, explicit operator deadlines, and the one-second controlled observation remain unchanged.

Current documentation and frozen replay authority identify the independently verified v0.10.13 files and all ten published crates. Basename-only managed-stage path verification, top-level acquisition timeout, and the combined live #547 source correction are described as shipped; later installed-product findings return as version-specific issues.