Problem
Many engineering teams run private LLMs or internal CLI tools that do not emit vendor telemetry. Without an explicit adapter, AI-generated edits appear in the editor but lack prompt, model, and session context. That gap reduces the usefulness of provenance for audits and PR reviews.
High-level approach
Define the signals you can trust: header signatures, stable user‑agent tokens, unique payload fields, or session identifiers. Rank them by trustworthiness.
Design evidence rules: for each detectable signal, document a short justification, the expected field, and an evidence weight (high for signed headers, lower for heuristics).
