Dmitriy Kovalenko caae161dd0 Keep thread storage available when diagnostic logs fail (#60466) ...

## Why

Failure to open the diagnostic logs database should not disable thread storage or database-only history listing. Thread deletion must still preserve saved conversations when diagnostic log cleanup cannot complete.

## What changed

- Allow state initialization to continue after non-corruption errors opening the logs database, while preserving corruption recovery.
- Report the original diagnostic database error after tracing is installed in the TUI and app server, and return it from log operations.
- Reject thread deletion before destructive cleanup when diagnostic storage failed to initialize.
- Continue periodic cleanup of legacy logs when the current logs database is unavailable.

## Testing

Extend coverage for unavailable log directories, database-only history listing, startup diagnostics, deletion preserving saved conversations, corrupt log headers, and periodic legacy log cleanup during a diagnostic storage outage.

GitOrigin-RevId: a5184580ae6c39ed0c4eefa8cb48ee7731a991c3

2026-11-09 23:22:08 +00:00

..

common

Stabilize cross-platform tests and directory-change fork permissions (#59369)

2026-11-04 09:51:28 +00:00

suite

Keep thread storage available when diagnostic logs fail (#60466)

2026-11-09 23:22:08 +00:00

all.rs

[codex] Use expect in integration tests (#28441)

2026-06-15 21:53:47 -07:00

prompt_prefix.rs

Disable bundled skills in the prompt-prefix comparison test (#60017)

2026-11-07 00:54:03 +00:00