Merge-Ready

• 

  Intake page with short tutorial popup open

• 

  Problem description

• 

  How merge is solved

• 

  Architecture

Inspiration

I have seen trusting AI commits to break builds in production. Reviewing diffs doesn't scale due to ai speed of coding. That painpoint is visible in Reddit channels where devs hang out. Then I wanted to build a gate that makes every AI claim checkable before merge.

What it does

Paste a ticket: the planner writes file-scoped steps, each drafted and verified in a sandbox branch. Green diffs compose the pull request with a cost receipt; red ones roll back, evidence kept.

How we built it

React and Vite console, Node API, Python sidecar over contree sandboxes; Nebius Nemotron plans and drafts, Tavily grounds context; verified live, shipped to Cloud Run behind Playwright gates.

Challenges we ran into

Cloud Run's edge reserves /healthz and 404s it before our container; we aliased /health and redeployed. Replay-vs-live parity and flaky sandbox timing took loud, logged retries.

Accomplishments that we're proud of

A deployed console that works as it was designed to even though using tools I've never used before. And a final proof of concept that shows the issue can be solved.

What we learned

A route defined in code may never reach the app on managed platforms, so verify on the real URL is mandatory.

What's next for Merge-Ready

Multi-repo baselines, budget-aware planner downgrades by default, and per-branch flakiness stats so red builds teach the planner.

Built With

• cloud-run
• docker
• ffmpeg
• html
• nebius
• nemotron
• node.js
• playwright
• python
• react
• tavily
• typescript
• vite