Record sanitized post-publication production validation

README.md

@@ -6,6 +6,8 @@
 
 **Portfolio evidence:** 225 automated tests at publication (178 unit + 47 Workers-runtime integration tests) · TypeScript · Cloudflare Workers/D1/Workflows · x402 payments · passing CI
 
+**Post-publication validation:** two separately approved 2026-09-10 Base-mainnet production audits exercised one-cent payment negotiation, paid wait creation, first-event acceptance, and successful callback delivery. The portfolio record intentionally omits wallet, capability, callback-token, receiver, and payment-proof identifiers. [Sanitized validation record](docs/POST_PUBLICATION_VALIDATION.md).
+
 An agent often needs to pause until another system sends an event. Keeping the agent running or repeatedly polling wastes resources and complicates recovery. Wait stores a temporary event receiver, accepts one future JSON event, and delivers it to the buyer's HTTPS callback.
 
 **The production Wait service is live and designed for largely autonomous machine-to-machine operation.** Once deployed and configured, the normal purchase, waiting, event acceptance, and callback-delivery lifecycle runs without a human operator. Human intervention is reserved for exceptional payment reconciliation, operational maintenance, or other unusual remediation cases.

docs/POST_PUBLICATION_VALIDATION.md

@@ -0,0 +1,21 @@
+# Post-publication validation
+
+This portfolio repository began as a sanitized snapshot published on 2026-09-07. The production Wait service continued to be exercised afterward. This note records only non-secret evidence that materially changes how the work sample should be interpreted; it intentionally omits wallet identifiers, capability URLs, callback tokens, receiver-specific URLs, payment proofs, credentials, and private operational records.
+
+## 2026-09-10 Base-mainnet cold audits
+
+Two separately approved one-cent Base-mainnet production audits exercised the Wait lifecycle through an iPhone Base App handoff. In each run:
+
+- an unsigned create request negotiated payment with HTTP 402 before wallet approval;
+- the buyer approved exactly one payment authorization;
+- the service reported successful paid wait creation;
+- the first event was accepted;
+- a disposable public HTTPS receiver observed one callback from the Wait Worker.
+
+In the second run, the receiver observed the callback about five seconds after event acceptance, consistent with first-attempt delivery. The first run also ultimately showed one delivered callback after an initially stale receiver dashboard view.
+
+These audits provide live evidence for the product path described by the public snapshot: payment-gated creation, durable event acceptance, and bounded callback delivery. They do not change the repository's publication boundary or make this snapshot a production configuration.
+
+## Publication boundary
+
+No wallet secrets, payment signatures, event/status capabilities, callback tokens, receiver URLs, production database records, or deployment credentials are included here. The public repository remains an isolated portfolio work sample whose external effects are mocked during its own CI validation.