Read /var/www/html/docs/inbox-workflow/GMAIL-TEST-HANDOFF.txt and inspect the current application before taking action. My objective is to automatically test, using my own server and mailboxes, whether a real reply, a Gmail-initiated conversation, or explicit recipient feedback helps later messages from admin@good-ideas.info via IP 151.80.142.110 reach the Inbox of zombiescloud454501@gmail.com. Determine what information from a reply is useful and measure actual Gmail delivery labels. Do not assume a special header guarantees Inbox. Use the existing encrypted Gmail connection on the API server; verify the mailbox identity and refresh credentials through the existing backend services. Keep all Google tokens, connection keys, passwords, and secrets out of chat, reports and logs. I authorize the bounded test run described in that handoff, only between those two mailboxes, including genuine test replies and the explicitly identified Not-spam intervention after its baseline is recorded. Do not send to workers or other people. Inspect the sending application's real single-message mechanism. Build an isolated test harness if needed, persist attempts before sending, avoid duplicate sends, and never automatically resend an uncertain attempt. Preserve existing production workflows. Proceed with the authorized tests when access is available. If sender access is missing, finish the preflight and prepare the concrete test/harness first, then tell me the missing project path or access mechanism. Do not request passwords or tokens in this conversation. Report the new run's measured evidence and limitations only; do not recount any previous tests or conversation history.