jif-oai 5d314f324c Allow Phase 2 memory claims after retry exhaustion (#19809) ...

## Why

The Phase 2 memories job row is only the global lock for the git-backed
memory workspace. Manual memory edits do not enqueue new Stage 1 work,
so a Phase 2 row with `retry_remaining = 0` could be skipped before the
worker ever claimed the lock and generated `phase2_workspace_diff.md`.

That left workspace-only changes unconsolidated after repeated failures,
even when retry backoff had elapsed and the filesystem had real diffable
work.

## What Changed

- Allow `try_claim_global_phase2_job` to claim the Phase 2 lock after
the retry budget is exhausted, while still respecting active `retry_at`
backoff and fresh running leases.
- Treat `SkippedRetryUnavailable` for Phase 2 as backoff-only, and
update the outcome docs to match.
- Clamp Phase 2 retry bookkeeping at zero when failed attempts are
recorded.

## Verification

- Added
`phase2_global_lock_can_be_claimed_after_retry_budget_is_exhausted` to
cover the exhausted-budget lock claim path.
- Ran `cargo test -p codex-state`.

5d314f324c · 2026-04-27 14:58:11 +02:00

History

..

logs_migrations

Align SQLite feedback logs with feedback formatter (#13494)

2026-03-18 22:44:31 +00:00

migrations

Add goal persistence foundation (1 / 5) (#18073)

2026-04-24 20:51:38 -07:00

src

Allow Phase 2 memory claims after retry exhaustion (#19809)

2026-04-27 14:58:11 +02:00

BUILD.bazel

fix bazel build (#13787)

2026-03-06 12:12:20 -08:00

Cargo.toml

Move git utilities into a dedicated crate (#15564)

2026-03-24 13:26:23 -07:00