[Feature]: Extend G07 (Search + PMax overlap) to cover DSA/Search cannibalization

What problem does this solve?

ads/references/google-audit.md has control G07 | Search + PMax overlap, but no equivalent control for Dynamic Search Ads. Mechanically it's the same failure mode: an auto-targeting ad group (DSA can match any page on the site when use_supplied_urls_only=false) competing in the same campaign's auction against manually-targeted Search keywords, diluting Ad Rank / impression share without being flagged.

Found on a real account (automotive vertical): a DSA ad group, ENABLED, delivering 144 impressions / 35 clicks / 30 days inside the same campaign as Search keywords showing a 60.9% rank-lost impression share. The existing audit never surfaced it because G07 is scoped only to PMax.

Separately, while investigating this we also found the same gap applies at a cross-campaign level: a near-abandoned Search campaign sharing a budget object with an active one carried 780 of 808 keywords (96.5%) as literal duplicates of the active campaign's list — a dormant self-cannibalization risk one geo-targeting fix away from triggering, also outside G07's current scope (which only compares Search vs. PMax within a campaign, not Search vs. Search across campaigns).

Proposed Solution

Generalize G07 into a broader "Search + automated/duplicate-targeting overlap" control, or add sibling controls with the same runtime disposition (conditional evidence control: establish applicability and evaluate from current account evidence; otherwise return unknown/not_applicable) covering:

1. Search + DSA overlap within the same campaign (same mechanism as existing G07, just extended to DSA ad group type).
2. Keyword duplication across different campaigns of the same account (real self-bidding risk, distinct from same-campaign relevance dilution — worth its own ID given the different severity).

Happy to share the anonymized GAQL used to detect both cases if useful for the reference doc.

Related Ad Platform

Google Ads (incl. AI Max)

Alternatives Considered

None — this is a coverage gap, not something with a workaround inside the existing registry.