# fix\(notifications\): keep a known incident across a failed status fetch \(\#406\) · lucenx/codexbar-plasma

[View on GitCafe](https://git.cafe/lucenx/codexbar-plasma/commit/930d8699d4553ce8d7a1438cd252fd1c69f9b9b5)

Repository: [lucenx/codexbar-plasma](https://git.cafe/lucenx/codexbar-plasma)

Visibility: public

Requested revision: 930d8699d4553ce8d7a1438cd252fd1c69f9b9b5

Requested commit: 930d8699d4553ce8d7a1438cd252fd1c69f9b9b5

Commit: 930d8699d4553ce8d7a1438cd252fd1c69f9b9b5

Tree: 8c39e6552bfb3b5b7896246e46bbd653912c2e40

Author: Simone

Committer: GitHub

## Message

```
fix(notifications): keep a known incident across a failed status fetch (#406)

The official CLI reports a status page it cannot reach as indicator
`unknown` (verified with CodexBar 0.67.0 in a network-isolated sandbox:
"Could not resolve host: status.claude.com"). The status memo stored that
severity over the known incident, keeping only its ID, so the next
successful fetch of the same incident ranked above `unknown` and was
announced again as a worsening.

`statusDecision` now keeps an existing baseline when the current severity
is `unknown`, without notifying. A replacement incident afterwards still
notifies. A first `unknown` with no incident baseline is unchanged.

Documentation: usage guide and the development notification contract
describe the preserved baseline.

Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
```

## Parents

- [3925997cb7c7d13b081bfb126e117bab98c335ed](https://git.cafe/lucenx/codexbar-plasma/commit/3925997cb7c7d13b081bfb126e117bab98c335ed?format=markdown)

[Source at this commit](https://git.cafe/lucenx/codexbar-plasma/tree/930d8699d4553ce8d7a1438cd252fd1c69f9b9b5?format=markdown)