247 upvotes, 34 comments, finished second on a Sunday. The July launch got 362 and finished third. Better rank, smaller day. Both true.

The comments were worth more than the votes. A few things I didn't have good answers for, which is more useful than an upvote.

Last launch ended with 91 comments. I answered every one, and in most of them I said "not yet, that's next."

Six weeks on, here's what actually happened.

Done: @maschiojv asked about Paddle, it now has 21 curated failure patterns instead of a bare spec import.

Since our last launch we've been heads-down on one thing: making "this integration works" actually mean something. Here's what changed, and why we're more confident than a month ago.

What we shipped?

Five integrations now recognize the bugs people actually hit and prove the fix with a real before/after:

I audited an AI-written billing service this week. 22 findings, 10 critical.

None of them crashed. All returned 200. Four that stuck with me: an auth check that silently lets anyone in when one env var is missing, SQL injection in the one query that wasn't parameterized, a broken permission boundary so anyone can attach a charge to a workspace that isn't theirs, and a Stripe retry that double-grants seats because there's no idempotency check anywhere.

What happened

A few weeks ago my coding agent wrote a Stripe webhook handler. Signature check, event type check, fulfillment, clean 200. I approved it in 90 seconds because every line was correct.

And it was, until Stripe delivered the same event twice. Which it's allowed to do. Then the handler credited the customer twice.

Why it slipped through

launch yesterday (july 12th) we told you all about @FetchSandbox.

today i'd rather hear about you.

The gap most auto-fix tools have

They tell you the bug is fixed. They don't show you. Our rule has always been: make the bug happen on real code, apply the fix, show it stops happening. The gap was we could only do that for bugs we'd scripted in advance. Anything unusual and the honest answer was "found it, fixed it, can't prove this one."

What we built

We taught FetchSandbox to write the reproduction itself, no pre-scripted test required.

three bugs an ai wrote for me this week. every test green. all three would've paged me in prod:

1. webhook retried charged the customer twice

2. subscription.activated arrived before subscription.created they paid, app said not entitled

3. a stale event flipped a canceled sub back to active free access, forever

none of these show up in a 200. you find them from a customer or you fire the ugly event orders on purpose and find them first.

we now throw every ordering + every duplicate at your handler and hand back the exact sequence that broke it.