Flash patch

Flash Patch is a self-maintaining API platform for the one workflow every team dreads: application maintenance after a third-party API changes underneath you. Register a GitHub repo once, and Flash Patch takes it from there — detecting breaking changes in the Stripe API, scanning your codebase for every affected call site, patching what it can safely fix on its own, running your full test suite in isolation to prove nothing broke, and opening a pull request with the fix ready for review. Under the hood, it's a five-stage pipeline built entirely with IBM Bob 2.0. Stage 1 diffs two versions of an OpenAPI spec into structured changes — renamed fields, removals, newly-required fields, deprecated endpoints, type changes — using similarity scoring to catch renames without ever guessing on ambiguous cases. Stage 2 walks your Python codebase with the ast module (no regex) to find every Stripe call site and response read actually affected. Stage 3 mechanically patches what's safe, falls back to an LLM for genuine judgment calls, and never silently deletes code that reads a field — that always goes to human review instead. Stage 4 runs your test suite against an isolated copy of the patched repo, with a baseline comparison so a pre-existing failure is never mistaken for a regression. Stage 5 decides whether it's safe to open a PR and, if so, actually commits the patched files and opens it via the GitHub API — merge is always left to a human, by design. The result is a hosted dashboard where "my Stripe integration might be broken" turns into a five-minute pull-request review instead of a production incident.