Overview
dsh-fail-logger
Community · Topic auto-analysis — Automatically discovered through the dsh-plugin GitHub Topic. Static checks verified a pinned public root bundle contract and committed files without executing third-party code. This is not a human review, security audit, runtime smoke test, publisher identity check, or official endorsement.
Install this bundle from GitHub
The CLI validates the bundle, invokes native DSH, then reports completion.
npx dshpub add Areium/dsh-fail-logger --ref 36a943632b5f6363d76b98ad8c6ad851fc582429Capabilities
What it contributes
README / EN
Package documentation
中文 | English
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.
