Added

Added scrubbed Steam and publisher-launcher proxy-inheritance findings for the Deep Capture issue #215 research.

Added the full alias-only proxy inheritance matrix for issue #215, including cold and warm platform launches, direct executable handoff behavior, and publisher-launcher proxy sensitivity findings.

Added a privacy-preserving proxy-inheritance report generator and alias-only evidence template for the issue #215 measurement work.

Adds a privacy-preserving measurement protocol for Steam and publisher-launcher proxy inheritance so Deep Capture launch compatibility can be recorded without committing local titles, paths, endpoints, or account material.

Added local Deep Capture compatibility fact storage to the targets database, including typed fact keys, launch-case context, proxy backend provenance, final socket-owner details, freshness fields, and stale observation support.

Added Deep Capture readiness and cleanup checks to fragcap doctor: proxy backend availability, local CA trust state, analyzer key-log readiness, stale proxy ports/processes, stale manifests, TLS key logs, sensitive sidecars, session storage reporting, manifest-declared sensitive artifact discovery, and confirmation-gated cleanup for unfinished manifests and known sensitive sidecars under fragcap-owned session storage.

Added the first Deep Capture command path. fragcap deep-capture resolves one stored target, requires managed launch ownership and explicit CA trust confirmation, refuses real targets without current scoped proxy compatibility, correlates packet and proxy observations with stable session-local flow ids, writes complete or partial bundles with application, proxy, process, compatibility, cleanup, optional HAR, and optional proxy-owned key-log artifacts, exposes requested key logs to live analyzers from their final bundle paths, emits Deep Capture lifecycle events, and updates local compatibility facts from scrubbed observations.

Published the current Deep Capture traffic-support reference and added a read-only compatibility matrix to fragcap targets show. The matrix comes from the selected target's local facts, preserves conflicting evidence, and labels source, launch case, freshness, and unknown state without guessing a title verdict.

The architecture documents now define Capture and Deep Capture as first-class product modes. Capture remains the passive, process-attributed packet-capture path, while Deep Capture is positioned as explicit, scoped local proxy inspection for authorized game-development and research workflows. The constitution now frames P-1 as no covert target instrumentation, wires AI_CONTEXT.md into agent-facing required context, and keeps process injection, hooks, memory reads, packet interception drivers, Winsock catalog modification, executable modification, and target TLS key extraction denylisted.

docs/plans/deep-capture.md records the planned Deep Capture product direction: explicit scoped application-layer inspection through a local proxy, preserved passive Capture mode, compatibility fact storage, session-bundle outputs, doctor cleanup requirements, and the first discovery workstreams.