Project blue unread dot persists after “Mark all as read”

Bug

In the Codex desktop app, a project can keep showing the blue unread indicator after using the project menu’s Mark all as read action.

Steps to reproduce

1. Open the Codex desktop app with a project that shows a blue unread dot.
2. Open the project’s menu in the left sidebar.
3. Select Mark all as read.
4. Observe the project row in the sidebar.

Expected behavior

The project’s blue unread dot disappears once all tasks in the project have been marked as read.

Actual behavior

The blue unread dot remains on the project row. In the observed case, it persisted on the Scout-Control project after running Mark all as read.

Environment

• Codex app: 26.721.41059
• Bundled Codex CLI: codex-cli 0.146.0-alpha.3.1
• macOS: 27.0 (26A5388g)

Related issue

Possibly related to #30855, which reports that project-level Mark all as read can leave visible threads unread. This report focuses specifically on the stale blue indicator on the parent project row.