TK-11409: rescue the text of two Aug-15 drafts ~4 days from permanent deletion

42b4eba743117431062d62a99b7499a3e0ac312c · 2026-09-10 11:53:24 -0700 · Steve Abrams

com.steve.george-drain-old-drafts permanently deletes info@ drafts at 30 days with no
Trash recovery. Both were written 2026-08-15, so deletion is ~2026-09-14. One is real
unfinished correspondence to Kravet asking two specific unanswered questions (delivery
destination on four samples, status of two outstanding ALTHEA items), unsent for 26 days.

Could not extend/send/move them: the Gmail trash+modify tools are on the claude.ai Gmail
connector (session expired) and the classifier blocks the credential read needed to reach
George's draft endpoints. Capturing the text was the only non-destructive action available.

Also records a separate live defect found while reading them: every chase draft AND every
chase already sent carries a visible 'From job: node' provenance banner inside the message
body, so vendors have been receiving it for weeks.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Files touched

A data/rescued-drafts-2026-09-10.md

Diff

commit 42b4eba743117431062d62a99b7499a3e0ac312c
Author: Steve Abrams <steve@designerwallcoverings.com>
Date:   Thu Sep 10 11:53:24 2026 -0700

    TK-11409: rescue the text of two Aug-15 drafts ~4 days from permanent deletion
    
    com.steve.george-drain-old-drafts permanently deletes info@ drafts at 30 days with no
    Trash recovery. Both were written 2026-08-15, so deletion is ~2026-09-14. One is real
    unfinished correspondence to Kravet asking two specific unanswered questions (delivery
    destination on four samples, status of two outstanding ALTHEA items), unsent for 26 days.
    
    Could not extend/send/move them: the Gmail trash+modify tools are on the claude.ai Gmail
    connector (session expired) and the classifier blocks the credential read needed to reach
    George's draft endpoints. Capturing the text was the only non-destructive action available.
    
    Also records a separate live defect found while reading them: every chase draft AND every
    chase already sent carries a visible 'From job: node' provenance banner inside the message
    body, so vendors have been receiving it for weeks.
    
    Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 data/rescued-drafts-2026-09-10.md | 62 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 62 insertions(+)

diff --git a/data/rescued-drafts-2026-09-10.md b/data/rescued-drafts-2026-09-10.md
new file mode 100644
index 0000000..b9ba002
--- /dev/null
+++ b/data/rescued-drafts-2026-09-10.md
@@ -0,0 +1,62 @@
+# Rescued draft content — captured 2026-09-10 (TK-11409)
+
+`com.steve.george-drain-old-drafts` **permanently deletes** info@ drafts at 30 days, with no Trash
+recovery. These two were created **2026-08-15**, so their deletion date is **~2026-09-14 — four days
+out** at time of capture. The text is preserved here so the content cannot be lost, regardless of
+what happens to the drafts themselves.
+
+I could not extend, send, or move these drafts: the Gmail trash/modify tools sit on the `claude.ai
+Gmail` connector (session expired) and the classifier blocks the credential read needed to reach
+George's draft endpoints directly. Capturing the text is the one non-destructive action available.
+
+---
+
+## 1. Kravet reply — REAL unfinished correspondence, not automation output
+
+* **Draft message id:** `1a006aa890e66af3`
+* **To:** matt.schoffman@kravet.com
+* **Subject:** Re: Sample Follow-Up — Outstanding Memos (Acct 10087117) — Designer Wallcoverings
+* **Written:** Sat, 15 Aug 2026 11:23 PT
+
+> Hi Matt,
+>
+> Thank you for the tracking! Quick confirmation on the four that show delivered — **2019101.34.0,
+> 2019101.313.0, F1562/04.CAC.0 and F1562/02.CAC.0**: were those shipped to our Sherman Oaks office,
+> or drop-shipped directly to the client? We just want to be sure we have the samples in hand before
+> we close them out on our end.
+>
+> Also, the two **ALTHEA** items (Cotton P. Citron and Linen Pr. Citron) are still outstanding for
+> us — could you check on those?
+>
+> Thank you!
+>
+> Best regards,
+> Designer Wallcoverings
+> 1-888-373-4564
+
+**Why this one matters:** it asks Kravet two specific unanswered questions — a delivery-destination
+confirmation on four samples, and the status of two outstanding ALTHEA items. It has sat unsent for
+26 days. If it is never sent, those six items stay unresolved and nobody is tracking them.
+
+---
+
+## 2. Unsent chase — Acct On File
+
+* **Draft message id:** `1a005fc3ff6c56ff`
+* **Subject:** Sample Follow-Up — Outstanding Memos (Acct On File) — Designer Wallcoverings
+* **Written:** Sat, 15 Aug 2026 08:13 PT
+* Standard template chase letter, never sent.
+
+---
+
+## Separate defect found while reading these
+
+Both drafts — and **all 12** chase drafts created 2026-09-10, and **every chase already sent to
+vendors** — carry a visible provenance banner at the top of the message body:
+
+> **From job:** node · Aug 15, 2026, 11:23 AM
+
+This is George's internal `withSourceFooter` tag. It is *inside the body*, so it reaches the vendor.
+Sent chases from 09/01 and 09/04 show it in their snippets, so vendors have been receiving it for
+weeks. George suppresses it when the caller passes `no_source_tag`, which the sample-followup
+pipeline does not do.

← b4d9ec1 TK-11409: anti-dup keys on the CHASE subject, not the new-or · back to Sample Followup Sweep · TK-11409: stop shipping the internal 'From job:' banner to v de5df55 →