Customer Comms Reader

Five client relationships across seven languages, and the state of each one lives in Gmail, Calendar and Drive and nowhere else. Reconstructing a week costs me 20 to 40 minutes of scrolling, and what scrolling misses is the part that matters, because absence does not appear in a list: an unanswered thread, a stakeholder who quietly stopped accepting invites, a decision postponed rather than made. So the failure I care about is not a wrong summary. It is a confident one. This runs in two phases with a file between them: harvest reads Gmail, Calendar and Drive and writes harvest.json using Google's own field names, then reasoning runs over that file and reads nothing. Because the manifest exists before any thinking happens, a claim either resolves to a real record or it is treated as fabricated. Three scripts print PASS or FAIL with numbers. Building it against a real account taught me the tooling lies three ways, each returning success: a result count that said 201 for a true 35, an output flag that writes nothing while exiting zero, and unsent drafts whose ids are genuine. Guidance-only, so there is no backend and no API key to hand over.