Document resilient reports and remove obsolete warning material
This commit is contained in:
@@ -2,13 +2,13 @@
|
||||
|
||||
**Last updated:** 2026-09-24
|
||||
|
||||
The documentation migration identified these existing behaviors for separate
|
||||
product consideration. Implementation status and any selected direction are noted
|
||||
below; this document does not claim that runtime changes have landed.
|
||||
The documentation migration identified existing behaviors for separate product
|
||||
consideration. The resilience implementation resolved the diagnostics-retention
|
||||
question; the input-timestamp question remains open.
|
||||
|
||||
- Decide whether the `never` retention selection should delete successful-run
|
||||
diagnostics; current behavior is documented in
|
||||
[operations](../operations.md#retention-behavior).
|
||||
- Resolved: legacy `auto`/`always`/`never` retention settings were removed.
|
||||
Debug is explicitly enabled with `diagnostics.debug` or `--debug`, creates no
|
||||
directory when disabled, and retains its directory on every outcome when enabled.
|
||||
- Resolved: [configuration](../config.md) now treats explicit zero as disabling
|
||||
transient retries or structural repair independently; PromptKit performs both.
|
||||
- Decide whether missing or null input timestamps should be rejected; current
|
||||
|
||||
Reference in New Issue
Block a user