Ruben FiszelandClaude Opus 5.5 e45797cdc2 fix: join a retried fork creation server-side, settle status by the fork's existence ...

A retry from the same user and parent joins the creation in flight instead
of being refused, so clients no longer match the refusal's wording, and
another requester can never adopt it. The status route reports a fork that
exists under its parent as completed, whatever its run's record says. Clients
give up on failing polls after a time window rather than a count, which a
rolling deploy can exhaust.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-09-29 12:37:41 +02:00

..

src

fix: join a retried fork creation server-side, settle status by the fork's existence

2026-09-29 12:37:41 +02:00

Cargo.toml

fix: drain background forks on shutdown and fork in the background from the CLI

2026-09-29 12:06:33 +02:00