Skip to content

v2.5.0 — Clear Status & Notifications - #9

Merged
bubblegump30 merged 1 commit into
mainfrom
release/v2.5.0-status
Oct 9, 2026
Merged

bubblegump30 merged 1 commit into
mainfrom
release/v2.5.0-status

Conversation

@bubblegump30

Copy link
Copy Markdown
Owner

The notification button displayed a static message, and failed process/app refreshes could look like empty zero-count inventories. Core center reads now show loading, ready, unavailable, unsupported, administrator-required or failure states, checked/last-success timestamps, and retry actions routed through existing read-only refresh functions. Failed process/app reads preserve the prior successful snapshot with a stale-data label.

Notifications have bounded session history, severity labels, unread count, dismissal, deduplication and clear history. Settings adds persistent Quiet Mode for routine in-app/Windows popups and a separate routine in-app switch. Errors remain visible. Desktop events are forwarded to the connected renderer; quiet-suppressed automation notifications remain recorded. Existing release-specific notification controls still apply.

Only boolean preferences persist. History/status details remain in memory and are not exported. New preference IPC checks the sender and validates booleans, with fixed-path atomic file writes. Retry never invokes system mutations, UAC approval, cleanup, installation or publication.

Validation passed: syntax; status classification/preferences/failure/last-success/retry/concurrency tests; navigation, workspace, dialog, updater, transaction and signed-publisher regressions; whitespace checks. Actual-page DOM fault injection checked quiet info suppression, visible errors, preserved snapshots, retries updating rendered data, escaped details, session history and unread clearing. Native Windows popups/UAC states, pixel layout/high-DPI and Setup/Portable packaging/upgrade acceptance remain unverified; PR is draft pending those checks.

Version: 2.5.0. Additive pt.notifications.v1 / notification-preferences.json; no migration. README retains v2.2.0 as published Stable; new changelog/release notes are unreleased. Guarded manual signed publisher is prepared. No release has been published.

@bubblegump30
bubblegump30 marked this pull request as ready for review October 9, 2026 02:32
@bubblegump30
bubblegump30 merged commit 7f421c7 into main Oct 9, 2026
2 checks passed
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-09T02:35:19.978833Z 6252878 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant