docs(campaign): define target-like mail evidence

docs/CAMPAIGN_DELIVERY_RUNBOOK.md

@@ -104,6 +104,19 @@ bed where possible:
 - IMAP append failure after SMTP acceptance.
 - Worker restart with queued, claimed, and sending jobs.
 
+For the maintained loopback baseline, run
+`dev/mail-testbed/run_campaign_acceptance.py`. It proves the public Campaign
+path for SMTP acceptance, IMAP append, repeat-send blocking, an SMTP connection
+failure before transmission, an explicit SMTP authentication rejection, and an
+IMAP authentication rejection after SMTP acceptance. Its evidence is an
+allowlisted classification/count projection; raw provider diagnostics and
+transport/account identifiers are deliberately excluded.
+
+The runner does not simulate a connection loss after SMTP DATA and does not
+restart a real worker. Keep those two checklist items open until a controlled
+fault proxy/target provider and supervised worker environment can produce the
+corresponding `outcome_unknown`, restart, retry, and reconciliation evidence.
+
 ## Reporting Checks
 
 - Partial delivery must show accepted, failed, and unknown counts separately.

docs/EXAMPLE_CAMPAIGNS_AND_RELEASE_CHECKLIST.md

@@ -26,7 +26,9 @@ schema and are safe to run in non-production environments.
 - campaign with blocked recipients or attachment errors that must not be sent
 - mock delivery campaign that captures SMTP and IMAP append messages in the mail
   development mailbox
-- real non-production delivery campaign against the GreenMail test bed
+- [`greenmail-delivery`](../examples/greenmail-delivery/campaign.json), a
+  credential-free real-delivery Campaign materialized with a temporary
+  Mail-owned profile by the loopback acceptance runner
 
 ## Fixture Rules
 
@@ -53,6 +55,13 @@ Before tagging a campaign release:
 - Run the mock delivery example when the mail development mailbox capability is
   enabled.
 - Run the GreenMail SMTP/IMAP smoke for a non-production real delivery path.
+- Run `dev/mail-testbed/run_campaign_acceptance.py` and retain its bounded JSON
+  projection. It must show one SMTP acceptance, one IMAP append, no duplicate
+  effect from a repeated ordinary send, matching Campaign report/audit state,
+  and no resolved transport material in Campaign JSON or its execution
+  snapshot.
+- Do not interpret the local failure drills as post-DATA ambiguity or worker
+  restart proof; the evidence coverage flags must keep those gaps explicit.
 - Confirm reusable mail profile selection is revalidated after campaign owner
   transfer.
 - Confirm every inline SMTP/IMAP field is rejected on import/write, omitted