Summary

Created agent-ready handoffs for five drift-and-clash items found in the June 13 Daily KB follow-up and drift scan. These are coordination handoffs, not live-system change approvals.

Handoff 1: Google Ads outage wording drift

Objective

Clean up or annotate KB language that says Google Ads is broadly down when live NotFair read access is working.

Current evidence

• June 13 drift scan verified NotFair listConnectedAccounts, summarizeAccountSetup, and a read-only runScript succeeded for account 3813916687, Sam Aguiar Injury Lawyers.
• Yesterday campaign rows returned successfully, including spend and conversions.
• Any remaining blocker should be narrowed to the failing lane, such as call-asset mutation OAuth, conversion import/readback, or another write path.

Work to do

1. Search SAIL KB for recent pages using phrases like Google Ads outage, NotFair blocked, deleted_client, call asset, and OAuth.
2. Fetch the relevant pages before changing anything.
3. If a page claims broad Google Ads outage without newer evidence, add a cleanup note or tag it as superseded by June 13 NotFair readback.
4. Do not mutate Google Ads campaigns, budgets, keywords, negatives, conversion actions, or imports.

Go-live or destructive gate

No Google Ads mutations. KB cleanup only, and only when the page is clearly stale.

Suggested closeout

Report which pages were corrected, which remain valid narrower blockers, and whether any Ads write-path auth still needs repair.

Handoff 2: June 13 GCLID Notion entry conflicts with June 12 verified JSON

Objective