Dmitriy Kovalenko c60cda34a3 Make observed thread metadata writes atomic and retryable (#59016) ...

## Why

A failed memory-mode update could leave other metadata changes applied. Failed observed metadata writes for paginated threads also need to remain pending so persistence can retry them.

## What changed

- Apply observed metadata, memory mode, and optional recency advancement in one SQLite upsert, preserving monotonic recency.
- Require successful SQLite writes for paginated thread metadata when a state runtime is configured, retaining failed writes for retry.
- Use SQLite busy-retry helpers for read-state writes and immediate transactions.

## Testing

Add regression tests that reject SQLite writes to verify pending metadata survives a failed persist and a rejected memory-mode update leaves existing metadata unchanged. Both tests verify a subsequent retry succeeds.

GitOrigin-RevId: 652bf6ebee0197976852aaf9f096b907697fd590

2026-11-03 00:16:13 +00:00

..

goals_migrations

Preserve thread context when retrying or editing turns (#33211)

2026-07-15 02:35:49 +00:00

logs_migrations

Align SQLite feedback logs with feedback formatter (#13494)

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

memory_migrations

Add memory dual writing and v2 readiness reporting (#43827)

2026-09-08 14:23:23 +00:00

migrations

Add experimental attached thread forks (#56351)

2026-10-23 04:52:47 +00:00

queue_migrations

Dispatch queued messages written by other processes (#39034)

2026-08-17 17:19:46 +00:00

src

Make observed thread metadata writes atomic and retryable (#59016)

2026-11-03 00:16:13 +00:00

thread_history_migrations

Expose and persist turn lineage across the app server (#51415)

2026-10-06 16:56:39 +00:00

BUILD.bazel

Shard state unit tests under Bazel (#37478)

2026-08-07 17:49:48 +00:00

Cargo.toml

Allow NFS database migration with shared file permissions (#57226)

2026-10-26 20:16:30 +00:00