dsh-fail-logger

LIMITATIONS

Known limitations

- **Only failures that reach the session log**: catastrophic process death during tool execution is out of scope. - **Corrupt state is backed up**: an unparseable `.failures.json` is renamed to `.failures.json.bak-<timestamp>` before reset. - **Non-zero exit codes are not recorded**: see the trigger conditions (DSH semantics, not a plugin bug). - **Dedup is heuristic**: keyed on the normalized first 1-3 lines of text; the same root cause with different wording may split, and different causes with identical wording may merge — acceptable, but be aware. - **Display keeps the original text**: path/username normalization affects the dedup key only; messages display the original (except redaction rules). For stricter privacy, configure `config.redact` per workspace.