RoboClaw c587214736 fix(codex): stop replaying diagnostic-log notices in chat (#161657) ... Route the two exact process-global Codex diagnostic-log warnings to Gateway warning logs at client receipt, before turn fan-out or replay. Keep other warnings on their existing delivery path and prevent a diagnostic-sink exception from closing the shared transport. Consolidate duplicate logger-failure test setup without removing startup or active-connection coverage (14 fewer test lines). Real native SQLite-lock and logger-fault probes, 83 focused cases, adjacent coverage, changed checks, and the production build support the repair. Logging remains best effort: these operator-only diagnostics do not fall back to chat if Gateway warning logging is disabled or broken. This does not repair native SQLite or update Codex. Worked on by: - @vyctorbrzezowski Co-authored-by: vyctorbrzezowski <51521767+vyctorbrzezowski@users.noreply.github.com>		2026-09-30 19:51:11 -07:00
..
compaction.md	fix(codex): reset native context after history cuts (#155207)	2026-09-21 16:13:35 -07:00
hooks.md	fix(hooks): retry native relay lookup after SQLite contention (#161822)	2026-09-30 05:01:13 -07:00
permissions.md	docs: explain Codex app approval precedence (#155089)	2026-09-24 22:55:34 +00:00
queue-and-feedback.md	fix(codex): stop replaying diagnostic-log notices in chat (#161657)	2026-09-30 19:51:11 -07:00
recovery.md
replies.md	fix: deliver side answers while channel tasks continue (#159416)	2026-09-26 22:14:00 -07:00
sandbox-streaming.md
threads.md
v1-support-contract.md